Fixed Mocha for CoffeeScript 1.7+ and Travis CI errors

Gruntfile.js and test are not currently compatible with CoffeeScript 1.7+ and they return the following error when executed:
Error: Use CoffeeScript.register() or require the coffee-script/register module to require .coffee.md files.

According to CoffeeScript's change log:
When requiring CoffeeScript files in Node you must now explicitly register the compiler. This can be done with require 'coffee-script/register' or CoffeeScript.register(). Also for configuration such as Mocha's, use coffee-script/register.

These changes fixes the error for when CoffeeScript 1.7+ is installed globally.
Also, https://github.com/hubot-scripts/hubot-example (which uses ~1.6) should probably be removed or edited to reflect the recent changes (Yeoman generator).

Thanks for digging into this. Working through https://github.com/github/hubot/pull/863 and running basically into the same problems.

I'm trying to think through this, and I'm having a hard time if scripts generated this will work with hubot as it is now, or if there needs to be support for newer coffeescript (ie https://github.com/github/hubot/pull/863)

I tried generating a new script, then running grunt test, and got:
$ grunt test
Running "mochaTest:test" (mochaTest) task
Warning: Cannot find module 'coffee-script/register' Use --force to continue.

Aborted due to warnings.

Looks like coffee-script needs to be a dependency (or dev dependency) of the generated script.

I agree. You might have to add the latest CoffeeScript as a dependency (or at least a dev dependency) in the script template. I realised that it doesn't work too well even with CoffeeScript installed globally if it is done via a NVM environment. It works best with a local copy of CoffeeScript in its directory.

Hi, I noticed that generator-hubot generates package.json which references very old coffeescirpt.
How is the progress?
https://github.com/github/generator-hubot/blob/v0.4.0/generators/script/templates/_package.json#L29
My package (hubot-test-helper) user want to use "yield".
https://github.com/mtsmfm/hubot-test-helper/issues/41#issuecomment-275914732

We will be updating all of Hubot to plain JavaScript soon, so this issue should go away. https://github.com/hubotio/evolution/pull/4


Beyond 3DP seconds causes incorrect format output

The following code:
var moment = require('moment')
var parseFormat = require('moment-parseformat')

var dp6 = "2019-05-25T15:30:42.526058+00:00"
var dp5 = "2019-05-25T15:30:42.52605+00:00"

var long6dp = moment(dp6)
var long5dp = moment(dp5)

var fmt6dp = parseFormat(dp6,{preferredOrder: {'/': 'DMY', '.': 'DMY', '-': 'YMD'}})
var fmt5dp = parseFormat(dp5,{preferredOrder: {'/': 'DMY', '.': 'DMY', '-': 'YMD'}})

var fmt6dpMoment = moment(dp6, fmt6dp)
var fmt5dpMoment = moment(dp5, fmt5dp)

console.log( 'long6dp', long6dp.format() )
console.log( 'long5dp', long5dp.format() )
console.log( 'fmt6dp parseFormat', fmt6dp )
console.log( 'fmt5dp parseFormat', fmt5dp )
console.log( 'fmt6dpMoment', fmt6dpMoment.format() )
console.log( 'fmt5dpMoment', fmt5dpMoment.format() )

Produces the following output:
long6dp 2019-05-25T16:30:42+01:00
long5dp 2019-05-25T16:30:42+01:00
fmt6dp parseFormat YYYY-MM-DDTHH:mm:ss.SSSDDDZ
fmt5dp parseFormat YYYY-MM-DDTHH:mm:ss.SSSDDZ
fmt6dpMoment 2019-02-27T15:30:42+00:00
fmt5dpMoment 2019-05-05T16:30:42+01:00

As you can see, anything beyond 3DP on the seconds value results in "D" specifications on the end of the fractional seconds which is clearly incorrect and produces uncertain output from moment.
Reported to me in the following issue:
https://github.com/TotallyInformation/node-red-contrib-moment/issues/24

It's not really within the scope of the project, moment-parseFormat is meant to parse date/time strings entered by humans.
Something like 2019-05-25T15:30:42.52605+00:00 is probably better parsed by using JavaScript’s native Date object
new Date('2019-05-25T15:30:42.52605+00:00')

A point. However, it shouldn't be very hard to fix - my regex skills are not the sharpest but it looks as though it would be possible to change the regex to include any number of fractional seconds. Though I think that >6 would fail in MomentJS.
Also you do already support the same format to 3dp.
The worst thing is that there is no warning so people entering longer strings may suddenly get an incorrect date/time output and may never realise.

I can’t tell from looking at it how complex it would be. Each feature we’d add would need to be supported until the end of time, and I certainly won’t need it myself.
I suggest you or someone else sends a pull request to see how much added complexity would be required to add support for it, then we can make a decision

This is still occurring and becoming more of an issue as more systems support 64bit data and more systems support micro- and nano-second data.
I have a partial work-around in node-red-contrib-uibuilder but it doesn't catch every case:
    // If ISO string w/ seconds >3dp, then process else exit
    if ( inp.match(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}.\d{4,}/) ) {
        inp = inp.replace(/^(\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}\.\d{3})\d*(.*)/, '$1$2')
    }

That is missing some data that has a +nn:nn timezone on the end.

I do agree @TotallyInformation. Node moment does have problems with some data formats (as last updated/last changed) going out from some most  fundamental nodes as e.g. events: state


drawio doesn't exit when clicking on save

Describe the Bug
when i click save on drawio page, the app doesn't return to the page and gets stuck in drawio.
Steps to Reproduce

Go to page
edit
insert/edit drawing
draw something & click on save

Expected Behaviour
when clicking on save, the app should exit Drawio & back to the edit page.
Screenshots or Additional Context

Browser Details
chrome
Exact BookStack Version
v23.08.1
PHP Version
PHP 8.2.9
Hosting Environment
Docker environment:
Image version: lscr.io/linuxserver/bookstack:23.08.1

Have same issue after update from 23.06.1 to 23.08. I also can not edit old drawio drawings. If i click on one in bookstack, nothing occurs... Also have the problem if on a page is an drawio drawing, cannot edit page content.
Error:
app.js?version=v23.08.1:26 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'includes')
at app.js?version=v23.08.1:26:124
at tinymce.min.js?version=v23.08.1:4:151017
at q (tinymce.min.js?version=v23.08.1:4:3324)
at tinymce.min.js?version=v23.08.1:4:150848
at ge (tinymce.min.js?version=v23.08.1:4:4719)
at n (tinymce.min.js?version=v23.08.1:4:150818)
at Yh (tinymce.min.js?version=v23.08.1:4:151045)
at Object.parse (tinymce.min.js?version=v23.08.1:4:213073)
at tinymce.min.js?version=v23.08.1:4:223347
at tinymce.min.js?version=v23.08.1:4:223469
at I.map (tinymce.min.js?version=v23.08.1:4:2258)
at tinymce.min.js?version=v23.08.1:4:222703
at Object.setContent (tinymce.min.js?version=v23.08.1:4:223532)
at tinymce.min.js?version=v23.08.1:4:236914
at tinymce.min.js?version=v23.08.1:4:236930
at Object.map (tinymce.min.js?version=v23.08.1:4:79331)

Thanks @oxismailxo for reporting, and thanks @hieste for the extra detail.
Has been patched in 2c20abc87245160229a48a8813df1c0c077a369e, and v23.08.2 is just being deployed to cover this.


Added Print all possible solutions to N–Queens problem

#hacktoberfest

#hacktoberfest

This question doesn't belong here

Where it should be come
On Wed, Oct 12, 2022, 1:40 PM Dipjul @.***> wrote:

Closed #3
https://github.com/dipjul/Grokking-the-Coding-Interview-Patterns-for-Coding-Questions/pull/3
.
—
Reply to this email directly, view it on GitHub
https://github.com/dipjul/Grokking-the-Coding-Interview-Patterns-for-Coding-Questions/pull/3#event-7569341011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALGQOWSFZX7H6NAASHWUCBDWCZW7JANCNFSM6AAAAAARC45YQA
.
You are receiving this because you authored the thread.Message ID:
<dipjul/Grokking-the-Coding-Interview-Patterns-for-Coding-Questions/pull/3/issue_event/7569341011
@github.com>

Where it should be come
On Wed, Oct 12, 2022, 1:40 PM Dipjul @.***> wrote:

