[libs/movex] Bug - On slower networks sometimes, when there is an ack mismatch the resyncLocalState() throws an error

What
When there is an "Ack Mismatch", but what happens is that if there is an another action being dispatched in between syncing the new state it seems the following error gets thrown:

Where
File: libs/movex/src/lib/MovexResource.ts:322 calls resyncLocalState()

Expected Behavior

[ ] No error gets thrown
[ ] The state eventually syncs up with no issue irrelevant of the order of the actions being dispatched and of the missmatched ack checksums

Notes
This is how I interpret the error at a glimpse but it might be something different. Need to investigate more.

This is an old issue, and it might have gotten resolved especially when I fixed the onFwd action resync bug


LESS Gem vs. Node Module

Because LESS is originally a Node module as opposed to a Ruby gem, it would be really nice to be able to filter LESS through the Node Module than the Ruby Gem. I'm actually curious as to why you've taken the Gem route.

When that filter was written, Less was Ruby-based. That no longer seems to be the case; in fact, there really seems to be no reference to the Ruby version anymore, except that the All-Ruby 1.x gems are still available.
So I would agree that the filter should use the JS version; The old filter could  be kept around as less-ruby or less1.

Cool, although the more I look into the matter it seems Less has a less-than-perfect command line implementation. Is it even possible to filter through the Node-based lessc?

Actually, it seems like the Less binary is quite a bit better in its Node implementation (although the ANSI escape codes in the error output are a bit annoying). Anyway, I created a webassets filter for the Node implementation of Less. Feel free to adjust and absorb it.


[KM] AI and Blockchain

KM撰寫

完成時間： 7 hr
https://github.com/CAFECA-IO/KnowledgeManagement/blob/master/Blockchain/ai_and_blockchain.md


Cannot select Kernel after selecting an SKU

Testing #13974
This is the error I get when I select an SKU (after its created)
Does not work in stable or pre-release version of Jupyter extension. (even tried Jupyter version 2023.3.*)

Using github.dev

Trying desktop now

Here's the error message when running in desktop
notificationsAlerts.ts:42 Failed to connect to the remote Jupyter Server 'donjayamanne-jupyter-server-...'. Verify the server is running and reachable. (request to https://donjayamanne-jupyter-server-....-8888.preview.app.github.dev/api/kernels?... failed, reason: Hostname/IP does not match certificate's altnames: .....  View Jupyter log for further details.

I then connected to our corpnet VPN and things started working from there.
Is this expected?

Closing as it may have been fixed.


Description of Set property and Set body are mentioning simple language only although simple, constant and jq can be used

Describe the Bug
Description of Set property is mentioning simple language only although simple, constant and jq can be used
Step Extension involved in the bug
set-property
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Create a Camel Route
add a step
add set-property
select set-property
go to details panel
--> descritpion is:
Add or modify a property on the message using en expression in simple language (Apache Camel).
but 3 languages can be used: simple, jq and constant

Screenshots or Videos
No response
Platform
OperateFirst

note also that there is a typo: the message using en expression -->  the message using an expression


Update do_dont.mdx

replaced text: 'local widget state' with 'Ephemeral state' along with the docs link explaining it
In my opinion, Ephemeral state (sometimes called UI state or local state) is more abstract. Besides, official flutter docs has explained it very well with example.

Related Issues
fixes #N/A

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).

[x] I have updated the CHANGELOG.md of the relevant packages.
Changelog files must be edited under the form:
## Unreleased fix/major/minor

- Description of your change. (thanks to @yourGithubId)

[x] If this contains new features or behavior changes,
I have updated the documentation to match those changes.

Good call. Especially the link to the Flutter doc. Thanks!


Failsafe from rollbar-gem. Net::OpenTimeout in /app/vendor/ruby-2.3.0/lib/ruby/2.3.0/net/http.rb:930:in `connect': error in process_payload

View details in Rollbar: https://rollbar.com/trystant/BOW/items/486/
Failsafe from rollbar-gem. Net::OpenTimeout in /app/vendor/ruby-2.3.0/lib/ruby/2.3.0/net/http.rb:930:in `connect': error in process_payload

I believe we can close this.


Fix: Title

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@freeCodeCamp/portuguese-language-editors How does this look?

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Error: Cannot find module '../utils/Utils'

internal/modules/cjs/loader.js:883
throw err;
^
Error: Cannot find module '../utils/Utils'
已经npm install utils了，怎么会报错呢？？

Oh, make sure you started the project on the node side, not the web side

Thank you for the answer， now i run "xvfb-run -s "-ac -screen 0 800x600x24" npm start". however nothing happened ,no process running , no port up, also no errors reported

Oh, there is too little information. Can you describe in detail your installation machine and node environment, operation steps and error messages

i run git clone https://github.com/tnfe/FFCreator.git in /root
edit package.jason add a line "start": "node /root/FFCreator/lib/node/node.js"
then run "xvfb-run -s "-ac -screen 0 800x600x24" npm start"

node /root/FFCreator/lib/node/node.js
It is wrong to execute this entry, please check the document carefully


[Timeline] Migrate TimelineConnector to emotion

[x] I have followed (at least) the PR section of the contributing guide.

One of #24405

reviewing the tests...


Gemfile not evaluated

This buildpack uses predefined gems rather than gems defined in a Gemfile. Jekyll supports the Gemfile as a location to define jekyll-plugins. Would it be possible to run bundle install just like the regular ruby buildpack does?

Would this solve the issue? https://github.com/inket/dokku-buildpack-jekyll3-nginx/pull/5

Brilliant! Just ran it and works like a charm. Not a big deal, but since I have jekyll itself in my Gemfile it installed jekyll twice.

Sweet. Merging it. 👍


Regression/Breakage in release process

Latest release https://github.com/contiv/netplugin/releases/tag/1.0.0-beta.3-03-08-2017.18-51-20.UTC includes PRs (e.g. https://github.com/contiv/netplugin/pull/774) that have not gone through release sanity.

I'll work to fix this. We need to investigate to figure out when was the last release made which wasn't affected by this issue.

I've looked into this. It seems we need to make some more changes to the release process. It's also likely that the different CI jobs which are part of the preview release can also experience a race condition.


runtime/trace: Bad HeapGoal/NextGC Metric

What version of Go are you using (go version)?

$ go version go1.21.3 darwin/arm64

Does this issue reproduce with the latest release?
Yes, including tip.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE='auto'
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/USER/Library/Caches/go-build'
GOENV='/Users/USER/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS='-count=1'
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/USER/go/pkg/mod'
GONOPROXY='github.com/Org'
GONOSUMDB='github.com/Org,go.orgbuild.io'
GOOS='darwin'
GOPATH='/Users/USER/go'
GOPRIVATE='github.com/Org'
GOPROXY='binaries.orgbuild.io,proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.21.3/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.21.3/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.3'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='c++'
CGO_ENABLED='1'
GOMOD=''
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/0t/nwrdnfnd2mjdgr0z_p_f6xww0000gq/T/go-build3503366670=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?
Capture a trace of running the encoding/json tests and then viewing it in go tool trace:
$ go test -trace json.trace encoding/json

(I did this while implementing heap metrics for CL 538515. At first I thought it's a bug in my code, but then I realized the problem exists in the old tracer as well 😅.)
What did you expect to see?
A reasonable NextGC metric value.
What did you see instead?
An unreasonable NextGC metric value. Maybe caused by a uint64 underflow?
As far as I can tell, the problem appears to be in the data, not the trace viewer.
$ go tool trace -d ./json.trace | grep HeapGoal
2023/11/01 09:10:58 Parsing trace...
2704 HeapGoal p=0 g=1 off=142 mem=4194304
3983536 HeapGoal p=3 g=36 off=133427 mem=5988680
7451664 HeapGoal p=0 g=35 off=4877 mem=10640088
12998705 HeapGoal p=8 g=19 off=144611 mem=18734952
22220882 HeapGoal p=5 g=19 off=141308 mem=32462632
41322629 HeapGoal p=2 g=36 off=117962 mem=49052584
73809753 HeapGoal p=1 g=36 off=95052 mem=38877592
100867596 HeapGoal p=0 g=34 off=49758 mem=17658824
103327101 HeapGoal p=1 g=80 off=95363 mem=49754376
106035005 HeapGoal p=1 g=34 off=95542 mem=55731352
112637966 HeapGoal p=1 g=34 off=95774 mem=67923528
122922303 HeapGoal p=0 g=50 off=57951 mem=91832744
127586144 HeapGoal p=1 g=146 off=97325 mem=8946670875736242639
128176272 HeapGoal p=1 g=146 off=97379 mem=91832744
135046177 HeapGoal p=6 g=15 off=143059 mem=19712536
144138898 HeapGoal p=7 g=14 off=144046 mem=35340824
165010277 HeapGoal p=1 g=14 off=104248 mem=53870584
185668071 HeapGoal p=0 g=121 off=80009 mem=8946670875735194404
186297063 HeapGoal p=0 g=121 off=80048 mem=53870584
199934729 HeapGoal p=4 g=34 off=138916 mem=33694248
214716523 HeapGoal p=1 g=50 off=115986 mem=50463048
233048733 HeapGoal p=3 g=18 off=136782 mem=22212712
250342656 HeapGoal p=3 g=19 off=136882 mem=34606152
260790321 HeapGoal p=2 g=35 off=132457 mem=35196680
265980994 HeapGoal p=2 g=14 off=132538 mem=62106312

cc @mknyszek @prattmic

Ugh. I think this might not be a bug, just an artifact of what happens when SetGCPercent(-1) is called. It sets the GC percent goal to defaultHeapMinimum*uint64(-1)/100. The heap goal calculation may then subtract some relatively small number from this, hence why it waffles a little.
I've always disliked this logic. Perhaps it's time to finally fix it.
This also made me realize we definitely do not emit enough HeapGoal events. We only emit one at the start of the trace and when SetGCPercent or SetMemoryLimit is called, AFAICT. We should be emitting one at least once per GC cycle.

Actually, how should we represent setting GOGC=off in the trace viewer? Just picking a high number doesn't seem quite right because they both make the graph look weird. I guess ideally the graph would just not have any data in that region, so maybe that means it should be zero?

Ah, I didn't realize the encoding/json tests are calling SetGCPercent(-1).
I think zero is a good value for the reason you mentioned. And it also works out nicely with the current cmd/trace code. So +1 to zero.


Get VideoSource from VlcControl

Does this new/re-write have a way to get the VideoSource like the old project? I use the below in the old project.
VlcControl _vlcControl = new VlcControl();
ImageSource imgSrc = _vlcControl.VideoSource;
Thanks.

VLC.DotNet is using HWND to display media, so you can't get VideoSource.
But if you using WPF, you can see my project xZune.Vlc.

There is no way to get the VideoSource, since the video is rendered directly. I'm closing this since this is an old issue, feel free to open a new issue if you have any other question


[sw,plic irq test] Enable the autogen'ed PLIC IRQ test on Verilator and FPGA

This test is auto-generated by topgen. It resides here: sw/device/tests/autogen/plic_all_irqs_test.c. It is already enabled and passing in DV. Since it touches (almost) all blocks, it will serve as a pretty good smoke test to run in CI.
I tried running it locally but it unfortunately fails on Verilator.
IE00000 plic_all_irqs_test.c:154] CHECK-fail: Interrupt from incorrect peripheral: exp = 16, obs = 1
I00001 test_status.c:34] FAIL!

