Question: Eye-safety of many D415 cameras used at the same time

Hello,
this is probably a dumb question, but since I am unfortunately not knowledgeable about the subject, I would be happy about any comment from the RealSense team on it: Does the use of many D415 cameras at the same time, with their infrared projectors set to maximum intensity, pose any issue for eye-safety?
Checking the D400 datasheet, it says "The infrared projector meets the Class 1 laser safety standard under normal operation". Wikipedia states on class 1 lasers: "A Class 1 laser is safe under all conditions of normal use. This means the maximum permissible exposure (MPE) cannot be exceeded when viewing a laser with the naked eye or with the aid of typical magnifying optics (e.g. telescope or microscope)."
However, I haven't found a statement on using multiple devices at the same time. For example, using 32 D415 devices in a setup for a volumetric video capture stage, all pointing towards the center of the stage. As a layman, I would guess that the safety of class 1 lasers viewed with "typical magnifying optics" means that at the very least the use of multiple class 1 lasers without any magnifying optics should definitely be safe. But I would be happy about a comment from someone who is knowledgeable rather than relying on my layman's guessing.
Thanks!

Hi @puzzlepaint  The number of 400 Series cameras with projectors equipped that are present in a volumetric setup should not make a difference to eye safety.
If you are still cautious though, if the scene is well lit then you may be able to disable the projector's laser completely.  This is because 400 Series cameras can alternatively use ambient light in the scene to analyse objects / surfaces for depth information instead of using the projector's dot pattern projection.
If you feel that the projector will be required, Intel's white-paper document about projector use with 400 Series cameras states that increasing the Laser Power of the camera's in-built projector from its default of '150' to its maximum of '360' only provides a limited improvement in range.  You could therefore likely achieve satisfactory results with the default Laser Power setting without maximizing it.
https://dev.intelrealsense.com/docs/projectors#section-4-increasing-range
Bear in mind that no matter how many cameras you have in the scene, there will only be one camera at a particular position in the room and so only one laser source from that particular trajectory, not multiple overlaid emissions on the same path.
Point number 3.  Use multiple projectors of the Intel projector white-paper section linked to above confirms that "if each individual projector is rated eye-safe, more can actually be added safely, as they do not originate from the same point source".

You may be interested in the large 100 camera volumetric space called Intel Studios that Intel created at LAX airport in the United States.  Whilst the cameras used are not RealSense and the scale of the room may be larger than your planned volumetric project, the YouTube video at the link below may provide some useful insights about implementing a setup with tens of cameras.
https://www.youtube.com/watch?v=76sehizdvjI

Bear in mind that no matter how many cameras you have in the scene, there will only be one camera at a particular position in the room and so only one laser source from that particular trajectory, not multiple overlaid emissions on the same path.
Point number 3. Use multiple projectors of the Intel projector white-paper section linked to above confirms that "if each individual projector is rated eye-safe, more can actually be added safely, as they do not originate from the same point source".

That makes a lot of sense and clarifies my question. Thank you very much for the detailed reply (and also thanks for the additional info about the Intel Studios setup)! Issue resolved.

You are very welcome  :)


HDFS-16237.Record the BPServiceActor information that communicates with Standby.

Description of PR
When BPServiceActor interacts with StandbyNN, we should record the information of BPServiceActor.
Details: HDFS-16237

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
12m 17s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m 34s

trunk passed

+1 :green_heart:
compile
1m 22s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 18s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 26s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 33s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
5m 18s

trunk passed

+1 :green_heart:
shadedclient
23m 26s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 12s

the patch passed

+1 :green_heart:
compile
1m 15s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 15s

the patch passed

+1 :green_heart:
compile
1m  8s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 51s

the patch passed

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
javadoc
0m 46s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 24s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m  6s

the patch passed

+1 :green_heart:
shadedclient
20m 58s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
235m 26s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

344m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3479/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3479

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 403f8bb0ff0b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / db27430bc1fe892574e051ccb236002b06c484c8

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3479/1/testReport/

Max. process+thread count
3674 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3479/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Checking errors in jenkins don't seem to be too stressful.
@ayushtkn @virajjasani, can you help review this pr?
thank you very much.

@jianghuazhu Thanks for reporting the issue & the patch.
Code changes are fine.
+1

Thanks @prasad-acit for the comment.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 43s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
36m  5s

trunk passed

+1 :green_heart:
compile
1m 24s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 17s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 26s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 27s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 10s

trunk passed

+1 :green_heart:
shadedclient
21m 19s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 14s

the patch passed

+1 :green_heart:
compile
1m 16s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 16s

the patch passed

+1 :green_heart:
compile
1m 10s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 50s

the patch passed

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
javadoc
0m 46s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 12s

the patch passed

+1 :green_heart:
shadedclient
21m  7s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
231m 52s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

331m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3479/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3479

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux c0c39d00203e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / abbb0c384ea30878c6097b78100189ca02f1e3c9

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3479/2/testReport/

Max. process+thread count
3474 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3479/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Hi @tomscut, I have updated some codes. Can you review it again?
thank you very much.

Thanks @tomscut for the comment.

@ferhui, can you help review this pr?
thank you very much.

Thanks @ferhui  for the comment.

Thanks @virajjasani  for the comment.

Thank you @ferhui  for the review.
I don’t know if it is possible to merge into the trunk branch. If the merge requirements are met now, can you help to try.
thank you very much.

@jianghuazhu Generally need to wait for 24 hours to merge after approving.

Okay, thanks @ferhui for the reminder, I may have overlooked this before then.


Fixed namespace issue in opts utility

Simple fix to address #2576.
In the ipython module where the magic is defined, self.shell.user_ns is used as the namespace passed to the parser which is safe as the entire subpackage assumes you are in an IPython environment. In this PR, the IPython namespace is used if available, otherwise it falls back to globals which should be fine outside of an IPython context.

Looks good, should I merge?

I think so. If there are any more issues I expect they would be subtle things to do with namespaces - this new behavior should be correct in the vast majority of cases.


:disabled selector does not apply when input is read-only.

Hello! This issue can be related to https://github.com/twbs/bootstrap/issues/30890, however my problem is different.
It's very easy to reproduce. ":disabled" style for .form-control does not applies if the control is in "readonly" state.
My fix in overriding CSS was following:
.form-control:disabled:read-only {
  background-color: #e9ecef;
  opacity: 1;
}

So .form-control:disabled selector is not enough. You should also add .form-control:disabled:read-only, to make the disabled background applied in readonly state.

Going back through the referenced issues, it looks like this has been mentioned and there seems to be a PR for this problem. Here is the original PR, and I'm not entirely sure if the comment in this file is referencing the issue

Could you please provide a reduced test case using CodePen or JSBin, as stated in our issue template?
FWIW, according to your explanations I don't think this is the same issue: my bet would be that :read-only might be declared after :disabled, thus overriding it. But I'd need a reduced test case to play with :)

Thinking this isn't a problem? The pair of these look the same as disabled and disabled readonly (placeholder on top two, value on bottom two).

@twbs/css-review is this still valid?

Readonly inputs seem to work as expected in v4 and v5


Add substring function alias for substr

Teradata SQL has "substring" function.
For compatibility an appropriate alias was added.
It's pluggable together with other Teradata functions.
Due to existing "SUBSTRING" token used in a grammar production of SUBSTRING(x FROM y [FOR z]) syntax
and clashing registered function name, SUBSTRING token had to become part of a nonReserved rule.
It fixes https://github.com/facebook/presto/issues/4607.

Rebased on master to fetch fix for failing unit test (7c99571dd5c946d362b5d5a82c40b5a400aa9ab0).

Merged, thanks!