Closed #3
https://github.com/dipjul/Grokking-the-Coding-Interview-Patterns-for-Coding-Questions/pull/3
.
—
Reply to this email directly, view it on GitHub
https://github.com/dipjul/Grokking-the-Coding-Interview-Patterns-for-Coding-Questions/pull/3#event-7569341011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALGQOWSFZX7H6NAASHWUCBDWCZW7JANCNFSM6AAAAAARC45YQA
.
You are receiving this because you authored the thread.Message ID:
<dipjul/Grokking-the-Coding-Interview-Patterns-for-Coding-Questions/pull/3/issue_event/7569341011
@github.com>

Did you see that question on Grokking the coding interview patterns?


Multiply + reduce

Code and tests are written.
Fixed the crash -- turns out you shouldn't dynamic cast f64 to a RankedTensor 🤪 (copy paste bug)

Pull Request Test Coverage Report for Build 922400837

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 80.966%

Totals

Change from base Build 919087501:
0.02%

Covered Lines:
1425

Relevant Lines:
1760

💛  - Coveralls


Add support for subscribing to updates by device MAC

Add options to subscribe for updates using device MAC (device ID)
Subscribing using device ID will help to support devices behind NAT, proxies, or if device IP changes
Implementation is backward compatible and allow subscribing for updates either by MAC or device IP, we can later drop the support for subscribing by IP.
Closes https://github.com/home-assistant-libs/aioshelly/issues/182
Gen1:

CoAP contains the device ID in CoAP option 3332, for this parsing of options was added, logic for parsing options is based on https://github.com/chrysn/aiocoap/blob/master/aiocoap/options.py
For compatibility with older Gen1 devices that only include the last 6 chars of MAC, comparison only compare the last 6 MAC chars

Gen2:

Device ID is sent on every frame as src

Checked on multiple Gen1/Gen2 devices with various firmware versions for Gen1.
Update example.py to test subscribing by MAC, for testing with debug enabled:
python example.py --ip <IP_ADDRESS> -i -deb -m "ABCDEF123456"

All my Shelly Plus Plug US work fine with this change

Thanks @bieniu @bdraco


Fix quad SITL

Instead of adding the same random noise to all axis, add random noise individually to each channel.
Choose lower noise numbers (wild guesses and not based on any data but at least, SITL is not unstable anymore).
Also, use isInfinite and isNan instead of isFinite which only exists
in Java8 (This solves #12).

Thanks - the noise values are realistic, the observed instability in SITL must have a different root cause and has been bothering me for some time. Either delays or minimal damping are not yet quite right in SITL. I planned to do the per-axis noise anyway, so that's great.
@thomasgubler The noise term works great in QGC - if you come to final conclusion please feel free to send a PR, but we need to focus on output, but development bandwidth wise we need to make sure to have clear priorities.

@LorenzMeier The (not yet merged) fix for qgc is correct in my opinion: https://github.com/mavlink/qgroundcontrol/pull/1817#discussion-diff-38394400L2989

Could you test and send a PR?  I don't think we'll merge that QGC PR and rather need to do something fresh against master, which scales noise also for Flightgear.


Kanban Board

Complete Kanban Board
Team Members : 5

Link To the KanBan Board

Hi STUDENT_MENTION
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not include a screenshot of the kanban board.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

Hi @Meltrust ,
Wow, you did it 🎉

Well done!
Congratulations! 🎉
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


What type of update are you requesting?
A new version of an existing package
Current Package Identifier
vlc
Package Version
3.0.21
Please describe the changes you would like to see
https://www.filepuma.com/download/vlc_media_player_64bit_3.0.21-39456/download/

When I checked last the MSI had not been released yet

https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe

https://get.videolan.org/vlc/3.0.21/win64/vlc-3.0.21-win64.exe

That is only the exe. The manifests needs to include the MSI.

If only the EXE is in the manifest, then for people with the MSI installed, I think the package manager will offer the upgrade, then deny with the message that they have the wrong installer type. This isn't a good UX and should be avoided if possible, especially since switching installer types isn't possible for some users, such as corporate users.
One option could be splitting this pacakge by installer type, with VideoLAN.VLC.EXE and VideoLAN.VLC.MSI - then the EXE version could be updated, and the MSI version could linger. But with the current arrangement, I believe that waiting for the MSI installer is preferrable.

This package is a community project - is there any way for extra community members to expedite the build and release of the MSI installer? There's obviously a supply of talented engineers demanding this installer, so where is the bottleneck, and how to embiggen it?

MSI is not ready yet because of bugs:

The msi package is not published yet, mainly because there are a couple of critical regressions that need to be fixed before that step.
As soon as the fixes are out, we will be able to generate and publish the msi (maybe with a new minor version).

https://code.videolan.org/videolan/vlc/-/issues/28677#note_441953

i have the same problem too. for personal reasons i prefer the MSI over the EXE


The role of the prior

Hi! Thank you for your work with the project.
I have a question that does not exactly concern this repository, rather the theory behind it.
I am confused when it comes to the role of the prior in Laplace approximation.
I thought, that the goal is to estimate the posterior $p(w|\mathcal{D})$:
$$
p(w|\mathcal{D}) = \frac{       p(\mathcal{D}|w) p(w)         }{       p(\mathcal{D})      } = \frac{1}{Z} f(w) \approx \mathcal{N}(w|m, S)
$$
,then the Taylor expansion and so on, so that finally we can do the predictions for example by sampling the weights distribution $p(w|\mathcal{D})$.
This is the idea I have right now, however I don't understand where the post hoc prior precision tuning fits here.
Sorry if the question is trivial, I am trying to clear the view on the theory behind Laplace

Hi Artur, that's indeed a good question. Theoretically, there is no clear justification to tun the prior precision post hoc but it has been observed in several papers that this improves performance or is even required to improve performance. A possible justification for it is that we do not end up at a true MAP when optimizing the neural network with SGD for a limited amount of epochs. However, it could also be seen as a type of temperature scaling because changing the prior post hoc can artificially concentrate or widen the posterior predictive.
We discuss this in appendix B 3 in the corresponding paper, where we also discuss the online empirical Bayes method to optimize the prior precision. This requires no post hoc adjustments for the posterior predictive but also does not seem to profit much from a posterior predictive over the MAP as we discuss in Appendix C.


Problem with running ng-cli.  SyntaxError: Unexpected token : in JSON at position 9...

Please provide us with the following information:

Windows 7 OS

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
v6.9.5

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

The log given by the failure.

Normally this include a stack trace and some more information.

Installed ng-cli and it worked. But then I uninstalled ng-cli:
npm -g uninstall @angular/cli
npm cache clean.
After that installed ng-cli one more time:
npm -g install @angular/cli@latest.
But using ng <some_command>  have such error log all the time:
C:\Users\user\AppData\Roaming\npm\node_modules@angular\cli\ember-cli\l
ib\models\project.js:537
throw reason;
^
SyntaxError: Unexpected token : in JSON at position 9
at Object.parse (native)
at Function.Project.closestSync (C:\Users\user\AppData\Roaming\npm
node_modules@angular\cli\ember-cli\lib\models\project.js:505:16)
at Function.Project.projectOrnullProject (C:\Users\user\AppData\Roa
ming\npm\node_modules@angular\cli\ember-cli\lib\models\project.js:532:20)
at module.exports (C:\Users\user\AppData\Roaming\npm\node_modules@
angular\cli\ember-cli\lib\cli\index.js:40:25)
at module.exports (C:\Users\user\AppData\Roaming\npm\node_modules@
angular\cli\lib\cli\index.js:39:10)
at C:\Users\user\AppData\Roaming\npm\node_modules@angular\cli\bin
ng:135:5
at C:\Users\user\AppData\Roaming\npm\node_modules@angular\cli\node
_modules\resolve\lib\async.js:47:14
at process (C:\Users\user\AppData\Roaming\npm\node_modules@angular
\cli\node_modules\resolve\lib\async.js:174:43)
at ondir (C:\Users\user\AppData\Roaming\npm\node_modules@angular\c
li\node_modules\resolve\lib\async.js:189:17)
at load (C:\Users\user\AppData\Roaming\npm\node_modules@angular\cl
i\node_modules\resolve\lib\async.js:70:43)
at onex (C:\Users\user\AppData\Roaming\npm\node_modules@angular\cl
i\node_modules\resolve\lib\async.js:93:31)
at C:\Users\user\AppData\Roaming\npm\node_modules@angular\cli\node
_modules\resolve\lib\async.js:23:47
at FSReqWrap.oncomplete (fs.js:123:15)
For trying to solve that issue took next steps:

Uninstalled ng-cli by:
npm -g uninstall @angular/cli
npm cache clean

2.deleted all the
node_modules,
package.json
in
C:\Users\Administrator\AppData\Roaming
included folders npm and npm-cache.

Then I uninstalled the nodejs

restarted pc

installed nodejs again

installed ng-cli:  npm -g install @angular/cli@latest

7 but then using ng new myNewApp have the error again
don't know what there may be a problem.
Mention any other details that might be useful.
Have such log after ng-cli installing:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules@a
ngular\cli\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)

