Problems when calculation curvature distribution: supplied range of [nan, nan] is not finite

After installation of version 0.13.0 and recalculating all curvature distribution analyses, I see several messages
like
celeryworker_1  | 2021-06-16T13:26:00.162998082Z [2021-06-16 15:26:00,162: ERROR/ForkPoolWorker-3] Task topobank.taskapp.tasks.perform_analysis[2364aa7d-a5ff-4a2b-9921-e60ca296f3e8] raised unexpected: ValueError('supplied range of [nan, nan] is not finite')
celeryworker_1  | 2021-06-16T13:26:00.163021434Z Traceback (most recent call last):
celeryworker_1  | 2021-06-16T13:26:00.163025501Z   File "/opt/conda/lib/python3.7/site-packages/celery/app/trace.py", line 412, in trace_task
celeryworker_1  | 2021-06-16T13:26:00.163028864Z     R = retval = fun(*args, **kwargs)
celeryworker_1  | 2021-06-16T13:26:00.163032895Z   File "/opt/conda/lib/python3.7/site-packages/celery/app/trace.py", line 704, in __protected_call__
celeryworker_1  | 2021-06-16T13:26:00.163036763Z     return self.run(*args, **kwargs)
celeryworker_1  | 2021-06-16T13:26:00.163039747Z   File "/app/topobank/taskapp/tasks.py", line 127, in perform_analysis
celeryworker_1  | 2021-06-16T13:26:00.163042729Z     result = analysis.function.eval(subject, **kwargs)
celeryworker_1  | 2021-06-16T13:26:00.163045406Z   File "/app/topobank/analysis/models.py", line 288, in eval
celeryworker_1  | 2021-06-16T13:26:00.163048281Z     return self.get_implementation(subject_type).eval(subject, **kwargs)
celeryworker_1  | 2021-06-16T13:26:00.163051166Z   File "/app/topobank/analysis/models.py", line 340, in eval
celeryworker_1  | 2021-06-16T13:26:00.163054009Z     return pyfunc(subject, **kwargs)
celeryworker_1  | 2021-06-16T13:26:00.163056660Z   File "/app/topobank/analysis/functions.py", line 315, in curvature_distribution
celeryworker_1  | 2021-06-16T13:26:00.163070037Z     density=True)
celeryworker_1  | 2021-06-16T13:26:00.163073123Z   File "<__array_function__ internals>", line 6, in histogram
celeryworker_1  | 2021-06-16T13:26:00.163077083Z   File "/opt/conda/lib/python3.7/site-packages/numpy/lib/histograms.py", line 792, in histogram
celeryworker_1  | 2021-06-16T13:26:00.163080020Z     bin_edges, uniform_bins = _get_bin_edges(a, bins, range, weights)
celeryworker_1  | 2021-06-16T13:26:00.163082876Z   File "/opt/conda/lib/python3.7/site-packages/numpy/lib/histograms.py", line 426, in _get_bin_edges
celeryworker_1  | 2021-06-16T13:26:00.163085715Z     first_edge, last_edge = _get_outer_edges(a, range)
celeryworker_1  | 2021-06-16T13:26:00.163088470Z   File "/opt/conda/lib/python3.7/site-packages/numpy/lib/histograms.py", line 316, in _get_outer_edges
celeryworker_1  | 2021-06-16T13:26:00.163091523Z     "supplied range of [{}, {}] is not finite".format(first_edge, last_edge))
celeryworker_1  | 2021-06-16T13:26:00.163094435Z ValueError: supplied range of [nan, nan] is not finite

Not sure whether these errors have been already there before the update, it happens roughly 60 times.
I've extracted the data from one case and loaded it separately:
In [1]: from SurfaceTopography.IO import open_topography

In [2]: r=open_topography("../data/issues/680/issue_680.OPDx")

In [3]: r.default_channel.physical_sizes
Out[3]:<PHONE_NUMBER>402419,<PHONE_NUMBER>776325)

In [4]: r.default_channel.height_scale_factor
Out[4]: 1

In [5]: t=r.topography()

In [6]: t.rms_curvature_from_area()
Out[6]: nan

So during the calculation nan is returned.

This topography has missing data points, related to #321


a little bit outdated?

Just read the GPT part and after this:
"GPT is a Family
GPT is not a single model, but rather a collection of models developed and trained by OpenAI. The latest model openly available is GPT-2, which has up to 1.5 billion parameters (there are several variations of the model, so you can select one for your tasks that is a good compromise between size/performance). Latest GPT-3 model has up to 175 billion parameters, and is available as a cognitive service from Microsoft Azure, and as OpenAI API."
I thought the course needs an update :).
Cheers, M.

you are right Sir.

Hi, thanks for this, currently working on it 😄, once updated I'll close the issue.

okay dear

The lessons are now up to date 😄


fetch in wrangler2 cannot take URL as a parameter

The following code works fine in Cloudflare Workers Playground
export default {
 async fetch(){
    const url=new URL('path','https://example.com')
    return fetch(url)
  }
}

Expected behavior
The same code, written in the project just initialized by the wrangler, will report the following error: Uncaught (in promise) TypeError: Invalid URL string.

Environment and versions
Fill out the following information about your environment.

operating system: windows 10
output of wrangler -V:2.0.25
output of node -v:v16.16.0
content of wrangler.toml:

name = "name"
main = "src/index.ts"
compatibility_date = "2022-12-08"

Same error  in wrangler 2.6.1


fix  sync

Among all backends, the memory order guarantee of WebGPU is the weakest
So Cubecl's memory order cannot be stronger than that of WebGPU,
Cuda
__syncthreads();

eq to
Wgsl
workgroupBarrier();
storageBarrier();

According to
https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#synchronization-functions
https://github.com/gpuweb/gpuweb/discussions/3935
https://github.com/gpuweb/gpuweb/discussions/4821
Unfortunately, there is no threadfence() function similar to Cuda  in Wgsl

@AntiAnimeGeneral Thanks for the fix. I think we should improve documentation before merging. We should describe what the synchronization does rather than comparing to other functions in other APIs. For sync_units and sync_storage we should tell that they operation only within a cube, and one synchronize in address space (local variables) and the other synchronize across global address space (global buffers). We could add in a details sections the links you provided for futher reference, but we will add more backend, so the documentation should be for the CubeCL API without having to go in details on all potential backends.


Automate the Docker Desktop extension update

The update of the Docker Desktop extension is a manual step, but it could be partially automated (updatecli?).
https://github.com/epinio/extension-docker-desktop

Looking at the last three version bumps I see that only three files require editing, in five places where the version number has to be bumped (always the dot form).

Looking at the updatecli we have (helm charts), and the docs a bit it seems that it should be possible (*) to use it to auto-create a PR for the repository, with updated version information.
I am unsure if such a PR could be (made to be) auto-merged, not to speak of if we want such an auto-merge.
(Ad *) It would need kind: file and the matchpattern, replacepattern spec fields, AFAICT.

I'm not a big fan of the automerge. A quick check and a manual merge is fine for me.


Follow global system-wide dark mode preference

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
misc
Description
Hello o/
Starting with https://github.com/echasnovski/mini.nvim/commit/d1d950c00eb247cdedf6e03f7c58e305b8fc7b72, mini.nvim now introduce synchronization between neovim background and the terminal. I propose that we follow through by introducing synchronization for system-wide dark mode preferences:
https://github.com/user-attachments/assets/5ea633be-e732-4a23-a323-12e6f9d15c4b

In general, each system offers a way to query its dark mode preference:
Linux:

Using org.freedesktop.appearance.color-scheme, which is managed by xdg-desktop-portal.

Windows:

Using reg.exe to query HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Themes\Personalize

MacOS:

Using defaults read -g AppleInterfaceStyle

Example:

[!IMPORTANT]
For the sake of this example, we are continuously polling org.freedesktop.appearance; implementations should consider using interrupts instead.

local timer = vim.fn.timer_start(
  2000,
  function()
    vim.fn.jobstart(
      table.concat(
        {
          "dbus-send --session --print-reply=literal --reply-timeout=1000",
          "--dest=org.freedesktop.portal.Desktop",
          "/org/freedesktop/portal/desktop",
          "org.freedesktop.portal.Settings.Read",
          "string:'org.freedesktop.appearance'",
          "string:'color-scheme'",
        },
        " "
      ),
      {
        stdout_buffered = true,
        on_stdout = function(_, res)
          local color_scheme = string.match(res[1], "uint32 1") ~= nil and "dark" or "light"
          if vim.o.background ~= color_scheme then
            vim.o.background = color_scheme
          end
        end,
      }
    )
  end,
  { ["repeat"] = -1 }
)

Thank to https://github.com/ormai/dotfiles/blob/0488ab3b4e0660ac7af3311852ccba01aa189302/.config/nvim/lua/auto_background.lua#L13
Bonus (randomhue)
https://github.com/user-attachments/assets/4c6b1627-d88e-4d83-8f89-355cfae8c25e

Thanks for the suggestion!
At the moment I don't really the idea for at least these reasons:

It depends on OS dependent tools, which 'mini.nvim' tries to avoid. Not only because "dependency is bad", but also due to implementation and maintenance complications.
Implementation indeed seems to be either constant rate polling or something more complex. Both options are not good.

I'll give it some thought, but at the moment it doesn't look like a good fit for 'mini.nvim'.

I am afraid I am more inclined to close this for the same reasons described in previous comment. Thanks for the suggestions, though!

I am afraid, this is not something that I think would justify all the code/doc/test/maintenance complexity.


Refactor cookie handling in coordinator.py

NOTE: For some reason, my UDM decided to stop sending cookies in its http responses. It's unknown if such behavior is expected, but this seemed like a good opportunity to update the cookie handing.
In UniFiOS 8.6.9 (possibly earlier 8.x.x releases), cookies are no longer explicitly returned as a response cookie. This means a cookie must be created using a 'Set-Cookie' token extracted from the response headers. Note: standalone network controller installations send two 'Set-Cookie' tokens in the response headers.
https://community.ui.com/questions/UDM-Pro-Unifi-API-Question/14e5fa72-4364-4958-b81f-fdded9e71a94
https://community.ui.com/questions/Unable-to-log-in-UDM-with-API/2dee8e20-28c1-49fc-9f4f-379b37e2af55
https://multidict.aio-libs.org/en/stable/multidict/#multidict.MultiDictProxy

https://developers.home-assistant.io/blog/2024/11/28/dt-util-utc-to-timestamp-deprecation/


[bindings] Fix Jcom + remove se3 namespace

