How to use options in nuxt.config.js

How do I use the options? I tried this in nuxt.config.js:
    serverMiddleware: [
        [
            "redirect-ssl",
            {
                redirect: process.env.SSL_REDIRECT_ENABLED === "true"
            }
        ]
    ],

But I get error ServerMiddleware should expose a handle: undefined.

Hi. Sorry for late response. I've updated nuxt.js section: https://github.com/nuxt-contrib/redirect-ssl#using-with-nuxtjs (please notice package version is bumped to 2)


Copied run{client,server}.bat to the content repo

Because this is apparently the right thing way to launch them (?)

Because this is apparently the right thing way to launch them (?)

I mean it's convenient if you use a file manager often I guess, but they don't do much more than just launching the exes directly.

Tbh I already keep them copied and ignored in content as well so this is pretty much necessary


highlight both username in password if login error

before

after

LGTM

Coverage remained the same at 88.053% when pulling 8e91daffe4e223c88116dd30e9d44ca14e152767 on vxsx:feature/login-error into 0c482a9bfecaa3e56bcd085f3b10a07feb80822c on divio:develop.


[tabs]: add custom selected item tab style

add support to customize a selected tab item in case you may want to have custom background for selected tab items

Had an issue after upgrading to the 3.26.30 because of this commit. I've a customized tabBarStyle and I want this style applied if I haven't specified a tabBarSelectedItemStyle for the selected item not the 'white' background. Can we replace the current line by this one or do I need to add tabBarSelectedItemStyle to every tabbar I use?
selectedIconStyle={[{ backgroundColor: 'white' }, state.tabBarStyle, state.tabBarSelectedItemStyle]}

I had the same experience and I had to null out the backgroundColor.  I don't think we need the default styling at all.  What about just:
            style={state.tabBarStyle}
            selectedIconStyle={state.tabBarSelectedItemStyle}

PR here: https://github.com/aksonov/react-native-router-flux/pull/839


[(LIVE.EPL)] Chelsea vs Arsenal Live Streams Free Premier League On Tv Channel 10 NOV 2024

Chelsea vs Arsenal live stream: English Premier League 2024 prediction, TV channel, how to watch, start time, odds Arsenal vs Chelsea : How to watch, schedule, live stream info, game time, TV channel
Arsenal v Chelsea live score and video online live stream starts on 10 November 2024 at 10:45 time in English Premier League - Rugby Union. English Premier League 2024 leaders Chelsea travel to Ellis Park, Johannesburg on Saturday with manager Mikel Arteta bidding to extend a surprising undefeated run away to Arsenal.
The Gunners won on each of their last two visits to west Melbourne in the top flight without particularly imposing themselves on their opposition, this time it may well be different for a side who have established themselves as a surprising early season contender for major honors.
Event details:
NAME: Chelsea vs Arsenal
DATE: 10 Nov 2024
TIME: 12:30 UTC .
VENUE: Stadium MK in Milton Keynes, Buckinghamshire United Kingdom
Arsenal, meanwhile, have work to do if they are to drag Chelsea into the battle for top four, rather than the title. Lose on Saturday and they will trail their rivals by 31 points, a sizeable gap to make up even with two-thirds of the season left to go.
Here is how you can watch the match and what you need to know: Arsenal and Chelsea are meeting up for their first leg of the season at 8.45 PM AEDT, 9.45 PM NZT on Saturday at Ellis Park, Johannesburg. The teams split their matchups last year, with Arsenal winning the first 2-0 on the road and Chelsea taking the second 4-2. Arsenal are taking on Melbourne rivals Chelsea at Ellis Park, Johannesburg as the Blues aim to close the 31-point gap between the two clubs in the English Premier League 2024 Saturday, 29 July 2024.
Arsenal had been going along nicely under Graham Potter until a chastening defeat at his former club Chelsea last weekend, and now face two tricky matches – against Chelsea and Arsenal – before the English Premier League break. The Gunners are looking to reach the English Premier League on top of the table and got back on track last weekend with a 5-0 win over Chelsea, having slipped to a 1-1 draw at Chelsea in their previous match. Chelsea won both of the past two corresponding fixtures away at Arsenal, earing a 4-2 victory last season Saturday, 29 July 2024.
Old foes and former colleagues will reunite at Ellis Park, Johannesburg on Saturday lunchtime as Arsenal tackle Chelsea in a mouth-watering English Premier League 2024 Melbourne Chelsea . Both sides enter the game on the back of continental successes, as the Blues got the better of Dinamo Zagreb 2-1 in the English Premier League 2024, while the Gunners advanced to the last 01 of the English Premier League 2024.
Winning in Europe is always the perfect tonic after a demoralising domestic defeat, especially one which saw Chelsea teach former manager Graham Potter a footballing lesson in a 4-1 Amex romping, but Arsenal were made to work for their success over Dinamo Zagreb. Electing to name a strong lineup despite already steering his side through as group winners, Potter witnessed Bruno Petkovic steal in and open the scoring after just seven minutes, but Raheem Sterling and debutant Denis Zakaria completed a much-needed turnaround for the Blues in the English capital.
The Blues' stellar defensive streak under Potter may have been wiped out, but suffering just one defeat in 01 games is far from the worst start for the Englishman, although his side do have some ground to make up in the English Premier League 2024 table as they lie in sixth position, three points behind Arsenal in fourth with a game in hand.
It would take results going their way and a 12-goal swing for Arsenal to rise into the English Premier League 2024 spots this weekend, but Ellis Park, Johannesburg has been kind to the Blues in recent memory, as they are unbeaten in 12 consecutive matches in all competitions in front of their own fans. However, Chelsea were the most recent team to overcome Arsenal on their own patch, and Ellis Park, Johannesburg has been a happy hunting ground for the North Melbourne club in recent memory, so taking advantage of their extra 24 hours' worth of rest will be of paramount importance to Potter and co.
In contrast, Chelsea sought to recover from a European defeat with a English Premier League 2024 win last weekend, and the Gunners certainly demonstrated a clinical edge that has been absent more often than not recently, putting five past Chelsea without rEnglish Premier League 2024y even after Bukayo Saka came off injured.
However, the Gunners' inability to kill games off when a goal to the good reared its ugly head in the English Premier League 2024 this week, as Kieran Tierney's sweetly-struck half-volley put Chelsea ahead against FC Zurich, but they nevertheless held on for a nervy 1-0 win which sent them straight through to the last 01.
Avoiding an extra playoff tie against an eliminated English Premier League 2024 club is a touch of gold for Chelsea, who enter the weekend still two points clear of Arsenal at the top of the English Premier League 2024 table, but they could be knocked down to second by Saturday if the champions beat Chelsea. All five of the points that Chelsea have dropped in the English Premier League 2024 this season have come on the road, but they nevertheless remain the division's best-performing away side this term and have only conceded four goals on rival turf so far - the best record of its kind in the league.
Arteta has led Chelsea to two consecutive triumphs at Ellis Park, Johannesburg in the last two seasons - with a 2-0 win for Arsenal at the Emirates sandwiched in between - and a new club record could also be set for the Gunners, who are aiming to win three successive English Premier League 2024 Melbourne derbies away from home without conceding for the very first time. If Arsenal did not already have enough defensive absentees to worry about with long-term knee victims Wesley Fofana and Reece James - as well as midfield duo N'Golo Kante (thigh) and Carney Chukwuemeka (hamstring) - Ben Chilwell had to come off with a hamstring injury in the win over Zagreb.
The sight of the left-back limping off the pitch was bad news for both Arsenal and Arsenal fans, who will now have to await for the results of a scan, but Chilwell will definitely be absent this weekend. Potter has already ruled Kepa Arrizabalaga out of contention too, so Edouard Mendy will keep his place in goal, and Mateo Kovacic should be fine to return to the engine room after missing out as a precaution in midweek with a tight calf.
Zakaria's strong debut ended with a minor contact injury, which should not rule him out of this game, but Potter may be hesitant to throw the Juventus loanee in the deep end and give him his first English Premier League 2024 start against the league leaders, so Kovacic's return to the first XI would not be a surprise.
As for Chelsea, fans witnessed the familiar yet painful sight of Takehiro Tomiyasu coming off injured in the dying embers of the win over Zurich. The severity of the defender's muscular issue is still unclear, but it would be a shock to see him line up here. Emile Smith Rowe - who has scored in each of Chelsea 's last two wins at Ellis Park, Johannesburg - is still out after undergoing groin surgery, and a problem in the same area could also force Matt Turner out of contention, but Arteta was handed two major boosts in midweek.
The injury that Saka sustained against Chelsea was only a minor one, and he was able to come on as a substitute in the English Premier League 2024, while Oleksandr Zinchenko was Manu Arsenal vs Flying Chelseaansly back in the squad after a troublesome calf injury. Zinchenko did not earn any minutes as Tierney produced a man-of-the-match performance, which has certainly given Arteta food for thought here, but the Ukrainian's ability to help overload the midfield could ultimately win over, assuming he is deemed fit enough to start.
Arsenal (1-15): possible starting lineup: Angus Bell, David Porecki, Allan Alaalatoa (c), Nick Frost, Will Skelton, Jed Holloway, Tom Hooper, Rob Valetini, Tate McDermott, Carter Gordon, Marika Koroibete, Samu Kerevi, Jordan Petaia, Mark Nawaqanitawase, Andrew Kellaway. Reserves: Jordan Uelese, James Slipper, Taniela Tupou, Richie Arnold, Rob Leota, Nic White, Quade Cooper, Izaia Perese.
Chelsea (1-15): possible starting lineup: Ethan de Groot, Codie Taylor, Tyrel Lomax, Brodie Retallick, Scott Barrett, Shannon Frizell, Dalton Papali'i, Ardie Savea (c), Aaron Smith, Richie Mo'unga, Mark Telea, Jordie Barrett, Rieko Ioane, Will Jordan, Beauden Barrett. Reserves: Samisoni Taukei'aho, Ofa Tu'ungafasi, Nepo Laulala, Samuel Whitelock, Luke Jacobson, Cam Roigard, Anton Lienert-Brown, Caleb Clarke.
We say: Arsenal 1-2 Chelsea Even if Chelsea can find the back of the net early doors at Ellis Park, Johannesburg - as they have done throughout the season - failure to put the game to bed would open the door for the Blues to dent the Gunners' early title aspirations.
Potter is yet to suffer defeat at Ellis Park, Johannesburg, but Chelsea have fond memories of their recent trips to West Melbourne and were able to rest a number of key first-team stars in midweek, so we expect the Gunners to take advantage of the Blues' d English Premier League 2024 eted defence and travel back to the Emirates with a hard-earned three points.
Arsenal vs Chelsea live Chelsea vs Arsenal all matches Arsenal vs Chelsea 3-1 Arsenal vs Chelsea 2-6 Arsenal vs Chelsea 2024 Arsenal vs Chelsea 2024 Arsenal vs Chelsea next match Arsenal vs Chelsea history where to watch Chelsea vs Arsenal Arsenal vs Chelsea live comments Chelsea v Arsenal tv usa Chelsea vs Arsenal today Chelsea vs Arsenal line up Chelsea tv live stream free onlined