feat(USA): Expose EV Trip Details (#473)

The US version of the MyHyundai app shows some details about the most recent trips; extract and expose this.
This change uses the same API call to pull the trip data and add to vehicle.daily_stats. The data in the Hyundai API response matches exactly with the existing EU Vehicle.DailyDrivingStats, so I reused that data structure despite the slight name difference.
A simple example:
#!/usr/bin/env python3

from hyundai_kia_connect_api import *
import pprint

vm = VehicleManager(region=3, brand=2<EMAIL_ADDRESS>password="hunter2", pin="1234")
vm.check_and_refresh_token()

vm.update_all_vehicles_with_cached_state()

for v in vm.vehicles:
    pprint.pprint(vm.vehicles[v].name)
    for s in vm.vehicles[v].daily_stats:
        # Avoid DIV0
        distance = (s.distance if s.distance > 0 else 1)
        # Total watt hours per mile
        whpmi = int(s.total_consumed / distance)
        # "Overhead" (anything except engine) Watt hours per mile
        whpmi_overhead = int((s.climate_consumption + s.onboard_electronics_consumption + s.onboard_electronics_consumption) / distance)
        # Regeneration as a percentage of total consumption
        regen_pct = int((s.regenerated_energy / s.total_consumed) * 100)

        print(f"{s.date} - {s.distance} miles - {s.total_consumed} watt hours - {whpmi} Wh/mi - {whpmi_overhead} Wh/mi overhead - {regen_pct}% regen pct")

    pprint.pprint(vm.vehicles[v].daily_stats)

And output:
$ python3 example.py
hyundai_kia_connect_api - get vehicle location rate limit exceeded.
'2023 IONIQ 5'
2024-01-04 21:11:45 - 1 miles - 509 watt hours - 509 Wh/mi - 320 Wh/mi overhead - 82% regen pct
2024-01-04 20:44:01 - 1 miles - 751 watt hours - 751 Wh/mi - 335 Wh/mi overhead - 72% regen pct

Awesome! Thanks for doing this.  If it appears to be an EV only call maybe it is worth adding an if statement to only place the api call it engine type is ev?

Great! Thanks for doing this.


JavaScript: redux.createStore return type inferred to be any

TS Template added by @mjbvz
TypeScript Version: 4.0.0-dev20200601
Search Terms

redux
typings
javascript
suggest, suggestions

Intellisense not recognising/suggesting for redux store object:

...
Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:33:47.663Z (2 wks ago)
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0

Minimal example:
//@ts-check
const redux = require('redux')

const initialState = { counter: 0 }

const rootReducer = (state, action) => {
    return state
}

const store = redux.createStore(rootReducer, initialState)

The bug is that store is inferred to be of type any. This may be an issue with the redux typings, or with TypeScript's type inference

You can workaround this by giving store an explicit type:
/**
 * @type {redux.Store<{ counter: number }>}
 */
const store = redux.createStore(rootReducer, initialState)

Awesome - thank you.


No matches for kind "ClusterRoleBinding"

Hi [@seglo, Thanks for taking over the repo, if this monitoring for kafka works, it would really be exactly what I am looking for. I am still getting this error that I got before the repo was forked:
> helm install kafka-monitor kafka-lag-exporter/kafka-lag-exporter \
  --namespace kafka-lag-exporter \
  --set watchers.strimzi=true --create-namespace --set serviceAccount.create=true
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "ClusterRole" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "ClusterRoleBinding" in version "rbac.authorization.k8s.io/v1beta1"]

I think from what I remember, if you want strimzi watchers, setting the service account is necesary.
But I thought I would post this as I feel it is a bug

Though I am just thinking, should it be rbac.authorization.k8s.io/v1 and not rbac.authorization.k8s.io/v1beta1?

please note PR here https://github.com/seglo/kafka-lag-exporter/pull/325 to fix.

Fixed in #325


Wrap(nil) should panic

I ran into an ugly bug today where I accidentally did this:
err := stuff()
if err != nil {
  return err
}
result := moreStuff()
if len(result.Failures) > 0 {
  // ... do stuff with failures ...
  return errors.Wrap(err, "Oops")
}

This returns nil because err is nil. The code wanted to make a new err, but it didn't. Due to Go's error conventions, you tend to have a single shared err shared across nested scopes like this, and one has to be careful about what it contains. It took me 10 minutes to realize that err was nil here.
In my opinion, Wrap(nil) should panic, because it makes no sense. The intent of the caller is clearly to wrap an error value (you shouldn't call Wrap if you don't have an error value), and you're telling it to wrap something that doesn't exist. I don't think this is controversial, but I think that, at best, it should return a new error with a nil cause.
I can see an opposite argument that "blanket wrapping" allowed:
return errors.Wrap(doStuff(), "it failed")

However, I think that's a special cause that ought to be relegated to something like MaybeWrap().

I see the justification, but it is too late to make this backwards incompatible change. Sorry.

That is what semantic versioning is for. Just bump the major version, problem solved.

On Oct 28, 2016, at 22:07, Dave Cheney<EMAIL_ADDRESS>wrote:
I see the justification, but it is too late to make this backwards incompatible change. Sorry.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I'm not going to do this. I agree that in a green field situation Wrap(nil) could panic, but in your example
err := stuff()
if err != nil {
  return err
}
result := moreStuff()
if len(result.Failures) > 0 {
  // ... do stuff with failures ...
  return err // not wrapped errors.Wrap(err, "Oops")
}

You still have the same scoping mistake. This is unrelated to the errors package.

But that scoping mistake is much easier to notice, and is semantically not a problem, because err is not being passed on to anything except the caller.
If Wrap() doesn't receive an error, it's accidentally throwing away semantic information in a manner which can be quite difficult to notice. The contract of Wrap() should be to wrap an error, and fail on input that isn't an error. This follows the same good design principles behind fmt.Sprintf() and friends, for example: If Sprintf() receives bad input (such as superfluous arguments), it doesn't ignore it, but signals the problem in its result value. That's just good design.
The likelihood of the scoping issue happening increases due to how Go encourages reusing error variables — protecting it with if x, err := ... often results in quite awkward, overly branching code, and in practice, relatively few err vars can be limited in scope that way. Conversely, I very much dobut that there's much code in the wild that relies on the fact that Wrap(nil) returns nil.
I don't know what greenfield has to do with anything. Semver makes the problem of introducing backwards-incompatible changes a moot point.

I'm sorry, my decision is final.
This package is released under a permissive open source licence, I suggest you fork it and modify it for your requirements.
Thanks
Dave

On 29 Oct. 2016, at 13:35, Alexander Staubo<EMAIL_ADDRESS>wrote:
But that scoping mistake is much easier to notice, and is semantically not a problem, because err is not being passed on to anything except the caller.
If Wrap() doesn't receive an error, it's accidentally throwing away semantic information in a manner which can be quite difficult to notice. The contract of Wrap() should be to wrap an error, and fail on input that isn't an error. This follows the same good design principles behind fmt.Sprintf() and friends, for example: If Sprintf() receives bad input (such as superfluous arguments), it doesn't ignore it, but signals the problem in its result value. That's just good design.
The likelihood of the scoping issue happening increases due to how Go encourages reusing error variables — protecting it with if x, err := ... often results in quite awkward, overly branching code, and in practice, relatively few err vars can be limited in scope that way. Conversely, I very much dobut that there's much code in the wild that relies on the fact that Wrap(nil) returns nil.
I don't know what greenfield has to do with anything. Semver makes the problem of introducing backwards-incompatible changes a moot point.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

I just ran into this exact bug and it swallowed a good hour. I think it would have been better to disallow wrap(nil...) as suggested by @atombender.

I understand, and if I was doing this again today I would not have put in
this convenience.
Sadly, without a functional package management solution for Go, I cannot
break backwards compatability at this time.
On Mon, Oct 16, 2017 at 9:14 PM, Mat Ryer<EMAIL_ADDRESS>wrote:

I just ran into this exact bug and it swallowed a good hour. I think it
would have been better to disallow wrap(nil...) as suggested by
@atombender https://github.com/atombender.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pkg/errors/issues/90#issuecomment-336855949, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA4gR07_G_mEzDwmhmTO9OC7Xx8qEks5sszp6gaJpZM4Kjyfh
.

Understood. I wanted to just contribute some experience. I remember loving that Wrap nil returned nil, but now it reaffirms my obsession with magicless code.
But errors isn't v1 yet is it?

A) It would be bad form for Wrap to panic. https://github.com/golang/go/wiki/CodeReviewComments#dont-panic
B) As for Wrap returning any value other than nil, that is also not a good idea, because then errors.Wrap(nil) != nil will be true.
This would require anyone calling into your library to use pkg/errors.Cause(err) != nil which is a poor choice that forces different error handling code on anyone using your code.
Yes, there is a loss of semantic information, but it is simply not possible to attach any semantic information to a nil error and still ensure that standard Go error checking would continue to work.

Without a functional dependency management solution for Go I have to assume
the 5900 users of this package are pulling from head so any change I make
will have to be backwards compatible for the forseeable future. Sorry.
That's the way the cookie crumbles.
On Mon, Oct 16, 2017 at 9:27 PM, Mat Ryer<EMAIL_ADDRESS>wrote:

Understood. I wanted to just contribute some experience. I remember loving
that Wrap nil returned nil, but now it reaffirms my obsession with
magicless code.
But errors isn't v1 yet is it?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pkg/errors/issues/90#issuecomment-336858673, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcA-m36kqZO0WY31mtsi5w7Ha1hs_Nks5ssz2IgaJpZM4Kjyfh
.

@davecheney just meet this issue, it's very tricky to find out what goes wrong when error gone silently when you accidentally warp an nil error
maybe you can bump a version and denote the incompatible changes?
if panic is a breaking change, at least warp should always return a error

for someone else run into this, I made a simple fork version which add MaybeWarp and Wrap on nil will panic: https://github.com/Ehekatl/errors

@Ehekatl the issue here is that returning a nil err instead of return Wrap(err, …) would present the same issues of difficulty in tracking down such a bug.
I once found a shadowed err bug in some RPC retry code, and it took a lot of work to figure out why the code was returning a non-error when we expected an error condition.
i.e. having Wrap panic on a nil error will not actually solve the root cause of returning a nil error when an error is expected.
Also, consider the following code:
n, err := w.Write(data)
return n, errors.Wrap(err, "error while writing data")

which is comparable to:
return w.Write(data)

vs.
n, err := w.Write(data)
if err != nil {
  return n, errors.Wrap(err, "error while writing data")
}
return n, nil

I consider @puellanivis 's opinions more reasonable. Please allow me to add more reasons against doing so.

panicing on error handling library is against the whole reason of having an error handling library.
The caller then have to do

defer func() {
   recover()...
}()

which makes the code less readable.
Panic recovery should be used in specific cases. panic on Wrap(nil) makes recover a general requirement.

I would consider

n, err := w.Write(data)
return n, errors.Wrap(err, "error while writing data")

without panicing a nice feature to have. err == nil should always be explicitly checked.
If you don't, the semantic, for me at least, is always "I don't care if it's nil."

@puellanivis
Sorry I didn't quite get your idea, I mean warp error should either panic or return a non-nil error, an error library should always report error, not eat it.
I think that certainly help with tracking down bugs.
@CreatCodeBuild
your comments are reasonable, of course err == nil should always be explicitly checked, but the problem is how could I possibly know if I forget doing so?
recover should not be a general requirement in such case, because you should never Wrap on anything nil, it should crash. I do agree it's better not to panic in error handling, but this situation is different. Wrap never expecting nil, the point of panic here is to make a equivalent effect of accessing a nil reference.

I mean Wrap(err) should either panic or return a non-nil error, an error library should always report error, not eat it.

But the error library is not eating any errors. It is strictly keeping the case that a non-error will remain a non-error. Wrapping a non-error, should remain a non-error, and the only way to keep this condition within golang, is: if nil is passed in, nil must come out.

…the point of panic here is to make a equivalent effect of accessing a nil reference.

But we are not accessing a nil reference here. A nil error is a defined and expected state, and using and passing it around as a value should therefore not cause a panic.

I understand the argument, but it does make sense to do something like, return errors.Wrap(json.Unmarshal(data, &v), "unmarshaling response failed")
The idea was that one could wrap an arbitrary error without needing to additionally care if it is nil or not.
The pkg/errors package was never designed as a stop-gap to help people avoid returning a nil error, where they are actually expected/thinking that they should be returning a non-nil error.
This is a fundamental issue/feature/bug of the language itself, and is entirely outside of the scope or ability of pkg/errors to solve. If we “fix“ this behavior, maybe we catch one or two accidental oversights, but we also risk causing panics in code that is otherwise correctly handling errors.

You are right, the problem isn't about the behavior.
It's more of an literal problem, MustX/MaybeY make a perfect sense to avoid misunderstanding.

@Ehekatl The best solution for you at the moment might be writing your own / fork this pkg.
As long as you implement .Cause(err) -> err interface, it should work with this pkg seamlessly


Binder Architecture with Apple's Combine Framework ?