I also fixed the bindings for exp3 because a unit test was failing on my Macbook (related to #597  and #598)


[fix]typo

Hi, I found some typo. Could you confirm this PR?
(sorry I forgot submitted an issue.)

Hi,
thanks this is already fixed in the development branch v3.1-working.


Cannot import SwAV

🐛 Bug
from pl_bolts.models.self_supervised import SwAV is not working for me.  BYOL and SimCLR all had no problem to import.
To Reproduce
Steps to reproduce the behavior:
I installed the package:
%pip install -q pytorch-lightning
%pip install -q pytorch-lightning-bolts
then import the package
import torch
import pytorch_lightning as pl
from pl_bolts.models.self_supervised import SwAV
then I got error:
ImportError: cannot import name 'SwAV'

Code sample

Expected behavior

Environment
Google Colab - free tier
AWS Sagemaker - kernel: pytorch-latest-p36 with 8 gpus..
Additional context

@userkkw Thank you for reporting the issue. Would you mind upgrading Bolts and retrying?
pip install git+https://github.com/PytorchLightning/pytorch-lightning-bolts.git@master --upgrade

@akihironitta it works now thanks :)


MixedModels Example in docs

Codecov Report

Merging #15 (c53f281) into main (5e27992) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   99.62%   99.62%
=======================================
  Files           4        4
  Lines         269      269
=======================================
  Hits          268      268
  Misses          1        1

Files Changed
Coverage Δ

src/BoxCox.jl
100.00% <ø> (ø)


Markdown renderer unescape is not totally fixed

Issue Type: Bug
I found this existing issue about Markdown renderer escapes, which was supposed to be fixed, but found an edge case that is still broken.
Load this repro in Code, then mouse over the "value" property name in data.jsonc.  You will see that the link ends with a superfluous literal backslash character, and clicking it opens a URL that ends with %5C.