cbcb

vcv


Some preparations

Some preparations before we start with the real work. Here is what happened:

resolved some PEP8 issues
added many type hints (not complete yet)
removed unused variables
... and other minor issues

Looks good to me!


Use fast-uuid for efficient toString and fromString calls in runtime

It is a small library without any dependencies: https://github.com/jchambers/fast-uuid

As we all migrate onto java 9 plus I think this becomes unnecessary.


Integration not appearing

Hello,
I installed the latest version from HACS (0.2.1) and I don't see any HA integration named govee in HA. I tried to restart the OS for many times but with the same result. I'm using hassio, version core-2021.11.1 on a rPI 4. I don't have any logs to provide since doesn't seems to throw any error at the installation of the HACS plugin.

I got the same issue

I rechecked and now seems to work. Not sure what was the problem. The plugin is the same version.

Same for me, installed via HACS, go to configuration, add integration and Govee is not in the list or if I search for it.

Same for me, installed via HACS, go to configuration, add integration and Govee is not in the list or if I search for it.

So you need to  “generate” the URL to add this integration:
Click here: Link to Integrations: Add integration – My Home Assistant 28

Same for me, installed via HACS, go to configuration, add integration and Govee is not in the list or if I search for it.

So you need to “generate” the URL to add this integration:
Click here: Link to Integrations: Add integration – My Home Assistant 28

Thanks a lot. Same problem, now solved

This happens often for integrations installed via HACS and can usually be solved by deleting browser cache and reloading the page.

Same for me, installed via HACS, go to configuration, add integration and Govee is not in the list or if I search for it.

So you need to “generate” the URL to add this integration:
Click here: Link to Integrations: Add integration – My Home Assistant 28

I have the same issue as above, but this link didn't solve things for me.
I've successfully added the govee add-on via HACS. It shows in the HACS->Integrations page within my Home Assistant. But if I go to Configuration -> Integrations -> Add Integration and search for govee, it doesn't show up.
I've restarted HA multiple times, tried clearing my browser cache/used a different browser. It's just not there...
Any idea what to try next? Thanks!

I am also having the same problem.
When clicking the generated link, it acts to setup Govee, I say yes and then get:
Error - Config flow could not be loaded
Logs show:
Logger: homeassistant.config_entries
Source: config_entries.py:711
First occurred: 20:45:56 (1 occurrences)
Last logged: 20:45:56

Cannot find integration govee

I've cleared browser cache, logged out and back in, and restarted HA multiple times.

Edit: Well not sure why, but re-installing the integration from HACS, then restarting, and then trying to add it again worked.

And now for me too! How strange. One thing that I did differently this time was to log out -> log in at each step. So to be specific I:

Uninstalled the integration via HACS
Restarted HA
Logged out of HA
Logged back in to HA
Hard refreshed (using Chrome on a Mac)
Installed the integration via HACS
Restarted HA
Logged out of HA
Logged back in to HA
Hard refreshed (using Chrome on a Mac)
Finally it shows up as an Integration

Oddly, I had tried via an incognito window before (requiring a log-in), but that didn't work. Maybe something about the act of logging-out clears some needed cache/cookies?
Anyway. Please to have this finally working. Thanks for the tip nathang21 !

Seems original poster has it solved, it's sometimes a hassle. Usually installing with hacs and waiting for some minutes does the trick. Also try clearing browser cache, restarting home assistant.


Unable to save new tasks

Description
Issue related to saving new tasks in Codabench. The issue is explained step-by-step in this document:
https://docs.google.com/document/d/1-InYnhHznnU0nqGfxfmHKYfSTsLX_klB4V32Uf08SNQ/edit?usp=sharing
Error logs
django-1  | Internal Server Error: /api/competitions/3863/
django-1  | Traceback (most recent call last):
django-1  |   File "/usr/local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner
django-1  |     response = get_response(request)
django-1  |   File "/usr/local/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response
django-1  |     response = self.process_exception_by_middleware(e, request)
django-1  |   File "/usr/local/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response
django-1  |     response = wrapped_callback(request, *callback_args, **callback_kwargs)
django-1  |   File "/usr/local/lib/python3.9/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
django-1  |     return view_func(*args, **kwargs)
django-1  |   File "/usr/local/lib/python3.9/site-packages/rest_framework/viewsets.py", line 116, in view
django-1  |     return self.dispatch(request, *args, **kwargs)
django-1  |   File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 495, in dispatch
django-1  |     response = self.handle_exception(exc)
django-1  |   File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 455, in handle_exception
django-1  |     self.raise_uncaught_exception(exc)
django-1  |   File "/usr/local/lib/python3.9/site-packages/rest_framework/views.py", line 492, in dispatch
django-1  |     response = handler(request, *args, **kwargs)
django-1  |   File "/usr/local/lib/python3.9/site-packages/rest_framework/mixins.py", line 84, in partial_update
django-1  |     return self.update(request, *args, **kwargs)
django-1  |   File "/app/src/apps/api/views/competitions.py", line 311, in update
django-1  |     self.perform_update(serializer)
django-1  |   File "/app/src/apps/api/views/competitions.py", line 590, in perform_update
django-1  |     self.run_new_task_submissions(instance.phases.get(pk=phase_id), new_tasks)
django-1  |   File "/app/src/apps/api/views/competitions.py", line 563, in run_new_task_submissions
django-1  |     leaderboard=submission.children.first().leaderboard,
django-1  | AttributeError: 'NoneType' object has no attribute 'leaderboard'

@Didayolo jjust checking in on this!
We are about to start our evaluation phase and are still facing this issue.
We tried creating a new Codabench from scratch with all the tasks we wanted, and it worked. However, we don’t want to migrate to a new Codabench as we already have many participants (421, the largest on Codabench to date).

