Contributor

class Solution {
public:
vector<vector> updateMatrix(vector<vector>& mat)
{
vector<vector>dp(mat.size(), vector(mat[0].size(), INT_MAX-100000));
for(int i=0; i<mat.size(); i++)
{
for(int j=0; j<mat[0].size(); j++)
{
if(mat[i][j]==0)
{
dp[i][j]=0;
}
else
{
if(i>0)
{
dp[i][j]= min(dp[i][j], dp[i-1][j]+1);
}
if(j>0)
{
dp[i][j]= min(dp[i][j], dp[i][j-1]+1);
}
}
}
}
for(int i=mat.size()-1; i>=0; i--)
{
for(int j=mat[0].size()-1; j>=0; j--)
{
if(mat[i][j]==0)
{
dp[i][j]=0;
}
else{
if(i<mat.size()-1)
{
dp[i][j]= min(dp[i][j], dp[i+1][j]+1);
}
if(j<mat[0].size()-1)
{
dp[i][j]= min(dp[i][j], dp[i][j+1]+1);
}
}
}
}
return dp;
}
};

class Solution { public: vector updateMatrix(vector& mat) { vectordp(mat.size(), vector(mat[0].size(), INT_MAX-100000)); for(int i=0; i<mat.size(); i++) { for(int j=0; j<mat[0].size(); j++) { if(mat[i][j]==0) { dp[i][j]=0; } else { if(i>0) { dp[i][j]= min(dp[i][j], dp[i-1][j]+1); } if(j>0) { dp[i][j]= min(dp[i][j], dp[i][j-1]+1); } } } } for(int i=mat.size()-1; i>=0; i--) { for(int j=mat[0].size()-1; j>=0; j--) { if(mat[i][j]==0) { dp[i][j]=0; } else{ if(i<mat.size()-1) { dp[i][j]= min(dp[i][j], dp[i+1][j]+1); } if(j<mat[0].size()-1) { dp[i][j]= min(dp[i][j], dp[i][j+1]+1); } } } } return dp; } };

could you explain more?

issue1.txt
This is my first ever contribution maybe this won't be accurate but i just wanted to try to contribute...
explanation :
The code starts with the inclusion of necessary headers  and  which provide functionality for vectors and limit values in C++.
The code defines a class Solution which contains a member function updateMatrix. This function takes a 2D vector mat as input and returns a 2D vector dp as output. The function aims to update the matrix mat by calculating the distance of each cell to the nearest cell containing zero.
Inside the updateMatrix function, a new 2D vector dp is created with the same dimensions as mat. The purpose of dp is to store the distance values.
The first pass of the algorithm is performed by iterating through each cell of mat in row-major order. For each cell, if the value is 0, it means it is already a zero cell, so the distance is set to 0. Otherwise, if the value is non-zero, the minimum distance is calculated by considering the neighboring cells above and to the left. The calculated minimum distance is stored in the corresponding cell of dp.
The second pass of the algorithm is performed by iterating through each cell of mat in reverse row-major order. This time, the neighboring cells below and to the right are considered to calculate the minimum distance, in addition to the existing values in dp. Again, the calculated minimum distance is stored in the corresponding cell of dp.
Finally, the dp matrix is returned, which contains the updated distance values for each cell.
The code also includes a placeholder main() function, which can be used to test the updateMatrix function by providing test inputs and calling the function accordingly.

_The given code represents a solution in C++ for updating a matrix with distances to the nearest zero. The input matrix mat is a 2D vector containing integers. The code uses dynamic programming to update the distances.
Here's how the code works:
Initialize a 2D vector dp with the same dimensions as mat. Each cell in dp is initialized with a large value INT_MAX-100000, which represents infinity.
Iterate through each cell in mat using two nested loops.
If the current cell in mat is 0, set the corresponding cell in dp to 0. This means that the distance to the nearest zero from a zero cell is 0.
If the current cell in mat is not 0, update the distance in dp by considering the minimum distance from the neighboring cells.
a. Check if there is a cell above the current cell (i > 0). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell above plus 1.
b. Check if there is a cell to the left of the current cell (j > 0). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell to the left plus 1.
At this point, the dp matrix will represent the minimum distances to the nearest zero for each cell in the top-left to bottom-right traversal.
Iterate through the cells in mat again, but this time in reverse order (from bottom-right to top-left).
If the current cell in mat is 0, set the corresponding cell in dp to 0. This handles the case where the nearest zero is at the current cell itself.
If the current cell in mat is not 0, update the distance in dp by considering the minimum distance from the neighboring cells.
a. Check if there is a cell below the current cell (i < mat.size() - 1). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell below plus 1.
b. Check if there is a cell to the right of the current cell (j < mat[0].size() - 1). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell to the right plus 1.
At the end of this step, the dp matrix will represent the minimum distances to the nearest zero for each cell in both directions.
Return the dp matrix as the updated matrix with distances to the nearest zero.
Overall, the code efficiently calculates the distances to the nearest zero for each cell in the input matrix using dynamic programming and two passes through the matrix.

`
vector<vector> updateMatrix(vector<vector>& mat) {
vector<vector> dp(mat.size(), vector(mat[0].size(), INT_MAX - 100000));
    for(int i = 0; i < mat.size(); i++) {
        for(int j = 0; j < mat[0].size(); j++) {
            if(mat[i][j] == 0) {
                dp[i][j] = 0;
            } else {
                if(i > 0) {
                    dp[i][j] = min(dp[i][j], dp[i - 1][j] + 1);
                }
                if(j > 0) {
                    dp[i][j] = min(dp[i][j], dp[i][j - 1] + 1);
                }
            }
        }
    }

    for(int i = mat.size() - 1; i >= 0; i--) {
        for(int j = mat[0].size() - 1; j >= 0; j--) {
            if(mat[i][j] == 0) {
                dp[i][j] = 0;
            } else {
                if(i < mat.size() - 1) {
                    dp[i][j] = min(dp[i][j], dp[i + 1][j] + 1);
                }
                if(j < mat[0].size() - 1) {
                    dp[i][j] = min(dp[i][j], dp[i][j + 1] + 1);
                }
            }
        }
    }

    return dp;
}

`
The provided code is a C++ implementation of a solution to the problem of updating a matrix with the distance of the nearest 0 for each cell.
for reference https://leetcode.com/problems/01-matrix/
Code Description:
The Solution class encapsulates the solution to the problem. It contains a single member function, updateMatrix, which takes a reference to a 2D vector (vector<vector>& mat) as input and returns a 2D vector (vector<vector>) as output.
We start our proceeding by intializing a 2D vector dp with the dimensions equals to the dimensions of mat 2D vector. Each cell in dp is initially set to INT_MAX-100000, a huge number that stands for infinity.
Use two nested loops to iterate through each cell in the matrix.
Set that particular cell in dp to 0 if the current cell in mat is 0. This indicates that the distance from a zero cell to the closest zero is 0.
Update the distance in dp by taking into account the shortest distance from the next cells if the current cell in mat is not 0.

Check if there is a cell above the current cell (i > 0). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell above plus 1.
Check if there is a cell to the left of the current cell (j > 0). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell to the left plus 1.

After completion of these loops we arrive at a situation where dp[i][j] represents the minimum distance of the nearest 0 in  top-left to bottom-right traversal.
Iterate through the cells in mat again, but this time in reverse order (from bottom-right to top-left).
If the current cell in mat is 0, set the corresponding cell in dp to 0. because the distance for the nearest cell is itself i.e., 0
If the current cell in mat is not 0, update the distance in dp by considering the minimum distance from the neighboring cells.

Check if there is a cell below the current cell (i < mat.size() - 1). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell below plus 1.
Check if there is a cell to the right of the current cell (j < mat[0].size() - 1). If so, update the distance in dp by taking the minimum between the current distance and the distance of the cell to the right plus 1.

At this point of time we have reached where dp[i][j] represents the minmum distance of the nearest 0 for the cell(i,j) in the mat 2D vector

Here is the  corrected code with some minor issues resolved:
class Solution {
public:
vector<vector> updateMatrix(vector<vector>& mat) {
vector<vector> dp(mat.size(), vector(mat[0].size(), INT_MAX-100000));
    // Top-left to bottom-right pass
    for (int i = 0; i < mat.size(); i++) {
        for (int j = 0; j < mat[0].size(); j++) {
            if (mat[i][j] == 0) {
                dp[i][j] = 0;
            } else {
                if (i > 0) {
                    dp[i][j] = min(dp[i][j], dp[i-1][j] + 1);
                }
                if (j > 0) {
                    dp[i][j] = min(dp[i][j], dp[i][j-1] + 1);
                }
            }
        }
    }

    // Bottom-right to top-left pass
    for (int i = mat.size() - 1; i >= 0; i--) {
        for (int j = mat[0].size() - 1; j >= 0; j--) {
            if (mat[i][j] == 0) {
                dp[i][j] = 0;
            } else {
                if (i < mat.size() - 1) {
                    dp[i][j] = min(dp[i][j], dp[i+1][j] + 1);
                }
                if (j < mat[0].size() - 1) {
                    dp[i][j] = min(dp[i][j], dp[i][j+1] + 1);
                }
            }
        }
    }

    return dp;
}

};
In the corrected code, the changes made include:

Adding the correct template parameter  when declaring the vector<vector> type.
Fixing the function signature to use the correct type vector<vector>& for the mat parameter.
Changing vector to vector when declaring the dp matrix to specify the element type as int.
Adjusting the indentation for better readability.
Adding comments to describe the purpose of each pass (top-left to bottom-right and bottom-right to top-left).

With these corrections, the code should now work as intended to update the matrix with the distances from zeros.