VS Code version: Code 1.62.2 (3a6960b964327f0e3882ce18fcebd07ed191b316, 2021-11-11T20:56:38.428Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (2.87GB free)

Process Argv
--crash-reporter-id 104bab69-2434-4424-a670-b65cf70439b5

Screen Reader
no

VM
0%

Extensions (20)

Extension
Author (truncated)
Version

vscode-m3u
af4
1.0.0

ng-template
Ang
13.0.0

npm-intellisense
chr
1.4.0

vscode-svgviewer
css
2.0.0

vscode-markdownlint
Dav
0.45.0

githistory
don
0.6.19

xml
Dot
2.5.1

EditorConfig
Edi
0.16.4

vscode-npm-script
eg2
0.3.23

json-tools
eri
1.0.2

JasmineSnippets
jor
0.1.0

xml-format
mik
1.1.2

remote-ssh
ms-
0.66.1

remote-ssh-edit
ms-
0.66.1

powershell
ms-
2021.10.2

java
red
1.0.0

vscode-autohotkey
sle
0.2.2

vscode-hexdump
sle
1.8.1

vscodeintellicode
Vis
1.2.14

html-css-class-completion
Zig
1.20.0

I tried to trace the problem and it ended up being in the markedjs tokenizer.
The tokenizer captures the entire URL (i.e., https://example.com/page\.) but after entering the loop below (which applies _backpedal RexExp) the trailing period character is dropped.
marked.js#L1177:
do {
    prevCapZero = cap[0];
    cap[0] = this.rules.inline._backpedal.exec(cap[0])[0];
} while (prevCapZero !== cap[0]);

The latest version of the markedjs has the same behavior since the RegExp patterns are not different than our copy.
@mjbvz So, I'm not sure if we'd want to take this fix to the markedjs community. Maybe it's a by-design thing. What's your opinion?


Map Service fix, Geocoding Service fix, Minor Map Usecase Improvement

#122 Should fix some of the issues
The VVS stem from VVS a re-run of the tests should solve it. We might think about excluding actual remote calls from integration tests.

Sorry about that one: #124


Add UT Cases for Reclaim Action

What this PR does / why we need it:
Added UT for Reclaim Action

/ok-to-test

/lgtm
/approve
Thanks!


Additional labware sorting : custom definition

Overview
On the labware landing page, there should be an option to sort by custom definitions in the "sort by" drop down menu. This was discussed in the pm + support meeting with Mike C.
Design
The existing labware landing sorting designs live here: https://www.figma.com/file/bVtCogdwiXj3ndpk4AWXCx/[working]-Milestone-1%3A-Read-and-Execute?node-id=1297%3A89221
Acceptance criteria

[ ] From labware landing page, users can find the "custom definition" option in the "sort by" drop down
[ ] When "custom definition" is selected, only custom definitions show in the labware list with no Opentrons definitions showing

This feature is being added to the category drop down list by ticket: #10917


[CI] Use v4 of actions/checkout

Update actions/checkout, actions/upload-artifact, and cross-platform-actions/action to fix NodeJS 16 deprecation warnings:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Latest run with deprecation warnings: https://github.com/liquidaty/zsv/actions/runs/8260147411
Signed-off-by: Azeem Sajid<EMAIL_ADDRESS>

@liquidaty: All warnings have been fixed. Please review and merge. Thanks!
PR latest run summary: https://github.com/liquidaty/zsv/actions/runs/8291562679


Configure Stripe for SCA (by September 14)

On 14 September 2019, a new European regulatory requirement called  Strong Customer Authentication (SCA) [https://stripe.com/payments/strong-customer-authentication] will introduce two-factor authentication requirements for many online payments in Europe. Payments that aren’t authenticated will be declined by your customers’ banks.

We’ve released a new payments API and SCA-ready products to help you prepare for this change. To get ready for these new rules and avoid having many European payments declined, you’ll need to make changes to your payment flows and Stripe integration by 14 September 2019. Read our docs to learn more about SCA and the required changes.

Read the docs [https://stripe.com/docs/strong-customer-authentication]

Looking at the docs, as long as we're using the stripe widget, we'll only need to enable the 3D Secure 2 integration in the Stripe dashboard.
Resources:

Flows: https://stripe.com/guides/sca-payment-flows
Authentication: https://stripe.com/docs/strong-customer-authentication
Webinar: https://stripe.events/sca-webinar

API Changes:

Docs: https://stripe.com/docs/payments/payment-intents

Checkout Changes:

Docs: https://stripe.com/docs/payments/checkout
Flows: https://stripe.com/en-de/guides/sca-payment-flows#e-commerce

Since we're using Charges here https://github.com/EuroPython/epcon/blob/dev/ep2020/conference/payments.py#L22 we probably need to migrate it to payment intents https://stripe.com/docs/payments/payment-intents/migration

Were is charge_for_payment used?

@patrick91 https://github.com/EuroPython/epcon/blob/8d0e8d0f50cb326eb2a142c322c58c5f4c7490a4/conference/cart.py#L183


#153728018 Add blog functionality

What does this PR do?
Users should be able to write blog posts on the health checks site
Description of Task to be completed?
Users should be able to write blog posts on the health checks site
Users should be able to share blog posts publicly
How should this be manually tested?
GIVEN users want to contribute knowledge
WHEN they login to their account
THEN they should be able to create categories, write blog posts and share those posts publicly
What are the relevant pivotal tracker stories?
#153728018

Coverage increased (+0.5%) to 77.651% when pulling 7d32b52882099d37b1b9eadf5381f10f8536121e on ft-blogs-153728018 into ab50fb0b4255b7c2e948c93ee337b9aca3c8b32d on develop.

Looks good!!


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1752 ms

Resolved: Bofrost.at performance has improved in 3b311aa after 10 minutes.


Fix all warnings from the latest Clippy

The Clippy from the stable channel now produces new warnings, which this PR addresses. Specifically, those warnings are:

declare_interior_mutable_const: For efficient Block initialization, a constant Slot is used, but it has interior mutability, which Clippy warns about. I believe that using the inline-const expression in Block::new is ideal, but it is experimental in the current MSRV (1.61). Other solutions either have performance overheads (e.g., array::map, array::from_fn) or require nightly features (e.g., MaybeUninit::uninit_array).

doc_lazy_continuation: Some indentations are missing in the documentation.

zero_repeat_side_effects: When there are no explicit cases for the select! macro, it creates a zero-sized array with initialization that calls a function. Clippy is concerned if the function has side effects. In our case, it has no side effects and can be trivially resolved.

I would prefer ignoring this lint at workspace level like my other projects.

I agree with your suggestion. I will add another commit to ignore the declare_interior_mutable_const warning at the module level. I found that there is another line that ignores the same warning 🙃.

I feel it is a clippy bug that this lint warns of a code that has no side effects...

It also seems strange to me because crossbeam_channel::never clearly does not have any side effects, and even changing that function to const does not resolve the warning. It might be worth looking into this issue more deeply if I have time.


Add veterans promo to homepage

This is a placeholder image, we're waiting for the final one.

We're going ahead with this image, and will swap it later.


Adding  custom cursor to website

Adding Custom Cursor to project
fixes #206
In this pull request, I've added a custom cursor to the website to enhance the user experience. The new cursor design improves the overall aesthetic and provides a unique touch to our website.
Added a custom cursor design to the website
Implemented the custom cursor using  CSS, JavaScript, etc.
https://github.com/user-attachments/assets/6b6902ea-10a6-4e0e-b7c1-ccc9aafa3f08
Could you please review the updated changes and merge this pull request when you're satisfied?

Resolve conflicts

@aditya-bhaumik
okey i will resolve it but can you guide me how to do it i am just confuse about it.....

Ask in discord many people can help u

I already told in discord i will be busy today till 6 but there are other contributors who can help u

Mentor is also there

@aditya-bhaumik
I have resolve all conflicts please review it and merge.....


Validate vSphere provider fingerprint

With the current implementation, the vSphere provider is validated by connecting to it with the provided URL and credentials. However, according to pkg/controller/provider/container/vsphere/reconciler.go#L476, the connection is insecure, so it will work even if the certificate is invalid. It would be great to add a validation of the thumbprint, as it is passed to VMIO and if it is incorrect the migration fails.
Technically, the thumbprint is the SHA1 digest of the raw certificate. Here is an example of how to retrieve the certificate and generate the MD5 digest. So, the implementation could be similar, but generate the SHA1 digest, instead of the MD5 one.
The thumbprint validation should be done before the credentials validation, as an invalid thumbprint means that something is wrong in the trust chain, so sending credentials to a possibly rogue server is not a good idea.

The insecure connect() is a leftover from the initial PoC.  We can construct the vSphere client differently and pass it the thumbprint and insecure=false and get the validation for free.


Feat!: Sync Connection Catalog With Model Default Catalog

This PR makes sure that default catalog is synced with the connection catalog. If they say different things then an error is raised. Also if a user sets a default catalog on an engine that doesn't support catalogs then an error is raised.

Reworking this change in new PR


Script not running

After installing the requirements I have tried to run the script but it is throwing some exceptions.
Please update me on this.
Thank you.

You haven't installed ngrok library properly.
pip3 install pyngrok
Then run the script, it should work properly.

Okay thanks I'll give it a try

Ngrok have made compulsory to include auth-token, so wait until tomorrow. I will release one major update on zcam including that.

Okay thanks I'll give it a try

Use newer version.....


Adding some webp handling to work with frigate >=0.14

Not exactly sure you would want it handled like that : trial and fail method with webp fallback.
My understanding is that frigate would completely move to webp at some point.
I'm using compreface so work out of the bow with webp, not sure if this is the case with other backends : tested only with compreface.

Still relevant


Add Content Security Policy

search/main.js also needs fixing (after the inline data change), but since we don't really need it right now (and I don't feel like making a “custom” search plugin just to fix it), I'll just fix it when I send the patches upstream.

Upstreaming in https://github.com/mkdocs/mkdocs/pull/1907

How come style-src is pointing at a js file?

That URI (https://cdnjs.cloudflare.com/ajax/libs/highlight.js/) covers both Javascript and CSS files:

https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/highlight.min.js
https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/github.min.css

This will actually need updating, if we load more things from CDNJS.
I'll update in a moment and request a re-review  :3

@reuvenpo Could you re-review?  Here is what changed:

I redid the changes to use the TOML config syntax instead, so the CSP should be more readable.
Since we excised the binaries from the repo (and load them from CDNJS instead), I had to update the CSP to whitelist more libraries from CDNJS.


Feature/Token-refresh

:tada: This PR is included in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issue when selecting model

Describe the bug
idk here's the full error:
(VoxNovel) drew@drew-System-Product-Name:~$   npx gpt4all-cli@latest
ℹ Welcome to the GPT4all CLI!                                      3:39:48 PM
✔ Choose a model (default: gpt4all-lora-quantized):
gpt4all-lora-unfiltered-quantized
[3:39:50 PM] ◐ Initialize and download gpt4all-lora-unfiltered-quantized model .
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0% | ETA: 0s | 0/100
[3:39:50 PM]  ERROR  ENOENT: no such file or directory, open '/home/drew/.nomic'
████████████████████████████████████████ 100% | ETA: NULLs | NaN/100node:event6
throw er; // Unhandled 'error' event
^
HTTPError: Response code 404 (Not Found)
at Request._onResponseBase (file:///home/drew/.npm/_npx/27661af4ada6ed12/no)
at Request._onResponse (file:///home/drew/.npm/_npx/27661af4ada6ed12/node_m)
at ClientRequest. (file:///home/drew/.npm/_npx/27661af4ada6ed12/)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:530:35)
at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
at TLSSocket.socketOnData (node:_http_client:540:22)
at TLSSocket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:559:12)
Emitted 'error' event at:
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:{
input: undefined,
code: 'ERR_NON_2XX_3XX_RESPONSE',
timings: {
start:<PHONE_NUMBER>280,
socket:<PHONE_NUMBER>281,
lookup:<PHONE_NUMBER>284,
connect:<PHONE_NUMBER>301,
secureConnect:<PHONE_NUMBER>322,
upload:<PHONE_NUMBER>323,
response:<PHONE_NUMBER>509,
end:<PHONE_NUMBER>538,
error: undefined,
abort: undefined,
phases: {
wait: 1,
dns: 3,
tcp: 17,
tls: 21,
request: 1,
firstByte: 186,
download: 29,
total: 258
}
},
options: Options {
_unixOptions: undefined,
_internals: {
request: undefined,
agent: { http: undefined, https: undefined, http2: undefined },
h2session: undefined,
decompress: true,
timeout: {
connect: undefined,
lookup: undefined,
read: undefined,
request: undefined,
response: undefined,
secureConnect: undefined,
send: undefined,
socket: undefined
},
prefixUrl: '',
body: undefined,
form: undefined,
json: undefined,
cookieJar: undefined,
ignoreInvalidCookies: false,
searchParams: undefined,
dnsLookup: undefined,
dnsCache: undefined,
context: {},
hooks: {
init: [],
beforeRequest: [],
beforeError: [],
beforeRedirect: [],
beforeRetry: [],
afterResponse: []
},
followRedirect: true,
maxRedirects: 10,
cache: undefined,
throwHttpErrors: true,
username: '',
password: '',
http2: false,
allowGetBody: false,
headers: {
'user-agent': 'got (https://github.com/sindresorhus/got)',
'accept-encoding': 'gzip, deflate, br'
},
methodRewriting: false,
dnsLookupIpVersion: undefined,
parseJson: [Function: parse],
stringifyJson: [Function: stringify],
retry: {
limit: 2,
methods: [ 'GET', 'PUT', 'HEAD', 'DELETE', 'OPTIONS', 'TRACE' ],
statusCodes: [
408, 413, 429, 500,
502, 503, 504, 521,
522, 524
],
errorCodes: [
'ETIMEDOUT',
'ECONNRESET',
'EADDRINUSE',
'ECONNREFUSED',
'EPIPE',
'ENOTFOUND',
'ENETUNREACH',
'EAI_AGAIN'
],
maxRetryAfter: undefined,
calculateDelay: [Function: calculateDelay],
backoffLimit: Infinity,
noise: 100
},
localAddress: undefined,
method: 'GET',
createConnection: undefined,
cacheOptions: {
shared: undefined,
cacheHeuristic: undefined,
immutableMinTimeToLive: undefined,
ignoreCargoCult: undefined
},
https: {
alpnProtocols: undefined,
rejectUnauthorized: undefined,
checkServerIdentity: undefined,
certificateAuthority: undefined,
key: undefined,
certificate: undefined,
passphrase: undefined,
pfx: undefined,
ciphers: undefined,
honorCipherOrder: undefined,
minVersion: undefined,
maxVersion: undefined,
signatureAlgorithms: undefined,
tlsSessionLifetime: undefined,
dhparam: undefined,
ecdhCurve: undefined,
certificateRevocationLists: undefined
},
encoding: undefined,
resolveBodyOnly: false,
isStream: true,
responseType: 'text',
url: URL {},
pagination: {
transform: [Function: transform],
paginate: [Function: paginate],
filter: [Function: filter],
shouldContinue: [Function: shouldContinue],
countLimit: Infinity,
backoff: 0,
requestLimit: 10000,
stackAllItems: false
},
setHost: true,
maxHeaderSize: undefined,
signal: undefined,
enableUnixSockets: false
},
_merging: false,
_init: [ { isStream: true } ]
}
}
Node.js v20.12.1
(VoxNovel) drew@drew-System-Product-Name:~$
Reproduction
idk just installed gpt4all and then ran your "npx gpt4all-cli@latest" command
System Info
(VoxNovel) drew@drew-System-Product-Name:~$ npx envinfo --system --binaries --bs
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

  System:
    OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (12) x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
    Memory: 27.73 GB / 31.26 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.12.1 - /usr/bin/node
    npm: 10.5.0 - /usr/bin/npm
  Browsers:
    Chrome: 122.0.6261.128
    Chromium: 123.0.6312.86

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Thanks. I will take a look sometime this week.


ScrollView contentContainerStyle flex doesn't adjust for contentInsetAdjustmentBehavior

React Native version: 0.59.9

Steps To Reproduce

Create a ScrollView with automaticallyAdjustContentInsets={true} contentInsetAdjustmentBehavior={'always'} contentContainerStyle={{flexGrow: 1}}
Add a child with flex: 1

Describe what you expected to happen:
Child component height should be equal to the scrollview height - content insets. Instead, it's equal to the scrollview height
Snack, code example, or link to a repository:
https://snack.expo.io/@louay/scrollview-layout-contentinset-issue

      <ScrollView
        style={{
          flex: 1,
          backgroundColor: '#efefef',
        }}
        automaticallyAdjustContentInsets={true}
        contentInsetAdjustmentBehavior={'always'}
        contentContainerStyle={{flexGrow: 1}}
      >
        <Text style={{backgroundColor: 'blue', padding: 16, color: 'white'}}>Test header</Text>
        <View style={{flexGrow: 1}} />
        <Text style={{backgroundColor: 'green', padding: 16, color: 'white'}}>Test footer</Text>
      </ScrollView>

I think this is similar to #19984
Moreover looking at ScrollView/RCTScrollView.m I can see that it's not using adjustedContentInset nor handling adjustedContentInsetDidChange(), which sounds like what the problem is

Happy to try to fix it if I can get a little bit of guidance on how to make RN layout use adjustedContentInset instead of contentInset


"Restore" button disappeared

Azure Data Studio Version:

Steps to Reproduce:
No " Restore" button at my function area
Anyone can give me a favor?
Thanks

The screenshot above is at the "instance" level for Azure SQL DB, restore is not supported for Azure SQL DB.
To export or import a database for Azure SQL DB, install the "SQL Server dacpac" extension and use the data tier application wizard.
Azure SQL DB, no restore button:

full SQL instance:

Thanks a lot

@Hang1314 do you have "Preview Features" setting enabled in the User Settings? Restore is currently considered a preview feature.

oh, it still doesn't work for me

this is by design. as @dzsquared mentioned above, you cannot restore the master database of SQL Azure server.
https://github.com/microsoft/azuredatastudio/blob/main/src/sql/workbench/contrib/dashboard/browser/pages/serverDashboardPage.contribution.ts#L83


Fix deprecation warning

In<EMAIL_ADDRESS>all rules which end with *-blacklist have been renamed to *-dissallow-list.
So, now this config causes deprecation warning:
Deprecation Warning: 'function-blacklist' has been deprecated. Instead use 'function-disallowed-list'. See: https://github.com/stylelint/stylelint/blob/13.7.0/lib/rules/function-blacklist/README.md

In this pull request I've fixed that.

@dissimulazione, would you mind to approve?

Published<EMAIL_ADDRESS>🚀


Strange 'sawtooth' pattern ICMP latency measurements

Disclaimer: I'm new to embedded
I'm running the WiFi example with my esp32c6 with a few changes (like mem::forget the wifi type to keep it running beyond main), and I pinged it from my laptop for a couple hours. I've tested and seen the same behavior on an XIAO ESP32-C6 and a ESP32-C6 WROOM I saw this 'sawtooth' pattern consistently basically the entire time.
What's interesting is that I'm seeing latency as short as 2ms but it's consistently very short and very long in a saw pattern (my laptop, the esp32c6 and the wifi AP are all within 2ft of each other). Is there an explanation for this behavior?
10641 packets transmitted, 10639 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.784/179.418/885.236/100.006 ms

The following image illustrates the saw pattern even more by plotting the latency (X) against the previous ICMP request's latency (Y).

As a point of reference, same laptop, same network, different target devices (instead of the ESP). None of these have the same reproducible pattern that the ESP has. Curious if that has anything to do with the networking implementation here.
A printer

Cell phone

Hardwired desktop

No idea, but to remove the Rust ESP IDF wrappers out of the equation, can you try with some of the C wifi examples and see if you still get this behavior? If so, I guess you need to re-open the same issue in the ESP IDF repo...

Try calling this function somewhere early in your Wi-Fi init:
pub fn wifi_disable_powersave() -> Result<(), EspError> {
    esp!(unsafe { sys::esp_wifi_set_ps(sys::wifi_ps_type_t_WIFI_PS_NONE) })
}

It should make a big difference, especially if you have a high DTIM on your network.


x/net/http2:

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.7.3 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build560134607=/tmp/go-build"
CXX="g++"
CGO_ENABLED="1"
What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
http2 server  getRequestBodyBuf() creates lots garbage and memory usage is high
What did you expect to see?
What did you see instead?
Most requests don't have body, but all allocates a 64K buffer, no request body read is called , therefore, putRequestBodyBuf() won't be called to recycle the buffer.
Is it possible to allocate 64k buffer only if there is a request body?

Fixed by https://github.com/golang/net/commit/3bafa3320efdf0c95d056586aa9abdd05ad72ee1

with golang/net@3bafa33 it still creates lots of garbage, the reason is for requests with no body, putRequestBodyBuf() is never called. Calling it in handlerDone() helps, but it still wastes lots of 64k buffer for requests without body (which is majority). I use this workaround, it saves lots of memory with busy servers:
--- a/http2/server.go
+++ b/http2/server.go
@@ -1418,13 +1418,12 @@ func (sc *serverConn) processData(f *DataFrame) error {
            return streamError(id, ErrCodeStreamClosed)
    }

  if st.body == nil {

          panic("internal error: should have a body in this state")

  }

  // Sender sending more than they'd declared?
  if st.declBodyBytes != -1 && st.bodyBytes+int64(len(data)) > st.declBodyBytes {

          st.body.CloseWithError(fmt.Errorf("sender tried to send more than declared Content-Length of %d bytes", st.declBody

          if st.body != nil {

                  st.body.CloseWithError(fmt.Errorf("sender tried to send more than declared Content-Length of %d bytes", st.

          }
          return streamError(id, ErrCodeStreamClosed)
  }
  if f.Length > 0 {

@@ -1435,6 +1434,16 @@ func (sc *serverConn) processData(f *DataFrame) error {
st.inflow.take(int32(f.Length))
            if len(data) > 0 {

                  reqbodyMu.Lock()

                  if st.body == nil {

                          //fmt.Println("getBuf in processData")

                          st.reqBuf = getRequestBodyBuf()

                          st.body = &pipe{

                                  b: &fixedBuffer{buf: st.reqBuf},

                          }

                          //panic("internal error: should have a body in this state")

                  }

                  reqbodyMu.Unlock()
                  wrote, err := st.body.Write(data)
                  if err != nil {
                          return streamError(id, ErrCodeStreamClosed)

@@ -1483,12 +1492,14 @@ func (st *stream) endStream() {
sc := st.sc
sc.serveG.check()

  if st.declBodyBytes != -1 && st.declBodyBytes != st.bodyBytes {

          st.body.CloseWithError(fmt.Errorf("request declared a Content-Length of %d but only wrote %d bytes",

                  st.declBodyBytes, st.bodyBytes))

  } else {

          st.body.closeWithErrorAndCode(io.EOF, st.copyTrailersToHandlerRequest)

          st.body.CloseWithError(io.EOF)

  if st.body != nil {

          if st.declBodyBytes != -1 && st.declBodyBytes != st.bodyBytes {

                  st.body.CloseWithError(fmt.Errorf("request declared a Content-Length of %d but only wrote %d bytes",

                          st.declBodyBytes, st.bodyBytes))

          } else {

                  st.body.closeWithErrorAndCode(io.EOF, st.copyTrailersToHandlerRequest)

                  st.body.CloseWithError(io.EOF)

          }
  }
  st.state = stateHalfClosedRemote

}
@@ -1741,11 +1752,6 @@ func (sc *serverConn) newWriterAndRequest(st *stream, f *MetaHeadersFrame) (*res
return nil, nil, err
}
if bodyOpen {

          st.reqBuf = getRequestBodyBuf()

          req.Body.(*requestBody).pipe = &pipe{

                  b: &fixedBuffer{buf: st.reqBuf},

          }

          if vv, ok := rp.header["Content-Length"]; ok {

To send changes, see https://golang.org/doc/contribute.html
We can't accept diffs over email or github.


Dark Theme Toggle

It would be nice to have a toggle to enable/disable the true dark theme from the unc0ver dark settings. Sometimes I just want to change up the look of my device and it would be really convenient to have both options available.

Finished ;) Sorry it took so long


Subscribe to window resize event?

As I understand it, subscription to the window resize event should happen within the initializer of a lifecycle component, since the render function only has access to the body element of a page, and not the window itself.
I'm having trouble navigating the types around eventSource though, and have come as far as the following (analogous to this example):
H.subscribe $ ES.eventSource' (?) (Just <<< H.request <<< WindowResizeQuery)

What should replace the ? above?  Or is this approach flawed?

something like this should work (haven't compiled tho).
import DOM.HTML.Window (document)
import DOM.HTML (window)
import DOM.Event.EventTarget as (addEventListener, removeEventListener, eventListener)
import DOM.HTML.Types (windowToEventTarget )
import DOM.HTML.Event.EventTypes as (resize)
import Halogen as H
import Halogen.Query.EventSource as ES

do
  win ← H.liftEff $ window <#> windowToEventTarget
  H.subscribe $
    H.eventSource'
      (\f -> do
        let listener = eventListener f
        addEventListener resize listener false win
        pure $ removeEventListener resize listener false win
        )
      (\e -> pure $ WindowResized ES.Listening)

you can also do:

Thank you - it works!  Just had to add avar :: AVAR to non-component-state effects of component.

Great, you are welcome!


Combining entity wise results into data set wise results

Dear authors,
in your paper you report results for SMAP, MSL and SMD however the anomaly detection is done at the entity level. Could you explain how you obtained precision, recall and f1 score for the whole data sets from the anomaly predictions you had for each of the entities that composed the data sets?
Best

Dear authors, is there any update for this? I would also like to know, especially for the SMD dataset, how the f1 score is combined from each machine-i-j into a single score? Is the simple average of f1 taken over all the datasets? Or do you use the total TP/TN/FP/FN to calculate?

did you figure this out?

did you figure this out?

total TP/TN/FP/FN to calculate

We use the total TP/TN/FP/FN to calculate the overall results for data sets

Dear authors,
in your paper you report results for SMAP, MSL and SMD however the anomaly detection is done at the entity level. Could you explain how you obtained precision, recall and f1 score for the whole data sets from the anomaly predictions you had for each of the entities that composed the data sets?
Best

We use the total TP/TN/FP/FN to calculate the overall results for data sets


feat: added a test to verify that WebSocket connections can be proxied.

@abstractj
Is proxying WS connections not a desired use case?

@abstractj
Is proxying WS connections not a desired use case?

Why not?

@abstractj
Is proxying WS connections not a desired use case?

Why not?

Yay.. was worried this test case was not of interest to you guys...


Remove IP address overwrite

Why

Listen on hostname of container instead of the up as this will remain fixed.
How

Remove IP address overwrite
References

Relates-to: #11
https://github.com/helium/gateway-rs/issues/82

Need to test on the hardware before removing draft status


[#1645] Prevent notifications produced on MODERATOR_ADD and REMOVE

Fixes #1645

Coverage remained the same at 35.547% when pulling 5d23c06ea961f96d176620b3df3edbc1e7585de8 on 1645-squelch-mod-notification into a68e0e617eaa1a3ffa134bc08250b27341e847b4 on v0.13.4-rc.

Quick testing suggests the missing moderator notifications don't hurt the client experience. Would need to produce a bunch of notifications to see what volume notifications might do when mod requests are being omitted...


Figure out why PowerIso is not at the latest version

Will have to fix up the ketarin query, as the layout of the page must have changed.

Done.
The download URL was not correct in the ketarin configuration.  So although it was detecting the latest version, it wasn't downloading anything, which meant the package was never getting created.


Add functionality for background-images on chart-segments

I think it has been requested before, but it was a long time ago and nothing happened.
This feature is really crucial for some projects I am working on.
Other than that: Oh my chart.js is so awesome! :)

:+1:

:+1:

I think this is asking for adding images as the fill of things like bars, arcs, etc.
You should be able to set the fillColor to a canvas pattern object since the fillColor is directly mapped to the canvas fillStyle property


Add SQL(DB), Node (Server), Induction and Launch to PD Milestone test

Background
We have created a Test Coursework to be able to do the PD Milestone test.
I have yet to import some modules, so I need to do that to have a complete overview.
Acceptance criteria

Import following coursework
- SQL DB
- Induction
- Node / Server
- Launch

Owner
@kfklein15
Stakeholder
@LaraHuzjan
Approver
@kfklein15

All copied.


New Sites

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[x] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[x] I'm requesting a feature unrelated to a specific site
[x] I've looked through the README
[ ] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[ ] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[x] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
add new sites, MediaDownloader supports many more sites
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

MediaDownlaoder uses yt-dlp (among optionally others) as their backend. If you have a request for a specific site, you can open it. Blanket statements like "support more sites" are not helpful.

ok


Fix GUI cursor problem

When sending hide-cursor sequence (e.g. echo -e "\e[?25l") to terminal-window on gvim,
it causes the delaying of moving cursor.
Repro steps:

I confirmed Vim 8.0.0802 (with gtk2) on Ubuntu 16.04

SHELL=/bin/bash gvim --clean +terminal
and execute the following on terminal-window
echo -e "\e[?25l"
then, putting <CR> key, cursor-move to the next line is delayed.
Solution:
Increase the frequency of calling gui_update_cursor() in update_cursor() while preventing cursor flicker:

calling always: when called from write_to_term()
calling when tl_cursor_visible is true: other callers (e.g. handle_movecursor())

Ozaki Kiichi

Codecov Report

Merging #1893 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1893      +/-   ##
==========================================
+ Coverage    75.1%    75.1%   +<.01%
==========================================
  Files          76       76
  Lines      125263   125264       +1
==========================================
+ Hits        94077    94085       +8
+ Misses      31186    31179       -7

Impacted Files
Coverage Δ

src/window.c
81.42% <0%> (-0.07%)
:arrow_down:

src/if_xcmdsrv.c
85.37% <0%> (ø)
:arrow_up:

src/channel.c
83.78% <0%> (+0.04%)
:arrow_up:

src/gui_gtk_x11.c
47.65% <0%> (+0.05%)
:arrow_up:

src/if_py_both.h
75.56% <0%> (+0.24%)
: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 70229f9...131ad55. Read the comment docs.


update deps, bump version

There's a dependency on<EMAIL_ADDRESS>- latest version is 0.4.0. Seems to be causing 'mismatched template version' errors.
Cheers!

Seems to be failing to load rcu/rcu.node... I'll see what I can find out.

Ah, yep - there's just the one dist file now, it's UMD. The older version had a bunch of different ones because that was the only way I could get certain dependants to build. That's no longer a problem, so it should just be require('rcu'). Have updated the branch.
The tests don't pass, because the template format has a few small difference. One less small difference is that line positions are now included - I can't recall exactly why that changed in rcu. Let me know if you think that needs to be changed at the rcu level

Alright, I've got everything working again (updated tests and all dependencies), once Travis-CI passes on master I'll publish the new version.
Thanks for the input and PR even though I'm not using it directly. :-)

Ok the tests pass but for some reason I can't npm publish:
$ npm publish
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm ERR! Darwin 14.1.0
npm ERR! argv "/Users/marcello/.nvm/versions/io.js/v1.5.1/bin/iojs" "/Users/marcello/.nvm/versions/io.js/v1.5.1/bin/npm" "publish"
npm ERR! node v1.5.1
npm ERR! npm  v2.7.0

npm ERR! Invalid Version: 0.6.0
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/marcello/Development/github/node-ractify/npm-debug.log```

In the package.json version is an array... is that the cause of the problem?

Yea, that was the problem. :D Bug in the changelog module


Influxdb support

I could use support for influx databases. Maybe consider adding it to your superset Docker file?
If I want to add influxdb support myself, how would I go about it?
Just add another line underneath pip3 install with influxalchemy in the Docker file?

Does InfluxDB have a SQLAlchemy driver? I wrote a workaround a while back, but it will need a actual driver in order to work with Superset.
In other words, Superset needs a url to hand off to SQLAlchemy that can be turned into an engine/session that conforms to SQLAlchemy's API. Something like:
influxdb://user:pass@host:port/db


[gpu] Driver installation breaking in Dataproc 2.1 image during initialization

Hi Team,
I was able to attach GPUs to Dataproc 2.1 cluster and it was working fine after disabling the secure boot. I am using the latest install_gpu_driver.sh from this repository. But I am getting the following error during cluster initialization now:-
++ lsb_release -is
++ tr '[:upper:]' '[:lower:]'

OS_NAME=debian
++ . /etc/os-release
+++ PRETTY_NAME='Debian GNU/Linux 11 (bullseye)'
+++ NAME='Debian GNU/Linux'
+++ VERSION_ID=11
+++ VERSION='11 (bullseye)'
+++ VERSION_CODENAME=bullseye
+++ ID=debian
+++ HOME_URL=https://www.debian.org/
+++ SUPPORT_URL=https://www.debian.org/support
+++ BUG_REPORT_URL=https://bugs.debian.org/
++ echo debian11
distribution=debian11
readonly OS_NAME
++ /usr/share/google/get_metadata_value attributes/dataproc-role
ROLE=Worker
readonly ROLE
DRIVER_FOR_CUDA=(['10.1']='418.88' ['10.2']='440.64.00' ['11.0']='450.51.06' ['11.1']='455.45.01' ['11.2']='460.73.01' ['11.5']='495.29.05' ['11.6']='510.47.03' ['11.7']='515.65.01' ['11.8']='520.56.06')
readonly -A DRIVER_FOR_CUDA
CUDNN_FOR_CUDA=(['10.1']='<IP_ADDRESS>' ['10.2']='<IP_ADDRESS>' ['11.0']='<IP_ADDRESS>' ['11.1']='<IP_ADDRESS>' ['11.2']='<IP_ADDRESS>' ['11.5']='<IP_ADDRESS>' ['11.6']='<IP_ADDRESS>' ['11.7']='<IP_ADDRESS>' ['11.8']='<IP_ADDRESS>')
readonly -A CUDNN_FOR_CUDA
NCCL_FOR_CUDA=(['10.1']='2.4.8' ['10.2']='2.5.6' ['11.0']='2.7.8' ['11.1']='2.8.3' ['11.2']='2.8.3' ['11.5']='2.11.4' ['11.6']='2.11.4' ['11.7']='2.12.12' ['11.8']='2.15.5')
readonly -A NCCL_FOR_CUDA
CUDA_SUBVER=(['10.1']='10.1.243' ['10.2']='10.2.89' ['11.0']='11.0.3' ['11.1']='11.1.0' ['11.2']='11.2.2' ['11.5']='11.5.2' ['11.6']='11.6.2' ['11.7']='11.7.1' ['11.8']='11.8.0')
readonly -A CUDA_SUBVER
++ get_metadata_attribute rapids-runtime SPARK
++ local -r attribute_name=rapids-runtime
++ local -r default_value=SPARK
++ /usr/share/google/get_metadata_value attributes/rapids-runtime
++ echo -n SPARK
RUNTIME=SPARK
DEFAULT_CUDA_VERSION=11.2
[[ 2.1 == 2.*
Building dependency tree...
Reading state information...
pciutils is already the newest version (1:3.7.0-5).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
return 0
configure_yarn
[[ ! -f /etc/hadoop/conf/resource-types.xml ]]
printf '\n'
set_hadoop_property resource-types.xml yarn.resource-types yarn.io/gpu
local -r config_file=resource-types.xml
local -r property=yarn.resource-types
local -r value=yarn.io/gpu
bdconfig set_property --configuration_file /etc/hadoop/conf/resource-types.xml --name yarn.resource-types --value yarn.io/gpu --clobber
set_hadoop_property capacity-scheduler.xml yarn.scheduler.capacity.resource-calculator org.apache.hadoop.yarn.util.resource.DominantResourceCalculator
local -r config_file=capacity-scheduler.xml
local -r property=yarn.scheduler.capacity.resource-calculator
local -r value=org.apache.hadoop.yarn.util.resource.DominantResourceCalculator
bdconfig set_property --configuration_file /etc/hadoop/conf/capacity-scheduler.xml --name yarn.scheduler.capacity.resource-calculator --value org.apache.hadoop.yarn.util.resource.DominantResourceCalculator --clobber
set_hadoop_property yarn-site.xml yarn.resource-types yarn.io/gpu
local -r config_file=yarn-site.xml
local -r property=yarn.resource-types
local -r value=yarn.io/gpu
bdconfig set_property --configuration_file /etc/hadoop/conf/yarn-site.xml --name yarn.resource-types --value yarn.io/gpu --clobber
lspci
grep -q NVIDIA
/usr/bin/nvidia-smi --query-gpu=mig.mode.current --format=csv,noheader
uniq
/etc/google-dataproc/startup-scripts/dataproc-initialization-script-0: line 533: /usr/bin/nvidia-smi: No such file or directory
wc -l
0
[[ debian == debian ]]
++ uname -r
execute_with_retries 'apt-get install -y -q '''linux-headers-5.10.0-30-cloud-amd64''''
local -r 'cmd=apt-get install -y -q '''linux-headers-5.10.0-30-cloud-amd64''''
(( i = 0 ))
(( i < 10 ))
eval 'apt-get install -y -q '''linux-headers-5.10.0-30-cloud-amd64''''
++ apt-get install -y -q linux-headers-5.10.0-30-cloud-amd64
Reading package lists...
Building dependency tree...
Reading state information...
linux-headers-5.10.0-30-cloud-amd64 is already the newest version (5.10.218-1).
linux-headers-5.10.0-30-cloud-amd64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
return 0
[[ 0 -eq 0 ]]
install_nvidia_gpu_driver
[[ debian == debian ]]
curl -fsSL --retry-connrefused --retry 10 --retry-max-time 30 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/cuda-keyring_1.0-1_all.deb -o /tmp/cuda-keyring.deb
dpkg -i /tmp/cuda-keyring.deb
Selecting previously unselected package cuda-keyring.
(Reading database ... 168905 files and directories currently installed.)
Preparing to unpack /tmp/cuda-keyring.deb ...
Unpacking cuda-keyring (1.0-1) ...
Setting up cuda-keyring (1.0-1) ...
curl -fsSL --retry-connrefused --retry 10 --retry-max-time 30 https://download.nvidia.com/XFree86/Linux-x86_64/495.29.05/NVIDIA-Linux-x86_64-495.29.05.run -o driver.run
bash ./driver.run --silent --install-libglvnd
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86_64 495.29.05.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

ERROR: An error occurred while performing the step: "Building kernel modules". See /var/log/nvidia-installer.log for details.
ERROR: An error occurred while performing the step: "Checking to see whether the nvidia kernel module was successfully built". See /var/log/nvidia-installer.log for details.
ERROR: The nvidia kernel module was not created.
ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
I can also see the following error in  the file /var/log/nvidia-installer.log in one of the cluster machine.
ld -r -o /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/nvidia-modeset/nv-modeset-interface.o /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/nvidia-modeset/nvidia-modeset-linux.o /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/nvidia-modeset/nv-kthread-q.o
LD [M]  /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/nvidia-modeset.o
LD [M]  /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/nvidia-peermem.o
MODPOST /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/Module.symvers
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
make[3]: *** [/usr/src/linux-headers-5.10.0-30-common/scripts/Makefile.modpost:123: /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/Module.symvers] Error 1
make[3]: Target '__modpost' not remade because of errors.
make[2]: *** [/usr/src/linux-headers-5.10.0-30-common/Makefile:1783: modules] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-5.10.0-30-cloud-amd64'
make[1]: *** [Makefile:192: __sub-make] Error 2
make[1]: Target 'modules' not remade because of errors.
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-30-common'
make: *** [Makefile:80: modules] Error 2
-> Checking to see whether the nvidia kernel module was successfully built
executing: 'cd ./kernel; /opt/conda/default/bin/make -k -j8 NV_KERNEL_MODULES="nvidia" NV_EXCLUDE_KERNEL_MODULES="" SYSSRC="/lib/modules/5.10.0-30-cloud-amd64/source" SYSOUT="/lib/modules/5.10.0-30-cloud-amd64/build"'...
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-30-common'
make[2]: Entering directory '/usr/src/linux-headers-5.10.0-30-cloud-amd64'
scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
MODPOST /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/Module.symvers
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
make[3]: *** [/usr/src/linux-headers-5.10.0-30-common/scripts/Makefile.modpost:123: /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/Module.symvers] Error 1
make[3]: Target '__modpost' not remade because of errors.
make[2]: *** [/usr/src/linux-headers-5.10.0-30-common/Makefile:1783: modules] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-5.10.0-30-cloud-amd64'
make[1]: *** [Makefile:192: __sub-make] Error 2
make[1]: Target 'modules' not remade because of errors.
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-30-common'
make: *** [Makefile:80: modules] Error 2
-> Error.
ERROR: An error occurred while performing the step: "Checking to see whether the nvidia kernel module was successfully built". See /var/log/nvidia-installer.log for details.
-> The command cd ./kernel; /opt/conda/default/bin/make -k -j8 NV_KERNEL_MODULES="nvidia" NV_EXCLUDE_KERNEL_MODULES="" SYSSRC="/lib/modules/5.10.0-30-cloud-amd64/source" SYSOUT="/lib/modules/5.10.0-30-cloud-amd64/build" failed with the following output:
make[1]: Entering directory '/usr/src/linux-headers-5.10.0-30-common'
make[2]: Entering directory '/usr/src/linux-headers-5.10.0-30-cloud-amd64'
scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
MODPOST /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/Module.symvers
FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'rcu_read_unlock_strict'
make[3]: *** [/usr/src/linux-headers-5.10.0-30-common/scripts/Makefile.modpost:123: /tmp/selfgz13916/NVIDIA-Linux-x86_64-495.29.05/kernel/Module.symvers] Error 1
make[3]: Target '__modpost' not remade because of errors.
make[2]: *** [/usr/src/linux-headers-5.10.0-30-common/Makefile:1783: modules] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-5.10.0-30-cloud-amd64'
make[1]: *** [Makefile:192: __sub-make] Error 2
make[1]: Target 'modules' not remade because of errors.
make[1]: Leaving directory '/usr/src/linux-headers-5.10.0-30-common'
make: *** [Makefile:80: modules] Error 2
ERROR: The nvidia kernel module was not created.
ERROR: Installation has failed.  Please see the file '/var/log/nvidia-installer.log' for details.  You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.
Is anyone facing similar issue with driver installation in Dataproc 2.1/2.2 clusters?

I could change the default driver and cuda versions on 2.1 images to be more current.

Thank you! Is there a specific CUDA and driver version to try as a workaround to get past this error in 2.1 images now?

I don't think I've tested the current code with cuda 12, but I think that's
what we should be targeting with a recent 5xx series driver.
I recently reimagined the installer to use , on bookworm and later, the
stock dkms from non-,free packages and sign drivers using the MOK.  That
requires that the MOK x509 cert be inserted into the efi header of the
block device.  I'll be writing it up with some example code shortly.
I will try to set it up to do cuda 12 on a 5xx series kernel module, but I
haven't tested it yet.  In 2.2 we should be able to use the one from Debian
stable non-free with dkms to install the current open module.
On Wed, Jun 12, 2024, 12:25 santhoshvly @.***> wrote:

@cjac https://github.com/cjac Thank you! Is there a specific CUDA and
driver version to try as a workaround to get past this error in 2.1 images
now?
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudDataproc/initialization-actions/issues/1189#issuecomment-2163747827,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAM6USGZGNQTQ3ZR6XCEE3ZHCOA3AVCNFSM6AAAAABJG5NGYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTG42DOOBSG4
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

@cjac Okay, Thank you!. I tried with latest CUDA version 12.0 and corresponding driver version using the latest install_gpu_driver.sh script from this repo, but got the same error. So, it looks like we can't really attach any GPUs to Dataproc 2.1/2.2  until we fix it. Please let me know if there are any other workarounds

I'm seeing a gcc error when trying to link gpl-incompatible code into
kernel modules for all variants available on Debian 11 ; Debian 12 offers
open driver support so I will start there tomorrow.
On Thu, Jun 13, 2024, 06:49 santhoshvly @.***> wrote:

@cjac https://github.com/cjac Okay, Thank you!. I tried with latest
CUDA version 12.0 and corresponding driver version using the latest
install_gpu_driver.sh script from this repo, but got the same error. So, it
looks like we can't really attach any GPUs to Dataproc 2.1/2.2 until we fix
it. Please let me know if there are any other workarounds
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudDataproc/initialization-actions/issues/1189#issuecomment-2165732651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAM6UUNC5SUOIVPDJUSYMLZHGPNVAVCNFSM6AAAAABJG5NGYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVG4ZTENRVGE
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

The latest Dataproc image that works with the .run file is 2.1.46-debian11
I am pushing a new change to the installer script.  Please see #1190 for something that has been tested to work with images prior to and including 2.1.46-debian11
I am also working on bookworm (2.2-debian12) support for installation using apt-get.

I'm also work on something in the custom-images repo.  I've got an in-progress PR open over there:
https://github.com/GoogleCloudDataproc/custom-images/pull/83

@cjac Okay, Thank you for the update.  We are unable to use GPU with latest 2.1/2.2 images until we get the fixed install_gpu_driver.sh. We always use the latest 2.1 image to launch the Dataproc cluster. Will this script change help attach the GPU to the latest 2.1 Debian 11 image (currently 2.1.53-debian11), or can we only use versions prior to and including 2.1.46-debian11?

We have been running data pipelines using the latest Dataproc 2.1 images with GPU attached, and they have been breaking for some time. However, the documentation does not mention this issue: https://cloud.google.com/dataproc/docs/concepts/compute/gpus. This makes Dataproc GPU clusters seem very unreliable if they can break at any time.

Yes, I agree.  I'm doing some work internally to build and distribute the kernel drivers with the stock image.  I hope to have the change reviewed and published this quarter.
You are correct that the initialization-actions script will presently only work with those versions mentioned.  I will do some work today to see if I can build drivers from bullseye-backports.

I've had some luck building from the open source github repo on the latest 2.1 images ; I'm integrating these changes into the open PR now.

The update is working on the latest 2.1 image.
Thu Jun 20 18:47:35 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.54.14              Driver Version: 550.54.14      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA L4                      Off |   00000000:00:03.0 Off |                    0 |
| N/A   76C    P0             37W /   72W |       0MiB /  23034MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

Okay, cool. Thank you so much!.  So, we should be able to attach the GPU to latest 2.1 once you merge this PR, https://github.com/GoogleCloudDataproc/initialization-actions/pull/1190. Is that correct?

The update is also working on 2.0 images:
Thu Jun 20 19:08:20 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.54.14              Driver Version: 550.54.14      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA L4                      Off |   00000000:00:03.0 Off |                    0 |
| N/A   62C    P0             32W /   72W |       0MiB /  23034MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

@cjac I am facing the following error while attaching GPU to Dataproc 2.2 cluster
The following packages have unmet dependencies:
systemd : Depends: libsystemd0 (= 252.26-1~deb12u2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

sleep 5
(( i++ ))
(( i < 10 ))
eval 'apt-get install -y -q pciutils'
++ apt-get install -y -q pciutils
Reading package lists...
Building dependency tree...
Reading state information...
pciutils is already the newest version (1:3.9.0-4).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
systemd : Depends: libsystemd0 (= 252.26-1~deb12u2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

sleep 5
(( i++ ))
(( i < 10 ))
eval 'apt-get install -y -q pciutils'
++ apt-get install -y -q pciutils
Reading package lists...
Building dependency tree...
Reading state information...
pciutils is already the newest version (1:3.9.0-4).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
systemd : Depends: libsystemd0 (= 252.26-1~deb12u2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

sleep 5
(( i++ ))
(( i < 10 ))
eval 'apt-get install -y -q pciutils'
++ apt-get install -y -q pciutils
Reading package lists...
Building dependency tree...
Reading state information...
pciutils is already the newest version (1:3.9.0-4).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
systemd : Depends: libsystemd0 (= 252.26-1~deb12u2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

sleep 5
(( i++ ))
(( i < 10 ))
return 1
Any workaround to proceed further? Tried with latest from master branch and the changes from 1190 PR

TL;DR: Debian started enforcing deprecation of apt-key add; must move repo signing key to its own file and reference by path in sources.list file
I am fixing.  You can find a workaround at the end of install_gpu_drivers.sh in my rapids work branch
https://github.com/cjac/initialization-actions/blob/e43a1eaa402dc8a81aa8853cafb32e906f72f80f/gpu/install_gpu_driver.sh#L1077

You can likely use that whole file if extracting the function is too complicated.

@cjac Okay,Thanks!. Will it work with secure boot disabled or should I enable it?.

@cjac I tried with that workaround script you mentioned  but still breaking with similar error in Dataproc 2.2
-----END PGP PUBLIC KEY BLOCK-----'

sed -i -e 's:deb https:deb [signed-by=/usr/share/keyrings/mysql.gpg] https:g' /etc/apt/sources.list.d/mysql.list
rm -rf /etc/apt/trusted.gpg
main
is_debian
++ os_id
++ cut -d= -f2
++ grep '^ID=' /etc/os-release
++ xargs
[[ debian == \d\e\b\i\a\n ]]
remove_old_backports
is_debian12
is_debian
++ os_id
++ xargs
++ cut -d= -f2
++ grep '^ID=' /etc/os-release
[[ debian == \d\e\b\i\a\n ]]
++ os_version
++ xargs
++ cut -d= -f2
++ grep '^VERSION_ID=' /etc/os-release
[[ 12 == \1\2* ]]
return
is_debian
++ os_id
++ xargs
++ cut -d= -f2
++ grep '^ID=' /etc/os-release
[[ debian == \d\e\b\i\a\n ]]
export DEBIAN_FRONTEND=noninteractive
DEBIAN_FRONTEND=noninteractive
execute_with_retries 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
local -r 'cmd=apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
(( i = 0 ))
(( i < 3 ))
eval 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
++ apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
sleep 5
(( i++ ))
(( i < 3 ))
eval 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
++ apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
sleep 5
(( i++ ))
(( i < 3 ))
eval 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
++ apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
sleep 5
(( i++ ))
(( i < 3 ))
return 1

package cache update command included in #1240 as commit 234515d

@cjac I tried with package cache update, but getting same error:-
cAZUlaj3id3TxquAlud4lWDz
=h5nH
-----END PGP PUBLIC KEY BLOCK-----'

gpg --dearmor -o /usr/share/keyrings/mysql.gpg
sed -i -e 's:deb https:deb [signed-by=/usr/share/keyrings/mysql.gpg] https:g' /etc/apt/sources.list.d/mysql.list
rm -rf /etc/apt/trusted.gpg
apt-get update
Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B]
Get:5 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B]
Get:7 https://packages.cloud.google.com/apt google-compute-engine-bookworm-stable InRelease [1321 B]
Get:8 https://download.docker.com/linux/debian bookworm InRelease [43.3 kB]
Hit:9 https://repo.mysql.com/apt/debian bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm InRelease
Get:3 https://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:4 https://deb.debian.org/debian bookworm-backports InRelease [59.0 kB]
Get:6 https://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:10 https://packages.adoptium.net/artifactory/deb bookworm InRelease [7517 B]
Get:11 https://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease [1654 B]
Get:12 https://packages.cloud.google.com/apt google-compute-engine-bookworm-stable/main amd64 Packages [3128 B]
Get:13 https://download.docker.com/linux/debian bookworm/stable amd64 Packages [31.3 kB]
Get:14 https://storage.googleapis.com/goog-dataproc-bigtop-repo-us-west4/2_2_deb12_20240606_230238-RC01 dataproc InRelease [3708 B]
Get:15 https://deb.debian.org/debian bookworm-updates/main Sources.diff/Index [11.7 kB]
Get:16 https://deb.debian.org/debian bookworm-updates/main amd64 Packages.diff/Index [11.7 kB]
Get:17 https://deb.debian.org/debian bookworm-updates/main Translation-en.diff/Index [11.7 kB]
Get:18 https://deb.debian.org/debian bookworm-updates/main Sources T-2024-09-10-2011.55-F-2024-09-10-2011.55.pdiff [562 B]
Get:19 https://deb.debian.org/debian bookworm-updates/main amd64 Packages T-2024-09-10-2011.55-F-2024-09-10-2011.55.pdiff [1116 B]
Get:18 https://deb.debian.org/debian bookworm-updates/main Sources T-2024-09-10-2011.55-F-2024-09-10-2011.55.pdiff [562 B]
Get:19 https://deb.debian.org/debian bookworm-updates/main amd64 Packages T-2024-09-10-2011.55-F-2024-09-10-2011.55.pdiff [1116 B]
Get:20 https://deb.debian.org/debian bookworm-updates/main Translation-en T-2024-09-10-2011.55-F-2024-09-10-2011.55.pdiff [538 B]
Get:20 https://deb.debian.org/debian bookworm-updates/main Translation-en T-2024-09-10-2011.55-F-2024-09-10-2011.55.pdiff [538 B]
Get:21 https://deb.debian.org/debian bookworm-backports/main Sources.diff/Index [63.3 kB]
Ign:21 https://deb.debian.org/debian bookworm-backports/main Sources.diff/Index
Get:22 https://deb.debian.org/debian bookworm-backports/main amd64 Packages.diff/Index [63.3 kB]
Get:23 https://deb.debian.org/debian bookworm-backports/main Translation-en.diff/Index [63.3 kB]
Get:25 https://deb.debian.org/debian bookworm-backports/main amd64 Packages T-2024-09-25-2006.54-F-2024-09-03-2007.15.pdiff [57.0 kB]
Get:25 https://deb.debian.org/debian bookworm-backports/main amd64 Packages T-2024-09-25-2006.54-F-2024-09-03-2007.15.pdiff [57.0 kB]
Get:26 https://deb.debian.org/debian bookworm-backports/main Translation-en T-2024-09-25-0804.34-F-2024-09-06-2122.28.pdiff [11.6 kB]
Get:26 https://deb.debian.org/debian bookworm-backports/main Translation-en T-2024-09-25-0804.34-F-2024-09-06-2122.28.pdiff [11.6 kB]
Get:24 https://deb.debian.org/debian bookworm-backports/main Sources [276 kB]
Get:27 https://deb.debian.org/debian-security bookworm-security/main Sources [110 kB]
Get:28 https://deb.debian.org/debian-security bookworm-security/main amd64 Packages [182 kB]
Get:29 https://deb.debian.org/debian-security bookworm-security/main Translation-en [111 kB]
Get:30 https://packages.adoptium.net/artifactory/deb bookworm/main amd64 Packages [7417 B]
Get:31 https://storage.googleapis.com/goog-dataproc-bigtop-repo-us-west4/2_2_deb12_20240606_230238-RC01 dataproc/contrib Sources [8442 B]
Get:32 https://packages.cloud.google.com/apt cloud-sdk-bookworm/main all Packages [1555 kB]
Get:33 https://packages.cloud.google.com/apt cloud-sdk-bookworm/main amd64 Packages [3337 kB]
Get:34 https://storage.googleapis.com/goog-dataproc-bigtop-repo-us-west4/2_2_deb12_20240606_230238-RC01 dataproc/contrib amd64 Packages [19.3 kB]
Fetched 6156 kB in 2s (3423 kB/s)
Reading package lists...
main
is_debian
++ os_id
++ grep '^ID=' /etc/os-release
++ xargs
++ cut -d= -f2
[[ debian == \d\e\b\i\a\n ]]
remove_old_backports
is_debian12
is_debian
++ os_id
++ grep '^ID=' /etc/os-release
++ xargs
++ cut -d= -f2
[[ debian == \d\e\b\i\a\n ]]
++ os_version
++ grep '^VERSION_ID=' /etc/os-release
++ xargs
++ cut -d= -f2
[[ 12 == \1\2* ]]
return
is_debian
++ os_id
++ grep '^ID=' /etc/os-release
++ xargs
++ cut -d= -f2
[[ debian == \d\e\b\i\a\n ]]
export DEBIAN_FRONTEND=noninteractive
DEBIAN_FRONTEND=noninteractive
execute_with_retries 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
local -r 'cmd=apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
(( i = 0 ))
(( i < 3 ))
eval 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
++ apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
sleep 5
(( i++ ))
(( i < 3 ))
eval 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
++ apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
sleep 5
(( i++ ))
(( i < 3 ))
eval 'apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64'
++ apt-get install -y -qq pciutils linux-headers-6.1.0-25-cloud-amd64
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
sleep 5
(( i++ ))
(( i < 3 ))
return 1


Decode PNG text chunks (tEXt, zTXt, iTXt)

Spun out of https://github.com/google/wuffs/issues/13#issuecomment-965769040

I need PNG metadata readout... complete support of text chunks (for thumbnails).

@pjanx can you clarify what "complete support" means? According to https://www.w3.org/TR/2003/REC-PNG-20031110/#11tEXt such chunks are actually key-value pairs. Do you need the keys too or only the values? iTXt chunks also have language codes (e.g. ISO 639, ISO 646) and the key can also be translated (e.g. from English to Japanese). Do you need that too?
It may be helpful if you can attach some example PNG files (with text chunks) and say what you need to crack out of them.

Complete means tEXt, zTXt, iTXt. Former two use Latin 1, last one UTF-8. There's also a minor complication in that these chunks can be at both ends of the file, the end user probably doesn't want to keep that distinction.
libpng simply accumulates them (though you need to read the start and end chunks both explicitly, unless using the constrained API) and then you can read an array out of the info structure. spng is rather similar.
What I'm doing is requesting values for particular keys, and I'm not interested in “translated keywords”. There can be multiple values for a given key, and the simplest viable high-level API is func(keyword string)[]string. ISO 8859-1 is trivially converted to UTF-8, so that defines the encoding. A low-level API would call back with:
struct {
    keyword, text string
    languageCode, translatedKeyword *string
}

Have a look at ~/.cache/thumbnails in a GNOME/KDE system. Specification.

Thanks for the comment. Just a quick reply to the idea of string, *string and []string in the APIs...
Wuffs' higher level auxiliary C++ API can do this but one memory-safety constraint on the lower level C API is that it cannot allocate memory and specifically, the callee cannot create or hold arbitrarily long strings. C also just doesn't have a good string type. I'm not sure which level you had in mind but, if your program is C and not C++, then you're obviously restricted to the C API, not C++.
In terms of API design, I'll also copy/paste from what I just wrote at https://github.com/google/wuffs/issues/39#issuecomment-966685935

Wuffs' image, image metadata and color correction APIs span many file formats... so there's some abstraction that might look weird at first glance.

In particular, languageCode and translatedKeyword may be part of PNG iTXt chunks, but IIRC they're not part of GIF, JPEG, etc.

The content encoding can be simply tagged, that would also be viable. I haven't had the necessity to learn about GIF or JPEG.
zTXt is compressed, not sure how you want to handle the decompression there, then.

iCCP payload is also zlib-compressed and we already handle that.

Where/by whom is the decompression buffer allocated?

Throughout Wuffs' C API, it's always the caller (not the callee) who allocates variable-length buffers. Pass that caller-allocated buffer as the wuffs_base__io_buffer* a_dst argument to wuffs_base__image_decoder__tell_me_more or wuffs_png__decoder__tell_me_more.
If the buffer is too short, that call will return wuffs_base__suspension__short_write and it's up to the caller to re-allocate and call again, or otherwise abort (because it cannot or will not allocate more memory).
The C++ API (e.g. used by example/imageviewer) manages the memory for you, so that the C++ callback (e.g. imageviewer's MyDecodeImageCallbacks::HandleMetadata) gets a contiguous (ptr, len) pair: the raw arg. If you want to dig into the C++ code, start with this line:
https://github.com/google/wuffs/blob/f4c2d4652e843ffbf63ab7e9898353044fdf59ba/internal/cgen/auxiliary/base.cc#L214

That sounds like ISO Latin 1 could still be just another decoder. Sadly, with zlib compression, it might be two levels of transformations to do.
Code for the encoding conversion is a trivial exercise, having it done automatically would just make the API less awkward to use.
Speaking of awkward, it looks like both libpng and spng make you assume the encoding based on the ‘type’ of the chunk, which is exposed in their structures. Luckily for me, everything above ASCII happens to be percent-encoded in thumbnails…

Wuffs' PNG decoder should now be able to give you text chunks (whether iTXt, tEXt or zTXt). If you're using the C++ API, this patch shows how to get the data. Starting at:
https://github.com/google/wuffs/blob/66cfd3e02f8c085963ca7ec122500f366226abe3/example/imageviewer/imageviewer.cc#L178
Apply:
diff --git a/example/imageviewer/imageviewer.cc b/example/imageviewer/imageviewer.cc
index 96938453..b0327414 100644
--- a/example/imageviewer/imageviewer.cc
+++ b/example/imageviewer/imageviewer.cc
@@ -175,6 +175,23 @@ class MyDecodeImageCallbacks : public wuffs_aux::DecodeImageCallbacks {
               1e5 / (g_flags.screen_gamma * minfo.metadata_parsed__gama());
           break;
       }
+    } else {
+      const char* name = nullptr;
+      switch (minfo.metadata__fourcc()) {
+        case WUFFS_BASE__FOURCC__KVPK:
+          name = "Key";
+          break;
+        case WUFFS_BASE__FOURCC__KVPV:
+          name = "Val";
+          break;
+      }
+      static char buf[4096];
+      if (name && (raw.len < 4096)) {
+        // Convert raw (a wuffs_base__slice_u8) to a NUL-terminated C string.
+        memcpy(buf, raw.ptr, raw.len);
+        buf[raw.len] = 0x00;
+        printf("    %s %s\n", name, buf);
+      }
     }
     return wuffs_aux::DecodeImageCallbacks::HandleMetadata(minfo, raw);
   }
@@ -244,6 +261,7 @@ load_image(const char* filename) {
   uint64_t dia_flags = 0;
   if (g_flags.screen_gamma > 0) {
     dia_flags |= wuffs_aux::DecodeImageArgFlags::REPORT_METADATA_GAMA;
+    dia_flags |= wuffs_aux::DecodeImageArgFlags::REPORT_METADATA_KVP;
   }

   MyDecodeImageCallbacks callbacks;

For example, running ./build-example.sh example/imageviewer && gen/bin/example-imageviewer ~/.cache/thumbnails/large/etc.png prints:
    Key Thumb::URI
    Val file:///usr/share/images/desktop-base/desktop-grub.png
    Key Thumb::MTime
    Val<PHONE_NUMBER>

If you're using the C API, test_wuffs_png_decode_metadata_kvp has some code you can study (link below). To keep the test simple, it assumes that the entire PNG input can fit into memory at once, as will each key/value pair within. If you're streaming, then you'll need to take care of Wuffs' usual "short read/write" suspensions.
https://github.com/google/wuffs/blob/66cfd3e02f8c085963ca7ec122500f366226abe3/test/c/std/png.c#L730

The callee, not the caller, translates from Latin-1 to UTF-8 when necessary.


Use the most current kube client connection for lease

Related Issue:  open-cluster-management/backlog#17342
Description of changes

Update the lease code to use the most current hub kube client every time the lease is renewed.
Reload config after any lease errors.
Reload config after any send error.

Instructions to test.  https://github.com/open-cluster-management/backlog/issues/17342#issuecomment-970770619


Can't send token to token/verify if http-only

In order to verify your token, you should send it to root/token/verify. However, if you are using JWT and are setting the tokens as HTTP-only cookies on the server, the client doesn't have access to this cookie and can thus not verify it.
The same is true for refreshing your token using root/token/refresh.
I think a feature should be added that takes the token from the HTTP-only cookies if no token is provided in the body of the request.

I briefly looked into this but I'm not very much at home in these packages. I'm not sure if the fix for this issue would require changes to rest_framework_simplejwt as well, since this package gets its response directly from that package in jwt_auth.py in line 14.
Would it be possible to add the value of the cookie to the request parameter before calling super().post()? This seems a bit hacky, though.

This issue is related to another one, someone proposed a temporary solution : #96
I tested the solution, and it's working pretty well ;)
Of course the best would be to resolve the issue, but since it's also linked to another package (djangorestframework-simplejwt) it's not that easy.

This issue is related to another one, someone proposed a temporary solution : #96
I tested the solution, and it's working pretty well ;)
Of course the best would be to resolve the issue, but since it's also linked to another package (djangorestframework-simplejwt) it's not that easy.

@SpicyPaper thanks for the link, I missed that issue. It seems (so far) to be working for me too, it seems like it wouldn't be a bad idea to implement this into this package and utilize it when using JWT, since it just doesn't work currently. @iMerica, could that code be used in the package?


apko is missing some version information

Run this following:
     _      ____    _  __   ___
    / \    |  _ \  | |/ /  / _ \
   / _ \   | |_) | | ' /  | | | |
  / ___ \  |  __/  | . \  | |_| |
 /_/   \_\ |_|     |_|\_\  \___/
apko

GitVersion:    v0.7.1
GitCommit:     unknown
GitTreeState:  unknown
BuildDate:     unknown
GoVersion:     go1.20.1
Compiler:      gc
Platform:      linux/arm64

The commit, tree state and build date are missing, which makes resolving issues a bit of guesswork to know what version someone is on.
When I run make apko, it does do the right thing:
     _      ____    _  __   ___
    / \    |  _ \  | |/ /  / _ \
   / _ \   | |_) | | ' /  | | | |
  / ___ \  |  __/  | . \  | |_| |
 /_/   \_\ |_|     |_|\_\  \___/
apko

GitVersion:    v0.7.2-11-gfab93a1
GitCommit:     fab93a165dcd81b06923a3dd6943a88223c19407
GitTreeState:  clean
BuildDate:     '2023-03-21T15:46:39Z'
GoVersion:     go1.20.1
Compiler:      gc
Platform:      darwin/arm64

So it has something to do with how it gets build for publishing in the release pipeline. I couldn't quite figure out where that is.
I think it has something to do with this in release.yaml:
    - name: Publish/Sign apko image
      run: |
        # If not a tagged release, override image tag to "canary"
        export IMAGE_TAG=${GITHUB_REF#refs/tags/}
        if [[ $GITHUB_REF != refs/tags/* ]]; then
          export IMAGE_TAG=canary
        fi
        make sign-image

This is probably due to how the apko apk is built in Wolfi: https://github.com/wolfi-dev/os/blob/main/apko.yaml

I was wondering why I could not find it in the pipelines in this repo. That explains it. 😄
The make apko target does the right thing with -X flags. Is there a way to use that instead? I don't quite know how to modify it.

Wolfi only ships the apko releases.  We provide ghcr.io/wolfi-dev/sdk:latest image for operational purposes.

@kaniini but we do still publish cgr.dev/chainguard/apko; should we not include the build information in them? We already have the semver and go ver; might as well get the rest?

Makes sense. I will file it.

Is it under [https://github.com/wolfi-dev/os/issues? That only gives the option for new package request or security vulnerability.

Just click other.  We will add package defect form.


Add cookies decision document

What is the context of this PR?
Documents the use of cookies and proposes some changes to simplify our usage of the session cookie.
How to review
Review the document and discuss.

@pricem14pc Yes. We changed from a permanent to a session cookie during the rehearsal to fix the weird IE bug with cookies being lost. expires_in is used to hold the amount of time to keep a server side session.


Exercise #2 Assigning Solid type to Shape3D type

For context, in Exercise #2, I have a Shape3D interface (implemented by Cuboid and Sphere) and a Solid interface (implemented by SolidCuboid and SolidSphere). Cuboid/Sphere are parent classes to SolidCuboid/SolidSphere.
Based on line 30-31 in the image, shape of type Shape3D is expected to be substituted by solid of type Solid.
I'm confused as to why substituting a Shape3D type with a Solid type is supposed to work if Shape3D is not a sub-type of Solid. Is there another connection that I should be making between the Shape3D and Solid interfaces to produce the expected assignment?

Shape3D is not a sub-type of Solid

you may want to reconsider this

Just a note, interfaces can extend other interfaces as well.


chore: update the repo URL

Closes #119

Current dependencies on/for this PR:

main

PR #123   👈

This stack of pull requests is managed by Graphite.

Merge activity

Dec 15, 11:38 AM: @@rphmeier started a stack merge that includes this pull request via Graphite.


failed to compile, Error in ... fesm5

Unable to use the package getting the following error.
ERROR in ./node_modules/ngx-daterangepicker/fesm5/ngx-daterangepicker.js Module not found: Error: Can't resolve 'date-fns' in '/home/velen/Desktop/dkt/santosh/rb2b-webapp/node_modules/ngx-daterangepicker/fesm5' ERROR in ./node_modules/ngx-daterangepicker/fesm5/ngx-daterangepicker.js Module not found: Error: Can't resolve 'date-fns/locale/en' in '/home/velen/Desktop/dkt/santosh/rb2b-webapp/node_modules/ngx-daterangepicker/fesm5' ERROR in ./node_modules/ngx-daterangepicker/fesm5/ngx-daterangepicker.js Module not found: Error: Can't resolve 'date-fns/locale/es' in '/home/velen/Desktop/dkt/santosh/rb2b-webapp/node_modules/ngx-daterangepicker/fesm5'
Is it related to installation? Please help how to fix this issue.

Fixed after installing date-fns
npm i<EMAIL_ADDRESS>


Add feature to automatically remove rules based on retention period

Add feature to automatically remove rules based on retention period
Description
We currently already have tasklog auto cleanup (https://github.com/apache/druid/pull/3677) and audit logs auto cleanup (https://github.com/apache/druid/pull/11084). This PR adds a similar auto cleanup based on duration (time to retained) but for the rules table to auto clean up rules of inactive datasource (datasource with no used and unused segments)
This is useful when Druid user has a high churn of task / datasource in a short amount of time causing the metadata store size to grow uncontrollably.
This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

LGTM

Overall LGTM
Is it possible for a user to create a segment with a custom version? What would happen in these cases? Do we need guardrails to prevent users from enabling this feature if there are segments that are not in the UTC format?

It is not possible for a user to specify a custom version. The only way possible would be for a user to connect to the metadata store directly and issue SQL to modify the version field. I don't think we need to consider this as that is not supported for regular operation.


integration-docs: Update for new format (Mention, Netlify, Opbeat, Open Collective)

Apply integration-docs' new format.
Fixes part of https://github.com/zulip/zulip/issues/29592.
Updated docs:

Mention

Netlify

Open Collective

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "buddy review"
@adnan-td @Niloth-p guys, please check this one out! Thanks

LGTM!

Thanks for the review guys, I mostly only update the Mention doc to address the reviews.
@zulipbot remove "buddy review"

@zulipbot add "mentor review"
@sbansal1999 Please review this too. Thanks

Update: addressed reviews, deleted Opbeat and updated the screenshots in PR description
@laurynmm Thanks for reviewing. let me know whether or not the changes looks good to you

@PieterCK - Looks like two of the review comments are still pending updates. Ping me again once those are addressed for another review.

@laurynmm - Ah, my bad. Sorry about that. I’ve updated the PR description and addressed the remaining comments.

@PieterCK - No worries and thanks for the quick update. Looks good and marking for integration review!
Noting that Netlify needs a logo update and the example message content in Mention should be improved; posting that in this CZO conversation.

Merged, thanks @PieterCK and reviewers!


Vim version of gloom color scheme.

This is a really good-looking color scheme, but since I'm a vim user, I wonder if there is a plan to make a vim version of this color scheme?

Currently I'm focusing on Atom, but I'm open to port it to vim and Sublime in the future.
In the spirit of open source I gladly let people make ports themselves if they reference and/or link to this repo. :)

+1 on a port to vim.
I tried to do it by myself with http://vim.ink/  but the tool doesn't allow you to setup different things :(

Guys i think you could give https://github.com/jacoborus/estilo a try it can quickly help you make themes for vim airline etc

Take a look at how this theme (the one i use currently on neovim is made)
https://github.com/mhartington/oceanic-next
Check under the estilo folder, everything seems quite readable tbh.
So maybe that could work?

Feel free to port it as long as you leave credit. I'm not a vim-user so it's better to let someone who knows what they're doing port this. 👍

awesome! i wont port it but hope someone else does 😛


Specify config file as parameter

Summary
It would be nice if I were able to specify the config file location in the indexer daemon. Being able to do something like:
./algorand-indexer daemon -f ~/node/indexer.yml
Current the only work around is to call the daemon directly from the directory where the config file is located.
Urgency/Relative Priority
Medium

https://github.com/algorand/ind exer/blob/develop/config/config.go#L23 looks like there are a few spots it could be read from

I'm aware of those options. That is however limiting in functionality as based on the individual developers directory/file structure, those areas may not be a convenient place to put the indexer config file. The ask is to open this up to allow for greater customizability by being able to specify the config file location when the process starts.