miflora sensor not working

Home Assistant release with the issue: 0.103.0
Last working Home Assistant release (if known): 0.102.0
Operating environment (Hass.io/Docker/Windows/etc.):

arch
armv7l

dev
false

docker
false

hassio
false

os_name
Linux

python_version
3.7.3

timezone
Europe/Berlin

version
0.103.0

virtualenv
true

Integration:
https://www.home-assistant.io/integrations/miflora/
Description of problem:
After start homeassistant this issue is reporting:
2019-12-16 18:05:27 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up platform miflora Traceback (most recent call last):   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 150, in _async_setup_platform     await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)   File "/usr/lib/python3.7/asyncio/tasks.py", line 416, in wait_for     return fut.result()   File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/miflora/sensor.py", line 75, in async_setup_platform     backend=backend,   File "/srv/homeassistant/lib/python3.7/site-packages/miflora/miflora_poller.py", line 37, in __init__     self._bt_interface = BluetoothInterface(backend, adapter) TypeError: __init__() takes 2 positional arguments but 3 were given
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
  - platform: miflora     mac: 'C4:7C:8D:6A:05:52'     name: Schlafzimmer Palme     force_update: true     median: 1     monitored_conditions:       - moisture       - light       - temperature       - conductivity       - battery
Traceback (if applicable):

Additional information:

This looks like it needs an update of the miflora library to version 0.6...

here the same error in the 0.103.2


How to work with file:/// format?

I tried following the pattern in your app linked me to https://developer.chrome.com/docs/extensions/mv3/match_patterns/
Pattern (example) file:///Users/somebody/dev/some-project does not work.  I tried dev/some-project and /Users/somebody/dev/some-project also.  Any hints?  "Allow in Private" is set to enabled.  I noticed "Allow access to file URLs" is missing, but maybe not needed for your extension?
Thanks for the extension!

Hey @kerryj89,
that one's on me, sorry — I slightly messed up the input validation pattern for file:// URLs.
Good news is that this bug is already fixed in the release I published on sunday (version 0.0.9). You just need to wait until someone from the Chrome team reviews the updated version and allows it into the Chrome web store. From my experience, this usually takes around 2-4 days, so you should receive the extension update by the end of the week. 🙂
FYI: Since the bug has already been fixed in code, I'm going to close this issue.

There we go, the new version is out. You can manually upgrade by going to chrome://extensions/?id=danncghahncanipdoajmakdbeaophenb and press the "Update" button. 🙂


TryFrom<starknet_api::transaction::InvokeTransaction> for InvokeFunction needs fixing

It needs to know the correct ChainId felt instead of using zero due to it being used in the tx hash value calculation, which will end up wrong always.
We either need to change  the tryfrom to a tuple or use  a standalone method. But the chainid data needs to be provided somehow.

This bug affects #967 and #970


Test - Quick recovery using wallet image in the relay

When ever there is any new data in the app like ward or name change or new account,
the details are encrypted and added to the wallet image
Test and close

-Verified this on live app and also on dev app version 1.4.0(180)


Update from pgrep to ps

This is still a work in progress, as I'm having lots of fun with the spec. I can't get them to run in their current state, so editing is proving to be fun.
Here's the proposed change so far, before tests are fixed.
Fixes #6

Tested on a dev cluster. Works as expected, and the latest change ensures it replicates the cmd and comm behavior we'd previously get from pgrep.

@aceofsteel says this is ok to merge as is, so I'll merge this. I'll also create a new issue and reference the need to fix the tests.


Channel force close stuck when min relay or mempool fee not met

This issue is related to #7512, but for channel force-close transactions specifically. The difference with the aforementioned issue is that commitment transactions may have been created at a time when the min mempool fee was lower still.
I did some testing on lnd v0.16.2-beta where I use a patch to force the commit tx fee to 253 sat/kw.

Set bitcoin core min relay fee to 100 sat/b
Alice and Bob open a channel
Bob goes offline, Alice force-closes

As expected, the logs shows: [ERR] CNCT: ChannelArbitrator(5dbde9dac766745bee8843be9fdff49eaef43b31f68962a04e1fbfdbc920cda9:0): unable to broadcast close tx: unmatched backend error: -26: min relay fee not met, 284 < 27900
At this point lncli pendingchannels shows the channel, but it doesn't seem to get out of this again? Is it expected that a retry happens at some point automatically? I see that a restart of lnd does a retry though.
I thought that https://github.com/lightningnetwork/lnd/pull/7448 would take care of it, but after a minute (default timeout) of waiting, is doesn't seem that it does.

Digging a little deeper, it seems that the rebroadcaster logs [ERR] BTCN: Broadcast attempt failed: -26: min relay fee not met, 2810 < 27900 and then also doesn't store the tx for rebroadcast.
https://github.com/lightninglabs/neutrino/blob/9badd7f8a27f0c24e9ba8cc191d58e7899e5e47f/pushtx/broadcaster.go#L177

The fix seems to be to parse the error string and to save the transaction if we encounter min relay fee not met. I could take a look at this.

Yes, and also the other one, min mempool fee not met.

@bitromortac the current IsBroadcastError was created mainly for neutrino, and also back when bitcoind actually sent reject messages (they removed it, but btcd still sends them). What we want to do here is also expand it to check the set of JSON RPC error messages, which we observe here: https://github.com/btcsuite/btcwallet/blob/4383930e9c4c07dba5cf7444b0c08c47bd2be30a/wallet/wallet.go#L3655-L3795
After that, we can get rid of this hack: https://github.com/lightningnetwork/lnd/blob/master/lnwallet/wallet.go#L476-L486

I reproduced your issue with min relay fee not met by setting -minrelaytxfee=0.00100000 :+1:. Something I'm not 100% clear on is why you needed to patch lnd to use a lower ctx fee?

Ah I think I wanted to be sure that the commit fee wouldn't exceed min relay tx fee. But on a test network that is indeed not going to happen anyway. No patching required.

@saubyk #7726 doesn't fix this.


Version 2.0.0

Pull Request Test Coverage Report for Build 84

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 59:
0.0%

Covered Lines:
114

Relevant Lines:
114

💛  - Coveralls


Use High Priority/Low Priority tags when ordering puzzles

High pri puzzles should appear above normal puzzles should appear above low pri puzzles. Should just add this logic to puzzleComparator in hunts/src/puzzleSlice.js

Hi @rgossiaux, sounds interesting. I'd like to work on this.

Hi @rgossiaux, sounds interesting. I'd like to work on this.

@SamuelJohnson01997 At the moment we're only looking for contributions from folks within the puzzle hunt community, sorry.

@SamuelJohnson01997 At the moment we're only looking for contributions from folks within the puzzle hunt community, sorry.

Fixed with #325 , thanks @leonyz !

Fixed with #325 , thanks @leonyz !


An issue about the AssertQubitWithinTolerance operation

Description
Hello! As shown in the below testcase, a qubit is defined, which is named NISLVariable0. When H is applied to NISLVariable0,  it has a 50% chance of being 0 and a chance of 50% being 1. But when excepted is set to Zero and tolerance is set to 0.5, the operation AssertQubitWithinTolerance throws an exception. Is this a normal behavior of the operation? And what does the tolerance parameter mean?
Testcase
namespace NISLNameSpace {
	open Microsoft.Quantum.Intrinsic;
	open Microsoft.Quantum.Convert;
	open Microsoft.Quantum.Math;
	open Microsoft.Quantum.Diagnostics;

	operation NISLOperation () : Unit {
		mutable expected = Zero;
		use NISLVariable0 = Qubit();
		H(NISLVariable0);
		mutable tolerance = 0.5;
		AssertQubitWithinTolerance(expected, NISLVariable0, tolerance);
        	Reset(NISLVariable0);
	}

