getIdentity returns null.

Hello!
Scatter Desktop 8.7.0
Scatter-js  2.5.1
Yesterday my Scatter Desktop and scatter-js worked fine but today I receive null identities.
I run Scatter Desktop. So basically, my websocket connects fine but ScatterDesktop doesn't pop any window in which I can choose my identity. It sends over a null identity and the getIdentity promise get resolved.
I don't know if the issue is at the Scatter Desktop level or scatter-js, on which side of the websockets there is an issue

Hmm, if this is still happening try seeing if there's any errors in the console of the website or Scatter.

Hi, getIdentity function returns null  intermittently. The probability of the null is approximately 1.5% in my experiment(about 15 out of 1000).  The only solution for this is to remove the Scatter ID and recreate it repeating this cycle. This is critical since authenticate function returns null signature too. Scatter chrome extension seems to be more concrete than Scatter Desktop and Scatter mobile.

Need some errors guys. I've yet to be able to reproduce this.
Need errors from the website ( probably won't get thrown ) or errors from inside Scatter Desktop ( </> button inside settings will open console )


Great package! But can we choose to disable the messages?

I really love this package. It's ultra simple and does exactly what I wanted to do.
I was first going in trouble with browserify, which does complex things for simple purposes.
And with this package, I can now keep my global variables and split all my js in as many files I want.
Now I just want to disable the two console.logs, because I want to keep my console clear.
Is there an option for that?

hi, sorry for long time waiting!
did you mean console like this
import filename --> path

or
ImportJS finished.

i will support next version, thanks for suggestion.

i have add hideConsole config, you can use like this
var gulp = require('gulp');
var jsImport = require('gulp-js-import');

gulp.task('import', function() {
  return gulp.src('index.js')
        .pipe(jsImport({hideConsole: true}))
        .pipe(gulp.dest('dist'));
});

Cool, thanks!


Resolve camel catalog from custom resource

Fixes #302
Fixes #414

@astefanutti mind doing a review ?


Rename files without file extensions

I downloaded some video (I think it was some Planet Wissen movie from WDR/ARD) and Android didn't wanted to handle the file because it had no file extension.
Maybe it would make sense to add a default file extension (maybe ….mp4?) so that it wouldn't require to rename a file (I'm not even sure whether renaming is generally possible with onboard tools in Android).

@alexanderadam I cannot reproduce this bug. Do you remember the exact show that caused the error?

@cemrich Actually a lot of "Planet Wissen" videos are affected (probably more).
For example when I search for "Planet Wissen" right now, there's a new video called "Was ist das Pferd eigentlich für ein Tier?" from ARD. When I tap now on the download button of "Low" quality, the resulting video doesn't have any extension.
I can play it in the view from the Download Manager app (I guess because it still knows the MIME type from the just downloaded file) but I can't open it from a file manager for example.

@alexanderadam Thank you, I can reproduce the issue.
For future reference: There seems to be an error with the construction of the download file name.

Got it! The question mark at the end of the title is causing this problem. File name sanitation has to be way better than now.


New helper (getter) functions

This originated from Discussion https://github.com/aquasecurity/libbpfgo/discussions/40
It adds the following functions.
For BPFMap:
GetFd()
GetName()
GetPinPath()
IsPinned()
GetModule()

For BPFProg:
GetName()
GetModule()

I split the functions commits leaving the GetModule() in the https://github.com/aquasecurity/libbpfgo/pull/41/commits/468d2b2e0185e60b6087c23d4a2a85254f00bf7e, since this getter might not be welcome.


deviceReady fire before vmsg plugin successfully init

hello,
i have been working on the vmsg plugin and found that deviceReady fire before the plugin init since the initiation of vmsg is async function. is there any other way that i can check if the plugin is successfully init?
really appreciate for the help.

what version of vmsg, videojs-record, browser etc?


Added lane information based on the osm tag turn:lanes, use

lane_info=true in the encoder string to enable it, it requrires 8
bytes_for_flags.
@karussell
@boldtrn
Issue #1131

Thank you very much for your contribution and sorry for the late reply. This PR looks very impressive. Having turn lane support would be great.
Since turn lanes are not important for the routing itself and are only required for the TurnInstruction generation, I would probably put them in a DataAccess, similar to the NameIndex. As you have seen yourself, it requires a lot of bits, and bits are very precious :). Using a DataAccess we could even think about just storing the whole turn:lane information and not needing to encode it (I am not sure if we cover every possible turn lane combination?).
WDYT @karussell, could we merge something like this, using DataAccess before #1112 or do we have to wait until #1112 is finished?
Regarding the PR itself, you included the tag turn:lanes, but not turn:lanes:forward and turn:lanes:backward. I think this will make the code a bit more complicated, but a lot of turn lanes are tagged like this, so I think it would be required to have that information.

@boldtrn Thanks for the comments. I saw the turn:lanes:forward and turn:lanes:backward I wanted to make a second pull request including them. It will take more memory (more bits are needed).

@boldtrn Thanks for the comments. I saw the turn:lanes:forward and turn:lanes:backward I wanted to make a second pull request including them. It will take more memory (more bits are needed).

There is a way to get around this by using a DataAccess, similar to the NameIndex or TurnCostExtension. Let's wait for Feedback from @karussell before deciding our next steps :).

Thanks @aramzl for this useful and big feature!
I'm not sure if we should merge such a complex thing before #1112 as this will highly likely needs a bigger refactoring. If you would have time it would be really interesting to see if you could base your PR on the mentioned branch. This could be also used as a test case if everything what we need is already possible

Thanks @aramzl for this useful and big feature!
I'm not sure if we should merge such a complex thing before #1112 as this will highly likely needs a bigger refactoring. If you would have time it would be really interesting to see if you could base your PR on the mentioned branch. This could be also used as a test case if everything what we need is already possible

I would try to redo it based on #1112 and create another pull request.

This is awesome! Please note that this is cutting edge, and could potentially use lots of your time ... we really appreciate your feedback e.g. if this feels better from a programming perspective.

Will close here, then resurrect #1269 (include the tests from here, maybe wait until #1548 is merged)
Sorry that this takes so long @aramzl. Now that #1447 was merged this is a much better time to do your change. Have marked #1269 for 0.13


When I run a command via ssh the result is not always displayed

Description
My server and my shellhub agent are in version v0.11.1.
When I run a command on my agent via my shellhub server the result of the command does not always reach my ssh client.
I suspect a race condition when the agent closes the connection, but I haven't been able to get the necessary logs to confirm or deny my theory.
The problem is quite easily reproducible in my environment by typing several times in a row a command of this type:
 ssh user@ns.agent@server date

Below the end of the logs of a command launched with the -v option of ssh, for the 2nd case, we see that the answer is not sent by the server.
OK:
debug1: Entering interactive session.
debug1: pledge: network
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending command: date
Wed Feb 22 22:45:22 CET 2023
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 2852, received 1756 bytes, in 3.0 seconds
Bytes per second: sent 943.4, received 580.9
debug1: Exit status 0

KO:
debug1: Entering interactive session.
debug1: pledge: network
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending command: date
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 2852, received 1704 bytes, in 9.4 seconds
Bytes per second: sent 303.0, received 181.0
debug1: Exit status 0

Can you reproduce the problem and what do you think?
Edition
Community
Version
v0.11.1

Hi @benasse, we are currently debugging this issue and will have a fix out soon

Hi @gustavosbarreto, your reactivity is amazing, thank you for your involvement ! 🤩
My long term dream would be to be able to run ansible through shellhub but I think the way to get there will not be easy.
I'm going to do some tests and go step by step.
When I have some content, I think I will open a discussion to share my progress on the subject. It may interest other people.

Hi @benasse, can you test test the latest release candidate version (v0.11.2-rc.1)?

Hi @gustavosbarreto, I made the upgrade and just tested to execute the date command like in my first post, the success rate is a bit better. But it is not yet 100%.
If it helps, the ssh client and agent logs are available below:
https://gist.github.com/benasse/fb2b162f5697f35a6f71ce697fe56a2c

Anyway, I didn't make the effort to quantify it but when I launch a normal ssh connection, it works, much better than before the patch.
This is ok in a "normal" use case.

We are considering doing a release due to this considerable improvement. But, next, we want to continue improving it for the next release.

Hi @benasse, can you please test the latest release candidate version (v0.11.3-rc.1)?

I @gustavosbarreto I tested the release candidate, but it remains random 😕
Below are the agent-side logs: https://gist.github.com/benasse/c97c12dbd4d4b7b00276188e07dd8e5b

I @gustavosbarreto I tested the release candidate, but it remains random 😕
Below are the agent-side logs: https://gist.github.com/benasse/c97c12dbd4d4b7b00276188e07dd8e5b

Please ensure that the agent version matches the server version, as the fix was implemented in the agent.

I double checked, I built the agent from the master branch directly on the host on which I did my tests.
This server is running Debian 10.

I am reopening this issue because I was able to confirm the same problem. The PR '#2532' fixes another issue related to this one that was discovered during the investigation of this issue.


[BUG] ...Authenticate against my Salesforce Org

I am trying to run the step "sfdx auth:web:login -r https://login.salesforce.com" to connect to the production but when it redirects me to login I enter my credentials and try to login it then throws me an error EPERM: operation not permitted, open 'C:\Users\ryyan.sf\sf.json'
I ran this step before when connecting staging to my lower sandbox and it worked. I went to the path that it mentioned in the error and the configurations were still for the lower sandbox. This was automatically generated for the lower sandbox but I did manually changed the configuration to match those of production and I still get the same error.
Expected behavior
The expected behavior is that I am logged in to my production.
Screenshot

Environment details:

Node version: v15.2.1
NPM version: 7.0.8
SFDX version: sfdx-cli/7.156.1 win32-x64 node-v16.15.1

Running an SFDX command and getting an error means you are having an issue with you setup. This has nothing related to b2c-crm-sync on its own.
Please, please don't deploy to production from your local machine, you should have setup a proper CI/CD and release management process to deploy to production safely...


I am trying to open a modal window using angular2  .is anybody suggest me the best way to do it

I am trying to open a modal window using angular2 . is anybody suggest me the best way to do it?
because I have tried   but that was not appropriate

Hi @npipada, I guess the best way is to use ng2-bootstrap http://valor-software.com/ng2-bootstrap/#/modals as it has modal component and is already integrated into ng2-admin.

The above link is broken.  Thanks


Forward declare of enum class in template argument is a Microsoft extension

Hello, currently the generated SDK can only be compiled with MSVC because the enum members of the generated classes (like TEnumAsByte<enum class ENetRole>) aren't standard C++.
I propose 3 solutions:

