text:
User Experience Feedback for the current state of Franklin.jl

I don't know where to place this, probably nowhere, but I hope it is still somehow valuable to know how painful it is to use Franklin.jl right now
unfortunately when I am working with Franklin, once a week, or more often, I am hitting some bug-like missing feature (something I expect just works) or a plain bug. Everytime something does not work, Franklin plainly crashes, which makes the process of working with Franklin quite difficult.
This state of franklin is quite unexpected given that so many users uses it and even juliacomputing uses Franklin.
I am sorry for these words of sorrow, but with every such issue I feel like I better had used something more mature than Franklin and am now developing Franklin instead of my webpage. However I wanted to make use of Julia in case I need it. Was a difficult decision and probably I already went to far and will stay with Franklin despite all these difficulties.
I would love seeing Franklin more userfriendly in this regard.
My excuses for the hard words, still they may give some valuable insights into the user perspective.

Hey Stephan, no problem, I know it's not always a smooth ride and thanks for giving it a fair shot already.
Some notes:

given the issues you opened here (thanks for those btw, it's always helpful), you're using a lot of 'advanced' features of Franklin; not that these shouldn't be used, but rather that the docs for those is less present and, as far as I could see, the issues you have are often about expecting X to work but in fact there's Y that could have been used instead.

For this, it's always the same; having patient users help me extend the docs is how things can become better.

with respect to other users, there's basically two groups of users: those who don't leverage a lot of the features like lx* or hfun*; for those "things generally work" and when it doesn't they shoot a message on Slack and it usually gets solved very quickly. This group includes the 'big' users you listed (Julia website, etc) and the second are people who do used the advanced features like you or the guy behind the Makie docs, and these people do run into issues because they use things that have been used less and are documented less. I typically try to help these people pretty actively and respond quickly (as I think you saw). The hope is that these people help me by trying stuff out and making suggestions for better docs or for better code.

A final note is that I'm working on a very big refactoring as I think I've mentioned in another issue; this also means that I'm not actively working on the current version (apart from fixes) because I'd like things to "keep working" for people who use Franklin now and have something they're happy with.
The next version will certainly not be perfect but will address a bunch of the issues you've opened recently. One thing to understand is that the initial design of Franklin had a simpler use case in mind but slowly people started using some more advanced stuff to a point which now suggests some core re-design for improved use.
This is a lot of work, and while the main building blocks are in place, there's still a lot of details to finalise before I can offer this for people to beta-test.
Anyway, I understand that things can be frustrating and I apologise; if you want to help me out with adding comments in the docs, this will be much appreciated. I'd also suggest you join the slack #Franklin channel to get help quicker than here (even though in some cases your issues are good reminders that I have to improve the docs on XYZ).

authors: schlichtanders tlienart


text:
prepath not applied on plotly json when publishing

Problem:
We followed this guide: https://franklinjl.org/extras/plotly/index.html
Our site is published on github.io, thus we have prepath set.
We include the plotly json like this:
\figalt{Barplot showing participants per country}{/assets/pages/datascience/plot_explorative_da_country.json}
After publishing, the json can not be found since prepath is not prepended.
Suspicion
\figalt and \fig both call html_plotly. This function produces the following output:

$src basically being the second argument of \figalt (/assets/pages/datascience/plot_explorative_da_country.json)
Publishing (and optimizing) calls fix_links which adds the prepath depending on this pattern:
const PREPATH_FIX_PAT = r"(src|href|formaction|action|url)\s*?=\s*?([\"\']?)\/"

But unfortunately this pattern does not apply for the previously generated code part:
plotlyPromise = PlotlyJS_json(graphDiv, '/assets/pages/datascience/plot_explorative_da_country.json');

Thanks for the report and going the extra mile to correctly diagnose the problem.
I think this can be fixed by adding a globvar("prepath") in the plotly logic but I need to play with it a bit to check.
Will try to fix this by eow.

Just released a patch with this, demo: https://tlienart.github.io/test-plotly/ , demo repo: https://github.com/tlienart/test-plotly

Thanks a bunch. We will apply this patch soon.
I would have loved to create a pull request but was unsure where to fix it without breaking the architecture.

Works like a charm. Thanks for the fast fix. :)

Great!

source: gharchive/issue

authors: noxthot tlienart

license: MIT

license_type: permissive

license_source: github-api


text:
Reduce argument allocations for checkArgument to reduce gc pressure.

PR description
The checkArgument( boolean, String, ... ) causes a large number of Integer and int[] to be created temporarily on the heap which causes gc pressure. This PR adds overloads which reduces object allocations to 0 for these method calls.
Fixed Issue(s)

You will need to run spotless.

@atoulme improvement for memory allocation - are you accepting PRs into this project?

looks like the GPG signing key has expired @atoulme

I'll take a look.

@atoulme would it be possible to get write access for me and a few others on this repo? Would like to get this change merged and be able to do releases when required.

@atoulme this PR includes groupid change in build.gradle which is going to cause issues when publishing

source: gharchive/pull-request

authors: ahamlat atoulme david-ry4n macfarla

repo: tmio/tuweni


text:
Setting env configuration with raw cookie value via attribute "cookie" appears to be deprecated.

Tried creating env with a custom configuration, like such, but the cookie header is absent from the resulting http request.
jsdom.env({
    url: 'http://localhost',
    cookie: 'key=value; expires=Wed, Sep 21 2011 12:00:00 GMT; path=/',
    done: function (err1, window1) {
        //...
    }
});

Confirmed. This is actually unfortunately hard to fix as all our cookie-related logic is confusingly wedged in after the initial request. I can continue giving it a try...

looks like the way to go is through headers:
jsdom.env({
    url: 'http://localhost',
    headers: {
      cookie: 'key=value; expires=Wed, Sep 21 2011 12:00:00 GMT; path=/',
    }
    done: function (err1, window1) {
        //...
    }
});

Going to close this as the new API provides a much better mechanism for adding cookies, and the old API has a workaround as documented above.

authors: danetb domenic kedadi

repo: tmpvar/jsdom

license: mit

license_source: bigquery


text:
Canvas element fails "instanceof HTMLElement"

At least the canvas element (I have not tested other) returns false on "element instanceof HTMLElement". It should return true.

Is there a way to get access to the HTMLElement class directly from jsdom, to be extended in es6 contexts?

window.HTMLElement works. Not sure what that has to do with this issue though.

Confirmed this is still broken as of 6.1.0.

authors: domenic mitar rgbkrk


text:
Add click activation behaviors for input elements

This PR fixes the issue reported in #1079 where change and input events were not being fired for inputs. It replaces this._eventDefaults with more granular actions to meet the requirements of the spec: _preClickActivationSteps, _activationBehavior, and _canceledActivationSteps.
It also partially fixes input.disabled behavior for inputs.
Relevant part of the spec (for input[type=checkbox]) behavior: https://html.spec.whatwg.org/#checkbox-state-(type=checkbox)
Todo:

[x] Do we need to implement "click in progress" flag handling? (it was mentioned in the spec)

[x] Yes
[x] Turn this._clickInProgress into a local variable

[x] Question mark?
Never mind don't do it

[x] Is the addition of HTMLInputElement._preCancelState reasonable? (in code)

[x] Yes, leave a comment

[x] What is the difference between outcome vs. event.defaultPrevented? (in code)

They're opposites
[x] Remove TODO comment

[x] Is replacing this.disabled with idlUtils.wrapperForImpl(this).disabled okay? (in code)

[x] Use this.hasAttribute("disabled")

[x] "add comments linking to the HTML bugs I mentioned in IRC"

[x] Is this right?
[x] Add second link

Move from nodeunit tests to to-upstream web-platform-tests

[x] Figure out what directory to put them in... https://github.com/w3c/web-platform-tests is big...
[x] Transfer the rest of the tests to to-upstream
[x] Update spec links in to-upstream tests

[x] Read the spec again to see if there's anything I missed
[ ] Rebase (last thing)

Is replacing this.disabled with idlUtils.wrapperForImpl(this).disabled okay?

Yeah, this is how the interaction with reflected attributes works for now.

Awesome stuff!! Will try to review in more detail later, but to answer some of your questions quickly:

Do we need to implement "click in progress" flag handling? (it was mentioned in the spec)

It seems like a reasonable thing to implement; not much work and will definitely cause different behavior. I'd go for it, personally, but a TODO is also OK.

Is the addition of HTMLInputElement._preCancelState reasonable?