Since ReactiveKit is in the process of API alignment with Apple's Combine framework, and more and more people are using SwiftUI, would it make sense to revisit the Binder Architecture and update it to reflect the use of both frameworks (Combine + SwiftUI)?
I'd find it particularly interesting to understand the impact on existing code as I am slowly learning/moving to Combine and SwiftUI (the latter somewhat forcing the former into light).
The AbsurdGitter sample would be a nice side-by-side comparison, especially if it showed how SwiftUI somewhat aligns with the concepts introduced by LayoutLess in this example.
Thanks!

Maybe we can start a discussion on this 😁 to kick things a little bit further down the road...
So from what I can tell (just getting acquainted with SwiftUI and Combine), it appears that SwiftUI forces the Binding layer into the View declarations with @EnvironmentObject and @ObservedObject. Effectively making the Binding layer sort of obsolete in that context.
I.e. any sort of binding between information provided by a service and a view, in the Binder Architecture, is pushed inside the View's struct declaration in most of the SwiftUI samples I have seen. That couples the model and the view definition very tightly and doesn't give much space to create the view / binding / service separation.
Using an intermediary object that relies on very simple types (String, Int, Bool, etc.) to be included in the View definition and then using that object in the Binding to bridge between the service data and the view data is one way to close the gap between SwiftUI and the Binder Architecture to leave as much of the Service logic hidden from the View.
However this only works well for changes in the "state" model. Actions on the other hand seem to be more difficult to abstract away from the View's struct definition (button clicks that drive an action, for example).
Would love to hear suggestions on how to make this "integration" possible...


FFI regression after Dart 2.14-0.74.0.dev

I'm seeing something weird that looks like it might be an FFI regression in recent Dart builds.
The following code runs fine in Dart 2.14.0-74.0.dev and has done for many releases:
https://github.com/timsneath/win32/blob/ffi-regression/example/wallpaper.dart
It should print out the filename of the current desktop wallpaper on Windows 10, for example:
[C:\src\win32] dart example\wallpaper.dart
Wallpaper path is: C:\Users\tim\AppData\Local\Packages\Microsoft.Windows.Photos_8wekyb3d8bbwe\LocalState\PhotosAppBackground\01815_sunsetneedlev2_2560x1600.jpg

Somewhere between this build and Dart 2.14.0-90.0.dev, it stopped working, and instead the process just fails with exit code 1.
This can be evidenced by a GitHub Actions job like the following test suite run, which runs successfully on older builds, but not on the latest Dart main build:
https://github.com/timsneath/win32/runs/2562872364?check_suite_focus=true
It's possible there's something wrong with my own code, which recent builds of Dart are for the first time exposing, but I can't figure out what is going wrong.
If I debug the code, it exits while trying to retrieve the ptr.ref.vtable.elementAt(4).value property in the line below:
  int GetWallpaper(
          Pointer<Utf16> monitorID, Pointer<Pointer<Utf16>> wallpaper) =>
      Pointer<NativeFunction<_GetWallpaper_Native>>.fromAddress(
                  ptr.ref.vtable.elementAt(4).value)
              .asFunction<_GetWallpaper_Dart>()(
          ptr.ref.lpVtbl, monitorID, wallpaper);

I can't fathom why this would give a different result from different Dart builds, so I'm logging this as a bug in case it rings a bell for you about something that might either have caused a regression, or might point me at something that has changed.
Thanks in advance!

/cc @dcharkes who is the wizard of all matters Dart FFI... :)

The example program works fine in .85 but not in .90 from the archive.
I landed 1 FFI commit in between these versions, so we have a suspect commit.
(I need to fix my Windows setup (SDK checkout, Goma, python, ..) in order to verify that this commit is indeed the cause and figure out what is wrong with it.)

Cause
By adding support for incremental compilation, we inadvertently started considering non-external getters as native fields. This caused them to be transformed and to be included in size calculation.
class COMObject extends Struct {
  external Pointer<IntPtr> lpVtbl;

  Pointer<IntPtr> get vtable => Pointer.fromAddress(lpVtbl.value);
}

sizeOf<COMObject>() turned 16 instead of 8.
Accessing vtable returned  value as if it was written as external Pointer<IntPtr> vtable;.
Fix
Fix is under way: https://dart-review.googlesource.com/c/sdk/+/200640.
Workaround
Change the .vtable into an extension method (requires imports on use sites) or method (requires adding () on use sites). cc @timsneath
Or patiently wait til the fix lands.
And thanks for thoroughly testing the FFI with patterns that are missing in our own test suite! 😅


Stack overflow with GHC 7.4.2

Running the test:
random -j1 "Logic 83 []" "Logic 82 [[]]" "Logic 81 [[Input 5],[Input 6,Input 6],[Input 2,Input 1]]" "Logic 80 [[Input 7,Input 4,Input 2]]" "Logic 79 []" "Logic 78 [[Output 83]]" "Logic 77 [[Output 82],[Output 82],[Input 10,Input 2]]" "Logic 76 []" "Logic 75 []" "Logic 74 [[Output 80],[Output 75],[Input 8]]" "Logic 73 []" "Logic 72 [[Output 75,Output 83,Input 7]]" "Logic 71 [[Output 73,Output 83,Input 10],[Output 83,Input 6,Output 79],[Input 8]]" "Logic 70 [[Output 75]]" "Logic 69 []" "Logic 68 [[Input 1,Output 78],[Output 76,Output 80],[Output 72]]" "Logic 67 [[Output 77,Output 83,Input 6],[Output 69]]" "Logic 66 [[Output 71,Input 2],[]]" "Logic 65 [[Input 2,Output 77],[]]" "Logic 64 [[],[]]" "Logic 63 [[Output 79,Input 7,Output 65],[Output 67,Output 72],[Output 79]]" "Logic 62 [[Input 6,Output 78],[Input 3,Output 83]]" "Logic 61 []" "Logic 60 [[],[Output 62,Output 61,Output 82]]" "Logic 59 []" "Logic 58 [[Output 72],[Input 4,Output 74]]" "Logic 57 [[Input 4],[Output 78,Output 71],[Output 75,Output 76,Output 59]]" "Logic 56 [[Output 59,Input 5,Output 79]]" "Logic 55 []" "Logic 54 [[Input 8,Output 76],[]]" "Logic 53 []" "Logic 52 [[Input 8],[Output 55],[]]" "Logic 51 [[]]" "Logic 50 []" "Logic 49 []" "Logic 48 []" "Logic 47 [[Output 79,Output 58],[],[Output 48,Output 55,Input 6]]" "Logic 46 [[Output 52,Output 70],[Output 60],[Input 2,Input 3]]" "Logic 45 [[Output 52,Output 53,Output 69],[Output 55,Output 64,Output 61]]" "Logic 44 []" "Logic 43 [[Output 69],[]]" "Logic 42 []" "Logic 41 [[]]" "Logic 40 [[Input 1,Input 2]]" "Logic 39 [[Input 6],[],[Output 42,Input 5]]" "Logic 38 [[Output 55,Output 69,Output 41],[Output 57,Output 68]]" "Logic 37 []" "Logic 36 [[],[Output 63,Output 74],[Output 60,Output 71,Output 69]]" "Logic 35 []" "Logic 34 []" "Logic 33 []" "Logic 32 [[Input 5,Output 44,Output 68]]" "Logic 31 []" "Logic 30 [[Output 66],[Output 59,Output 57,Output 42],[Output 57,Output 47]]" "Logic 29 [[Output 55,Output 61,Output 71],[Output 48,Output 61,Output 50],[Output 34,Output 72]]" "Logic 28 []" "Logic 27 [[],[Output 58,Output 59]]" "Logic 26 []" "Logic 25 []" "Logic 24 []" "Logic 23 [[]]" "Logic 22 [[Output 29,Input 6],[],[Output 77,Output 80,Output 62]]" "Logic 21 []" "Logic 20 [[],[Input 5,Input 2,Output 38],[]]" "Logic 19 [[Output 52,Output 41,Output 33]]" "Logic 18 [[Output 61,Output 59,Input 3],[Output 55,Output 35],[Output 46]]" "Logic 17 [[Output 24],[Input 4,Output 74,Output 41],[]]" "Logic 16 [[Output 37,Output 83,Input 9],[Output 51,Output 56],[]]" "Logic 15 [[Output 60]]" "Logic 14 [[],[Output 29],[Output 36,Output 70]]" "Logic 13 []" "Logic 12 [[]]" "Logic 11 []" "Logic 10 [[Output 83,Output 83,Input 6],[Output 34,Output 22,Output 63]]" "Logic 9 [[Output 53],[Output 26],[Output 66]]" "Logic 8 [[Output 46],[],[]]" "Logic 7 []" "Logic 6 [[Output 60,Output 75,Output 8],[Output 35,Output 74],[Output 57]]" "Logic 5 [[Output 50,Output 69,Output 80]]" "Logic 4 [[Output 57,Output 13]]" "Logic 3 []" "Logic 2 [[Output 37,Output 45],[Output 64,Output 35],[Output 36,Output 56,Output 42]]" "Logic 1 []" "Want [83,82,81,80,79,78,77,76,75,74,73,72,71,70,69,68,67,66,65,64,63,62,61,60,59,58,57,56,55,54,53,52,51,50,49,48,47,46,45,44,43,42,41,40,39,38,37,36,35,34,33,32,31,30,29,28,27,26,25,24,23,22,21,20,19,18,17,16,15,14,13,12,11,10,9,8,7,6,5,4,3,2,1]" "Want [65,65]" "Want [56,50,74]" "Want [61]" "Want [66,71]" "Want [70,67,62]" "Want [10,70,41,59]" "Want [26,45,53]" 3m

Gives a Stack overflow.

To get it happening reliably I need to rm output/random/.shake.database first.

It takes somewhere in the range 2.5K-3K stack when run normally. Unfortunately adding -auto-all makes the stack usage reduce < 1K once more.

@ndmitchell Uhh...there's something weird about the data you posted:

Unfortunately with -auto-all at -O0 and -O2 it works in < 1K, so the techniques from http://neilmitchell.blogspot.co.uk/2015/09/detecting-space-leaks.html don't shed any light. I might need to blow away everything first and have it recompile though.

@kirbyfan64 - I think it's just really long lines that get messed up by the browser.

