DNS lookup cached for http services

This is similar to  #7354 - TCP now reacts to changes so is it possible to apply similar to HTTP services as presently the target address isn't refreshed, ideally this should be configurable as transient DNS errors will cause requests to fail so an on/off switch would be useful for instances where it should continue to only be looked up on start/reload

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
Issue templates help us help you by providing all necessary information.
Please edit your issue and use the available templates:

Feature request
Bug report

And remember: each time someone ignores the template, a cute little bunny dies.

#SaveTheCuteBunny :heart: :rabbit: :heart:

I was just about to open an issue for this, after talking today to @emilevauge about it. Happy to see someone already did that.
My use case is for all routers defined via file providers (not only TCP or HTTP). Nginx has a caching control option - so basically that's what I'm using right now:
Request --> Traefik --> Nginx --> Service.
The relevant Nginx configuration is:
stream {
  resolver <IP_ADDRESS> valid=1s ipv6=off;
  map $remote_addr $backend_udp {
    default openvpn-udp;
  }
  map $remote_addr $backend_tcp {
    default openvpn-tcp;
  }
  server {
    listen 1194 udp;
    proxy_pass $backend_udp:1194;
  }
  server {
    listen 1194;
    proxy_pass $backend_tcp:1194;
  }
}

If I were able to define that valid=1s option for the router, I would get rid of quite a few containers floating around.

@jwh and @tlex I don't see an issue with HTTP routers on this matter, as they are already doing lookup on a request basis when using a hostname as URL.
If that is not happening on your use case it may be another issue, so can you share the static + dynamic configs for a reproducible case?

Sorry, my comment was more of a general nature, not necessarily for HTTP routers. My pain is for TCP and UDP routers (as documented by the workaround above)

This is the configuration I was using without nginx:
udp:
  routers:
    openvpn-udp:
      entryPoints:
        - openvpn-udp
      service: openvpn-udp
  services:
    openvpn-udp:
      loadBalancer:
        servers:
          - address: "openvpn-udp:1194"
tcp:
  routers:
    openvpn-tcp:
      entryPoints:
        - openvpn-tcp
      rule: "HostSNI(`*`)"
      service: openvpn-tcp
  services:
    openvpn-tcp:
      loadBalancer:
        servers:
          - address: "openvpn-tcp:1194"

@jwh and @tlex I don't see an issue with HTTP routers on this matter, as they are already doing lookup on a request basis when using a hostname as URL.
If that is not happening on your use case it may be another issue, so can you share the static + dynamic configs for a reproducible case?

The destination address of a service doesn't appear to be re-resolved at any point, whereas for TCP it is now (after the commit linked in the issue) - nothing special in my config

@tlex thanks, so for you it should be fine after v2.3.3 as TCP was fixed and UDP already works in a per request basis.
@jwh for UDP, as I mentioned, it should be already covered. See here:
https://github.com/traefik/traefik/blob/2112de6f1515da1fa1d093697ed09e40c2622d58/pkg/udp/proxy.go#L22-L32
It resolves per request when serving, there is even a comment suggesting the reverse:
https://github.com/traefik/traefik/blob/2112de6f1515da1fa1d093697ed09e40c2622d58/pkg/udp/proxy.go#L12
which is really not what we want now :-)

@jwh I did some quick tests with the File provider + k8s (local k3d) and, as expected, could not reproduce on http:
File provider:
http:
  routers:
    whoami:
      entryPoints:
      - web
      service: whoami@file
      rule: Host(`whoami.docker.localhost`)
  services:
    whoami:
      loadBalancer:
        servers:
        - url: http://whoami.apps.svc.cluster.local

Service:
---
kind: Deployment
apiVersion: apps/v1
metadata:
  name: whoami
  labels:
    app: whoami
spec:
  replicas: 2
  selector:
    matchLabels:
      app: whoami
  template:
    metadata:
      labels:
        app: whoami
    spec:
      containers:
        - name: whoami
          image: containous/whoami
          ports:
            - name: web
              containerPort: 80

---
apiVersion: v1
kind: Service
metadata:
  name: whoami
spec:
  ports:
    - protocol: TCP
      name: web
      port: 80
  selector:
    app: whoami

Deleting the pods, thus changing the underlying IP addresses of the service, has no impact and I can keep hitting then as soon as the new pod goes live.
curl -H "Host:whoami.docker.localhost" localhost

but maybe I missed something here

hm, it does actually appear to lookup for some services sporadically (just dumping traffic to 53 from traefik to observe) but not all, maybe its actually something else thats going on - will watch a bit more and close this if it turns out its actually ok and its something else

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
I have to close this one because of its lack of activity :disappointed:
Feel free to re-open it or join our Community Forum.

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
I have to close this one because of its lack of activity :disappointed:
Feel free to re-open it or join our Community Forum.


Show PR settings on empty repos

Previously the settings page would not show the PR section if the repository was empty.
Fix #12788
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

Merging #12808 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12808      +/-   ##
==========================================
- Coverage   43.22%   43.20%   -0.03%
==========================================
  Files         651      651
  Lines       72118    72118
==========================================
- Hits        31174    31157      -17
- Misses      35902    35912      +10
- Partials     5042     5049       +7

Impacted Files
Coverage Δ

modules/notification/mail/mail.go
34.48% <0.00%> (-3.45%)
:arrow_down:

modules/notification/ui/ui.go
80.55% <0.00%> (-2.78%)
:arrow_down:

modules/process/manager.go
72.50% <0.00%> (-2.50%)
:arrow_down:

services/pull/check.go
47.69% <0.00%> (-2.31%)
:arrow_down:

models/notification.go
66.13% <0.00%> (-0.92%)
:arrow_down:

models/error.go
34.81% <0.00%> (-0.86%)
:arrow_down:

services/pull/pull.go
41.57% <0.00%> (-0.47%)
:arrow_down:

modules/log/event.go
59.43% <0.00%> (+1.88%)
:arrow_up:

Continue to review full report at Codecov.

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


return 409 conflict when a file was already created

We now return the correct 409 conflict status code when a file was already created by another upload.

hm ... some test fallout ... I need to investigate.

it was just a hiccup in the posixfs tests 🤔 rerunning the ci worked: https://drone.owncloud.com/cs3org/reva/5341
cc @aduffeck


Fixes 'aad oauth2grant list' command. Closes #2710

Fixes 'aad oauth2grant list' command. Closes #2710
Updated to use the Microsoft Graph v1.0 endpoint.

Thank you @nanddeepn we will review shortly

What's the added value of listing all grants for all service principals? What would be the use case for that? Also, we'd need to adjust the command's description as well as other aad oauth2grant commands to keep them consistent.

To keep things moving, let's keep the command as-is aligned with the current spec and the clientId required. We can revisit in the future if necessary.


EO up to 0.23.17

@yegor256 please check/merge

@Graur this code is already in master (I made similar changes)


[Driver] [GPIO] pca_series gpio expander driver

Scope
I was trying to write a new driver for PCAL6524, a i2c gpio expander. Going thourgh existing drivers, there are numbers of driver for different PCA(L) series devices. They share similiar register layout and control logic. So I intends to unify these drivers for PCA(L)xxxx series i2c gpio expanders.
If this driver gets merged, it should retire pca95xx , pca953x and pcal64xxa drivers.
Method
By referencing exsisting gpio_pca95xx and pcal64xxa driver, I have drafted these code to show my intended implementation. As shown in code, different capablilties can be defined:

basic functions
this applies to all compatiable devices.
"latch" and drive strength
this is what "L" in PCALxxxx means. allows to "latch" input until read and configure drive strength to one of 4 levels.
pull up/down
pull enable and pull select
interrupt mask
able to mask interrupt on certain pins. most PCAL devices has this, as well as PCA957x.
interrupt edge / clear
seen on PCAL6524.
output config
seen on PCAL6524. note that although many devices is able to configure push-pull or open-drain on a per-port basis, PCAL6524 suports configure on a per-pin basis.

We can describe a compatible device using a set of feature flags and ngpios property. Based on that, it's possible to create separate register maps and api maps to drive different devices.
Question

Is it necessary to maintain cache for all config registers?
In the original code, lots of registers are "cached" to speed-up the "read-modify-write" process. In my view, I/O expanders are not meant to be frequenty reconfigured. We also do not have tools like regmap in linux to automate the caching. Maintaining cache for devices with different port size can be complicated in coding. My intention is to only cache output values.
update: The final implementation use Kconfig to control caching. I've tested the GPIO_PCA_SERIES_CACHE_ALL=n option on pcal6524 on mimx93_evk_a55 board. The GPIO_PCA_SERIES_CACHE_ALL=y option remains to be fully tested.

Is there way to avoid creating multiple dt-bindings?
I tried to avoid creating a lot of dt-bindings by put a "part_no" property under a single nxp,pca_series.yaml dt-binding.

Any suggestions are welcomed.
Thanks

This is a re-open of #63101 .

@dleach02 @danieldegrasse please take a look

Thanks. I'm out of office right now, will be back handling the comments in a week or so.

@CkovMk please address the CI issues

Tested with PCAL6524 on i.MX 93 EVK: configure, read, write apis are working. will test interrupt and full_cache mode.

@danieldegrasse The code is in ready state.
I stripped away plenty of code and only left code supporting pcal6524 and pcal6534. I'll open new pr to expand it in the (near) future.
It is fully tested on i.MX 93 EVK with pcal6524 on board. A total of 4 cases tested: interrupt support enabled / disabled combined with cache all enabled and disabled.

gpio shell is working properly.
samples/basic/button working with interrupt enabled.

ci issues resolved

Soft ping to @danieldegrasse , Have you got time to review this? Thanks

also add pca9554 and 9555, which are basically variants of pca9538 and pca9539 respectively.

fixed bug when configuring pin input/output.

uh there's an issue when multiple part# is present in the same app. inst# is reused, causing redefinition of inst##_cfg and inst##_data. need to encode part no into variable names.
haven't anticipate that...

above issue is fixed.
Now CI is failing because
zephyr/drivers/gpio/gpio_pca_series.c:524:79: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast]
  524 |         LOG_DBG("cache read type %d len %d mem addr 0x%8.8x", reg_type, size, (uint32_t)src);

If I use %lx and (size_t)ptr conversion, it will report error on 32bit machines. If I use %x with (uint32_t)ptr conversion, it will report error on 64bit machines.
Not sure what to do...

above issue is fixed.
Now CI is failing because
zephyr/drivers/gpio/gpio_pca_series.c:524:79: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast]
  524 |         LOG_DBG("cache read type %d len %d mem addr 0x%8.8x", reg_type, size, (uint32_t)src);

If I use %lx and (size_t)ptr conversion, it will report error on 32bit machines. If I use %x with (uint32_t)ptr conversion, it will report error on 64bit machines.
Not sure what to do...

Pointers can be printed using the %p format string.

Pointers can be printed using the %p format string.

Oh, one nice tip : )