It seems reasonable; I'd maybe add a comment above it to explain what it's used for (to implement the spec's "The canceled activation steps consist of setting the checkedness and the element's indeterminate IDL attribute back to the values they had before the pre-click activation steps were run.")

What is the difference between outcome vs. event.defaultPrevented? (in code)

Fascinating. Per https://dom.spec.whatwg.org/#concept-event-dispatch (which I assume we follow), they're simply opposites of each other.
What's interesting here is the overriding of dispatchEvent on HTMLElement-impl.js. I guess it doesn't cause web-observable changes, due to the (awesome!) wrapper-delegates-to-impl setup. But I wonder if it might be clearer to move all of the overrides into EventTarget. I'm OK either way.
We should add comments linking to the HTML bugs I mentioned in IRC, though.

Is replacing this.disabled with idlUtils.wrapperForImpl(this).disabled okay? (in code)

Hmm, I'd prefer using this.hasAttribute("disabled") personally, which keeps things inside the impl. @Sebmaster what do you think?

Hmm, I'd prefer using this.hasAttribute("disabled") personally, which keeps things inside the impl.

I'm not sure - idl2js does the actual logic here so I'd like to keep it DRY, but meh.

I guess what makes me slightly sad is that if someone defines a getter for disabled on the wrapper the implToWrapper(...).disabled code will trigger it, which is one of the things we try to avoid these days now that we have a nicely stratified setup.

Ohhh, right, true. Let's not do that then and keep it in impl.

Just added "click in progress" support.

add comments linking to the HTML bugs I mentioned in IRC

I could only find one HTML bug you linked to. This was part of the original PR, is it enough?
https://github.com/tmpvar/jsdom/pull/1412/files#diff-a25a2d736e80c21d50966e0dbc0681f5R70
Also thank you @Sebmaster for your IDL/refactoring work!! It's a delight to work with.

This is looking pretty solid; I'm really excited! If you wouldn't mind moving to to-upstream web-platform-tests instead of nodeunit tests, that'd be really nice?

Hokay, all tests have been moved to to-upstream. This PR should be ready for more review.

This looks great! Minor nits, which either you can fix or I can fix while merging. <3 Will merge by this weekend at the latest.
This is a big improvement for jsdom!!

Merged as 35a89db8611d1bf2d7ad50e3fa6c9176a50150df, with a new release going out today. Thanks so much!!

Yay!! :tada: Thank you for all the help! I always learn a ton from each PR.

authors: Sebmaster domenic jeffcarp


text:
Undefined name: from functools import partial

flake8 testing of https://github.com/toandaominh1997/EfficientDet.Pytorch on Python 3.8.0
$ flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
./eval.py:81:32: F821 undefined name 'device'
            images = images.to(device)
                               ^
./eval.py:82:42: F821 undefined name 'device'
            annotations = annotations.to(device)
                                         ^
./utils/vis_bbox.py:107:26: F821 undefined name 'label_names'
            label_names= label_names
                         ^
./models/bifpn.py:91:17: F821 undefined name 'xavier_init'
                xavier_init(m, distribution='uniform')
                ^
./models/bifpn.py:167:17: F821 undefined name 'xavier_init'
                xavier_init(m, distribution='uniform')
                ^
./models/retinahead.py:8:13: F821 undefined name 'partial'
    pfunc = partial(func, **kwargs) if kwargs else func
            ^
6     F821 undefined name 'device'
6

https://flake8.pycqa.org/en/latest/user/error-codes.html
On the flake8 test selection, this PR does not focus on "style violations" (the majority of flake8 error codes that psf/black can autocorrect).  Instead these tests are focus on runtime safety and correctness:

E9 tests are about Python syntax errors usually raised because flake8 can not build an Abstract Syntax Tree (AST).  Often these issues are a sign of unused code or code that has not been ported to Python 3.  These would be compile-time errors in a compiled language but in a dynamic language like Python they result in the script halting/crashing on the user.
F63 tests are usually about the confusion between identity and equality in Python.  Use ==/!= to compare str, bytes, and int literals is the classic case.  These are areas where a == b is True but a is b is False (or vice versa).  Python >= 3.8 will raise SyntaxWarnings on these instances.
F7 tests logic errors and syntax errors in type hints
F82 tests are almost always undefined names which are usually a sign of a typo, missing imports, or code that has not been ported to Python 3.  These also would be compile-time errors in a compiled language but in Python a NameError is raised which will halt/crash the script on the user.

One issue remains: https://app.circleci.com/jobs/github/toandaominh1997/EfficientDet.Pytorch/58


text:
loops need its own variables

Feature-request
Description
Loops should have its own variables. Beside this, the for-loops should be marked as parent too. This is necessary for parallel for-loops, which need to store temporary results. So the new variable-fields must be thread-save.
Kitsunemimi-Repos, which have to be updated

libKitsunemimiSakuraParser

was fixed with the last rework #80

repo: tobiasanker/SakuraTree


text:
e131 mode switching bug

When i switch mode to e131 using the webinterface and the button, it works without a problem
but using the http get with http://hostname/e131, the LEDs stay in the previous selected mode, like for example static.
As soon as an e131 signal is sent with a software like jinx, it starts to switch constantly between the e131 signal and the selected mode through the webinterface before.

Thanks for reporting this, it is indeed a bug.
You can add
if(strip->isRunning()) strip->stop();

before this line to fix this https://github.com/toblum/McLighting/blob/0fee256c3abd5b7e6c40cccf05f35025a7124555/Arduino/McLighting/McLighting.ino#L1063

Thanks for the fast fix! Really appreciate your work!

authors: colarocker debsahu

repo: toblum/McLighting


text:
feat: 🔥 Better header and changed search bar location on mobile

2 commit so fire siuuuu

hmm ok i approve ur commit

repo: tobycm/emochoice


text:
Parent process not being killed when executing through a init script?

Overview
We discovered an issue with running env-cmd through a init script, the parent is not being killed when we use CTRL+C to terminate the node express process from the terminal.
Error message:
Unable to terminate parent process successfully

Background
We basically have a crontab job that starts our node server on boot with a tmux session, this way we can easily restart it or view the console and this approach is just a proof of concept, we'll be using a process manager such as PM2 down the road for production.
Setup
crontab -e (this spawns a init session, there's no user and it's the system running this):
@reboot tmux new -d -s node && tmux send-keys -t node.0 "yarn --cwd /home/node start:staging" ENTER

package.json (scripts section):
"start:staging": "env-cmd -e staging --use-shell 'wait-on tcp:27017 && node server.js --dev'"

Dependencies:
Distro: Ubuntu 18.04.3 LTS
Node: v8.10.0
Express: v4.17.1
env-cmd: v10.0.1

The above approach does not generate a stacktrace, we played around with the env-cmd command and we managed to generate one this way:
root@ip-172-31-40-55:/home/node# yarn env-cmd -e staging 'node server.js --dev'
yarn run v1.19.1
$ /home/node/node_modules/.bin/env-cmd -e staging 'node server.js --dev'
spawn node server.js --dev ENOENT
internal/process.js:178
        throw new Error(`Unknown signal: ${sig}`);
        ^

Error: Unknown signal: 1
    at process.kill (internal/process.js:178:15)
    at TermSignals._terminateProcess (/home/node/node_modules/env-cmd/dist/signal-termination.js:47:28)
    at process.terminateSpawnedProcessFuncHandlers.(anonymous function) (/home/node/node_modules/env-cmd/dist/signal-termination.js:20:30)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at process.emit (events.js:211:7)
    at process.exit (internal/process.js:157:15)
    at TermSignals._uncaughtExceptionHandler (/home/node/node_modules/env-cmd/dist/signal-termination.js:68:17)
    at process.on (/home/node/node_modules/env-cmd/dist/signal-termination.js:40:53)
    at emitOne (events.js:116:13)
error Command failed with exit code 7.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Let us know if you need more information, thanks!

Yeah, this is very helpful. It looks like sig is coming in as a number rather than a signal string. I can add a safety check if sig is a non-zero number then act appropriately.

This should now be resolved by commit: https://github.com/toddbluhm/env-cmd/commit/f92f8b51ff642448b4cd6d855ad88e4e28058216
Feel free to let me know if it is working or close the ticket if it is not needed anymore. I will update this thread once the release is out.

I have released 10.1.0 with the fix for this issue.

authors: toddbluhm xRiot

repo: toddbluhm/env-cmd


text:
Win app acting slow despite clearing cache

windows_native_app/7.4.73

Toggl has become very slow and laggy. I have cleared the cache but it doesn't make much difference. Is it a known issue? Do I need to archive some old entries/projects?

Logs: #587741

Same. It's starting to feel almost as bad as using it from my browser. Changing time entries, editing entry names, or starting and stopping tasks takes half a second. Often going from editing one entry to another results in the wrong entry being edited because my inputs are too fast.

closed together with #2042 Will be released to beta next week

authors: IndrekV kadrihvl mavericknm

repo: toggl/toggldesktop


text:
Make the find command case insensitive

@tshradheya

@tshradheya Okay! Thank you! Toh Yunqi Cheryl is my full name! May I know if I have to make any other changes to the code e.g. refactoring and following of style guide (based on the LOs for Week 3)? And will there be a need to commit those changes and push them on to github?


text:
[モニタリング指標：残作業] 補助線の実装

モニタリング指標関連のグラフのうち３つのグラフに補助線を引きたいです。
参考イメージ（オレンジの線が補助線）

モニタリング指標(1)新規陽性者数
補助線２本を実装

ラベル：緩和の目安
位置：Y軸 20（人）
線の種類：破線
線の色： #1B4D30
ラベル：再要請の目安
位置：Y軸 50（人）
線の種類：直線
線の色： #1B4D30

モニタリング指標(2)新規陽性者における接触歴等不明率
補助線１本を実装

ラベル：緩和・再要請の目安
位置：Y軸 50（%）
線の種類：破線
線の色： #1B4D30

モニタリング指標(3)週単位の陽性者増加比
補助線２本を実装

ラベル：緩和の目安
位置：Y軸 1の目盛り
線の種類：破線
線の色： #CC7004
ラベル：再要請の目安
位置：Y軸 2の目盛り
線の種類：直線
線の色： #CC7004

※補助線の太さは2pxでお願いします。

やります

authors: kaizumaki y-chan


text:
Resizing window: 'unexpected error: DeviceLost'

I am trying to implement window resizing by following the sample code at https://docs.rs/vulkano/0.3.1/vulkano/swapchain/index.html#recreating-a-swapchain, unsuccessfully.
Here is a simple modification to the triangle example I tried: commit.
I run on Arch Linux with Nvidia driver v375.26.  On resize, I see the process hogging 100% CPU for ~15 seconds, FPS printouts stop, then it crashes.  Any ideas what I am doing wrong?
$ cargo build && RUST_BACKTRACE=1 ../target/debug/triangle
warning: cpp_set_stdlib is specified, but the Gnu compiler does not support this option, ignored
   Compiling examples v0.1.0 (file:///home/skirmis/Temp/vulkano/examples)
    Finished debug [unoptimized + debuginfo] target(s) in 5.26 secs
Using device: GTX 750 Ti (type: DiscreteGpu)
----- Event Resized(796, 1196)
FPS: 2011.6
FPS: 2100.7
FPS: 2115.7
FPS: 2113.4
FPS: 2000.1
FPS: 2022.4
----- Event Resized(796, 1179)
>>>>> Recreate swapchain with dimensions (796, 1179)
<<<<< Recreate swapchain with dimensions (796, 1179)
----- Event Resized(796, 1196)
FPS: 61.2
>>>>> Recreate swapchain with dimensions (796, 1196)
<<<<< Recreate swapchain with dimensions (796, 1196)
FPS: 59.1
thread 'main' panicked at 'unexpected error: DeviceLost', /home/skirmis/Temp/vulkano/vulkano/src/lib.rs:151
stack backtrace:
   1:     0x5598268eea3c - std::sys::imp::backtrace::tracing::imp::write::h2a972e172776bc73
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:42
   2:     0x5598268f0fde - std::panicking::default_hook::{{closure}}::h3350be9abe4c8496
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:351
   3:     0x5598268f0be4 - std::panicking::default_hook::h255964940ef72e84
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:367
   4:     0x5598268f1487 - std::panicking::rust_panic_with_hook::ha02a85ff57cdb669
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:555
   5:     0x5598268f12c4 - std::panicking::begin_panic::h3472a76248a19370
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:517
   6:     0x5598268f1239 - std::panicking::begin_panic_fmt::h353221386e3766a5
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:501
   7:     0x55982672f27b - <vulkano::OomError as core::convert::From<vulkano::Error>>::from::hdafa6a42b8d0928d
                        at /home/skirmis/Temp/vulkano/examples/<panic macros>:8
   8:     0x5598266b3aea - <vulkano::sync::fence::Fence<D>>::ready::ha74003902015a3d8
                        at /home/skirmis/Temp/vulkano/examples/<try macros>:6
   9:     0x559826734739 - vulkano::command_buffer::inner::Submission::finished::h90661d9d840bb060
                        at /home/skirmis/Temp/vulkano/vulkano/src/command_buffer/inner.rs:2095
  10:     0x55982673464c - vulkano::command_buffer::inner::Submission::destroying_would_block::h40b8771bd3ea06ff
                        at /home/skirmis/Temp/vulkano/vulkano/src/command_buffer/inner.rs:2089
  11:     0x55982676033d - triangle::main::{{closure}}::h28239630505198cb
                        at /home/skirmis/Temp/vulkano/examples/src/bin/triangle.rs:406
  12:     0x5598266a235b - <collections::vec::Vec<T>>::retain::h4e9a7cd363228a59
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libcollections/vec.rs:802
  13:     0x55982675ecd4 - triangle::main::h845c4b617f32f93f
                        at /home/skirmis/Temp/vulkano/examples/src/bin/triangle.rs:406
  14:     0x5598268f7f0a - __rust_maybe_catch_panic
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libpanic_unwind/lib.rs:98
  15:     0x5598268f1986 - std::rt::lang_start::h836f853bc2506201
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:436
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panic.rs:361
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/rt.rs:57
  16:     0x559826765272 - main
  17:     0x7fbd13713290 - __libc_start_main
  18:     0x559826668529 - _start
  19:                0x0 - <unknown>

The "crash" is caused by a device lost, which means that the GPU likely took too much time or had a problem while processing a command buffer.
If I had to guess, it's maybe vulkano's internals that ask to wait on a semaphore that is never signalled.
I'm not going to deep down into this, as this part of the code is being totally reworked in the incoming branch.

Pierre,
Thanks for taking a look.  I tried the same approach on top of incoming branch, and it works just fine there.
I will just use the incoming branch then.  This is a personal project to learn Vulkan, so unstable base is fine as long as I can find some commit that works for my simple needs.
Do you plan to merge incoming into master any time soon?

Do you plan to merge incoming into master any time soon?

Soon, no. There's still an aspect whose design is blurry.

authors: skligys tomaka

repo: tomaka/vulkano


text:
JsonException when a field contains a ']'

I have a string in a record containing a bracket which throws an exception on push query. It jumps to the OnError method and the query stops. Is there any solution to isolate the exception within line processing (skip the malformed line) and keep the query running?
Only proper solution I see... is to escape all strings before sending them to Kafka. Is there any other?
System.Text.Json.JsonException: ':' is invalid after a value. Expected either ',', '}', or ']'. Path: $.after | LineNumber: 4 | BytePositionInLine: 20.
 ---> System.Text.Json.JsonReaderException: ':' is invalid after a value. Expected either ',', '}', or ']'. LineNumber: 4 | BytePositionInLine: 20.
   at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
   at System.Text.Json.Utf8JsonReader.ConsumeNextToken(Byte marker)
   at System.Text.Json.Utf8JsonReader.ConsumeNextTokenOrRollback(Byte marker)
   at System.Text.Json.Utf8JsonReader.ReadSingleSegment()
   at System.Text.Json.Utf8JsonReader.Read()
   at System.Text.Json.Serialization.Converters.ObjectDefaultConverter`1.OnTryRead(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options, ReadStack& state, T& value)
   at System.Text.Json.Serialization.JsonConverter`1.TryRead(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options, ReadStack& state, T& value)
   at System.Text.Json.Serialization.Metadata.JsonPropertyInfo`1.ReadJsonAndSetMember(Object obj, ReadStack& state, Utf8JsonReader& reader)
   at System.Text.Json.Serialization.Converters.ObjectDefaultConverter`1.OnTryRead(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options, ReadStack& state, T& value)
   at System.Text.Json.Serialization.JsonConverter`1.TryRead(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options, ReadStack& state, T& value)
   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state)
   --- End of inner exception stack trace ---
   at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& state, JsonReaderException ex)
   at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state)
   at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 utf8Json, JsonTypeInfo jsonTypeInfo, Nullable`1 actualByteCount)
   at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 json, JsonTypeInfo jsonTypeInfo)
   at System.Text.Json.JsonSerializer.Deserialize[TValue](String json, JsonSerializerOptions options)
   at ksqlDB.RestApi.Client.KSql.RestApi.Query.KSqlDbQueryProvider.CreateRowValue[T](String rawJson)
   at ksqlDB.RestApi.Client.KSql.RestApi.Query.KSqlDbQueryProvider.OnLineRead[T](String rawJson)
   at ksqlDB.RestApi.Client.KSql.RestApi.KSqlDbProvider.ConsumeAsync[T](StreamReader streamReader, SemaphoreSlim semaphoreSlim, CancellationToken cancellationToken)+MoveNext()
   at ksqlDB.RestApi.Client.KSql.RestApi.KSqlDbProvider.ConsumeAsync[T](StreamReader streamReader, SemaphoreSlim semaphoreSlim, CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
   at ksqlDB.RestApi.Client.KSql.RestApi.KSqlDbProvider.Run[T](Object parameters, CancellationToken cancellationToken)+MoveNext()
   at ksqlDB.RestApi.Client.KSql.RestApi.KSqlDbProvider.Run[T](Object parameters, CancellationToken cancellationToken)+MoveNext()
   at ksqlDB.RestApi.Client.KSql.RestApi.KSqlDbProvider.Run[T](Object parameters, CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
   at System.Linq.AsyncEnumerable.ToObservableObservable`1.<>c__DisplayClass2_0.<<Subscribe>g__Core|0>d.MoveNext() in /_/Ix.NET/Source/System.Linq.Async/System/Linq/Operators/ToObservable.cs:line 50

Hi @blatda,
could you please provide an example record which causes you the above mentioned error, please?
Short code snippet of your model and query etc. would be also helpful in order to reproduce your issue.
Thank you in advance

Thanks for the quick reaction!
I couldn't get exactly the same error. It depends on the exact position of the ']' obviously. But throws very similar one:
// Topic: 'clients' contains Key: {"Id": 1}, Value: {"Before": {"Id":1, "Name": "John]"}, "After": {"Id":1, "Name": "John"}} // Stream: CREATE STREAM CLIENTS (keystruct STRUCT<IdINT> KEY,IdINT,Name` STRING) WITH (KAFKA_TOPIC='clients', KEY_FORMAT='JSON', VALUE_FORMAT='JSON');
using ksqlDB.RestApi.Client.KSql.Linq;
using ksqlDB.RestApi.Client.KSql.Query.Context;
using ksqlDB.RestApi.Client.KSql.Query.Options;
const string kSqlDbUrl = "http://dev-oms-lnx.prague.wood.cz:8088";
const string kStreamName = "CLIENTS";
IDisposable subscription = RunQuery();
Console.WriteLine("Waiting for query results... press key to exit.");
Console.ReadKey();
subscription.Dispose();
IDisposable RunQuery()
{
KSqlDBContext kContext = new KSqlDBContext(kSqlDbUrl);
return kContext.CreateQuery<CdcObject>(kStreamName)
    .WithOffsetResetPolicy(AutoOffsetReset.Earliest)
    .ToObservable()
    .Subscribe(client =>
    {
        Console.WriteLine($"Next: '{client}'");
    }, e =>
    {
        Console.WriteLine($"Error: '{e}'.");
    }, () =>
    {
        Console.WriteLine("Completed.");
    });

}
record CdcObject
{
public Client? Before { get; set; }
public Client? After { get; set; }
}
record Client
{
public long Id { get; set; }
public string Name { get; set; }
}`

Thank you for the details @blatda! I hopefully found a solution for your issue.
Could you please try out the RC I've just published?
dotnet add package ksqlDb.RestApi.Client --version 2.7.0-rc.2

Let me know if you will find any issue or have suggestions for improvements.
Thank you again!

Yes, it works! Thank you for such a quick fix.

authors: blatda tomasfabian


text:
OverviewMap

The OverviewMap control can be added:
extend angular-openlayers-directive.js:
line 840: add               overviewmap: ol.control.OverviewMap, then
line 1509: add                overviewmap : false
extend 100-controls-example.html
line  32: add               { name: 'overviewmap', active: true }

Sorry, I did not notice: the overview map exhibits the sector but there is no underlying map. Have to investigate
.

Closing this.

authors: apoigne tombatossals

repo: tombatossals/angular-leaflet-directive


text:
New Component Type: Embedded Video

Ability to add an Embedded Video from typical providers onto a section within the Page Builder.

This has been implemented and released

repo: tommcclean/PortalCMS


text:
Is Possible to Support Snapshot

Is possible to support Snapshot? I see the V8 support snapshot for common script that used often

Yes, I don't see any reason it shouldn't be.
Isolate creation would have to take a snapshot blob: https://v8.github.io/api/head/classv8_1_1Isolate.html#a508901d16ef77659eb9e2b3dd476db07
Context creation would need to take a snapshot index: https://v8.github.io/api/head/classv8_1_1Context.html#ad4da29f2cbb305504d24e88700af5443
And I think SnapshotCreator is used to create the data: https://v8.github.io/api/head/classv8_1_1SnapshotCreator.html


text:
Minify Razor @helper functions by implementing a build provider, resolves #5

See #5.
Because ASP.NET will not use the configured Razor host factory for App_Code files, a minifying build provider has been implemented. For App_Code files, ASP.NET uses WebCodeRazorHost instead of MvcWebPageRazorHost, so I have also implemented a MinifyingWebCodeRazorHost similar to the existing MinifyingMvcWebPageRazorHost.
I updated the sample and documentation. Additional configuration is required to make minification of Razor @helper functions work:
<compilation debug="true" targetFramework="4.7.2">
    <buildProviders>
        <add extension=".cshtml" type="RazorHtmlMinifier.Mvc5.MinifyingRazorBuildProvider, RazorHtmlMinifier.Mvc5" />
    </buildProviders>
</compilation>

I tested a new build of RazorHtmlMinifier.Mvc5 in my own codebase to verify all minification works as expected.

Thanks for contributing, I had a brief look and it looks great!
I'll look at this closer soon and try to merge it and release it.

authors: RudeySH tompazourek


text:
Fix for #114

This fix introduces a validation of the cursor at the DatabaseWrapper to make sure the search_paths are always applied even if we get a different cursor pointer

@perrohunter Thanks

authors: perrohunter tomturner

repo: tomturner/django-tenants


text:
Log probe

Not very clean, but works as a proof of concept :).
Here's a sample program that I used to test it:
use std::time::Duration;

use log::{error, warn};

fn main() {
    log::set_boxed_logger(Box::new(
        log_probe::LogProbe::new(None, Duration::from_millis(500)).unwrap(),
    ))
    .unwrap();
    log::set_max_level(log::LevelFilter::Trace);

    loop {
        std::thread::sleep(Duration::from_millis(100));
        error!("Oops, something bad happened");
        warn!("Oops, something not so bad happened");
        std::thread::sleep(Duration::from_millis(100));
        warn!("Oops, something not so bad happened");
    }
}

and here's the output on the server side:
Received an event (36 bytes): LogStats(LogStats { span: 500.089013ms, error_records: 2, warn_records: 5, info_records: 0, debug_records: 0, trace_records: 0 })
Received an event (36 bytes): LogStats(LogStats { span: 499.889905ms, error_records: 3, warn_records: 5, info_records: 0, debug_records: 0, trace_records: 0 })
Received an event (36 bytes): LogStats(LogStats { span: 500.194193ms, error_records: 2, warn_records: 5, info_records: 0, debug_records: 0, trace_records: 0 })
Received an event (36 bytes): LogStats(LogStats { span: 499.49606ms, error_records: 3, warn_records: 5, info_records: 0, debug_records: 0, trace_records: 0 })
// ...

It would be very nice to put your sample program in crates/log_probe/examples.

Good idea, done!


text:
openwrt package

I wonder what different openwrt archs would make sense to support. I guess armv7l would be quite common

https://github.com/toltec-dev/toltec/pull/350
Not openwrt, but it does produce a ipk package for opkg/entware.

As far as I'm aware, most ARM variants should be supported and if they're not I'm happy to make changes to add support!

@mcginty Is there any update on this request? Can this be run on openwrt?

authors: Eeems NikhilMJain mcginty ptman

repo: tonarino/innernet


text:
Exception in shim delegate doesn't respect try/catch in isolated method

Here is some code where MethodA calls MethodB - if there is no exception, MethodA returns "0" otherwise it returns "1".  However, if I make a shim for MethodB that calls an exception, Pose execution stops and the exception isn't caught in MethodA.
Is there a way to throw exceptions in shims that are caught in the isolated method?
        [Fact]
        public void Test()
        {
            int i = MethodA();
            Assert.Equal(0, i);

            PoseContext.Isolate(() =>
            {
                i = MethodA();
            }, Shim.Replace(() => MethodB()).With(() => { throw new Exception("test"); }));
            Assert.Equal(1, i);
        }

        public static int MethodA()
        {
            try
            {
                MethodB();
            }
            catch
            {
                return 1;
            }
            return 0;
        }

        public static void MethodB()
        {
        }

Hi @dtkujawski, Pose currently doesn't seem to handle try...catch blocks quite well. Will look into it

Hi @dtkujawski #31 currently respects exception handling in methods. Will push out a new release tomorrow

Thank you for the fix!  This works great.

authors: dtkujawski tonerdo

repo: tonerdo/pose


text:
Add frozen string literal to all files

[x] I've added tests (if it's a bug, feature or enhancement)
[x] I've adjusted the documentation (if it's a feature or enhancement)
[x] The test suite passes (run bundle exec rspec to verify this)

Summary
Freeze all of the strings!!
Currently working through a couple of spec fixes on this one. Should improve performance, but will certainly need some QA.

Context
N/A

Version Changes
Patch, but might become a minor

This is passing tests, but I would appreciate some QA on this one. 🤠

Think will wait until ruby 3.0 to deal with this. Know that lots of places will need to be updated since did a bunch of gsub! and other mutable string operations throughout Jets. So it'll be a decent amount of work. FWIW, with the Lambda Runtime, functions get recycled after a few hours so memory usage is mitigated with the way Lambda works.

authors: jacobherrington tongueroo

repo: tongueroo/jets


text:
Deprecated selector in slack-ui/index.less

In slack-ui/index.less:
Starting from Atom v1.13.0, the contents of atom-text-editor elements are no longer encapsulated within a shadow DOM boundary. This means you should stop using :host and ::shadow pseudo-selectors, and prepend all your syntax selectors with syntax--. To prevent breakage with existing style sheets, Atom will automatically upgrade the following selectors:

atom-text-editor[mini], atom-text-editor[mini]::shadow => atom-text-editor[mini], atom-text-editor[mini].editor

atom-text-editor[mini] .cursor, atom-text-editor[mini]::shadow .cursor => atom-text-editor[mini] .cursor, atom-text-editor[mini].editor .cursor

atom-text-editor[mini] .selection .region, atom-text-editor[mini]::shadow .selection .region => atom-text-editor[mini] .selection .region, atom-text-editor[mini].editor .selection .region

atom-text-editor[mini] .placeholder-text, atom-text-editor[mini]::shadow .placeholder-text => atom-text-editor[mini] .placeholder-text, atom-text-editor[mini].editor .placeholder-text

atom-text-editor[mini].is-focused, atom-text-editor[mini].is-focused::shadow => atom-text-editor[mini].is-focused, atom-text-editor[mini].is-focused.editor

atom-text-editor[mini].is-focused .placeholder-text, atom-text-editor[mini].is-focused::shadow .placeholder-text => atom-text-editor[mini].is-focused .placeholder-text, atom-text-editor[mini].is-focused.editor .placeholder-text

atom-text-editor[mini].is-focused .selection .region, atom-text-editor[mini].is-focused::shadow .selection .region => atom-text-editor[mini].is-focused .selection .region, atom-text-editor[mini].is-focused.editor .selection .region

atom-text-editor .gutter.drop-shadow, atom-text-editor::shadow .gutter.drop-shadow => atom-text-editor .gutter.drop-shadow, atom-text-editor.editor .gutter.syntax--drop-shadow

Automatic translation of selectors will be removed in a few release cycles to minimize startup time. Please, make sure to upgrade the above selectors as soon as possible.

Thanks @steveoh ! I'm going to get that changed out this today or tomorrow.

Any luck moving forward with this?

Closed this in https://github.com/tony-jones/slack-ui/commit/f44e9c861fdbb56c1742b72e73c7e0dc37f5704c
Release just published to Atom @steveoh @gut4

authors: steveoh tony-jones

repo: tony-jones/slack-ui


text:
Use pyperformance to test the performance of pyjion，SURPRISE!!!

i install pyjion, and use pyperformance to test
pyperformance run -p=/usr/local/python3.10/bin/pyjion -o py-jit.json
then i use pyperformance to test with python3.10
pyperformance run -p=/usr/local/python3.10/bin/python3.10 -o py310.json
i found, It has no performance boost at all, why????

If the numbers are 1.0x, then it's definitely not running Pyjion. (it would be slower or faster)
I've never tried running the Pyperformance benchmark suite in that way, I don't think it would work because of how it invokes Python interpreters.

In this case, what should be used to test the performance of pyjion?

There is a benchmark suite script in the source repo, it gets run on CI
https://github.com/tonybaloney/Pyjion/runs/5967372554?check_suite_focus=true
See https://github.com/tonybaloney/Pyjion/blob/develop/main/Tests/benchmarks/suite.py
python Tests/benchmarks/suite.py
If you want to add another benchmark you can to the folder in tests, e.g. bench_example by adding a __benchmarks__ list to the bottom of the file.
python Tests/benchmarks/suite.py example
There are some existing benchmarks from the pyperformance suite already in the folder (e.g. delta blue, fannkuch, n-body).

This is only using the performance of pyjion.

How do compare performance with pyjion and without pyjion in python using  a benchmark suite script in the source repo

This is only using the performance of pyjion.

How do compare performance with pyjion and without pyjion in python using  a benchmark suite script in the source repo

It runs each benchmark twice. Once without Pyjion and once with Pyjion. The number without is the numbers in purple.
The right 3 columns show the percentage difference between the two

WHAT! it is surprised me so much!
So the performance of using pyjion may be reduced?

WHAT! it is surprised me so much!
So the performance of using pyjion may be reduced?

Yes. Some benchmarks are faster and some are slower.

authors: alittlesir tonybaloney

repo: tonybaloney/Pyjion


text:
Add snail pet

Hi there, I want to contribute to this repo by adding a new feature (pet snail). This is my first open-source PR, let me know if there is any problem, perhaps some guidance would be nice too. :)

This is a great PR, please can you look at my comments. Also please add an attribution for the artwork to README along with the others.

Codecov Report
Attention: Patch coverage is 38.46154% with 8 lines in your changes missing coverage. Please review.

Project coverage is 17.06%. Comparing base (61374a6) to head (c3dbc03).
Report is 28 commits behind head on main.

Files
Patch %
Lines

src/panel/pets/snail.ts
50.00%
4 Missing :warning:

src/extension/extension.ts
0.00%
2 Missing :warning:

src/panel/pets.ts
33.33%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #577      +/-   ##
==========================================
+ Coverage   16.58%   17.06%   +0.47%
==========================================
  Files          23       25       +2
  Lines        1236     1260      +24
  Branches      167      167
==========================================
+ Hits          205      215      +10
- Misses       1025     1039      +14
  Partials        6        6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I had rename the gif files as requested.

authors: WoofWoof0 codecov-commenter tonybaloney

repo: tonybaloney/vscode-pets


text:
Show Import Notifications in Navigation Sidebar not working...

I'm on win10 using new Microsoft Edge... it no longer has a line under account when there are transactions to be imported.  I'll click account and see 7 transactions waiting... Not sure about chrome or firefox.. :)
[{"key":"AccountsDisplayDensity","value":"1"},{"key":"AccountsEmphasizedOutflows","value":true},{"key":"AccountsStripedRows","value":true},{"key":"AutoDistributeSplits","value":true},{"key":"AutoEnableRunningBalance","value":true},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BottomNotificationBar","value":false},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":true},{"key":"BudgetSpendingGoal","value":false},{"key":"BulkManagePayees","value":true},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"CategorySoloMode","value":"cat-solo-mode-toggle-all"},{"key":"ChangeEnterBehavior","value":true},{"key":"ChangeMemoEnterBehavior","value":true},{"key":"CheckCreditBalances","value":false},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":true},{"key":"CollapseSideMenu","value":true},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":true},{"key":"ConfirmKeyboardCancelationOfTransactionChanges","value":true},{"key":"CreditCardEmoji","value":true},{"key":"CtrlEnterCleared","value":false},{"key":"CurrentMonthIndicator","value":true},{"key":"CustomFlagNames","value":false},{"key":"DateOfMoney","value":false},{"key":"DaysOfBuffering","value":false},{"key":"DaysOfBufferingDate","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DeselectTransactionsOnSave","value":true},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":false},{"key":"DisplayUpcomingAmount","value":true},{"key":"EasyTransactionApproval","value":true},{"key":"EditAccountButton","value":"2"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"1"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":true},{"key":"HideClosedAccounts","value":true},{"key":"HideHelp","value":true},{"key":"HideReferralBanner","value":true},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":true},{"key":"ImportNotification","value":"1"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":true},{"key":"LinkToInflows","value":true},{"key":"MonthlyNotesPopupWidth","value":"2"},{"key":"NavDisplayDensity","value":"0"},{"key":"NotesAsMarkdown","value":false},{"key":"POSStyleCurrencyEntryMode","value":false},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"4"},{"key":"RemovePositiveHighlight","value":true},{"key":"RemoveZeroCategories","value":true},{"key":"ResizeInspector","value":true},{"key":"ResizeSidebar","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"1"},{"key":"RowsHeight","value":"1"},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"StripedBudgetRows","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":true},{"key":"ToggleSplits","value":true},{"key":"ToggleTransactionFilters","value":"2"},{"key":"ToolkitReports","value":true},{"key":"ViewZeroAsEmpty","value":true},{"key":"l10n","value":"0"}]

I'm having the same issue. I'm using OS X Catalina on Chrome Version 84.0.4147.89 (Official Build) (64-bit)

Any update on this issue?  No import indicators for me either.

Hey @deermont2 the fix for this should be in our current release! If you notice the issue still exists and you're definitely running the newest version of the toolkit, please reopen! Thanks!
Please note, all browser can take up to an hour to provide updates to all users. You can force an update if it's available for you by going to chrome://extensions and clicking the "Update" button. Firefox users can go to about:addons, click the setting cog, and click "Check for updates...".

authors: JamesValero deermont2 joshmadewell tzusman

repo: toolkit-for-ynab/toolkit-for-ynab


text:
godep restore makes impossible to update project with go get

Currently godep restore puts the repositories in detached HEAD and this makes impossible to execute a go get -u github.com/foo/bar. If a high number of projects using godeps are used and if godep restore is used frequently, this leads to a very high number of projects in detached state which makes very hard to update them.
Are we able to avoid this somehow?

Longer term, yes, by removing the need to godep restore. A go tooling change recently (go1.6) made this a problem AFAIK.

PS: godep restore is doing what it's always done, restore the recorded versions to the $GOPATH. it can only do this by checking out the various shas (AFAIK) it's recorded.
As a temp work around I could implement a godep unrestore, which would check out master again. But I'm hesitant to add another command that should be removed in the future and I'm not sure it's super helpful in the workflow ... ie. you have to remember to use it.
Thoughts?

I was about to implement a godep unrestore myself, I think it would be useful (I can work on it and submit a PR, but if you want to work on it, as you whish). More important, though is to document in the README what happens now if a user executes godep restore.
Also, can you give me the detail of this change in 1.6 you are mentioning above?

PRs welcome. I don't have an exact commit to golang where this broke. Let me see if I can dig it up though.

It was likely this one: https://github.com/golang/go/commit/42206598671a44111c8f726ad33dc7b265bdf669

@Raffo What would you suggest be added to the README? It states what godep restore already does in a non VCS specific manner, since godep handles multiple types of VCS.

Thanks for the link to the commit.
Do you think that a warning like "godep restore could leave some of the dependencies in a detached state. This could lead to problems to update your dependencies" would be too much? Maybe we could add some text to specify that the users should avoid using godep restore if not strictly necessary.

How about
NOTE: godep restore leaves git repositories in a detached state. go1.6+ no longer checks out the master branch when doing a go get, see here.
Then if you land an unrestore PR we can adjust that to recommend the usage of unrestore afterwards?

Sounds good to me.

@Raffo README / restore help text updated in 584a3f5bf2671886bd3f7dc2b252762b5aa2a087

:+1:

As I imagined, it's very easy to hack an "unrestore" command to checkout the master, but it's not so easy to make the unrestore command so general that can handle cases in which the default remote branch is different from the master. I would have to add this information to Godeps.json (the remote HEAD), but I'm not sure we want that.
If we agree that we will implement that, I wouldn't know any valid command that will give me the current remote HEAD. The only valid info I know how to get is in git remote show origin, but I don't really want to parse the output. Any suggestion/help?

@freeformz Any input on what I wrote above?

Why does the remote branch matter? I don't think we want to pull new code with unrestore, just check out the local master.

@freeformz because it's not obvious that the main branch is the master. If you clone a repository which remote HEAD is not the master you will end up with something different than a master branch. In such a case, if godep unrestore tries to restore it to the master branch this could lead to wrong results.

It only matters what it's merged to locally AFAIK, so git config --local branch.master.merge should tell us what to checkout.
I could totally be wrong here, I don't think I've ever worked with remotes who HEAD was not master.

Take the gin repository: the master`` branch exist, but the remote HEAD is develop```. I think that in this case it will not work.

I see. If there is only one branch returned with git config --local --get-regexp 'branch.*' we could check that out and otherwise punt with instructions to the user to start?

Or we just modify Godep.json to be something like:
	{
			"ImportPath": "github.com/spf13/pflag",
			"Rev": "8f6a28b0916586e7f22fe931ae2fcfc380b1c0e6",
			"RemoteHEAD": "master"
		},

And use the RemoteHEAD when executing unrestore. This will break only in case the remote head of the repo changes from the last time the Godep.json is updated, which is not perfect, but acceptable (IMO).

I'm not sure I really want to require people to populate that field manually. Also AFAICT RemoteHEAD is detectable through either:
$ git remote show origin
...
HEAD branch: develop
...

or
$ git branch -r | grep "origin/HEAD ->"
  origin/HEAD -> origin/develop

possibly some other means as well.

This is exactly what I meant, RemoteHEAD would be populated when godep save is executed. When doing godep unrestore we could also add a --force option (I'm not sure if this flag is already used in another way in other godep commands) to remove the dependency and re-executing a go get from scratch in case of failures. Obviously after a warning and a confirmation from the user.

I'm not sure we should save RemoteHEAD though and just honor the remote head from git info for what's already there.

So, what you suggest is to just use the info from git remote show origin , i.e:
* remote origin
  Fetch URL: https://github.com/kubernetes/kubernetes.git
  Push  URL: https://github.com/kubernetes/kubernetes.git
  HEAD branch: master
  Remote branches:

Is this right?

FWIW, today I got fed up with this and just banned godep restore from my entire system.  I did this with a script:
https://github.com/eduncan911/dotfiles/blob/master/bin/godep
If you want it, check it out into your ~/bin, first make sure your personal ~/bin comes before your $GOPATH/bin:
If so, you are good to go.  If not, you may want to tweak your $PATH to use your personal ~/bin before your GOPATH/bin.
Get the file locally:
curl -L https://raw.githubusercontent.com/eduncan911/dotfiles/master/bin/godep --create-dirs -o ~/bin/godep
chmod 755 ~/bin/godep

Use it normally:
godep go run main.go
godep get foo/bar

...etc.  And when you try to do godep restore:
$ godep restore
WARNING: godep restore <- this will frack with your /Users/eric/go !!
WARNING: to override, use your installed version of godep like this:
WARNING:      $GOPATH/bin/godep restore
WARNING: Aborting ...

hehe.  👍
I'm in the habit of using the godep prefix for all my go needs anyways:
godep go test ./...
godep go run main.go
godep get foo/bar

...etc.  But I've accidently used godep restore a few times, like today when I ran a Makefile for a new repo I was working on.  Argh!  Spent over an hour restoring all of my $GOPATH repos back to master.
No more!

No need to spend an hour restoring them all, just do:
find $GOPATH/src -type d -name .git -execdir git --git-dir={} checkout master \;

i have to exclude the dozen or so that I am working on...  that do have pending commits, on different branches, etc.

authors: Raffo eduncan911 freeformz tsuna

repo: tools/godep


text:
使用.Net 4.x时，某些情况捕获不到异常，导致luastate崩溃

将scripting runtime version 设置为 .net 4.x equivalent
然后在updateBeat 里设置transform.localPosition = nil时 , luastate会崩溃

在luajit 跟 .net4.x 用的同样的异常处理方式，这种情况对于为性能特殊写得Vector3类Get,Set函数不能出错，因为这些函数用的lua_call调用。1.用luac5.3分支可以避免这种异常 2.不要写错

authors: lllllgb topameng

repo: topameng/tolua


text:
Explosions!

Because why not?
And have explosions have an AOE

We need an explosion Animation @Heebe , might I suggest just one frame as a red circle, and the next the same circle black

Going to use emanuals animation instead

Cause we could ;)
via c1c72e086ca34cffaf34fe901048b87d72b06fa8


text:
rviz plugin get segmentation fault when it stated

$ roslaunch jog_launch ur5.launch use_fake_joint:=true use_rviz:=false use_moveit:=true
$ rviz -d default

get segfault. It happens only the released binary, not with the binary built from source.
Stack trace:
Thread 1 "rviz" received signal SIGSEGV, Segmentation fault.
0x00007ffff43bd4a1 in ros::Time::now() ()
   from /opt/ros/kinetic/lib/librostime.so
(gdb) bt
#0  0x00007ffff43bd4a1 in ros::Time::now() ()
   from /opt/ros/kinetic/lib/librostime.so
#1  0x00007fff9824fbbe in jog_controller::JogFramePanel::publish() ()
   from /opt/ros/kinetic/lib//libjog_controller.so
#2  0x00007ffff1f7fd2a in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007ffff1f8c5c8 in QTimer::timerEvent(QTimerEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007ffff1f80bb3 in QObject::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ffff746405c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x00007ffff7469516 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x00007ffff1f5138b in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ffff1fa65ed in QTimerInfoList::activateTimers() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ffff1fa6af1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff14a8197 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff14a83f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#12 0x00007ffff14a849c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff1fa77cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop:
:ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ffff1f4eb4a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>
) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ffff1f56bec in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x0000000000400c99 in main ()

