text:
Tentatively remove CUDA 11.3 from support list

We observed failure in CUDA 11.3 fft cache tests, so let's skip supporting it in this month's release.
https://github.com/chainer/chainer-test/pull/658

Jenkins, test this please

Hmmm this is weird. I think the error happens in other modules. I've run all FFT tests with CUDA 11.3 and didn't find any issue.

I think something is wrong in test_memory.py. The earliest error happened there. In a previous CI run, it also had errors, but tests in test_cache.py passed.
https://jenkins.preferred.jp/job/chainer/job/chainer-test_pr/357/label=mn1-p100,test=cupy-py36/console
https://jenkins.preferred.jp/job/chainer/job/chainer-test_pr/356/label=mn1-p100,test=cupy-py36/console

I guess some tests started to run after driver version bump in Jenkins node?
https://github.com/cupy/cupy/blob/master/tests/cupy_tests/cuda_tests/test_memory.py#L1108
Btw is it mandatory to use driver API version to skip condition? If possible I want to use runtime API version because the driver  version is tied with the version of kernel module in the host environment, not isolated docker image.
https://github.com/cupy/cupy/blob/master/tests/cupy_tests/cuda_tests/test_memory.py#L1108
I tried it locally and after running it several times it failed:

========================================================================================================================================================================= FAILURES =========================================================================================================================================================================
___________________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_free_bytes ____________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_free_bytes>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='free_bytes is supported with driver 11.3+')
def test_free_bytes(self):
    with cupy.cuda.Device():

      assert 0 == self.pool.free_bytes()

E           AssertionError: assert 0 == 33554232
E            +  where 33554232 = <built-in method free_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa881280>()
E            +    where <built-in method free_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa881280> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa881280>.free_bytes
E            +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa881280> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_free_bytes>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1143: AssertionError
___________________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_total_bytes ___________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_total_bytes>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='total_bytes is supported with driver 11.3+')
def test_total_bytes(self):
    with cupy.cuda.Device():

      assert 0 == self.pool.total_bytes()

E           AssertionError: assert 0 == 33554432
E            +  where 33554432 = <built-in method total_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9c3280>()
E            +    where <built-in method total_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9c3280> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9c3280>.total_bytes
E            +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9c3280> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_total_bytes>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1192: AssertionError
__________________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_total_bytes2 ___________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_total_bytes2>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='total_bytes is supported with driver 11.3+')
def test_total_bytes2(self):
    # Note: MemoryAsyncPool works differently from MemoryPool. The first
    # allocation would be much bigger than requested, and the pool size
    # increases as needed. As a result, this test method is very different
    # from TestSingleDeviceMemoryPool.test_total_bytes(), in that the pool
    # size is either 0 or a fixed value (outside of our control).
    p1 = self.pool.malloc(self.unit * 2)
    current_size = self.pool.total_bytes()

    assert current_size == self.pool.total_bytes()
    p2 = self.pool.malloc(self.unit * 4)
    assert current_size == self.pool.total_bytes()
    del p1
    assert current_size == self.pool.total_bytes()
    del p2
    assert current_size == self.pool.total_bytes()
    self.pool.free_all_blocks()

  assert 0 == self.pool.total_bytes()

E       AssertionError: assert 0 == 33554432
E        +  where 33554432 = <built-in method total_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9eeb80>()
E        +    where <built-in method total_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9eeb80> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9eeb80>.total_bytes
E        +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9eeb80> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_total_bytes2>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1213: AssertionError
_______________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_total_bytes_stream ________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_total_bytes_stream>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='total_bytes is supported with driver 11.3+')
def test_total_bytes_stream(self):
    # Note: MemoryAsyncPool works differently from MemoryPool. The first
    # allocation would be much bigger than requested, and the pool size
    # increases as needed. As a result, this test method is very different
    # from TestSingleDeviceMemoryPool.test_total_bytes_stream(), in that
    # the pool size is either 0 or a fixed value (outside of our control).
    p1 = self.pool.malloc(self.unit * 4)
    current_size = self.pool.total_bytes()
    assert current_size > 0
    del p1
    assert current_size > 0
    self.pool.free_all_blocks()

  assert 0 == self.pool.total_bytes()

E       AssertionError: assert 0 == 33554432
E        +  where 33554432 = <built-in method total_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84cf40>()
E        +    where <built-in method total_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84cf40> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84cf40>.total_bytes
E        +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84cf40> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_total_bytes_stream>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1239: AssertionError
___________________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_used_bytes ____________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='used_bytes is supported with driver 11.3+')
def test_used_bytes(self):
    with cupy.cuda.Device():

      assert 0 == self.pool.used_bytes()

E           AssertionError: assert 0 == 200
E            +  where 200 = <built-in method used_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9ee610>()
E            +    where <built-in method used_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9ee610> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9ee610>.used_bytes
E            +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa9ee610> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1112: AssertionError
___________________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_used_bytes2 ___________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes2>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='used_bytes is supported with driver 11.3+')
def test_used_bytes2(self):
    p1 = self.pool.malloc(self.unit * 2)

  assert self.unit * 2 == self.pool.used_bytes()

E       AssertionError: assert (512 * 2) == 1224
E        +  where 512 = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes2>.unit
E        +  and   1224 = <built-in method used_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84c580>()
E        +    where <built-in method used_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84c580> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84c580>.used_bytes
E        +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa84c580> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes2>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1118: AssertionError
________________________________________________________________________________________________________________________________________________________ TestMemoryAsyncPool.test_used_bytes_stream ________________________________________________________________________________________________________________________________________________________
self = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes_stream>
@pytest.mark.skipif(cupy.cuda.runtime.driverGetVersion() < 11030,
                    reason='used_bytes is supported with driver 11.3+')
def test_used_bytes_stream(self):
    p1 = self.pool.malloc(self.unit * 4)
    del p1
    with self.stream:
        p2 = self.pool.malloc(self.unit * 2)

  assert self.unit * 2 == self.pool.used_bytes()

E       AssertionError: assert (512 * 2) == 2248
E        +  where 512 = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes_stream>.unit
E        +  and   2248 = <built-in method used_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa8819d0>()
E        +    where <built-in method used_bytes of cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa8819d0> = <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa8819d0>.used_bytes
E        +      where <cupy.cuda.memory.MemoryAsyncPool object at 0x7fd3fa8819d0> = <cupy_tests.cuda_tests.test_memory.TestMemoryAsyncPool testMethod=test_used_bytes_stream>.pool
tests/cupy_tests/cuda_tests/test_memory.py:1136: AssertionError
================================================================================================================================================================= short test summary info ==================================================================================================================================================================
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_free_bytes - AssertionError: assert 0 == 33554232
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_total_bytes - AssertionError: assert 0 == 33554432
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_total_bytes2 - AssertionError: assert 0 == 33554432
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_total_bytes_stream - AssertionError: assert 0 == 33554432
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_used_bytes - AssertionError: assert 0 == 200
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_used_bytes2 - AssertionError: assert (512 * 2) == 1224
FAILED tests/cupy_tests/cuda_tests/test_memory.py::TestMemoryAsyncPool::test_used_bytes_stream - AssertionError: assert (512 * 2) == 2248
============================================================================================================================================================== 7 failed, 120 passed in 5.57s ===============================================================================================================================================================

Jenkins CI test (for commit 604727b5f656f3f682e3b56c93fb7970ec687810, target branch master) succeeded!

Btw is it mandatory to use driver API version to skip condition? If possible I want to use runtime API version because the driver version is tied with the version of kernel module in the host environment, not the CUDA version used in isolated docker image.

It is not enough to for driver 11.2 + Toolkit 11.3 to support the new allocator query functionalities. The CUDA runtime API raises errors. I feel the whole new forward compatibility thing makes it very complicated...
btw Docker uses the host's driver. Isn't that what we need here? I thought our Jenkins workers have their driver updated?

I tried the test locally and after running it several times it failed:

Could you share a reproducer so that I can look into it? I tried repeating pytest tests/cupy_tests/cuda_tests/test_memory.py but haven't seen any errors.

@emcastillo Failed to backport automatically.

Not cleanly cherry-picked

Backport unnecessary as #5232 is not merged yet

@kmaehashi Are you on CUDA 11.3.0 or 11.3.1?