@ihsaan-ullah May have a clue about this problem. Please keep us updated.

When you update a competition by adding a new task to a phase, the following happens:

we fetch all submissions that are parent submissions
we loop over all these submissions and we find missing tasks (missing task = all_tasks_of_this_phase - submission.children.tasks).
we then create a new submission which is a child submission with this new task or missing task
Problem occurs in the leaderboard assigning

leaderboard=submission.children.first().leaderboard

Error says AttributeError: 'NoneType' object has no attribute 'leaderboard'. children.first is None. I am checking why it is None


INTLY-2347 Don't use Service Instance for AMQ Online

Verification:

Run the server locally against an OpenShift 3 cluster

OPENSHIFT_HOST=<openshift-host> SSO_ROUTE=<sso-route> GITEA_TOKEN=<gitea-token> GITEA_HOST=<gitea-host> yarn start:dev
You can get the values for the above command with with oc get dc tutorial-web-app -n webapp -o yaml

Wait for localhost:3006 to load in your browser
Login as evals01, for example
Start walkthrough 1 (AMQ Online and Fuse Online)
Ensure AMQ Online is provisioned and shown in the loading screen

oc get addressspace --all-namespaces has an AddressSpace named after the user
oc get messaginguser --all-namespaces has a MessagingUser in the created AddressSpace

Go through Walkthrough 1 and ensure it still works as expected
Login as a different user, provision AMQ Online from the right-hand side of the main page

@leaannegaffney @dimitraz Mind taking a look?

:eyes:


Complete PFA DSL for built-in function library

I am in the process of adding the missing functions, let me know if this has been done

I'm going to code generate the Function Lib DSL from here: https://github.com/datamininggroup/pfa/blob/master/libfcns.xml

That would be a great solution, thanks!


Community forum

Describe the feature
Creating a platform for farmers to share their experiences success storiesand challenges fostering a supportive community where knowledge and real hands on practices can be exchanged as coming from a agriculture background I think having or acknowledging someone real experience gives good idea and good understanding also as of giving taking back in the form of feedback or the real experience matters most
Add ScreenShots
Following the above feature idea I think the key components like discussion categories such as crop cultivation livestock management sustainability practices etc
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign me i would like to work on it @Suchitra-Sahoo

What is the update?

Hello mam sorry for not updating I am working on it .
On Wed, 22 May 2024, 21:10 Suchitra Sahoo, @.***> wrote:

What is the update?
—
Reply to this email directly, view it on GitHub
https://github.com/Suchitra-Sahoo/AgriLearnNetwork/issues/135#issuecomment-2125112856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHGKAUIXNRYIXVVVT4DGG7TZDS36BAVCNFSM6AAAAABHSAYOXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRVGEYTEOBVGY
.
You are receiving this because you were assigned.Message ID:
@.***>


Once suspend, never back the display output until reboot since NixOS 24.11

Since GH-943
Both HDMI and DisplayPort. I'm using HDMI switcher, but directly connecting DisplayPort having same issue
Partially similar of GH-894

Want https://github.com/kachick/dotfiles/issues/802 for addressing these issues

Clicked power button does not resolve this, so looks different of https://github.com/kachick/dotfiles/issues/894 🤔
This is a much blocker for daily driver use...

Also happened in moss...

https://discord.com/channels/568306982717751326/741347063077535874/1305036722228166719
https://discord.com/channels/568306982717751326/1274321389989400577/1306711297714290752

https://gitlab.freedesktop.org/drm/amd/-/issues/3208#note_2681390
https://github.com/NixOS/nixpkgs/issues/170429
https://github.com/NixOS/nixpkgs/issues/223690#issuecomment-1491931884
https://git.dolansoft.org/lorenz/memreserver

🙄 I have 2 NixOS installed devices, both are powered by AMD APU...

https://github.com/NixOS/nixpkgs/pull/225819 👁

https://github.com/search?q=repo%3Atorvalds%2Flinux+suspend+amd&type=commits

Much activity...

uname --kernel-release
6.6.63

Am I using old kernel even after NixOS 24.11...? :thinking:
https://github.com/torvalds/linux/releases/tag/v6.6

https://nixos.wiki/wiki/Linux_kernel
https://en.wikipedia.org/wiki/Linux_kernel_version_history

https://wiki.archlinux.jp/index.php/電源管理/サスペンドとハイバネート
https://wiki.archlinux.jp/index.php/AMDGPU