Running the test suite normally, without -prof -auto-all, at -O0 it works fine but at -O1 or -O2 it fails. Seems like there is a bug in GHC 7.4 that when some particular code is compiled with optimisations it introduces a space leak. I'm sure it could be tracked down, but it's certainly not going to be fixed (I have severe doubt I can persuade the GHC team to release a GHC 7.4.3!) so I'm just going to not apply the stack overflow checks.


Srcset documentation

Hi,
Can you please expand a bit on the srcset documentation?
Thanks!
Darren

Hi @darren131,
Currently don't have much time, so it will probably be some time before I get to it.
Feel free to send a pull request.

Hi @darren131
Hope this code helps you!
First set som transforms, this example is only scaling the width of the image. You can read more about the API here. We also format, compress (auto), convert the Color Space (cs) to srgb and then sharpen the image (sharp).
{% set transforms = [
    {
        w: 800,
        auto: 'format,compress',
        cs: 'srgb',
        sharp: 10
    },
    {
        w: 600,
        auto: 'format,compress',
        cs: 'srgb',
        sharp: 10
    },
    {
        w: 400,
        auto: 'format,compress',
        cs: 'srgb',
        sharp: 10
    },
    {
        w: 291,
        auto: 'format,compress',
        cs: 'srgb',
        sharp: 10
    }
] %}

{% set transformedImage = craft.imgix.transformImage( image, transforms) %}
{{ transformedImage.srcset({ 'class': 'any-CSS-class', 'alt': image.title, 'itemprop': 'image' }) }}

If you want to crop the image
    {
        w: 800,
        h: 600,
        auto: 'format,compress',
        crop: 'center,center',
        fit: 'crop',
        cs: 'srgb',
        sharp: 10
    }

How do I use defaultSettings? Lets say I use the example above but instead I want to use (instead of repeating myself):
{% set imageOptions =
    {
        cs: 'srgb',
        auto: 'format,compress',
        crop: 'top,right',
        fit: 'crop',
        cs: 'srgb',
        sharp: 80
    }
%}

I thought this would work... but no luck
{% set transformedImage = craft.imgix.transformImage( image, imageSizes, imageOptions ) %}

@skramstad I think that was a bug. Could you try again?

@sjelfull I believe this issue was because it was not implemented yet. But it's working now!

@skramstad Kool. Yeah, that is the "bug" I had in mind 😁


build(deps): bump nest.js from 7 to 9

To keep the commit history clean, I recommend that you pull the most recent changes to the base branch (i.e. development) before creating the feature branch.
$ git fetch origin --prune
$ git rebase origin/development


pretrained weights

Hi, is there any possibility of releasing a pre-trained weights file?

updated.


Adding a demo notebook to showcase the Energy Balance Model

For SIO Climate Journal club presentation of the MARGO paper.

@fonsp, this is awesome! I even was able to understand the javascript well enough to retool some of your functions.

@fonsp, for some reason the @bind Slider reactivity is hit-or-miss. It worked last time I ran the notebook but this time the sliders don't do anything and the variables just stay at their default values. Could you look into it? If it works for you than we can ship the notebook as is and I'll present it on Thursday!

@fonsp, I realized the problem was that I have mistakenly copied the standard Pluto.jl header
using Markdown
using InteractiveUtils

# This Pluto notebook uses @bind for interactivity. When running this notebook outside of Pluto, the following 'mock version' of @bind gives bound variables a default value (instead of an error).
macro bind(def, element)
    quote
        local iv = try Base.loaded_modules[Base.PkgId(Base.UUID("6e696c72-6542-2067-7265-42206c756150"), "AbstractPlutoDingetjes")].Bonds.initial_value catch; b -> missing; end
        local el = $(esc(element))
        global $(esc(def)) = Core.applicable(Base.get, el) ? Base.get(el) : iv(el)
        el
    end
end

into a cell within the ebm.jl notebook itself. This understandably broke the bind macro's reactivity.
Everything is now working as expected!


Range-versioned dependencies are not correctly found with overridden repos configuration

steps
@joescii reproduced it on https://github.com/joescii/sbt-reproduced/tree/issue-752
original report
Depending on a Maven artifact, which depends transitively on a range-versioned dependency, doesn't work if repos configuration is overridden.
SBT launcher: 0.12.3
With default repos configuration:
[info] Resolving org.avaje.ebeanorm#avaje-ebeanorm-agent;[3.1,4) ...
...
[info] downloading http://repo1.maven.org/maven2/org/avaje/ebeanorm/avaje-ebeanorm-agent/3.2.1/avaje-ebeanorm-agent-3.2.1.jar ...
[info] 	[SUCCESSFUL ] org.avaje.ebeanorm#avaje-ebeanorm-agent;3.2.1!avaje-ebeanorm-agent.jar (7ms)

With overridden repos configuration:
[info] Resolving org.avaje.ebeanorm#avaje-ebeanorm-agent;[3.1,4) ...
[warn] 	module not found: org.avaje.ebeanorm#avaje-ebeanorm-agent;[3.1,4)
[warn] ==== local: tried
[warn]   /home/jenkins/.ivy2/local/org.avaje.ebeanorm/avaje-ebeanorm-agent/[revision]/ivys/ivy.xml
[warn] ==== maven-central-cloudbees-mirror: tried
[warn]   http://repo.cloudbees.com/content/groups/public/org/avaje/ebeanorm/avaje-ebeanorm-agent/[revision]/avaje-ebeanorm-agent-[revision].pom
[warn] ==== sonatype-snapshots: tried
[warn]   https://oss.sonatype.org/content/repositories/snapshots/org/avaje/ebeanorm/avaje-ebeanorm-agent/[revision]/avaje-ebeanorm-agent-[revision].pom

Notice the [revision] in URLs, which is not substituted by right revision.

Yo, @jsuereth... It's easily reproducible here.

@joescii,thanks! Hope it get fixed soon

@joescii Thanks for the repro case.
In both yours in the original case, the dynamic revision is specified incorrectly according to Ivy's dependency, which different from Maven's Version Range Specification.

Resolving org.avaje.ebeanorm#avaje-ebeanorm-agent;[3.1,4)
Resolving rubygems#middleman-core;[3.3.7,<IP_ADDRESS>.<IP_ADDRESS>)

In other words, you need [ to mean less-than instead of ).
Maybe we should issue a warning about this, but this is not a bug as far as sbt is concerned.

I see... So the repos in the overrides must be ivy style whereas a resolver can be either?
Joe
Sent from my iPhone

On Jan 16, 2015, at 22:21, eugene yokota<EMAIL_ADDRESS>wrote:
@joescii Thanks for the repro case.
In both yours in the original case, the dynamic revision is specified incorrectly according to Ivy's dependency, which different from Maven's Version Range Specification.
Resolving org.avaje.ebeanorm#avaje-ebeanorm-agent;[3.1,4)
Resolving rubygems#middleman-core;[3.3.7,<IP_ADDRESS>.<IP_ADDRESS>)
In other words, you need [ to mean less-than instead of ).
Maybe we should issue a warning about this, but this is not a bug as far as sbt is concerned.
—
Reply to this email directly or view it on GitHub.

