Can't download from sohu

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 reporting that yt-dlp is broken on a supported site
[X] I've verified that I'm running yt-dlp version 2023.06.22 (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 checked that all URLs and arguments with special characters are properly quoted or escaped
[X] 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
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
China
Provide a description that is worded well enough to be understood
Can't download videos from sohu. Use URL https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html
Provide verbose output that clearly demonstrates the problem

[X] 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
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
yt-dlp -vU -F "https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html"
[debug] Command-line config: ['-vU', '-F', 'https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html']
[debug] Encodings: locale cp936, fs utf-8, pref cp936, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[812cdfa06] (pip)
[debug] Lazy loading extractors is disabled
[debug] Python 3.10.9 (CPython AMD64 64bit) - Windows-10-10.0.22621-SP0 (OpenSSL 1.1.1t  7 Feb 2023)
[debug] exe versions: ffmpeg N-110972-gbaa9fccf8d-20230601 (setts), ffprobe N-110972-gbaa9fccf8d-20230601, phantomjs 2.1.1
[debug] Optional libraries: Cryptodome-3.18.0, brotli-None, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:1080', 'https': 'http://<IP_ADDRESS>:1080', 'ftp': 'http://<IP_ADDRESS>:1080'}
[debug] Loaded 1851 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>yt-dlp is up to date<EMAIL_ADDRESS>[generic] Extracting URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html
[generic] MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html
Traceback (most recent call last):
  File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\YoutubeDL.py", line 1555, in wrapper
    return func(self, *args, **kwargs)
  File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\YoutubeDL.py", line 1631, in __extract_info
    ie_result = ie.extract(url)
  File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\extractor\common.py", line 708, in extract
    ie_result = self._real_extract(url)
  File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\extractor\generic.py", line 2568, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html

Looks like that's a new type of URL.
A patch like this should handle it:
diff --git a/yt_dlp/extractor/sohu.py b/yt_dlp/extractor/sohu.py
index a8f1e4623..5f0fb6192 100644
--- a/yt_dlp/extractor/sohu.py
+++ b/yt_dlp/extractor/sohu.py
@@ -1,3 +1,4 @@
+import base64
 import re

 from .common import InfoExtractor
@@ -9,6 +10,7 @@
     ExtractorError,
     int_or_none,
     try_get,
+    urljoin,
 )

@@ -196,3 +198,12 @@ def _fetch_data(vid_id, mytv=False):
             }

         return info
+
+
+class SohuVIE(InfoExtractor):
+    _VALID_URL = r'(?P<base>https?://tv\.sohu\.com/)v/(?P<id>[\w=-]+)\.html'
+
+    def _real_extract(self, url):
+        base_url, encoded_id = self._match_valid_url(url).group('base', 'id')
+        path = base64.urlsafe_b64decode(encoded_id).decode()
+        return self.url_result(urljoin(base_url, path), SohuIE)

I'm geo-blocked, but it should work for someone who's not:
$ yt-dlp -F "https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html"
[SohuV] Extracting URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html
[Sohu] Extracting URL: https://tv.sohu.com/20230614/n601315192.shtml
[Sohu] 601315192: Downloading webpage
[Sohu] 601315192: Downloading JSON data for 8484094
ERROR: [Sohu] 601315192: Sohu said: The video is only licensed to users in Mainland China.
You might want to use a VPN or a proxy server (with --proxy) to workaround.

I think someone just needs to find out if there are my.tv.sohu.com links like this, too, and we could match them if so

Looks like that's a new type of URL.
A patch like this should handle it:
diff --git a/yt_dlp/extractor/sohu.py b/yt_dlp/extractor/sohu.py
index a8f1e4623..5f0fb6192 100644
--- a/yt_dlp/extractor/sohu.py
+++ b/yt_dlp/extractor/sohu.py
@@ -1,3 +1,4 @@
+import base64
 import re

 from .common import InfoExtractor
@@ -9,6 +10,7 @@
     ExtractorError,
     int_or_none,
     try_get,
+    urljoin,
 )

@@ -196,3 +198,12 @@ def _fetch_data(vid_id, mytv=False):
             }

         return info
+
+
+class SohuVIE(InfoExtractor):
+    _VALID_URL = r'(?P<base>https?://tv\.sohu\.com/)v/(?P<id>[\w=-]+)\.html(?:$|[#?])'
+
+    def _real_extract(self, url):
+        base_url, encoded_id = self._match_valid_url(url).group('base', 'id')
+        path = base64.urlsafe_b64decode(encoded_id).decode()
+        return self.url_result(urljoin(base_url, path), SohuIE)

I'm geo-blocked, but it should work for someone who's not:
$ yt-dlp -F "https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html"
[SohuV] Extracting URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html
[Sohu] Extracting URL: https://tv.sohu.com/20230614/n601315192.shtml
[Sohu] 601315192: Downloading webpage
[Sohu] 601315192: Downloading JSON data for 8484094
ERROR: [Sohu] 601315192: Sohu said: The video is only licensed to users in Mainland China.
You might want to use a VPN or a proxy server (with --proxy) to workaround.

I think someone just needs to find out if there are my.tv.sohu.com links like this, too, and we could match them if so