Thanks! We'll be in touch soon.

Had a similar error with "Unexpected token /" instead of "Unexpected token :"
Solution: Removed my (silly beginner!) comment (/* */) from package.json :-)

I am having the same error with the same stack trace.....I find it hard to figure out what the error really is

Me too.

Giovanni it is most likely because you upgraded urban global clip and you are using an older version on the current project, I fixed mine by following the official upgrade guideline for the project angular cli

https://github.com/angular/angular-cli#updating-angular-cli

@Itsdenty I had to reinstall the node and upgrade angular-cli by following these instructions https://github.com/angular/angular-cli#updating-angular-cli Thank you!

Reinstalling node fixed it for me. Ensure to update both global and project versions.


VISUALS (SPEC): Planner Work Board (Drag & Drop Cards)

Verification Requirements:

Refer to previous visual story: VISUALS: Planner Work Board (Drag & Drop Cards), then:

Add specifications to previous visuals work
Post new visual specs to InVision, review with UX team members
Link to InVision prototypes from this story
Tag story as "Ready for Development"

Added Drag & Drop to #136


DBZ-4321 New PostProcessor contract and Column Reselection

https://issues.redhat.com/browse/DBZ-4321
Supersedes https://github.com/debezium/debezium/pull/5065

[x] Implement Db2
[x] Implement Informix
[x] Implement Vitess
[x] Implement Spanner
[x] Add hook in Task for MongoDB
[x] Documentation

Let me explain my thinking with BeanRegistry and ServiceRegistry to provide some context before you review the changes @jpechane :grin:
BeanRegistry
So, this provides a simple object lookup concept based on a key.  I took some inspiration from Camel on this, as there may be future value in finding ways to integrate with CDI frameworks like Quarkus, Spring, etc.  The idea would be that all Debezium components would interact with our BeanRegistry for a universal contract. If a CDI provider were found, a primary registry would be injected into our BeanRegistry, and we would first resolve beans against that provider, falling back to our registry if not found.
This could be useful for Debezium Server users who may want to grab a Quarkus bean in some Debezium component or some Spring bean if using Debezium Embedded Engine in a Spring application.  In fact, it could be utilized with any CDI provider we want to integrate with.
ServiceRegistry (Service Locator)
So this introduces the Service Locator pattern with some simple dependency injection of services into other services. Any class in Debezium can implement the Service contract and define a ServiceProvider to be registered with the registry.
When a Debezium connector requests a service, it will be constructed if it does not exist. This allows for complex, and straightforward construction with dependencies managed, as one service can request another and they'll be created in dependency order.  Additionally, services can also implement lifecycle callbacks to be configured, started, and stopped.  And finally, the registry manages an ordered list of the services so that during the shutdown, they'll be stopped in reverse order to avoid any issues with the dependency chain.
I ended up injecting the BeanRegistry as our first Service and I also added the new PostProcessorRegistry as the second service, showing the provider pattern and how that can likely help us subdivide our classes and code into more modular components.
I'll be interested in your thoughts.

@roldanbob, just an FYI that a whole new section is coming in the documentation called "Post Processors".  You can align these with transformations from a Kafka sense. Still, these operate within the Debezium runtime rather than as part of Kafka Connect, and allow access to more Debezium internals.  These are all incubating new features, but I wanted to give you a heads-up in case you had any questions.

@jpechane I looked at Vitess and Spanner and overall I believe there the ReselectColumnsPostProcessor may not be applicable because they're basing their data stream with the source more like PostgreSQL's replication rather than the more traditional JDBC connection like what we have in our other relational connectors.
What I did do; however, was at least introduce the changes to spin up the BeanRegistry and the ServiceRegistry.

@Naros And it is done, thanks! There is just a test failure in Informix PR. When addressed please feel free to merge yourself.

Applied to main (=2.5).

/packit test --labels oracle


Problem with Krita icon

Krita logo have some artifacts in the header.

I generated the header in my machine and it's ok, also checked the font and it's ok too.

Intersection in the brush:

Extra nodes (bottom left):

And I already pushed to NPM :grimacing:
https://npmfs.com/package/font-logos/
It's also in the font:

I opened the ttf font from the GitHub release and have the artifact

I'm fighting with inkscape right now, am used to work in Glyphs and need to find out how to remove the handle :-D

I pushed to master an update, let's see if that fixes the problem

I can fix that, or do you want to fix that, I always am confused.

I removed the intersection but that didn't resolve the problem, did you find another problematic node? I'll let you fix it

Are the more bugs or is it time for 1.1.1 ;-)

I'm looking at the new logos but still don't find anything odd. If you want to 1.1.1 is ok, (always could be an 1.1.2)

I guess I need to be more thorough...

Tip of the brush stroke in the left of the icon

Found more issues ... prepared the new svg

Ah the reason that local and workflow differ is that different fontforge versions are used.

At least I guess you use (as I do) Fontforge 20230101 ?
In fact I usually use a self-build Fontforge with some patches in.
If you also use a newer version I will change the workflow to use a newer fontforge to prevent unexpected surprises. (Hmm, are there expected surprises? ;-)
Fontforge is two revisions ahead of the default workflow version.
At NerdFont I learned that one always needs to use the latest ff release as there really are bugs fixed.

So, please tell me your libfontforge version? (apt show python3-fontforge)

I use this version that dates from April
paru -Qi fontforge
Name            : fontforge
Version         : 20230101-3
Description     : Outline and bitmap font editor
...
Build Date      : 2023年04月07日 00時26分40秒

Well, there is no newer release than 2023-01-01, but you use that already.
Now the workflow uses that fontforge. All the workflow snippets are taken from Nerd Fonts.


Create event addition form to submit event event objects to database

Might have to update the model at the same time.

I will complete this task.

I added a whiteboard, discussion #9 , for reference

@InstincDev I've created the eventSchema. Would love your thoughts! Issue related for discussion can be found at #12 I've created a branch called Schema as well that includes the information.


use more advanced parsing for argument lists

Currently the argument checker only looks for the first pair of braces "(" and ")", we should do something a little bit more advanced and try to really get the argument list. Note that just looking for the first occurrence of the kernel name is not safe enough either, the name itself could appear in multiple places as a substring of something else, or inside a comment.
So depending on the language it would be best to look for something like "__kernel"  "void"  "kernel_name"  "(" comma-separated argument list ")". Multiline regexes are probably what we need.

Didn't see this until now.

Code committed.


Deleted all the branches!

There were a bunch of branches that our Build Apps tutorial was pointing to.
Why were they removed and please add them back ASAP!!!
https://developers.stellar.org/docs/building-apps/
This repo isn't just a reference implementation, it was first and still is a tutorial resource.
Might be worth splitting it but until we've done that please keep the branches that the tutorial is pointing to.
cc:
@JakeUrban
@Zagan202
@lydiat

Currently restoring now.
Apologies, we can discuss a path forward for maybe splitting the repo
or
Make tags on Master and have the docs point to specific versions (like setup etc.) to keep the "stale branches" to a minimum.

Moving forward we should do one of the following if these branches are important:

Use GitHub's protected branch feature to prevent pushes to the branches or deletes.
Use tags instead of branches since they're harder to delete via the UI.

If it is possible for us to change the name of the branches referenced in the docs it might be worth us prefixing them with a common name like tutorial- so it is a bit clearer what they are too.

Updating the README with this use of branches would be helpful as well. Coming it to this as an outside/new developer, I wouldn't expect to use branches in this way.

Agree with all of the points here. After Meridian let's regroup and come up with our game plan for this repo. I don't think I've ever really used tags but I like the sound of that idea.

We'll keep the branches as-is, sorry for deleting them. Just want to confirm that @Zagan202 and I are free to change master as we see fit, is that alright?

That's correct. Sorry for the confusion and lack of clarity around the other branches. The repo kinda took on a life of it's own after I created it for the tutorial. 😆

Thats the price of creating something valuable!


File Save and File Save As produce error message

POST of 'FeasibleStartPointForSeekTesting' design failed: Bad Request
POST of 'FeasibleStartPointForSeekTesting' design failed: Unexpected end of JSON input
PUT of 'SeekStartPoint1From_in.txt' design failed: Unexpected end of JSON input