This basically means on the the Verilator build, some IP is generating a spurious interrupt that the test does not expect.
Hoping someone with spare cycles can debug this and get it working on Verilator.
$ cd $REPO_TOP
$ fusesoc --cores-root . run --flag=fileset_top --target=sim --setup --build lowrisc:dv:chip_verilator_sim
$ ./meson_init.sh
$ ninja -C build-out/ all
$ ./build/lowrisc_dv_chip_verilator_sim_0.1/sim-verilator/Vchip_sim_tb -meminit=rom,build-bin/sw/device/boot_rom/boot_rom_sim_verilator.scr.39.vmem --meminit=otp,build-bin/sw/device/otp_img/otp_img_sim_verilator.vmem --meminit=flash,build-bin/sw/device/tests/plic_all_irqs_test_sim_verilator

The DV setup circumvents the use of on-device resources for logging, which the Verilator and FPGA setups cannot. The latter use UART0 for logging. Consequently, if the PLIC all IRQs test enables UART0 interrupts, the logging mechanism ends up triggering an interrupt (TX empty, for example, when UART0 is done transferring all characters in a log) inadvertently, when the test is expecting an interrupt from some other peripheral.
The solution here is to enable UART0 to test the interrupts only for DV and skip for the other platforms. This test is now passing.
Fixed in #10183.

sounds great!


Delete manager.py

Many thanks for the PR - unfortunately it introduces some test failures. Assuming this was not made in error, perhaps you could add a note to explain what the PR is attempting to achieve?

Closing this as it is likely made in error and no new information is provided.


Can't show operations logs in Deployment page when clicking on View

This issue was duplicated with #123 (123-past-deployment-text-logs)

Closed because duplicated with #123


Add tcp client processor/source

TCP client apps can now be used both as a processor (where request can be sent to TCP server and receive continuous messages from it) and as a source where the client receives messages from TCP server
Add tests

This resolves #47
This resolves #180

Addressed review comments.

squashed, rebased, merged as c34d845730d7ea8ac699169c479554e4edd67c69


feat: add-edit-mileage changes for commute-details

Description
copilot:summary
copilot:poem
Walkthrough
copilot:walkthrough
Clickup
app.clickup.com
Code Coverage
Please add code coverage here
UI Preview
Please add screenshots for UI changes

Subsequent PR - https://github.com/fylein/fyle-mobile-app/pull/2820
https://github.com/fylein/fyle-mobile-app/pull/2823


add options as a variable to be set

to be able to pass in OPTIONS as a variable and not just as part of the query string

This has conflicts and no test case. Can you fix those please?


Update hosted docs

https://snus-kin.github.io/twitter.nim/twitter.html was Generated: 2020-07-25 15:37:44 UTC , since the library was updated the documentation is outdated.
It would be really cool if you could regenerate it. :]

Hi, yeah you should be able to do it manually locally but I broke the pipeline that does it for me somehow :~) I'm not sure how well the docs work right now either

Yea, I can generate them manually but I think it would be better to just update the hosted ones.
Here's a GitHub action I use for it if you want to check it https://github.com/Patitotective/niprefs/actions/workflows/docs.yml.


Generate Lexicon Docs

Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for new/updated/fixed functionality.
[ ] I have updated/added dartdoc comments with ///.

Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Related Issues

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (4777497) 83.13% compared to head (a6cb4c9) 86.41%.
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1101      +/-   ##
==========================================
+ Coverage   83.13%   86.41%   +3.28%
==========================================
  Files         360        3     -357
  Lines        4282       81    -4201
==========================================
- Hits         3560       70    -3490
+ Misses        722       11     -711

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


ci: Ensure devcontainer is pushing correctly

I'm seeing an error around true at https://github.com/PRQL/prql/actions/runs/6525681773

I fear this may be over complicating things. Could you please explain your intent?

I fear this may be over complicating things. Could you please explain your intent?

Yes for sure.
The main issue is that we haven't had a devcontainer be pushed since August. Hence https://github.com/PRQL/prql/issues/3671.
GHA has some very awkward and (to me) complicated rules around when values are typed as bools vs strings, so this tries to:

Clean those up
Encapsulate the logic a bit more, similar to some of the other jobs in tests.yaml

I kinda agree it's over complicated, though...

There are lots of commits here, because the only way of testing is by pushing! So I did at least confirm that it passes true through to the docker action when it should ...
Unless you disagree, I'd be up for merging and ensuring this works (i.e. does it actually push the image next time that it should), even if we later simplify it.

This does seem to work: https://github.com/PRQL/prql/actions/runs/6527982444/job/17723556755#step:8:8


Change default dashboard message when the user haven't any interaction

Refers to scenario 1) of https://github.com/CoderDojo/community-platform/issues/1243

List of PRs to be reviewed :
Frontend:

https://github.com/CoderDojo/cp-zen-frontend/pull/249
Backend:
https://github.com/CoderDojo/users-service/pull/3
https://github.com/CoderDojo/clubs-service/pull/5
Middleware:
https://github.com/CoderDojo/cp-zen-platform/pull/1354


fix: refactored the hardcoded data of casestudy section

Description

This Pr removes the hardcoded data where the data type was of an array.
added some test data in yml file

Related issue(s)

PR fixes #1505

@sambhavgupta0705 All good from my side. @derberg your review needed.

ready for review

/rtm


Feature suggestion - Add partial options overwrite with default values

Hi there,
I would like to know if it would be possible to add a way to specify default PdfOptions but still let the calling site specify some options that should overwrite preset options and complement the ones that were not defined in the defaultOptions?
For example, if someone would define the default conversion options to have a specific format, etc.... which should be applied by default everytime, but then for one specific conversion would need to change the format. It would be nice to be able to pass a partially filled PdfOptions instance which would overwrite the properties it redefines within the default set of options....
I tried using Automapper to do it by mapping object to object, ignoring null members from the source object (which is the new set of options that should overwrite existing ones), but because the PdfOptions properties are not nullable, they get their default values so the mapper overwrites everything from my default set of options...
As of right now, the only way to pass specific options for a conversion is to pass a full PdfOptions object, which is not really optimal as it causes code duplication and if the defaults were to change, then it would require "shotgun surgery" to update every calling site.... What do you think?

I implemented a really dump POC here in which I check if a value was passed within the custom PdfOptions object by checking if they are defined (for nullable properties like string and reference types) or if they have a different value than their default one for non nullable properties.
public static void MergeOptionsWith(this PdfOptions defaultOptions, PdfOptions customOptions)
{
    defaultOptions.HeaderTemplate = !string.IsNullOrEmpty(customOptions.HeaderTemplate) ? customOptions.HeaderTemplate : defaultOptions.HeaderTemplate;
    defaultOptions.Height = customOptions.Height != null ? customOptions.Height : defaultOptions.Height;
    defaultOptions.Width = customOptions.Width != null ? customOptions.Width : defaultOptions.Width;
    defaultOptions.Format = customOptions.Format != null ? customOptions.Format : defaultOptions.Format;
    defaultOptions.PageRanges = !string.IsNullOrEmpty(customOptions.PageRanges) ? customOptions.PageRanges : defaultOptions.PageRanges;
    defaultOptions.Landscape = customOptions.Landscape != default ? customOptions.Landscape : defaultOptions.Landscape;
    defaultOptions.PrintBackground = customOptions.PrintBackground != default ? customOptions.PrintBackground : defaultOptions.PrintBackground;
    defaultOptions.FooterTemplate = !string.IsNullOrEmpty(customOptions.FooterTemplate) ? customOptions.FooterTemplate : defaultOptions.FooterTemplate;
    defaultOptions.PreferCSSPageSize = customOptions.PreferCSSPageSize != default ? customOptions.PreferCSSPageSize : defaultOptions.PreferCSSPageSize;
    defaultOptions.DisplayHeaderFooter = customOptions.DisplayHeaderFooter != default ? customOptions.DisplayHeaderFooter : defaultOptions.DisplayHeaderFooter;
    defaultOptions.Scale = customOptions.Scale != default(double) ? customOptions.Scale : defaultOptions.Scale;
    defaultOptions.MarginOptions = customOptions.MarginOptions != null ? customOptions.MarginOptions : defaultOptions.MarginOptions;
}