issue.txt
The first pass of the algorithm is performed by iterating through each cell of the mat in row-major order. For each cell, if the value is 0, it means it is already a zero cell, so the distance is set to 0. Otherwise, if the value is non-zero, the minimum distance is calculated by considering the neighboring cells above and to the left. The calculated minimum distance is stored in the corresponding cell of dp.
The second pass of the algorithm is performed by iterating through each cell of the mat in reverse row-major order. This time, the neighboring cells below and to the right are considered to calculate the minimum distance, in addition to the existing values in dp. Again, the calculated minimum distance is stored in the corresponding cell of dp.
Finally, the DP matrix is returned, which contains the updated distance values for each cell.
The code also includes a placeholder main() function, which can be used to test the updateMatrix function by providing test inputs and calling the function accordingly.
The algorithm's initial pass is accomplished by iterating through each cell of the mat in row-major order. If the value for a cell is 0, it signifies it is already a zero cell, and the distance is set to 0. If the value is non-zero, the minimum distance is computed by taking into account the neighboring cells above and to the left. The computed minimum distance is saved in the appropriate dp field.
Finally, the DP matrix with the updated distance values for each cell is returned.
The code also provides a placeholder main() method that can be used to test the updateMatrix function by passing test inputs to the function and invoking it accordingly.
The algorithm's second pass involves iterating through each cell of the matrix in reverse row-major order. In addition to the current values in dp, the neighboring cells below and to the right are evaluated this time to compute the minimum distance. The estimated minimum distance is once again saved in the relevant cell of dp.
Finally, the DP matrix with the updated distance values for each cell is returned.
The code also provides a placeholder main() method that can be used to test the updateMatrix function by passing test inputs to the function and invoking it accordingly.

class Solution { public: vector updateMatrix(vector& mat) { vectordp(mat.size(), vector(mat[0].size(), INT_MAX-100000)); for(int i=0; i<mat.size(); i++) { for(int j=0; j<mat[0].size(); j++) { if(mat[i][j]==0) { dp[i][j]=0; } else { if(i>0) { dp[i][j]= min(dp[i][j], dp[i-1][j]+1); } if(j>0) { dp[i][j]= min(dp[i][j], dp[i][j-1]+1); } } } } for(int i=mat.size()-1; i>=0; i--) { for(int j=mat[0].size()-1; j>=0; j--) { if(mat[i][j]==0) { dp[i][j]=0; } else{ if(i<mat.size()-1) { dp[i][j]= min(dp[i][j], dp[i+1][j]+1); } if(j<mat[0].size()-1) { dp[i][j]= min(dp[i][j], dp[i][j+1]+1); } } } } return dp; } };

could you explain more?

The updateMatrix function takes a 2D vector mat as input and returns a 2D vector dp which represents the minimum distances from each cell in mat to the nearest cell containing a zero.
Here's a step-by-step breakdown of the code:
The code initializes the dp vector with dimensions mat.size() by mat[0].size(). Each element in dp is initially set to INT_MAX, representing an infinite distance.
The first nested loop iterates through each cell in mat to fill the dp vector. If the current cell in mat contains a zero, the corresponding cell in dp is set to zero.
If the current cell in mat contains a non-zero value, the code checks the cells above and to the left of the current cell. If there is a shorter path to a zero in the adjacent cells, the distance in the current cell of dp is updated accordingly.
The second nested loop iterates through each cell in mat in reverse order (from bottom-right to top-left) to update the distances again. This time, it checks the cells below and to the right of the current cell.
Finally, the dp vector, which now contains the minimum distances from each cell to the nearest zero, is returned.
The algorithm works by performing two passes over the matrix. The first pass checks for the shortest distance from above and to the left, while the second pass checks for the shortest distance from below and to the right. This approach ensures that each cell in dp contains the minimum distance to a zero, considering all possible paths.
Also there is a minor issue in the code that can be corrected. In the line vector<vector> dp(mat.size(), vector(mat[0].size(), INT_MAX-100000));, the initialization of dp is not done correctly. Subtracting 100000 from INT_MAX is not necessary and could potentially cause integer overflow issues. It's better to initialize dp with a large value such as INT_MAX directly.

Can you provide the Question number of this problem in Leetcode !


Added *big.Int, [16]byte, int64 and uint64 types as destina…

…tion types for cast decimal value with types.CastTo(types.Value, &dst)
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Patch coverage: 15.00% and project coverage change: -0.81 :warning:

Comparison is base (5859c85) 65.04% compared to head (609ac71) 64.24%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #718      +/-   ##
==========================================
- Coverage   65.04%   64.24%   -0.81%
==========================================
  Files         228      225       -3
  Lines       22231    22123     -108
==========================================
- Hits        14461    14212     -249
- Misses       7014     7131     +117
- Partials      756      780      +24

Flag
Coverage Δ

51.05% <0.00%> (-0.95%)
:arrow_down:

1.17.x
45.91% <15.00%> (-18.49%)
:arrow_down:

1.19.x
64.32% <15.00%> (-0.01%)
:arrow_down:

1.20.x
46.16% <15.00%> (-18.56%)
:arrow_down:

integration
51.05% <0.00%> (-0.95%)
:arrow_down:

macOS
46.09% <15.00%> (-0.02%)
:arrow_down:

secure
51.05% <0.00%> (-0.95%)
:arrow_down:

ubuntu
46.11% <15.00%> (-0.01%)
:arrow_down:

unit
46.11% <15.00%> (-0.10%)
:arrow_down:

windows
?

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

Impacted Files
Coverage Δ

table/types/value.go
72.55% <0.00%> (+0.46%)
:arrow_up:

internal/value/value.go
62.49% <15.78%> (-0.61%)
:arrow_down:

... and 24 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


$this->auth is not defined in API controllers

IncidentController::postIncidents and ComponentController::postComponents relays in the auth data, but it seems that does not exists:
'Undefined property: CachetHQ\Cachet\Http\Controllers\Api\IncidentController::$auth' in /vagrant/app/Http/Controllers/Api/IncidentController.php:68

@joecohens can we fix this in https://github.com/cachethq/Cachet/pull/638 as well?

Yes we can :smile: we need to update the responses as well so we will inject the auth on this one.

@joecohens moved this into the V1.0.0 milestone and assigned to you because this can be fixed in #638 :)

:+1:

Fixed by https://github.com/cachethq/Cachet/pull/654 and https://github.com/cachethq/Cachet/pull/638


refactor: twitter share feature

✨ Fix #311
✨ Fix #303
✨ Fix #302

Looking pretty good. One change I'd make is that: if the user clicks the Twitter button then I think it should directly make the intent to Tweet, instead of going to an additional popup that basically amounts to "are you sure you want to tweet?"

Makes sense


Refactor WorkflowExecutor

Pull Request type

[ ] Bugfix
[ ] Feature
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] WHOSUSING.md
[ ] Other (please describe):

Changes in this PR

WorkflowExecutor is now an interface making it easy to extend based on various implementation
Removed spring-events and relying on the workflow executor
Removed StartWorkflowOperations and putting startWorkflow operations back into WorkflowExecutor

@v1r3n , the original implementation (before this PR) makes the startWorkflow the async call with spring event publisher https://github.com/conductor-oss/conductor/blob/v3.21.1/core/src/main/java/com/netflix/conductor/core/operation/StartWorkflowOperation.java#L161
    private void createAndEvaluate(WorkflowModel workflow) {
        if (!executionLockService.acquireLock(workflow.getWorkflowId())) {
            throw new TransientException("Error acquiring lock when creating workflow: {}");
        }
        try {
            executionDAOFacade.createWorkflow(workflow);
            LOGGER.debug(
                    "A new instance of workflow: {} created with id: {}",
                    workflow.getWorkflowName(),
                    workflow.getWorkflowId());
            executionDAOFacade.populateWorkflowAndTaskPayloadData(workflow);
// here is the async call
            eventPublisher.publishEvent(new WorkflowEvaluationEvent(workflow));
        } finally {
            executionLockService.releaseLock(workflow.getWorkflowId());
        }
    }

however, with this PR, it becomes sync call: https://github.com/conductor-oss/conductor/blob/main/core/src/main/java/com/netflix/conductor/core/execution/WorkflowExecutorOps.java#L1910
private void createAndEvaluate(WorkflowModel workflow) {
        if (!executionLockService.acquireLock(workflow.getWorkflowId())) {
            throw new TransientException("Error acquiring lock when creating workflow: {}");
        }
        try {
            executionDAOFacade.createWorkflow(workflow);
            LOGGER.debug(
                    "A new instance of workflow: {} created with id: {}",
                    workflow.getWorkflowName(),
                    workflow.getWorkflowId());
            executionDAOFacade.populateWorkflowAndTaskPayloadData(workflow);
// decide is sync call
            decide(workflow);
        } finally {
            executionLockService.releaseLock(workflow.getWorkflowId());
        }
    }

is the change made by purpose?

The issue we had today is, originally the startWorkflow REST API return the workflow ID immediately and leave the workflow execution in the background (asynchronously)
however, today the API blocks until the workflow finished which is not ideal for a long running workflow.


nsls2-collection 2022-1.0 envs

Uses new NSLS-II Docker image:

https://github.com/NSLS-II/docker-images/pull/1
https://hub.docker.com/r/nsls2/linux-anvil-cos7-x86_64/tags

Diffs
nsls2-collection-2021-3.1-py37-env.yml vs. nsls2-collection-2022-1.0-py37-env.yml

$ diff nsls2-collection-2021-3.1-py37-env.yml nsls2-collection-2022-1.0-py37-env.yml
1c1
< name: nsls2-collection-2021-3.1-py37
---
> name: nsls2-collection-2022-1.0-py37
48a49
>   - intake <=0.6.4
66a68
>   - mxtools >=0.0.2
73c75
<   - nslsii >=0.3.0
---
>   - nslsii >=0.3.2
75a78
>   - nyxtools >=0.0.2
108a112
>   - silx >=0.15.2,<1
128,129c132,137
<   - xpdan
<   - xray-vision
---
>   # TODO: xmidas has a dependency of scipy>1.7 that is conflicting with some
>   # packages in this env (also conflicts with scipy>1.6). Need to resolve it
>   # first before including of the xmidas package.
>   # - xmidas >=0.1.1
>   - xpdan >=0.8.2
>   - xray-vision >=0.1.1
148c156
<   - pyolog >=4.4.0
---
>   - pyolog >=4.5.0
156c164
<   - hxnfly
---
>   - hxnfly >=0.0.10

nsls2-collection-2021-3.1-py39-env.yml vs. nsls2-collection-2022-1.0-py39-env.yml