btw I think having this PR merged is OK. I remember when I tried driver 11.2 + Toolkit 11.3, I encountered some PTX related errors, and had to ask NVRTC to give me SASS instead (#5097). It's best to get #5097 completed before declaring the support of 11.3.

The fix in #5264 solved memory-related test failures on CUDA 11.3 in my environment.
Reproducible with both on CUDA 11.3.0 and 11.3.1, and any of A100/V100/P100.

authors: chainer-ci emcastillo kmaehashi leofang


text:
Remove scipy import

Follows up #7190, which causes CI failure in cupy.linux.cuda111 and cupy.linux.cuda111.multi

@takagi Approved. Please merge by yourself when necessary tests pass.

@ev-br We are keeping CuPy importable without scipy installation like this:
https://github.com/cupy/cupy/blob/445169dae3d1a5e5a9e6ec9adbef441a5ea4f70f/cupyx/scipy/sparse/linalg/_solve.py#L17-L22
We are also trying to keep the code runnable without scipy installation whenever possible, with some exceptions e.g., conversion of sparse arrays from GPU to CPU (which obviously requires scipy.sparse.*_matrix data structure) and sparse linalg functions like SuperLU.

source: gharchive/pull-request

authors: kmaehashi takagi

repo: cupy/cupy

license: MIT

license_type: permissive

license_source: github-api


text:
Port vectorstrength, coherence and spectrogram from CuSignal to cupyx.scipy.signal

See https://github.com/cupy/cupy/issues/7403
Depends on https://github.com/cupy/cupy/pull/7838

/test full

Would you add these APIs to signal.rst? Then, I will kick the CI again to merge this.

/test full

Would you check the CI result? It still seems to have relatively larger differences even with newer scipy.
_tests/scipy_tests/signal_tests/test_spectral.py::TestVectorstrength::test_opposite_1dperiod
_tests/scipy_tests/signal_tests/test_spectral.py::TestVectorstrength::test_opposite_2dperiod

AssertionError:
Not equal to tolerance rtol=1e-07, atol=1e-07

Mismatched elements: 10 / 10 (100%)
Max absolute difference: 0.32175055
Max relative difference: 0.1201483
 x: array([2.356194, 2.356194, 2.356194, 2.356194, 2.356194, 2.356194,
       2.356194, 2.356194, 2.356194, 2.356194])
 y: array([2.677945, 2.677945, 2.677945, 2.677945, 2.677945, 2.677945,
       2.677945, 2.677945, 2.677945, 2.677945])

I cannot reproduce this locally. I'm using SciPy 1.11.3

Record: full test result
https://ci.preferred.jp/p/dashboard_by_commit_id?commit_id=a54fcce947623353e474c9bf46e555f2cfc77d28

/test mini

Thanks for the marks on the tests. It seems that the problematic tests pass on linux with scipy==1.8 (cupy.linux.cuda113). Because I'd like to minimize the conditions to mark as xfail, would you change the xfail condition to on linux with sicpy>=1.9 only? Then, I will kick the full test again and merge this pull request.

I investigated the case in the CI environment for a short time, but couldn't reproduce the error.

/test full

For record: https://ci.preferred.jp/p/dashboard_by_commit_id?commit_id=e6ef62ecd79d28f68eed3bac03995b9be1b06e90

/test full

/test full

Record: https://ci.preferred.jp/p/dashboard_by_commit_id?commit_id=aeb198931458564f4cfade8b1265908580d0c9dd

/test cuda113

LGTM!

Record: https://ci.preferred.jp/p/dashboard_by_commit_id?commit_id=e5ef6ab2ca5678457fc618136dbaf807d5f8683f

Thanks, @andfoy!

authors: andfoy takagi


text:
Android 13 targeting investigation + disable AAID at GMS level

User Story
As a Product Owner,
I want to create a Curious Reader production build that targets Android 13 (API level 33) that disables Android Ad ID collection at the GMS level (see note from Google Play below for more),
So that we can QA test Curious Reader compatibility with Android 13 and fill out the additional compliance declarations on Google Play associated with Android 13 and have it checked for compliance by the Google Play Store.
From Google Play:
If your app is updated to target API level 33 (Android 13), ensure that your app or a library included in your app does not declare the new AAID permission, or that AAID is disabled. For more information on this permission and how to include or disable AAID, see this article. By updating to target API level 33 and not including the permission, AAID will automatically be disabled (set to a string of zeros).
Acceptance Criteria
Given that I have made a build of the Curious Reader container app that targets Android 13 (API level 33),
When I play it on a physical or virtual device that uses Android 13,
Then the app should behave as it did on previous versions of Android.

@burrage As the current prod app is working as expected and also is approved by play store, please let us know if we still need to proceed with this task?

@divyahariharan2103 We can indeed move this to DONE! The

line in the Android Manifest took care of the compliance stuff in conjunction with the new OS targeting :-)
Thankfully much easier than expected and less effort than we were anticipating with the 3! (hopefully!)

ok thanks Ben !!

source: gharchive/issue

repo: curiouslearning/FeedTheMonsterJS


text:
Compact Mode Inline - not working

Checklist:

[ x ] I updated to the latest version available
[ x ] I cleared the cache of my browser

Release with the issue:
1.10.9
Last working release (if known):
N/A
Browser and Operating System:
Chrome - Windows 11
Android - HA App (Latest)

Description of problem:
When enabling compact mode with "compact: true" the icon and name are not inline. Instead, the icon is showing below the name. Unless you add the following which forces the icon and text to be inline with each other again:
action_button:
show: true

Javascript errors shown in the web inspector (if applicable):

Additional information:

I'm not able to reproduce this with 1.12.0. Please upload a screenshot and provide your full config if you run into this issue again.

authors: PhAzE-Variance rohankapoorcom

repo: custom-cards/slider-button-card


text:
toMendeley / fromMendeley improvements

Null check
https://github.com/customcommander/ris/blob/998c6d97f10486044f2258959f8b96f0b099a7a7/src/mendeley.js#L143
The function will throw an error if risText can't be parsed. It should return null instead.
Tasks

[x] toMendeley should return null if the text can't be parsed (and mention this in the README)
[x] fromMendeley should return null if argument is not an array or doesn't contain any valid references

:tada: This issue has been resolved in version 5.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: customcommander/ris


text:
Upgrade to 3.3.2 with expo 49

SDK version: I wanted to update to 3.3.2
Environment: Development or Production
Describe the bug
Building the iOS dev client with expo fails (see screenshot) with expo 49.
To Reproduce
Update the package.
Expected behavior
It should work
Screenshots

Additional context
It happens when building iOS with expo 49.

Hey @enisze, can you please try expo prebuild --clean. It looks like a pod issue so that should resolve it. If no then please delete the podlock file.

Closing issue due to inactivity.
Feel free to add new comments and we would be happy to re-open and help.

authors: Shahroz16 enisze levibostian

repo: customerio/customerio-reactnative


text:
Bump nu.validator.validator to v15.3.28

Fixes #81.

FYI I have another minor release on the way soon, to fix a couple of regressions I introduced in the v15.3.28 release

Noted. Thanks for the heads-up.

authors: cvrebert sideshowbarker

repo: cvrebert/lmvtfy

license: mit

license_source: bigquery


text:
Evaluate Objective function at user provided solution

Problem - A minimal example
I am trying to solve the following convex problem.

I want to compare the performance of my own algorithm with solver provided by CVXPY. I tried two different way of expressing the objective, where I set w_{ij} = 1 for the sake of simplicity,
u = cp.Variable((n,d))
1. objective = cp.Minimize((0.5 * cp.sum_squares(data - u))+ penalty * cp.norm(u[t1] - u[t2], 1) )
2. objective = cp.Minimize((0.5 * cp.norm(data - u, "fro") ** 2)+ penalty * cp.norm(u[t1] - u[t2], 1) )

These two formulations gave me nearly the same solution, but when I plugged the u.value back to my objective function, which was written as
a = 0.5 * np.sum(np.linalg.norm(data - u.value, 2, axis=1) ** 2.0)
b = penalty * np.sum(np.linalg.norm(u.value[t1] - u.value[t2], ord=1,axis=1))
a + b

it produced totally different results.
The value provided by CVXPY is 2943.0156660023194, while the expression a+b yields 5488.4470645803785.
I have no idea how to debug.
Describe the solution you'd like
It would be convenient for users to evaluate the objective specified in CVXPY at their provided solution, such that they can know at least whether they are using correct objective functions.
I would expect something like
problem._evaluate_objective(user-provided-solution)

Appendix
The complete code for CVXPY solving the problem is attached below.
np.random.seed(521)
group1 = np.random.multivariate_normal(mean = [10,10], cov=np.eye(d), size=n)
group2 = np.random.multivariate_normal(mean = [-10,10], cov=np.eye(d), size=n)
group3 = np.random.multivariate_normal(mean = [-10,-10], cov=np.eye(d), size=n)
group4 = np.random.multivariate_normal(mean = [10,-10], cov=np.eye(d), size=n)
data = np.vstack((group1, group2, group3, group4))
n,d = data.shape
penalty = 0.1
w = np.array([])
for i in range(n-1):
    for j in range(i+1, n):
        w = np.append(w, [i, j, 1])
w = w.reshape(-1, 3)
t1, t2, w_t = w[:, 0].astype("int"), w[:, 1].astype("int"), w[:, 2]
u = cp.Variable((n,d))
#objective = cp.Minimize((0.5 * cp.sum_squares(data - u))+ penalty * cp.norm(u[t1] - u[t2], 1) )
objective = cp.Minimize((0.5 * cp.norm(data - u, "fro") ** 2)+ penalty * cp.norm(u[t1] - u[t2], 1) )
prob = cp.Problem(objective)
prob.solve(solver="ECOS", verbose=True)

You can set the variable value fields yourself, then evaluate any expression involving them. In your case, u.value = ...; print(objective.value). Perhaps this functionality should be better documented. I'm not sure why you're getting something different with numpy. Probably some subtle difference in the two expressions.

You can set the variable value fields yourself, then evaluate any expression involving them. In your case, u.value = ...; print(objective.value). Perhaps this functionality should be better documented. I'm not sure why you're getting something different with numpy. Probably some subtle difference in the two expressions.

I know I can retrieve the objective value by objective.value. But what I really what to do is to evaluate the objective function value at my solution (derived from another algorithm ) not the solution provided by the cvxpy.

I believe the following code does what you are asking for.
x = cp.Variable(shape=(3,))
x.value = np.array([1,2,3])
expr = cp.sum_squares(x)
print(expr.value)

I.e. you can manually assign a Variable a value, and that value is propagated through calculation of subsequent expressions.

I believe the following code does what you are asking for.
x = cp.Variable(shape=(3,))
x.value = np.array([1,2,3])
expr = cp.sum_squares(x)
print(expr.value)

I.e. you can manually assign a Variable a value, and that value is propagated through calculation of subsequent expressions.

Thanks. It indeed works, but the rounding error seems to be a little bit large. See figure below.

May  I ask one more question?
Why the following two expressions are different?
# the way I express the objective function using numpy
0.5 * np.sum(np.linalg.norm(data - u.value, 2, axis=1) ** 2.0) + penalty * np.sum(np.linalg.norm(u.value[t1] - u.value[t2], ord=1,axis=1))

# the way I express the objective function using CVXPY
(0.5 * cp.sum_squares(data - u))+ penalty * cp.norm(u[t1] - u[t2], 1)

# t1, t2 here are vectorized indices for summation.

I think essentially they are both equivalent to

where w_{ij}=1.
If not, what is the correct way to specify the objective in the CVXPY?

It looks fine to me. Maybe try writing both expressions using abs instead of the L1-norm.

authors: Rothdyt SteveDiamond rileyjmurray

repo: cvxgrp/cvxpy


text:
minor typo in project description.

Great job here; this is helpful as an ally. Minor misspelling in the About section on the right. I only noticed it as a header auto-populated with it when I posted it elsewhere. Bless & have a good one.

Thank you very much for letting me know, I will update this later today!