Thankyou!!!! But it seems like it has other issues.
yt-dlp -vU -F "https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html" [debug] Command-line config: ['-vU', '-F', 'https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html'] [debug] Encodings: locale cp936, fs utf-8, pref cp936, out utf-8, error utf-8, screen utf-8 [debug] yt-dlp version<EMAIL_ADDRESS>[812cdfa06] (pip) [debug] Lazy loading extractors is disabled [debug] Python 3.10.9 (CPython AMD64 64bit) - Windows-10-10.0.22621-SP0 (OpenSSL 1.1.1t  7 Feb 2023) [debug] exe versions: ffmpeg N-110972-gbaa9fccf8d-20230601 (setts), ffprobe N-110972-gbaa9fccf8d-20230601, phantomjs 2.1.1 [debug] Optional libraries: Cryptodome-3.18.0, brotli-None, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3 [debug] Proxy map: {} [debug] Loaded 1851 extractors [debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>yt-dlp is up to date<EMAIL_ADDRESS>[generic] Extracting URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html [generic] MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==: Downloading webpage WARNING: [generic] Falling back on generic information extractor [generic] MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==: Extracting information [debug] Looking for embeds ERROR: Unsupported URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html Traceback (most recent call last):   File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\YoutubeDL.py", line 1555, in wrapper     return func(self, *args, **kwargs)   File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\YoutubeDL.py", line 1631, in __extract_info     ie_result = ie.extract(url)   File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\extractor\common.py", line 708, in extract     ie_result = self._real_extract(url)   File "C:\python_conda_package\Anaconda3\lib\site-packages\yt_dlp\extractor\generic.py", line 2568, in _real_extract     raise UnsupportedError(url) yt_dlp.utils.UnsupportedError: Unsupported URL: https://tv.sohu.com/v/MjAyMzA2MTQvbjYwMTMxNTE5Mi5zaHRtbA==.html

@Thalia500 I've applied the patch by bashonly to this branch (New IE class needs to be imported in _extractors.py). You can take a look at this:
https://github.com/c-basalt/yt-dlp/tree/sohu-fix
I checked some old my.tv.sohu.com links in test cases and they are redirected as well, though the redirected domain is also tv.sohu.com.
The Multipart video link in the test case appears to be broken. Might want to fix that before starting a PR.

Duplicate of #1667 (thanks for finding that @c-basalt)


insert a column to an empty dataframe gets "Length of values does not match length of index" error

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Modin installed from (source or binary): binary
Modin version: 0.2.5
Python version: 3.6.4
Exact command to reproduce: snippet below

Describe the problem
Dataframe().insert fails with "Length of values does not match length of index" when trying to insert a column to an empty dataframe. A reindex of the axis should probably be done according to the new column in case the dataframe does not have an index yet
Source code / logs
# works

import pandas as pd

df = pd.DataFrame()
df['x'] = [1, 2, 3]
print(df)

# does not work

import modin.pandas as pd

df = pd.DataFrame()
df['x'] = [1, 2, 3]
print(df)

The ValueError: Length of values does not match length of index raised because the previous columns you have added in the DataFrame are not the same length as the most recent one you have attempted to add in the DataFrame. So, you need make sure that the length of the array you are assign to a new column is equal to the length of the dataframe .
The simple solution is that you first convert the list/array to a pandas Series , and then when you do assignment, missing index in the Series will be filled with NaN values .


Reduce Infinispan timeouts

remote-timeout set to 5 seconds
lock acquire-timeout set to 4 seconds
cross-site timeout set to 4.5 seconds

I'd like to record the "why" so that my future self know why this has been changed. From our previous chat I recall: The retry mechanism in Keycloak have an incremental back-off parameterized starting with 10 milliseconds and 10 retried, which results in a maximum wait time of 10230 ms.
I also recall that you added some debug statements when analyzing this. Feel free to create a PR to add those on the trace or debug level as well to help future investigations.
Please add anything I have missed. I will merge it in a second.


Enhancement Proposal Model

From discussion in issue ( https://github.com/zarr-developers/zarr/issues/291 ), there was interest in an Enhancement Proposal model. Would be good to discuss here how we make proposals, decide on proposals, track history, etc.

This also has a (positive) overlap with community/governance.

I assume this is covered by the ZEP (Zarr Enhancement Proposal) as described in ZEP 0. Please feel free to re-open if this misses the point.


Support message overrides properly

Waiting on https://github.com/PartMan7/PS-Client/issues/14

Partially done in pm-to-room spoofs; need a more-consistent way


nixos/nftables: extend check redirects

Description of changes
The checkPhase script that runs nft --check uses libredirect to link
/etc/services and /etc/protocols inside the sandbox. The problem is that it
resets NIX_REDIRECTS after running the user-provided preCheckRuleset, so
it's not possible to add more redirects.
This adds the generated /etc/hosts as well, needed to resolve static hostnames,
and a :$NIX_REDIRECTS to make this extensible.
Things done

Tested via:

[x] nixosTests.nat.nftables
[x] nixosTests.firewall

[x] Checked the manual with nix build -f nixos/release.nix manual.x86_64-linux
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Btw, if you want to do this now, here's a hack to work around the limitation:
export(){
  command export "$1:/etc/hosts=${config.environment.etc.hosts.source}"
}

related https://github.com/NixOS/nixpkgs/pull/241680

if i understand it compared to https://github.com/NixOS/nixpkgs/pull/241680 this allows users to reference paths from the current machine. this doesn't really make sense to me as this build might be building the configuration for another machine that has nothing to do with this one.
when would we want this?

No, it's really the same thing: yes, can try to reference any path on the machine, but they won't work because of the sandbox (even if build==host). The paths essentially must be in the store.
The only difference is that in the other PR you have a proper option to define more links, here you do that with a piece of shell script in preCheckRuleset.

ok. in that case i prefer the option, as that can be part of the machine config while in this case it's basically an impure input.

The rational for not having a dedicated option is that probably no one will ever need to add more links, but you never now.
I'm closing in favour of the other PR.


Add Human Activities Table

[ ] Create a table for the human activities section of the report with threats for rows and activities as columns:

eg.                       Lobster Fishing   |   Waste  |  Power
Noise                 |
Entanglement    |
Pollution            |

[ ] Look into table with stressors/ threats as rows and species observations as columns?
[x] Group stressors by sections: rivers, offshore, coastal
[ ] Look into NOAA / NASA data layers

Sample table:

List data columns not in found in search area in column header.  Avoid silent omission.


jshint error for 'describe/it not defined' on generated helper tests

When generating a new helper the associated test does not run due to globals 'describe' and 'it' not being defined.
Generated
/* jshint expr:true */
import {
  aHelper
} from 'hub/helpers/a-helper';

describe('AHelperHelper', function() {
  // Replace this with your real tests.
  it('works', function() {
    var result = aHelper(42);
    expect(result).to.be.ok;
  });
});

Results in:
unit/helpers/a-helper-test.js: line 6, col 1, 'describe' is not defined.
unit/helpers/a-helper-test.js: line 8, col 3, 'it' is not defined.

solution....sort of
I manually added 'describe' and 'it' to tests/.jshintrc after looking at #3
Is there another way of doing this or am I hooking things up wrong somewhere else?

:+1: Would appreciate the correct path to import 'describe' from. The generators here don't specify one.

I just added describe & it inside tests/.jshintrc and it seems to have solved it for now.
I can generate helper helper-name without the generated tests tripping JSHint now.
tests/.jshintrc
{
  ⋮
  "predef": [
    ⋮
    "describe",
    "it"
    ⋮
  ],
  ⋮
}

Ember-cli 0.1.13 update is trying to move away from any global like this: http://reefpoints.dockyard.com/2015/02/06/ember-qunit-0-2.html
https://github.com/ember-cli/ember-cli/releases/tag/v0.1.13

I think this should be handled up stream, and created an issue in ember-mocha for it: https://github.com/switchfly/ember-mocha/issues/22

@rwjblue good call, thanks for raising.
Is it worth raising about exposing assert, should and expects from chai.js too?

Is it worth raising about exposing assert, should and expects from chai.js too?

Not sure, I'm not a heavy ember-mocha user, I was mostly trying to help point @dgeb and others towards a possible solution (that we pulled into ember-qunit).

Thanks @rwjblue
@jonathanKingston @DisruptiveMind et al - PRs welcome over in ember-mocha as spec'd out in https://github.com/switchfly/ember-mocha/issues/22

Is it worth raising about exposing assert, should and expects from chai.js too?

Seems like an additional top-level chai module would be most appropriate.

@dgeb I'll make a PR for the describe at some point soonish unless someone else gets to it first.
I made a quick chai package to expose the main interfaces to chai. This might be a better fragmentation from just having ember-cli module define the use of Chai too: https://github.com/jonathanKingston/ember-cli-chai

Submitted https://github.com/switchfly/ember-mocha/pull/23 to add the shims, this repo will still need to be updated (mostly blueprints I think) once that lands.

I've just added the import statements for the helpers blueprint in disruptivemind/ember-cli-mocha@afe57116b35d5659efde57aff8b3d98ac7f1e841. I'm holding off the PR for now.
Just wondering, should expect be imported as well?

@DisruptiveMind I was thinking about this the other day, would it make more sense to have ember-cli-mocha more configurable so that any assertion library can be used. The addon could take a config argument for example, which would then modify the helpers accordingly.
So something like: config/environment.js:
ENV['ember-cli-mocha'] = {
  assertion: 'chai.assert' // Valid values: 'chai.assert', 'chai.should', 'chai.expects', 'qunit'
}

Would generate:
/* jshint expr:true */
 import {
  describe,
  it
} from 'ember-mocha';

import {
  assert
} from 'chai';

This might be something that can be made generic enough to be usable from ember-cli-qunit too.
What do you think @rwjblue.

@jonathanKingston :+1: on configurable options

Please upgrade to ember-cli-mocha 0.5.0 and then run ember g ember-cli-mocha to get the latest ember-mocha.
ember-mocha now exports shimmed mocha and chai modules.
Note that only expect and assert are exported from chai for now. should requires injections which most developers will want to avoid (perhaps we can figure out how to better support should at some point).
I've also updated the blueprints to use these new shims. I like the idea in theory of making these blueprints more flexible as you've described above, as long as we can do so without too much noise in the blueprints. If you want to pursue an approach, please open a new issue / PR.

@dgeb :+1:
Does doing the following with 'should' not work as expected:
  import should from 'ember-mocha';
  should();

  thing.should...

As far as I was aware exporting the should method then using this within a module scope should have a self contained impact.

@jonathanKingston - I am not an expert on chai but it seems that should actually adds a bunch of methods to the core object prototype which means using it anywhere would affect all the rest of the tests.

https://github.com/chaijs/chai/blob/master/chai.js#L3782-L3786

But I do agree that the chai shim should export should, and the actual assertion lib/mechanism is completely independent (as it should be).

@rwjblue yeah it does, I guess I just assumed ES6 modules completely isolated their code even for native prototypes (It hasn't been something I had tried before because of it's edge usecase - however would certainly help if that was the expected behaviour and Babel just needed to implement).

@jonathanKingston - I'm pretty sure that ES6 does not suggest that modifications to core prototypes are isolated within each module (and if it did, I highly doubt that it could be polyfilled via babel).

Yeah, once should is invoked, its core object injections could affect other tests - even those that don't use should. I guess I see should as a footgun (i.e. anti-pattern), especially when presented alongside expect and assert as equivalents. I really am on the fence about exposing it from the chai shim - but I'd be willing to do so if there's sufficient demand.

I guess I see should as a footgun (i.e. anti-pattern), especially when presented alongside expect and assert as equivalents.

This is exactly why I left it out of my initial chai shim PR.  I think if you really really want to use should syntax you can figure it out on you own.  I would personally rather steer folks towards the right way...

And, I still haven't heard anyone say they wanted to use should syntax: unless I am mis-reading @jonathanKingston's comment he was mostly advocating for it to be pluggable (which it is already).

And, I still haven't heard anyone say they wanted to use should syntax

@rwjblue oh, I almost forgot about #14. Let me comment there.

@rwjblue yes I am advocating for it to be pluggable (I was just trying to ascertain if it would be isolated).

From my quick scrambling through the ES6 spec (I'm probably not reading this right).
Object Environment Records

Immutable bindings do not exist for object environment records.

So no help there, however I believe that is just describing normal behaviour of scripts.

Well known intrinsic objects

Unless otherwise specified each intrinsic object actually corresponds to a set of similar objects, one per Realm.

 Conceptually, a realm consists of a set of intrinsic objects, an ECMAScript global environment

Module evaluation

Set the Realm of moduleCxt to module.[[Realm]].

My reading of that is Object is considered an Intrinsic object which is related to the Realm it is in, Modules appear to run in their own Realm. Creating a new Real appears to reinstantiate new Intrinsics.
I could be wrong in how that is supposed to be read, however if that is the case Babel could be updated with this behaviour.
@dgeb I was just about to quote #14 :+1:

Also:
Crossing realms with symbols

The problem is that each realm has its own local copy of Array and, because objects have individual identities, those local copies are considered different

So I will double check this issue exists in Babel, if it does then hopefully that can be fixed there to isolate the prototypes.


Integration Test: Append Transaction Entries and Read on Another Server

Why
We need to ensure the integrity and correctness of the transaction entries across multiple servers in a distributed system. By appending transaction entries on one server and reading them on another, we can verify the consistency and reliability of our consensus and mining mechanisms.
How

Setup Two Servers: Initialize two servers in the test environment. Server A will be used to append transaction entries, and Server B will be used to read the appended entries.

Append Transaction Entries: On Server A, create and append a set of transaction entries using the existing append mechanism.

Synchronization: Ensure the synchronization between Server A and Server B using the consensus protocol. This involves making sure that Server B receives and processes the entries appended on Server A.

Read Transaction Entries: On Server B, read the transaction entries that were appended on Server A. Use both the mined data and consensus data to verify the integrity and correctness of the entries.

Assertions: Verify that the transaction entries read on Server B match exactly with those appended on Server A. Include checks for the data integrity and consistency.

Automate the Test: Ensure that this integration test is automated and can be run as part of the CI/CD pipeline.

We've shelved raft for now, closing.


Istio-proxy readiness probe failure when k8s cross AWS account and logs stuck after trust anchor

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Our k8s has cross AWS account(VPC) worker nodes. The cross account worker node can start up pod and service correctly except pod with istio-sidecar proxy. When we try to start up the pod with istio-proxy, the istio-proxy will be stuck and the readiness probe will be failed (endpoint will not connect). This issue is never happening in the pod which deploy on the worker in same AWS account(VPC). When we check the starting logs of the istio-proxy, following failure is found:
2024-09-10T12:08:39.427311Z     info    FLAG: --concurrency="2"
2024-09-10T12:08:39.427336Z     info    FLAG: --domain="taichi-prj-ko1g2veg.svc.cluster.local"
2024-09-10T12:08:39.427342Z     info    FLAG: --help="false"
2024-09-10T12:08:39.427344Z     info    FLAG: --log_as_json="false"
2024-09-10T12:08:39.427347Z     info    FLAG: --log_caller=""
2024-09-10T12:08:39.427349Z     info    FLAG: --log_output_level="default:info"
2024-09-10T12:08:39.427352Z     info    FLAG: --log_rotate=""
2024-09-10T12:08:39.427354Z     info    FLAG: --log_rotate_max_age="30"
2024-09-10T12:08:39.427357Z     info    FLAG: --log_rotate_max_backups="1000"
2024-09-10T12:08:39.427359Z     info    FLAG: --log_rotate_max_size="104857600"
2024-09-10T12:08:39.427362Z     info    FLAG: --log_stacktrace_level="default:none"
2024-09-10T12:08:39.427379Z     info    FLAG: --log_target="[stdout]"
2024-09-10T12:08:39.427387Z     info    FLAG: --meshConfig="./etc/istio/config/mesh"
2024-09-10T12:08:39.427390Z     info    FLAG: --outlierLogPath=""
2024-09-10T12:08:39.427393Z     info    FLAG: --proxyComponentLogLevel="misc:error"
2024-09-10T12:08:39.427397Z     info    FLAG: --proxyLogLevel="warning"
2024-09-10T12:08:39.427401Z     info    FLAG: --serviceCluster="istio-proxy"
2024-09-10T12:08:39.427404Z     info    FLAG: --stsPort="0"
2024-09-10T12:08:39.427408Z     info    FLAG: --templateFile=""
2024-09-10T12:08:39.427412Z     info    FLAG: --tokenManagerPlugin="GoogleTokenExchange"
2024-09-10T12:08:39.427422Z     info    FLAG: --vklog="0"
2024-09-10T12:08:39.427429Z     info    Version 1.16.0-8f2e2dc5d57f6f1f7a453e03ec96ca72b2205783-Clean
2024-09-10T12:08:39.521342Z     info    Maximum file descriptors (ulimit -n):<PHONE_NUMBER>
2024-09-10T12:08:39.521536Z     info    Proxy role      ips=[<IP_ADDRESS>] type=sidecar id=taichi-notebook-pyvwev37-0.taichi-prj-ko1g2veg domain=taichi-prj-ko1g2veg.svc.cluster.local
2024-09-10T12:08:39.521676Z     info    Apply proxy config from env {}

2024-09-10T12:08:39.523577Z     info    Effective config: binaryPath: /usr/local/bin/envoy
concurrency: 2
configPath: ./etc/istio/proxy
controlPlaneAuthPolicy: MUTUAL_TLS
discoveryAddress: istiod.istio-system.svc:15012
drainDuration: 45s
parentShutdownDuration: 60s
proxyAdminPort: 15000
serviceCluster: istio-proxy
statNameLength: 189
statusPort: 15020
terminationDrainDuration: 5s
tracing:
  zipkin:
    address: zipkin.istio-system:9411

2024-09-10T12:08:39.523598Z     info    JWT policy is third-party-jwt
2024-09-10T12:08:39.523602Z     info    using credential fetcher of JWT type in cluster.local trust domain
2024-09-10T12:08:39.524969Z     info    Workload SDS socket not found. Starting Istio SDS Server
2024-09-10T12:08:39.524989Z     info    CA Endpoint istiod.istio-system.svc:15012, provider Citadel
2024-09-10T12:08:39.525028Z     info    Using CA istiod.istio-system.svc:15012 cert with certs: var/run/secrets/istio/root-cert.pem
2024-09-10T12:08:39.525102Z     info    citadelclient   Citadel client using custom root cert: var/run/secrets/istio/root-cert.pem
2024-09-10T12:08:39.621256Z     info    Opening status port 15020
2024-09-10T12:08:39.923078Z     info    ads     All caches have been synced up in 498.271769ms, marking server ready
2024-09-10T12:08:39.923528Z     info    xdsproxy        Initializing with upstream address "istiod.istio-system.svc:15012" and cluster "Kubernetes"
2024-09-10T12:08:39.923602Z     info    sds     Starting SDS grpc server
2024-09-10T12:08:39.924088Z     info    starting Http service at <IP_ADDRESS>:15004
2024-09-10T12:08:39.925931Z     info    Pilot SAN: [istiod.istio-system.svc]
2024-09-10T12:08:39.927435Z     info    Starting proxy agent
2024-09-10T12:08:39.927458Z     info    starting
2024-09-10T12:08:39.927499Z     info    Envoy command: [-c etc/istio/proxy/envoy-rev.json --drain-time-s 45 --drain-strategy immediate --parent-shutdown-time-s 60 --local-address-ip-version v4 --file-flush-interval-msec 1000 --disable-hot-restart --log-format %Y-%m-%dT%T.%fZ        %l      envoy %n        %v -l warning --component-log-level misc:error --concurrency 2]
2024-09-10T12:08:41.821377Z     info    xdsproxy        connected to upstream XDS server: istiod.istio-system.svc:15012
2024-09-10T12:08:42.136692Z     info    cache   generated new workload certificate      latency=2.213249652s ttl=23h59m59.863318089s
2024-09-10T12:08:42.136722Z     info    cache   Root cert has changed, start rotating root cert
2024-09-10T12:08:42.136740Z     info    ads     XDS: Incremental Pushing:0 ConnectedEndpoints:0 Version:
2024-09-10T12:08:42.136790Z     info    cache   returned workload trust anchor from cache       ttl=23h59m59.863212464s
**2024-09-10T12:09:21.831399Z     warn    xdsproxy        upstream [1] terminated with unexpected error rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout**
2024-09-10T12:09:22.289640Z     info    xdsproxy        connected to upstream XDS server: istiod.istio-system.svc:15012
**2024-09-10T12:09:32.361335Z     warn    xdsproxy        upstream [2] terminated with unexpected error rpc error: code = Unavailable desc = error reading from server: readtcp <IP_ADDRESS>:60696-><IP_ADDRESS>:15012: read: connection timed out**

By the information provided by the logs, seems the connection to the istiod service is work properly, but some service is failed at TCP keepalive handshake procedure
And we try to find any useful information from istiod, there is any error returned, but only the terminate info:
2024-09-11T01:04:47.895841Z     info    ads     ADS: "<IP_ADDRESS>:46496"  terminated
2024-09-11T01:05:36.535990Z     info    ads     ADS: "<IP_ADDRESS>:35166"  terminated
2024-09-11T01:06:52.058140Z     info    ads     ADS: "<IP_ADDRESS>:58580"  terminated

Version
$ istioctl version
Istio is not present in the cluster: no running Istio pods in namespace "istio-system"
client version: 1.23.1
$ kubectl version
Client Version: v1.28.6
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.6
$ kubectl get po -n istio-system
NAME                                     READY   STATUS    RESTARTS   AGE
istiod-554c7bf657-8gc89                  1/1     Running   0          12h
istiod-554c7bf657-mxcdz                  1/1     Running   0          12h
$ kubectl describe po istiod-554c7bf657-8gc89 -n istio-system | grep -i image
Image:         artifact.roche.com.cn/common-dockerhub-docker-r/istio/pilot:1.16.0
Image ID:      artifact.roche.com.cn/common-dockerhub-docker-r/istio/pilot@sha256:ac0284d75ec9e6a73acaeb787881779ed27342c10fa5589d873dd30790a57868
$ kubectl describe po <ISTIO_INGRESS_GATEWAY> -n istio-system | grep -i image
Image:         artifact.roche.com.cn/common-dockerhub-docker-r/istio/proxyv2:1.16.0
Image ID:      artifact.roche.com.cn/common-dockerhub-docker-r/istio/proxyv2@sha256:f6f97fa4fb77a3cbe1e3eca0fa46bd462ad6b284c129cf57bf91575c4fb50cf9

Additional Information
No response

And as a part of debug process, we use flannel as our cni and we check the node status and flannel pod and the flannel/cni information in worker, all the items work properly

this seems like we are blocked from reaching Istiod. This isn't going through any fancy Istio networking, so really the only root cause that is plausible is your k8s networkijg setup has an issue. Istio depends on the core network to work

@howardjohn Hello John. Thank you for your reply. If you check the logs, the proxy/istiod are actual connected. From intermittent operation it fails. We try to check all traffic rule on the Firewall and security group, there is no any blocking record

Hi John：     We‘ve solved the issue. The issue is caused by the MTU limit mismatch in the whole network chain, by limiting the CNI MTU, the package loss issue is fixed, you may close the ticket and thank you very much for your kind support发自我的 iPhone在 2024年9月11日，23:09，John Howard @.***> 写道：
It maybe not be a completely broken network but intermittent issues. This is incredibly basic TCP connection between two pods, there is nothing Istio specific that can cause this. Note none of this traffic goes through Istio's proxy, etc.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Fix jwt not active error by adding a small clock tolerence

WHY are these changes introduced?
Fixes #207

auth0/node-jsonwebtoken supports a clockTolerance option for small differences between machines on the internet. There are multiple users complaining about running into jwt not active errors.
WHAT is this pull request doing?
Uses the clockTolerance option from auth0/node-jsonwebtoken. Sets it at a respectable 5 seconds. All my issues where small differences from 4 seconds to 2 seconds.

Type of change

[x] Patch: Bug (non-breaking change which fixes an issue)
[ ] Minor: New feature (non-breaking change which adds functionality)
[ ] Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above
[x] I have added/updated tests for this change
[x] I have documented new APIs/updated the documentation for modified APIs (for public APIs)

Any updates on this? This seems a blocker to move to latest shopify pkgs.
"@shopify/app-bridge-react": "^2.0.3",
        "@shopify/app-bridge-utils": "^2.0.3",
        "@shopify/koa-shopify-auth": "^4.1.4",
        "@shopify/koa-shopify-graphql-proxy": "^5.0.2",
        "@shopify/koa-shopify-webhooks": "^3.0.2",
        "@shopify/react-shopify-app-route-propagator": "^3.0.8",
        "@shopify/polaris": "^6.6.0",
        "@shopify/polaris-icons": "^4.6.2",
        "@shopify/shopify-api": "^1.4.1",

Any updates on this? This seems a blocker to move to latest shopify pkgs.
"@shopify/app-bridge-react": "^2.0.3",
        "@shopify/app-bridge-utils": "^2.0.3",
        "@shopify/koa-shopify-auth": "^4.1.4",
        "@shopify/koa-shopify-graphql-proxy": "^5.0.2",
        "@shopify/koa-shopify-webhooks": "^3.0.2",
        "@shopify/react-shopify-app-route-propagator": "^3.0.8",
        "@shopify/polaris": "^6.6.0",
        "@shopify/polaris-icons": "^4.6.2",
        "@shopify/shopify-api": "^1.4.1",


Whitelist the jekyll-redirect-from

Since this commit the reference.html links on the homepage don't work anymore: well-documented API or API documentation
Based on the installation procedures of this plugin it's recommended to whitelist it if Jekyll use the safe mode (which I guess you're using as it's hosted on Github Pages).
I didn't try locally (so maybe double check) but hopefully it will solve this issue. :sparkles:

Hi and thanks!
Weird thing is the redirect worked up until yesterday, when we changed the redirect. Maybe something in GitHub's Jekyll setup changed since the site was last generated?
Anyway, you suggestion looks very promising, I've scratched my head over this since yesterday, so I'm going to merge this in the hope that it resolves the problem!

Unfortunately does not seem to have improved the situation :(
Related to #5585. I've contacted GitHub support, lets hope they can explain what's going on.

You mean it worked on the live website or locally?
Because based on your Contributing page you do jekyll serve --watch which may work.
But I think Github Pages launch it with: jekyll serve --safe and the safe might be the issue.
But ok, :crossed_fingers: because I have played with Jekyll for years.

Ok :sob:.
I tried; I failed. :see_no_evil:

It worked on the live website up until yesterday. Still works locally for me, but as you say that might be because of some other mode/config.


Running snapshot on separate module framework

Do anyone encounter tableview cannot render its view due to running the snapshot not in host application?

I found out that each time I run the snapshot not in host application, the tableview will log some kind of warning like this
/[TableView] Warning once only: UITableView was told to layout its visible cells and other contents without being in the view hierarchy (the table view or one of its superviews has not been added to a window). This may cause bugs by forcing views inside the table view to load and perform layout without accurate information (e.g. table view bounds, trait collection, layout margins, safe area insets, etc), and will also cause unnecessary performance overhead due to extra layout passes. Make a symbolic breakpoint at UITableViewAlertForLayoutOutsideViewHierarchy to catch this in the debugger and see what caused this to occur, so you can avoid this action altogether if possible, or defer it until the table view has been added to a window. Table view: <UITableView: 0x7f77ce832200; frame = (-196.5 -360; 393 720); clipsToBounds = YES; gestureRecognizers = <NSArray: 0x60000265bcc0>; backgroundColor = <UIDynamicProviderColor: 0x6000028d0a40; provider = <NSMallocBlock: 0x6000026e7cf0>>; layer = <CALayer: 0x600002897b00>; contentOffset: {0, 0}; contentSize: {393, 0}; adjustedContentInset: {0, 0, 0, 0}; dataSource: <RxCocoa.RxTableViewDataSourceProxy: 0x600000ca7780>>/


New capitation report test run

Run capitation report on the prod volumes with the DS check on.

Testing results on pre-prod (without DS check procedure)
Input
Contracts: 1,312
Contract employees: 291,522
Declarations: 16,010,226
Declarations status history: 16,653,818
Persons: 15,694,250
Divisions: 10,539
Legal entities: 1,354
Output
Status: OK
Report details: 13,120
Total declaration count: 15,609,794
Process time: about 1.5 days


No buildpack groups passed detection for cf-acceptance-test java and dotnet-core sample

I am using your buildpack gcr.io/buildpacks/builder to build cf-acceptance-tests application, like java and dotnet-core. But they are both fail at detect step:
ERROR: No buildpack groups passed detection.
ERROR: Please check that you are running against the correct path.
ERROR: failed to detect: no buildpacks participating

I don't know if you ever tested CTAs samples or not? Or for above samples, they are not suitable for your buildpack?
BTW, I added -log-level=debug flag and check ed, and they reported below log:
Java:
$ /cnb/lifecycle/detector -app=/workspace/source/assets/java -group=/layers/group.toml -plan=/layers/plan.toml -log-level=debug
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
No project files nor .dll files found.
======== Output<EMAIL_ADDRESS>========
no project file found and GOOGLE_BUILDABLE not set.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
skip<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No project files nor .dll files found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.go files found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
No *.go files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_CLEAR_SOURCE not set
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.go files found.
======== Output<EMAIL_ADDRESS>========
No *.go files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_CLEAR_SOURCE not set
======== Results ========
fail<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
pom.xml not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
pom.xml not found.
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
build.gradle not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
build.gradle not found.
======== Results ========
fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.py files found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
requirements.txt not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.py files found.
======== Output<EMAIL_ADDRESS>========
requirements.txt not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
yarn.lock not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
package.json not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>ERROR: No buildpack groups passed detection.
ERROR: Please check that you are running against the correct path.
ERROR: failed to detect: no buildpacks participating

Dotnet-core:
$ /cnb/lifecycle/detector -app=/workspace/source/assets/dotnet-core -group=/layers/group.toml -plan=/layers/plan.toml -log-level=debug
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
no project file found and GOOGLE_BUILDABLE not set.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
pass<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.go files found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
No *.go files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_CLEAR_SOURCE not set
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.go files found.
======== Output<EMAIL_ADDRESS>========
No *.go files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_CLEAR_SOURCE not set
======== Results ========
fail<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
pom.xml not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
pom.xml not found.
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
build.gradle not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.java or *.jar files found.
======== Output<EMAIL_ADDRESS>========
build.gradle not found.
======== Results ========
fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.py files found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
requirements.txt not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
No *.py files found.
======== Output<EMAIL_ADDRESS>========
requirements.txt not found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
yarn.lock not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
package.json not found.
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_FUNCTION_TARGET not set
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>skip<EMAIL_ADDRESS>======== Output<EMAIL_ADDRESS>========
package.json not found and no *.js files found
======== Output<EMAIL_ADDRESS>========
GOOGLE_ENTRYPOINT not set and Procfile not found
======== Results ========
fail<EMAIL_ADDRESS>fail<EMAIL_ADDRESS>ERROR: No buildpack groups passed detection.
ERROR: Please check that you are running against the correct path.
ERROR: failed to detect: no buildpacks participating

If my command is lacking of some parameters or something? Could you have any opinion, please? Thanks in advance!

Thanks for pointing this out @xiujuan95 — I wasn't aware of these tests.  We don't have perfect overlap with the Cloud Foundry buildpacks, so it's not surprising that there are failures.  Our focus is on supporting build-from-source rather than packaging up existing binary blobs.  But it's something for us to consider.

We only support .NET Core 3.0+ applications. The one in the repo seems to use .NET Core 1.x.

I see, thanks @lukasberger @briandealwis

Currently, spring-boot supports image customization via maven or gradle in the latest snapshots get
[INFO] Building image 'docker.io/library/demo:0.0.1-SNAPSHOT'
[INFO]
[INFO]  > Pulling builder image 'gcr.io/buildpacks/builder:latest' 100%
[INFO]  > Pulled builder image 'gcr.io/buildpacks/builder@sha256:efb5f9b7cd976ab6e5a959f453795863a476878be8e5c20b50db22c8aec1227f'
[INFO]  > Pulling run image 'gcr.io/buildpacks/gcp/run:latest' 100%
[INFO]  > Pulled run image 'gcr.io/buildpacks/gcp/run@sha256:9b3973dd6765f88815318454e337b7f5aacf25cf27f3038be49ef18cf6fce3b1'
[INFO]  > Executing lifecycle version v0.7.5
[INFO]  > Using build cache volume 'pack-cache-5cbe5692dbc4.build'
[INFO]
[INFO]  > Running creator
[INFO]     [creator]     ---> DETECTING
[INFO]     [creator]     ERROR: No buildpack groups passed detection.
[INFO]     [creator]     ERROR: Please check that you are running against the correct path.
[INFO]     [creator]     ERROR: failed to detect: failed to detect: no buildpacks participating

and this is due to spring-boot already build the jar so the builder is not able to detect the jar produced. I think will be nice to have this.

@eddumelendez we don't support packaging up a jar directly into a container image at the moment. Could you please open a new issue as your request is not directly related to this issue.

Closing this issue: we discussed this issue as a team and feature parity with the Cloud Foundry buildpacks is not a goal of this project.


Liquid templates with Node

We're considering migrating the Electron site from Jekyll to a Node server. We want to make this change in a granular way, with minimal disruption to the shape of the app, i.e. stylesheets, templates, _data directory, etc should stay where they are.
I'm creating this issue to evaluate the existing tools on npm for rendering Liquid templates.

https://github.com/sirlantis/liquid-node
https://github.com/leizongmin/tinyliquid
https://github.com/harttle/shopify-liquid
https://github.com/leizongmin/express-liquid
https://github.com/jonschlinkert/liquid-to-handlebars

Starting with liquid-node. It gives this error out of the box:

Liquid.FileSystemError: This file system doesn't allow includes

Found an issue: https://github.com/sirlantis/liquid-node/issues/24
Original author is not maintaining:

when I built this library (some years ago) the include-tag didn't exist in the Ruby implementation. ... I currently don't have the time for it though.

The feature was apparently added eventually, but is not documented. ☹

Made a little video that demos my experimentation with liquid stuff so far: https://www.youtube.com/watch?v=XBXLhXj7ZuA

Liquid is not well-supported in node userland, so we ended up migrating everything to Handlebars.


Real isn't a real real

Real in Gram is a double precision floating point number, so is the name Real (excuse the pun) really adequate?

That's true. Change to Float?

Just changed this.


Fix for issue 2370, show machine state after kill is executed

Hi,
This fixes #2370 "kill does not return any message to the user #2370". docker-machine kill displays machine(s) state after kill is executed.
Thanks...

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "2370-kill-return-message" git@github.com:ksasi/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~15
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.


Added new audio device functions to set/get the audio device

This PR adds new functions for audio device handling:
	Array get_device_list();
	String get_device();
	void set_device(String device);

These can be called from GDscript using for example: AudioServer.get_device_list()
This simple project can be used to test this new functionality: Device Changer.zip
Implemented and tested: WASAPI, CoreAudio, PulseAudio and ALSA.

I've just finished implementing this.
I had to re-write some parts of the PulseAudio driver to make it work, so it would be nice to give that some testing before merging. If the other drivers could also be tested it would be great as well.

Confirmed with the just-reenabled Travis iphone builds: https://travis-ci.org/godotengine/godot/jobs/364543876


kivy.logger.FileHandler discards parts of the log message

FileHandler's _write_message never formats the record it receives; instead, it just writes the "msg" field out to the file.  The "msg" field is the format string.  It needs to be merged with the arguments before it is written.  Usually by calling the Handler's Formatter instance.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

FileHandler now inherits from logging.Handler, and calls self.format(record) which does what you are asking.
Closing as fixed (at least a year ago, probably more).


[Pipeline] Push fastlane files to GPlay to keep them synced

The files in fastlane/metadata are currently only used by F-Droid.
Sync with GPlay happens by hand.
This should be automated via a new pipeline.
This way we just need to update them in the repo itself.

no prio for now


Echo at start of install_swift_binaries.sh

This adds an echo statement at the start of the script, so we can tell that it's started in CI logs.
There have been instances of Travis runs that have hung and it hasn't been immediately clear where - e.g. https://travis-ci.org/IBM-Swift/Kitura/jobs/344670075
This would help diagnosis in those cases.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #129 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #129   +/-   ##
=====================================
  Coverage      50%    50%
=====================================
  Files           1      1
  Lines          10     10
=====================================
  Hits            5      5
  Misses          5      5

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 7a688bc...1d9583e. Read the comment docs.


[FEATURE REQUEST] savings ratio for date range on inflow/outflow

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
I would like to see an overall savings rate for the entire selected time span in the Inflow/Outflow page
Describe alternatives you've considered
I can't think of anything else that would provide that functionality

I see that this is implemented in the income/expense tab instead


chore: Add kubebuilder directive to setup default value

What this PR does / why we need it:
This is a follow up PR for https://github.com/envoyproxy/gateway/pull/1661#discussion_r1323545758 to add kubebuilder directive to provide default value

@arkodg EnvoyGateway is not a real CRD, do we really need this?

This is not needed.


Can we have a new release?

This temporarily added code  in victory-label.js throws a warning when I run my app (transform cannot accept string ...)
  // temporarily override methd in victory-core. remove once once issue in rnsvg is fixed
  // https://github.com/react-native-community/react-native-svg/issues/242
  // note: this change will temporarily ignore all transformations other than rotations.
  gettransform(props, style) {
    const { x, y, polar } = props;
    const defaultangle = polar ? labelhelpers.getpolarangle(props) : 0;
    const angle = style.angle || props.angle || defaultangle;
    const r = angle ? angle * (math.pi / 180) : 0;
    const a = math.cos(r);
    const b = math.sin(r);
    const c = -1 * math.sin(r);
    const d = math.cos(r);
    const e = (-1 * x * math.cos(r)) + (y * math.sin(r)) + x;
    const f = (-1 * x * math.sin(r)) - (y * math.cos(r)) + y;
    return `matrix(${a}, ${b}, ${c}, ${d}, ${e}, ${f})`;
  }

I looked at the code base and it has been removed (the issue it links to it's resolved too). Can we release a new version of victory-native without this method?
Thanks.

<EMAIL_ADDRESS>🚀


Create Tok.txt

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the dev branch, not the master branch

Other information:

Hi,
It would help to see your package.json, packer version and what os that your using.
looking at the stack trace it seems it's having issues finding or loading (possible permission issue) the hot-client.js file. It's a simple file that is added to all dev entrypoints in development mode (watch/start)
/* eslint-env browser */
const tmpPublicPath = webpack_public_path;
webpack_public_path = webpack_public_path.replace(//$/, '');
// eslint-disable-next-line node/no-missing-require
const client = require('webpack-hot-middleware/client?dynamicPublicPath=true');
webpack_public_path = tmpPublicPath;
window.shopify_should_reload = false;
client.subscribe((event) => {
if (event.action === 'shopify_upload_finished') {
if (event.force || window.shopify_should_reload) {
window.location.reload();
}
}
});
Potential fixes:
removing packer globally and reinstalling
installing a different version in the project. You can have a global version and a local override. The local will always be used and can be a different version.
Packer v1 - uses webpack 4 and the latest version is v1.4.0
Packer v2 - uses webpack 5 and has a ton of optimizations.


Create Fedora Linux version

Create a version to build VMWare host modules in Fedora Linux

Is there any updates about that ?!

Hello @ahmmeeeddd
Sorry for the delayed response. I have been off github for a while now. But I will soon resume on this item.

That would be amazing!