@joescii I've been looking into this more.
As you suggested, sbt does support Maven repository on its resolvers, so it should handle Maven's version semantics.
There are some puzzling things, however. I tried running your repro case locally, and my failure is different from what's on your README:
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: rubygems#middleman;3.3.7: rubygems-release: unable to get resource for rubygems#middleman;3.3.7: res=http://rubygems-proxy.torquebox.org/releases/: java.text.ParseException: null in file:/var/folders/xxx/xxx/T/ivy6973646341199185799xml
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn]  Note: Unresolved dependencies path:
[warn]    rubygems:middleman:3.3.7 (/xxx/xxx/sbt-reproduced/build.sbt#L12-15)
[warn]      +- com.joescii:sbt-reproduced-752_2.11:0.0.1-SNAPSHOT
sbt.ResolveException: unresolved dependency: rubygems#middleman;3.3.7: rubygems-release: unable to get resource for rubygems#middleman;3.3.7: res=http://rubygems-proxy.torquebox.org/releases/: java.text.ParseException: null in file:/var/folders/xxx/xxx/T/ivy6973646341199185799xml

Next I went looking for other examples of Maven version range.
# if you have silver searcher
$ ag '<version>\[' ~/.ivy2/cache | less
# if not, the slow version
$ grep -R '<version>\[' ~/.ivy2/cache

One I found is:
libraryDependencies += "com.amazonaws" % "aws-java-sdk" % "1.2.6"

pom contains:
<dependency>
  <groupId>commons-logging</groupId>
  <artifactId>commons-logging</artifactId>
  <version>[1.1, 2.0)</version>
</dependency>
<dependency>
  <groupId>org.apache.httpcomponents</groupId>
  <artifactId>httpclient</artifactId>
  <version>[4.1, 5.0)</version>
</dependency>

When I run this, sbt seems ok with the versions:
[info] Resolving commons-logging#commons-logging;[1.1, 2.0) ...
[info] Resolving commons-logging#commons-logging;[1.1, 2.0) ...
[info] Resolving org.apache.httpcomponents#httpclient;[4.1, 5.0) ...
[info] Resolving org.apache.httpcomponents#httpclient;[4.1, 5.0) ...
...
[info] Done updating.

Then it finally dawned on me 5:00 in the morning that the problem could be in your repositories file:
[repositories]
  local
  typesafe-releases: http://repo.typesafe.com/typesafe/ivy-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]
  sbt-plugin-releases: http://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]
  rubygems-release: http://rubygems-proxy.torquebox.org/releases/,
  maven-central-releases: http://repo1.maven.org/maven2

Sure enough you have an extra comma after the URL without specifying the repository layout.
I removed the comma, and sure enough, the middleman started resolving:
[info] Resolving rubygems#middleman;3.3.7 ...
[info] Resolving rubygems#middleman;3.3.7 ...
[info] Resolving rubygems#middleman-core;[3.3.7,<IP_ADDRESS>.<IP_ADDRESS>) ...
[info] Resolving rubygems#middleman-core;[3.3.7,<IP_ADDRESS>.<IP_ADDRESS>) ...
[info] Resolving rubygems#bundler;[1.1,1.99999] ...
[info] Resolving rubygems#bundler;[1.1,1.99999] ...

That's funny because at some point I added the comma to get it to work at all.  Maybe I had some other problem and I never went back to undo the unneeded comma.  I removed it and it seems to work here.  Now I've got to figure out what I've done wrong with my repos file at work.
Glad this old issue can be closed tho. :+1:

Please reopen this bug. Doing a packet capture with tshark, it seems that the problem is actually that sbt - when a version from a range is requested - literally retrieves a directory listing from the proxy repository, but a directory listing from Nexus only lists the versions that Nexus has currently proxied, not all versions. So a workaround is to manually request a particular version from Nexus, and then it will work thereafter - which explains why this bug has been so hard to reproduce. (Another factor that would make it hard to reproduce is if you didn't delete your ivy cache, you wouldn't see it again after that version had been downloaded.)

@greenrd Which sbt version did you use? The screen scraping behavior is an Ivy fall back when it can't find maven-metadata.xml, but until 0.13.9 (#2075) sbt had been falling back every time because we customized the repository pattern.
Whether sbt uses maven-metadata.xml or does the screen scraping, the issue remains that it probably won't find the latest version when it hits the proxy. I personally think that's exactly how it should behave since that's what it found on the repository.

@eed3si9n I'm using sbt 0.13.8 so that makes sense.
So you think that my workaround should be the correct way to deal with this problem? Surely Maven must have a better way of dealing with this issue?
Anyway, I will try using 0.13.9. Maybe Nexus merges the maven-metadata.xml so maybe it will work.

Yes, it works in 0.13.9 - thanks @eed3si9n! I assume that it downloads maven-metadata.xml from the proxied repo.


Add domain specific evaluation of predictions

Add evaluation.py, which performs an evaluation of a (fine-tuned) model based on our domain specific expected behavior. For this, treat a prediction as a kind of multiclass multioutput classification of its chat history. A prediction is parsed into a set of calls, each having a sequence of arguments.
Since evaluation.py is very different from the perplexity based evaluations in the evaluate folder, and expects a dataset that can be created with other scripts in this folder, put evaluation.py in this folder, too.
Add README.md to describe this prediction-evaluation-pipeline.
TODO:

add cosine similarity comparisons where similar text (e.g. the msg argument) is sufficient.
construct a full confusion matrix and report it to tensorboard.

Sorry, this PR meant to merge into a fork.


KinematicCollision.get_local_shape() always returns the KinematicBody's first CollisionShape

Godot version:
3.1.1
OS/device including version:
macOS 10.14.5
Issue description:
KinematicCollisions returned by KinematicBody.move_and_collide or get_slide_collision will always return the acting KinematicBody's first CollisionShape as the local_shape, even if that CollisionShape is disabled, sizeless, or otherwise incapable of colliding with anything.
Steps to reproduce:
Create a KinematicBody with two CollisionShapes, disabling the one which is first in the child node hierarchy or, alternatively, arranging them such that only one could collide with your chosen target.
Move the KinematicBody to collide with the target via a method of your choice.
Get the local_shape of the KinematicCollision. It will invariably be the first CollisionShape in the KinematicBody's child node hierarchy.

I was able to reproduce the issue with Godot 3.1.1 on 64-bit Windows 10 (version 1903). The attachment has a small test project that demonstrates the problem.
KinematicCollisionLocalShape.zip

GodotPhysic is fine, happens only in bullet physics.

CC @AndreaCatania

This exact issue Appears again in Godot 4, I Tested in Godot 4.0.1.stable and 4.1.stable and both got the same issue


cli: improve coverage

Close #1576.

Where is codecov when we really need it?

Codecove job is also adjusted.


Can't run on Debian 10

I downloaded the binary, but when I try to run, I get an error:
# /usr/bin/youtubedr
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /usr/bin/youtubedr)

This is the last release of Debian and I have no way to update the glibc.

@aufr33  can you try ldd --version to see what version of GLIBC you currently use?
I am thinking we might need to use go 1.13 or go 1.12 to build youtubedr binary.

ldd (Debian GLIBC 2.28-10) 2.28

solved by f10c54c5e122c1fba390ca72da949d805fd4f3fe

cool thx a lot.


Smarty support

Why you're ignoring smarty? Please support it.

I'm not familiarized with smarty, but if you want to work in a pull request, I'd happy to include it.

@aolko its working with https://github.com/smarty-gettext/smarty-gettext

@aolko @oscarotero
I've written a "function scanner" for smarty tpl files. It's kinda hacky but works for single strings with the smarty {t}MY STRING{/t} syntax. No comments and plural forms are implemented yet.
Usage:
Gettext\Extractors\Tpl::fromFile($file_path, $translations);
gettext.zip


modem: gsm_ppp: CONFIG_GSM_MUX: Unable to reactivate modem after executing gsm_ppp_stop()

Initially after reboot the LWPA modem works correctly and following is reported according GSM muxing:
[00:00:12.477,386] <dbg> modem_gsm: gsm_configure: GSM muxing enabled
[00:00:12.494,262] <dbg> modem_gsm: mux_attach_cb: DLCI 0 to GSM_0 connected
[00:00:12.502,075] <inf> sample_gsm_ppp: gsm state: 5, net_state: -1
[00:00:12.512,176] <dbg> modem_gsm: mux_attach_cb: DLCI 1 to GSM_1 connected
[00:00:12.530,059] <dbg> modem_gsm: mux_attach_cb: DLCI 2 to GSM_2 connected
[00:00:12.531,188] <inf> modem_gsm: PPP channel 1 connected to GSM_1

But when stopping the modem by executing gsm_ppp_stop() and restarting again by gsm_ppp_start() following is reported according GSM muxing:
[00:01:53.272,338] <dbg> modem_gsm: gsm_configure: GSM muxing enabled
[00:01:53.295,593] <inf> sample_gsm_ppp: gsm state: 4, net_state: -1
[00:01:53.585,449] <dbg> modem_gsm: mux_attach_cb: DLCI 0 to GSM_0 disconnected
[00:01:53.585,510] <dbg> modem_gsm: mux_attach_cb: DLCI 0 to GSM_0 disconnected
[00:01:53.595,825] <inf> sample_gsm_ppp: gsm state: 5, net_state: -1
[00:01:53.899,627] <dbg> modem_gsm: mux_attach_cb: DLCI 1 to GSM_1 disconnected
[00:01:53.899,688] <dbg> modem_gsm: mux_attach_cb: DLCI 1 to GSM_1 disconnected
[00:01:53.996,093] <inf> sample_gsm_ppp: gsm state: 6, net_state: -1
[00:01:54.213,806] <dbg> modem_gsm: mux_attach_cb: DLCI 2 to GSM_2 disconnected
[00:01:54.213,867] <dbg> modem_gsm: mux_attach_cb: DLCI 2 to GSM_2 disconnected
[00:01:54.214,965] <inf> modem_gsm: PPP channel 1 connected to GSM_1

As a result of this DLCI disconnected state, the serial receive interrupt seems to be no more enabled, the driver sends AT commands but noting is received anymore until the SoM (not the modem) is rebootet.
Platform used: nRF52840DK with a SIMCOM SIM7080G LPWA module.


Wording on tabs of "Create Request" process (enhancements and maybe one bug)

Testing Environment:
Windows 10, Google Chrome 73.0.3683.86 (64bit), 15.6", 1920х1080
Steps to reproduce:

Navigate to http://rfai.singularitynet.io.s3-website-us-east-1.amazonaws.com/
Press "Create" button in the right upper corner of the page
Observe the result

Possible points for improvement:
Tab "Overview"
Maybe such text will be more accurate

You can request for any AI Service that you would like to see built on top of the SingularityNet platform. Requests should be detailed enough to allow discussion and development and should be in the form of a GitHub pull requests to the repository. You can view the template for the request here
We would like to have an objective and measurable acceptance criteria (get accuracy above X% of this data, etc). The foundation will review and approve requests which will appear on here

Tab "Process"
Maybe such text will be more accurate

Raise a GitHub pull request based on the template to
Provide a title and description along with the URL of the GitHub pull request
In order to incentivize people to develop solutions we require that you back your requests with AGI tokens. The tokens will be distributed to the accepted solutions. See the Submission Evaluation process for more details
Provide an expiry date for the request. Meaning the date post which you can withdraw your funds if no submission has been made
Also the sentence "Raise a GitHub pull request based on the template to" looks like unfinished so I suppose it can be some bug

Please see the video below

@raamb Can you please suggest from the content perspective.


handle Technology selected without any Projects

From MarineEnergy.app_Review_GCS_120921.docx - Google Docs:

Projects page – an error occurs if one selects a technology that is not available (e.g., Current or Offshore Wind). Only Riverine, Tidal, and Wave work. We need to have a solution for this.

SOLUTION
Present something like:
Sorry, the Technology {tech-selected} does not match any available Projects. Instead, please select one of the following available technologies: {tech-available-list}.
Preferably:

color code (i.e. blue banner) each Technology

Step 1. Empty Map & Timeline

Step 2. Add message to app
Here:

using:

conditionalPanel() in ui.R
reactiveValues() in server.R for some variable like msg_projects starting with value of NULL and then if a condition arises replacing or appending to show.
ixn_to_colorhtml() in scripts/shiny_report.R

Select OTEC

Get message without Map or Timeline

Add Riverine

Get message still for OTEC, but Map and Timeline show for Riverine


fix(schema): add missing models

Pull Request Test Coverage Report for Build 414322043

1 of 2 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 49.238%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

queenbee/job/init.py
0
1
0.0%

Totals

Change from base Build 414058840:
-0.02%

Covered Lines:
1357

Relevant Lines:
2756

💛  - Coveralls


unauthorizedRedirectUrl service option is not respected

[x] CAS server version
[x] Container/environment type/version (Tomcat, Jetty, Java, Linux/Windows, etc)
[x] Steps to duplicate the problem along with your CAS settings and properties
[x] Stacktraces and CAS DEBUG logs where appropriate.
[x] Configuration/Overlay pushed to https://github.com/cas-projects/cas-issues/ or attached to the issue.

