Back port DCHECK() removal

1. DCHECK_GE(num_voters, 1);
In UCC, we set VD to -2 , so (-2 / 2) + 1 = 0
However, DCHECK_GE(-2, 1); would aways fails
2. DCHECK(has_responded_);
In some cases, say in VD {"atn": 3}, but atn only has one voter. Then that atn starts an election, and all peers responds yes.
Election finishes in the sense that it gets votes from all peers, and LeaderElection destructor is called.
However, there is no ElectionResult yet, because candidate region does not have enough votes. (not satisfied, and still satisfiable).
This check will fail.
Test
Test and code review has been completed in fbcode

I already merged this. Rebase on 1.8.raft and I think you'll see there's no changes. 7fa3cfe542536756620c3b8ccfed83453eeb26b4

Close PR as change has already been made in trunk


Issue with Pehkui

When you use Pehkui mod with GravityChanger, motion multiplier doesn't change player's speed when your gravity is changed.

Gravity and scale works fine but now player animations don't scale properly. (When you're 1/16 of a normal scale, your limbs barely move, though they should move just like if they were normally scaled.) It's only visual glitch though, but still annoying.

Still happens in 1.18.1, and there also the issues of not being able to break blocks when in a another gravity and under 0.25 base scale


Complete rewrite

Goals/Plan
Might not get to all of these. Ideal case.

Better organization

Refactor code to make more sense
Structure bot components as a package instead of loose files

Better design principles

Make it as easy as possible to add new functionality.
In order to match the style of the discord.py rewrite, avoid god-classes
Move beyond lazily using json for everything

YAML for configs, db for everything else

Take advantage of more discord.py features

Especially new stuff in the rewrite branch of d.py
Use embeds more

Use actual logging
Take advantage of helpful packages, such as humanize and tabulate, rather than trying to roll my own bad solution

Cleaner, more readable code
Remove old, poorly written and rarely used commands/features.
Documentation, Documentation, Documentation

Have lots of local progress that will be pushed hopefully tonight.

Upcoming major change: database.
Json doesn't make a lot of sense for what it is used for here (especially the TagMap, which is awful and can be much better represented by a many-to-many relationship). Not only is it slow, it doesn't represent the data as well as SQL could. Configs have already been moving away from json, while really the db is a greater concern. As such, I plan to use SQLAlchemy and PostgreSQL for the majority of data storage.


Request credentials for an os-climate bucket

Requesting credentials for github user: jeffchenchengyi-bcg
Requesting credentials for the bucket: os-climate
Email address to send a credential download link<EMAIL_ADDRESS>Request checklist:

[✔] User can establish connection with the bucket
[✔] User can read files from the bucket
[✘] User can write files to the bucket

Sent invitation to join. Please reach out if you need anything further.


Restructer and expand examples

Test

Hello @rickvanveen! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file examples/01_basic_usage/plot_01_glvq.py:

Line 22:80: E501 line too long (84 > 79 characters)
Line 31:80: E501 line too long (90 > 79 characters)
Line 32:80: E501 line too long (87 > 79 characters)
Line 51:80: E501 line too long (92 > 79 characters)
Line 52:80: E501 line too long (95 > 79 characters)
Line 61:80: E501 line too long (86 > 79 characters)
Line 68:80: E501 line too long (95 > 79 characters)
Line 69:80: E501 line too long (95 > 79 characters)
Line 103:80: E501 line too long (96 > 79 characters)
Line 104:64: W292 no newline at end of file
Line 104:64: W292 no newline at end of file
Line 104:64: W292 no newline at end of file

In the file examples/01_basic_usage/plot_02_gmlvq.py:

Line 22:80: E501 line too long (84 > 79 characters)
Line 31:80: E501 line too long (90 > 79 characters)
Line 32:80: E501 line too long (87 > 79 characters)
Line 52:80: E501 line too long (93 > 79 characters)
Line 53:80: E501 line too long (95 > 79 characters)
Line 62:80: E501 line too long (86 > 79 characters)
Line 69:80: E501 line too long (93 > 79 characters)
Line 78:80: E501 line too long (81 > 79 characters)
Line 84:80: E501 line too long (83 > 79 characters)
Line 85:80: E501 line too long (93 > 79 characters)
Line 86:80: E501 line too long (90 > 79 characters)
Line 87:80: E501 line too long (95 > 79 characters)
Line 88:80: E501 line too long (95 > 79 characters)
Line 94:80: E501 line too long (85 > 79 characters)
Line 103:80: E501 line too long (97 > 79 characters)
Line 124:80: E501 line too long (83 > 79 characters)
Line 131:80: E501 line too long (96 > 79 characters)
Line 132:80: E501 line too long (97 > 79 characters)
Line 133:80: E501 line too long (90 > 79 characters)
Line 143:80: E501 line too long (88 > 79 characters)
Line 157:80: E501 line too long (97 > 79 characters)
Line 158:80: E501 line too long (96 > 79 characters)
Line 159:80: E501 line too long (87 > 79 characters)
Line 160:80: E501 line too long (93 > 79 characters)
Line 165:80: E501 line too long (96 > 79 characters)
Line 166:68: W292 no newline at end of file
Line 166:68: W292 no newline at end of file
Line 166:68: W292 no newline at end of file

In the file examples/01_basic_usage/plot_03_lgmlvq.py:

Line 20:80: E501 line too long (84 > 79 characters)
Line 29:80: E501 line too long (92 > 79 characters)
Line 30:80: E501 line too long (87 > 79 characters)
Line 51:80: E501 line too long (94 > 79 characters)
Line 52:80: E501 line too long (95 > 79 characters)
Line 61:80: E501 line too long (86 > 79 characters)
Line 67:80: E501 line too long (96 > 79 characters)
Line 68:80: E501 line too long (95 > 79 characters)
Line 69:80: E501 line too long (95 > 79 characters)
Line 70:80: E501 line too long (95 > 79 characters)
Line 71:80: E501 line too long (95 > 79 characters)
Line 72:80: E501 line too long (94 > 79 characters)
Line 101:80: E501 line too long (90 > 79 characters)
Line 102:80: E501 line too long (97 > 79 characters)
Line 107:80: E501 line too long (86 > 79 characters)
Line 108:80: E501 line too long (95 > 79 characters)
Line 112:80: E501 line too long (87 > 79 characters)
Line 158:80: E501 line too long (96 > 79 characters)

In the file examples/01_basic_usage/plot_04_NaNLVQ.py:

Line 6:80: E501 line too long (99 > 79 characters)
Line 7:80: E501 line too long (99 > 79 characters)
Line 8:80: E501 line too long (89 > 79 characters)
Line 9:80: E501 line too long (81 > 79 characters)
Line 41:80: E501 line too long (91 > 79 characters)
Line 42:80: E501 line too long (87 > 79 characters)
Line 59:80: E501 line too long (95 > 79 characters)
Line 64:80: E501 line too long (93 > 79 characters)
Line 65:80: E501 line too long (95 > 79 characters)
Line 74:80: E501 line too long (86 > 79 characters)
Line 78:80: E501 line too long (92 > 79 characters)
Line 84:80: E501 line too long (98 > 79 characters)
Line 85:80: E501 line too long (88 > 79 characters)
Line 86:53: W292 no newline at end of file
Line 86:53: W292 no newline at end of file
Line 86:53: W292 no newline at end of file

In the file examples/02_pre_processing/plot_01_pipeline_lvq.py:

Line 7:80: E501 line too long (98 > 79 characters)
Line 23:80: E501 line too long (95 > 79 characters)
Line 24:80: E501 line too long (94 > 79 characters)
Line 25:80: E501 line too long (94 > 79 characters)
Line 26:80: E501 line too long (90 > 79 characters)
Line 32:80: E501 line too long (97 > 79 characters)
Line 45:80: E501 line too long (96 > 79 characters)
Line 50:80: E501 line too long (86 > 79 characters)

In the file examples/03_model_selection/plot_01_crossvalidation_lvq.py:

Line 8:80: E501 line too long (93 > 79 characters)
Line 10:80: E501 line too long (82 > 79 characters)
Line 44:80: E501 line too long (96 > 79 characters)
Line 45:80: E501 line too long (90 > 79 characters)
Line 52:80: E501 line too long (90 > 79 characters)
Line 54:80: E501 line too long (91 > 79 characters)

In the file examples/03_model_selection/plot_02_gridsearch_lvq.py:

Line 6:80: E501 line too long (95 > 79 characters)
Line 7:80: E501 line too long (93 > 79 characters)
Line 8:80: E501 line too long (86 > 79 characters)
Line 39:80: E501 line too long (93 > 79 characters)
Line 43:80: E501 line too long (88 > 79 characters)
Line 58:80: E501 line too long (95 > 79 characters)
Line 64:80: E501 line too long (96 > 79 characters)
Line 65:80: E501 line too long (82 > 79 characters)
Line 66:80: E501 line too long (88 > 79 characters)

In the file examples/05_customization/plot_04_solvers.py:

Line 5:4: W292 no newline at end of file


Error in call to target 'models.mask3d.Mask3D'

Hello,  I met an error when I ran the command python main_instance_segmentation.py.  The error message is as follows:
wandb: WARNING `resume` will be ignored since W&B syncing is set to `offline`. Starting a new run with run id DEBUG_ABLATION.
wandb: Tracking run with wandb version 0.16.1
wandb: W&B syncing is set to `offline` in this directory.
wandb: Run `wandb online` or set WANDB_MODE=online to enable cloud syncing.
Error executing job with overrides: []
Error in call to target 'models.mask3d.Mask3D':
InstantiationException('Cannot instantiate config of type Res16UNet34C.\nTop level config must be an OmegaConf DictConfig/ListConfig object,\na plain dict/list, or a Structured Config class or instance.')
full_key: model

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
......

How can I fix it?

I met the same problems.

I had the same problem, have you solved it yet?

I had the same problem, have you solved it yet?

I am sorry. I have not soloved it.

Hello, may I ask how this issue was resolved? Can you share it? Thank you very much


updated the logo

A logo with the circular background was needed, so I have made a logo with high px quality, along with the size of 60X60 px, white background as per the instructions. Do let me know if you need any further changes here. Glad to help :)
I'm attaching the same file here so that it would be easy for you to review.