repo: cvyl/awesome-transgender


text:
grammar conflicts

Hi.
When I use command 'node_modules/.bin/jison src/cssparser.y src/css.l -t -o p.js 2>err.log | tee debug.log', jison gives me 634 conflicts in grammar.
It's possible to make this zero?
update1: note - http://stackoverflow.com/questions/15825195/debugging-in-jison

I rewrote css parser for improve features, and this issue is cleared at new version.

authors: cwdoh mainiak


text:
V3 release date

Hi, i consider use this library to my service.
Could you share when V3 release?

Shooting to have it as a Beta release by end of year :)

@dsboo   You can take a look at this, this is the implementation of the reference v3 version https://github.com/geekskai/react-network-detect

authors: cwise89 dsboo geekskai


text:
MIND-SSC implementation for lung/abdominal MR-CT

Which MIND-SSC features implementation are you using for the lung/abdominal MR-CT dataset?
And in your slides of the miccai 2021 oral are you training this dataset unsupervised or semi-supervised? If the latter, do you remember if the unsupervised version gives good results too?
Thanks!

Hi @annareithmeir,
I use the MIND-SSC implementation at https://github.com/multimodallearning/convexAdam/blob/main/convex_adam_utils.py
For the Learn2Reg 2021 challenge, I use semi-supervised loss (with dice loss). I didn't try the unsupervised version for the MR-CT task. However, I did try the unsupervised version for abdominal CT-CT registration. It shows ~10% drop in Dice. The result is in  https://arxiv.org/abs/2306.16997.

authors: annareithmeir cwmok


text:
Error when trying to scan all pages

Hello,
I am attempting to scan from an Epson DS-6500 scanner through the feeder, and when I set it to scan all available pages, it returns an error from the Download() method. I'm just using SetProperty(WiaPropertyId.IPS_PAGES, WiaPropertyValue.ALL_PAGES) to set the page value. Is there something different I should be doing?
Message: "Value does not fall within the expected range."
InnerException:null
StackTrace:
at NAPS2.Wia.Native.IWiaTransfer.Download(Int32 lFlags, IWiaTransferCallback pIWiaTransferCallback)
at NAPS2.Wia.Native.NativeWiaMethods.Download2(IntPtr transferPtr, TransferStatusCallback func)
at NAPS2.Wia.WiaTransfer.Download()

Here is the code that does the scanning:
private static List<ScannedImage> scanFromDevice(Device device, bool duplex, int pagesToScan)
{
    List<ScannedImage> images = new List<ScannedImage>();

    // Get device
    using var deviceManager = new WiaDeviceManager();
    device.nativeDevice = deviceManager.FindDevice(device.Id);

    // Select "Feeder"
    using var item = device.nativeDevice.FindSubItem("Feeder");

    // Scan all pages in the feeder at once if greater than
    // max pages per scan
    if (pagesToScan > ApplicationConfig.GetMaxPagesPerScan())
        item.SetProperty(WiaPropertyId.IPS_PAGES,
                        WiaPropertyValue.ALL_PAGES);
    else
        item.SetProperty(WiaPropertyId.IPS_PAGES,
                        pagesToScan);
    // Set BW scan
    item.SetProperty(WiaPropertyId.IPA_DATATYPE, 0);
    item.SetProperty(WiaPropertyId.IPS_XRES, 300);
    item.SetProperty(WiaPropertyId.IPS_YRES, 300);

    if (duplex)
    {
        try
        {
            // Enable duplex scanning
            item.SetProperty(WiaPropertyId.IPS_DOCUMENT_HANDLING_SELECT,
                                WiaPropertyValue.DUPLEX);
        }
        catch (System.ArgumentException)
        {
            Console.WriteLine("Duplex scanning not allowed on this machine.");
        }
    }

    // Set up the scan
    using var transfer = item.StartTransfer();
    transfer.PageScanned += (sender, args) =>
    {
        using (args.Stream)
        {
            var bitmap = new System.Drawing.Bitmap(args.Stream);
            // Do something with the image
            string fileName = Path.ChangeExtension(Path.GetTempFileName(), "png");

            File.Delete(fileName);
            bitmap.Save(fileName, ImageFormat.Png);

            // add file to output list
            System.Windows.Controls.Image image = new System.Windows.Controls.Image();

            ScannedImage scannedImage = DrawImage(fileName);
            images.Add(scannedImage);
        }
    };

    // Do the actual scan
    transfer.Download();
    if( images.Count <= 0 )
    {
        Console.WriteLine("No images scanned.");
    }
    return images;
}

Thanks

I'm not sure, you can trying comparing against what NAPS2 does or just try using NAPS2.Sdk and see if that resolves the issue.

authors: aditya-gune cyanfish


text:
tmLanguage file doesn't work with Sublime Text 4

Description

Hi! It seems the tmLanguage file is not compatible with Sublime Text. At least, not with the version 4, the latest build (4152).
Following the instructions to install the package doesn't do anything, the Cylc syntax doesn't get added to the list.
Reproducible Example
I dug deeper and opened the Cylc.tmLanguage file. In Sublime, I did Tools > Developers > New syntax from Cylc.tmLanguage. This is supposed to convert the file to a sublime-syntax file.
In Sublime's console I got:
patterns and includes are not supported within captures: {'0': {'patterns': [{'include': '#headers'}]}}
patterns and includes are not supported within captures: {'1': {'patterns': [{'include': '#jinja2'}, {'match': '[\\w\\+\\^\\$][\\w\\+\\-\\^\\$\\/\\t ,:]*', 'name': 'keyword.graph.cylc'}]}, '2': {'name': 'keyword.operator.assignment.cylc'}}
patterns and includes are not supported within captures: {'0': {'patterns': [{'include': '#graphSyntax'}]}}
Traceback (most recent call last):
  File "/opt/sublime_text/Lib/python38/sublime_plugin.py", line 1659, in run_
    return self.run()
  File "/opt/sublime_text/Packages/Default.sublime-package/convert_syntax.py", line 433, in run
  File "/opt/sublime_text/Packages/Default.sublime-package/convert_syntax.py", line 358, in convert
  File "/opt/sublime_text/Packages/Default.sublime-package/convert_syntax.py", line 269, in make_context
  File "/opt/sublime_text/Packages/Default.sublime-package/convert_syntax.py", line 328, in make_context
Exception: unknown pattern type: dict_keys(['name', 'patterns'])

Maybe the latest Sublime has gone incompatible ? Or maybe that the tmLanguage has changed in ways incompatible with Sublime's implementation ?
It's not a major problem. If the solution isn't easy, it could at least be helpful to indicate on the README that some versions of Sublime are not supported.
I am running Sublime on a Fedora 38 Linux machine.

Apologies for not spotting this issue sooner.
Unfortunately, none of us have access to Sublime Text at present. The underlying TextMate grammar has not changed in a year (https://github.com/cylc/Cylc.tmbundle/commit/9b43c77297e23f61c2c1d20639a3b922a188d9cd) so this is probably due to changes in Sublime rather than changes in the TextMate grammar which we also use in other text editors. There are a few mentions of syntax highlighting improvements in the v4 changelog, but no mention of compatibility breaking changes.
The issue appears similar to this unanswered question: https://forum.sublimetext.com/t/convert-syntax-py-exception-unknown-pattern-type/15076
I'm not sure what to make of that error unfortunately (it's coming from within the Sublime Python code). We're trying to use this grammar in a new context at the moment which means passing it through another validator, will see if it flags anything.

authors: aulemahal oliver-sanders


text:
i3wm - hide xorg start messages

Hi!
I use i3wm and I really like ly DM, thanks for sharing.
However, xorg's start output gives the impression that something is wrong even though it is not.
My proposal here is just to suppress it:
From:
	config.x_cmd = strdup("/usr/bin/X");

To:
	config.x_cmd = strdup("/usr/bin/X -keeptty > ~/.xorg.log 2>&1");

Thank you! :)

Hi, this is already configurable in /etc/ly/config.ini, but thank you for your interest :)

authors: cylgom raphaunix

repo: cylgom/ly

license: WTFPL


text:
v10 examples do not use latest version 12.x

Current situation
Example workflows in examples/v10 are configured to use Cypress 10.0.0, released on June 1, 2022. Since then, Cypress 11 and Cypress 12 have been released. The version is stored in package.json files, package-lock.json, yarn.lock and pnpm-lock.yaml files.
Suggested change
Update all v10 example workflows in examples/v10 to use the latest Cypress version according to the Cypress changelog.
Benefits
Updating the v10 examples to use the latest Cypress version provides increased confidence that GHA is up-to-date and compatible with the latest Cypress major version (12).

I already successfully tested updating the v10 examples to use Cypress 12, however I will hold back on submitting a PR until PR https://github.com/cypress-io/github-action/pull/673 is completed to avoid getting into package-lock.json and yarn.lock conflicts. Also it would be good to hear if updating is actually wanted or not.

@jaffrepaul
Any feedback on this suggestion? It makes sense to me to update.

Agreed. We're working to get all of our ancillary tools and repos to use the latest version of Cypress. Certainly applies here. We'll need to land on some appropriate naming conventions, i.e the /v10 folder, etc.

@jaffrepaul

We'll need to land on some appropriate naming conventions, i.e the /v10 folder, etc.

The naming of examples/v10 would be misleading after updating the examples to Cypress 12.x. So I follow your thinking about settling on a different naming convention.
One possibility would be:

examples/v9 - leave unchanged
examples  - remove the v10 level and move it up one level for 12.x and any later versions

If there is a prospect in the future of another breaking change in Cypress which could create the need for another complete set of compatible examples, then it would be better to keep the v10 level and rename v10 in examples/v10 to, for example, one of the following:

v1x (which would cover Cypress versions 10-19)
v1n
current
latest

Removing the v10 level would be my first choice and renaming v10 to v1x would be my second choice.

@jaffrepaul
If there is a change in the v10 directory I would suggest to split the changes into two separate PRs:

No change to v10 directory, update Cypress to latest 12.x
Change the directory name or location for the 12.x tests. This also affects documentation.

That would make it easier for testing and review.

[ ] PR #725 is now submitted to update the examples to Cypress 12.3.0