Fix forward declaration somehow?
Put the enums in x_structs.hpp after constants and before structs (don't know how that would work with package ordering though).
Change TEnumAsByte<enum class ESomeEnum> to uint8_t/*ESomeEnum*/ or TEnumAsByte<uint8_t/*ESomeEnum*/>

Didn't know only MSVC can do this. Could you test if the SDK works after changing to code generation in GenericTypes.cpp to
return Info::Create(PropertyType::Primitive, sizeof(uint8_t), false, "TEnumAsByte<" + MakeUniqueCppName(enumObj) + ">");

The enums should be known at every class, so the forward declaration may not be necessary. If that doesn't work, the "put them into an other file" could be a good solution.

No, that doesn't work. It works better if combined with the "enums in another x_structs.hpp", but I get a name collision in PUBG (between a member variable and an enum).
What is wrong with the other compiler (Clang) is that the compiler shouldn't know the size of an enum, so it fails. I tried adding " : uint8_t" in various forms (lots of them) but still didn't make it work.
So I used the uint8_t/* ESomeEnum */ solution.

I moved the enums in the structs file. Now they are known to structs and classes and the forward decleration isn't needed anymore.


Add folder structure for EventFiltration and PrivacyBudgetManager + cel-java dependency

This change is

@SanjayVas changed the folder names. Created the folder structure because Dulio will be working on the validation library and wanted to point him where to put the code also wanted to see what you think about going for this top level eventdataprovider folder.


License file containing Apache-2.0 not being matched

If you run licensee against https://github.com/twitter/twitter-text/blob/master/LICENSE it doesn't match the Apache-2.0 license.

The issue appears to be that the author took the Apache boilerplate (normally found at the bottom of the license and applied to individual files) and added it to the top of the LICENSE file.

https://github.com/twitter/twitter-text/blob/master/LICENSE doesn't include the appendix at the end of the text and prepends notice text that's usually used in file headers, NOTICE, or README. I wouldn't be surprised for it to not match Apache-2.0 or any license, but seems that it matches the Apache-2.0 derived and recently added ECL-2.0 license:
$ script/git-repo  https://github.com/twitter/twitter-text
License file: LICENSE
License hash: e19a9d85daf301edc053c9617910d0f730ec0dd6
Attribution: Copyright 2011 Twitter, Inc.
License: Educational Community License v2.0
Confidence: 96.04%
Method: Licensee::Matchers::Dice

One approach to fixing might be along the lines of how we avoid detecting CC NC or ND licenses as CC-BY-4.0 or CC-BY-SA-4.0, but instead of failing a detection if a license text includes certain strings, fail detection of ECL-2.0 if the license text does not include certain strings (probably "Educational Community License").
That would have the same effect as removing the vendored ECL-2.0 text, which obtains what I'd expect:
$ script/git-repo  https://github.com/twitter/twitter-text
License file: LICENSE
License hash: e19a9d85daf301edc053c9617910d0f730ec0dd6
Attribution: Copyright 2011 Twitter, Inc.
License: Not detected


Pinch to zoom doesn't appear to be working :/

I just built this awesome library into my project and everything seems to be working great except that zooming does not seem to be working. When I use a pinch gesture nothing happens at all. Tap to focus works and everything but literally nothing occurs when i pinch. I have not messed with any of the setup but I checked to ensure that zooming was enabled and it is. Any thoughts on why this feature isn't working for me?  iPhone 5S running iOS 9

Update to this: it appears that zooming doesn't work initially but if i flip the camera it starts working, even if i flip it back. Can anybody help me understand why zooming doesn't work on the initial view?

I have the same issue - only after flipping it works

@lauraskelton any ideas on what might be causing this?

Have the same issue too

+1 After I minimized the app and open it again starts working.

A temporary solution is to just flip the camera twice when starting it... But this issue has been around for some time now - still hoping for a fix :)

    func startCamera(){

        guard !UIDevice.isSimulator() else {
            return
        }
        //this solved it for me. In my case, there wasn't front cam.
        if FastttCamera.isCameraDeviceAvailable(.rear) {
            camera.cameraDevice = .rear
        }
        camera.startRunning()
    }


animated-clip: creating the stylesheet with keyframes takes too long

The generation of the stylesheet for the keyframes takes almost 200ms

I tried saving the contents into a separate file, but it is ~3MB non-gzipped!
This could probably be reduced to half by using animation-direction.

Whoa. How long was the transition? And on how many elements?
The keyframe-per-frame method is probably better suited for transitions under 1.6s since over that you'll generate over 100 frames.

I guess the bug is this._frameTime being in seconds (1/60) instead of milliseconds (1000/60).

Oh wow. DERP. 😣


More buttons, NSFW and other stuff

Pushing this before it's too late for tonight; I am having immense difficulty with the region select button for some reason, which I believe is the only button left I have to finish.
Also, don't know why the spacing for text shadow is screwy, but that'll be fixed in the next release.

Closed; Newer version released.


etcdserver/ARM: starting etcd on crashes the first time, succeeds subsequently

Title says it all. First time -> crash, second time -> works (this is raspberry pi b+)
2015/02/14 07:47:55 no data-dir provided, using default data-dir ./pi0.etcd
2015/02/14 07:47:55 etcd: listening for peers on http://<IP_ADDRESS>:2380
2015/02/14 07:47:55 etcd: listening for client requests on http://localhost:2379
2015/02/14 07:47:55 etcd: listening for client requests on http://localhost:4001
2015/02/14 07:47:55 etcdserver: name = pi0
2015/02/14 07:47:55 etcdserver: data dir = pi0.etcd
2015/02/14 07:47:55 etcdserver: member dir = pi0.etcd/member
2015/02/14 07:47:55 etcdserver: heartbeat = 100ms
2015/02/14 07:47:55 etcdserver: election = 1000ms
2015/02/14 07:47:55 etcdserver: snapshot count = 10000
2015/02/14 07:47:55 etcdserver: advertise client URLs = http://localhost:2379,http://localhost:4001
2015/02/14 07:47:55 etcdserver: initial advertise peer URLs = http://<IP_ADDRESS>:2380
2015/02/14 07:47:55 etcdserver: initial cluster = pi0=http://<IP_ADDRESS>:2380,pi1=http://<IP_ADDRESS>:2380,pi2=http://<IP_ADDRESS>:2380
2015/02/14 07:47:55 etcdserver: start member 1dc862383bd186a1 in cluster 985788d45a3370a0
2015/02/14 07:47:55 raft: 1dc862383bd186a1 became follower at term 0
2015/02/14 07:47:55 raft: newRaft 1dc862383bd186a1 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/02/14 07:47:55 raft: 1dc862383bd186a1 became follower at term 1
2015/02/14 07:47:55 etcdserver: added local member 1dc862383bd186a1 [http://<IP_ADDRESS>:2380] to cluster 985788d45a3370a0
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x4 pc=0xb9dd0]

goroutine 18 [running]:
sync/atomic.storeUint64(0x1073065c, 0x1, 0x0)
        /home/miek/upstream/go/src/sync/atomic/64bit_arm.go:20 +0x48