Merged into master, closing


Fix for PersistGate hanging on loading screen

These changes should avoid the situation where PersistGate hangs. A race condition can occur when the data finished loading (in LoadManager) before the PersistGate has had a chance to render (and register it's custom callback with LoadManager). This means the callback is never called and the isReady state in PersistGate is never set to true. Should fix both #4 and #9.

Going to redo this PR, removing unnecessary commits.


Not all emojis on GitHub are displayed correctly and duplication of :emoji: depending on their origin.

Continuation of #220. What I wanted was to show an example, but with many more emojis, I show a text in code as shown and as seen on the web.

Is it also possible to define in some way the origin of the emoji code? There are emojis that are different depending on the origin. For example :pencil:
:pencil: (GitHub, Slack, Discord) -> 📝
:pencil: (Emojipedia) -> ✏

Thank you very much for your suggestions. Initially, this library was primarily designed to have an equivalent emoji that could be rendered in the same way across all browsers on any operating system. This was because I encountered the problem that some emojis did not render correctly in some browsers or operating systems.
Now, the same emoji is rendered the same regardless of the platform where it is written.
It is quite complex to standardize all emojis since each platform represents them with one or another; for example, on Slack, the same 📝 emoji is represented as :pencil: but also as :memo:. Therefore, I decided that the same emoji should only correspond to one shortcode to avoid redundancies.
Based on your suggestions, I can think of two things to work on:

As you suggest, enhance the emoji-lib.json file with more fields that allow defining some variations between emojis depending on one platform or another.
Allow the library to be instantiated with a dictionary that can configure some emoji variations we want.

Right now, I don't have an ETA for these changes, but I will keep you updated here when I have it.
Thanks.

I have been looking for a way to obtain all the shortcodes and create a database with all the emoji information in such a way that it is easy to use and can be updated comfortably. I created this script that generated a json:
import { writeFile } from "node:fs/promises";
import fetch from "node-fetch";

// Database emojis: https://github.com/milesj/emojibase

// URLs for JSON data
const dataUrl = "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/data.raw.json";
const messagesUrl = "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/messages.raw.json";

// URLs for JSON data of shortcodes
const shortcodesUrls = {
    cldr: "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/shortcodes/cldr.raw.json",
    emojibase: "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/shortcodes/emojibase.raw.json",
    emojibaseLegacy: "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/shortcodes/emojibase-legacy.raw.json",
    github: "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/shortcodes/github.raw.json",
    slack: "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/shortcodes/iamcal.raw.json",
    discord: "https://raw.githubusercontent.com/milesj/emojibase/master/packages/data/en/shortcodes/joypixels.raw.json",
};

// Function to fetch JSON data from a URL
async function fetchJson(url) {
    try {
        const response = await fetch(url);
        if (!response.ok) {
            throw new Error(`Failed to fetch data: ${response.statusText}`);
        }
        return await response.json();
    } catch (error) {
        console.error(`Error fetching data from ${url}: ${error.message}`);
        return null;
    }
}

// Function to fetch shortcodes from all available JSON sources
async function fetchAllShortcodes() {
    const allShortcodes = {};

    // Iterate over shortcode URLs and fetch data
    for (const key of Object.keys(shortcodesUrls)) {
        const url = shortcodesUrls[key];
        const data = await fetchJson(url);
        if (data) {
            // Add shortcodes to allShortcodes object using hexcode as key
            for (const hexcode of Object.keys(data)) {
                allShortcodes[hexcode] = {
                    ...allShortcodes[hexcode],
                    [key]: data[hexcode],
                };
            }
        }
    }

    return allShortcodes;
}

async function main() {
    try {
        const emojis = await fetchJson(dataUrl);
        const groupsSubgroups = await fetchJson(messagesUrl);
        const allShortcodes = await fetchAllShortcodes();

        // Create maps of groups and subgroups by order
        const groupsMap = new Map(groupsSubgroups.groups.map((group) => [group.order, group.message]));
        const subgroupsMap = new Map(groupsSubgroups.subgroups.map((subgroup) => [subgroup.order, subgroup.message]));

        // Map group and subgroup based on order/message correspondence
        const emojisWithMappedGroups = emojis.map((emoji) => {
            const groupMessage = groupsMap.get(emoji.group);
            const subgroupMessage = subgroupsMap.get(emoji.subgroup);

            // Create an object with new fields group_name and subgroup_name
            const mappedEmoji = {
                ...emoji,
                group_name: groupMessage !== undefined ? groupMessage : undefined,
                subgroup_name: subgroupMessage !== undefined ? subgroupMessage : undefined,
                shortcodes: allShortcodes[emoji.hexcode] || undefined, // Add shortcodes using hexcode as key
            };

            // Check skins
            if (mappedEmoji.skins && mappedEmoji.skins.length > 0) {
                // Add skin_tone_support property
                mappedEmoji.skin_tone_support = true;

                // Map skins to add group_name and subgroup_name if they exist
                mappedEmoji.skins = mappedEmoji.skins.map((skin) => {
                    const skinGroupMessage = groupsMap.get(skin.group);
                    const skinSubgroupMessage = subgroupsMap.get(skin.subgroup);

                    const mappedSkin = {
                        ...skin,
                        group_name: skinGroupMessage !== undefined ? skinGroupMessage : undefined,
                        subgroup_name: skinSubgroupMessage !== undefined ? skinSubgroupMessage : undefined,
                        shortcodes: allShortcodes[skin.hexcode] || undefined, // Add shortcodes using hexcode as key
                    };

                    return mappedSkin;
                });
            } else {
                // If no skins, add skin_tone_support property as false
                mappedEmoji.skin_tone_support = false;
            }

            return mappedEmoji;
        });

        // Save the updated emoji dictionary to a JSON file
        await writeFile("emoji-db.json", JSON.stringify(emojisWithMappedGroups, null, 2), "utf-8");
        console.log("Updated emoji dictionary saved to emoji-db.json");
    } catch (error) {
        console.error("Error processing data:", error);
    }
}

main();

emoji-db.json
I hope this can be helpful in improving this repository.

Thanks for your contribution. Give me some days to review and apply improvements.


doc: Package name: hello_world or hello-world ?

Problem
In https://doc.rust-lang.org/cargo/reference/manifest.html, we have:
name = "hello_world" # the name of the package

The same on master: https://github.com/rust-lang/cargo/blob/master/src/doc/src/reference/manifest.md#L12
But the common package name pattern (on crates.io and rest of the community) is to use hyphen-minus, like hello-world, and not underscore (hello_world).
Possible Solution(s)
Assuming that it's not intentional to use underscore (for some system compatibility reason), I think it's better to rename that like to use hyphen-minus.
What do you think?

But the common package name pattern (on crates.io and rest of the community) is to use hyphen-minus, like hello-world, and not underscore (hello_world).

I don't have pure data, but a casual glance at the front page of https://crates.io/ today actually shows more underscore usage than hyphen-minus (a few crates related to swc_ecma_parser released).
Anyways this changed in https://github.com/rust-lang/cargo/pull/522 and this issue seems duplicate of https://github.com/rust-lang/book/issues/1709.  But also here's a few more hyphen-minus vs underscore issues:

https://github.com/rust-lang/cargo/issues/380
https://github.com/rust-lang/cargo/issues/2775
https://github.com/rust-lang/cargo/issues/3085
https://github.com/rust-lang/cargo/issues/3925

Closing as in ok status quo, as explained in rust-lang/book#1709, with a better future tracked in #2775.


Add Support for Normal in IndexedFaceSet

This is a trial of adding normal support for the indexedFaceSet.
Remainings task:

[x] Normal per face.
[x] Triangle mesh cash.
[x] Doc.
[x] Tests.

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/457/consoleText

test me

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/458/consoleText

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

test me

test me

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

test me

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

test me

test me

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

I have checked with the normals from the universal robot URDF model and it is working as expected. Unfortunately, the result is better with the crease angle than with the normal from the URDF (which are probably not set manually), but at least it proves that the normal in Webots are working as expected.

:+1:

test me

test me

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

:+1:

:eyes:

test me

test me

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

Build Passed :ok_hand:
You can safely merge 'feature-normal-support' into 'develop'.

@omichel I definitely can't reproduce the problem that you have with the test suite that is not failing when expected. I tested, on my Linux environment, Windows environment and on Jenkins.
In all the cases if I remove the normals or I move the shape the test fails, the only minor exception is if I don't move the shape enough (because since it reflects the upper background as long as the camera doesn't see the border of the shape the image remains the same).