Next step:

Move the Cypress 12.3.0 examples from examples/v10 to examples and eliminate the  examples/v10 directory, since the label v10 no longer fits the v12 version (or any future possible later major version v13, etc.).

repo: cypress-io/github-action


text:
please make declarations independent from generator

Hi,
thank you for making you work available.
I only want to get the declarations, and for now I think I don't need the entire generator. Is it possible to package it a little bit differently so that the declarations do not have a dependency on the generator and are thus more independent?
So than I could avoid adding additional repositories to my gradle file.
I Could build it just fine without additional repositories, but idea intelijii was marking everything red, because the generator module had certain dependencies which I would not get.
Thanks

Hi @runkelstein,
When you're depending on com.github.cypressious.kotlin-webextensions-declarations:webextensions-declarations, you're only getting the declarations. They don't have any dependencies on the generator.

Hi  cypressious,
ok than maybee is a problem with my gradle file or inteliji. I can build it without the generator, but intelijii marks it still red:

Ok, now I see it, I have to change that line
compile("com.github.cypressious", "kotlin-webextensions-declarations", Versions.kotlinWebextensions);
to
compile("com.github.cypressious.kotlin-webextensions-declarations", "webextensions-declarations", Versions.kotlinWebextensions);
then it is working as expected

Perfect, thx for reporting your solution.

authors: cypressious runkelstein


text:
Errors: KeyError: '<pod_name>' and AttributeError: 'NoneType' object has no attribute 'group'

I set this up in my kubernetes cluster
[init] Checking for kube config ...OK
[init] KUBE_CONTEXT not set, relying on context set in /etc/kube/config
[init] Checking current kube context ...OK
[init] Current context: aws
[init] Checking cluster info ...OK
2019-03-01 01:45:18,634 CRIT Set uid to user 0
2019-03-01 01:45:18,636 INFO supervisord started with pid 1
2019-03-01 01:45:19,638 INFO spawned: 'transformer' with pid 32
2019-03-01 01:45:19,640 INFO spawned: 'kubectl-proxy' with pid 33
[uWSGI] getting INI configuration from uwsgi.ini
*** Starting uWSGI 2.0.18 (64bit) on [Fri Mar  1 01:45:19 2019] ***
compiled with version: 6.3.0 20170516 on 01 March 2019 01:10:52
os: Linux-4.14.88-88.76.amzn2.x86_64 #1 SMP Mon Jan 7 18:43:26 UTC 2019
nodename: metrics-server-2-prom-755b964746-p6rhc
machine: x86_64
clock source: unix
detected number of CPU cores: 2
current working directory: /home/prometheus/transform
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
your memory page size is 4096 bytes
detected max file descriptor number: 65536
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address 0.0.0.0:9100 fd 3
Starting to serve on 127.0.0.1:8080
Python version: 3.7.2 (default, Feb  6 2019, 03:40:10)  [GCC 6.3.0 20170516]
Set PythonHome to /home/prometheus/transform/transformenv
*** Python threads support is disabled. You can enable it with --enable-threads ***
Python main interpreter initialized at 0x562b2e793850
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 218712 bytes (213 KB) for 2 cores
*** Operational MODE: preforking ***
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x562b2e793850 pid: 32 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 32)
spawned uWSGI worker 1 (pid: 39, cores: 1)
spawned uWSGI worker 2 (pid: 40, cores: 1)
2019-03-01 01:45:21,536 INFO success: transformer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-03-01 01:45:21,536 INFO success: kubectl-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[pid: 40|app: 0|req: 1/1] 10.10.113.116 () {24 vars in 287 bytes} [Fri Mar  1 02:02:56 2019] GET / => generated 297 bytes in 2 msecs (HTTP/1.1 200) 2 headers in 80 bytes (1 switches on core 0)
[2019-03-01 02:17:36,085] ERROR in app: Exception on /metrics [GET]
Traceback (most recent call last):
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "./transform.py", line 278, in metrics
'pods': trans_pod_metrics(json['pods'])
File "./transform.py", line 199, in trans_pod_metrics
more[lbl['pod']]['node'],
KeyError: 'kube-proxy-9jqrt'
[pid: 40|app: 0|req: 2/2] 10.10.115.20 () {28 vars in 466 bytes} [Fri Mar  1 02:17:35 2019] GET /metrics => generated 291 bytes in 329 msecs (HTTP/1.1 500) 2 headers in 84 bytes (1 switches on core 0)
[2019-03-01 02:17:40,894] ERROR in app: Exception on /metrics [GET]
Traceback (most recent call last):
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "./transform.py", line 278, in metrics
'pods': trans_pod_metrics(json['pods'])
File "./transform.py", line 199, in trans_pod_metrics
more[lbl['pod']]['node'],
KeyError: 'ingress-nginx-ingress-default-backend-6679dd498c-s7cxc'
[pid: 39|app: 0|req: 1/3] 10.10.115.20 () {28 vars in 466 bytes} [Fri Mar  1 02:17:40 2019] GET /metrics => generated 291 bytes in 138 msecs (HTTP/1.1 500) 2 headers in 84 bytes (1 switches on core 0)
[pid: 40|app: 0|req: 3/4] 10.10.115.20 () {28 vars in 453 bytes} [Fri Mar  1 02:17:41 2019] GET / => generated 297 bytes in 1 msecs (HTTP/1.1 200) 2 headers in 80 bytes (1 switches on core 0)
[pid: 40|app: 0|req: 4/5] 10.10.115.20 () {28 vars in 491 bytes} [Fri Mar  1 02:17:42 2019] GET /apis/k8s.metrics.io => generated 233 bytes in 2 msecs (HTTP/1.1 404) 2 headers in 72 bytes (1 switches on core 0)
[2019-03-01 02:17:45,886] ERROR in app: Exception on /metrics [GET]
Traceback (most recent call last):
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "./transform.py", line 278, in metrics
'pods': trans_pod_metrics(json['pods'])
File "./transform.py", line 199, in trans_pod_metrics
more[lbl['pod']]['node'],
KeyError: 'prometheus-prometheus-node-exporter-978th'
Also This:
2019-03-01 03:07:15,396 INFO success: transformer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-03-01 03:07:15,396 INFO success: kubectl-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[pid: 72|app: 0|req: 1/1] 172.17.0.1 () {24 vars in 255 bytes} [Fri Mar  1 03:07:27 2019] GET / => generated 297 bytes in 1 msecs (HTTP/1.1 200) 2 headers in 80 bytes (1 switches on core 0)
[2019-03-01 03:07:37,133] ERROR in app: Exception on /metrics [GET]
Traceback (most recent call last):
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functionsrule.endpoint
File "./transform.py", line 278, in metrics
'pods': trans_pod_metrics(json['pods'])
File "./transform.py", line 174, in trans_pod_metrics
more = get_pod_metrics_from_cli()
File "./transform.py", line 238, in get_pod_metrics_from_cli
'ns': line.group(1),
AttributeError: 'NoneType' object has no attribute 'group'
[pid: 72|app: 0|req: 2/2] 172.17.0.1 () {24 vars in 269 bytes} [Fri Mar  1 03:07:33 2019] GET /metrics => generated 291 bytes in 3899 msecs (HTTP/1.1 500) 2 headers in 84 bytes (1 switches on core 0)

Do you also have metrics-server deployed and configured correctly in Kubernetes?

Yes, I was able to pull down some stats with the API.

Using gcr.io/google_containers/metrics-server-amd64:v0.3.3 and metrics-server-prom 0.9.0.
[2019-07-18 17:25:19,457] ERROR in app: Exception on /metrics [GET]
Traceback (most recent call last):
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 2446, in wsgi_app
response = self.full_dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1951, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1820, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise
raise value
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1949, in full_dispatch_request
rv = self.dispatch_request()
File "/home/prometheus/transform/transformenv/lib/python3.7/site-packages/flask/app.py", line 1935, in dispatch_request
return self.view_functionsrule.endpoint
File "./transform.py", line 275, in metrics
'pods': trans_pod_metrics(json['pods'])
File "./transform.py", line 171, in trans_pod_metrics
more = get_pod_metrics_from_cli()
File "./transform.py", line 235, in get_pod_metrics_from_cli
'ns': line.group(1),
AttributeError: 'NoneType' object has no attribute 'group'
[pid: 92|app: 0|req: 3/3] 172.17.0.1 () {36 vars in 680 bytes} [Thu Jul 18 17:25:12 2019] GET /metrics => generated 290 bytes in 7243 msecs (HTTP/1.1 500) 2 headers in 84 bytes (1 switches on core 0)

This is will be dealt with here: #12

Solved

authors: cytopia kanewinter

repo: cytopia/metrics-server-prom


text:
Empty classes being added cause a crash

if you add a whitespace too much in your classes you want added, you'll get a crash
https://github.com/czeckd/angular-svg-icon/blob/1790114e5f1b0173e0741212d3fb2d5e350b3822/projects/angular-svg-icon/src/lib/svg-icon.component.ts#L269
Should check for any empty classes

@icorne : I'll update this issue when I get a release built with this fix. Thank you!

Released in v13.0.0.

authors: czeckd icorne

repo: czeckd/angular-svg-icon


text:
Visualization code for Figure 3 (left) in Paper

Provides solution to following issues:
https://github.com/d-ailin/GDN/issues/77
https://github.com/d-ailin/GDN/issues/51

Many thanks for your interest and codes :). Sorry for the late response, and I will do the code review later this week.

Provides solution to following issues:
#77
#51
ValueError: not enough values to unpack (expected 3, got 1),run your code [graph_visualization.py]

Provides solution to following issues:
#77
#51

hello,i can't find the file anomaly.py in your readme file

authors: d-ailin shahaamirbader wuchenhu98 zfnaixuexi

repo: d-ailin/GDN


text:
Test env log adding ::f to end of test name

I think that test_env_log::test is modifying test names as reported by the runner. Here's a test annotated with #[test]:
     Running target/debug/deps/quwue-ace6fa7a6ba4cdb3

running 1 test
test run::tests::parse_message ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

[Finished running. Exit status: 0]