Hi, thank you for the driver. I know this is merged but just want ask is it possible to include samples on how to use different pca9xxx to configure a single input/output pin? (not an entire port).

@cyberjupiter This driver can be used just like other GPIO drivers, input / output is configured via Zephyr GPIO API. You may refer to samples/basic/button.
What else would you like to know with a new sample?

@cyberjupiter It depends on board design. For i.MX 93 EVK it's possible to connect 2 onboard buttons to PCAL6524 chip, by flipping a series of dip switches. I could provice such use casse as a dt overlay, is that something u r intersted in?

@CkovMk Yes, that would be great. TIA.

@cyberjupiter you may refer to #78693


Remove @app alias (discussion)

A common error developers make is treating themselves like their own vendor.  Such as building an application in the vendors which is dependent on the actual application built at the same time.
In your use of @app to alias the core module I do not see any benefit.  Including index.ts files to simplify includes inside the application is just more work to maintain.
I propose we remove the @app alias and directly include core files using the same relative path.
While I appreciate the artistic quality of using @app I do not believe it offers any engineering benefit.  Please comment.

Well. I can see your point, but I'm not certain if this is the correct approach. I can understand the benefit by removing the index.ts- and @app-alias in favor of using relative paths reduce the maintenance of the codebase, but there are some benefits here as well.
When using relative path to locate files in the core-folder, you need to update each path accordingly if you decide to re-locate a folder or file. The main reason I decided to use path-aliases for @app and @env in this application is down to the clean look and feel of the imports.
The main goal of this repo is however to offer developers a highly scalable and clean codebase, which can easily be applied to personal applications, and reduce tedious maintenance is a big part of that. Creating and updating index.ts-files are without a doubt tedious work, but using relative path has some downsides as well.
Will share this question between some devs. to see what they think of it.
Thanks for asking.

One observation: this repo is about directory structure and if the first thing you do is start aliasing the directories and taking them out of the structure; well, that's not what this repo is for.  Certainly aliasing directories has its place and we can address that in the new documentation I've started.

Using alias can also improve clarity. It is down to personal preference but there are some who use it extensively such as in projects like ngrx.
Personally I like it for readability if nothing else.

Comparing this beginner project to ngrx isn't very fair.  Everyone has to start somewhere and this repository is a good starting point.  I would like this to be an easy starting point for any experienced developer and not require prerequisites like understanding how to structure a directory as an alias.
I'm all for adding links in the documentation for further reading on subjects like aliases and I think the more paths we can create away from this starting point on an app's journey the better.

The approach to aliasing used in core/@app is tedious and must be micro managed.  I found a node module which accomplishes the same thing with just a little configuration.  I've added a link in the documentation:  https://github.com/mathisGarberg/angular-folder-structure/blob/368d55dea38c10f4844a0bf0b965141c97d2f953/.documentation/additional-resources.rst

Comparing this beginner project to ngrx isn't very fair.

Personally I don't think it is fair to classify a cited example of a feature in use as a comparison to a project in its entirety but that might be just me.
Can I ask if it is wise to suggest introducing unnecessary dependencies to beginners?  You've mentioned a package named module-alias but is that not simply wasteful duplication since Typescript has a native path mapping feature.  You can see this configured here and used here.  It adds clarity to a project and even a beginner would be able to understand the simple concept.
Clarity over brevity should be prefered, code needs to be readable especially when working in teams. Maybe @app is a bit ambiguous perhaps it might be better to rename it to @example-app.  Furthermore, for consistency we could replace all applicable paths to use the alias in every instance like the aforementioned ngrx example.  Thoughts?

Thanks for this repo. But I have a question.
When I building the dev server, to the console output some circular dependency errors. After reviewing the logs, I saw that complaining about index.ts in src/app/core. And yes, previously I have replaced the relative paths of imports to aliases.
How do I fix this errors without remove index.ts-s files?

@dougal83 Now that the documentation is in place I hope you will add your knowledge about aliasing directories using path mapping.  This technique is new to me so I don't have much to say about it.
I would like to try to find common ground to differentiate features like path mapping:
This repository is the result of a single blog post.
Teaching someone about path mapping is not the same subject and would be a new blog post.
Teaching someone about using singular vs plural naming in their app would be a new blog post.
I would like to see this repository remain single-blog-post worthy.  Uncomplicated, to the point, and teaching a single principle.

@sharkeron your question is exactly what we're discussing here.  If we remove the alias as I'm promoting then your problem will go away.

@TomHAnderson it’s ok, but if I remove index.ts files and set imports with alias, build will be compiled successful.
I don’t understand for what were added this files. Maybe I don’t know about this features in typescript. :(

@sharkeron Please follow this repo for the next couple days and I believe your issue will become fixed.

I think I've found a compromise!  In my latest PR I've removed the @app and @shared aliases and kept the @env alias.  This way we can continue to have an example of an aliased directory in the application but it is done in a very minor way.

@dougal83 I've come around and see the reasoning behind @app.  I hope you'll help in the discussion on my new thread: #61

Documentation for aliases is now an official PR:
https://github.com/mathisGarberg/angular-folder-structure/pull/63
https://github.com/mathisGarberg/angular-folder-structure/blob/5b891f95d3f0adf24997c46580ab91520b140f6d/path-alias.rst


postpone-checkout: ensure artifacts don't interfere

what

test postponing the checkout until after dependencies are installed to avoid triggering pipelines with potential artifacts.

why

Future-proofing

references
N/A

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/bjd2385/dynamic-continuation?version=dev:ecf74d0178d98409493086e095c2c9dbe88ea16e

This move is actually irrelevant, as I commonly forget that git diff-tree commands in this orb are only comparing two commits, not unstaged changes. Would still ofc be a nice-to-have?

Cf. #70


fadeIn effects are jumping on mobile

on mobile all the fadeIn effects jump at the last second. all other effects are smooth as butter but the fadeIn on mobile is just choppy. any idea how i can fix this? thank you!!

This is a perfomance problem. Probably there's something happening in your page at the same time of this animation. A script or other animation running concurrently.

What is your framework to do that? Is it ionic?

Closing as it's stale.

I encountered a similar issue with the CSSTransition method from react-transition-group. The animation duration of the method was set to 2 seconds, while the default duration in the animate.css library is 5 seconds. As a result, the method ends the animation before the animate.css class animation is complete.
Although this may not be relevant to the problem you're currently experiencing, future visitors should consider checking for any mismatch in the animation duration between the methods (if you're using a component that manages them).


feat: add --start and --size flags

Description:
Add --start and --size flags to the dictzip command.
Related Issues:
Updates #13
Checklist:

[ ] Review the CONTRIBUTING.md documentation.
[ ] Add a reference to a related issue in the repository.
[ ] Add a description of the changes proposed in the pull request.
[ ] Add unit tests if applicable.
[ ] Update documentation if applicable.
[ ] Add a note in the CHANGELOG.md if applicable.
[ ] Sign the Google CLA.

Codecov Report
Attention: Patch coverage is 0% with 33 lines in your changes missing coverage. Please review.

Project coverage is 37.14%. Comparing base (4acab95) to head (96355bb).

Files with missing lines
Patch %
Lines

cmd/dictzip/app.go
0.00%
22 Missing :warning:

cmd/dictzip/decompress.go
0.00%
11 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
- Coverage   38.31%   37.14%   -1.17%
==========================================
  Files           8        8
  Lines         924      953      +29
==========================================
  Hits          354      354
- Misses        514      543      +29
  Partials       56       56

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


First section have excessive whitespace

...for scale.    This article...

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

ID: c7b6e2b9-7808-6c9b-101e-e6c49c14e175
Version Independent ID: 92c38af6-f984-5833-bbee-513c4731ecc5
Content: Security framework - Azure IoT Edge
Content Source: articles/iot-edge/security.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

Thank you for your feedback @perkops. We want to improve the documentation based on your valuable feedback, can you please elaborate more so I can move your feedback through the right path?
Appreciate your time in advance.

@perkops I opened the article in a different browser and it was clear what you mean :). Fixing it now. Thank you so much.


Add missing wearable background

See https://github.com/rock3r/squanchy/blob/db69860c8d6b5abaabdb53ea738aa24e601b31e8/app/src/main/java/net/squanchy/notification/NotificationCreator.java#L85

CC @danybony

Done in #277


Adding CONTRIBUTORS.md file

CONTRIBUTORS.md file is added and it contains the photos along with usernames of the contributors and have a hyperlink pointing to their profiles.

Please ignore the previous pull requests as i was trying to squash and was facing difficulty in that.
The latest pull request is updated and contains content as per your specifications and is available at -
https://github.com/bddenhartog/docker-murmur/pull/44

Closed per #44.


Updating Intune device config images

Recommendation to update current Silverlight console images in doc to the current policies available within the Microsoft Endpoint Manager admin center.
VPN connection settings:

Custom OMA-URI policy settings:

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

ID: 746fd1a2-12c0-692c-f22a-251b370df7d7
Version Independent ID: 71ca5f84-9afb-4007-6d2d-db953756feca
Content: VPN connection types (Windows 10) - Microsoft 365 Security
Content Source: windows/security/identity-protection/vpn/vpn-connection-type.md
Product: w10
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Closing as duplicate of: https://github.com/MicrosoftDocs/windows-itpro-docs/pull/8638.


fix Windows ARM64 build and detect ARM64EC as ARM64

This PR solves two issues when building for Windows on ARM:

A compilation error in blake3_dispatch.c due to a missing include.
A misdetection of the ARM64EC ABI as AMD64.

The first issue manifests as follows. You can repro in an ARM64 Visual Studio Developer Command Prompt:
> cl.exe /nologo /diagnostics:caret /c blake3_dispatch.c

blake3_dispatch.c(106,16): error C2061: syntax error: identifier 'g_cpu_features'
    ATOMIC_INT g_cpu_features = UNDEFINED;
               ^
blake3_dispatch.c(106,16): error C2059: syntax error: ';'
blake3_dispatch.c(106,31): error C2513: ' ': no variable declared before '='
    ATOMIC_INT g_cpu_features = UNDEFINED;
                              ^
blake3_dispatch.c(115,31): error C2065: 'g_cpu_features': undeclared identifier
  enum cpu_feature features = ATOMIC_LOAD(g_cpu_features);

The second issue is more subtle. When building for the ARM64EC ABI, the compiler defines the _M_X64 macro and not the _M_ARM64 macro, to make incremental porting existing X64 Windows code to ARM easier.
This means that the BLAKE3 library was detecting ARM64EC as AMD64 and defining IS_X86 and IS_X86_64. This causes the library to compile in the SSE2 and SSE4.1 vector implementations of the algorithm instead of NEON, which amazingly does work even when building for Windows on ARM64, because Windows provides an emulated implementation of Intel SIMD instruction sets up to SSE4.2 in the softintrin.lib library. The end result is not ideal though, because it mixes native ARM64 code for the portable parts of the algorithm with emulated Intel SIMD intrinsics.
The second change is thus to make the CPU architecture detection in blake3_impl.h aware of the ARM64EC ABI so it can choose the NEON implementation.