I built it in Release mode and stripped, but  I can't reproduce this with the library built from source code.
When I copied the libjog_controller.so to system, it works.
What could be difference between source built library and the released library?

Any thought @534o ?
Have you experienced the difference between local build and build farm's build?

one possibility is you have rviz or other deb which is build before the newer the latest rostime, that includes changes in it's header files https://github.com/ros/roscpp_core/blob/kinetic-devel/rostime/CHANGELOG.rst
you can check the build time by https://github.com/tork-a/88_tools/pull/20
easy way is to run apt-get dist-upgrade,


text:
Modernize Repository (First Pass)

[x] Reorganize Package Structure
[x] Packages Directly Reference Each other
[x] Format Code
[x] Update to Rust 2021 Standard
[x] Fix Various Package Incompatibilities
[x] Apply Clippy Auto-Fixes
[x] Fix Spelling Errors
[x] Basic Testing Workflow

ACK 196a87ae9f481b24be2cc6fa6a8bef44fae56835


text:
does this library support DDL?

if no - is DDL support planned in the future, and when?
(P.S. I mean automatic DDL - I define only model, and library does all ALTER/CREATE TABLE, etc.)

Hi @Jusys,
it's very complicated to do it through the all DB engines. It's good idea, but currently we don't have any free time for it. Of course, it would be nice to have it :-)