	@EntryPoint()
	operation main() : Unit {
		mutable tmp = NISLOperation();
	}
}

Actual Behavior
Unhandled exception. Microsoft.Quantum.Simulation.Core.ExecutionFailException: Qubit in invalid state. Expecting: Zero with tolerance 0.5
        Expected:       1
        Actual: 0.4999999999999999

Expected Behavior
No exception
Environment
Operating system: Windows 10
dotnet version: 3.1.414
QDK: 0.21.2111177148
Command
dotnet run

@QuXing9: I am transferring this issue, since AssertQubitWithinTolerance is implemented in this repository. It seems that the problem arises from this line:
https://github.com/microsoft/qsharp-runtime/blob/e5be79bf9781f228c99b5d0d1d7ccd944ef20a89/src/Simulation/Simulators/CommonNativeSimulator/AssertProb.cs#L46
where a > comparison is used, which might be intended. Therefore, you would need to reduce your tolerance to a value below 0.5, e.g., 0.49.

Thanks for the reply! I understand the meaning of the tolerance parameter.
Meanwhile, there is another question that confused me.
from this line:
https://github.com/microsoft/qsharp-runtime/blob/e5be79bf9781f228c99b5d0d1d7ccd944ef20a89/src/Simulation/Simulators/CommonNativeSimulator/AssertProb.cs#L44
ensemblePr will always return 0.500……1. Does this mean that when H operation is applied to a qubit, it returns Zero with a probability of 0.499……9 and One with a probability of 0.500……1 ? Why not just return 0.5?

By the way, there is a small suggestion.
Since the value of tolerance ranges from 0.0 to 1.0. If it is less than 0.0, the AssertQubitWithinTolerance will throw an exception always. If it is greater than 1.0. the AssertQubitWithinTolerance will execute correctly. Therefore, is it possible to add judgment or assertion on tolerance value at Line 28 of the AssertMeasurementProbability ? In this way, it will avoid the execution of redundant code and improve the efficiency of program execution.
https://github.com/microsoft/qsharp-runtime/blob/e5be79bf9781f228c99b5d0d1d7ccd944ef20a89/src/Simulation/Simulators/CommonNativeSimulator/AssertProb.cs#L27-L28
Forgive me if I'm wrong.


#[document_codes] attribute macro

So it turns out that derive macros can't expand anything in-place: they can only generate new code in a completely different area.
We need a #[document_codes] attribute macro that you can slap at the toplevel of anything using the Diagnostic derive, which goes through and adds #[doc(alias = "my::code::here")] to the error struct or enum, in the appropriate places.
This might be tricky because you're injecting stuff in the middle of a tokenstream, but maybe it's easier than it sounds?

Update: This isn't possible on stable Rust yet (booo).
Tracking issue for stabilization: https://github.com/rust-lang/rust/issues/81119

You know what? I'm just gonna scrap this idea for the foreseeable future, seeing as we have url(...) (and particulaly url(docsrs) now. Wee


Consider Monorepository

Having gazillions of repositories for something that is essentially just an adapter seems overkill for maintenance and user adoption. See for example doctrine/cache, which has all the adapters in a single project.

Same as #52 actually

lets discuss in #52


feat: add update autofocus z position + tests

This PR adds a logic to the AutoFocusPlan event method to get and update the z position that should be used in the autofocus event in case of a relative zplan.

@tlambert03 this should be ok for you to have a look I think. I did the update mentioned here https://github.com/pymmcore-plus/useq-schema/pull/96#discussion_r1264549235 and I also worked a bit on the docs.


Add datasource for deployment-templates

Description

Adds a new datasource for deployment-templates.
By default the hidden deployment templates are filtered out. I think this is useful to show only the preferred templates similar to the UI

It is possible to get the full list of older templates by setting show_hidden: true

The data for the datasource looks like this:
> data.ec_deployment_templates.test
{
  "region" = "aws-eu-west-1"
  "show_hidden" = false
  "stack_version" = "8.7.0"
  "templates" = tolist([
    {
      "description" = "Suitable for ingestion use cases with 1-4 days of data available for fast access and for search use cases with indexing and querying workloads. Provides the most CPU resources per unit of RAM."
      "hidden" = false
      "id" = "aws-cpu-optimized-arm"
      "min_stack_version" = "7.14.0"
      "name" = "CPU optimized (ARM)"
    },
   [...]
  ])
}

Related Issues

https://github.com/elastic/terraform-provider-ec/issues/724
Motivation and Context

How Has This Been Tested?

Some manual testing in QA with a simple tf file containing just the datasource

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (improves code quality but has no user-facing effect)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation

Readiness Checklist

[x] My code follows the code style of this project
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Yeah, the topology could be useful to see the available instance-sizes 🤔

I agree with @dimuon that it makes sense to have the ability to get a template by id too (as I understand, this gets the template by name?)
not sure if the ID part has to be part of this PR, or can be left to a later stage though.

as I understand, this gets the template by name

Currently it lists templates in a region. The idea behind that being that as a user you wouldn't actually know the deployment-templates or their ids, so you can list all available ones.
When getting by id, what kind of information would you want to see in the template? (Since currently the main useful info is the id itself to be used when creating a deployment).
Though it could be very useful to add the topology in the same format as used for the resource. Then it would be easier to configure a deployment by taking info from the template.

Ah gotcha @gigerdo . Yes, topology and Id are definitely the key aspects here, getting one by ID should be useful that way too

Also I'm wondering if I should change hidden to deprecated as it is done here: https://www.elastic.co/guide/en/cloud/current/ec-regions-templates-instances.html
Although in our API we use hidden, I think it is more clear to call them deprecated to make it clear that the non-deprecated ones should be used.

I updated the PR:

Now it is also possible to filter by id
The returned template contains topology information as well

@gigerdo , can you also please check why the acc test failed?

@gigerdo @dimuon , can we please release a version of the provider after this one is merged?


[To Main] Style hotfix for Chromium-based browsers

Issue #: N/A
Description of changes:

Hotfix Fix styling issues with the new admin header

Fixed an issue where page widths above 100% were causing the header to become misaligned
Fixed a z-index issue with the tenant selector on mobile

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.03%. Comparing base (ec3c7be) to head (2435d29).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2572   +/-   ##
=======================================
  Coverage   76.03%   76.03%
=======================================
  Files         609      609
  Lines       22075    22075
  Branches     1782     1782
=======================================
  Hits        16785    16785
  Misses       5026     5026
  Partials      264      264

Flag
Coverage Δ

metweb
65.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...eb/src/components/layout/Header/InternalHeader.tsx
87.12% <ø> (ø)


Stop relying on galaxy.ansible.com service

With the amount of failures of the service, we can't realy rely on it anymore. Using plain git as sources for
ansible-galaxy collection install should make molecule runs more stable.
If needed, we may also pin a collection to a specific version, just by adding "version: foo" to the entry.

Locally tested here:
Cloning into '/root/.ansible/tmp/ansible-local-162mxb90_6e/tmpuun9h0ts/ansible.posixls4nymre'...
Your branch is up to date with 'origin/main'.
Cloning into '/root/.ansible/tmp/ansible-local-162mxb90_6e/tmpuun9h0ts/community.general59gsi2wo'...
Your branch is up to date with 'origin/main'.
Cloning into '/root/.ansible/tmp/ansible-local-162mxb90_6e/tmpuun9h0ts/ansible-podman-collections28siuaou'...
Your branch is up to date with 'origin/master'.
Starting galaxy collection install process
Process install dependency map
Starting collection install process
Installing 'ansible.posix:1.5.0' to '/usr/share/ansible/collections/ansible_collections/ansible/posix'
Created collection for ansible.posix:1.5.0 at /usr/share/ansible/collections/ansible_collections/ansible/posix
ansible.posix:1.5.0 was installed successfully
Installing 'community.general:6.5.0' to '/usr/share/ansible/collections/ansible_collections/community/general'
Created collection for community.general:6.5.0 at /usr/share/ansible/collections/ansible_collections/community/general
community.general:6.5.0 was installed successfully
Installing 'containers.podman:1.10.1' to '/usr/share/ansible/collections/ansible_collections/containers/podman'
Created collection for containers.podman:1.10.1 at /usr/share/ansible/collections/ansible_collections/containers/podman
containers.podman:1.10.1 was installed successfully

