OData V4 Filtering with EnumType BoYesNoEnum fails

OpenUI5 version: 1.61.1
How to filter from data type I need to filter from the field "VALID" which is of type "BoYesNoEnum", but it gives me the following error

Failed to get contexts for / destinations / ****** / BusinessPartners with start index 0 and length 30 - Error: Unsupported type: SAPB1.BoYesNoEnum

The property is:
<Property Name = "VALID" Type = "SAPB1.BoYesNoEnum" />
That contains the values in JSON: tYES, tNO, but to filter only the N and Y are used
The filter controlller:
    onSearch:function(oEvent){
        var oFilterModel = this.getView().getModel("filters");

        var sStatus= oFilterModel.getProperty("/status");
           if( sStatus ) {
		aFilters.push( new Filter("Valid", FilterOperator.Contains, sStatus ) );
	   }
}

The View
                        <fb:FilterGroupItem visibleInFilterBar="false" groupName="Partner" groupTitle="{i18n>filterPartnerInfo}" name="PartnerStatus" label="{i18n>filterPartnerStatus}">
                            <fb:control>
                                <ComboBox
                                    selectedKey="{filters>/status}"
                                    showSecondaryValues="true"
                                    items="{
                                        path: 'data>/status',
                                        type: 'sap.ui.model.type.String',
                                        templateShareable: false
                                        }">
                                     <items>
                                    <core:Item key="{data>code}" text="{data>name}" />
                                     </items>
                                </ComboBox>
                            </fb:control>
                        </fb:FilterGroupItem>

Data.JSON
{ "status": [ { "name": "Active", "code": "Y" }, { "name": "Inactive", "code": "N" }, { "name": "Other", "code": "" } ]}

Hi @jsondesign ,
the status has not changed, Enum types are not supported by the OData V4 Model. Also it has become less likely that this will change in the last three years.
As there has been no discussion since three years, I am closing the issue.
Best regards
Mathias.


python310Packages.wand: 0.6.11 -> 0.6.13

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.wand is: Ctypes-based simple MagickWand API binding for Python
meta.homepage for python310Packages.wand is: http://wand-py.org/
meta.changelog for python310Packages.wand is: https://docs.wand-py.org/en/0.6.13/changes.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.13 with grep in /nix/store/w0h0dplxx6i4hlp9g3dwyyhcxsr4rs9g-python3.10-wand-0.6.13
found 0.6.13 in filename of file in /nix/store/w0h0dplxx6i4hlp9g3dwyyhcxsr4rs9g-python3.10-wand-0.6.13

Rebuild report (if merged into master) (click to expand)

20 total rebuild path(s)

20 package rebuild(s)

First fifty rebuilds by attrpath
calibre-web
conjure
halftone
python310Packages.layoutparser
python310Packages.pdfplumber
python310Packages.py-pdf-parser
python310Packages.unstructured-inference
python310Packages.wagtail
python310Packages.wagtail-factories
python310Packages.wagtail-localize
python310Packages.wand
python310Packages.willow
python311Packages.layoutparser
python311Packages.pdfplumber
python311Packages.py-pdf-parser
python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wagtail-localize
python311Packages.wand
python311Packages.willow

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w0h0dplxx6i4hlp9g3dwyyhcxsr4rs9g-python3.10-wand-0.6.13 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.wand https://github.com/r-ryantm/nixpkgs/archive/e74be1faa65dffffae0a3512454b56f86f856228.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e74be1faa65dffffae0a3512454b56f86f856228#python310Packages.wand

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w0h0dplxx6i4hlp9g3dwyyhcxsr4rs9g-python3.10-wand-0.6.13
ls -la /nix/store/w0h0dplxx6i4hlp9g3dwyyhcxsr4rs9g-python3.10-wand-0.6.13/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

python310Packages.wagtail-localize
python311Packages.wagtail-localize

17 packages built:

calibre-web
conjure
halftone
python310Packages.layoutparser
python310Packages.pdfplumber
python310Packages.py-pdf-parser
python310Packages.wagtail
python310Packages.wagtail-factories
python310Packages.wand
python310Packages.willow
python311Packages.layoutparser
python311Packages.pdfplumber
python311Packages.py-pdf-parser
python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wand
python311Packages.willow

Maintainer pings
cc @infinisil @dotlambda for testing.

Result of nixpkgs-review pr 265501 at e74be1fa run on x86_64-linux 1

1 package marked as broken and skipped:

python310Packages.unstructured-inference

2 packages failed to build:

python310Packages.wagtail-localize
python311Packages.wagtail-localize

17 packages built successfully:

calibre-web
conjure
halftone
python310Packages.layoutparser
python310Packages.pdfplumber
python310Packages.py-pdf-parser
python310Packages.wagtail
python310Packages.wagtail-factories
python310Packages.wand
python310Packages.willow
python311Packages.layoutparser
python311Packages.pdfplumber
python311Packages.py-pdf-parser
python311Packages.wagtail
python311Packages.wagtail-factories
python311Packages.wand
python311Packages.willow

wagtail-localize also fails on master
cc @sephii


Test

Testing a new workflow with a tiny copy change.

@marionnegp Please approve and merge this when convenient.


I know, I know. Thank you for responding to my question. What I want to ask is why you sort them like this, for example ('B', 0), ('B', -1) and ('Br', 0), ('Br', -1), ('Br', 2), etc. all start with 0 charge, then why 'I' starts with -1 charge，such as ('I', -1), ('I', 0), ('I', 1), ('I', 2), ('I', 3)?

    I know, I know. Thank you for responding to my question. What I want to ask is why you sort them like this, for example ('B', 0), ('B', -1) and ('Br', 0), ('Br', -1), ('Br', 2), etc. all start with 0 charge, then why 'I' starts with -1 charge，such as ('I', -1), ('I', 0), ('I', 1), ('I', 2), ('I', 3)?

Originally posted by @sincebreeze in https://github.com/wengong-jin/multiobj-rationale/issues/14#issuecomment-1312398237

Oh I see. Uh... There is no particular ordering I think... The order doesn't change the result and I don't remember why there are in this order...


New correction needed for ASLLVD

I found an error in the glossing, unfortunately.  The sign we have glossed as UNDEWEAR/PRECIOUS is actually identical with the sign we gloss as CHERISH.
The easiest way to fix this is for you to change the one ASLLVD occurrence of UNDERWEAR/PRECIOUS to CHERISH.
To make the other corrections, I will need to edit the 4 SignStream files for re-upload... sigh.

THANKS.

Those four files are now ready for re-upload.  THANKS.

All 4 updated collections have been uploaded to dev1.cs.  Video processing is in progress

Video and thumbnail generation is complete

thank you!


Class 'Company' not found

Bug report
Title
Installing SASS package in new bagisto project.
Issue Description
**In several class in SAASCustomizer package  use Company class is use,  but the class is not existing and is showing an error all the logic in bagisto is under namespace Webkul in package folder so why use Company is called 4 classes are avelable
use Webkul\SAASCustomizer\Contracts\Company;
use Webkul\SAASCustomizer\Company;
use Webkul\SAASCustomizer\Facades\Company;
use Webkul\SAASCustomizer\Models\Company;

.**
Preconditions
Please provide as detailed information about your environment as possible.
1. Laravel 8 and 7 (tested on both version )

Steps to reproduce
use tutorial in bagisto doc and in the end just run composer dump

https://webkul.com/blog/laravel-ecommerce-multi-tenant-saas-module/
composer dump-autoload

Expected result
Tell us what should happen.
Zorans-MacBook-Pro:bookmark-ecommerce zoranbogoevski$ composer dump-autoload
Generating optimized autoload files
composer/package-versions-deprecated: Generating version class...
composer/package-versions-deprecated: ...done generating version class
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover

In Helper.php line 110:

  Class 'Company' not found

Script @php artisan package:discover handling the post-autoload-dump event returned with error code 1
Zorans-MacBook-Pro:bookmark-ecommerce zoranbogoevski$ Company

Hi @KalimeroMK,
This is a paid module please raise a support ticket here,
https://bagisto.uvdesk.com/en/member/login


Mod Incompatibility With Mo' Bends

I just recently started using your mod and I added it to a custom modpack me and my friends use to play. While making the armor, I found that it did not work as expected and the armor would display as just normal armor while on the player, but on an armor stand, it displays correctly. I did some testing and found out that the mod Mo' Bends seems to cause this issue.

Just found out that Mo' Bends has an experimental version that fixes it. Nevermind.


No output for curl command

Hi All,
I cloned the repo and ran the cli:
Prabuddhs-MacBook-Air:spacy-api-docker pg$ docker run -p "<IP_ADDRESS>:8080:80" jgontrum/spacyapi:en
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2017-10-20 15:46:48,043 CRIT Supervisor running as root (no user in config file)
2017-10-20 15:46:48,043 WARN Included extra file "/etc/supervisor/conf.d/supervisor.conf" during parsing
2017-10-20 15:46:48,070 INFO RPC interface 'supervisor' initialized
2017-10-20 15:46:48,070 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2017-10-20 15:46:48,072 INFO supervisord started with pid 1
2017-10-20 15:46:49,081 INFO spawned: 'nginx' with pid 7
2017-10-20 15:46:49,087 INFO spawned: 'api' with pid 8
2017-10-20 15:46:49,093 INFO spawned: 'frontend' with pid 9
2017-10-20 15:46:50,149 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-10-20 15:46:50,150 INFO success: api entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-10-20 15:46:50,150 INFO success: frontend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
when I run the curl command:
curl -s localhost:8000/ent -d '{"text":"Pastafarians are smarter than people with Coca Cola bottles.", "model":"en"}'
I dont get any output.

Did you maybe use the wrong port? You call localhost:8000 instead of localhost:8080. Also, could you try to specify the content type in the curl request as JSON?

Oops sorry 8080 it is!

Thanks for responding :-)


Unable to remove Lambda layer

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
Added a Lambda layer to my project, added a lambda function and configured it to use the layer.  Updated function to remove lamba layer config and then tried to remove the layer, get error: Resource cannot be removed because it has a dependency on another resource
Amplify CLI Version
4.34.0
To Reproduce
add lambda layer
add function and configure to use layer
push
update function to not use layer
push
try remove layer and error appears
Expected behavior
expect layer to be removed

workaround for this bug:

edit backend-config.json and remove the layer as dependency from the function
amplify env checkout
amplify remove function & delete the layer
-amplify push will then delete the layer

if you do amplify update function and unselect the layer from the function configuration, amplify does NOT remove the dependency for the function layer

@frankclaassen Did you try to push after the you removed it from the function?

@ammarkarachi yes, when I do the push is when I get the error

Just a bit of extra info. In my case I got it to work without having to remove the function.
If you edit these files, removing references to the layer in your function's dependencies, the layer can be properly deleted.

backend-config.json
amplify-meta.json
function-cloudformation-template

I ran into exactly the same problem and could not solve it. I manually removed dependsOn items in backend-config.json  but it did not work. It would be great if this problem is not forgotten...

This has been addressed in the latest version of the CLI


Keycloak doesn't properly upgrade

Keycloak doesn't upgrade properly.  Either the old version is still used, or the database doesn't migrate.
Solutions:

Ideal solution seems to be to use mysql db Backend.  This would allow for future redundancy for high availability configuration.  The second part of the solution is to install keycloak to /opt/keycloak- with a symlink /opt/keycloak
Another solution: same directory configuration as above, then another directory for data that is linked to each time.

We'll use the symlink method for now.

Completed with 5e5516e


Add automated test for ExclusiveModeGpuDiscoveryPlugin

Is your feature request related to a problem? Please describe.
we don't have an automated test for ExclusiveModeGpuDiscoveryPlugin, we should add one that at least sanity checks basic job works and it loads properly.

Created the pipeline in Blossom rapids_it-WITHOUT-isolation to run a sample test with spark.resources.discoveryPlugin=com.nvidia.spark.ExclusiveModeGpuDiscoveryPlugin. If this conf is not set, it will FAILED with "23:55:43  gpu -> [name: gpu, addresses: 0,1,2,3]"
We can run this job once a week.

@tgravescs  Could you please help to check if this job rapids_it-WITHOUT-isolation meet all the requirements?

it should be fine, but builds not working right now. I want to verify spark ui but it looks like this job doesn't save history , so I want to run it and see while running.

it should be fine, but builds not working right now. I want to verify spark ui but it looks like this job doesn't save history , so I want to run it and see while running.

the failures are due to Artifact revisions are inconsistent,  cudf JNI jar downloaded from URM was inconsistent with the cuDF JNI building against rapids-4-spark jar.
You can skip consistent check by SKIP_REVISION_CHECK=true  in OVERWRITE_PARAMS

ok, verified that job looks good we can resolve, please just make sure its pinging slack and we have it documented

ok, verified that job looks good we can resolve, please just make sure its pinging slack and we have it documented

We have pinged the test result to the slack notifications
For the docs  ExclusiveModeGpuDiscoveryPlugin :  https://nvidia.github.io/spark-rapids/docs/get-started/getting-started-on-prem.html#yarn-without-isolation. Need we update other docs besides this one

Sorry I meant our internal spreadsheet for mapping builds to what its testing, confluence page

Sorry I meant our internal spreadsheet for mapping builds to what its testing, confluence page

Thanks for remind, we have already have internal confluence page for all the pipelines. I also added description for the ExclusiveModeGpuDiscoveryPlugin pipeline

so let close this issue as the nightly pipeline runs well.


Copy over the entire :plugins subkey from the config map.

Changes proposed in this PR

Copy over the entire :plugin map from the config.

Why are we making these changes?
So we have a place to put plugin-relevant arguments.

Can you give a specific example of why this is needed?

The configuration map used internally is built from config.edn. The only way for a plugin to get parameters is by examining the config map defstate. WIth this code, plugin parameters can be put in a key (or dictionary) under :plugins in config.edn, and will be copied into the config defstate. Without this code, config.clj would drop the parameters and we don't have a good place for plugin configuration.


enable sync and import trainees from dttp

Context
Required for DTTP migration.

We may not end up needing this once we're done the migration.

Suprceded by https://github.com/DFE-Digital/register-trainee-teachers/pull/2197/


Please check and fix the Learn more link in the string

Hello,
please fix the Learn more link in this sentence:  "Learn more [here](https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/quickstart/javascript/node/text to speech)" under the section "Speech SDK 1.11.0: 2020-March release".
The text 'to speech' is not included in the link tag and it breaks it. The Learn more link should lead to this page: https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/quickstart/javascript/node/text-to-speech
Thanks and kind regards,
Anne H., QC

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

ID: 2f5049c5-bf3f-46fa-fbcd-5178e130bb4c
Version Independent ID: 3c481a07-5a2c-0429-7bb6-bf5d92654905
Content: What's new - Speech service - Azure AI services
Content Source: articles/ai-services/speech-service/releasenotes.md
Service: azure-ai-speech
GitHub Login: @eric-urban
Microsoft Alias: eur

@QueryCoordinator
Thanks for your feedback! We will investigate and update as appropriate.

@QueryCoordinator
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


refactor: split Document into TextDocument and VectorDocument

Based on

#95
#101

I like this PR

from my side ready to merge - any final thoughts?


Notion code blocks still being imported without line breaks

Hey there! Notion import has been the main roadblock for me to switch to Obsidian, so thanks for adding this functionality! I tried to import my workspace today, however I'm still facing the issue first reported in #82. I confirmed that the version of the plugin being used is 1.3.1, which should have the fix, however all my code blocks are still ending up without any line breaks (And my notion is absolutely full of them). Let me know if I can provide anything to help debug this further!

Originally posted by @aksh1618 in https://github.com/obsidianmd/obsidian-importer/issues/82#issuecomment-1717428382

I fiddled around today with this issue, and it looks like after replacement, the tags turn into unterminated ones (
 to
), which leads to the replacement not working. So first I tried changing the replacement logic to replace
 for code blocks, but that could also fail in edge cases, where the code itself contains
, which IMO is likely for a code block. So instead I went for adding a pre & post processing using a placeholder, which works without any issues. Submitting a quick MR for the same.

Just created a pull request that will fix this.

Fixed by https://github.com/obsidianmd/obsidian-importer/pull/118