make the border white or remove the black one.

@reveurguy  please check the new commit.


Update docs to include information about removing android event listeners

Found those methods in the tests when looking for a way to remove the listeners in my app when the user is logged out. I think it's worth including them in the README.

can't someone merge this into master?


Typo in README

There is no tag with name "denormalizer"
services:
    uuid_denormalizer:
        class: GBProd\UuidNormalizer\UuidDenormalizer
        tags:
            - { name: serializer.denormalizer }

This should be
services:
    uuid_denormalizer:
        class: GBProd\UuidNormalizer\UuidDenormalizer
        tags:
            - { name: serializer.normalizer }

Yes ! Thank you !


UnboundLocalError in test_dt_accessor when dd._dask_expr_enabled is False

Describe the issue:
While attempting to construct debian packages for dask, I hit an UnboundLocalError while running the tests suite.  The test_dt_accessor seems to have a problem of scoping the ctx variable when dd._dask_expr_enabled returns False.
Minimal Complete Verifiable Example:
$ pytest dataframe/tests/test_accessors.py::test_dt_accessor
[...]
_______________________________ test_dt_accessor _______________________________

df_ddf = (  str_col  int_col                  dt_col string_col
E     abc        1 1970-01-01 00:00:01.000       <NA>
f     bcd...         ...        ...
h                 ...     ...             ...        ...
Dask Name: from_pandas, 1 graph layer)

    @pytest.mark.skipif(
        not PANDAS_GE_210 or PANDAS_GE_300, reason="warning is None|divisions are incorrect"
    )
    def test_dt_accessor(df_ddf):
        df, ddf = df_ddf

        assert "date" in dir(ddf.dt_col.dt)

        # pandas loses Series.name via datetime accessor
        # see https://github.com/pydata/pandas/issues/10712
        assert_eq(ddf.dt_col.dt.date, df.dt_col.dt.date, check_names=False)
        warning_ctx = pytest.warns(FutureWarning, match="will return a Series")
        # to_pydatetime returns a numpy array in pandas, but a Series in dask
        # pandas will start returning a Series with 3.0 as well
        with warning_ctx:
            ddf_result = ddf.dt_col.dt.to_pydatetime()
        with warning_ctx:
            pd_result = pd.Series(
                df.dt_col.dt.to_pydatetime(), index=df.index, dtype=object
            )
        assert_eq(ddf_result, pd_result)

        assert set(ddf.dt_col.dt.date.dask) == set(ddf.dt_col.dt.date.dask)
        if dd._dask_expr_enabled():
            # The warnings is raised during construction of the expression, not the
            # materialization of the graph. Therefore, the singleton approach of
            # dask-expr avoids another warning
            ctx = contextlib.nullcontext()

>       with ctx:
E       UnboundLocalError: cannot access local variable 'ctx' where it is not associated with a value

/usr/lib/python3/dist-packages/dask/dataframe/tests/test_accessors.py:127: UnboundLocalError

Anything else we need to know?:
The below patch works around the issue by sticking as closely as possible to the semantic of the test without reducing coverage, but I am not confident at all it is a proper approach given the repetition of the same test item, so I haven't proposed a merge:
--- dask.orig/dask/dataframe/tests/test_accessors.py
+++ dask/dask/dataframe/tests/test_accessors.py
@@ -123,8 +123,11 @@
         # materialization of the graph. Therefore, the singleton approach of
         # dask-expr avoids another warning
         ctx = contextlib.nullcontext()
-
-    with ctx:
+        with ctx:
+            assert set(ddf.dt_col.dt.to_pydatetime().dask) == set(
+                ddf.dt_col.dt.to_pydatetime().dask
+            )
+    else:
         assert set(ddf.dt_col.dt.to_pydatetime().dask) == set(
             ddf.dt_col.dt.to_pydatetime().dask
         )

I believe someone more fluent than I am with Python or with dask codebase will surely find a much better approach.
Environment:

Dask version: 2024.5.2
Python version: 3.12.3
Operating System: Debian sid
Install method: source

Thanks for the issue @emollier. I'm able to reproduce and pushed a fix up over in https://github.com/dask/dask/pull/11177

Hi James,
James Bourbeau, on 2024-06-13:

Thanks for the issue @emollier. I'm able to reproduce and pushed a fix up over in https://github.com/dask/dask/pull/11177

You're welcome, glad that helped!
Have a nice day,  :)
Étienne.


PSR-2 for the Queue component

Only a few of those actually fall under the Rule. Argument lists don't have to be split across multiple lines, but if they are....
From the psr2 official guidelines:

Argument lists MAY be split across multiple lines, where each subsequent line is indented once. When doing so, the first item in the list MUST be on the next line, and there MUST be only one argument per line.

When the argument list is split across multiple lines, the closing parenthesis and opening brace MUST be placed together on their own line with one space between them.

Please, can you point to a piece of code where you think I made a mistake? I will check it.
As I get it:
Correct:
$this->method($a, $b);

Correct:
$this->method(
    $a,
    $b
);

Error:
$this->method(
    $a, $b
);

P.S. I used phpcs for checking psr-2.

No mistake, just some unnecessary changes.


#87 Use https for media urls

Fixes #87

I ended up making this change myself, some additional changes were necessary.


Label Python external SchemaTransform with its URN

Doing this so that we can identify the transform URN when looking at a pipeline DAG.

stop reviewer notifications

LGTM. Thanks.


Cube demo does not broadcast mouse events. Other scenes work perfectly.

There are no Spline events in that scene, it's used only to demo the code.
Please submit another bug if you're having issues with Spline events not being broadcasted.


Tests regression

Description
Full test suite has been implemented for all ipynb files. Along with that a starter template has been added that will help make adding all future demos easy in the new testing suite. This has also gong through quite a bit of changes as I have gone, and I do plan to continue improving this now that the first version of these tests is passing. e.g. I learned later about the ".to" function, so there are some checks using the IN_GITHUB variable that can be simplified.
These tests do take a really long time to execute though, and you cannot replicate the execution locally without having it run in the GItHub specific environment due to unknown settings they have in place that affect the execution. My plan is that as I have more time to work on this project to make some changes when I start for the day, do something else on the project while the GitHub actions run, and as I improve the individual demos, submit smaller more digestible pull requests. The goal is to figure out a way to remove as many of the IN_GITHUB flags as I can. For the time being, everything is passing, and everything is ready for new demos to be submitted with minimal inconvenience on the creator.
Fixes #213
Type of change
Please delete options that are not relevant.

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

Screenshots
Please attach before and after screenshots of the change if applicable.

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have not rewritten tests relating to key interfaces which would affect backward compatibility

@bryce13950 Thanks again for this! I think what I'd like is for someone to go through each and see that the output is scientifically as expected. I'll tag some people on the slack.

[ ] Activation_Patching_in_TL_Demo.ipynb
[ ] Attribution_Patching_Demo.ipynb
[ ] Exploratory_Analysis_Demo.ipynb
[ ] Grokking_Demo.ipynb
[ ] Head_Detector_Demo.ipynb
[ ] Interactive_Neuroscope.ipynb
[ ] LLaMA.ipynb
[ ] Main_Demo.ipynb
[ ] No_Position_Experiment.ipynb
[ ] Old_Demo.ipynb
[ ] Othello_GPT.ipynb
[ ] Tracr_to_Transformer_Lens_Demo.ipynb

I'm optimistic I'll get people to look at these eventually :) @bryce13950  sorry it's taking so long.

No worries! I should have some time to mess around with it a bit next week. The execution of this was basically untouched in anything but GitHub, so there shouldn't be any differences. Some of these did not work before though, so that may be a bit of challenge to track down when they last worked.

@alan-cooney I would discuss some of this with @jbloomAus. We had discussions about this topic, and decided that separating them on branches was going to make them harder to maintain in the future. As for the length of time, the purpose of separating the notebooks onto their own runner group is to mitigate this issue. The tests for the code checks are still run first, and still fail first in case a change in a pull request breaks an existing test. Within 5-10 minutes the developer will know if they are going to break the tests in 95% of the cases.
If we want to speed up these tests as is, there is a flag in all of these files that we can use to skip parts that take a long time, which are not important to test. As for converting them to py files, and then running them that way, I do not believe that is going to achieve the desired effect of making this code test faster, since the underlying reason these take so long to test is due to how much stuff is actually happening in these sets of code. As is, to run these in an environment like colab, some of these can still take close to an hour to fully complete. One thing that would speed up everything is to check if there are parts of the code that are iterating a lot, and dropping that number down drastically when run in GitHub. I did go through and do some of that, but I did not do it systematically. It is on my list of things to do to improve the second iteration of this.
For now, I want to get it in the code base, so I don't have to worry about continuously merging large changes into these files. The goal is to make those small incremental improvements to individual examples after this large change is merged, so that those improvements can be more easily managed. In order to mitigate this time need for the time being, we could also set it up, so that this test group only runs when we are ready to publish a release. There were a number of issues with these files when I went through them, but they are going to likely break very infrequently now that they have been fixed, so only running this test group periodically would probably suffice in achieving the point while keeping the day to day pull request workflow unimpeded.

@alan-cooney @bryce13950

As a general rule, entire CI/CD workflows should take less than 10 minutes to run (ideally less than 5). This is because if someone submits a PR they should be able to grab a tea and then come back and see any issues, so that they can make changes and work synchronously. If the checks take much longer, it means that they have to leave it and come back later, which creates a lot of friction and slows down work a lot.

This is generally true but I wanted to have the tutorials tested to track when we were breaking them. Doesn't have be triggered on every PR, maybe on releases? Would that work @alan-cooney ?

In addition, notebooks are just not great for version control and it's really hard to see what has changed between revisions. I'm thinking a better approach here may be to store the notebooks as .py files and then first run a tool that converts them to notebooks (and publishes this to e.g. an "examples" branch), and then secondly runs your checks here. It would be great if you're able to make both changes (either here or as separate PRs), and I can review that (and ask Neel to update his links to the notebooks to keep them working as well).

