EFLOW deployment failing

Describe the Problem
Hi Team,
I followed this document to deploy but having couple of issues as follows:

After following steps it installed Azure IoT Edge msi on my windows which i am unable to uninstall.
Provisioned failed and not able to connect to VM whenever i try to connect i am getting below error
ERROR: 0x80072741

Windows Host OS (please complete the following information):
Edition	Windows 10 Enterprise
Version	20H2
Installed on	12/17/2021
OS build	19042.1706
Experience	Windows Feature Experience Pack 120.2212.4170.0

Hi @techipank,
Thanks for your update - We will try to repro your issue. In the meantime, you can uninstall using the Windows troubleshooter.
Please let me know if that works for you.
Thanks,
Francisco

Hi @fcabrera23 ,
Thanks for the info but Windows troubleshooter doesn't help and it completed with below screenshot:

Hi @techipank,
What's the error when you try uninstalling from Apps list?  Can you try the following steps:

Download Microsoft Program Install and Uninstall
Run the downloaded tool
Select Next and wait for the problem detection to end
Select Uninstalling
Wait for problem detection ends (can take some minutes)
Select Azure IoT Edge LTS from the list
Select Yes, try uninstall and wait for the uninstallation to finish

Hi @fcabrera23 ,
I did the same thing only but for me Step 4,5,6,7 is not coming after 3rd step i got the above screenshot.

what i did is Stop-eflowVm and Start-eflowvm and it worked again.


Via: Change separator character to '-' instead of ' '.

To avoid future compatibility issues with plugins and origins that parse the VIA header, the protocol stack should be a single space delimited value rather than a variable number.

it looks good.

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/497/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/492/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/749/


Add SVG language mode

This has been mentioned in https://github.com/Microsoft/vscode/issues/375, would be great to see it happen in .svg and .html files.

Looking at the code, the first step towards this is probably to factor out XML-only logic from the HTML code to XML (closing tags, tokenizing, etc.) and have HTML extend that. SVG can then extend XML in the same way HTML does.

Would be nice to also add svg support to html

Try this extension: https://marketplace.visualstudio.com/items?itemName=jock.svg
It contributes a new svg language mode and basic completion support for svg files


upload jars from Travis CI to Maven

P.S. This assumes that there are 2 env variables configured in Travis:

$sonatypeUsername
$sonatypePassword

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Checklist

[ ] Checkstyle and unit tests pass locally with my changes by running gradle check chrome htmlunit command
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Coverage remained the same at 66.832% when pulling dca5a7a135583076ce3423d4653b8dccaa9fa9cb on deploy-jars-from-travis-to-maven into ad4557c37d9b0df153e5bd8d4c0cd62320d77dac on master.

Codecov Report

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

@@            Coverage Diff            @@
##             master     #742   +/-   ##
=========================================
  Coverage     63.56%   63.56%
  Complexity      878      878
=========================================
  Files           154      154
  Lines          3030     3030
  Branches        298      298
=========================================
  Hits           1926     1926
  Misses         1005     1005
  Partials         99       99

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 ad4557c...dca5a7a. Read the comment docs.

Obsolete


Support for Threaded Comments

When you use Set-CellComment it created a note rather than a threaded comment. I've looked through the documentation but I can't seem to find a reason for this. Is it just that there is no support for threaded comments currently?
It looks like EPPlus has this functionality: https://github.com/EPPlusSoftware/EPPlus/wiki/Threaded-comments

Thank you for the issue. The link is for the EPPlus which I don’t support. It requires a paid license. The version I do use may not support this feature.

Those methods were not fixed in the version used in ImportExcel.
You're free to use VBA. I believe Excel has to be running to execute it. ImportExcel works only on creating/reading the xlsx.
I have some examples of creating VBA with the model, but I did not got down that rabbit hole too far.


Deploy Checklist: Expensify.cash 2021-05-22

Release Version: 1.0.52-0
Compare Changes: https://github.com/Expensify/Expensify.cash/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/Expensify.cash/pull/2810
[x] https://github.com/Expensify/Expensify.cash/pull/2818
[x] https://github.com/Expensify/Expensify.cash/pull/3061
[x] https://github.com/Expensify/Expensify.cash/pull/3067
[x] https://github.com/Expensify/Expensify.cash/pull/3069
[x] https://github.com/Expensify/Expensify.cash/pull/3077

cc @Expensify/applauseleads

Starting QA 🚀

Regression is finished!
We were able to reproduce this issue today https://github.com/Expensify/Expensify.cash/issues/3094
No issues found.
PRs are finished too
No comments added.
Thanks

:shipit:


Manually Releasing Individual Repos does not use collaborators

When manually releasing repositories using the Graphical interface, Classy automatically defaults to not using collaborators, even when explicitly set.
This is due to the UI code being hard coded to not use the collaborators flag.
The "Release all" button and the scheduler does not have this problem.

Addressed in: 0ddd912e6fcb79c77e5b33de5625e01638038e52
Closed.


Fix inconsistent use of checksumAlgorithm

When creating new System Metadata records, this package is sometimes using a checksumAlgorithm of SHA1 and sometimes SHA-1. This is technically valid but, in reality, probably a bad thing. Also see https://github.nceas.ucsb.edu/KNB/arctic-data/issues/283 as it relates to the issue there.

Find the right way to write algorithm names
Change the relevant sections of code to reflect that change

this was fixed in PR #175


SDK with support for python 3

I was wondering if there is already support for python 3.
I have worked on making the changes necessary to support an older version of the SDK on python 3 and was considering sharing my version but if there is no support I could create a python3 branch and contribute the changes?

Dear VathsalaAchar,
yes, we don't have any support yet for Python 3, so it would be great if you would be willing to contribute a pull request for python 3 support.
Ideally the new version supports both Python 2 and 3 so that we have to maintain only a single version - but not sure how this works out for this module, what do you think about this?

@VathsalaAchar,
just for clarification: Even if it would be a separate branch, it would still be interesting to have Python 3 support. At this point having a single codebase it is nice-to-have. If we have separate versions for python 2 and 3 we could still merge them in future.

Hi @andrehacker .
Sorry for getting back to you so late, I've been away for a few weeks.
Yes I'll work on a separate branch first and then we can see if it would be feasible to have a single version.

Hi,
I did a similar job as @VathsalaAchar but my PR #6  supports both Python 2 and 3.

Hi @expobrain and @VathsalaAchar,
thanks a lot for your pull requests, and sorry @VathsalaAchar for the delay. We will review the pull requests the next days asap. BTW: I almost finished a new travis config which will enable you to test your forks and pull requests (currently both will always fail).
Best

Is Python3 supported now?

JFYI, python 3.6+ is supported in pyexasol: https://github.com/badoo/pyexasol

Python 3 is now supported after merging #10 (@Ashafix) based on #6 (@expobrain).


Add IF-native CSV exporter

Story
As a user I want to be able to export my ompl data to CSV without having to spawn a shell model
Rationale
We currently have a CSV model implemented as a Python script accessible via the shell, but it makes sense for this to be a core piece of infrastructure that comes bundled in IF or if-models.
Implementation details

add a csv-exporter model plugin
the model should receive an ompl as an argument
the model should traverse the entire yaml file and ad each piece of data to its own row in a csv
each row should include the field name and contents
each row should have a unique identifier structured as the yaml path to the data, e.g. graph.children.child1.1.timestamp
csv data is dumped to a file, with the savepath being defined as a model arg

Priority
2/5
Scope
All changes should be confined to a model plugin and therefore not affect any IF code
Size
1 day
What does "done" look like?
A model plugin exists that converts an ompl toa csv file
Unit tests exist, giving 100% coverage, and they pass.
Does this require updates to documentation or other materials??
Requires documentation int he form of a model README
What testing is required?
Unit tests
Is this a known/expected update?
Discussed several times in several contexts over past weeks

each row in the csv should have a unique identifier defining the location in the graph. It makes sense for the ID to be the yaml path to the data, e.g.
id = graph.children.child1.0.carbon
id = graph.children.child1.1.carbon
id = graph.children.child1.1.timestamp
etc etc
In theory this should enable roundtripping from impl -> csv -> impl

Discussion with @jmcook1186 makes sense to add into https://github.com/Green-Software-Foundation/if-unofficial-models.

HI @perkss when you are ready to work on this let us know and we'll arrange a more detailed scoping call (cc @narekhovhannisyan )

@gnanakeethan to sketch out a design

Hi @perkss any update on this?

Ok plan to start on this this week. Hold up for admin reasons.

Have a phase one implementation same as what the python exporter does without the join part at this time. https://github.com/perkss/if-unofficial-models/tree/csv-exporter-issue-298
its not clear what is the best test input to use. @jmcook1186 maybe you could provide an example after checking the branch I have added test cases for the input data. The concept of id wasnt set in the default projection list of it simply takes the inputs and writes as outputs. Is this still relevant?

each row in the csv should have a unique identifier defining the location in the graph. It makes sense for the ID to be the yaml path to the data, e.g.
id = graph.children.child1.0.carbon id = graph.children.child1.1.carbon id = graph.children.child1.1.timestamp
etc etc
In theory this should enable roundtripping from impl -> csv -> impl

Chatted with @pazbardanl on this.
@jmcook1186 on this specifically there is no reference to the to anything in the yaml except the inputs
Therefore on the configure and execute calls to the model we cannot know what the graph.children name is.
For example I tried with this and only the inputs are sent on the execute.
A suggestion is to provide as config to the model a prefix identifier. Then we can have the prefix.[index].paramname
graph:
  children:
    child:
      pipeline:
        - csvexport
      config:
        csvexport:
          output-path: example.csv
      inputs:
        - timestamp: 2023-07-06T00:00
          duration: 3600
          energy: 5
          operational-carbon: 5
          embodied-carbon: 0.02
          requests: 100

Current state of this to me is will now be replaced by #411 due to limitations on the id not provided to the model parameters as a normal plugin model.
I can host the plugin i built though in my own repo as an option to not just throw it away.

Closing as complete


Update script.js

I have add the function to get current location with the weather information status

valid changes


Does not support fluent schema queries

http://isaac.su/2014/05/mocking-fluent-objects-in-javascript/
Looking for a tool that will give me a drop-in mock for a schema-based query using fluent syntax. This tool lacks the recursive aspect necessary for that.
e.g. schema.find().where('name').equals('John').exec(callback);

This would be really useful for my use-case too

Hello I found sinon-mongoose which seems to let you test chained mongoose queries if that helps

the methods are missing, (like, lean), etc - but for chaining you can Model.find.returns(Model) within the test case, leveraging the sinon stub api to achieve what you're looking for


TBomb is No Longer Obfuscated xD

TBomb is No Longer Obfuscated xD
Thanks To You @darkestentropy and @scpketer For Your Help
Looking Forward To Your Contributions !!!
The Code Might Be A bit naive Cause i coded it long ago xD

Great news! If so, bombcrack will be really abandoned from now on.
Will get in touch with you at TBomb repo :)