Seems even faster. Now, the only issue is: maybe github will rate limit us. Though I doubt it will get to that extend.

/lgtm


Custom node labels based on node pools

User Story
- As a cluster admin I want to ensure that all worker nodes in a node pool have the same set of custom labels, so that we can schedule workloads in a targeted and flexible way.
Details, Background
Currently worker nodes with the same node pool share the node pool identifier as a label, however this identifier is currently created by Giant Swarm when creating a node pool.
This makes it difficult to decide for a given workload (e. g. deployment) to use some node pool(s), but avoid using some other node pool(s). It enforces any node selectors being very specific to the tenant cluster used.
One practical use case is a tenant cluster where one node pool provides GPUs while the others do not. Adding a custom label to all nodes of the pool, indicating that the node has a GPU, would allow to define node selectors and taints which assign workloads that need the GPU to the right nodes, while allowing other workloads to specifically avoid these (expensive) nodes.
Defining the custom labels on the node pool level would conceptually allow to ensure them on every new node being added to the pool.
Lifecycle:

Modifying the custom labels (adding a label, deleting a label, changing a label) on the node pool must affect all existing nodes of the pool.

Blocked by / depends on

Related function: We already support custom labels on the tenant cluster level. These affect the Cluster resource, but they don't affect the kubernetes nodes. Here, in contrast, the labels would likely have to be set on the MachineDeployment level and be copied to the worker nodes.

@alex-dabija we have a customer requesting this on Azure as well, could you invite Team Celestial to the refinement session so we are on the same page?


Syntax highlighting in code frames and diffs

We should consider highlighting code frames and diffs.
I think a good first step would be to implement semantic highlighting into ruff server that, given a string, emits a description of the highlighting. The codeframe and diff rendering can then reuse the same infrastructure to implement.
This is related to https://github.com/astral-sh/ruff-lsp/issues/237

This is really important. I hope this feature can be implemented soon.

I'd very much like to see that.
Currently when using VSCode, you must use the Python extension for syntax highlighting so ruff can't completely replace it and they be used together (which kind-of misses the point of being fast when you must use another extension that's slow).

While this feature is also important to me, I believe a linter shouldn't be concerned with it. Ruff should focus on "making every kind of linter work within its scope," rather than "trying to solve everything."

I think ruff's leap into automatic formatting - and doing a damn good job of it - kinda broke that seal already. I think the desire to see this feature seems from that, and sort of completing the "triad" of core tools that having ruff replace would be a Godsend.
I'd very much enjoy having centralized configuration if these elements in ruff so I can fully replace the Intelligence stuff (it can be very slow).