> journalctl --system --reverse | grep user.slice
12月 02 00:16:24 algae systemd-sleep[3606]: Failed to freeze unit 'user.slice': Connection timed out
12月 02 00:14:27 algae systemd[1]: user.slice: Consumed 15min 16.390s CPU time, 12G memory peak, 8.4G read from disk, 1.1G written to disk, 1M incoming IP traffic, 451.5K outgoing IP traffic.
12月 01 23:33:12 algae systemd-sleep[3742]: Failed to freeze unit 'user.slice': Connection timed out
12月 01 23:31:12 algae systemd[1]: user.slice: Consumed 10min 16.670s CPU time, 8.7G memory peak, 5.1G read from disk, 842.7M written to disk, 5.5M incoming IP traffic, 826.7K outgoing IP traffic.
12月 01 00:18:24 algae systemd-sleep[9858]: Failed to freeze unit 'user.slice': Connection timed out
11月 29 02:48:05 algae systemd-sleep[223576]: Failed to freeze unit 'user.slice': Connection timed out
11月 26 04:16:05 algae systemd-sleep[278606]: Failed to freeze unit 'user.slice': Connection timed out
11月 25 22:22:11 algae systemd-sleep[209444]: Failed to freeze unit 'user.slice': Connection timed out
11月 25 12:24:08 algae systemd[1]: user.slice: Consumed 37.146s CPU time, 1.5G memory peak, 1.7G read from disk, 26.2M written to disk, 2.5M incoming IP traffic, 43.4K outgoing IP traffic.
11月 25 12:15:43 algae systemd[1]: user.slice: Consumed 3min 30.100s CPU time, 3.6G memory peak, 2.6G read from disk, 92.1M written to disk, 10.3M incoming IP traffic, 1.1M outgoing IP traffic.
11月 25 12:02:21 algae systemd[1]: user.slice: Consumed 34min 51.706s CPU time, 9.3G memory peak, 7.5G read from disk, 2G written to disk, 15.5K incoming IP traffic, 13.8K outgoing IP traffic.
11月 25 10:33:45 algae systemd-sleep[6472]: Successfully thawed unit 'user.slice'.
11月 25 03:57:48 algae systemd-sleep[6472]: Successfully froze unit 'user.slice'.
11月 25 03:40:31 algae systemd[1]: user.slice: Consumed 7min 40.098s CPU time, 5.1G memory peak, 3G read from disk, 381.6M written to disk, 202.4M incoming IP traffic, 3.9M outgoing IP traffic.
11月 24 20:10:31 algae systemd-sleep[215088]: Failed to freeze unit 'user.slice': Connection timed out
11月 24 09:21:36 algae systemd-sleep[84593]: Successfully thawed unit 'user.slice'.
11月 24 01:26:01 algae systemd-sleep[84593]: Successfully froze unit 'user.slice'.
11月 23 22:31:24 algae systemd-sleep[2472]: Successfully thawed unit 'user.slice'.
11月 23 22:25:46 algae systemd-sleep[2472]: Successfully froze unit 'user.slice'.
11月 23 10:03:00 algae systemd[1]: user.slice: Consumed 14min 37.368s CPU time, 6.1G memory peak, 5G read from disk, 788.1M written to disk, 56.9M incoming IP traffic, 7.2M outgoing IP traffic.
11月 23 02:41:54 algae systemd[1]: user.slice: Consumed 4h 52min 36.824s CPU time, 23.1G memory peak, 16.8G read from disk, 9.2G written to disk, 77.7M incoming IP traffic, 5.7M outgoing IP traffic.
11月 22 19:55:19 algae systemd[1]: user.slice: Consumed 4h 26min 4.396s CPU time, 24.3G memory peak, 25.2G read from disk, 11.8G written to disk, 25K incoming IP traffic, 14.9K outgoing IP traffic.
11月 22 16:47:28 algae systemd-sleep[113415]: Successfully thawed unit 'user.slice'.
11月 22 13:16:54 algae systemd-sleep[113415]: Successfully froze unit 'user.slice'.
11月 22 02:39:54 algae systemd-sleep[668762]: Failed to freeze unit 'user.slice': Connection timed out
11月 21 11:00:47 algae systemd-sleep[347911]: Successfully thawed unit 'user.slice'.
11月 21 03:29:05 algae systemd-sleep[347911]: Successfully froze unit 'user.slice'.
11月 20 15:38:46 algae systemd-sleep[73890]: Successfully thawed unit 'user.slice'.
11月 20 14:23:21 algae systemd-sleep[73890]: Successfully froze unit 'user.slice'.
11月 20 09:32:02 algae systemd-sleep[6339]: Successfully thawed unit 'user.slice'.
11月 20 02:52:52 algae systemd-sleep[6339]: Successfully froze unit 'user.slice'.
11月 20 02:44:11 algae systemd[1]: user.slice: Consumed 1h 29min 9.642s CPU time, 20.4G memory peak, 9.5G read from disk, 12.4G written to disk, 2.7G incoming IP traffic, 60.5M outgoing IP traffic.
11月 17 01:07:35 algae kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=user.slice,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-kitty-1696066.scope,task=nix,pid=2482265,uid=1001
11月 17 00:37:21 algae kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=nix-daemon.service,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-google\x2dchrome-1699315.scope,task=chrome,pid=1991163,uid=1001
11月 11 21:11:24 algae systemd[1]: user.slice: Consumed 6min 23.843s CPU time, 5.0G memory peak, 0B memory swap peak, received 71.4M IP traffic, sent 2.2M IP traffic.
10月 28 16:10:46 algae systemd[1]: user.slice: Consumed 1min 11.971s CPU time, 4.7G memory peak, 0B memory swap peak, received 2.4M IP traffic, sent 276.7K IP traffic.
10月 28 16:05:25 algae systemd[1]: user.slice: Consumed 1h 31min 16.641s CPU time, 13.0G memory peak, 0B memory swap peak, received 554.7M IP traffic, sent 25.5M IP traffic.
10月 28 03:25:30 algae systemd[1]: user.slice: Consumed 6min 1.543s CPU time, 6.1G memory peak, 0B memory swap peak, received 17.2M IP traffic, sent 1.9M IP traffic.
10月 28 03:08:38 algae systemd[1]: user.slice: Consumed 2h 33min 9.057s CPU time, 16.8G memory peak, 0B memory swap peak, received 712.8M IP traffic, sent 47.9M IP traffic.
10月 27 19:48:35 algae systemd[1]: user.slice: Consumed 44min 45.847s CPU time, 9.8G memory peak, 0B memory swap peak, received 365.8M IP traffic, sent 12.1M IP traffic.
10月 27 16:58:37 algae systemd[1]: user.slice: Consumed 12h 6min 29.877s CPU time, 26.6G memory peak, 0B memory swap peak, received 8.1G IP traffic, sent 264.5M IP traffic.
10月 23 21:32:10 algae systemd[1]: user.slice: Consumed 6min 24.434s CPU time, received 67.3M IP traffic, sent 2.4M IP traffic.
10月 23 21:18:24 algae systemd[1]: user.slice: Consumed 4min 28.315s CPU time, 7.4G memory peak, 0B memory swap peak, received 57.5M IP traffic, sent 1.1M IP traffic.
10月 23 21:08:31 algae systemd[1]: user.slice: Consumed 2h 51min 34.014s CPU time, 18.5G memory peak, 0B memory swap peak, received 1.2G IP traffic, sent 54.9M IP traffic.
10月 22 13:50:41 algae systemd[1]: user.slice: Consumed 4h 40min 48.754s CPU time, received 1.4G IP traffic, sent 66.2M IP traffic.
10月 21 20:33:32 algae systemd[1]: user.slice: Consumed 16h 57min 42.062s CPU time, received 1.2G IP traffic, sent 89.1M IP traffic.
10月 20 23:46:08 algae systemd[1]: user.slice: Consumed 1h 44min 29.280s CPU time, 11.8G memory peak, 0B memory swap peak, received 248.6M IP traffic, sent 24.6M IP traffic.
10月 20 17:23:07 algae systemd[1]: user.slice: Consumed 11h 8min 11.291s CPU time, 30.7G memory peak, 0B memory swap peak, received 11.5G IP traffic, sent 216.5M IP traffic.
10月 11 11:11:05 algae systemd[1]: user.slice: Consumed 54min 56.053s CPU time, 8.4G memory peak, 0B memory swap peak, received 332.4M IP traffic, sent 14.5M IP traffic.
10月 10 22:05:25 algae systemd[1]: user.slice: Consumed 18.615s CPU time, received 28.9K IP traffic, sent 4.1K IP traffic.
10月 10 22:02:44 algae systemd[1]: user.slice: Consumed 1h 12min 7.498s CPU time, 13.4G memory peak, 0B memory swap peak, received 735.6M IP traffic, sent 22.6M IP traffic.
10月 04 02:08:44 algae systemd[1]: user.slice: Consumed 1h 42min 57.560s CPU time, 15.5G memory peak, 0B memory swap peak, received 2.4G IP traffic, sent 35.8M IP traffic.
10月 03 20:22:33 algae systemd[1]: user.slice: Consumed 5h 10min 35.198s CPU time, received 200.6M IP traffic, sent 20.0M IP traffic.
10月 03 13:31:25 algae systemd[1]: user.slice: Consumed 2h 11min 26.023s CPU time, 16.3G memory peak, 0B memory swap peak, received 805.0M IP traffic, sent 41.3M IP traffic.