authors: Jusys petersirka

repo: totaljs/node-sqlagent


text:
Not showing CoreProtect data

Tested on 1.8
Watson version 0.10.0
Prism results show just fine.
Breaking block and running '/co l r:10' - nothing appears.

I just retested everything and it's still working fine for me.
What version of CoreProtect are you using?  Are you enabling the watson display first with /w display on?

I was using CoreProtect 2.0.9, but after updating to 2.1.2, the issue is now resolved.
Apologies for the inconvenience .

authors: Iraos tompreuss

repo: totemo/watson


text:
USB MIDI HOST failed on ESP32 S3 potentially on S2 as well?

Built midi project with your library but seems like real midi devices(self powered) don't work on ESP32 S3 and probably on S2 as well?
Here is output from serial monitor
E (1604) HUB: Configuration descriptor larger than control transfer max length
E (1605) HUB: Stage failed: CHECK_SHORT_CONFIG_DESC
This is with normal Yamaha piano has dc power and usb midi port.
EDIT: Seems like the issue could be defualt menu config value for max transfer value which is 256 bytes arduino core for esp32 probably has that as default as well. The hard part now is to change that.

I have 0 issues with phone as midi or Arduino Leonardo as midi device both work fine maybe the descriptor is small enough so esp can enumerate the device without issues?
Here is difference between working midi device and non working one(the error i mentioned above)
    Configuration Descriptor (Working Device):
    wTotalLength: 0x00AF (175 bytes)
    bNumInterfaces: 0x04 (4 Interfaces)
    bmAttributes: 0xA0 (Self-Powered, Remote Wakeup)
    MaxPower: 0xFA (500 mA)

    Configuration Descriptor (Problematic Device):
    wTotalLength: 0x012F (303 bytes)
    bNumInterfaces: 0x04 (4 Interfaces)
    bmAttributes: 0xC0 (Self-Powered)
    MaxPower: 0x01 (2 mA)