Note that if #383 is merged after this change, it probably needs to change how it detects NEON so it doesn't just check for an __aarch64__ define and instead use IS_AARCH64 from blake3_impl.h.

Thanks for the fix and for the clear explanation!

Thanks! Will add a note to the other PR I mentioned so it’s compatible with this change.

the inline ARM assembly won't be compatible with Windows on ARM

why not? modern MSVC doesn't support __asm__ ?

It doesn't, no. It used to support it for 32-bit Windows apps (https://learn.microsoft.com/en-us/cpp/assembler/inline/inline-assembler?view=msvc-170), but it never supported inline assembly for 64-bit Windows.
They provide intrinsics for many common uses of inline assembly. For all other use cases, you need to use separate assembly files.


Use wharf-cmd-worker Docker image in wharf-cmd-provisioner

Inspired by RFC-0025: wharf-cmd provisioning

Depends on:

#10
#12

Requirements

Dockerfile to build wharf-cmd.
Publish to quay.io
Change wharf-cmd-provisioner to use wharf-cmd image

Out of scope (don't focus on this yet)

Publishing Docker image to quay.io. Instead we can rely on local testing or our internal Harbor.

Add CLI args or configs to wharf-cmd-worker to take in build metadata. Continued in #27

Change wharf-cmd-worker to log the build metadata. Continued in #28

Stealing this task from @Nisserino, as discussed in PM


Astropy style setup files

Closes: #16  this PR fixes the issues with the setup.py framework, which previously did not correctly place the awesimsoss directory in the site-packages/awesimsoss-egg.
This PR puts awesimsoss back on the astropy format for the setup.py files.
Behaviour:
The installation process finishes successfully
pip install git+https://github.com/spacetelescope/awesimsoss

results in: Successfully built awesimsoss
The failure occurs with python -c "import awesimsoss", which results with
ModuleNotFoundError: No module named 'awesimsoss'.
[Note: I also cloned the github repo and ran python setup.py install]
There exists a directory in my site-packages $HOME/anaconda3/lib/python3.6/site-packages/awesimsoss-0.1-py3.6.egg/. But the contents of that directory are only the EGG-INFO directory, and not awesimsoss directory; the latter is necessary for python to import awesimsoss.
It's likely that the setup.py file does not properly include the necessary features to create the full egg for installation.

Fixed in #14


Fix 64735 ServletContext.addJspFile() always fails with SecurityManager

Fix for: https://bz.apache.org/bugzilla/show_bug.cgi?id=64735

9.0.x PR: https://github.com/apache/tomcat/pull/358

Closing this PR. I'll add tests and fix the other SecurityManager issues in this class and resend.

Updated PR: https://github.com/apache/tomcat/pull/359


Docker doesn't work in the latest image

Docker daemon doesn't run by default. When trying to run it manually, it throws the following error:

Tested on:
RPi 4 / 4GB, running Umbrel OS v<IP_ADDRESS>

Looks like it worked after a reboot? The Pi was probably rebooted twice or thrice before docker seemed to work:

Ok so after I did docker-compose up, it pulled the latest images but all the services ran into FS errors:

Did a reboot, and docker-compose up again and there were no more FS errors. This also happened when I ran umbrel-compose on the 64-bit RPi (first run caused FS errors which were fixed after a reboot), so this issue is probably not related to umbrel-os.
Looking good now:

Looks like some hardware (media) issues? Im going to try it out soon

Not entirely sure... but it looks like the compose systemd service isn't working too. The containers don't autostart on boot:

Yes that is intentional not to autostart without the partitioning

btw I also have no issues with the image also

If you updated from very old images, you might need to chown data directories.

It was a fresh install on a new SD, so no old data :|

I can't reproduce this. I've already burned two images and installed on two different PIs

I'll retry 3rd time, nice and slow

Run 3 on Raspberry Pi 4 / 4GB running release v<IP_ADDRESS>
Errored out again:

dockerd logs (from /var/log/daemon.log):
May 31 15:56:31 umbrel fake-hwclock[129]: Sun 31 May 15:56:27 UTC 2020
May 31 15:56:31 umbrel systemd-fsck[142]: e2fsck 1.44.5 (15-Dec-2018)
May 31 15:56:31 umbrel systemd-fsck[142]: Superblock last write time is in the future.
May 31 15:56:31 umbrel systemd-fsck[142]: #011(by less than a day, probably due to the hardware clock being incorrectly set)
May 31 15:56:31 umbrel systemd-fsck[142]: rootfs: clean, 56619/137632 files, 443862/549888 blocks
May 31 15:56:31 umbrel systemd[1]: Started udev Coldplug all Devices.
May 31 15:56:31 umbrel systemd[1]: Starting Helper to synchronize boot up for ifupdown...
May 31 15:56:31 umbrel systemd[1]: Started Set the console keyboard layout.
May 31 15:56:31 umbrel systemd[1]: Started File System Check on Root Device.
May 31 15:56:31 umbrel systemd[1]: Starting Remount Root and Kernel File Systems...
May 31 15:56:31 umbrel systemd[1]: Started Helper to synchronize boot up for ifupdown.
May 31 15:56:31 umbrel systemd[1]: Started Remount Root and Kernel File Systems.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
May 31 15:56:31 umbrel systemd[1]: Starting Create System Users...
May 31 15:56:31 umbrel systemd[1]: Starting Load/Save Random Seed...
May 31 15:56:31 umbrel systemd[1]: Starting Flush Journal to Persistent Storage...
May 31 15:56:31 umbrel systemd[1]: Started Load/Save Random Seed.
May 31 15:56:31 umbrel systemd-sysusers[152]: Creating group systemd-coredump with gid 996.
May 31 15:56:31 umbrel systemd-sysusers[152]: Creating user systemd-coredump (systemd Core Dumper) with uid 996 and gid 996.
May 31 15:56:31 umbrel systemd[1]: Started Flush Journal to Persistent Storage.
May 31 15:56:31 umbrel systemd[1]: Started Create System Users.
May 31 15:56:31 umbrel systemd[1]: Starting Create Static Device Nodes in /dev...
May 31 15:56:31 umbrel systemd[1]: Started Create Static Device Nodes in /dev.
May 31 15:56:31 umbrel systemd[1]: Reached target Local File Systems (Pre).
May 31 15:56:31 umbrel systemd[1]: Starting udev Kernel Device Manager...
May 31 15:56:31 umbrel systemd[1]: Started udev Kernel Device Manager.
May 31 15:56:31 umbrel systemd-udevd[160]: Using default interface naming scheme 'v240'.
May 31 15:56:31 umbrel systemd[1]: Found device /dev/serial1.
May 31 15:56:31 umbrel systemd-udevd[163]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
May 31 15:56:31 umbrel systemd-udevd[168]: Using default interface naming scheme 'v240'.
May 31 15:56:31 umbrel systemd[1]: Found device /dev/disk/by-partuuid/7740b94a-01.
May 31 15:56:31 umbrel systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in FUSE Control File System being skipped.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in Huge Pages File System being skipped.
May 31 15:56:31 umbrel systemd[1]: Starting File System Check on /dev/disk/by-partuuid/7740b94a-01...
May 31 15:56:31 umbrel systemd[1]: Starting Load/Save RF Kill Switch Status...
May 31 15:56:31 umbrel systemd[1]: Started Load/Save RF Kill Switch Status.
May 31 15:56:31 umbrel systemd-fsck[274]: fsck.fat 4.1 (2017-01-24)
May 31 15:56:31 umbrel systemd-fsck[274]: /dev/mmcblk0p1: 308 files, 106175/516190 clusters
May 31 15:56:31 umbrel systemd[1]: Started File System Check on /dev/disk/by-partuuid/7740b94a-01.
May 31 15:56:31 umbrel systemd[1]: Mounting /boot...
May 31 15:56:31 umbrel systemd[1]: Mounted /boot.
May 31 15:56:31 umbrel systemd[1]: Reached target Local File Systems.
May 31 15:56:31 umbrel systemd[1]: Starting Commit a transient machine-id on disk...
May 31 15:56:31 umbrel systemd[1]: Starting Preprocess NFS configuration...
May 31 15:56:31 umbrel systemd[1]: Starting Raise network interfaces...
May 31 15:56:31 umbrel systemd[1]: Starting Set console font and keymap...
May 31 15:56:31 umbrel systemd[1]: Starting Create Volatile Files and Directories...
May 31 15:56:31 umbrel systemd[1]: nfs-config.service: Succeeded.
May 31 15:56:31 umbrel systemd[1]: Started Preprocess NFS configuration.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
May 31 15:56:31 umbrel systemd[1]: Reached target NFS client services.
May 31 15:56:31 umbrel systemd[1]: Reached target Remote File Systems (Pre).
May 31 15:56:31 umbrel systemd[1]: Reached target Remote File Systems.
May 31 15:56:31 umbrel systemd[1]: Started Set console font and keymap.
May 31 15:56:31 umbrel systemd[1]: Started Create Volatile Files and Directories.
May 31 15:56:31 umbrel systemd[1]: Starting Update UTMP about System Boot/Shutdown...
May 31 15:56:31 umbrel systemd[1]: Starting Network Time Synchronization...
May 31 15:56:31 umbrel systemd[1]: etc-machine\x2did.mount: Succeeded.
May 31 15:56:31 umbrel systemd[1]: Started Commit a transient machine-id on disk.
May 31 15:56:31 umbrel systemd[1]: Started Update UTMP about System Boot/Shutdown.
May 31 15:56:31 umbrel systemd[1]: Started Raise network interfaces.
May 31 15:56:31 umbrel systemd[1]: Started Network Time Synchronization.
May 31 15:56:31 umbrel systemd[1]: Reached target System Initialization.
May 31 15:56:31 umbrel systemd[1]: Started Daily Cleanup of Temporary Directories.
May 31 15:56:31 umbrel systemd[1]: Starting Docker Socket for the API.
May 31 15:56:31 umbrel systemd[1]: Listening on D-Bus System Message Bus Socket.
May 31 15:56:31 umbrel systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
May 31 15:56:31 umbrel systemd[1]: Listening on triggerhappy.socket.
May 31 15:56:31 umbrel systemd[1]: Reached target System Time Synchronized.
May 31 15:56:31 umbrel systemd[1]: Started Daily apt download activities.
May 31 15:56:31 umbrel systemd[1]: Started Daily man-db regeneration.
May 31 15:56:31 umbrel systemd[1]: Started Daily apt upgrade and clean activities.
May 31 15:56:31 umbrel systemd[1]: Started Daily rotation of log files.
May 31 15:56:31 umbrel systemd[1]: Reached target Timers.
May 31 15:56:31 umbrel systemd[1]: Listening on Docker Socket for the API.
May 31 15:56:31 umbrel systemd[1]: Reached target Sockets.
May 31 15:56:31 umbrel systemd[1]: Reached target Basic System.
May 31 15:56:31 umbrel systemd[1]: Starting dphys-swapfile - set up, mount/unmount, and delete a swap file...
May 31 15:56:31 umbrel systemd[1]: Starting LSB: Resize the root filesystem to fill partition...
May 31 15:56:31 umbrel systemd[1]: Starting Copy user wpa_supplicant.conf...
May 31 15:56:31 umbrel systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
May 31 15:56:31 umbrel systemd[1]: Starting rng-tools.service...
May 31 15:56:31 umbrel systemd[1]: Starting System Logging Service...
May 31 15:56:31 umbrel systemd[1]: Starting Configure Bluetooth Modems connected by UART...
May 31 15:56:31 umbrel systemd[1]: Starting triggerhappy global hotkey daemon...
May 31 15:56:31 umbrel systemd[1]: Starting Login Service...
May 31 15:56:31 umbrel systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
May 31 15:56:31 umbrel systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
May 31 15:56:31 umbrel systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
May 31 15:56:31 umbrel systemd[1]: Starting Regenerate SSH host keys...
May 31 15:56:31 umbrel rngd[362]: rngd 2-unofficial-mt.14 starting up...
May 31 15:56:31 umbrel rng-tools[348]: Starting Hardware RNG entropy gatherer daemon: rngd.
May 31 15:56:31 umbrel systemd[1]: Started Regular background program processing daemon.
May 31 15:56:31 umbrel systemd[1]: Started Manage Sound Card State (restore and store).
May 31 15:56:31 umbrel systemd[1]: Starting Save/Restore Sound Card State...
May 31 15:56:31 umbrel alsactl[370]: Found hardware: "bcm2835_headpho" "Broadcom Mixer" "" "" ""
May 31 15:56:31 umbrel alsactl[370]: Hardware is initialized using a generic method
May 31 15:56:31 umbrel thd[353]: Found socket passed from systemd
May 31 15:56:31 umbrel avahi-daemon[346]: Found user 'avahi' (UID 108) and group 'avahi' (GID 113).
May 31 15:56:31 umbrel systemd[1]: Started D-Bus System Message Bus.
May 31 15:56:31 umbrel rpi-eeprom-update[355]: BCM2711 detected
May 31 15:56:31 umbrel rpi-eeprom-update[355]: Dedicated VL805 EEPROM detected
May 31 15:56:31 umbrel alsactl[371]: /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
May 31 15:56:31 umbrel alsactl[371]: Found hardware: "bcm2835_headpho" "Broadcom Mixer" "" "" ""
May 31 15:56:31 umbrel alsactl[371]: Hardware is initialized using a generic method
May 31 15:56:31 umbrel systemd[1]: Starting WPA supplicant...
May 31 15:56:31 umbrel alsactl[370]: alsactl 1.1.8 daemon started
May 31 15:56:31 umbrel systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)...
May 31 15:56:31 umbrel alsactl[370]: /usr/sbin/alsactl: load_state:1683Cannot open /var/lib/alsa/asound.state for reading: No such file or directory
May 31 15:56:31 umbrel systemd[1]: Started triggerhappy global hotkey daemon.
May 31 15:56:31 umbrel avahi-daemon[346]: Successfully dropped root privileges.
May 31 15:56:31 umbrel systemd[1]: Started rng-tools.service.
May 31 15:56:31 umbrel avahi-daemon[346]: avahi-daemon 0.7 starting up.
May 31 15:56:31 umbrel systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master).
May 31 15:56:31 umbrel systemd[1]: Started Save/Restore Sound Card State.
May 31 15:56:31 umbrel resize2fs_once[340]: Starting resize2fs_once:resize2fs 1.44.5 (15-Dec-2018)
May 31 15:56:31 umbrel systemd[1]: Reached target Sound Card.
May 31 15:56:31 umbrel dd[358]: 1+0 records in
May 31 15:56:31 umbrel dd[358]: 1+0 records out
May 31 15:56:31 umbrel dd[358]: 4096 bytes (4.1 kB, 4.0 KiB) copied, 0.226699 s, 18.1 kB/s
May 31 15:56:31 umbrel systemd[1]: Started System Logging Service.
May 31 15:56:31 umbrel rngd[362]: entropy feed to the kernel ready
May 31 15:56:34 umbrel systemd[1]: Started Login Service.
May 31 15:56:34 umbrel avahi-daemon[346]: Successfully called chroot().
May 31 15:56:34 umbrel avahi-daemon[346]: Successfully dropped remaining capabilities.
May 31 15:56:34 umbrel wpa_supplicant[376]: Successfully initialized wpa_supplicant
May 31 15:56:34 umbrel systemd[1]: Started Copy user wpa_supplicant.conf.
May 31 15:56:34 umbrel systemd[1]: Started Avahi mDNS/DNS-SD Stack.
May 31 15:56:34 umbrel systemd[1]: Started WPA supplicant.
May 31 15:56:34 umbrel systemd[1]: Starting dhcpcd on all interfaces...
May 31 15:56:34 umbrel avahi-daemon[346]: No service file found in /etc/avahi/services.
May 31 15:56:34 umbrel avahi-daemon[346]: Network interface enumeration completed.
May 31 15:56:34 umbrel avahi-daemon[346]: Server startup complete. Host name is umbrel.local. Local service cookie is 232090797.
May 31 15:56:34 umbrel systemd[1]: systemd-rfkill.service: Succeeded.
May 31 15:56:34 umbrel raspi-config[357]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory
May 31 15:56:34 umbrel raspi-config[357]:  No. Switching to ondemand scaling governor.
May 31 15:56:34 umbrel systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
May 31 15:56:34 umbrel dhcpcd[427]: dev: loaded udev
May 31 15:56:34 umbrel dphys-swapfile[339]: want /var/swap=100MByte, generating swapfile ... of 100MBytes
May 31 15:56:34 umbrel systemd[1]: Started dphys-swapfile - set up, mount/unmount, and delete a swap file.
May 31 15:56:37 umbrel ssh-keygen[434]: ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
May 31 15:56:38 umbrel systemctl[463]: Removed /etc/systemd/system/multi-user.target.wants/regenerate_ssh_host_keys.service.
May 31 15:56:38 umbrel systemd[1]: Reloading.
May 31 15:56:39 umbrel systemd[1]: regenerate_ssh_host_keys.service: Succeeded.
May 31 15:56:39 umbrel systemd[1]: Started Regenerate SSH host keys.
May 31 15:56:39 umbrel dhcpcd[427]: wlan0: starting wpa_supplicant
May 31 15:56:40 umbrel dhcpcd-run-hooks[494]: wlan0: starting wpa_supplicant
May 31 15:56:41 umbrel dhcpcd[427]: wlan0: connected to Access Point `'
May 31 15:56:41 umbrel dhcpcd[427]: eth0: waiting for carrier
May 31 15:56:41 umbrel dhcpcd[427]: wlan0: waiting for carrier
May 31 15:56:41 umbrel dhcpcd[427]: wlan0: carrier acquired
May 31 15:56:44 umbrel systemd[1]: Condition check resulted in Turn on SSH if /boot/ssh is present being skipped.
May 31 15:56:44 umbrel dhcpcd[427]: DUID 00:01:00:01:26:66:90:3c:dc:a6:32:28:6c:1e
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: IAID 32:28:6c:1e
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: adding address fe80::5414:3551:c5b7:cd7b
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: carrier lost
May 31 15:56:44 umbrel avahi-daemon[346]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::5414:3551:c5b7:cd7b.
May 31 15:56:44 umbrel avahi-daemon[346]: New relevant interface wlan0.IPv6 for mDNS.
May 31 15:56:44 umbrel avahi-daemon[346]: Registering new address record for fe80::5414:3551:c5b7:cd7b on wlan0.*.
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: deleting address fe80::5414:3551:c5b7:cd7b
May 31 15:56:44 umbrel avahi-daemon[346]: Withdrawing address record for fe80::5414:3551:c5b7:cd7b on wlan0.
May 31 15:56:44 umbrel avahi-daemon[346]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::5414:3551:c5b7:cd7b.
May 31 15:56:44 umbrel avahi-daemon[346]: Interface wlan0.IPv6 no longer relevant for mDNS.
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: carrier acquired
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: connected to Access Point `SevenLuxury'
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: IAID 32:28:6c:1e
May 31 15:56:44 umbrel dhcpcd[427]: wlan0: adding address fe80::e9a0:bd3f:cc1b:a516
May 31 15:56:44 umbrel avahi-daemon[346]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::e9a0:bd3f:cc1b:a516.
May 31 15:56:44 umbrel avahi-daemon[346]: New relevant interface wlan0.IPv6 for mDNS.
May 31 15:56:44 umbrel avahi-daemon[346]: Registering new address record for fe80::e9a0:bd3f:cc1b:a516 on wlan0.*.
May 31 15:56:45 umbrel dhcpcd[427]: wlan0: soliciting an IPv6 router
May 31 15:56:45 umbrel dhcpcd[427]: wlan0: soliciting a DHCP lease
May 31 15:56:47 umbrel dhcpcd[427]: wlan0: Router Advertisement from fe80::217:7cff:fe70:8108
May 31 15:56:47 umbrel dhcpcd[427]: wlan0: no global addresses for default route
May 31 15:56:47 umbrel dhcpcd[427]: wlan0: requesting DHCPv6 information
May 31 15:56:47 umbrel dhcpcd[427]: wlan0: fe80::217:7cff:fe70:8108 is reachable again
May 31 15:56:49 umbrel btuart[351]: bcm43xx_init
May 31 15:56:49 umbrel btuart[351]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
May 31 15:56:49 umbrel btuart[351]: Set Controller UART speed to 3000000 bit/s
May 31 15:56:49 umbrel btuart[351]: Device setup complete
May 31 15:56:49 umbrel systemd[1]: Starting Load/Save RF Kill Switch Status...
May 31 15:56:49 umbrel systemd[1]: Started Configure Bluetooth Modems connected by UART.
May 31 15:56:50 umbrel systemd[1]: Created slice system-bthelper.slice.
May 31 15:56:50 umbrel systemd[1]: Starting Bluetooth service...
May 31 15:56:50 umbrel dhcpcd[427]: wlan0: probing for an IPv4LL address
May 31 15:56:50 umbrel rpi-eeprom-update[355]: BOOTFS /boot
May 31 15:56:50 umbrel rpi-eeprom-update[355]: BOOTLOADER: up-to-date
May 31 15:56:50 umbrel rpi-eeprom-update[355]: CURRENT: Thu 16 Apr 17:11:26 UTC 2020<PHONE_NUMBER>)
May 31 15:56:50 umbrel rpi-eeprom-update[355]:  LATEST: Thu 16 Apr 17:11:26 UTC 2020<PHONE_NUMBER>)
May 31 15:56:50 umbrel rpi-eeprom-update[355]:  FW DIR: /lib/firmware/raspberrypi/bootloader/critical
May 31 15:56:50 umbrel rpi-eeprom-update[355]: VL805: up-to-date
May 31 15:56:50 umbrel rpi-eeprom-update[355]: CURRENT: 000137ad
May 31 15:56:50 umbrel rpi-eeprom-update[355]:  LATEST: 000137ad
May 31 15:56:50 umbrel systemd[1]: Started Check for Raspberry Pi EEPROM updates.
May 31 15:56:51 umbrel dhcpcd[427]: wlan0: offered <IP_ADDRESS> from <IP_ADDRESS>
May 31 15:56:51 umbrel dhcpcd[427]: wlan0: ignoring offer of <IP_ADDRESS> from <IP_ADDRESS>
May 31 15:56:51 umbrel dhcpcd[427]: wlan0: probing address <IP_ADDRESS>/24
May 31 15:56:54 umbrel systemd[1]: Started Load/Save RF Kill Switch Status.
May 31 15:56:55 umbrel dhcpcd[427]: wlan0: using IPv4LL address <IP_ADDRESS>
May 31 15:56:55 umbrel avahi-daemon[346]: Joining mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
May 31 15:56:55 umbrel dhcpcd[427]: wlan0: adding route to <IP_ADDRESS>/16
May 31 15:56:55 umbrel dhcpcd[427]: wlan0: adding default route
May 31 15:56:55 umbrel avahi-daemon[346]: New relevant interface wlan0.IPv4 for mDNS.
May 31 15:56:55 umbrel avahi-daemon[346]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
May 31 15:56:55 umbrel dhcpcd[427]: forked to background, child pid 546
May 31 15:56:55 umbrel systemd[1]: Started dhcpcd on all interfaces.
May 31 15:56:55 umbrel systemd[1]: Reached target Network.
May 31 15:56:55 umbrel systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
May 31 15:56:55 umbrel systemd[1]: Starting Anonymizing overlay network for TCP...
May 31 15:56:55 umbrel systemd[1]: Starting OpenBSD Secure Shell server...
May 31 15:56:55 umbrel systemd[1]: Starting Permit User Sessions...
May 31 15:56:55 umbrel systemd[1]: Reached target Network is Online.
May 31 15:56:55 umbrel systemd[1]: Starting /etc/rc.local Compatibility...
May 31 15:56:56 umbrel systemd[1]: Starting Docker Application Container Engine...
May 31 15:56:56 umbrel systemd[1]: Started Permit User Sessions.
May 31 15:56:56 umbrel bluetoothd[530]: Bluetooth daemon 5.50
May 31 15:56:56 umbrel dhcpcd[546]: wlan0: leased <IP_ADDRESS> for 7200 seconds
May 31 15:56:56 umbrel avahi-daemon[346]: Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
May 31 15:56:56 umbrel dhcpcd[546]: wlan0: adding route to <IP_ADDRESS>/24
May 31 15:56:56 umbrel dhcpcd[546]: wlan0: changing default route via <IP_ADDRESS>
May 31 15:56:57 umbrel systemd[1]: Started Bluetooth service.
May 31 15:56:57 umbrel systemd[1]: Started Raspberry Pi bluetooth helper.
May 31 15:56:57 umbrel systemd[1]: Reached target Bluetooth.
May 31 15:56:58 umbrel bluetoothd[530]: Starting SDP server
May 31 15:56:59 umbrel bluetoothd[530]: Bluetooth management interface 1.14 initialized
May 31 15:56:59 umbrel dbus-daemon[372]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.6' (uid=0 pid=530 comm="/usr/lib/bluetooth/bluetoothd ")
May 31 15:56:59 umbrel systemd[1]: systemd-rfkill.service: Succeeded.
May 31 15:56:59 umbrel bluetoothd[530]: Sap driver initialization failed.
May 31 15:56:59 umbrel bluetoothd[530]: sap-server: Operation not permitted (1)
May 31 15:56:59 umbrel systemd[1]: Starting Hostname Service...
May 31 15:56:59 umbrel bthelper[588]: Changing power off succeeded
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F Powered: yes
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 00001801-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 00001200-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 00001800-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 00001801-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 00001200-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F UUIDs: 00001800-0000-1000-8000-00805f9b34fb
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F Alias: BlueZ 5.50
May 31 15:56:59 umbrel bthelper[588]: [#033[0;93mCHG#033[0m] Controller DC:A6:32:28:6C:1F Pairable: yes
May 31 15:56:59 umbrel bthelper[588]: Changing power on succeeded
May 31 15:57:00 umbrel systemd[1]: systemd-fsckd.service: Succeeded.
May 31 15:57:01 umbrel tor[553]: May 31 15:57:01.099 [notice] Tor <IP_ADDRESS> running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
May 31 15:57:01 umbrel tor[553]: May 31 15:57:01.100 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 31 15:57:01 umbrel dbus-daemon[372]: [system] Successfully activated service 'org.freedesktop.hostname1'
May 31 15:57:01 umbrel systemd[1]: Started Hostname Service.
May 31 15:57:01 umbrel avahi-daemon[346]: Withdrawing address record for <IP_ADDRESS> on wlan0.
May 31 15:57:01 umbrel avahi-daemon[346]: Leaving mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
May 31 15:57:01 umbrel avahi-daemon[346]: Joining mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
May 31 15:57:01 umbrel dhcpcd[546]: wlan0: deleting route to <IP_ADDRESS>/16
May 31 15:57:01 umbrel dhcpcd[546]: wlan0: failed to request information
May 31 15:57:01 umbrel dhcpcd[546]: wlan0: pid 546 deleted default route via <IP_ADDRESS>
May 31 15:57:01 umbrel tor[553]: May 31 15:57:01.477 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
May 31 15:57:01 umbrel systemd[1]<EMAIL_ADDRESS>Succeeded.
May 31 15:57:01 umbrel systemd[1]: Started OpenBSD Secure Shell server.
May 31 15:57:01 umbrel tor[553]: May 31 15:57:01.808 [notice] Read configuration file "/etc/tor/torrc".
May 31 15:57:04 umbrel tor[553]: Configuration was valid
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.008 [notice] Tor <IP_ADDRESS> running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.008 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.008 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.008 [notice] Read configuration file "/etc/tor/torrc".
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.018 [notice] Opening Socks listener on <IP_ADDRESS>:9050
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.018 [notice] Opened Socks listener on <IP_ADDRESS>:9050
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.018 [notice] Opening Control listener on <IP_ADDRESS>:9051
May 31 15:57:07 umbrel tor[635]: May 31 15:57:07.019 [notice] Opened Control listener on <IP_ADDRESS>:9051
May 31 15:57:08 umbrel Tor[635]: Tor <IP_ADDRESS> running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
May 31 15:57:08 umbrel Tor[635]: Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
May 31 15:57:08 umbrel Tor[635]: Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
May 31 15:57:08 umbrel Tor[635]: Read configuration file "/etc/tor/torrc".
May 31 15:57:08 umbrel Tor[635]: Opening Socks listener on <IP_ADDRESS>:9050
May 31 15:57:08 umbrel Tor[635]: Opened Socks listener on <IP_ADDRESS>:9050
May 31 15:57:08 umbrel Tor[635]: Opening Control listener on <IP_ADDRESS>:9051
May 31 15:57:08 umbrel Tor[635]: Opened Control listener on <IP_ADDRESS>:9051
May 31 15:57:08 umbrel Tor[635]: Your log may contain sensitive information - you're logging more than "notice". Don't log unless it serves an important reason. Overwrite the log afterwards.
May 31 15:57:08 umbrel Tor[635]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Jun  6 03:59:14 umbrel systemd[1]: Created slice User Slice of UID 1000.
Jun  6 03:59:14 umbrel systemd[1]: Starting User Runtime Directory /run/user/1000...
Jun  6 03:59:14 umbrel systemd[1]: Starting Daily man-db regeneration...
Jun  6 03:59:14 umbrel systemd[1]: Starting Rotate log files...
Jun  6 03:59:14 umbrel systemd[1]: Starting Daily apt download activities...
Jun  6 03:59:16 umbrel systemd[1]: Started User Runtime Directory /run/user/1000.
Jun  6 03:59:16 umbrel systemd[1]: Starting User Manager for UID 1000...
Jun  6 03:59:17 umbrel Tor[635]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Jun  6 03:59:21 umbrel systemd[1]: logrotate.service: Succeeded.
Jun  6 03:59:21 umbrel systemd[1]: Started Rotate log files.
Jun  6 03:59:24 umbrel systemd[1]: Started /etc/rc.local Compatibility.
Jun  6 03:59:24 umbrel systemd[1]: Started Getty on tty1.
Jun  6 03:59:24 umbrel systemd[1]: Reached target Login Prompts.
Jun  6 03:59:24 umbrel Tor[635]: Bootstrapped 0%: Starting
Jun  6 03:59:24 umbrel Tor[635]: Starting with guard context "default"
Jun  6 03:59:24 umbrel Tor[635]: Signaled readiness to systemd
Jun  6 03:59:24 umbrel systemd[1]: Started Anonymizing overlay network for TCP.
Jun  6 03:59:25 umbrel Tor[635]: Opening Control listener on /run/tor/control
Jun  6 03:59:25 umbrel Tor[635]: Opened Control listener on /run/tor/control
Jun  6 03:59:25 umbrel Tor[635]: Bootstrapped 5%: Connecting to directory server
Jun  6 03:59:25 umbrel Tor[635]: Bootstrapped 10%: Finishing handshake with directory server
Jun  6 03:59:25 umbrel systemd[645]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun  6 03:59:25 umbrel systemd[645]: Reached target Paths.
Jun  6 03:59:25 umbrel systemd[645]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jun  6 03:59:25 umbrel systemd[645]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jun  6 03:59:25 umbrel systemd[645]: Reached target Timers.
Jun  6 03:59:25 umbrel systemd[645]: Listening on GnuPG cryptographic agent and passphrase cache.
Jun  6 03:59:25 umbrel systemd[645]: Listening on GnuPG network certificate management daemon.
Jun  6 03:59:25 umbrel systemd[645]: Reached target Sockets.
Jun  6 03:59:25 umbrel systemd[645]: Reached target Basic System.
Jun  6 03:59:25 umbrel systemd[645]: Reached target Default.
Jun  6 03:59:25 umbrel systemd[645]: Startup finished in 8.712s.
Jun  6 03:59:25 umbrel systemd[1]: Started User Manager for UID 1000.
Jun  6 03:59:25 umbrel systemd[1]: Started Session c1 of user umbrel.
Jun  6 03:59:25 umbrel Tor[635]: Bootstrapped 15%: Establishing an encrypted directory connection
Jun  6 03:59:25 umbrel Tor[635]: Bootstrapped 20%: Asking for networkstatus consensus
Jun  6 03:59:25 umbrel Tor[635]: Bootstrapped 25%: Loading networkstatus consensus
Jun  6 03:59:30 umbrel Tor[635]: I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Jun  6 03:59:30 umbrel Tor[635]: Bootstrapped 40%: Loading authority key certs
Jun  6 03:59:31 umbrel Tor[635]: The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Jun  6 03:59:31 umbrel Tor[635]: Bootstrapped 45%: Asking for relay descriptors for internal paths
Jun  6 03:59:31 umbrel Tor[635]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6294, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Jun  6 03:59:32 umbrel Tor[635]: Bootstrapped 50%: Loading relay descriptors for internal paths
Jun  6 03:59:32 umbrel Tor[635]: I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6294, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Jun  6 03:59:32 umbrel systemd[1]: systemd-hostnamed.service: Succeeded.
Jun  6 03:59:37 umbrel Tor[635]: The current consensus contains exit nodes. Tor can build exit and internal paths.
Jun  6 03:59:40 umbrel Tor[635]: Bootstrapped 57%: Loading relay descriptors
Jun  6 03:59:40 umbrel Tor[635]: Bootstrapped 65%: Loading relay descriptors
Jun  6 03:59:40 umbrel Tor[635]: Bootstrapped 72%: Loading relay descriptors
Jun  6 03:59:41 umbrel Tor[635]: Bootstrapped 80%: Connecting to the Tor network
Jun  6 03:59:41 umbrel Tor[635]: Bootstrapped 85%: Finishing handshake with first hop
Jun  6 03:59:42 umbrel Tor[635]: Bootstrapped 90%: Establishing a Tor circuit
Jun  6 03:59:46 umbrel Tor[635]: Bootstrapped 100%: Done
Jun  6 04:00:17 umbrel dockerd[551]: time="2020-06-06T04:00:17.726733537Z" level=info msg="libcontainerd: started new docker-containerd process" pid=725
Jun  6 04:00:17 umbrel dockerd[551]: time="2020-06-06T04:00:17.755891038Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Jun  6 04:00:17 umbrel dockerd[551]: time="2020-06-06T04:00:17.755986661Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Jun  6 04:00:18 umbrel dockerd[551]: time="2020-06-06T04:00:18.493839801Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0  <nil>}]" module=grpc
Jun  6 04:00:18 umbrel dockerd[551]: time="2020-06-06T04:00:18.494052345Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jun  6 04:00:18 umbrel dockerd[551]: time="2020-06-06T04:00:18.494637766Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x49082c0, CONNECTING" module=grpc
Jun  6 04:00:27 umbrel dockerd[551]: time="2020-06-06T04:00:27.756097420Z" level=error msg="failed connecting to containerd" error="failed to dial \"/var/run/docker/containerd/containerd.sock\": context deadline exceeded" module=libcontainerd
Jun  6 04:00:27 umbrel dockerd[551]: time="2020-06-06T04:00:27.856557841Z" level=info msg="killing and restarting containerd" module=libcontainerd pid=725
Jun  6 04:00:27 umbrel dockerd[551]: time="2020-06-06T04:00:27.959481629Z" level=error msg="containerd did not exit successfully" error="signal: killed" module=libcontainerd
Jun  6 04:00:28 umbrel dockerd[551]: panic: runtime error: invalid memory address or nil pointer dereference
Jun  6 04:00:28 umbrel dockerd[551]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x18df928]
Jun  6 04:00:28 umbrel dockerd[551]: goroutine 38 [running]:
Jun  6 04:00:28 umbrel dockerd[551]: github.com/containerd/containerd.(*Client).Close(0x0, 0x0, 0x0)
Jun  6 04:00:28 umbrel dockerd[551]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/containerd/containerd/client.go:536 +0x24
Jun  6 04:00:28 umbrel dockerd[551]: github.com/docker/docker/libcontainerd/supervisor.(*remote).monitorDaemon(0x44a01a0, 0x2787fa8, 0x47d2f20)
Jun  6 04:00:28 umbrel dockerd[551]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:321 +0x1dc
Jun  6 04:00:28 umbrel dockerd[551]: created by github.com/docker/docker/libcontainerd/supervisor.Start
Jun  6 04:00:28 umbrel dockerd[551]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:90 +0x2ec
Jun  6 04:00:28 umbrel systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun  6 04:00:28 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Jun  6 04:00:28 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Jun  6 04:00:29 umbrel systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Jun  6 04:00:29 umbrel systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Jun  6 04:00:29 umbrel systemd[1]: Stopped Docker Application Container Engine.
Jun  6 04:00:29 umbrel systemd[1]: docker.socket: Succeeded.
Jun  6 04:00:29 umbrel systemd[1]: Closed Docker Socket for the API.
Jun  6 04:00:29 umbrel systemd[1]: Stopping Docker Socket for the API.
Jun  6 04:00:29 umbrel systemd[1]: Starting Docker Socket for the API.
Jun  6 04:00:29 umbrel systemd[1]: Listening on Docker Socket for the API.
Jun  6 04:00:29 umbrel systemd[1]: Starting Docker Application Container Engine...
Jun  6 04:00:34 umbrel dockerd[734]: time="2020-06-06T04:00:34.053077528Z" level=info msg="libcontainerd: started new docker-containerd process" pid=747
Jun  6 04:00:34 umbrel dockerd[734]: time="2020-06-06T04:00:34.056815686Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Jun  6 04:00:34 umbrel dockerd[734]: time="2020-06-06T04:00:34.058006014Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Jun  6 04:00:34 umbrel dockerd[734]: time="2020-06-06T04:00:34.059481984Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0  <nil>}]" module=grpc
Jun  6 04:00:34 umbrel dockerd[734]: time="2020-06-06T04:00:34.060521491Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jun  6 04:00:34 umbrel dockerd[734]: time="2020-06-06T04:00:34.061689651Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x4cf0910, CONNECTING" module=grpc
Jun  6 04:00:44 umbrel dockerd[734]: time="2020-06-06T04:00:44.057163729Z" level=error msg="failed connecting to containerd" error="failed to dial \"/var/run/docker/containerd/containerd.sock\": context deadline exceeded" module=libcontainerd
Jun  6 04:00:44 umbrel dockerd[734]: time="2020-06-06T04:00:44.157676713Z" level=info msg="killing and restarting containerd" module=libcontainerd pid=747
Jun  6 04:00:44 umbrel dockerd[734]: time="2020-06-06T04:00:44.261152004Z" level=error msg="containerd did not exit successfully" error="signal: killed" module=libcontainerd
Jun  6 04:00:45 umbrel dockerd[734]: panic: runtime error: invalid memory address or nil pointer dereference
Jun  6 04:00:45 umbrel dockerd[734]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x18fc928]
Jun  6 04:00:45 umbrel dockerd[734]: goroutine 13 [running]:
Jun  6 04:00:45 umbrel dockerd[734]: github.com/containerd/containerd.(*Client).Close(0x0, 0x0, 0x0)
Jun  6 04:00:45 umbrel dockerd[734]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/containerd/containerd/client.go:536 +0x24
Jun  6 04:00:45 umbrel dockerd[734]: github.com/docker/docker/libcontainerd/supervisor.(*remote).monitorDaemon(0x48ac1a0, 0x27a4fa8, 0x4d65400)
Jun  6 04:00:45 umbrel dockerd[734]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:321 +0x1dc
Jun  6 04:00:45 umbrel dockerd[734]: created by github.com/docker/docker/libcontainerd/supervisor.Start
Jun  6 04:00:45 umbrel dockerd[734]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:90 +0x2ec
Jun  6 04:00:45 umbrel systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun  6 04:00:45 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Jun  6 04:00:45 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Jun  6 04:00:45 umbrel systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Jun  6 04:00:45 umbrel systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Jun  6 04:00:45 umbrel systemd[1]: Stopped Docker Application Container Engine.
Jun  6 04:00:45 umbrel systemd[1]: docker.socket: Succeeded.
Jun  6 04:00:45 umbrel systemd[1]: Closed Docker Socket for the API.
Jun  6 04:00:45 umbrel systemd[1]: Stopping Docker Socket for the API.
Jun  6 04:00:45 umbrel systemd[1]: Starting Docker Socket for the API.
Jun  6 04:00:45 umbrel systemd[1]: Listening on Docker Socket for the API.
Jun  6 04:00:45 umbrel systemd[1]: Starting Docker Application Container Engine...
Jun  6 04:00:49 umbrel dockerd[756]: time="2020-06-06T04:00:49.261899517Z" level=info msg="libcontainerd: started new docker-containerd process" pid=765
Jun  6 04:00:49 umbrel dockerd[756]: time="2020-06-06T04:00:49.263359355Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Jun  6 04:00:49 umbrel dockerd[756]: time="2020-06-06T04:00:49.263555080Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Jun  6 04:00:49 umbrel dockerd[756]: time="2020-06-06T04:00:49.264000551Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0  <nil>}]" module=grpc
Jun  6 04:00:49 umbrel dockerd[756]: time="2020-06-06T04:00:49.264139442Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jun  6 04:00:49 umbrel dockerd[756]: time="2020-06-06T04:00:49.264409928Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x440d550, CONNECTING" module=grpc
Jun  6 04:00:59 umbrel dockerd[756]: time="2020-06-06T04:00:59.263720771Z" level=error msg="failed connecting to containerd" error="failed to dial \"/var/run/docker/containerd/containerd.sock\": context deadline exceeded" module=libcontainerd
Jun  6 04:00:59 umbrel dockerd[756]: time="2020-06-06T04:00:59.364345498Z" level=info msg="killing and restarting containerd" module=libcontainerd pid=765
Jun  6 04:00:59 umbrel dockerd[756]: time="2020-06-06T04:00:59.468295697Z" level=error msg="containerd did not exit successfully" error="signal: killed" module=libcontainerd
Jun  6 04:01:00 umbrel dockerd[756]: panic: runtime error: invalid memory address or nil pointer dereference
Jun  6 04:01:00 umbrel dockerd[756]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x185b928]
Jun  6 04:01:00 umbrel dockerd[756]: goroutine 68 [running]:
Jun  6 04:01:00 umbrel dockerd[756]: github.com/containerd/containerd.(*Client).Close(0x0, 0x0, 0x0)
Jun  6 04:01:00 umbrel dockerd[756]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/containerd/containerd/client.go:536 +0x24
Jun  6 04:01:00 umbrel dockerd[756]: github.com/docker/docker/libcontainerd/supervisor.(*remote).monitorDaemon(0x449c410, 0x2703fa8, 0x49cc1c0)
Jun  6 04:01:00 umbrel dockerd[756]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:321 +0x1dc
Jun  6 04:01:00 umbrel dockerd[756]: created by github.com/docker/docker/libcontainerd/supervisor.Start
Jun  6 04:01:00 umbrel dockerd[756]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:90 +0x2ec
Jun  6 04:01:00 umbrel systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun  6 04:01:00 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Jun  6 04:01:00 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Jun  6 04:01:00 umbrel systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Jun  6 04:01:00 umbrel systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun  6 04:01:00 umbrel systemd[1]: Stopped Docker Application Container Engine.
Jun  6 04:01:00 umbrel systemd[1]: docker.socket: Succeeded.
Jun  6 04:01:00 umbrel systemd[1]: Closed Docker Socket for the API.
Jun  6 04:01:00 umbrel systemd[1]: Stopping Docker Socket for the API.
Jun  6 04:01:00 umbrel systemd[1]: Starting Docker Socket for the API.
Jun  6 04:01:00 umbrel systemd[1]: Listening on Docker Socket for the API.
Jun  6 04:01:00 umbrel systemd[1]: Starting Docker Application Container Engine...
Jun  6 04:01:00 umbrel dockerd[791]: time="2020-06-06T04:01:00.880983448Z" level=info msg="libcontainerd: started new docker-containerd process" pid=799
Jun  6 04:01:00 umbrel dockerd[791]: time="2020-06-06T04:01:00.881411385Z" level=info msg="parsed scheme: \"unix\"" module=grpc
Jun  6 04:01:00 umbrel dockerd[791]: time="2020-06-06T04:01:00.881455808Z" level=info msg="scheme \"unix\" not registered, fallback to default scheme" module=grpc
Jun  6 04:01:00 umbrel dockerd[791]: time="2020-06-06T04:01:00.881635926Z" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///var/run/docker/containerd/containerd.sock 0  <nil>}]" module=grpc
Jun  6 04:01:00 umbrel dockerd[791]: time="2020-06-06T04:01:00.881692960Z" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jun  6 04:01:00 umbrel dockerd[791]: time="2020-06-06T04:01:00.881810138Z" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0x489f4f0, CONNECTING" module=grpc
Jun  6 04:01:10 umbrel dockerd[791]: time="2020-06-06T04:01:10.881967827Z" level=error msg="failed connecting to containerd" error="failed to dial \"/var/run/docker/containerd/containerd.sock\": context deadline exceeded" module=libcontainerd
Jun  6 04:01:10 umbrel dockerd[791]: time="2020-06-06T04:01:10.984937687Z" level=info msg="killing and restarting containerd" module=libcontainerd pid=799
Jun  6 04:01:11 umbrel dockerd[791]: time="2020-06-06T04:01:11.089729239Z" level=error msg="containerd did not exit successfully" error="signal: killed" module=libcontainerd
Jun  6 04:01:12 umbrel dockerd[791]: panic: runtime error: invalid memory address or nil pointer dereference
Jun  6 04:01:12 umbrel dockerd[791]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x190f928]
Jun  6 04:01:12 umbrel dockerd[791]: goroutine 26 [running]:
Jun  6 04:01:12 umbrel dockerd[791]: github.com/containerd/containerd.(*Client).Close(0x0, 0x0, 0x0)
Jun  6 04:01:12 umbrel dockerd[791]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/containerd/containerd/client.go:536 +0x24
Jun  6 04:01:12 umbrel dockerd[791]: github.com/docker/docker/libcontainerd/supervisor.(*remote).monitorDaemon(0x48ac1a0, 0x27b7fa8, 0x491e4c0)
Jun  6 04:01:12 umbrel dockerd[791]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:321 +0x1dc
Jun  6 04:01:12 umbrel dockerd[791]: created by github.com/docker/docker/libcontainerd/supervisor.Start
Jun  6 04:01:12 umbrel dockerd[791]: #011/home/pi/dev/docker.io-18.09.1+dfsg1/.gopath/src/github.com/docker/docker/libcontainerd/supervisor/remote_daemon.go:90 +0x2ec
Jun  6 04:01:12 umbrel systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun  6 04:01:12 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Jun  6 04:01:12 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Jun  6 04:01:12 umbrel systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart.
Jun  6 04:01:12 umbrel systemd[1]: docker.service: Scheduled restart job, restart counter is at 4.
Jun  6 04:01:12 umbrel systemd[1]: Stopped Docker Application Container Engine.
Jun  6 04:01:12 umbrel systemd[1]: docker.socket: Succeeded.
Jun  6 04:01:12 umbrel systemd[1]: Closed Docker Socket for the API.
Jun  6 04:01:12 umbrel systemd[1]: Stopping Docker Socket for the API.
Jun  6 04:01:12 umbrel systemd[1]: Starting Docker Socket for the API.
Jun  6 04:01:12 umbrel systemd[1]: Listening on Docker Socket for the API.
Jun  6 04:01:12 umbrel systemd[1]: docker.service: Start request repeated too quickly.
Jun  6 04:01:12 umbrel systemd[1]: docker.service: Failed with result 'exit-code'.
Jun  6 04:01:12 umbrel systemd[1]: Failed to start Docker Application Container Engine.
Jun  6 04:01:12 umbrel systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
Jun  6 04:02:07 umbrel systemd[1]: apt-daily.service: Succeeded.
Jun  6 04:02:07 umbrel systemd[1]: Started Daily apt download activities.
Jun  6 04:02:07 umbrel systemd[1]: Starting Daily apt upgrade and clean activities...
Jun  6 04:02:08 umbrel systemd[1]: apt-daily-upgrade.service: Succeeded.
Jun  6 04:02:08 umbrel systemd[1]: Started Daily apt upgrade and clean activities.
Jun  6 04:02:12 umbrel resize2fs_once[340]: Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required
Jun  6 04:02:12 umbrel resize2fs_once[340]: old_desc_blocks = 1, new_desc_blocks = 4
Jun  6 04:02:12 umbrel resize2fs_once[340]: The filesystem on /dev/mmcblk0p2 is now 15596288 (4k) blocks long.
Jun  6 04:02:21 umbrel systemd[1]: Reloading.
Jun  6 04:02:21 umbrel systemd[1]<EMAIL_ADDRESS>Current command vanished from the unit file, execution of the command list won't be resumed.
Jun  6 04:02:21 umbrel systemd[1]: Reached target Multi-User System.
Jun  6 04:02:21 umbrel systemd[1]: Reached target Graphical Interface.
Jun  6 04:02:21 umbrel systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jun  6 04:02:21 umbrel resize2fs_once[340]: .
Jun  6 04:02:21 umbrel systemd[1]: Started LSB: Resize the root filesystem to fill partition.
Jun  6 04:02:21 umbrel systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jun  6 04:02:21 umbrel systemd[1]: Started Update UTMP about System Runlevel Changes.
Jun  6 04:02:21 umbrel systemd[1]: man-db.service: Succeeded.
Jun  6 04:02:21 umbrel systemd[1]: Started Daily man-db regeneration.
Jun  6 04:02:21 umbrel systemd[1]: Startup finished in 1.050s (kernel) + 3min 54.356s (userspace) = 3min 55.407s.


Update mesos-util dependency to 0.22.1-1

Dockerfile should be updated to use the new mesos.

Will do once a 0.22.1 image has been pushed.


refactor: missing a value for letterSpacing

If used like this definition letterSpacing: theme('letterSpacing.tight'), we need to have its value or remove it from the code.

It's a default, see tailwind docs.

According to this docs, the default value tightest not tight

It's a default, see tailwind docs.

Right. But for some reason, it doesn't always work (on my side) for MDX without specifying it in tailwind.config.js


Unexpected layer enum behavior

Unexpected layer enum behavior
Expected behavior
When selecting layers in the inspector with parent box fields
Code Sample
[System.Serializable, DeclareFoldoutGroup("Raycaster")]
public class RaycasterSettings
{
    [GroupNext("Raycaster")]
    [ShowInInspector, HideReferencePicker] public LayerMask MaskRoomInteract { get; private set; }
    [ShowInInspector, HideReferencePicker] public LayerMask MaskAimInteract { get; private set; }
    [ShowInInspector, HideReferencePicker] public LayerMask MaskAimDistance { get; private set; }
    [ShowInInspector, HideReferencePicker] public float MaxInteractDistance { get; private set; } = 3.1f;
    [ShowInInspector, HideReferencePicker]
    public float MaxAimDistance { get; private set; } = 700f;
}