Documentation: django.urls.exceptions.NoReverseMatch (and other Documentation issues)

Description
Using the tutorial found here: http://docs.django-cms.org/en/latest/introduction/05-apphooks.html. Up to step 5, there has not been any major issue. However, when completing the steps in step 5, the following error appears:

django.urls.exceptions.NoReverseMatch: 'polls' is not a registered namespace

Screenshot available here: https://imgur.com/6i0hnTG.
This is after completing step 5.1.3 Restart the runserver.

Steps to reproduce
Followed tutorial up to step 5.1.3.

Expected behaviour
Should not cause 500.

Actual behaviour
Causes 500.

Additional information
Any page with the following causes the 500 error to be raised:
<form action="{% url 'polls:vote' instance.poll.id %}" method="post">
However, I can also add back to urls.py the following, which fixes the error (although I believe this is not the purpose of the documentation tutorial):
url(r'^', include('polls.urls', namespace="polls")),
Also, in step 9 (http://docs.django-cms.org/en/latest/introduction/09-third_party.html), aldryn_reversion is suggested to install. However, aldryn_reversion requires django < 1.11, whereas in step 1 (http://docs.django-cms.org/en/latest/introduction/01-install.html) django >= 1.11 is required! Migrate does not work if reversion or aldryn_reversion are included in settings.py.

Environment:
Python version: 3.7.6
Django version: 2.2.11
django CMS version: 3.7.1

set app_name = 'polls' in your polls/urls.py . That will solve the problem

I got the same issue T_T

Added the need for app_name = polls to the docs!

Hi, this issue still persists for me, on removing the line re_path(r'^polls/', include('polls.urls')), I start getting 'polls' is not a registered namespace on any page I have added a poll to.
in polls/urls.py i have the line app_name = 'polls' and in my installed apps I have polls. I have tried app_name = 'polls' and app_name = "polls"
I am running django-cms==3.11.4 and Django==3.2 and following the instructions at https://docs.django-cms.org/en/release-3.10.x/introduction/05-apphooks.html (specifically section 5.1.12)
FYI, leaving that line in, does not result in the error URL namespace 'polls' isn't unique. You may not be able to reverse all URLs in this namespace. as indicated in the docs.
Is there something I am missing here?

I got the same issue T_T


🐛 [Bug] PixelShuffle with dynamic shape error

Bug Description
Trying to convert a model with pixel shuffle and dynamic shape results in many errors, with this message reshape dimension with more than one -1 wildcard.
Converting the model with a static shape works fine.
To Reproduce
Steps to reproduce the error:

Use a model with a nn.PixelShuffle layer
Use a torch_tensorrt.Input with min_shape, opt_shape and max_shape
Try to convert with torch_tensorrt.compile

To reproduce the error use the following code and execute the with dynamic as input:
python pixel_shuffle_bug.py dynamic

Example code
# Save as pixel_shuffle_bug.py
import torch
import torch.nn as nn
import torch_tensorrt

class MyModel(nn.Module):
    def __init__(self):
        super().__init__()
        self.conv = nn.Conv2d(3, 16, kernel_size=3, padding=1)
        self.shuffle = nn.PixelShuffle(2)

    def forward(self, x):
        return self.shuffle(self.conv(x))

@torch.no_grad()
def main(shape_mode):
    input_data = torch.rand(1, 3, 1280, 720)
    factory_kwargs = {"dtype": torch.float32, "device": torch.device("cuda:0")}

    precision = torch.float32
    x = input_data.to(**factory_kwargs)

    m = MyModel().to(**factory_kwargs)
    m = m.eval()
    out = m(x)

    sm = torch.jit.trace(m, example_inputs=(x,))
    sout = sm(x)

    if shape_mode == "dynamic":
        inputs = [
            torch_tensorrt.Input(
                min_shape=[1, 3, 852, 480],
                opt_shape=[1, 3, 1280, 720],
                max_shape=[1, 3, 3840, 2160],
                dtype=factory_kwargs["dtype"],
            )
        ]
    else:
        inputs = [
            torch_tensorrt.Input(
                shape=[1, 3, 1280, 720],
                dtype=factory_kwargs["dtype"],
            )
        ]
    torch_tensorrt.logging.set_is_colored_output_on(True)
    with torch_tensorrt.logging.warnings():
        compile_spec = {
            "ir": "ts",
            "inputs": inputs,
            "enabled_precisions": {precision},
            "truncate_long_and_double": False,
            "require_full_compilation": True,
        }
        trtm = torch_tensorrt.compile(sm, **compile_spec)

    print("\033[92m" + "=========== Model converted ===========" + "\033[0m")

    trtout = trtm(x)

    print(f"greatest difference trt ({precision}): {(out - trtout).max().item()}")

if __name__ == "__main__":
    import argparse

    parser = argparse.ArgumentParser()
    parser.add_argument("shape_mode", choices=["dynamic", "static"])

    args = parser.parse_args()
    main(args.shape_mode)

Error messages and stack traces
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 4: [graphShapeAnalyzer.cpp::analyzeShapes::1872] Error Code 4: Miscellaneous (IShuffleLayer (Unnamed Layer* 1) [Shuffle]: reshape dimension with more than one -1 wildcard. Reshaping [1,16,(# 2 (SHAPE input_0)),(# 3 (SHAPE input_0))] to [1,4,2,2,-1,-1].)
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 4: [graphShapeAnalyzer.cpp::analyzeShapes::1872] Error Code 4: Miscellaneous (IShuffleLayer (Unnamed Layer* 1) [Shuffle]: reshape dimension with more than one -1 wildcard. Reshaping [1,16,(# 2 (SHAPE input_0)),(# 3 (SHAPE input_0))] to [1,4,2,2,-1,-1].)
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 4: [graphShapeAnalyzer.cpp::analyzeShapes::1872] Error Code 4: Miscellaneous (IShuffleLayer (Unnamed Layer* 1) [Shuffle]: reshape dimension with more than one -1 wildcard. Reshaping [1,16,(# 2 (SHAPE input_0)),(# 3 (SHAPE input_0))] to [1,4,2,2,-1,-1].)
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 4: [graphShapeAnalyzer.cpp::analyzeShapes::1872] Error Code 4: Miscellaneous (IShuffleLayer (Unnamed Layer* 1) [Shuffle]: reshape dimension with more than one -1 wildcard. Reshaping [1,16,(# 2 (SHAPE input_0)),(# 3 (SHAPE input_0))] to [1,4,2,2,-1,-1].)
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 4: (Unnamed Layer* 1) [Shuffle]: at most one dimension may be inferred
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 4: [network.cpp::validate::2991] Error Code 4: Internal Error (Layer (Unnamed Layer* 1) [Shuffle] failed validation)
ERROR: [Torch-TensorRT TorchScript Conversion Context] - 2: [builder.cpp::buildSerializedNetwork::751] Error Code 2: Internal Error (Assertion engine != nullptr failed. )
Traceback (most recent call last):
  File "pixelshuffle_dynamic_shape_error.py", line 72, in <module>
    main(args.shape_mode)
  File "/usr/local/lib/python3.8/dist-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "pixelshuffle_dynamic_shape_error.py", line 56, in main
    trtm = torch_tensorrt.compile(sm, **compile_spec)
  File "/usr/local/lib/python3.8/dist-packages/torch_tensorrt/_compile.py", line 125, in compile
    return torch_tensorrt.ts.compile(
  File "/usr/local/lib/python3.8/dist-packages/torch_tensorrt/ts/_compiler.py", line 136, in compile
    compiled_cpp_mod = _C.compile_graph(module._c, _parse_compile_spec(spec))
RuntimeError: [Error thrown at core/conversion/conversionctx/ConversionCtx.cpp:169] Building serialized network failed in TensorRT

Expected behavior
The model should be converted with dynamic shape support.
Environment
The official NVIDIA Pytorch Docker image version 22.12 is used.

Build information about Torch-TensorRT can be found by turning on debug messages

Torch-TensorRT Version (e.g. 1.0.0): 1.3.0a0
PyTorch Version (e.g. 1.0): 1.14.0a0+410ce96
CPU Architecture: AMD64
OS (e.g., Linux): Ubuntu
How you installed PyTorch (conda, pip, libtorch, source): preinstalled in the Docker image
Build command you used (if compiling from source):
Are you using local sources or building from archives:
Python version: 3.8.10
CUDA version: 12.0
GPU models and configuration: NVIDIA GeForce RTX 2080 Ti, driver version 525.60.11
Any other relevant information:

We are aware of this limitation. Currently we don't have support for dynamic shape with aten::size (which gets passed to aten::reshape resulting in multiple wildcard dimensions). We plan to address this as a part of https://github.com/pytorch/TensorRT/issues/1562

Sorry this was closed by the bot, but I received no update. Is is really important for us to have dynamic shapes with pixel shuffle. Is someone working on #1577 ?
@peri044
Thank you

any update on this issue?


Inconsistent .pk behaviour

Hi, I've tripped over how the .pk property works for Models.
Consider this:
>>> from redis_om import HashModel, Field, Migrator
...
... class A(HashModel):
...     x: int
...
... class B(HashModel):
...     x: int = Field(primary_key=True)
...
... Migrator().run()
...
... a = A(x=3)
... b = B(x=3)
>>> a.pk
'01H9MZDZRHHDAQZY28F7ETGFHB'
>>> b.pk
<redis_om.model.model.ExpressionProxy object at 0x7f635ceb1d50>

What is an ExpressionProxy object?
Why is b.pk not 3?

In my opinion, using any HashModel or JsonModel should not require knowledge about whether their pk is auto-generated or explicitly declared.
I hope this was not described anywhere in the docs, but I did not find anything.

Related to #612 #669 @slorello89 @guyroyse


a标签链接 点击 无反应

1 a标签链接 点击 无反应；正常应该是弹出一个新tab来浏览新闻，结果 怎么点击都没有反应
2 右下角一直 提示  loading playbooks....

Thanks for trying out! I'll look into it as soon as possible. 😄
Besides, the taskbar below is still under development, so you can just ignore it for now.


Does this run on MacOS Monterey

In the past I have used a MacBook and yaagl worked well, I had pretty high resolution and no noticeable bugs. But I have tried to get yaagl on MacOS Monterey multiple times but every time when I get to the launch part it says “Failed to Initialize graphics. Make sure you have DirectX 11 installed (I do), have up to date drivers for your graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphic failed.” Any help on this? Or does yaagl just not run on MacOS Monterey.

I will only focus on Sonoma. It may work on lower macOS version but not guaranteed.


WMS: 11481 - Updated Get Started lab with latest ecpu changes(common lab)

Add here your WMS ID
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

@apoosrini please update the Last Updated By/Date line to reflect your name and the date.


Format Code workflow to generate signed commits.

User Story
As a member of staff in the MOJ who wishes to create a PR in either the Modernisation-Platform repo or in those MP managed modules
I need any commits generated by the code formatter workflow to be signed.
So that PRs containing these commits do not block the merging of an approved PR.
Value / Purpose
Without this issue resolved, MP staff will need to either intervene to help the user.
Useful Contacts
No response
Additional Information
No response
Definition of Done

[ ] Changes identified so code formatter workflow generates signed commits.
[ ] Changes test & confirmed as working in one of the MP-managed repositories.
[ ] Roll out changes across all MP-managed repositories.
[ ] Review with team & close.

closing as a duplicate


Tidy up Title Case Conversions

Some Acronyms are coming through as camel case - instead of uppercase. e.g. ASA in asa_physical_status_classification_system_code
Angela assigned - so any spotted can be added to this ticket.

GS1 vs Gs1 - (Supporting Definitions)

READ codes vs Read Codes

TRUD vs TRUD

All of the above are found under supporting definitions folder

GS1 is OK in the text but the name is still Gs1. Also:
Gs1 Application Identifier (Global)
Gs1 Application Identifier (Internal)
Gs1 Global Service Relation Number
TRUD is OK in the text but the name is still Technology Reference Data Update Distribution (Trud).
Also still have names as:
International Classification of Diseases (Icd)
International Classification of Diseases for Oncology (Icd-o)


why remove the relu after P6 in  FPN of the retinanet?

hi , I read in code of FPN , and the relu_before_extra_convs constructor  parameter catches my eye , but in the config of retinanet,  relu_before_extra_convs is False.
In the original RetinaNet paper, there is a relu before the conv after P6 of FPN, while in this repo the relu is removed. Is this an intended behavior?
The question is also mentioned in issue

There is no difference of performance, this argument is added to align some third party implementations of one-stage detectors


Monetization for video creators?

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question
Do video creators make money from youtube-dl? Also, does it count as a view with full watch time? I'm using --include-ads, but it doesn't seem to work. I'm making an offline YouTube viewer and I want to make sure it doesn't harm the creator in any way compared to watching the video normally, either by not making them money, not adding views, making the algorithm think the video isn't being watched all the way through because it isn't interesting, messing up analytics or anything like that.
Sorry if this has been asked before, but I can't find anything in the GiutHub issues search and Googling youtube-dl monetization just gives me info about the RIAA takedown (I'd be surprised if no-one has ever been worried about this though).

Full command line options: `--mark-watched --include-ads --write-info-json --write-thumbnail --write-sub --write-auto-sub``

youtube-dl only partially emulates browser's behavior, whether this affects monetization is up to Youtube. youtube-dl does not provide (and actually can't) any guarantees on that.

OK, I did a test on my own unlisted video and it doesn't seem to add a view, but then neither does a signed-out view from the same PC... Maybe I should test from another IP

I know it might be hard to keep up with YouTube's API changes and also it could be abused as view bot, but it would be nice if it could count as a view... That might be a job for a browser automation library though

Doesn't seem to be going up to 2, so for anyone finding the issue through search, no, it doesn't seem to add a view


Introduce a consistent Code style

While working on #294 I noticed there's a bit of a mess from a code style point of view.
See e.g. IsCollectionWithSize: there's a mix of tabs with 2 spaces and others with 4 spaces.

That's unfortunate. My preference is for 2 spaces (I like to conserve horizontal line space). This is not just the thing about initial indentation vs further indentation?

If it is simply an indentation concern, then I think it's straightforward to address that using CheckStyle to assist with a consistent code style. I've opened up a PR which adds such a rule.

Yes, thanks @brownian-motion, that's what I meant.
Shall we go a little further and provide a code style settings so that everyone is on the same page and up & running in few secs?

I like this idea, but I'm only familiar with a small set of style settings. I know IntelliJ can import code style from CheckStyle, can Eclipse or other IDEs do the same? If all can, it may be simple enough to define a CheckStyle file.

I don't know, but if we want to keep it simple, we may just use Google's styles: they are using 2 spaces anyways.
https://github.com/google/styleguide
They provide both for Eclipse and Intellij.


Improve tty and fix fmt bugs

This PR adds support for TAB/BS characters in the TTY implementation and adds a workaround that prevents the early_fmt code from triggering the Go memory allocator when trying to print long format strings.

Codecov Report

Merging #10 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #10   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         264    281   +17
=====================================
+ Hits          264    281   +17

Impacted Files
Coverage Δ

kernel/driver/tty/vt.go
100% <100%> (ø)
:arrow_up:

kernel/kfmt/early/early_fmt.go
100% <100%> (ø)
: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 0154c13...6d3c463. Read the comment docs.


Add MultiMaps

MultiMaps relax the restriction that every K can associate with at most
one V; in general, a query for K can result in any set of V, including
empty ones.
These were already used in a few areas of code, refactored to consider
them.

Aaaalright. Tests were added, cleanups were done, I think this is ready for another look-over. I'm definitely not happy with the structure of that test (and how much of it is abject copying), but--until I find out more about JUnit--it does stand and work.
Score one for the testing framework: I was using getOrElse when I meant to use getOrPut. That bug was stomped out nice and early.
(Propose ready for review.)

(just rebased onto the new master, sorry about that; ready for review again.)

forgot to mention: ready for next review :)
The println is a dprintln, now; it's not terrible using the debug infrastructure in tests, right?

I haven't determined why, but Codacy reports some of these files have issues and they don't seem to exist when I actually drill down, but in other files where they do exist, it doesn't show up on the main page. I'm going to propose we use a different code quality tool that actually works.


Add Risk Assessment Report Template reference

Risk Process refers to the a. Risk Assessment Report Template reference which does not exists in the repo. Please add.

+1 please add.

+1ing this

1

1

+1


Update virtual-machines-common-isolation.md

Added DC8_v2 to the list, DC8_v2 is the maximum size node for DCsv2-series machines.

@mmcrey : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @mmcrey - This pull request was opened in the public repo. This content has a private repository, and PMs usually work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!

Making the amendment in the private repo after conversation with @ktoliver


carousel stops in between items when fast scrolling

As you can see in the last scroll, when I scroll fast enough it stops off center of any item. Gif is from simulator but the same thing happen on device. I thought it was side effect of PR: #12 but it seems this behavior was there before. Not really that annoying as I noticed it only now and as I said you have to scroll really fast.

Yeah I've noticed it too, not really sure of a cause right on the spot. Will try to find it in a free time. Thanks for the issue! 🎉

Hello, I am facing same issue here. Do you have any updates?

I am also facing this issue. Any updates?


Stargate Arbitrum, Avalanche, BSC, Optimism, Polygon QA

@pietydespises Can you give these deployments a quick scan, mark them off if they look good and leave any comments for @dhruv-chauhan in this issue?
Deployment to QA:

[x] #1847
[x] Avalanche: https://okgraph.xyz/?q=QmYFygCMetwkxpib8E1RWcbPckSJ819rKRSYdMudgmLiHU
[x] BSC: https://okgraph.xyz/?q=QmPoYMaS8XDL3y7iuc9SjJXwje5akWV62v218v3HW35yqr
[x] Optimism: https://okgraph.xyz/?q=QmVkLyV8ga4ZSwtWLjS2HhEbhCLusJDDQSUST3Dx2wnLAP
[x] Polygon: https://okgraph.xyz/?q=QmbADHmhjQrgZR8W3HrGceyzEEAvJYWsuWXPzuhYiBxWzT

These all look good to go


error TS2345: Argument of type '(string | number | boolean | BigNumber)[]' is not assignable to parameter of type 'ContractDataType[]

I am getting a variety of these errors:
/MiniMeToken.ts(50,13): error TS2345: Argument of type '(string | number | boolean | BigNumber)[]' is not assignable to parameter of type 'ContractDataType[]'
Type 'string | number | boolean | BigNumber' is not assignable to type 'ContractDataType'.
Type 'BigNumber' is not assignable to type 'ContractDataType'.
Type 'BigNumber' is not assignable to type 'BigNumber[]'.
Property 'includes' is missing in type 'BigNumber'.
MultiSigWallet.ts(50,13): error TS2345: Argument of type '(number | string[] | BigNumber)[]' is not assignable to parameter of type 'ContractDataType[]'.
Type 'number | string[] | BigNumber' is not assignable to type 'ContractDataType'.
Type 'BigNumber' is not assignable to type 'ContractDataType'.
Type 'BigNumber' is not assignable to type 'BigNumber[]'.
These are standard MiniMeToken and MultiSigWallet implementations. I can't figure out what's happening here. I have about 10 classes that fail like this.
FYI I can compile and tests my contracts without errors.

I found out the issue. My project had latest version of bignumber.js dependency ^6.0.0. Is there a requirement to not have the latest version or use the same version as Ethereum?

Yes, web3 v0.20 works with bignumber.js v.4.0.
We will migrate to BN.js soon when integrate with web3.js 1.0.
"peerDependencies": {
        "bignumber.js": "^4.0.0"
    },


nixos/redis: disable transparent huge pages (TLP) before starting Redis

Redis doesn't cope well with TLP and wants it disabled before the main process is started. I put the shell code into a separate systemd unit (instead of adding it to preStart in the existing one) because I thought it might be useful for other services with the same problem to depend on this unit and re-use it rather than everyone cooking their own soup.

This makes sense for Redis but I don't like that we're setting options with system-wide implications in the redis systemd unit.

This makes sense for Redis but I don't like that we're setting options with system-wide implications in the redis systemd unit.

What do you propose we do instead?

What do you propose we do instead?

I'm not sure what the correct approach is, but what's currently proposed in this PR is counter-intuitive.
At the very least the Redis module should contain a note stating that this is a side-effect of enabling the module.

The Redis module should contain a note stating that this is a side-effect of enabling the module.

I extended the documentation of redis.enable accordingly.

@peti at least for me, the redis module is entirely broken, noticed during https://github.com/NixOS/nixpkgs/pull/67770. PR at https://github.com/NixOS/nixpkgs/pull/67845.

@flokli,

at least for me, the redis module is entirely broken

Can you be a little more specific, please?

The service fails to startup, see the gitlab vm log from https://github.com/NixOS/nixpkgs/pull/67770#pullrequestreview-282112596.

The service fails to startup, see the gitlab vm log from #67770 (review).

Maybe I am blind or something, but to me eyes that snipped contains zero information about Redis. All I see are log messages from Gitlab, which is not the same thing, no? Anyhow, this is probably not the right place to discuss this topic anyway. https://github.com/NixOS/nixpkgs/pull/67845 probably is.

I'd really have preferred to have seen the fixes added inside the PR.
Adding more commits disconnected to the PR makes things much less understandable, especially if pushed to master without a reference in the commit message.
I added the small cosmetic changes, and included the release notes changes into https://github.com/NixOS/nixpkgs/pull/67845.


Issue with interpolating data from ndax file

Hi, having an issue with interpolating missing data from ndax files.  Have not modified any of the original code.  Just installed the package and am trying to run the example usage (import NewareNDA --> df = NewareNDA.read('testndax.ndax').  Consistently seeing the following issue:

/usr/local/lib/python3.10/dist-packages/pandas/core/frame.py in interpolate(self, method, axis, limit, inplace, limit_direction, limit_area, downcast, **kwargs)
11853         **kwargs,
11854     ) -> DataFrame | None:

11855         return super().interpolate(
11856             method,
11857             axis,

TypeError: super(type, obj): obj must be an instance or subtype of type

triggered by this line in the _data_interpolation(df) function

/usr/local/lib/python3.10/dist-packages/NewareNDA/NewareNDAx.py in _data_interpolation(df)
103
104     # Group by step and run 'inside' interpolation on Time
--> 105     df['Time'] = df.groupby('Step')['Time'].transform(
106         lambda x: pd.DataFrame.interpolate(x, limit_area='inside'))
107

any help is appreciated.  thanks!

Hi @lithiosEngineering what version of pandas are you using? Can you try upgrading to the latest version? I'm noticing this error goes away starting in pandas 2.1.0. I will investigate a workaround for older versions of pandas. The code in NewareNDA causing this error is new and has not had much testing.

This might be a quick fix for older pandas versions. Can you test the latest commit to development and see if the issue is fixed? 6f28da8

Thanks Dan that works!


@ashkan18 =>Payment request rendering inline

Super early wip, but just for some context on the recent Radiation/Impulse/Lewitt/Metaphysics PR's, which winds up with a very simple Emission PR!

(ignore the 'pdf' icon)
Basically, with every message that contains an invoice attachment, we can render the invoice details. That is: amount, state, and link (tap to open webview). Some of those are still to come of course, but the basic structure is there.

Fails

:no_entry_sign:

No CHANGELOG added.

:no_entry_sign:

Missing Test Files:

src/lib/Components/Inbox/Conversations/Preview/__tests__/InvoicePreview-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

gettin' there!
Need to clean up the CSS so the text isn't truncated (+ the amount is visible), but you get the idea.

w00t

cc @sarahscott I think this is good to go.
This uses the new APIs and schema to render Invoice detail inline (with support for onSelected, similar to the PDF and image tap to load).
This is basically where the tap should take you to the webview, and then return you here. I'm down to pair on this! Or I can show you the existing setup and API/schema for invoices, and you can work on it a bit and then we can pair (or whatever you prefer).

I think I responded to the feedback, might be good to go!

Lets go then! at some point i'll ping you to help me setup emission!


Replace url-scheme-compiler with a cerebral-scheme-parser

Hello! :)
A lot has happened since the initial implementation of cerebral-addons and where we are today with our official operators. Who would know how productive a simple state:foo.bar could be. So I have been thinking a bit. How we can expose a simple API to build whatever schemes we want. There will of course still be official Cerebral operators, but it would be good to give developers the ability to create their own.
Basically we give:
import {parseScheme} from 'cerebral'

This function lets you pass in any string and it will parse the following for you, if matches scheme of target:value:

target. The target is whatever is in front of the colon. Example: state:foo. The target is state. But it can be anything: state[myModule]:foo, where state[myModule] will be the target

value. The value will be whatever is after the colon. Example: state:foo. The value is foo

schemes. An array of schemes found in the value. Example: state:users.{{input:id}}. The schemes will be: [{target: 'input', value: 'id'}]

The parsed result will also give you a getValue(scheme =>) method. The callback allows you to return a replacement for the scheme in the value. There is also a getValuePromise(scheme =>) which does the same, only returning a promise. Lets look at an example.
Reimplement the SET operator
import {parseScheme} from 'cerebral'

function set(path, value) {
  const scheme = parseScheme(path);

  // scheme returns null if not a scheme
  if (!scheme || scheme.target !== 'state') {
    throw new Error('The set operator only supports setting to state target')
  }

  function action({input, state}) {
    const parsedPath = scheme.getValue(scheme => {
      if (!scheme || (scheme.target !== 'state' && scheme.target !== 'input')) {
        throw new Error('The set operator only supports state and input as target in inline schemes')
      }
      return (
        scheme.target === 'state' ?
          state.get(scheme.value)
        :
          input[scheme.value]
      )
    })

    state.set(parsedPath, value)
  }
  action.displayName = 'operator SET'

  return action
}

This implementation lets you do:
set('state:foo.{{input:bar}}', 'woop')
set('state:{{state:currentPath}}.{{input:bar}}', 'woop')

The point is that with this API it becomes very easy to reimplement all the operators and we allow you to develop your own custom scheme based action factories, whatever you come up with :)
Maybe you want to create your own set of operators that allows you to also access module and modules on the context, using cerebral-provider-modules. The HTTP service can very easily now create:
http('get:/items/{{input:id}}')
// or
http('patch:/items/{{state:currentItemId}}', 'state:currentItem')
// or
http('get:/items', {
  page: 'state:currentPage'
})

So basically instead of having a preset behaviour of compiling these strings we rather just parse it and give you the details to do whatever you want.

As you can imagine, I think this is a GREAT idea! 😀 Giving factories full access to context will really open up a lot of very elegant, concise API's-- like the http example you gave. Very exciting that we can make these patterns first class citizens....it really is a unique to Cerebral.

Nice!  This will truly allow a lot of flexibility to use the operators however you'd like to use them in your application.  And I agree, something very unique to cerebral!


CurlFormatter fails on large boddies

Q
A

Bug?
yes

New Feature?
no

Version
Master

Actual Behavior
When posting super large bodies you will get an error because escshellargs does not allow more than X chars. https://github.com/php-http/message/blob/v1.4.1/src/Formatter/CurlCommandFormatter.php#L42
We should make sure to catch/suppress that error and write a better error message in the curl string.

I will do it)

I've also noticed the following error:
Fatal error: escapeshellarg(): Input string contains NULL bytes

I know it occurs when I upload a binary file. Im probably doing something wrong but the cUrl formatter is not the right place to complain about this. We should make sure to catch this as well.

Hi ! Still got the issue on PHP 7.3  with php-http/message 1.7.2 :
Error: escapeshellarg(): Argument exceeds the allowed length of 8192 bytes
in CurlCommandFormatter.php line 48

Maybe something like:
 if (preg_match('/[\x00-\x1F\x7F]/', $data) || mb_strlen($data) > $theAllowedLength) {
    $data = '[binary stream omitted]';
}

would do the trick, or wrap it in a try catch. Anyone know how to get the limit for the function?


[FLINK-10527] Cleanup constant isNewMode in YarnTestBase

What is the purpose of the change
This pull request cleanups constant isNewMode in YarnTestBase
Brief change log

Cleanup constant isNewMode in YarnTestBase

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@yanghua thanks for raising this thread! I think YARNHighAvailabilityITCase, YARNSessionCapacitySchedulerITCase#testClientStartup and YARNSessionCapacitySchedulerITCase#testTaskManagerFailure are ignored by assumeTrue.
You remove the assumeTrue statement and re-enable them. It looks like unintended. Maybe do some analysis to see if we can remove them as (covered by existing tests/not supported any more) or port them to FLIP-6 code base?

@TisonKun it seems it is not been ignored, it causes my PR failed, see here.

I try to remove these test methods.

@tillrohrmann What do you think of this way of handling?

I agree with @TisonKun. I think we cannot simply remove the tests but instead need to port them to the Flip-6 codebase. For example, the Yarn tests verify that the Yarn application master can be killed multiple times. Also the TaskManager failure test seems to be a valid one.

hi @TisonKun and @tillrohrmann OK. So, what does "port to FLIP-6 code base" specifically mean? where is the "FLIP-6 code base" .Maybe I am missing some understanding of the context.

Porting to Flip-6 code base means to make it run with the Flip-6 code. There are some things which no longer work as a testing criterion (e.g. Flip-6 does not bring up TMs upfront). Ideally it is only about setting a different entrypoint but sometimes one need to adapt a bit more.

OK, I know. The "code base" misleads me.

I don't know why all the yarn tests have been unable to run successfully in my local (since I started participating in the Flink community), so I can only rely on Travis's exception detection while changing.

You need to build build flink-dist and flink-yarn-tests first. Alternatively you could simply use mvn verify -pl flink-yarn-tests -am. Please also make sure that you don't have any HADOOP env variables defined.

@tillrohrmann For test case testTaskManagerFailure, the current test mode (based on stdout and stderr's special print message) cannot verify the Flip-6 scene. Because it doesn't pre-start a TM, so I can only commit a job to drive the TM registration, but this will cause the Job's output to flush out the flink's output, which shares stdout and stderr. Therefore, many judgments will not take effect.

Hi @yanghua , I see your last commit and think it is still use the legacy mode. (Since you start an actor system and use ActorGateway instead of using FLIP-6 components.)
To minimize this pull request as its title "Cleanup constant isNewMode in YarnTestBase", I propose remain the clean up in YARNSessionFIFOITCase, simply remove isNewMode and add @Ignore to YARNHighAvailabilityITCase, YARNSessionCapacitySchedulerITCase#testClientStartup and YARNSessionCapacitySchedulerITCase#testTaskManagerFailure. Meanwhile, raising a JIRA about port those tests.   What do you think?

I agree with @TisonKun to do the porting step by step. I would even say to remove the isNewMode last after all the porting has been done.
Concerning YARNSessionCapacitySchedulerITCase#testTaskManagerFailure, I think you're right @yanghua and we have to submit a blocking job to test the behaviour.

Hi @yanghua , I see your last commit and think it is still use the legacy mode. (Since you start an actor system and use ActorGateway instead of using FLIP-6 components.)

@TisonKun  From my last comment, I am currently focusing on the failure of YARNSessionCapacitySchedulerITCase#testTaskManagerFailure.

To minimize this pull request as its title "Cleanup constant isNewMode in YarnTestBase", I propose to retain the clean up in YARNSessionFIFOITCase, simply remove isNewMode and add @Ignore to YARNHighAvailabilityITCase, YARNSessionCapacitySchedulerITCase#testClientStartup and YARNSessionCapacitySchedulerITCase#testTaskManagerFailure. Meanwhile, raising a JIRA about port those tests. What do you think?

Agree your opinion.

Concerning YARNSessionCapacitySchedulerITCase#testTaskManagerFailure, I think you're right @yanghua and we have to submit a blocking job to test the behaviour.

Agreed, as like in JobManagerHAProcessFailureBatchRecoveryITCase but this time we have a Yarn based AM and TMs.

Hi @tillrohrmann and @TisonKun what about this change? In addition, I create a single JIRA issue FLINK-10558 to track the porting.

@yanghua changes LGTM and for your statement on "block FLINK-10292", it should have not been.
Document on Junit announces:
/**
     * If called with an expression evaluating to {@code false}, the test will halt and be ignored.
     *
     * @param b If false, the method will attempt to stop the test and ignore it by
     * throwing {@link AssumptionViolatedException}.
     * @param message A message to pass to {@link AssumptionViolatedException}.
     */
    public static void assumeTrue(String message, boolean b) {
        if (!b) throw new AssumptionViolatedException(message);
    }

So the error message occurs on https://api.travis-ci.org/v3/job/439612829/log.txt can be ignored. Also I'd like to get input from @zentol to see if the test env has some trouble.

@TisonKun About the "block" I mean that if we fix this could let FLINK-10292 's travis become green.


ui: add soft delete option for services and limit actions for soft deleted entities

Affected module
Does it impact the UI, backend or Ingestion Framework?
UI
Describe the bug
A clear and concise description of what the bug is.

[ ] Add soft delete option for services.
[ ] Limit the actions for all the soft deleted entities. We should not allow actions such as edit owner, tier, etc. The entity details should have read-only view when soft deleted.

To Reproduce
Screenshots or steps to reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: [e.g. 0.8]
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@aniketkatkar97 Let's close it for 1.2.1


[US] Lookup Table References

As a user, I want look-up tables to be bidirectional, so that I can look up any tables that reference or are referenced by the original table.

MoSCoW
Risk
Story Points

Must
medium
5

Acceptance Criteria
Tables that reference or are referenced can be looked up
Risks
adding complexity to look up table's logic
Pre-requisites

[x] Meet with the stakeholders to clarify the requirements
[x] Complete the requirements of this US

Tasks

[x] change the meta.sql for columns to be able to have bidirectional referencing
[x] add functionality for the new data
[x] add tests

Turn into a US because it is not a BUG

@MaximeJoanisse Will turn it into a US

https://github.com/WillTrem/UInnovate/assets/92006009/fb7066b5-ec42-479f-8e5a-315eb88b19fa
this includes sign-off for #212

Looks good!
Signing off!


Multi-level summaries

Description
This pull request implements multi-level summaries for the LightRAG project, enhancing code understanding and navigation. The main changes include:

Introduction of a new SummaryNode class and related functionality in lightrag/palmier/tree.py to generate and manage summaries for files, directories, and the entire project.
Integration of summary generation into the main LightRAG class and the kg_query function.
Implementation of a standardized database retry mechanism across different storage implementations (Neo4J, S3, Supabase, Qdrant) using the tenacity library.
Refactoring of the embedding generation process in MilvusVectorDBStorge, QdrantStorage, and NanoVectorStorage classes to improve efficiency and progress tracking.
Enhancement of code summarization prompts and token usage tracking for OpenAI API calls.
Removal of unused summary-related functionality from the CodeChunker class.
Improvement of file filtering logic and path handling.

The changes aim to improve the overall functionality, reliability, and performance of the LightRAG system, particularly in handling large codebases and providing more context for code understanding.
Changes that Break Backward Compatibility
The removal of summary_enabled and summary_model parameters from the CodeChunker class and the chunk_summary_enabled parameter from LightRAG may break backward compatibility for users who were relying on these features. Users will need to update their code to remove these parameters when instantiating CodeChunker or LightRAG objects.
Documentation
The PR introduces new prompts for file, folder, and global summaries in lightrag/prompt.py. These new prompts should be documented to explain their purpose and usage in the summary generation process. Additionally, the changes to the retry mechanism and embedding generation process should be reflected in the documentation to guide users on the new behavior and any configuration options.
Created with Palmier

@palmier-bot describe

@palmier-bot describe

@palmier-bot review


Parsing "" gives strange LaTeX

Parsing the empty string gives incorrect LaTeX in the parsed JSON; instead of getting latex: "", you get latex: '\\mathrm{Nothing}'.
This was tested on compute-engine 0.6.0.
const ce = new ComputeEngine();
ce.jsonSerializationOptions.metadata = ['latex'];
ce.parse("").json
> { sym: 'Nothing', latex: '\\mathrm{Nothing}' }

I can see why this would be unexpected. However, the "correct" behavior, is not immediately obvious.
Parsing an empty string result in the empty MathJSON expression Nothing.
Serializing the Nothing symbol to LaTeX yields \\mathrm{Nothing}.
That symbol could also appear anywhere as a subexpression, for example in {1,,3} -> ["List", 1, "Nothing", 3].
One option would be to always serialize the Nothing symbol as... nothing, i.e. an empty string. Seems like there could be cases where you'd want to know, though.
Another option would be to do this only for top-level expressions, but that seems fraught with peril, as expressions can of course be combined, and what used to be a top-level expression could become a sub-expression.

Hmm, interesting!
One question to clarify -- I've been assuming that the latex metadata for a parsed string will be equivalent to the input; ie:
inputString
  === parse( inputString ).json.latex

Is this a desired invariant?
Assuming the above invariant is true, I think I'd expect serialize() to behave by:

If latex exists on the MathJSON string, simply return that.
If not, re-create it from the MathJSON.

So, in this case, you'd end up with:
computeEngine.parse("").json
  -> "Nothing"

computeEngine.serialize(computeEngine.parse("").json)
  -> "\\mathrm{Nothing}"

// Now, we turn on the latex metadata and do it again:
computeEngine.jsonSerializationOptions.metadata = ['latex']

computeEngine.parse("").json
  -> "Nothing"

computeEngine.serialize(computeEngine.parse("").json)
  -> ""

Is this a desired invariant?

Yes, this is true if the ce.latexOptions.preserveLatex flag is true (which it is by default).
OK, so I see what you're saying, you're expecting the LaTeX to round-trip in the example you gave, which is fair enough. It should and that's a bug that it doesn't.
My previous comment was more applicable for a dynamically generated expression, not a parsed one. Still keeps open the question of the appropriate behavior if not round-tripping (i.e. preserveLatex is false, or Nothing is the result of an evaluation). I'll need to think about this one.
Just in case this wasn't clear, I'd like to clarify that there are two settings that control the LaTeX in MathJSON expressions:

ce.latexOptions.preserveLatex, when true indicate that the verbatim LaTeX that is input will be attempted to be preserved
ce. jsonSerializationOptions.metadata = ["latex"], indicate that the MathJSON expressions (i.e. from expr.json) should include LaTeX as metadata, either from the verbatim LaTeX captured during parsing, or generated dynamically if not available.

Oh! I hadn't actually come across ce.latexOptions.preserveLatex -- I'll add that in :)

Yeah, ce.latexOptions.preserveLatex should be true by default, so your example should behave as you expect, and the fact it doesn't indicate indeed a problem

This should work now, but I had to change the default value of ce.latexOptions.preserveLatex to false, so make sure to set it to true to preserve the LaTeX


Autorest Regen Preview to 3.0.0-alpha.20231120.2 by Alexander Sher from refs/pull/3953/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3953

API change check
API changes are not detected in this pull request.


duplicate key check in plain yamls

ytt crashes when running  against the current tekton release:
ytt --file-mark '*.yaml:type=yaml-plain' -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.21.0/release.yaml

panic: Unexpected duplicate key: name

goroutine 1 [running]:
github.com/k14s/ytt/pkg/yamlmeta.convertToGo(0x158b5c0, 0xc0002d5a40, 0x0, 0x0)
        github.com/k14s/ytt/pkg/yamlmeta/convert.go:65 +0x7ca
github.com/k14s/ytt/pkg/yamlmeta.convertToGo(0x158b300, 0xc0002d54a0, 0xc000197e50, 0x0)
        github.com/k14s/ytt/pkg/yamlmeta/convert.go:74 +0x454
github.com/k14s/ytt/pkg/yamlmeta.convertToGo(0x158b5c0, 0xc0002d5380, 0xc000197df0, 0x0)
        github.com/k14s/ytt/pkg/yamlmeta/convert.go:67 +0x5ed
github.com/k14s/ytt/pkg/yamlmeta.convertToGo(0x158b5c0, 0xc0002d4f00, 0x10ff7a7, 0xc00046853a)
        github.com/k14s/ytt/pkg/yamlmeta/convert.go:67 +0x5ed
github.com/k14s/ytt/pkg/yamlmeta.(*Document).AsYAMLBytes(0xc00032e8a0, 0xc00014c940, 0x4, 0x4, 0x4, 0x0)
        github.com/k14s/ytt/pkg/yamlmeta/document.go:25 +0x3c
github.com/k14s/ytt/pkg/yamlmeta.(*YAMLPrinter).Print(0xc0003ce5e0, 0xc00032e8a0, 0x0, 0x0)
        github.com/k14s/ytt/pkg/yamlmeta/printers.go:36 +0x42
github.com/k14s/ytt/pkg/yamlmeta.(*DocumentSet).AsBytesWithPrinter(0xc000116000, 0x1674e98, 0x2e, 0x30, 0xc000220800, 0x2e, 0x40)
        github.com/k14s/ytt/pkg/yamlmeta/document_set.go:58 +0xe8
github.com/k14s/ytt/pkg/yamlmeta.(*DocumentSet).AsBytes(...)
        github.com/k14s/ytt/pkg/yamlmeta/document_set.go:43
github.com/k14s/ytt/pkg/workspace.(*LibraryLoader).Eval(0xc0000d9ad8, 0xc0000b0fc0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
        github.com/k14s/ytt/pkg/workspace/library_loader.go:151 +0x343
github.com/k14s/ytt/pkg/cmd/template.(*TemplateOptions).RunWithFiles(0xc0000d1540, 0xc0000ac0d0, 0x1, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
        github.com/k14s/ytt/pkg/cmd/template/cmd.go:168 +0x55c
github.com/k14s/ytt/pkg/cmd/template.(*TemplateOptions).Run(0xc0000d1540, 0x0, 0x0)
        github.com/k14s/ytt/pkg/cmd/template/cmd.go:97 +0x2b6
github.com/k14s/ytt/pkg/cmd/template.NewCmd.func1(0xc0000f6dc0, 0xc0000b0ec0, 0x0, 0x4, 0x0, 0x0)
        github.com/k14s/ytt/pkg/cmd/template/cmd.go:61 +0x2a
github.com/cppforlife/cobrautil.WrapRunEForCmd.func1.1(0xc0000f6dc0, 0xc0000b0ec0, 0x0, 0x4, 0x0, 0x0)
        github.com/cppforlife/cobrautil@v0.0.0-20200514214827-bb86e6965d72/misc.go:45 +0xaf
github.com/cppforlife/cobrautil.WrapRunEForCmd.func1.1(0xc0000f6dc0, 0xc0000b0ec0, 0x0, 0x4, 0x0, 0x0)
        github.com/cppforlife/cobrautil@v0.0.0-20200514214827-bb86e6965d72/misc.go:45 +0xaf
github.com/spf13/cobra.(*Command).execute(0xc0000f6dc0, 0xc0000b6010, 0x4, 0x4, 0xc0000f6dc0, 0xc0000b6010)
        github.com/spf13/cobra@v1.0.0/command.go:842 +0x453
github.com/spf13/cobra.(*Command).ExecuteC(0xc0000f6dc0, 0xc0000f6dc0, 0x1a87b00, 0xc0000c01f8)
        github.com/spf13/cobra@v1.0.0/command.go:950 +0x349
github.com/spf13/cobra.(*Command).Execute(...)
        github.com/spf13/cobra@v1.0.0/command.go:887
main.main()
        github.com/k14s/ytt/cmd/ytt/ytt.go:21 +0x112

I think this is because of the strange merge syntax within the manifest:
- !!merge <<: *version
   name: v1beta1
   storage: true

Environment:

ytt version (use ytt --version): 0.31.0
OS (e.g. from /etc/os-release): macOS Big Sur (11.2.1)

Hello @mhubig
After some scavenging, I was able to reproduce your issue. Definitely, it is related to that piece of YAML there.
Unfortunately at this point in time ytt does not support the merge operator as described in https://yaml.org/type/merge.html
We do have another open issue with the same ask #299 but in your case, it is causing a panic because the file is marked as plain YAML and ytt is not try to process it.
Another interesting part of your issue is that the panic is not very helpful, so I think I would keep this issue open to tracking the enhancement of this panic with maybe the filename and line to at least help us find the culprit line more quickly.

Unfortunately at this point in time ytt does not support the merge operator as described in https://yaml.org/type/merge.html

ytt does support merge. can be demonstrated by following that works successfully+correctly:
stuff: &version
  non_name_key: val
array:
- !!merge <<: *version
  name: v1beta1

the underlying problem here is that ytt is strict about setting same key in a map twice (there is a flag to control that feature --implicit-map-key-overrides). in the example above *version already includes a name, and the next line tries to set name again. this is a safety feature which is quite useful in other contexts but may not be as useful as when consuming third party yaml.
i think we need to think hard about what kind of functionality we want to have for this. for example, should we do something similar to what we are planning to do with unknown comments (disable that check for plain yaml files -- non ytt templates).

For this issue, we would like to make a couple of improvements here:

[ ] provide a better UX for this scenario (we shouldn't panic, consider referencing the --implicit-map-key-overrides flag)
[ ] ensure that documentation around the --implicit-map-key-overrides is clear

As @cppforlife mentioned, we should think more about the functionality that we want for plain yaml vs ytt templates.

FWIW, at least in this specific Tekton case, this was resolved for users on the source side: tektoncd/pipeline#3842

i think we need to think hard about what kind of functionality we want to have for this. for example, should we do something similar to what we are planning to do with unknown comments (disable that check for plain yaml files -- non ytt templates).

Idea:

for now, extend the --implicit-map-key-override to plain YAML file evaluation.
restore the balance of usability with security by introducing a new File Mark: options which is a CSV with possible values implicit-map-key-overrides, ignore-unknown-comments, strict.
deprecate and then remove the all-or-nothing mode of these flags

if someone wants everything to be configured to allow implicit map keys, glob it;
this reduces interface complexity: there's one mechanisms to set the parser options;
it also encourages being judicious in disabling such checks.

Example:
$ ytt -f plain.yml -f template.yml --file-mark 'plain.yml:options=implicit-map-key-overrides`

Looking deeper, other YAML processing tools override keys, implicitly.
In ytt, once we've determined that a YAML file is "plain YAML", there's no need to require the --implicit-map-key-override flag to perform the override for that document.
This is the approach we took in #550. That work is done and will be included in the next release. 👍🏻


When naming branches let us not use "/" as separator

We got the feedback that this is confusing. Let us use '-' or '_'.

yourname/somefeature


Bumpminor

What kind of change does this PR introduce?

Update the version to 0.3.0

Looks good. Just be sure to tag (v0.3.0) on the main branch!


[HUDI-2150] Rename/Restructure configs for better modularity

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
1.Move clean related configuration to HoodieCleanConfig
2.Move Archival related configuration to HoodieArchivalConfig
3.hoodie.compaction.payload.class move this to HoodiePayloadConfig
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@codope  thanks


-> self.D_mtrain = len(self.D.MTRAIN)

I have theses mistakes:
> /home/user/code/modular-metalearning/modular_metalearning.py(223)create_dataset()
-> self.D_mtrain = len(self.D.MTRAIN)
(Pdb)
(Pdb)

Sorry for the very late response. This isn't a mistake, it's just pdb.set_trace() on the line before to give the possibility of inspecting some variables, if the user wants. Since it can cause confusion I've removed it.


Proper system wide installation

Sorry for the delay, but this PR should fix #134.

Hmm let me try to break that circular dep (though it is working fine)

Oooohhh yeahhh. :satisfied:

I finished the check.
When https://github.com/Kuniwak/vint/pull/143#discussion_r46039257 is done, I'll merge it.

Here's the rebased variant. Everything is the same except for compat/ is moved to vint/compat/ as a whole instead of being split across several __init__.py files

Looks good to me!
Thanks a lot! :pray:

Thank you!
Sadly landscape cannot properly detect that zip_longest and mock are used.
Let me try to fix this.


All api get routes returning 404 not found

Hello thank you for the awesome starter pack, Could you please investigate the reason why I cannot access the API.
Step to reproduce;
Clone project with degit command.
cd into the Project directory run pnpm i
cd into backend run pnpm i
cd into frontend run pnpm i
cd ..
run pnpm dev
Projects started successfully and both front and backend are working except strapi api get routes saying 404 not found the same error is showing for todos route which came with this template.

I'm Sorry! I didn't do enough testing before releasing and your run failed.
I've fixed the issue at https://github.com/kuizuo/vitesse-nuxt3-strapi/commit/04c983d21bc3cbdbd66b1c577ff0d909489443b1 commit
https://github.com/kuizuo/vitesse-nuxt3-strapi/blob/7839d4739a9bdeb06897809698104a72bbdcdbb8/backend/src/api/todo/routes/todo.ts#L18
https://github.com/kuizuo/vitesse-nuxt3-strapi/blob/04c983d21bc3cbdbd66b1c577ff0d909489443b1/backend/src/api/todo/routes/todo.ts#L18


Replaced @QueryParams with @BeanParams

Fixes https://github.com/quarkiverse/quarkus-openapi-generator/issues/59

Cherry-picked to quarkus2 branch: https://github.com/quarkiverse/quarkus-openapi-generator/pull/317


Fix Install Instructions

Thanks for this project, it looks awesome! A really cool project.
Had some problems following the install instructions though.

Following the install instructions:
python3 -m venv .venv
pip install .

I have python3.13 installed.
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11; 1.26.0 Requires-Python <3.13,>=3.9; 1.26.1 Requires-Python <3.13,>=3.9
ERROR: Could not find a version that satisfies the requirement torch>=2.0.0 (from video-analyzer) (from versions: none)
ERROR: No matching distribution found for torch>=2.0.0

So added the version needed to the readme instructions.

Then got this:
(.venv) kylehowells@Kyles-MBP video-analyzer % pip install .
Processing /Users/kylehowells/Developer/Example-Projects/video-analyzer
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting opencv-python>=4.8.0 (from video-analyzer==0.1.0)
  Using cached opencv_python-<IP_ADDRESS>-cp37-abi3-macosx_11_0_arm64.whl.metadata (20 kB)
Collecting numpy>=1.24.0 (from video-analyzer==0.1.0)
  Using cached numpy-2.2.1-cp311-cp311-macosx_14_0_arm64.whl.metadata (62 kB)
Collecting torch>=2.0.0 (from video-analyzer==0.1.0)
  Using cached torch-2.5.1-cp311-none-macosx_11_0_arm64.whl.metadata (28 kB)
Collecting openai-whisper>=20231117 (from video-analyzer==0.1.0)
  Using cached openai_whisper-20240930-py3-none-any.whl
Collecting requests>=2.31.0 (from video-analyzer==0.1.0)
  Using cached requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting Pillow>=10.0.0 (from video-analyzer==0.1.0)
  Using cached pillow-11.0.0-cp311-cp311-macosx_11_0_arm64.whl.metadata (9.1 kB)
Collecting numba (from openai-whisper>=20231117->video-analyzer==0.1.0)
  Using cached numba-0.60.0-cp311-cp311-macosx_11_0_arm64.whl.metadata (2.7 kB)
Collecting tqdm (from openai-whisper>=20231117->video-analyzer==0.1.0)
  Using cached tqdm-4.67.1-py3-none-any.whl.metadata (57 kB)
Collecting more-itertools (from openai-whisper>=20231117->video-analyzer==0.1.0)
  Using cached more_itertools-10.5.0-py3-none-any.whl.metadata (36 kB)
Collecting tiktoken (from openai-whisper>=20231117->video-analyzer==0.1.0)
  Using cached tiktoken-0.8.0-cp311-cp311-macosx_11_0_arm64.whl.metadata (6.6 kB)
Collecting charset-normalizer<4,>=2 (from requests>=2.31.0->video-analyzer==0.1.0)
  Using cached charset_normalizer-3.4.0-cp311-cp311-macosx_11_0_arm64.whl.metadata (34 kB)
Collecting idna<4,>=2.5 (from requests>=2.31.0->video-analyzer==0.1.0)
  Using cached idna-3.10-py3-none-any.whl.metadata (10 kB)
Collecting urllib3<3,>=1.21.1 (from requests>=2.31.0->video-analyzer==0.1.0)
  Using cached urllib3-2.2.3-py3-none-any.whl.metadata (6.5 kB)
Collecting certifi>=2017.4.17 (from requests>=2.31.0->video-analyzer==0.1.0)
  Using cached certifi-2024.12.14-py3-none-any.whl.metadata (2.3 kB)
Collecting filelock (from torch>=2.0.0->video-analyzer==0.1.0)
  Using cached filelock-3.16.1-py3-none-any.whl.metadata (2.9 kB)
Collecting typing-extensions>=4.8.0 (from torch>=2.0.0->video-analyzer==0.1.0)
  Using cached typing_extensions-4.12.2-py3-none-any.whl.metadata (3.0 kB)
Collecting networkx (from torch>=2.0.0->video-analyzer==0.1.0)
  Using cached networkx-3.4.2-py3-none-any.whl.metadata (6.3 kB)
Collecting jinja2 (from torch>=2.0.0->video-analyzer==0.1.0)
  Using cached jinja2-3.1.5-py3-none-any.whl.metadata (2.6 kB)
Collecting fsspec (from torch>=2.0.0->video-analyzer==0.1.0)
  Using cached fsspec-2024.12.0-py3-none-any.whl.metadata (11 kB)
Collecting sympy==1.13.1 (from torch>=2.0.0->video-analyzer==0.1.0)
  Using cached sympy-1.13.1-py3-none-any.whl.metadata (12 kB)
Collecting mpmath<1.4,>=1.1.0 (from sympy==1.13.1->torch>=2.0.0->video-analyzer==0.1.0)
  Using cached mpmath-1.3.0-py3-none-any.whl.metadata (8.6 kB)
Collecting MarkupSafe>=2.0 (from jinja2->torch>=2.0.0->video-analyzer==0.1.0)
  Using cached MarkupSafe-3.0.2-cp311-cp311-macosx_11_0_arm64.whl.metadata (4.0 kB)
Collecting llvmlite<0.44,>=0.43.0dev0 (from numba->openai-whisper>=20231117->video-analyzer==0.1.0)
  Using cached llvmlite-0.43.0-cp311-cp311-macosx_11_0_arm64.whl.metadata (4.8 kB)
Collecting numpy>=1.24.0 (from video-analyzer==0.1.0)
  Using cached numpy-2.0.2-cp311-cp311-macosx_14_0_arm64.whl.metadata (60 kB)
Collecting regex>=2022.1.18 (from tiktoken->openai-whisper>=20231117->video-analyzer==0.1.0)
  Using cached regex-2024.11.6-cp311-cp311-macosx_11_0_arm64.whl.metadata (40 kB)
Using cached opencv_python-<IP_ADDRESS>-cp37-abi3-macosx_11_0_arm64.whl (54.8 MB)
Using cached pillow-11.0.0-cp311-cp311-macosx_11_0_arm64.whl (3.0 MB)
Using cached requests-2.32.3-py3-none-any.whl (64 kB)
Using cached torch-2.5.1-cp311-none-macosx_11_0_arm64.whl (63.9 MB)
Using cached sympy-1.13.1-py3-none-any.whl (6.2 MB)
Using cached certifi-2024.12.14-py3-none-any.whl (164 kB)
Using cached charset_normalizer-3.4.0-cp311-cp311-macosx_11_0_arm64.whl (118 kB)
Using cached idna-3.10-py3-none-any.whl (70 kB)
Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Using cached urllib3-2.2.3-py3-none-any.whl (126 kB)
Using cached filelock-3.16.1-py3-none-any.whl (16 kB)
Using cached fsspec-2024.12.0-py3-none-any.whl (183 kB)
Using cached jinja2-3.1.5-py3-none-any.whl (134 kB)
Using cached more_itertools-10.5.0-py3-none-any.whl (60 kB)
Using cached networkx-3.4.2-py3-none-any.whl (1.7 MB)
Using cached numba-0.60.0-cp311-cp311-macosx_11_0_arm64.whl (2.6 MB)
Using cached numpy-2.0.2-cp311-cp311-macosx_14_0_arm64.whl (5.3 MB)
Using cached tiktoken-0.8.0-cp311-cp311-macosx_11_0_arm64.whl (982 kB)
Using cached tqdm-4.67.1-py3-none-any.whl (78 kB)
Using cached llvmlite-0.43.0-cp311-cp311-macosx_11_0_arm64.whl (28.8 MB)
Using cached MarkupSafe-3.0.2-cp311-cp311-macosx_11_0_arm64.whl (12 kB)
Using cached mpmath-1.3.0-py3-none-any.whl (536 kB)
Using cached regex-2024.11.6-cp311-cp311-macosx_11_0_arm64.whl (284 kB)
Building wheels for collected packages: video-analyzer
  Building wheel for video-analyzer (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for video-analyzer (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [36 lines of output]
      running bdist_wheel
      running build
      running build_py
      copying video_analyzer/config.py -> build/lib/video_analyzer
      copying video_analyzer/analyzer.py -> build/lib/video_analyzer
      copying video_analyzer/__init__.py -> build/lib/video_analyzer
      copying video_analyzer/audio_processor.py -> build/lib/video_analyzer
      copying video_analyzer/cli.py -> build/lib/video_analyzer
      copying video_analyzer/frame.py -> build/lib/video_analyzer
      copying video_analyzer/prompt.py -> build/lib/video_analyzer
      copying video_analyzer/clients/openrouter.py -> build/lib/video_analyzer/clients
      copying video_analyzer/clients/__init__.py -> build/lib/video_analyzer/clients
      copying video_analyzer/clients/llm_client.py -> build/lib/video_analyzer/clients
      copying video_analyzer/clients/ollama.py -> build/lib/video_analyzer/clients
      running egg_info
      writing video_analyzer.egg-info/PKG-INFO
      writing dependency_links to video_analyzer.egg-info/dependency_links.txt
      writing entry points to video_analyzer.egg-info/entry_points.txt
      writing requirements to video_analyzer.egg-info/requires.txt
      writing top-level names to video_analyzer.egg-info/top_level.txt
      reading manifest file 'video_analyzer.egg-info/SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      warning: no files found matching '*' under directory 'config'
      warning: no files found matching '*' under directory 'prompts'
      warning: no previously-included files matching '__pycache__' found anywhere in distribution
      warning: no previously-included files matching '*.py[cod]' found anywhere in distribution
      warning: no previously-included files matching '*.so' found anywhere in distribution
      warning: no previously-included files matching '.DS_Store' found anywhere in distribution
      warning: no previously-included files matching '.git*' found anywhere in distribution
      adding license file 'LICENSE'
      writing manifest file 'video_analyzer.egg-info/SOURCES.txt'
      installing to build/bdist.macosx-14.0-arm64/wheel
      running install
      running install_lib
      running install_data
      error: can't copy 'config/default_config.json': doesn't exist or not a regular file
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for video-analyzer
Failed to build video-analyzer
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (video-analyzer)

Changed setup.py to this fixed it:
# From
data_files = [
    ('video_analyzer/config', ['config/default_config.json'])
]

# To
data_files = [
    ('video_analyzer/config', ['video_analyzer/config/default_config.json'])
]

Then a successful installation, but running it resulted in:
(.venv) kylehowells@Kyles-MBP video-analyzer % video-analyzer
Traceback (most recent call last):
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/bin/video-analyzer", line 5, in <module>
    from video_analyzer.cli import main
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/lib/python3.11/site-packages/video_analyzer/cli.py", line 14, in <module>
    from .analyzer import VideoAnalyzer
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/lib/python3.11/site-packages/video_analyzer/analyzer.py", line 6, in <module>
    from .audio_processor import AudioTranscript
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/lib/python3.11/site-packages/video_analyzer/audio_processor.py", line 7, in <module>
    from pydub import AudioSegment
ModuleNotFoundError: No module named 'pydub'

So have added pydub to the requirements.txt file.

Then:
(.venv) kylehowells@Kyles-MBP video-analyzer % video-analyzer '/Users/kylehowells/Movies/Movies/Making a Desktop Fusion Reactor.mp4'
2024-12-22 03:27:55,379 - ERROR - Error loading Whisper model: No module named 'faster_whisper'
2024-12-22 03:27:55,379 - ERROR - Error during video analysis: No module named 'faster_whisper'
Traceback (most recent call last):
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/bin/video-analyzer", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/lib/python3.11/site-packages/video_analyzer/cli.py", line 114, in main
    audio_processor = AudioProcessor(model_size=config.get("audio", {}).get("whisper_model", "medium"))
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/kylehowells/Developer/Example-Projects/video-analyzer/.venv/lib/python3.11/site-packages/video_analyzer/audio_processor.py", line 23, in __init__
    from faster_whisper import WhisperModel
ModuleNotFoundError: No module named 'faster_whisper'

So have added faster_whisper to requirements file.

Thanks for doing that. Looks like I didn't try an install from scratch after my last changes.

I will go back to python3 though not 3.11 it'll work with versions other than 3.11 users can specify a specific version other than 3.11. looks like 3.13 specifically is missing a wheel for something


AnalogSignalArray and numpy.diff

I encounterd a problem when changing an AnalogSignal to an AnalogSignalArray and using numpy.diff() function. Here's an example code:
import neo
import numpy as np

anasig = neo.AnalogSignal([0,1,2]*pq.s, t_start=0*pq.s, t_stop=2*pq.s, sampling_rate=10*pq.Hz)
anasigarr = neo.AnalogSignalArray([0,1,2]*pq.s, t_start=0*pq.s, t_stop=2*pq.s, sampling_rate=10*pq.Hz)

np.diff(anasig) # works fine
np.diff(anasigarr) # gives an error

The Error occurs in neo/core/analogsignalarray.py
line 193: j,k = i
ValueError: need more than 1 vlaue to unpack

AnalogSignalArray has to be two-dimensional.
If you change the line to
anasigarr = neo.AnalogSignalArray([[0,1,2]]*pq.s, t_start=0*pq.s, t_stop=2*pq.s, sampling_rate=10*pq.Hz)

(note the extra square brackets)
then numpy.diff(anasigarr) works.
Really there should be a warning when creating an AnalogSignalArray with a 1D array, or it should be automatically coerced to 2D. This is done in the apibreak branch, where AnalogSignalArray and AnalogSignal have been merged.


Perform Load Testing and Security Audits for ECS Deployment with JWT Authentication

Discovery:
With the recent addition of JWT authentication to LibreChat, it's important to verify that the system can handle high traffic while maintaining performance and stability. This includes conducting load testing to simulate heavy traffic, stress testing the ECS service, and performing security audits to ensure JWT tokens are handled securely and that the system is resilient to attacks under load.
Problem Definition:
The current deployment of LibreChat on ECS has not been stress-tested to ensure that JWT authentication functions correctly under heavy traffic. Without load testing and security audits, there may be performance bottlenecks, token validation issues, or security vulnerabilities that could compromise system reliability and user experience during periods of high demand.
Motivations:
By conducting thorough load testing and security audits, we can:

Ensure that ECS can handle JWT authentication correctly at scale.
Identify any performance bottlenecks or system failures under heavy traffic.
Verify the security of JWT handling, especially during high traffic, to prevent unauthorized access or token misuse.
Ensure system stability and resilience during peak loads, maintaining a high-quality user experience.

Proposed Solution:

Perform Load Testing:

Use load testing tools (e.g., Apache JMeter, k6, or Gatling) to simulate heavy traffic and test the performance of JWT authentication under load.
Simulate a range of scenarios, including:

High frequency of authentication requests.
Users logging in and authenticating with valid JWT tokens.
Invalid or expired tokens being rejected.
Simultaneous creation of new users when JWT user.id is not found in the database.

Test how the system handles varying traffic levels, from normal operation to extreme traffic spikes.

Stress Testing:

Stress test the ECS service to identify any limitations, such as CPU or memory constraints, that could affect JWT authentication during high traffic.
Measure how ECS scales under load and whether the auto-scaling policies are sufficient to handle the increased demand without affecting authentication performance.
Monitor ECS task health and behavior under stress to identify potential issues like task crashes, slowdowns, or failure to validate tokens.

Security Audits:

Conduct security audits to ensure that JWT tokens are handled securely during load testing. This includes:

Ensuring that the JWT_SECRET_KEY is not exposed or vulnerable during high traffic.
Verifying that invalid tokens are rejected consistently, even under heavy load.
Checking for any potential vulnerabilities in token expiration, token renewal, or replay attacks.
Auditing logs for any security anomalies or suspicious activity related to token validation or user authentication.

Monitor System Performance:

Use Amazon CloudWatch to monitor key metrics during load testing, such as CPU utilization, memory usage, ECS task health, request latency, and error rates.
Set up CloudWatch alarms for performance thresholds (e.g., CPU > 80%, high error rates) to identify potential problems during testing.
Monitor logs for JWT-specific errors, such as validation failures or missing environment variables.

Optimize Based on Findings:

Analyze the results of the load and stress tests to identify any performance bottlenecks or system limitations.
Make necessary adjustments to ECS configurations (e.g., scaling policies, resource allocation) or application code (e.g., optimizing token validation processes) based on the findings.
Ensure that security vulnerabilities identified during the audit are addressed and that token handling is secure under all traffic conditions.

Definition of Done:

[ ] Load testing is performed, simulating various traffic levels and scenarios to verify that JWT authentication works correctly under heavy load.
[ ] Stress testing is conducted on the ECS deployment to identify performance bottlenecks and ensure system stability.
[ ] Security audits are completed, verifying that JWT tokens are handled securely under load and that there are no vulnerabilities in the authentication process.
[ ] Monitoring and logging are configured to track performance and security during testing.
[ ] Findings from the load tests and security audits are analyzed, and necessary optimizations are made to the ECS deployment and application code.

Additional Information:

Load Testing Tools: Consider using tools like Apache JMeter, k6, or Gatling for load testing.
Monitoring Tools: Use Amazon CloudWatch and AWS X-Ray to monitor system performance and trace authentication requests during load testing.
Security Auditing: Consider using security scanning tools like OWASP ZAP or manual code reviews to verify the security of JWT handling.

The execution of the tests resulted into this results:

Success Rate: 100% of requests returned a 200 OK.
Response Time: Average between 2-3.5 seconds per request.
Latency: Consistently between 250ms and 450ms.
Concurrency: The plan handled 5 concurrent users during an scenario of 20 messages in a conversation without failures or performance degradation.


Mark tasks triggered by all_success as upstream_failed ...

…if any upstream task is marked as upstream_failed

https://github.com/airbnb/airflow/issues/718

Yeah there's probably more of those... Until we find something more generic I'll just merge it in.


Filetree activity heatmap over project lifespan

It'd be useful to identify which parts of a codebase receive the most attention, especially over the lifespan of a project, broken down by activity / time bucket.
This would be a visualization that's complementary to #234.
y-axis: file-tree documents at a certain level
x-axis: time-bins in months, from most recent collection back to start of project
z-axis: number of PRs relating to the files in the x-axis row.
Some parts of the codebase will likely have large bursts of activity (docs, config) but be silent for other long periods, whereas high traffic parts (internal functionality) are more likely to be consistently 'red hot' in the heatmap.
This is useful because, from 30k feet, the application user can see where the traffic in the community is centered, where people are spending the most time, and where they can look in the codebase to find the core of the functionality of the project.
This would also help community managers to identify areas of the codebase that aren't high-churn, that maybe should be. Consider the docs folder- if it hasn't been updated in 18mos, maybe that should be checked in on.

Extension idea of this: z-axis having a flip mode to LOC

moved to other issue #


can't complie in android

Hi. first of all . Thanks for your work . that's pretty nice work.
in my exists project  can't complie in android studio
android studio 4.1.3
gradle 5.6.4
kotlin 1.3.24
i got error like kotlin version too high about this.
i wanna know how to work fine and don't change the kotlin version and gradle version.

The binary version of its metadata is 1.6.0, expected version is 1.4.2.

Hi @jamninetyfive
Could you attach original error, please?
I've used latest Kotlin version in example project, so yeah, it can be an issue😅

log.txt
log here .

@jamninetyfive could you check whether https://github.com/kirillzyusko/react-native-keyboard-controller/pull/5 fixes the problem?

it's work, thanks!


[Draft] Formatting for entire openfl namespace (including experimental)

Pylint score before any changes: 5.45/10
Edit: Pylint score after this PR: 8.09/10

[x] Convert all imports to be absolute.
[x] Migrate all imports to be on top-level.
[x] Sort all imports.
[x] Re-insert updated Copyright headers in all impacted files.
[x] Update Github actions workflow to use the new linting script.
[x] Format code.
[x] Clear all CI tests.

Reviewers, pls note: https://github.com/securefederatedai/openfl/blob/ac3ed37f13c8f8e1e9f7dd8f355545f6069d93c1/tests/openfl/interface/test_aggregator_api.py#L70-L77

This has been a tiring one. Request this be merged as soon as we can (ideally before any open feature PRs), so future PRs can make use of the updated code practices.


Refine README Badges

Added APM Installs, APM Version, ApppVeyor Shield, Slack Badge.
Adjusted Travis and Gitter Badge.

Thanks!


add proximity link

can i get a testing id

muse pushed with id 4383294b-2b44-4fed-a0b6-3e591c179904

pushed. please update and commit your local idea.json to match the changes
"id": "07354d78-1833-4a3a-9c54-58ad3ff3c2cd",
"predecessor": "4383294b-2b44-4fed-a0b6-3e591c179904",
"purpose": "exist. Links end visitors when they walk in given radius. fixes."


Resolve failed-precondition error

Move the firestore-rules logic to the client
Update the rules in the security store to prevent it from blocking the data access

Resolved by adding an Index in Firestore


Add empty space where there is no column

Fixes #1040
@XPoppyX could you verify whether this PR leads to the desired behaviour?

@gave92 Can you check if the seperater between the headers on the content is missing for you?

Selection:

file explorer:

Is it ok if the separator is like this?

@XPoppyX issue is only with drag-select right? just clicking should be ok

yeah, and it's not an annoying issue, so it's okay I guess

@XPoppyX last commit should fix the issue you reported 👍

@gave92 Great work!


drop support for julia 0.3

:+1:
Hopefully we can get rid of Compat in the tests soon!

Looks like there were some changes in 0.5:
[nl_convert] check comparison expansion
  Failure :: (line:-1) :: fact was false
    Expression: AmplNLWriter.convert_formula(expr) --> $(Expr(:quote, :(1 < 2 && (2 < 3 && 3 < 4))))
      Expected: :(1 < 2 && (2 < 3 && 3 < 4))
      Occurred: :((1 < 2 && 2 < 3) && 3 < 4)

But irrelevant to this PR.


Sortable functionality causes every item to be re-rendered during dragging

When using the sortable functionality, there seems to be a lot of re-rendering of items that have not changed. See this code sandbox:
https://codesandbox.io/s/intelligent-brook-vi0rsb
Whenever you click on an item, everything is re-rendered multiple times and whenever you drag to change the position, every item is re-rendered (see the console for the log that happens in the sortable item component or use the react dev tools). The example is using React.memo() on the sortable item component but it is still happening.
Is this expected? If so, is there a reason why as I don't see why all items have to be re-render instead of the 2 items that are changing and makes larger list harder to work with (when virtualization is not an option)?

Having the same issue. Even in list of 50 items it makes the situation unpleasant for the user if non-trivial components are getting rendered.

If anyone is still stuck on this issue, something that helped resolve it for me was to create a separate file/functional component for the SortableItem and pass in all of the props like such:
`import React, {ReactElement} from 'react';
import BeaconChartCard from 'Apps/beacon3ui/features/atAGlanceV3/beaconChartCard';
import {useSortable} from '@dnd-kit/sortable';
import {CSS} from '@dnd-kit/utilities';
import {DashboardSavedObject} from 'Apps/beacon3ui/services/waveApiSlices/waveSavedObjectsSlice';
import {BeaconDefaultAagChart, Chart, CompareChart} from 'Apps/beacon3ui/services/types';
export default function SortableItem(props: any): ReactElement {
const chart = props.chart;
const charts = props.charts;
const {attributes, listeners, setNodeRef, transform, transition} =
    useSortable({id: props.id});

const style = {transform: CSS.Transform.toString(transform), transition, border: 'none'};

return (
    <div
        className='card'
        ref={setNodeRef}
        style={style}>
        <BeaconChartCard
            chart={chart}
            defaultDashboard={props.defaultDashboard}
            dndAttributes={attributes}
            dndListeners={listeners}
            searchString={props.searchString}
            setCharts={props.setCharts}
            visibleCharts={charts} />
    </div>
);

}
`


cEUR support for contractkit

Expected Behavior
Once cEUR is deployed, the cli and the contractkit will need to be updated. See the proposal here.
**Contractkit: registry, wrappers (exchange and stabletoken), add it in balances. Gas payment is handled via the whitelist as token that can afford gas. Here we have two implementation choices. A) duplicate cusd wrapper. B) something generic for multiple new tokens of the future (if we know that a new stable is in a near future, we should think abut spending a little more time on this)

It looks like #6792 was closed, @martinvol are you sure this epic covers contractkit support?

Looking at the labels I assumed it did, is that not the case @aslawson

Per @nvtaveras the cEUR oracle work depends on this

Scratch that ^ there is apparently a workaround


Panic in reconcile loop and " Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource"

I was running the example in https://github.com/pulumi/pulumi-kubernetes-operator/pull/339, and when I updated the Stack resource to point to a new stackname (since I had used an invalid one initially), I saw this in logs.
E1019 04:36:47.002143       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.1/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource

Nothing else happened though, so I destroyed the app stack (the pulumi.com/v1/stack, Secret and source.toolkit.fluxcd.io/v1beta2/GitRpository resources).  That led to this:
E1019 04:37:19.908322       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.21.1/tools/cache/reflector.go:167: Failed to watch *unstructured.Unstructured: failed to list *unstructured.Unstructured: the server could not find the requested resource
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x1659330]

goroutine 1098 [running]:
github.com/pulumi/pulumi-kubernetes-operator/pkg/controller/stack.(*ReconcileStack).Reconcile(0xc0009324b0, {0x1d8f7a0, 0xc0004c6de0}, {{{0xc0006b36b0?, 0x198d120?}, {0xc0006b36a0?, 0xc0006d9840?}}})
	/home/runner/work/pulumi-kubernetes-operator/pulumi-kubernetes-operator/pkg/controller/stack/stack_controller.go:462 +0x2770
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc000950000, {0x1d8f6f8, 0xc000895800}, {0x18eaca0?, 0xc00055c3e0?})
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:298 +0x303
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc000950000, {0x1d8f6f8, 0xc000895800})
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:253 +0x1d9
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:214 +0x85
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
	/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.0/pkg/internal/controller/controller.go:210 +0x307

/home/runner/work/pulumi-kubernetes-operator/pulumi-kubernetes-operator/pkg/controller/stack/stack_controller.go:462
This line is after it should have bailed from not finding the resource; no wonder it's an NPE. I'll start with a test case to reproduce.

Which revision of the code were you running? If I look at either the default branch, 1.10.0-rc.0, or 1.10.0-rc.1, L462 is https://github.com/pulumi/pulumi-kubernetes-operator/blob/v1.10.0-rc.1/pkg/controller/stack/stack_controller.go#L462 (the second line here):
if instance.Status.LastUpdate != nil {
   if instance.Status.LastUpdate.LastSuccessfulCommit == currentCommit && !stack.ContinueResyncOnCommitMatch

I'm struggling to see that line leads to an NPE given the guard immediately before it. stack is a shared.StackSpec rather than a pointer. (L462 in the branch with the example is a closing brace).


fix ghcr.io org name for releases

We were using the QUAY_ORG instead of the ghcr org (which, by definition, is the repository_owner), so no one could pull it down.

Looks like we also need to update ci.yaml.