The tests are now failing when they should on Windows. Thank you for investigating this.


Wish: rest line show

sorry for my short-english
Wish: Show rest lines
ex:
source code lines: 10 lines
option: data-gist-line="1, 3-5, 7-"
result: show 1, 3-5, 7-10 lines
data-gist-highlight-line option also

Sounds like a great idea. Feel free to contribute a patch and i will be
happy to include it. Directions are on the main page on how to develop a
new modifier. If not, will take a look within the next few days.
On Tue, Feb 25, 2020 at 9:43 PM DeaDCaTsSociety<EMAIL_ADDRESS>wrote:

sorry for my short-english
Wish: Show rest lines
ex:
source code lines: 10 lines
option: data-gist-line="1, 3-5, 7-"
result: show 1, 3-5, 7-10 lines
data-gist-highlight-line option also
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bvanderhoof/gist-embed/issues/2?email_source=notifications&email_token=AAE4C2PZFOMOL34AEKV52N3REX6RXA5CNFSM4K35NKJ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IQKBZPQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE4C2J6ETTN4UMFWN37IOLREX6RXANCNFSM4K35NKJQ
.

I know how to add that feature but  but I can't build develop environment (I totally noob to nodejs. I'm java/C# programmer)
1st try:

VSCode + live server extension
-> tsc build fail
-> add lib[es2016]
-> export not found

2nd try:

VSCode + live server extension
-> corejs install
-> require not found
-> now I know I need node.js server environment

3rd try:

VSCode + nodejs + guide in your README.md
-> test.html is not found

I'm totally frustrated :(

Sorry for the trouble! I’ll take a look at your issues this week and see if
I can improve the documentation. Will also quickly implement the feature.
Thanks for looking into it.
On Wed, Feb 26, 2020 at 10:59 PM DeaDCaTsSociety<EMAIL_ADDRESS>wrote:

I know how to add that feature but but I can't build develop environment
(I totally noob to nodejs. I'm java/C# programmer)
1st try:

VSCode + live server extension
-> tsc build fail
-> add lib[es2016]
-> export not found

2nd try:

VSCode + live server extension
-> corejs install
-> require not found
-> now I know I need node.js server environment

3rd try:

VSCode + nodejs + guide in your README.md
-> test.html is not found

I'm totally frustrated :(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bvanderhoof/gist-embed/issues/2?email_source=notifications&email_token=AAE4C2PWMXB645LW643OON3RE5QGZA5CNFSM4K35NKJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENDGAQQ#issuecomment-591814722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE4C2KAAIBCKKSBOTJ3G73RE5QGZANCNFSM4K35NKJQ
.

thanks for your fasteeest reaction :D

Just added the support, check the example for how to use it (using your suggested syntax). I also updated the readme to make it less confusing when developing (I mistakenly referenced test.html instead of just going to localhost:8080 with no suffix path).


Proposal to add Microsoft.Identity.Web

Closing while we determine the right ship vehicle for the identity.web contents


running multiple Maps on Centos 7 with alternative glibc 2.18

Hey there,
I would like to host several Maps on my Factorio Server (running Centos 7 with alternative gllibc 2.18).
Is this somehow possible with this Init Script?
thx, bye from Austria
Andreas Schnederle-Wagner

this script sadly was not designed to run multiple maps its intended to be a single server automation script. That being said its not "impossible" just some extra work would be involved. You would have to have multiple copies of the script in different folders and then modify the service files to target the different scripts
PIDFile=/opt/factorio/server.pid
Type=forking
TimeoutStartSec=20
ExecStart=/opt/factorio-init/factorio start
TimeoutStopSec=20
ExecStop=/opt/factorio-init/factorio stop
those would be what you would need to change in the service file as well as the name I do believe ( so factorio1.service, factorio2.service etc, etc)
now you can use the same factorio install just make sure you tell it the different paths for the different server configs ( otherwise it will use the same config for all and im confident that's not what you want it to do )
SERVER_SETTINGS=${FACTORIO_PATH}/data/server-settings.json
have that point to say
${FACTORIO_PATH}/configs/server-settings1.json
for the first server and
${FACTORIO_PATH}/configs/server-settings2.json
for the second server and so forth


Determine the performance differences between taxonomy and ssdv faceting

Description
Since January of this year (after bringing hierarchical faceting to SSDV - LUCENE-10250), taxonomy and SSDV faceting have feature parity (as far as I'm aware). I'd like to consider moving to a single implementation to simplify things for our users (deprecating one of the existing ones or moving it to the sandbox). As a next step, it would be good to understand specific pros/cons in terms of performance between these two implementations to help guide our thinking. We can start with the existing nightly benchmark tasks, but may want to consider if any additional tasks would be helpful in eliminating blindspots.

Some of the differences are not performance related, but instead usability. In some of those cases I think we can still improve.
For example, it is a usability improvement for the SSDV-based faceting that there is no sidecar index to deal with (for replication, etc).
On the other hand, there's a warming cost for the OrdinalMap with SSDV that you need to incur on refresh. But we don't have any way to assist the user in doing this efficiently so that it doesn't actually block any search. Maybe something around SearcherManager could help? I'm not sure if we can do anything with IndexReaderWarmer as it works at a lower level and only operates on LeafReader.

Some of the differences are not performance related, but instead usability. In some of those cases I think we can still improve.

+1. Agreed there are some usability differences. The one you called out is an important one; thanks for bringing that up. We've got an issue tracking it over in #11601.
Anyway, I agree that there are considerations beyond just performance to figuring out if/how we can converge on a single implementation. I still think it would be useful to pull together a summary of the performance differences between the two to help guide our thinking.
Thanks for the input!


some advise about rulerz

ruler provide easer way find cursor when you tired
so ruler style must be simple clear no ugly
I think ruler color should like cursor color than text color, and add opacity: 0.5
ruler line should use dashed not solid just like editpus
solid line is more annoying, maybe that is not best but better than now
should have shortcut easy hide or show ruler,  is the best

Let's roll this into #15 - having a discussion about @n3dst4 about this same thing.


Allow access to writer and provider (Part II )

In issue #158 the access to the writers were enhanced. Although initially discussed the third getter
TinylogLoggingProvider.setWriters(final String tag, final Level level) // The same but with a level (all at and above the level)
was  not implemented. It turns out that it might be nice to have it after all. Can we add the third getter?

Fixed by pull request #178


Initial maestro config for Dell5000

This is the initial maestro config for Dell5000, required for turning on Dell 5000 gw.

looks good.


SQL editor toolbar redesign

We have too many SQL buttons on the main toolbar.
Let'\s combine them in a single action with dropdown.
We also could improve behavior of "Open Recent Script" action so it will show script selector when recent script is already open and active.

considering which button appear in the toolbar is already configurable through "customize perspective", what about adding a new button with dropdown, showing only that one by default, but allowing users to choose to reinstate the multiple buttons if they so desire?

The idea is to combine all SQL buttons in a single drop-down.
Perspective customization is great but is for advanced users. We want to make default perspective presentation lighter.

verified

Yeah what I meant is: put this new dropdown in the perspective by default, but leave the old ones in the perspective configuration, invisible by default, to be added if the advanced users prefer them.


HARP-8523: Fix zoom level jitter and tiles flickering.

Inaccuracies on the 13-th fractional digit of zoom level calculation
may be observed when doing small tilt changes, thus causing the zoom level
to be discretized to smaller value then real one, especially when
calculating tiles' storage or visibility level.
This causes displaying wrong tile set (with different zoom level) for
a certain camera arrangement (angles).
The change introduces zoom level rounding above 10-th fractional digit,
giving enough safety margin for inaccurate zoom level from distance
calculus and quite good precision for zoom level based interpolations.
Signed-off-by: Krystian Kostecki<EMAIL_ADDRESS>Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

Codecov Report

Merging #1319 into master will increase coverage by 0.16%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1319      +/-   ##
==========================================
+ Coverage   53.81%   53.97%   +0.16%
==========================================
  Files         253      264      +11
  Lines       23367    23663     +296
  Branches     5225     5279      +54
==========================================
+ Hits        12575    12773     +198
- Misses      10792    10890      +98

Impacted Files
Coverage Δ

@here/harp-mapview/lib/Utils.ts
67.15% <100%> (+0.13%)
:arrow_up:

@here/harp-utils/lib/MathUtils.ts
88% <100%> (+5.14%)
:arrow_up:

@here/harp-mapview/lib/MapView.ts
60.58% <100%> (+0.03%)
:arrow_up:

@here/harp-materials/lib/IconMaterial.ts
44.44% <0%> (-55.56%)
:arrow_down:

@here/harp-map-controls/lib/Utils.ts
46.15% <0%> (-23.85%)
:arrow_down:

@here/harp-omv-datasource/lib/OmvTiler.ts
50% <0%> (-16.67%)
:arrow_down:

@here/harp-utils/lib/ObjectUtils.ts
83.33% <0%> (-10.22%)
:arrow_down:

@here/harp-utils/lib/UrlUtils.ts
84.09% <0%> (-7.81%)
:arrow_down:

@here/harp-datasource-protocol/lib/Extruder.ts
8.33% <0%> (-5.96%)
:arrow_down:

@here/harp-lines/lib/TriangulateLines.ts
11.9% <0%> (-2.99%)
:arrow_down:

... and 31 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 b1e2ec3...a3732d7. Read the comment docs.


Severe performance degradation with long running processes

Hi there
I'm working at a company that is using a nest backend together with neo4j as a data store for business applications. Lately, we've decided to migrate away from drivine because we were facing a lot of race-condition / deadlock problems for a long time and decided to use the neo4j driver directly to mitigate those.
The transition was rather smooth, since all of our database operations were abstracted away behind a base repository class, so it was mainly a matter of replacing all usages of drivine with the Neo4jService provided by this package. Our first tests all seemed very promising and solved all the previous problems we had with using the other library.
But now comes the catch: Locally everything was running fine and even in productive environments. However, after some time (less than one day with production load), the responses we got from neo4j got slower and slower, up to a 10x increase, which made everything unbearable for our end users to use (and basically broke the frontend because of the 30s timeout we enforce). We're now investigating for quite some time already, but cannot find the root cause of the issue. One way to temporarily fix the issue is to restart the backend process, that's why we're now looking into our integration of neo4j.
We have several "suspects", and I hope that one of you can point us into the right direction or maybe you see something suspicious (sorted from most to least likely to be the cause, in my opinion):

We use the node cluster module in production, with at least 4 child processes being forked on startup. I'm pretty sure the driver is instantiated once at startup of the application and then either copied or made available to those child processes in some other fashion. I haven't found something obvious while googling and looking through the issues/code here and in the neo4j-js driver repository.

Since switching we had to implement our own transaction handling. We decided to go the easy route and wrap each request in a transaction (since we write to the database on each request anyway). Since we're using GraphQL on the API layer it can happen that a single HTTP request can result in several of the GraphQL endpoints being called. We start a transaction for each endpoint, hence we have a 1-n relation between HTTP requests and transactions run. Also we're using continuous-local storage (using nest-cls) to keep track which endpoint is wrapped in which transaction and to pass it on to Neo4jService#write calls, even when multiple requests are processed simultaneously.

We make use of as much concurrency as we can when implementing endpoints. This means we often use Promise.all(inputs.map(async () => { ... })) constructs to fetch data from the database (this is what was causing a lot of the problems with drivine previously). Again, I think this is most certainly not an issue since the neo4j driver itself should be able to handle all this, and I haven't seen anything to the contrary, be it here on in the neo4j-js driver.

Does any of the points mentioned above raise any red flag in your opinion? If not I'd probably try to create a reproduceable example repo and will post it here.
Thanks in advance! :-)
Some additional infos:

We use the following versions of related libraries (I know those are old versions, upgrade is on the way):

node: 14.x
nest: `8.x
neo4j-js: 4.x
neo4j: 4.4.14

Hey @vongruenigen,
Queries getting slower and slower indicates a problem with an inefficient query or possibly missing indexes.  How are you running Neo4j?  You could check query.log on the neo4j instance to look for slow-running queries.  You can take those, prepend with EXPLAIN and look for areas that may cause problems.
It's hard to say without seeing the graph though.  I'm happy to have a call in the new year to investigate if you can wait that long - adam at neo4j dot com.  I'd also suggest contacting your sales rep if you are running Enterprise edition.

Thranks for your reply @adam-cowley. The strange thing is that those particular queries haven't changed from one release (where everything was fine) to the next one (where we run into the performance issues).
We did quite a lot of investigation over the weekend and realised that the async local storage (that we use for transaction handling now) might be to blame. We're in the process of deploying the solution to all environments today.
I'll update (and hopefully close) this issue then.

Totally forgot to update this issue: After some investigation, we found out that the issue was not linked to this library, or any external library at all really, but the specific node version we were using, because prior to 14.15.2 there was a performance degradation over time when it came to tracking of promises (see the pull request that fixed).


Cannot Login Newest Release

@tomlandia
I downloaded the newest release and I am stuck on the login screen, the login button grays out when I hit login and sits there.

Gotcha 😨 will fix in 8 hours as I'm at work 😛. Must be a Chrome Webrequest API problem with the new Node-Webkit version.

@tomlandia  Thank You

Fixed in v1.6.1, thanks again for reporting.


Homework 2

Homework 2:
Description of Repository and check of Tasks

Looks like I did not accept the invitation to be a maintainer of this repository, so I cannot approve the pending workflows.
@AxelHallander, can you please approve the two workflows?

@danielhuppmann & @Elisabeth2002S approval done!


require Swipe-to-Dismiss action on Slidable widget

We need to enhance the swipe functionality to require explicit user gestures (e.g., swipe right or swipe up) for confirming actions, reducing unintentional button clicks. Currently, the Slidable widget does not support executing a function upon a complete swipe.
e.g: Robin hood swipe up tp the confirm order

Example EDL:
View:
  header:
    title: "Slidable with Listview"
  body:
    Column:
      children:
        - ListView:
            id: listView
            styles: { expanded: true }
            item-template:
              data: ${[1,2,3,4,5,6,7,8,9]}
              name: num
              template:
                Slidable:
                  styles:
                    direction: horizontal
                    closeOnScroll: false
                    DragStartBehavior: start
                    useTextDirection: true
                  startDrawer:
                    options:
                      extentRatio: 0.001
                      openThreshold: 0.25
                      motion: behind
                      autoClose: true
                    dismissible:
                      dismissThreshold: 0.5
                      onDismissed:
                        showToast:
                          message: "Item deleted"
                  endDrawer:
                    children:
                      - icon: star
                        label: Favorite
                        backgroundColor: yellow
                        onTap:
                          showToast:
                            message: Added to favorites
                  child:
                    Text:
                      styles:
                        width: ${device.width}
                        height: 50
                      text:
                        This is widget to slide ${num}

Working Video
sliadble.webm


Fix docs about build hooks

Maybe contents of hook_post_update and hook_done_update is reversed?
I read followings.
https://github.com/Shougo/dein.vim/blob/ece3f7940d277570b823c18c4c5275988e493301/doc/dein.txt#L1474-L1475
https://github.com/Shougo/dein.vim/blob/ece3f7940d277570b823c18c4c5275988e493301/autoload/dein/install.vim#L1606

Thanks.


Getting a fail scenario when using Ensure that to validate an element visibility

Hi everyone,
I'm using the following template in order to run the tests with serenity+playwright:https://github.com/serenity-js/serenity-js-cucumber-playwright-template/
I would like to use the Ensure.that in order to validate the visiblity of the elements,
This is the element
export const LoginForm= {
    username: () =>
        PageElement.located(By.id('username')])).describedAs('test element'),
}

This is my validation
import { Ensure, equals } from '@serenity-js/assertions';
import { Navigate, Click, Enter, Select, isVisible } from '@serenity-js/web';
import { Answerable, Check, d, Task, Wait } from '@serenity-js/core';

export const Login= {
    using: () =>
        Task.where(`#actor`,
            Ensure.that(LoginForm.username(), isVisible())),
}

After the execution I got this in the report
AssertionError: Expected test element to become present but got undefined
The element is visible in the html document. I tried with isPresent but I got the same error. Any ideas about this?
Thanks in advanced.

Hi @julian-mesa, are you sure, this is your code? Looks like there is some confusion with the closing brackets:.located(By.id('username')]'))

Hi @viper3400 , yes sorry for typo, I changed a little bit the code in order to don't expose information related for the company I'm working on and I messed up, but the code works, the issue is in the Ensure.that line, I'm able to run the code but the test fails in that line. The thing is that if I interact with the element that in this case is a textbox I'm can write  a text using the Enter interaction.
Regards,

Hi @julian-mesa, thought it was a typo ;)
But still, it's hard to tell without seeing the code. So you say, this will work:
Enter.theValue('username').into(LoginForm.username())
Are you sure the page resp. the part of the page was completely loaded, when you access the field? Can you try to put a short Wait.for(Duration.ofSeconds(5)) before you call the isVisible() task?
Can you try an isClickable() instead of the isVisible()?

Hi @viper3400,
I tried putting a Wait.for before the Ensure.that and it worked, but I don't want to wait for a static period of time, is there another way to wait until the element is visible in dynamic way?

@julian-mesa , sure: You can either use Wait.until or Wait.upTo.
Wait.until will wait until the default timeout of your test setup, with Wait.upTo you can specify the desired Duration for the call. Both  Interactions are polling until the element under question, in you case, isVisible(). It would fail, if the element does not become visible within the Duration.

cool! thanks @viper3400 using the Wait.until works as expected but just one more question, the Ensure.that shouldn't expect implicitly for the condition to be meet?

Hi @julian-mesa, not sure if I get your point. Do you mean you've expected Ensure.that to have an implicit wait? Well,  Wait.until is the implicit wait in Serenity/JS, I guess. If you like to Ensure.that(anElement(), isVisible) then it should already be visible.
Normally, I use Wait.until for page elements loaded dynamically. If I assume, that all elements are then loaded (for example fields in a form) I go on with Ensure.that.
You can expect the condition to be met in both cases.

Actually, @jan-molak, I wonder where to configure the default timeout for a playwright project. For webdriverio I would do this in the wdio.conf.ts.
Would it be the expect.timeout in playwright.conf.ts.
(Comments in both of the configuration files are a bit misleading then, I guess)

@viper3400 so the comment in playwright.conf.ts is auto-generated by Playwright Test and related to Playwright's expect function:
https://github.com/serenity-js/serenity-js/blob/dc008deea3df025eff0230546100d89156564a8e/examples/playwright-test-todomvc/playwright.config.ts#L17-L23
I wonder if it's best to remove that comment from the template. Config option and comment are valid, but you're right, they might be confusing.

@julian-mesa

just one more question, the Ensure.that shouldn't expect implicitly for the condition to be meet?

In Serenity/JS 3.0.0-RC.44 I introduced a new assertion to Ensure.eventually(question, expectation).
It evaluates the condition, and if no errors are thrown but the condition is not met, it will evaluate it again with an exponential backoff until the timeout is reached.
The timeout can be configured on a per-assertion basis, e.g.:
await actor.attemptsTo(
  Ensure.eventually(element, isPresent()).timeoutAfter(Duration.ofSeconds(3))
)

or globally via Serenity/JS configuration (#1083):
import { configure } from '@serenity-js/core'

configure({
  interactionTimeout: Duration.ofSeconds(5), // timeout for Wait.until and Ensure.eventually
})

Let me know if this addresses your use case and if we can close this ticket?

@jan-molak thanks. Sure, we can close the issue.


The "Next" button is overlapped by system keyboard on the Sign up screen

Steps to reproduce:

Navigate to the Sign up screen
Pay attention to the "Next" button

Actual result: The "Next" button is overlapped by system keyboard on the Sign up screen
Expected result: The "Next" button is located above and should not overlaps by system keyboard on the Sign up screen
Note: the issue is performed on Dev, QA, and eWallet environments
Device: Xiaomi mi8 // Android 9
The issue happens only on Android devices

@LiavGut we can either always hide the button
or on larger screens we can allow the button to show (compress the space between the input and button).
If you want to show it on larger screens that we need the minimum height of the area you think will look good, meaning button wont be too close to the input. (height - from top of screen to start of keyboard)

@sirpy @Nordwhale @AlexeyKosinski
We can watch if the keyboard is visible, then change the position of the button, shifting it under the input field.
do it in src/components/appNavigation/stackNavigation.js in NextButton

@sirpy Please approve

@Nordwhale @AlexeyKosinski
lets hide the button
use something like https://github.com/bamlab/react-native-hide-with-keyboard
verify the "enter" button on the keyboard initiate press on the hidden button (i think we capture enter event on signup buttons)

@sirpy @Nordwhale @AlexeyKosinski
react-native-hide-with-keyboard does not work on the web platform.
I suggest hiding the button during focus on the input.

ok.
please checkout current implementation that we have for keyboard on ios
(search code for "isMobileSafariKeyboardShown")
try to be DRY/refactor where needed

suggestion:

change space between input and content (button/text) when focus event triggered
try to hide button/text under the keyboard on most of devices
make sure to keep margin from input + error message to button
@LiavGut please approve or/and add your thoughts

Sound good :)
@sirpy ?

Hadar:

on iOS it's not an issue I guess. on Android the screen size is updated when keyboard is open. so probably the simplest solution is to use fixed height with original device height

Checked on Preview
The numeric keyboard overlaps the button on Android

Checked on the Dev environment.
The issue isn't reproduced on Android devices
Checked on:
Samsung Galaxy S6 // Android 8.0
Google pixel 3XL // Android 9.0
As for iOS devises, the issue is reproduced sometimes (it depends from screen sizes), but according to comments above, I don't determine it as a bug.
Checked on:
iPhone 6+ // iOS 12.4
iPhone XS // iOS 13.2


Use /usr/bin/env bash in hashbang

From https://github.com/atom/apm/issues/282#issuecomment-100289741
Refs https://github.com/atom/apm/pull/361

:+1:


Bugfix: Multiselect field saving only one value

Fixed issue where multiselect fields only select last value when creating/editing.

Thanks for the PR 🎉

Happy to help!


Change taint-and-uncordon worker task to use docker for now

rkt has a gnarly bug (coreos/rkt#3181) that won't be fixed in a hurry (coreos/rkt#3486). It least to continuous task failures that eventually totally wreak worker nodes (#224). In the meantime we can use docker just as easily for this simple task. This work around was discussed in #199.
I tested deploying a node-pool or workers with this patch and the experimental.taint setting enabled and the right thing happened. The taint was applied and the node uncordoned. All looks good in the log and CPU load is nominal.

Current coverage is 68.87% (diff: 100%)

Merging #231 into master will not change coverage

@@             master       #231   diff @@
==========================================
  Files             4          4
  Lines          1134       1134
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            781        781
  Misses          263        263
  Partials         90         90

Powered by Codecov. Last update b7587a6...7ff77b9

Shortly after boot pre-patch:
cat /proc/mounts | wc -l
203365

:)

Two hours after boot with patch
cat /proc/mounts | wc -l
152

You win 😏

don't we need similar change on controllers?

The controller has also been patched @redbaron - see #199
I got bitten by that one too 😄

LGTM & E2E passed.
Thanks again for your contribution @whereisaaron!


bevy 0.13 support is not on crates.io

the pull request for bevy 0.13 support was already merged but no crates.io version got pushed

Should be up now!


Added support for metadata.rb

Adding support for metadata.rb in order to be able to upload this to a local supermarket.

:+1: LGTM
Thanks for the patch!


Remove error checks that were causing problems with GovCloud

Description
Removed some checks that were causing havoc with GovCloud. Hopefully the build passes!

Warnings

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

  Generated by :no_entry_sign: dangerJS against 3beb864686fd31b1556f42c65a25ef2f05d8f112


Update libjpeg Conan revision

The non-corp build started failing due signature mismatch when
downloading the libjpeg library archive. Updating to the latest
revision found on https://conan.io/center/libjpeg fixes the issue.
Also, the pcre2 10.33 package was referencing a server that no longer
exist, update to 10.40.
b/240705088

Actually, it seems we should not manually edit the lockfile, we should instead modify the conanfile.py files.

I uploaded all the missing packages. It compiles now!

Thanks for uploading the packages! Thinking a bit more about this however I'm not sure changing the lock file manually is the proper fix. I think we should probably change the conanfile.py from which the lock file is generated. Let's chat about it offline. I'll hold back from merging until then.


More efficient generic gate creation for linear combinations

Why
Currently, when doing chains of .add() and .mul(constant), snarky doesn't create any generic gates. Instead, it maintains an arbitrarily long unreduced AST using the Add and Scale combinators.
The AST is reduced to generic gates whenever the variable that holds it is included in a gate.
This can lead to a bad explosion of gates used, because the same unreduced AST can be included multiple times in gates.
Example:
// u = 5x + 10y + 2z
let u = x.mul(5).add(y.mul(10)).add(z.mul(2));
Gadgets.rangeCheck64(u); // causes 1st chain of generic gates from u
let v = u.mul(u); // causes 2nd and 3rd chain of generic gates from u