And here's one with test_env_log::test:
     Running target/debug/deps/quwue-ace6fa7a6ba4cdb3

running 1 test
test run::tests::parse_message::f ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

[Finished running. Exit status: 0]

Notice the extra ::f.

That is required to allow for global imports. What exactly is the problem you are having?

No particular problem, it's just unattractive and makes the test runner output harder to read.

I am not aware of another way to solve the problem, so I don't see how it can be removed. If you have a suggestion please let me know.

Ahh, okay, I looked at the code and this is definitely a harder problem than I thought. I have no clever ideas to solve it 😅

FYI, I found a way to fix that peculiarity while keeping the desired behavior. Contained in 0.2.4.

FYI, I found a way to fix that peculiarity while keeping the desired behavior. Contained in 0.2.4.

NIce!

NIce!

authors: casey d-e-s-o

repo: d-e-s-o/test-env-log


text:
Custom weapons appear to cause incorrect calculations

Adding a custom axe to a character and setting the physical damage range to 1-1 will produce a value of 10-13 weapon damage in the right side. A completely new level 70 profile has 217 mainstat. My expected value would be 1 * 3.17 = 3.17 weapon damage.
Changing the equipped weapon to 100-100 weapon damage range produces a value of 323-327 weapon damage (still with 217 strength). My expected value is 100 * 3.17 = 317 weapon damage.
It looks like planner adds 2-3 weapon damage range as a base value or something similar.

Ah yes, you can't really make custom weapons. You might've noticed that they have no attackspeed and other weapon-specific stats on the tooltip. Setting physical damage to 1-1 effectively adds 1-1 to your unarmed damage, as if you were wearing a piece of jewelry.

I've added custom weapons a while ago, so it should work now.


text:
🛑 Staging Homologation WebSocket is down

In 1079ebc, Staging Homologation WebSocket ($STAGING_HOMOLOGATION_WEBSOCKET) was down:

HTTP code: 503
Response time: 719 ms

Resolved: Staging Homologation WebSocket is back up in d13416e.


text:
Scroll within a section

For the Different Heights feature, when the section is much taller than the viewport height, scrolling down will take you to the next section, cutting off the rest of the text of the current section that lies 'below' the viewport.
It would be an improvement / feature to allow normal scrolling until you reach the bottom of the current section, and then section scrolling will take effect again.

Resolved in ea24834


text:
fp16 winograd

In the paper, you mentioned that the implementation can be ported to  fp16 version.
So, have you succeed in implementing fp16 Winograd with tensor-core and beating the performance of the cudnn.
I found that the cudnn doesn't have fp16 Winograd convolution3x3 but only fp16 gemm convolution3x3. I have no idea why Nvidia doesn't implement one.

Hi.
I have not implemented fused Tensor Core fp16 Winograd yet.
I believe cuDNN's non-fused Winograd leverages Tensor Core.

authors: clarencewxl daadaada

repo: daadaada/turingas


text:
Same road mode

Implements #44
Performance-wise, I don't really see a difference. All tested.

Also closes #45

My bad, i'll try to fix the problems asap

https://github.com/dabreegster/route_snapper/assets/32068559/c4de90d3-bef2-499d-a059-0a98d3ede8d6
this should work now


text:
The benchmark kafka got an 'InvocationTargetException'

My JDK is java 11.0.22 2024-01-16 LTS. I got an 'InvocationTargetException' when I ran Kafka. How can I solve this exception?
`root@a100:/dacapobench/benchmarks# java -jar dacapo-evaluation-git-b281fb21.jar -c ExampleCallback kafka
IMPORTANT NOTICE:  This is NOT a release build of the DaCapo suite.
Since it is not an official release of the DaCapo suite, care must be taken when
using the suite, and any use of the build must be sure to note that it is not an
offical release, and should note the relevant git hash.
Feedback is greatly appreciated.   The preferred mode of feedback is via github.
Please use our github page to create an issue or a pull request.
https://github.com/dacapobench/dacapobench.
Using scaled threading model. 256 processors detected, 256 threads used to drive the workload, in a possible range of [1,unlimited]
Version: kafka 3.3.1 (use -p to print nominal benchmark stats)
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.dacapo.harness.Kafka.prepare(Kafka.java:46)
at org.dacapo.harness.Benchmark.run(Benchmark.java:229)
at org.dacapo.harness.TestHarness.runBenchmark(TestHarness.java:225)
at org.dacapo.harness.TestHarness.main(TestHarness.java:170)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at Harness.main(Harness.java:39)
Caused by: java.lang.ClassNotFoundException: org.apache.zookeeper.server.ZooKeeperServerMain
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:476)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
at org.dacapo.harness.DacapoClassLoader.loadClass(DacapoClassLoader.java:152)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:398)
at org.dacapo.kafka.ZookeeperStarter.(Unknown Source)
at org.dacapo.kafka.Launcher.launching(Unknown Source)
... 13 more`

I'm not sure what's going on here.  Is there a reason you're not using a release build?  I suggest you see if this is issue arrises on a release build before pursing this further.

I have tried to reproduce this, but cannot.  Please feel free to reopen if you have more specific information.
$ java -jar dacapo-evaluation-git-b281fb21.jar -c ExampleCallback kafka
--------------------------------------------------------------------------------
IMPORTANT NOTICE:  This is NOT a release build of the DaCapo suite.
Since it is not an official release of the DaCapo suite, care must be taken when
using the suite, and any use of the build must be sure to note that it is not an
offical release, and should note the relevant git hash.

Feedback is greatly appreciated.   The preferred mode of feedback is via github.
Please use our github page to create an issue or a pull request.
    https://github.com/dacapobench/dacapobench.
--------------------------------------------------------------------------------

Using scaled threading model. 24 processors detected, 24 threads used to drive the workload, in a possible range of [1,unlimited]
Version: kafka 3.3.1 (use -p to print nominal benchmark stats)
Starting Zookeeper...
Starting Kafka Server...
Example callback starting kafka
===== DaCapo evaluation-git-b281fb21 kafka starting =====
Trogdor is running the workload....
Starting 1000000 requests...
100%
Completed requests
Finished
Example callback stopping
===== DaCapo evaluation-git-b281fb21 kafka PASSED in 6683 msec =====
Example callback PASSED kafka, observed 1000000 requests
===== DaCapo processed 1000000 requests in 5284 msec, 189250 requests per second =====
===== DaCapo simple tail latency: 50% 17221 usec, 90% 54859 usec, 99% 329900 usec, 99.9% 339911 usec, 99.99% 342694 usec, max 344178 usec, measured over 1000000 events =====
===== DaCapo metered tail latency: 50% 157837 usec, 90% 313883 usec, 99% 345952 usec, 99.9% 348139 usec, 99.99% 349177 usec, max 349614 usec, measured over 1000000 events =====

repo: dacapobench/dacapobench


text:
🛑 render webhook line notify is down

In 57d06f6, render webhook line notify (https://node-ts-webhook.onrender.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: render webhook line notify is back up in 557c6c3 after 28 minutes.

repo: daddybannk/uptime


text:
DryIoc.Microsoft.DependencyInjection Dependencies

Hey, I'm working on a new asp.net core 2.1 app (I don't want to use 2.2 cuz of missing long term support) and I wanted to check out your nice work at DryIoc 4.0. But I can't use it, because DryIoc.Microsoft.DependencyInjection needs Microsoft.Extensions.DependencyInjection.Abstractions 2.2 which violates the project constraints.

Microsoft.AspNetCore.App 2.1.1 requires Microsoft.Extensions.DependencyInjection.Abstractions (>= 2.1.1 && < 2.2.0) but version Microsoft.Extensions.DependencyInjection.Abstractions 2.2.0 was resolved.

Another problem is, that it seems I can't use .net core 2.2.2x with Visual Studio 2017:
https://stackoverflow.com/questions/53329290/net-core-2-2-cant-be-selected-in-visual-studio-build-framework#answer-55529011
So I don't see any good way to use DryIoc 4.0 in asp.net core 2.1 currently. :(

This is bad. I will try to release 2.1 compat version.

I tested it out out: VS 2019 supports the new .net core version. But no LTS for 2.2. It's kinda like a joke from microsoft.

I am not aware about LTS support, but apperently they're not changing MS.Ext.DI 2.2 version in Asp .Net Core 3. That way DryIoc.MS.DI is kinda ready for v3 without changes.

I switched to VS19 and changed the project SDK to 2.2.2x for my new project.
But I'm not sure if commercial users of VS17 with business or enterprise license can also easily upgrade to VS19 to use DryIoc 4 in asp.net core projects.
I also think that this is a problem for LTS awared users like me: I can't upgrade another project to DryIoc 4 and need to stick to a DryIoc 3 Preview because of performance issues - until core 3.0 LTS comes out.

I have published DryIoc.Microsoft.DependencyInjection.3.0.2.nupkg with direct support for A.NC 2.1.1
Check in a minute.

Hey, thank you! Will check it out later.

I have the same issue.
The DryIoc.Microsoft.DependencyInjection.3.0.2.nupkg  helps for .NETStandard projects.
But for .NETCoreApp the problem is still there.