In a small wrapper I made a long time ago for WkHtmlToPdf, what I did was that I did use only nullable properties for the options object (doing the proper null-checking where required before using the options). This by default did let me simply overwrite a default set of options by simply mapping between the custom options and the default ones, ignoring null properties), but this might need too much changes for what it's worth. The only thing I don't really like with the above implementation is that if you ever change the PdfOptions object definition, this code will break... so that's why I thought it could be nice if it was part of the library directly so that we can ensure it always maps to the correct properties....
Anyways I'd be glad if you could share your thought on the topic (don't worry if you don't want to implement something similar, I won't complain and I will keep using my custom implementation, hoping the PdfOptions object definition won't be changed silently ahah) :)
Cheers and keep up the good work, this and PuppeteerSharp are really nice projects! (it's just sad that the community decided to work on 2 parallel projects that are essentially the same, especially now that Puppeteer also supports multiple browsers.... and now you have to maintain/choose to focus on only one instead of focusing all the community efforts into a single web automation library!)

Thank you for your feedback and your nice words @os1r1s110 :)
I love your idea. I would like to see this in all our options. I have two thoughts about this:

This is something the user can implement on their side. You can already accomplish this with your function :) So I wouldn't consider it a high priority.
We would get this feature with the with statement in C# 9. So the question would be, should we implement this or should we wait for C# 9?

Oh didn't know about the C# 9 with statement, I guess we can wait for that then :) (and effectively I understand it's not top priority ahah)
That means the options would become Records (so declared with public data class) correct?
I will close the issue as using native C# language features is normally well received compared to hacking an in-house solution :P
Thanks for the hint!


⚠ Bofrost.lu has degraded performance

In 8301cd5, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1671 ms

Resolved: Bofrost.lu performance has improved in c7422fe after 1 hour, 21 minutes.


Add space supporter docs

add brief description
add to roles table

Currently available with a code flag in cc, soon to be available
without a feature flag.
Co-authored-by: Matthew Kocher<EMAIL_ADDRESS>Co-authored-by: Mona Mohebbi<EMAIL_ADDRESS>

Thanks @mkocher @monamohebbi! The EasyCLA bot is complaining, but I can see that you're covered under the corporate CLA so I can merge this.


[DOCFIX] Update Release Notes 2.9.2

What changes are proposed in this pull request?
update release number in acknowledgements
Why are the changes needed?
wrong release number
Does this PR introduce any user facing changes?
na

alluxio-bot, merge this please


Can we still aim for layering react4j on top of GWT-React?

I thought I would apporach you so that I can share our experience with using React from Java so far, and ideally, we all can converge our efforts in creating a one, single React library for Java. (By the way, the "react4j" name is already taken by an (inactive?) effort to introduce FRP to Java... don't know if you are aware of that, but this might cause additional confusion.)
First of all, let me share one concern: while everyone is of course free to put on GitHub their own interpretation of what React under Java should look like, the GWT/J2CL user-base is so small, that having multiple incompatible bindings of JS libraries is probably giving the wrong signals.
While I understand that your bindings are "oppinionated", as opposed to GWT-React being mostly a 1:1 mapping of the JS React API, I don't think it is impossible to layer one on top of the other so that users are able to pick one or the other approach, or even a mixture of the two (like, going with your notion of stateful components, while also using the stateless components of GWT-React).
Here's why we find stateless components useful:
Our code base is split roughly into two types of components:

Stateless, "dumb" components that are capable of rendering e.g. simple collections of objects and are notifying for changes via callbacks supplied in their props
Stateful, smart components which bind the "dumb" components from above to our models. The key thing here is that the stateful components follow the HOC pattern in a fashion similar to React-Redux, where the manual creation of smart components and the manual maintenance of their state is avoided altogether, by having a simplistic "smart" component builder, which is using a DSL to bind the models to properties of the dumb component and is thus building the smart stateful component "on the fly".

Thanks to stateless components being just functions, we don't have your issues of having to annotate lots of methods in the stateless component with @JsIgnore or @JsOverlay. Moreover, mind you, there is no complete escape path from the JSInterop annotations anyway: the Props class and the State class of each custom component have to be marked with the verbose @JsType(isNative = true, namespace = JsPackage.GLOBAL, name = "Object") annotation.
So to summarize, we are overall happy with GWT-React, aside from some small pain points we hope to fix in future (https://github.com/GWTReact/gwt-react/issues/16, https://github.com/GWTReact/gwt-react/issues/9, https://github.com/GWTReact/gwt-react/issues/17). If we can take measures not to divide the potential GWTReact/react4j community, that would be great.

We are just getting started with our use of gwt/react so it is interesting to see how it is being used elsewhere. When we started this journey we planned on riding on top of GWTReact and just adding our enhancements as needed. However we found a few things that we wanted to change.
I should note that in an ideal world there would be one java/gwt adapter for react and would be happy if we could just use it. I guess an ideal world would see it generated from the react source code so that the react team is effectively maintaining it. I also don't see a problem with multiple variants, particularly if they are experimenting with different approaches.
So the things we wanted to change. Almost all of these things required breaking backwards compatibility. The things that we wanted which GWTReact would likely get to in time that broke backwards compatibility:

Elemental2
React 16 (Fragments, componentDidCatch() and Portals being the most interesting, some of which has landed in react4j and some which is still in development in downstream apps)
context
Improve interoperability with the DevTools. (component display name, callback names etc). Although I am not sure how this could be done gracefully without an annotation processor.

Somethings that we wanted to do which may not ever be desired in GWTReact:

Generate all the dom props from typescript type definition file.
Remove of need to enable js exports
migration of lots of "utilities" from javascript to java. The ultimate goal being to give the closure/gwt compiler the ability to optimize them away unless used. Examples include the removal of dom factories and moving them into java, probably removing usage of React.createElement(..) and direct implementation in java.
Rework the way props, state and context is done. Dramatically reduce boilerplate. (This is our next mini project)
etc.

As our library mandates the use an annotation processor we have gone down the path of code generation to solving a lot of our problems and that is how we ended up with the dual component hierarchy with native versus java components.
We also wanted to make it so it was easy for our components to be fast by default. i.e. Our annotation processor caches event handlers so we could use PureComponents for all of our dumb components. Etc etc.
As to other things like your comments on stateless components. We have them - they just have the same syntax as stateful components. The reason roughly being that in java the number of tokens between the two approach was roughly the same whether you represented them as a functional class or a normal class so no need to add multiple syntaxes for the same thing. That is one of the few things that there is a FAQ for at http://realityforge.org/react4j/faq/#where-is-the-equivalent-of-reacts-stateless-function-components
Anyhoo we have a lot of work planned on react4j and am not sure where it will end up. I am reluctant to try and merge or anything like that as I expect the changes we will be doing will result in a lot of churn. I am sure it will settle in time.
I am happy to work together if you see an area where there is something we could work together.
Thoughts?

Sounds like you have an ambitious plan and you need the freedom to experiment, unconstrained by the release cycles and point of views of another library/maintainer. Fair enough.
I will take the freedom to comment on a few technical points:

Elemental2

Are you DOM diffing with React or are you manipulating the native DOM directly? in a 10K React LOC codebase, we have, like, 30 lines of code in total where we need to deal with the native DOM directly (primarily fetching stuff from the native DOM elements on key-press, clipboard copy and a couple of others), where we currently still use the GWT DOM API. Not the end of the world, especially if this is isolated in utility methods. Also, Elemental2 is a moving target still, with the "beta1" tag attached to it (since, like 6+ months in the meantime?). Not exactly giving me a warm fuzzy feeling that we should commit to it right away. With that said, sooner or later it will come: https://github.com/GWTReact/gwt-react/issues/9

React 16 (Fragments, componentDidCatch() and Portals being the most interesting, some of which has landed in react4j and some which is still in development in downstream apps)

Fair enough. But also coming, I think: https://github.com/GWTReact/gwt-react/issues/15

context

I have 0% use of contexts, but my use case is not everybody's use case.
Have you actually tried contributing pull requests to GWTReact? Paul is relatively responsive on these. See here: https://github.com/GWTReact/gwt-react/issues/6

Improve interoperability with the DevTools. (component display name, callback names etc). Although I am not sure how this could be done gracefully without an annotation processor.

I'm a bit lost here. What are you trying to do? Have some meaningful fields when inspecting the ReactElement object from within the Chrome debugger?

Generate all the dom props from typescript type definition file.

Quite ambitious. You need a good TypeScript parser (ideally, the Microsoft one, as TypeScript is also a moving target), that can generate an AST tree and then you can walk the AST and generate your JSInterop annotated Java sources. And if you take the burden to implement all of this, why not walk the extra mile and make it working for all of React, or in fact, for any d.ts file? And then, maybe rather contribute here (https://github.com/ltearno/typescript2java), and once it stabilizes, and you have a good argument, talk to Paul for a change of course regarding how GWTReact is generated/maintained? By the way, the d.ts bindings for React are not maintained by the React team itself.

Remove of need to enable js exports
migration of lots of "utilities" from javascript to java. The ultimate goal being to give the closure/gwt compiler the ability to optimize them away unless used. Examples include the removal of dom factories and moving them into java, probably removing usage of React.createElement(..) and direct implementation in java.

If you - already now - feel the pain of having too many un-minifed JS function calls - fine. But otherwise (a bit Mr Obvious here) with J2CL + webpack/closure minifying/removing dead code on all of the sources combined, JS exports become a non-issue.

As to other things like your comments on stateless components. We have them - they just have the same syntax as stateful components. The reason roughly being that in java the number of tokens between the two approach was roughly the same whether you represented them as a functional class or a normal class so no need to add multiple syntaxes for the same thing. That is one of the few things that there is a FAQ for at http://realityforge.org/react4j/faq/#where-is-the-equivalent-of-reacts-stateless-function-components

I still think this is a bit subjective. For us, for small components, not having the ceremony of inheriting from React.Component, the meaningless constructor, protected ReactElement<?, ?> render(Props props) does count. And also the promise that stateless functions might be lighter-weight and optimized in future React versions.

Re: Elemental2
We use Elemental2 for much the same purpose as you. However none of our new apps use any of the GWT framework at all. Actually that is a lie we have some common libraries that still use EventBus but that will likely be phased out relatively soon. We want to be able to move to j2cl as soon as it is available. IIRC were have a checkstyle rule that warns on gwt framework imports except for a few classes (ExceptionHandler, Entrypoint etc).
Re: context
We though we had no use for them but it seems a lot of the animation libraries make use of them which we want to port across.
Re: DevTools
React has some pretty nice devtools for chrome and soon to be other browser I believe. See the chrome store. Heres a screen shot from the todo app with dev tools open.

The DevTools was one of the draw cards of adopting react.
Re: TypeScript Code Generator
We are not planning to have a typescript interop layer but more to read very specific file and generate a very specific output format. Reading typescript is not the hard problem as such - it is figuring out what we want the output to look like. We still haven't come up with anything we like that is significantly better than what is currently in GWTReact. The best idea we have had is really just a slight improvement ala h1().className('foo').tabIndex(3).children("Hello",span().className('red').children('World')).
If we figure it out I can certainly show you how we did it.
Re: J2CL minifying react
The react js library is a massive way off, being able to be optimized by closure in advanced mode. One of the React core developers is currently tinkering to get it working in whitespace mode with renames disabled so they can replace uglify. I hold out hope that there may be a chance that it could run in advanced mode some day but I would not hold my breath. And you can not get rid of js exports until that happens...
Also: Some of the optimisations I describe are because they are things that the react community has already decided are necessary and implemented as part of jsx compilation in production mode in most apps.
Re: Stateless components
It may not have been obvious from the link above but the code snippets include all the code that is required to implement stateless components using a class syntax. React4j does not require that you implement a constructor ... ever. In fact if you want to implement initialization code you instead override lifecycle method componentDidConstruct. You can see a basic explanation at http://realityforge.org/react4j/compared_to_react/#the-constructor-versus-componentdidconstruct
and an example in TodoEntry class.
if you compare the number of tokens between the Stateless as a Component and Stateless as a Function examples at the above link you will see that there is exactly one token difference (Namely BaseState to indicate the component has no state.) In one of our projects we actually have a StatelessComponent class that you can extend from that would make the two approaches identical in the number of tokens.
When there is a performance difference between SFCs and regular react components we will just update out annotation processor so that our components are exported as SFCs to react (if they can be).
Stylistically you may prefer a function but performance wise and level-of-boilerplate wise there is no benefit to them. And we find that having a single, consistent way to author components makes it easier for people to develop components.
I am not trying to convince you to change but just pointing out that in React4j, some of the problems you see in ES6 and GWTReact do not apply.
Anyhoo I will keep in mind GWTReact and when we figure out where we want to be, if it is compatible with where that project wants to go then I will be happy to collaborate. Right now we are focused on building out what we need for our apps ;)

Re: DevTools
React has some pretty nice devtools for chrome and soon to be other browser I believe. See the chrome store. Heres a screen shot from the todo app with dev tools open.

Cool toy. Thanks or the link.
If you are already committed to Java annotations for other reasons, sure - this can be done with annotations & code generation I guess, at least for component names and for callbacks which you implement as Java methods.
We went for a simpler approach. We just call this:
	public  static native <T> T name(T component, String name) /*-{
		if(typeof component.displayName == "undefined")
			component.displayName = name;

		return component;
	}-*/;

... from our code base for each custom component. For stateful components, there is probably a cleverer way to do this e.g. in a base class constructor or so, so that you don't have to have it in each custom component constructor. And you can automatically supply the Java class name, so that its simple name is extracted etc. etc.

Re: TypeScript Code Generator
We are not planning to have a typescript interop layer but more to read very specific file and generate a very specific output format. Reading typescript is not the hard problem as such - it is figuring out what we want the output to look like. We still haven't come up with anything we like that is significantly better than what is currently in GWTReact. The best idea we have had is really just a slight improvement ala h1().className('foo').tabIndex(3).children("Hello",span().className('red').children('World')).
If we figure it out I can certainly show you how we did it.

I'm still convinced that parsing TypeScript & generating jsinterop Java bindings is a nontrivial task, but I see where you are going. You just want a more beautiful DSL to fill in the gap of JSX missing in Java.
Here perhaps simple Props interfaces with custom annotations and Java annotation processor generating the DSL code from these might save the day.
In the meantime, we went with a much simpler approach - we just use the "double curly braces" trick described here: https://github.com/GWTReact/gwt-react/issues/16
Pros:

Simplicity. No need for code generation
Custom props classes are created in no time. Just a bunch of public properties, that's all.

Cons:

Not as beautiful as a dedicated DSL. But then, beauty is in the eye of the beholder

Re: J2CL minifying react
The react js library is a massive way off, being able to be optimized by closure in advanced mode. One of the React core developers is currently tinkering to get it working in whitespace mode with renames disabled so they can replace uglify. I hold out hope that there may be a chance that it could run in advanced mode some day but I would not hold my breath. And you can not get rid of js exports until that happens...

What you are referring to? This? https://github.com/facebook/react/pull/10236/files (btw, it is not "tinkering" but merged already, and it is not "whitespace", but "simple mode", but that's a detail).
The way I understand it, this is an effort to improve the React library download code size, which will only slightly benefit people still using React via CDN / separate download or us who still compile Java code separately from JS code with GWT.
I think the above is very different form what I had in mind which is funneling your app generated code generated with J2CL + all 3rd party JS libraries' code TOGETHER via webpack/uglify/closure/whatever (which is the main use case and why j2cl is so important isn't it - it does not optimize by itself),  as then -
I was thinking - the closed world assumption kicks in and uglify or closure can minify ALL methods in the app (including the React API, your exported methods from your Java code, etc. etc.; and do some real DCE, etc. etc.) - simply because in an app (unlike a library), there is no API anymore.
Perhaps I'm missing something - correct me if I'm wrong.

The Closure Compiler change for React that just landed in closure compiler repo is https://github.com/google/closure-compiler/pull/2707

There does not seem to be an interest in pursuing this. Closing the issue until there is a practical way forward.


idea

it would be cool if mxnet would feature:

a deep convolutional recursive swarm of hybrid bdi and artificial neural networks;
it would be cool if it would be possible to feed such a thing with elastic fusion for gesture recognition using advanced computer vision algorithms

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


Normalize border style setting

All annotations are using setBorderStyle function to set the border options to canvas context.
This could be helpful for shadowing impl.

@kurkle May we close the milestone 1.2.2?

@kurkle May we close the milestone 1.2.2?

Yes, I always forget to close it when releasing :/


Add support for a custom Display Name in the authenticator app

I use this because my invoices will mention Company X, whereas the product is titled differently.
Alternatively, I think a sane default value would be $details['product'] instead of $details['vendor'], but this way it's configurable.

Damn you're fast, thanks! 👏


Update sbt-scoverage to 2.0.11

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

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

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

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 50.00%. Comparing base (4344935) to head (0c527a2).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #514   +/-   ##
========================================
  Coverage    50.00%   50.00%
========================================
  Files            5        5
  Lines           84       84
========================================
  Hits            42       42
  Misses          42       42

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


support multiple reads libs and alter coords if new STOP codon

self-merging to test in Narrative.  Will not promote past beta.


Remove development dependencies when building release

Due to the way that distributions for Packagist needs to be configured, according to the Laravel Zero docs, all dependencies need to be dev-dependencies.
This presents a problem. We don't want to include the actual development dependencies in the release. My best solution as of now is to simply remove them before building the release version. Sadly, this means we cannot cache the Composer packages for the job anymore.
Fixes https://github.com/hydephp/cli/issues/26. Tested in https://github.com/caendesilva/hyde-standalone-release-experiments/actions/runs/7172386137/job/19529422427.

Ah, so this presents a problem. It commits the changes to the Composer files. We could unstage them, but what if the release needs to change them?

Hard to inspect the binary, but based on the filesize it sure seems like this did something :)


Shortcut & UI Improvements

Hi all,
This pull request includes a series of improvements to the user interface and functionality of the code editor.
Shortcuts:

Added a shortcut for strg+a to quickly select all of the code content.
Also added a shortcut for strg+s to save the changes made to the code. A new reset icon has been added to the interface as well.

Navigation & Style:

A simple modern touch has been added to the navigation and main interface.
Modified the navigation item by adding a dark mode and a transition to improve the overall user experience.

Dark Mode:

The dark mode coloring has been changed to the tw-zinc color to provide a more consistent experience.

Please let me know if you have any questions or suggestions.
Best regards,
René Roscher

Thanks! Can you show some before/after screenshots?

Sure!
Before:

After:

Sure! I have fixed the overflow and some other misstakes

Did you also revert the changes to the colors like I asked?

No, the previous colors don't look as good

I think for now, I'd like to keep the previous colors as I personally find them more appealing. We could try to find a better theme for the editor though that matches the dark more colors better. Thanks for your work.


Add a test to show that the failure is not minimal

This PR encodes the expectation that a solver failure should lead to the minimal diagnostic explaining the failure. For now, this test fails with:
   Expected: `Error
                Can't find all required versions.
Selected: irmin.1.0.0 ppxlib.0.1.0
- irmin-watcher -> (problem)
    No usable implementations:
      irmin-watcher.0.3.0: unavailable
      irmin-watcher.0.1.2: unavailable'

   Received: `Error
                Can't find all required versions.
Selected: irmin.1.0.0 ppxlib.0.1.0
- irmin-watcher -> (problem)
    No usable implementations:
      irmin-watcher.0.3.0: unavailable
      irmin-watcher.0.1.2: unavailable
- ocaml -> ocaml.4.11.0
    ppxlib 0.1.0 requires = 4.11.0
- ocaml-base-compiler -> (problem)
    irmin 1.0.0 requires >= 4.12.0
    Rejected candidates:
      ocaml-base-compiler.4.10.0: unavailable
      ocaml-base-compiler.4.13.0: Requires ocaml = 4.13.0
      ocaml-base-compiler.4.12.0: Requires ocaml = 4.12.0
      ocaml-base-compiler.4.11.0: Incompatible with restriction: >= 4.12.0'

which shows that additional (useless) diagnostics are present in the error message.

In general, there is no one explanation for why a solve failed. This example is rather simple, as there's only one version of the package you want, and it depends on something that doesn't exist at all. I guess you could special-case that. But in general there will be many not-quite-solutions and it's useful to see a bit more context.
The example is also a bit confusing in that it lists e.g. ppxlib 0.1.0 above 0.3.1, which the real system wouldn't do (higher version numbers are normally preferred).
I'm sure there are some things that could be done to improve the diagnostics, though. Highlighting the problem cases more clearly would be good (they tend to get lost amongst the "not the latest version" selections).
Another possibility would be to try to improve the initial diagnostic solution by trying to force each "problem" case to solve in turn. e.g. if we said that ocaml-base-compiler MUST succeed then we would get a better solution (OCaml 4.12 instead of 4.11). We could keep doing that as long at the number of problem cases got smaller.
Finally, after a failed solve it should probably display a message pointing you at a web-page explaining how to debug it.

Hello ! Thank you for your answer. I've simplified and updated the tests so that they pinpoint exactly what I find is the problem.

The example is also a bit confusing in that it lists e.g. ppxlib 0.1.0 above 0.3.1, which the real system wouldn't do (higher version numbers are normally preferred).

Taken into account in the updated example.

This example is rather simple, as there's only one version of the package you want, and it depends on something that doesn't exist at all.

I tried to simplify to what I thought was the "core" of the issue. Because my initial problem happens when solving with >50 dependencies so it would have been hard to reason on it. Now the "depends on something that doesn't exist at all" part is actually quite common in opam-monorepo, as we exclude all packages that doesn't depend on dune.
Do you have ideas of situations where a "best-effort" mechanism (improving the failure to have a maximal set of solved packages)  would be harmful to the diagnostics ?

Do you have ideas of situations where a "best-effort" mechanism (improving the failure to have a maximal set of solved packages) would be harmful to the diagnostics ?

The way I'd expect it to fail would be by selecting an extremely old version of something (though that can happen anyway). The current system is biased towards problems showing recent versions. Choosing what to display as the example problem is always a heuristic and will always be wrong sometimes, but I think it would be worth trying to improve the failure examples that way.
opam uses a different approach I think, where it tries to explain more generally why no solution was possible. But I find that output even harder to understand. The 0install way is to show a concrete example of a problem and then have the user explore it interactively by pinning down particular versions where they think the example shown is wrong.


Introduce dendrogram construction based on union-find

This PR introduced dendrogram construction. Dendrogram is a binary tree on $n$ vertices. We store this tree as a set of parents of size $2n-1$, with the first $n-1$ corresponding to internal nodes, and last $n$ to the original vertices.
This PR also does two additional changes:

Move out WeightedEdge out of the minimum spanning tree header
Update to #767 to allow using serial union-find even when Kokkos is compiled without Serial namespace

I'm checking performance on the HACC problem and the main loop seems slower than I recall. Investigating.

Moved the union-find change into its own PR #780.

The current status is that our union-find structure works OK, but there is some room for improvement. There is an alternative way to do serial union-find, which may be faster. However, I struggle to find the conditions under which it would work. I pushed some union-find benchmark into a branch. So far, it seems like it it can be done twice faster (for that benchmark), but it needs a graph without cycle (e.g., MST). I tried to incorporate some changes into our union-find, but that slowed it down somehow.
In any case, I think this is good enough for now, and I cannot really justify spending more time on it.

I find starting labeling internal nodes with 0 quite confusing in the output and would prefer shifting them by num_vertices.

I think it's better to have internal nodes first because we need to keep the heights arround, and it is nice that the heights can be addressed using the same index as the corresponding internal edge.


Change infraction methods to OOP based api and update output formatting.

This issue is to outline the changes that I'm working on regarding our infraction commands and the internal changes to how we'll be able to request and manipulate infraction data, hopefully in an update that will be more friendly for future maintenance and adjustments.
Infractions will have a proper Infraction class, with data we receive from the site API being converted into instances representing individual infractions. All standard actions we'd do to view, format and edit infraction data will be assisted by attributes and methods of this class.
In order to better organise the required class models for API objects, it'll be organised into its own package directory under bot.api and easily imported from anywhere in the project, rather than the current setup where helper methods are spread across multiple modules and extensions.
The API client will gain methods for retrieving these new objects, such as api_client.get_infraction which will fetch the required data from the api and return the already created model instances for us to use.
The formatting for our infraction search commands will be updated also, hopefully giving us an improvement in information density and general aesthetic appeal over the old layouts. Current in-progress example is:

Anything close by relating to user-facing formatting or general usability improvements will be attempted to be addressed also while touching this section of the bot.

I filed #1241 before noticing this, but that's something this should cover.

@scragly If you haven't thought about this already, a nickname (if it exists) should be included at the top of the embed.

@scragly If you haven't thought about this already, a nickname (if it exists) should be included at the top of the embed.


.mov Upload to Server Not Returning full length of video

Steps to reproduce

Capturing video on component via:
captureTarget: Camera.constants.CaptureTarget.cameraRoll,
captureMode: Camera.constants.CaptureMode.video,

Capturing path from this.camera.capture().then(data)=> {
const file = {
path: data.path,
name: myvideo.mov,
type: video/quicktime
}
...

Uploading file via RNS3 component (react-native-aws3)

Expected behaviour
Pushes full length of video to server.
AWS returns full length of video.
Actual behaviour
Returning a <00:01 video with a single frame.
Environment

Node.js version: nodejs v6.3.0
React Native version: react-native v0.34.1
React Native platform + platform version: iOS 10.0, Android 6.0

react-native-camera
Version: v0.3.9

@rajinwonderland seeing the same exact issue here. did you manage to get to the bottom of this?


Apache not starting using xampp control panel when switched to other php version.

Hi there,
Firstly, I would like to thank you for the solution which you have made. I have been looking a long for something like this.
Unfortunately, Apache is not starting using xampp control panel when switched to other php version which has been added using command 'xphp add "......blah...blah...".
The error message is given below:
2:11:59 AM  [Apache] 	Error: Apache shutdown unexpectedly.
2:11:59 AM  [Apache] 	This may be due to a blocked port, missing dependencies,
2:11:59 AM  [Apache] 	improper privileges, a crash, or a shutdown by another method.
2:11:59 AM  [Apache] 	Press the Logs button to view error logs and check
2:11:59 AM  [Apache] 	the Windows Event Viewer for more clues
2:11:59 AM  [Apache] 	If you need more help, copy and post this
2:11:59 AM  [Apache] 	entire log window on the forums

Do you have enough time to look into the matter or is there any solution that may be helpful for me?
Thanks in advance.
P.S: Apache starts perfectly when I switch back to the original PHP version.

I also would like to inform you that, after installing other PHP versions following your documentation (https://github.com/JackieDo/Xampp-PHP-Switcher#add-other-php-versions-to-your-xampp), I have deleted those unzipped xampp folder.

I have the same problem.  It appears the dependencies are not correct.

To @curiousteam , @erniegenaw :
First, I apologize for the delay in replying and handling the project's issues for quite a while.
Next, I took a close look at the issue you guys posted. I noticed that this error occurs in the following cases:

Built-in (original) version of Xampp PHP is PHP5/PHP7 and we proceed to add PHP8 version
Built-in (original) version of Xampp PHP is PHP8 and we proceed to add PHP5/PHP7 version.

Reason:
This happens because the "xampp-httpd.conf" file structure of Xampp 8.x version is different from 7.x version and earlier. Meanwhile, this file generation mechanism for additional PHP builds of the project is essentially copying from the original file in the installed Xampp App.
Therefore, I have changed the mechanism for generating this file for new additional builds in the project source code (commit fcfb0cf01f492b6a690cfa3d93731324132300a0) and this has solved the problem.
Step-by-step troubleshooting for your Switcher system:

Update your Xampp PHP Switcher according to the instructions here.
Replace the contents of the httpd-xampp-php(x).conf file in the apache\conf\extra\ subdirectory of your XAMPP installation directory with the corresponding file in the src\Templates\xampp-config\ subdirectory of XAMPP PHP Switcher. Remember to replacing the string {{xamppDir}} in the content with the path to your Xampp directory.

Note: (x) in the above filename is the major-version of the faulty PHP version.

Hopefully the new version will improve the user experience for you more.
Cordially greet.

Thanks again for solving the issue.
I have installed my Xampp using "xampp-windows-x64-7.4.12-0-VC15-installer.exe". I have also updated the Xampp PHP Switcher according to your instructions. After troubleshooting the switcher following your step-by-step guide, I was able to successfully switch between various PHP versions of 7 modules (7.3.24, 7.4.12, and 7.4.22). It works fine with these aforesaid PHP versions.
Unfortunately, I got the following result while trying to switch to PHP 5.6.40:

Apache does not restart, it just showing that message repeatedly like the screenshot. But it works when I restart the apache manually using the control panel.
And also got the following error for PHP 8.0.9:

Is it possible to add PHP 8.* versions to my existing Xampp installation with this switcher? I don't wanna reinstall the latest Xampp.
Regards.

To @curiousteam :
My installed Xampp version is 7.3.12. And i added other PHP build from 5.6.40 to 8.0.9. Following is the list of builds that have been added to my PHP repository.

All versions I added work perfectly, but yours doesn't. I'm guessing it's because all of my computers have compatible Visual Studio C++ packages installed.

Use the command xphp info to see the Compiler information for your PHP build version, then you will know which Visual C++ package it needs. (With PHP 5.6.40 is VC++ 2012, and PHP 8.0.9 is VC++ 2019)

Then download the corresponding Microsoft Visual Studio C++ Redistributable package here and install it.
Hope you solve the problem.
Best regards.


Update how-to-open-a-pull-request.md

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ ] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

@RandellDawson Please close this.


jupyter_ydoc 0.3.4 add tests, pip check, maintainers, more automation

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

References:

includes #23
blocks https://github.com/conda-forge/jupyterlab-feedstock/pull/367

Notes:

adds pip check`
updates with more metadata

docs_url

add the grayskull-based bot instpection
adds test suite with coverage (currently 71%)

requires full build with yarn, lerna, tsc, etc.
getting the tests from github

ideally, these would be included in the upstream sdist, but not worth the hassle today

adds the maintainer collective @conda-forge/jupyter_server

I accept on our behalf

Future Work:

should run mypy check
maybe there's a less nuts-and-bolts way to get the JS stuff without downloading a few hundred MB of js tool cruft during test

Yeah, sure we can do that. Let's merge this, so theres >1 maintainer, and we can take care of the branching akido and follow-on PR.


Only render LCanvas when r3f prop is defined and allow to pass page props to r3f prop

This PR makes two changes:

Conditionally render LCanvas component. It will only render if r3f is defined in the page. Resolve #74
Convert r3f prop into a function. This allows to pass pageProps in _app.jsx into the R3F tree and get access to all the props obtained from getStaticProps, getServerSideProps, etc.

Awesome! Thanks


Include dependency overrides in list of dependencies to update

Often time vulnerabilities are found in transitive dependencies, if you list all your project's dependencies (including transitive) in dependencyOverrides and we enable Scala Steward to check for library upgrades to dependencyOverrides then Scala Steward can help automatically keep transitive dependencies up to date.

Switching the import statements from _ to * would only work on sbt 1.6.0 and newer.
Could you revert these changes please.
Other than that I think the change makes sense.  There was a discussion about dependencyOverrides  https://github.com/scala-steward-org/scala-steward/discussions/3041 without any answer...

Switching the import statements from _ to * would only work on sbt 1.6.0 and newer. Could you revert these changes please.
Other than that I think the change makes sense. There was a discussion about dependencyOverrides  scala-steward-org/scala-steward#3041 without any answer...

Reverted those changes in 529d9a6


There is no such thing in just traitlets as Sentinel

…it actually was/is in traitlets.utils.sentinel for a long time being, so the correct curated syntax, taken from line 4 would be (forgive my ignorance, but how 0.2.x releases were being made, so it has slipped through?):
from traitlets.utils.sentinel import Sentinel

I am not sure that we need to do that since Sentinel is imported at the top level in traitlets.
Is there a reason why it would be cleaner to import it from utils?

Maybe this is inconsistent between versions of traitlets (it definitely works for some versions). @mprogram which version of traitlets are you using?

err… Sentinel is not being imported at the top level in traitlets, had you tried to run the line?:

from traitlets import TraitType, TraitError, Undefined, Sentinel
Traceback (most recent call last):
File "", line 1, in
ImportError: cannot import name 'Sentinel'

@mprogram from traitlets import TraitType, TraitError, Undefined, Sentinel appears to work.
Do you know a version of traitlets for which it would not

@SylvainCorlay, with all due respect, shall it be a repeating question, to which I've already posted the answer? To recount, and based on the actual absence of class Sentinel in just traittypes in the relevant part of the traittypes code (so, it could just work), it is the master branch of traitlets, as well as the 4.0.0 through 4.3.2 releases from 11.07.2015 through 23.02.2017 (admittedly, I have not tested all of them), where it has moved, in early 2015, to utils/sentinel.py, at the time when setup.py of traittypes requires traitlets to be >=4.2.2.
It appeared to me as such a simple issue, I'm truly surprised I was not understood from my very first comment. It's truly discouraging, and re-typing the whole comment only cloaks the clarity of original reporting. Am I missing, might be, some possibly hidden backgrounds on reporting issues on Github?…

From a technical standpoint
I have tested that all released versions of traitlets support from traitlets import Sentinel.

There appears to be a regression in the development version of traitlets in that regard.
Traittypes is a dependency to a number of projects (bqplot, ipydatawidgets, ipyvolume), so I was surprised it would be so "obviously" broken, hence the question about the version that you used.
 We are all giving each other a service here. I get that working with software is frustrating and discouraging at times, but I would really like that you remain civil in your interactions with the volunteers maintaining the project.

@SylvainCorlay Thanks for doing the legwork here and actually testing the different versions! So the issue here is that Sentinel is no longer exported on the top-level in the development version of traitlets. We should probably copy out the definition from traitlets then in order to future-proof ourselves.

Sounds good to me!

@SylvainCorlay, my apologies for not testing the released versions of traitlets – it was more difficult for me to do that as I'm struggling to maintain a tiny single system-wide set of the bleeding-edge python packages for my personal project on a weak computer system. That known to me the fact of traittypes being a dependency to a number of major projects must have triggered a reasonable doubt the issue might have been with the development version of traitlets is my faux pas. It happens in written communications one's intentions when read perceived differently, that were with my edits, to "self-contained" which I referred to: I was, indeed, so frustrated with rewriting my explanation, correcting typos, that had to edit it four times. However, I watched my language, and at no time implied anything personally wrong, or behaved in uncivil manner, I'm truly sorry if it might have been perceived uncollaborative.
The reason to write a closing comment after the issue is over, however, is different from a technical point of view:
I think, on more general, if not yet philosophical level, the decision to import … Sentinel at the top level directly from traitlets while it was in .utils.sentinel was conceived prematurely, – as avoidance of the use of 'internal utilities such as class of' in pull's ipython/traitlets#416 was a time bomb since the first release of traitlets in 2015, – as evidenced by a much heated similar discussion about moving pip's version 10 "guts" to pip._internal. Looking forward-retrospectively, I suggest reverting the closing merge, while thanking @vidartf for the pull, and replace it with my suggestion from the first comment (ignoring the rest of the discussion). The reason for it is that possible changes to traitlets.utils.sentinel would not be automatically accounted for in future versions of traittypes, and the move would maintain a good backward compatibility referring to the internal utility of traitlets' class Sentinel in "an internal, non-top level way".


Notifying Ocelli Of Bad Server

I posed on the Eureka 2 list only to be directed here.
I understand that the API is volatile at this point. In my use case, I will be obtaining a Host from the load balancer, invoking a request and if it were to fail, I would like to notify the load balancer and underlying strategy of a failure with the mentioned host so the underlying strategy would be able to determine when and if the host gets used next.
For example:
List<Instance> instances = membershipSource
.forInterest(interest)
.take(1)
.toList().toBlocking()
.toFuture()
.get(1, TimeUnit.SECONDS);
try {
String url = ...//computed from host
jerseyClient.execute(url); //My custom code higher up that has no knowlede of Ocelli
}
catch (ProcessingException e) {
memershipSource.noteFailure(url); // Or tell some Ocelli class
}
If my understanding is right, it looks like Ocelli expects a Callback and handles exception and re-use strategy.  Would there be a way to do this without having to call Ocelli via a Callback. My code is hoping to use Ocelli only as Load Balancer to obtain available Servers (based of a Strategy). Would this be something that can be done?
Thanks.

My code is hoping to use Ocelli only as Load Balancer to obtain available Servers (based of a Strategy). Would this be something that can be done?

Failure detection in ocelli is optional, so you can certainly use Ocelli without a failure detector. However, it is important to give feedback to the load balancer of errors while connecting to clients so that it can detect whether a host is healthy or not.

it looks like Ocelli expects a Callback

The way failure detection is exposed in ocelli is via a stream of errors which is expressed as a Func1<HttpClientHolder<I, O>, Observable<Throwable>> with an implementation like this for RxNetty. It isn't really a callback perse.
Feel free to suggest an alternative if this isn't a good abstraction in your opinion.

I totally understand the need to give feed back to the load balancer of errors so that the underlying strategy can decide whether or not to serve the same server on subsequent calls.  I an using Jersey and jersey syntax requires a URL: client.target(url). The URL could be obtained from Ocelli. However I would prefer not to have Ocelli bleed into the Jersey usage tier, it would not be ideal to have knowledge of the underlying load balancer and have to code with it.
With Jersey it is possible to catch an exception via a Client filter or other mechanism at a framework level and with some scaffolding code have it notify the load balancer of an error with a server it used to execute a request with. With this way, the Load Balancer is not really having to do error detection,  code that used to call a server determines that it could not communicate and lets the load balancer know that it faced an error.
I am expecting a maintainer of a client to be provided a javax.inject.Provider which provides a URL to call via provider.get(). The implementation would delegate to Ocelli to obtain back a URL.
jeseryClient.target(urlProvider.get()).path("/someresource")..get();
In short, what I am asking for is a way to tell Ocelli about a bad server.
In the event of failure, I want to be able to simply say something to the equivalent of ocelliBalancer.noteError(host, port) somewhere in my API. This would not bleed into code higher up where jersey is being used to execute calls but instead handled via Client Filter that is registered once.

Ocelli was designed to be composible at the cost of being a bit too low level of an API and requiring additional code to glue all the components together.  To mitigate this complexity I created the concept of the ExecutorBuilder.  Through the ExecutorBuilder you should be able to construct a load balancer with a failure detector through which you can manually push failures.  With that said, I'm not too happy with the ExecutorBuilder since it current has 4 generic parameters.
Here's an example for how to set this up.  Keep in mind that this example is overly simplified and doesn't deal with any cleanup at host shutdown or handling of all edge cases.
ConcurrentMap<String, PublishSubject<Throwable>> hosts = Maps.newConcurrentMap();

...
builder.withFailureDetector(new Func1<String, Observable<Throwable>>() {
   public Observable<Throwable> call(String host) {
      return hosts.put(host, PublishSubject.create());
   }
});

...

String host = urlProvider.get();
try {
   jeseryClient.target(host).path("/someresource")..get();
}
catch (Exception e) {
   hosts.get(host).onError(e);
}

K the above looks like what I was trying to achieve. I will hook it up with my eureka 2 Client and jersey to see how the API plays out.

I am having some issues trying to integrate this. Some assistance would be appreciated. So it looks like ocelli-eureka2 depends on a EurekaClient. I don't see that as part of eureka-client-2.0.0.rc1. How do I go about setting up a LoadBalancer that I can hold onto for the lifecycle of application. I was doing the following:
ServerResolver resolver = fromEureka(fromDnsName(writeServerDns).withPort(writeInterestPort)).forInterest(forVips(readServerVip));
EurekaInterestClient interestClient =  new EurekaInterestClientBuilder().withServerResolver(resolver)
      .build();

With the above, I was able to obtain an InstanceInfo and thus host/port to build a URL to talk to a server via:
   InstanceInfo info = interestClient.forInterest(forApplications("ServiceA"))
        .filter(new Func1<ChangeNotification<InstanceInfo>, Boolean>() {
          @Override
          public Boolean call(ChangeNotification<InstanceInfo> notification) {
            // filter out all non-data and delete notifications
            return notification.isDataNotification() && notification.getKind() != ChangeNotification.Kind.Delete;
          }
        }).map(new Func1<ChangeNotification<InstanceInfo>, InstanceInfo>() {
          @Override
          public InstanceInfo call(ChangeNotification<InstanceInfo> notification) {
            return notification.getData();
          }
        }).take(1).toBlocking().firstOrDefault(null);

How does one create a Eureka2 Load balancer with the Executor and how does one get a Host to work with similar to the above?
Thanks.

Dead project


Explain how the DB is locked

There is a short FAQ entry about this but it is rather vague
https://duckdb.org/faq#how-can-multiple-processes-write-to-duckdb

Explain why does this limitation exist? Compared to SQLite (which does not have a cache) or Postgres (where you cannot launch multiple Postgres instances on the same database file).

How do your design patterns need to change --> that's a guide
e.g., "double-buffering style" for locking.
Here's how you do this in Python.

This should go under the new Concurrency page.


Review how RS creates self links that are valid for ingress

RS is running behind a reverse proxy (IG).
Cluster ingress routes everything with /rs prefix to IG, the routes in IG then drop the /rs prefix and forward requests on to the RS (except for Consents but this will hopefully change...)
Open Banking response objects contain a Links object which must contain URLs which are valid for ingress, so that the client can take such a URL and build a new request from it that is valid.
Currently, there are 2 approaches for building such links

x-ob-url header

IG sets this header equal to the mtls address with the original path suffix
Accounts API use this approach
Payemnt API funds confirmations use this approach (this is because there is a single controller on the backend so we have no context as to where the request originally came from)

This issue should go away when consents are managed in RS

X-Forwaded-Scheme + X-Forwarded-For + X-Forwarded-Prefix + Controller path mapping

Uses Spring HATEOAS
Payments API use this approach

We should use a single approach consistently across the board.

As part of #1008 this has been cleaned up, all self links use the Spring HATEOAS approach.


Configuration of git and tools (.gitconfig)

Fixes #5

I general I approve, imho there should be also added less windows/microsoft centric examples, but that's a job for someone who uses them (me), so I'll make separate issue for that.


Does this work with mac?

Odd questions, I am new to all of this, but I am attempting to follow instructions, but fail to execute properly.
I follow 1 & 2
Open mac terminal copy/past
3 (git clone https://github.com/VVNoodle/PS5bot)
Which successfully downloads it. I close, then re open terminal.
copy/paste cd /the/project/directory in terminal, but it comes up directory not found?
I don't know if i'm inept or if this doesn't work with Mac?

This does indeed work on Mac. As long as you have node installed, it runs without issue.
The /the/project/directory is just an example. You need to insert the actual directory for where the project was downloaded.
 Thank you so much - I'll take a look once I get home!

I am getting ps5bot is not recognized command

Make sure to run yarn and yarn link to install any dependencies. This also has an impact on path configuration.
You can also preface ps5bot with the word node, to specify that it is a nodejs script.
node ps5bot followed by node ps5bot scrape, after config has been generated.

Is this for digital version or full version of ps5?

Is this for digital version or full version of ps5?

By default, PS Direct and Walmart monitor the physical and Target monitors the Digital, however, you can edit the item links to be whichever version you want.
The files to edit are located in ps5bot/src/utils/ and are named scrape-store-util.ts


Investigate the performance degradation in latest Promscale

As described in the thread on slack

The root cause was discovered - basically benchmark test had rules turned on accidentally which affected ingest performance. So we can close this one.

Ingest performance with heavy recording rules is not affected after #1451 was merged. This was confirmed in the benchmarks discussed in the demo call.


How to use data ?

Hi,
I can recover all data in my city, thanks to your plugin !
But when I have them in my client side (With angular), I can't use them ...
Have you an idea for me ? A point of start ?
Thank you ...

Sorry, but I don't really understand what you mean. If you can query the data successfully, then you should be able to use it via a Angular service or direct http call. It's not a "problem" of this project though.

Concretely, I try to use them with ng-repeat like this :
HTML :

{{event.id}}

JS :
$scope.getFBevent = function() {

$http.get("http://localhost:9311/getEvent", { params:{

                  lat: $scope.latpos,

                  lng: $scope.lngpos

                }

              }).success(function(response) {

                  console.log("Success" + response)
                  $scope.eventfb = response;

              }).error(function(response) {

                  console.log("ERROR" + response);

              });

}

I have successfully recover the long array (like in documentation) in my console log, but in view nothing happen ... I'm sure I've made a mistake, but since yesterday I search (and struggling) to find the solution with my friend, Google.
If you can tell me how can I display the array information in my view, you are my savior !
Thank you !

Sorry, I can't really help you with that.

That's cool, I found solution. :)
But now, I have this error :
"message":"Please specify the lat and lng parameters!","code":1
My server.js :
var lat = req.body.lat;
var lng = req.body.lng;
var accessToken = myaccesstoken;

var es = new EventSearch({
"lat": lat,
"lng": lng,
"accessToken": accessToken
});

And my JS :
    $scope.latpos = "43.5847713";
    $scope.lngpos = "2.2472819";

// GET FACEBOOK EVENT

$scope.getFBevent = function() {

$http.get("http://localhost:9311/getEvent", { params:{

                  lat: $scope.latpos,

                  lng: $scope.lngpos

                }

              }).success(function(response) {

                  console.log("Success" + response)
                  $scope.eventfb = response;

              }).error(function(response) {

                  console.log("ERROR" + response);

              });

  }

Have I miss something ?
Thank you for support.


Text is not laid out according to textContainerInset assigned to TextView

Runestone's TextView has textContainerInset property to configure amount of spacing around text, but the width of the text in the TextView does not match this setting. Setting textContainerInset to UIEdgeInsets.zero causes the text to flow over from trailing edge of the view. Same thing happens with and without line numbers.
To reproduce the issue, configure a TextView with some piece of text in it, so that it spans multiple lines. Enable line wrapping. Configure textContainerInset to zero margins. You should see the text flow over the trailing edge of the TextView.

I'm using an iPhone 13 Pro and the string I used as text was:
"GET /foo?bar=bot HTTP/1.1\r\nHost: yle.fi\r\nAccept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8\r\nIf-None-Match: W/9bffb-ObiqDBe6TUk2tCRTC23kIE9yGHY\r\nCookie: _cb=D2Ymc3iL-h78xwcT;_chartbeat2=.1649775273764.1651322673611.1111100000011111;AMCV_3D717B335952EB220A495D55%40AdobeOrg=1585540135%7CMCMID%7C42221234440619613390653998522601201420%7CMCAAMLH-1651922838%7C6%7CMCAAMB-1651922838%7C6G1ynYcLPuiQxYZrsz_pkqfLG9yMXBpb2zX5dvJdYQJzPXImdj0y%7CMCOPTOUT-1651325238s%7CNONE%7CvVersion%7C4.4.0; _cb_ls=1; areena_ab=aa0%2CsimilarityPopConcepts0;yle_rec=1633807336366133786052; yleconsent=v1|development|personalization|embedded_social_media;yle_selva=16380777628504398330\r\nUser-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 15_4_1 like Mac OS X)AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Mobile/15E148 Safari/604.1\r\nAccept-Language: fi-FI,fi;q=0.9\r\nAccept-Encoding: gzip, deflate, br\r\nConnection: keep-alive\r\n\r\n"

Thanks for reporting this. It should be fixed in #36.


🐛: Main thread is blocked on biosimulation.org/projects

Contact Details
No response
Location
BioSimulations
What happened?
When loading https://biosimulations.org/projects the main thread is blocked.
What made it happen?
Load https://biosimulations.org/projects
While projects are loading, try to click on the nav buttons. The input is not processed indicating that the main thread is blocked.
Version
Production (Deployed on a .org domain)
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is one of the performance issues that we've discussed. This needs to be addressed by pagination and/or moving the calculation of filters to the server.

Yup, I had considered this a slightly different issue since  It might be possible to make the calculation asynchronous in some way. While the loading might still take time, it should be on a separate thread

I see. You're right that the calculation could be moved to a separate thread.

Before working on this,  we should actually profile the page loading. I suspect its more likely caused by waiting for a network request on the main thread than computation.
But if it is computation, this would be the approach:  https://angular.io/guide/web-worker

And a quick example: https://dev.to/ngconf/supercharge-your-angular-application-using-web-workers-5h9b


Develop

DLEP discovery message is sent with TTL 255 and discovery is for local LAN only.
Thus radio need to filter all packets with destination address equals to multi-cast discovery address and not pass it to AIR.
Added functionality for radio to filter out discovery packets based on multi cast discovery address.

Is it safe to assume ALL downstream packets are ETH_IP ?
//get ipv4 addr destination of the packet

std::uint32_t addrV = ((Utils::Ip4Header*) ((Utils::EtherHeader*) v.iov_base + 1))->u32Ipv4dst;

Added check that packet is IPv4 packet. If packet is IPv4, then we check if packet has dlep multicast address.

Hello,
I fixed the bug were talking about, and added the check if the packet is an IP packet.
Your feedback can be helpful for me.
Regards.

Hi,
Your approach makes the assumption that the data in the downstream pkt is Ethernet. At this layer the data is considered opaque. The more correct approach would be filter these at the emulator data entry point.
I suspect EMANE::RawTransport would encounter this problem regardless of the IP.TTL and an ip tables rule would help if using the EMANE::Virtual transport.
Are you using an EMANE Transport or something custom?


Feature/directory structure

Codecov Report

Merging #63 (c08a198) into master (acb7176) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #63   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        23   +11
  Lines           26        36   +10
=========================================
+ Hits            26        36   +10

Impacted Files
Coverage Δ

src/paths.js
100.00% <ø> (ø)

src/rules/base/base.js
100.00% <ø> (ø)

src/rules/errors/errors.js
100.00% <ø> (ø)

src/rules/es6/es6.js
100.00% <ø> (ø)

src/rules/jest/jest.js
100.00% <ø> (ø)

src/rules/practices/practices.js
100.00% <ø> (ø)

src/rules/react/react.js
100.00% <ø> (ø)

src/rules/style/style.js
100.00% <ø> (ø)

src/rules/base/index.js
100.00% <100.00%> (ø)

src/rules/errors/index.js
100.00% <100.00%> (ø)

... and 23 more

Continue to review full report at Codecov.

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

:tada: This PR is included in version 5.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Emit initial update event for tokens with zero balance

A token constructed without a balance is no longer initialized with a balance of zero. This ensures that an update event is emitted if the balance is then updated to be zero.
Fixes #14

Ah, it looks like CI is broken on this repo:

Service alert: Your project references CircleCI 1.0 or it has no configuration. CircleCI 1.0 and projects without configuration files are no longer supported. You must update your project to use CircleCI 2.0 configuration to continue

It looks like CI is working again now (fixed in #17)

The balance instance field is a BN instance, which should always be truthy if it's defined. I'm not sure what the expectations are about the balance parameter, other than that it should be something that BN accepts and that it should be truthy. A non-truthy balance parameter was already being substituted for '0'.
And sure, I'll looking into adding a test as well.

This is superseded by #33 . That approach seemed simpler.


fix: don't crash the derper

Ensures flushing when ClientConn closes. Also, ensures the ClientConn closes when it gets an EOF after reading off the connection.


random but persistent lurching forward at stop lights, stop signs, and when stopped behind a car

Describe the bug
I am using a Comma 3 with Open Pilot on a 2020 Hyundai Sonata using Experimental mode. This issue seems to happen regardless of the situation as long as my car has been brought to a complete stop with Open Pilot engaged. As you can see in the video, my car just continually inches forward even after coming to a complete stop and the car in front of me has not moved at all. It also sometimes will do a rapid pumping of the brakes which makes a really weird sound.
The issue is very clearly happening at 18:27:58 within the route mentioned in this issue
Which car does this affect?
Hyundai Sonota 2020
Provide a route where the issue occurs
e8b1f9ef35c46678|2023-06-23--18-11-12--16
openpilot version
0.9.4
Additional info
No response

Found an existing ticket. Closing


Disable self-linking

User test reports have shown this to be confusing, as once they configure a second cluster, they forget to attach back to the original one.
https://jira.mesosphere.com/browse/DCOS-21047

run linux integration tests


Explicitly link against libc++ on Darwin

I have had complaints from a couple of developers that their builds are
failing on Darwin because clang is defaulting to linking against
libstdc++ on https://github.com/pantsbuild/pants/issues/4975.

PTAL @overvenus

Thanks for the review @overvenus - definitely cleaner :) Done!

PTAL @BusyJay

LGTM


Adding a byte array converter

Useful for applications that uses cryptography, to reduce window size of String polling when work with passwords.

since IMHO it's 135 lines of dead code

I'll close this pull request without applying, since in the opinion of project leader this is only 135 lines of dead code.
Thank you.

I don't think this is dead code, but I don't agree with the implementation.
In my experience coercing bytes that are not text to String and back can lead to all kinds of nonsense and hidden bugs (forget about encoding in one place and you're doomed!). It's very hard when you know what you're doing, imagine how it could confuse users.
One good way to do this is to use Base64 or Base32, so there is no room for encoding problems.
What do you think about changing this PR to use Base64?

Hi @garcia-jj, notice that @Turini didn't mean to say that your whole PR is dead code. It was just a way to say that he believes that most of the users won't use this feature, so it would be as if this was dead code for those users. Probably he haven't used the best words to expose his idea, but that's what can happen when none us is using our mother language :-)
I think that PR's discussions like that are the best place to improve our skills and we should try to learn as much as we can from them instead of just arguing what feature should get in or out.

I've oppened https://github.com/caelum/vraptor4/issues/1043 to track lucas' suggestion. Thank you guys.


Stackedit changes non-breaking spaces to ordinary spaces

There is a distinction between different types of whitespace in the content I edit in Stackedit.

normal space: allow browser to break a line here.
No-breaking space: Prevent browser from breaking line here.

In some documents,  nobreaking space is used for links to titles of other documents, so that their names do not break on two lines.
Current problem with stackedit that it converts all whitespace to spaces. This makes it appear like a lot of changes happened in your edit.
I want to prevent Stackedit from converting whitespace. Non-breaking space must be preserved.
How could I do that or where should I look?

If special characters can be preserved, I would like a special visualization of those. Perhaps functionality/stylesheet to toggle hidden characters. How could I achieve that?

use

This issue remains unresolved, and   is not acceptable, e.g., for Markdown export.

I see that this issue was posted in 2015, and the last comment is from 2017. I'd like to argue that this is quite a serious issue.
As a french user, there is a very important typographic distinction between "normal" spaces and non breaking spaces.
For example, typographic characters like « : », « ; », « » », « ? », « ! » etc. must be preceded by a non breaking space (whereas in english, most of those are not preceded by any space). You can guess that such a character is typed very often.
For this very reason, resolving to type «   » twice or thrice every sentence is hardly a solution.
Would there be a possibility to maybe reconsider this issue?


manifests: trim spaces on template

This can cause issues with later comparing
Please provide a description of this PR:

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
cb44542b7840f0be0911c7734a8be2f64346f8de
link
true
/test gencheck

unit-tests-arm64_istio
450b5365339fd5113c29883cc3aa16d2fceba574
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

retest

/retest


Image inferrer is getting 404s and 403s for a handful of images

In today's reindex, four images went to the image inferrer DLQ:

[ ] L0080109 gets a 404 when it tries to retrieve the image:
ERROR u.a.wellcome.messaging.sqs.SQSStream - Unrecognised failure while: Image request for Some(https://iiif.wellcomecollection.org/image/L0080109.jpg/full/224,224/0/default.jpg) failed with status 404 Not Found
java.lang.RuntimeException: Image request for Some(https://iiif.wellcomecollection.org/image/L0080109.jpg/full/224,224/0/default.jpg) failed with status 404 Not Found

The image is also unavailable on the /works page: https://wellcomecollection.org/works/gjraz9ny

[ ] L0080110 also gets a 404
ERROR u.a.wellcome.messaging.sqs.SQSStream - Unrecognised failure while: Image request for Some(https://iiif.wellcomecollection.org/image/L0080110.jpg/full/224,224/0/default.jpg) failed with status 404 Not Found
java.lang.RuntimeException: Image request for Some(https://iiif.wellcomecollection.org/image/L0080110.jpg/full/224,224/0/default.jpg) failed with status 404 Not Found

See broken image on https://wellcomecollection.org/works/wgfp759n

[ ] L0078598 also gets a 404
ERROR u.a.wellcome.messaging.sqs.SQSStream - Unrecognised failure while: Image request for Some(https://iiif.wellcomecollection.org/image/L0078598.jpg/full/224,224/0/default.jpg) failed with status 404 Not Found
java.lang.RuntimeException: Image request for Some(https://iiif.wellcomecollection.org/image/L0078598.jpg/full/224,224/0/default.jpg) failed with status 404 Not Found

See broken image on https://wellcomecollection.org/works/w5awmw78

[x] b28634810_0001 is a 403 error:
ERROR u.a.wellcome.messaging.sqs.SQSStream - Unrecognised failure while: Image request for Some(https://dlcs.io/iiif-img/wellcome/5/b28634810_0001.jp2/full/!400,400/0/default.jpg) failed with status 403 Forbidden
java.lang.RuntimeException: Image request for Some(https://dlcs.io/iiif-img/wellcome/5/b28634810_0001.jp2/full/!400,400/0/default.jpg) failed with status 403 Forbidden

The image is available; I think this might be a thumbnail issue. https://dlcs.io/iiif-img/wellcome/5/b28634810_0001.jp2/full/2048%2C/0/default.jpg

Donald has fixed b28634810_0001

Donald has fixed b28634810_0001

Slack discussion: https://wellcome.slack.com/archives/CQ720BG02/p1610035431009700?thread_ts=1610034898.007700&cid=CQ720BG02

Slack discussion: https://wellcome.slack.com/archives/CQ720BG02/p1610035431009700?thread_ts=1610034898.007700&cid=CQ720BG02

I found the files, and I realised why they're not kept as JPEGs or available to Loris:

https://console.aws.amazon.com/s3/buckets/wellcomecollection-assets-workingstorage?region=eu-west-1&prefix=miro%2FWellcome_Images_Archive%2FL Images%2FLarge Files%2F

Even if we could make those images available, I suspect the image inferrer might get unhappy.

Actually, the inferrer might be fine – it only loads a small thumbnail. Loris, otoh, might get upset.

I've done a Miro reindex and none of these errors came up; the images on /works are fixed, so closing.

I've done a Miro reindex and none of these errors came up; the images on /works are fixed, so closing.


Android wear support

Need to add some support for android wear

This has been added and fixed, but still very buddy, opening a new issues to address this