I don't think I'm opposed to python files (or python files that produce jupyter notebooks on a separate branch). What I was advising against was always having all of these files on a separate branch (not sure if that's being suggested).

Hey both,
Responses here, and I've also suggested a high level approach to resolve this:

The tests for the code checks are still run first, and still fail first in case a change in a pull request breaks an existing test. Within 5-10 minutes the developer will know if they are going to break the tests in 95% of the cases.

The problem is that since these notebooks use a lot of the underlying functionality of TransformerLens, it's pretty likely that they will fail if e.g. a bug is introduced (the codebase otherwise has relatively sparse testing). This is of course assuming that we get them to install from the local directory rather than from using the pypi/main branch version.

If we want to speed up these tests as is, there is a flag in all of these files that we can use to skip parts that take a long time, which are not important to test.

Great yes I think this is the better approach - to skip things that take too long. Let's do this in this version at a minimum.

As for converting them to py files, and then running them that way, I do not believe that is going to achieve the desired effect of making this code test faster, since the underlying reason these take so long to test is due to how much stuff is actually happening in these sets of code.

This part is not to make them run faster, it's just to make it easy for maintainers to review changes to the notebooks (as you can then view the diffs).

This is generally true but I wanted to have the tutorials tested to track when we were breaking them. Doesn't have be triggered on every PR, maybe on releases? Would that work @alan-cooney ?

I think they'll regularly break with bugs introduced in the underlying lib, so I think it's better to run on every PR.
Suggested Approach
The way I think we should tackle this is to convert all the notebooks to .py files (using e.g. jupytext) and have those as the checked in versions. These are easy to use and view changes. Then we have 2 GitHub action pipelines:
Notebook checks pipeline
This can be added to the existing checks pipeline (runs on all PRs) and does the following:

Build the notebooks using jupytext
Config pip to use the local version of TransformerLens (not from PyPi or GitHub)
Run pytest with nbmake (or alternatively we may be able to test the notebooks directly now they are .py files)

Notebook deploy pipeline
This runs after checks on every push to main where the notebooks have changed, and does the following:

Build notebooks using jupytext
Publish changed notebooks to a different protected branch (e.g. notebooks) that only contains built notebooks. This is simply a place to store the deployed notebooks, so that they can be used directly with e.g. Colab.

Closing as stale, but feel free to re-open if you want


'NoneType' object has no attribute 'get_filings'

When I'm doing company = Company(cik), it works fine for CIK-1067491 and fetches filings but for CIK-927628 it returns null with a Warning message :
`WARNING
To use get_company() provide a valid cik or ticker.
                    e.g. to get by cik
                    >>> get_company(91184670) or get_company("0091184670")

                    or to get by ticker

                    >>> get_company("SNOW") or get_company("snow")`

I tried upgrading all packages to latest version but didn't help.

Did you try
Company(927628)

Company("1067491")

Infosys


fix: add option to decode unicode in order to prevent crash

Solves https://github.com/privateOmega/html-to-docx/issues/130
As far as I've been able to test, it works fine. But please, do test it thoroughly!

@tasola Please resolve the conflicts in this. Thanks

@privateOmega Fixed! I also added a description of the flag in the README.

@tasola Sorry for getting to this late, but could you please rebase instead of merge with develop, thats our default strategy.

Also please add html-entities into rollup-config's external array

@privateOmega Excuse my delay as well! Done!


Investigate issues with booting from disk

Inconsistent issues in Python with booting from disk that were not present during early 1.0 testing, not sure of the cause yet. login.py in particular is failing in a few different ways on different builds.

even though booting doesn't work, I'd like some way to set a hard drive as the main drive instead of using a tempfs, so I can keep my work.

I do want to look into overlay filesystems, so that a live CD's content could be supplemented with changes and new files from a persistent source, but resolving the issues with booting from an ext2 partition on a disk is more important.

Fair enough, It's obviously stopping quite a bit of progress.


Update hyperdiffusion tendencies in sgs equations to use 3d vector form

https://github.com/CliMA/ClimaAtmos.jl/pull/1658 Updates the grid-mean equations.
Similar updates to the expressions for subgrid-scale hyperdiffusion tendencies are necessary.

Closed because the scope of #1658 has been extended.


Tune the antlr performance by warming up cache

Warming up antlr cache when postmaster starts up, then the first query will be accelerate by the cache.
Task: BABEL-4595
Description
[Describe what this change achieves - Guidelines below (please delete the guidelines after writing the PR description)]

What is the change? This is best described in terms of “Currently, Babelfish does X. With this change it now does Y.” Think of “What did it used to do?” and “What does it do now?”

Why was the change made? What drove our desire to put effort into the change?
How was the code changed should only appear for large commits. This can serve as a rough roadmap to what’s contained in the commit. It should be very high level; if it’s directly referencing code it’s probably too detailed. It’s also critical that this section of a commit message does not try to replace proper code documentation (ie, block comments or README files). Generally, this section should only appear if the commit itself is large enough that it’s helpful to provide a roadmap to someone looking at the commit.
The last descriptive piece is the “title” for the commit: the very first line of the commit message, which should typically be less than 80 characters. A good title is critical, because it’s the only thing that shows up in places like the Github commit listing. No one’s got time to read through full commit messages when trying to find a single commit out of dozens.

Issues Resolved
[List any issues this PR will resolve]
Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

15 of 19 (78.95%)  changed or added relevant lines in 2 files are covered.
1439 unchanged lines in 9 files lost coverage.
Overall coverage increased (+0.05%) to 74.432%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/tsqlwarmup.cpp
13
17
76.47%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tsql/src/tsql_for/forxml.c
1
93.25%

contrib/babelfishpg_tsql/src/catalog.c
1
87.15%

contrib/babelfishpg_common/src/datetimeoffset.c
51
85.05%

contrib/babelfishpg_tsql/src/dbcmds.c
92
75.44%

contrib/babelfishpg_tsql/src/pl_handler.c
129
90.16%

contrib/babelfishpg_tsql/src/rolecmds.c
151
83.08%

contrib/babelfishpg_tsql/runtime/functions.c
200
83.45%

contrib/babelfishpg_tsql/src/pl_exec-2.c
217
81.72%

contrib/babelfishpg_tsql/src/pl_exec.c
597
44.32%

Totals

Change from base Build<PHONE_NUMBER>9:
0.05%

Covered Lines:
44922

Relevant Lines:
60353

💛  - Coveralls


#[pyo3::pymodule] triggers missing documentation for a module lint

Bug Description
I'm using roughly this code:
#![warn(missing_docs)]

#[cfg(feature = "pyo3")]
pub use version::PyVersion;

mod version;

#[cfg(feature = "pyo3")]
#[pyo3::pymodule]
#[pyo3(name = "_pep440_rs")]
/// Python bindings shipped as `pep440_rs`
pub fn python_module(module: &pyo3::Bound<'_, pyo3::types::PyModule>) -> pyo3::PyResult<()> {
    module.add_class::<PyVersion>()?;
    Ok(())
}

This causes a lint error:
warning: missing documentation for a module
  --> src/lib.rs:51:1
   |
51 | #[pyo3::pymodule]
   | ^^^^^^^^^^^^^^^^^
   |
note: the lint level is defined here
  --> src/lib.rs:35:9
   |
35 | #![warn(missing_docs)]
   |         ^^^^^^^^^^^^
   = note: this warning originates in the attribute macro `pyo3::pymodule` (in Nightly builds, run with -Z macro-backtrace for more info)

This lint error is confusing, because i didn't define a rust module (i defined a function) and that function has a docstring.
 Did you use a virtualenv?
pyenv, yes.
Additional Info
No response

I think the problem here is, that #[pymodule] creates a Rust module (at the same visibility as the function) during macro expansion. As a workaround you could just make python_module private or pub(crate), which will not trigger the lint. The real solution is probably to emit #[doc(hidden)] on that module during expansion.

Yep, given that all items inside of that module already have #[doc(hidden)] attached, I think it's reasonable to also hide the module itself. I opened #4067 to fix that.


feat(ssrf): adds rules to check for IP based SSRF

extends the original IPs handled in RFI rules to IPv6 and other IPv4 evasions
added the regular expressions used to data file
tests check the expressions

Signed-off-by: Felipe Zipitria<EMAIL_ADDRESS>

I'd like to see this into the rules file that #2163 renames.

Is this is a generic attack now, or is it because two rules are not too much to throw in new files?

What about the new ssrf_score? Does it make sense to people here?

I'm personally not a fan of the separate scores, but some people are. In this particular case I doubt it makes much sense, unless it's really a separate rule group.
Generic or not: There are a lot of different rule categories. Adding a new rule category / group brings at least 8 administrative rules. That's a lot if it's only going to be 2-3 rules. So I think we need a group for "various rules". In my eyes, the new generic rules group was such a place.

Meeting decision December: This PR will be shifted into the new category "generic attacks" after #2163 is merged.

SSRF rules, 🎄 edition! 🎉

moved rules to "generic attacks"
added all tests for each bypass

Before merge, we just need to think:

right now it is applying only to ARGS: do we need additional variables?
any other transformation to prevent evasions?

Meeting decision January: @franbuehler will review it and pass it to @lifeforms for testing.

We're you able to review this one @franbuehler ?

Hi @fzipi,
Sorry for my late reply. I didn't see your ping.
No, unfortunately not yet...

I will run the rule on traffic starting next Wednesday.

Can you give us an estimate on the number of requests for this?

I should improve my logging, but if I look at some access_logs from yesterday, I think something like 2 million requests.

Thank you.
 (Sadly also no true positives)


Use of self

I noticed Application+Route uses self unnecessarily:
public final func get(path: String, handler: Route.Handler) {
    self.add(.Get, path: path, handler: handler)
}

These usages should probably be removed as the consensus is to only use self when required (see the rejection of SE-9).

This is consistent throughout Vapor, not an isolated to this specific case.  We had a discussion on this a few weeks ago and opted to continue using self. for the sake of clarity, despite the guidelines.

I think that's a very bad idea and a dangerous precedent. There's been enough discussion about this proposal on the mailing lists and it has been ultimately rejected. Vapor should not place itself above this. Practices that go against Swift's accepted guidelines will only deter possible contributors. I know I would think twice about spending time on a project that doesn't care enough about Swift to follow its guidelines.

I agree, self should be removed to reduce bugs.

I'm all for a revisit, I'm personally not a fan, but have been using self. for consistency of style.

@ketzusaka: What bugs does using self. introduce?  The rejection posting on this seemed to be philosophical, not technological, mainly around "visual clutter".
@svanimpe: I'd say this is an exception, not a rule.  We generally follow Swift guidelines, we're not going around actively seeking them to break.
From the rejection posting:

This proposal spawned a massive, polarized discussion with 200+ messages involving 80+ participants. We’re thrilled at the enthusiasm and thank all who participated. There were many, many interesting points made, along with experience reports from various Swift code bases, ideas to help mitigate the concerns that motivated the proposal, and so on. Quantitatively, the overall community assessment of the proposal was roughly 5:2 against requiring “self.”.

And:

Individuals or teams that feel that explicit “self.” is beneficial for their own code bases can enforce such a coding convention via tooling with the status quo. If this proposal were accepted, those opposed to the proposal would effectively have no recourse because the language itself would be enforcing “self.”.

Unless I'm misunderstanding, by not accepting the proposal to require self., it was left up to individual projects to decide whether to use it.  If it had been accepted, there wouldn't be an option and everyone would be forced to use self..  While I prefer self., I'd oppose a proposal to require it as well.
Either way, when I jump into open source projects I follow what's been established in the project itself.  If Vapor switches to dropping self., I'll begrudgingly follow along.  My vote though, would be to continue using it as I find it impossible to follow code without it.

The proposal is against requiring the use of self.. It doesn't mention anything about recommended style. If there are some important points from the mailing list about why using self. is bad, then I'm interested to hear them.
But being clear that you are using a member variable vs a local variable has a lot of utility. Take the following example.

class Foo {
    var bar: String

    func baz() {
    	/* Various code here */

    	//I want to add to the member variable here
    	bar += "..."
    }
}

Some time later...

class Foo {
    var bar: String

    func baz() {
    	//Other dev adds local variable
    	//They have no idea this is going to change
    	//the functionality of the code below
    	var bar = ""

    	/* Various code here */

        //Now this is not working
    	bar += "..."
    }
}

@tannernelson Your example is why we write tests in the first place.
@shnhrrsn The key bug commonly introduced by always using self is retain cycles, which is scary to for a server program. See: http://www.magicalpenguin.com/blog/stop-using-self-for-methods-and-properties
The use of self within the codebase was extremely frightening to me when I first looked at Vapor. self always feels unnecessary, and often leads to bugs like the one mentioned in the above blog post.

I think the rejection rationale makes a strong case against explicit self, which is why I see it as a recommendation not to use self` unless necessary (and not just as a rejection of requiring it).
In all my years (15) of programming, I have never ever written a single bug that could have been solved by using explicit self. Any decent IDE or editor should make it clear if you're referencing a property or a local variable. I wholeheartedly agree with the rationale that explicit self adds nothing but visual clutter, which is annoying to write and makes code harder to read and understand.
@tannernelson: Prefixes like m are actually frowned upon in Java.

@ketzusaka I'm not sure I buy this as a good reason, if you're always used to using self in closures, you're going to end up doing it anyway.

@svanimpe Can you please supply a link to the rejection rationale? From SE-9 all I can see are reasons to use self. The community response section is full of good reasons.

@shnhrrsn you don't always use self in closures. i think it's on the rarer side.
Swift has always been about safer code. Explicit use of self goes against that..

The rejection rationale can be found here.

Mandatory “self.” introduces a significant amount of verbosity that does not justify itself with added clarity. While it is true that mandatory “self.” may prevent a class of bugs, the cost of eliminating those bugs is fairly high in terms of visual clutter, which goes against the generally uncluttered feel of Swift.

Well that's pretty clear.
If that is where the Swift team stands, then Vapor should follow. Despite my personal preference.


Installation errors: Tensorflow-protobuf incompatibility with tensor flow v2.13.0

Hello all,
I tried to install the DIRT renderer using a variant of the described docker approach since the original DockerFile didn't work for me. I'm using the following libraries:

Using this setup, I get exceptions during the pip install . command:

I believe this error is related to a mismatch between tensor flow 2.13.0 and protobuf 4.24.0.
Did anyone recently succeeded to install the Dirt renderer using the described docker approach, or knows how this dependency mismatch can be fixed? As I wrote before, installing all libraries using the same version numbers are specified in the provided DockerFile didn't work for me.

As far as I know we can solve the tensorflow mismatch by using pip install -e . --no-deps.  I can install dirt successfully but when I import dirt I got errors.

@NaToh5 Thank you for your fast reply. I'll give this a try. What kind of errors do you get when you import dirt?

I am still finding a way to solve these errors . Look like this repo is really old and no longer supported by developer.
I go this error when I import dirt. I run on both linux and window, still have same errors.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\ADMIN\Desktop\Project\dirt\dirt\__init__.py", line 2, in <module>
    from .rasterise_ops import rasterise, rasterise_batch, rasterise_deferred, rasterise_batch_deferred
  File "C:\Users\ADMIN\Desktop\Project\dirt\dirt\rasterise_ops.py", line 6, in <module>
    _rasterise_module = tf.load_op_library(_lib_path + '/librasterise.so')
  File "C:\Users\ADMIN\anaconda3\envs\Octopus\lib\site-packages\tensorflow\python\framework\load_library.py", line 61, in load_op_library
    lib_handle = py_tf.TF_LoadLibrary(library_filename)
tensorflow.python.framework.errors_impl.NotFoundError: C:\Users\ADMIN\Desktop\Project\dirt\dirt\librasterise.so not found

I am not sure how can I find that librasterize.so ?
I have this under dirt/dirt

Thank you for helping me. Do you have any social media accounts (Wechat? ) We can discuss more on there.

Thank you for helping me. Do you have any social media accounts (Wechat? ) We can discuss more on there.

You're welcome. I don't have WeChat, but I'm happy to further discuss this issue.

I already search that file , there is no librasterise.so file on my PC. I am not sure what should I do next. You can share with me any social media app that you are comfortable with.

Let me think about the social media platform…
There is another issue that seems related:
https://github.com/pmh47/dirt/issues/100
It seems that you had installation errors so that the .so library didn’t
get installed. Apparently it can be solved by downgrading cmake.
On Fri, 18 Aug 2023 at 11:14, NaToh5 @.***> wrote:

I already search that file , there is no librasterise.so file on my PC. I
am not sure what should I do next. You can share with me any social media
app that you are comfortable with.
—
Reply to this email directly, view it on GitHub
https://github.com/pmh47/dirt/issues/114#issuecomment-1683612183, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHYXEV4AM26XPUPC4G4JLS3XV4W6RANCNFSM6AAAAAA3UQVWGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok, I will try it. In case you can install it and run successful. Please let me know.

Please read the README, which says Linux is required. This repo does not support Windows. librasterise.so would, on Linux, be built automatically during the installation.

@pmh47  thank you for your reply. But I already try on my Linux PC, still have same error. I already try pip install -e . --no-deps and install successfully, but when I import dirt I got same error like window.
So I am trying to install with Cmake again on Linux,  I can run cmake ../csrc successfully, however when I run make,  I got many errors, so I cannot install with cmake process for now on my Linux.
Please help me to solve my issue.

This parameter packs not expanded error is a gcc/nvcc bug, not a problem in DIRT itself; using g++ 10 should fix it; see e.g. https://github.com/NVlabs/instant-ngp/issues/119

@pmh47 I still got this error when I run cmake ../csrc . I already have nvcc version 11.5

@aquatic282 did you solve it ? I have an error when I run the python test/test.py I  got this error
 2020-04-16 11:39:05.592220: F /home/frank/Documents/dirt/csrc/gl_common.h:46] extensions eglQueryDevicesEXT, eglQueryDeviceAttribEXT and eglGetPlatformDisplayEXT not available

I stopped my attempt to install the DIRT renderer and continued working on another project. Now I'm trying to install it again but don't seem to find a suitable Docker container configuration that works for me.


Crash in Sketch 42

Hi there,
in Sketch 42, we've removed an exception we used to have for NSAppTransportSecurity, so now you're only allowed to load remote content over HTTPS. The Rad Faces feature tries to load content over HTTP, and that's crashing Sketch 42.
You may want to look for an alternative URL for that JSON that uses HTTPS.
Hope it helps!

Is the same with Persona > Female, Male or Neutral ? Because I can't load any data from it.

I miss Rad Faces 😢  You could use InVision's Craft plug-in, and navigate to the faces from there using their Web tab

So that doesn't even work now, since Craft recognizes it's not via HTTPS. I found a solution though, I used the Custom tab in Craft, and made my own collection using local files:


kconfig: Abusive/undocumented syntax

Describe the bug
In the tree we can find the following undocumented Kconfig syntax:
config FOO
	default BAR

as a short for
config FOO
	default y if BAR

with FOO being a bool
For instance:
config USB_CDC_ACM
	default SERIAL

This syntax is unclear as when reading it can suggest that FOO is selecting BAR option.
Also it is undocumented.
Expected behavior
This syntax should be forbidden and existing occurrences cleaned up
Impact
This makes kconfig.defconfig files reading quite confusing.
Logs and console output
One example:
https://github.com/zephyrproject-rtos/zephyr/blob/c211cb347e0af0a4931e0e7af3d93577bcc7af8f/boards/nordic/nrf52840dongle/Kconfig.defconfig#L30-L48

Expected behavior
This syntax should be forbidden and existing occurrences cleaned up

Certainly not, this is a common shorthand, see also Linux kernel tree.
https://docs.zephyrproject.org/3.6.0/build/kconfig/tips.html#common-kconfig-shorthands

In the tree we can find the following undocumented Kconfig syntax:
...
as a short for

no, actually that's not what this means, the construct:
config FOO
	default BAR

actually means default the value of BAR to the value of FOO.
Now with bools this really doesn't change anything in practice, because at the end of the day, whether you do:
default y if BAR, meaning assign y if BAR is also y.
or you say
default BAR, assign the value of BAR to this setting, results in same value
but if starting to play with combinations of strings and bools, then the difference becomes clearer, for example:
config FOO_STRING
        string
        default "foo"

config BAR_BOOL
        bool
        default FOO_STRING # <-- illegal, because a string cannot be assigned to bool.

config BAR_BOOL
        bool
        default y if FOO_STRING = "foo"

Not a bug.

Thanks for the feedback. Then it would need to be documented in the, otherwise fairly complete, Kconfig tips and tricks doc page.
Does it sound reasonnable ?

An example is used, but the shorthand is not explicitly documented in https://docs.zephyrproject.org/latest/build/kconfig/tips.html#common-kconfig-shorthands.

yep, seems that the docs could be improved, but that should be under setting of values and not a short-hand.
A short-hand is where the short syntax actually means the same as the long syntax.
And that is not the case with default BAR, as that is assigning a value.

https://github.com/zephyrproject-rtos/zephyr/pull/73270


[FTU] - Add Pi

Is your feature request related to a problem? Please describe.
Nil.
What is the feature request?
Add Pi.
Describe the solution you'd like
Nil.
Describe alternatives you've considered
Nil.
Additional context
Nil.

adding pi is easy just use
from math import pi

adding pi is easy just use
from math import pi

yeah, but we want to give different variations of pi.

yeah, but we want to give different variations of pi.

22 over 7, 3.14 and calculator pi

22 over 7, 3.14 and calculator pi

That seems good too
On Sun, Jan 3, 2021, 12:04 PM CodeAsherPlayz<EMAIL_ADDRESS>wrote:

22 over 7, 3.14 and calculator pi
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/PythonMathCalculator/python-math-calculator/issues/20#issuecomment-753575590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIJBH3DKUMY6PW5CPF7PLTSYAFWRANCNFSM4VRTV4SQ
.

That seems good too
On Sun, Jan 3, 2021, 12:04 PM CodeAsherPlayz<EMAIL_ADDRESS>wrote:

22 over 7, 3.14 and calculator pi
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/PythonMathCalculator/python-math-calculator/issues/20#issuecomment-753575590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASIJBH3DKUMY6PW5CPF7PLTSYAFWRANCNFSM4VRTV4SQ
.


[JBEE-256] Convert Jakarta Activation to JBoss Jakarta Activation

Jira issue: https://issues.redhat.com/browse/JBEE-256

Upss, sorry, wrong upstream


Not able to match sound mode: Multi In + Neural:X

Not able to match sound mode so it appears this sound mode needs to be added.
Thank you in advance
source: Game
sound_mode: Multi In + Neural:X
media_title: Game
media_content_type: channel
sound_mode_raw: Multi In + Neural:X

This PR will add the sound mode.

Available in 0.7.6


Please add support to connect falcon and llama models with this .

Please add support to connect falcon and llama models with this .

This has been referenced in #27

One idea for this is that you could allow up to two local models to be loaded and assigned to one or more agents. We could load one model into the GPU and the other into the CPU with some RAM allocated to it. So say llama2 into the gpu and use it for most of the agents, and then a Python optimized smaller model into cpu for the engineer agent.

In theory a long running process could:

accumulate a queue of prompts/tasks for a specific agent
swap the engine to that agent and load it in 10-30s
perform actions and save the queue results of the agent
then prepare queues for other agents from results
repeat at 1.

This would allow us to use big models more efficiently, not accumulating a lot of time penalty for VRAM loading times on swaps.

@andraz @j-loquat your solution and suggestions are looking good to implement.

One thing to consider with local LLM agents is that we should keep the prompts shorter than for OpenAI and reduce the temperature to perhaps lower than 0.5. Lower temp and shorter prompts makes a huge difference in local response times as per GPT4All project.

Hello, regarding the use of other GPT models or local models, you can refer to the discussion on our GitHub page: https://github.com/OpenBMB/ChatDev/issues/27. Some of these models have corresponding configurations in this Pull Request: https://github.com/OpenBMB/ChatDev/pull/53. You may consider forking the project and giving them a try. While our team currently lacks the time to test every model, it's worth noting that they have received positive feedback and reviews. If you have any other questions, please don't hesitate to ask. We truly appreciate your support and suggestions. We are continuously working to improve more significant features, so please stay tuned.😊


Update zio, zio-test, zio-test-sbt to 2.1.4

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #645.


Slow track transitions - implement crossfade maybe?

I noticed huge (2-5 seconds) silence gaps between tracks when playing music from koel in Chrome on Linux. Could this be avoided? Maybe even implement crossfade option?

Currently, this gap comes from downloading the next song (or part of the song). You can reduce it by making sure you have enough (upload) bandwidth. There is no prefetching of the next song IIRC, and no crossfading in Koel right now.

The next song in the queue should be buffering before the current song ends.

Yes, but if you don't have enough bandwidth, the player will stop between songs. There is no "bandwidth adaptive streaming" in Koel, that triggers downloading at the right time. Right now, it's set to 10s before the end of current song (that the next song is preloaded, IIRC), and this might not be enough if you can't load enough of the song to start decoding it. For MP3, it's usually not an issue since they are small w.r.t upload bandwidth (and you can start playing with only part of the files downloaded), but for large files, it is.
In a perfect world, the "upload bandwidth" should be estimated and so should be the next's song minimum decoding size, and the preloading should happens at the right time to ensure the next song will be here when required (this is what's called usually prefetching: making sure the data is ready when required). Both of these requirements are difficult right now (understand: not done).

In theory you can tell if thats the case by how long it takes for the first song to play.

Thank you for the explanation. I have enough bandwidth (~10Mbit/s) between server and client, my mp3s are mostly <10Mb files, but gaps are still too long, up to 5s. Hopefully prefetching and crossfading will be implemented in koel some time down the road. It looks like cool piece of software, browsing its simple interface is nice, but listening to music from it is far from satisfactory at the moment, because of too long gaps between tracks, and playback stops on Android/Chrome.

@pacija if you just click on a song play, does it take 15 seconds till it starts playing?

15 is really extreme, but for me who is used to crossfade playback, even 2 seconds of silence between tracks is too much. If I click a song it takes about 2 seconds to start playing, and grey line which indicates how much of a track is buffered is half full. It would be better listening experience if it started sooner, waiting less to be buffered.

A workaround might be an option (yes, yet another option) to determine the "time until the current song ends" to start prefetching. I'm not a fan of the idea, though, to be honest. Too nitty-gritty for me.

I'm not fan either of such option. Maybe (and it's an hypothetic maybe) we could preload the next song when the current song has finished loading (so no need anymore to have a "preload" time before end of current song). In all cases, whatever the actual bandwidth, you can't do better anyway than this. This might even permit crossfading in the future...

Is "prefetching"different then the buffering we do now?


Add OS Version to Deprecations & Output Issues via Text or Other File Formats

:bulb:Add OS Version to Deprecations
Would be nice to a specific versions of OS that the deprecations for payloads are noted.
Also, would be nice to be able to export out as text or "share sheet functionality" issues to make it easier to distribute it via other mechanisms.
:white_check_mark: Proposed solution
Add details for operating systems that the deprecation applies when listing payload is deprecated.
:adhesive_bandage: Alternatives Solutions + Workarounds
Research it yourself outside application.
:information_source: Additional context
For example on "Deprecation" icon, could add OS version its deprecated to bottom image, etc.

For example, would be nice to have an export as text, or some other file format or use share sheet via OS?

Low Profile relies on the Profile-Specific Payload Keys metadata, which currently does not provide OS versions for when keys are deprecated. For example, the Parental Controls (Game Center) payload properties metadata is sourced from here: ParentalControlsGameCenter
Apple does, however, provide this metadata in the Device Management Client Schema project. For example: com.apple.gamed.yaml
Low Profile relies on Yams for YAML parsing, which currently does not support circular references that exist in the schema. Until https://github.com/jpsim/Yams/issues/274 is fixed, or until I find a clever way around the circular references, Low Profile may just have to wait for this feature to be implemented 🙏
Regarding the exporting of issues, Low Profile does support exporting a full report to a .lowprofile file (which can be opened on another Mac). What was the specific use-case you had in mind regarding the export of issues?


Build settings fixed.

Build settings fixed. I checked out the code to check the project settings. So I fixed this. You can take pull now.

@ashar02 Could you make sure it merges correctly with master branch? Thanks!

Are you facing any conflict in its merging?

Yup, a lot. Please hold on cause I think I have a solution for the quality
stuff we discussed yesterday.
2016-05-10 11:50 GMT-03:00 ashar_clary<EMAIL_ADDRESS>
Are you facing any conflict in its merging?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/zevarito/Licode-ErizoClientIOS/pull/27#issuecomment-218181920

--
Alvaro

okay, let me send you again.


Enable SourceMgrDiagnosticHandler in importers.

This is a strict improvement over not having a diagnostic handler.
Also introduces a stub pass for cleaning up TensorFlow locations but I have not yet found an algorithm I like so just leaving it as a stub for later.
Progress on #5295

This breaks the integrations build. It looks like presubmits didn't run. Kokoro has been wonky (first noticed on Friday). https://source.cloud.google.com/results/invocations/1cf1254a-8fa0-4298-86bb-cd7699b2f9f9/targets/iree%2Fgcp_ubuntu%2Fcmake-bazel%2Flinux%2Fx86-swiftshader%2Fmain/log
ERROR: /tmpfs/src/github/iree/integrations/tensorflow/iree_tf_compiler/BUILD:74:10: C++ compilation of rule '//iree_tf_compiler:iree-import-tflite' failed (Exit 1): clang failed: error executing command /usr/bin/clang -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -fcolor-diagnostics -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 245 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox clang failed: error executing command /usr/bin/clang -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -fcolor-diagnostics -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 245 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
iree_tf_compiler/iree-import-tflite-main.cpp:79:19: error: variable has incomplete type 'llvm::SourceMgr'
  llvm::SourceMgr sourceMgr;
                  ^
external/llvm-project/mlir/include/mlir/IR/Diagnostics.h:22:7: note: forward declaration of 'llvm::SourceMgr'
class SourceMgr;
      ^
1 error generated.

I think https://github.com/google/iree/pull/5612 will fix this, fyi.

I think #5612 will fix this, fyi.

Yeah just saw that, thanks


Change order of groups on plots

Jordan requested the ability to change the order of groups in the dot plot.
This can be done in R by re-factoring the metadata column in question. A user interface for choosing the order can be created using the drag-and-drop interfaces in the sortable package.
For defaults, it would be reasonable to re-factor categorical metadata with str_sort(numeric=TRUE) so groups are plotted in lexicographical order.

This feature now exists as described for ridge plots and cell type proportion plots.


feat(background): store spent amount on payment to retrieve balance

Context

Closes #272.
Changes proposed in this pull request

Saves grantSpentDebitAmount as amountSpent in storage, which we can later use to retrieve balance. To handle race conditions, we store the max of amount spent in the batch of multiple (possibly parallel) calls.
Extracted from https://github.com/interledger/web-monetization-extension/pull/379, but using throttling instead of debouncing.

Extension builds preview

Name
Link

Latest commit
2fa592980569aa17b90e318dbf144a65f0179c89

Latest job logs
Run #9759865145

DownloadDownload


Add option to dig so we can specify type

Specify the type as a parameter to dig (e.g. NS, TXT, MX) and return a list, similar to how it currently returns multiple A records.
Currently the action can only return A records since that is the default to dig, this PR adds a new parameter and sets the default to "A".

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

@armab wonder if you can approve the workflows next time you are online for this PR. Issue: https://github.com/StackStorm/st2/issues/5772
Sorry to bug you, but wasn't sure if I need to reach out for visibility that these are queued or not.

@cognifloyd looks like some CI checks are failing on the new pants stuff. Are they expected to fail?

No it should not be failing. I'll look into what's wrong.

The pants CI fix is in #5782


Poor search results

When searching for tracks, via youtube on pimusicbox, many relevant results seem to be omitted. The issue seems to be related to special characters, search results with the character '-' almost never appear. This vastly reduces the usability of the youtube service as music is generally uploaded with the naming convention  - .
The puzzling thing is that occasionally a track will appear with the '-' symbol, this is making it difficult to troubleshoot. Am I the only one experiencing this? It's happening with multiple fresh installs of 0.6. I have not seen many similar complaints, and I would expect a lot.

I am playing a track from "Sense Field" on Spotify while writing this, yet searching for "Sense Field" does not show any artists at all. No even when searching for "Sense".
Besides all that it's way too slow to be usable.

Did you try to limit the search to spotify only? Slow backends are mostly out of our control.

And this original issue is specifically regarding youtube results, not Spotify. Please make your own issue and make it in the musicbox-webclient repository.

Thanks, wasn't aware of the other repo. https://github.com/pimusicbox/mopidy-musicbox-webclient/issues/160

Mopidy-youtube was upgraded in 0.7.0rc4. Please reopen if this issue is not fixed. If you can provide the exact steps to reproduce the problem that would be very helpful.

I am currently away from my pi but I will check out the new release when I can and see if there are improvements. Having used the youtube api (which I believe is what is being used in the background here) in an unrelated ruby based project and getting similar issues with the results (although subjectively less pronounced) I am now inclined to believe thats where the issue is. Possibly an issue in how searches are defined?
I will try to look into it myself when I have the time.


nixos/zfs: check pool state with -d, like import

This can avoid unnecessary wait-looping for pool to be 'ready' on some systems when the paths don't match
Description of changes
add the same zpool import -d <dir> argument to the import command used to check pool readiness, as is used when actually importing the pool.  This makes the check symmetrical with the import, and helps avoid unnecessary delays when the pool requires the specified -d path to be found.
However, it's not entirely clear why some systems require this argument, even if it seems like a sensible change. Discussed in Matrix with @ElvishJerricco, more detail in comments to follow.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

On one system I have two pools I want imported at boot: rpool added via the filesystems.* detection in stage1, and a secondary on an internal sata ssd, imported in stage2 via boot.zfs.extraPools = [ "opool" ];.
Without this patch, the zfs-import-opool systemd unit hangs for ~ 1m15s before importing, and the disk lightls flicker each second. Adding some debug confirms that this is looping 60 times around the poolReady() check and 1s sleep, before importing successfully. It also confirms that the -d argument makes the difference:

a plain zpool import (as used by the ready check) sees no pools ready to import
a zpool import -d … sees the pool ONLINE and ready to import, from the first iteration.

However, I'm still not sure why. I don't see the same behaviour interactively after login. I don't see the same behaviour on another system with the same setup. There's something going on with the zpool import command I don't yet understand. Guesses include some difference of state in the zpool.cache file, or perhaps with the way the disks are labelled between systems, but I haven't had the time and energy to pursue this all the way to full diagnosis just yet, since it involves rebooting my main workstation each time.  I would like to.
Regardless, this makes the two import attempts symmetrical and seems like a correct change.

In the meantime, I've done some more debugging.  strace confirms that zpool import is looking at devices under /dev and /sys/block, including the device(s) that contain the pool in question.
There is something amiss with disk labelling though, some disks are not showing up in blkid or with the /dev/disk/by- symlinks that would be expected.
Here's another example, from a different host, of a pool that only imports with -d /dev/disk/by-id.

[root@ilus:~]# zpool status cpool
  pool: cpool
 state: ONLINE
  scan: scrub repaired 0B in 02:48:45 with 0 errors on Mon Dec 18 13:44:14 2023
config:

	NAME                        STATE     READ WRITE CKSUM
	cpool                       ONLINE       0     0     0
	  mirror-0                  ONLINE       0     0     0
	    wwn-0x5000c500c4791fbd  ONLINE       0     0     0
	    wwn-0x5000c500ccfe3f82  ONLINE       0     0     0

errors: No known data errors

[root@ilus:~]# zpool status -L cpool
  pool: cpool
 state: ONLINE
  scan: scrub repaired 0B in 02:48:45 with 0 errors on Mon Dec 18 13:44:14 2023
config:

	NAME        STATE     READ WRITE CKSUM
	cpool       ONLINE       0     0     0
	  mirror-0  ONLINE       0     0     0
	    sdd     ONLINE       0     0     0
	    sdc     ONLINE       0     0     0

errors: No known data errors

[root@ilus:~]# sgdisk -p /dev/sdc
Disk /dev/sdc:<PHONE_NUMBER> sectors, 3.6 TiB
Model: Expansion Desk
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 89CD8EF2-05CB-0F4D-A4D6-1EC6BC1F43F9
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is<PHONE_NUMBER>
Partitions will be aligned on 2048-sector boundaries
Total free space is 3692 sectors (1.8 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048<PHONE_NUMBER>   3.6 TiB     BF01  zfs-06cca00f4ac3e221
   9<PHONE_NUMBER><PHONE_NUMBER>   8.0 MiB     BF07

[root@ilus:~]# sgdisk -p /dev/sdd
Disk /dev/sdd:<PHONE_NUMBER> sectors, 3.6 TiB
Model: Expansion Desk
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 5A8719C3-9E21-D24B-96AF-24FD0F760BD6
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is<PHONE_NUMBER>
Partitions will be aligned on 2048-sector boundaries
Total free space is 3692 sectors (1.8 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048<PHONE_NUMBER>   3.6 TiB     BF01  zfs-7403528230ddb949
   9<PHONE_NUMBER><PHONE_NUMBER>   8.0 MiB     BF07

[root@ilus:~]# blkid /dev/sdc
/dev/sdc: PTUUID="89cd8ef2-05cb-0f4d-a4d6-1ec6bc1f43f9" PTTYPE="gpt"

[root@ilus:~]# blkid /dev/sdd
/dev/sdd: PTUUID="5a8719c3-9e21-d24b-96af-24fd0f760bd6" PTTYPE="gpt"

[root@ilus:~]# blkid /dev/sdc1

[root@ilus:~]# blkid -p /dev/sdc1

[root@ilus:~]# blkid -p /dev/sdd1

[root@ilus:~]# lsblk | grep 'sd[cd]'
sdc                                                                        8:32   0   3.6T  0 disk
├─sdc1                                                                     8:33   0   3.6T  0 part
└─sdc9                                                                     8:41   0     8M  0 part
sdd                                                                        8:48   0   3.6T  0 disk
├─sdd1                                                                     8:49   0   3.6T  0 part
└─sdd9                                                                     8:57   0     8M  0 part

[root@ilus:~]# l /dev/disk/by-partlabel/
total 0
drwxr-xr-x 2 root root 120 Dec 18 20:13 .
drwxr-xr-x 9 root root 180 Dec 18 20:12 ..
lrwxrwxrwx 1 root root  10 Dec 18 20:13 export_cache -> ../../sda1
lrwxrwxrwx 1 root root  10 Dec 18 20:13 export_NAAAVAPH -> ../../sdb1
lrwxrwxrwx 1 root root  10 Dec 18 20:13 export_NAAAYS0N -> ../../sde1
lrwxrwxrwx 1 root root  15 Dec 18 20:13 export_slog -> ../../nvme0n1p5

[root@ilus:~]#

note:

blikid just doesn't print anything for the partitions (which seems to be why zpool import ignores them). The partitions for other pools have all the expected UUIDs, TYPE="zfs_member", and so on.
the zfs-UUID labels don't show up in by-partlabel, whereas others do.

So, this is all very weird, but I feel is a separate bug (probably in zfs that made these labels?), and this change is still correct on its own.


Sometimes worker nodes are Unavailable for long time on scaling up

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Have an rke cluster- AWS - 1 etcd, 1 control plane and 1 worker node. in v2.2.8
Upgrade to rancher master latest - 4c7e3263a - commit id.
Scale up the number of worker nodes

Expected Result:
The scaled up worker node should come to Active state.
Actual Result:
It is taking really long for the worker node to come up Active.
Error seen:

Note:
Even after 10 minutes, it failed to come up.
Scaled up worker node by 1 more. Then both the scaled up nodes came up Active quickly.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.2.8 to rancher-master
Installation option (single install/HA): single

@sangeethah @sowmyav27 can we fetch these details once you see the issue happening again:

kubectl get nodes // see if the node appears in the output
See if the node agent gets deployed successfully on the host. If it does, get the logs from the node agent container.

Same issue was observed on Rancher HA installations when provisioning new clusters or scaling up node pools. As visible in the screenshot below, the nodes have a status ready in downstream K8s API but not in Rancher API.

Rancher v2.2.8
Management Cluster: K8s v1.14.6
User Cluster: K8s v1.14.6
RancherOS v1.5.3
Docker 18.9.2

This appears to be a node syncer issue. I was able to workaround this issue by triggering an update of the v3.Node in some other way (ie adding a description).

@ibuildthecloud 's PR here https://github.com/rancher/rancher/pull/22866

For testing:
This issue can be tested by observing the revision numbers of the v3.Node objects on provisioning via kubeclt get nodes.management.cattle.io -n <cluster-namespace> -o yaml | grep "revision"
These values before these fixes should be high (over 300 for the worker before this fix). After this fix they should be under 100 after provisioning.
For posterity: The root cause of this issue was high contention on nodesyncer.go which was resolved by fixing a loop bug between syncLabels and labels.go

verified on rancher:v2.3.0-rc4
Steps:

Deploy and rke DO cluster with 3 nodes - 1 etcd, 1 control plane and 1 worker node.
The worker node is initially in Unavailable state - with the Runtime error on the UI.
But it comes to Active quickly, less than a minute.
Verified by scaling up the worker nodes also.
The nodes come up to Active state quickly. They do not take much time like mentioned in the issue - https://github.com/rancher/rancher/issues/22669#issue-490048097

Also the generation numbers on rancher:v2.3.0-rc4 with the fix is : (on a cluster with 3 nodes, scale up the number of worker nodes, and observe the generation numbers)
kubectl get nodes.management.cattle.io -n c-2bpwx -o yaml | grep "generation"
    generation: 33
    generation: 25
    generation: 25
    generation: 33
    generation: 33

In rancher:v2.3.0-rc3 without the fix: (on a cluster with 3 nodes, scale up the number of worker nodes, and observe the generation numbers)
kubectl get nodes.management.cattle.io -n c-gmckf -o yaml | grep "generation"
    generation: 10
    generation: 606
    generation: 4
    generation: 89
    generation: 2
    generation: 319


Setup Django

Setup Django and configure it for the project

also change the database to mysql and maintain a requirement.txt file and describe about the setup
like : dependencies , project_name , app name , database ,etc

create a superuser also and start a app for the user_auth(login /registration/ and logout ).

I would like to work on this issue.

use "postgresql" as a database instead of MySql

use "postgresql" as a database instead of MySql
but mysql is mentioned in readme file

This seems to have been taken care of.
Closing this.
Thanks, @pythongiant.


pythonPackages.apache-airflow: broken on 20.03

Describe the bug
ERROR: Could not find a version that satisfies the requirement pandas<1.0.0,>=0.17.1 (from apache-airflow==1.10.5) (from versions: none)
ERROR: No matching distribution found for pandas<1.0.0,>=0.17.1 (from apache-airflow==1.10.5)
builder for '/nix/store/p506y8fw0sgsgdnqf04yvs1ij144gdkf-python3.7-apache-airflow-1.10.5.drv' failed with exit code 1

https://hydra.nix-data.org/build/209
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

@costrouc @ingenieroariel

@GrahamcOfBorg build python37.apache-airflow

Seems to build for me in 296793637b22bdb4d23b479879eba0a71c132a66


🐛 [Transmission NAS] Cannot move downloaded data to other CIFS directory

Description
I have four shared folders on my NAS that is accessible to transmission user, and I'm using SMB/CIFS for sharing.
all the folders are accessible and configured inside the addon, via docker exec I can find the folders and the path is mounted correctly. but when I try to move to another folder when the torrent is downloading or downloaded, it cames to an error and not move any file. only creates some 0kb files on the destination.
Reproduction steps
1. download a torrent
2. right click on the torrent go to set location, and choose another CIFS folder
3. if "move data" is NOT selected, it only creates a 0kb file
4. if "move data" is selected, the torrent came to an error:

[Error text]
Couldn't move '/mnt/Transmission' to '/mnt/Filmes': Unable to copy: Unable to read/write: No such file or directory (2)

Addon Logs
nothing is showed on the addon logs

Architecture
amd64
OS
HAos

any news about that?

Hi sorry I don't really see how to help as the cause could be the addon, the system, or tranmission itself... I'm using the qbittorrent addon and it automatically moves my files from one folder to another after download but I've never tried from one CIFS folder to another.
Perhaps you could use a script to do it instead? I think transmission can execute a script after the download is complete
Perhaps it would be easier if you downloaded to a single CIFS folder, but with subfolders below to manage "downloading" vs "downloaded" ?

do you have github link for me to asking them about this issue? I believe it could be something about move one mounted folder to another. they are in the same Filesystem btw

Hi Alex, I've changed my client to your version of qbittorrent that it fixed my demand, you can close this ticket.
thank you for all

Thanks! sorry I didn't see any potential solution for your initial issue but qbittorrent is a great app too :-)


Slow CSS animation performance on Linux.

Describe the bug
CSS seem animations / transitions to be much slower than in Chromium and Firefox (at least on Linux). You can notice this if you go to pages that make heavy use of CSS animations.
If I use a transparent window especially, I get low FPS / stuttering even on a simple page with only a few CSS animations. EDIT: This is incorrect, apologies.
Using this benchmark, with the engine set to CSS Transitions and number of Dots set to 50, I get these results:

Vivaldi Browser (Chromium): ~100 FPS
Epiphany Browser: ~14 FPS
Wry (hello_world.rs): ~14 FPS

Note the Epiphany browser is also slow, so to me this seems to be an issue with WebKit.
Steps To Reproduce

Edit the hello_world.rs example to go to this URL: https://greensock.com/js/speed.html (or any other CSS animation heavy page)
Run cargo run --example hello_world --release
If using the above benchmark, set "Engine" to CSS Transitions and "Dots" to a small amount (I used 50).

Expected behavior
CSS animations should be smooth like in Firefox or Chromium. The FPS should be comparable to other browsers.
Screenshots
Video of the benchmark running in Wry:
https://user-images.githubusercontent.com/13304815/174199291-461be883-55ab-42f3-81e3-be35c87855b7.mp4
Platform and Versions (please complete the following information):
OS: Arch Linux
Rustc: 1.61.0 (fe5b13d68 2022-05-18)
Would you assign yourself to resolve this bug?

[ ] Yes
[x] No

Additional context
Hardware:  AMD Ryzen 3900X, Nvidia GTX 980ti, 32GB RAM.

I've also just noticed that there's stuttering on that page when moving the mouse, no matter the selected engine. Curious thing is, it doesn't stutter in Epiphany, so that seems like an issue in Wry?
Video of stuttering:
https://user-images.githubusercontent.com/13304815/174200010-274d5565-7e1e-4550-b4c2-338d36f98513.mp4

I was a little stupid, and I was moving my mouse while testing transparent windows, which caused the stuttering I mentioned above. From a cursory search I can't find this problem being reported previously, so I'll make yet another issue about it.

Closed by #618


List items being interpreted as lists?

I am using block-content-to-react for some basic rich text. Somewhere in the pipeline it is turning what should be:

Alpha

Bravo

Charlie

Into

Alpha

Bravo

Charlie

Which is affecting the numberd list and intended spacing for the elements.
Here is what I have in sanity and what I expect:

...but here in staging it breaks what should be a list into multiple lists:

I am facing the exact same issue for the past 2 weeks, that was present on a 1.x.x release also updating to 2.0.7 doesn't solve the problem.
However got me thinking and found out that the list items are sent as single nodes rather than a node with multiple children.
One idea (which I haven't implemented due to time constraints) is to cycle on each node until the prop listItems doesn't exist anymore and then render the collected children on a custom component instead invoking the block serializer.

@OllieJT @luigimannoni Are you by any chance sending each block item to the renderer separately? Like mapping over them and passing them in? That will produce this kind of output. If you instead pass in the whole array of block items it should render correctly.

If you are able to reproduce this issue in the @portabletext/react module, let us know!
Closing this as we are missing reproduction data.

Sorry @rexxars completely forgot about this issue.
Coincidentally I had picked up an old codebase in these weeks with this exact bug happening again after updating the block to content, latest sanity client and latest react.
I have solved by using @portabletext/react instead


Microservices that use a webhook should replace PROVIDER_BASE_URL with WEBHOOK_BASE_URL

Description
The gateway microservices that use webhooks previously used the environment variable PROVIDER_BASE_URL as the webhook target server. The social-app-template has adopted a new nomenclature using WEBHOOK_BASE_URL. All micro services should be in sync with the social-app-template and use the new nomenclature.
Acceptance Criteria

[ ] All microservices that use webhooks use WEBHOOK_BASE_URL to provision their webhook.

Actually, WEBHOOK_BASE_URL in SAT is meant to be used with services that allow for webhook registration a la content-watcher. Any Gateway services currently using a statically-configured webhook should instead adopt an ability to dynamically register webhooks.


Kore 2.4.4 : New function "Play on local device" not working if kodi http password is set

Hi!
I just tested the new function "Play on local device" with the 2.4.4 version under Android 7.0, and Kodi 17.6.
Sadly, this function doesn't work for me when the webserver is password protected, but works fine if I remove the password, whatever the player is (VLC or the movie player shipped with the phone).
Should you need more info or test, please just let me know.
All the best.
Smeulf.

Fixed in #576.


./tool/android-build failed by no such file src/Algorand/Transaction.cpp

Describe the bug

Task :trustwalletcore:externalNativeBuildRelease
Build TrustWalletCore_armeabi-v7a
ninja: Entering directory `/Users/xxx/wallet-core/android/trustwalletcore/.cxx/cmake/release/armeabi-v7a'
clang++: error: no such file or directory: '../../../../../../src/Algorand/Transaction.cpp'
clang++: error: no input files

Task :trustwalletcore:externalNativeBuildRelease FAILED

FAILURE: Build failed with an exception.
To Reproduce
./bootstrap.sh
./tool/android-build
Expected behavior
build pass

Need's to be delete android/trustwalletcore/.cxx  dir


proposal:  feat: add report bug button

Summary
Add "Report an Issue"  button on the top right corner
Background
We are currently expanding and concerned about the stability of our released application. We want to leverage our beta testers and public to continuously release patch versions.
Proposed Solution

Add "Report an Issue"  button on the top right corner

Implementation Plan
@Dineshjnld

Add a "Report an issue" Red button
Styling: color: #751919.  on hover it should transition to #2B3A4F
Onclick: it should open this is link in the new tab: https://github.com/DeCenter-AI/decenter-ai.streamlit.app/issues/new?assignees=&labels=bug&projects=&template=00-bug.md&title=bug%3A++


Unfortunately go template if does not shortcut

Go template's {{if ...}} does not shortcut its tests therefore it is
possible to cause a NPE unless you separate ifs into two.
Fix #11230
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Very weird though.

https://github.com/golang/go/issues/31103


Difference between Old folder and top-level Resource folder.

Hi @sgotti,
Running into the same problems you ran into trying to get a persistent cluster up. Opening an issue since its the best way to contact you. Can you provide a quick update of the changes you made since? Seems like there is no longer a requirement to use ip address and so the new solution is a statefulset of n members where n is the number of etcd pods.
Thanks.

Ah, thanks for the quick reply. Awesome. I was looking at https://hk.saowen.com/a/74678175df97e5cfb694be8f9e47b59833f8e062c7e6669145e4d63a7004c056 which hasn't been updated with the latest solution.
Am I right to say this set up takes care of dead pod/node rescheduling at the kube level. e.g. if a pod dies or a node goes out, the statefulset will create the pod and attach it to the correct PV asap. However, this does not take care of disruptions in etcd space, hence the need for the preStop hook to remove etcd from the cluster so the pods can properly join.
Is this hook defined in the latest etcd.yaml file, or am I missing something? Also, is my understanding correct when I say because the prehook removes the associated etcd node from the cluster if/when pods are killed, any internal etcd churn should not affect applications, since it cluster views this as a decrease in size instead of a quorum loss (unless all members are lost).
I'm curious how this set up has been working for you in terms of reliability. Can you comment on that? Our use case is somewhat similar to yours in that we are using it to coordinate in-house brokers that are managing queues - data inconsistency can result in hairy situations.
Surprised more people have not shouted about this problem.

However, this does not take care of disruptions in etcd space, hence the need for the preStop hook to remove etcd from the cluster so the pods can properly join.

Can you provide more details? I don't understand what is "disruption in etcd space".
In a real life scenarios with a persistent etcd data if a node crashes or is manually stopped the etcd cluster will continue to work and then the node can rejoin without the need to remove it from the cluster, and the same will happen with k8s. So, as I explained in the post, I don't understand why the node should be removed from the cluster when the pod is stopped (and also it's not guaranteed that the preStop hook is executed: i.e k8s node crashes).