Cas server version: 5.1.0
Container version/env: Tomcat 8.5.11
When using a CAS RegEx service such as the one below which denies access via requiredAttributes:
{
  "@class" : "org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(https|imaps)://.*",
  "name" : "HTTPS and IMAPS",
  "id" : 10000001,
  "description" : "This service definition authorizes all application urls that support HTTPS and IMAPS protocols.",
  "evaluationOrder" : 10000,
  "proxyPolicy" : {
      "@class" : "org.apereo.cas.services.RefuseRegisteredServiceProxyPolicy"
  },
  "evaluationOrder" : 10,
  "usernameAttributeProvider" : {
      "@class" : "org.apereo.cas.services.DefaultRegisteredServiceUsernameProvider"
  },
  "logoutType" : "BACK_CHANNEL",
  "attributeReleasePolicy" : {
      "@class" : "org.apereo.cas.services.ReturnAllAttributeReleasePolicy",
      "authorizedToReleaseCredentialPassword" : false,
      "authorizedToReleaseProxyGrantingTicket" : false
  },
  "accessStrategy" : {
      "@class" : "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
      "enabled" : true,
      "ssoEnabled" : true,
      "unauthorizedRedirectUrl": "http://www.google.com",
      "requiredAttributes" : {
          "@class" : "java.util.HashMap",
          "cn" : [ "java.util.HashSet", [ "different" ] ]
    }
  }
}

If the user who logs in has a cn value of "testing" for example, the login fails with the message: "Invalid Credentials"
It is my understanding that the unauthorizedRedirectUrl parameter is used to redirect the client on failure and while it is set in the service, the redirection is not happening.
Debug logs of failed session: https://gist.github.com/petracvv/272d5cbb221ee7768a4b090b70fa0f1b
I will push an overlay containing the config I was using to reproduce the issue.

Sounds like a bug.
Thanks for the logging the issue report. Please investigate the problem, evaluate and analyze your logs at DEBUG level and whenever reasonable, file a pull request to address this case.


Web configuration interface

Need to decide on a frontend stack and how we're gonna compartmentalize the various settings into categories and stuff like that. A whole lot of organization needs to go into this.
Ideally we could have some sort of module-like internal interface where each part of the bot can live in its own directory and provide Discord commands and provide configuration hooks through a standard format used by all parts of the bot. This would help naturally separate commands and their settings in a consistent way across the bot. (#14)

The web interface definitely exists now - closing this since it doesn't really have much other point and #14 has a clearer purpose that hasn't been accomplished yet


Update wdtk-datamodel, wdtk-dumpfiles, ... to 0.14.5

About this PR
📦 Updates

org.wikidata.wdtk:wdtk-datamodel
org.wikidata.wdtk:wdtk-dumpfiles
org.wikidata.wdtk:wdtk-rdf
org.wikidata.wdtk:wdtk-storage
org.wikidata.wdtk:wdtk-util
org.wikidata.wdtk:wdtk-wikibaseapi

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

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.14.0).
You might want to review and update them manually.
website/yarn.lock

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

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

labels: library-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #496.


Should we guard against including pico/platform.h

I've seen a couple of cases where code is including "pico/platform.h" which causes the wrong defines for pico_w. The right thing to do is include pico.h? Should we guard against this?

This has been done - should throw an error.


Update Element Template Feature broken

Describe the Bug
Update Element Template Feature broken
Steps to Reproduce

Have multiple templates from Cawemo synced
Apply one template
=> note that even though the template does not have a newer version, one can apply a new version. => the actual template is changed

(It seems the update logic does not filter on template id?)
Expected Behavior
Update element template logic only available for template with the same ID (and multiple versions)
Environment
https://github.com/bpmn-io/bpmn-properties-panel/pull/161

It seems that we'd need to re-render the templates group whenever templates are changed.


APEXMALHAR-2409 PojoInnerJoin accumulation to emit a POJO

@tushargosavi Please review and merge.

Fix following checkstyle error.
src/test/java/org/apache/apex/malhar/lib/window/accumulation/PojoInnerJoinTest.java:[170,47] (whitespace) NoWhitespaceAfter: ')' is followed by whitespace.

@tushargosavi Done the changes


How to compile?

Hi,
How should I compile the project BlazorSample?
I get these errors during compilation:
Severity	Code	Description	Project	File	Line	Suppression State
Error (active)	CS0246	The type or namespace name 'ComponentMetadata' could not be found (are you missing a using directive or an assembly reference?)	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	34
Error (active)	CS0246	The type or namespace name 'ComponentMetadata' could not be found (are you missing a using directive or an assembly reference?)	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	39
Error (active)	CS0246	The type or namespace name 'ComponentMetadata' could not be found (are you missing a using directive or an assembly reference?)	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	47
Error (active)	CS0246	The type or namespace name 'ComponentMetadata' could not be found (are you missing a using directive or an assembly reference?)	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	51
Error (active)	CS0246	The type or namespace name 'ComponentMetadata' could not be found (are you missing a using directive or an assembly reference?)	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	55
Error (active)	CS0103	The name 'RocketLabWithWindowSeat' does not exist in the current context	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	67
Error (active)	CS0103	The name 'APP' does not exist in the current context	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	75
Error (active)	CS1073	Unexpected token 'NAMESPACE'	BlazorSample	C:\yi\blazor\ms-blazor-samples\6.0\BlazorSample_Server\Pages\dynamiccomponent\DynamicComponentExample2.razor	75

Many thanks,
Yi

Yeah im getting the exact same error.

I just found these over here. It wasn't the best spot to open an issue because these samples are all linked into the Blazor doc set, and that's where we normally work. However, no worries ... I'll see if I can address this today (6/16). I'll respond back later today.


Sign out prompt to save URL + code styling

Moved sign out modal to its own component.

Show warning if there is session data user will lose when signed out.
Add "Copy URL" button to copy the link to save session data.

Add code styling.
Write Log text in markdown to support code because we can't use components there (logs are mostly in helper files, without JSX).
Parse markdown to sanitized HTML in Logs view.

Preview is available here:http://stellar-demo-wallet-pr127.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-demo-wallet-pr127.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-demo-wallet-pr127.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-demo-wallet-pr127.previews.kube001.services.stellar-ops.com/


Request for new GH repo, "rufio"

As we at AWS (mainly @pokearu) have looked into refactoring PBnJ to run as a kubernetes controller (tinkerbell/pbnj#121), the paradigm is very different from the current "PBnJ as a server" architecture. I have a branch of pbnj adding some kubebuilder-generated scaffolding, but it became obvious to me that almost no code will be re-used, and there is a lot of modification to get the kubebuilder generated pieces to play nice. PBnJ has make targets that overlap with the kube-builder generated makefile, and existing make targets like make image would need to be refactored for multiple images.
Given the difference in architecture and maintenance, I propose a new GitHub repo. This is similar to how Hook replaced OSIE.
I propose the name "Rufio" after the character from the 1991 movie Hook.

Loving Rufio

How would we describe Rufio, and most importantly what is the backronym?

The goals are largely the same, but the implementation and architecture is the difference.
Goals:

Declaratively enforce and ensure BMC state such as:

Power state
Persistent boot order
NTP/LDAP/TLS Cert configuration (probably future scope)

Declaratively enact actions such as:

Power reset
Configure ephemeral boot order

Report state such as:

Firmware version
Other Redfish/Swordfish machine metadata

Implementation

Kubernetes-based controller instead of gRPC server
AuthN/Z is enforced with Kubernetes Authentication/RBAC instead of a gRPC API
BMC authentication is managed with Kubernetes Secrets instead of passed through per-request by clients

How would we describe Rufio, and most importantly what is the backronym?

Rufio is a declarative state manager for BMCs.
Rufio is the leader of the Lost Boys in the 1991 movie Hook.

Rufio is the leader of the Lost Boys in the 1991 movie Hook.

If we're going to re-brand PBnJ (or fork it) I would like to throw out the name "dust"
Pixie dust is the magic of flying in the clouds (as long as you have happy thoughts).
If you want a backronym
D ust
U pdates
S tate for
T inkerbell
I :heart: Rufio. It has been 31 years and it's still too soon :cry:
I'm fine with either (they're both better than PBnJ) but wanted to suggest my idea from last year.

So the name tinkerbell I believe was chosen due to the fact that the whole platform is powered by PXE dust. 😂

I have no idea how I didn't even know that was a repo. I retract my suggestion. That would be very confusing.

What about 'brig' or 'roger'. Captain hook sailed a brig named Jolly Roger

For a backronym:
Rufio
Utilizes
Fancy
IPMI
Operations

I'm asking the CNCF for recommendations on the rufio name.
#15 is one of the first steps there.

Closing this now that we have the repo

Request for CNCF clarity submitted: https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-1261


NetManager.PollEvents Exception and Crash on Nintendo Switch

I've got a weird crash/Exception occuring on a Nintendo Switch game, while puting the game in the background when coming back to it:

Attached a stacktrace showing the
_netEventsQueue.Dequeue()

call throwing an Empty Exception.
Seeing at the code of the PollEvents method and the 2 lock() sections, i can only imagine a different Thread Removing elements from the Queue, or Clear() while Shuting down due to inactivity in the background?
Right now i just tried to try/catch my PollEvent() call, and i didn't managed to reproduce the crash, but this kind of bugs are hardly easy to reproduce.
protected NetManager _netManager;
void Update()
{
     _netManager?.PollEvents();
}

Library version: [release version (<IP_ADDRESS>)]
Framework: [Unity 2021.3.12f1 Nintendo Switch platform (LiteNet sources included into the project)]
OS: [Nintendo SDK 12.3.11]

I had a similar 'queue empty' issue a while ago. In my case this was caused by a client disconnection while processing received packets. It got fixed by this commit https://github.com/RevenantX/LiteNetLib/commit/3f6a1911796ed0476f069c530c6a8a2d0ef07eb9
It's possible that this applies to your older library version

@Vonak should be fixed by latest LiteNetLib version 1.0.1.


CkIO is not SMP safe

Original author: Thomas Quinn
Original issue: https://charm.cs.illinois.edu/redmine/issues/550

The Manager constructor in ckio.C sets the global variable "manager" to the "this" pointer.  All accesses
through "manager" on the node will refer to the same Manager object: the last one to call the constructor.
In particular the call to mananger->get(file_) at the top of the WriteSesson constructor can be executed by many PEs at once leading to a race condition on "files[token].fd" and the CmiOpen()s.  The result is that a file can be opened many times on the same node.  The Manager::doClose() method is executed in serial, so the file only gets closed once.  The end result is that a program using CkIO (e.g. ChaNGa) running on an SMP machine runs out of file descriptors and crashes.
I've got a kludgy fix: putting a CmiLock() around the if() block at line 192 in ckio.C.  This let's ChaNGa run without crashing; however, I think there is a deeper design problem here that needs to be addressed.
I need this working for my big runs on Blue Waters, so let me know if you want to see my fix on gerrit.