here is full configuration_descriptors for both working one and non working one
Working one(Arduino Leonardo as MIDI and Android phone as MIDI)
 bLength                  : 0x09 (9 bytes)
 bDescriptorType          : 0x02 (Configuration Descriptor)
 wTotalLength             : 0x00AF (175 bytes)
 bNumInterfaces           : 0x04 (4 Interfaces)
 bConfigurationValue      : 0x01 (Configuration 1)
 iConfiguration           : 0x00 (No String Descriptor)
 bmAttributes             : 0xA0
  D7: Reserved, set 1     : 0x01
  D6: Self Powered        : 0x00 (no)
  D5: Remote Wakeup       : 0x01 (yes)
  D4..0: Reserved, set 0  : 0x00
 MaxPower                 : 0xFA (500 mA)
 Data (HexDump)       :
                       09 02 AF 00 04 01 00 A0 FA 08 0B 00 02 02 02 00   ................
                       00 09 04 00 00 01 02 02 00 00 05 24 00 10 01 05   ...........$....
                       24 01 01 01 04 24 02 06 05 24 06 00 01 07 05 81   $....$...$......
                       03 10 00 40 09 04 01 00 02 0A 00 00 00 07 05 02   ...@............
                       02 40 00 00 07 05 83 02 40 00 00 08 0B 02 02 01   .@......@.......
                       01 00 00 09 04 02 00 00 01 01 00 00 09 24 01 00   .............$..
                       01 09 00 01 03 09 04 03 00 02 01 03 00 00 07 24   ...............$
                       01 00 01 41 00 06 24 02 01 01 00 06 24 02 02 02   ...A..$.....$...
                       00 09 24 03 01 03 01 02 01 00 09 24 03 02 04 01   ..$........$....
                       01 01 00 09 05 04 02 40 00 00 00 00 05 25 01 01   .......@.....%..
                       01 09 05 85 02 40 00 00 00 00 05 25 01 01 03      .....@.....%...