"native-assets" feature should surface stdout/stderr from build.dart

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
When using the new native assets feature (https://github.com/dart-lang/sdk/issues/50565 and https://github.com/flutter/flutter/issues/129757), the code that invokes build.dart seems to be burying its stdout and stderr.
I think it makes sense that end developers will not want to be bothered by log statements from these build steps during flutter run/build ..., but seeing output / logging statements is important when writing or debugging build.dart.
Proposal
I'm not sure how to differentiate between these two scenarios, but an escape hatch for build.dart authors would be a significant DX improvement.
(similar to dart-lang/sdk#53732)
cc @dcharkes @stuartmorgan

I think it makes sense that end developers will not want to be bothered by log statements from these build steps during flutter run/build ..., but seeing output / logging statements is important when writing or debugging build.dart.

I believe we usually address this kind of thing in the flutter tool by passing verbosity flags through to sub-tools.

Running flutter run/build -v outputs so many logs, that I pipe them to log.txt and use a text editor to search for "native assets" while working on this feature. The amount of output is staggering in verbose mode.
I'm  not sure what the right solution is from a user experience POV here.

I second that using -v creates a suboptimal experience. Without shell modification, I suspect the volume of output would easily crash through terminal buffer limits and not even all be visible.
This feels like a problem that the various logging levels were designed to solve. With -v passed, the tooling could initialize the logging package to respond to all messages up to... I suppose FINEST; whereas without it could only listen to WARNING and above (or maybe even more strict).
This would allow folks writing build hooks to spam messages to themselves at logging.SEVERE if necessary during development, then turn them down to logging.FINE before releasing.

Because it is a CLI, we only have two log-levels in practise, stdout and stderr. Maybe we should consider always forwarding stderr to the logs?
(Side note: none of the native build logs are visible for MSVC builds at all without -v https://github.com/flutter/flutter/blob/a047358c5c8d6cdb395d833fdd365ae1492e7e32/packages/flutter_tools/test/integration.shard/native_assets_test.dart#L245)

Oh right, I didn't think about the fact that build.dart is a separate process. That certainly breaks the logging levels idea.
Always surfacing stderr seems like both a reasonable general practice, and sufficient escape hatch.


not working key-binding with JIS Keyboard

I make VIM-style key-binding plugin ( https://github.com/74th/vscode-vim ).
I use keybinding with JIS keyboard on MacOSX, bellowing keys not work.

no key hits

shift+2
shift+7
shift+[
shift+;
'
`
space

a number of keys hits ( key-bind -> JIS Key )

- -> -,_
shift+= -> =,+
[ -> [,@
shift+' -> ",'
shift+`  -> ~,```` `

strange keys hits

shift+- -> shift+_
= -> ^

I am happy to be able to use : and " for key-binding setting , instead of shift+; and shift+2.

@74th the nasty problem here is that the keyboard dispatching happens in the browser "keydown" event which doesn't hint whatsoever to what a follow-up "keypress" would produce. It literally only gives the key code in the form of a number (numbers which of course vary across browsers and OSes :)).
That is what makes supporting : and " very difficult.
Will try all the other combos you mention, most likely there's some issues with the tables in https://github.com/Microsoft/vscode/blob/master/src/vs/base/browser/keyboardEvent.ts . I will check them and follow up

@74th I didn't get yet to try out the keyboard combos you mention with the JIS keyboard on MacOSX (need help from some colleagues to do that), but please check out #713 in the meantime for an explanation of what's going on.

@74th
Please see https://github.com/alexandrudima/vscode-vim if you are authoring a vim emulation extension for VS Code - it shows how to capture typed characters (not through keybinding rules).


feat(ericbuettner/career-timeline): implement Date Objects for Start- & End Dates of Job Positions

Background:
Currently, the "ericbuettner/career-timeline" library uses string representations for start and end dates of job positions. This approach can lead to potential issues, such as incorrect date formatting, difficulties in sorting, and limited date manipulation capabilities. To enhance the project's functionality and data consistency, it would be beneficial to replace these string representations with Date objects.
Task:

Replace string-based representations of start and end dates with Date objects throughout the codebase.
Ensure that the date parsing and formatting functions are robust and handle various date formats gracefully.

Acceptance Criteria:
Start and end dates are stored and manipulated as Date objects, not strings/enums.
The codebase is thoroughly tested to validate that the changes do not introduce any regressions.
The project's documentation is updated to include instructions for developers on how to work with Date objects for job positions.
Additional Information:
Please ensure that this change adheres to best practices for maintainability. Be mindful of backward compatibility if necessary and thoroughly test the code to ensure it functions as expected.

hey @tuffz,  could you please review it? Your feedback is highly appreciated.


Rosinstall error

@marioney , can you check this:
I am getting the following error:
/home/darko/rospy3_melodic/venv3.6_ros/lib/python3.6/site-packages/wstool/config_yaml.py:74: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
yamldata = yaml.load(stream)
ERROR in config: Invalid multiproject yaml format in [https://github.com/rosin-project/mros1_reasoner/blob/mvp/mros1_reasoner/mros1_reasoner.rosinstall]: mapping values are not allowed here
in "", line 115, column 73
Furthermore, the link to rosinstall is also wrong in this command:
wstool init src https://raw.githubusercontent.com/rosin-project/mros1_reasoner/mvp/mros1_reasoner.rosinstall

Furthermore

actually, that is the reason for the error.
Try this instead:
wstool init src -j8 https://github.com/rosin-project/mros1_reasoner/raw/mvp/mros1_reasoner/mros1_reasoner.rosinstall

can we close this issue @darkobozhinoski ?


Remove script that is no longer used

Only problem here atm is that the script has really nice docs about sentencepiece, not sure where to put them. it's a bit too long for making it comments. maybe a new doc.md somewhere... hmmm

done ty


Updated

Timetable feature added. UI changed

Error thrown and still a new timetable is being made for each timetable insertion

Fixed the timetable creation issue.

Clean up non important print statements and then push


Folding not working

Apache conf file on Ubuntu
Folding is not working.

Hello @NealRM,
"Folding is not working" is not an appropriate issue description. You need to provide at least some minimal reproduction information, for example contents of the configuration file.
I don't know what an "Apache conf file on Ubuntu" exactly is. Is this a system configuration file? As far as I know, Ubuntu config files don't use HOCON. It's unfortunate that the .conf file extension is used by various configuration formats.

Hello @NealRM,
"Folding is not working" is not an appropriate issue description. You need to provide at least some minimal reproduction information, for example contents of the configuration file.
I don't know what an "Apache conf file on Ubuntu" exactly is. Is this a system configuration file? As far as I know, Ubuntu config files don't use HOCON. It's unfortunate that the .conf file extension is used by various configuration formats.


Valid's Cleaning Service

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).
Please provide enough information so that others can review your pull request:
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos etc...

Finished, go ahead


Upgrade coackroachdb helm chart to version 8.1.7, for compatibility with Kubernetes 1.25+

Description
Attempting to deploy the ACP stack on kind v1.25+, yields the following errors from the cockroachdb chart:
  helm upgrade acp acp/kube-acp-stack \
                  --values ./values/kube-acp-stack.yaml \
                  --namespace acp-system \
                  --timeout 30m \
                  --install
  Release "acp" does not exist. Installing it now.
  Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "acp-cockroachdb-budget" namespace: "acp-system" from "": no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"
  ensure CRDs are installed first, resource mapping not found for name: "acp-cockroachdb-rotate-self-signer-client" namespace: "acp-system" from "": no matches for kind "CronJob" in version "batch/v1beta1"
  ensure CRDs are installed first]
  make: *** [install-acp-stack] Error 1

On earlier kind releases, these generate deprecation warnings:
W1003 17:04:08.939807   11242 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
W1003 17:04:08.965993   11242 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob
W1003 17:04:08.996090   11242 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
W1003 17:04:09.206890   11242 warnings.go:70] batch/v1beta1 CronJob is deprecated in v1.21+, unavailable in v1.25+; use batch/v1 CronJob

These issues can be fixed by adopting the currently release 8.1.7 of the cockroachdb helm chart.
Information for QA

[ ] Is QA testing required?
[ ] Does PR contain unit tests?
[ ] Should QA create E2E tests for the change?

Additional QA Procedures (Optional)

I have this task on my board, blocked by:
https://cloudentity.atlassian.net/browse/AUT-7252

@ppodbielski-cloudentity Would you prefer that i close this PR?

yes, please

Closing, because Pawel is already working this issue.


Timeout in gurobi

Currently, CPMpy does not support returning sub-optimal solutions due to a timeout.
As many MIP-like solvers support timing out and returning the best-found solution this might be desirable to support it as well.
Maybe this requires an update to the ExitStatus enum. We also have to check if we want to return True or False for the solve call...

I don't think it would matter for the explanations. We use Gurobi as hitting set solver, the model of which is always satisfiable. So we 'know' that when the answer from model.solve() is False, it happened because of a time-out.
I do think an extra field in the solver status to indicate if a timeout happened might be useful for other applications tho.


Tapping any surface will show iOS keyboard.

For some reason on iOS whenever any piece of paper or other mui elements are tapped, (like the BottomNavigation) the iOS keyboard shows up, in safari & chrome.
This problem does not occur on the web or on Android (both chrome)
Any ideas why this happens?  Anyone had this happen before?
I don't have access to an iOS device to continuously test this.
I'm googling this issue but it doesn't seem a know issue thusfar.
Mui: v0.16.1
React: 15.3.2

Ok, what I did is replace all onTouchTap events with onClick and remove the injectTapEventPlugin, this fixed the issue...
Anyone know if injectTapEventPlugin is still needed for modern(ish) browsers OSes? I don't have to support Internet Explorer or other outdated browsers.

Might be related to: https://github.com/callemall/material-ui/issues/5522

I am having the same issue on iOS device on safari. Chrome ok.
Mui: v0.16.1
React: 15.3.1

I am having the issue with mui 16.1 and react 15.4 with iphone 7 chrome 54.

Would it be useful for there to be an interim release between current master and next which would be master but without the touchtap plugin and onTouchTap replaced with onClick?
This would be a good stepping stone for later consuming the next branch changes, and is what I'm doing at the moment to get a version that doesn't require the plugin.

Would it be useful for there to be an interim release between current master and next which would be master but without the touchtap plugin and onTouchTap replaced with onClick?

@nealeu That's something we could have done, however, I have a low incentive in going into that direction. I have been migration my app a long time ago to the v1-beta branch. The less I work on the master branch and the more appealing the v1-beta branch is the better. I'm closing as the v1-beta branch is no longer using the plugin.

Yes. Totally agree.


Fix #14466

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14471/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14471/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14471/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14471/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14471/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14471/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14471/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14471/merge#BCU1XR#0


Ingressgateway pod restart became ready with empty XDS config

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
We have an Ingressgateway pod restarted(due to node reboot) became ready with empty config. Istioctl pc all got an empty config for that ingressgateway pod.
The bug here seems that with PILOT_DISABLE_SDS_INITIAL_FETCH_TIMEOUT = false and  PILOT_XDS_SEND_TIMEOUT = 0s, if the initial SDS push failed then ingressgateway will stuck forever at ready state.
Istiod and IngressGateway :
024-03-12 14:19:56.000
2024-03-12T06:19:56.238930Z info  xdsproxy  connected to upstream XDS server: istiod-staging-117.istio-stagingcluster:15012
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267710Z info  cache generated new workload certificate  latency=366.768537ms ttl=23h59m59.732307205s
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267774Z info  cache Root cert has changed, start rotating root cert
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267793Z info  ads XDS: Incremental Pushing:0 ConnectedEndpoints:0 Version:
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267887Z info  cache returned workload trust anchor from cache ttl=23h59m59.732116592s
2024-03-12 14:19:56.001
2024-03-12T06:19:56.263940Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628029
2024-03-12 14:19:56.001
2024-03-12T06:19:56.278688Z info  ads CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1553 size:2.4MB cached:1539/1553
2024-03-12 14:20:36.001
2024-03-12T06:20:36.224037Z info  ads ADS: "<IP_ADDRESS>:41176" istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628029 terminated
2024-03-12 14:20:59.000
2024-03-12T06:20:59.950296Z warning envoy config external/envoy/source/common/config/grpc_stream.h:163  StreamAggregatedResources gRPC config stream to xds-grpc closed: 13,  thread=30
2024-03-12 14:21:00.000
2024-03-12T06:21:00.104643Z info  xdsproxy  connected to upstream XDS server: istiod-staging-117.istio-stagingcluster:15012
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747701Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747791Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-2
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747903Z info  cache returned workload certificate from cache  ttl=23h58m55.252105979s
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747922Z info  cache returned workload trust anchor from cache ttl=23h58m55.252083683s
2024-03-12 14:21:00.000
2024-03-12T06:21:00.748431Z info  ads SDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:8.9kB resource:default
2024-03-12 14:21:00.000
2024-03-12T06:21:00.748507Z info  ads SDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:1.8kB resource:ROOTCA
2024-03-12 14:21:00.006
2024-03-12T06:21:00.132822Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518
2024-03-12 14:21:00.006
2024-03-12T06:21:00.154959Z info  ads CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1553 size:2.4MB cached:1539/1553
2024-03-12 14:21:00.006
2024-03-12T06:21:00.222308Z info  ads EDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1471 size:903.7kB empty:34 cached:841/1471
2024-03-12 14:21:23.006
2024-03-12T06:21:23.745526Z info  ads LDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:908 size:5.1MB
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330737Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330780Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
.
.
.

2024-03-12T06:21:53.337398Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.337406Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.006
2024-03-12T06:21:53.348159Z info  ads RDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:905 size:1.7MB cached:0/0
2024-03-12 14:22:03.006
2024-03-12T06:22:03.275173Z info  ads Client closed connection istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518
2024-03-12 14:22:03.006
2024-03-12T06:22:03.275195Z info  ads ADS: "<IP_ADDRESS>:41180" istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518 terminated with stream closed
2024-03-12 14:22:03.006
2024-03-12T06:22:03.275256Z info  ads Client closed connection istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518
2024-03-12 14:22:15.006
2024-03-12T06:22:15.848115Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628589
2024-03-12 14:22:15.006
2024-03-12T06:22:15.848301Z info  ads CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:22:15.006
2024-03-12T06:22:15.860614Z info  ads LDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:30:10.008
2024-03-12T06:30:10.129347Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:30:10.008
2024-03-12T06:30:10.129429Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:10.009
2024-03-12T06:33:10.015255Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:10.009
2024-03-12T06:33:10.015337Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:14.010
2024-03-12T06:33:14.950132Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:14.010
2024-03-12T06:33:14.950238Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:23.000
2024-03-12T06:33:23.077625Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:23.000
2024-03-12T06:33:23.077706Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:24.001
2024-03-12T06:33:24.391412Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:24.001
2024-03-12T06:33:24.391501Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:34:08.002
2024-03-12T06:34:08.470863Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:34:08.002
2024-03-12T06:34:08.470967Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:34:20.003
2024-03-12T06:34:20.054052Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:34:20.003
2024-03-12T06:34:20.054142Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:35:43.004
2024-03-12T06:35:43.892543Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:35:43.004
2024-03-12T06:35:43.892658Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:36:02.005
2024-03-12T06:36:02.484679Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:36:02.005
2024-03-12T06:36:02.484771Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B

Here we can see after ingressgateway terminated with stream closed, then a new  ADS connection for istio-ingressgateway-5f7fcd8cb5-sx7h6,  then it stuck at ads LDS: resources:0 size:0B and  ads CDS: resources:1 size:24B forever. After that the ingressgw cps dropped to 0.

Here is another case for a normal ingressgateway stream close and reconnect, it didn't get stuck:
2024-03-12 11:17:41.010
2024-03-12T03:17:41.818918Z	info	ads	ADS: "<IP_ADDRESS>:37264" istio-ingressgateway-5f7fcd8cb5-phbrf.istio-staging-1619251 terminated with stream closed
2024-03-12 11:17:42.000
2024-03-12T03:17:42.154177Z	info	xdsproxy	connected to upstream XDS server: istiod-staging-117.istio-staging.svc.140.tess.io:15012
2024-03-12 11:17:42.010
2024-03-12T03:17:42.197426Z	info	ads	ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-phbrf.istio-staging-1620563
2024-03-12 11:17:42.010
2024-03-12T03:17:42.274140Z	info	ads	CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-phbrf.istio-staging resources:1553 size:2.4MB cached:2/1553
2024-03-12 11:17:42.010
2024-03-12T03:17:42.313155Z	info	ads	EDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-phbrf.istio-staging resources:1471 size:905.5kB empty:33 cached:1040/1471
2024-03-12 11:17:42.010
2024-03-12T03:17:42.479810Z	info	ads	LDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-phbrf.istio-staging resources:908 size:5.1MB
2024-03-12 11:18:25.001
2024-03-12T03:18:25.566385Z	info	ads	Client closed connection istio-ingressgateway-5f7fcd8cb5-phbrf.istio-staging-1619251

Version
istio 1.17
k8s 1.23

Additional Information
No response

neither PILOT_DISABLE_SDS_INITIAL_FETCH_TIMEOUT or PILOT_XDS_SEND_TIMEOUT seem to be flags...? PILOT_XDS_SEND_TIMEOUT is but was removed, SDS one never was?

neither PILOT_DISABLE_SDS_INITIAL_FETCH_TIMEOUT or PILOT_XDS_SEND_TIMEOUT seem to be flags...? PILOT_XDS_SEND_TIMEOUT is but was removed, SDS one never was?

This one PILOT_XDS_SEND_TIMEOUT was removed. PILOT_DISABLE_SDS_INITIAL_FETCH_TIMEOUT this one is a custom flag, basically it's to set ingressgateway SDS initial_fetch_timeout to 0s.
So the problem here is if the ingressgateway SDS initial_fetch_timeout to 0s and if the initial SDS push failed, then igw will stuck at empty pushes.

It sounds like you forked Istio and the fork doesn't work how you want it to...? If so it's not clear what Istio is supposed to do here - it's an issue with your fork, not Istio.

It sounds like you forked Istio and the fork doesn't work how you want it to...? If so it's not clear what Istio is supposed to do here - it's an issue with your fork, not Istio.

@howardjohn  The fork here is mainly to support to configure SDS_INITIAL_FETCH_TIMEOUT=0s which got removed by https://github.com/istio/istio/pull/30948(not quite understand the background), while we need to configure it as 0s in the listener and this can also be done through EnvoyFilter.  And the problem here is with 0s SDS InitialFetchTimeout, if the first SDS push fail then xDS could stuck.

yes that's because of the setting. I don't understand what you want from this issue. You are running into an issue caused by a fork changing a setting Istio doesn't set. There is nothing Istio can do to fix it because Istio doesn't have the problem

I see, thanks @howardjohn

yes that's because of the setting. I don't understand what you want from this issue. You are running into an issue caused by a fork changing a setting Istio doesn't set. There is nothing Istio can do to fix it because Istio doesn't have the problem

@howardjohn  Actually when we ran into this issue, there was no custom behavior, i.e. there was no InitialFetchTimeout configured, so I'd believe it's upstream behavior.
For now we'll enable the custom flag to configure InitialFetchTimeout=0s to intentionally keep ingressgateway from becoming ready with empty configure.

send timeout is also not supported/removed
On Wed, Mar 20, 2024, 9:01 AM Chen Youxiong @.***>
wrote:

yes that's because of the setting. I don't understand what you want from
this issue. You are running into an issue caused by a fork changing a
setting Istio doesn't set. There is nothing Istio can do to fix it because Istio
doesn't have the problem
@howardjohn https://github.com/howardjohn Actually when we ran into
this issue, there was no custom behavior, i.e. there was no
InitialFetchTimeout configured, so I'd believe it's upstream behavior.
For now we'll enable the custom flag to configure InitialFetchTimeout=0s
to intentionally keep ingressgateway from becoming ready with empty
configure.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/49929#issuecomment-2008983853, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXO5OADVYAVP54KJHVDYZE663AVCNFSM6AAAAABEXMZ7MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBYHE4DGOBVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes, my previously description was wrong, this issue happened without send timeout nor InitialFetchTimeout configured.
And to mitigate we'll configure the InitialFetchTimeout to 0s.

got it, thanks
On Wed, Mar 20, 2024, 9:21 AM Chen Youxiong @.***>
wrote:

Yes, my previously description was wrong, this issue happened without send
timeout nor InitialFetchTimeout configured.
And to mitigate we'll configure the InitialFetchTimeout to 0s.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/49929#issuecomment-2009011150, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXKB7547CYQNOUMYXPLYZFBKBAVCNFSM6AAAAABEXMZ7MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBZGAYTCMJVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

If the node was restarted, why does envoy logs not show the process starting?
warning envoy config external/envoy/source/common/config/grpc_stream.h:163  StreamAggregatedResources gRPC config stream to xds-grpc closed: 13,  thread=30
warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30

Shouldn't node restart == process restart?

@howardjohn  I think I omitted the envoy start up log and now the log was rotated, but from workload certificate ttl we can see it's a new cert after envoy start:
2024-03-12T06:19:56.267710Z info  cache generated new workload certificate  latency=366.768537ms ttl=23h59m59.732307205s

Can you show the full logs? I don't think we can debug tricky cases like this with partial information...

Thanks @howardjohn, I find more logs:
IngressGateway log, it just restarted after node restart:
2024-03-12 14:19:55.000
 --concurrency 40]
2024-03-12 14:19:55.000
[2024-03-12 06:19:55.925][30][debug][misc] [./source/extensions/filters/http/bpf_network_policy/bpf_network_policy.h:52] BpfNetworkPolicyFilterConfigFactory::BpfNetworkPolicyFilterConfigFactory
2024-03-12 14:19:55.000
[2024-03-12 06:19:55.925][30][debug][misc] [./source/extensions/filters/http/bpf_source_security_id/bpf_source_security_id.h:55] BpfSourceSecurityIdFilterConfigFactory::BpfSourceSecurityIdFilterConfigFactory
2024-03-12 14:19:56.000
2024-03-12T06:19:56.238930Z info  xdsproxy  connected to upstream XDS server: istiod-staging-117.istio-staging.svc.140.tess.io:15012
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267710Z info  cache generated new workload certificate  latency=366.768537ms ttl=23h59m59.732307205s
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267774Z info  cache Root cert has changed, start rotating root cert
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267793Z info  ads XDS: Incremental Pushing:0 ConnectedEndpoints:0 Version:
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267887Z info  cache returned workload trust anchor from cache ttl=23h59m59.732116592s
2024-03-12 14:20:59.000
2024-03-12T06:20:59.950296Z warning envoy config external/envoy/source/common/config/grpc_stream.h:163  StreamAggregatedResources gRPC config stream to xds-grpc closed: 13,  thread=30
2024-03-12 14:21:00.000
2024-03-12T06:21:00.104643Z info  xdsproxy  connected to upstream XDS server: istiod-staging-117.istio-staging.svc.140.tess.io:15012
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747701Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747791Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-2
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747903Z info  cache returned workload certificate from cache  ttl=23h58m55.252105979s
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747922Z info  cache returned workload trust anchor from cache ttl=23h58m55.252083683s
2024-03-12 14:21:00.000
2024-03-12T06:21:00.748431Z info  ads SDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:8.9kB resource:default
2024-03-12 14:21:00.000
2024-03-12T06:21:00.748507Z info  ads SDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:1.8kB resource:ROOTCA
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330737Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330780Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330791Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330800Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330809Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30

Joint log for ingressgateway/istiod
2024-03-12 14:19:56.000
2024-03-12T06:19:56.238930Z info  xdsproxy  connected to upstream XDS server: istiod-staging-117.istio-staging.svc.140.tess.io:15012
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267710Z info  cache generated new workload certificate  latency=366.768537ms ttl=23h59m59.732307205s
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267774Z info  cache Root cert has changed, start rotating root cert
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267793Z info  ads XDS: Incremental Pushing:0 ConnectedEndpoints:0 Version:
2024-03-12 14:19:56.000
2024-03-12T06:19:56.267887Z info  cache returned workload trust anchor from cache ttl=23h59m59.732116592s
2024-03-12 14:19:56.001
2024-03-12T06:19:56.263940Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628029
2024-03-12 14:19:56.001
2024-03-12T06:19:56.278688Z info  ads CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1553 size:2.4MB cached:1539/1553
2024-03-12 14:20:36.001
2024-03-12T06:20:36.224037Z info  ads ADS: "<IP_ADDRESS>:41176" istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628029 terminated
2024-03-12 14:20:59.000
2024-03-12T06:20:59.950296Z warning envoy config external/envoy/source/common/config/grpc_stream.h:163  StreamAggregatedResources gRPC config stream to xds-grpc closed: 13,  thread=30
2024-03-12 14:21:00.000
2024-03-12T06:21:00.104643Z info  xdsproxy  connected to upstream XDS server: istiod-staging-117.istio-staging.svc.140.tess.io:15012
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747701Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747791Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-2
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747903Z info  cache returned workload certificate from cache  ttl=23h58m55.252105979s
2024-03-12 14:21:00.000
2024-03-12T06:21:00.747922Z info  cache returned workload trust anchor from cache ttl=23h58m55.252083683s
2024-03-12 14:21:00.000
2024-03-12T06:21:00.748431Z info  ads SDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:8.9kB resource:default
2024-03-12 14:21:00.000
2024-03-12T06:21:00.748507Z info  ads SDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:1.8kB resource:ROOTCA
2024-03-12 14:21:00.006
2024-03-12T06:21:00.132822Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518
2024-03-12 14:21:00.006
2024-03-12T06:21:00.154959Z info  ads CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1553 size:2.4MB cached:1539/1553
2024-03-12 14:21:00.006
2024-03-12T06:21:00.222308Z info  ads EDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1471 size:903.7kB empty:34 cached:841/1471
2024-03-12 14:21:23.006
2024-03-12T06:21:23.745526Z info  ads LDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:908 size:5.1MB
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330737Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.330780Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
.
.
.

2024-03-12T06:21:53.337398Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.000
2024-03-12T06:21:53.337406Z warning envoy config external/envoy/source/common/config/grpc_subscription_impl.cc:120  gRPC config: initial fetch timed out for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret thread=30
2024-03-12 14:21:53.006
2024-03-12T06:21:53.348159Z info  ads RDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:905 size:1.7MB cached:0/0
2024-03-12 14:22:03.006
2024-03-12T06:22:03.275173Z info  ads Client closed connection istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518
2024-03-12 14:22:03.006
2024-03-12T06:22:03.275195Z info  ads ADS: "<IP_ADDRESS>:41180" istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518 terminated with stream closed
2024-03-12 14:22:03.006
2024-03-12T06:22:03.275256Z info  ads Client closed connection istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628518
2024-03-12 14:22:15.006
2024-03-12T06:22:15.848115Z info  ads ADS: new connection for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging-1628589
2024-03-12 14:22:15.006
2024-03-12T06:22:15.848301Z info  ads CDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:22:15.006
2024-03-12T06:22:15.860614Z info  ads LDS: PUSH request for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:30:10.008
2024-03-12T06:30:10.129347Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:30:10.008
2024-03-12T06:30:10.129429Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:10.009
2024-03-12T06:33:10.015255Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:10.009
2024-03-12T06:33:10.015337Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:14.010
2024-03-12T06:33:14.950132Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:14.010
2024-03-12T06:33:14.950238Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:23.000
2024-03-12T06:33:23.077625Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:23.000
2024-03-12T06:33:23.077706Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:33:24.001
2024-03-12T06:33:24.391412Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:33:24.001
2024-03-12T06:33:24.391501Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:34:08.002
2024-03-12T06:34:08.470863Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:34:08.002
2024-03-12T06:34:08.470967Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:34:20.003
2024-03-12T06:34:20.054052Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:34:20.003
2024-03-12T06:34:20.054142Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:35:43.004
2024-03-12T06:35:43.892543Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:35:43.004
2024-03-12T06:35:43.892658Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B
2024-03-12 14:36:02.005
2024-03-12T06:36:02.484679Z info  ads CDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:1 size:24B
2024-03-12 14:36:02.005
2024-03-12T06:36:02.484771Z info  ads LDS: PUSH for node:istio-ingressgateway-5f7fcd8cb5-sx7h6.istio-staging resources:0 size:0B

Does the bootstrap config (especially node metadata) get correctly set on the restart?

@howardjohn  I think so since it's node restart, there is no ingressgateway pod recreation.  The metadata you refer to is the envoy-rev.json as below right?
istio-p+      22       1  1  2023 ?        3-01:25:19 /usr/local/bin/envoy -c etc/istio/proxy/envoy-rev.json

Before the node restart we'll send sigterm to ingressgateway pod containers then reboot the node. And after the reboot the envoy-rev.json remains the same as before restart.

@howardjohn  Where is the another file? For files under /etc they will remain intact after node reboot.  Another thing is, this issue is not 100% reproducible since we rebooted multiple nodes but only one got this issue.
It seems to me the init SDS push failed then it stuck at this state.

/etc/istio/pod
On Tue, Apr 16, 2024 at 10:34 PM Chen Youxiong @.***>
wrote:

@howardjohn https://github.com/howardjohn Where is the another file?
For files under /etc they will remain intact after node reboot. Another
thing is, this issue is not 100% reproducible since we rebooted multiple
nodes but only one got this issue.
It seems to me the init SDS push failed then it stuck at this state.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/49929#issuecomment-2060388142, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXN7IDUKNAC2JE5QXBTY5YCYBAVCNFSM6AAAAABEXMZ7MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRQGM4DQMJUGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Make bcrypt-ruby a runtime dependency so it works out of the box

As noted by Ryan Bates in the RailsCast on OmniAuth Identity it currently requires you to add both omniauth-identity and bcrypt-ruby gems to the gemfile in order to work properly. Changing the bcrypt gem to be a runtime dependency allows it to work out of the box.

I'm merging this but I'd rather have a solution that is more friendly to non-native Ruby environments. I think I'll make bcrypt optional (somehow) for the next release.


feat(pcdn): implemented workaround to support custom domain names for…

… private rest apis
Issue #, if available:
N/A
Description of changes:
Adding a new sample, implementing custom domain name support for private REST API endpoints. Additional details of the sample can be found in README.md.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you please add cleanup instructions to the README file?


Inventory Action for connecting animation sequence to level sequence loaded from the layout product type

Changelog Description
This PR is to add inventory action which allows the animation sequence from the animation product type connecting to the level sequence which includes skeletal mesh with the rig.
Additional info
This is only applicable when you loaded the level sequence with layout product type.
There is some adjustment on adding frame range data into the container. Users need to remove and re-load the animation sequence before testing this ticket.
Testing notes:

Load Layout which stores the transformation data of the rig
Load animation which stores the animation data related to the rig
Ayon -> Manage
Select the loaded layout instance and the loaded animation instance
Right click -> Action -> Connect Animation to Level Sequence
Click the level sequence located in the layout folder
The related animation track should be added and bind to the animation sequence

Im experiencing empty Scene Inventory (AYON>Manage) as it does not show any content atm

Im experiencing empty Scene Inventory (AYON>Manage) as it does not show any content atm

I can apply the action in my side.
https://github.com/user-attachments/assets/e137720e-1c4a-4234-b049-aa4f53619f04

It does not throw any error when using both layout in FBX or ABC  when loading it...but it seems that ```Animation got automatically in too... as seen on the scrnshot below as there is a rig asset and animation asset upon loading the layout into UE project:

...not sure if this is intended or not atm (even tho it makes very sense to get layout containing the animation asset in single step via loading Layout)
thoughts?

It does not throw any error when using both layout in FBX or ABC when loading it...but it seems that ```Animation got automatically in too... as seen on the scrnshot below as there is a rig asset and animation asset upon loading the layout into UE project:

...not sure if this is intended or not atm (even tho it makes very sense to get layout containing the animation asset in single step via loading Layout)
thoughts?

This inventory action is only applicable when the rig asset is loaded with layout and the users wants to import the animation sequences along with the asset. But I actually agree that we can make some adjustments where we can create layout with animation, and this way is good for the alembic import or the fbx export with full skeleton set in animation product type

I can also think we might need to have an option for the Connect Animation action to be able to choose also Alembic as if the user chooses Layout (Abc) it always get in the Animation(FBX) even when the preference been set to Alembic. So there is no way to choose the prefered product type e.g. to use pointcacheAnim(Alembic) instead.
For occasion of using Layout (FBX) it works ok even now (as it brings skeletonAnim(FBX) always)

I can also think we might need to have an option for the Connect Animation action to be able to choose also Alembic as if the user chooses Layout (Abc) it always get in the Animation(FBX) even when the preference been set to Alembic. So there is no way to choose the prefered product type e.g. to use pointcacheAnim(Alembic) instead.
For occasion of using Layout (FBX) it works ok even now (as it brings skeletonAnim(FBX) always)
...this is something for consideration, as of course its possible to bring those pointcache Alembics manually atm

I am thinking if we should support to export alembic for rig product type in maya which makes the workflow easier. The current connect animation workflow for alembic is to replace skeletal mesh loaded from the rig product type to that loaded from the animation product type. But it would cause the transformation issue when users use connect alembic animation and then the connect fbx animation.
Maybe we should keep it simple, just support the fbx animation connection instead?(As for the current stage, we dont support rig product type publish in alembic in maya AFAIK)

The connection Action works when using Layout and Animation (FBX) but when going with Alembics it gives an error and no connection happens in the end

LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\core_0.4.5-dev.1\ayon_core\tools\sceneinventory\view.py", line 581, in _process_custom_action
LogPython: Error:     result = action.process(list(containers_by_id.values()))
LogPython: Error:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
LogPython: Error:   File "c:\Work\REPO\ayon-unreal\client\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 36, in process
LogPython: Error:     self.import_animation(containers, sequence)
LogPython: Error:   File "c:\Work\REPO\ayon-unreal\client\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 58, in import_animation
LogPython: Error:     frameStart = next((
LogPython: Error:                  ^^^^^^
LogPython: Error:   File "c:\Work\REPO\ayon-unreal\client\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 59, in <genexpr>
LogPython: Error:     int(container.get("frameStart")) for container in containers
LogPython: Error:     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
LogPython: Error: TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

It's quite weird to see this bug as it is supposed that the imprinted data from load alembic animation already included the frame range data. But anyways, can you try to test it again with the fix?

still throws the error on me...its the very same error

Im getting different error now when trying to connect latest Animation version with Layout>
LogPython: Error: Traceback (most recent call last):
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\core_0.4.4\ayon_core\tools\sceneinventory\view.py", line 581, in _process_custom_action
LogPython: Error:     result = action.process(list(containers_by_id.values()))
LogPython: Error:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 40, in process
LogPython: Error:     self.import_camera(containers, sequence)
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 92, in import_camera
LogPython: Error:     import_camera_to_level_sequence(sequence, parent_id, version_id, layout_world)
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\api\lib.py", line 102, in import_camera_to_level_sequence
LogPython: Error:     repre_entity = get_representation(parent_id, version_id)
LogPython: Error:                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\api\lib.py", line 92, in get_representation
LogPython: Error:     return next(
LogPython: Error:            ^^^^^
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\api\lib.py", line 93, in <genexpr>
LogPython: Error:     (repre for repre in ayon_api.get_representations(
LogPython: Error:   File "C:\Program Files\Ynput\AYON 1.0.4\dependencies\ayon_api\server_api.py", line 6373, in get_representations
LogPython: Error:     for parsed_data in query.continuous_query(self):
LogPython: Error:   File "C:\Program Files\Ynput\AYON 1.0.4\dependencies\ayon_api\graphql.py", line 378, in continuous_query
LogPython: Error:     raise GraphQlQueryFailed(
LogPython: Error: ayon_api.exceptions.GraphQlQueryFailed: GraphQl query Failed: Variable '$versionIds' got invalid value None at 'versionIds[0]'; Expected non-nullable type 'String!' not to be None. (Line 1 Column 50)

Interestingly if I choose different Animation version (in my case one version older one) it wont throw the error but just warning msg:
LogPackageName: Warning: TryConvertFilenameToLongPackageName was passed an ObjectPath (/Game/Ayon/episodes/ep01/sq01/sh010/layoutMain/sh010_map.sh010_map) rather than a PackageName or FilePath; it will be converted to the PackageName. Accepting ObjectPaths is deprecated behavior and will be removed in a future release; TryConvertFilenameToLongPackageName will fail on ObjectPaths.
LogFileHelpers: All files are already saved.

However in both cases the connect action results into no animation added to the rig actor within the layout.

Im getting different error now when trying to connect latest Animation version with Layout>
LogPython: Error: Traceback (most recent call last):
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\core_0.4.4\ayon_core\tools\sceneinventory\view.py", line 581, in _process_custom_action
LogPython: Error:     result = action.process(list(containers_by_id.values()))
LogPython: Error:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 40, in process
LogPython: Error:     self.import_camera(containers, sequence)
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\plugins\inventory\connect_animation_to_sequence.py", line 92, in import_camera
LogPython: Error:     import_camera_to_level_sequence(sequence, parent_id, version_id, layout_world)
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\api\lib.py", line 102, in import_camera_to_level_sequence
LogPython: Error:     repre_entity = get_representation(parent_id, version_id)
LogPython: Error:                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\api\lib.py", line 92, in get_representation
LogPython: Error:     return next(
LogPython: Error:            ^^^^^
LogPython: Error:   File "C:\Users\lbate\AppData\Local\Ynput\AYON\addons\unreal_0.2.3-dev.1\ayon_unreal\api\lib.py", line 93, in <genexpr>
LogPython: Error:     (repre for repre in ayon_api.get_representations(
LogPython: Error:   File "C:\Program Files\Ynput\AYON 1.0.4\dependencies\ayon_api\server_api.py", line 6373, in get_representations
LogPython: Error:     for parsed_data in query.continuous_query(self):
LogPython: Error:   File "C:\Program Files\Ynput\AYON 1.0.4\dependencies\ayon_api\graphql.py", line 378, in continuous_query
LogPython: Error:     raise GraphQlQueryFailed(
LogPython: Error: ayon_api.exceptions.GraphQlQueryFailed: GraphQl query Failed: Variable '$versionIds' got invalid value None at 'versionIds[0]'; Expected non-nullable type 'String!' not to be None. (Line 1 Column 50)

Interestingly if I choose different Animation version (in my case one version older one) it wont throw the error but just warning msg:
LogPackageName: Warning: TryConvertFilenameToLongPackageName was passed an ObjectPath (/Game/Ayon/episodes/ep01/sq01/sh010/layoutMain/sh010_map.sh010_map) rather than a PackageName or FilePath; it will be converted to the PackageName. Accepting ObjectPaths is deprecated behavior and will be removed in a future release; TryConvertFilenameToLongPackageName will fail on ObjectPaths.
LogFileHelpers: All files are already saved.

However in both cases the connect action results into no animation added to the rig actor within the layout.

@LiborBatek can you test again to see the frame range has been resolved? Thanks!


[STORM-788] Fix key for process latencies

Built this and saw two different values, proc-lat < exec-lat, while running word_count.

+1

Looks good to me.

+1


Main production website showing old version of the website.

The main production version of the website is showing the old version of the website instead of the new website. Use the alternative version of the website for now.

Just needed to wait some time before the website got updates.


consider using quick-fedora-mirror for fedora syncing

https://pagure.io/quick-fedora-mirror
It's using zsh, but aside that it should be pretty portable. It's really a lot nicer/faster than bare rsync (for both us and you!)

I don't see any upside to using quick-fedora-mirror. Our upstream mirror.fcix.net is easily able to handle the 20 simultaneous rsync metadata walks that are triggered when we push-mirror out to the Micro Mirror fleet for the EPEL and fedora modules.
quick mirror would also require us to install an additional script plus supporting config files and give up flexibility just for the one project.
What behavior of the current rsync commands that we're using should we be trying to improve?

Ah, I missed that you were pulling from fcix.net. I thought you were pulling from our master mirrors.
Then yes, no advantage unless you hit problems on mirror.fcix.net with metadata walking. :)

Yeah, we definitely couldn't be adding 20 mirrors to some other projects given the state of their tier0 / tier1 mirrors, so currently our big iron in Fremont pulls from all the projects, then immediately sends out MQTT messages to push the Micro Mirror fleet to all pull the updates at the same time, since that reduces the IOPS load on our main mirror since everyone is asking for the same diff at the same time.


Update jsoniter-scala-core, ... to 2.7.1

Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.7.0 to 2.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

labels: library-update, semver-patch

Superseded by #792.


Wrong state count shown for new cases!

Hi Team,
Thanks for the great work !
I just checked that, wrong state count is getting displayed under "Punjab".
The total count of new cases shown is 5 for Punjab, but under the cities, it's showing 6 for Jalandhar.
Please find the

attached screenshot for the same.

I will fix this. Assign it to me

Please report data discrepancies in this form https://forms.gle/7NRSrbspW2a6pbm58, thanks :)


Support custom hashed file name formats

Some bundlers like rollup (also implicitly used by vite) use other file name formats by default, which are not supported by single-page-application-server at the moment. It would be nice optionally to support other file names formats.
See https://rollupjs.org/configuration-options/#output-hashcharacters and https://rollupjs.org/configuration-options/#output-chunkfilenames
As a workaround for vite I recommend to adjust the rollupOptions to use hex as hash-characters and adjust the filenames formats like documented in the rollupjs documentation:
Example:
export default defineConfig(({ mode, command }) => {
  return {
    build: {
      rollupOptions: {
        output: {
          hashCharacters: 'hex',
          entryFileNames: `assets/[name].[hash].js`,
          chunkFileNames: `assets/[name].[hash].js`,
          assetFileNames: `assets/[name].[hash].[ext]`
        }
      },
      [...]
    },
    [...]
  };
});

The same issue applies to Angular since angular-cli application builder is based on rollup.js since v17. Currently I see no way in customizing the filename formats.


ARROW-6465: [Python] Improvement to Windows build instructions

The current instructions for building the pyarrow python extension are incomplete.
Problems include:

missing re2, llvm, clang prerequisites
missing info on which MSVC toolsets are supported
missing info on how the build commands to different MSVC toolsets
missing warning about currently broken Windows build config

This amends the python developer documentation with above.

This is not ready for merging. The rendering is broken. I am trying to learn enough RST to fix it...

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d2be6a5). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #5294   +/-   ##
=========================================
  Coverage          ?   65.15%
=========================================
  Files             ?      497
  Lines             ?    68345
  Branches          ?        0
=========================================
  Hits              ?    44532
  Misses            ?    23813
  Partials          ?        0

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 d2be6a5...927c6cc. Read the comment docs.

@kiszk I am encountering further issues:
Issue 1:
If I do not follow the entire build recipe, but only want to re-build the extension, I need to set the env variables ARROW_HOME and PATH=%ARROW_HOME%\bin;%PATH% if my anaconda prompt was closed since the first build. This should probably also go in the instructions or is that self-evident?
Issue 2:
After I run python setup.py install, close my anaconda propt, re-open the anaconda prompt and try to import pyarrow in python I get the error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Z:\Systemdateien\Miniconda3\envs\pyarrow-dev\lib\site-packages\pyarrow-0.14.1.dev430+g1c42e6f1b.d20190906-py3.7-win-amd64.egg\pyarrow\__init__.py", line 49, in <module>
    from pyarrow.lib import cpu_count, set_cpu_count
ImportError: DLL load failed: The specified module could not be found.

To fix this, I again need to set PATH=%ARROW_HOME%\bin;%PATH%. Should the DLLs not be installed during python setup.py install?

Issue 1:
If I do not follow the entire build recipe, but only want to re-build the extension, I need to set the env variables ARROW_HOME and PATH=%ARROW_HOME%\bin;%PATH% if my anaconda prompt was closed since the first build. This should probably also go in the instructions or is that self-evident?

It may or may not be self-evident depending on the person. Probably a good idea to mention it explicitly in the document.

To fix this, I again need to set PATH=%ARROW_HOME%\bin;%PATH%. Should the DLLs not be installed during python setup.py install?

In general yes this is the recommendation for development.
You can use --bundle-arrow-cpp (and this may work, I haven't tried doing a local install with bundling, we only use this for wheel installs)
You can mention both options

@wesm I updated my local copy from #5297 to the current master and am now encountering new problems with the build:
>>> import pyarrow
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Z:\dev\arrow\python\pyarrow\__init__.py", line 49, in <module>
    from pyarrow.lib import cpu_count, set_cpu_count
ImportError: DLL load failed: The specified procedure could not be found.

I cherry-picked 314e9f0 onto 2164e3b4 (common ancestor of master and #5297) and that works ok. So somewhere since 2164e3b4 an issue seems to have cropped up.
Can you guess where this was introduced? Or shall I try building at different points in between 2164e3b4 and master to identify which commit is causing the issue?
I thought, that maybe a dll was no longer getting built, but that does not seem to be the issue.

With 314e9f0:
>>> import pyarrow
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Z:\dev\arrow\python\pyarrow\__init__.py", line 49, in <module>
    from pyarrow.lib import cpu_count, set_cpu_count
ImportError: DLL load failed: The specified procedure could not be found.
>>> quit()

(pyarrow-dev) Z:\dev\arrow-dist\bin>dir
 Volume in drive Z has no label.

 Volume Serial Number is 08E2-3231

 Directory of Z:\dev\arrow-dist\bin

07/09/2019  21:45    <DIR>          .
07/09/2019  21:45    <DIR>          ..
07/09/2019  21:39         5.629.440 arrow.dll
07/09/2019  21:40            76.288 arrow_dataset.dll
07/09/2019  21:42           764.416 arrow_python.dll
07/09/2019  21:44        22.038.528 gandiva.dll
07/09/2019  21:40         1.306.112 parquet.dll
               5 File(s)     29.814.784 bytes
               2 Dir(s)  216.336.334.848 bytes free

@wesm I updated my local copy from #5297 to the current master and am now encountering new problems with the build:
>>> import pyarrow
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "Z:\dev\arrow\python\pyarrow\__init__.py", line 49, in <module>
    from pyarrow.lib import cpu_count, set_cpu_count
ImportError: DLL load failed: The specified procedure could not be found.

Never mind, I finally found the culprit: When I tested --bundle-cpp-arrow, I combined it with --inplace. This copied the .dll-files to the python source tree and they do not get cleaned out with python setup.py clean.
In my later builds without --bundle-arrow-cpp they thus remained in place and took precedence over the newer .dll-files in PATH.
I added a note to this effect in the updated instructions.


Some characters are not displayed / rendered.

When we create simple and complex pdfs with Oracle Outside in Technology, we get pdfs as a result where some characters will not be displayed in pdf.js. But rendering / displaying these pdfs in Adobe Acrobat Reader and other web pdf viewer works fine.
Attached you will find a simple Excel converted to pdf with the text: Das ist ein Test
The t is missing , but text layer is working.
Mappe123.pdf
Configuration:

Web browser and its version:
Microsoft Edge (Chromium) Windows Version 121.0.2277.112, Chrome (Mac OS) Version 121.0.6167.160

Operating system and its version:
Windows 11, MacOS 14.2.1

PDF.js version:
PDF.js: 4.1.181 and PDF.js: 4.0.379

Is a browser extension:
no

Steps to reproduce the problem:

open attached pdf in pdf.js
compare displaying result with adobe acrobat reader (and other)

What is the expected behavior? (add screenshot)

What went wrong? (add screenshot)

ttx is unhappy with the font:
ERROR: An exception occurred during the decompilation of the 'glyf' table
Traceback (most recent call last):
  File "/home/calixte/.local/lib/python3.8/site-packages/fontTools/ttLib/ttFont.py", line 470, in _readTable
    table.decompile(data, self)
  File "/home/calixte/.local/lib/python3.8/site-packages/fontTools/ttLib/tables/_g_l_y_f.py", line 109, in decompile
    raise ttLib.TTLibError("not enough 'glyf' table data")
fontTools.ttLib.TTLibError: not enough 'glyf' table data

and in trying to open the font in fontforge I get an error for glyph 9 (its data length is negative) and the glyph maps to the missing t.


Help setting up

Hey Manuel. Just saw your talk @ the bevy_meetup #2. Great talk!!
Really amazed by your work.
I've been trying to set up the editor and everything.
So I have a model in blender with an armature rig. (mixamo)

I have exported the model to assets/models/library/BasePlayerModel.glb
assets/animated_scenes/base_player_model.animscn.ron:
(
    source: "models/library/BasePlayerModel.glb#Scene0",
    path_to_player: ["Entity/BasePlayerModel"],
    animation_graph: "animation_graphs/base_player_model.animgraph.ron",
)

assets/animation_graphs/base_player_model.animgraph.ron:
(
)

This is the structure in the bevy_inspector

I'm not sure what I need to do to get my model(scene) to show up in the editor.

Running the command: bevy_animation_graph_editor -a assets/
2024-03-12T19:27:35.931310Z  INFO bevy_render::renderer: AdapterInfo { name: "Apple M1 Pro", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
2024-03-12T19:27:36.075518Z  INFO bevy_winit::system: Creating new window "App" (0v0)
2024-03-12T19:27:36.120602Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "MacOS 14.2.1 ", kernel: "23.2.0", cpu: "Apple M1 Pro", core_count: "8", memory: "32.0 GiB" }
2024-03-12T19:27:36.442789Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442822Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442833Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442840Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442867Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442884Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442897Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442902Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442909Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442919Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.442928Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.443031Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.443049Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.443057Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
2024-03-12T19:27:36.443071Z  WARN bevy_gltf::loader: Failed to generate vertex tangents using the mikktspace algorithm: MissingVertexAttribute("Vertex_Uv")
thread 'IO Task Pool (0)' panicked at /Users/<REDACTED>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_asset-0.12.1/src/io/mod.rs:260:10:
asset paths must have extensions
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I tried to switch around the path_to_player, in many ways. With / without Scene0.

Entity/BasePlayerModel
Entity/BasePlayerModel/Russian_Tactical_Soldier
BasePlayerModel/Russian_Tactical_Soldier
Russian_Tactical_Soldier

No luck yet. Sorry for bothering you!

First thing I noticed is that the path should be in list form, not string form. So it would be ["Entity", "BasePlayerModel"] rather than ["Entity/BasePlayerModel"].
Thanks for the reply! That's great to know!

However, the error seems to indicate something else. Can you run with backtrace enabled (RUST_BACKTRACE=1 bevy_animation_graph_editor -a assets)? I want to get an idea of which asset is causing the problem

Yeah, sure. Although I just noticed. bevy_animation_graph is using bevy 12.1. And I'm on 13.0
Will it work for me if I'm using 0.13?

thread 'IO Task Pool (1)' panicked at /Users/<REDACTED>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_asset-0.12.1/src/io/mod.rs:260:10:
asset paths must have extensions
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::option::expect_failed
   3: bevy_asset::io::get_meta_path
   4: bevy_asset::io::AssetReader::read_meta_bytes::{{closure}}
   5: bevy_asset::server::AssetServer::load_internal::{{closure}}
   6: bevy_asset::server::AssetServer::load_folder_internal::load_folder::{{closure}}
   7: std::panicking::try
   8: async_task::raw::RawTask<F,T,S,M>::run
   9: <futures_lite::future::Or<F1,F2> as core::future::future::Future>::poll
  10: async_executor::Executor::run::{{closure}}
  11: futures_lite::future::block_on
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Yeah, sure. Although I just noticed. bevy_animation_graph is using bevy 12.1. And I'm on 13.0 Will it work for me if I'm using 0.13?

That explains it :)
Currently only 12.1 is supported. I'm planning to push an update for 0.13 this weekend, it's a bit overdue but I've been pretty busy lately

That explains it :) Currently only 12.1 is supported. I'm planning to push an update for 0.13 this weekend, it's a bit overdue but I've been pretty busy lately

Got it! Thank you for the time. No hurry. Great talk!!

Alright, version 0.3 is live now with Bevy 0.13 support. This should fix the problem

Hey! I downloaded the new version, I get no visible errors, but I still can't seem to get the scene to show up!

It seems like you're running bevy_animation_graph_editor -a assets/model/library but your animated scene is at assets/animated_scenes/. Try just running bevy_animation_graph_editor -a assets and send me the output of that.
What the editor does is recursively load all assets under the target directory you pass it, and it will list the detected animated scenes in the UI. If the scenes are not under the assets folder you point the editor to, they won't get detected and nothing will show.
Also, thank you testing this :). Being the one that wrote the software I have a biased view on how confusing parts of it are. I really should make getting started a bit more approachable, maybe add a step-by-step tutorial to the README or add some UI for creating animated scenes from within the editor.

Thank you so much! So I've been testing a few things, tried the /assets approach first but it seems to not like other assets being inside.
2024-03-18T18:54:44.372776Z ERROR bevy_asset::server: Failed to load folder. Could not find an asset loader matching: Loader Name: None; Asset Type: None; Extension: None; Path: Some("splashscreen-01.txt");
Although now that I know that the assets path that you give the bevy_animation_graph_editor is for the animscn files, I just give it the correct path and all good.
➜  game_bevy git:(master) ✗ bevy_animation_graph_editor -a assets/animated_scenes
This is what shows up, looks good at first, seems to load the glb file correctly but doesn't seem to be correct.

The preview hierarchy is completely empty, and there's an error in the console.

So just to understand, is the path_to_player supposed to point at the AnimationPlayer in the hierarchy?

The recursive part seems to fail if there's any asset that doesn't have an asset loader available. I assume that's why it doesn't like the .txt files but it doesn't care about the .jpg files.

Solved it! I had to remove the first entity in the path.

Thanks for all your hard work.

The recursive part seems to fail if there's any asset that doesn't have an asset loader available. I assume that's why it doesn't like the .txt files but it doesn't care about the .jpg files.

Yeah, I'm tracking this one in issue #43. I use AssetServer::load_folder to trigger the load of all assets in the given directory. In 0.12, this used to silently ignore files it did not know how to load, but in 0.13 it now just fails.
I might need to add some code iterate through the directory and load files one by one, but for now like you found out a good workaround is to just use a directory that doesn't have any problematic files

Solved it! I had to remove the first entity in the path.
There is now this error though:

Thanks for all your hard work.

Interesting, does the animation actually work despite the error?

So just to understand, is the path_to_player supposed to point at the AnimationPlayer in the hierarchy?

Yeah, that's correct. It uses the path to replace bevy's animation player with an animation graph player.
Honestly though, looking back at it I'm not sure why I made it this way. I can probably just auto detect where the animation player is and save all of us some time in the future :)

Oops sorry, it seems like I edited your message instead of replying to it. The GitHub mobile UI is not great

Closing for now since it's been inactive for a while, but feel free to reopen if you're still having issues


Update doctr deploy

The --gh-pages-docs flag is deprecated and the deploy directory is now a required argument.

I guess I have a bug in my .travis.yaml. I'll fix that later in another PR.
Thanks @gforsyth!


Where's the spec?

I can't use one of the predefined client libraries, but want to roll my own. Do you expose the actual openapi spec somewhere over https or do I have to clone this project, build it to get tmp/spec.yml and then consume that?

Oh, nevermind, found it in one of the closed issues :)
https://developers.phrase.com/api/compiled.json

also: https://github.com/phrase/openapi/blob/master/doc/compiled.json


After switching to viewing pieces in trash, the batch operation button is still "trash," not "rescue"

This was fixed.


This PR adds support for exporting files to a (S)FTP remote location

The last Travis run timed out when trying to connect to https://repository.apache.org. I verified locally that the unit tests run through, re-triggering the Travis run when the repository is available again should fix the issue.

Migrated to different PR


Expose more details about torrent files

Hi, I'm very interested in using this software, however I find it a bit terse regarding the files downloaded via the torrents. Could it be possible to expose more information via the RPC, such as file-level statistics (e.g. file list, size, % completion etc)? I'm thinking of trying to implement this in a fork and submit it to the original project for upstream integration if you're interested: if so, do you have tips as to where to start looking in the codebase?
Thanks! 😊

Another feature I'd be very to see implemented is a basic hook system to execute shell commands on torrent completion, e.g. to trigger downloaded file processing. Same deal, I can try to implement it if you think it can make it upstream.

Hi @falzm . That would be great to see this feature in Rain.
To implement file level statistics, you can add a new rain client files CLI command after rain client peers here:
https://github.com/cenkalti/rain/blob/324770b69a591fe925ec36b47ce342f44e414089/main.go#L239
Another option would be to add file level statistics into rain client stats command but I don't want to do that because currently it is very cheap to call rain client stats and I would like to keep it that way. Iterating over files and pieces can be slow on big torrents.
You can follow the same code path that is similar to rain client peers command for a guideline about the implementation. Please let me know if you have a specific question.
I'll create a separate to issue for your second comment to keep the discussion topics separate.