Original date: 2014-09-04 05:25:50

The right fix would be for Manager *manager to be Ckpv instead of a simple global, so that each PE points at its own instance of the group. If you're comfortable implementing that, please assign this to yourself and go ahead. Otherwise, please assign it to Ronak.

Original author: Thomas Quinn
Original date: 2014-09-04 17:42:45

Proposed patch is at http://charm.cs.uiuc.edu/gerrit/364

Original author: Thomas Quinn
Original date: 2014-09-17 22:05:52

The patch has been merged.


TDVP improvements

I already changed a few minor things in dad01750aa019e7415a4ded2d0b431594f9f4481, but the TDVP code still needs some improvements.

[ ] The test should work for any seed, but it fails e.g. for the seed 31415.
[ ] The "bigger" interface should be the same as for TEBD.
-> same parameter structure! trunc_params, N_steps in TDVP_params
[ ] sort methods by what the "enduser" needs to call: put run_* directly after init.
[ ] Clean up: remove unneeded varibales/arguments, e.g. spectrum.
[ ] Document every function, including the arguments.
[ ] Document Class attributes.
[ ] Using different order of indices might help to avoid unnecessary transposes -> speedup!
[ ] calculate_error_left_right should either return something or not be present?
[ ] No need to convert everything to numpy in the tests. Just use tenpy MPS.overlap

One minor fix: The reference [Haegeman2014]_ should read [Haegeman2016]_ (since the paper was only published in a Journal in 2016, although it was on the arxiv in 2014).


Initial state bug when sticky element should begin active (with demo)

Hi team, first of all thanks for the great component.
A reduced example of a bug that happened to me is below. Note the sticky element doesn't work when it's initialized in a moment it should be active. Forgive me if my description is incorrect or even if I'm misusing it.

Normal behavior

Buggy behavior

Demo Code: https://github.com/captivationsoftware/react-sticky/compare/master...rxaviers:initial-active-state-bug?expand=1
I've noticed this.state.containerOffset is undefined when isSticky() is called. I believe the bug is related to channel update not being called in that situation.
Please, just let me know if you need additional information about it.
Can you help me fixing it? Thanks.

Hi @rxaviers, do you know if this is still a problem? I don't see the demo repo (thank you 100000x for making that!) or I would verify, and I'm clearing out old issues as I've just come on as a new maintainer.
I'm going to close this out, but I will be happy to reopen it if it's still a problem.


Question about the released Resnet-50 trained models

Hi, thank you very much for sharing the code. I've tried the code and find a question, when I use the Resnet50 trained model (ROMP_ResNet50_V1.pkl)，there's problem with the results by observing the "save_visulization_on_image" images. The question is that all the predicted person's positions are higher than the ground-truth in vertical direction, however, when I use the trained HRNet32 models, it seems everything all right. So I wonder if there's problem with the released Resnet50 trained model?

above are the result images

Please set 'smpl_mesh_root_align': True.

Great, the results are right now. Thanks very much!

Thanks for your report!
Best,
Yu


Admin view + custom relationships [WIP]

Large set of changes to support advanced admin functionality in the admin renderer.
API layer:

Added support for self-links, which allows downstream code or consumers to easily identify the PK and type of a record
Added support for bulk create via CSV file upload

Admin renderer:

Relationship fields automatically render as hyperlinks in the admin view, using the serializer's natural key
Added Import CSV option to list view
Added proper DynamicRelationField support, using select2 with query on natural key
Various design / layout changes

Internals:

Made serializer_class optional on DynamicRelationField. If not passed, DREST will infer the serializer using DynamicRouters registry (map of model -> canonical serializer for that model)
Added getter/setter support on DynamicRelationField. If specified, DREST will call the given methods to get and set relationship values instead of using the model source. This is useful for e.g. higher level APIs that want to hide complicated internal modeling. Unlike DynamicMethodField, a DynamicRelationField with a getter will be automatically properly serialized and will support include[] and exclude[]
Added an internal post-save hook to support DynamicRelationField setter for many-relations
Added a get_url method to serializers, which will resolve the serializer's endpoint based on the first registered viewset. Works even if the serializer is not canonical, but will fall back to using DynamicRouter's map of canonical serializers
Introduced the concept of "natural key" for serializers, a single field that can display a human-friendly string representation for a serializer

would be great if you pull and rebase against master to resolve conflicts

@ryochiji  @aleontiev We want to perform frontend regression testing on the feature deploy for the admin product, so I rebased from master to take into account the new ufd login redirect change from last week (Zoe needs a reliable login flow for some of her tests). I'm now getting a circle failure for dynamic_rest/test.py on instance.save() in create_instance. Is this something you can address from here, or do you recommend I work around this somehow?

when we can try the 2.0 version? did you add drf 3.7 compat for 2.0 release?

sorry for bugging! can anyone give any idea about this work? will this ever be merged? what helps needed to complete this?

@aleontiev do you have plan to complete this? or it would be ok to take over?

@auvipy, I've left the org and have since forked the project here, where I have continued most of this work. Would love to merge in to the main project at some point, time permitting :)

@aleontiev I would love to help in maintaining this package :) you could add me as a co maintainer :)


Improve display of the social network buttons

On small screens (i.e. phones), the buttons can be on two lines, it shouldn't

Done with https://github.com/Doreapp/Doreapp.github.io/commit/cf5c0bc5f791f970cc4651cf391571ec0b2655b6


Add integration with XCTest

As suggested by @dabrahams, it would be good to have an integration with XCTest to run benchmarks as tests.
This would imply that we can create an XCTest test suite out of benchmark suite and run all benchmarks. Each benchmark will map to a single test case where the benchmark is run a single iteration.

This doesn't require anything really fancy.  Some small amount of boilerplate would be OK.

Thanks for the suggestion, @dabrahams! 👍

Oh, @shabalind, I would be happy enough if there was just a single test case for all the benchmarks.  It's not like we're going to get useful error reports; this is just about having an automated way to ask "did I break anything" before pushing a change and having the answer consider the benchmarks.

@dabrahams Does this need to go through XCTest, or is the high-level goal to add CI coverage to the examples? If that's actually the case, I have branch on my fork that has CI passing with both the unit tests and the examples:
https://github.com/mattt/swift-benchmark/pull/1
The challenge with doing this through a conventional Swift Package Manager test target is that the executables must be run in release mode. Compiling tests in release mode means that we can't use @testable import. Even if we create a separate test target and --filter the swift test -c release invocation on it, that still wouldn't work, as swift test builds all test target modules.

@mattt it needs to be that a single simple command from the command-line will test all the code and make sure the benchmarks build/run.  I don't care too much what that command is, but I think as long as we are exposing SPM Packages we should make swift test do this.
It's easy enough to set flags to build any test in the equivalent of release mode... but why can't we build and run debug benchmark executables?

It's easy enough to set flags to build any test in the equivalent of release mode... but why can't we build and run debug benchmark executables?

Aren't we in 100% control of what happens when these executables are run?
It's still way better than nothing, as it makes sure the benchmarks still compile.

Aren't we in 100% control of what happens when these executables are run?

Of course. But changing these example benchmarks to run normally in debug mode would entail the same for all other benchmark executables, unless we either make this behavior configurable or special-case these, specifically.
It's the same kind of problem you run into with testability of libraries. Unfortunately, I don't see a way to smoke test these example benchmarks with a single swift test invocation.

It's still way better than nothing, as it makes sure the benchmarks still compile.

My proposed branch would ensure this on the CI level.
If you wanted to do this with a single command locally, maybe there's a way to do that with CMake?

@mattt I don't see what the problem is.  I haven't looked at the code of this library, but it sees to me  there must be lots of ways we could make this work for all executables built with this library, including checking environment variables or arguments passed on the command line.


How to display each images per row dynamically

So I have an array of images and I'm using base64 to display images.
const images = [{name: "dog", link: base64link}, {name: "cat", link: base64link}, {name: "bird", link: base64link}]
Can I display this images per row without specifying the fix cell position of this images.  I just want to display it vertically and continuously to bottom depending of the number of data inside my array
   A         B

1   Dog    Image
2   Cat     Image
3   Bird    Image
My array is not fix so the data is somewhat changing over time. Please let me know if this is possible. Thanks in advance

+1 for this question


JAMES-3729 LocalDelivery error handling is non-standard

jira: https://issues.apache.org/jira/browse/JAMES-3729

I'm not sure when onMailetException=propagate

Please add a test for the default behaviour when there is an error, if it is not tested yet ;-)

It's already org.apache.james.transport.mailets.delivery.MailDispatcherTest#errorsShouldBeWellHandled


Vref in data

At the moment the tutorial converts data as follows:
ACE1pack.AtomsData(atoms, "energy", "force", "virial", weights, Vref)

I understand that the weights Dict will specify the weight for that training structure. This is a nice way to do it.
But I don't understand why AtomsData needs to know about Vref? That seems extremely unnatural.

I don't find it too unnatural for AtomsData to contain reference energies (e.g., isolated atom energies), which is all that is stored. In principle there could also be reference forces and virials, etc.
Roughly, I think of AtomsData (and ACEfit.AbstractData more generally) as containing everything required to enable
submatrix = feature_matrix(d::AtomsData, basis)

I have considered changing the syntax to something like
feature_matrix(d::AtomsData, basis; kwargs...)

in which case AtomsData could depend on less. We can do that if you prefer.

Logically/conceptually what bothers me is that this is part of the model and not part of the data. We have an affine model not a linear model.

I'm a little confused then - what abstract structure do you have in mind?

I just don't want to conflate model and data. I have two suggestions:
(1) keep separate data, basis, Vref
(2) get rid of basis and just have data, model -- of course internally model = (basis, Vref) but that's an implementation detail.

I posted on slack...

I think we won't fix this for a while - the current code is now pretty much settleed...


Michael theme switching

This allows theme to be toggled, we can tweak the color scheme later. Just wanted to get this implemented.

@MichaelAThew make sure these angular cache files and node_modules files are not synced to the repo

There are a string of commits that I need from here. Was wondering if from your side you can cherry pick changes to approve

closing pull request, cherry picked changes to a new branch


wpewebkit: drop obsolete ENABLE_VIDEO_TRACK from PACKAGECONFIG[video]