github.com/coreos/etcd/etcdserver.(*EtcdServer).apply(0x10730630, 0x107882c0, 0x3, 0x4, 0x1078a380, 0x0, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:696 +0x210
github.com/coreos/etcd/etcdserver.(*EtcdServer).run(0x10730630)
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:398 +0xfd0
created by github.com/coreos/etcd/etcdserver.(*EtcdServer).start
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:294 +0x2cc

goroutine 1 [runnable]:
github.com/coreos/etcd/etcdmain.Main()
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:79 +0x56c
main.main()
        /home/miek/g/src/github.com/coreos/etcd/main.go:48 +0x250

goroutine 5 [syscall]:
os/signal.loop()
        /home/miek/upstream/go/src/os/signal/signal_unix.go:21 +0x1c
created by os/signal.init·1
        /home/miek/upstream/go/src/os/signal/signal_unix.go:27 +0x40

goroutine 19 [runnable]:
github.com/coreos/etcd/etcdserver.(*EtcdServer).Do(0x10730630, 0xb6eef6f8, 0x107a0180, 0xe70d0001, 0xa14b870e, 0x38e5a0, 0x3, 0x10732510, 0x26, 0x10710190, ...)
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:488 +0x49c
github.com/coreos/etcd/etcdserver.(*EtcdServer).publish(0x10730630, 0x2a05f200, 0x1)
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:650 +0x294
created by github.com/coreos/etcd/etcdserver.(*EtcdServer).Start
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:275 +0x58

goroutine 20 [runnable]:
github.com/coreos/etcd/etcdserver.(*EtcdServer).purgeFile(0x10730630)
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:305 +0x38c
created by github.com/coreos/etcd/etcdserver.(*EtcdServer).Start
        /home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:276 +0x80

goroutine 21 [IO wait]:
net.(*pollDesc).Wait(0x107370f8, 0x72, 0x0, 0x0)
        /home/miek/upstream/go/src/net/fd_poll_runtime.go:84 +0x3c
net.(*pollDesc).WaitRead(0x107370f8, 0x0, 0x0)
        /home/miek/upstream/go/src/net/fd_poll_runtime.go:89 +0x38
net.(*netFD).accept(0x107370c0, 0x0, 0xb6eedab0, 0x1073a638)
        /home/miek/upstream/go/src/net/fd_unix.go:419 +0x390
net.(*TCPListener).AcceptTCP(0x1071c620, 0x0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/tcpsock_posix.go:234 +0x50
net.(*TCPListener).Accept(0x1071c620, 0x0, 0x0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/tcpsock_posix.go:244 +0x3c
github.com/coreos/etcd/pkg/transport.(*rwTimeoutListener).Accept(0x1078a1c0, 0x0, 0x0, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/pkg/transport/timeout_listener.go:44 +0x64
net/http.(*Server).Serve(0x107a0280, 0xb6eef018, 0x1078a1c0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/http/server.go:1728 +0x98
github.com/coreos/etcd/etcdmain.serveHTTP(0xb6eef018, 0x1078a1c0, 0xb6eef638, 0x1078a280, 0xd964b800, 0x45, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/http.go:36 +0x1b8
github.com/coreos/etcd/etcdmain.func·005(0xb6eef018, 0x1078a1c0)
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:180 +0x58
created by github.com/coreos/etcd/etcdmain.startEtcd
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:118 +0x17d8

goroutine 22 [IO wait]:
net.(*pollDesc).Wait(0x107371b8, 0x72, 0x0, 0x0)
        /home/miek/upstream/go/src/net/fd_poll_runtime.go:84 +0x3c
net.(*pollDesc).WaitRead(0x107371b8, 0x0, 0x0)
        /home/miek/upstream/go/src/net/fd_poll_runtime.go:89 +0x38
net.(*netFD).accept(0x10737180, 0x0, 0xb6eedab0, 0x1073a650)
        /home/miek/upstream/go/src/net/fd_unix.go:419 +0x390
net.(*TCPListener).AcceptTCP(0x1071c6f0, 0x0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/tcpsock_posix.go:234 +0x50
net.(*TCPListener).Accept(0x1071c6f0, 0x0, 0x0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/tcpsock_posix.go:244 +0x3c
github.com/coreos/etcd/pkg/transport.(*keepaliveListener).Accept(0x1071c6f8, 0x0, 0x0, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/pkg/transport/keepalive_listener.go:48 +0x64
net/http.(*Server).Serve(0x107a02c0, 0xb6eef038, 0x1071c6f8, 0x0, 0x0)
        /home/miek/upstream/go/src/net/http/server.go:1728 +0x98
github.com/coreos/etcd/etcdmain.serveHTTP(0xb6eef038, 0x1071c6f8, 0xb6eef720, 0x1073a450, 0x0, 0x0, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/http.go:36 +0x1b8
github.com/coreos/etcd/etcdmain.func·006(0xb6eef038, 0x1071c6f8)
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:188 +0x8c
created by github.com/coreos/etcd/etcdmain.startEtcd
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:118 +0x18e0

goroutine 23 [IO wait]:
net.(*pollDesc).Wait(0x10737278, 0x72, 0x0, 0x0)
        /home/miek/upstream/go/src/net/fd_poll_runtime.go:84 +0x3c
net.(*pollDesc).WaitRead(0x10737278, 0x0, 0x0)
        /home/miek/upstream/go/src/net/fd_poll_runtime.go:89 +0x38
net.(*netFD).accept(0x10737240, 0x0, 0xb6eedab0, 0x1073a6b8)
        /home/miek/upstream/go/src/net/fd_unix.go:419 +0x390
net.(*TCPListener).AcceptTCP(0x1071c740, 0x0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/tcpsock_posix.go:234 +0x50
net.(*TCPListener).Accept(0x1071c740, 0x0, 0x0, 0x0, 0x0)
        /home/miek/upstream/go/src/net/tcpsock_posix.go:244 +0x3c
github.com/coreos/etcd/pkg/transport.(*keepaliveListener).Accept(0x1071c748, 0x0, 0x0, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/pkg/transport/keepalive_listener.go:48 +0x64
net/http.(*Server).Serve(0x107a0300, 0xb6eef038, 0x1071c748, 0x0, 0x0)
        /home/miek/upstream/go/src/net/http/server.go:1728 +0x98
github.com/coreos/etcd/etcdmain.serveHTTP(0xb6eef038, 0x1071c748, 0xb6eef720, 0x1073a450, 0x0, 0x0, 0x0, 0x0)
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/http.go:36 +0x1b8
github.com/coreos/etcd/etcdmain.func·006(0xb6eef038, 0x1071c748)
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:188 +0x8c
created by github.com/coreos/etcd/etcdmain.startEtcd
        /home/miek/g/src/github.com/coreos/etcd/etcdmain/etcd.go:118 +0x18e0

goroutine 24 [chan receive]:
github.com/coreos/etcd/pkg/osutil.func·001()
        /home/miek/g/src/github.com/coreos/etcd/pkg/osutil/osutil.go:66 +0x50
created by github.com/coreos/etcd/pkg/osutil.HandleInterrupts
        /home/miek/g/src/github.com/coreos/etcd/pkg/osutil/osutil.go:82 +0x1d4

goroutine 25 [runnable]:
github.com/coreos/etcd/pkg/fileutil.func·001()
        /home/miek/g/src/github.com/coreos/etcd/pkg/fileutil/purge.go:69 +0x5d0
created by github.com/coreos/etcd/pkg/fileutil.PurgeFile
        /home/miek/g/src/github.com/coreos/etcd/pkg/fileutil/purge.go:75 +0x26c

goroutine 26 [runnable]:
github.com/coreos/etcd/pkg/fileutil.func·001()
        /home/miek/g/src/github.com/coreos/etcd/pkg/fileutil/purge.go:69 +0x5d0
created by github.com/coreos/etcd/pkg/fileutil.PurgeFile
        /home/miek/g/src/github.com/coreos/etcd/pkg/fileutil/purge.go:75 +0x26c

@miekg Can you reliably reproduce this? It is a transient bug?

Yes. Deleting the datadir re-triggers this.
On 14 Feb 2015 16:42, "Xiang Li"<EMAIL_ADDRESS>wrote:

@miekg https://github.com/miekg Can you reliably reproduce this? It is
a transient bug?
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/etcd/issues/2308#issuecomment-74381954.

Yes. Deleting the datadir re-triggers this.

I tend to think this is an arm specific problem. I cannot reproduce this on x86.
I do not have arm env around. I think it should be easy to debug by adding a few checking around the panic line.
If you have time, can you help to fix it?

From some prints the error seems to actual be in
/home/miek/upstream/go/src/sync/atomic/64bit_arm.go:20 +0x48

Which makes it a wider Go (arm) problem.

This  atomic.StoreUint64 is fishy on arm (pi  b+), if i just use assignment, i.e.
diff --git a/etcdserver/server.go b/etcdserver/server.go
index 0249506..569de00 100644
--- a/etcdserver/server.go
+++ b/etcdserver/server.go
@@ -693,8 +693,10 @@ func (s *EtcdServer) apply(es []raftpb.Entry, confState *raftpb
                default:
                        log.Panicf("entry type should be either EntryNormal or Entry
                }
-               atomic.StoreUint64(&s.r.index, e.Index)
-               atomic.StoreUint64(&s.r.term, e.Term)
+               s.r.index = e.Index
+               //atomic.StoreUint64(&s.r.index, e.Index)
+               s.r.term = e.Term
+               //atomic.StoreUint64(&s.r.term, e.Term)
                applied = e.Index
        }
        return applied, shouldstop

It crashes on
goroutine 18 [running]:
sync/atomic.storeUint64(0x1070a66c, 0x0, 0x0)
	/home/miek/upstream/go/src/sync/atomic/64bit_arm.go:20 +0x48
github.com/coreos/etcd/etcdserver.(*EtcdServer).run(0x1070a630)
	/home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:359 +0x378
created by github.com/coreos/etcd/etcdserver.(*EtcdServer).start
	/home/miek/g/src/github.com/coreos/etcd/etcdserver/server.go:294 +0x2cc

which is another storeUint64

ok, as starting point: the following just works.
package main

import "sync/atomic"

type X struct {
	index uint64
}

func main() {
	x := new(X)
	println(x.index)
	atomic.StoreUint64(&x.index, 1)
	println(x.index)
}

This bug (from the docs) maybe:

On both ARM and x86-32, it is the caller's responsibility to arrange for
64-bit alignment of 64-bit words accessed atomically. The first word in a
global variable or in an allocated struct or slice can be relied upon to
be 64-bit aligned.

This is one problem, but looking at the original post there may be two.
The first is an honest to god nil pointer exception, something is passing 0x4 as the address of the unit64 inside the struct, so that is nil + offset of the field.
The second problem is while the runtime guarantees that structures will always be heap aligned on 8 byte boundaries, if you have something like this
type T struct {
       p *Something
       val uint64
...
}

val will be 4 bytes offset from the start of the structure on 32 bit platforms. The 32 bit compilers do not insert the correct padding here. There are a number of ways to tackle this, the simplest is to move val to the top of the structure so it will be 8 byte aligned. You could also use built tags to provider a properly padded version of the struct depending on the platform.

thanks @davecheney
This patch makes the crash go away (fixes the allignment).
(Still wondering about that nil pointer though)
diff --git a/etcdserver/raft.go b/etcdserver/raft.go
index 0d7d5d0..b533078 100644
--- a/etcdserver/raft.go
+++ b/etcdserver/raft.go
@@ -37,6 +37,11 @@ type RaftTimer interface {
 }

 type raftNode struct {
+       // Cache of the latest raft index and raft term the server has seen
+       index uint64
+       term  uint64
+       lead  uint64
+
        raft.Node

        // config
@@ -51,11 +56,6 @@ type raftNode struct {
        // clients should timeout and reissue their messages.
        // If transport is nil, server will panic.
        transport rafthttp.Transporter
-
-       // Cache of the latest raft index and raft term the server has seen
-       index uint64
-       term  uint64
-       lead  uint64
 }

 // for testing
diff --git a/etcdserver/server.go b/etcdserver/server.go
index 0249506..6b7a9d2 100644
--- a/etcdserver/server.go
+++ b/etcdserver/server.go
@@ -113,10 +113,9 @@ type Server interface {

 // EtcdServer is the production implementation of the Server interface
 type EtcdServer struct {
+       r   raftNode
        cfg *ServerConfig

-       r raftNode
-
        w          wait.Wait
        stop       chan struct{}
        done       chan struct{}

LGTM. What is the definition of raft.Node ?

On 15 Feb 2015, at 18:41, Miek Gieben<EMAIL_ADDRESS>wrote:
thanks @davecheney
This patch makes the crash go away (fixes the allignment).
(Still wondering about that nil pointer though)
diff --git a/etcdserver/raft.go b/etcdserver/raft.go
index 0d7d5d0..b533078 100644
--- a/etcdserver/raft.go
+++ b/etcdserver/raft.go
@@ -37,6 +37,11 @@ type RaftTimer interface {
}
type raftNode struct {

  // Cache of the latest raft index and raft term the server has seen

  index uint64

  term  uint64

  lead  uint64

  raft.Node

  // config

@@ -51,11 +56,6 @@ type raftNode struct {
// clients should timeout and reissue their messages.
// If transport is nil, server will panic.
transport rafthttp.Transporter

  // Cache of the latest raft index and raft term the server has seen

  index uint64

  term  uint64

  lead  uint64

}
// for testing
diff --git a/etcdserver/server.go b/etcdserver/server.go
index 0249506..6b7a9d2 100644
--- a/etcdserver/server.go
+++ b/etcdserver/server.go
@@ -113,10 +113,9 @@ type Server interface {
// EtcdServer is the production implementation of the Server interface
type EtcdServer struct {

  r   raftNode
  cfg *ServerConfig

  r raftNode

  w          wait.Wait
  stop       chan struct{}
  done       chan struct{}

—
Reply to this email directly or view it on GitHub.

@miekg I do not think you are 100% safe by only changing this.
We are not in control of all the dependencies and are not sure of other sub pkgs in etcd. We probably need more effort to say we do support 32bit or arm well enough.

@xiang90 Ack. At least I can play some more now :)
etcdserver/raft.go has the def (note this is my changed struct)
type raftNode struct {
	// Cache of the latest raft index and raft term the server has seen
	index uint64
	term  uint64
	lead  uint64

	raft.Node

	// config
	snapCount uint64 // number of entries to trigger a snapshot

	// utility
	ticker      <-chan time.Time
	raftStorage *raft.MemoryStorage
	storage     Storage
	// transport specifies the transport to send and receive msgs to members.
	// Sending messages MUST NOT block. It is okay to drop messages, since
	// clients should timeout and reissue their messages.
	// If transport is nil, server will panic.
	transport rafthttp.Transporter
}

I just made the above changes and this is now working on an odroid u3 as well. It would be great to have this working out of the box though.

[ Quoting<EMAIL_ADDRESS>in "Re: [etcd] etcdserver/ARM: starting..." ]

I just made the above changes and this is now working on an odroid u3 as well. It would be great to have this working out of the box though.

Note that the same bug is triggered on 32 bit intel.
(my lousy virtual machine which I sometimes use for development, is only 32 bits)

@Audumla do you have a repo/changeset I can build from for odroid?

I did not create one for this, as I just made the change to the file mentioned above and rebuilt using the code from a master git repository. It just worked!
If I get a chance Ill make a branch, but that might be weeks away due to time restrictions.

I'm trying to get this to build today.

I put this into a changeset and rebuilt:
https://github.com/hh/etcd/tree/32bit
I had to start with a clean data-dir, but it seems to be working.
https://github.com/hh/etcd/commit/3060f863f0152b8fb77e651398788e9c81c01cdd

@hh. I've used your version of the source code, with go 1.4.2 (built from source) and I'm getting
etcdserver: publish error: etcdserver: request timed out
My go skills are non existent, otherwise I would have a look at the code.
I'm  building and running it on a raspberry pi 2 with hypriot image(http://blog.hypriot.com/post/hypriotos-back-again-with-docker-on-arm/)

I've found some patches described on http://mkaczanowski.com/building-arm-cluster-part-3-docker-fleet-etcd-distribute-containers/#install_docker to make etcd 2.0.4 run on a raspberry pi. Is it possible to merge these changes ? They are the same as @hh but for some reason etcd works with those patches. Unless I'm being a noob.

+1 for patch on raspberry pi (ARM)

getting exact same error as @ajazam also on raspberry pi 2 and go 1.4.2

I looked at the three patches:

https://raw.githubusercontent.com/mkaczanowski/docker-archlinux-arm/master/archlinux-etcd/patches/raft.go.patch
https://raw.githubusercontent.com/mkaczanowski/docker-archlinux-arm/master/archlinux-etcd/patches/server.go.patch
https://raw.githubusercontent.com/mkaczanowski/docker-archlinux-arm/master/archlinux-etcd/patches/watcher_hub.go.patch

They all do the same, move some struct fields to the beginning of the struct, to be sure of the 8 byte alignment. I think they could be applied without consequence.

Applied the patches and etcd works fine for now.
+1 for 32-bit branch or something until etcd is completely cross-platform
Now I should step forward to next problem...
I'm building a "cloud-in-a-box" with Raspberry Pi 2 and Kubernetes, not the easiest one :)

I've come across this as well and confirm that the patches from @mkaczanowski work. Changing struct alignment seems to be the key here, and I now have etcd running happily on both a Raspberry Pi 2 and and ODROID-U3 (both running Ubuntu 14.04 armhf).
It might be worthwhile applying these on an ARM-related branch (just for archival purposes) before merging...

Fixed via https://github.com/coreos/etcd/pull/3249


[FEATURE] Copy Controls

Feature Description

Put a copy control in the upper right hand corner of the Query pane to copy the contents of the Query pane (the query) to the clipboard
Put a copy control in the upper right hand corner of the Results pane, if...
Get Types is invoked (to copy the type definitions to the clipboard); or
The JSON tab is active (to copy the pretty printed JSON query results to the clipboard)

Use the MUI ContentCopy Icon button
import ContentCopyIcon from '@mui/icons-material/ContentCopy';

[ ] add the button to query pane
[ ] Add copy to clipboard capability
[ ] add button to result pane
[ ] Only render the button when it is getText and is results tab


CUDA: Add binary ufunc support

Following from #8294, this PR adds support for binary ufuncs for the CUDA target (bitwise_and, bitwise_or, etc.). Currently there aren't any unit tests for np.left_shift and np.right_shift. I didn't add them because there was a comment here saying the tests were not added for the CPU target either.

gpuci run tests

gpuci run tests


@exception.status == "500" is always false (even during a 500 error)

This is probably due to something I've set up in my application (newish to Rails,  and Rails 5 doubly so), but:
None of the logic contained within the div tag on the show page ever triggers, as
if @exception.status == "500" is always false.
(Here is the div tag for reference):
<%= content_tag :div, class: "exception", data: { status: @exception.status, response: @exception.response.to_s.humanize, rails: Rails.version }, onclick: ("location.href=\"#{root_url}\";" if @exception.status == "500" && Rails.application.routes.recognize_path("/")), title: ("Return Home" if @exception.status == "500" && Rails.application.routes.recognize_path("/")) do %>
Changing this to if @exception.status == 500 works
(no quotes, comparing against an integer instead of a string)
I added the following span tags to the show page, to test whether the new comparison works:
  <%= @exception.status == "500" %>

  <%= @exception.status == 500 %>

Below, you can see that it still regards the comparison using "500" as false,
but evaluates the comparion using 500 as true.

Is this something unique to Rails 5? Perhaps some setting I toggled/forgot to toggle somewhere in a config file?
Changing "500" to 500 works just fine and allows me to go about my day, so this is purely motivated by curiosity.
Thanks!

Works for me and I'm using Rails 5.1.2 - do you have a repo I could look at? Or maybe you have some settings in application.rb which could be causing problems?

Ahhh, that'd probably do it -- I'm running Rails 5.0.1.
Unfortunately, a lot of the project is locked in to that version (just tried to update, and some of our weird, niche gems are leaning on ActiveRecord 5.0.0, which blocks the upgrade to Rails 5.1.2)
Again, I found a workaround (just changing "500" to 500), so this was mostly just curiosity.
I'd be fine chalking this up to Rails versioning weirdness and marking this resolved.
Thanks!

I've closed the issue but I doubt it is a Rails versioning problem. If you have niche gems which rely on 5.0, perhaps they could be causing a deeper conflict?
Off hand, do you know which gems are locking the version?

Sure.
We're using tinyTDS to connect to a SQL Server.
Based on my Lockfile, it looks like tiny_tds is reliant on composite_primary_keys, and both those gems are locked into activerecord 5.0.0


Connect to domain (will get domain tomorrow)

matt you have 3 hours

Mart where is the domain

jesse plox halp


Call to an undefined method, that is defined

Larastan Version: 0.5.8
--level used: 5 -- but I can replicate this at 2

Description
I'll be honest, I'm not sure if I'm doing something wrong in my configuration or not, but this feels like an issue for Larastan. I'm using the repository pattern so I've got an EloquentRepository that gets extended.
Here's the EloquentRepository
<?php

declare(strict_types=1);

namespace App\Domain\Repositories;

use App\Helpers\QueryCache;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Support\Collection;
use Ramsey\Uuid\Uuid;

class EloquentRepository
{
    protected Model $model;
    protected QueryCache $cache;
    protected string $cacheKey = '';

    protected array $withData = [];

    public function __construct()
    {
        $this->cache = resolve('QueryCache');
        $this->cache->setKey($this->cacheKey);
    }

In my extending class:
<?php

declare(strict_types=1);

namespace App\Domain\Repositories;

use App\Domain\Models\Listing;

class EloquentListingRepository extends EloquentRepository
{
    public function __construct(Listing $model)
    {
        parent::__construct();
        $this->model = $model;
    }

    public function hasSlug(string $slug): bool
    {
        return $this->model->where('slug', '=', $slug)->count() > 0;
    }

Laravel code where the issue was found

    public function hasSlug(string $slug): bool
    {
        return $this->model->where('slug', '=', $slug)->count() > 0;
    }

So this code runs fine, but when I run phpstan I get:
  21     Call to an undefined method Illuminate\Database\Eloquent\Model::where().

Listing is a descendant of Model too. This is getting rather verbose so let me know if you need something else from me...or if I'm just totally screwing something up.

Hi,
Yes this is a known issue. And I think it'll be fixed with #565

Very tricky!
You need
parameters:
    inferPrivatePropertyTypeFromConstructor: true

@szepeviktor Tried that it didn't make a difference

@canvural Thanks!

@JoeCianflone #565 was merged. Can you try this again on master?

@canvural I'll check this out tonight for sure and I'll let you know.
Thanks!

@canvural This seems to be fixed with #565 I've been kinda pulling apart my codebase for the past couple of days so I've got some other issues I need to resolve, but it's looking good!


Unable to create new template  Error while querying work items: VS403474

So I am having frustrations creating a template.

Getting this error
Error while querying work items: VS403474: You requested 424 work items which exceeds the limit of 200
Error while querying work items: VS403474: You requested 415 work items which exceeds the limit of 200
Whilst the project has 0 work items

AB#3616

When I do this (colleague of Rob's)

@SQLDBAWithABeard thanks for reporting. We will inspect this. Meanwhile, Template Builder has some limitations which it can handle up to 200 work items of a type. If it exceeds, this would be expected error.

@aksh-h Excellent, it was very strange as there were no work items in the Project as it is a brand new template Project, I had hit that earlier when I used a project with many work items (which is why this is an empty one!)

@SQLDBAWithABeard we suspect this is returning from API end. If this is the case we will check with product team and get back to you.

Thank you :-)

@SQLDBAWithABeard Area you still facing the same issue?

@aksh-h I will let you know when I am back at my client this week

HI @SQLDBAWithABeard  - Any update?  Aksh-h and I are doing routine maintenance and wanted to see if this is still causing an issues.  Thanks!

I have encountered the same error:
Error while querying work items: VS403474: You requested 480 work items which exceeds the limit of 200
It has just started today. Maybe it is caused by recent intense usage. Looking for an immediate help on this. Thanks!

I'm getting the same error:

But on project:

Thanks all.  I want to make sure everyone understands.  The 200 limit is related to a limitation in the Azure DevOps API where we're limited to 200 work items without implementing paging (which we have considered out-of-scope).  We would consider accepting PRs if anyone is interested in implementing paging to get past the 200 work item limit, but we don't have any plans for change this ourselves.  Akshay has published a list of known limitations here: https://github.com/microsoft/AzureDevOpsDemoGenerator/blob/master/docs/Limitations.md

This error occurs when creating a template based off a brand new new project with no work items in a brand new org as well. The resulting template does import successfully.
_Selected Project: Template,   Process Template: Agile (system)
Teams: 1
Iteration: 1
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Invalid URI: The Uri string is too long.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Invalid URI: The Uri string is too long.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Invalid URI: The Uri string is too long.
Error while querying work items: Object reference not set to an instance of an object.
Error while querying work items: Invalid URI: The Uri string is too long.
Error while querying work items: VS403474: You requested 222 work items which exceeds the limit of 200
Error while querying work items: VS403474: You requested 222 work items which exceeds the limit of 200_

@DevOps-Travis  - Do you think this issue is related to the original opened last October?  We'd already closed this issue and it may get lost.  If you think it is related, let me know and I'll reopen it.  Otherwise, can you copy/pasted with any other details into a new issue?  Thank you!

As of 2/16/2021, what has been described above has not been resolved.  Using the AzureDevOpsDemoGenerator tool, I get the VS403474 error when trying to create a template.  In my case, my project had less than 60 total work items, far below the 200 limit.  This tool could be enormously helpful if it would work properly.  Please advise as to what can be done to resolve this error.

@tinylabspace could you please try out in prod? let us know your feedback.

did anyone resolve this VS403474 issue?


Benchmark upload failure: No such file or directory

Description
just benchmarks/tpch upload_log main<PHONE_NUMBER> 1
just tpch/upload_log main<PHONE_NUMBER> 1
cp: cannot stat 'timings.csv': No such file or directory
Connected to Cloud deployment (TLS enabled): benchmarks
┌──────────┐
│ Int64(1) │
│       ── │
│    Int64 │
╞══════════╡
│        1 │
└──────────┘
Error: External error: External error: No such file or directory (os error 2)

Caused by:
    0: External error: No such file or directory (os error 2)
    1: No such file or directory (os error 2)
error: Recipe `upload_log` failed with exit code 1
error: Recipe `tpch` failed on line 5 with exit code 1

the timings file is only generated if you export LOG_TIMINGS=true.

I don't think this is an issue anymore? Should we close this?

I think the problem was "if the benchmarks failed and didn't write a file" we tried to upload a file that didn't exist.
I'm not sure what changed to make this not possible, but if so, then I'm happy to close it.

Yeah, that might still be a problem. But I'll take this up when benchmarking dist exec stuff. Let's leave this open and I'll assign it to myself.

Reassigned to me as I wrote those benchmarks.


[SUGGESTION] Split Screen Pathway Overlap

A lot of the time I work from my laptop where I have a small workspace and have both a browser and obsidian open. With this layout, the pathway in the top bar overlaps the title set by obsidian. Would it be possible to remove the obsidian native title when obsidian window is < a certain window size? Or another way to avoid this overlap?
BTW I love this add-on. Thank you so much for making it!!

You can use CSS to set an opaque background for #quick-explorer, which will make it block out the title, e.g.
div#quick-explorer {
    background-color: var(--background-modifier-cover) !important;
}

This used to be the default, but it made the explorer bar unusable on certain light themes that used titlebar text colors close to the background-modifier-cover color.

Your Awesome! Thanks!


Updating go.opentelemetry.io/contrib

Fixes for https://issues.redhat.com/browse/RHOAIENG-1263
Introduced through<EMAIL_ADDRESS><EMAIL_ADDRESS>and others
<EMAIL_ADDRESS><EMAIL_ADDRESS>Fixed in<EMAIL_ADDRESS>

The PR does not look right to me. There is a change in go.mod without any corresponding induced change in go.sum, that's a first red flag. I'll take a better look tomorrow, if nobody preempts me sooner.


Add support for building master/release branches to Jenkins configuration

Flyby: Try to fix setting buildid for GitHub status links, format CTest script, general cleanup.

Merging as this is required to have builds on the master and release branches.


Timeout waiting for camera

Hello, sir.
Today I found that the camera will take several seconds to get an image use the code under:
        stopWatch.reset();
        fg->SWTrigger(); //TRIGGER
        if (! fg->WaitForFrame(im.get(), 0))
        {
          std::cerr << "Timeout waiting for camera!" << std::endl;
          return -1;
        }
        double time = stopWatch.getTime();
        std::cerr<< "elapsed_time:" << time << std::endl;

And I notice that when camera temperature is up to 50℃ will cause that to happen.
But It can work normally when the temperature is around 30℃.
(When Temperature 36.7℃，the elapsed_time:18435ms)
Do you have any advice?

When Temperature 36.7℃，the elapsed_time:18435ms

Hey @GoodTekken , what type of camera are you using? I guess it is an O3D3xx am I right?
The general recommendation is to mount the camera in a way that there is a good heat dissipation provided.

Yes,sir. The camera is O3DP03.
And Ping is okay.
jt@JT:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.276 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.359 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.365 ms
64 bytes from <IP_ADDRESS>: icmp_seq=4 ttl=64 time=0.405 ms

Now I switch the camera to string mode and use the order with"ifm",It hints "Timeout waiting for camera!" too.
[ INFO] [1652252488.667637285]: Loading nodelet /ifm3d_ros_examples/camera of type ifm3d_ros/camera_nodelet to manager camera_standalone_nodelet with the following remappings:
[ INFO] [1652252488.671071466]: waitForService: Service [/ifm3d_ros_examples/camera_standalone_nodelet/load_nodelet] has not been advertised, waiting...
[ INFO] [1652252488.677003864]: Initializing nodelet with 4 worker threads.
[ INFO] [1652252488.692297637]: waitForService: Service [/ifm3d_ros_examples/camera_standalone_nodelet/load_nodelet] is now available.
[ INFO] [1652252488.756652292]: IP default: <IP_ADDRESS>, current <IP_ADDRESS>
[ INFO] [1652252488.757925027]: pcic port check: current 50010, default 50010
[ INFO] [1652252488.849718817]: Running dtors...
[ INFO] [1652252488.849813273]: Initializing camera...
[ INFO] [1652252489.866697382]: Initializing framegrabber...
[ INFO] [1652252489.867918164]: Nodelet arguments: 16, 50010
[ INFO] [1652252489.868028264]: Initializing image buffer...
[ WARN] [1652252490.369207744]: Timeout waiting for camera!
[ WARN] [1652252490.869767394]: Timeout waiting for camera!

The mount is same as preview. And the camera can run well a few days ago.
What can make the camera timeout? Or XMLRPC ?

Okay, it looks like you are using the O3DP03 with the standard ROS node. Typically the O3DP03 comes with its own interface which configures the camera to software trigger. As in your example above one has to trigger the camera. As far as I know the standard ROS node expects the camera to be configured in continuous mode. This means it times out because no data is received because no one triggers the camera.
Can you please describe what is your goal and what data you are looking for?

Yes, I have set the camera in continuous mode, but still "TimeOut".
I want to get the point cloud from the camera and make a test for pallet detection.

How odd! I can get the data from the camera before. No mather triggered mode or continuous mode.

Can you please grab the trace logs from the camera?
$ ifm3d trace

No , it cannot.
jt@JT:~$ ifm3d trace
ifm3d error: -100001
Lib: XMLRPC Timeout - can you `ping' the sensor?
jt@JT:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.243 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.341 ms

Please try
$ ifm3d trace --limit 100

There is a known bug in the libxmlrpc when it comes to larger chunks of data

jt@JT:~$ ifm3d trace --limit 100
ifm3d error: too many positional options have been specified on the command line
jt@JT:~$ ifm3d trace --limit 1
ifm3d error: too many positional options have been specified on the command line
jt@JT:~$ ifm3d trace --limit 2
ifm3d error: too many positional options have been specified on the command line
jt@JT:~$ ifm3d trace --limit 1000
ifm3d error: too many positional options have been specified on the command line
jt@JT:~$ ifm3d trace --limit 100
ifm3d error: too many positional options have been specified on the command line

Sorry there was a typo:
$ ifm3d trace --limit=100

$ ifm3d trace --limit=100
https://pastebin.com/H2ygapN6$ ifm3d trace --limit=100

T: 366.4476, P: 375,  C: WARN,  S: iom,  M: DIAGC_DBUS_EVENT_UB_UNDERVOLT
T: 366.4504, P: 375,  C: WARN,  S: iom,  M: DIAGC_DBUS_EVENT_VLED_UNDERVOLT
T: 366.4521, P: 375,  C: WARN,  S: iom,  M: DIAGC_DBUS_EVENT_UB_UNDERVOLT
T: 395.5820, P: 375,  C: WARN,  S: iom,  M: DIAGC_DBUS_EVENT_VLED_UNDERVOLT

Indicates your power supply is not able to provide the specified current and voltages. Please check your power-supply

It can get the Image suddenly , the trace below:
can get the image

May I suggest to use a power-supply for testing, to get it out of the loop.

Thank you, sir. And sorry for the late reply.
when I use the power supply, It can work quite well.


Switch main branch from master to main

I'd say V2 is the perfect time to switch to using main branch instead of master.

yes, agree. For late this week the M1 is planned to be released, will do the switch that time if not objections.
Also @metacosm is working on fixes for quarkus extension AFAIK, do you tink we will need a release for the SDK itself for that?

Yes, we probably should release a version of 1.9.x as well.

Accidentally released 1.10.0, I mean to test it  but turns out the workflow is picked up from the branch where the tag is selected from. [facepalm]
But renamed master to main. Now main is the default branch.

Not sure if we can get 1.10.0 removed from Maven central…

Then again, the release is there so… 🤷🏼
This issue should be closed now, though, correct?

Not sure if we can get 1.10.0 removed from Maven central…

Me neither. Maybe @adam-sandor ?
Sure will close the issue.


White line separating maximized app and taskbar on windows

Hi,
There is a small white line separating the bottom of the app and the taskbar when the app is maximized on windows. This is a minor issue, so no need to fix it urgently.  See image: https://imgur.com/WKS8ww2
Version: 0.12.0
OS: Windows 8.1

This has nothing to do with the dark theme, it's a NW.js related issue and I can't do anything about it. It's a miscalculation of the content height of the application window in NW.js v0.12.3. This has been fixed in the latest release (v0.13.0), but I can't upgrade right now because of some other issues.


fix: error handling for display name in idp creation

Description
Updated regex for the allowed characters for displayName in idp creation. Previously we were not showing any error message against violation of regex. Updated regex and error translations bases on certain violation.
Changelog entry:
- **IDP Creation**
  - display error message for invalid input of displayName [#1264](https://github.com/eclipse-tractusx/portal-frontend/issues/1264)

Why
To have better UX to let the user know what he is doing wrong and what is expected for displayName and what type of string value BE expects for displayName.
Issue
https://github.com/eclipse-tractusx/portal-frontend/issues/1264
Checklist

[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[x] I have added tests that prove my changes work
[x] I have checked that new and existing tests pass locally with my changes
[x] I have updated the changelog of my change

Please update changelog

@lavanya-bmw We don't recommend to update the changelog anymore, as it just lead to one conflict after the other and in general issues, we recommend to add it to the PR description now.

Please resolve conflicts

conflicts are resolved.

Hi @isaadansari @kunalgaurav-bmw  @ss-nikunj ,
Please review. This is impacting the productive environment.


add stateful checkpoints support for java statemgrs

This is the java state manager changes to support stateful processing

the last commit includes

some code refactoring in the IStateManager.java for easier reading
updated getStatefulCheckpoint  to getStatefulCheckpoints

In the future please don't reorder unrelated methods in a feature PR, since it makes it hard to read the diff of functional changes.


[SYSTEMML-625] Handle circular import references

This patch updates parser component to allow scripts to run in cases where circular source references exist.  Previously, a circular import (e.g., a script sources itself) would result in stack overflow error where
DMLParserWrapper.doParse and DMLSyntacticValidator.exitImportStatement infinitely loop during ParseTreeWalker.walk.  Test scripts are included for both DML and PyDML to exercise various forms of circular dependencies.

The new code tracks imported scripts in a static variable and skips/defers building the corresponding DMLProgram for redundant/circular reference.  A static variable was used to facilitate access in exitImportStatement across multiple DMLSyntacticValidator's which get instantiated during processing.
Note importing the same script under different namespace is allowed (namespace conflicts to be addressed in SYSTEMML-631).
All tests passed in OnDemand build 149.

thanks @gweidner that looks already pretty good - just two comments.

Thread-local state: could you please change the global state (static map) to thread-local state management in order to prevent side-effects between concurrent scripts parsing in a shared JVM process. The scenario is JMLC scoring (one prepared script per core) in a shared Spark executor process.
Consistency function keys: Internally (independent of the language facet), we try to always use DMLProgram.constructFunctionKey() for building fully qualified function names. It would be good to reuse that in order to avoid surprises for devs expecting a certain schema.

Thank you @mboehm7 for your time and always helpful comments.  I've incorporated ThreadLocal for the static map in CommonSyntacticValidator and constructFunctionKey for the map's keys in DML/PyDMLSyntacticValidator.  I patterned ThreadLocal changes after similar ThreadLocal usage in hops Recompiler but please let me know if I've misinterpreted anything.
Prior to pushing this commit of 3 files I rebased and pushed this branch to merge in latest parser updates from master.  PR build 287 in progress for commits containing ThreadLocal.

LGTM - thanks @gweidner

Thank you @gweidner . I will merge.

Thanks Glenn for this great contribution! I'll close the JIRA since Apache JIRA is on 'lockdown' mode today.

Thanks, @gweidner!


Push updates to Docker

Good day all,
Do you plan on pushing the latest release of elasticsearch-dump v6.84.1 to your docker registry? Some of the updates you have made to that version would resolve a few of our CVE findings from our scan tools.
Please let me know if you need any more information.

Done, sorry for the slow turnaround


Patch to surface elevation LUT grid.

This fixes a bug in assigning the surface elevation LUT grid in case just a mean value is used.

This is a no-brainer typo fix that we'll fold in as soon as checks pass.  Thanks Niklas.


Adding Quality Selector to plyr when using HLS Stream

I was looking at a lot of PR's if this feature is supported but came across a lot where  it is closed and the implementation or the CRUX is not shared.
In one such PR is saw CRUX implementation , and tried to use it along with plyr and Hls, but seems like it dosent work can you please shed some light, if this feature is supported or not.
I have added this code but the selector fails to add the details from the manifest to the plyr controls..
<!DOCTYPE html>
<html>
   <head>
      <meta charset="utf-8">
      <title>HLS Demo</title>
      <link rel="stylesheet" href="https://cdn.plyr.io/3.5.10/plyr.css" />
      <style>
         body {
         max-width: 1024px;
         }
      </style>
   </head>
   <body>
      <video preload="none" id="player" autoplay controls crossorigin></video>
      <script src="https://cdn.plyr.io/3.5.10/plyr.js"></script>
      <script src="https://cdn.jsdelivr.net/hls.js/latest/hls.js"></script>
      <script>
         (function () {
         	var video = document.querySelector('#player');
         	var playerOptions= {
         		quality: {
         			default: '720',
         			options: ['720']
         		}
         	};
         	var player;
         	 player = new Plyr(video,playerOptions);
         	if (Hls.isSupported()) {
         		var hls = new Hls();
         		hls.loadSource('https://content.jwplatform.com/manifests/vM7nH0Kl.m3u8');
         				//hls.loadSource('https://test-streams.mux.dev/x36xhzz/x36xhzz.m3u8');
         	hls.attachMedia(video);
         	hls.on(Hls.Events.MANIFEST_PARSED,function(event,data) {

 // uncomment to see data here
//                   		console.log('levels', hls.levels);  we get data here but not able to see in settings .

         		playerOptions.quality = {
         			default: hls.levels[hls.levels.length - 1].height,
         			options: hls.levels.map((level) => level.height),
         			forced: true,
             // Manage quality changes
             onChange: (quality) => {
             	console.log('changes',quality);
             	hls.levels.forEach((level, levelIndex) => {
             		if (level.height === quality) {
             			hls.currentLevel = levelIndex;
             		}
             	});
             }
         };
        });
       }

          // Start HLS load on play event
          player.on('play', () => hls.startLoad());

          // Handle HLS quality changes
          player.on('qualitychange', () => {
          	console.log('changed');
          	if (player.currentTime !== 0) {
          		hls.startLoad();
          	}
          });
         })();

      </script>
   </body>
</html>

Can you please use the existing issue for this.

https://github.com/sampotts/plyr/issues/1741

@sampotts But most of the issues are not tracked , can you please shed some light , i will add my findings in the comment in #1741

They are tracked but I get very little time to look at issues. My job gets more painful when there's 5 issues for the same thing because people are too lazy to use the search...
I have a life, family and a full time job so as you can imagine I have to prioritise where I spend the little time I have. For me at the moment the next big thing will be making a v4 that can handle plug-ins so it's easier for other developers to write add-ons such as HLS quality options.
I don't know a huge amount about HLS so I can't help but the best place to discuss this is in one issue rather than spread across multiple issues.

@sampotts i really appreciate the help you are giving to the community and having such a library that helps a hell lot of devs and keeping all of them happy is really difficult task, unfortunately i was able to search all the issues but die to no outcome in them i thought of raising another but now i have added my findings there in #1741 . Looking forward to a solve .

I'll have a read through when I get a chance. HLS obviously seems very popular in recent times so I'm keen to get up to speed on it and hopefully get some features out for it.


Missing mmcif package

Hello, I really appreciate your work and contributions. Recently I was trying to access the rna3db-mmcifs.tar.xz download link but find the link is missing. Would you mind helping figuring it out?

There is an updated file with a fix
https://github.com/marcellszi/rna3db/releases/download/2024-01-10/rna3db-mmcifs.v2.tar.xz


Update search_tweets.py

fix a bug that cause the param "results_per_file" cannot be loaded as "int" when writing result stream

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


[JavaToolInstallerV0] Updated dependencies

Task name: JavaToolInstallerV0
Description: Updated dependencies to fix vulnerabilities.
#14619 is required. Successful build example.
Documentation changes required: No
Added unit tests: No
Attached related issue: #903
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

ToDo: commit package-lock.json after #14619 is merged and related package is released.

ToDo: update artifact-engine package containing the following change.

Already updated in https://github.com/microsoft/azure-pipelines-tasks/pull/14703


Dart2js shouldn't warn about a non-abstract class not implementing its interface if a superclass overrides noSuchMethod.

Example:
class Mock {  noSuchMethod(i) => 42; }
abstract class Foo { int foo(); }
class DontWarnMe extends Mock implements Foo {}
main() { print(new DontWarnMe().foo()); }

This prints a warning that DontWarnMe doesn't implement foo, which is no longer allowed by the specification. The analyzer does not give that warning.
This incorrect warning causes uses to have to add an unnecessary noSuchMethod(i) => super.noSuchMethod(i); on all Mock classes to avoid the warning. It would be great to not have to do that.

@johnniwinther All yours!


docs: automate docs with eslint-doc-generator

I built this CLI tool eslint-doc-generator for automating the generation of the README rules list and rule doc title/notices for ESLint plugins. It follows common documentation conventions from this and other top ESLint plugins and will help us standardize documentation across ESLint plugins (and generally improve the usability of our custom rules through better documentation and streamline the process of adding new rules).
This is a follow-up to my previous work to manually improve the documentation. eslint-doc-generator is significantly more robust compared to the previous documentation generator script/tests which I have now removed. It has additional functionality (for example, the rules list legend is auto-generated, and the rules list will show additional columns of information when applicable) and 100% test coverage.

Thanks @MichaelDeBoey! Yes I think it's a good goal to move eslint-doc-generator to @eslint-community after it reaches a v1 release. I am currently working to implement all the essential functionality and bug fixes in it so that I can introduce it to ~10 of the top ESLint plugins (and address feedback that I hear during this process).

That's fair. But yeah, it shouldn't be a big deal, I'll be keeping this updated as I work toward v1.


Remove manifest added by mistake

I don't see any makefile targets to generate that specific file in the root dir so I think it could have been specific to what he was doing (perhaps run the manifest image and choose that path himself) - correct me if I am wrong.
If that was the case then I say no @mhmxs


convert onnx to trt fault

hello, when i used onnx convert to trt engine ,some mistakes occured:
[07/13/2022-16:04:45] [TRT] [V] --------------- Timing Runner: Slice_4 (Slice)
[07/13/2022-16:04:45] [TRT] [V] Setting a default quantization params because quantization data is missing for Slice_4
[07/13/2022-16:04:45] [TRT] [W] GPU error during getBestTactic: Slice_4 : an illegal memory access was encountered
[07/13/2022-16:04:45] [TRT] [E] 1: [resizingAllocator.cpp::deallocate::100] Error Code 1: Cuda Runtime (an illegal memory access was encountered)
[07/13/2022-16:04:45] [TRT] [E] 1: [virtualMemoryBuffer.cpp::~StdVirtualMemoryBufferImpl::121] Error Code 1: Cuda Runtime (an illegal memory access was encountered)
[07/13/2022-16:04:45] [TRT] [V] Deleting timing cache: 788 entries, 2475 hits
[07/13/2022-16:04:45] [TRT] [E] 10: [optimizer.cpp::computeCosts::2011] Error Code 10: Internal Error (Could not find any implementation for node Slice_4.)
Failed to create the engine

似乎是TensorRT的bug, 可以尝试更换trt版本


[Request] Cache expiration based on a time of the day.

Hello,
i have data that is invalid everyday at 9am. So far i have setup a 1 day cache first, but it is not perfect, because if a user came at 23:00 the day before, he will have the invalid data from 9 to 23:00 the next day.
Is it possible to do ?

I'm not 100% sure what the time-related logic would look like for your specific use case, but in general, the cachedResponseWillBeUsed lifecycle callback gives you a chance to inspect a cached response prior to its use, and return null if it should be considered invalid.
You can use this like:
const customExpirationPlugin = {
  cachedResponseWillBeUsed: async ({cacheName, request, matchOptions, cachedResponse, event}) => {
    // I'm assuming that this is what you want? Customize as needed.
    const dateHeader = cachedResponse.headers.get('date');
    if (dateHeader) {
      const parsedDate = new Date(dateHeader);
      // Check whether parsedDate meets some criteria?
      if (...) {
        // If whatever your criteria for expiration is met, return null.
        return null;
      }
    }

    // Otherwise, consider the cached response "fresh" and return it.
    return cachedResponse;
  },
};

const cacheFirstStrategy = new CacheFirst({
  cacheName: '...',
  plugins: [customExpirationPlugin],
  ...
});


Rest API, doesnt show releases of Migrated Repository

Gitea version (or commit ref):1.7.3
Git version: 2.11.0
Operating system:debian stretch
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
If I create a repository via the migration tool  releases dont show up in the rest response.
Steps to reproduce:
click on "+" "new migration"
enter https://github.com/go-gitea/gitea into "clone url"
query the rest interface via bash (or swagger)
token=xxx
usern=xxx
server=server .name
curl -X GET "https://$server/api/v1/repos/$user/gitea/releases?access_token=$token" -H  "accept: application/json"
No  migrated releases are  shown, if you create a new release in this  this repository the rest api returns a result, but the migrated ones are still missing.
Screenshots

hiere is a screenshot, the newly entered release "test" is shown in the api, the migrated ones are not.

There is a difference between releases and tags. Note in your screenshot how the new release you created looks different from the imported tags.

ah ok, thats confusing, but the migrated repository still lists 53 releases, so they must have been imported? or not?

just like on github the releases tab includes tags as well as releases.

Thanks for the quick reply, so to summerize:
even if counterintuitive at first it works as intended.
Releases are not imported from github only tags are.
Tags can not by queried at the moment by the rest api but will be in the 1.8 release
https://github.com/go-gitea/gitea/issues/2738


Welcome: links to install extension could read a little more (aria)

Currently all I hear from a screen reader is the text of the link, but I suggest to add an aria label that tells that the link is for installing the extension.

@bpasero  I've added a title attribute that is read by VoiceOver. Which reader are you using?

I take it back, VoiceOver first reads "link, Docker" but then a much longer explanation.


Click on nth element that have the same reference than others

Expected behavior
I have a page with three links and the same text.
Example:
Click here
Click here
Click here
I try to click on the 3rd link with the command click(link("Click here")) or click("Click here").
All the times when the script runs, the clicks occurs on the first link e i don't know if the taiko don't have a parameter to select the nth element with the same reference or if i'm doing something wrong.
Actual behavior
I don't have an appropriate parameter to select the nth element that have the same reference than others
Versions
Taiko 1.0.0
Node 12.6.0

@paulofrizzo Hey Taiko doesn't have index access to specify which element you wanna click. It takes the first element matches that your query. For now, you can use our proximity selectors to select the specific element you wanna click.

Is there any intention to develop this feature? Currently proximity selectors don't meet
some needs.

@paulofrizzo does chaining of proximity selectors help in your case?
$ selector may be helpful. Kindly let us know if this helps.

For more info on the $ selector please refer
https://taiko.gauge.org/#dollar

Closing this due to inactivity. Feel free to reopen if the issue persists.


"Type a file name" button

When I use the button that allows the user to type in a location and press the Enter key the plugin will use the current location and will not change to the new one. It would not be a problem except that I am trying to use AutoIt to automate some repetitive tasks and want to type in this location.

Using Windows 7
Gimp 2.8.14

Incorporated in version 2.3.


test: heapsampling.go is flaky

heapsampling.go is flaky.
It needs to either be fixed to not be flaky, or be deleted.
/cc @aclements @dr2chase @dvyukov and @rauls5382 (who appears to be the first and only person to ever touch that file when it was added in https://go-review.googlesource.com/14590 for #12620)

I'll take a look. Please assign it to me.

I can't assign you until you're a "member of a team", so I did that. See if you can assign yourself now after accepting. That said, we don't use the "Assignee" all the time. Just saying you're working on it is enough.

Assigned.

Example failure:
https://storage.googleapis.com/go-build-log/0f9f239a/windows-amd64-gce_a28c2438.log
# go run run.go -- heapsampling.go
exit status 1
panic: main.alloc want total count > 0 && <= 307200000, got 0

goroutine 1 [running]:
main.checkAllocations(0xc102f5c000, 0x9, 0x3b, 0x5338c0, 0xa, 0x186a0, 0xc08202bef0, 0x3, 0x3)
	C:/workdir/go/test/heapsampling.go:82 +0x578
main.main()
	C:/workdir/go/test/heapsampling.go:34 +0x164
exit status 2

FAIL	heapsampling.go	2.465s
2015/10/29 14:50:56 Failed: exit status 1

I don't seem to be able to reproduce this on linux.
In any case, getting a 0 means that no samples were collected in main.alloc , which shouldn't happen with the default sampling rates. We will collect a minimum of 1 sample every ~10MB, and the loop in that function allocates 180MB.
Is it possible that sampling is disabled on this platform, or that the sampling rate has been changed? Or could there be background goroutines allocating memory? How flaky is the testcase, does it fail frequently?

@aclements might have some stats on flakiness and where it occurs.

Seems to happen just about everywhere except Linux, but always on amd64:
2015-10-06T07:05:51-3e6334e/openbsd-amd64-gce56
2015-10-10T00:49:00-2d5601d/dragonfly-amd64
2015-10-12T22:35:31-8dd52cf/dragonfly-amd64
2015-10-14T00:46:21-a6f69b3/dragonfly-amd64
2015-10-19T09:58:15-5d88323/dragonfly-amd64
2015-10-20T15:48:49-7d2c6eb/dragonfly-amd64
2015-10-20T15:48:49-7d2c6eb/freebsd-amd64-gce93
2015-10-20T22:11:11-7628521/freebsd-amd64-gce93
2015-10-21T04:21:16-b60c820/dragonfly-amd64
2015-10-21T16:26:34-a42f668/dragonfly-amd64
2015-10-21T18:37:45-c279250/windows-amd64-gce
2015-10-23T17:30:09-3abb844/windows-amd64-gce
2015-10-23T20:07:52-9238cbd/dragonfly-amd64
2015-10-28T05:53:28-492a62e/dragonfly-amd64
2015-10-29T16:25:37-ab7e82e/dragonfly-amd64
2015-10-29T16:25:37-ab7e82e/freebsd-amd64-gce93
2015-10-29T19:44:59-6f8a665/dragonfly-amd64
2015-10-30T18:40:31-ddbc802/freebsd-amd64-gce93
2015-10-30T20:35:20-729abfa/dragonfly-amd64
2015-10-30T20:35:20-729abfa/windows-amd64-gce
And, since I've been playing with the statistics of flaky tests, I can tell you that the probability that a commit will fail this test is 6.5% since it started happening. Assuming the failure is Bernoulli (which looks about right, but I don't have my automatic test working yet :), there's better than even odds that the bug was introduced within 10 commits of the first failure, but you have to go back 44 commits to get to 95% odds.

Austin, I've been trying to look into this further but even on a windows
machine I haven't been able to reproduce (after reenabling the testcase).
Would you have any suggestions as to how can I reproduce it for further
investigation? Are there any machines I could access where the problem
reproduces?
Thanks,
Raúl E Silvera | SWE |<EMAIL_ADDRESS>|<PHONE_NUMBER>
On Mon, Nov 2, 2015 at 2:52 PM, Austin Clements<EMAIL_ADDRESS>wrote:

Seems to happen just about everywhere except Linux, but always on amd64:
2015-10-06T07:05:51-3e6334e/openbsd-amd64-gce56
http://build.golang.org/log/fcc29751c221513de9d9b6a645ce0ffc9d8f240b
2015-10-10T00:49:00-2d5601d/dragonfly-amd64
http://build.golang.org/log/622c9583b6e4bfda4c8b229538115bc46a82bd6c
2015-10-12T22:35:31-8dd52cf/dragonfly-amd64
http://build.golang.org/log/77978e8cc57d7a58ed76a621d66125a1f0961f47
2015-10-14T00:46:21-a6f69b3/dragonfly-amd64
http://build.golang.org/log/89359a7670dde5d7c27f200942494f94d6806757
2015-10-19T09:58:15-5d88323/dragonfly-amd64
http://build.golang.org/log/9c20053bd47f9166f0456eb1eede2ce8a20f6e5a
2015-10-20T15:48:49-7d2c6eb/dragonfly-amd64
http://build.golang.org/log/8ffd10f4920f64d4117e119b015f0d0cd9f60ff8
2015-10-20T15:48:49-7d2c6eb/freebsd-amd64-gce93
http://build.golang.org/log/c6d175f682432d5302436470c0308d0479bac687
2015-10-20T22:11:11-7628521/freebsd-amd64-gce93
http://build.golang.org/log/8d1788ea388a34d116e81cb4ce06d9ffd5863131
2015-10-21T04:21:16-b60c820/dragonfly-amd64
http://build.golang.org/log/1e506754bc30614d41b298b2682134cd6123ebab
2015-10-21T16:26:34-a42f668/dragonfly-amd64
http://build.golang.org/log/f71535ec1d0ad8c29ae98328663cb978f3b3c9e4
2015-10-21T18:37:45-c279250/windows-amd64-gce
http://build.golang.org/log/6c58cc5feba66cd5df15adf54f06c46a162d7072
2015-10-23T17:30:09-3abb844/windows-amd64-gce
http://build.golang.org/log/ef52aebbed1b3ddb17abbb31578004ba89f32720
2015-10-23T20:07:52-9238cbd/dragonfly-amd64
http://build.golang.org/log/c939abf58e57f72bdbf2b54b071466415290a269
2015-10-28T05:53:28-492a62e/dragonfly-amd64
http://build.golang.org/log/c726fcd133ddcd99f91d26ac2f9d5b5924fb3ee7
2015-10-29T16:25:37-ab7e82e/dragonfly-amd64
http://build.golang.org/log/a3baf376900aeea228843b99a9da5e45702b1090
2015-10-29T16:25:37-ab7e82e/freebsd-amd64-gce93
http://build.golang.org/log/509fd21de367c0ad8778c490a12dcce74459d7f8
2015-10-29T19:44:59-6f8a665/dragonfly-amd64
http://build.golang.org/log/335f661625f274df4101879f0013990d216839d6
2015-10-30T18:40:31-ddbc802/freebsd-amd64-gce93
http://build.golang.org/log/3af876cdb42922709111d07ac714eb873752a534
2015-10-30T20:35:20-729abfa/dragonfly-amd64
http://build.golang.org/log/ea1959dba0bab3304994b84996930da55ee42460
2015-10-30T20:35:20-729abfa/windows-amd64-gce
http://build.golang.org/log/aed17d73dd72153e5c4673416b3b9676f9e707cd
And, since I've been playing with the statistics of flaky tests, I can
tell you that the probability that a commit will fail this test is 6.5%
since it started happening. Assuming the failure is Bernoulli (which looks
about right, but I don't have my automatic test working yet :), there's
better than even odds that the bug was introduced within 10 commits of the
first failure, but you have to go back 44 commits to get to 95% odds.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/13098#issuecomment-153183278.

It took an overnight run, but I was able to reproduce this four times in ~150 runs on freebsd-amd64-gce93 for commit ddbc802 (the last known failure) with the following:
git checkout ddbc802 && \
VM=$(gomote create freebsd-amd64-gce93) && \
gomote push $VM && \
gomote run $VM ./go/src/make.bash && \
gomote run -e GOPATH=/tmp/workdir/x $VM /bin/sh -c 'PATH=$PWD/go/bin:$PWD/x/bin:$PATH; go get golang.org/x/tools/cmd/stress && cd go/test && stress -failure "main.alloc want" go run run.go'

while running the following to keep the VM up
while sleep 300 && gomote ping user-austin-freebsd-amd64-gce93-0; do true; done

It seems that running heapsampling.go in isolation isn't sufficient. The perturbation caused by the tests running concurrently seems necessary.
I'm going to try adding some more debugging information to the failure and will run it again.

Note that, even on Linux, we get only 2 to 3 samples from main.alloc, but it seems like the intent is that we should be getting roughly ((1024+512+256) * 100000) / (512 * 1024) = 341.

Sorry, I was completely misreading my debug output. There are >300 samples from main.alloc on Linux.

Here's the contents of the memory profile and its symbolization for a failure. It's very interesting that we in fact have samples for the lines in main.alloc, but their byte and object counts are 0.
# go run run.go -- heapsampling.go
exit status 1
{0 0 0 0 [4199461 4198675 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.alloc:56 main.main:34 runtime.main:137 runtime.goexit:1809
{0 0 0 0 [4199498 4198675 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.alloc:57 main.main:34 runtime.main:137 runtime.goexit:1809
{0 0 0 0 [4199420 4198675 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.alloc:55 main.main:34 runtime.main:137 runtime.goexit:1809
{768 768 3 3 [4199141 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.allocInterleaved:47 main.main:30 runtime.main:137 runtime.goexit:1809
{2048 2048 4 4 [4199063 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.allocInterleaved:45 main.main:30 runtime.main:137 runtime.goexit:1809
{15360 15360 15 15 [4198981 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.allocInterleaved:43 main.main:30 runtime.main:137 runtime.goexit:1809
{64421888 64421888 983 983 [4198940 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.allocInterleaved:42 main.main:30 runtime.main:137 runtime.goexit:1809
{64421888 64421888 983 983 [4199104 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.allocInterleaved:46 main.main:30 runtime.main:137 runtime.goexit:1809
{62586880 62521344 955 954 [4199022 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]} main.allocInterleaved:44 main.main:30 runtime.main:137 runtime.goexit:1809
panic: main.alloc want total count > 0 && <= 307200000, got 0

goroutine 1 [running]:
main.checkAllocations(0xc822ca6000, 0x9, 0x3b, 0x50a800, 0xa, 0x186a0, 0xc822cbfec0, 0x3, 0x3)
        /tmp/workdir/go/test/heapsampling.go:98 +0x79f
main.main()
        /tmp/workdir/go/test/heapsampling.go:34 +0x1cc
exit status 2

FAIL    heapsampling.go 2.439s

Here's a second sample because I have it, but I don't think there's anything different about it:
# go run run.go -- heapsampling.go
exit status 1
{0 0 0 0 [4199498 4198675 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.alloc:57 main.main:34 runtime.main:137 runtime.goexit:1809
{0 0 0 0 [4199461 4198675 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.alloc:56 main.main:34 runtime.main:137 runtime.goexit:1809
{0 0 0 0 [4199420 4198675 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.alloc:55 main.main:34 runtime.main:137 runtime.goexit:1809
{256 256 1 1 [4199141 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.allocInterleaved:47 main.main:30 runtime.main:137 runtime.goexit:1809
{6144 6144 12 12 [4199063 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.allocInterleaved:45 main.main:30 runtime.main:137 runtime.goexit:1809
{19456 19456 19 19 [4198981 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.allocInterleaved:43 main.main:30 runtime.main:137 runtime.goexit:1809
{67960832 67960832 1037 1037 [4198940 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.allocInterleaved:42 main.main:30 runtime.main:137 runtime.goexit:1809
{67633152 67567616 1032 1031 [4199104 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.allocInterleaved:46 main.main:30 runtime.main:137 runtime.goexit:1809
{71761920 71761920 1095 1095 [4199022 4198444 4368464 4543105 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0]}
main.allocInterleaved:44 main.main:30 runtime.main:137 runtime.goexit:1809
panic: main.alloc want total count > 0 && <= 307200000, got 0

goroutine 1 [running]:
main.checkAllocations(0xc8376c6000, 0x9, 0x3b, 0x50a800, 0xa, 0x186a0, 0xc8376dfec0, 0x3, 0x3)
        /tmp/workdir/go/test/heapsampling.go:98 +0x79f
main.main()
        /tmp/workdir/go/test/heapsampling.go:34 +0x1cc
exit status 2

FAIL    heapsampling.go 7.956s

I've found the cause. The byte and object counts are only updated at a GC, though the buckets are created eagerly. Hence, if a GC happens part way through allocInterleaved, but then doesn't happen after we start calling main.alloc, we'll see the buckets but they won't contain any counts.
I can reliably reproduce the failure on Linux with GOGC=10000 go run heapsampling.go.
One possible solution is to call runtime.GC() at the top of the test's getMemProfileRecords. I've sent https://go-review.googlesource.com/16846 with this fix.


Do not allow update of the user's display name

https://github.com/dinsic-pim/riot-android/issues/134

For  displaynamePref used in refreshDisplay, it's already done.


Funky font ?

Your font has 3 lines with 0x00 is that why all chars look cropped on the top and bottom on a 128x32 OLED ?
Board : NodeMCu ttgo

For an OLED that's 128x32, in OLED.cpp change
    //sendcommand(0x12);           //COMSCANDEC     sendcommand(0x02);           //COMSCANDEC


Question, Next point along Edge

Given an EdgeId of a RouterPoint and the EdgeId of another RouterPoint, if they do not match I would like to take the first EdgeId from the first RouterPoint and determine the next point in the Db.Network along the same edge.
Looking through the code I didn't see an easy way to accomplish this, if this something which is not possible would it be difficult to add? I would be able to take a shot at adding if you could provide some direction.
Thank you

You mean the vertex of the edge?

This could help:
https://github.com/itinero/routing/blob/develop/src/Itinero/Data/Network/RoutingNetwork.cs#L226

Thanks for the quick response. I will take a look.
What I am trying to achieve is the ability to prevent side switching e.g. (N/S or E/W) tracks which run adjacent to each other, sometimes GPS resolves on the opposite side and we know based on the heading that it's on the adjacent track, rather than manipulate GPS I would like to find the next vertex which connects to the last known good point using something like GetNextLocation(edgeId) which would provide me the next location along the same edge of the first RouterPoint so I can use that instead of the point which was resolved on the adjacent side.
Thank you

I am going to give this a try, was wondering if this was the correct approach:
var edge = Router.Db.Network.GetEdge(lastPoint.EdgeId);

									uint oldEdge = resolved.Value.EdgeId;

									resolved = Router.TryResolve(profile, (float)ll.Latitude, (float)ll.Longitude, (r)=> r == edge, (float)50, new Itinero.Algorithms.Search.ResolveSettings() {  }, System.Threading.CancellationToken.None);

									if (resolved.IsError)
									{
										System.Console.WriteLine($"Discarding non matching edgeID from previous {lastPoint.EdgeId} to {resolved.Value.EdgeId}");
										continue;
									}

									System.Console.WriteLine($"Re-Routed non matching edgeID from previous {oldEdge} to {resolved.Value.EdgeId}");

It seems that this is mostly working, there are some instances where points are resolving on adjacent tracks but I think that has something to do with the PBF or how it's converted into a graph network e.g. the EdgeId is the same for both sets of tracks which are close together...
More succinctly, Is there a direct way to go from a RouterPoint to the next forward or backward RouterPoint along the same exact Edge? E.g. the next Vertex which would correspond to a RouterPoint I think...
Thank you for your time and assistance!

I think that I got the hang of GetVertex as it seems to take values in terms of EdgeId.
var edge = Router.Db.Network.GetEdge(lastPoint.EdgeId);

									var vertex = Router.Db.Network.GetVertex(edge.To);

									uint oldEdge = resolved.Value.EdgeId;

I would then call TryResolve using the lat and lng from the vertex.
I am going to also give this a try and analyze and let you know what I find.

@xivk , Is there an easy way one can get a RoutPoint after they have a PositionAfter/PostionNext from a Route? or must one manually resolve the point obtained from PostionAfter/PositionNext and if so why is that?

@xivk  still waiting for a quick way to get a RoutePosition or RouterPoint from PositionAfter etc.
Manually resolving seems unnecessary yet I don't see another obvious way besides manually building a Route with those manually built RoutePositions...


Performances of the translatable extension

The performances of the Translatable extension should be optimized when loading a collection.
Generating my page uses currently 24 requests and 20 of them are done by the extension to load the translations for the loaded collection.
Considered features:

translation collection persistence
overrided persister to transform find requests and collection loads into translated, without issuing additional query
build a query walker which could be attached to any ORM query and autojoin translations without issuing additional queries.

1, 3 will require personalized translation entity, with a composite constraint.

Hi there,
I just wanted to submit a major issue I have and cannot solve with this new Translatable feature talked about here, allowing us to get the translated attribute directly joined in the query, and hydrated objects. (HINT_CUSTOM_OUTPUT_WALKER, HINT_TRANSLATABLE_LOCALE..).
Using this, a same query sometimes returns me only one or two results instead of the full result set, when I'm not in the default locale (and so using this feature).
This only happens on the production server, running under Linux, and can't be reproduced in my local WAMP server environment, neither in dev or prod environment.
I work with SQL server, and this could be coming from doctrine SQL server pilots, which could handle queries differently on windows and on Linux..
I think the issue happens during Doctrine Objects hydration, as I get the correct full result set when using getArrayResult() function..
Here is my thread in stackoverflow about this: http://stackoverflow.com/q/33544302/2707018
I know this might not be the right place for me to ask, but I really don't see how to solve this.
Thank you for your help.
@l3pp4rd @stof

hi @Cedoriku this looks like a complicated issue. What may be different in production is query caching. And in doctrine query result cache keys are built based on query hints also. So if you have a global locale changing, you should make a hint of locale to query too. Also, if you have a fallback option changes, you should make that as a hint too.
I doubt that it has something to do with Windows or Linux environment differences, most probably it is a cache related issue. Try to disable query result caches and see whether you get the same problem in production.

@l3pp4rd  YOU ROCK! ! !
You definitely made my day!
This was effectively a query cache issue.
Setting the query cache to false solves it.
So the solution to my problem was:
$query->->useQueryCache(false);
However I do not know what I really do by doing this.
What do I loose by bypassing Doctrine Query cache?
Doesn't it affect the app's performance too much?
If you please I'm gonna answer my own question on the Stackoverflow thread to indicate the solution.
Maybe I could quote you if you please if I know your Stackoverflow pseudo?
Thank you very much.

Its http://stackoverflow.com/users/186355/gediminas. but you can just answer to yourself. disabling query cache is one side of the coin, another is why the query cache produced bad result. You should try to figure that out, since caching is useful and I would recommend to use it. So try to debug:

the query cache key for your query.
how does it change or not when your query state changes.

Because it is possible that you may experience the same issue again at another query.

Thank you for these advices. I will, but I am not so familiar with cache issues, and don't really know how to debug this, so if you have any advice on how to do it, I'd be glad.
how (where?) do I find the query cache keys?
I will try by myself meanwhile.
Thank you.


Unable to open IPC Camera video stream

Unable to open IPC Camera video stream.
In logs:
`Logger: homeassistant.components.stream.stream.camera.ipc_none
Source: components/stream/init.py:431
Integration: Stream (documentation, issues)
First occurred: 18:25:41 (29 occurrences)
Last logged: 19:31:33
Error from stream worker: Stream ended; no additional packets
Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsps://:@wework-5-eu.stream.iot-11.com:443/v1/bfb94622c3f2900ea0tloz/cl3r379int5m4f82pbm09ckDm4YKJq4X?signInfo=kLOCpE2BqAnrSyf0BvFsi0WVRhOhh2VJ-gJlhiHukB_XIMTos30M4ZlH4apat_B0ucTOUqvPt6Z7LtB38hLp718u_dPtp6eJMBHYEHxJWVafAiSy0rGtnpUMAdQYq5v4vc4fFUOTt5f98ZLAWqbA3gSiAPKqTtFoXzRTnHSP4hU`

the stream stops working after a few minutes. Reloading the plugin fixes the stream. Based on the logs I see, it looks to me that there is a parameter signInfo with some kind of a token that probably doesn't get refreshed? Might be a hint, might not. Hope for a fix

Can you provide the diagnostics file?

smartlife-59a14ad77c1bf4b2b765c0fe5f8c0ce8-Камера-6a0033e48abed8ebd9b0462f8a63db9c.json
Diagnostics file

Currently the way to obtain video stream through the URL provided by Cloud has a validity period of 30 seconds and the maximum streaming time is 10 minutes.

Will this be extended in the future?
With this given limitations the camera integration is not very useful…
Thanks in advance,
parkflyer

Sorry, there is currently no plan to support it.


Availability Test in Application Insights atuomatically disables

Hi All,
We have a very simple Application Insights Availability Test (That hits an HTTPS URL across 4 US regions) (basically it hits our App Service).
What we have observed it this Availability test automatically stops (not a fixed scheduled) but it abruptly stops and then what we have to do is go back to Availability test Edit the Test and Save it again so that it restarts.
This is really weird as we have checked the Activity log also and nothing is reported in it about someone stopping the Test, etc.
Any help on how this can be tackled? As abrupt stoppage of Availability Test (Tests getting grayed out) is really serious as we wont know if there is any outage untill someone reports back on the service.
Thank you,

AvailabilityTest is not a feature shipped from this repo. Please get support from Azure Support Center


[Packager] Cannot Redirect Dependency Like "xmlhttprequest": "./lib/xmlhttprequest-browser.js"

The packager cannot handle redirection from a dependent module to a local module, for example:
"browser": {
    ...
    "xmlhttprequest": "./lib/browserify-wrapper/xmlhttprequest-browser.js",
    "localStorage": "./lib/browserify-wrapper/localstorage-browser.js",
    ...
  },

When generating search path for the redirected module, it is expects that the module is in node_module directory which cannot work with redirection like: "xmlhttprequest": "./lib/xmlhttprequest-browser.js"

@brentvatne consolidate to https://github.com/facebook/react-native/pull/2499 ? Also with the packager splitting off not sure how we want to handle migrating packager issues.

Indeed, #2499 seems to cover this, thanks for the report @Hybrid-Force!


Rhmap 10243 apply default values

Motivation
When a new submission is created with a form, it should automatically apply the default values for the field.
This is to ensure that any default values that affect rules are applied before testing rule values.
Changes

Added a applyDefaultValues function to the submission model. This is called when a new submission is initialised with a form.
Added logic to the Field model to get default values from multi-choice and non-multichoice fields.

LGTM