$ diff nsls2-collection-2021-3.1-py39-env.yml nsls2-collection-2022-1.0-py39-env.yml
1c1
< name: nsls2-collection-2021-3.1-py39
---
> name: nsls2-collection-2022-1.0-py39
48a49
>   - intake <=0.6.4
66a68
>   - mxtools >=0.0.2
73c75
<   - nslsii >=0.3.0
---
>   - nslsii >=0.3.2
75a78
>   - nyxtools >=0.0.2
108a112
>   - silx >=0.15.2,<1
128,129c132,137
<   - xpdan
<   - xray-vision
---
>   # TODO: xmidas has a dependency of scipy>1.7 that is conflicting with some
>   # packages in this env (also conflicts with scipy>1.6). Need to resolve it
>   # first before including of the xmidas package.
>   # - xmidas >=0.1.1
>   - xpdan >=0.8.2
>   - xray-vision >=0.1.1
148c156
<   - pyolog >=4.4.0
---
>   - pyolog >=4.5.0
156c164
<   - hxnfly
---
>   - hxnfly >=0.0.10

nsls2-collection-2022-1.0-py37-env.yml vs. nsls2-collection-2022-1.0-py39-env.yml

$ diff nsls2-collection-2022-1.0-py37-env.yml nsls2-collection-2022-1.0-py39-env.yml
1c1
< name: nsls2-collection-2022-1.0-py37
---
> name: nsls2-collection-2022-1.0-py39
10c10
<   - python >=3.7,<3.8
---
>   - python >=3.9,<3.10

Closes
Closes #50
Closes #51
Closes #53
Closes #54
Closes #55

We now have artifacts available to download for preliminary testing:

That eliminates the need of building both locally and in CI.

Thanks, @dmgav! I deposited the artifacts to https://zenodo.org/record/5954331. The envs are in a standard place for the internal deployment.


Error in grad when using arctan2 function

The autograd function arctan2 seems to work fine on its own:
>>> import autograd.numpy as anp
>>> anp.arctan2(1.0, 0.0)
1.5707963267948966
>>>

But when I try to grad a function that uses arctan2, I get an error:
Contents of test_arctan2.py:
import autograd.numpy as anp
from autograd import grad

def arctan2(xy):
    return anp.arctan2(xy[1], xy[0])

garctan2 = grad(arctan2)
garctan2((0.0, 1.0))

Output of test_arctan2.py
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/hodsonjd/dev/test_arctan2.py", line 9, in <module>
    print(garctan2((0.0, 1.0)))
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/wrap_util.py", line 20, in nary_f
    return unary_operator(unary_f, x, *nary_op_args, **nary_op_kwargs)
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/differential_operators.py", line 24, in grad
    vjp, ans = _make_vjp(fun, x)
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/core.py", line 10, in make_vjp
    end_value, end_node =  trace(start_node, fun, x)
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/tracer.py", line 10, in trace
    end_box = fun(start_box)
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/wrap_util.py", line 15, in unary_f
    return fun(*subargs, **kwargs)
  File "/home/hodsonjd/dev/test_arctan2.py", line 5, in arctan2
    return anp.arctan2(xy[1], xy[0])
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/tracer.py", line 45, in f_wrapped
    node = node_constructor(ans, f_wrapped, argvals, kwargs, argnums, parents)
  File "/home/hodsonjd/.linuxbrew/Cellar/python/3.6.5/lib/python3.6/site-packages/autograd/core.py", line 30, in __init__
    self.vjp = primitive_vjps[fun](parent_argnums, value, args, kwargs)
KeyError: <function primitive.<locals>.f_wrapped at 0x7f57be01ea60>

I am quite new to autograd (just started working with it yesterday), so this may simply be user error. If someone can offer some insight as to what I might be doing wrong, any help would be greatly appreciated!
Thanks,
Josh

Try installing Autograd from the master branch on Github. I think support for numpy.arctan2 was only add relatively recently and isn't yet in the version on PyPI.

You are right, arctan2 seems to work with the master branch. thanks!


feat: Add handling for ITensor mean and var in batch_norm

Description
Support ITensor type running_mean and running_var arguments for Batch Norm converter.
Fixes # (issue)
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

LGTM

If the CI results show no more batch_norm errors, it's good to merge.

@zewenli98  Although it's beyond the scope of this PR, I noticed something regarding the converters for layer_norm, group_norm, and native_group_norm.
Currently, weight and bias are defined as:
weight: Optional[Union[torch.Tensor, np.ndarray]],
bias: Optional[Union[torch.Tensor, np.ndarray]],

Is this incorrect? Fortunately, unlike batch norm, there's no issue with adding eps or applying to_numpy on the weight or bias of TRTTensor (or ITensor), so it doesn't seem to cause any problems with the converter. However, it seems like the case where the default value for weight in layer_norm is None might not be handled properly.
Here are schema:

group_norm
layer_norm
native_group_norm

Merging this as the other failures are unrelated.

@chohk88 Thanks for pointing out the issue. I think your understanding is correct. Although there's no errors out now, they should be Optional[Union[TRTTensor, torch.Tensor, np.ndarray]]. Since the Issue #3114 has been opened above to track it, could you modify them to Optional[Union[TRTTensor, torch.Tensor, np.ndarray]] like what you did for the batch_norm?


noIntro should apply to child components

Demo: http://jsfiddle.net/rich_harris/rhdaezxm/

Why not set option on that component? http://jsfiddle.net/rhdaezxm/2/

Yeah, I second @martypdx. There could be situations where you would want to preserve child intros.

I think, lize lazy and twoway, it would be helpful to have element-level attributes. Though the name might need to change because <div noIntro='true' intro='fade'>. is a head scratcher.  While were at it, I've needed a noOutro as well...

It seems like this should be a larger discussion than just intros. It would be nice to address the nested transitions issue from #1397 as well.

Wanted to see if you could dynamicatlly control noIntro from the parent (you can), so leaving this link here.