Improve timestamp field accuracy for YouTube livestreams

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

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

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I'm running yt-dlp version 2022.11.11 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Netherlands
Example URLs
Any livestream that finished a few hours ago.
Provide a description that is worded well enough to be understood
When invoking yt-dlp with --flat-playlist and --extractor-args youtubetab:approximate-date it extracts the timestamp field from the humanized date form that YouTube exposes.
For normal videos, this is accurate.
However, for livestreams: YouTube displays when the livestream ended, not when it started.
It would improve the accuracy if yt-dlp subtracted the length of the video from the timestamp field for livestreams.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp -vU --flat-playlist --skip-download --playlist-reverse -O '%(.{availability,webpage_url,timestamp,release_timestamp,live_status})#j' --extractor-args youtubetab:approximate-date -f 'bestvideo[vcodec^=avc1][height=720]+bestaudio[ext=m4a]/bestvideo[vcodec!*=av01][vcodec!*=vp9.2][height=720]+bestaudio/bestvideo[vcodec^=avc1][height<=720]+bestaudio[ext=m4a]/bestvideo[vcodec!*=av01][vcodec!*=vp9.2]+bestaudio/best[vcodec!*=av01][vcodec!*=vp9.2]/bestvideo[ext=mp4]+bestaudio[ext=m4a]/best' --compat-options no-youtube-unavailable-videos https://www.youtube.com/c/DePoppenCast/videos
[debug] Command-line config: ['-vU', '--flat-playlist', '--skip-download', '--playlist-reverse', '-O', '%(.{availability,webpage_url,timestamp,release_timestamp,live_status})#j', '--extractor-args', 'youtubetab:approximate-date', '-f', 'bestvideo[vcodec^=avc1][height=720]+bestaudio[ext=m4a]/bestvideo[vcodec!*=av01][vcodec!*=vp9.2][height=720]+bestaudio/bestvideo[vcodec^=avc1][height<=720]+bestaudio[ext=m4a]/bestvideo[vcodec!*=av01][vcodec!*=vp9.2]+bestaudio/best[vcodec!*=av01][vcodec!*=vp9.2]/bestvideo[ext=mp4]+bestaudio[ext=m4a]/best', '--compat-options', 'no-youtube-unavailable-videos', 'https://www.youtube.com/c/DePoppenCast/videos']
[debug] User config "/home/ewout/.config/yt-dlp/config": ['--cookies-from-browser', 'firefox', '--no-mtime']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.11.11 [8b64402]
[debug] Compatibility options: no-youtube-unavailable-videos
[debug] Python 3.10.8 (CPython x86_64 64bit) - Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 (OpenSSL 3.0.7 1 Nov 2022, glibc 2.36)
[debug] exe versions: ffmpeg 5.1.2 (setts), ffprobe 5.1.2, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.15.0, brotlicffi-<IP_ADDRESS>, certifi-2022.09.24, mutagen-1.46.0, secretstorage-3.3.3, sqlite3-2.6.0, websockets-10.3, xattr-0.10.0
[Cookies] Extracting cookies from firefox
[debug] Extracting cookies from: "/home/ewout/.mozilla/firefox/7twg5yyt.default-release-backup/cookies.sqlite"
[Cookies] Extracted 1708 cookies from firefox
[debug] Proxy map: {}
[debug] Loaded 1723 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.11.11, Current version: 2022.11.11
yt-dlp is up to date (2022.11.11)
[debug] [youtube:tab] Extracting URL: https://www.youtube.com/c/DePoppenCast/videos
[youtube:tab] DePoppenCast/videos: Downloading webpage
[debug] [youtube:tab] Selected tab: 'videos' (videos), Requested tab: 'videos'
[download] Downloading playlist: De PoppenCast - Videos
[debug] [youtube:tab] Extracted SAPISID cookie
[youtube:tab] UCuuFekvVyvN0qYs1sWWYFzQ page 1: Downloading API JSON
[youtube:tab] UCuuFekvVyvN0qYs1sWWYFzQ page 2: Downloading API JSON
[youtube:tab] UCuuFekvVyvN0qYs1sWWYFzQ page 3: Downloading API JSON
[youtube:tab] UCuuFekvVyvN0qYs1sWWYFzQ page 4: Downloading API JSON
[youtube:tab] Playlist De PoppenCast - Videos: Downloading 125 videos of 125
[debug] The information of all playlist entries will be held in memory
[download] Downloading video 1 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=fN5w40KGQEk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 2 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=fi9yzzekv5s",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 3 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=9f5VmLNauac",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 4 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=RTN3WNJ5TX0",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 5 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=7hdfEEQ2DW4",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 6 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=xHSigu-D-XQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 7 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=BC7HCjokuHk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 8 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=Y0EJgMFYoCY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 9 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=4YqyoqPA17g",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 10 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=MOXapxfuAMg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 11 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=r3v5ewYvitU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 12 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=KckFaKkSyd4",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 13 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=Sbx-_BN9kaU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 14 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=m1IvMnylFa8",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 15 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=y8ys8sGcscI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 16 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=Z4MOYNqvOvs",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 17 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=npCWT4auTzg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 18 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=jGPpPi2Ln5U",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 19 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=sGV1WqO0s-I",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 20 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=fVkeM8PSfPQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 21 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=McEoFTbrB78",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 22 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=a7pwUkOAglA",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 23 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=HG1CGgt2HNQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 24 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=4evaSHfaW58",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 25 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ZBX06onPfrg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 26 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=WHMRv3x1jD8",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 27 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=m7Gtp-vUQ4I",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 28 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=cFhxKLPS2R0",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 29 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=4i8fVTXz7ok",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 30 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=GBRW24jLBzY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 31 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=otflXObtatQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 32 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=mYqcHabRBxk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 33 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=FxiXRVdzMLQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 34 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=xp_-O2g8QEc",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 35 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=8QuQjQMm0Og",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 36 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=060j1pkv-cA",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 37 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=42Ro6mFQShQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 38 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=TWdwPV6RGNw",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 39 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=G5hjArJ6Ejs",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 40 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=BQ5z1fkuU20",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 41 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=fBlCNZQFBxo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 42 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=XSRmNczSy7k",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 43 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=YNigal6EBTg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 44 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=JCuJKtgyoMY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 45 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=DQ4CLHTDDvw",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 46 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=IaOuz1A1Czc",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 47 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=0NVNG3LezFo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 48 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ieozMNC-ZVg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 49 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=RjBX-bTPYpo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 50 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=qy5SA9ZUP8k",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 51 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=UlKL8fG48OU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 52 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=kc6COgdeqko",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 53 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=nAqQ98bztro",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 54 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=IM_gvx6iw2s",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 55 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=W5N4-m0D04E",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 56 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=-z7rjXYi_gw",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 57 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=6eaZ-GdJJZY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 58 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=dRU860U0CLg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 59 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=93WHVSDbFVA",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 60 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=hZHEZb9VQRk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 61 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=msKdKxyQYuk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 62 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ywA0qOvO0Uo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 63 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=RZbpbxpo5UI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 64 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=BIdFbVaEc0M",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 65 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=GWqS6T2KkmY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 66 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=oDsAkLyim5E",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 67 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=2qG3zYj186w",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 68 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=_0kKUAxzUW4",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 69 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=h8p5rgtvaVA",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 70 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=bhXhe6h_c4M",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 71 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ecFZP_9P3yk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 72 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=9nj0zwM33JU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 73 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=mYQodRXOsw4",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 74 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=odVEaZPjyXE",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 75 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=xiAB7BqnFgc",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 76 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=jfd8F7egNYU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 77 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=N_0oeRINz0Q",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 78 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=Kxo246AKb0k",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 79 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=7MIDnEbonfc",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 80 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=W3uKiZKHC9o",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 81 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=D6_Zk9c20Ws",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 82 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ohyq4w9nvfo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 83 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=lNJ1heGFGjI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 84 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=r6nR-9hzrIg",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 85 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=fRubqI9h9AE",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 86 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ggIX_wKN5NU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 87 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=a4lAnWmMIi8",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 88 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=RVQ3vriSIfo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 89 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=HAtGc2i9emY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 90 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=ejw5UMQ3vY0",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 91 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=sv65cZJkOJU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 92 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=9pRskyCQOog",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 93 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=6OMw_eZy4cI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 94 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=YIStul-rMvM",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 95 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=rV_ndfWlcwY",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 96 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=f0BeGpCoKZI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 97 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=c5TJDjPvEWQ",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 98 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=zatWyoLwh7s",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 99 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=HqEB4hD-L0E",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 100 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=GJxrDM-pXZs",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 101 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=6KksUbsbhQU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 102 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=a_w-HNDCUVw",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 103 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=IaapLYra1F0",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 104 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=l-Bk9UiokEk",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 105 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=KeGkWLy9wB4",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 106 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=lCucrQsSl3E",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 107 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=2tFJAKfZokI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 108 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=AH3rWn3moy0",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 109 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=pGZyUIOONGo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 110 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=AF8ODjJ3ITM",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 111 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=GcrdleooWIs",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 112 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=XYfdjarBuMI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 113 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=U1nrBfAPZN4",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 114 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=FlP8jgZre60",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 115 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=c41-jE_Yn5c",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 116 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=oIHikokBi54",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 117 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=SIwCIENNE8c",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 118 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=Vx4Fc8KYiAo",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 119 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=thZOvF-jfco",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 120 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=yiKglrS4t6o",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 121 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=AyC0qN2M8go",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 122 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=K86aXi16fGc",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 123 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=aFHm_O5xYYI",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 124 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=6lmWWe_f9kU",
    "timestamp":<PHONE_NUMBER>
}
[download] Downloading video 125 of 125
{
    "webpage_url": "https://www.youtube.com/watch?v=gE7HiFyH630",
    "timestamp":<PHONE_NUMBER>
}
[download] Finished downloading playlist: De PoppenCast - Videos

@coletdjnz

This doesn't make sense in most cases as the relative time will not be precise enough to get any meaningful value. E.g. subtracting 2 hours from a date that is only accurate up to the day.
It's an "approximation", not to be treated as accurate.

This doesn't make sense in most cases as the relative time will not be precise enough to get any meaningful value. E.g. subtracting 2 hours from a date that is only "accurate" up to the day.

It approximates to minute and hours precision as well, as that's the relative time YouTube shows depending on the time the tab is crawled.

Edit: also I believe for the full video extractor, the date that youtube provides us for upload date is the stream end time. But before and partly during the stream however it provides the earlier upload date iirc.

Yes, it should only subtract on livestreams that ended.

Currently using the logic implemented within yt-dlp to retrieve an approximation of the original publish date during channel synchronization from YouTube towards PeerTube.
This synchronization executes every hour after the video has been transcoded/processed by YouTube (filtering out post_live).
For normal videos, this results in accurate approximations. For livestreams it's always off the length of the video.


Added programs.

Zig Zag Array
Efficient Janitor

You can follow me on github

You can follow me on github


[CARBONDATA-4308]: added docs for streamer tool configs

Why is this PR needed?
What changes were proposed in this PR?
Does this PR introduce any user interface change?

No
Yes. (please explain the change and update document)

Is any new testcase added?

No
Yes

@akashrn5 please take a look.

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4416/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6159/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/550/

retest this please

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/551/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6160/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4417/

retest this please

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/552/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6161/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4418/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4422/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/556/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6165/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4423/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/557/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6166/

retest this please

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/558/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6167/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4424/

retest this please

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/560/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6169/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4426/

@ydvpankaj99 can you please check why this error keeps on coming? Can we do something to make CI more stable?

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6170/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4427/

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/561/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4429/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6172/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/563/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4432/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6176/

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/567/

retest this please

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/569/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4434/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6178/

@pratyakshsharma can you please fix the compilation issues

@akashrn5 Fixed.

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4438/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6182/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/573/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4439/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/574/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6183/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4440/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6184/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/575/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4441/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6185/

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/576/

retest this please

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4442/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/577/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6186/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6187/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4443/

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/578/

retest this please

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6188/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4444/

Build Success with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/579/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/6190/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/4446/

Build Failed  with Spark 3.1, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_3.1/581/

LGTM, the CI failure is not related to this PR


Updating kerl to follow master as well kerl org.

The version of kerl we were pinned to has a reference to the old
download page for OTP. The new version should look at the most recent
page.

👍

👍 pending travis happiness

👍


fix: Evade false positives for inout variable usage

I don't think this is the best/neatest solution, but it fixes the false positives

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.99%. Comparing base (3dd5dd3) to head (02431a3).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #493   +/-   ##
=======================================
  Coverage   91.99%   91.99%
=======================================
  Files          59       59
  Lines        5922     5923    +1
=======================================
+ Hits         5448     5449    +1
  Misses        474      474

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


Lack of i18n for error messages

MediaWiki uses this schema validation library for internal matters where non-English support is less important. However, JSON schemas are increasingly being used throughout MediaWiki, and we would like to use this library for all our needs, but lack of error message internationalization is an issue. I volunteer to address this but would like to check with you all first. (I am happy to keep English as a default language of sorts for backwards compatibility.)

Validation errors should provide a general key to indicate the error in a language-agnostic fashion. There has been debate about this in the past and while I understand the goal I believe it is important to keep validation logic separate from UI/content. Maintaining translations for validation failures in multiple languages is simply not a primary function of this package nor the maintainers, and the last thing we need is back and forth over error message semantics in, say, korean.
https://github.com/justinrainbow/json-schema/pulls?utf8=✓&q=is%3Apr is%3Aclosed i18n
Please see those closed PRs and give me your thoughts.

I agree that having language-agnostic error codes is good policy.
However, I look throughout the code, and I do not see language-agnostic error codes, but actual English strings. See this arbitrary example. Having a totally separate mechanism that takes validator errors and outputs localized strings is certainly workable, but first I would need proper error codes to work with. To use the linked example, the code could be something like ERROR_EXCLUSIVEMINIMUM_NOT_MET, which is then fed into something like ErrorLocalization::getErrorString( ERROR_EXCLUSIVEMINIMUM_NOT_MET, 'fr' ), and that would output a localized error message in a way that uncouples validation from UI.
Do you think this approach would work?

From the example (formatted for clarity):
$this->addError(
  $path,
  'Must have a minimum value of ' . $schema->minimum,
  'exclusiveMinimum',
  array('minimum' => $schema->minimum)
);

The addError method signature (formatted for clarity):
public function addError(
  JsonPointer $path = null,
  $message,
  $constraint = '',
  array $more = null
);

Does the $constraint and $more array in the example not provide the relevant data? It defines the constraint that failed and constraint criteria for clarification (e.g. the minimum that was not met in the example).
I used the example schema from the following page in the demo and it happened to demonstrate the example constraint/message:
http://json-schema.org/examples.html
$ php demo.php
JSON does not validate. Violations:
# var_dump of error array
array(5) {
  'property' =>
  string(3) "age"
  'pointer' =>
  string(4) "/age"
  'message' =>
  string(30) "Must have a minimum value of 0"
  'constraint' =>
  string(7) "minimum"
  'minimum' =>
  int(0)
}

Perhaps not every constraint is pushing out all of the details, but the error output today seems to meet the requirements for a separate mechanism for providing human-readable messages. Am I missing something?

@bighappyface I agree with everything you say, but perhaps we could make things a little easier for people that want to localize error messages by moving all of the possible values for $constraint to a separate file and referencing constants when calling addError? It wouldn't change the way errors look at all, but it would provide a centralized reference for anyone interested in localizing.

I am game for a PR

Okie-doke. Comin' up.

I also agree with @shmax that the error handling could use some improvement - thanks for the PR :-).

See #364 - Will be official in 6.0.0


change detection of valid modules for eunit

beam_lib:chunks(..) needs a path to object code which, frustratingly,
code:which/1 won't return for cover compiled modules. instead just
assume that if code:which/1 doesn't return non_existing a module
is something we can run tests on
fixes #1014

That does seem reasonable. +1.

Thanks!


Make NPM package leaner

Summary
The downloaded NPM package contains a few somewhat heavy gifs to not much benefit. This PR removes them and some other files not useful for production environments.
Test Plan
npm pack and see that these files are omitted from the resulting tarball.
What's required for testing (prerequisites)?
N/A
What are the steps to reproduce (after prerequisites)?
yarn add lottie-react-native && ls -la node_modules/lottie-react-native
Checklist

[ ] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

good catch! thanks @oblador


Fs 3570 Update to dataset lists

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Please also include any acceptance criteria if you have any.
https://dluhcdigital.atlassian.net/browse/FS-3570
https://dluhcdigital.atlassian.net/browse/FS-3572
https://dluhcdigital.atlassian.net/browse/FS-3569

Making changes to the data set forms to match the mural

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce
the testing if necessary.
Before PR's can be merged they will need to be tested by QA and approved where
applicable. To flag the change to QA assign @XGovFormBuilder/qa as one of the reviewers.

[ ] See the changes on the dataset form

Checklist:

[ ] My changes do not introduce any new linting errors
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation and versioning
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have rebased onto main and there are no code conflicts
[ ] I have checked deployments are working in all environments
[ ] I have updated the architecture diagrams as per Contribute.md

@adamdavies1 Since you partially fixed this ticket in your PR: https://dluhcdigital.atlassian.net/browse/FS-3569
Can you also update the question too?

@adamdavies1 Since you partially fixed this ticket in your PR: https://dluhcdigital.atlassian.net/browse/FS-3569
Can you also update the question too?

Done :)


Can't access koel via Web

After entering php artisan serve the Laravel developement server is starting, but everytime I try to access it via web-browser the conenction drops and gives Segmentation fault as output.
Is it a bug or do I have to take a look at my webserver config?
Worked everything fine on my local network.

Hi
Try this maybe php artisan serve --host <IP_ADDRESS>


Converting to .npy for test images

Hello SeanChenxy, can you kindly direct me to the code you executed to generate the .npy files for the test images you used? I have my custom dataset and want to test them but I am unable to generate the equivalent .npy for them. Any feedback is greatly appreciated.

Hi, if you do not need a accurate K, you can use a default K (see #7). Otherwise, please use following code to extract hand RoI and its K (i.e., my npy file).  https://github.com/SeanChenxy/HandMesh/blob/dbdca0d4fba75d7b010762edd4499b8102e06071/cmr/datasets/FreiHAND/freihand.py#L58


Getting started tutorial needs updating

Compiled SDFG does not require keyword args
In the Getting Started tutorial, just before code cell 11, the notebook states:
"A compiled SDFG, however, has to be invoked like an SDFG, with keyword arguments only:"
This does not seem to be correct; I can run the line fine with A as a positional argument.
Final SDFG does not match latest dace output
In the Explicit Dataflow example the outputted graph does not match that produced using Dace 0.13.1 and Python 3.10.4:
sse_sigma.txt

You are correct, if the SDFG was generated from one of the frontends (Python for example) it retains the order of the arguments. However, if the SDFG API is used, and sdfg.arg_names is not provided, keyword arguments must still be used. We'll clarify, thanks for reporting!


Package precompiled wasm files and make option available

manual cherry-pick of #25589

Package precompiled wasm images
Create wasmEnabled option with default false.

This PR DOES NOT turn on wasm/v8 for istio stats, but makes it available for experimentation.
@PiotrSikora @kyessenov

@mandarjog: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
9250bb7f36ec8b82ce338de51df7ae87d4520bd8
link
/test release-notes_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio_release-1.7


Allow ceres instances ssh to receive Instance ID from stdin

It would be very helpful if ceres instances ssh could receive json formatted instance information via stdin, similar to ceres instances run. This probably only makes sense if there is exactly one instance in the input data. In case more than one instance was passed in, an error should be issued.

NO!
But I can make instances list to allow for plain output as well.


ReadTimeout raised from general exception catching

Sentry link
https://sentry.io/share/issue/89863f561e9146fba39bb084e6310a68/
Description

This produces most of the events we are receiving from errors on the API, with 3.2k observations in the last 14 days at the moment of writing.
Origin in source code:
https://github.com/WordPress/openverse-api/blob/9f8b15773df511b0900e2a0adf7785382abee450/api/catalog/api/views/media_views.py#L206

Reproduction
visit https://api.openverse.engineering/v1/images/b312f615-6c9e-46e4-8738-d97e7836a8e1/thumb/

Rising this to high priority because this has been the main source of events in Sentry.

@krysal If it is okay with you, I'm going to close this issue in favour of https://github.com/WordPress/openverse/issues/1231 which has details more relevant to the current situation. The solution is probably still what @dhruvkb suggested, however, to just increase the timeout.


Is there a way to implement a model class into moor table

I'm creating a db implementation which is decoupled from ui modules and contact with the domain layer through models and abstract classes, I was able to implement an abstract class into moor's dao. Any way for me to implement this model into moor table?
class UserModel {
  final int localId;
  final int serverId;
  final String hostname;
  final String token;
  final int syncFreqInSeconds;
  final String syncPeriod;
  final bool darkThemeEnabled;
  final String language;

  UserModel({
    @required this.localId,
    @required this.serverId,
    @required this.hostname,
    @required this.token,
    this.syncFreqInSeconds,
    this.syncPeriod,
    @required this.darkThemeEnabled,
    this.language,
  });
}

Since moor generates classes from table declarations and not Dart models, doing this directly is impossible at the moment (see also #144).
To give more context, I'm a bit hesitated to work on features like that because moor isn't supposed to be an ORM. I see it more as a typesafe and convenient wrapper around sql that's still relational. If we were to support entities, we'd also have to support all kinds of references between them, which increases complexity of the generator. It could also be confusing for users, who'd have to decide between the Dart extends Table api, moor files, or generated tables from models.
I'd recommend to write an independent moor table with the same fields and then map between those:
@DataClassName('MoorUserModel')
class UserModels extends Table {
  IntColumn get localId => integer().primaryKey()();
  IntColumn get serverId => integer()();
  TextColumn get hostname => text()();
  // ...
}

Without leaking information between the domain and the data layer, you can then write mapping methods as extensions:
extension DomainToMoorExtension on UserModel {
  MoorUserModel get asMoor => MoorUserModel(
    localId: localId,
    serverId: serverId,
    hostname: hostname,
    // ...
  );
}

extension MoorToDomainExtension on MoorUserModel {
  UserModel get asDomain => UserModel(
    localid: localId,
    serverId: serverId,
    hostname: hostname
  );
}

Finally, you can then use the moor models in your dao
@UseDao(tables: [UserModels])
class MyDao extends DatabaseAccessor implements SomeDomainRepository {

  @override
  Future<UserModel> loadModelById(int id) => select(...).map((row) => row.asDomain).getSingle();

  @override
  Future<void> writeModel(UserModel model) {
    return into(userModels).insert(model.asMoor, mode: InsertMode.orReplace);
  }
}

If you're using companions for inserts, your might want to skip the domain -> moor extension and instead create a UserModelsCompanion.forInsert based on the domain model class.
I know that boilerplate is always boring, but this kind of mapping code helps to keep a clean separation between the data and domain layer. Further, the mapping code is still typesafe.

@simolus3 got it, thank you!


[Docker] Change base image for docker container: openjdk is being deprecated

Hello here!
According to the docker hub, the openjdk container is being deprecated completely

See also https://github.com/docker-library/openjdk/issues/505
The docker build of skill-services is based on the openjdk:18-jdk-slim-bullseye image
The discussion will probably be around which image to use as base from now on

PR: https://github.com/NationalSecurityAgency/skills-service/pull/1623

@antonionardella - the skills-service docker build has been updated to use eclipse-temurin. Thanks!


cacao 0.3.0 doesn't compile for iOS

I get the following error after upgrading cacao to the latest version.
error[E0308]: mismatched types
--> .../cacao-0.3.0/src/image/image.rs:211:26
|
211 |                   false => {
|  _________^
212 | |                     #[cfg(target_os = "macos")]
213 | |                     panic!("SFSymbols are only supported on macOS 11.0 and up.")
214 | |                 }
| |^ expected *-ptr, found ()
|
= note: expected raw pointer *mut Object
found unit type ()

Hmmm, are you trying to construct an Image here? At first I though this issue was a duplicate that'd be solved by #46, but now I suspect you're trying to do something that's not supported on iOS yet.
Have a code block I could glance at?

#49 should have fixed this, I think - curious if it takes care of your issue~

Closing this for now as I can't reproduce this - but if you (or anyone) can, feel free to comment and I can take another look~

I think the problem was just me not noticing that with cacao 3+ you need to enable uikit feature for ios development.


No 'Lease Status' property displays for one ADLS Gen2 blob container

Storage Explorer Version: 1.14.0-dev
Build: 20200614.2
Branch: rel/1.14.0
Platform/OS: Windows 10/ macOS Catalina / Linux Ubuntu 18.04
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand one ADLS Gen2 storage account -> Blob Containers.
Create a new blob container -> Check its Properties panel.

Expect Experience:
The property 'Lease Status' displays.
Actual Experience:
No property 'Lease Status' displays.

Hi @MRayermannMSFT
Verified this issue on build master/20200630.1.

The property 'Lease Status' displays well for one existing ADLS Gen2 blob container.

The property 'Lease Status' doesn't auto display for one new created ADLS Gen2 blob container.

Ok, fix fully checked into master now. Closing.


@chkr1011

when target to net461,  Framework dll files are copied to the target directory. eg netstandard.dll .

Originally posted by @panyi-dotnet in https://github.com/chkr1011/MQTTnet/issues/411#issuecomment-420921694

v 3.0

Hi,
this is correct because in nuspec we use netstandard library because .net 4.6.1+ support them properly.
Best regards
Christian

Please try with 3.0.1.


Truncation throws away stacktrace when request is too large

Looking at this code: https://github.com/rollbar/rollbar-gem/blob/a294430137758455d0a4ec0d45f08cb5aa50d5d6/lib/rollbar/truncation.rb#L20
Because of the order of operations in the .truncate method the Rollbar gem will choose a short backtrace using MinBodyStrategy, then if the payload is still too large it will throw away the request using RemoveRequestStrategy. But in the case of a very large request the old backtrace wouldn't necessarily have been too big on its own. It's also not clear if the payload is supposed to be mutated between strategies. It seems like there are a few ways to go with this algorithm:

Don't mutate the payload between strategies. Or maybe first try each strategy in a non-mutating way and then use a cumulative/mutating approach if that fails.
Put RemoveRequestStrategy before MinBodyStrategy
Put RemoveRequestStrategy before MinBodyStrategy and make RemoveRequestStrategy truncate individual keys in the request parameters to see if it will fit.
Some sort of approach where all permutations of different strategies are compared for the one that gets closest to the limit.

I would be in favor of allowing custom ordering (and removal) of strategies via the config, as well as allowing custom strategies.
Another thing that may help in your case, or for others. In practice, Rails backtraces are one of the biggest causes of large payloads. Recent support for Backtrace Cleaner can help with that. (Discussed here. https://docs.rollbar.com/docs/ruby#enabling-local-variables-in-stack-traces) It is smarter than the current backtrace strategy in the truncation code, and can be customized.


Color classes not working in specific browsers.

Description
I don't know, if i should use the @extend function anytime, but the color classes are not working on Safari, Firefox, IE. Only browser where it seems to work is Chrome.
I do not know, why this happend. Any help?
Repro Steps
http://codepen.io/anon/pen/dvrbOV
Very basic classes used.
I am using webpack (laravel) to compile the sass files.
Screenshots / Codepen

Working on my side on Chrome, Firefox and Edge.
There's a typo in the codepen, should be grey not gray.

You are right, but in my code it is "grey" just misspelled. As you can see on the screenshots the grey is correct (on Chrome).

I noticed the same since a few weeks on my site, but thought I messed things up.
But on the materialize sample pages for instance the striped example table doesn't show any color at all (no striped effect).
http://materializecss.com/table.html
using Firefox 52.0.2, using IE11 on Windows 7

Can you send a screenshot?

I have been using firefox debugging and just found out the striped color applied is gray95 which is practically invisible on my screen.
table.striped > tbody > tr:nth-child(odd) {
background-color: #f2f2f2;
}
So my report is bogus, question is, howcome only now this is showing.
Not sure what changed when exactly.


building ue4-build-prerequisites fails at apt update

Output of the ue4-docker info command:
ue4-docker version:         0.0.114 (latest available version is 0.0.114)
Operating system:           Linux (Arch Linux, 6.11.4-zen2-1-zen)
Docker daemon version:      27.3.1
NVIDIA Docker supported:    No
Maximum image size:         No limit detected
Available disk space:       500.34 GiB
Total system memory:        62.7 GiB physical, 36 GiB virtual
CPU:                        16 physical, 32 logical ()

Additional details:

Are you accessing the network through a proxy server? No

Build output:
➜  docker-root ue4-docker build 4.24.3
[ue4-docker build] COMMAND-LINE INVOCATION:
[ue4-docker build] ['ue4-docker', '4.24.3']

[ue4-docker build] UNREAL ENGINE VERSION SETTINGS:
[ue4-docker build] Custom build:  No
[ue4-docker build] Release:       4.24.3
[ue4-docker build] Repository:    https://github.com/EpicGames/UnrealEngine.git
[ue4-docker build] Branch/tag:    4.24.3-release

[ue4-docker build] ADVANCED CONFIGURATION OPTIONS:
[ue4-docker build] credential_mode: "secrets"
[ue4-docker build] excluded_components: {"ddc": false, "debug": false, "templates": false}
[ue4-docker build] gitdependencies_args: "--exclude=Android --exclude=Mac --exclude=Win32 --exclude=Win64"

[ue4-docker build] LINUX CONTAINER SETTINGS
[ue4-docker build] Base OS image: nvidia/opengl:1.0-glvnd-devel-ubuntu22.04

[ue4-docker build] GENERAL SETTINGS
[ue4-docker build] Build targets: build-prerequisites minimal source
[ue4-docker build] Changelist override: (None specified)
[ue4-docker build] Not excluding any Engine components.

Retrieving the Git credentials that will be used to clone the UE4 repo
Username: superyu1337
Access token or password:

[ue4-docker build] Building image "adamrehn/ue4-build-prerequisites:opengl-ubuntu22.04"...
[+] Building 22.1s (5/9)                                                                                docker:default
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 4.10kB                                                                                0.0s
 => WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 2)                                                                                0.0s
 => WARN: InvalidDefaultArgInFrom: Default value for ARG ${BASEIMAGE} results in empty or invalid base image name (line 2)                                                                                0.0s
 => [internal] load metadata for docker.io/nvidia/opengl:1.0-glvnd-devel-ubuntu22.04                                                                                1.3s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [1/6] FROM docker.io/nvidia/opengl:1.0-glvnd-devel-ubuntu22.04@sha256:c030a21588ddb89c245c8a2a24d6e68772cfa5939d312bab19f0833b90e9620a                                                                                16.3s
 => => resolve docker.io/nvidia/opengl:1.0-glvnd-devel-ubuntu22.04@sha256:c030a21588ddb89c245c8a2a24d6e68772cfa5939d312bab19f0833b90e9620a                                                                                0.0s
 => => sha256:1bc677758ad7fa4503417ae5be18809c5a8679b5b36fcd1464d5a8e41cb13305 30.43MB / 30.43MB                                                                                0.9s
 => => sha256:004619d771963a6538b82e9a6f657b6a5286a9ef59a7e88eddc268aeecfc6106 7.25MB / 7.25MB                                                                                0.9s
 => => sha256:cf44605dc541c5b92e23b49f974d95802af2f2da5b35af03846c9603962996a2 186B / 186B                                                                                0.7s
 => => sha256:c030a21588ddb89c245c8a2a24d6e68772cfa5939d312bab19f0833b90e9620a 1.79kB / 1.79kB                                                                                0.0s
 => => sha256:96334240cf5a2a45373deeec7b2f751a66741457b2cf3cf67480fd90b575fe0e 5.28kB / 5.28kB                                                                                0.0s
 => => sha256:df6e1db9485a3e9606c978d735853b66a824aaf7cb57437e92259e1ff9db005c 6.43kB / 6.43kB                                                                                0.9s
 => => sha256:0304682b62bc4f472af25e5e3be7b845d33a889ed17300eb41cae79cc345bec2 131.33MB / 131.33MB                                                                                4.6s
 => => sha256:f9f325c4255e261572a3145bf296593a52b884910ef1426ef2155faafb72b33d 298B / 298B                                                                                1.0s
 => => extracting sha256:1bc677758ad7fa4503417ae5be18809c5a8679b5b36fcd1464d5a8e41cb13305                                                                                1.2s
 => => sha256:5ace3e86e3122c2418e1f757c0e4525181a28b9ad3b8cdca9d1a10091fc62248 16.07MB / 16.07MB                                                                                2.0s
 => => extracting sha256:004619d771963a6538b82e9a6f657b6a5286a9ef59a7e88eddc268aeecfc6106                                                                                1.1s
 => => extracting sha256:cf44605dc541c5b92e23b49f974d95802af2f2da5b35af03846c9603962996a2                                                                                0.0s
 => => extracting sha256:df6e1db9485a3e9606c978d735853b66a824aaf7cb57437e92259e1ff9db005c                                                                                0.0s
 => => extracting sha256:0304682b62bc4f472af25e5e3be7b845d33a889ed17300eb41cae79cc345bec2                                                                                2.2s
 => => extracting sha256:f9f325c4255e261572a3145bf296593a52b884910ef1426ef2155faafb72b33d                                                                                0.0s
 => => extracting sha256:5ace3e86e3122c2418e1f757c0e4525181a28b9ad3b8cdca9d1a10091fc62248                                                                                3.5s
 => ERROR [2/6] RUN apt-get update && apt-get install -y --no-install-recommends   build-essential   ca-certificates   curl   git   git-lfs   gpg-agent   python3   python3-dev   python3-pip   shared-mime-info   software-propertie  4.3s
------
 > [2/6] RUN apt-get update && apt-get install -y --no-install-recommends               build-essential                 ca-certificates                 curl            git             git-lfs                 gpg-agent               python3             python3-dev             python3-pip             shared-mime-info                software-properties-common              sudo            tzdata          unzip           xdg-user-dirs           xdg-utils               zip &&      rm -rf /var/lib/apt/lists/* && echo '' && echo 'RUN directive complete. Docker will now commit the filesystem layer to disk.' && echo 'Note that for large filesystem layers this can take quite some time.' && echo 'Performing filesystem layer commit...' && echo '':
3.685 Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
3.688 Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
3.837 Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
3.865 Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB]
3.905 Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
3.905   At least one invalid signature was encountered.
4.078 Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
4.078   At least one invalid signature was encountered.
4.182 Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
4.182   At least one invalid signature was encountered.
4.295 Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
4.295   At least one invalid signature was encountered.
4.299 Reading package lists...
4.314 W: GPG error: http://security.ubuntu.com/ubuntu jammy-security InRelease: At least one invalid signature was encountered.
4.314 E: The repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
4.314 W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: At least one invalid signature was encountered.
4.314 E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
4.314 W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: At least one invalid signature was encountered.
4.314 E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
4.314 W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: At least one invalid signature was encountered.
4.314 E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
------
Dockerfile:23
--------------------
  22 |     # Install our build prerequisites
  23 | >>> RUN apt-get update && apt-get install -y --no-install-recommends \
  24 | >>>              build-essential \
  25 | >>>              ca-certificates \
  26 | >>>              curl \
  27 | >>>              git \
  28 | >>>              git-lfs \
  29 | >>>              gpg-agent \
  30 | >>>              python3 \
  31 | >>>              python3-dev \
  32 | >>>              python3-pip \
  33 | >>>              shared-mime-info \
  34 | >>>              software-properties-common \
  35 | >>>              sudo \
  36 | >>>              tzdata \
  37 | >>>              unzip \
  38 | >>>              xdg-user-dirs \
  39 | >>>              xdg-utils \
  40 | >>>              zip && \
  41 | >>>      rm -rf /var/lib/apt/lists/* && echo '' && echo 'RUN directive complete. Docker will now commit the filesystem layer to disk.' && echo 'Note that for large filesystem layers this can take quite some time.' && echo 'Performing filesystem layer commit...' && echo ''
  42 |
--------------------
ERROR: failed to solve: process "/bin/sh -c apt-get update && apt-get install -y --no-install-recommends \t\tbuild-essential \t\tca-certificates \t\tcurl \t\tgit \t\tgit-lfs \t\tgpg-agent \t\tpython3 \t\tpython3-dev \t\tpython3-pip \t\tshared-mime-info \t\tsoftware-properties-common \t\tsudo \t\ttzdata \t\tunzip \t\txdg-user-dirs \t\txdg-utils \t\tzip && \trm -rf /var/lib/apt/lists/* && echo '' && echo 'RUN directive complete. Docker will now commit the filesystem layer to disk.' && echo 'Note that for large filesystem layers this can take quite some time.' && echo 'Performing filesystem layer commit...' && echo ''" did not complete successfully: exit code: 100
[ue4-docker build] Error: failed to build image "adamrehn/ue4-build-prerequisites:opengl-ubuntu22.04".

Trying to build images keeps failing at the prerequisites. Could be related to #329, not sure.
Line that fails specifically seems to be this one.
I'm running on archlinux 6.11.4-zen2-1-zen, installed using pipx install ue4-docker.

It doesn't look related to #329, it looks like the APT signatures are failing for some reason. It was working in March (seen in https://github.com/adamrehn/ue4-docker/issues/353#issue-2208665244) and the relevant files don't appear to have changed since 2022, and there's definitely a signature at the end of http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease so I don't immediately know what's going on here.
That said, this is over http, not https, so I wonder if there's some kind of intervening transparent proxy that is modifying the file in-flight?
What if you try running the official ubuntu:22.04 image from Docker Hub and apt-get update in that, does it work? If not, then something in your network environment is corrupting something on the wire, either the package update or the original image.
If ubuntu:22.04 works, then try running the nvidia/opengl:1.0-glvnd-devel-ubuntu22.04 image from Docker Hub and see if apt-get update in that works.
If the ubuntu image works but not the nvidia/opengl image, then something has changed in Ubuntu's infrastructure, e.g. old keys have expired and new keys added; the nvidia/opengl image hasn't been changed since May 2023, but the ubuntu image is being kept up-to-date. I don't think this is the case, because the files in question haven't changed since 2022, so could not have been resigned.
And just a quick sanity check: Is the system clock correct on your host?

And just a quick sanity check: Is the system clock correct on your host?
Actually this could be it, I was SSHing into my home machine from work through a vpn. And I run a windows dual boot at home which could mess with the system clock I guess.
I'll be home soon and test. I'll also try updating the base ubuntu:22.04 image.

I've just retested, ue4-docker build --target=build-prerequisites builds properly on Linux

Issue seems to be related to my home machine for sure. On my office PC I'm able to run apt-get update fine, but not on my home PC. I'll investigate further when I'm home.

I had my docker data set to an NTFS partition due to space constaints, im running docker on the default storage location now and ubuntu:22.04 is updating fine now... interesting.

I'm guessing your setup is something like https://github.com/moby/moby/issues/25328 which I suspect is not well (or at all) supported; either way, not something we can do anything about in ue4-docker.


Global VS Code settings

Could we have a global VS Code config file for sasjs lint ?

A global settings file is a good idea.  Perhaps for the CLI it could be in the home directory (.sasjs/.sasjslint ), and for the extension, in the extension settings.
Currently it is necessary to have the .sasjslint in the root of the VS Code project, which isn't always convenient.


Docs: missing ] character in database->aggregate documentation

Bug Report
Hi 👋 ,
Was going through the documentation for the MongoDB PHP Library and came across this example,
which seems to result in a syntax error when taken verbatim due to a missing ] character.
If so, it looks like this is the corresponding block of code/text that needs to be updated.
Let me know if this is the incorrect place/avenue to report this.
Thanks!
Environment
n/a
Test Script
n/a
Expected and Actual Behavior
n/a
Debug Log
n/a

Thanks for reporting this, I've created #1285 to fix the issue.


Tailwind is not purging in production

Getting following message when running npm run prod
������  Tailwind is not purging unused styles because no template paths have been provided.
If you have manually configured PurgeCSS outside of Tailwind or are deliberately not
removing unused styles, set purge: false in your Tailwind config file to silence
this warning.
what do I need to do to set the paths?

Hi @Hitchhooker,
Thanks for your note. I think it actually is purging, despite the messages- just compare the size in dev and prod builds.
I'll see what causes it over the next couple of days.

using purge through tailwind.config.js got rid of the warning but as you said, it did purge regardless of those warnings.
purge: [
'./pathto//*.htm',
'./pathto//.css',
'./pathto/**/.js',
],

Resolved with release 1.0.1 - removed purgeCSS config from laravel mix manifest, switched to TailwindCSS' internal support for purgeCSS


Add Randoop and the Checker Framework

ℹ Repository information
The repository has:

[x] At least three issues with the good first issue label.
[x] At least 10 contributors.
[x] Detailed setup instructions for the project.
[x] CONTRIBUTING.md
[x] Actively maintained.

@ping Can this pull request be reviewed?  I don't understand the Vercel deployment failure, but I see it has occurred on previously-merged commits such as https://github.com/deepsourcelabs/good-first-issue/commit/68d4fcb1d99edf02afd528d20cf5ac6bc146fb95 .  Thanks!

Hey @mernst  ! I tried to contribute to this repo as well but I haven't seen any activity in the last few months. I decided to fork it to keep it alive. Please see https://github.com/lucavallin/gfi and feel free to open a pull request there. At this time I am setting up the hosting and cleaning up the code. If you're up for it, I could use some help to convert the app from Nuxt.js & Python to Next.js & Typescript.


Only allow services defined in the catalog to be instantiated

We would like the ability to restrict the services available to run on Rancher to those defined within the catalog only. This allows us to gate what ends up being spun up on our internal network and assures us that only approved services can be started.

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


[Bug]: Repo picker does not show all org repos

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
The "Open Github Repo" repo picker does not show all repos in an organization, it seems to only show the first 30 in alphabetical order. This seems to be a problem with pagination.
We should write tests to confirm the issue and fix it.
OpenHands Installation
app.all-hands.dev
OpenHands Version
No response
Operating System
None
Logs, Errors, Screenshots, and Additional Context
No response

OpenHands started fixing the issue! You can monitor the progress here.

An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-5683' has been created with the attempted changes. You can view the branch here. Manual intervention may be required.

Took a quick look at the current draft PR, I think it's a little off in resolving this issue
I think it may be something to do with extractNextPageFromLink, as the next page parameter might be returned in a different format from the backend
I'll investigate this further

Cool, thanks!

Adding critical severity as pagination is not working. All users can only see first page of repos when paginating

Fixed in main. Waiting for release.

Fixed now in 0.16.1. @neubig can you triple check this please.