https://github.com/systemd/systemd/issues/33083 ? :eyes:
> journalctl --system --reverse | grep -i 'Freezing user'
12月 02 00:16:30 algae kernel: Freezing user space processes completed (elapsed 0.001 seconds)
12月 02 00:16:30 algae kernel: Freezing user space processes
12月 01 23:33:14 algae kernel: Freezing user space processes completed (elapsed 0.001 seconds)
12月 01 23:33:14 algae kernel: Freezing user space processes
12月 01 23:33:13 algae kernel: Freezing user space processes completed (elapsed 0.001 seconds)
12月 01 23:33:13 algae kernel: Freezing user space processes
12月 01 10:31:47 algae kernel: Freezing user space processes completed (elapsed 0.001 seconds)
12月 01 10:31:47 algae kernel: Freezing user space processes
11月 30 21:45:35 algae kernel: Freezing user space processes completed (elapsed 0.016 seconds)
11月 30 21:45:35 algae kernel: Freezing user space processes
11月 26 08:32:44 algae kernel: Freezing user space processes completed (elapsed 0.018 seconds)
11月 26 08:32:44 algae kernel: Freezing user space processes
11月 25 23:02:32 algae kernel: Freezing user space processes completed (elapsed 0.018 seconds)
11月 25 23:02:32 algae kernel: Freezing user space processes
11月 25 10:33:45 algae kernel: Freezing user space processes completed (elapsed 0.002 seconds)
11月 25 10:33:45 algae kernel: Freezing user space processes
11月 24 20:29:11 algae kernel: Freezing user space processes completed (elapsed 0.009 seconds)
11月 24 20:29:11 algae kernel: Freezing user space processes
11月 24 09:21:36 algae kernel: Freezing user space processes completed (elapsed 0.002 seconds)
11月 24 01:26:01 algae kernel: Freezing user space processes
11月 23 22:31:24 algae kernel: Freezing user space processes completed (elapsed 0.001 seconds)
11月 23 22:31:24 algae kernel: Freezing user space processes
11月 22 16:47:28 algae kernel: Freezing user space processes completed (elapsed 0.002 seconds)
11月 22 16:47:28 algae kernel: Freezing user space processes
11月 22 09:35:20 algae kernel: Freezing user space processes completed (elapsed 0.002 seconds)
11月 22 09:35:20 algae kernel: Freezing user space processes
11月 21 11:00:47 algae kernel: Freezing user space processes completed (elapsed 0.002 seconds)
11月 21 11:00:47 algae kernel: Freezing user space processes
11月 20 15:38:46 algae kernel: Freezing user space processes completed (elapsed 0.001 seconds)
11月 20 15:38:46 algae kernel: Freezing user space processes
11月 20 09:32:02 algae kernel: Freezing user space processes completed (elapsed 0.002 seconds)
11月 20 09:32:02 algae kernel: Freezing user space processes
11月 19 08:57:28 algae kernel: Freezing user space processes failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 08:57:08 algae kernel: Freezing user space processes
11月 19 08:57:08 algae kernel: Freezing user space processes failed after 20.006 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 08:56:48 algae kernel: Freezing user space processes
11月 19 06:56:47 algae kernel: Freezing user space processes failed after 20.002 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 06:56:47 algae kernel: Freezing user space processes
11月 19 06:56:27 algae kernel: Freezing user space processes failed after 20.005 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 06:56:27 algae kernel: Freezing user space processes
11月 19 04:56:06 algae kernel: Freezing user space processes failed after 20.001 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 04:56:06 algae kernel: Freezing user space processes
11月 19 04:55:46 algae kernel: Freezing user space processes failed after 20.002 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 04:55:46 algae kernel: Freezing user space processes
11月 19 02:55:25 algae kernel: Freezing user space processes failed after 20.003 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 02:55:25 algae kernel: Freezing user space processes
11月 19 02:55:05 algae kernel: Freezing user space processes failed after 20.006 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 19 02:54:45 algae kernel: Freezing user space processes
11月 18 20:48:45 algae kernel: Freezing user space processes failed after 20.002 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 20:48:25 algae kernel: Freezing user space processes
11月 18 20:48:25 algae kernel: Freezing user space processes failed after 20.009 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 20:48:05 algae kernel: Freezing user space processes
11月 18 10:39:55 algae kernel: Freezing user space processes failed after 20.000 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 10:39:35 algae kernel: Freezing user space processes
11月 18 10:39:35 algae kernel: Freezing user space processes failed after 20.002 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 10:39:15 algae kernel: Freezing user space processes
11月 18 08:19:03 algae kernel: Freezing user space processes failed after 20.008 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 08:18:43 algae kernel: Freezing user space processes
11月 18 08:18:43 algae kernel: Freezing user space processes failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 08:18:23 algae kernel: Freezing user space processes
11月 18 06:18:22 algae kernel: Freezing user space processes failed after 20.005 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 06:18:02 algae kernel: Freezing user space processes
11月 18 06:18:02 algae kernel: Freezing user space processes failed after 20.001 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 06:17:42 algae kernel: Freezing user space processes
11月 18 04:17:41 algae kernel: Freezing user space processes failed after 20.002 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 04:17:21 algae kernel: Freezing user space processes
11月 18 04:17:21 algae kernel: Freezing user space processes failed after 20.004 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 04:17:01 algae kernel: Freezing user space processes
11月 18 02:17:00 algae kernel: Freezing user space processes failed after 20.005 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 02:16:40 algae kernel: Freezing user space processes
11月 18 02:16:40 algae kernel: Freezing user space processes failed after 20.003 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 18 02:16:20 algae kernel: Freezing user space processes
11月 17 23:46:16 algae kernel: Freezing user space processes failed after 20.000 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 23:45:56 algae kernel: Freezing user space processes
11月 17 23:45:56 algae kernel: Freezing user space processes failed after 20.000 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 23:45:36 algae kernel: Freezing user space processes
11月 17 21:45:36 algae kernel: Freezing user space processes failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 21:45:35 algae kernel: Freezing user space processes
11月 17 21:45:15 algae kernel: Freezing user space processes failed after 20.004 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 21:44:55 algae kernel: Freezing user space processes
11月 17 19:44:55 algae kernel: Freezing user space processes failed after 20.008 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 19:44:35 algae kernel: Freezing user space processes
11月 17 19:44:34 algae kernel: Freezing user space processes failed after 20.009 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 19:44:14 algae kernel: Freezing user space processes
11月 17 17:44:14 algae kernel: Freezing user space processes failed after 20.003 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 17:43:54 algae kernel: Freezing user space processes
11月 17 17:43:53 algae kernel: Freezing user space processes failed after 20.003 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 17:43:33 algae kernel: Freezing user space processes
11月 17 15:43:33 algae kernel: Freezing user space processes failed after 20.003 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 15:43:33 algae kernel: Freezing user space processes
11月 17 15:43:13 algae kernel: Freezing user space processes failed after 20.006 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 15:42:52 algae kernel: Freezing user space processes
11月 17 13:42:52 algae kernel: Freezing user space processes failed after 20.005 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 13:42:32 algae kernel: Freezing user space processes
11月 17 13:42:32 algae kernel: Freezing user space processes failed after 20.001 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 13:42:12 algae kernel: Freezing user space processes
11月 17 11:42:11 algae kernel: Freezing user space processes failed after 20.008 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 11:41:51 algae kernel: Freezing user space processes
11月 17 11:41:51 algae kernel: Freezing user space processes failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0):
11月 17 11:41:31 algae kernel: Freezing user space processes

https://github.com/systemd/systemd/issues/33626

> systemctl --version
systemd 256 (256.8)
+PAM +AUDIT -SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP -SYSVINIT +LIBARCHIVE

Summarizing this issue for visitor to resolve easily.
Check your environment might have same problem
# systemd is 256 or newer
> systemctl --version
systemd 256 (256.8)

# There are some error logs
> journalctl --system --reverse --grep 'Freezing user space processes failed'
... kernel: Freezing user space processes failed after 20.007 seconds (5 tasks refusing to freeze, wq_busy=0):

Then, set an env and reboot
systemd.services.systemd-suspend.environment.SYSTEMD_SLEEP_FREEZE_USER_SESSIONS = "false";


Export resource return empty C# script file

Godot version:
3.2 stable mono
OS/device including version:
Debian 10
Issue description:
When I export a c# script in PCK/Zip format the  script inside is empty
Steps to reproduce:
Make a basic project in c#
add a basic c#script with any text inside
then export it
Project->Export->Resources->Export Selected resources (and dependencies)
Select a c# script
press button "Export PCK/Zip"
give a name + extension
Minimal reproduction project:
NA

C# is compiled to bytecode, I'm surprised the source files still exist in the exported game

I guess you are referring to "Export Project" options but
We talk about "Export PCK/Zip" options.  In this case I expect to have the whole project exported (scripts included)

Export and Docs changed. Close.


Branding Updates: Step 10

Only typography update #734

Should be working with all previous updates
Current Look :

@sydney-devine please confirm

Should be working with all previous updates
Current Look :

@sydney-devine please confirm

Minus the question typography changing we talked about this morning, this looks great.


Prepare release 0.1.0

We have solved the versioning issue, see #92. So we can release a version and publish the package on npm.
See also #41 (May 2021).
Documentation tasks

[x] Review milestone 0.1.0
[x] Configure GitHub auto-generated release notes: https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes #142
[x] Review repository labels and the labels applied to merged Pull Requests. Labels are used to auto-generate the GH release notes
[x] Update the Changelog file. List fixes or add a link to the GH release. #146

Content of the npm package

[x] Ensure that a README file is included. To avoid duplication with the main README, it can provide minimal information (description, how to install) and a link to the main README (https://github.com/maxGraph/maxGraph#readme) #144
[x] Include the LICENSE files #144

Publishing tasks

[ ] Publish the npm package. This will be probably done from a local dev machine. If so list the command that have been run in a comment to let other review. To be improve later by automating with GitHub Actions for instance
[ ] Update the README #145

[x] add a npm status badge
[x] update the status paragraph and explain how to install the package

After merging #142, here is how the auto-generated release notes will look like:

ℹ I should be able to publish the npm package and the release notes today 🤞🏿

The first version of the npm package has been published<EMAIL_ADDRESS>Manual actions done to tag and publish
git tag
commit c60b8496a39538771c4c8eb1bf9962bf5fc5b3c0
git tag v0.1.0
git push origin v0.1.0
npm publish
from commit c60b8496a39538771c4c8eb1bf9962bf5fc5b3c0 (HEAD -> development, tag: v0.1.0, origin/development)
Run npm publish --access=public
About --access=public
This was required for the initial publish and should not be required anymore. See https://docs.npmjs.com/cli/v8/commands/npm-publish#access

When publishing scoped packages, the access level defaults to restricted. If you want your scoped package to be publicly viewable (and installable) set --access=public. The only valid values for access are public and restricted. Unscoped packages always have an access level of public.
Note: Using the --access flag on the npm publish command will only set the package access level on the initial publish of the package. Any subsequent npm publish commands using the --access flag will not have an effect to the access level. To make changes to the access level after the initial publish use npm access.


Merges Master to Live. See commits for details.

Docs Build status updates of commit 4e30424:
:clock10: Full build: the average full build time is 12 min(s) 48 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 4e30424:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsTenantTrustedIPAddress.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 88c8089:
:clock10: Full build: the average full build time is 12 min(s) 49 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 88c8089:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsTenantTrustedIPAddress.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


SpringFox is incompatible with spring-boot-starter-validation

Actually add dependency io.springfox:springfox-boot-starter:3.0.0 with org.springframework.boot:spring-boot-starter-validation:2.4.0.
The incompatibility is between Javax Validation and Jakarta Validation depend by Spring Validation

you could just remove springfox-boot-starter,and create another one starter youself

you could just remove springfox-boot-starter,and create another one starter yourself


drop ghost tables code and move to a callback based architecture

Let's remove the guessing code from rails and move to a callback based architecture from cartodb-postgres extension

cc @gfiorav @juanignaciosl

@javisantana there is (at least) one use case that is harder to handle from the extension: deletion + recreation. There are some users that have scripted the deletion of table and, just afterwards, its recreation. Current ghost tables behaviour doesn't delete the visualizations, but a callback based one might do.

I understand that but that behavior could fail with current ghost tables as well, right?
My point is, the behavior should be consistent, if someones removes a table it must remove everything using it. If someone just wants to replace table contents, they should replace them (not drop and recreate the table)

@javisantana Current code for ghost tables detected drop + create.
Like I said: we can't blame the ghost table manager for flow errors. It would be like blaming CARTO for a Rails issue. This solution has proven stable for sometime as well.
For the record, what happened today is:

Rename was cut in half (in between deploys) and vis was broken.
Ghost table manager realised the discrepancy and tried renaming the table visualization to match the physical table name.
Since vis was broken, rename failed.
Ghost table manager removed it as it couldn't be fixed, and the relinked it again.

@javisantana @juanignaciosl
Maybe the real deal here is to actually rethink how we store metadata. Imagine a dataset dashboard that would just show whatever is in your db. Then metadata can be stored elsewhere and discarded if physical table disappears.
The current modeling of a dataset is kind of artificial, and that requires a "Ghost table manager" to make sure everything is synced.

@gfiorav we tried to to that in the past and it's what i'm proposing here: have a real sync between database and metadata.
Nothing is being blamed, ghost tables is working but it has some issues due it's an async process.

we tried to to that in the past and it's what i'm proposing here: have a real sync between database and metadata.

Ah! Didn't understand this was what you propose, I though it was using callbacks (not sold it would solve anything since a callback can fail and is asynchronous (race conditions).

ghost tables is working but it has some issues due it's an async process.

Yes but it's concurrent! I uses mutex like structures so it's serial per user (we made the Carto::Bolt using the redlock algorithm, redis and atomic operations https://github.com/CartoDB/cartodb/blob/master/lib/carto/bolt.rb).

Nothing is being blamed

Of course 😄  I'm just pointing out it might not be such a bad solution after all. It's concurrent and has proven stable.

Hey, @juanignaciosl and I have been speaking about this and some conclusions were driven:

Callback require hacking the SQL API which might not be ideal.
We can move metadata to vis and remove the concept of User Table, but it's vertical to the builder and will take a lot of time.
The current implementation is "good enough", but we tend to hate it because it exposes other issues (rename fails -> a map is lost vs a map is unusable).

IMHO:
Our implementation is "Good enough" really and the other alternatives, albeit more beautiful, require a lot of time and deep transformation: for callbacks, the bigger change is in the SQL API. For dropping user table concept, the it's the Builder.
Non of this should stop us at a philosophical level (let's do the best we can and never settle for middle solutions) but deciding we should spend 3 weeks (worst case I guess) on either of these is more of an administration decision than a technical one.
Let us know @javisantana 😄

Let me clarify things here:

when I say callbacks I mean database http hooks as we do when user groups. If we need to spend time on that, let's spend it, don't be affraid :)
the way ghost tables work is limiting for us, we should be able to control which tables are registered and be kind of transactional if we need it. For example, should a conector table be shown in the UI? maybe no, we should be able to control those things but the current implementation does not allow that

when I say callbacks I mean database http hooks as we do when user groups

Looking into that :)

the way ghost tables work is limiting for us, we should be able to control which tables are registered and be kind of transactional if we need it

What do you mean with transactional? It's concurrent right now: 1 process per user at a time (redlock algorithm)

What do you mean with transactional? It's concurrent right now: 1 process per user at a time (redlock algorithm)

If I do a "select cdb_cartodbfytable(...)" and the table can't be registered in metadata database it should fail


Is the way blake3 implemented here preventing using the arm optimized NEON version of it?

Does this take into account the blake3 version that uses NEON for ARM cpus that support it like the apple M1?  I don't see it listed in the CMakeLists.txt .
Originally posted by @AndyRPH in https://github.com/madMAx43v3r/chia-plotter/issues/59#issuecomment-859567749

no I guess not

Will this help better ID M1 apple build env to properly setup the Cmake stuff?
https://discourse.cmake.org/t/how-to-determine-which-architectures-are-available-apple-m1/2401/12

the place for this discussion is on the BLAKE3 site....
since this app pull directly from the BLAKE3 code.
The real BLAKE3 compile experts will be in that group.

I don't think it's a Blake3 issue, it looks like the correct version can be pulled in via the right cmake setup, which is far more likely to happen quickly than the blake3 group making large changes to how they have their end setup...

you can try to make it work, just edit your CMake file

Will do!

actually all the SIMD optimizations will never be used for chia, for that the input size would have to be more than 1 kB, but in chia the max is 64 bytes...

Thanks for the follow up!


Word corrections -> 'on-premise' to 'on-premises'

Changed a couple of occurrences of on-premise to on-premises.

Hi @1brianjones, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@1brianjones : Thanks for your contribution to the Azure documentation! The author, @adrianhall, has been notified to review your proposed change.

Hi @1brianjones, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

#sign-off


Fusion manual correction

I use the "cornerstone-tools": "^6.0.6"
Hello, I would like to ask you a question, I'm doing manual correction fusion pet image, click on the correct button, the Settings enabledElement. SyncViewports = false, pet images can be moved alone, then click the save button, display the pet fusion diagram, Also the enabledElement. SyncViewports set to false. But when I use PanTool can only move to CT images, PET image won't move, if the enabledElement syncViewports set to true, the image will return to the starting position. Can CT and PET move together while moving the image and retain the corrected position?


NuGet 5.1.0 deletes key references

When upgrading from 5.0.1 to 5.1.0 the following lines were removed from my web project file (csproj):
<Reference Include="System.Web.Helpers, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.Helpers.dll</HintPath>
</Reference>
<Reference Include="System.Web.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.Http.dll</HintPath>
</Reference>
<Reference Include="System.Web.Http.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.Http.WebHost.dll</HintPath>
</Reference>
<Reference Include="System.Web.Mvc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.Mvc.dll</HintPath>
</Reference>
<Reference Include="System.Web.Razor, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.Razor.dll</HintPath>
</Reference>
<Reference Include="System.Web.WebPages, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.WebPages.dll</HintPath>
</Reference>
<Reference Include="System.Web.WebPages.Deployment, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.WebPages.Deployment.dll</HintPath>
</Reference>
<Reference Include="System.Web.WebPages.Razor, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
  <HintPath>..\packages\Unity.5.0.1\lib\net45\System.Web.WebPages.Razor.dll</HintPath>
</Reference>

I'm assume only the hints should have been removed or updated. The result is that it breaks the app because these references are all needed in an ASP.NET MVC project.

Visual Studio is not under our control.

I don't understand. Why is it deleting references that are in there from other packages? Unless I'm missing something, this is a really horrible experience. I upgraded fro Unity 5.0 to Unity 5.1, and immediately had 407 build errors. That's not the way things should go.

Agreed, its is painful. Unity.Abstractions and Unity.Configuration seem to work. I'm guessing there is a bug in the NuGet deployment that is uses a wildcard search but it casting a larger net deleting out the wrong references. I don't know who to report this bug to since NuGet point backs to this repo as the owner.

You are welcome to contribute better experience. We welcome any help.

Don't know enough of the NuGet packages to create, I can test if someone posts an update

@jmhongithub  You could file an issue with Visual Studio. It ultimately controls all these nuances.
...and up until couple of weeks ego I knew nothing about NuGet. (Hence these issues)

@ENikS are there any Microsoft staff still contributing to Unity or is it just you?

No. No one contributed to this project since 2015. Microsoft stopped supporting it in 2013.

Wow, I understand the issue now.

Do you want to help? Plenty of opportunities...

(And definitely sorry for being grumpy - I had thought I was complaining to MS, which feels a lot different than complaining to a guy who's just doing his best.)

No biggie

It sounds like plenty opportunities. Right now I need to get this DI library running configured correctly for our team. I saw the author as "Microsoft.Practices.Unity" in NuGet so I had assumed Microsoft staff was still contributing. Sounds like that is not the case. Was version 3.5.1404 the last one they contributed?

Yes. since than it is only community support.

Anyway, it is stable enough and if you link to individual packages it should work.

I would recommend pulling 5.1.0 from NuGet, others are going to receive the same error.

I'll deploy 5.1.1 later. It only breaks in certain conditions.

Unfortunately the issue goes back to 5.0.1. When I uninstalled 5.0.1 it deletes those other references as well.  I'm going to to need to manually edit the project files to fix.

This is not the package, it is the new NuGet manager. Package lists these as dependencies and when you delete it manager thinks you no longer need these dependencies as well.
I do not think it will do it again though. The MVC package had problem with signing certificate and had to be resigned with correct one. For the manager it is completely different package now, hence all the commotion with dependencies.

Deployed 5.1.2


fix: #67 fix radius + autocomplete api

Fix #67
Autocomplete url : https://photon.komoot.io/

Codecov Report

Merging #69 (bd19ed5) into master (ac52e72) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
- Coverage   21.91%   21.85%   -0.06%
==========================================
  Files          23       23
  Lines         730      732       +2
  Branches      123      123
==========================================
  Hits          160      160
- Misses        570      572       +2

Impacted Files
Coverage Δ

src/components/home/SearchBox.vue
83.33% <ø> (ø)

src/pages/StreetView.vue
0.00% <0.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 ac52e72...1763ab7. Read the comment docs.


Showing that the version is 1.0.0.

It keeps showing that the version is 1.0.0.
What is the correct way to reinstall the GUI ?

This was an error on my part - you should be able to update now. You may receive a prerequisites error after updating this time, since I changed the way that it works, but you can safely close/ignore it.


Add accesibleSearchEnabled prop for TreeView component

Description of Proposed Change
Purpose
Add the accessibleSearchEnabled property to allow users to control when the component focuses automatically while typing.
Change Details

New Property: accessibleSearchEnabled

Type: boolean
Default Value: true
Description: Allows enabling or disabling the accessible search functionality. When enabled, the component will automatically focus on nodes that match the key pressed.

Modification in handleKeyDown:

The accessibleSearchEnabled property is added to the parameter list.
Additional logic is included to handle accessible search based on the new property. If accessibleSearchEnabled is true, the function will search and automatically focus on nodes whose names start with the pressed key.

Relevant Code
const handleKeyDown = ({
  accessibleSearchEnabled = true,
  data,
  expandedIds,
  selectedIds,
  disabledIds,
  tabbableId,
  dispatch,
  propagateCollapse,
  propagateSelect,
  multiSelect,
  expandOnKeyboardSelect,
  togglableSelect,
  clickAction,
}: {
  accessibleSearchEnabled?: boolean;
  data: INode[];
  tabbableId: NodeId;
  expandedIds: Set<NodeId>;
  selectedIds: Set<NodeId>;
  disabledIds: Set<NodeId>;
  halfSelectedIds: Set<NodeId>;
  dispatch: React.Dispatch<TreeViewAction>;
  propagateCollapse?: boolean;
  propagateSelect?: boolean;
  multiSelect?: boolean;
  expandOnKeyboardSelect?: boolean;
  togglableSelect?: boolean;
  clickAction: ClickActions;
}) => (event: React.KeyboardEvent) => {
  // Existing logic
  // ...

  if (event.key.length === 1 && accessibleSearchEnabled) {
    let currentId = getNextAccessible(data, id, expandedIds);
    while (currentId !== id) {
      if (currentId == null) {
        currentId = getTreeParent(data).children[0];
        continue;
      }
      if (
        getTreeNode(data, currentId).name[0].toLowerCase() ===
        event.key.toLowerCase()
      ) {
        dispatch({
          type: treeTypes.focus,
          id: currentId,
          lastInteractedWith: id,
        });
        return;
      }
      currentId = getNextAccessible(data, currentId, expandedIds);
    }
  }

  // Existing logic
  // ...
};

Benefits

Improved Accessibility: Allows users to navigate the component more easily using the keyboard.
Flexibility: Developers can enable or disable this feature as needed, adapting to various usage scenarios and accessibility requirements.

This change enhances the user experience when interacting with the component, particularly in terms of keyboard accessibility and usability.

@mellis481 can you take a look at this?


[DO-NOT-MERGE] Run tests against hadoop-3.1 to see the test failures

What changes were proposed in this pull request?
Want to see the test results against hadoop-3.1 profile.
How was this patch tested?
N/A

Test build #91215 has started for PR 21441 at commit a1b5c36.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3632/
Test PASSed.

Test build #91215 has finished for PR 21441 at commit a1b5c36.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91215/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/73/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3962/
Test PASSed.

Test build #91740 has started for PR 21441 at commit a1b5c36.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3963/
Test PASSed.

Test build #91740 has finished for PR 21441 at commit a1b5c36.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91740/
Test FAILed.

retest this please

Test build #91750 has started for PR 21441 at commit 2778dbc.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/79/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3969/
Test PASSed.

Test build #91750 has finished for PR 21441 at commit 2778dbc.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91750/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3973/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/83/
Test FAILed.

Test build #91755 has started for PR 21441 at commit ec4c377.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/84/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3974/
Test PASSed.

Test build #91755 has finished for PR 21441 at commit ec4c377.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91755/
Test FAILed.

Test build #91756 has finished for PR 21441 at commit 2778dbc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91756/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3977/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/87/
Test PASSed.

Merged build finished. Test PASSed.

Test build #91762 has started for PR 21441 at commit a57dd09.

Test build #91762 has finished for PR 21441 at commit a57dd09.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91762/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3982/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/92/
Test FAILed.

Test build #91770 has started for PR 21441 at commit a57dd09.

Test build #91776 has started for PR 21441 at commit da92e01.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/94/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3985/
Test PASSed.

retest this please

Test build #91777 has started for PR 21441 at commit da92e01.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3986/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/95/
Test PASSed.

Test build #91776 has finished for PR 21441 at commit da92e01.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91776/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/117/
Test PASSed.

Test build #91809 has started for PR 21441 at commit f16c7f7.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4007/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/118/
Test PASSed.

Test build #91810 has started for PR 21441 at commit f16c7f7.

Test build #91809 has finished for PR 21441 at commit f16c7f7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91809/
Test FAILed.

Test build #91810 has finished for PR 21441 at commit f16c7f7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91810/
Test FAILed.

Merged build finished. Test FAILed.

Test build #91837 has started for PR 21441 at commit cd3a0d1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/138/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4027/
Test PASSed.

Test build #91839 has started for PR 21441 at commit c630f4a.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4028/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/139/
Test PASSed.

Merged build finished. Test PASSed.

Test build #91840 has started for PR 21441 at commit c630f4a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4029/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/140/
Test PASSed.

Test build #91841 has started for PR 21441 at commit ed6b9a0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/141/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4030/
Test PASSed.

Test build #91842 has started for PR 21441 at commit 8000b6b.

Test build #91839 has finished for PR 21441 at commit c630f4a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91839/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/145/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4034/
Test FAILed.

Test build #91851 has started for PR 21441 at commit 57b545e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4035/
Test PASSed.

Test build #91837 has finished for PR 21441 at commit cd3a0d1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91837/
Test FAILed.

Test build #91840 has finished for PR 21441 at commit c630f4a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91840/
Test FAILed.

Test build #91842 has finished for PR 21441 at commit 8000b6b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91842/
Test FAILed.

Test build #91841 has finished for PR 21441 at commit ed6b9a0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91841/
Test FAILed.

Test build #91851 has finished for PR 21441 at commit 57b545e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91851/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/172/
Test FAILed.

Test build #91889 has started for PR 21441 at commit 3400071.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/174/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4064/
Test PASSed.

Test build #91889 has finished for PR 21441 at commit 3400071.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91889/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4121/
Test PASSed.

Test build #91954 has started for PR 21441 at commit 6c86d92.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/226/
Test PASSed.

Test build #91954 has finished for PR 21441 at commit 6c86d92.

This patch fails build dependency tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91954/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test build #91957 has started for PR 21441 at commit 6c86d92.

Test build #91958 has started for PR 21441 at commit 66d2437.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/230/
Test PASSed.

Test build #91957 has finished for PR 21441 at commit 6c86d92.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91957/
Test FAILed.

Test build #91958 has finished for PR 21441 at commit 66d2437.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91958/
Test FAILed.

retest this please

Test build #91973 has started for PR 21441 at commit 66d2437.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4131/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/236/
Test PASSed.

Test build #91973 has finished for PR 21441 at commit 66d2437.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91973/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4143/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/248/
Test PASSed.

Test build #91990 has started for PR 21441 at commit 2c4bc85.

Test build #91990 has finished for PR 21441 at commit 2c4bc85.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/91990/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4169/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/275/
Test PASSed.

Test build #92024 has started for PR 21441 at commit 4b30099.

retest this please

Test build #92024 has finished for PR 21441 at commit 4b30099.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92024/
Test FAILed.

Test build #92025 has started for PR 21441 at commit 13918d9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/276/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4170/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/278/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4172/
Test PASSed.

Test build #92025 has finished for PR 21441 at commit 13918d9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92025/
Test FAILed.

Test build #92032 has started for PR 21441 at commit 8be8b7f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/280/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4174/
Test PASSed.

Test build #92032 has finished for PR 21441 at commit 8be8b7f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92032/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/4196/
Test PASSed.

Merged build finished. Test PASSed.

Test build #92057 has started for PR 21441 at commit d05c5d0.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/302/
Test PASSed.

Merged build finished. Test PASSed.

This now more targets to fix SPARK-24590. Let me open a WIP PR and proceed there.

Test build #92057 has finished for PR 21441 at commit d05c5d0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92057/
Test FAILed.


Update dotnet

This PR contains the following updates:

Package
Type
Update
Change

GDataCyberDefense.Vaas
nuget
patch
6.0.2 -> 6.0.3

Websocket.Client
nuget
minor
5.0.0 -> 5.1.1

xunit
nuget
minor
2.6.6 -> 2.7.0

xunit.runner.visualstudio
nuget
patch
2.5.6 -> 2.5.7

Release Notes

xunit/xunit (xunit)
v2.7.0
Compare Source

xunit/visualstudio.xunit (xunit.runner.visualstudio)
v2.5.7
Compare Source

Configuration
:date: Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
:warning: Warning: custom changes will be lost.


Support for restriction value 'destination'

From: https://discuss.graphhopper.com/t/restrictedvalues-destination/475
The access restriction value destination is not regarded. A high penalty has to be applied when changing from an unrestricted way to a way with destination restriction.
Test case 1: Legal path avoids the hamlet Heitersberg and will make a ~20km detour.
https://graphhopper.com/maps/?point=47.414905%2C8.343494&point=47.415366%2C8.346804&locale=en-US&vehicle=car&weighting=fastest&elevation=true&layer=Omniscale
Test case 2: Fastest path is through Bellikon
https://graphhopper.com/maps/?point=47.36249%2C8.367419&point=47.415231%2C8.346503&locale=en-US&vehicle=car&weighting=fastest&elevation=true&layer=Omniscale

Not sure if this belongs here, but I found a routing issue yesterday, that seems to happen, due to not correctly interpreted destination:
https://graphhopper.com/maps/?point=48.710638%2C9.450173&point=48.712171%2C9.453017&locale=de-DE&vehicle=car&weighting=fastest&elevation=true&use_miles=false&layer=Omniscale
This way should not be used:
http://www.openstreetmap.org/way/362442354#map=19/48.71141/9.45258&layers=ND

We currently ignore the destination thatswhy the issue. If we introduce this we would either need to introduce an additional priority (like we do e.g. for bikes) or make time estimates slightly incorrect.

Wouldn't be this priority exactly the right thing (speaking semantically)?
https://github.com/graphhopper/graphhopper/blob/ea1a8e207d02cb52f2b062712b2c7e9689830c5c/core/src/main/java/com/graphhopper/routing/util/PriorityCode.java#L30

I am currently looking into this issue.
IMHO, adding a penalty when switching from non-destination roads, to destination roads would not justify the the effort of implementation.
There are some other options I see right now:

Implement it in the current CarFlagEncoder (probably the most helpful encoder for this right now)
We could modify speed to e.G. 5km/h (However, this would make the estimated travel times incorrect)
We could add a Priority to the CarFlagEncoder (probably not very nice, but the solution would be more correct)
Implement it in the DataFlagEncoder, however this would require us to save the access tags of each highway and analyze them per vehicle (not supported yet)

Right now I guess, that the DataFlagEncoder solution would be the best in terms of future oriented development. The speed "trick" in the CarFlagEncoder would be a fast improvement for the current situation. Maybe we even want to implement both?

Yes, this sounds good

We could add a Priority to the CarFlagEncoder (probably not very nice, but the solution would be more correct)

This is the correct solution, but we loose (like we do for bike&foot) that the weight is proportional to the time which is sometimes good for performance reasons, see #240
So I vote to make your two proposed changes and potentially we need to revert the change in CarFlagEncoder e.g. if there are too many long ways with destination.

A strict implementation of this was just feature-requested on Facebook.
In a posting which I'm afraid I cannot link to at the moment because something is broken on Facebook. :-)

With 'strict' you mean that uses a priority difference and not via speed?

A strict implementation of this was just feature-requested on Facebook.

The issue with this is, that we don't have enough context to create a wise decision here. Areas tagged with access=destination should be allowed to enter, but only if there is a waypoint in that area or the waypoint is only reachable using this road. AFAIK we cannot model this relation right now?

EDITed to 'stricter'. I think the strict meaning of the rule is "don't go there except if you destination is exactly on this road", and yes, I think we cannot model this right now.

Just wanted to pass on the interest in this feature.

yes, I think we cannot model this right now

We could model it via priorities IMO (?) I.e. all destination tags get a very bad weighting that will only be used if necessary.

Infinite, even? Don't know exactly what a priority is (haven't looked at road routing much), but sounds good.

Infinite, even?

This could make problems. E.g. in #729 we say that we want to consider the weighting to exclude edges based on infinite weights.

Don't know exactly what a priority is (haven't looked at road routing much), but sounds good.

For bike routing we call the part of the flags this way and have different priorities like 1-7 to say it should be preferred without the need to change the speed

Ah, no, the reason is that with Infinity, all paths would be equally bad and the problem collapses. So almost infinity.

Ah, no, the reason is that with Infinity, all paths would be equally bad and the problem collapses. So almost infinity.

You should be aware of the "Connection not found" issue, if the weight is exceeding a certain threshold, so I am not sure if this is practicable?

You should be aware of the "Connection not found" issue, if the weight is exceeding a certain threshold, so I am not sure if this is practicable?

No, I'm not -- I'm not a road router at the moment. ,-) Tell me more, please.. What is that threshold and where does it come from?

@michaz, look for the ConnectionNotFoundException. I would assume this could happen for non road routing as well, but very unlikely, except there are different subnetworks. Also see the maxVisited nodes in the different RoutingAlgorithm classes. This could be one example where it might fail. Not sure if there are more cases @karussell?

Ah I forgot, if we now set the weight very high, close to infinite, we most likely traverse the whole graph before even consider taking this road, this would make it a) very slow and b) might fail due to maxVisitedNode.

True, true, true.

And anything "properly multi-criteria" is super-slow and super-vulnerable to accidentally traversing the whole graph. Tricky.

Ah I forgot, if we now set the weight very high, close to infinite, we most likely traverse the whole graph before even consider taking this road, this would make it a) very slow and b) might fail due to maxVisitedNode.

So if we want to do this strict, I think we have to get more context into the calculation, like checking every waypoint if it's only reachable from the outside without  using destination roads, if not, run a second shortest path search that allows destination roads, which could be still vulnerable for taking the wrong destination roads between two points, but if destination roads are also slow are have a bad priority it could work.

Or sneakily look at OSRM how they do it.

Or sneakily look at OSRM how they do it

They do it via priorities, I think. Before they did it via manipulating the speed (ugly). But as they only use CH they won't get big performance issues I think.

PR #1752 does not fully fix this, especially for short edges. Maybe we use a weight offset, not (only) a factor?


ibus not working in isolated Telegram Desktop

ibus does not work after isolating even with passed environment variables since d7bd645.

Likely due to Qt not supporting xim mode anymore.