:( Something tells me that I need to release a specific version (different from the 3.0.2) targeting netcoreapp 2.1, or may be even create a separate package.
But before that could you try to add explicit project reference to MS.DI?
<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="2.1.1" />

I have tried that before. It bubbles up to Microsoft.AspNetCore.Mvc.Core downgrade.
NU1605: Detected package downgrade: Microsoft.Extensions.DependencyInjection.Abstractions from 2.2.0 to 2.1.1. Reference the package directly from the project to select a different version.
.....Tests.netCore -> ......Web.AspNetCore.netCore -> Microsoft.AspNetCore.Mvc.Core 2.2.2 -> Microsoft.Extensions.DependencyInjection 2.2.0 -> Microsoft.Extensions.DependencyInjection.Abstractions (>= 2.2.0)
......Tests.netCore -> Microsoft.Extensions.DependencyInjection.Abstractions (>= 2.1.1)

I have split package in two and published DryIoc.MS.DI v3.0.3 and DryIoc.MS.DI.AspNetCore2_1 v3.0.3

Now nuget update succedded.
Thank you.

authors: Fruchuxs dadhi deathgore

repo: dadhi/DryIoc


text:
PHP Fatal error:  Class 'Pool' not found in /srv/twitchbot/console-cli-thread.php on line 73

Hey there, I've set everything up as described and I'm getting the following error:

PHP Fatal error:  Class 'Pool' not found in /srv/twitchbot/console-cli-thread.php on line 73
Fatal error: Class 'Pool' not found in /srv/twitchbot/console-cli-thread.php on line 73

I can't find the class 'Pool' anywhere, am I missing some not mentioned requirements?

Hi,
sorry it is a very basic alpha release on github. I had not have time to upload the "final" version, which I have currently running.
The readme is also quite old, currently there are missing requirements:

https://github.com/krakjoe/pthreads

authors: TheTimmaeh daeks

repo: daeks/TwitchBot-Console


text:
feat: init first dafiti-group orb

init: start new jobs
fix: erros in lint to deploy
fix: list script issues
fix: include descriptions missing and move complex scripting to script bash file
fix: scripting linter issues
fix: script lint
fix: script lint
fix: script lint
fix: lint script
fix: :zap:
fix: :zap: :ninja:
fix: linters
fix: lint issues
fix: include circleci token to publish
fix: pipelines
fix: linters
:tractor:
chore: general fix
chore: update example comments
chore: update files

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: gritzkoo
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: dft-deploy gritzkoo

repo: dafiti-group/orb-standard-pipeline


text:
Completion is broken

Sometimes, when I edit fish files, I get this error many times:
Error detected while processing function fish#Complete:
line    8:
E484: Can't open file /tmp/vCliDT0/13
Press ENTER or type command to continue

What I did:
vim /tmp/test.fish

iif test -e "/ca

Then this error occurs after every character I type.
I also have vim-mucomplete installed. So vim tries to autocomplete.

Meanwhile I know this issue has nothing to do with vim-mucomplete. This is how to reproduce:
Create a file named ~/.vim/fish-test.vim:
set nocompatible
set runtimepath=$VIMRUNTIME
set runtimepath+=~/.vim/pack/plugins/start/vim-fish
set omnifunc=fish#Complete

Run vim -u ~/.vim/fish-test.vim /tmp/test.fish. Switch to insert mode and type "te. Press Ctrl-x Ctrl-o for autocompletion. This causes the error from my initial post.
I found a similar issue in another plugin:
https://github.com/kristijanhusak/vim-js-file-import/issues/31
Apparently, it has to do with doubles quotes in fish. This patch doesn't fix this issue but at least it occurs less often:
diff --git a/autoload/fish.vim b/autoload/fish.vim
index 2c4d894..199e155 100644
--- a/autoload/fish.vim
+++ b/autoload/fish.vim
@@ -48,9 +48,10 @@ function! fish#Complete(findstart, base)
         if empty(a:base)
             return []
         endif
+        let l:base = substitute(a:base, '"', "'", "")
         let l:results = []
         let l:completions =
-                    \ system('fish -c "complete -C'.shellescape(a:base).'"')
+                    \ system('fish -c "complete -C'.shellescape(l:base).'"')
         let l:cmd = substitute(a:base, '\v\S+$', '', '')
         for l:line in split(l:completions, '\n')
             let l:tokens = split(l:line, '\t')

repo: dag/vim-fish


text:
core git should have keepGitDir option and perhaps depth. Should it be true by default?

I've found it confusing that when I see demos of doing a git pull of the dagger/dagger repo and a dockerbuild that the docker version command run afterwards doesn't show a short git hash in the version number like it does when I git clone and build dagger locally on my machine.
For example:
dagger devel (708210f74) darwin/arm64

dagger devel (708210f74) linux/arm64

{
    core {
        git(remote: "https://github.com/dagger/dagger") {
            dockerbuild(dockerfile: "Dockerfile") {
                exec(input:{args:["dagger", "version"]}) {
                    stdout
                }
            }
        }
    }
}

{
  "data": {
    "core": {
      "git": {
        "dockerbuild": {
          "exec": {
            "stdout": "dagger devel () linux/arm64\n"
          }
        }
      }
    }
  }
}

I expected a git clone type functionality. Not sure if other folks are expecting something else. If the size of the .git directory is a concern, we could use something like git clone --depth=1.
It seems that perhaps the default BuildKit behavior is to not preserve the .git directory (not sure), but I see that this is an option in BuildKit LLB land (depending on things like dockerfile frontends and such I think), and so we should have that option in cloak to keep the .git directory and likely limit the clone depth and other bells and whistles.
https://github.com/dagger/dagger/blob/main/plan/task/gitpull.go#L40-L43
https://github.com/dagger/dagger/blob/main/version/version.go#L16-L30
https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/reference.md#example-keep-git-dir

We have support for including the git dir now. We don't have an option for git depth though

I'm leaning towards keeping the .git dir by default at this point. It seems like we've needed it more than half the time we've used the Git API.

Closing since this is done. If reopening because of making keepGitDir default to true, please update issue or create new one.

authors: helderco jpadams sipsma vito

repo: dagger/dagger


text:
Vanara.PInvoke.User32_Gdi.DISPLAYCONFIG_MODE_INFO has wrong layout

Hi, great work on the library! It's been very helpful to me.
I found a small bug, however. I noticed that QueryDisplayConfig returns invalid display modes because DISPLAYCONFIG_MODE_INFO is missing a union for the actual mode information types (see https://docs.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-displayconfig_mode_info and https://github.com/dahall/Vanara/blob/c45e2ddc4c991d497acd6a949acd64de4cafb6e9/PInvoke/Gdi32/WinGdi.Display.cs#L593).
I've added a pull request for the fix, but I don't have the correct build tools installed to test it. I tried the fix in my own code, though, and it seems to work. If you find it easier to just patch it in yourself then that's fine as well.

Will you try the following in your code to see if it works? I think this is more in keeping with the layout of the union.
/// The DISPLAYCONFIG_MODE_INFO structure contains either source mode or target mode information.
[StructLayout(LayoutKind.Explicit, CharSet = CharSet.Auto, Pack = 4)]
public struct DISPLAYCONFIG_MODE_INFO
{
   ///
   /// A value that indicates whether the <c>DISPLAYCONFIG_MODE_INFO</c> structure represents source or target mode information. If
   /// <c>infoType</c> is DISPLAYCONFIG_MODE_INFO_TYPE_TARGET, the targetMode parameter value contains a valid
   /// DISPLAYCONFIG_TARGET_MODE structure describing the specified target. If <c>infoType</c> is
   /// DISPLAYCONFIG_MODE_INFO_TYPE_SOURCE, the sourceMode parameter value contains a valid DISPLAYCONFIG_SOURCE_MODE structure
   /// describing the specified source.
   ///
   [FieldOffset(0)]
   public DISPLAYCONFIG_MODE_INFO_TYPE infoType;

   /// The source or target identifier on the specified adapter that this path relates to.
   [FieldOffset(4)]
   public uint id;

   /// The identifier of the adapter that this source or target mode information relates to.
   [FieldOffset(8)]
   public ulong adapterId;

   ///
   /// A valid DISPLAYCONFIG_TARGET_MODE structure that describes the specified target only when <c>infoType</c> is DISPLAYCONFIG_MODE_INFO_TYPE_TARGET.
   ///
   [FieldOffset(16)]
   public DISPLAYCONFIG_TARGET_MODE targetMode;

   ///
   /// A valid DISPLAYCONFIG_SOURCE_MODE structure that describes the specified source only when <c>infoType</c> is DISPLAYCONFIG_MODE_INFO_TYPE_SOURCE.
   ///
   [FieldOffset(16)]
   public DISPLAYCONFIG_SOURCE_MODE sourceMode;

   ///
   /// <para>
   /// A DISPLAYCONFIG_DESKTOP_IMAGE_INFO structure that describes information about the desktop image only when <c>infoType</c> is DISPLAYCONFIG_MODE_INFO_TYPE_.
   /// </para>
   /// <para>Supported starting in Windows 10.</para>
   ///
   [FieldOffset(16)]
   public DISPLAYCONFIG_DESKTOP_IMAGE_INFO desktopImageInfo;
}

Yes, this works just as well and it's even a bit nicer to use. I tested it in my own code. Do you want me to update the PR or can you make the change yourself?

I've made the code change here. I'll include in the next release.

Okay, thank you very much!

authors: KeloCube dahall

repo: dahall/Vanara


text:
Changed favicon to dahliaOS logo

Description

Changed favicon to dahliaOS logo

Type of change
Please tick the relevant option by putting an X inside the bracket

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

Checklist:

[x] My code follows the guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] All current GitHub actions pass
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have read the CONTRIBUTING document

thx


text:
Package scheduler is missing in bundle

Seems that scheduler packages should be not used as a peerDependency, coz this can affect other packages
Module not found: Error: Can't resolve 'scheduler' in '...\projectName\node_modules\formik\node_modules\use-context-selector\dist'

https://github.com/formium/formik/pull/2846/files#diff-bb9bd4f1dbd843424d2c07aab952490a2b9c95c6d2474db9a0ee03eed56cfaf1R43
Okay, so formik v3 is trying to use use-context-selector.
They need to add scheduler in their peer dependencies.
We have some discussions about peer dependencies in jotai repo.
It's really annoying and only the solution seems app developers to install peer dependencies explicitly. Note npm7 does it by default.
I don't think adding it in dependencies is not an option, because it might lead having two versions of scheduler which doesn't work at all (like react).

Thanks @yekver for reporting the issue.
Pinning @jaredpalmer. Also notice there is the latest version, which is better (without hacks) in a long term.

authors: dai-shi yekver

repo: dai-shi/use-context-selector


text:
デバッグ出力のon/offを変えられるようにする

大量の端末を検知したときなどブラウザの挙動が重くなることがありうる。
デバッグ出力をon/offできるようにし、初期値をoffにする。

実験で確認出来たので他のツールに適用する

適用出来たのでclose

repo: daisuke-nogami/cocoa-tools


text:
Bump log4j2 version for cve-2021-44228

Addressing vulnerability to remote code execution via log4j2 JNDI lookup: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228

From version 2.16.0, this functionality has been completely removed

This should probably upgrade to 2.17.0 since another release was created to address the DOS issue.

Bumped to 2.17.1 https://logging.apache.org/log4j/2.x/security.html

Merged, thanks!

authors: dakrone eltonlaw

repo: dakrone/clj-http


text:
Merge commits

deny

Rejected it.


text:
Override checks and non-committer flow

Example of overriding failing checks and when the pr gets assigned to a non-committer

There's still some bugs to work out with the processNewPrs apparently 😅 digging into why it keeps pinging after a pr is processed now

Fixed - turns out the bot was running on me deleting its old comments and it was triggering more comments 😢

R: @damccorm for final approval

repo: damccorm/beam-pr-bot-demo


text:
Classy installable

We can begin with the merge, if you are up to it. My work here is almost done :D
What this branch is capable of:

installable version of classy_blocks
automated and reproducible installation of dependencies
pytest test module
continious integration using github action runner on a vanilla ubuntu system

The review should focus on the compatability of classy_examples. How can we make use of the installable version in this repository? I did NOT register the package on pypi, you cant install it with "pip install classy_blocks" (yet). you would need to use pip install git+[https-git-link[ to install the package without cloning the repository and installing from source.
Have a look at the sphynx-documentation probably. We could delete it before the merge. Or you consider using it.
Also focus on the test defined in the pytest-module here. there are two automatically generated tests in there that i don't understand. we might delete them. the test i wrote is also not want you want in the long term as no assert is used. I think this might be a story for another issue and we could leave it like that.  You know yourself better what needs to be tested and how.
consider a version tag "0.1.0" when merged.

I need a little more time, working on this and all the underlying stuff at the moment...
[Please be patient]

Hey MaNyh, although I am not review assignee for this PR, Franz asked me to step in and... well, do my job :)
Although this PR is one of the first things needed to be done with classy blocks also on our (damogran labs) list,
here are a couple of things would do different compared to your PR:

I would use only one main package description file, that is setup.py. That way pkg info is stored in one (and only) place.
TODO: Get rid of setup.cfg. Data like version can go into the package itself in __init__.py or version.py, also easily accessible in programmatic way.
setup.py should list pkg requirements directly, that is: populate install_requires field. requirements.txt should be used for
development and/or test requirements, which are not needed for package to work. This idea comes from here.
TODO: populate setup.py->install_requires field with actual classy_blocks requirement, while move test and development dependencies to requirement files.
Personally, I would also separate development dependencies (example, black formatter) from test dependencies (pytest) to a separate requirements_dev.txt and requirements_test.txt files respectively. That is (almost) done anyway :).
Read procedures (with open()... blocks) of README, HISTORY and other files in setup.py should be performed in a functions, that return that content.
That way no code is executed unless setup() is actually called and IDE tools are not performing anything on import or actions taken on setup.py file, like linting.
TODO: wrap with open()... blocks to a separate functions and execute them once needed, in setup().
Personally, I would remove "test instructions" and test dependencies from setup.py. Package tests - from my point of view - are used in development stage
where entire repository checkout is necessary, while they are not needed by the end user. Detailed instructions and how-to procedures are (should be) available in CONTRIBUTING.rst anyway.
TODO: remove test stuff from setup.py and instead write down how-to contribute in CONTRIBUTING.rst.
Package layout: I would go with /src layout. It is better designed for further package additions (like, adding another tool is just another dir in /src) and better isolate sources from other stuff - maybe one day, there would be a special dir with C/Rust/whatever language source files.
TODO: create src dir on the root and move classy_blocks there. Update setup.py to search packages only in src dir, like here.
MANIFEST.in include a lot of files, which are not really needed by the package end user and shouldn't be part of final distribution. For example, Makefile for documentation generation is not needed by the end user, we have online docs for this purpose.
TODO: cleanup MANIFEST.in document of all dependencies, that are not explicitly required by package itself (that is development, test and other files).
Maybe we don't need anything shipped with wheel, and we don't need Manifest.in at all?!  Is setup.py->zip_safe= setting needed?
Abstract vs pinned dependencies: It is a good practice to use pinned dependencies only where absolutely necessary, and even than, specify range, not exact version. This adds more freedom to end-user environment, where class_blocks might not be the only dependency using jinja2 and one might work on HEAD, instead on 3.1.2.
TODO: use latest and the greatest versions if possible - remove pinned dependencies or add lowest allowed version for any dependency in requirements_*.txt files and in setup.py->install_requires.
Development/test tools should have its own cfg file if possible, for example pytest.ini, black.toml and .pylint. That way it is really obvious how to configure any IDE and, for example, CI actions.
What is Makefile on the root? I am not familiar with this, although I can see what it is doing from the code. Is this something that tox could do (since you already prepared everything, and we would only have one tool)?
It is great you've added GitHub actions to perform per-commit tests. Maybe we should do something similar for classy_examples!
Anyway, I think we should make sure tests are performed on a clean environment with only package and test dependencies installed, and possibly generate some report files, like pip freeze for the times something goes wrong and user inspection is needed.

Overall, this is a great PR. Stuff described above comes from my experiences with packaging and packaging tools from my day job, which are - of course - subjective and might not be the best, but I know for sure some of the points mentioned above bit us before, so why bother repeating them again. :) Feel free to comment and further discuss the ideas!
And of course, thank you for your contribution, it is great!