Screenshots
https://github.com/user-attachments/assets/da2f7075-7613-488b-ab89-5046d990be8c
Desktop: Windows 11
Unity version: 2022.3.14f1
Tri Inspector version: 1.14.1

Also, the problem could persist due to parent attributes
[InlineProperty, HideLabel] public RaycasterSettings Raycaster;


⚠ quantum-cli has degraded performance

In c5e0aa9, quantum-cli (https://cli.planetary-quantum.com/) experienced degraded performance:

HTTP code: 200
Response time: 3884 ms

Resolved: quantum-cli performance has improved in 2a9d33e.

Looks like Github Pages was degraded. Couldn't find an incident though.


Connection to  Exposed ports on containers fails intermittently.

Server version - Build from master on Aug 4
Create service1 which is linked to service2. Service 1 has exposed port - public port - 309 -> private port - 22.
Waited for both the services to be activated.
After 5 sec delay , tried to access -service1 by trying to ssh to port 309 on the host the container of service1 is running.
We get "Connection refused" error.
After few minutes , when i try to access the same ports , i get access to the containers.
Why is there a delay in accessing the exposed ports? This issue is not always reproducible. I have been able to access the exposed ports after 5 secs of creation most of the time.

Validation tests run on V1.0.0-rc3 does not encounter this problem anymore.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2994

Questions ?
Please refer to the Backport tool documentation


feat: add onSubgraphError

Change the behavior on fetching subgraph schema: instead of throwing an error, emit an event.
This allow to have partial schema from the defined ones

cc @cjihrig


Feature/geography homepage

What
added
CodeLists API URL config
GeographyRender to GeographyHomepageRender
log.Errors
404 error
geographyTypes loop
Name to Label for api consistency
remove instance/instance_internal_test.go
govendor
How to review
Run geography
https://github.com/ONSdigital/dp-frontend-geography-controller/tree/feature/geographyHomepage
https://github.com/ONSdigital/dp-frontend-renderer/tree/feature/geography-controller
https://github.com/ONSdigital/dp-frontend-models/tree/feature/geography-controller
and goto
http://localhost:23700/geography
Who can review
all

Another thing which is probably worth doing is


Text in non-HTML editors can be formatted (e.g., bolded)

Describe the Bug with repro steps

Open any workflow in the designer.
Ensure the open workflow has some action or trigger with a text-based input that is NOT an HTML editor.
Enter something in the above text-based input.
Highlight the entered text.
Hit Ctrl+B (or Cmd+B on Mac).

Expected: Nothing should happen.
Actual: Text becomes bold.
(Also works with italics using Ctrl+I, etc.)
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Windows 11 / Chrome 119.0.6045.159.
Additional context
No response
AB#25854136

Does this have any functionality issues or just cosmetic?

It's purely cosmetic, due to how our serialization works on non-htmlEditor editors which only get the the text content from the lexical text node


Add the tenant into the short URL once the short URL is resolved

Description
This is a duplicate PR (closed) to https://github.com/opensearch-project/security-dashboards-plugin/pull/1443,
Copying the changes from a branch branched from main allowed me a cleaner & safer way to perform similar rebase.

When the tenancy is being changed after copying a short URL, if the user then pastes this short URL into a new tab, the user will be redirected to the current selected tenant, not the tenant as specified in the copied short URL.
We need to retain this information in the URL and redirect so the user is brought to the correct link, with the correct user.
Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Why these changes are required?
To enable sharing of a short URL with the tenant as specified in the URL remaining selected as the active tenant.
What is the old behavior before changes and new behavior after changes?
The old behaviour is:

A short URL is copied (tenant is specified in the URL)
The tenant is changed
The link is loaded in a new tab
The tenant remains as is specified in 2, not as we would want/expect it to be as per the URL
The new behaviour is:
A short URL is copied (tenant is specified in the URL)
The tenant is changed
The link is loaded in a new tab
The link is loaded with tenant info retained.

The goal of the piece of code

Solve issue 1203 which led to the user being directed to the incorrect tenant. This was happening in the case the short URL was copied, then the tenant was changed & the URL was loaded in a new tab.The outcome was the tenant specified in the short URL was not maintained on page load.

How it is done

The short URL when copied and pasted has the security_tenant, however, when the URL is being rendered and parsed, this information was not retained in the resolved short URL.
Upon page reload, the security tenant was fetched again from the localstorage, which was the switched tenant (not the tenant originally specified in the short URL.)

Why it is done this way

Therefore in the case of multitenancy, when parsing the short URL, we inject the security tenant into the short URL, adding it as a parameter and retaining this information then in the resolved URL. Allowing the page to correctly load the page, with the correct tenant that was specified & copied in the short URL.
The addTenantParameterToResolvedShortLink controls this functionality.

Other attempted solutions:
The first solution implemented to fix this issue, was to wipe the local storage to solve this issue.
However, once it was done, I realised the localstorage value was needed elsewhere & could not be wiped as intended.
New solutions were considered, perhaps using a cookie, which came with it's own challenges to change how localstorage is currently being used.
In the end, the solution that maintained the localstorage (as it was needed in the code for other purposes) and solved the issue at hand (couldn't change the tenant after copying the short URL), was to, if the tenant was changed in multitenancy mode, to make sure the tenant information remained in the short URL (it was there before page load but is removed from the resolved URL, we ensured the tenant information was retained in the resolved URL) and also, remove any specifics of the URL (so the user wouldn't be brought to a dashboard that doesn't exist in that tenant and get an error message).
Issues Resolved
[BUG] Shortlinks to other Tenants do not work #1203
Testing
Submitting the PR for an initial review of changes, tests will follow.
Check List

[x] New functionality includes testing
[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Details

Hi @DarshitChanpura, some of the tests seem to be failing. Do you have any guidance on what I can do to solve this please?

@scrawfor99 Could you look into the failures, seems like there is an issue with the ubuntu build.  Might be from OpenSearch, it might be from security?
java.lang.Exception: java.lang.NoClassDefFoundError: org/opensearch/common/lease/Releasable
	at org.opensearch.transport.netty4.Netty4MessageChannelHandler.exceptionCaught(Netty4MessageChannelHandler.java:106) [transport-netty4-client-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
...

@peternied

Can we add or modify an integration test for this scenario? Thanks for the unit tests; testing this in a browser seems like a requirement to know if this issue is fixed.

Sure.
I would like to check just one thing:
There is already a test suite at https://github.com/opensearch-project/security-dashboards-plugin/blob/e628c81b4589b63264158a971f95a7b5a1e5e4a1/test/jest_integration/multi_tenancy.test.ts which we could extend.
However, it seems that the preferred way of writing tests is now adding these to https://github.com/opensearch-project/opensearch-dashboards-functional-test  according to https://github.com/opensearch-project/opensearch-dashboards-functional-test/blob/main/DEVELOPER_GUIDE.md#tests-for-opensearch-dashboard-plugins
What do you think?

I'd bow to the wisdom of anyone with more experience in these different frameworks, @RyanL1997 @DarshitChanpura do you have thoughts for testing this scenario?
My off the cuff suggestion would be to write them with jest since its in this repository.

I'd bow to the wisdom of anyone with more experience in these different frameworks, @RyanL1997 @DarshitChanpura do you have thoughts for testing this scenario?
My off the cuff suggestion would be to write them with jest since its in this repository.

Hi @DarshitChanpura & @RyanL1997, to follow on from this we had a further look into the testing and there are some multitenancy tests that have been added recently to the external functional test repo:
https://github.com/opensearch-project/opensearch-dashboards-functional-test/tree/main/cypress/integration/plugins/security-dashboards-plugin
These tests then seem to be triggered through github actions in the plugin repo:
https://github.com/opensearch-project/security-dashboards-plugin/blob/main/.github/workflows/cypress-test-tenancy-disabled.yml#L76
Those tests are cypress test, it seems that could be a good path forward? Thanks.

Hey @leanneeliatra I'd suggest writing a unit test in jest and an end-to-end test in functional test repo.

Thanks @DarshitChanpura, I'll do that.


Add login for mlx-ui

Add authentication in /login path. Use basic auth and simple
user model from a configuration in local file system. After a
successfull login, a cookie will be set in the browser and the user
info will be store in server. Currently, memorystore is used to
store session information. we can move it to persistent storage
later.
Signed-off-by: Yihong Wang<EMAIL_ADDRESS>

LGTM
@drewbutlerbb4 @Tomcli -- are we okay to merge this?

@yhwang did this PR included the changes you have from yesterday?

@Tomcli this PR is for serving basic authentication in <base path>/login. for basic authentication, it enables the session and cookie.

lgtm


Enhancing UI of login section

I would like to improve the UI of login section. Could you please assign this issue to me under hacktoberfest2022 @ishitakapoor26

@sirichandana-v go ahead!

Hi @ishitakapoor26 I can make a nice login page for you, which will add value. Please assign this to me

@c99SRS go ahead!

i want to contribute on it please assign

@c99SRS go ahead!

@ishitakapoor26 Is it still open??


Unable to create remote tunnel through a proxy

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: code-cli 1.81.0 (commit 6445d93c81ebe42c4cbd7a60712e0b17d9463e97)
OS Version: Linux g110 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I want to reopen https://github.com/microsoft/vscode/issues/169333.
Here is what I get
code-insiders --disable-extensions tunnel --cli-data-dir "$TMPDIR" --verbose
*
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
*
[2023-08-03 14:31:51] debug Starting tunnel with `code-insiders code-insiders --disable-extensions tunnel --cli-data-dir /tmp --verbose`
[2023-08-03 14:31:51] debug starting as new singleton
[2023-08-03 14:31:51] debug Using file keychain storage due to: error reading keyring: Platform secure storage failure: no secret service provider or dbus session found
[2023-08-03 14:31:51] trace Found token in keyring
[2023-08-03 14:31:51] debug [reqwest::connect] starting new connection: https://api.github.com/
[2023-08-03 14:31:51] debug [reqwest::connect] proxy(http://proxy:8080) intercepts 'https://api.github.com/'
[2023-08-03 14:31:51] debug [reqwest::connect] starting new connection: https://euw.rel.tunnels.api.visualstudio.com/
[2023-08-03 14:31:51] debug [reqwest::connect] proxy(http://proxy:8080) intercepts 'https://euw.rel.tunnels.api.visualstudio.com/'
[2023-08-03 14:31:51] debug Starting tunnel to server...
[2023-08-03 14:31:51] trace Found token in keyring
[2023-08-03 14:31:52] debug [tunnels::connections::relay_tunnel_host] connecting via http_proxy on http://proxy:8080
[2023-08-03 14:31:57] warn Error connecting to relay, will retry: error connecting to tunnel: proxy connection failed: failed to lookup address information: Try again
[2023-08-03 14:31:57] error Error connecting to tunnel endpoint: error connecting to tunnel: proxy connection failed: failed to lookup address information: Try again
[2023-08-03 14:31:57] trace Found token in keyring
[2023-08-03 14:32:02] debug Starting tunnel to server...
[2023-08-03 14:32:02] trace Found token in keyring
[2023-08-03 14:32:02] trace Successfully refreshed access token
[2023-08-03 14:32:02] trace Found token in keyring
[2023-08-03 14:32:02] debug [tunnels::connections::relay_tunnel_host] connecting via http_proxy on http://proxy:8080

I also tried code instead of code-insiders, the same issue occurs.
It runs fine as long as there is no proxy, but once the proxy is set, it does not work. Websockets are supported according to http://websocketstest.com.
Btw, I am using /tmp because that is the only directory which supports file locking.

Same issue for me with GitHub Copilot on Remote SSH:
GitHub Copilot could not connect to server. Extension activation failed: "tunneling socket could not be established, cause=Failed to establish a socket connection to proxies: ["SOCKS brd-customer@brd.superproxy.io:22225"]"
This error started happening after update to 1.81.0

I also encountered this problem, maybe vscode tried to resolve the proxy URL, but on my server, DNS was not available, so I provided the IP address as proxy url. I think that the DNS query should not be called when the proxy URL is an IP.

I tested many possibilities and finally found that when I set the http_proxy to <IP_ADDRESS>:1080, vscode would resolve the proxy url through DNS server and fail. But when I set the http_proxy to localhost:1080, vscode will resolve using hosts file and work normally. I think this feature is strange.

Most likely your proxy server is bound to your IPv6 loopback and not your IPv4 loopback.

Merging into https://github.com/microsoft/vscode/issues/201417


(PTS)Bluetooth: SM/SLA/SIP/BV-01-C Error

Describe the bug
MITM bit in Pairing Request cannot be set to cleared. Zephyr aplication doesn't support set BTP MITM off command.
To Reproduce
run auto-pts
SM_SLA_SIP_BV-01-C-FAIL.zip

CC @jhedberg @joerchan

Lowering to medium since this is a tester issue.

The BTP MITM command needs to be implemented.

The test doesn't seem to bue using the MITM command (0x1b):
*** Booting Zephyr OS build v2.2.0-rc1-263-gcee1954ac394  **
[00:00:00.000,000] <dbg> bttester.tester_init: Initializing tester
[00:00:00.020,294] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.020,324] <inf> bt_hci_core: HW Variant: nRF52x (0x0002)
[00:00:00.020,324] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 2.2 Build 0
[00:00:00.021,514] <inf> bt_hci_core: Identity: e6:37:9e:89:3f:ab (random)
[00:00:00.021,514] <inf> bt_hci_core: HCI: version 5.1 (0x0a) revision 0x0000, manufacturer 0x05f1
[00:00:00.021,514] <inf> bt_hci_core: LMP: version 5.1 (0x0a) subver 0xffff
[00:00:00.034,667] <dbg> bttester_gap.tester_handle_gap: opcode: 0x03
[00:00:00.360,900] <dbg> bttester_gap.tester_handle_gap: opcode: 0x10
[00:00:07.799,133] <dbg> bttester_gap.tester_handle_gap: opcode: 0x08
[00:00:07.804,321] <dbg> bttester_gap.tester_handle_gap: opcode: 0x0a
[00:00:08.037,933] <dbg> bttester_gap.tester_handle_gap: opcode: 0x11


⚠ Bofrost.lu has degraded performance

In 79178cc, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1287 ms

Resolved: Bofrost.lu performance has improved in 7c88774 after 29 minutes.