I have never seen such an awkward upgrade. The version 3 does not support import of an existing Excel or CSV file. This is really making it useless.

Prerequisites

[ ] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[ ] Checked that your issue isn't already filed.
[ ] Checked if no PR was submitted that fixes this problem.

Versions

PHP version:
Laravel version:
Package version:

Description

Steps to Reproduce

Expected behavior:

Actual behavior:

Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Thanks for the constructive feedback

To those who gave my comment a thumb down:
It would be better if you just explained what was wrong with the comment. If I was wrong, show me the way how to do import a file.

Firstly, thank you for providing a free tool. You might be right, but try to see the other side of the table. I use this tool in an application, and by updating the tool, everything stops working. I spend a couple of hours to find out how to resolve the issues, and finally I get the point that the new upgrade is missing half of the functionality (Considering import and export each one covers half of the use cases).

OK Patrick, you are right. I cannot complain about something that I am using for free. As an apology, I changed the title of the issue.


Update impersonation_dhl.yml

Description
Negating additional domains, replies, and removing case-insensitivity for \bD.{0,2}H.{0,2}L.{0,2}\b condition.
Associated samples

https://platform.sublimesecurity.com/messages/fb20874e4ec32f712b1177df0ae20d0e5c82ecd340b99135ca77992320d9eb40
https://platform.sublimesecurity.com/messages/e51f3c71c027e509c73e5a7edaedfde2193717698c6811658b17a7310ebf2242
https://platform.sublimesecurity.com/messages/1cc4d96361afc1f5ad7c5b0a167c4e6adc232e6beecee28502846550265df31b

/mql-mimic-exempt 258747, 296343, 296345, 296349, 296344, 296347, 296346, 296350, 296348, 296351, 123504, 368556, 403844
All unrelated to DHL entirely.

/mql-mimic-exempt 475457
Mimic being silly, it does still flag.


+0 Generates error

Describe the bug
When a user inputs +0 e.g. 1d20+0 the script responds with an error.
Please note that this was actually working as expected on the previous version.

Hey guys. That could definitely not throw an error!
Is this on the latest version (4.5.1)? I'll take a look.

Just checked, yes, it's 4.5.1

Okay, that should be fixed now, in v4.5.2. Let me know if you have any issues!

Confirmed - working - will deploy new version on World Anvil thank you so much @GreenImp for the amazingly quick response.


bazel-gazelle: 0.33.0 -> 0.35.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bazelbuild/bazel-gazelle/releases.
meta.description for bazel-gazelle is: Gazelle is a Bazel build file generator for Bazel projects. It natively
supports Go and protobuf, and it may be extended to support new languages
and custom rule sets.
meta.homepage for bazel-gazelle is: https://github.com/bazelbuild/bazel-gazelle
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.34.0 in filename of file in /nix/store/ng1wh7jni8dm04vrqgcgjb0gc5bnyp54-bazel-gazelle-0.34.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
bazel-gazelle
envoy
pomerium

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ng1wh7jni8dm04vrqgcgjb0gc5bnyp54-bazel-gazelle-0.34.0 \
  --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 bazel-gazelle https://github.com/r-ryantm/nixpkgs/archive/dce7c1b877e7d3866d1ef9564977068366d8a78f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/dce7c1b877e7d3866d1ef9564977068366d8a78f#bazel-gazelle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ng1wh7jni8dm04vrqgcgjb0gc5bnyp54-bazel-gazelle-0.34.0
ls -la /nix/store/ng1wh7jni8dm04vrqgcgjb0gc5bnyp54-bazel-gazelle-0.34.0/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

3 packages built:

bazel-gazelle
envoy
pomerium

Maintainer pings
cc @kalbasit for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bazelbuild/bazel-gazelle/releases.
meta.description for bazel-gazelle is: Gazelle is a Bazel build file generator for Bazel projects. It natively
supports Go and protobuf, and it may be extended to support new languages
and custom rule sets.
meta.homepage for bazel-gazelle is: https://github.com/bazelbuild/bazel-gazelle
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.35.0 in filename of file in /nix/store/v25r2vj2z80fi3h510gm50glkq06f92w-bazel-gazelle-0.35.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
bazel-gazelle
envoy
pomerium

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/v25r2vj2z80fi3h510gm50glkq06f92w-bazel-gazelle-0.35.0 \
  --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 bazel-gazelle https://github.com/r-ryantm/nixpkgs/archive/b42317907737990d36dc72bdbec1043409e25f4b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b42317907737990d36dc72bdbec1043409e25f4b#bazel-gazelle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/v25r2vj2z80fi3h510gm50glkq06f92w-bazel-gazelle-0.35.0
ls -la /nix/store/v25r2vj2z80fi3h510gm50glkq06f92w-bazel-gazelle-0.35.0/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

3 packages built:

bazel-gazelle
envoy
pomerium

Maintainer pings
cc @kalbasit for testing.


Remove broccoli-unwatched-tree dependency.

This package is unused in ember-cli-mirage (and it has been deprecated upstream).

thanks ya big bear


[Question]: Using Hugging Face Text Generation Inference with llama-index

Question Validation

[x] I have searched both the documentation and discord for an answer.

Question
I was curious if there was a recommended approach for using llama-index alongside Hugging Face's Text Generation Inference Server.
There seems to be langchain support for defining the llm
Wanted to see if I should use that and pass it directly into my service context, or if I should write an LLMPredictor wrapping it, or if there was any other recommended route for utilizing TGIS as the "llm".
For context, I am currently using Falcon-7B directly with the HuggingFaceLLMPredictor in llama-index, but would like to switch to running Falcon-7B via TGIS, then using llama-index on top of that.

It shouuuld work if you wrap it with the LLMPredictor class yea @Maxusmusti

Got it, I'll give it a try!

Update: I managed to get it working via the following:
tgis_predictor = LLMPredictor(
        llm=HuggingFaceTextGenInference(
            inference_server_url="http://localhost:8010/",
            max_new_tokens=256,
            temperature=0.7,
            server_kwargs={},
        )
    )

however, I realized my model performed much worse without being able to pass in system prompts and query wrapper prompts into the predictor, like you can with the HuggingFaceLLMPredictor, so I made some changes to the standard LLMPredictor to make the following possible:
    system_prompt = """# Falcon-7B Instruct
    - You are a helpful AI assistant and provide the answer for the question based on the given context.
    - You answer the question as truthfully as possible using the provided text, and if the answer is not contained within the text below, you say "I don't know".
    """

    # This will wrap the default prompts that are internal to llama-index
    query_wrapper_prompt = SimpleInputPrompt(">>QUESTION<<{query_str}\n>>ANSWER<<")

    # Change default model
    embed_model = LangchainEmbedding(HuggingFaceEmbeddings())
    tgis_predictor = LLMPredictor(
        llm=HuggingFaceTextGenInference(
            inference_server_url="http://localhost:8010/",
            max_new_tokens=256,
            temperature=0.7,
            server_kwargs={},
        ),
        system_prompt=system_prompt, # added in llama-index by myself
        query_wrapper_prompt=query_wrapper_prompt # added in llama-index by myself
    )

This addition SIGNIFICANTLY improved model response accuracy/desirability.
I've opened up a PR to add the feature to llama-index upstream: #6647

@logan-markewich Let me know if there's anything improperly formatted or set up with the way I made the PR, and thanks again for the quick response!