hey there. i just found your message and want to let you know, that an answer will take approx. 2 weeks. i am currently really busy.
you have a lot of comments and some are not that easy to answer. but i am looking forward for a discussion on all of your comments.

I am happy that you are using my work. But I am not happy with me not resolving the remaining questions.

For next PRs, please make a fork of this repository and then make a PR from your fork.

Sure. I will do that. But i dont understand why this is advantageous. Can you explain?

It is a common workflow - fork, commit, pull request.
I am not sure about the fork. I am mostly working on gitlab, also in a professional context. We don't fork for a PR. Is there any obvious advantage?

What other questions remain?
@schperplata has listed issues and questions about the PR

I am not sure about the fork. I am mostly working on gitlab, also in a professional context. We don't fork for a PR. Is there any obvious advantage?

@MaNyh The reason for that might be that in a professional context you are describing, you might be a part of the repository owners or participant, which is a common practice for internal repositories. However, with a public repositories, PR are done almost exclusively over fork - being part of repository owner/moderator/maintainer also grants you some permissions that can have unwanted side effect on a repository that owner itself should know about it and/or have control over it. That being said, don't feel that it is you only, that this concept apply to - anybody outside of repository/organizator owner should do it that way.
About other points of my review: feel free to open a discussion (here) about anything you feel needs to be discused. In any case, certain points will for sure be done as proposed as I happen to have some (bad and good) experiences with current implementation and these things are best solved as fast as possible. One such example is package layout and where and how dependencies are written.
Thank you again, I think we will create a great package, or at least, perform our packaging kung-fu :)

Thanks to you both for your explanations! It's a good idea to avoid granting write permissions and now the process makes sense to me.

authors: FranzBangar MaNyh schperplata


text:
Failed to launch chrome buecause Running as root without --no-sandbox

Saving as PDF
(node:24806) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!
[1012/081529.390835:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.

TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
at onClose (/usr/lib/node_modules/percollate/node_modules/puppeteer/lib/Launcher.js:339:14)
at Interface.helper.addEventListener (/usr/lib/node_modules/percollate/node_modules/puppeteer/lib/Launcher.js:328:50)
at emitNone (events.js:111:20)
at Interface.emit (events.js:208:7)
at Interface.close (readline.js:368:8)
at Socket.onend (readline.js:147:10)
at emitNone (events.js:111:20)
at Socket.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1064:12)
at _combinedTickCallback (internal/process/next_tick.js:139:11)

(node:24806) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:24806) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I've added support for the --no-sandbox flag in percollate@0.2.7, let me know if it solves your  issue!

authors: danburzo mengyyy

repo: danburzo/percollate


text:
updates for 0.7

Summary of changes (purescript 0.7 migration guide)
Dependencies

All bower dependencies updated for 0.7 compatibility
Express updated: 4.11 -> 4.13

Language

No more implicit prelude import: import Prelude added to files
[a] syntax for array types replaced with Array a
Debug.Trace.trace replaced with Control.Monad.Eff.Console.log
Number type replaced with Int where appropriate (status code)
Inline FFI javascript definitions no longer allowed: moved to separate .js files (with same name as .purs file)
Infix operators in instance definitions replaced with function names
Cons pattern matching (x : xs) removed; replaced with folds or other functions (QueryString.purs)
Also in QueryString.purs, Text.Parsing.Parser api was modified slightly

Build system
Biggest change was to the build system. grunt-purescript no longer works with purescript 0.7 (and looks unlikely that it will be updated soon). I haven't taken a dependency on another build tool but have instead written build scripts in package.json that use the native purescript compiler tools:

npm install: install all bower & npm dependencies and build the project
npm run build: builds package & creates docs
npm test: builds, creates docs and builds & runs tests
npm run build-examples: builds package and all examples (examples are output to "./output/examples/" I also had to modify the namespaces in the examples to make this work)

Some warnings come up during build, these are from dependencies and don't do any harm.
These build scripts work fine, but using pulp for building might be something to consider (a lot of other purescript packages have moved to pulp). Unline grunt & gulp, pulp requires no extra dependencies to be installed with the package nor config files written; it just needs to be installed as a global npm package on your machine.

I forgot about travis. Thought i'd fixed it but the travis build's still failing because it's looking for grunt (which is no longer there)

To fix Travis, you need to update .travis.yml with new build and test commands.

Ok thanks, I've made the changes to maxAge and to the travis build

This looks great. :shipit:

@stkb I tried this out in my 0.7 project and everything worked flawlessly. Upgrade was painless.
@dancingrobot84 I think this is good to go.

@michaelficarra Good to hear; thanks for the endorsement!

This one is a nice work. Thank you very much! As soon as some minor flaws are fixed I will accept your PR.

Ok, have

moved purescript-console to devDependencies
removed comment in EmbedApp.purs

and squashed the commits.

Great! Thank you.

Thanks!