@Madgvox is right, there is a need for a larger discussion about transitions. Their main virtue at the moment is their simplicity (and the fact that they're not restricted to CSS transitions), but there is a cost associated with that in terms of expressiveness. Handling nested transitions is one part of that discussion; so are...

how to have better control over the timing of when elements are removed from the DOM
how to set parameters in a non-hacky way based on the states we're transitioning from and to (e.g. if you're transitioning from the settings > account route to settings, the current page should fly out to the right, but if you're transitions to settings > account > name, it should fly out to the left
in a similar vein, how to think about transitioning between states full stop. intro and outro are fairly crude. I watched @ef4's EmberConf talk about liquid fire with some jealousy - there's a really great moment when speaker headshots remain on the page even as you move from one page to a completely different one. That kind of object constancy is tricky (though not impossible) to achieve with Ractive transitions as they are now.
how to handle things like spring dynamics (a la Facebook's Rebound)
using non-CSS timing functions with CSS transitions (which are normally limited to linear, ease[-in][-out], or cubic-bezier(...) - but you can 'prebake' keyframes with e.g. an elastic timing function and still do the transition off the main thread. We've done this and the result is glorious on mobile - would like to get some of that buttery smooth goodness into Ractive)
whether Web Animations have a role to play

...and probably some other stuff I've forgotten.
Just for clarity on the noIntro thing, my current use case is that I'm rendering pages on the server, then re-rendering them on the client once JS kicks in (no progressive enhancement yet! hopefully not before too long...), and in that situation I want the noIntro setting of the top level new Ractive() call to be respected by the entire tree, otherwise it's visually rather jarring - I don't want components to be able to make their own decisions about whether to use transitions or not. As usual though, this conversation shows there's all sorts of nuance... man, good APIs are hard.

I have no real useful input on the subject at hand, but I'd like to throw in that it'd be pretty nice to be able to trigger animations at arbitrary points not necessarily related to transitioning. To my severe inexperience, it feels like that, transition tracking, and flexibility for type of transition are closely related.
This is probably a stupid question, but would it make sense to pull transitions out into a separate project and replace them with some (very carefully crafted) animation hooks?

but would it make sense to pull transitions out into a separate project and replace them with some (very carefully crafted) animation hooks?

I suspect it would, in an ideal world. I've resisted that so far because of the complexity around controlling when elements can be removed from the DOM following an outro, which is something I believe most libraries/frameworks struggle with. If there's a good way to offload some of this tricky (and opinionated) stuff to an external package, then :+1:
The one thing to be wary of, I think, is making everything so modular that plugins have their own plugins, since that's confusing. I'm a fan of 'batteries included'. But in any case, figuring out what those hooks would look like would make for better internal APIs.

I think if ractive supplied the template hooks and api - and people could easily plug in their favorite animation library, that would be ideal.

in that situation I want the noIntro setting of the top level new Ractive() call to be respected by the entire tree, otherwise it's visually rather jarring - I don't want components to be able to make their own decisions about whether to use transitions or not

Ractive.prototype.noIntro = true;
Seems like a nice API to me. ;)

Almost... it doesn't quite capture the same intent though! http://jsfiddle.net/rich_harris/ekq2ufma/

Ah, what you want is this: http://jsfiddle.net/ekq2ufma/3/
Which shows two things:

I should put back ractive.rendered. I took it out because I didn't realize it was useful as an api
The semantics for intro transitions are tied to not only if the current instance is already rendered, but possible if the parent is already rendered. So true/false isn't quite enough.

Actually, it looks like along the way in cleaning things up for 0.7 we lost the ability to use functions for basic options. I think for a case like this, it would be handy to write:
    noIntro: function(){
        return !this.parent.rendered;
    }

Oops, that's almost certainly my bad. Something something test suite something...
That would work, certainly, but it still feels like kind of a hack. I guess the thing is I'm expecting noIntro to apply to the whole tree when used as a new Ractive(...) option, rather than just the top-level instance. It's one of those rare cases where something that makes sense as an instantiation option doesn't really make sense as a Ractive.extend(...) option, or at least means something different.
I suppose what noIntro really means (in my head anyway) is something that sidesteps talk of trees and instances altogether:
// I'm imagining this...
var ractive = new Ractive({..., noIntro: true });

// ...to be equivalent to this:
var enabled = Ractive.transitionsEnabled; // global flag. not actually a thing
Ractive.transitionsEnabled = false;

var ractive = new Ractive(...);

Ractive.transitionsEnabled = enabled;

Ractive.prototype.transitionsEnabled is close (http://jsfiddle.net/rich_harris/cqdj9bpm/), but it still allows components to override the setting (http://jsfiddle.net/rich_harris/gr709Lq4/) which is exactly what needs to be avoided on first render in this case.
Whoever first said 'the devil is in the details' was pretty smart.

Oops, that's almost certainly my bad. Something something test suite something...

I just went back through commits and it's been missing awhile. Easy fix, plus a test :)

I suppose what noIntro really means (in my head anyway) is something that sidesteps talk of trees and instances altogether

I when I've been using it, I've been going the other way, wanting element specific directives because it's not granular enough, and I end up bailing out of ractive intro/outro and use class add/remove hacks with css animations.

Easy fix, plus a test :)

Having said that do we need it? No-one missed it while it was away! Maybe it's better to leave that stuff in the hands of onconstruct - that way we'll never run into e.g. problems where someone innocently defines a method with the same name as an option they didn't know about, and gets confused about why the method executes on initialisation.

I end up bailing out of ractive intro/outro and use class add/remove hacks with css animations.

That's a sure sign that the whole system needs a bit of a rethink. Not something I desperately wanted us to get bogged down in for 0.8... but I suppose that's how it goes.

Having said that do we need it? No-one missed it while it was away! Maybe it's better to leave that stuff in the hands of onconstruct

Fair enough, though it would be onconfig in this case.

That's a sure sign that the whole system needs a bit of a rethink. Not something I desperately wanted us to get bogged down in for 0.8... but I suppose that's how it goes.

Well let's keep in mind how the other half lives. I showed someone the basic intro/outro support the other day and their jaw dropped with how simple it is. I think 0.9 for transition/animations would be fine.

hat way we'll never run into e.g. problems where someone innocently defines a method with the same name as an option they didn't know about, and gets confused about why the method executes on initialisation.

Should we test for that? none of the standard options are function. If they did do a function it would be truthy and could cause unexpected results

Should we test for that?

Yeah, maybe. I'm basically in favour of doing whatever we can to guide people away from that sort of accident, as long as it doesn't unduly impact performance.

I think 0.9 for transition/animations would be fine.

Makes sense. Will give this the appropriate milestone and we can come back to it.


Changing/Updating Itemsource at Runtime

How can I change the Itemsource property in Runtime? I am fixing threshold in xamal to 8, When the selected item text reached 7; I want to change the Itemsource. Based on the new Itemsource the algorithm should be executed and show the result. Is't possible with this plugin?

This is addressed in #23 if I'm reading this correctly. If you want to fully update the items source, you just set it in your code behind.

@ChaseFlorell  Thank you for helping me. I have tried and changed the complete datasource at runtime, but still suggestions are not being shown. below is the code.
Xaml
<xfx:XfxComboBox x:Name="cmbText"  Text="{Binding SelectedName}"
ItemsSource="{Binding SuggestionItemSource}"
SortingAlgorithm="{Binding SortingAlgorithm}" WidthRequest="300" Threshold="9"  />
ViewModel
When the text of combo box reaches 6 characters, I am recreating my suggestionItemSource. Below method is called properly and StringSuggestionItemSource is populating with new data properly.
public void MyViewModel_PropertyChanged(object sender, PropertyChangedEventArgs e)
{
if (e.PropertyName == "SelectedName")
{
if (this.SelectedName.Length==6 )
{
this.StringSuggestionItemSource.Clear();
StringSuggestionItemSource = new ObservableCollection( buildPatientSearchItemSource(SuggestionItemSource));
            }

        }
    }

But still new suggestion are being shown :(.
StringSuggestionItemSource -> I am raising OnPropertyChanged event also when this property is updated.
Algorithm
public Func<string, ICollection, ICollection> SortingAlgorithm { get; } =
(text, values) => values
.Where(x => x.ToLower().Contains(text.ToLower())).Select(x=>x)
.OrderBy(x => x)
.ToList();


openssl signature could not be verified

I'm trying to install the latest alpha version of the phpDocumentor, but the install fails with the message:

PHP Fatal error:  Uncaught PharException: phar "/usr/local/bin/phpDocumentor.phar" openssl signature could not be verified: openssl public key could not be read in /usr/local/bin/phpDocumentor.phar:10

Expected Behavior
I expect it to be working
Actual Behavior
When I try to see if it works I get this error
PHP Fatal error:  Uncaught PharException: phar "/usr/local/bin/phpDocumentor.phar" openssl signature could not be verified: openssl public key could not be read in /usr/local/bin/phpDocumentor.phar:10
Stack trace:
#0 /usr/local/bin/phpDocumentor.phar(10): Phar::mapPhar('box-auto-genera...')
#1 {main}
  thrown in /usr/local/bin/phpDocumentor.phar on line 10

Fatal error: Uncaught PharException: phar "/usr/local/bin/phpDocumentor.phar" openssl signature could not be verified: openssl public key could not be read in /usr/local/bin/phpDocumentor.phar on line 10

PharException: phar "/usr/local/bin/phpDocumentor.phar" openssl signature could not be verified: openssl public key could not be read in /usr/local/bin/phpDocumentor.phar on line 10

Call Stack:
    0.0009     391656   1. {main}() /usr/local/bin/phpDocumentor.phar:0
    0.0009     391656   2. Phar::mapPhar() /usr/local/bin/phpDocumentor.phar:10

Steps to Reproduce the Problem

Download the phar file
Move it to /usr/local/bin/
chmod it sudo chmod +x /usr/local/bin/phpDocumentor.phar
Try to run phpdoc --version

Your environment
OS
macOS Mojave version 10.14.1 (18B75)

PHP
PHP 7.2.10 (cli) (built: Sep 14 2018 07:06:17) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Xdebug v2.6.0, Copyright (c) 2002-2018, by Derick Rethans
    with Zend OPcache v7.2.10, Copyright (c) 1999-2018, by Zend Technologies

Version used: 3.0.0-alpha.3
Install method: Downloaded phar from the repo
I've also downloaded the pubkey and tried to do
openssl verify phpDocumentor.phar.pubkey

But this fails with
unable to load certificate
4712818284:error:09FFF06C:PEM routines:CRYPTO_internal:no start line:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-22.200.4/libressl-2.6/crypto/pem/pem_lib.c:683:Expecting: TRUSTED CERTIFICATE

You need to store the pubkey file with the name phpDocumentor.phar.pubkey in the same dir as you stored the phar file.
Please let me know when you have any issues.

Yup, just read this on one of the articles and now it seems to be working (the version at least). Wasn't aware of the signing. Thanks!


Property used for board view columns does not render well when this property is an internal link

What happened?
In dataview query mode, when using a property "property:: [[Note]]" as the column-sorting property of a board view, the titles of the columns are "[[parent_directory/Note.md|Note]]" and non-clickable.
What did you expect to happen?
Having the titles of the columns be "[[Note]]" and clickable.
How can we reproduce it (as minimally and precisely as possible)?
In dataview query mode, use a property "property:: [[Note]]" as the column-sorting property of a board view. Witness that the titles of the columns are "[[parent_directory/Note.md|Note]]" and non-clickable.
Anything else we need to know?
No response
Plugin version
1.11.5
Obsidian version
1.1.9
OS
Linux

In Projects version > 1.17.1 this is already supported. Enable rich text formatting of the status field then the corresponding board column header would be checked and parsed. See #732 for more details.


Add source map on debug mode with Sprockets 4

This fix https://github.com/sass/sassc-rails/issues/161. With Sprockets 4, when debug mode was enabled, the source map wasn't added correctly at the end of the file.

This branch does make SCSS sourcemaps work for me with sprockets 4 (in Rails).
Without the fix in this branch, dev tools debugging of SCSS was pretty impossible in sprockets 4; I had to disable source maps in my browser. (The source maps resulted in unusable mapping, where Chrome just though every line of CSS came from an @import statement, and I couldn't figure out how to disable source map generation altogether for sprockets).
Thanks @GCorbel, amazing work.
I would love to see this merged and in a sassc-rails release, so I can re-enable use of source maps in Chrome.
(Still very mystified why this hasn't been a higher-profile issue; is nobody else using SCSS and sprockets 4? That seems hard to believe, as they are both standard installs in a new rails app. Mystified!)

@jrochkind thanks for your review. I applied your comments and did some refactoring.

Would love to see this fix deployed in a new release. Debugging sass in a complex app is pretty painful as things stand.

I ran into this issue today, and fixed by using the code in this PR:

Made my Gemfile reference these commits:

gem 'sassc-rails', github: 'GCorbel/sassc-rails', branch: 'add-source-maps-on-debug'

Changed ./config/environments/development.rb to have:

  config.sass.inline_source_maps = true
  config.assets.debug = true

rm -rf ./tmp/cache based on the gem's README
Restarted my development server
Now the Chrome Inspector directly links to the SCSS source.

I would +1 merging and cutting a new release, as a result.
(I am not a maintainer of this project, just a user.)


[Bug] [dolphinscheduler-tools] The MigrateResourceService class failed to compile in the zookeeper 3.4.14 version

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The MigrateResourceService.java failed to compile with the zookeeper 3.4.14 version.   Error Log: /dolphinscheduler-tools/src/main/java/org/apache/dolphinscheduler/tools/resource/MigrateResourceService.java:[30,35] 找不到符号. The reason is zk doesn't have StringUtils.java in zookeeper3.4.14.  An incorrect jar package was imported.

What you expected to happen
dolphinscheduler should build successful with zookeeper 3.4.14 version.
How to reproduce
build dolphinscheduler with zk3.4.14
Anything else
No response
Version
dev
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for correct this import, please use org.apache.commons.lang3.StringUtils instead.


Regression in PHP 7.0 - Unable to dynamically access class properties in backend

I'm running PHP v7.0.7 on my development machine and stumbled upon a regression in the core:
Because "dereferencing a variable property that is an array has different semantics between PHP 5 and PHP 7", model properties can no longer be retrieved in core/helpers/mvc_helper::admin_table_cell and the fields are not shown in the backend.
This section in the migration guide explains the new behaviour.
However this issue can be fixed easily by adding curly braces to resolve the ambiguity. I'm sending a PR.

Thanks for this!


.xschemrc is not present after installing skywater

The file is called xschemrc and not .xschemrc. If you want to work with sky130 you need to install open_pdks, which will install all the spice models, digital cell characterization data and xschem libraries. After installing open_pdks you will have the xschemrc file located in /share/pdk/sky130A/libs.tech/xschem/xschemrc. Create a new empty directory, go into this directory, copy the above xschemrc file into it and start xschem from that directory.

If you want you can install xschem_sky130 alone, but then you must supply the spice models yourself. Open_pdks gets all the needed stuff from skywater-pdk, does numerous corrections , gets the xschem_sky130 repository and installs everything .
If you install xschem_sky130 alone  the xschemrc file should be there. Look here.

If you installed xschem_sky130 using a docker / some sandbox environment and xschemrc is missing please contact the container creators.


Convert goog.events.BrowserFeature to goog.module

When compiling something that depends on this file, the closure compiler will give me an internal compiler error. I figured that since lines from this file were present in the  stack trace, I could try to get rid of the goog.scope and make this file use goog.module. The error appears to be gone now.
I am not sure if different builds of the compiler fix this error, but if it helps, I am using a maven plugin to run it located at (https://github.com/blutorange/closure-compiler-maven-plugin).

Would you mind posting the full error you get from the compiler?
We can try and land this change, but it might be hard to land this internally. I'll pull it in and see.

There are some internal build failures that need to be fixed before this can land - once they have done so I'll attempt to get this merged. Nothing for you to do now but wait.

Sounds good.

H

I just fixed the clang-format errors; I was using a different one in my path.

This has been merged. Thanks for contributing!


updated infra donation address

new cold wallet for teis infra donations (held by manitcor)
added longform too bc enough space and people have been asking

Ah ok, I now understand, but this is just the display text, ktorn added it to the dropdown of the default suggested collaborators

mel now it says "please consider donating to the address" before the sentence starts again

mel now it says "please consider donating to the address" before the sentence starts again or wait, actually in the code it looks fine .... i am confused.

I'm sorry I don't understand what you mean, I attached a screenshot of the result, you edited the wrong file, files in languages are only used in the about, but it's kept for future localization

Follow up in #100


plot_myarray bug in W2D1 tutorial 3

In the latest version of this notebook (per google colab) ax.imshow is called without origin argument, causing all colormaps in the notebook to be plotted in what appears to be reverse order from what is intended:
colormap = ax.imshow(array, extent=[-10, 10, 8, -8])

adding an origin='lower' argument, to start plotting the array from the bottom row up, appears to fix all the colormaps. Note that the examples will need to be replaced manually;
colormap = ax.imshow(array, extent=[-10, 10, 8, -8], origin='lower')

The heatmap orientation went through two rounds of last minute changes last night, but I believe the latest version is now correct (the orientation of an imshow heatmap is overdetermined, origin is not strictly necessary).
If you are looking at the latest version of the notebook and think it’s wrong, can you please upload an example image and an image that you think would be correct?

Also just pedantically, the color map is how you map from the numeric value in each cell of the heatmap to an rgb value. Here we are using “viridis” as the color map. It’s distinct from the heatmap, which is the overall plot. If the colormap were reversed, we’d see bright colors for low probability and dark colors for high probability.
It’s not a big deal, but given the overall confusion about these plots I want to make sure we’re taking about the same thing.

Regardless of imshow's  intended use, the imshow() call is the culprit of the bug here.
Here's what the figure looks like now: (note anti-correlated ~x and x, where one would expect a correlated one):

And here's what I believe it should look like, and what changes when origin = 'lower' is added to the imshow call (~x and x are correlated, as one would expect from a brain representation and the underlying stimulus):

Worth noting that 'overdetermined' has little meaning here, as imshow still has to be told to start drawing the image from the top or the bottom.
In case there's some uncertainty that my idea of the correlation of x and ~x is correct: Inspecting the data visually will reveal that this is the intended relationship (and is actually preserved in the underlying data):
print(hypothetical_stim[0],x[np.argmax(likelihood_array[0,:])])
print(hypothetical_stim[-1],x[np.argmax(likelihood_array[-1,:])])

which returns
-8.0 -8.000000000000007
8.0 7.999999999999936

Note that this doesn't correspond to the graph as it is now!

And yes, I'm looking at the latest version of the notebook (I've been constantly reloading the google colab version to check if the error was indeed me using an old version, but it's still plotting it the wrong way around!)

All good. For the record:

Worth noting that 'overdetermined' has little meaning here, as imshow still has to be told to start drawing the image from the top or the bottom.

It’s also possible to invert the y axis and change where it’s “top” or “bottom” appears. So between extent, origin, and the axis orientation, it’s possible to get the plot correct in multiple ways (and wrong in more ways, apparently).
Personally I find imshow really confusing and always use pcolormesh when I have a matrix and x/y coordinate grids.
Anyway I think we agree the problem is resolved, so I’ll close.


Votes do not disappear from the map when they are deleted

Pretty much down except: if the user has the map loaded up on two places and deletes the votes in one, the other map will not hide the vote.  The other map has no way of knowing that the vote was deleted, because that map might still be being used to pick a location.


completions not working in php file

This might be due to this being a Wordpress template, where it by definition is a partial "html" file, but as you can see, trying to add a div with div.foo[tab] or .foo[tab] does nothing.
It works fine in a plain vanilla HTML file.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4033715-completions-not-working-in-php-file?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github).

Now you can easily enable the Tab key for other languages. More info here.
I think this can be closed then.

Thank you so much @KeitIG. worked perfectly!

FYI regarding the official info, you can use

'atom-text-editor[data-grammar*="html"]:not([mini])':
  'tab': 'emmet:expand-abbreviation-with-tab'

instead of targeting a specific grammar (e.g. text html php), this targets all grammars with html detected.

This doesn't fix php tags.
I want to be able to use emmet's div.className tab completion as well as being able to type php and it auto completes to <?php ?> on tab... I can't seem to get the best of both worlds?

EDIT: I've found a fix for anyone else who's having the same issue... the following worked for me:
`'atom-text-editor[data-grammar="text html basic"]:not([mini])':
'tab': 'emmet:expand-abbreviation-with-tab'
'atom-text-editor:not([mini])':
'tab': 'emmet:expand-abbreviation-with-tab'
'.pane .editor:not(.mini)':
'tab': 'snippets:expand' `

@rockethouse you said it! that solution works proper for me. thanks!

@rockethouse This worked for me for quite a while until I bumped into another problem. Say I type input and expand it. The type attribute is highlighted and if I change it to something like text and hit tab to get to the next tab stop, instead of doing that, it expands text to <text></text> which sucks.
For now, adding the cson code posted in #86 along with this seems to get things going smooth.

Finally got the solution for this issue. With this code in the keymap.cson it will work the same way as .html files.
Your keymap

Atom keymaps work similarly to style sheets. Just as style sheets use
selectors to apply styles to elements, Atom keymaps use selectors to associate
keystrokes with events in specific contexts. Unlike style sheets however,
each selector can only be declared once.

You can create a new keybinding in this file by typing "key" and then hitting
tab.

Here's an example taken from Atom's built-in keymap:

'atom-text-editor':
'enter': 'editor:newline'

'atom-workspace':
'ctrl-shift-p': 'core:move-up'
'ctrl-p': 'core:move-down'

You can find more information about keymaps in these guides:
* https://atom.io/docs/latest/using-atom-basic-customization#customizing-key-bindings
* https://atom.io/docs/latest/behind-atom-keymaps-in-depth

If you're having trouble with your keybindings not working, try the
Keybinding Resolver: Cmd+. on OS X and Ctrl+. on other platforms. See the
Debugging Guide for more information:
* https://atom.io/docs/latest/hacking-atom-debugging#check-the-keybindings

This file uses CoffeeScript Object Notation (CSON).
If you are unfamiliar with CSON, you can read more about it in the
Atom Flight Manual:
https://atom.io/docs/latest/using-atom-basic-customization#cson
'atom-pane atom-text-editor[data-grammar~="html"]:not([mini]):not(.autocomplete-active), atom-pane atom-text-editor[data-grammar~="html"]:not([mini]):not(.autocomplete-active), atom-pane atom-text-editor[data-grammar~="php"]:not([mini]):not(.autocomplete-active), atom-pane atom-text-editor[data-grammar~="php"]:not([mini]):not(.autocomplete-active), atom-pane atom-text-editor[data-grammar~="xml"]:not([mini]):not(.autocomplete-active)':
'enter': 'emmet:insert-formatted-line-break-only'
language-specific Tab triggers
you can add more triggers by changing grammar attribute values
'atom-text-editor[data-grammar="text html basic"]:not([mini]), atom-text-editor[data-grammar="text html php"]:not([mini]), atom-text-editor[data-grammar~="erb"]:not([mini]), atom-text-editor[data-grammar~="jade"]:not([mini]), atom-text-editor[data-grammar~="css"]:not([mini]), atom-text-editor[data-grammar~="stylus"]:not([mini]), atom-text-editor[data-grammar~="sass"]:not([mini]), atom-text-editor[data-grammar~="scss"]:not([mini])':
'tab': 'emmet:expand-abbreviation-with-tab'
Stop emmet from hijacking tab from snippets and autocomplete
'atom-text-editor.autocomplete-active:not([mini])':
'tab': 'autocomplete-plus:confirm'
Stop emmet from hijacking tab from snippet tab stops
'atom-text-editor[data-grammar="text html basic"]:not([mini]), atom-text-editor[data-grammar="text html php"]:not([mini]), atom-text-editor[data-grammar~="jade"]:not([mini]),
atom-text-editor[data-grammar="text html php"]:not([mini]), atom-text-editor[data-grammar~="css"]:not([mini]), atom-text-editor[data-grammar~="sass"]:not([mini])':
'tab': 'snippets:next-tab-stop'

@KeitIG Thanks so much!

@MikedeJong Thank you heaps!! Your fix works great.

For macOS Sierra user's ONLY:
Atom(upper right next to apple logo) ->  Keymap... -> paste it like this:
  'alt-tab': 'emmet:expand-abbreviation'```

NOT LIKE THIS:

```# '.platform-darwin atom-text-editor:not([mini])':
#   'alt-tab': 'emmet:expand-abbreviation'```

Let me know if it doesn't work.
- yekurtal

It happens to be Cmd + Shift + E on Mac :(

Is there a way to change Cmd + Shift + E on Mac to just Tab or no?


Tasks600-606

@Nikhitha0911, thank you for your submission. I have renamed your PR to 600-606 since task numbers till 599 were taken in the previous PR. Also can you please add your file names in readme so that tests pass?

Reviews: https://github.com/swarooprm/CSE576HW/pull/37

@Nikhitha0911 thanks for the PR! Looks like the tests are failing because some files are uppercase and probably the exact file names are not included in the readme file.

task600_qangaroo_answer_generation: In the examples, should they be "Question: What interacts_with DB00773?"
task603_wikitext-103_fill_in_the_blank: I think you can drop this: "A sentence from the passage will be picked as the question with a blank. "
task606_qangaroo_classification: "Indicate your choice with the number of the option you choose." -> "Indicate the answer with the number associated with the answer entity".

@swarooprm what do you think about these tasks?

@Nikhitha0911 could you drop the tasks that are difficult to read (e.g., Qangroo) so that we can move this PR?


Switch to using the WinPR ASN1 library in nla.c

@freerdp-bot test

@freerdp-bot test

General remark: tscredentials.[ch] were the only users of the tools/asn_parser_generator.py script, so perhaps that if we remove these files, the script shall be removed too (or at least updated to use WinPRAsn1). This can also be part of another PR, when we'll have removed all instance of BER/DER functions...
libfreerdp/core/credssp.asn1 shall be removed too as it was the source to generate tscredentials.[ch].

@freerdp-bot can you test the new version please ?

I've complemented the checks for ContextualReads in #8085

@freerdp-bot can you test again ?


Adds an example to generate a portrait plot with modal support

@doutriaux1 @James-Crean this is great! Do we have a live demo somewhere to see how things look?


Renaming "this week in infosec" post to prevent name collision

I noticed that my most recent post's name collided with my previous post, which messed up the ability to read that old post (the link now points to the most recent one). I've renamed the file for the most recent post and appended a "-1", which I'll increment in the future to track successive weeks.
Let me know if you have any suggestions for a better approach going forward. If not, I'll follow this format going forward. Thanks!

Could make the title include the date instead.

I like that better. Changed with the newest commit. Let me know if you need anything else from me. Thanks!

:+1: I'll sync these up when I get the chance.

:+1: Looks good now on both systems.


ruff: 0.0.274 -> 0.0.275

Diff: https://github.com/astral-sh/ruff/compare/v0.0.274...v0.0.275
Changelog: https://github.com/astral-sh/ruff/releases/tag/v0.0.275
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 239234 run on x86_64-linux 1

10 packages built:

emacsPackages.lsp-bridge
python310Packages.python-lsp-ruff
python310Packages.python-lsp-ruff.dist
python310Packages.ruff-lsp
python310Packages.ruff-lsp.dist
python311Packages.python-lsp-ruff
python311Packages.python-lsp-ruff.dist
python311Packages.ruff-lsp
python311Packages.ruff-lsp.dist
ruff


Icon submission: Shareworks

[x] I have read and followed CONTRIBUTING document.
URL of the site or app (required): https://www.shareworks.com/
Logo resources for the icon:

SVG logo on homepage

Uploaded files:
Shareworks.zip

I had to remake this one, sorry about that. It's my fault really.
If logo is just really generic sans-serif font based, then I personally don't use first letter of the logo. Because it doesn't differentiate from the Aegis's default letter icon.

That's fine. I'll mention that the "S" is used by their app, so it is recognizable to me.


Unclear Documentation for use of factor in conjunction with minimum and maximum

If factor is set, the value given by the provider must be displayed by the consumer dividing value by factor (which then mght change from INTEGER to REAL...
But how to handle the minimum and maximum properties?
Shall i assume the they are also multiplied by factor, so that i can compare the value to minimum and maximum to check whether it is valid or not, or do i have to assume minimum and maximum are given as values already devided by factor and i have to check minimum <= value/factor <= maximum?
???

Hi,
the parameter properties Value, DefaultValue, Minimum and Maximum shall always be reported in the same unit. So you have to divide all of them by the factor or apply a formula (if provided) to them.

Is this explicitly stated in the documentation somewhere, or do we have to clarify this?

I was unable to find anything in the Documentation; That is why i asked. I stumbled over a device had a maximum of 320, a factor of 100 and a value of 5217. And my range-check failed; but it was a temperature and therefore 52.17 degree celsius is quite valid ... i guess.

The documentation now also clarifies that a factor has to be applied to the minimum, maximum and the default value, if specified.


File Upload (Not a Real Issue)

The GitHub wiki does not allow file uploads to it, so if you ever want to host a file and link to it from the wiki, the "normal" procedure is to have someone on the team make a "File Upload" issue like I am doing now.
The issue will be closed, but if you ever want to share a file (GitHub supports a few image types), just drag and drop the file into a comment response here.
PS: You can ping someone on GitHub (and GitHub will email them if they have email notification turned on), by using the following syntax: @idmontie.


Avoid passing event listener when attaching when process state is connected

Fixes #519

This is no longer needed as f75f54b0eda30f fixed the issue.


Will like to add techstack section used ( logo also )

I will like to add the tech stack used and also their logo this will make the read me file more attractive !! Will start the work as soon as I get assigned

@rohank2502  Go ahead
you can add html, css, js, django, php, mysql and any other that you discover

@rohank2502 Go ahead
you can add html, css, js, django, php, mysql and any other that you discover

Ok will do in 10 mins

Done Already ! BY me LOL


perf(file_server): hoistStatic and simplify operations

The file_server example has been optimized without unfairness。
Here is the performance of file_server/deno_server.ts before and after optimization
Before optimization

After optimization

Other examples have been more or less optimized.
Test data provided by plow
Similar optimization tips in the community:

vitejs/vite/pull/12654
vue-macros.sxzz.moe/features/hoist-static

I'm skeptical about this PR for multiple reasons. It might improve performance but gives up on readability, and it isn't what most people would do – std manual shows usage as shown below:

Additionally by running benchmarks on my PC it seems like it doesn't do anything regarding performance (if not degrades it). Benchmark results from your code show some receiving 0.5-3% decline in throughput. These amounts (looking that the second place also dropped by the same amount) mean that these changes do neglibile amounts of gains while loose substantial amounts of readability.
[BEFORE]

[AFTER]

I'm still open for these kinds of PR's. If these results show significant enough performance gains on anyone else's computers, please let me know.

I'm sorry I only tested file_server/deno_server.ts and used plow to keep hitting http://localhost:8000/doggy.jpeg。
Optimized for better performance on the computer it is on. Of course I have no more other computers to provide bench data.
I will close this pr for the balance of readability and performance improvement.
Thank you for providing the performance bench for all cases.


Fix #318

PR #272 was incomplete. I've added handling more window states.

Codecov Report

Merging #319 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #319      +/-   ##
=========================================
+ Coverage   94.46%   94.5%   +0.03%
=========================================
  Files          49      49
  Lines       19563   19565       +2
=========================================
+ Hits        18481   18489       +8
+ Misses       1082    1076       -6

Continue to review full report at Codecov.

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


Create a slack for users.

I use Slack more than Discord. GitHub discussion is helpful, but only for devs.

I have decided to use Discord since it is free when open ci users join the channel. I have to pay around 10 USD per user if I use Slack.

relate to #42


Add Virtasant to landscape Monitoring

Virtasant’s Cloud Optimization solution includes program setup, global cloud expertise, and a proprietary technology platform that offers complete end-to-end automation to manage Cloud FinOps programs and optimize cloud resources.
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

LGTM


[feat][broker][PIP-278] Support pluggable topic compaction service

PIP: #20624

Motivation
Support pluggable topic compaction service
Modifications

Verifying this change

[x] Make sure that the change passes the CI checks.

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

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Could you please split this PR into multiple?

Could you please split this PR into multiple?

This is a bit difficult. If only submit part modifications, the CI will not be able to pass.
In fact, most of them are modifications to test to be compatible with the new interface.

Honestly, It's tough for other committers to review this whole bunch. Maybe we can add some interface or other new things first? :)

Honestly, It's tough for other committers to review this whole bunch. Maybe we can add some interface or other new things first? :)

Ok, I push a new PR only include the new topic compaction interface and pulsar implementation. PR: https://github.com/apache/pulsar/pull/20645


bug(datepicker): Time Zone transformation applied when it shouldn't

According to ISO 8601, "If no UTC relation information is given with a time representation, the time is assumed to be in local time".  The UI-Bootstrap datepicker is not honoring that specification.
Dates in the following formats are coming back from the webapi we're using - 2013-09-01T00:00:0.  This is standard format for a date that has no time or time zone information.  Notice the lack of a "Z" or "+00" at the end.
Start with your own plunker for the datepicker (on docs page) and paste this time into the input box - 2013-09-04T00:00:00.000.  It's obviously a date representation for September 4th, but notice the datepicker popup shows September 3 as the date.  You're applying time zone transformation to a date that according to spec should be assumed to be in the same time zone (i.e. DON'T MESS WITH IT).
This is a big problem, causing every date to display as the prior day.  I'm amazed no one has used the datepicker with an api, or this would be seen.  Perhaps you're apis are explicity specifying the time zone.  I'm not sure we can get that changed, but regardless it should work according to ISO.

Directive to fix issues with negative timezones:
https://gist.github.com/nsilvah/a7a31f017de098a79f38

WELL DONE @nsilvah !!!
(http://www.gifbin.com/bin/1233928590_citizen kane clapping.gif)


Add adjust angle vector ROS server/client

Usage
Command
ri.angle_vector([0,0,0,0,0,0,0,0,0,0], 5)
ri.wait_interpolation(adjust_angle_vector=True, error_threshold=5)

Log
Servo [4] error [6.][deg] exceeds threshold [5.][deg].
Stop motion by overriding reference angle vector with current angle vector.
[WARN] [1724857818.102982]: Stop motion by adjust angle vector.

Thank you for your review.
I pushed some commits.

I rebased the latest origin/master and tested this PR again.


Plan go rewrite

The event forwarder is in node for historical reasons. To better match up the rest of the software run by validators, this should be rewritten in golang.

Hey @ValentinTrinque,
Is this superseded by the eef work you are doing to bring it into the core?

Yes @gordsport yihbare right. I didn't see this issue previously.

Closing as a duplicate as now superseded by: https://github.com/vegaprotocol/vega/issues/4553


TypeError: unhashable type: 'list' Raised when the batch_size is set

Hi, thanks for your efforts on this wonderful project! When I am setting the batch_size in the config.yaml. There is error like this. I have seen the same issue, and tried to set the save_pred: true in the config.yaml, but still the same error.
main.py 94 decorated_main
_run_hydra(

utils.py 394 _run_hydra
_run_app(

utils.py 457 _run_app
run_and_report(

utils.py 223 run_and_report
raise ex

utils.py 220 run_and_report
return func()

utils.py 458 <lambda>
lambda: hydra.run(

hydra.py 132 run
_ = ret.return_value

utils.py 260 return_value
raise self._return_value

utils.py 186 run_job
ret.return_value = task_function(task_cfg)

train_real_temp.py 180 main
metric_dict, _ = pinnstorch.train(

utils.py 85 wrap
raise ex

utils.py 73 wrap
metric_dict, object_dict = task_func(

train.py 174 train
preds_list = trainer.predict(

trainer.py 864 predict
return call._call_and_handle_interrupt(

call.py 44 _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)

trainer.py 903 _predict_impl
results = self._run(model, ckpt_path=ckpt_path)

trainer.py 987 _run
results = self._run_stage()

trainer.py 1028 _run_stage
return self.predict_loop.run()

utilities.py 182 _decorator
return loop_run(self, *args, **kwargs)

prediction_loop.py 124 run
self._predict_step(batch, batch_idx, dataloader_idx, dataloader_iter)

prediction_loop.py 231 _predict_step
batch = call._call_strategy_hook(trainer, "batch_to_device", batch, dataloader_idx=dataloader_idx)

call.py 309 _call_strategy_hook
output = fn(*args, **kwargs)

strategy.py 278 batch_to_device
return model._apply_batch_transfer_handler(batch, device=device, dataloader_idx=dataloader_idx)

module.py 347 _apply_batch_transfer_handler
batch = self._call_batch_hook("transfer_batch_to_device", batch, device, dataloader_idx)

module.py 336 _call_batch_hook
return trainer_method(trainer, hook_name, *args)

call.py 157 _call_lightning_module_hook
output = fn(*args, **kwargs)

pinn_module.py 241 transfer_batch_to_device
self.copy_batch(batch)

pinn_module.py 329 copy_batch
spatial, time, solution = self.static_batch[key]

TypeError:
unhashable type: 'list'

It seems the copy_batch() in pinns_module.py is accepting the last batch but a tuple, here I tried to figure this out by adding a judgement on the type of batch before proceeding the batch copy to self.static_batch. I am still trying to find the source of this issue by going through the LightningModule class. If you have any adivce on this to solve this issue intrinsically, that would be of great help!
Here is my patch on the code may tentatively solve this issue, in pinn_module.py:
  def copy_batch(self, batch) -> None:
      """
      Fills the graph's input memory with new data to compute on. If the batch_size is not
      specified, the model uses all the available data, and there is no need to copy the data.

      :param batch: A batch of data (a tuple) containing the input tensor of images and target labels.
      """
      if isinstance(batch, dict):
          import time as tm
          st = tm.time()

          for key in batch:
              spatial, time, solution = self.static_batch[key]
              spatial_new, time_new, solution_new = batch[key]
              time = time.requires_grad_(False).copy_(time_new)
              x = [
                  spatial_.requires_grad_(False).copy_(spatial_new[i])
                  for i, spatial_ in enumerate(spatial)
              ]
              if solution_new is not None:
                  solution = {
                      key_sol: solution[key_sol].copy_(solution_new[key_sol])
                      for key_sol in solution_new
                  }

          self.times_batch.append(tm.time() - st)

I've met the same issue those days and it really bothered me. I've searched a lot of content but I still cannot fix the problem. Thank for your contribution and it really help me a lot.

I think the issue is the prediction step will return a pred as a list, but the copy_batch() method cannot process list. It is caused by the statement that if it is not val_stage, it will run copy_bath() instead of transfer_batch_to_device(). What I did is changing val_stage to True in predict_step and it seems to work fine to me.


fixed faulty column numbers in dbnsfp vcfanno configs

fixed issue with column numbering in vcfanno config, where the wrong values would be in the wrong column.
Cheers
M

Matthias -- thanks much for the fix.


HasSingleElement

I often find myself wanting to either check that I've only got 1 element, or condition my code on whether or not a collection has exactly 1 element.
If I want to efficiently check whether my IEnumerable (foo) is Empty, I can use !foo.Any().
If I want to efficiently check whether it has exactly 1 element, it's much less pleasant. foo.Skip(1).Any() is correct and efficient, but isn't really clear what you're trying to say. foo.Count() = 1 is inefficient if the answer is "No, there are more elements.", anything resembling catch() {foo.Single()} is just appauling for multiple reasons.
I propose adding HasSingleElement  (or IsSingle, or ContainsOnlyOneElement, or any other variation of the name that people prefer.) which implements this efficiently at the manual enumeration level.
The implementation would follow the logic of foo.Skip(1).Any()
Questions:
A) How do you (people who have design understanding of MoreLINQ) feel about this proposal?
B) What do I need know about contributing to MoreLINQ in order to produce a PR for this myself? Is there an "ideal PR" for a new function that I should use as a template?

Why not use Exactly, as in Exactly(1)?

Ah ... because I didn't know that existed, and it doesn't show up if you search the docs for anything that mentions "Single" or "One" :)
Now that I've seen that, I also searched for "Count", which I note doesn't hit Exactly but does hit CountBetween which would work just as well.
I shall use that in future.
I would argue that adding that method may still be useful, in terms of adding discoverability (or perhaps renaming / adding an alternate name of CountIsExactly), but I agree that it's much less important if the functionality does already exist.

I agree that the document search isn't the best so I would recommend searching the docs using Google instead.

in terms of…discoverability

I think this is a separate issue that could apply to a number of other operators.

I agree that it's much less important if the functionality does already exist.

I'll close this issue on that basis.

FBM. Thanks for the responses.


Faker::Internet.slug generates strings with dots

I found myself searching for a bug among Capybara, DatabaseCleaner, Rails, etc. settings. However the problem was somewhere else.
I was using Faker::Internet.slug to generate the slug of a model and then visit it using Capybara. The controller could not find the model randomly. I thought it was a concurrency problem but the real reason was that sometimes the slug method returned strings with dots, ie: 'et.consequatur'. Rails thought the consequatur part was the format of the request like '.json' or '.xml', so it was finding only for the first word of the slug.
Maybe it will be safer to use '-' to join words as default option. Just in my opinion. It would have saved me some hours.
Thank you for your time :)

@alex-rodriguez Not sure this is bug since you can just pass in the separator you'd like to use in your slug like so:
Faker::Internet.slug(nil, '-')

This would insure that any words that are randomly generated in slug will always use the separator you pass in as 2nd argument.

@lacostenycoder I know, but I wonder that maybe for the next breaking release it would be better to change the default to '-' instead of '.' (IMHO of course :)

@alexcastano
Since a slug could potentially contain . and might even be needed or useful in some cases, as from the wiki example:
http://example.com/cgi-bin/feed.cgi?feed=news&frm=rss could be with slug	http://example.com/news.rss
see https://en.wikipedia.org/wiki/Semantic_URL#Structure
Since the method has the flexibility of accepting arguments, why not just use the one you would use as need as slug separator - ?
Although, I guess I agree that omitting it from the defaults might be useful.


“catastrophic forgetting” after transfer learning on MS2

Transfer learning may predict quite a few intensities with only one or two non-zero values.

It turns out that this is not “catastrophic forgetting”, this is due to low matching quality of DIA data.

Using spectral library tsv to training the model may also result in low-quality MS2 prediction. It depends on how many low-quality matches are there in spectral library.


How to change themeModel to change widget

Use case
hello guys,I know that I can change various colors and many styles in changeThemeMode, and use ThemeExtension to extend certain custom variables, but these variables do not involve widget. For example, I have a custom lightIcon and a darkIcon, how can I add them  in ThemeData for unified management.
Proposal
MaterialApp(
    home: HomePage(),
    themeMode: ThemeMode.light,
    theme: ThemeData.light().copyWith(widgetScheme: WidgetScheme()),//like ColorScheme
    darkTheme: ThemeData.dark().copyWith(colorScheme: ColorScheme()),
  )

@jy6c9w08
I think your question is better suited for support channels like StackOverflow so please ask the same there.
Closing from here, as this is more of a support question rather than a bug or feature request.

@darshankawar
yes，this question is more of a support question,I've seen examples of custom colors with ThemeExtension, and I tried to write a custom  widget example, but there is a override method lerp, and the widget type can't use it, so I think this can be  a feature. As far as my title is concerned, I know that it can be implemented with some state management plugins, such as providers, etc. But I feel that it will be much more convenient to put these widgets  into themeData for unified management，Thanks。


Feature/basic service structure

What
Basic API package structure for for handlers and middleware.
How to review
Check code makes sense, stategy seems sensible
Who can review
Anyone

The unit test checks have failed.

Sorry Joshua but I just noticed that the imports also need to be organised in service/interface and service/routes

Note:
In the following PR I removed some files, so I think the following issues don't need to be addressed:

example_component.go -> is removed in next PR
hello.go -> is removed in next PR


[FLINK-18570][hbase][WIP] SQLClientHBaseITCase.testHBase fails on azure

What is the purpose of the change

This pull request try to fix SQLClientHBaseITCase.testHBase fails on azure

Brief change log

Add log  for troubleshoot
Note unessary e2e test for test puerpose

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

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

Documentation

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

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure


Android: Test app functionality for Android

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Displaying a pdf in android does not work correctly.  There is a known issue with react-native-webview.
A work around is to access the help docs in strabospot.org but internet is required.

Also fix Drag Animation for Android.

Also fix Drag Animation for Android. Freehand drawing buttons.

Currently Mapbox is still having issues with adding draw tools because of Android will not support multiple touch events (https://github.com/nitaliano/react-native-mapbox-gl/issues/1058#issue-298910805). This has been a low priority since then.

@NathanNovak @jessicagood  Do we still want this open or should we report Android problems as their own separate issues?

We should report Android issues separately but tag the issue as Android.
Nathan Novak
On Wed, Feb 15, 2023, 11:41 AM Ellen Nelson @.***>
wrote:

@NathanNovak https://github.com/NathanNovak @jessicagood
https://github.com/jessicagood Do we still want this open or should we
report Android problems as their own separate issues?
—
Reply to this email directly, view it on GitHub
https://github.com/StraboSpot/StraboSpot2/issues/338#issuecomment-1431838351,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIO6OIVYBUVPRMQSSYB5JMLWXUPM3ANCNFSM46O62TIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Issues need to be in separate issue threads.


Revert strange changes, +monthsTitle

Q
A

Bug fix?
no

New feature?
no

BC breaks?
no

Related tickets
fixes #X, partially #Y, mentioned in #Z

License
MIT

These changes were submitted in #1705. @tigranbalayan what do you think about this change?

@acrobat, I have used "standart" shortening for daysShort and monthsShort, which used in books and other open source products.
Array daysMin should contains 2-chars shortening instead of 3-chars shortening as in daysShort.

Thanks @hayk, I will wait a few days to give @tigranbalayan some time to provide feedback. Otherwise I will merge this in a few days!

@acrobat, thanks!

Thanks @hayk @acrobat I mean it is ok to merge this change.

Ok thanks @hayk and @tigranbalayan!


Rasberry pi 4

Hello, does anyone know if nsynth works with rasberry Pi 4? Thank you!

I tried and it does not. I think it could work for sure but it requires maybe some source code modifications since a lot of the software versions need to be changed. I tried using all the same versions of sw in this package as on the raspi 4, and got pretty far but at some point the errors just got to be a pain and i bought a raspi 3 on ebay lol. Basically every time a new error popped up, I downgraded that software package to the version used on the version of raspian stretch indicated in the build docs. I didn't follow the rabbit hole the entire way, but this could be a possible avenue. I was concerned that as I downgraded these software packages I might be creating other errors elsewhere in the system (not necessarily in the nsynth stuff but in the actual OS)


Exception: Could not make request.

I made this very simple call just to test the library using python 3.8 in windos and it worked beautifully:
searchString = "any song here"
search = Search(searchString, limit=1)
print(search.result())

But, when I ran the same code in macOS big sur it returned me this error: Exception: Could not make request.
I can't think of any reasons as to why  this is happening...

You might be helped by someone experienced the same problem on Mac OS.
https://github.com/alexmercerind/youtube-search-python/issues/65#issuecomment-865888284


Support for username and password

Hi,
ist there a chance that you add support for username and password usage for client connection?

Yes ofcourse, I will include that in QOS-1 version.


how to finetune with gemma model？

how to finetune with gemma model？

help

I had download gemma-7b-it model from hugging face already, but not find the script that can finetune wiht my own data

How to sft with gemma？Can you tell me the sft data format?

I had download gemma-7b-it model from hugging face already, but not find the script that can finetune wiht my own data

How to sft with gemma？Can you tell me the sft data format?

@pengchongjin

e......
I have tried https://github.com/yongzhuo/gemma-sft, but sometimes NAN, maybe not stable.
logs:
{'loss': 0.0401, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0378, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0339, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0411, 'lr': 0.0003, 'epoch': 0.76}
{'loss': nan, 'lr': 0.0003, 'epoch': 0.76}
{'loss': nan, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0436, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0336, 'lr': 0.0003, 'epoch': 0.76}
{'loss': nan, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0514, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.05, 'lr': 0.0003, 'epoch': 0.76}
{'loss': 0.0696, 'lr': 0.0003, 'epoch': 0.76}
{'loss': nan, 'lr': 0.0003, 'epoch': 0.76}

@pengchongjin Is it possible to implement a class for fine tuning the model similar to what done with llama-recipes?

Are there any tutorials for fine-tuning 7b-it-quant model ?

Hi @aliasneo1
There are a few tutorials that demonstrate fine-tuning the gemma-2b model. You can follow similar procedures to fine-tune the Gemma variant gemma-7b-it.
Here are some resources:

Fine-tuning Gemma using JAX and Flax.
Fine-Tuning Gemma Models in Hugging Face with PyTorch on GPU and TPU.

Hi @runningabcd,
Could you please confirm if this issue is resolved for you with the above comment ? Please feel free to close the issue if it is resolved ?
Thank you.

Hi @runningabcd,
Closing this issue due to lack of recent activity,  Please reopen if this is still a valid request.
Thank you!


remove a tags around non expandable properties

I'm trying to make expandable properties bold but i noticed you add an a tag around all properties even if it can not be expanded this is the class json-formatter-toggler-link on that a tag

A pull request is welcome


Add full configuration support for OpenAI SDK models

This PR adds support for full configuration of OpenAI SDK models that were previously not exposed in the repository. The changes enable passing the complete configuration to OpenAI models through the API, providing greater flexibility and customization.
Previously, OpenAI models used a limited set of pre-defined configurations, which limited the ability of users to customize their models for specific use cases. With this change, we can now support more advanced use cases by enabling users to pass in their own custom configurations.
These changes are particularly useful for developers who are working with OpenAI models and want to fine-tune their configurations. The updated API enables them to do so without having to modify the source code or switch to a different SDK.
Overall, this PR improves the usability and flexibility of the OpenAI SDK and allows for more advanced use cases.

Thanks @jeekdong !


FOSCommentBundle + Pager

Hi there!
I tried to use your bundle - its kind of voodoo magic for the beginers in Symfony2
My cliend want to use threaded comments with pager - is it possible to use pager with FOSCommentBundle?
I ask it because I would like to get some advice before spending a couple days while trying to integrate FOSCommentBundle into my application :)

The CommentBundle does not currently support using pagination.
It shouldnt be too hard to add, but you might need to implement your own route to the comment thread (and adding your own controller) rather than using our built in render call.

If anyone ends up writing code for paginating CommentBundle, a pull request would be appreciated.


[Investigation] WebXR teleportation on the oculus quest has unexpected results

On some cases - when teleporting using the oculus quest controllers, the teleportation state gets "stuck" even thou the finger is off the trigger.
This is hard to reproduce, and, according to initial investigation, actually happens because the "touched" state is not updated correctly.
Need to make sure that :

touched/pressed state is correctly updated (i.e. - is it a driver/browser problem, or a problem with our implementation)
is there a way to make sure that it works correctly, even when touched is not correctly set. For example - if the thumbstick is exactly at 0,0, we can assume that the user has let go the thumbstick (even if touched is 0). This is not foolproof, but a way to make sure it does work correctly.
other controllers are working correctly. In personal tests - i couldn't recreate that using the MS MX controllers, but i am not using the MX controllers on a daily base

After a quick investigation - it seems like the touch controller is not always detecting touch events (even when it is clear that the component was touched). In case anyone wants, I have a video showing the issue.
When touching or pushing the edges of the button the thumbstick doesn't register the touch, but does have its values change.
Recommendation here would be to find a different method to detect when a teleport started and when the teleport ended.
The best candidate is still the touch event. When the user touches the component and moves it forward - a teleport started. In this case it is possible to detect when the teleportation started even without the touch event - if the axes moved forward, teleportation started.
Regarding teleportation ended - the issue here is that the rotation of the future position is based on the current axes position. We could say that when the axes are at 0,0 (i.e. The user released it) the teleportation is done, but there are two problems:

The final rotation might be wrong
The user can still move the axes to the middle during a rotation.

What will (probably) be developed is this:

Rotation of the future teleportation position will be calculated based on a previous position of the axes (a few frames back, will have to investigate what the number will be). This will lead to a short delay in visually changing the rotation, but if we are talking about 5-10 frames it will be unnoticeable / acceptable.
When axes stay 0,0 for a few frames (less than the number of frames in (1) - it will be considered a teleportation-ended event. In this case we could also inspect a change in delta for a short period of time, but this can be problematic when releasing the thumbstick close to the middle.

Both will be integrated WITH the touch event. We need to ignore touch events during a single teleportation if the even started using the axes instead of touch.

I independently discovered that tapping the thumbstick confirms as a touch and moves the view properly. It makes it tough to use the axis turning feature before teleporting and if attempting to use I face the wrong direction often.  I can produce it every time I use an Oculus Quest on the Oculus Browser.  Happy to pull any logs if needed/desired since I can get it to do this every time.

This is the same finding I have. If pushed from above, teleportation works, but if pushed from the side, the touched parameter is not set correctly, so teleportation never ends. Will be fixed :-)


carthage install libwebp issue

am trying to install with carthage but am getting an:
A shell task failed with exit code 128:
fatal: http://git.chromium.org/webm/libwebp.git/info/refs not valid: is this a git repository?
i am guessing the address for the library has changed or something?

can you check using master ?

that did the trick, thanks.

I'm having the exact same problem. I assume you mean checkout carthage from master branch and use make install? I removed carthage from brew before installing using make, still get error.
It's reporting version 0.7.5


Cant open scanner

Please restart transfer. Failed to scan QR code: com.google.mlkit.common.MlKitException: Code scanner module is not supported on current Google Play Services version, please upgrade.

solved

How did you solve this?

update to the latest google play service

Sadly not all phones have Google Play service installed :(

Yep, unfortunately Google's QR code viewer requires Play Services and it doesn't work on some devices. I link to this https://issuetracker.google.com/issues/261579118 in the readme. On the devices I've been able to test, deleting Play Services' data and letting it download again fixes the issue: https://support.google.com/googleplay/answer/9037938.

If anyone has a better QR code scanner Kotlin library to recommend, please do and I'll look into replacing it.


Bump to 0.3.2

Description

Bump to 0.3.2 and update changelog.
Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

If applicable:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass with my changes (locally and CI/CD build)
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (692b8fe) compared to base (9de3dec).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #347   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1202      1202
=========================================
  Hits          1202      1202

Impacted Files
Coverage Δ

xcdat/temporal.py
100.00% <ø> (ø)

xcdat/__init__.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.