Non working Yamaha digital piano configuration_descriptor
 bLength                  : 0x09 (9 bytes)
 bDescriptorType          : 0x02 (Configuration Descriptor)
 wTotalLength             : 0x012F (303 bytes)
 bNumInterfaces           : 0x04 (4 Interfaces)
 bConfigurationValue      : 0x01 (Configuration 1)
 iConfiguration           : 0x00 (No String Descriptor)
 bmAttributes             : 0xC0
  D7: Reserved, set 1     : 0x01
  D6: Self Powered        : 0x01 (yes)
  D5: Remote Wakeup       : 0x00 (no)
  D4..0: Reserved, set 0  : 0x00
 MaxPower                 : 0x01 (2 mA)
 Data (HexDump)       :
                       09 02 2F 01 04 01 00 C0 01 08 0B 00 03 01 00 20   ../............
                       00 09 04 00 00 00 01 01 20 00 09 24 01 00 02 08   ........ ..$....
                       5D 00 00 08 24 0A 01 01 03 00 00 12 24 06 06 02   ]...$.......$...
                       0C 00 00 00 00 00 00 00 00 00 00 00 00 11 24 02   ..............$.
                       02 01 01 00 01 02 03 00 00 00 00 00 00 00 0C 24   ...............$
                       03 03 17 07 00 06 01 00 00 00 11 24 02 04 17 07   ...........$....
                       00 01 02 03 00 00 00 00 00 00 00 0C 24 03 05 01   ............$...
                       01 00 02 01 00 00 00 09 04 01 00 00 01 02 20 00   .............. .
                       09 04 01 01 01 01 02 20 00 10 24 01 02 00 01 01   ....... ..$.....
                       00 00 00 02 03 00 00 00 00 06 24 02 01 02 10 07   ..........$.....
                       05 05 05 B4 00 01 08 25 01 00 00 00 00 00 09 04   .......%........
                       02 00 00 01 02 20 00 09 04 02 01 01 01 02 20 00   ..... ........ .
                       10 24 01 05 00 01 01 00 00 00 02 03 00 00 00 00   .$..............
                       06 24 02 01 02 10 07 05 84 25 B4 00 01 08 25 01   .$.......%....%.
                       00 00 00 00 00 09 04 03 00 02 01 03 00 00 07 24   ...............$
                       01 00 01 41 00 06 24 02 02 01 00 09 24 03 01 61   ...A..$.....$..a
                       01 01 01 00 06 24 02 01 21 00 09 24 03 02 41 01   .....$..!..$..A.
                       21 01 00 09 05 03 02 40 00 00 00 00 05 25 01 01   !......@.....%..
                       21 09 05 82 02 40 00 00 00 00 05 25 01 01 61      !....@.....%..a

Can you provide guidance on how to fix this or give me some hints where to look?
Thanks!

I resloved the issue, after re compile of sdk for s2/s3 with CONFIG_USB_HOST_TRANSFER_MAX_SIZE=4096 and deleting esp32s2/s3 folder from the Arduino15\packages\esp32\hardware\esp32\2.0.14\tools\sdk and placing my recompiled sdk's it works. I'm closing this as I resloved my issue!


text:
Add a concurrency param to integration test workflow

If multiple PRs are building at the same time, our integration tests can publish multiple versions and get stuck (triggering #117). We should adjust the workflow to make sure it runs serially, similar to KMMBridgeGithubWorkflow.
Note that we don't want a dynamic key in this case. eg if we had a different key for each PR, then this would not work.

Should just need to update the integration test workflow in KMMBridge

To test. trigger multiple workflows at the same time and make sure the versions process correctly

repo: touchlab/KMMBridge


text:
🛑 Accela is down

In a0be394, Accela (https://aca-prod.accela.com/santaclara) was down:

HTTP code: 503
Response time: 109 ms

Resolved: Accela is back up in 862b830 after 16 minutes.

repo: touzesabine/uppdownn


text:
Green Lamp - Gateway unreachable

Actually the adapter doesn't show if the ems-esp gateway is reachable:

Today my gateway get stuck, and I didn't recognize, because the lamp was green.
Isn't there a possibility to make it like this:

I tried my best to implement. Since the adapter supports 2 gateways parallel (ems-esp and km200) and there is only one connection status available, the status shows availability of one gateway as an error.
Within the states under info.connection and  info_connection__ems / info.connectio_km200 the details can be seen.
You can test by installing the latest version from Github. Please report if any disconnection is properly seen.

so you did something for this in the latest version?
I mean, you could implement it like the adapter only checks the checkmarked gateways.

Please install the version from GH and give a Feedback.

Looks good actually.

Looks good actually.


text:
"incompatible library version"

I have ruby 2.6.5 and 2.6.6 installed with communized gems. I have noticed I'm getting errors like:
Traceback (most recent call last):
...
.../lib/active_support/dependencies.rb:324:in `require': incompatible library version - .../redcarpet-3.5.0/lib/redcarpet.bundle (LoadError)

Has anyone else been having this trouble? I know it's not caused by this plugin, just wondering if other users are having the same trouble and if the plugin might not work for future versions.

Can confirm, Ruby 2.6 has given me so many problems that I ended up disabling communize-gems entirely.

ended up disabling communize-gems entirely

Yeah, I did the same 😞

repo: tpope/rbenv-communal-gems


text:
Fix field variable in NTT constants generation

Hi,
I noticed a small typo in the NTT constant generation script, that prevents from directly reproducing this step.

I committed a second change replacing a hard-coded constant in the NTT code by an existing variable.
It makes it a bit easier to reuse the code with a different modulo.


text:
Unable to Query deleted records - UNEXPECTED EXCEPTION:TypeError: Cannot read properties of undefined (reading 'length')

When performing a query and selecting "Add deleted record" checkbox, I always get the following error:
UNEXPECTED EXCEPTION:TypeError: Cannot read properties of undefined (reading 'length')
This is happening to me and other colleagues in any org and for any object (both standard and customs)
This is happening from version 1.240

Hi @frpanico ,
This is a duplicate of the #538 where I provided more info about the resolution and a workarounf.
I'm closing this issue.

authors: frpanico tprouvot

repo: tprouvot/Salesforce-Inspector-reloaded


text:
Update scala-library to 2.13.10

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

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:2

Superseded by #189.


text:
Old 32-bit version of Ubuntu used for image

To avoid problems with Android SDK 32-bit toolchain I've used 32-bit old Ubuntu. I should add 32-bit support to my image based on Ubuntu 14.04

I got your docker image of android emulator: tracer0tong/android-emulator  from github. I use it this way:

        $ docker pull tracer0tong/android-emulator:latest

        $ docker run -d -P --name android tracer0tong/android-emulator

        $ docker ps –a

I get:
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                        PORTS                         NAMES
a5f9318c6496        tracer0tong/android-emulator   "/entrypoint.sh -e an"   25 minutes ago      Up 25 minutes                 0.0.0.0:32771->22/tcp, 0.0.0.0:32770->5554/tcp, 0.0.0.0:32769->5555/tcp, 0.0.0.0:32768->5900/tcp android
So, it seems working and it can provide adb ports.
4)             $ adb connect 192.168.99.100:32769, it succeed
5)             $ adb devices. It failed, does not display any information
I tried to play with this image for 2 days, used different ways , but can’t make it work.
I hope to get an android emulator that can support adb commands, so I can install software in it. And by using Appium, I can control this android emulator, just like I control android physical devices.


text:
Feat/untagged resources

Split PR#230 (https://github.com/trackit/trackit/pull/230) - Part 1
This branch is reserved for the feature.

The branch hasn't been tested yet.

@cruffinoni let us know when this pull request has been tested and is ready to review ;)

Blocked because we don't have a pagination mechanism with Elasticsearch. To be brainstormed by @hug33k @giubil @thibautcornolti @jgchoppe @cruffinoni
This comment is just to keep track, no worries ;)

Blocked because we don't have a pagination mechanism with Elasticsearch. To be brainstormed by @hug33k @giubil @thibautcornolti @jgchoppe @cruffinoni
This comment is just to keep track, no worries ;)

@hug33k any news about this ?

@Dr0p42 : I found a solution to decrease the size of Aggregation queries. I use "partitions" that allow to paginate the aggregations. It works correctly and there is no data loss. I don't know the specific cases that were problematic, so I'll let you test this upgrade on this cases when you have the time.

This PR is now redundant with tagbot

authors: Dr0p42 alexandre-snr cruffinoni simonmeyerrr

repo: trackit/trackit


text:
Protect cluster ProductID checks for empty collections in MkFitProducer

PR description:
Backport from https://github.com/cms-sw/cmssw/pull/35457.
PR validation:
None beyond what is in https://github.com/cms-sw/cmssw/pull/35457.

I'm getting crashes in the "cube" sample tests, which should apparently be fixed by this PR.
Is there any concern to merge it?

Merging already before  cms-sw#35457 since there appears to be actual need for the fix.

repo: trackreco/cmssw


text:
ConvertTranslatableTask: Uncaught LogicException: Cookie 'alc_enc' can't be set.

When trying to run ConvertTranslatableTask I get the following error:
Uncaught LogicException: Cookie 'alc_enc' can't be set.
If I then remove the following line from ConvertTranslatableTask (line 127):
Security::findAnAdministrator()->login();
It will run fine, if I am logged in as admin of course.
I've not yet looked at what could be causing the problem, just figured I'd create an issue

Oh, thanks for checking that. There is a config flag we can set, I believe, that disables that error. We can probably set that during migration.

authors: sanderha tractorcow

repo: tractorcow/silverstripe-fluent


text:
Intended behavior of layering (z-index?) of price lines relative to candlesticks data? How do I have price lines show above the candlesticks?

I classified this issue as "Other" in the event that it's not a bug and I'm going about this the incorrect way.
What is the intended behavior of the layering of the price lines relative to the candlestick data? It seems I'm unable to have the price line appear above the candlesticks data. Please see image below for what I am experiencing.

I tried calling the createPriceLine() and setData() methods on the candlestick series both before and after each other but was unable to achieve a different outcome in the ordering in the layering of elements in the chart. The candlesticks data always appears above or on top of the price lines, as shown in the image.
Am I missing something?
These price lines are attached to the candlestick series.
I love the library, by the way.
Many thanks!

Duplicate of https://github.com/tradingview/lightweight-charts/issues/684 and https://github.com/tradingview/lightweight-charts/pull/806?
Are we still waiting on the next major version (4.0.0) to drop before seeing this fix? I'm using version 3.8.0 (latest).

Yes, this is fixed in the next major release (4.0.0). If you need the fix before it is released then you can clone this repo and build the library off the master branch. You could then use the pre-release version within the dist folder.

This issue has been resolved with the v4.0.0 release.

authors: SlicedSilver jakemayfield

repo: tradingview/lightweight-charts


text:
Browser freezes when updating chart data.

Lightweight Charts™ Version: 4.1.2
Steps/code to reproduce:
const chart = LightweightCharts.createChart(document.getElementById("chart"));
let series = chart.addLineSeries();
series.update({
	"time": "2023-12-27",
	"value": 459761321634093
});

Actual behavior:
Browser freezes.
Expected behavior:

Screenshots:

CodeSandbox/JSFiddle/etc link:
https://jsfiddle.net/L3rvudpc/

Thanks @pkquell
The library does appear to have an issue when the data value becomes very large. The test value is less than Number.MAX_SAFE_INTEGER so it is something that should be fixable in the library without needing to use BigInt. However support for BigInt is really good across browsers so it should be safe to use that if required.

authors: SlicedSilver pkquell


text:
feat: unify plugin import between traefik and this chart

What does this PR do?
Fix issue https://github.com/traefik/traefik-helm-chart/issues/953
Motivation
need it
More
Only syntax test with https://helm-playground.com
Result not tested...

Thanks for this PR !
It needs also some tests, to be sure it will be kept in the future.

authors: mloiseleur mysiki

repo: traefik/traefik-helm-chart


text:
Router priority is not shown in dashboard

Let's say that you define a router in traefik.yml like this:
http:
  routers:
    catch-all:
      rule: "HostRegexp(`{host:(blog|support)(-(dev|test))?\\.company\\.(local|com)}`)"
      priority: 1
      tls: {}
      service: "noop@internal"

Once you open the dashboard, priority isn't shown anywhere in router details:

Can priority info be added to router details?

Fixed by #9004

authors: aleksvujic tomMoulard

repo: traefik/traefik


text:
How to specify Output Class in Process Builder

Hi,
How do I specify an the field to Output to in the 'Calculate Business Hours' class when called from a Process Builder
I have specified my inputs, but there doesn't appear to be an area for setting which field should be updated
Thanks

Hi @neilascott, thanks for reaching out.
Invocable Actions are shared between Process Builder and Flow Builder.
Unfortunately Process Builder does not support output for actions. This means that you can only use the calculate business hours actions in a Flow.

I'm sorry for the confusion but there's - sadly - no way to disable the action in Process Builder.

authors: neilascott pozil

repo: trailheadapps/automation-components


text:
Update README.md

Added documentation regarding the --extensions_default_index=false flag for the fwctl extension
Applicable Issues
#58
#65

Thanks for identifying this Garret

authors: GarretReece mike-myers-tob

repo: trailofbits/osquery-extensions


text:
Split Item and TraktItem models

Item and TraktItem are now split between episode, show and movie.
This PR has the potential to break a lot of things, because the structure of the models has been changed a bit. But I tested a bit and it seems to be working.

Some of the error where because I forgot to migrate config.json to .env.
I haven't been able to pinpoint the exact problem, but it seems to search for episode titles even when season and episode information is available.

The updates I just pushed fixed the matching errors for me (remember to clear your cache when testing).

authors: MrMamen rafaelgomesxyz

repo: trakt-tools/universal-trakt-scrobbler


text:
🛑 Portainer is down

In 8e4bcf0, Portainer (https://prt-prod.langstadlinger.eu) was down:

HTTP code: 521
Response time: 183 ms

Resolved: Portainer is back up in 28dd731.

repo: traktuner/status


text:
[android] Java.Net.SocketException and Javax.Net.Ssl.SSLException are thrown in Debug not in Release

I see in code that you correctly catch Java exceptions and re-throw them as HttpRequestExceptions.
Strangely when i am in Debug mode only i catch no HttpRequestException instead the Java ones as
unhandled exceptions.
Its an edge-case but maybe if you have time you can have a look at it.
Glad to help when a time-window opens.
var innerHandler = new SecureHttpClientHandler(null);
client = new HttpClient(innerHandler);

at Java.Interop.JniEnvironment+InstanceMethods.CallObjectMethod (Java.Interop.JniObjectReference instance, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x0006e] in <1959115d56f8444789986cf39185638c>:0
at Android.Runtime.JNIEnv.CallObjectMethod (System.IntPtr jobject, System.IntPtr jmethod, Android.Runtime.JValue* parms) [0x00000] in /Users/builder/azdo/work/2/s/xamarin-android/src/Mono.Android/Android.Runtime/JNIEnv.g.cs:102
at Square.OkHttp3.IInterceptorChainInvoker.Proceed (Square.OkHttp3.Request request) [0x0005a] in <0eabf675945747edb17222b3720748da>:0
at SecureHttpClient.DecompressInterceptor.Intercept (Square.OkHttp3.IInterceptorChain chain) [0x00007] in :0
at Square.OkHttp3.IInterceptorInvoker.n_Intercept_Lokhttp3_Interceptor_Chain (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_chain) [0x0000f] in <0eabf675945747edb17222b3720748da>:0
at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.115(intptr,intptr,intptr)
--- End of managed Javax.Net.Ssl.SSLException stack trace ---
javax.net.ssl.SSLException: Write error: ssl=0x6ecedf6d08: I/O error during system call, Software caused connection abort
at com.android.org.conscrypt.NativeCrypto.SSL_write(Native Method)
at com.android.org.conscrypt.NativeSsl.write(NativeSsl.java:426)
at com.android.org.conscrypt.ConscryptFileDescriptorSocket$SSLOutputStream.write(ConscryptFileDescriptorSocket.java:626)
at okio.OutputStreamSink.write(JvmOkio.kt:56)
at okio.AsyncTimeout$sink$1.write(AsyncTimeout.kt:99)
at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.kt:255)
at okio.RealBufferedSink.write(RealBufferedSink.kt:146)
at okhttp3.internal.http1.Http1ExchangeCodec$KnownLengthSink.write(Http1ExchangeCodec.kt:271)
at okio.ForwardingSink.write(ForwardingSink.kt:29)
at okhttp3.internal.connection.Exchange$RequestBodySink.write(Exchange.kt:218)
at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.kt:255)
at okio.RealBufferedSink.write(RealBufferedSink.kt:185)
at okhttp3.RequestBody$Companion$toRequestBody$2.writeTo(RequestBody.kt:152)
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:59)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at crc647d92411772b9fe65.DecompressInterceptor.n_intercept(Native Method)
at crc647d92411772b9fe65.DecompressInterceptor.intercept(DecompressInterceptor.java:30)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:919)

Yes, I'm aware of it. I think it's related to the way xamarin handles exceptions and pass then between java and .net, which is different between debug and release. But so far I haven't found a proper explanation and a way to fix it.
However, I was assuming this issue is not occurring when using the SecureHttpClient nuget, right ? (since it's built in release mode).
Could you explain what is your scenario ?

are you debugging an application that uses the SecureHttpClient nuget ?
or are you debugging the SecureHttpCient code ?

i am deubbing an application that uses the SecureHttpClient nuget.

I will try it and report to you. Also i noticed in AppCenter logs that i do not have a single HttpRequestException.
Since you catch some Java exceptions and rethrow them as HttpRequestExceptions i should at least have one
instead of Java ones. This is not the case.

Fixed in 1.18.4

Could you add a catch also for Java.Net.ConnectException when there is no internet connection

@gsgou Could you please open a new issue ? I'm not sure I understand your request, so it's better to separate discussions.


text:
test old demo deploy

old demo deploy

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against d27a57b3c872194c9515667d573af710067678f0

authors: deandreJones robot-mymove

repo: transcom/mymove


text:
Load testing with locust.io

Description
This PR implements load testing with the locust.io load testing framework. The application code relies on using the Yelp Bravado Swagger Client which uses our applications own swagger files to create API calls.
The load testing demo implements these things:

Anon User: Touching home page only
Service Member App: PPM Flow only
Office App: Queue and Move Inspection (no move modification)
TSP App: Queue and Move Inspection (no move modification)

To enable load testing these PRs had be merged in transcom/mymove:

#1685 - automated creation of devlocal users
#1823 - don't return nil for dutystation
#1824 - rework devlocal methods for signin
#1861 - logout should use POST (See #1858 and #1830)
#1905 - devlocal create and login as any user
#2071 - Authentication POST issues
#2072 - Unique Devlocal Users
#2073 - Fix Swagger Office Queue Spec
#2074 - Remove 'format: string' from spec
#2081 - Enable devlocal auth from flag
#2187 - Fix move queue last modified date and name
#2213 - Fix missing swagger payloads
#2241 - Devlocal login using email
#2268 - Return 404 for missing PPM Discount information
#2269 - Fix entitlement calculator with missing weight estimate
#2299 - Remove troubleshooting queue item
#2306 - Fix nil error bug for TSP API
#2319 - Missing 422 errors

And these changes had to be made in transcom/ppp-infra:

https://github.com/transcom/ppp-infra/pull/532 - Make Experimental env match Staging/Prod

As part of load testing these PRs were created to fix our systems:

#2324 - Set DB Pool size

Reviewer Notes
I feel as though this ought to be a separate repository from MilMove. I can easily move this and maintain the history if folks would like it.
Setup
Local Development
First install the requirements:
cd load_testing
virtualenv .venv
source .venv/bin/activate
pip install -r requirements.txt
cd ../

Then in one terminal make sure the application is running:
make server_run

From another terminal you can run in the browser with:
locust -f load_testing/locustfile.py

And then visit http://localhost:8089. Or you can run without the web interface here:
locust -f load_testing/locustfile.py --no-web --clients=50 --hatch-rate=5 --run-time=120s

Here is an example of the load testing output: https://gist.github.com/chrisgilmerproj/7f542d94d90dfd515b076ef10771b1a3
Experimental Environment
To load test the experimental environment you must modify the DEVLOCAL_AUTH environment variable and deploy the code to the experimental environment.
Then you can use the same steps as the development as above as long as you change the host parameter in the locustfile.py test classes and point them to the experimental domains:

https://my.experimental.move.mil
https://office.experimental.move.mil
https://tsp.experimental.move.mil

Code Review Verification Steps

[ ] Test against Experimental
[ ] Request review from a member of a different team.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change

There's a "60 day rule" that means we don't guarantee data more than 60 days out. So the load test should enforce dates be within that 60 days.

@pjdufour-truss @rdhariwal @tinyels - I think the next step here is to get this approved. Instead of merging it I'll open a new git repository and make this the initial commit (I can keep the commit history when I copy it over). Then folks can start making changes to that code as they see fit.

I have moved the code to a new repository: https://github.com/transcom/milmove_load_testing


text:
[MB-4229] Hide back btn and add 'finish later' btn to review page

Description
Removes "back" button and adds "Finish Later" button to the review page. Since there are a handful of other tickets to deal with routing and buttons on the whole flow (see tickets tagged with the epic "routing updates" - https://dp3.atlassian.net/browse/MB-3849), I adapted the Wizard Page to take props to hide the back btn and to show the "finish later" button. I thought this best in order to roll out the changes iteratively.
Review notes
The desktop view shows the cancel button still. Since we will be removing the cancel button in a future ticket, it seems like that work will be taken care of outside of the scope of this ticket.
Setup
See the review page and ensure that there is no back button, and the "finish later" routes to the home page.
Code Review Verification Steps

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Warnings

:warning:

Files located in legacy directories (src/shared or src/scenes) have
been edited. Are you sure you don’t want to also relocate them to the new file structure?
View the frontend file org ADR for more information

Messages

:book:
:link: MB-4229

  Generated by :no_entry_sign: dangerJS against a6cf67e6451a3f8b3572aad066b4aec1363e4277

@Shkeating @suzubara I'm having trouble with the formatting and display of the buttons to match the spec and was hoping you could offer some insight and help. I'll list the issues here, referencing the screenshots in the PR description:

Because the wizard buttons are inside a grid-row, it seems like the spacing of the buttons on the right is off and doesn't align with the "add a shipment" button. Moving them out of a row and into a grid-col-row fixes it, but then the buttons are not horizontally aligned on desktop view, but rather, vertically aligned. Not a good look :/
The "finish later" button size does not match the "next" button, and it's much "smaller", as compared to the screenshot of the buttons Kim posted above.
I'm not sure how to handle the margin between the "next" and "finish later" buttons and the "add shipment button" section. I adapted the existing style applied to the div on the wizard page (changed from .5rem to 2rem) but am not sure if this is the best practice way to handle this. I also don't know what the units in abstract represent - is that 6 px? Or 6 units of a pixel measurement?


text:
[MB-14533] capture updates to customer information

Jira ticket for this change
Summary
Two bugs are being handled in this PR. The first is surrounding customer name updates by service counselor not being captured. That was due to a missing template which has now been added. The second was a similar bug; but for the backup contact. Which was resolved by adding a wildcard event name to the pre-existing template updateServiceMemberBackupContact since the only difference in the code would be the event name.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the UI locally.
make client_run

Terminal 2
Start the Go server locally.
make server_run

Additional steps

Login as a services counselor
Find a move (I used 8B63JG)
On move details page, scroll down and click "Edit customer info"
Update a field for the customer name
update a filed for the backup contact
Click "Save"

Verification Steps for Author
These are to be checked by the author.

[x] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Screenshots
Updating Customer Name Before:

Updating Customer Name After 🎉 :

Updating Backup Contact Before:

Updating Backup Contact After 🎉 :

Messages

:book:
:link: MB-14533

  Generated by :no_entry_sign: dangerJS against f8f3881a99914746482e24e304250b0fcf543bcf

authors: robot-mymove ruizajtruss


text:
Remove Ruby 1.8 support, gem requires at least 1.9.2 now.

This is the counterpart to https://github.com/transloadit/ruby-sdk/pull/23, same things apply :)

Done this with a bunch of commits in master.

repo: transloadit/rails-sdk


text:
remote_syslog2 needs updating to 0.14+ to continue to work

http://blog.papertrailapp.com/april-14-new-sha2-tls-certificate-for-log-destinations/
On April 14, Papertrail deployed a new SHA-2 certificate, discovered that older versions of remote_syslog2 (0.13 and prior) did not accept the certificate, and reverted to the prior SHA-1 certificate.
...
The certificate will be deployed permanently on *Wednesday, May 4*, 2016.

There is now 0.17 released as of 16th Feb

Actual path to the released 0.17 file is https://github.com/papertrail/remote_syslog2/releases/download/v0.17/remote_syslog_linux_i386.tar.gz.
(i symbol is missing in this commit)

fixed

I'll get this update published to the supermarket on Monday. Thanks for contributing!

This is now live in 0.3.0 on the supermarket: https://supermarket.chef.io/cookbooks/remote_syslog2#changelog

authors: andytson trappar uson1x


text:
🛑 TechinAsia_WordPress_API is down

In 63159e6, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 227 ms

Resolved: TechinAsia_WordPress_API is back up in fde8095 after 13 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia_Laravel_API is down

In c64d83c, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 232 ms

Resolved: TechinAsia_Laravel_API is back up in f8e403a after 14 minutes.


text:
🛑 TechinAsia is down

In 4737406, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 957 ms

Resolved: TechinAsia is back up in 860d34e after 9 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 99c9e9f, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 230 ms

Resolved: TechinAsia_WordPress_API is back up in 370f72d after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 099cd4f, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 232 ms

Resolved: TechinAsia_WordPress_API is back up in c688284 after 22 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In 1f58fb1, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 173 ms

Resolved: TechinAsia_Laravel_API is back up in 76ef86a after 9 minutes.


text:
APT whitelist request for cython

This replaces travis-ci/travis-ci#4226.
The original text by @safl follows

Ran tests and found setuid bits by purely textual search. Further analysis is required.
If these are found to be benign, add:
cython cython-dbg cython3 cython3-dbg cython-doc
See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72545432.

Adding another request for cython cython-dbg cython3 cython3-dbg cython-doc to be white listed for ubuntu-trusty (they are already white listed for ubuntu-precise).
It would be useful for the continuous integration testing of envytools, a piece of the tooling for the nouveau open source driver effort for nvidia GPUs.

repo: travis-ci/apt-package-whitelist


text:
Pull request for python3-nose

For travis-ci/travis-ci#4252.
Ran tests and found no setuid bits.
See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72207634

Closing this in favor of #463.


text:
Builds for pull requests should checkout a static commit hash

Fixes https://github.com/travis-ci/travis-ci/issues/5882

This pull request also serves as a demonstration of https://github.com/travis-ci/travis-ci/issues/5882, because the build for 3198884 should have failed, but since I pushed https://github.com/travis-ci/travis-build/pull/698/commits/d9d261a0a66969f85c16cc94115604bc0b1979e9 before it ran, FETCH_HEAD for +refs/pull/698/merge resolved to https://github.com/travis-ci/travis-build/commit/8a413e0cbf40ccb1349a40984fd5504f16530874 (the merge commit for https://github.com/travis-ci/travis-build/pull/698/commits/d9d261a0a66969f85c16cc94115604bc0b1979e9 into master).
The commit hash provided by the GitHub event for the first commit of this pull request is correctly displayed in the Travis build header as https://github.com/travis-ci/travis-build/commit/917aa1a43ed254db4dab955e3c939bae1a17b35f (the merge commit for https://github.com/travis-ci/travis-build/commit/94ba5849c6f11c95135848bd97a43f16240f149a into master), so it should be used instead of letting a dynamic reference to FETCH_HEAD resolve after the build is started.

Closing due to inactivity.

repo: travis-ci/travis-build