authors: dancingrobot84 michaelficarra stkb


text:
Blog Post Showcasing Data Reuse

This PR adds a blog post showcasing data reuse for Dandiset #000458

@yarikoptic, thanks for the feedback!

we just merged

https://github.com/dandi/dandi.github.io/pull/75
so if you merge or rebase, you could take advantage of pre-commit ;)

@yarikoptic, this should be ready to publish now!

Let's proceed then. Thank you @pauladkisson and @bendichter !

i directly edited the filename, but all blog posts need to have a date at the beginning of the filename.

authors: pauladkisson satra yarikoptic


text:
Use the Comment#generated_by_danger? method #trivial

Reduces knowledge about that particular string in the codebase

          1 Warning

:warning:
Tests were not updated

  Generated by :no_entry_sign: Danger

Cool, makes sense to me :+1:

authors: DangerCI hanneskaeufler orta

repo: danger/danger


text:
MudCalendar not displaying properly.

I'm new to MudCalendar so this could be a configuration error on my part.
With that in mind, I have installed the Heron.MudCalendar 2.0.0 into my project via Nuget.
I have added...
@using Heron.MudCalendar
to my _Imports.razor file.
I have also added (after the calendar was not displaying properly)...
<link href="_content/Heron.MudCalendar/Heron.MudCalendar.min.css" rel="stylesheet" />
and

to index.html in my WASM Client www folder.
I am using Chrome Version 126.0.6478.127 (Official Build) (64-bit).
Here is a snapshot of my page.
To get started, I have only included <MudCalendar /> to the page.
@
I have noticed that the Heron.MudCalendar.min.js file does get automatically injected without the

in index.html. However, I must include
<link href="_content/Heron.MudCalendar/Heron.MudCalendar.min.css" rel="stylesheet" />
in index.html because the Heron.MudCalendar.min.css file does not get automatically injected.
Any help would be much appreciated.

Here is a completer copy of my index.html file...
`

eBailiff.Client

    An unhandled error has occurred.
    Reload
    🗙

`

Here is my TestCalendar.razor file...
@page "/TestCalendar"
<MudCalendar />

It looks like the CSS file is not being loaded.  The link you have added to Heron.MudCalendar.min.css is correct.
However it looks like you are creating a PWA.  Is it possible it's loading an offline version that was downloaded before you added the link?

Thanks Dan. That was the issue. Everything looks good. Now off to find a solution that will cache bust the PWA.

authors: TSMarcus danheron


text:
"Close Current" option does not work in new version

Thank you for the extension.
I upgraded to the new version and "close current" option stopped working.
Environment:

OS: Windows 7 SP1
Atom: 1.10.2
Atom-Project-Manager: 3.2.1

Let me know if you need more info.

It has been replace with either using shift+enter in the projects list or by setting Always Open In Same Window to true.

I'm not following. I would expect it to close the current instance of atom if I'm not using "shift+enter" and have set the following options
Close Current - Enabled
Always open in Same Window - Disabled

authors: danielbrodin modulexcite

repo: danielbrodin/atom-project-manager


text:
Fix Setup Script

Make it possible to run command from any directory that starts sample app.

Fixed! Closing issue.

authors: DerekPena danielcasto

repo: danielcasto/AIRPrediction


text:
Error in mobx strict mode

I am getting following error while using promiseComputed inside mobx project with strict mode enabled.
promisedComputed.js:26 Uncaught Error: [mobx] Since strict-mode is enabled, changing observed observable values outside actions is not allowed. Please wrap the code in an `action` if this change is intended. Tried to modify: PromisedComputed@121.refreshCallCount
    at invariant (mobx.module.js:148)
    at fail (mobx.module.js:143)
    at checkIfStateModificationsAreAllowed (mobx.module.js:1186)
    at ObservableValue.prepareNewValue (mobx.module.js:793)
    at ObservableObjectAdministration.write (mobx.module.js:3956)
    at PromisedComputed.set [as refreshCallCount] (mobx.module.js:4179)
    at PromisedComputed.set [as refreshCallCount] (mobx.module.js:369)
    at new PromisedComputed (promisedComputed.js:26)
    at promisedComputed (promisedComputed.js:109)
    at asyncComputed (asyncComputed.js:28)

Enabled flag is
configure({ enforceActions: 'always' });

Mobx Versions:
"mobx": "^5.8.0",
"mobx-react": "^5.4.3",
"mobx-react-lite": "^1.4.1"

Thanks for reporting this. This library doesn't currently support 'always' mode. Referring to https://github.com/mobxjs/mobx/issues/1473 when the multiple levels of checking were added, there is:

'never' (false)
'observed' (true)
'always'

The first two work, but the last does not. I hadn't noticed this because I never use that mode (it stops you initialising observable fields in constructors etc.)
I will take a look at what is required to enable this library to work in 'always' mode.

The new version 4.2.0 is tested against 'always' mode.

authors: danielearwicker thecodejack

repo: danielearwicker/computed-async-mobx


text:
How to pull?

How to pull?

???

Not Osiris problem, close the issue.

authors: Cyk-Fad Sapphire1337420 hyperxpro

repo: danielkrupinski/Osiris


text:
Angry hackers best config

hvh

i dont get it what do u mean?

he means rage cfg

u can try this
https://anonfiles.com/J901p1Mfo0/rage_as_fuck
old osiris cfg

Title makes me laugh hard

Air out of nose

https://anonfiles.com/91cdOfM5o3/HVH
What does he need to improve?

authors: A1gaoshanlaiyige EzekielCloud aljawary newcommerdontblame notgoodusename


text:
suggestion

maybe a dead esp would be gud to have

Do you mean dead bodies?

No like when u die u see the esp


text:
Only allows the use of 1 steam instance at a time

I'm trying to use this for multiple instances. The problem is that if I open a second steam instance (Even if it is sandboxed using avast sandbox) it automatically closes if I already have an instance with VAC bypass enabled. Hopefully there is a fix for this. I also tried the other repo of Vac-Bypass-Loader and that also closes existing steam instances, even if they are sandboxed.
Thanks

Use sandboxie, it allows vac bypass, just create how many sandbox you want, and open vac bypass in each one .
https://sandboxie-plus.com/downloads/ ive been using since march for operation broken fang farm.
you can check is open source, tottaly legit

I second this

repo: danielkrupinski/VAC-Bypass


text:
Update README.md

Fix broken link.

Fixed, thank you!

authors: danielmiessler iqbalabd

repo: danielmiessler/fabric


text:
🛑 Bancolombia - Portal is down

In c521621, Bancolombia - Portal (https://www.bancolombia.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bancolombia - Portal is back up in a199692 after 15 minutes.

repo: danielqb/status


text:
g-drive sync missing from repo

I'd really like to use the gsync back up for hassio but it's missing from the repo

Well, it doesn’t work.

authors: danielwelch smashah

repo: danielwelch/hassio-addons


text:
Unable to change output format in 1.14.3

I'm trying to configure zigbee2mqtt with the following config field:
experimental:
  output: 'attribute_and_json'

but seems like it does not work, and i've got the message in the supervisor logs:
20-04-18 01:31:57 WARNING (MainThread) [supervisor.addons.validate] Unknown options experimental

I am using HassOS 4.12 and addon version 1.14.3

@mozoh can you please post your add-on config?

data_path: /config/zigbee2mqtt
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: mqtt
  password: my mqtt password
serial:
  port: /dev/ttyACM1
advanced:
  pan_id: 6754
  channel: 11
  network_key: my network key
  availability_blacklist: []
ban: []
whitelist: []
queue: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false
experimental:
  output: attribute_and_json

According to (docs)[https://www.zigbee2mqtt.io/information/configuration.html] you should have:
experimental:
  output: 'json'

Please read the docs more careful:
# Optional: experimental options
experimental:
  # Optional: MQTT output type: json, attribute or attribute_and_json (default: shown below)
  # Examples when 'state' of a device is published
  # json: topic: 'zigbee2mqtt/my_bulb' payload '{"state": "ON"}'
  # attribute: topic 'zigbee2mqtt/my_bulb/state' payload 'ON"
  # attribute_and_json: both json and attribute (see above)
  output: 'json'

I need to use exactly attribute_and_json

You need to use ' around your value like:
experimental:
  output: 'attribute_and_json'

Also keep in mind that this repository is for zigbee2mqtt home assistant addon. The settings discussed and considering you're changing the actual yaml hint that you should be adressing such issues in http://github.com/koenkk/zigbee2mqtt

But hassio automatically removes '' on config save.
Btw, the issue is:
20-04-18 01:31:57 WARNING (MainThread) [supervisor.addons.validate] Unknown options experimental

and not the even output field

Ok, I tested this out and it seems the problem is missing support for output inside experimental. See: https://github.com/danielwelch/hassio-zigbee2mqtt/blob/master/zigbee2mqtt/config.json#L146
There must have been something wrong in your config because the error should have been:
20-09-17 13:34:04 WARNING (MainThread) [supervisor.addons.validate] Unknown options output
This requires a PR to fix.

I've added https://github.com/danielwelch/hassio-zigbee2mqtt/pull/389 to support this.

closed by #389, please re-open if still having issues.

authors: ciotlosm danielwelch mozoh


text:
basis functions

npivreg should

allow for argument that selects which basis to use ("B-spline", "polynomial", ...)
use separate function for generating basis depending on above argument (generate the P,Q matrices)
allow for user to specify degree of polynomials, number of knots

Now users can specify the number of knots and the power for basis functions. If those options left unspecified, then default setting runs.

cubic B-spline  for both bases should be default

authors: beelzeb danielwilhelm

repo: danielwilhelm/STATA-NPIV


text:
add --import work

This should read csv files, as produced by --export.
Once this is done, I can start using this app in trial work ... i.e. I can taste the dogfood.

I renamed, as follows; tests indicate that this works OK
diary --writeCSV > ~/diary.csv
diary --database ~/new.db --readCSV ~/diary.csv

repo: dankelley/diary


text:
Add mainDish.html

This webpage will be populated with all the filipino main dish recipes from my family: Adobo, dinuguan, etc... each recipe needs their own website.

DONE

repo: dannisse/KainNa