As mentioned by @philn in..
https://bugs.webkit.org/show_bug.cgi?id=225310#c1
..ENABLE_VIDEO_TRACK was removed with..
https://bugs.webkit.org/show_bug.cgi?id=212568
This patch set is included in all wpewebkit versions in meta-webkit, so drop ENABLE_VIDEO_TRACK from PACKAGECONFIG[video].

Are you sure about this? Grepping VIDEO_TRACK through the 2.30.* sources shows no matches.

You're right, VIDEO_TRACK was removed in r262695, before 2.30 was branched ( r265544 )


python issue, follow up on #326

This is still an issue to me.

Hi @zaqes, I'm sorry I missed that comment. I have added some replies there. In short, there are two options here:

Do not update Python and stay at 3.7.x
Install FLARE-VM on Windows 10.

Can this not be excluded when running "cup all" on Windows 7?

As far as I know, cup all will try to update all packages, including python3 package. You can cup libraries.python3.fireeye to only update the libraries instead.

What I meant was if this newer python version can't be excluded from Windows 7 installations when you do cup all?

@zaqes , can you elaborate a bit more? As far as I know, Python 3.8 does not support Windows 7 any more. FLARE-VM has to limit the Python version to 3.7 to keep Windows 7 support.
I don't think I know if a way to exclude Python when you perform cup all. I think cup all will try to update everything to the latest version, including Python

Ok, if there's no way to exclude a newer version on a specific OS I assume this issue cannot be resolved?

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM has just been released and will make the project more open and maintainable.
Please check out our blog post at https://www.mandiant.com/resources/blog/flarevm-open-to-public and give the new installation a try.
If this problem still persists with the new installation, please report:

new tools or tool-related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Please note that we use this message to close all legacy issues in this repository. We look forward to your feedback and support for the next generation of FLARE VM.


slot filling

Hi
I am using user_name as slot . when user give the input as "my name is david " , then bot should respond as "hey david , how can i help you " . for this i have added {{slots.user_name.value}} but its not working ....
can you please help me .

Saying it's not working doesn't give us enough information to help you troubleshoot. Can we get a screenshot of what the conversation does do? What your training data looks like, etc? If possible share the entire export with us. Also, please fill out the issue template so that we know which version you are running to eliminate bugs we have squashed in previous versions.
My guess (with little information to go on) is that David is not being recognized as a keyword. if it isn't recognized as a keyword it won't fill the slot, which means the handlebars won't work.

Question answered


Github action for generating typescript models automatically from crds

What does this PR do?
This PR introduces a github action for automatically generating typescript models from crds. It contains two things:

A python script for processing the crds and putting them into a format that kubernetes-client/gen understands
A github action that uses the python script and kubernetes-client/gen to generate a typescript package with typescript models

This approach makes it possible to generate types for any other language that is supported by kubernetes-client/gen. The only difference would be the release process.
@elsony Is it possible for someone from the devfile api team to create an organization on npm and add the npm token to this repo so that this github action can reference it?
What issues does this PR fix or reference?
https://github.com/devfile/api/issues/353
Is your PR tested? Consider putting some instruction how to test your changes
The github action was tested on my fork: https://github.com/JPinkney/api/actions
Docs PR

cc @benoitf since you were interested in this as well but I'm unable to add you as a reviewer

@sleshchenko so let's try ?

/approve

Merged. First job run failed due unclear reason https://github.com/devfile/api/runs/2191535613?check_suite_focus=true, but the rerun by Florent helped and now types are available https://www.npmjs.com/package/@devfile/api.
Florent just has better luck )


Unable to update language stats for ID and stats queue indexer.Index(1424) failed

Description
I mirrored the repository,Every time I restart gitea will report some error.

Unable to update language stats for ID
stats queue indexer.Index(1424) failed

Gitea Version
v1.20+
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Ubuntu
How are you running Gitea?
./gitea web
Database
MySQL

Unrelated problem: it seems that you use "conn" mode for your loggers , which is not correctly configured. I guess you could remove the "conn" mode for loggers.
For the duplicate key problem, is it possible to debug what the content of statsmap  is in the UpdateLanguageStats, and what are the lagnuage_stat database records for the repo 1424  ?

OK, reproduced. The problem is this:
stats = {map[string]int64}
 0 = Shell -> 5131
 1 = Java -> 961174
 2 = java -> 6992114
 3 = PHP -> 15460
 4 = SCSS -> 66518
 5 = PLpgSQL -> 266014
 6 = Groovy -> 2134

What should I do for the second question?

thank you


Feature Request: Ability to transmit/receive to/from TCP/UDP ports

Type: Feature Request
I'm not sure if this request fits the focus of this extension but I believe having functionality such as transmitting to and receiving from network ports would be useful. In the port drop down we could have like a network selection which could bring up a ip:port textbox. This would disable the Baud Rate selection. And we could have the option to create such connections as a "Server" or a "Client"

Hi @rendayigit! Thanks for your suggestions. However, while it's a great suggestion, this is likely out of the scope of what we have planned for the serial monitor extension. I'll close this item due to that reason. Thanks again!

This feature was added in version 0.6.0 of the extension, which is now available in the VS Code Marketplace. Thanks again for your feedback!


⚠ Bofrost.lu has degraded performance

In 69817b5, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 927 ms

Resolved: Bofrost.lu performance has improved in 67ad66c after 6 minutes.


Avoid problems with circular reference in object over responsive layout

This change avoid issues with circular reference in objects. A issue very common working with chartjs.
This is the source.

+1

+1

External objects or properties should be kept outside of layoutItem obj, no reason right now to merge this.


Draco compression corrupt armature animations

Describe the bug
Exporting gltf with draco compression on object with armature animation causes random jitter of verticies
Video: https://streamable.com/3ju4b (he should jump and move his fins up while jumping) from https://gltf.insimo.com/
To Reproduce
Steps to reproduce the behavior:

Download my project file
Select armature object and penguin object (penguin as first)
Export as gltf with those options

Import gltf file here https://gltf.insimo.com/

Expected behavior
Properly exported animation like without draco compression or error message that draco cant handle armature(?)
Screenshots
Corrupted animation:

.blend file/ .gltf
blend and draco-gltf and no-draco-gltf
RecoverForAnim.zip
Version

OS: [Windows10 Home]
Blender Version [2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: build date: 2019-07-29, 09:44 AM platform: Windows]

Additional context
Add any other context about the problem here.

@UX3D-nopper Can you please have a look on it?

@UX3D-eckerlein Any news ?

Hi everyone,
I almost have the same problem with Blender 2.80 final version and Blender 2.81 beta with version 1.01 of glTF exporter. For me, with Draco Compression, the animation armature doesn't play when I drag and drop glb file on Sandbox Babylon.JS
Sources files here
Thank you very much for your work
Version
OS: [Windows 10 Pro]
Blender Version 2.81 [commit date: 2019-10-07 14:47, hash: a856c5eccffb]

@UX3D-nopper and @UX3D-schmithuesen Any news ?

We and/or @UX3D-eckerlein is activly working on this - like the rest of Draco issues.

About to be fixed with #813.

Hi,
I just tested with version 2.82 Alpha - 416e66c7fe21 of Blender and it's good.
Great.


Add support for Flash Attention 3

Feature request
Adds speedup to H100s
Motivation
generation speed
Your contribution
NA

waiting for TGI integration with flash-attention-3

+1 here ! It would be great to have flash attention 3 available for tgi


[automation_testing] automate testcases for capacity_reservation

develop testsuit for capacity  reservation on the Threefold Grid
testsuit contain :
Framework  which include:

js installtion
utils
testcases

testcases :
wallet creation
scenario1

Create  tfchain client  with "Test" network type , should succeed
Create  tfchain  client with wrong network type , should fail .

Scenario 2

Create wallet with name [N1],should succeed.
Get the wallet with give it name[N1], should return same wallet with same seed[S1].
Get the wallet by seed[S1], should return same wallet with same name
Use get method without pass name or seed, should create new one with main name

Before redoing something they already exists. Please check the already existing testsuite there is for the tfchain client.
Most of the features already have tests. So before going any further on this issue, validate what you want to implements as tests doesn't already exists.
Also, everything you have written about the test case you want I create have nothing to do with capacity reservations. This is only basic tfchain client features...

https://github.com/threefoldtech/jumpscaleX/tree/master/Jumpscale/clients/blockchain/tfchain/tests


fix(docs): header anchors

Description
Fixes a position for anchors related to headers in .md
Type of change

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

ToDo's

[x] Documentation added/updated

Screenshots (if applicable)

Additional context

unfortunately still not working (hovered title on screen)


Remove "whitelist" in FDL source

Consider "allowlist" instead
$ git grep whitelist
FirebaseDynamicLinks/Sources/FIRDynamicLinks.m:// Custom domains to be whitelisted are optionally added as an array to the info.plist.
FirebaseDynamicLinks/Sources/Utilities/FDLUtilities.h: Add custom domains from the info.plist to the internal whitelist.

Internally tracked at b/178199888

Internally tracked at b/178199888

Done. Closing the issue.

Done. Closing the issue.


update dockerfile to install dependencies

Signed-off-by: anandrkskd<EMAIL_ADDRESS>What type of PR is this:
/kind tests
/kind cleanup
What does this PR do / why we need it:
This PR adds dependencies installation in Dockerfile and removes dependencies from function.sh script.
Which issue(s) this PR fixes:
Fixes #
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

/lgtm
/approve


feat(OCPADVISOR-124): workloads feature flag

Add a new feature flag to the unleash that will allow us to develop workloads
To test run "npm run start:proxy:beta"
add to the Recstable or other component
const workloadsEnabled = useFeatureFlag(WORKLOADS_ENABLE_FLAG);
console.log(workloadsEnabled, 'FLAG');
Import required functions and stuff
Check that the console log prints TRUE

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

src/Utilities/useFeatureFlag.js
78.57% <40.00%> (ø)

... and 33 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!.

:tada: This PR is included in version 1.19.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Fix]: Data for Orthos Microsystem

Mob Id
12121, 12120
What threat level sould the mob have
Easy
What agro type does the mob have
Proximity
Vulnerabilities for the enemy

[ ] Stun
[ ] Heavy
[ ] Slow
[ ] Sleep
[ ] Bind
[ ] Undead

Additional mob text guide
No response

Agro type also applies to mob ID 12120
Video proof: https://youtu.be/JF2z809ZLLU


create public cert - challenges added

create public cert - challenges added
Release 1.0.37

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: