fix for newer Unity versions

Hello, thank you for your feedback. The changes introduced in https://github.com/steve3003/unity-profiler-data-exporter/commit/0c9f20437479283e215a513f7c371b25b55018c0 were automatically created by the Unity API Updater. However, your proposal is definitely cleaner.
I tried the second change you requested. Unfortunately, this doesn't fix the problem I had initially. With Unity 2018.1.8f1 and your suggestions I get the following errors:
NullReferenceException: Object reference not set to an instance of an object
ProfilerDataExporter.GUIClip..cctor () (at Assets/Editors/UnityWrappers/GUIClip.cs:14)
Rethrow as TypeInitializationException: An exception was thrown by the type initializer for ProfilerDataExporter.GUIClip
ProfilerDataExporter.TableGUILayout.AddRow (ITableState tableState, Int32 rowIndex, IEnumerable`1 values) (at Assets/Editors/Utils/TableGUILayout.cs:44)
ProfilerDataExporter.ProfilerDataExporter.DrawStats () (at Assets/Editors/ProfilerDataExporter.cs:104)
ProfilerDataExporter.ProfilerDataExporter.OnGUI () (at Assets/Editors/ProfilerDataExporter.cs:71)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
 Make sure they are balanced)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Unfortunately, my C# and Unity API knowledge is too limited to understand the error.

Hello fabolhak, I see the issue.
In Unity 2018.1.8f1 GUIClip.visibleRect is public but in 2018.2 is internal.
Your solution works in both cases but I tested mine only in 2018.2.
The only issue with yours is that allocates memory every time get visibleRect is called because is creating a delegate every time.
I'll merge your changes and then move what you have done in a static initializer.
Thanks for the help!


redux-thunk not waiting for my promise to be fulfilled

I have the following setup following your examples for chaining async actions:
// final action
function finalAction (status) {
  return {
    type: 'AUTH_STATUS'
    , status
}

// thunk action
function thunkAction () {
  return (dispatch, getState) => {
    return getStatusApi()
    .then((status) => {
      return dispatch(finalAction(status))
    })
    .catch((err) => {
      return dispatch({type: 'AUTH_ERROR'})
    })
  }
}

// api function returning another promise
function getStatusApi () {
  return myAsyncApiCall().then((res) => {
    return res.status
  })
}

// dispatch
store.dispatch(thunkAction())
.then(() => {
  // the end
})

What happens is that the flow is like this:
store.dispatch
thunkAction
getStatusApi
end
myAsyncApiCall
finalAction
reducer

For one reason or another store.dispatch resolves before myAsyncApiCall is resolved.
I either receive then a TypeError or if wrapping the whole into a promise an undefined action error.
Any idea?

I tested now with latest versions and severals actions and I always receive the following type of error if wrapped in a promise:
app/login-page.component: {"stack":"Error: Actions may not have an undefined "type" property. Have you misspelled a constant?
at dispatch (http://localhost:9000/dist/lib/redux.js:305:14)
at http://localhost:9000/dist/lib/redux-logger.js:172:29
at http://localhost:9000/dist/lib/redux-thunk.js:9:74
at dispatch (http://localhost:9000/dist/lib/redux.js:510:19)
at http://localhost:9000/dist/app/store/actions/usage.actions.js:35:20
at Object.dispatch (http://localhost:9000/dist/lib/redux-thunk.js:9:45)
at StoreService.dispatch (http://localhost:9000/dist/app/store/store.service.js:23:21)
at LoginPageComponent._navigate (http://localhost:9000/dist/app/main/login-page.component.js:145:28)
at LoginPageComponent._determineNavigationTarget (http://localhost:9000/dist/app/main/login-page.component.js:141:25)
at http://localhost:9000/dist/app/main/login-page.component.js:99:30","message":"Actions may not have an undefined "type" property. Have you misspelled a constant?","name":"Error","logData":"login"}

If I reorganise my flow into resolving the promise first and then calling a normal non-async action it works perfectly fine. I do not make any modifications getStatusApi by doing this. So I have absolutely no idea what causes these errors (Angular2, zone.js, core.js, redux-thunk, ...)?

I'm having the same issue since upgrading to React Native 0.19

I'm having the same problem with async actions.
// actionCreator
export function asyncAction () {
  return dispatch => api().then(data => data.id)
}

// component
dispatch(asyncAction()).then(() => console.log('done'));
// => Cannot read property 'then' of undefined

The library code has not changed since its initial release.
Please post a complete project reproducing the problem.
At this point my only guess is you might be using the new store creation API where middleware is the last argument, but have not upgraded to Redux >= 3.1.0 which is when this API was added.
I have two guesses why this might be happening.

Are you using the new API without updating to Redux 3.1.0?

// Note: this API requires<EMAIL_ADDRESS>const store = createStore(
  rootReducer,
  applyMiddleware(thunk)
);

Before 3.1.0, you had to do this:
const createStoreWithMiddleware = applyMiddleware(thunk)(createStore)
const store = createStoreWithMiddleware(rootReducer);

Are you using any store enhancers that have not updated to pass the underlying enhancer?

If you are using the new API I mentioned above, make sure you are not using any store enhancers that are not yet compatible with it. We should have addressed this better—I still plan to send PRs to popular store enhancers to allow this API.
For example, Redux DevTools must be >= 3.0.2 to use the new store creation API. Example of how that change looks like for the enhancers: https://github.com/rackt/redux/pull/1302.
My suggestion would be to file a bug against any enhancers that you use if they don’t pass the last parameter to the underlying createStore.
In the meantime, the fix would be to use the old API if you use any enhancers that don’t support the new API yet.

My second suggestion is incorrect. Existing store enhancers should work fine as long as you don’t mix the new and the old styles of applying them.
So this is potentially problematic (depending on whether the store enhancer has been updates to match 3.1 API):
const finalCreateStore = someStoreEnhancer()(createStore)
const store = finalCreateStore(reducer, applyMiddleware(thunk))

If you have code like this, either convert it fully to the old style:
const finalCreateStore = compose(
  someStoreEnhancer(),
  applyMiddleware(thunk)
)(createStore)
const store = finalCreateStore(reducer)

or to the new style:
const store = createStore(
  reducer,
  compose(
    someStoreEnhancer(),
    applyMiddleware(thunk)
  )
)

Just make sure you don't mix these styles.

In any case, there is nothing further I can do to help unless you post a complete project reproducing the issue.

@gaearon here is a plunker demonstrating the effect:
http://plnkr.co/edit/fpOYFDr2mgO2vuohWuZ2
(TypeError: Cannot read property 'then' of undefined)
The error is thrown before the promise is fulfilled. If you wrap the dispatch in a promise Promise.resolve().then... you can also follow the logging in the console.

I also tried wrapping the various parts of the async thunk into zone.bind() but it doesn't help. If you rearrange the setup, first do async then call a non-async action it works fine.

@gaearon and another plunker not involving Angular at all:
https://plnkr.co/edit/66hXPwHRi27Esp5tT79o
It doesn't throw but still then is called before the async actions resolves.

In your second example:
      return setTimeout(() => {
        console.log('save-async-resolved')
        return dispatch(_save(name))
      }, 2000)

setTimeout does not return a Promise. It returns a timeout ID.
Therefore the returned promise is just a resolved Promise with the result equal to the timeout ID.
You don’t wait for the timeout, so it is resolved immediately.
To fix this, you want to create a Promise-friendly wrapper for timeout. For example:
function delay(ms) {
  return new Promise(resolve => setTimeout(resolve, ms))
}

// later
      return delay(2000).then(() => {
        console.log('save-async-resolved')
        return dispatch(_save(name))
      })

The problem with the first example is exactly the same: the mistaken assumption that setTimeout returns a Promise.
Finally, note that Redux Thunk does not require you to use Promises. Thunk dispatches will return whatever you return from thunks. But Promises are usually handy so we suggest using them. Just make sure you actually return Promises and not something else.

In my real app I don't use setTimeout but a promise. I will update my plunker and come back to you.

Please provide the exact example that fails. People spend time helping reproduce issues, so it is essential that you provide the exact code that fails rather than an approximation that fails for a different reason. Thank you!

Sorry, my fault. Am new to all of this. I updated my plunks:
non-angular (works fine!): https://plnkr.co/edit/66hXPwHRi27Esp5tT79o
angular (fails): http://plnkr.co/edit/KP3xZVH9GIdglZJLZrlb

@alexanderharm
Thank you very much for the complete example. In your code, StoreService wraps the Redux store. However, it does not return the dispatch() return value from its own dispatch() method:
  dispatch (action): any {
    this._store.dispatch(action)
    // should have been:
    // return this._store.dispatch(action)
  }

This is why store.dispatch() returns undefined for you. Therefore, this:
    .then((res) => {
      return this._storeService.dispatch(this._nameActions.save('Redux'))
    })

does not actually wait for the async action to finish, and the promise immediately resolves.
Be careful to always return Promises if you want to wait for them :wink:

@nicohvi If you have this problem, please also post the full example reproducing it. It’s hard to say at which point return value got lost for you. It could be due to a middleware that forgets to return it, a bad middleware configuration, etc.

Damn it, I copied this from https://github.com/jhades/angular2-redux-store because I thought he would knew. I will drop him a note. Thanks a million!

Easy to overlook if they didn’t use async middleware yet. Thank you for bringing this up!

It was a faulty store setup @gaearon, thank you very much for pointing me in the right direction :+1:

To add to @gaearon's example, per the createStore api documentation:
// Works only with redux >= 3.1.0
let initialState = {};
const store = createStore(
  reducer,
  initialState,
  compose(
    someStoreEnhancer(),
    applyMiddleware(thunk)
  )
)

This got me a little tripped up, so I hope it helps someone else.

@petermikitsh Thanks for the help but when I do that I get an error:
TypeError: (0 , _store2.default) is not a function
This is my code:
let initialState = {
	recipeSearch: '',
	recipes: [],
	recipeChked: [],
	viewRecipes: [],
	viewIngredients: []
}

const store = createStore(
  reducer,
  initialState,
  compose(
    applyMiddleware(thunk, logger())
  )
)

export default store

is compose needed anymore? the docs don't mention it.
thanks.


chore: to_lowercase -> to_lowercase_cow

Summary

Test Plan

@dyc3 There are still places which are cannot easily migrated to Cow version. For now I just want to see if there is any perf improvement.
I will likely finish migrating/enforcing with separate PR.


New FftInputs trait

This PR partly addresses #93. It introduces a FftInput trait in the maths crate, which defines the shape of the input for the FFT computation. This trait is implemented on [E]in this PR.

This PR has been broken down further into 3 new PRs. The first PR(current one) introduces the FftInput trait in serial.rs expect for evaluate_poly_with_offset.

Thanks @irakliyk for the review. Benchmark runs show that f64/fft_interpolate_poly/simple/1048576 has
dropped by ~2.5%, whereas the rest all seem to be at the same the performance level.

@irakliyk Thanks for the review! I did a benchmark analysis(this PR vs Main) on a Macbook Pro with M1 chip.
f64/fft_evaluate_poly/simple/262144
                        time:   [5.2651 ms 5.2752 ms 5.2851 ms]
                        change: [-2.0300% -1.7274% -1.4336%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild
f64/fft_evaluate_poly/simple/524288
                        time:   [11.131 ms 11.144 ms 11.153 ms]
                        change: [-3.4868% -2.3287% -1.2115%] (p = 0.00 < 0.05)
                        Performance has improved.
f64/fft_evaluate_poly/simple/1048576
                        time:   [23.450 ms 23.481 ms 23.495 ms]
                        change: [-3.8105% -2.6461% -1.5983%] (p = 0.00 < 0.05)
                        Performance has improved.
f64/fft_evaluate_poly/with_offset/262144
                        time:   [5.7104 ms 5.7136 ms 5.7150 ms]
                        change: [-3.9474% -3.2772% -2.5663%] (p = 0.00 < 0.05)
                        Performance has improved.
f64/fft_evaluate_poly/with_offset/524288
                        time:   [11.916 ms 11.926 ms 11.935 ms]
                        change: [-1.2804% -0.6625% -0.1137%] (p = 0.03 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild
f64/fft_evaluate_poly/with_offset/1048576
                        time:   [24.904 ms 24.910 ms 24.913 ms]
                        change: [-0.7624% -0.5275% -0.3145%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 2 outliers among 10 measurements (20.00%)
  1 (10.00%) low severe
  1 (10.00%) low mild

f64_quad/fft_evaluate_poly/simple/262144
                        time:   [8.1970 ms 8.2128 ms 8.2233 ms]
                        change: [-0.2712% +0.1428% +0.5941%] (p = 0.54 > 0.05)
                        No change in performance detected.
f64_quad/fft_evaluate_poly/simple/524288
                        time:   [17.144 ms 17.158 ms 17.166 ms]
                        change: [-2.9753% -1.6194% -0.5066%] (p = 0.01 < 0.05)
                        Change within noise threshold.
f64_quad/fft_evaluate_poly/simple/1048576
                        time:   [36.466 ms 36.507 ms 36.524 ms]
                        change: [-2.7131% -1.8831% -1.0936%] (p = 0.00 < 0.05)
                        Performance has improved.
f64_quad/fft_evaluate_poly/with_offset/262144
                        time:   [8.1432 ms 8.1475 ms 8.1499 ms]
                        change: [-2.9101% -2.1345% -1.4438%] (p = 0.00 < 0.05)
                        Performance has improved.
f64_quad/fft_evaluate_poly/with_offset/524288
                        time:   [17.079 ms 17.095 ms 17.106 ms]
                        change: [-0.1825% +0.0339% +0.2405%] (p = 0.77 > 0.05)
                        No change in performance detected.
f64_quad/fft_evaluate_poly/with_offset/1048576
                        time:   [36.127 ms 36.137 ms 36.143 ms]
                        change: [-0.5137% -0.2235% +0.0047%] (p = 0.13 > 0.05)
                        No change in performance detected.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) low severe

f64_cube/fft_evaluate_poly/simple/262144
                        time:   [11.248 ms 11.266 ms 11.278 ms]
                        change: [-4.0939% -3.0034% -1.7962%] (p = 0.00 < 0.05)
                        Performance has improved.
f64_cube/fft_evaluate_poly/simple/524288
                        time:   [23.778 ms 23.803 ms 23.820 ms]
                        change: [-3.1312% -1.9150% -0.6785%] (p = 0.01 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) low mild
f64_cube/fft_evaluate_poly/simple/1048576
                        time:   [49.413 ms 49.537 ms 49.694 ms]
                        change: [+0.5457% +1.1376% +1.7086%] (p = 0.00 < 0.05)
                        Change within noise threshold.
f64_cube/fft_evaluate_poly/with_offset/262144
                        time:   [11.423 ms 11.708 ms 11.875 ms]
                        change: [+1.5217% +3.2481% +5.2445%] (p = 0.00 < 0.05)
                        Performance has regressed.
f64_cube/fft_evaluate_poly/with_offset/524288
                        time:   [23.256 ms 23.310 ms 23.406 ms]
                        change: [-0.0482% +0.6838% +1.2725%] (p = 0.06 > 0.05)
                        No change in performance detected.
Found 3 outliers among 10 measurements (30.00%)
  1 (10.00%) low severe
  1 (10.00%) low mild
  1 (10.00%) high severe
f64_cube/fft_evaluate_poly/with_offset/1048576
                        time:   [48.939 ms 49.095 ms 49.275 ms]
                        change: [-2.6747% -1.5169% -0.2587%] (p = 0.04 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) low mild

f64/fft_interpolate_poly/simple/262144
                        time:   [5.4510 ms 5.4724 ms 5.5139 ms]
                        change: [-0.3636% +0.3893% +1.3029%] (p = 0.41 > 0.05)
                        No change in performance detected.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild
f64/fft_interpolate_poly/simple/524288
                        time:   [11.786 ms 11.981 ms 12.091 ms]
                        change: [+0.1043% +1.6921% +3.4173%] (p = 0.06 > 0.05)
                        No change in performance detected.
f64/fft_interpolate_poly/simple/1048576
                        time:   [24.381 ms 24.553 ms 24.719 ms]
                        change: [+0.8572% +1.5401% +2.1405%] (p = 0.00 < 0.05)
                        Change within noise threshold.
f64/fft_interpolate_poly/with_offset/262144
                        time:   [6.3199 ms 6.4513 ms 6.6823 ms]
                        change: [+0.8724% +2.5547% +5.1051%] (p = 0.02 < 0.05)
                        Change within noise threshold.
Found 2 outliers among 10 measurements (20.00%)
  1 (10.00%) high mild
  1 (10.00%) high severe
f64/fft_interpolate_poly/with_offset/524288
                        time:   [13.217 ms 13.351 ms 13.526 ms]
                        change: [+1.0659% +1.8573% +2.8208%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild
f64/fft_interpolate_poly/with_offset/1048576
                        time:   [27.683 ms 27.927 ms 28.246 ms]
                        change: [+2.4457% +3.8879% +5.3281%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild

fft_get_twiddles/262144 time:   [1.8241 ms 1.8379 ms 1.8446 ms]
                        change: [-0.0129% +0.5954% +1.2336%] (p = 0.09 > 0.05)
                        No change in performance detected.
fft_get_twiddles/524288 time:   [3.7273 ms 3.7544 ms 3.7771 ms]
                        change: [+0.4761% +1.7563% +3.0816%] (p = 0.01 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild
fft_get_twiddles/1048576
                        time:   [7.4698 ms 7.5297 ms 7.5925 ms]
                        change: [+1.1288% +1.8560% +2.7234%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 1 outliers among 10 measurements (10.00%)
  1 (10.00%) high mild


Controller public override void OnActionExecuting() Order should not be int.MinValue;

In DefaultApplicationModelProvider  you set the delegating filter. The source for ControllerActionFilter sets  public int Order { get; set; } = int.MinValue; putting it closest to the action. The comment "Controller-filter methods run farthest from the action by default." makes me think you meant to set it to int.MaxValue;
The problem with setting it to int.MinValue; , I can't get my action level filter SampleActionFilter to run before  public override Task OnActionExecutionAsync
public class Test3Controller : Controller
{
    [SampleActionFilter(Order = int.MinValue)]
    public IActionResult FilterTest2()
    {
        var m = MethodBase.GetCurrentMethod();
        MyDebug.Write(m, HttpContext.Request.Path);
        return Content(m.ReflectedType.Name + "." + m.Name);
    }

    public override Task OnActionExecutionAsync(ActionExecutingContext context,
                                                ActionExecutionDelegate next)
    {
        MyDebug.Write(MethodBase.GetCurrentMethod(), HttpContext.Request.Path);
        return base.OnActionExecutionAsync(context, next);
    }

}

I'm forced to move the filter to class scope if I want SampleActionFilter to run first:
[SampleActionFilter(Order = int.MinValue)]
public class Test3Controller : Controller

I think ControllerActionFilter should set  public int Order { get; set; } = 0;
for maximum flexibility.
I realize this would be a breaking change.  Is there any way to set the order on controller filter overrides so I can make public override Task OnActionExecutionAsync or public override void OnActionExecuting( run after filters applied to a method?

The comment "Controller-filter methods run farthest from the action by default." makes me think you meant to set it to int.MaxValue;

The order is correct, setting it to int.MinValue means it always runs first i.e. before any other filter and furthest from the action.


Prevent update pull refs manually

All refs under refs/pull should only be changed from Gitea inside but not by pushing from outside of Gitea.
This PR will prevent the pull refs update but allow other refs to be updated on the same pushing with --mirror operations.
The main changes are to add checks on update hook but not pre-receive because update will be invoked by every ref but pre-receive will revert all changes once one ref update fails.

If a repository contains open pull requests, executing git push --mirror will result in an error. This behavior seems somewhat unreasonable to me.

There are other ref "types", eg: IsRemote, and there will be more in the future (there is a comment TODO: /refs/for-review for suggest change interface)
Ideally, I think the switch/default block should be changed:

If a ref "type" is recognized (eg: branch, tag agit-for), then handle it.
Otherwise, skip it

If it is impossible to skip, then stop the push, just like what the PR did in the first commit

I need to clarify there are two kinds of skips here. One is just executed and don't return error. another is don't execute it and don't return error.

ps: just realized that this logic is in "pre-receive" hook , no idea whether it is possible to only skip some branches. If it is impossible to skip, then maybe the only choice is to "stop the loop" (just like what the PR did in the first commit).

If a repository contains open pull requests, executing git push --mirror will result in an error. This behavior seems somewhat unreasonable to me.

I think now it should resolve your problem. Although you will get some errors but that will not affect other refs update. Currently I don't know how to let git ignore those error informations.

ps: just realized that this logic is in "pre-receive" hook , no idea whether it is possible to only skip some branches. If it is impossible to skip, then maybe the only choice is to "stop the loop" (just like what the PR did in the first commit).

I changed it to update hook. I think it should be OK now.

suggest add some test code.

Tests added.

Please fire a new issue to report it.


Update cats-core, cats-laws to 2.5.0

Updates

org.typelevel:cats-core
org.typelevel:cats-laws

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

Files still referring to the old version number
The following files still refer to the old version number (2.4.2).
You might want to review and update them manually.
project/plugins.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-minor, old-version-remains

Codecov Report

Merging #1701 (91fffaf) into master (1157e4a) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1701      +/-   ##
==========================================
- Coverage   86.95%   86.78%   -0.17%
==========================================
  Files          59       59
  Lines        2392     2392
  Branches      142      136       -6
==========================================
- Hits         2080     2076       -4
- Misses        312      316       +4

Impacted Files
Coverage Δ

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0.00%> (-2.71%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
86.54% <0.00%> (-1.17%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.60% <0.00%> (-0.27%)
:arrow_down:

Continue to review full report at Codecov.

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


Add Andrew to LICENSE file

It seems like @Flumble is missing too, and things like this can be added directly, not worth a PR.

Put in master as 8ecb40422a7b6ab80182ce254b91dd67f806a037, closing.


RpmUpload.java:33-50: Finish implementation of RpmUpload...

The puzzle 162-efa52435 from #162 has to be resolved:
https://github.com/artipie/rpm-adapter/blob/16abd083878c0dbffbadebf27343c7011fc78378/src/main/java/com/artipie/rpm/http/RpmUpload.java#L33-L50
The puzzle was created by paulodamaso on 24-May-20.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@g4s8/z, @olenagerasimova/z please, pay attention to this issue

@0crat assign me

@0crat assign me (here)

@olenagerasimova The job #253 assigned to @olenagerasimova/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

The puzzle 162-efa52435 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #260 is still not solved.

@0pdd the only puzzle #260 is solved here.


Test push

Testing if CLA issues have been resolved.

@googlebot please check again

Testing access issues.


Will there ever be a new release?

It's (again) more than 2 years since the latest release. Important issues are already fixed on master (e.g. commit https://github.com/jmock-developers/jmock-library/commit/dad8d62e1f10464ce0d36f3bcb011a1dfe86d58f).
I'm wondering if this project is now finally retired after having returned from the dead already once or if we will see some updates at some point in time? Or at least a new release with the existing changes...
@jmock-developers (@olibye, @tobyweston, @npryce, @sf105, @PASimmons)

https://github.com/jmock-developers/jmock-library/releases/tag/2.13.0


Add new color modes to color input

We currently only support rgba, hsla as well as 3-/4-digit hex values.
We've received requests to extend this to other color modes:
### Tasks
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1637
- [ ] https://github.com/tokens-studio/figma-plugin/issues/1608

Feel free to comment on this issue to request additional color modes.

LCH would be good, but OKLCH would be great. I won't write an essay on why as this article by Evil Martians already does a great job covering it.

HSLuv support would be awesome, since I cannot use the brand colors in a project I'm working on currently. HSLuv extends the CIELUV color space.
Read more here: https://www.hsluv.org

I've added these and other color space requests in a combined post on Feature base. Please go upvote! (: Added to Featurebase Request-	💡 Expand functionality of color space

Migrated to Featurebase


Update Database Clarity

Summary
Describe your changes here.
Fixes #Issue_Number (if available)

Internal previews

📄 File
🔗 Preview link

docs/database/azure-cosmos-db-component.md
.NET Aspire Azure Cosmos DB component

docs/database/azure-cosmos-db-entity-framework-component.md
.NET Aspire Microsoft Entity Framework Core Cosmos DB component

docs/database/mongodb-component.md
.NET Aspire MongoDB database component

docs/database/mysql-component.md
.NET Aspire MySQL database component

docs/database/mysql-entity-framework-component.md
docs/database/mysql-entity-framework-component

docs/database/oracle-entity-framework-component.md
.NET Aspire Oracle Entity Framework Component

docs/database/postgresql-component.md
.NET Aspire PostgreSQL component

docs/database/postgresql-entity-framework-component.md
.NET Aspire PostgreSQL Entity Framework Core component

docs/database/sql-server-component.md
docs/database/sql-server-component

docs/database/sql-server-entity-framework-component.md
.NET Aspire SqlServer Entity Framework Core component

@IEvangelist
1.) sorry you caught a typo in my PR. It should be:
var mysql = builder.AddMySql("mysql");
var mysqldb = mysql.AddDatabase("mysqldb");

2.) a little context here as I was on the docs triage on Friday with @DamianEdwards  and @bradygaster  looking at these docs. We actually thought the chaining was a bit confusing. In eShop (https://github.com/dotnet/eShop/blob/main/src/eShop.AppHost/Program.cs#L10-L17) for example we break each DB out separate and pass them in with reference. While chaining is nice, it can be confusing that it is actually first creating the server and then the database. There are somethings you can't do to the database... like add another database or add pgadmin.
So for example this doesn't compile:
var postgres = builder.AddPostgres("db").AddDatabase("mydb").WithPgAdmin();

or this:
var postgres = builder.AddPostgres("db").AddDatabase("mydb").AddDatabase("anotherone");

Our feeling was most folks will actually have to split this out and we should show that a bit more in the docs. Thoughts?


Updating template for Jenkinsfile

Minor Jenkinsfile and license updates. This simplifies some things in the Jenkinsfile, and conforms to my current template I'm using for several RPMs used in the PIT and NCN images.

/backport release/1.3


'comcast.net' no longer suggested for 'comcast.com' emails

In master, mailcheck no longer suggests<EMAIL_ADDRESS>as a correction for<EMAIL_ADDRESS>addresses, even though this is a common user error.
In the v1.1.0 release tag, running
Mailcheck.run({email:'joe@comcast.com'});
correctly returns the suggestion
Object {address: "joe", domain: "comcast.net", full<EMAIL_ADDRESS>In master, running the same thing:
Mailcheck.run({email:'joe@comcast.com'});
returns no suggestion at all.

I have the exact same problem for gmail.fr versus gmail.com
it seems the general treshold (2) is used whereas difference is 3 here.
maybe there should be a special case when secondLevel is a complete match, but topLevel is wrong ?

You can adjust threshold like so:
Mailcheck.domainThreshold = 3

so that comcast.com gets suggested as comcast.net


Mojo: error: execution exited with a non-zere result:1

The error occurs when running llama.mojo
My environment: Python  3.10(ubuntu22.04)
console imformation bellow:

mojo llama2.mojo stories15M.bin -s 100 -n 256 -t 0.5 -i "Llama is an animal"
num hardware threads:  192  SIMD vector width:  16
Unhandled exception caught during execution: An error occurred in Python.
mojo: error: execution exited with a non-zero result: 1

Hi @Cyria7 , probably you haven't downloaded model file stories15M.bin
See how it works on HF https://huggingface.co/spaces/radames/Gradio-llama2.mojo


ReadLen=36

Hi,
You have set your biasFree script analysis to "ReadLen=36".
Does that not mean that if someone uses this with a bam file of different read length, the analysis will be wrong ?

Hi Panos,
Thank you for this question.
Actually, the ReadLen parameter is used to calculate genome mappability. This parameter can be trace-backed to the seqOutBias tallymer --read-size parameter, and further to the gt tallymer mkindex -mersize parameter. The reasons why we use k=36 as the default value are as follows:

A benchmark study tested different read lengths and reported that when using k=36 compared to k=75, the difference of uniquely mapped positions is ~2% for smaller genome size like C.elegans and D.melanogaster, ~7% for larger genome size like human and mouse. But the time cost is about 6-fold.
Another study made a more detailed benchmark and found the ratio of uniquely mapped positions reaches the plateau after k>20.
So, this is a trade-off. Considering our pipeline is intended to generalize for many species, we choose the least acceptable length k=36 to pre-calculate the mappability files. That's also the default values seqOutBias chose in their analysis.

Yes, you are right, using the specific read length from your experiment (usually 150 bp nowadays) will lead to a more accurate result, but may need more computational cost.
Maybe it's a good practice to modify the ReadLen parameter as a user-defined parameter in a new version.
Glad to discuss more.
Houyu Zhang

Thank you for the swift answer !
So, while computing the genome mappability for the exact readLength would be more accurate, the 36bp calculation is still a "good-enough" approximation ?
Thank you also for the offer to discuss more, I will probably come back with further questions :)
Best Regards,
Panos

Hi Panos,
Thank you for the further question.
I have checked our previous analytic script. We used k=51 for the mESC ATAC-seq data in our paper since the exact read length is 51bp. We have not tested other k values.
https://github.com/YenLab/Tn5InsertPrefer/blob/518572f22f62ea3c573ae4b7bc44f4ad227a66e3/5_BiasFreeATAC_mESC.sh#L20
As for your question about the "good-enough" approximation, I think maybe a titration using varied k values will tell us whether this parameter affects the final results of our pipeline. However, based on the theories from the papers I listed, I personally think using k=36 or a larger value will give pretty similar results. I will update the testing result here when possible.
Anyway, following your suggestions, I will open the ReadLen parameter to users in the next version.
Best wishes,
Houyu Zhang


RouteHealthDegraded - 503 Service Unavailable

Describe the bug
OKD4 web-console inaccessible
I deployed this cluster around 2 weeks ago and it hosts eclipse che, which is accessible. The web-console for OKD4 however is not and I am not quiet sure how to resolve this matter.
ClusterOperator-Console-Output.txt
No changes have been made by me directly, since I last logged into the console successfully.
Version
Client Version: 4.5.0-0.okd-2020-08-12-020541
Server Version: 4.5.0-0.okd-2020-08-12-020541
How reproducible
100% reproducible
Log bundle
The server is currently unable to handle the request (get imagestreams.image.openshift.io must-gather)

I also was wondering if the slack channel is an open or private channel?

Is it still happening on latest stable release? Is etcd complaining about slow queries (check pod logs)?

I re-deployed the instance and it seems stable now. I have noticed an issue with the image pruner now and will file a new bug report.


Outline inputs don't support all states

There are few unstyled states in outline theme variant of input fields.
Appears that disabled, readonly and invalid states do not have styles yet. In addition each state needs to work together with hover and focus states.

@juuso-vaadin try now. Minimal CSS again to match the default Lumo styles, also an effort to try to keep it consistent.


Make Complement work through the Nix flake, and implement Complement in CI

Now that Conduwuit has working Complement support overall, we need to remove the dependency on Docker/Dockerfile, and get a system going in CI using the Nix flake for regression testing and such.
https://github.com/AwesomeQubic/conduwuit-eXtreme/blob/main/flake.nix

Just needs to be implemented in CI now, fully works through Nix

This is implemented but because of fragile concurrency catching some bugs, the results are marginally differing every time so we're unable to do a diff between the checked in repo results and the current ran results. For now that CI run is allowed to fail.


Doesn't display anything when only one marker is present

I'm not reporting a bug, asking for help.
Clustering works properly when multiple (even only 2) markers are present but when I filter to 1 marker, it's not displaying anything. But in a different project it works fine even when it's just 1 marker i.e. it displays the marker icon instead of cluster icon and that's fine. I'm using almost the same code in both projects. Any idea what could cause this problem of not displaying, theoretically?

@BartjeD Unfortunately, no.

I worked around it by adding a fake marker if there was only 1 marker in the collection.
Just copy the position of the first marker and it displays the markers on the map.
Obviously we needed to adjust the count mechanism as well, to exclude the fake marker from the count.
It's very ugly and probably only works in this exact situation.
We noticed sometimes clusters with only 1 marker also don't show on the map, so we suddely miss clusters after zooming.
If we can recognize those clusters with only one marker programatically this hack wil also work there.

Sounds like a good enough workaround.
But I guess there won't be any one-marker clusters. From what I understood, the plugin displays the marker instead of cluster in the only-one-marker case, even after zooming in.

Hi @BartjeD @RoboVij
I am experiencing the same issue Did you find any good solution to the problem?

If it helps anyone my solution is to just skip the usage of markercluster and add it directly to the map instead when there is only one marker

Hi everyone,
Please, have a look at
https://stackoverflow.com/questions/57383443/single-marker-fails-to-get-rendered-if-it-is-not-in-or-close-to-a-cluster
I provided a description as to why this occurs. Hope this helps

In our case we still require the work around even if we apply the zoom rounding you mentioned. @BeAllAround
It doesn't seem to be the same issue.


Fix TestTaskRunRetry for k8s 1.22.9 and later

Changes
We just switched to k8s 1.22.9 on CI last night, and TestTaskRunRetry started failing. After a bunch of investigation, I determined this was due to https://github.com/kubernetes/kubernetes/pull/108366, which went into k8s 1.22.9. This resulted in the pod.Status.Phase that TestTaskRunRetry expected to be updated instantly having a delay. I could have fixed this with a sleep, but decided verifying that each container in the pod had terminated with the expected exit code was cleaner.
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Docs included if any changes are user facing
[x] Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been filled in
(if there are no user facing changes, use release note "NONE")

Release Notes
NONE

/assign @vdemeester @lbernick @afrittoli @jerop

/test pull-tekton-pipeline-alpha-integration-tests

Thanks @abayer 🎉
/lgtm


Failed to activate ZGLDS_DEMO_USR

hi,
the DB table cannot be activated - error msg:

ZGLDS_DEMO_USR-SOURCECODE: Too long for activation of 'not null' flag (>255)

Cheers
Hendrik

If you go to table definition in SE11 and deactivate the "Initial Values" Flag of field "SOURCECODE" the table could be activated.

Thanks! Works now.
ABAP PLATFORM	1909.


Add aodh api service check

add missing aodh api status check.
The reason of not adding for cinder/neutron is : there are many other cinder/neutron service status check already exists.

LGTM


luci-app-travelmate: "final" fixes

during intense testing with different browsers (Chrome/Firefox/partly IE
in a VM) I found & fixed some more minor things:

re-add accidently removed "apply_on_parse" attribute in overview cbi
fixed a corner case where the "Restart" button not works correctly
Removed leftovers from last commit

Signed-off-by: Dirk Brenken<EMAIL_ADDRESS>

@dibdot - feel free to merge but please use git cherry-pick -x <commithash> to pull it into 18.06.


Rails assets not loading with Nixpacks

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
I tried to deploy a Rails app on Railway using the default compilation method - Nixpacks. The app is a vanilla rails app, with minimal config. All the secret keys are check into the repo as encrypted credentials. Following are the only env vars apart from Rails defaults
NIXPACKS_BUILD_CMD
bundle exec rake assets:precompile && bundle exec rails db:migrate

NIXPACKS_START_CMD
bundle exec rails s -b <IP_ADDRESS>

With nixpacks, my build step works fine but fails to load any of the assets as shown in the screenshots below. Heroku buildpack works just fine. The issue happens even when I remove the above env vars.

To reproduce
Steps to reproduce the bug:

Deploy a rails app with standalone tailwind CSS - rails new testapp --css tailwind.
Set up some basic styles.
Push to trailway.
Navigate to the railway url.

Expected behavior
The styles must load like so, when nixpacks are selected -

Environment

Rails 7
Latest Nixpacks ( default )

@coffee-cup this is the repo i'm trying to deploy - https://github.com/safewlabs/comix-mono. That's odd because i don't get any build errors while deploying.

It uses a standalone version of Tailwindcss - https://github.com/rails/tailwindcss-rails / https://tailwindcss.com/blog/standalone-cli

I'm seeing the same behavior in my repo.
Additional info:

Nixpacks builder + RAILS_ENV variable not set = assets pipeline works
Nixpacks builder + RAILS_ENV=production variable = assets do not load
Heroku builder + RAILS_ENV=production variable = assets pipeline works

This is currently deployed to: https://web-production-61e7.up.railway.app/
As of October 12 @ 11:30p PST, I've switched back to the failing scenario above (Nixpacks builder + RAILS_ENV=production variable, assets do not load). Hopefully the logs linked to that deployment are helpful to diagnose.
Is there anything else I can do to help investigate?

When I compare the deployment logs, searching for "rake assets", I notice one difference that may be directly relevant:
Heroku builder + RAILS_ENV=production variable = assets pipeline works
Running: rake assets:precompile
Running: rake assets:clean

Nixpacks builder + RAILS_ENV=production variable = assets do not load
║ build      │ bundle exec rake assets:precompile                              ║
#20 [stage-0 16/18] RUN  bundle exec rake assets:precompile

It appears that the Nixbuilds are missing the "rake assets:clean" invocation.
Not sure if there are other meaningful distinctions too -- I focused on the word "assets" in my comparison, but there may be other subtleties.

@coffee-cup fyi ^

I split my issue to a separate ticket (https://github.com/railwayapp/nixpacks/issues/672) and will delete my previous comments, to keep this original issue cleaner.


chore: update the readme file

https://github.com/OpenPromisesProject/op-serverless-api/issues/142
Based on the PR: https://github.com/OpenPromisesProject/op-serverless-api/pull/143

@lilsweetcaligula thank you so much for this!


Allow easy discovery of other benches nearby.

As I user I want to be able to easily discover other benches near the bench I'm currently looking at.
Possible implementations:
1] Provide link to a map which shows any other nearby benches.
I see a bench on Twitter, click the link and end up at https://openbenches.org/bench/8455 which shows a map with a single bench marked on it. I click a suitably prominent button/link labelled "See other benches near this one", or words to that effect, and am taken to https://openbenches.org/#51.520279/-0.153611/16
Pros:

bench.php already constructs the HTML using variables for the coordinates https://github.com/edent/openbenches/blob/dd649f71da155ca1914712cdedc4bb39081ef201/www/bench.php#L60 so adding a   link like https://openbenches.org/#51.520279/-0.153611/16 would be easy.

Cons:

Maybe there are no other benches near this one so following the link doesn't make any other benches visible, at least not without the user zooming out. This may be potentially confusing. ("It says see other benches but doesn't show any other benches when I click it.")

2] Always show all benches.
The map on a bench page shows all benches the map, with the pointer of the bench the page is about differentiated somehow. E.g. the pointer for the bench this page is about is in red
.
Pros:

Nearby benches are discoverable without an clicking anything to make them show up.

Cons:

Differentiation by colour may not work for all types of colour blindness.
I've no idea how differentiation would be done for screenreaders.
In my observations, if a bench is very close to another bench it's pointer is not visible without clicking on a circle with a number in it, even with high zoom value. Unless there's some way around that, there would be a lot of cases where the pointer for bench wouldn't be visible on it's page without user interaction.
Seems harder to implement than possible implementation 1.

I like option 2.  I think a change of colour and a change of shape would work well.

See I like option 1 because implementation is trivial enough I know I could do it, whereas I have no idea about how to do option 2 or if it would even would work for benches very close together.

Haha! OK - write a pull request for 1 :-)

This is now on the site. Thanks!


Issue with NextJS

Hi, I am trying to use rn-css with a mono-repo using NextJS and React-Native. I get the below error while trying to run it on NextJS
Do you have a working example with NextJS or any SSR app? Could you please help me out with this?
Error: Cannot find module 'react-native'
Require stack:
- /app-path/node_modules/rn-css/dist/index.js
- /app-path/web/.next/server/pages/index.js
- /app-path/node_modules/next/dist/next-server/server/require.js
- /app-path/node_modules/next/dist/next-server/server/load-components.js
- /app-path/node_modules/next/dist/next-server/server/api-utils.js
- /app-path/node_modules/next/dist/next-server/server/next-server.js
- /app-path/node_modules/next/dist/server/next.js
- /app-path/node_modules/next/dist/server/lib/start-server.js
- /app-path/node_modules/next/dist/cli/next-dev.js
- /app-path/node_modules/next/dist/bin/next

My app structure looks something like below
- web
   - package.json(includes react-native-web)
- app
   - package.json(includes react-native)
- shared
   - package.json(includes rn-css)

The structure of your project seems wrong. Can you confirm that your intention is to use a common code for the app and the web?
You can try to use this tool to create your React-Native + React-Native-Web if you want to study the classic structure.
Basically, what you are missing here is the instruction that will explain that import from react-native package should be made from react-native-web instead. In webpack, that would be done with this alias:
{
  resolve: {
    alias: {
        'react-native$': 'react-native-web'
    }
  }
}

This should be part od your webpack-config.js

Thank you for the quick response @Sharcoux
I found the fix. Had to include the package for transpile in next.config.js file as below.
const withTM = require('next-transpile-modules')([   'rn-css' ])
This also causes build errors because of the regex I believe, so had to add the below in the babel.config.js file
presets: [       'next/babel',       '@babel/preset-env', {         'exclude': ['@babel/plugin-proposal-unicode-property-regex', '@babel/plugin-transform-unicode-regex']       }     ],

Great package though. Excited to use it. Makes life easy for creating a mono-repo for react web and native


Investigate performance characteristics

We’ve found in production that the go parser is surprisingly slow: it can pull 1.25 MB/sec, which is no slouch, but in contrast, a language like C#, which has much more syntax, is nearly twice as fast. This isn’t a showstopper, but it might be interesting to look into exactly why this is!

This parser appears to handle Unicode characters correctly; might be it?


highValue also changes when changing value

When I am sliding from the left side  it should only change the value but it also changes the highValue this issue I am using milliseconds  as the values.

I don't quite understand - is the high value changing when you slide the low value handle? Can you post an example StackBlitz with your code? You can fork and edit for example this one.

I had the same issue on rtl pages. the workaround is to use the manualRefresh on ngAfterViewInit()


Fix server ip blocked issues

Bing changed arguments for requesting variants, where sending galileo in Balanced mode would get an internal error message. This branch fixes the issue.

Fixed issue #26

Please merge this!


Fixes rounded corners on city picker component

~This PR is a WIP because it needs to be integrated with the changes in #1387 once that PR is merged. Otherwise it will look like this:~
This got messy (rootView vs view, etc) but the fix was just to take the safe area into account. React Native does this and now that we do too, our corners line up.

Fixes LD-319. #native_no_changes

Fails

:no_entry_sign:

This PR includes changes to the Emission Pod's native code but does not have a package.json
change for the update to the "native-code-version". If this is fine, add #native_no_changes to your PR message.

  Generated by :no_entry_sign: dangerJS

Cool, yep - looks good to me, nice digging


matter's install.sh Installation has some problem.

swz@swz-ubuntu:~/esp/esp-matter$ . ./install.sh
dirname: 不适用的选项 -- b
请尝试执行 "dirname --help" 来获取更多信息。

Connection closed.

Disconnected from remote host(swz_ubuntu 22) at 08:39:51.

Type `help' to learn how to use Xshell prompt.

swz@swz-ubuntu:~/esp/esp-matter$ sudo ./install.sh

Running Matter Setup

  WELCOME TO...

  BOOTSTRAP! Bootstrap may take a few minutes; please be patient.

Downloading and installing packages into local source directory:

  Setting up CIPD package manager...[/]
b'[P2490 08:54:15.862 client.go:306 W] RPC failed transiently. Will retry in 1s    {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"1s"}\n[P2490 08:54:37.872 client.go:306 W] RPC failed transiently. Will retry in 2s    {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"2s"}\n[P2490 08:55:00.880 client.go:306 W] RPC failed transiently. Will retry in 4s    {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"4s"}\n[P2490 08:55:26.014 client.go:306 W] RPC failed transiently. Will retry in 8s    {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"8s"}\n[P2490 08:55:55.023 client.go:306 W] RPC failed transiently. Will retry in 16s   {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"16s"}\n[P2490 08:56:32.049 client.go:306 W] RPC failed transiently. Will retry in 32s   {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"32s"}\n[P2490 08:57:25.097 client.go:306 W] RPC failed transiently. Will retry in 1m4s  {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"1m4s"}\n[P2490 08:58:50.171 client.go:306 W] RPC failed transiently. Will retry in 2m8s  {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"2m8s"}\n[P2490 09:01:19.241 client.go:306 W] RPC failed transiently. Will retry in 4m16s {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"4m16s"}\n[P2490 09:05:56.349 client.go:306 W] RPC failed transiently. Will retry in 8m32s {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository", "sleepTime":"8m32s"}\n[P2490 09:14:50.030 client.go:350 W] RPC failed permanently: rpc error: code = Internal desc = prpc: when sending request: Post "https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix": dial tcp <IP_ADDRESS>:443: connect: connection refused {"error":"rpc error: code = Internal desc = prpc: when sending request: Post \\"https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix\\": dial tcp <IP_ADDRESS>:443: connect: connection refused", "host":"chrome-infra-packages.appspot.com", "method":"ListPrefix", "service":"cipd.Repository"}\nError: prpc: when sending request: Post "https://chrome-infra-packages.appspot.com/prpc/cipd.Repository/ListPrefix": dial tcp <IP_ADDRESS>:443: connect: connection refused.\n'
Traceback (most recent call last):
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 795, in <module>
    sys.exit(main())
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 787, in main
    return EnvSetup(**vars(parse())).setup()
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 457, in setup
    result = step(spin)
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 564, in cipd
    if not cipd_update.update(cipd=cipd_client,
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/cipd_setup/update.py", line 311, in update
    if not check_auth(cipd, package_files, spin):
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/cipd_setup/update.py", line 85, in check_auth
    inaccessible_paths = _check_all_paths()
  File "/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/cipd_setup/update.py", line 68, in _check_all_paths
    output = subprocess.check_output(
  File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 524, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/home/swz/esp/esp-matter/connectedhomeip/connectedhomeip/.environment/cipd/cipd', 'ls', 'pigweed/third_party/gcc-arm-none-eabi']' returned non-zero exit status 1.

Hi, swz1314520ll. This is the instalation problem. Follow this method

@swz1314520ll are you still facing this issue?
Can you try removing rm -rf connectedhomeip/connectedhomeip/.environment from your top directory and re-running ./install.sh

yes,I try as you said,but there is the same problem.
------------------ 原始邮件 ------------------
发件人:                                                                                "espressif/esp-matter"                                                                                @.>;
发送时间: 2022年12月1日(星期四) 中午1:30
@.>;
<EMAIL_ADDRESS>主题: Re: [espressif/esp-matter] matter's install.sh Installation has some problem. (Issue #96)
@swz1314520ll are you still facing this issue?
Can you try removing rm -rf connectedhomeip/connectedhomeip/.environment from your top directory and re-running ./install.sh
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@swz1314520ll I also got the same error while installing I guess you are using Ubuntu 22. Follow this

ok,thanks!If I have any problem,i will tell you.
------------------ 原始邮件 ------------------
发件人: "Ali Hassan @.>;
发送时间: 2022年12月1日(星期四) 下午2:36
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [espressif/esp-matter] matter's install.sh Installation has some problem. (Issue #96)
@swz1314520ll I also got the same error while installing I guess you are using Ubuntu 22. Follow this
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@swz1314520ll Is your issue solved?

The link of baidu pan is here.链接: https://pan.baidu.com/s/1nfVhxe-Uy8LXzhwB16UZaA?pwd=6666 提取码: 6666 复制这段内容后打开百度网盘手机App，操作更方便哦
------------------ 原始邮件 ------------------
发件人: "Hrishikesh @.>;
发送时间: 2022年12月6日(星期二) 下午4:21
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [espressif/esp-matter] matter's install.sh Installation has some problem. (Issue #96)
@swz1314520ll Is your issue solved?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@swz1314520ll From your previous log, it's caused by some network connectivity issue. You may need a VPN to setup the Matter build environment.

@swz1314520ll Please close this if your issue is resolved

Closing this now. Please re-open if you face any issue using the VPN as suggested above


Add fields to eth_getTransaction series of RPCs

Add fields for chainId, publicKey, and raw to RPCs where detailed
transaction data is returned (eth_getTransactionByBlockHash,
eth_getTransactionByBlockNumber, eth_getTransactionByHash, and
eth_getBlock with certain parameters).
Addresses #1802
Signed-off-by: Danno Ferrin<EMAIL_ADDRESS>Changelog

[x] I thought about the changelog and included a changelog update if required.

Doc change is to update the JSON-RPC samples to show the three included fields in calls to eth_getTransactionByBlockHash,
eth_getTransactionByBlockNumber, eth_getTransactionByHash and maybe eth_block

Doc change is to update the JSON-RPC samples to show the three included fields in calls to eth_getTransactionByBlockHash,
eth_getTransactionByBlockNumber, eth_getTransactionByHash and maybe eth_block


docs: broken links in README.md and CONTRIBUTING.md

The link mentioned in https://github.com/intel/dffml/blob/f76f2ce94c3972634053377b00e7c16530f7f0a4/README.md#contributing is broken and leads to an error 404 page.
The link mentioned in https://github.com/intel/dffml/blob/f76f2ce94c3972634053377b00e7c16530f7f0a4/CONTRIBUTING.md is also broken, just like the above one.

I'd like to fix this. I'll submit a PR in a moment.


What class types do I need to bind to ensure interopability?

I have defined lua bindings on my texture manager like so:
  auto textureresource_record = engine_namespace.new_usertype<TextureResourceManager>("TextureResourceManager",
    sol::constructor<TextureResourceManager()>(),
    "LoadTextureFromFile", &TextureResourceManager::LoadTextureFromFile
  );

This function returns a type std::shared_ptr<sf::Texture>
I've bound another object to take in that shared texture from lua:
  auto player_record = engine_namespace.new_usertype<Player>("Player",
    "SetTexture", &Player::setTexture
  );

  // signature Player::setTexture(std::shared_ptr<sf::Texture>)

and I have a script that looks like this:
local textures = Engine.TextureResourceMananger.new()

function load_player(player)
    player:SetName("Player1")
    player:SetHealth(100)
    player:SetTexture(textures:LoadTextureFromFile("hero.png"))
end

When I run the script, I can see basic things like string names, integer health, etc have been correctly modified. However my shared pointers are remaining empty (nullptr).
I wondered, do I have to bind everything including the sf::Texture class in lua for it to work or if sol just passes along the memory that is allocated from the C++ side (the TextureResourceManager class returns the shared ptr from C++ so it's not like lua needs to know...) ?
Thanks again for this awesome library. I'm pretty excited to use it.

You don't need to bind everything. What does the SetTexture method look like, what does the LoadTextureFromFile look like? Are you sure it's loading properly?

Ok my hunch was correct, the memory on the C++ side gets passed through. I was incorrectly calling a function when I had described it as a property in my texture resource manager's lua bindings. We are rockin' and rollin'!


Documentation output fixes

[x] It would be useful to show default messages if translations are missing.
[x] Fix anchor links so that dereferencing works. This may require layout changes. Note: also need to use rdfs:domain to map property to class.

Done https://github.com/fortunejs/fortune/commit/c433116c63a26514efa603a35221c737d97a9b9b.


New format computed property accessor not recognised

Versions:

ide-helper Version: 2.12.2
Laravel Version: 9.0.0
PHP Version: 8.1.2

Description:
PR #1289 added support for the new attribute mutator/accessor format, but calculated properties/attributes aren't recognised yet.
Steps To Reproduce:
This example calculated property results in * @property-read string $full_name:
public function getFullNameAttribute(): string
{
    return "$this->first_name $this->last_name";
}

The following example is not recognised and does not add the same @property.
public function fullName(): Attribute
{
    return Attribute::get(fn() => "$this->first_name $this->last_name");
}

It should also result in (only) $fullName instead of $full_name.
The latter should also be protected instead of public of course, but that's a separate issue (#1293).

are there any progress/PR on this?

If you make the function public, and provide a return type like so: fn(): string, it works.

That's true, but then it's no longer an accessor/mutator, which is the topic of this issue.

What I mean is, if you do this:
public function fullName(): Attribute
{
    return Attribute::get(fn(): string => "$this->first_name $this->last_name");
}

It will generate a full_name property for you.

does it matter though using public/protected?

does it matter though using public/protected?

The Laravel docs makes them protected. But ide-helper only picks them up when they are public.

What I mean is, if you do this:

public function fullName(): Attribute

{

    return Attribute::get(fn(): string => "$this->first_name $this->last_name");

}

It will generate a full_name property for you.
That's all you want, isn't it?

True. That's what I do nowadays. That said, Laravel supports accessors without typehinting whereas IDE Helper doesn't.
Hence my PR #1411.

Any idea when this will be released on packagist? I'd prefer not to directly require dev-master, but this does work great for our use case. @barryvdh

I have given up on waiting for this and have stopped using this package in favour of the Laravel IDEA plugin.

A new version was released an hour ago; https://github.com/barryvdh/laravel-ide-helper/releases/tag/v2.14.0


chai-json not working

Hi,
I tried to follow the documentation and written below:-
const chai = require('chai');
chai.use(require('chai-json'));
const expect = chai.expect;
describe('test project components', () => {
it('should have package.json', () => {
expect('./hi.json').to.be.a.jsonFile();
});
});
I am getting below error:-
Error: Invalid Chai property: jsonFile
at Error (native)
at Object.proxyGetter [as get] (node_modules\chai\lib\chai\utils\proxify.js:66:17)
at Context.it (test\project.spec.js:10:36)
Similar issue is with other chai plugins (chai-js) that I tested. Am I missing anything?
Regards,
Sanjeev

Hi @skumar568, your syntax is correct.
Could you tell me which nodejs and chai version are you using?
If you're using chai v4.x.x could you try to downgrade chai to version 3 (try 3.5.0) and retry to use chai-json, chai-js and other plugins with this issue  ?
Maybe these library has incompatibility with newer chai version.

Thanks @giper45 . It seems like two issues are there:-

With<EMAIL_ADDRESS>plug-in doesn't work. Have to use<EMAIL_ADDRESS>Syntax mentioned in read-me is not correct.
expect(testFile).to.be.a.jsonFile(); : doesn't work
expect(testFile).to.be.a.jsonFile(); : it works

Hi @skumar568

With<EMAIL_ADDRESS>plug-in doesn't work. Have to use<EMAIL_ADDRESS>
Ok, I'll try to fix this, that's a common issue that affect different plugins, I have to find a solution to keep backward compatibility, or I just add to readme that my plugin needs chai version 3.x.x.

Syntax mentioned in read-me is not correct.
This is a strange, because the syntax in readme is the correct syntax... you shouldn't trust about the second syntax because I think that it always gives true (try to use that syntax with a no existent file or with a json file with a wrong syntax).
Can you send me the testFile.json file are you using and which error it gives so I try to fix the problem? Now I restart to work to the plugin to resolve these issues ;)
Thanks for your collaboration!


AzCopy thinks a blob snapshot and its base are the same location

Which version of the AzCopy was used?
10.6.0
Which platform are you using?
macOS
What command did you run?
copy
What problem was encountered?
Set the src to be a blob snapshot, dst to be its base. Run copy.
How can we reproduce the problem in the simplest way?
./azcopy copy "https://acct.blob.core.windows.net/container/filename?sv=2019-12-12&se=2020-11-18T21%3A10%3A28Z&sr=c&sp=rl&sig=redacted&snapshot=2020-10-19T21%3A05%3A50.1136138Z" "https://easybugs110.blob.core.windows.net/container/filename?sv=2019-12-12&se=2020-11-18T21%3A10%3A28Z&sr=c&sp=rwl&sig=redacted" --overwrite=true --s2s-preserve-access-tier=false --recursive;
Have you found a mitigation/solution?
Nope.

10.7.0 released


Screenmarkers plugin redesign (Unfinished)

I'm sorry, it's 8h30m in the morning and I have been coding this for
7 straight hours, I underestimated the size of this commit.
I can't think clearly enough to write a proper commit or PR message.
I would ask of the other developers that were involved in this project already to please finish this PR.
@Kamielvf  @deathbeam  @Adam-
TO-DO list:

(Maybe) add a PluginErrorPanel explaining what screen markers are if the list is empty (see implementations on ExpTrackers or Ge)
Hover effects, different shade versions of icons as an hover effect
Only allow creation of markers when logged in, and if player logs out in the process of creating one, dismiss the creation mode

I'm sorry if the code isn't up to my latest standarts, just trying to get this out before thursday, would love some patches from other devs.

If I could add my two cents, the first character of the marker name is chopped off no matter how much you resize.

Been testing your changes, if you start creating one and press right mouse button, it removes the creation panel on the side but still allows you to draw screen markers.

@j03l that is not in this PR, that's the outdated version I'm trying to update

Fixed @deathbeam's review requests
Added Hover effects
Added tooltips
Added introduction text panel
Fixed right click to cancel

Moved a constant to a more appropriate class.

@deathbeam we gud

Fixed bug with introduction panel appearing when it shouldn't
Made the thickness editor only save to config when exiting to display mode
Changed click listener on panels to focus lost listener on the spinner to save

Removed click-outside to save
Fixed enter keypress to save


Cannot use with ActiveForm::begin(['enableAjaxValidation' => true])

Hi author,
Your lib is great but I found that it cannot be used with the form that is set using Ajax globally.
$form = ActiveForm::begin([
'id' => 'register-form',
'enableAjaxValidation' => true
]);
I've spent much time to find the problem already.... ><
Will you add the support to it, in case others set the form using ajax globally...
thx so much

Also faced with this. It's not the widget issue. You just need to disable ajax validation for field:
echo $form->field($user, 'reCaptcha', ['enableAjaxValidation' => false])->widget(\himiklab\yii2\recaptcha\ReCaptcha::class);
Suggest add this case to the docs.

https://github.com/himiklab/yii2-recaptcha-widget/commit/48cbc958bea004cf41f3774a4a1d445f42499fbc

Also faced with this. It's not the widget issue. You just need to disable ajax validation for field:
echo $form->field($user, 'reCaptcha', ['enableAjaxValidation' => false])->widget(\himiklab\yii2\recaptcha\ReCaptcha::class);
Suggest add this case to the docs.

please @himiklab  add to readme this!)


gg

Challenge Say Hello to HTML Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

Hello word

@ahmathamid
Thanks for reporting this. But your code is incorrect.
GitHub Issues are for reporting bugs on the website only.
Please use the Help chat room for getting challenge related help.
Happy Coding.


Added a few lines to document the main difference between maturin and…

… setuptools-rust as far as building manylinux-compliant wheels is concerned.

Thanks! This looks rather helpful. Could you squash the two commits please?

bors r+


[refactoring] Test Executable Name with Spaces in Path

The executable name provided in the credential process template can include spaces from the file system path.

Referring to #160
Implementation

Enhance Tests to cover cases where executable paths may contain (allowed) special characters and whitespaces

Enhance Tests to cover cases where executable paths may contain (allowed) special characters and whitespaces

Does executable means the output of os.Executable() in ProcessCredentialProcessTemplate?

Yes, os.Executable() - the test case should ensure, that special characters or whitespaces are put into the final aws_credentials file correctly

,that special characters or whitespaces are put into the final aws_credentials file correctly

ok, so we are going to test WriteAWSCredentialsFile  in cross-platform envs?
https://github.com/theurichde/go-aws-sso/blob/main/pkg/sso/file_system.go#L53
because at first I thought that we are going to test ProcessCredentialProcessTemplate and see the output (i.e. the returned CredentialsFileTemplate) when os.Executable() returns an exe name with spaces

Hey there @rafiramadhana. Sorry for the ultra late reply.

because at first I thought that we are going to test ProcessCredentialProcessTemplate and see the output (i.e. the returned CredentialsFileTemplate) when os.Executable() returns an exe name with spaces

You are right, I was mistaken on that.


Animate the Testimonial Section

Due to the fact that there will be more testimonial cards in the testimonial section on the landing page, there is a need to design the cards such that they can be scrolled horizontally both in desktop and mobile view. This should be implemented in a carousel kind of design

This will be my first contribution to open source, I believe I can work on this

Can i work on this

Hello @mihrab34 looks like @Ruth-ikegah assigned this to someone. you can look through for the issues that have not yet been assigned

Done ✅
@kaxada @Ruth-ikegah
https://user-images.githubusercontent.com/56253512/213582987-2ea7976f-e830-410d-bbb0-bd1ae90a85e0.mp4

@mr-pandy I am wondering why you deleted these changes? Was there something wrong?

Hi @mr-pandy, how is this coming along? Do you need any help?

Hi @kaxada, can I take this on?

@kaxada, please help take a look at this and see if we need to reassign to someone else
Thanks!


Update notifications.php

French translation

@sedan07 here is a PR for you

Sorry @Yves911 you already put the fact it was for French translation in your message, just not on the primary line... I need more coffee.


zpa_talker needs a method to list application segments

list_application_segments expects an application ID, but you don't provide a method to discover all the app IDs.
application-controller
def list_application_segments(self, applicationId=None):
    """
    Method to obtain application segments
    :param applicationId type int. Application unique identified id
    """
    if applicationId:
        url = f'/mgmtconfig/v1/admin/customers/{self.customerId}/application/{applicationId}'
        response = self.hp_http.get_call(url, headers=self.header, error_handling=True)
        return response.json()
    url = f'/mgmtconfig/v1/admin/customers/{self.customerId}/application'
    response = self._obtain_all_results(url)
    return

Instead make list_application_segments return a list of all applications
url = f"https://config.private.zscaler.com/mgmtconfig/v1/admin/customers/{customer_id}/application"
And then add a new method get_application_segment(appid)
to get the app details
url = f'/mgmtconfig/v1/admin/customers/{self.customerId}/application/{applicationId}'

@zetan503 the applicationid is optional and by default set to NONE. If value not passed, the method will list all applications

Perfect, that worked. Thank you for the quick support!


Certification updates

Pre-submission checklist:
Please check each of these after submitting your pull request:

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

:heavy_check_mark: Deploy preview for landscape ready!
:hammer: Explore the source changes: f21cc037ad34965b1f3946002d8e8cdde1854c59
:mag: Inspect the deploy logs: https://app.netlify.com/sites/landscape/deploys/5fece5dbe5b99d0007836275
:sunglasses: Browse the preview: https://deploy-preview-1945--landscape.netlify.app

LGTM

LGTM


MSID: 92175 Version: 2 DOI: 10.1101/2<IP_ADDRESS>9560

MSID: 92175
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>9560
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92175
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>9560

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/92175v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>9560
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/92175/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Figure supplements are in the wrong order


Use one line for entire prompt

I have been trying to kick into effect, the option BULLETTRAIN_PROMPT_SEPARATE_LINE which supposedly puts the entire prompt on one line.
Does anyone know how this works or should I contribute my change that enables this option to work ?

Checked the latest version and everything seems ok. Sorry. I checked out the wrong version.


Piral-ng should respect --public-url

Bug Report
For more information, see the CONTRIBUTING guide.
Prerequisites

[ ] Can you reproduce the problem in a MWE?
[x] Are you running the latest version?
[x] Did you perform a search in the issues?

Environment Details and Version
All Piral packages are at latest Version, Angular is at 13.0.2
Description
Currently piral-ng hardcodes Angulars APP_BASE_HREF to "/", which causes routing inconsistencies when --public-url is used during build. React based pilets use the prefixed path, ng-piral Pilets don't.
Steps to Reproduce

Create a piral-ng based Pilet
Add some Angular routing
Verify lcally everything works
Do a release build using a --public-url != "/"
React Pilets will use it a prefix, piral-ng Pilets don't

Expected behavior
Angular Pilets should respect the set --public-url
Actual behavior
Angular Pilets always use "/" as base href
Possible Origin / Solution
The relevant code is here https://github.com/smapiot/piral/blob/4553e585d9cbb9ebd71d032a8fde55c305aaa268/src/converters/piral-ng/src/startup.ts#L31

We will solve it with 2 enhancements. First, we will introduce a new env variable called: PIRAL_PUBLIC_PATH, which will be available at build-time (and set to the configured public path). This variable is used to populate the context also with a value publicPath.
Now piral-ng can just access the public path via context.publicPath (or similar) - falling back to "/" if its not there.

This is available in the preview @next.


Add support for new fields in Soroban RPC's sendTransaction endpoint

Soroban RPC Changes
With the introduction of stellar/soroban-tools#1152, the Soroban RPC server introduces the following changes:
sendTransaction
The response will include a new, optional field in its response schema:

diagnosticEventsXdr: string[] - If the transaction status is "ERROR", this field may be present with an array of base64-encoded strings. Each string will decode to a raw DiagnosticEvent XDR struct containing details on why stellar-core rejected the transaction.

SDKs should add support for this field.

References

The documentation PR: soroban-docs#700.
An example implementation in JavaScript: stellar-sdk#905.

Hi @Shaptic, thanks for the issue.
This new field was supported and is now available on soroban.ex#v0.19.0.


DecryptQuery failed: cipher: message authentication failed

Hello. How does this Bug happen when everything is configured correctly? I need to restart 2-3 times then it works. Can you fix that please?

Hi @Pushergene -- can you please provide more details? Do you have a reproducible test case for this? Please re-open this ticket if you do!


No window titlebars

Rules:
awful.rules = {
        { rule = {}, properties = { titlebars_enabled = true } }
}

Nice init:
nice{
        titlebar_font = 'DejaVuSansMono Nerd Font Mono 10'
}

I did awful.rules.rules instead of awful.rules and now I get this error:
2020-10-18 17:04:03 E: awesome: Error during a protected call: /usr/share/awesome/lib/wibox/hierarchy.lua:124: attempt to call a nil value (method 'weak_connect_signal')
stack traceback:
        /usr/share/awesome/lib/wibox/hierarchy.lua:124: in upvalue 'hierarchy_update'
        /usr/share/awesome/lib/wibox/hierarchy.lua:222: in function 'wibox.hierarchy.update'
        /usr/share/awesome/lib/wibox/hierarchy.lua:208: in function 'wibox.hierarchy.new'
        /usr/share/awesome/lib/wibox/drawable.lua:94: in upvalue 'do_redraw'
        /usr/share/awesome/lib/wibox/drawable.lua:390: in function </usr/share/awesome/lib/wibox/drawable.lua:388>
        [C]: in function 'xpcall'
        /usr/share/awesome/lib/gears/protected_call.lua:36: in function </usr/share/awesome/lib/gears/protected_call.lua:35>
        (...tail calls...)
        /usr/share/awesome/lib/gears/timer.lua:231: in function </usr/share/awesome/lib/gears/timer.lua:229>
2020-10-18 17:04:03 E: awesome: Error during a protected call: /usr/share/awesome/lib/wibox/hierarchy.lua:124: attempt to call a nil value (method 'weak_connect_signal')
stack traceback:
        /usr/share/awesome/lib/wibox/hierarchy.lua:124: in upvalue 'hierarchy_update'
        /usr/share/awesome/lib/wibox/hierarchy.lua:222: in function 'wibox.hierarchy.update'
        /usr/share/awesome/lib/wibox/hierarchy.lua:208: in function 'wibox.hierarchy.new'
        /usr/share/awesome/lib/wibox/drawable.lua:94: in upvalue 'do_redraw'
        /usr/share/awesome/lib/wibox/drawable.lua:390: in function </usr/share/awesome/lib/wibox/drawable.lua:388>
        [C]: in function 'xpcall'
        /usr/share/awesome/lib/gears/protected_call.lua:36: in function </usr/share/awesome/lib/gears/protected_call.lua:35>
        (...tail calls...)
        /usr/share/awesome/lib/gears/timer.lua:231: in function </usr/share/awesome/lib/gears/timer.lua:229>

i get blank space above my windows while those are being shifted down with awful.rules.rules. with awful.rules nothing happens at all

@RossComputerGuy Looks like you are using the branch of nice meant for awesome-git version but are actually using awesome stable.

@mut-ex, you're totally right! ...it didn't cross my mind to check that beforehand what you wrote in the readme. sry


Added notcurses

Rebased.

I also added some tags: I've been working trough the Notcurses book and the library's demo code and there are terms (and variants of them) that come up frequently.


Mouse utilities, Mouse Jump, show on all screens.

Description of the new feature / enhancement
An option to show the "desktop thumbnail" on all displays an not just the active would be nice.
Scenario when this would be used?
It can be jarring to not really know where it might appear and there is no reason to not have it on all displays, is there? Doing this would allow this tool to be used to quicky get to the other monitors. This might be just as important to getting to a different place on the same monitor.
If not on all displays, it would be just as useful to me if you could also have it always display on a configurable display or even just aways on the primary display.
Supporting information
No response

The mouse jump mini-preview window shows up right under my cursor, and shows all monitors so I can jump my mouse anywhere on them, Why would you want to show the mini-preview on every screen requiring you to move your mouse all the way to the other screen to use it? Doesn't that defeat the purpose of this utility? /needinfo

I suppose the idea would be that if I had a large center monitor, and two or more single use "side" monitors, mini-preview, when activated, could display on the primary, moving my mouse to the center of that. Let's assume the side monitors are VERY small, and the mini-preview is too small to use there.

Now activate the mini-preview, which shows large and easy to see on primary, and you click something on "Side 1"
Now when done with that task, I can use mini-preview (which show on primary, with mouse of the center of it) and I can click to resume work on "Main"

Also, because I don't want to go the Side 1 or 2 by "accident" I use "Dual Monitor Tools" to make the mouse "sticky" to each screen.
I will be honest, I think I can get mostly what I want with DMT Cursor options, but don't want to run another program for that.
Maybe "Mouse Jump" is not exactly what I want/need for this, but it's the closest thing to what DMT Cursor options can do.
For quick reference it has these:
General:

Again, I'm probably barking up the wrong tree trying to get this done with "Mouse Jump".


Fix XDG well known directories

Refactored a lot of code to be more modular. Even tho the code in the current state is BAD, it works now without the need to specify a fixed number of well known directories.
This change could also allow to render more menu items on the side bar more easily.
Fixes #30
Fixes #41
CC: @AnshumanNeon Could you please test this?

Thanks for updating the code and making it cleaner!

Does this work for the MacOs?
func getExternalMediaFolders() []directory {
	var paths []string
	directories := []directory{}

	currentUser, err := user.Current()
	if err != nil {
		OutPutLog("Get user path error", err)
	}
	username := currentUser.Username

	folderPath := filepath.Join("/run/media", username)
	entries, err := os.ReadDir(filepath.Join("/run/media", username))
	if err != nil {
		OutPutLog("Get external media error", err)
	}
	for _, entry := range entries {
		if entry.IsDir() {
			paths = append(paths, filepath.Join(folderPath, entry.Name()))
		}
	}
	return directories
}

I fix the conflict, Would you like to review it?

So it seems have some background problem I fix it down below,and I change to the new version get external media
https://github.com/MHNightCat/superfile/commit/ae6d7de9bc63e667446097a373c1cb79aa244475
https://github.com/MHNightCat/superfile/commit/60f3e7fd735f5dc39550fcb7357acc2fb27455ce

well now, no other folder is shown except home

I solved this issue now in #51


Add API docs sphinx builder

Replaced by https://clusterhq.atlassian.net/browse/FLOC-101
This will help validate the format of the API docs are correct.
Insofar as our internal API is not stable (and perhaps might never be, perhaps only external HTTP API will be), probably not necessary for first release.

We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-101. You are welcome to file additional issues in GitHub if that's easier for you.


Fixed issue regarding node stop method not called in the correct context

Fixed issue regarding the node stop method not being called with the correct context when the topology destroy method is called.

Awesome. Thanks for the PR. Merging now.

Will publish a new NPM version shortly.

Great! Thank you for this great package!
On Wed, May 8, 2019 at 4:54 PM Simon Swain<EMAIL_ADDRESS>wrote:

Will publish a new NPM version shortly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/simonswain/straw/pull/14#issuecomment-490664865, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADEL3ARIOQZ7FJESWKEMJMLPUNDYJANCNFSM4HLVKZKQ
.


[BUG] Error message when attempting to claim airdrop at app.tangle.tools/claim

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The claim airdrop dapp gives an error when I try to claim an airdrop from my Ledger device using Talisman wallet.

The airdrop remains unclaimed after the error.
Expected Behavior
I expected to receive the airdrop.
Steps To Reproduce

I have attempted this in both Chrome and Opera with the same result
Submit claim using Talisman extension connected to my Ledger wallet (Nano X). Ledger Polkadot address is 1D51dxpuGv1mWxstx7ERWyEWieLHSeQ8NBVX7VxkxT5PuKg.
Specify a recipient address of 5HMnzhxodNNpAW9s2aa4js6ffgcJGBUJgxhKaS1V82CojdHA
Click claim now and approve signing of the text on my Ledger wallet
App immediately shows error message (which goes away almost immediately)

Screenshot
https://github.com/webb-tools/webb-dapp/assets/150610035/038f91a1-2a3f-40eb-b0c5-5d491c271d06
Anything else?
No response

This error is due to Tangle network not being supported by Ledger app, we plan to release a ledger app soon.

We're investigating @validorange and will get back to you to re-test.

After conducting some investigations, I have reached several conclusions:

By default, Ledger employs the ed25519 curve for signing messages. However, in the claim pallet, we use sr25519 to verify signatures from Substrate wallets here.
To verify an Ethereum signature from Ledger, we must modify the last bytes of the signature. For more information, please refer to https://mirror.xyz/coa.eth/mvPbLPXvy375CXi1_XwMTzG84lwlSKYUBHDx_R1TIgU.
In the case of Ledger signatures from Substrate wallets where their length exceeds 64 bytes (65 bytes and 66 bytes), the initial bytes are utilized to detect the cryptographic curve. The subsequent part constitutes the signature itself. You can refer to the signatureVerify function for further details.

For signatures of 65 bytes and 66 bytes, the getVerifyFn and verifyMultisig functions are employed. Initially, the first byte is used to determine the verification function, followed by the utilization of the remaining bytes (with the first byte truncated) as input for the verification function.

Regarding which signature scheme to use when users employ Ledger via Talisman, I'm uncertain. However, based on my research findings, I propose modifying the last byte if the signature is from EVM wallets and truncating the first byte if the signature is from Substrate wallets, whether both are via Ledger.

Hello, @validorange! Could you please try signing and claiming with your Ledger wallet on this PR preview link?


Update action to Node@16

Hey @al-cheb, were you planning to update the action to Node@16? Seems like Node@12 is deprecated and all actions should be updated to 16. Happy to submit a PR if that helps.

#6 would also solve this I guess :)

#6 is a larger change that contains other adjustments and requires more time to review. Let's hear from @al-cheb how he'd prefer to go about it 🙂

@waldekmastykarz , thank you for bringing to my attention it. I have released a new v1.3 version.


Add some Mentimeter polls/quizzes?

As we have a tough engagement issue here, with most interested people being on Zoom, I thought we could scatter a few mentimeter polls and quizzes into the tutorial.
The hope would be that by soliciting some audience feedback we'd keep people interested/awake.

this would also be useful for deciding discussion priorities for many session, do you know how to set it up?

I signed up and I am playing around with it now (at least as much as I can on a weak internet connection on the train!)

Yes, Mentimeter is an excellent idea, I wanted to bring it up in the last meeting but forgot about it.
Should we collect some questions here?

I just realised that the free plan has some limitations (50 participants/month), if I understood correctly.

The wording is interesting - it says you can go over the limit in a single presentation, after which your account blocks until you upgrade.

Yes, kind of sounds like you have only one chance to get it right ;) Btw. they only offer yearly payments, or at least that's the only option I could find...

I have done some really simple quiz questions for the first part of the tutorial tomorrow.
If anyone else wants to use it, I suggest they sign up independently, in case it's a one-shot wonder tomorrow morning!

This was done and it worked. I think it was quite successful as it's a nice pace changer and re-engager after people have been listening to a lecture for some time. Still, it definitely worked better for people in the room - these were pretty much experts, but the discussion was fun. It's just really hard in a hybrid event to engage with the remote participants as much.
Next time I would probably use it more interspersed between each of the sections (but on the day I really didn't want to break anything as were were delivering the material).


Use open-simulation-interface package from ConanCenter

Since the open-simulation-interface package is available on ConanCenter, we should probably remove the versions we have from optional/vtd/vendor.
Tasks:

[x] Check compatibility with different protobuf versions
[x] Update cloe-plugin-vtd

This is already complete, but because open-simulation-interface 3.5.0 and 3.6.0 are not on CCI, we still include our version here.


Document how to pass args to event handlers

This issue was originally reported by @StokeMasterJack via facebook/react/issues/9685
A similar issue was reported by @Frazer via facebook/react/issues/8065
Text of original issue #9685
Inside a loop it is common to want to pass a param to an event handler:
<button onClick={(event) => this.deleteRow(23)}>Delete Row</button>
<button onClick={this.deleteRow.bind(this,23)}>Delete Row</button>

That would be a good thing to add to this doc page:
https://facebook.github.io/react/docs/handling-events.html
Also, how to pass args without triggering a re-render in the child component (i.e. creating a new function every time).

will work on this

This issue is all yours! 😄
I've added an "in-progress" label so that others will know not to start work on the issue. If you change your mind about the issue, no worries! Just let me know so that I can remove the label and free it up for someone else to claim.
Cheers!

This topic was also been suggested for the FAQ in #29, so I included some comments in PR #43 (diff).
It might be a good idea to merge the docs on this subject, or link from one to the other.

I think @hedgerh suggestion should also be included.
Delete Row
deleteRow (e) {
// do some action to (e.target.name)
}

@Frazer added to the FAQ version of this topic: https://github.com/reactjs/reactjs.org/pull/43/commits/b2ef5ff1737b339df61d135d39bf0a9e22869775

Closed by #81 I think

@StokeMasterJack @bvaughn There is also a third way through currying (see How to pass variables to a function reference?, thx @esthercuan)  👍
deleteRow = id => event => {
    console.log('row ${id} deleted');
 }

<button onClick={this.deleteRow(23)}>Delete Row</button>

Thanks for the interesting example. This creates a copy of the function
every time it is rendered, so I'm guessing wouldn't be good when
performance is an issue.
On Tue, Oct 8, 2019, 11:55 PM Guillaume FORTAINE<EMAIL_ADDRESS>wrote:

@StokeMasterJack https://github.com/StokeMasterJack @bvaughn
https://github.com/bvaughn There is also a third way through currying
(see How to pass variables to a function reference?
https://stackoverflow.com/a/50631170, thx @esthercuan
https://github.com/esthercuan) 👍
deleteRow = id => event => {
console.log('row ${id} deleted');

}
Delete Row
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/reactjs/reactjs.org/issues/75?email_source=notifications&email_token=AAC3NQHEHUZMVFBON5ITSNLQNV55LA5CNFSM4D6HFTJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAW26WY#issuecomment-539864923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC3NQFCHELK3CDPCUNGQOTQNV55LANCNFSM4D6HFTJQ
.

how many times do we need to have this debate in react.

@Frazer The overhead of creating a function during render is rarely a performance problem. We do it all the time to add event handlers, map arrays, etc. The new hooks API also makes heavy use of this pattern for hooks like useEffect and useMemo (which require creating a function every render, even if it's not called every render).
When it can be a problem is when it breaks memoization and causes a performance sensitive subtree of your application to re-render when it would otherwise not have re-rendered. This is something the DevTools Profiler UI can help you identify and fix though.