The example creates 6 generic gates (3 rows) just from doing the same reduction of $5x + 10y + 2z$ (which costs 2 addition gates) three times. On top of that, it creates 1.5 rows for the range check and multiplication. Total cost: 4.5 rows
PLONK can only do 1 addition (with optional multiplying constants) per generic gate: $ax + by$. So, there seems to be zero value in maintaining unreduced ASTs from addition chains with 3 or more variables.
As soon as the third distinct variable is added, it's definitely time to reduce it!
How
In the above example, we would add a generic gate for $5x + 10y$ as soon as doing .add(z.mul(2)). Then, u would be an unreduced AST containing a single addition. The subsequent inclusions in gates would reduce the remaining addition 3 times at a cost of 1 generic gate each. Total cost: 3.5 rows
If we implement #1312 as well, the multiplication would be intelligent enough to only use 1 generic gate for everything, so we're down to: Total cost: 2.5 rows
This is a simple change which seems to have no negative impact in practice.

this is a zkDSL level change that I think we should make wherever our DSL core will live in the future


added operationType attribute to executable object, and added headerv…

added operationType attribute to executable object, and added headerview tab to show this attribute.

Content looks good, though your indentation doesn't match.


Fix typos.

Fix typos in:

engine/userguide/storagedriver/aufs-driver.md
engine/userguide/storagedriver/btrfs-driver.md
engine/userguide/storagedriver/selectadriver.md

Thanks @danix800 ! I jumped in and fixed a few nits because it was faster than going back and forth. Appreciate the PR greatly. :)


Upgrade terriajs & terriajs-cesium to fix gulp tasks in node v14

For the sake of connectedness, this PR completes another step of TerriaJS/terriajs#4617


Swift: Use of unresolved identifier 'Auth'

I cant compile because xcode throws Use of unresolved identifier 'Auth'. I am using

Using Firebase (4.6.0)
Using FirebaseAnalytics (4.0.5)
Using FirebaseAuth (4.3.2)
Using FirebaseCore (4.0.11)
Using FirebaseDatabase (4.1.1)
Using FirebaseInstanceID (2.0.6)
Using FirebaseStorage (2.0.2)
Using GTMSessionFetcher (1.1.12)
Using GoogleToolboxForMac (2.1.3)
Using leveldb-library (1.20)
Using nanopb (0.3.8)

import UIKit
import Firebase

@objc func handleRegister(){
        guard let email = emailTextField.text, let password = passwordTextField.text else  {
            print("Form is not valid")
            return
        }
        Auth.auth().createUser(withEmail: email, password: password) {
            (user, error) in
            if let error = error {
                print(error)
                return
            }
            print("\(user!.email!) created")
        }
    }

I am new to swift.
Please help!!
Thanks.

Make sure you're using the .xcworkspace file and not the .xcodeproj file.
If you change your import to import FirebaseAuth, does the error go away?

Changing the import to import FirebaseAuth made the error go away.
Thanks a lot. 👍


Completely delete a product

Hi,
I'm still new to the application, please is there a simple way to completely delete a product? I mean hard delete.  If not I will have to write the sql query to delete product and linked data

Why you want to do hard delete the product.  Its just in a scenario where I finish testing with products data and want to clean database for production. In that case, I do not want to delete things like product attributes and options but only the products and categories. I can import new products for production in excel files (using https://github.com/SheetJS/js-xlsx)

@selombanybah to clean up the database, you can prefer to the script https://github.com/simplcommerce/SimplCommerce/blob/master/src/Modules/SimplCommerce.Module.SampleData/SampleContent/Fashion/ResetToSampleData.sql and modify it according your need


QIIME 2 plugin 'diversity' has no action 'core-metrics-phylogenetic'

Hello, and apologies in advance for what is probably a very basic question:
I am working through the Moving Pictures Tutorial and I have gotten up to doing the diversity analysis. however when I type in
qiime diversity core-metrics-phylogenetic \
  --i-phylogeny rooted-tree.qza \
  --i-table table.qza \
  --p-sampling-depth 1109 \
  --output-dir core-metrics-results

the output is:
QIIME 2 plugin 'diversity' has no action 'core-metrics-phylogenetic'
However, If I do the same thing but without "phylogenetic" on the end...
qiime diversity core-metrics \
  --i-phylogeny rooted-tree.qza \
  --i-table table.qza \
  --p-sampling-depth 1109 \
  --output-dir core-metrics-results

It works. But what is the reason for the first problem?

Hi @slh277, this is better posted on the QIIME 2 Forum, but to answer briefly: We just released a new version 2017.9 which has both:

core-metrics (no phylogenetic metrics)
core-metrics-phylogeny (formerly core-metrics in older versions).

We recommend installing the latest version!


UI evaluation (scaling, fonts etc.)

UI issues such as iOS shadows, extended navbar buttons overflow, and modal scaling have been already addressed. Closing this issue.


Add Dependabot/Github Actions

Adds various github actions

Adds a build action so you can know on push whether the tests pass
Adds EA build actions so you can catch issues with future JDKs before they go GA
Configures dependabot to auto-update your dependencies
Adds an action to auto merge dependency upgrades from dependabot if tests pass

For that last one, you must enable auto-merge on the repo, and enable branch protection for master using the other actions as status checks.

I added a branch called next for this work, please re-target your pull request.


How to set value for elements marked "Config false"

Hi,
I want to import some data for testing only,  for example:
sysrepocfg --import=mytest.xml --format=xml --datastore=startup myTestModule
As some elements are defined as "config false" in the module file, so the import was failed.
Could you please help me how should I do for this? Thanks in advance.

Hi,
for the import you should be able to use -n (--not-strict) sysrepocfg option.
Regards,
Michal

Great, thanks very much!

Hi,
-n, --not-strict   Flag used to silently ignore unknown data from any supplied data file.
This will ignore the configuration for the elements marked with "config false", but I just want to set the values for these elements.
If I can't imported the data as this, is there any other way I can set the values for these elements?
Thanks.

Hi,
in that case look here.
Regards,
Michal

Thanks, so for supporting that, we should write a new plugin or service base on sysrepo, do netopeer2 also provide similar framework or add source codes in some places to extend the functionalities?

Hi,
if you mean adding some sysrepo plugins directly into netopeer2 then no, this is not supported (and I do not think it even should be).
Regards,
Michal

I mean how to extend the netopeer2 functionalities to support customize the user defined model.
After took a look at the netopeer2 source, it seems we can add some like the following(take ietf-netconf-monitoring as an example):
rc = sr_dp_get_items_subscribe(np2srv.sr_sess.srs, "/ietf-netconf-monitoring:netconf-state", np2srv_state_data_clb, NULL, SR_SUBSCR_CTX_REUSE, &np2srv.sr_subscr);
provide the data in the callback function, right?

Well, yes, you can modify netopeer2-server code as you see fit. My point was that this should not be done, why do you want to add your custom model state data callback directly into netopeer2-server? It has callbacks for ietf-netconf-monitoring and ietf-netconf-server (and one for ietf-system because of ietf-netconf-server), which are NETCONF-specific models.
To support other models you should follow the general sysrepo principles (it actually has nothing to do with netopeer2-server) meaning either write your own daemon that will provide these data or use sysrepo-plugind and write just a plugin for this purpose.
Regards,
Michal

Got it, thanks very much for your reply!


[Feature] Support native ESM explicitly in package.json

What problem does this feature solve?
Looks like the space and standards are moving towards ESM, it'd be cool if this library embraced that by switching to a package.json that embraces the latest best practices in multi-format support.
See:
Additional context about this issue:

https://v3.nuxtjs.org/concepts/esm/#what-kinds-of-problems-can-there-be
antfu/vite-ssg#201

What does the proposed API look like?
package.json would include the type and exports options:
  "type": "module",
  "exports": {
    ".": {
      "require": "./dist/echarts.js",
      "import": "./dist/echarts.esm.js",
      "types": "./index.d.ts"
    },
    "./core": {
      "import": "./core.js",
      "types": "./core.d.ts"
    },
    "./renderers": {
      "import": "./renderers.js",
      "types": "./renderers.d.ts"
    },
    "./charts": {
      "import": "./charts.js",
      "types": "./charts.d.ts"
    },
    "./components": {
      "import": "./components.js",
      "types": "./components.d.ts"
    },
     "./features": {
      "import": "./features.js",
      "types": "./features.d.ts"
    }
  },

The suggestion here would break cjs builds. Closing this as that is probably not a good idea....
I will come back with a  PR to update the build process to create .mjs and .cjs files.