Thanks for working on this- I stumbled across it after making something similar (I'm running falcon 40b-instruct with TGI locally along with my own hosted embedding service). fwiw, I also implemented my own custom HuggingFaceTextGenInference for other things I needed, so I just ended up implementing the query wrapper there (along with adjusting max_new_tokens to avoid size issues).


Reactivate the builds of jodconverter-gui/jodconverter-rest when they are Java11 compatible

See https://github.com/sbraconnier/jodconverter/pull/128

done, its all j11 now


Anti xray is exempted from authority

Are there any exemptions?
How to use the waiver？

Antixray.bypass is gone Why?

The bypass permission has been removed, because it caused to many mod incompatibilities.


Travis CI: Update install-jdk.sh to version 2018-09-26

@rhusar     :smile:
What's wit these "no language set" in Travis? :disappointed:

@Karm rather than managing the CI infrastructure, the installation of JDKs on Travis is handled by a (this) script. However, the script needs an update from time to time when a JDK goes GA. Looks like the thus the download location changed. Not ideal, but...

@Karm the "no language set" thing is a Travis concept. But travis is ridiculously horribly bad with JDK support :-(


Enable Paranext core component styles in web views

Right now, the only way we are getting styles in web views is by copying the material ui styles and putting them in a web view stylesheet. Either pass down styles from the renderer into each iframe or package paranext core component styles in with the components (which would hopefully be accomplished by #139

Since #139 is not yet done nor even in the current sprint, investigate passing styles to each iframe.
Assumptions: this is a react only problem.
Questions:

[ ] Can we include MUI styles in the webview CSS?
[ ] Can use the StylesProvider component provided by MUI to pass down the MUI styles from the parent document into the iframe.

Agreed, I believe this is a React-only problem as well.
#139 is older than this issue and lower priority. If the best way to solve this issue is to create an npm library, do not avoid it just because this issue isn't #139. If you want to go with a different strategy, though, whatever works best.
I think passing styles down might be adding unnecessary complications and fragility to the styles, so I recommend investigating making a library first. Basically I think passing down styles would mean creating a hook that listens for changes in styles in the parent frame and adjusts them in the child. I made useStyle to use a style string in the POC, but it does not do what we need it to do.
I think potentially the easier and more efficient solution would be to bundle the components up into a library. That way, styles are applied in a very expected and normal fashion (required styles are carried in through the library's JS) unlike passing all styles from the parent to the child and updating anytime styles in the parent change.
There are a couple of complications I see potentially happening... If we depend on the papi in these components, that creates a circular dependency because the components are on papi but using papi. Not sure what to do about that to be honest. Maybe putting the hooks and context into this library would help somewhat...? But it would still have the circular dependency. Interesting 🤔
I think including MUI styles in the webview CSS would mean we would have to update the styles manually with every update to MUI or every additional MUI component we use. I think a solution similar to we have done as mentioned in the issue regarding copying styles is a very error-prone, temporary solution.
It would be best to make the solution MUI-independent as we already include and may subsequently include even more libraries other than MUI.

Future TODO:

[ ] Decide if this package will be public, if not it will probably need an NPM organization setup to publish it to privately.
[ ] What NPM user login will we use to publish it (each developer or an app-wide user)?
[ ] Currently the package is called papi-components, perhaps we need to namespace it, e.g. sil-papi-components or ubs-components?

Also completes #139.

WebView bundle size is controlled by extensions\vite\vite-web-view.config.ts. The papi-component is ~2.2MB because it includes source maps but even by not generating source maps there, they are still generated by extensions\vite\vite-web-view.config.ts. It is possible to remove them for an individual package something like this:
// vite-web-view.config.ts
export default {
  // Other Vite configuration options...

  rollupOptions: {
    output: {
      sourcemap: true,
      sourcemapExcludeSources: true,
    },
    // Exclude source maps for a specific package
    plugin: [
      {
        name: 'exclude-source-maps-plugin',
        generateBundle(_, bundle) {
          for (const fileName in bundle) {
            if (fileName.includes('papi-components')) {
              bundle[fileName].map = undefined;
            }
          }
        },
      },
    ],
  },
};

The rollupOptions.output.sourcemap option is set to true to enable the generation of source maps for all the packages except the specific one. The rollupOptions.output.sourcemapExcludeSources option is set to true to exclude the actual source code from the generated source maps.
The rollupOptions.plugin section includes a custom plugin that loops through the generated bundle and sets the map property to undefined for the specific package, effectively excluding its source maps.
By configuring Vite in this way, you should be able to prevent source maps from being added for the particular package while still generating them for everything else.


Langsmith tracing latencies don't add up

Bug Description
If you run a flow enabling langsmith tracing, the total time of a run is mostly correct. However each component shows a very short time (milliseconds).

After checking the code, I've realized that for each component we only trace the build output part, without considering the init of the class which normally is the operation that takes longer (.e.g init http clients and connect to servers)
Reproduction
Run any flow with langsmith enabled.
Expected behavior
All the components sub-times should add up to the total time
Who can help?
No response
Operating System
macos
Langflow Version
1.0.13
Python Version
None
Screenshot
No response
Flow File
No response

Maybe the trace time is set only once when the component starts.


Occupied and disputed territories on the map

First of all, thanks for creating this project!
I've noticed the map displays some disputed territories by on the ground rule, which will eventually violate some local laws and might trigger some people. For example:
I'm from Ukraine. Russia illegally annexed the Crimea peninsula in 2014. This act was not recognized by almost every country, but your map shows Crimea as a part of Russia:

This looks offensive and displays support to the Russian war machine. Additionally, this map shows unrecognized Northem Cyprus.
Yes, I know you're using react-simple-maps and vector maps by natural-earth-vector. I just want to let you know, that this map might be offensive. You should use admin_0 geojson maps to avoid this.
You can find additional info about this issue here: https://github.com/nvkelso/natural-earth-vector/issues?q=is%3Aissue+is%3Aopen+crimea

I also opened an issue in react-simple-maps repo: https://github.com/zcreativelabs/react-simple-maps/issues/251

I just want to let you know, that this map might be offensive.

No, not "might be". It is offensive and hugely politically incorrect. I think that data source should be switched to something respected.

@webknjaz I agree. For me, personally, it is offensive. My eyes are hurting every time I see this map. Though, I'm trying to be as polite as possible.

I don't really have a political opinion on the matter. I will just wait for react-simple-maps to make the change and I will gladly update. And switching to admin_0 does not help because it still lists the territory as Russia.

Will update once the dependencies update.

@mikecao I've found a datamaps project which contains a correct map. Would you mind using this instead of the wrong one?
Plausible.io project is using it like this:
Datamap.prototype.worldTopo.objects.world.geometries

It can also be easily installed via npm, so you don't have to update deps manually in the future.

Hey @mikecao, I've sent a PR with a fix: #575
Hopefully, we will get this merged soon to resolve this unpleasant mistake.


change the fixed upstream server name to variable - [merged]

In GitLab by @tmon546596046 on Sep 15, 2020, 06:49
Merges nginxdns -> dev
fix nginx panic when upstream server is not ready
fix nginx wrong dns resolve when upstream ip changes
relate issue #2627

In GitLab by @wknet123 on Sep 15, 2020, 08:14
mentioned in commit 3b323e85b386fc5e9a2ac1d90a9d56a9eea310df

In GitLab by @wknet123 on Sep 15, 2020, 08:14
merged


Remove Unused Import

This is leftover from #285 and should be removed. Will merge after CI if no review.

"If you make you’re being a part of Pinterest public, the build system will automatically approve your ci requests on PINRemoteImage." --some smart dude
https://github.com/orgs/pinterest/people?utf8=✓&query=adlai
@maicki @nguyenhuy @Adlai-Holler


feature(workflows): Introduces automatic documentation builds.

This pull request fixes the lack of Makefile and make.bat when trying to build the documentation locally. Also, it removes the burden of having statically compiled outputs of the documentation inside the repository.
Its main feature is an automatic workflow, based on GitHub actions, that builds a new documentation whenever a pull request is made to master and places the output files into the gh-pages branch, which is then loaded by GitHub Pages and provided as the documentation root.
At the end of the day, the idea is to remove unnecessary files from the repository and let GitHub take care of updating the documentation.

I would say that the ‘gh-pages’ branch does not belong to the main tree, so it is easily detachable and do not interfere in the main history.
Though you are right, every new documentation, for example, each new pull request according to the provided workflow, will build up new files and deploy to the ‘gh-pages’ branch as a new commit.
Let me check if there is a way to rebuild the ‘gh-pages’ branch for every new deploy, so it is essentially always a 1-commit branch holding the updated documentation.

PR will be holded for now, for prior nlp -> master merging.


SitRep Feed

Sharing an idea from Alexei from BRC. He's proposing a view in the front end that serves as a feed of all SitReps (basically anything from the /situation_report/ endpoint, akin to how ReliefWeb does it.
I imagine it would make sense to have this be both a complete feed in chronological order and also be filterable by emergency, emergency type, region, country, etc.
Since documents' locations seem to be stored with either the document or document_url key, I think the solution here would just require a simple if/else across those two fields. I did something similar with a simple Streamlit app my team uses to grab those docs on a disaster-specific basis.

Sounds like it could be part of the Analysis/Reporting hub.


Waymo open dataset docker image pip install issue

When building a docker image from the Dockerfile, I am getting the following error:
Could not find a version that satisfies the requirement tensorflow==2.5.0 (from versions: 0.12.1, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.7.1, 1.8.0, 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.12.2, 1.12.3, 1.13.1, 1.13.2, 1.14.0) No matching distribution found for tensorflow==2.5.0
I fixed this by adding
RUN python3 -m pip install --upgrade pip
to the Dockerfile before the install tensorflow line, but then I get this error:
ERROR: Could not find a version that satisfies the requirement waymo-open-dataset-tf-2-5-0==1.4.1 (from versions: none) ERROR: No matching distribution found for waymo-open-dataset-tf-2-5-0==1.4.1
I dont know what to do because the latest version is 1.4.1 according to pypi which I also have locally.
I am running on Ubuntu 18.04.

I did a version check on python and found out python is Python 3.6.9. This is the problem, python is not updating to 3.8.

Fixed by adding
RUN update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.6 1
RUN update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.8 2
RUN python3 -m pip install --upgrade pip
before the tensorflow install command.
Now there is another compatibility issue though.


Creating Topic via email - Detecting and separating a mail message in headers and body

File / function:
EmailParse.class.php:327 / _split_headers()
Problem:
The function tries to detect beginning and end of the header section by using regular expressions. The problem is that this function is called recursively for parsing the sections of a multipart message. The sequence is:

for the whole message
for first section
for second section
...

As a matter of fact, when called for a section, this will never include a header. Hence the existing code will always return without filling the body block, since this is done by the second regular expression that fills the reg exp result in the $match[] array.
Solution:
Just delete / comment the header start check:
// Do we even start with a header in this boundary section?
// if (!preg_match('~^[\w-]+:[ ].*?\r?\n~i', $this->raw_message))
// {
// 	return;
// }

I think its fine to remove that check block.
Looking at the code it should only be going recursive when it finds boundary sections, it then "expodes" those sections and does a trim, so that boundary section should start with a header at that point.  At least its working on a well formed message.  Of course there are lots of less than well formed emails and thats what makes email such a difficult beast.


Modify makefile to build rpm successfully through 'make --all' command

@TimothyAsir Please have a look to makefile as we are not able to create rpm successfully through make --all command.

@gnehapk Could you try "make setup" and run "make rpm" ? and let me know whether you are able to build the rpm.

@gnehapk , I have send a pr https://github.com/Tendrl/dashboard/pull/201 which does not required any make setup. It will pickup the required java build packaged at run-time from the tendrl-dashboard-build-packages tar at the build time. You can just run "make rpm" to build the rpm once the PR is merged.
This issue can be closed after the PR is merged.


[错误报告]手动添加RSS显示已经加入订阅

确认

[X] 我的版本是最新版本，我的版本号与 version 相同。
[X] 我已经查阅了排错流程，确保提出的问题不在其中。
[X] 我已经查阅了已知问题，并确认我的问题不在其中。
[X] 我已经 issue 中搜索过，确认我的问题没有被提出过。
[X] 我已经修改标题，将标题中的 描述 替换为我遇到的问题。

 Wait for 5 seconds.
[2023-11-13 10:44:52] WARNING:  [Network] Cannot connect to https://mikanani.me/RSS/MyBangumi?token=KOX6oINEVHD2ZFtYyY267twMpQHQJkgYjC4BFEHTuzk%3d. Wait for 5 seconds.
[2023-11-13 10:45:03] WARNING:  [Network] Cannot connect to https://mikanani.me/RSS/MyBangumi?token=KOX6oINEVHD2ZFtYyY267twMpQHQJkgYjC4BFEHTuzk%3d. Wait for 5 seconds.
[2023-11-13 16:11:45] INFO:     Config loaded
[2023-11-13 16:11:45] INFO:     Config updated
[2023-11-13 16:11:45] INFO:     Config loaded
[2023-11-13 16:11:45] INFO:     Program running.
[2023-11-13 16:20:56] INFO:     Start collecting 某大叔的VRMMO活动记 Season 1...
[2023-11-13 16:20:56] WARNING:  Already collected 某大叔的VRMMO活动记 Season 1.
[2023-11-13 16:22:48] INFO:     Start collecting 圣女的魔力是万能的 Season 2...
[2023-11-13 16:22:49] WARNING:  Already collected 圣女的魔力是万能的 Season 2.
[2023-11-13 16:23:54] INFO:     Start collecting 16bit的感动 ANOTHER LAYER Season 1...
[2023-11-13 16:23:55] WARNING:  Already collected 16bit的感动 ANOTHER LAYER Season 1.
[2023-11-13 16:24:20] INFO:     Config loaded
[2023-11-13 16:24:20] WARNING:  Failed to start program
[2023-11-13 16:25:02] INFO:     Config loaded
[2023-11-13 16:25:02] INFO:     Config updated
[2023-11-13 16:25:02] INFO:     Config loaded
[2023-11-13 16:25:02] INFO:     Program running.
[2023-11-13 16:26:02] INFO:     Config loaded
[2023-11-13 16:26:02] INFO:     Program running.
[2023-11-13 16:26:53] INFO:     Start collecting 捡走被人悔婚的千金，教会她坏坏的幸福生活 Season 1...
[2023-11-13 16:26:54] WARNING:  Already collected 捡走被人悔婚的千金，教会她坏坏的幸福生活 Season 1.
[2023-11-13 16:35:56] INFO:     Start collecting 盾之勇者成名录 Season 3...
[2023-11-13 16:35:56] WARNING:  Already collected 盾之勇者成名录 Season 3.

已更新至3.1.11版本，问题依旧，同样qb无法自动下载订阅的番剧
甚至更新完无法复制日志Your browser does not support Clipboard API

随后的日志：
[2023-11-13 16:52:04] INFO:     Started server process [8]
[2023-11-13 16:52:04] INFO:     Waiting for application startup.
[2023-11-13 16:52:04] INFO:
[2023-11-13 16:52:04] INFO:                     _        ____                                    _
[2023-11-13 16:52:04] INFO:          /\        | |      |  _ \                                  ()
[2023-11-13 16:52:04] INFO:         /  \  _   | | ___ | |) | __ _ _ __   __ _ _   _ _ __ ___  _
[2023-11-13 16:52:04] INFO:        / /\ | | | | / _ |  _ < /  | '_ \ / _ | | | | ' ` _ | |
[2023-11-13 16:52:04] INFO:       / ____ \ || | || () | |) | (| | | | | (| | || | | | | | | |
[2023-11-13 16:52:04] INFO:      //    __,|__/|/ _,|| ||_, |_,|| || |||
[2023-11-13 16:52:04] INFO:                                                 / |
[2023-11-13 16:52:04] INFO:                                                |/
[2023-11-13 16:52:04] INFO:     Version 3.1.11  Author: EstrellaXD Twitter: https://twitter.com/Estrella_Pan
[2023-11-13 16:52:04] INFO:     GitHub: https://github.com/EstrellaXD/Auto_Bangumi/
[2023-11-13 16:52:04] INFO:     Starting AutoBangumi...
[2023-11-13 16:52:04] INFO:     Config loaded
[2023-11-13 16:52:05] INFO:     Program running.
[2023-11-13 16:52:05] INFO:     Application startup complete.
[2023-11-13 16:52:05] INFO:     Uvicorn running on http://<IP_ADDRESS>:7892 (Press CTRL+C to quit)
[2023-11-13 16:52:29] INFO:     Config loaded
[2023-11-13 16:52:29] INFO:     Config updated
[2023-11-13 16:52:29] INFO:     Config loaded
[2023-11-13 16:52:29] INFO:     Program running.
[2023-11-13 16:53:59] INFO:     [Manager] Delete rule for 盾之勇者成名录
[2023-11-13 16:54:10] INFO:     Start collecting 盾之勇者成名录 Season 3...
[2023-11-13 16:54:10] WARNING:  Already collected 盾之勇者成名录 Season 3.
[2023-11-13 19:09:40] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aaae89d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:40] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aa836590>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:40] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa85bdd0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/auth/login
[2023-11-13 19:09:40] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa8425d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:40] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aa85aa10>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:40] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa835d10>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/auth/login
[2023-11-13 19:09:40] ERROR     Cannot connect to qBittorrent Server
[2023-11-13 19:09:40] INFO:     Please check the IP and port in WebUI settings
[2023-11-13 19:09:50] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa83f150>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:50] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aaa96050>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:50] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa8a3d50>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/auth/login
[2023-11-13 19:09:50] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aaa96990>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:50] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aaaeb350>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:09:50] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa8370d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/auth/login
[2023-11-13 19:09:50] ERROR     Cannot connect to qBittorrent Server
[2023-11-13 19:09:50] INFO:     Please check the IP and port in WebUI settings
[2023-11-13 19:10:00] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa840f50>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:10:00] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aa8a3d50>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:10:00] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aaa51bd0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/auth/login
[2023-11-13 19:10:00] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa843750>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:10:00] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aa843250>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:10:00] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa8588d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/auth/login
[2023-11-13 19:10:00] ERROR     Cannot connect to qBittorrent Server
[2023-11-13 19:10:00] INFO:     Please check the IP and port in WebUI settings
[2023-11-13 19:10:10] ERROR     [Downloader] Auth failed.
[2023-11-13 19:10:10] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa83dad0>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/torrents/info
[2023-11-13 19:10:10] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aaaeafd0>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:10:10] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f36aaac6c90>: Failed to establish a new connection: [Errno 111] Connection refused')': /
[2023-11-13 19:10:10] WARNING:  Retrying (Retry(total=0, connect=0, read=1, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aab08c10>: Failed to establish a new connection: [Errno 111] Connection refused')': /api/v2/torrents/info
[2023-11-13 19:10:10] WARNING:  Failed to connect to qBittorrent. Connection Error: ConnectionError(MaxRetryError("HTTPConnectionPool(host='<IP_ADDRESS>', port=8085): Max retries exceeded with url: /api/v2/torrents/info (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f36aa841bd0>: Failed to establish a new connection: [Errno 111] Connection refused'))"))
[2023-11-13 19:10:10] WARNING:  Cannot connect to qBittorrent. Wait 5 min and retry...


Support for Python 3

Since Python 2 is EOL in January 2020, is there any plans to support Python 3?

We already support Python 3.
See also Travis build on Python 3: https://travis-ci.org/opennode/python-freeipa/jobs/526468923
Do you have any issues with Python-FreeIPA on Python 3?

I just tried to dumb down my code to see where it fails and it seems that some of my logging code was the one to blame.


Webpack v4.0 introduces plugin changes

This plugin may soon have issues, since the way the plugins are written has changed substantially:
See: Breaking changes for plugins/loaders
https://github.com/webpack/webpack/releases/tag/v4.0.0-beta.0

hi @pentatronix . thanks for the notice, i gonna update the plugin to support these breaking changes

@pentatronix @malinushj hi guys. with the release of webpack v4 i've reviewed the plugin code and did not find any difference between how it's written and how webpack suggests to write a plugin (Plugin API, Writing a Plugin). I have no project on Webpack 3 can painlessly migrate to check though. Have you?

@Va1 @pentatronix  hello! didn't manage to have a look at the new docs but I do have some projects to migrate to webpack 4. I'll do that later today and come back with a response.

@Va1 @pentatronix hi guys!
So Valentyn, you were right, the docs haven't been updated for v4 which is quite sad but I've managed to find the proper way to do it in this repo.
Made #61 and #60.
Not sure if I proceeded correctly with the branching and tagging, feel free to correct me.
And let me know what you think.
As a side note, the adoption rate for the community isn't too great, in my opinion. I think they jumped the boat too fast, not updating the docs and not giving plugin developers more time to migrate... But overall I love v4! Awesome new features.

Not sure anyone is noticing or finding this, but I've isolated that it is this plugin chucking this warning from Webpack with v4.0:
DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead

new release of 2.2.1 is published and it includes support for Webpack v4 while still keeping compatibility with older versions.
big thanks to @malinushj @KyKyPy3 for the code and participation


Make Y-axis for Layer#tile_at reversible

It will go off the tile render order set for the map. The right-down behavior is inconsistent with DragonRuby's pixel coordinates and makes calculations involving tile positions more complicated.

Thanks!


Jittery animation when blending an animation with another animation player track

Godot version
3.4.2.stable
System information
Windows 11, RTX 2060, Core i9-10900KF, GLES3
Issue description
Whenever i try to use Blend2/Add2 in AnimationTree with an animation that contains an Animation track, animation just flickers between "in" and "blend/add" animation.

Steps to reproduce
Select AnimationTree node in the repoduction project, then click on the little "Play" Button of a BlendTree node.

Minimal reproduction project
Animation.zip

It is caused by track caches conflict, duplicate of #43848, and fixed by #56902.

It is caused by track caches are incompatible/conflicted between PropertyTrack and BezierTrack. Duplicate of #43848, and fixed by #56902.
Still you need to match the paths between the 2 tracks, see #49411 (comment).

As you mentioned SkeletonRetarget works only in 3D, i don't really think that's the case but my problem relates to a Skeleton2D node, anyway, i already wrote a small bone merger thing, might upload it to asset lib later.

@MUTEDGALAXY That's PR include #49411, see description.


FR: Changing the reference beat

Requested by ZackTheCardshark:

it would be nice to be able to specify the start and end tempos in different types of BPM—quarters, eighths, halves, and the dotted augmentations of the same

Note to self: thanks to @lasconic we now know that note duration characters are available from a plugin using the 'MScore Text' font in the range \uE1D0 - \uE1E7


Dollar value of RBTC is not updating on Liquality

Hi,
Dollar value of RBTC is not updating on Liquality

I think it's fixed on version 0.14

I think it's fixed on version 0.14


Setting variable bounds (domain?)

Bounded variables are very common (LB <= var  <= UB).
Some have internal bounds like nonneg And boolean and for others, one needs to add the bound constraints. For example an integer variable cannot be specified to be nonneg.
When linearizing various formulations (eg big-M methods) one needs to pass around big M bounds in addition to the bound constraints.
This is inconvenient and makes interfaces cumbersome.
Is there some place that these bounds are stored within a Leaf, Variable or Atom?
I saw something called domain.
Is that relevant?

We currently don't have such a feature. You just append LB <= var and var <= UB to the list of constraints.
Right now CVXPY doesn't treat domain constraints differently than expression constraints. For example, x = Variable(nonneg=True) is later replaced by y = Variable(),  y >= 0 when CVXPY prepares data for a solver. This sort of conversion isn't ideal because it means solvers can't exploit efficient methods for bound constraints. I'm personally in favor of changing this so that domain information is processed in a specialized way. However, there is currently no timeline for adding such a feature.
Maybe you're asking about something else, though?

Thanks. That was the question.
The API I was hoping for was something conceptually like having
lower_bound and upper_bound members or properties which can be set and
queried.
When you have these coupled to the variable they be used in eg big-M
constraints and also no need to add them explicitly to the constraints
(they will be added automatically like with booleans).

Clarifying for people who may work on this, step 1 is to add support for a bounds attribute to Variables and Parameters. After that is implemented we can look into passing bounds information directly to the solvers.

To add my 2 cents, I don't think adding bounds to the variable is a great API gain, as x >= 0 is easier to understand and more general.
What I think could be really useful is if CVXPY were able to infer some variable bounds from the constraints without having to explicitly use the bounds attribute. So that e.g. x <= 3 can be interpreted as a domain constraint and not just like any other constraint. That information can then be passed to the underlying solver.

@jonathanberthias I have worked now with OR people and they consider bounds an important part of the API. Adding automatic checks for variable bounds is an interesting idea but not something we intend to add because it would increase the compile time, which is a major concern for many users.

Closed by #2234


0.50: Initial review of loader.js

Nothing against Joel's work, of course, but I'm seriously wondering whether it wouldn't be simpler to start from scratch. I hadn't realised that the spec had changed so much.

I'd rather not just remove this code actually. Better to get the tests running then move through code changes that keep the tests running. Otherwise the codebase will drift off too much - it then becomes as good as a rewrite getting the tests going eventually.

(Happy to take comment PRs that update the function numbers, note spec deprecations though)

although in principle I think it would be better to start from scratch, in practice I'm not sure that will work, as I doubt whether I will have time to do more than a small part of what needs doing. I can do some work over the next couple of weeks, but after that I'm not sure.
So an incremental approach might be better, but I'm not sure how that would work either, as changing for example Loader.prototype functions means you have to implement the new functions called by those functions, which for the most part don't currently exist or need rewriting. The Registry functions should be reasonably straightforward to implement, so perhaps we could start with that.
But to get the tests working, the environment needs changing - later version of Node, include URL in Node version including Travis, module-only version of Traceur/Babel (what about Typescript?), catering for script type="module" being implemented in browsers. So maybe we should start with that, and leave loader.js for the moment.
As for the missing semicolon, this is something the linter in my editor complained about. I think it would be better for Travis/the build system to run a linter, but presumably it doesn't atm because of the way the code is split into different files and concated into a wrapper. So perhaps converting to ES6 modules and using Rollup to convert into IIFE should also be a priority?
For the time being, I'll change this PR to be comments only. I'll list in the comments for each function which other functions it runs/is dependent on.
I'll also try and draw up some task lists. Rather than preface all these with '0.50', it might be better to create a new Github label and/or milestone for this. I could do this, but because of Github's limited permissions system would have to have commit rights to the repo - otherwise you would have to do it.

@probins https://github.com/whatwg/loader/issues/147 changes things significantly now so I think we should put this effort on hold until that clarifies. It does sound like that will be largely a rewrite direction, so I will aim to jump into this work as soon as it becomes possible now.

yes, I noticed that, though it's all rather vague atm "not an actual plan, just food for thoughts"

might as well close this for the moment

Now to plan that upgrade path :)

whatwg/loader#147 changes things significantly now

@guybedford I'm not sure it does, does it? It changes what is exposed to users, but AIUI the basic Reflect.Loader and Reflect.Module are unchanged. The default browser loader too remains as is, just that it wouldn't be exposed as System.loader any more. The new import() would be used in apps instead of System.loader.import, and you could access the current loader with import.loader. IOW, we can carry on with changing Reflect.Loader and Reflect.Module, leaving the System side of things till later.

@probins if you do want to continue working on PRs based on the new directions I guess we can do that too.

shan't have time this month; perhaps in August. So if you have time to work on this ...

I've been working on a rewrite already of just the shell API for a fast
production loader. Will share something on an experimental branch soon and
copy you in.
On Mon, 25 Jul 2016 at 17:50, Peter Robins<EMAIL_ADDRESS>wrote:

shan't have time this month; perhaps in August. So if you have time to
work on this ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ModuleLoader/es6-module-loader/pull/500#issuecomment-234994725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkiyvcSg83E2qG53ZjKW2jGxG2EL8CDks5qZNtGgaJpZM4I76Re
.


Add optional mutual TLS for internal syslog drains

Description
Activates mutual TLS  for the internal drains in the syslog agents. All of the outgoing connections through internal syslog drains will be secured with mTLS, if the parameter to use mTLS for syslog drains is set to true. The goal is to harden the communication between the Syslog Agents running on all BOSH VMs and the Log-Cache Syslog Server and secure it with mutual TLS.
Changes:

adjust BOSH job templates and add flag to activate mTLS for internal syslog drains like for example log-cache
configure the syslog agent to use mTLS for internal syslog drains in case the DrainUseMTLS flag is true
add test syslog  mTLS configuration to log-cache

Is there any documentation which should be updated?
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Testing performed?

[X] Unit tests
[ ] Integration tests
[ ] Acceptance tests

Checklist:

[X] This PR is being made against the main branch, or relevant version branch
[ ] I have made corresponding changes to the documentation
[X] I have added testing for my changes

@chombium this is blocked on https://github.com/cloudfoundry/cloud_controller_ng/pull/2903 being merged, correct?

@ctlong this PR is not blocked by the cloud controller PR.
The changes only touch the TLS configuration for the internal syslog drains (which means the aggregate drains from the syslog agent to log-cache). I thought that I can reuse the loggregator_tls_agent certificate from the cf-deployment for mTLS between the syslog agent and log-cache as is used in all other places for creating GRPC connections with mTLS between the Loggregator components. As the TLS cert-key pair are used for identification and are already present in the bpm config, I've added a new parameter with which the operators can explicitly activate mTLS for internal drains. Marking a syslog drain as internal is done by adding  ssl-strict-internal=true query parameter to the syslog drain url as used in the cf-deployment and the internal TLS config is used when creating the writer here.
As this configuration is for internal drains between syslog agent and log-cache I think that it should not be done via the binding-cache, but explicitly via envvars (deployment.yml configuration). As I've written earlier, for the mTLS I've reused the loggregator_tls_agent cert-key pair which is used for GRPC. If you think that hat's not the right certificate to use, we can discuss if we maybe need to introduce another cert.

@chombium My thought/hope, honestly, was to be able to refactor aggregate drains to take a query parameter with a named set of named certs configured in bosh?
Maybe there's a future even betterer version of configuring things, but I can't think of anything more natural that doesn't require a lot of work right now either.
Moreso, I also broadly suspect anyone who would want to setup a external tool like a elk stack would find the bosh certificates as client certificates of limited value, but also the ca certificate pool of limited value as well? I think there was a wish to avoid some hard-coded special purpose stuff for log-cache, and I think to a large degree it was achieved, however it was still a little too custom coded with the "ca_certificate" for trust, for example. I'd like to see log-cache just seen by syslog-agent as "just a configured drain" in the future even moreso. It ensures that options for syslog drains carry over well to non-internal syslog drains, but also I think is a little easier to reason about and less magical.
Does that make sense?

(I was also expecting to see a pr like this after we finished up the individual mutual tls changes go through tbh)

Hi @Benjamintf1,
I'm glad that we are thinking in the right direction.
TBH. When I started working with Loggregator two years ago, it was more from the CF operator point of view, but when I did some problem triaging, I've stumbled upon the syslog agent and it was always bugging me why there are two TLS configs (internal and external) when every syslog drain should be treated equally. I thought that there is some special treatment for internal drains, but I was always wondering why, when the log-cache-syslog-server (then part of the Shared Nothing Loggregator Architecture) actually is yet another syslog drain.
I was trying to implement mTLS for the internal drains with as less changes as possible. As there is already implementation about optional activation of TLS, I've followed the same pattern. We also had doubts if we should reuse the same certificate as for GRPC or add more config parameters for a new one. As we were concentrated on internal drains and I saw that the certificate passed to the GRPC tls config is used everywhere in cf-deployment I've decided to reuse what's already existing.
I find the idea of waiting for the other PR for the external syslog drains to be merged and then refactoring and unifying the TLS configuration and handling really good.
We should definitely discuss the future of Loggregator and the direction in which the project goes more often. We've gained big knowledge in operating Loggregator int he past few years and we've have ideas for many possible improvement. Let's find a communication format how we can discuss all things Loggregator ;)
Now back to the PR, do you think its worth improving it and adding extra configuration parameters for the ca, cert and key which will be used for mTLS with internal syslog drains? Would that be a viable option until we do a proper refactoring or I should close the PR and we discuss the things further?

also had doubts if we should reuse the same certificate as for GRPC or add more config parameters for a new one.

I think my own inclination is to use a new one. You can always reuse the certificate if you wish, but ability to have seperate sets of certs i think is hypothetically a bit more secure and also better wrt configuration in general for drains.
Now back to the PR, do you think its worth improving it and adding extra configuration parameters for the ca, cert and key which will be used for mTLS with internal syslog drains? Would that be a viable option until we do a proper refactoring or I should close the PR and we discuss the things further?

I mean it's a bit rich for me to say to some degree given I'm not actually doing the work, but I think it'd be a good idea to at least have a configuration parameter in syslog-agent that allows setting certificates for use by aggregate drains, then you could just use the special aggregate only query params to refer to the map key?

So, just to reiterate some thoughts here.
My thought on how to do mtls for aggregate drains.
have a bosh setting, example config(aggregate_drain_certificates is the only one defined in the spec, all the rest dynamic?).
Ideally in terms of uptime we define it in the binding-cache, but it would be easier to define in the agent.
aggregate_drain_certificates:
    log_cache_certs:
       ca: |
          --begin cert--...
        cert: |
           -- begin cert--....
         key: |
           -- begin key--...
     elk_certs:
        ca: |
          --begin cert--...
        cert: |
           -- begin cert--....
         key: |
           -- begin key--...

then we can define aggregate drains with
<log-cache-address>?certs=log_cache_certs,<elk-address>?certs=elk_certs

Make a v2 binding-cache endpoint just like before but for aggregate which combines this information. This would allow us to have differing client identies and ca's for each aggregate drain(i suspect usually 1 log-cache and 1 other drain for external use). Then we can make sure log-cache can do mtls. Then we can make a pr for cf-d to update the bosh properties and bosh releases to use this new feature.

@Benjamintf1 I like your idea. So far I've drafted the PR for a single "internal" cert/key pair to log-cache.
I will rework this PR add everything to the binding cache and adapt it to cover all aggregate drains.

Do you think we need to support multiple cert-key pairs on the log-cache side as well?
No, honestly, I think it should be fine. Sorry I forgot about the log-cache side/havn't processed it at all. I'll try and find some time to look into/process it sometime soon. I either might not have realized that pr existed, or falsely gated it on the loggregator-agent work.

I've closed this PR in favor of #187. We can continue the discussion there.


ci: add golangci-lint configuration

204 issues:

dupword: 1
errcheck: 44
gci: 10
gosimple: 17
govet: 1
revive: 3
staticcheck: 2
testifylint: 124
unused: 2

This is the first iteration of #264
It can be merged it won't cause problem
You can launch golangci-lint locally and start fixing the issues one by one
$ golangci-lint run

golangci-lint action still fails the test
https://github.com/dromara/carbon/actions/runs/12308019441

Sorting things is a journey, yes.


Recursive expansion seems to be broken?

Hello. Given this simple example: https://github.com/j7nw4r/utoipauto-bug the macro expansion seems to be broken. It fails with the error message:
error: unexpected attribute, expected any of: handlers, components, modifiers, security, tags, external_docs, servers, expected identifier at the #[utoipauto(paths = "./src")] annotation.
I believe this is because the expansion mistakenly expands to the below and includes an erroneous # [ openapi   ].
#[derive(OpenApi)]
#[openapi(paths   (), components   ( schemas   (), responses   () ), # [ openapi   ])]
struct ApiDoc;

I'm not super familiar with proc-macros, but if pointed in the correct direction, maybe I can look into it.

Hmm. That doesn't seem to work for me either. I'll continue manually adding for now.

The thing I'm 100% sur works is to add a description and info field since it's what is in the tests and what I use in other projects.
#[openapi(info(title = "Percentage API", version = "1.0.0"))]
I'll try to fix it when I can

However, can you clarify what do you mean when you say that '#[openapi()]' doesn't work ?
For me it works...

In my bug example, when I do:
#[utoipauto(paths = "./src")]
#[derive(OpenApi)]
#[openapi()]
struct ApiDoc;

I get a:
`derive` can only be applied to structs, enums, and unions [E0774]

from the compiler. I do not get the same error when I remove the #[utoipauto(paths = "./src")] macro. It seems that the first level macro expansion for the utoipauto macro is:
#[derive(OpenApi)]
#[openapi()]
struct ApiDoc;

So I'm not sure what's the actual issue.
I'm using rustrover, if that helps.

Hmm as I look into it more. Your suggestion may work. I think the issue with suggestion actually lies with RustRover interpretation of the code. I will use your suggestion. Thank you.
The first issue still stands though.

@ProbablyClem If you can point me in a direction, I can fix it.

There's the update_openapi_macro_attributes function in utoipauto-core that'sformating the output

@ProbablyClem Can you look at this PR please? https://github.com/ProbablyClem/utoipauto/pull/17

@ProbablyClem I realized I snuck a change in that accidentally changed functionality. Fix is here: https://github.com/ProbablyClem/utoipauto/pull/18


Add TransferShares and TransferSharesFrom

Codecov Report

Merging #255 (e41d45a) into master (6aaf59a) will decrease coverage by 0.15%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #255      +/-   ##
==========================================
- Coverage   15.95%   15.80%   -0.16%
==========================================
  Files          16       16
  Lines        1736     1753      +17
  Branches      321      322       +1
==========================================
  Hits          277      277
- Misses       1459     1476      +17

Impacted Files
Coverage Δ

contracts/Pool/Pool.sol
0.00% <0.00%> (ø)

contracts/SavingsAccount/SavingsAccount.sol
8.96% <0.00%> (-0.81%)
:arrow_down:

contracts/SavingsAccount/SavingsAccountUtil.sol
0.00% <0.00%> (ø)

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 6aaf59a...e41d45a. Read the comment docs.


First attempt to move to path for states.

Here is a first draft of my code to fix #65. The role of open() seems a little weird, because even if the file has not be opened, we can still get data using get_file_handle(). Same for close(). What do you think @vdumoulin?
I also moved from dataset.close(handle) to dataset.close(), since we don't need to pass the handle anymore, is it okay?

You do have a point: passing the file path as the handle is pretty reduntant, and we could just as well pass None.
Here's an alternative:

We put the code from get_file_handle back in _out_of_memory_open (except that it doesn't return anything) and we remove the get_file_handle method.
The open method calls self._out_of_memory_open() if self.load_in_memory is False and returns None no matter what.
We introduce the following property:

@property
def _file_handle(self):
    if not self.path in self._file_handles:
        raise IOError('no open handle for file {}'.format(self.path))
    return self._file_handles[self.path]

File handles are accessed like so:

handle = self._file_handle

We put the implementation of release_file_handle into out_of_memory_close and remove the release_file_handle method.

It would also be good to add a unit test that fails currently but passes with your changes.
Try adding a test like
# ...
dataset = H5PYDataset(...)
stream = DataStream(dataset)
cPickle.dumps(stream)

@vdumoulin: The problem now is that when we instantiate a new H5PYDataset, the function split_dict() is called (through available_splits()), but the dataset is not opened yet.
Is it okay to call open() at this moment (or _out_of_memory_open()), and immediately close it afterwards?

Yes, that would be acceptable: you're opening the file to read the metadata and then closing it.

I still have some tests that fails. It seems that I have trouble getting the data or when there is two different H5PYDataset on the same hdf5 file.

Which tests, exactly?

test_hdf5.test_h5py_dataset_split
-> ValueError: 'test' split is not provided by this dataset. Available splits are (u'train',).
test_hdf5.test_h5py_dataset_out_of_memory
-> ValueError: 'test' split is not provided by this dataset. Available splits are (u'train',).
test_hdf5.test_h5py_flatten_in_memory
-> AssertionError: Arrays are not equal
test_hdf5.test_h5py_flatten_out_of_memory
-> AssertionError: Arrays are not equal

Weird. Could you fix what I've outlined just to see if it solves the issue?

It don't solve the issuse ... :-(

Calling self._out_of_memory_open and self._out_of_memory_close in load seems to solve at least part of the failures for me.

Mhhh strange. For me the 4 tests don't pass using self._out_of_memory_open and self._out_of_memory_close.

You need to open and close in load.
I think I found why the tests fail: in test_dataset_datastream_pickles, you're not closing the data stream, which leaves a dangling file handle in the _file_handles dict. Since we're re-using 'tmp.hdf5' everywhere in the tests, it causes some issues.
The solution is to make sure that close gets called no matter what, by putting it in the finally block. (By the way, it would be a good thing to do that for all tests in that file as well.)

Great! I'll change that!

Looks good, thanks a lot!

@vdumoulin thanks for your help ;-)


ERROR:    closing handshake failed

ERROR:    closing handshake failed
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 959, in transfer_data
message = await self.read_message()
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 1029, in read_message
frame = await self.read_data_frame(max_size=self.max_size)
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 1104, in read_data_frame
frame = await self.read_frame(max_size)
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 1161, in read_frame
frame = await Frame.read(
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/framing.py", line 68, in read
data = await reader(2)
File<EMAIL_ADDRESS>line 721, in readexactly
raise exceptions.IncompleteReadError(incomplete, n)
asyncio.exceptions.IncompleteReadError: 0 bytes read on a total of 2 expected bytes
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/server.py", line 248, in handler
await self.close()
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 766, in close
await self.write_close_frame(Close(code, reason))
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 1232, in write_close_frame
await self.write_frame(True, OP_CLOSE, data, _state=State.CLOSING)
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 1205, in write_frame
await self.drain()
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 1194, in drain
await self.ensure_open()
File "/usr/local/lib/python3.9/site-packages/websockets/legacy/protocol.py", line 935, in ensure_open
raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: sent 1000 (OK); no close frame received
INFO:     connection close

same issue here

Hey, @sandeepsingh
Please, create an issue according to the issue template. There's not much information that I can help you with in this issue.

same issue


fix: ssl use cache

Please answer these questions before submitting a pull request

Why submit this pull request?

[x] Bugfix

[ ] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues

Bugfix

Description
Fix: https://github.com/apache/apisix-ingress-controller/issues/179

@gxthrj The unit test cases failed.

@gxthrj The unit test cases failed.

Codecov Report

Merging #203 (7eeb37f) into master (b7fa57e) will increase coverage by 0.93%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##           master     #203      +/-   ##
==========================================
+ Coverage   44.61%   45.54%   +0.93%
==========================================
  Files          32       32
  Lines        2024     2033       +9
==========================================
+ Hits          903      926      +23
+ Misses        982      971      -11
+ Partials      139      136       -3

Impacted Files
Coverage Δ

pkg/apisix/cluster.go
35.21% <66.66%> (+6.30%)
:arrow_up:

pkg/apisix/ssl.go
41.44% <100.00%> (+2.40%)
:arrow_up:

pkg/ingress/apisix/tls.go
92.30% <100.00%> (+0.30%)
:arrow_up:

pkg/seven/state/solver.go
1.98% <0.00%> (-1.99%)
:arrow_down:

pkg/apisix/cache/memdb.go
67.27% <0.00%> (+0.90%)
:arrow_up:

pkg/apisix/route.go
41.72% <0.00%> (+1.98%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #203 (7eeb37f) into master (b7fa57e) will increase coverage by 0.93%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##           master     #203      +/-   ##
==========================================
+ Coverage   44.61%   45.54%   +0.93%
==========================================
  Files          32       32
  Lines        2024     2033       +9
==========================================
+ Hits          903      926      +23
+ Misses        982      971      -11
+ Partials      139      136       -3

Impacted Files
Coverage Δ

pkg/apisix/cluster.go
35.21% <66.66%> (+6.30%)
:arrow_up:

pkg/apisix/ssl.go
41.44% <100.00%> (+2.40%)
:arrow_up:

pkg/ingress/apisix/tls.go
92.30% <100.00%> (+0.30%)
:arrow_up:

pkg/seven/state/solver.go
1.98% <0.00%> (-1.99%)
:arrow_down:

pkg/apisix/cache/memdb.go
67.27% <0.00%> (+0.90%)
:arrow_up:

pkg/apisix/route.go
41.72% <0.00%> (+1.98%)
:arrow_up:

Continue to review full report at Codecov.

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

@gxthrj Conflict again.

@gxthrj Conflict again.


Placement information is sometimes not available

Hello.
Sometimes I dont get information about a teams placement. Is there any fix?

Thanks!

(addition)
The placements arent available for the places 1-14

If you leave before the game is finished, we obviously dont know the placements of the remaining players at that point.
If that isnt the case, please share the replay and I can have a look to see where it goes wrong.
Placement is coming from FortPlayerStateAthena if you want to debug it yourself:
https://github.com/Shiqan/FortniteReplayDecompressor/blob/master/src/FortniteReplayReader/Models/NetFieldExports/FortPlayerState.cs#L119-L120

Hey again.
Thanks for your response!
I got first place in this replay, so I was the last one alive.
Here is the replay file: Uploading UnsavedReplay-2024.03.23-15.18.05.zip…

Hey again.
Thanks for your response!
I got first place in this replay, so I was the last one alive.
Here is the replay file:
UnsavedReplay-2024.03.23-15.18.05.zip

Had a quick look, and they are indeed not there🤔
Cant see anything going wrong either, but something could be failing silently...
Would have to see what changed in the recent UE builds.

Would be amazing if you could check this!
Please let me know if you got more informations!
Have a great easter festival!

He, if you play this play in replay in Fortnite, does it include the end?
It almost feels like it is straight up missing the last chunk(s) of the replay.
If I log all events for your user (for FortPlayerStateAthena, coming in on channel 213 if you want to have a look yourself) I barely get anything after the initial values. Only that you were bInAircraft,  bThankedBusDriver (important 👍) and bHasEverSkydivedFromBus, followed by bHasEverSkydivedFromBusAndLanded and then the 2 kills you had early on (updated on TeamKillScore and KillScore). After that, nothing but CompressedPing events until the very end...

Thank you for taking the time to help me!
I'm gonna try another replay, where I got first place to see, if its maybe corrupted!


Add verify register by email

Sending emails using queue.

Implement enhancement with sending activation email, added api call:
POST /register/verify Verify user's email


return usage in disposing block's is flawed and we need to revist.

use @pony_exitcode[None](code: I32)

class Disposble
  var _exit_code: I32

  new create() =>
    _exit_code = 0

  fun ref set_exit(code: I32) =>
    _exit_code = code

  fun dispose() =>
    @pony_exitcode(_exit_code)

actor Main
  new create(env: Env) =>
    with d = Disposble do
      d.set_exit(10)
      return
    end

was done as a validation test for "with disposable block" tests but as we see in #4036.

This example program creates a compiler crash:
use @pony_exitcode[None](code: I32)

class Disposble
  var _exit_code: I32

  new create() =>
    _exit_code = 0

  fun ref set_exit(code: I32) =>
    _exit_code = code

  fun dispose() =>
    @pony_exitcode(_exit_code)

actor Main
  new create(env: Env) =>
    with d = Disposble do
      d.set_exit(10)
      return
    end
    let x = "foo"

with doesn't create a scope right now, which may or not be correct. We should revisit that thinking as part of this review.

If the with is in a conditional block like if then this (having a return inside the with) should be a valid thing to do.
But without the conditional it is nonsensical.

with shouldn't create a scope.

I think I have a small change for expr_return that would address the issue we found @jemc. It would change so that the with-return test is an error case.
diff --git a/src/libponyc/expr/control.c b/src/libponyc/expr/control.c
index 72f3f255..146d9906 100644
--- a/src/libponyc/expr/control.c
+++ b/src/libponyc/expr/control.c
@@ -444,6 +444,14 @@ bool expr_return(pass_opt_t* opt, ast_t* ast)
     return false;
   }

+  if(ast_id(parent) == TK_DISPOSING_BLOCK)
+  {
+    ast_print(parent, 80);
+    ast_error(opt->check.errors, ast,
+      "use return only to exit early from a disposing block, not at the end");
+    return false;
+  }
+
   ast_t* type = ast_childidx(opt->check.frame->method, 4);
   ast_t* body = ast_child(ast);


Fix missing update (from PR #508)

What changes does this PR introduce?
Changes from PR #538 in ecco_readparms.F dropped the update from PR #508.
Put them back in.
What is the current behaviour?
Problem in ecco_readparms.F (missing updated from PR #508 that got removed by PR #538).
What is the new behaviour
fix
Does this PR introduce a breaking change?
Other information:
Suggested addition to tag-index
none if merged after PR #538

Looks like a straightforward fix. LGTM.

GOing to merge it before the end of the day.


called Result::unwrap() on an Err value: TryFromSliceError(())

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (b51c057 2024-01-18T00:23:54.396010000Z)
What command(s) is the bug in?
forge script script/DeployAll.s.sol:DeployAll --rpc-url $RPC_URL --private-key $PRIVATE_KEY --broadcast --slow -vvv
Operating System
macOS (Apple Silicon)
Describe the bug
Script ran successfully.

## Setting up 1 EVM.
The application panicked (crashed).
Message:  called `Result::unwrap()` on an `Err` value: TryFromSliceError(())
Location: /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alloy-primitives-0.6.0/src/bits/address.rs:45

This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
/bin/sh: line 1: 32126 Abort trap: 6           FOUNDRY_PROFILE=stg forge script script/DeployAll.s.sol:DeployAll --rpc-url $RPC_URL --private-key $PRIVATE_KEY --broadcast --slow -vvv
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Could you provide a repro for this? it's hard to look into otherwise

I cannot find any panics in the logged files, so without a backtrace or repro this issue is not actionable. Feel free to reopen if you can provide anything.


Update node.js.yml

this change allows manual execution (authorizations provided) of the node.js CI

test failures not related to this change but to https://github.com/SAP-samples/cap-sflight/issues/841


Handling of parameters with integer values

Treating integer-valued parameters as floats can be sub-optimal for the maximization procedure. This is discussed in https://arxiv.org/abs/1706.03673, where the authors have shown that accounting for the integer nature of some parameters can lead to faster convergence (see for example their figure 3). Given that optimizing the machine learning hyperparameters involves many times integer parameters, I think it is a worthwhile problem.
The same paper proposes a simple way of dealing with integer parameters with minimal changes to the code. For backward compatibility, the simplest way to implement the changes would be to add an extra dictionary where you specify the integer variables (if no such dictionary is given, then all are assumed to be floats).
Is this a change worth considering? If so, I can give it a try and implement it as a pull request.

Have you read this example, item 2:
https://github.com/fmfn/BayesianOptimization/blob/master/examples/advanced-tour.ipynb
?
If so, how would what you propose differ? (sorry, I haven't read the paper!)

I saw the example in the advanced tour. The idea is that if you know a parameter is an integer then the Bayesian Optimizer can find the maximum faster (i.e achieve convergence in a smaller number of samples) than if you were to treat that parameter as a float.
The quickest would be to have an extra list or dictionary where you specify all the integer parameters. Then, when you calculate the Gaussian Process value for a point in parameter space, you round to integer values all the parameters that are defined as integers. The paper I pointed to claims that this extra step, which has minimal computation overhead, should speed up finding the maximum.
The idea is that if you have an integer parameter and you know the value of your black-box function at n and n+1, then you know the value of that function in the interval [n,n+1]. If you treat that parameter as a float, then even if you know the value of the function at n and n+1, your function still has the freedom to take a different value (within the dispersion of the fitted Gaussian Process) in the (n,n+1) interval. This means that you know less information than in the case of an integer parameter. This is why implementing integer parameters can speed up finding the maximum.

Certainly sounds interesting. I was wondering how this works with the acquisition function and I think their figure 1 explains that very nicely. I guess you saw my reply on your other proposal that pull requests will likely take quite some time. But I think many people would be interested in the ability to better handle integers, especially if you can replicate some of these results showing aster convergence.

I've had a closer look at categorical/integer parameters and it shouldn't be too hard to implement. The only thing that is unclear to me is how the acquisition function will be maximized -- finding extrema of mixed value functions is a nontrivial problem. In Garrido-Merchan/Hernandez-Lobato there's no mention of a specific method used to find the maximum, as far as I can tell. If anyone has suggestions as to how to solve this sub-problem, I would be interested.

@till-m - should we close this for now given the issue in 430?

Implemented in #531 and published as a beta release, version 3.0.0b1. If someone is working on problems using typed optimization, I would love some getting some feedback from beta testers. :)


Add LTS 18.18 with latest freckle-app

This version of freckle app contains frame-embedding denial middleware that we'd
like to use across our APIs. Middleware was added in this PR and more info
can be found therein.
LTS Updates seem to be mostly focused around aeson 2.0 support,
bounds relaxing and hashable 1.4 support.

Suggestion: upgrade<EMAIL_ADDRESS>to newer Hackage version <IP_ADDRESS>
Suggestion: upgrade<EMAIL_ADDRESS>to newer Hackage version 2.9.2
Suggestion: upgrade<EMAIL_ADDRESS>to newer Hackage version 2.9.2
Suggestion: upgrade<EMAIL_ADDRESS>to newer Hackage version <IP_ADDRESS>
Suggestion: remove<EMAIL_ADDRESS>(Stackage has version 1.39.0)
Suggestion: upgrade<EMAIL_ADDRESS>to newer Hackage version 1.40.2
Suggestion: remove<EMAIL_ADDRESS>(Stackage has version <IP_ADDRESS>)
Suggestion: upgrade<EMAIL_ADDRESS>to newer Hackage version <IP_ADDRESS>

(Yes, I decided to work on a tool to find these things)
For dhall and generic-lens I would go with removal instead of updating.

@pbrisbin can do! Just out of curiosity, how do you get the package SHAs?
I was updating a random project to reference it and taking whatever it generated. Is there a better way?

That's the only way, but bin/check is there to help. It's mentioned in the README.


fix/Only update CORS on resources which have an OPTIONS method

Description
Don't try to modify the OPTIONS methods on resources which don't have one
GitHub Issues
https://github.com/Miserlou/Zappa/issues/1035

Coverage remained the same at 74.062% when pulling 7813d85556157e9f3f80f50fa29fa057857bf362 on jakul:fix/cors-support-for-apis-with-extra-methods into a21c9733eb82725f178190b75918cc810a9bc613 on Miserlou:master.

@eely22 FYI

Thanks! Definitely not something we have tried (or even knew people did) so thanks for catching that corner case.


Finetuning commands for other glue tasks

HI,
Can you share what finetuning commands you used for other glue tasks? Did you use the same warmup, hyperparameters etc as for the example MRPC command you shared?

Authors have sweeped the parameters for the tasks (you can check Table 7 of the paper).
Hope it helps.


[3.0]Registry configuration is not required

What is the purpose of the change
resolve #3604
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8032 (e7b0d49) into 3.0 (f07640f) will decrease coverage by 0.24%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##                3.0    #8032      +/-   ##
============================================
- Coverage     60.84%   60.60%   -0.25%
  Complexity      312      312
============================================
  Files          1068     1068
  Lines         44718    44724       +6
  Branches       6679     6677       -2
============================================
- Hits          27209    27103     -106
- Misses        14512    14625     +113
+ Partials       2997     2996       -1

Impacted Files
Coverage Δ

...in/java/org/apache/dubbo/config/ServiceConfig.java
61.51% <ø> (ø)

.../apache/dubbo/config/bootstrap/DubboBootstrap.java
69.06% <65.38%> (-0.28%)
:arrow_down:

...g/apache/dubbo/config/AbstractInterfaceConfig.java
86.84% <100.00%> (+1.62%)
:arrow_up:

...a/org/apache/dubbo/rpc/filter/AccessLogFilter.java
25.00% <0.00%> (-44.74%)
:arrow_down:

...va/org/apache/dubbo/rpc/support/AccessLogData.java
53.16% <0.00%> (-37.98%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
76.92% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
43.47% <0.00%> (-15.22%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-13.80%)
:arrow_down:

.../remoting/transport/netty4/NettyServerHandler.java
61.36% <0.00%> (-9.10%)
:arrow_down:

... and 24 more

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 f07640f...e7b0d49. Read the comment docs.


Correctly cache "COPY --from"

Ref #72
Code is from @bpaquet

I thought of a cleaner way. Trying that first.

Going with #279


Links index is too wide

Links index page is too wide for mobile.
Achievements is okay but check it too in case.

https://github.com/loftwah/linkarooie/pull/84


[airflow]: extend removed method class attributes and more methods (AIR302)

Summary
Airflow 3.0 removes various deprecated functions, members, modules, and other values. They have been deprecated in 2.x, but the removal causes incompatibilities that we want to detect. This PR add rules for the following.

Removed class attribute

airflow.providers_manager.ProvidersManager.dataset_factories → airflow.providers_manager.ProvidersManager.asset_factories
airflow.providers_manager.ProvidersManager.dataset_uri_handlers → airflow.providers_manager.ProvidersManager.asset_uri_handlers
airflow.providers_manager.ProvidersManager.dataset_to_openlineage_converters → airflow.providers_manager.ProvidersManager.asset_to_openlineage_converters
airflow.lineage.hook.DatasetLineageInfo.dataset  → airflow.lineage.hook.AssetLineageInfo.asset

Removed class method (subclasses in airflow should also checked)

airflow.secrets.base_secrets.BaseSecretsBackend.get_conn_uri → airflow.secrets.base_secrets.BaseSecretsBackend.get_conn_value
airflow.secrets.base_secrets.BaseSecretsBackend.get_connections → airflow.secrets.base_secrets.BaseSecretsBackend.get_connection
airflow.hooks.base.BaseHook.get_connections → use get_connection
airflow.datasets.BaseDataset.iter_datasets → airflow.sdk.definitions.asset.BaseAsset.iter_assets
airflow.datasets.BaseDataset.iter_dataset_aliases → airflow.sdk.definitions.asset.BaseAsset.iter_asset_aliases

Removed constructor args (subclasses in airflow should also checked)

argument filename_template inairflow.utils.log.file_task_handler.FileTaskHandler
in BaseOperator

sla
task_concurrency → max_active_tis_per_dag

in BaseAuthManager

appbuilder

Removed class variable (subclasses anywhere should be checked)

in airflow.plugins_manager.AirflowPlugin

executors (from #43289)
hooks
operators
sensors

airflow.hooks.base_hook.BaseHook → airflow.hooks.base.BaseHook

Test Plan

A test fixture is included in the PR.

@MichaReiser, Pinging in case we missed this one 🙂 Would be awesome if we could get this re-reviewed when bandwidth allowed. Thanks a lot!

Thank you!
I've a few minor nits but I can't push it to this branch, I'll create a follow-up PR instead.

Thanks a ton! Not sure why you cannot push to this branch 😢 I read through the refactor PR. Everything looks much better! But I noticed there one minor typo and created a PR for this fix https://github.com/astral-sh/ruff/pull/15211


Maintain Github Pages for Hera

Describe the current situation / your motivation for the change
The by Github Pages generated Website is currently just a reflection of the README.md file on the repository root of the master branch.
Describe the solution you'd like
By creating a custom page we could provide a styled command overview for users, without them needing to visit the repository itself which can be quite confusing for non programmers.
Additional context
URL to existing page: https://chromeroni.github.io/Hera-Chatbot/

index.html already created.
It contains a html version of the README.md file converted with https://dillinger.io/.
The converter created css too, but its quite a mess, thus i suggest removing all css and writing it on your own.

Styles are now implemented.
The help command can now be updated to use this site as a command reference.
Still thinking about including a link to Heras main discord server

Page is now finished and all affected comands are updated.
Visit the page here: https://chromeroni.github.io/Hera-Chatbot/


Controllers interface

Implemented a method interface to initialize all test controllers (Jira issue: https://issues.redhat.com/browse/RHDP-444) and replaced the existing references to them with the new framework.
Moved pkg/tests to the root, api clients to apis/ and created the constants/ folder to avoid import cycles.
Updated the readme file with the new changes.

/ok-to-test

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e


inverse relations not asserted as such - s-depends

From<EMAIL_ADDRESS>on June 27, 2012 18:55:02
"specifically depends on at some time" hierarchy should be asserted as inverse of "has specifically dependent at some time" At the moment only top-level relations are. (I would expect "has function at all times" to be inverse of "function of at all times" for example)
Original issue: http://code.google.com/p/bfo/issues/detail?id=74

From<EMAIL_ADDRESS>on June 27, 2012 20:46:08
Fixed in the most recent checkin.
Regarding "(I would expect "has function at all times" to be inverse of "function of at all times" for example)" this is not the case - see https://code.google.com/p/bfo/issues/detail?id=49#c2

From<EMAIL_ADDRESS>on June 27, 2012 20:51:04
propose that this be closed as fixed

From<EMAIL_ADDRESS>on June 28, 2012 09:48:24
Could you give me an example for https://code.google.com/p/bfo/issues/detail?id=49#c2? I have trouble understanding the issue as it is, and I think this may make cause me to generate invalid tracker items :)

From<EMAIL_ADDRESS>on June 28, 2012 20:07:41
See recently added https://code.google.com/p/bfo/issues/detail?id=73#c8

From<EMAIL_ADDRESS>on June 29, 2012 13:19:34
Status: Fixed


Allow admin password to be set prior to install

Right now the admin password is set to a default. It would be nice if you could override the default with a docker parameter, or something.

This is already a feature, I just forgot I had added it. The dockerfile allows you to set an admin password template variable.


Added jsonGet support to template_funcs

I added support for getting values for properties inside a JSON value.
I find it useful when I store large JSON structures.
Example from docs/templates.md
{{jsonGet (getv "/test/data/") "animals.0.name"}}
{{ $animal := jsonGet (getv "/test/data/") "animals.1"}}
type: {{ $animal.type }}
name: {{ $animal.name }}
{{range jsonGet (getv "/test/data/") "animals.*.name"}}
{{.}}
{{end}}

LTGM!

on second thought, https://github.com/kelseyhightower/confd/blob/master/docs/templates.md#json accomplishes the same thing.

Yes, you are right, I guess I should have read the go templates doc a bit more :)


831 - Isolate solution images.

Type of PR

Documentation changes

Purpose
Moving images from parent folder to solution specific folder to isolate solution changes.
Does this introduce a breaking change? If yes, details on what can break
No
Author pre-publish checklist
[X ] Made corresponding changes to the documentation
Validation steps
Verify all images in E2E Sample documentation reference valid files.
Issues Closed or Referenced

Closes #831
References #888

Normally, I wouldn't create this PR direct to main, but for some reason the intermediate branch was not working on my computer, so I took a shortcut and went direct to main.

@ydaponte - That's interesting, because the preview works just fine. I'll have to dig into the linkspector to figure out how it is resolving the link and failing.

@bsherwin the link inspector is raising issues on all the links - I think you need to change either the way the path is built or change the configuration on the linkinspector.yml: https://github.com/UmbrellaDocs/linkspector?tab=readme-ov-file#directories-to-search

@ydaponte...the "directories to search" is a configuration of where to look for markdown files. I think the problem was the "?raw=true" on the end of the image links. Anyway...they are all clear now. Please review and approve.

@bsherwin - you are still requesting to merge to main. Can you change to the feature branch please?

Sure...I'll just redo this.


Issue with named instances

Hi,
I am having issues with running migrations on from/to named instances.
For example, if I run:
Copy-SqlLinkedServer -Source server\instance -Destination server\instance2
I get the following error:
WARNING:  could not be added to server\instance
WARNING: Reason: System.Management.Automation.RuntimeException: The regular expression pattern 'server\instance' is not valid. ---> System.ArgumentException: parsing "'server\instance'" - Unrecognized escape sequence \i.
at System.Text.RegularExpressions.RegexParser.ScanCharEscape()
at System.Text.RegularExpressions.RegexParser.ScanBasicBackslash()
at System.Text.RegularExpressions.RegexParser.ScanRegex()
at System.Text.RegularExpressions.RegexParser.Parse(String re, RegexOptions op)
at System.Text.RegularExpressions.Regex..ctor(String pattern, RegexOptions options, TimeSpan matchTimeout, Boolean useCache)
at System.Text.RegularExpressions.Regex..ctor(String pattern, RegexOptions options)
at System.Management.Automation.ParserOps.NewRegex(String patternString, RegexOptions options)
at System.Management.Automation.ParserOps.ReplaceOperator(ExecutionContext context, IScriptExtent errorPosition, Object lval, Object rval, Boolean ignoreCase)
--- End of inner exception stack trace ---
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
at lambda_method(Closure , Object[] , StrongBox`1[] , InterpretedFrame )

Hey @demyte,
Thanks for reporting an issue. This issue was addressed in a previous version. Please update to the latest one and let me know if you continue to have issues.

I updated today using the "Invoke-Expression (Invoke-WebRequest https://git.io/vn1hQ)" method which from what I can see replaces all the old files.
Is that the correct method?

Hi @ctrlbold
I think it must have had the files loaded in a session somewhere, I updated and then closed down all my sessions ISE/Prompts etc and it is now working.
Thanks for the quick response :)


Does v5 work yet with Redux?

I "upgraded" to react-router v4 today, then realized it doesn't work with react-router-redux v4 (ouch). Trying v5-alpha and redux store.dispatch(push) doesn't seem to worker yet either?
Version
5.0.0-alpha.6
Test Case
store.dispatch(push('/foo')); (see below)
Steps to reproduce
Expected Behavior
Navigation to occur.
Actual Behavior
Nothing happens.
import React from 'react';
import ReactDOM from 'react-dom';
import { Provider, connect } from 'react-redux';
import { createStore, combineReducers } from 'redux';
import { ConnectedRouter, push, routerReducer } from 'react-router-redux';
import { Route, Link } from 'react-router-dom';
import createHashHistory from 'history/createHashHistory';

import './test_router.less';

const Header = (props) => (

    <Link to="/foo">Foo</Link>
    <Link to="/bar">Bar</Link>

    <button onClick={ props.nav.bind(null, '/foo') }>Foo</button>

);

const Foo = () => (

Foo

);

const Bar = () => (

Bar

);

const HeaderWithRedux = connect(
  (state, ownProps) => ({
    // No-op.
  }),
  (dispatch, ownProps) => ({
    nav: (path) => {
      console.log('Nav:', path);
      dispatch(push(path));
    }
  })
)(Header);

const store = createStore(
  combineReducers({
    routing: routerReducer
  })
);

const history = createHashHistory();

const Root = () => (
  <Provider store={ store }>
    <ConnectedRouter history={ history }>

        <HeaderWithRedux/>
        <Route path="/foo" component={ Foo }/>
        <Route path="/bar" component={ Bar }/>

    </ConnectedRouter>
  </Provider>
);

ReactDOM.render(Root(), document.getElementById('app-root'));

setTimeout(() => {
  // Doesn't work.
  store.dispatch(push('/foo'));
}, 5000);

You have to hook up the middleware.


[HUDI-1538] Try to init class trying different signatures instead of checking its name

What is the purpose of the pull request
UtilHelpers.createSource had a hardcoded way of checking which
constructor signature needs to be used to instantiate a class
which makes it impossible to override those hardcoded classes outside of Hudi
and use them instead as their signature remains the same.
Verify this pull request
This pull request is a trivial rework / code cleanup without any test coverage.

@yanghua This is a new PR that is based on not diverted master branch.

@yanghua This is a new PR that is based on not diverted master branch.

Codecov Report

Merging #2476 (d504a97) into master (048633d) will decrease coverage by 0.32%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #2476      +/-   ##
============================================
- Coverage     50.17%   49.84%   -0.33%
+ Complexity     3050     2989      -61
============================================
  Files           419      413       -6
  Lines         18931    18545     -386
  Branches       1948     1930      -18
============================================
- Hits           9498     9244     -254
+ Misses         8657     8541     -116
+ Partials        776      760      -16

Flag
Coverage Δ
Complexity Δ

hudicli
37.21% <ø> (ø)
0.00 <ø> (ø)

hudiclient
100.00% <ø> (ø)
0.00 <ø> (ø)

hudicommon
51.49% <ø> (+0.02%)
0.00 <ø> (ø)

hudiflink
0.00% <ø> (ø)
0.00 <ø> (ø)

hudihadoopmr
33.16% <ø> (ø)
0.00 <ø> (ø)

hudisparkdatasource
65.85% <ø> (ø)
0.00 <ø> (ø)

hudisync
48.61% <ø> (ø)
0.00 <ø> (ø)

huditimelineservice
?
?

hudiutilities
69.46% <100.00%> (+0.03%)
0.00 <1.00> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...in/java/org/apache/hudi/utilities/UtilHelpers.java
64.53% <100.00%> (+0.37%)
32.00 <1.00> (-1.00)
:arrow_up:

...udi/timeline/service/handlers/BaseFileHandler.java

...apache/hudi/timeline/service/handlers/Handler.java

.../apache/hudi/timeline/service/TimelineService.java

...udi/timeline/service/handlers/TimelineHandler.java

...e/hudi/timeline/service/FileSystemViewHandler.java

...di/timeline/service/handlers/FileSliceHandler.java

...e/hudi/common/table/log/HoodieLogFormatWriter.java
79.68% <0.00%> (+1.56%)
26.00% <0.00%> (ø%)

Codecov Report

Merging #2476 (d504a97) into master (048633d) will decrease coverage by 0.32%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #2476      +/-   ##
============================================
- Coverage     50.17%   49.84%   -0.33%
+ Complexity     3050     2989      -61
============================================
  Files           419      413       -6
  Lines         18931    18545     -386
  Branches       1948     1930      -18
============================================
- Hits           9498     9244     -254
+ Misses         8657     8541     -116
+ Partials        776      760      -16

Flag
Coverage Δ
Complexity Δ

hudicli
37.21% <ø> (ø)
0.00 <ø> (ø)

hudiclient
100.00% <ø> (ø)
0.00 <ø> (ø)

hudicommon
51.49% <ø> (+0.02%)
0.00 <ø> (ø)

hudiflink
0.00% <ø> (ø)
0.00 <ø> (ø)

hudihadoopmr
33.16% <ø> (ø)
0.00 <ø> (ø)

hudisparkdatasource
65.85% <ø> (ø)
0.00 <ø> (ø)

hudisync
48.61% <ø> (ø)
0.00 <ø> (ø)

huditimelineservice
?
?

hudiutilities
69.46% <100.00%> (+0.03%)
0.00 <1.00> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...in/java/org/apache/hudi/utilities/UtilHelpers.java
64.53% <100.00%> (+0.37%)
32.00 <1.00> (-1.00)
:arrow_up:

...udi/timeline/service/handlers/BaseFileHandler.java

...apache/hudi/timeline/service/handlers/Handler.java

.../apache/hudi/timeline/service/TimelineService.java

...udi/timeline/service/handlers/TimelineHandler.java

...e/hudi/timeline/service/FileSystemViewHandler.java

...di/timeline/service/handlers/FileSliceHandler.java

...e/hudi/common/table/log/HoodieLogFormatWriter.java
79.68% <0.00%> (+1.56%)
26.00% <0.00%> (ø%)

Can anybody merge this PR, please?

Can anybody merge this PR, please?


Add some elements for CEP

Add Cep Dispatcher

It seems this pull request is based on an outdated version of JASM. In particular, the code in Component.java has evolved quite a bit (sending a message is now implemented into the port). Please sync and re-submit a pull request. Now the code is stable and I won't refactor it for a while.


qt: Move SplashFinished to after ClientModel/WalletModel creation

With a large wallet there was a noticable gap between hiding of the
splash and showing the main window.

utACK