I'm curious how this set up has been working for you in terms of reliability. Can you comment on that?

My environments are active for months and tested various crash scenarios, also a full k8s cluster restart doesn't gave any problem. Etcd versions upgrades (for example 3.2.2 to 3.3.8) also worked quite well (update the etcd.yaml with the new image version and kill a pod by one or setup automatic statefulset rolling upgrades).
My suggestion is always to try it and stress it with any possible failure.

Thanks!


ACCUMULO-4511 Removed Accumulo Examples

Moved code and documentation to new accumulo-examples repo
Updated references in user manual
Update README.md to reflect the change
Example docs and source are no longer included in tarball

See https://github.com/apache/accumulo-examples/pull/1 for corresponding PR to add examples to new repo.


fix(resolver): ipld, double-fetching, and trailing slash fixes

closes #207
closes #383

So I can confirm that this fixes a bug on main that I discovered when looking into weird behaviour with getting to validate https://github.com/n0-computer/iroh/pull/411


Using 'back' mouse button while in Recycle Bin causes crash if there are many items in Recycle Bin

Description
Files crashes if you attempt to go back to the previous directory, while in the Recycle Bin folder and there are items in it.
Steps To Reproduce

Have a recycle bin with several items in it (I can't reproduce it with the Recycle Bin empty)
Navigate to some other directory
Navigate to the recycle bin using the same tab
Use the 'back' mouse button to try to go back to that other directory from step 2
Files crashes

Steps to fix
To fix issue:
Be able to return to previous directory after going to the Recycle Bin, without needing to have an empty Recycle Bin all the time.
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22621.521
Windows Version
Windows 11 Pro Version	22H2  OS build 22621.521 	Windows Feature Experience Pack 1000.22634.1000.0
Relevant Assets/Logs
debug_fulltrust.log
debug.log

Are you using column view?

It's in 'adaptive'.

Is this an issue in the preview version? https://files.community/download/preview

Seems like that fixed it!


⚡ Feature | Add CTA on mobile

While waiting for the hamburger menu to be deployed later, we need to be able to write a new story at any time on the mobile version.
To do that, place a mobile CTA (Use this Figma file for the CTA: https://www.figma.com/file/uPVMeBq0bERyViiRMXzLN8/Sigle-design-system?node-id=2635%3A5002) On the top right corner of the followed pages:

Drafts
Published
Analytics
Profile (The page is not working on mobile version tho)

FIGMA FILE : https://www.figma.com/file/elxKahbV8rj85IWOEyZeVu/Product-design?node-id=4662%3A31674

@QuentinSaubadu isn't it better to just fix the hamburger menu? This seems like work that will be removed soon no ?


Cannot install firebase-ios-sdk

Description
I am starting an iOS project from scratch and am trying to add the firebase-ios-sdk according to the instructions in the console. I've selected the following setup.

When I attempt to add the firebase package, I get the following errors:

 and

If I select to add anyway, no amount of refreshing caches/updating/quitting Xcode, clearing DerivedData gets me able to move forward. I was hoping to use this for my new app. Help a dev out?
Reproducing the issue
Create a new iOS project in Xcode, register it in the Firebase console and try to add firebase-ios-sdk package.
Firebase SDK Version
9.0.0
Xcode Version
14.0
Installation Method
Swift Package Manager
Firebase Product(s)
Analytics
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
I cannot find this file

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

I've managed to create it using Xcode 13.

For others having the same issue:
I could install it with Xcode 14 by setting the minimum version to to 9.6.0


[MNOE-426] - Logged additional events

@ouranos for review

Thx @hedudelgado !

@ouranos you can have a look, I moved logic in to_audit_event for widgets, for the others extra parameters are contextual to the call so I left them as additional metadata.
I also merged existing metadata with provided ones rather than replacing.

@ouranos ready for final review

@ouranos ivar reverted


Issues with Sockets

Hey there, I am having issues with the sockets on Windows 11. I recently transferred a project from one PC to another, the previous one being Windows 10, and the new one being 11. After setting up the venv and all that again, I get a new issue. I tried backdating the websockets install; but it didn't do anything. It's running the same version of pyvts as before, too. The only change is a new PC. Obviously, the "Remote Computer" in this given error is not remote, but the same PC. I have no strange anti-virus or anything that I could imagine would block ports; just a bog standard Windows 11 Pro install. The error happens when running to attempt and create the connection; this happens on script startup.
python=3.11.6
websockets=11.0.3
pyvts=0.3.1
It keeps giving me this full error log:

Exception in thread Thread-3 (run_vtube_studio_connection):
Traceback (most recent call last):
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 1045, in _bootstrap_inner
self.run()
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 982, in run
self._target(*self._args, **self._kwargs)
File "C:\MiquellaMain\Waifu-master\utils\vtube_studio.py", line 33, in run_vtube_studio_connection
asyncio.run(vtube_studio_connection())
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\runners.py", line 190, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "C:\MiquellaMain\Waifu-master\utils\vtube_studio.py", line 36, in vtube_studio_connection
await VTS.connect()
File "C:\MiquellaMain\Waifu-master\venv\Lib\site-packages\pyvts\vts.py", line 70, in connect
self.websocket = await websockets.connect(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\MiquellaMain\Waifu-master\venv\Lib\site-packages\websockets\legacy\client.py", line 655, in await_impl_timeout
return await self.await_impl()
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\MiquellaMain\Waifu-master\venv\Lib\site-packages\websockets\legacy\client.py", line 659, in await_impl
_transport, _protocol = await self._create_connection()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 1090, in create_connection
raise exceptions[0]
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 1069, in create_connection
sock = await self._connect_sock(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 973, in _connect_sock
await self.sock_connect(sock, address)
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\proactor_events.py", line 726, in sock_connect
return await self._proactor.connect(sock, address)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\windows_events.py", line 846, in _poll
value = callback(transferred, key, ov)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Michola\AppData\Local\Programs\Python\Python311\Lib\asyncio\windows_events.py", line 633, in finish_connect
ov.getresult()
ConnectionRefusedError: [WinError 1225] The remote computer refused the network connection

I... was being dumb. I forgot I had to turn on the VTube Studio API after I installed it on the new computer. Turned it on in the menus, worked first try.
No issues now. If anyone in the future gets this "ConnectionRefusedError: [WinError 1225] The remote computer refused the network connection", you need to turn on the API in VTube Studio, as there is no open socket to send it to otherwise lol.


Testnet- Failed to redirect to sign transaction

I opened an a testnet on Banana- Wnear recently, but it show error as tittle. i can not add  liquidity for them, some pics attd. Pls help!

Dear user,
Thank you for reaching us. I searched for the transaction on the explorer, here, and I found the following failure reason:
{
  "ActionError": {
    "index": 0,
    "kind": {
      "FunctionCallError": {
        "ExecutionError": "Smart contract panicked: panicked at 'Failed to deserialize input from JSON.: Error(\"missing field `pool_id`\", line: 1, column: 62)', ref-exchange/src/lib.rs:54:1"
      }
    }
  }
}

I suggest reaching out to ref.finance support directly, as it seems that later on you were able to add liquidity to some pools (as from here).
Let me know if you have any other questions, or I can close this issue


Data API not obeying cache control headers with Edge CDN

Describe the bug
When using the Enterprise Edge CDN, it is not obeying the cache control headers for the Data API. We should be able to set these headers in the config.
We have a simple CRUD app which we update data, and it's unacceptable to wait 5+ minutes or purge the cache every time to see these updates.
To Reproduce

Set the Cache-Control headers in the staticwebapp.config.json file.
Turn on enterprise edge
Turn on data API
Go to website, and notice results are getting cached.

Expected behavior
The Cache-Control headers should be obeyed by Data API when using Enterprise Edge.
Screenshots

Any feedback on this? This seems like a huge bug that would prevent anyone from using Data API with enterprise CDN.
I know it's "in preview" which is the saving grace right now.