Quick Links and Events

First of all, awesome job with this calendar! Is really useful, complete and powerful.
There are three things I would like to ask:
1.- Is there a way to create a side calendar in month view so I can use as quick links? In other words, I want to use a second calendar to change the days in the main calendar. The main calendar would be in day view and the second in month view.
2.- How can I display the number of total events of the current day view?
3.- For this calendar I'm taking the events to display from a database. So, as soon as the page loads I request ALL the events in the DB, your directive takes care of sorting them pretty well, the thing is that I'm thinking that after a couple of months when I have hundreds of events in the DB the process will become really slow. Is there a way I can tell the controller in what day is the user so I request the events of only that day? Same for month view, can I tell what month to request the events of that month only?

1 - you mean something like in Coocle Calendar?
2 - would have to look at this
3 - have a look at this post

1 - I guess the best option would be to create a simple table with dates as links changing vm.viewDate (I'd use moment for simpler generating the table)

1 - you mean something like in Google Calendar? I guess the best option would be to create a simple table with dates as links changing vm.viewDate (I'd use moment for simpler generating the table)
2 - nothing comes to my mind at this time
3 - have a look at this post in issue #547

Not sure if simple links would work. For example, the buttons to switch days are using the mwl-date-modifier directive, but they send the next or previous date with decrement or increment. Another option to tell the directive to switch to a custom date maybe?

Why not? Have a look at this plunker. Of course it's dirty and not pretty, but shows how it would work.

For 2 you can use this helper method to get the current view events:
const totalEvents = calendarHelper.getEventsInPeriod(vm.viewDate, 'day', vm.events).length;

Thanks for the helper, and the suggestion dor number 3.
Any ideas guys how to solve number 1? @mattlewis92

One more idea from me - you can create small calendar with month view and use it's on-timespan-click property to detect the onclick event and then change bigger calendar's vm.viewDate. Look at this example how on-timespan-click works.

You could just use a standard date picker to select the date maybe?

On 23 Mar 2017, at 12:05, burtek<EMAIL_ADDRESS>wrote:
One more idea from me - you can create small calendar with month view and use it's on-timespan-click property to detect the onclick event and then change bigger calendar's vm.viewDate. Look at this example how on-timespan-click works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey guys, bothering with silly questions again.
About the total events in current period, how can I use the helper? Do I need to download the js and include it just like the angular-bootstrap-calendar-tpls-min.js file?

@burtek thanks for suggesting a new calendar with month view and passing the date with on-timespan-click, this works great. Your idea of just making links with moment works good too, however, with the new calendar I'm able to switch between months pretty easy and I can disable switching views in the small calendar.

Just add calendarHelper dependency to your controller, as you'd do with other angularJS dependiences.
Glad I could help :)

Hey guys.
I get some errors trying to use the helper, could you please help me one more time?

Uncaught ReferenceError: require is not defined at calendarHelper.js:3
calendarHelper.getEventsInPeriod is not a function

also, @burtek going back to your code for the calendar that you made, what would be the best way to add other two calendars? Then you would have three months in a row

As for those errors, you'll need to wait for @mattlewis92's answer.
As for three calendars, I think I'd add three identical <mwl-calendar> tags with different view-date parameters and then add a $scope.$watcher in controller. Look at index.html:64-116 and example.js:11-20 in this plunker. It kinda looks dirty, but it's the simplest example I could think of at 3 a.m. while pretending to be learning for mid-term ;) But I guess it's good enough for most projects.
The best solution would actually be to pass all three variables to @mattlewis92's mwl-date-modifier directive through the increment/decrement buttons, but I have no clue if that's possible at the moment.

For the mini calendar I just added three in a row and increased 1 by 1 the values passed to monthDate as you did with the first calendar. But that is not optimized at all. Plus I had to add an extra row for the months like April, one week was missing.

Ah, you meant three months of the mini-calendar! I misunderstood you, sorry for that. I'm unable to think any more at this moment, but I'll try to think of something later today.

Yeah I decided to give your mini calendar a chance 😄 Some css can make it look pretty and even similar to the mwl-calendar

@burtek did you have a chance to try something?
@mattlewis92 do you know why am I getting those errors with the helper?


Added requestTeamIDByName function

It's now possible to obtain a team ID when given the team name. I deviated slightly from our usual treatment of responses in emitting an event in the case of a bad response. The GC returns a fail message when it doesn't  find a team matching the name you specified. I felt that it would be better in this case to emit an event with an empty team ID to indicate nothing was found instead of just never responding.

Nice! I love how you guys are updating the docs as you go.
If it was me, I would probably do the lazy and leave it until it was time to merge the dev branch. :+1:

I'm trying to be on my best behaviour 😝 it sucked having to try and find out everything I had changed for the 1.0.0 release 😐
On 11 Nov 2015 00:14, jimmydorry<EMAIL_ADDRESS>wrote:Nice! I love how you guys are updating the docs as you go.
If it was me, I would probably do the lazy and leave it until it was time to merge the dev branch.
—Reply to this email directly or view it on GitHub.

Is that @Smashman ?

KappaRoss, who people have queried whether he is my father who not...


Command line binary

To aide testing integration between python-paillier and javallier, add a command line program to:

generate and serialize key pairs (of different key sizes)
encrypt and serialize given a public key and a plaintext number
decrypt given a private key and the ciphertext
add two encrypted numbers together
add an encrypted number to a plaintext number
multiply an encrypted number to a plaintext number

Initially use a standard encoding scheme.
Associated issue on python-paillier#6.

Apache commons provides a useful library to help: https://commons.apache.org/proper/commons-cli/usage.html

CLI has been included in master branch as of dcdb3c85768994cb87efd81dcb264e29a6362124.
I notice the following issues:

It cannot encrypt negative number (Issue #34). The main problem is it can't properly read negative number from the command line, even after following the note in the help menu.
Some options are inconsistent (Issue #35). Using -v and --verbose gives different results. Likewise for -h and --help.
It currently only supports one type of Paillier Context (Issue #36). Ideally users should be able to provide a specific Paillier Context set up.


[Chore] Remove SF partial migration from balancer to CL

Closes: #XXX
What is the purpose of the change
Remove Partial Migration
Testing and Verifying
Remove Partial Migration Tests
Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

We might also want to remove this:

https://github.com/osmosis-labs/osmosis/blob/d70e4e1059087e6eebbe62d05cdb247edad2de49/x/superfluid/keeper/migrate.go#L327-L332

@stackman27 Can you modify this https://github.com/osmosis-labs/osmosis/blob/d70e4e1059087e6eebbe62d05cdb247edad2de49/x/superfluid/keeper/migrate.go#L318-L333
To just check if they are equal? Other than that it looks good to me

@stackman27 Can you modify this
https://github.com/osmosis-labs/osmosis/blob/d70e4e1059087e6eebbe62d05cdb247edad2de49/x/superfluid/keeper/migrate.go#L318-L333
To just check if they are equal? Other than that it looks good to me

added check around this! lmk what you think


error log. ver 	1.6.5

ical.0  2018-10-22 22:00:06.623  info  terminating
ical.0  2018-10-22 22:00:06.109  error  at processImmediate [as _immediateCallback] (timers.js:617:5)
ical.0  2018-10-22 22:00:06.109  error  at tryOnImmediate (timers.js:645:5)
ical.0  2018-10-22 22:00:06.109  error  at Immediate. (C:\ioBroker\node_modules\iobroker.ical\main.js:215:25)
ical.0  2018-10-22 22:00:06.109  error  at processData (C:\ioBroker\node_modules\iobroker.ical\main.js:260:34)
ical.0  2018-10-22 22:00:06.109  error  at RRule.between (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1759:18)
ical.0  2018-10-22 22:00:06.109  error  at Cache._cacheAdd (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1561:36)
ical.0  2018-10-22 22:00:06.109  error  at Object.dateutil.cloneDates (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:364:34)
ical.0  2018-10-22 22:00:06.109  error  at Object.dateutil.clone (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34)
ical.0  2018-10-22 22:00:06.109  error  TypeError: Cannot read property 'getTime' of undefined
ical.0  2018-10-22 22:00:06.109  error  uncaught exception: Cannot read property 'getTime' of undefined

Version?
Vladimir Vilisov<EMAIL_ADDRESS>schrieb am Mo., 22. Okt. 2018,
18:10:

ical.0 2018-10-22 22:00:06.623 info terminating
ical.0 2018-10-22 22:00:06.109 error at processImmediate [as
_immediateCallback] (timers.js:617:5)
ical.0 2018-10-22 22:00:06.109 error at tryOnImmediate (timers.js:645:5)
ical.0 2018-10-22 22:00:06.109 error at Immediate.
(C:\ioBroker\node_modules\iobroker.ical\main.js:215:25)
ical.0 2018-10-22 22:00:06.109 error at processData
(C:\ioBroker\node_modules\iobroker.ical\main.js:260:34)
ical.0 2018-10-22 22:00:06.109 error at RRule.between
(C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1759:18)
ical.0 2018-10-22 22:00:06.109 error at Cache._cacheAdd
(C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1561:36)
ical.0 2018-10-22 22:00:06.109 error at Object.dateutil.cloneDates
(C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:364:34)
ical.0 2018-10-22 22:00:06.109 error at Object.dateutil.clone
(C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34)
ical.0 2018-10-22 22:00:06.109 error TypeError: Cannot read property
'getTime' of undefined
ical.0 2018-10-22 22:00:06.109 error uncaught exception: Cannot read
property 'getTime' of undefined
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ioBroker/ioBroker.ical/issues/75, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEXqgBIVbkh6REiA6qwuCIiTg82EC5XMks5une31gaJpZM4XzrJy
.

The ics file would also be cool

Version? Vladimir Vilisov<EMAIL_ADDRESS>schrieb am Mo., 22. Okt. 2018, 18:10:
…
ical.0 2018-10-22 22:00:06.623 info terminating ical.0 2018-10-22 22:00:06.109 error at processImmediate [as _immediateCallback] (timers.js:617:5) ical.0 2018-10-22 22:00:06.109 error at tryOnImmediate (timers.js:645:5) ical.0 2018-10-22 22:00:06.109 error at Immediate. (C:\ioBroker\node_modules\iobroker.ical\main.js:215:25) ical.0 2018-10-22 22:00:06.109 error at processData (C:\ioBroker\node_modules\iobroker.ical\main.js:260:34) ical.0 2018-10-22 22:00:06.109 error at RRule.between (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1759:18) ical.0 2018-10-22 22:00:06.109 error at Cache._cacheAdd (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1561:36) ical.0 2018-10-22 22:00:06.109 error at Object.dateutil.cloneDates (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:364:34) ical.0 2018-10-22 22:00:06.109 error at Object.dateutil.clone (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34) ical.0 2018-10-22 22:00:06.109 error TypeError: Cannot read property 'getTime' of undefined ical.0 2018-10-22 22:00:06.109 error uncaught exception: Cannot read property 'getTime' of undefined — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#75>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEXqgBIVbkh6REiA6qwuCIiTg82EC5XMks5une31gaJpZM4XzrJy .

1.6.5

Same Problem here (version 1.6.5) and google ical
`

ical.0
2018-10-31 12:33:39.055
info
terminating

ical.0
2018-10-31 12:33:38.541
error
at processImmediate [as _immediateCallback] (timers.js:617:5)

ical.0
2018-10-31 12:33:38.541
error
at tryOnImmediate (timers.js:645:5)

ical.0
2018-10-31 12:33:38.541
error
at Immediate. (C:\Program Files\ioBroker\node_modules\iobroker.ical\main.js:325:13)

ical.0
2018-10-31 12:33:38.541
error
at processData (C:\Program Files\ioBroker\node_modules\iobroker.ical\main.js:260:34)

ical.0
2018-10-31 12:33:38.541
error
at RRule.between (C:\Program Files\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1759:18)

ical.0
2018-10-31 12:33:38.541
error
at Cache._cacheAdd (C:\Program Files\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1561:36)

ical.0
2018-10-31 12:33:38.541
error
at Object.dateutil.cloneDates (C:\Program Files\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:364:34)

ical.0
2018-10-31 12:33:38.541
error
at Object.dateutil.clone (C:\Program Files\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34)

ical.0
2018-10-31 12:33:38.541
error
TypeError: Cannot read property 'getTime' of undefined

ical.0
2018-10-31 12:33:38.538
error
uncaught exception: Cannot read property 'getTime' of undefined

`

Is the problem solved with version 1.6.6?

No the problem is still present

ical.0
2018-11-06 11:06:47.449
error
TypeError: Cannot read property 'getTime' of undefined at Object.dateutil.clone (C:\Program Files\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34) at Object.dat

ical.0
2018-11-06 11:06:47.449
error
uncaught exception: Cannot read property 'getTime' of undefined

I need more infos to help you. Can you set the log level to debug and post the messages or provide a minimal example file which causes the error?

Log level is set to debug
win32 (win7) + node 6.14.4
ical_log.txt <= log from ical instance
basic.txt <= example google ics

1,6,6

ical.0
2018-11-06 23:19:59.082
error
TypeError: Cannot read property 'getTime' of undefined at Object.dateutil.clone (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34) at Object.dateutil.cloneDat

ical.0
2018-11-06 23:19:59.082
error
uncaught exception: Cannot read property 'getTime' of undefined

@instalator: Your pasted log is trimmed after about 200 character. Can you provide the full log as a file?

Short summary: I couldn't reproduce the error 😭
Calendar file from Raptor8604
Adapter-Version: 1.6.6 or 1.6.5
nodejs version: 6.13.0 or 6.14.4
local timezone: North Asia Standard Time (UTC+07:00) or W. Europe Standard Time (UTC+01:00)

@Raptor8604 & @instalator: I realign and optimized the debug output. Could you try again with the version from https://github.com/twonky4/ioBroker.ical
And please add adapter debug log as a downloaded file. If its containing to much personal data for github you can also send me a PN via https://forum.iobroker.net/memberlist.php?mode=viewprofile&u=3596

A question: Have you tried to delete, uninstall and re-install the adapter?

@Raptor8604: Could you try with the version of https://github.com/twonky4/ioBroker.ical
The log file is also trimmed to about 200 character :sad

ical_log.txt
with latest version installed from git

@Raptor8604: The logfile is still trimmed up to 200 character per line. Can you provide a non trimmed version?
I made also some error detection change. So if you use the newest version from https://github.com/twonky4/ioBroker.ical the event import doesn't stop any more but log the error with more detailed debug information.

iobroker.log.2018-11-14.txt

@Raptor8604: Can you try with the recent version of https://github.com/twonky4/ioBroker.ical

iobroker.log.2018-11-15.txt
updated via admin and url

@Raptor8604: Thx! It looks like the the error occurs only for one event. There have to be some special case.

Altpapier - 31.04.2015

Since it's an outdated event I think you can live with it, because all other events are working very well.
I still can not reproduce the problem locally 😢
Maybe more example data from other users will help with the problem. It looks like the rrule library has a bug.

@Apollon77: Can you add the help wanted label?

@instalator: I can't reproduce the problem locally.

Please retry with current Github version

ical.0 Issue detected in RRule, event ignored; Please forward debug information to iobroker.ical developer: TypeError: Cannot read property 'getTime' of undefined
at Object.dateutil.clone (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:358:34)
at Object.dateutil.cloneDates (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:364:34)
at Cache._cacheAdd (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1561:36)
at RRule.between (C:\ioBroker\node_modules\iobroker.ical\node_modules\rrule\dist\es5\rrule.js:1759:18)
at processData (C:\ioBroker\node_modules\iobroker.ical\main.js:280:31)
at Immediate. (C:\ioBroker\node_modules\iobroker.ical\main.js:216:25)
at tryOnImmediate (timers.js:645:5)
at processImmediate [as _immediateCallback] (timers.js:617:5)
RRule object: {"_string":null,"_cache":{"all":false,"before":[],"after":[],"between":[]},"origOptions":{"dtstart":"2016-05-20T00:00:00.000Z","freq":0,"wkst":{"weekday":0},"until":"2018-05-19T00:00:00.000Z"},"options":{"dtstart":"2016-05-20T00:00:00.000Z","freq":0,"wkst":0,"until":"2018-05-19T00:00:00.000Z","interval":1,"count":null,"tzid":null,"bysetpos":null,"bymonth":[5],"bymonthday":[20],"bynmonthday":[],"byyearday":null,"byweekno":null,"byweekday":null,"bynweekday":null,"byhour":[0],"byminute":[0],"bysecond":[0],"byeaster":null},"timeset":[{"hour":0,"minute":0,"second":0,"millisecond":0}],"_len":2}
now3: Tue Dec 04 2018 00:00:00 GMT+0700 (RTZ 6 (зима))
endpreview: Wed Dec 12 2018 21:46:53 GMT+0700 (RTZ 6 (зима))

I still can not reproduce it. 😞 I added 2 more informations to the error message. But it looks like there is an error in the rrule library. But I can only create a bug issue there if I can reproduce it.
@instalator: You have also knowlegde about adapter development. Can you create a simple script to reproduce it without the whole adapter?
Here is the rrule object create:
https://github.com/ioBroker/ioBroker.ical/blob/751c3b78c9e5a723ff847cb4a4e70ab880ed3577/main.js#L272
And the error is thrown here:
https://github.com/ioBroker/ioBroker.ical/blob/751c3b78c9e5a723ff847cb4a4e70ab880ed3577/main.js#L280
It should looks like:
var RRule   = require('rrule').RRule;
var rule = new RRule({
  freq: RRule.YEARLY,
  dtstart: new Date(Date.UTC(2016, 4, 20, 0, 0, 0)),
  until: new Date(Date.UTC(2018, 4, 19, 0, 0, 0))
})

var dates = rule.between(new Date(Date.UTC(2018, 11, 3, 17, 0, 0)), new Date(Date.UTC(2018, 11, 11, 14, 46, 53)), true);

I saved the problem entries in the calendar and now there is no error.

The problem is again relevant.


Update hugo-theme-scroll.md after repository transfer

Updated reference to Hugo Scroll theme after transfer new owner

Preview looks good.


Running the script again wiped out previous log and error files. The input and output data also disappeared.

Since the acme_diags were not calculated, I tried to run updated processflow on the previous run (with input files already transferred and amwg and ncclimo already finished). The process claims: '[+] All processing complete'. Looking for the previous logs and errors, I noticed that the new run overwritten the old files. Looking further, both my input data (except case_scripts) and the output were wiped out as well.
I propose to always write the new state, log and error files, maybe append the date-time stamp to them.
I am not sure how the input and output data were deleted, might be the user error, but obviously that should never be done.
directory: /p/cscratch/acme/mccoy20/test_2017-09-14-Chris

(workflow) bash-4.1$ processflow.py -c ./run.cfg
acme1.llnl.gov requires manual activation, please open the following URL in a browser to activate the endpoint:
https://www.globus.org/app/endpoints/a871c6de-2acd-11e7-bc7c-22000b9a448b/activate
Press ENTER after activating the endpoint
edisongrid.nersc.gov requires manual activation, please open the following URL in a browser to activate the endpoint:
https://www.globus.org/app/endpoints/b9d02196-6d04-11e5-ba46-22000b92c6ec/activate
Press ENTER after activating the endpoint
Globus authentication complete
Checking file access on globus transfer nodes
Turning on the display........
[+] All processing complete

The config includes:
# The year to start the post processing, typically 1
simulation_start_year =  1980

# The last year to run post processing jobs on
simulation_end_year = 10

Thats your problem. I updated the docs yesterday (so you probably havent seen the changes). The new sample run config includes a better explanation of what those fields should be. The tool isnt seeing anything to run, since year 10 doesnt come after year 1980.
# The year to start the post processing, typically 1
# If the first year of the simulation is 0001, use 1, but if
#  it started later e.g. 1980, use 1980
simulation_start_year =  1

# The last year to run post processing jobs on
# The highest number year, so if your simulation starts in 1980
#   and you want to process 20 years, this should be 2000
simulation_end_year = 20

OK. I will change that and re-run.
Please add the check and give a user an error if the simulation_end_year is lower then simulation_start_year. Also if you cannot find data with given year specification -- also give a warning on that.


VX_NN - bug fix

Fixes a bug introduced by #732. Noticed by @paveltc and me while testing NN unit tests.
@paveltc Can you try building the C unit tests with this PR and let me know if the enum error goes away

@LakshmiKumar23 @kiritigowda This fixes the issue we were seeing.


Banner / Projects compatibility - Frontmatter mode

Both the Banner and Projects plugin use the frontmatter to select the image to display. It is also possible to use the same key and with a single line you can see the thumbnail in the Gallery view of Projects and as a Banner of the note.
It would be great if image inserter was also compatible with this system.
I propose:

An option in preferences to select the frontmatter key, by default "image"
A new command in the command palette, Insert Image to Frontmatter

Projects
https://github.com/marcusolsson/obsidian-projects

Banner
https://github.com/noatpad/obsidian-banners

@javiavid
Thank you for the idea.
Could you try https://github.com/cloudy9101/obsidian-image-inserter/releases/tag/0.1.8-pre and see if there's any issue or thought?
I also updated the README https://github.com/cloudy9101/obsidian-image-inserter/blob/frontmatter/README.md

It works fine, although I found a bug.
If you have the key image_y: doesn't do it right and duplicates the image key.
Here are some examples:
GOOD
image: "https://images.unsplash.com/photo-1498887960847-2a5e46312788?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=MnwzNjAwOTd8MHwxfHNlYXJjaHwxM3x8Y2FyfGVufDB8MHx8fDE2NzA0NDI0ODI&ixlib=rb-4.0.3&q=80&w=1080"
WRONG
image: "https://images.unsplash.com/photo-1498887960847-2a5e46312788?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=MnwzNjAwOTd8MHwxfHNlYXJjaHwxM3x8Y2FyfGVufDB8MHx8fDE2NzA0NDI0ODI&ixlib=rb-4.0.3&q=80&w=1080"
image_y: 0.724

Haha, I made a silly mistake. Will fix it later. Thanks for the test.

Thanks

Released in https://github.com/cloudy9101/obsidian-image-inserter/releases/tag/0.2.0. Please update the plugin.


Jupyterlab_latex 3.1.0, extension smoke tests, maintainer

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)
[ ] 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.

Notes:

updates for jupyter-packaging specialness
adds some lab/server extension validation smoke tests
removes vendored license (will do some upstream PRs to get that better squared away)
adds self as maintainer

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender


Turning on area colors results in each underlying mesh face being a different color

Originally posted by @mikerife in https://github.com/pyansys/pymapdl/issues/1993#issuecomment-1515676588
Hi @mcMunich
The two aplot commands are independent - I suspect the second plot with all the areas, colored and numbered, is behind the plot window shown.
@germa89 we have a funny issue; turning on area colors results in each underlying mesh face being a different color.  Something broke - you can see it in Step 3 of the Lathe Cutter example model compared to the plot shown in the Objective.  Here is the aplot of the block from above:
from ansys.mapdl.core import launch_mapdl
mapdl = launch_mapdl()
mapdl.clear()
mapdl.prep7()
mapdl.block(0,1,0,1,0,1)
mapdl.aplot(vtk=True, show_area_numbering = True, color_areas = True)
mapdl.exit()

Mike

The issue with this is that mapdl.aplot duplicate areas and on the way, it actually refines it. Then it plots them.
It actually a mess to touch that. But I will think about it.


Fix getCameraPosition()

getCameraPosition() not fire callback

Thank you for sending a pull request, but actually, taking callback is wrong.
The v2 is designed the most of all methods work as synchronously.
https://github.com/mapsplugin/v2.0-demo/blob/master/www/Map/getCameraPosition.html#L37


fix : updated installation guide

as using npm packages were not working and actual commands were missing

Hi @iprankurpandey , thanks for taking time to make this PR. After having a look, this approach (# 3) which is added is actually identical to the Approach 1.
You can have a look at active issues and feel free to submit a contribution. Closing this for now. Once again, thanks a lot!

Hey @sohamsshah thanks for replying on this , i would love to contribute to this amazing project .


Site relevance

This is the old OMS doc skeleton I believe. It's also still one of the first links that comes up in search engines for "azure backup". Are we going to retire these pages any time soon so that the current Backup docs are the only ones exposed?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b084d947-abfd-a8f9-b09f-d07f39eb5ad7
Version Independent ID: a935fe20-e074-1fb0-1810-5cf384abb55e
Content: What is Azure Backup?
Content Source: articles/backup/backup-introduction-to-azure-backup.md
Service: backup
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@dcbrown16 Thanks for the feedback. We are looking into this and will get back to you shortly.

@dcbrown16 Appreciate your patience and time and thanks for bringing this to our attention. We have deprecated the old OMS docs. Closing this for now and if you've any concerns in this matter, tag me in your reply and we shall continue the discussion.


AreasExample

I tried to run the AreasExample but how can I make the lines straight?

Please check examples and read wiki. The issues are not for this kind of questions, as mentioned in the template.


Regression Tests Failure using "ctest"

Bug Report

What is the issue you have?

After using the build process to create the tests (documented at bottom of README.md file), all of the tests run by "ctest" are built and run successfully, except for two regression tests. The "ctest" application produced the following results:
-- The CXX compiler identification is GNU 6.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/local/src/json-develop/build
Scanning dependencies of target catch_main
[  1%] Building CXX object test/CMakeFiles/catch_main.dir/src/unit.cpp.o
[  1%] Built target catch_main
Scanning dependencies of target test-unicode
[  2%] Building CXX object test/CMakeFiles/test-unicode.dir/src/unit-unicode.cpp.o
[  4%] Linking CXX executable test-unicode
[  4%] Built target test-unicode
Scanning dependencies of target test-reference_access
[  5%] Building CXX object test/CMakeFiles/test-reference_access.dir/src/unit-reference_access.cpp.o
[  7%] Linking CXX executable test-reference_access
[  7%] Built target test-reference_access
Scanning dependencies of target test-msgpack
[  8%] Building CXX object test/CMakeFiles/test-msgpack.dir/src/unit-msgpack.cpp.o
[  9%] Linking CXX executable test-msgpack
[  9%] Built target test-msgpack
Scanning dependencies of target test-modifiers
[ 11%] Building CXX object test/CMakeFiles/test-modifiers.dir/src/unit-modifiers.cpp.o
[ 12%] Linking CXX executable test-modifiers
[ 12%] Built target test-modifiers
Scanning dependencies of target test-meta
[ 14%] Building CXX object test/CMakeFiles/test-meta.dir/src/unit-meta.cpp.o
[ 15%] Linking CXX executable test-meta
[ 15%] Built target test-meta
Scanning dependencies of target test-json_pointer
[ 16%] Building CXX object test/CMakeFiles/test-json_pointer.dir/src/unit-json_pointer.cpp.o
[ 18%] Linking CXX executable test-json_pointer
[ 18%] Built target test-json_pointer
Scanning dependencies of target test-class_parser
[ 19%] Building CXX object test/CMakeFiles/test-class_parser.dir/src/unit-class_parser.cpp.o
[ 21%] Linking CXX executable test-class_parser
[ 21%] Built target test-class_parser
Scanning dependencies of target test-regression
[ 22%] Building CXX object test/CMakeFiles/test-regression.dir/src/unit-regression.cpp.o
[ 23%] Linking CXX executable test-regression
[ 23%] Built target test-regression
Scanning dependencies of target test-class_lexer
[ 25%] Building CXX object test/CMakeFiles/test-class_lexer.dir/src/unit-class_lexer.cpp.o
[ 26%] Linking CXX executable test-class_lexer
[ 26%] Built target test-class_lexer
Scanning dependencies of target test-cbor
[ 28%] Building CXX object test/CMakeFiles/test-cbor.dir/src/unit-cbor.cpp.o
[ 29%] Linking CXX executable test-cbor
[ 29%] Built target test-cbor
Scanning dependencies of target test-udt
[ 30%] Building CXX object test/CMakeFiles/test-udt.dir/src/unit-udt.cpp.o
[ 32%] Linking CXX executable test-udt
[ 32%] Built target test-udt
Scanning dependencies of target test-algorithms
[ 33%] Building CXX object test/CMakeFiles/test-algorithms.dir/src/unit-algorithms.cpp.o
[ 35%] Linking CXX executable test-algorithms
[ 35%] Built target test-algorithms
Scanning dependencies of target test-comparison
[ 36%] Building CXX object test/CMakeFiles/test-comparison.dir/src/unit-comparison.cpp.o
[ 38%] Linking CXX executable test-comparison
[ 38%] Built target test-comparison
Scanning dependencies of target test-class_const_iterator
[ 39%] Building CXX object test/CMakeFiles/test-class_const_iterator.dir/src/unit-class_const_iterator.cpp.o
[ 40%] Linking CXX executable test-class_const_iterator
[ 40%] Built target test-class_const_iterator
Scanning dependencies of target test-element_access1
[ 42%] Building CXX object test/CMakeFiles/test-element_access1.dir/src/unit-element_access1.cpp.o
[ 43%] Linking CXX executable test-element_access1
[ 43%] Built target test-element_access1
Scanning dependencies of target test-iterator_wrapper
[ 45%] Building CXX object test/CMakeFiles/test-iterator_wrapper.dir/src/unit-iterator_wrapper.cpp.o
[ 46%] Linking CXX executable test-iterator_wrapper
[ 46%] Built target test-iterator_wrapper
Scanning dependencies of target test-noexcept
[ 47%] Building CXX object test/CMakeFiles/test-noexcept.dir/src/unit-noexcept.cpp.o
[ 49%] Linking CXX executable test-noexcept
[ 49%] Built target test-noexcept
Scanning dependencies of target test-allocator
[ 50%] Building CXX object test/CMakeFiles/test-allocator.dir/src/unit-allocator.cpp.o
[ 52%] Linking CXX executable test-allocator
[ 52%] Built target test-allocator
Scanning dependencies of target test-capacity
[ 53%] Building CXX object test/CMakeFiles/test-capacity.dir/src/unit-capacity.cpp.o
[ 54%] Linking CXX executable test-capacity
[ 54%] Built target test-capacity
Scanning dependencies of target test-class_iterator
[ 56%] Building CXX object test/CMakeFiles/test-class_iterator.dir/src/unit-class_iterator.cpp.o
[ 57%] Linking CXX executable test-class_iterator
[ 57%] Built target test-class_iterator
Scanning dependencies of target test-convenience
[ 59%] Building CXX object test/CMakeFiles/test-convenience.dir/src/unit-convenience.cpp.o
[ 60%] Linking CXX executable test-convenience
[ 60%] Built target test-convenience
Scanning dependencies of target test-concepts
[ 61%] Building CXX object test/CMakeFiles/test-concepts.dir/src/unit-concepts.cpp.o
[ 63%] Linking CXX executable test-concepts
[ 63%] Built target test-concepts
Scanning dependencies of target test-readme
[ 64%] Building CXX object test/CMakeFiles/test-readme.dir/src/unit-readme.cpp.o
[ 66%] Linking CXX executable test-readme
[ 66%] Built target test-readme
Scanning dependencies of target test-constructor1
[ 67%] Building CXX object test/CMakeFiles/test-constructor1.dir/src/unit-constructor1.cpp.o
[ 69%] Linking CXX executable test-constructor1
[ 69%] Built target test-constructor1
Scanning dependencies of target test-pointer_access
[ 70%] Building CXX object test/CMakeFiles/test-pointer_access.dir/src/unit-pointer_access.cpp.o
[ 71%] Linking CXX executable test-pointer_access
[ 71%] Built target test-pointer_access
Scanning dependencies of target test-deserialization
[ 73%] Building CXX object test/CMakeFiles/test-deserialization.dir/src/unit-deserialization.cpp.o
/usr/local/src/json-develop/test/src/unit-deserialization.cpp: In function ‘void ____C_A_T_C_H____T_E_S_T____0()’:
/usr/local/src/json-develop/test/src/unit-deserialization.cpp:72:18: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
j << ss;
^~
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:29:0:
/usr/local/src/json-develop/test/src/unit-deserialization.cpp:129:34: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
CHECK_THROWS_AS(j << ss1, json::parse_error&);
^
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:29:0:
/usr/local/src/json-develop/test/src/unit-deserialization.cpp:130:36: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
CHECK_THROWS_WITH(j << ss2,
^
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
/usr/local/src/json-develop/test/src/unit-deserialization.cpp:532:18: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
j << s;
^
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
/usr/local/src/json-develop/test/src/unit-deserialization.cpp:534:18: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
j << s;
^
In file included from /usr/local/src/json-develop/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
[ 74%] Linking CXX executable test-deserialization
[ 74%] Built target test-deserialization
Scanning dependencies of target test-testsuites
[ 76%] Building CXX object test/CMakeFiles/test-testsuites.dir/src/unit-testsuites.cpp.o
[ 77%] Linking CXX executable test-testsuites
[ 77%] Built target test-testsuites
Scanning dependencies of target test-conversions
[ 78%] Building CXX object test/CMakeFiles/test-conversions.dir/src/unit-conversions.cpp.o
[ 80%] Linking CXX executable test-conversions
[ 80%] Built target test-conversions
Scanning dependencies of target test-element_access2
[ 81%] Building CXX object test/CMakeFiles/test-element_access2.dir/src/unit-element_access2.cpp.o
[ 83%] Linking CXX executable test-element_access2
[ 83%] Built target test-element_access2
Scanning dependencies of target test-inspection
[ 84%] Building CXX object test/CMakeFiles/test-inspection.dir/src/unit-inspection.cpp.o
[ 85%] Linking CXX executable test-inspection
[ 85%] Built target test-inspection
Scanning dependencies of target test-json_patch
[ 87%] Building CXX object test/CMakeFiles/test-json_patch.dir/src/unit-json_patch.cpp.o
[ 88%] Linking CXX executable test-json_patch
[ 88%] Built target test-json_patch
Scanning dependencies of target test-iterators1
[ 90%] Building CXX object test/CMakeFiles/test-iterators1.dir/src/unit-iterators1.cpp.o
[ 91%] Linking CXX executable test-iterators1
[ 91%] Built target test-iterators1
Scanning dependencies of target test-serialization
[ 92%] Building CXX object test/CMakeFiles/test-serialization.dir/src/unit-serialization.cpp.o
/usr/local/src/json-develop/test/src/unit-serialization.cpp: In function ‘void ____C_A_T_C_H____T_E_S_T____0()’:
/usr/local/src/json-develop/test/src/unit-serialization.cpp:71:18: warning: ‘std::ostream& nlohmann::operator>>(const nlohmann::basic_json<>&, std::ostream&)’ is deprecated [-Wdeprecated-declarations]
j >> ss;
^~
In file included from /usr/local/src/json-develop/test/src/unit-serialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:12933:26: note: declared here
friend std::ostream& operator>>(const basic_json& j, std::ostream& o)
^~~~~~~~
/usr/local/src/json-develop/test/src/unit-serialization.cpp:80:18: warning: ‘std::ostream& nlohmann::operator>>(const nlohmann::basic_json<>&, std::ostream&)’ is deprecated [-Wdeprecated-declarations]
j >> ss;
^~
In file included from /usr/local/src/json-develop/test/src/unit-serialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:12933:26: note: declared here
friend std::ostream& operator>>(const basic_json& j, std::ostream& o)
^~~~~~~~
/usr/local/src/json-develop/test/src/unit-serialization.cpp:91:18: warning: ‘std::ostream& nlohmann::operator>>(const nlohmann::basic_json<>&, std::ostream&)’ is deprecated [-Wdeprecated-declarations]
j >> ss;
^~
In file included from /usr/local/src/json-develop/test/src/unit-serialization.cpp:31:0:
/usr/local/src/json-develop/src/json.hpp:12933:26: note: declared here
friend std::ostream& operator>>(const basic_json& j, std::ostream& o)
^~~~~~~~
[ 94%] Linking CXX executable test-serialization
[ 94%] Built target test-serialization
Scanning dependencies of target test-constructor2
[ 95%] Building CXX object test/CMakeFiles/test-constructor2.dir/src/unit-constructor2.cpp.o
[ 97%] Linking CXX executable test-constructor2
[ 97%] Built target test-constructor2
Scanning dependencies of target test-iterators2
[ 98%] Building CXX object test/CMakeFiles/test-iterators2.dir/src/unit-iterators2.cpp.o
[100%] Linking CXX executable test-iterators2
[100%] Built target test-iterators2
Test project /usr/local/src/json-develop/build
Start  1: test-algorithms_default
1/70 Test  #1: test-algorithms_default .............   Passed    0.01 sec
Start  2: test-algorithms_all
2/70 Test  #2: test-algorithms_all .................   Passed    0.01 sec
Start  3: test-allocator_default
3/70 Test  #3: test-allocator_default ..............   Passed    0.00 sec
Start  4: test-allocator_all
4/70 Test  #4: test-allocator_all ..................   Passed    0.00 sec
Start  5: test-capacity_default
5/70 Test  #5: test-capacity_default ...............   Passed    0.01 sec
Start  6: test-capacity_all
6/70 Test  #6: test-capacity_all ...................   Passed    0.01 sec
Start  7: test-cbor_default
7/70 Test  #7: test-cbor_default ...................   Passed    3.87 sec
Start  8: test-cbor_all
8/70 Test  #8: test-cbor_all .......................   Passed   47.03 sec
Start  9: test-class_const_iterator_default
9/70 Test  #9: test-class_const_iterator_default ...   Passed    0.01 sec
Start 10: test-class_const_iterator_all
10/70 Test #10: test-class_const_iterator_all .......   Passed    0.01 sec
Start 11: test-class_iterator_default
11/70 Test #11: test-class_iterator_default .........   Passed    0.01 sec
Start 12: test-class_iterator_all
12/70 Test #12: test-class_iterator_all .............   Passed    0.01 sec
Start 13: test-class_lexer_default
13/70 Test #13: test-class_lexer_default ............   Passed    0.01 sec
Start 14: test-class_lexer_all
14/70 Test #14: test-class_lexer_all ................   Passed    0.00 sec
Start 15: test-class_parser_default
15/70 Test #15: test-class_parser_default ...........   Passed    0.17 sec
Start 16: test-class_parser_all
16/70 Test #16: test-class_parser_all ...............   Passed    0.17 sec
Start 17: test-comparison_default
17/70 Test #17: test-comparison_default .............   Passed    0.02 sec
Start 18: test-comparison_all
18/70 Test #18: test-comparison_all .................   Passed    0.02 sec
Start 19: test-concepts_default
19/70 Test #19: test-concepts_default ...............   Passed    0.00 sec
Start 20: test-concepts_all
20/70 Test #20: test-concepts_all ...................   Passed    0.00 sec
Start 21: test-constructor1_default
21/70 Test #21: test-constructor1_default ...........   Passed    0.05 sec
Start 22: test-constructor1_all
22/70 Test #22: test-constructor1_all ...............   Passed    0.04 sec
Start 23: test-constructor2_default
23/70 Test #23: test-constructor2_default ...........   Passed    0.00 sec
Start 24: test-constructor2_all
24/70 Test #24: test-constructor2_all ...............   Passed    0.01 sec
Start 25: test-convenience_default
25/70 Test #25: test-convenience_default ............   Passed    0.00 sec
Start 26: test-convenience_all
26/70 Test #26: test-convenience_all ................   Passed    0.00 sec
Start 27: test-conversions_default
27/70 Test #27: test-conversions_default ............   Passed    0.03 sec
Start 28: test-conversions_all
28/70 Test #28: test-conversions_all ................   Passed    0.03 sec
Start 29: test-deserialization_default
29/70 Test #29: test-deserialization_default ........   Passed    0.01 sec
Start 30: test-deserialization_all
30/70 Test #30: test-deserialization_all ............   Passed    0.02 sec
Start 31: test-element_access1_default
31/70 Test #31: test-element_access1_default ........   Passed    0.02 sec
Start 32: test-element_access1_all
32/70 Test #32: test-element_access1_all ............   Passed    0.02 sec
Start 33: test-element_access2_default
33/70 Test #33: test-element_access2_default ........   Passed    0.02 sec
Start 34: test-element_access2_all
34/70 Test #34: test-element_access2_all ............   Passed    0.03 sec
Start 35: test-inspection_default
35/70 Test #35: test-inspection_default .............   Passed    8.58 sec
Start 36: test-inspection_all
36/70 Test #36: test-inspection_all .................   Passed    8.51 sec
Start 37: test-iterator_wrapper_default
37/70 Test #37: test-iterator_wrapper_default .......   Passed    0.01 sec
Start 38: test-iterator_wrapper_all
38/70 Test #38: test-iterator_wrapper_all ...........   Passed    0.01 sec
Start 39: test-iterators1_default
39/70 Test #39: test-iterators1_default .............   Passed    0.03 sec
Start 40: test-iterators1_all
40/70 Test #40: test-iterators1_all .................   Passed    0.02 sec
Start 41: test-iterators2_default
41/70 Test #41: test-iterators2_default .............   Passed    0.07 sec
Start 42: test-iterators2_all
42/70 Test #42: test-iterators2_all .................   Passed    0.07 sec
Start 43: test-json_patch_default
43/70 Test #43: test-json_patch_default .............   Passed    0.02 sec
Start 44: test-json_patch_all
44/70 Test #44: test-json_patch_all .................   Passed    0.02 sec
Start 45: test-json_pointer_default
45/70 Test #45: test-json_pointer_default ...........   Passed    0.01 sec
Start 46: test-json_pointer_all
46/70 Test #46: test-json_pointer_all ...............   Passed    0.01 sec
Start 47: test-meta_default
47/70 Test #47: test-meta_default ...................   Passed    0.00 sec
Start 48: test-meta_all
48/70 Test #48: test-meta_all .......................   Passed    0.00 sec
Start 49: test-modifiers_default
49/70 Test #49: test-modifiers_default ..............   Passed    0.02 sec
Start 50: test-modifiers_all
50/70 Test #50: test-modifiers_all ..................   Passed    0.02 sec
Start 51: test-msgpack_default
51/70 Test #51: test-msgpack_default ................   Passed    3.60 sec
Start 52: test-msgpack_all
52/70 Test #52: test-msgpack_all ....................   Passed   46.60 sec
Start 53: test-noexcept_default
53/70 Test #53: test-noexcept_default ...............   Passed    0.00 sec
Start 54: test-noexcept_all
54/70 Test #54: test-noexcept_all ...................   Passed    0.00 sec
Start 55: test-pointer_access_default
55/70 Test #55: test-pointer_access_default .........   Passed    0.01 sec
Start 56: test-pointer_access_all
56/70 Test #56: test-pointer_access_all .............   Passed    0.01 sec
Start 57: test-readme_default
57/70 Test #57: test-readme_default .................   Passed    0.00 sec
Start 58: test-readme_all
58/70 Test #58: test-readme_all .....................   Passed    0.01 sec
Start 59: test-reference_access_default
59/70 Test #59: test-reference_access_default .......   Passed    0.01 sec
Start 60: test-reference_access_all
60/70 Test #60: test-reference_access_all ...........   Passed    0.01 sec
Start 61: test-regression_default
61/70 Test #61: test-regression_default .............***Failed    8.60 sec
Start 62: test-regression_all
62/70 Test #62: test-regression_all .................***Failed    8.48 sec
Start 63: test-serialization_default
63/70 Test #63: test-serialization_default ..........   Passed    0.00 sec
Start 64: test-serialization_all
64/70 Test #64: test-serialization_all ..............   Passed    0.00 sec
Start 65: test-testsuites_default
65/70 Test #65: test-testsuites_default .............   Passed    0.17 sec
Start 66: test-testsuites_all
66/70 Test #66: test-testsuites_all .................   Passed    0.10 sec
Start 67: test-udt_default
67/70 Test #67: test-udt_default ....................   Passed    0.01 sec
Start 68: test-udt_all
68/70 Test #68: test-udt_all ........................   Passed    0.01 sec
Start 69: test-unicode_default
69/70 Test #69: test-unicode_default ................   Passed    0.00 sec
Start 70: test-unicode_all
70/70 Test #70: test-unicode_all ....................   Passed  396.11 sec
97% tests passed, 2 tests failed out of 70
Label Time Summary:
all        = 507.38 secproc (35 tests)
default    =  25.40 secproc (35 tests)
Total Test time (real) = 532.83 sec
The following tests FAILED:
61 - test-regression_default (Failed)
62 - test-regression_all (Failed)
Errors while running CTest

Please describe the steps to reproduce the issue. Can you provide a small but working code example?

$ mkdir build
$ cd build
$ cmake ..
$ cmake --build .
$ ctest

What is the expected behavior?

That all tests would return success.

And what is the actual behavior instead?

All but the two regression tests passed.

Which compiler and operating system are you using? Is it a supported compiler?

$ g++ --version
g++ (GCC) 6.2.0
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ uname -a
Linux maczorin6 3.13.0-107-generic #154~precise1-Ubuntu SMP Tue Dec 20 10:36:28 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Did you use a released version of the library or the version from the develop branch?

I downloaded a ZIP file from the GitHub site called "json-develop.zip".

If you experience a compilation error: can you compile and run the unit tests?

Yes.

Could you try to use the last 3.0.0 release? If the tests are still failing, could you run ctest with the --output-on-failure parameter so we can see what the output of the failing tests is.

I downloaded the "json-release-3.0.0.tar.gz" and installed it and built it with the following instructions:
$ mkdir build
$ cd build
$ cmake .. && cmake --build . && ctest --output-on-failure
Here is the output of the test with the "--output-on-failure" flag below.
-- The CXX compiler identification is GNU 6.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/local/src/json-release-3.0.0/build
Scanning dependencies of target catch_main
[  1%] Building CXX object test/CMakeFiles/catch_main.dir/src/unit.cpp.o
[  1%] Built target catch_main
Scanning dependencies of target test-unicode
[  2%] Building CXX object test/CMakeFiles/test-unicode.dir/src/unit-unicode.cpp.o
[  4%] Linking CXX executable test-unicode
[  4%] Built target test-unicode
Scanning dependencies of target test-reference_access
[  5%] Building CXX object test/CMakeFiles/test-reference_access.dir/src/unit-reference_access.cpp.o
[  7%] Linking CXX executable test-reference_access
[  7%] Built target test-reference_access
Scanning dependencies of target test-msgpack
[  8%] Building CXX object test/CMakeFiles/test-msgpack.dir/src/unit-msgpack.cpp.o
[  9%] Linking CXX executable test-msgpack
[  9%] Built target test-msgpack
Scanning dependencies of target test-modifiers
[ 11%] Building CXX object test/CMakeFiles/test-modifiers.dir/src/unit-modifiers.cpp.o
[ 12%] Linking CXX executable test-modifiers
[ 12%] Built target test-modifiers
Scanning dependencies of target test-meta
[ 14%] Building CXX object test/CMakeFiles/test-meta.dir/src/unit-meta.cpp.o
[ 15%] Linking CXX executable test-meta
[ 15%] Built target test-meta
Scanning dependencies of target test-json_pointer
[ 16%] Building CXX object test/CMakeFiles/test-json_pointer.dir/src/unit-json_pointer.cpp.o
[ 18%] Linking CXX executable test-json_pointer
[ 18%] Built target test-json_pointer
Scanning dependencies of target test-class_parser
[ 19%] Building CXX object test/CMakeFiles/test-class_parser.dir/src/unit-class_parser.cpp.o
[ 21%] Linking CXX executable test-class_parser
[ 21%] Built target test-class_parser
Scanning dependencies of target test-regression
[ 22%] Building CXX object test/CMakeFiles/test-regression.dir/src/unit-regression.cpp.o
[ 23%] Linking CXX executable test-regression
[ 23%] Built target test-regression
Scanning dependencies of target test-class_lexer
[ 25%] Building CXX object test/CMakeFiles/test-class_lexer.dir/src/unit-class_lexer.cpp.o
[ 26%] Linking CXX executable test-class_lexer
[ 26%] Built target test-class_lexer
Scanning dependencies of target test-cbor
[ 28%] Building CXX object test/CMakeFiles/test-cbor.dir/src/unit-cbor.cpp.o
[ 29%] Linking CXX executable test-cbor
[ 29%] Built target test-cbor
Scanning dependencies of target test-udt
[ 30%] Building CXX object test/CMakeFiles/test-udt.dir/src/unit-udt.cpp.o
[ 32%] Linking CXX executable test-udt
[ 32%] Built target test-udt
Scanning dependencies of target test-algorithms
[ 33%] Building CXX object test/CMakeFiles/test-algorithms.dir/src/unit-algorithms.cpp.o
[ 35%] Linking CXX executable test-algorithms
[ 35%] Built target test-algorithms
Scanning dependencies of target test-comparison
[ 36%] Building CXX object test/CMakeFiles/test-comparison.dir/src/unit-comparison.cpp.o
[ 38%] Linking CXX executable test-comparison
[ 38%] Built target test-comparison
Scanning dependencies of target test-class_const_iterator
[ 39%] Building CXX object test/CMakeFiles/test-class_const_iterator.dir/src/unit-class_const_iterator.cpp.o
[ 40%] Linking CXX executable test-class_const_iterator
[ 40%] Built target test-class_const_iterator
Scanning dependencies of target test-element_access1
[ 42%] Building CXX object test/CMakeFiles/test-element_access1.dir/src/unit-element_access1.cpp.o
[ 43%] Linking CXX executable test-element_access1
[ 43%] Built target test-element_access1
Scanning dependencies of target test-iterator_wrapper
[ 45%] Building CXX object test/CMakeFiles/test-iterator_wrapper.dir/src/unit-iterator_wrapper.cpp.o
[ 46%] Linking CXX executable test-iterator_wrapper
[ 46%] Built target test-iterator_wrapper
Scanning dependencies of target test-noexcept
[ 47%] Building CXX object test/CMakeFiles/test-noexcept.dir/src/unit-noexcept.cpp.o
[ 49%] Linking CXX executable test-noexcept
[ 49%] Built target test-noexcept
Scanning dependencies of target test-allocator
[ 50%] Building CXX object test/CMakeFiles/test-allocator.dir/src/unit-allocator.cpp.o
[ 52%] Linking CXX executable test-allocator
[ 52%] Built target test-allocator
Scanning dependencies of target test-capacity
[ 53%] Building CXX object test/CMakeFiles/test-capacity.dir/src/unit-capacity.cpp.o
[ 54%] Linking CXX executable test-capacity
[ 54%] Built target test-capacity
Scanning dependencies of target test-class_iterator
[ 56%] Building CXX object test/CMakeFiles/test-class_iterator.dir/src/unit-class_iterator.cpp.o
[ 57%] Linking CXX executable test-class_iterator
[ 57%] Built target test-class_iterator
Scanning dependencies of target test-convenience
[ 59%] Building CXX object test/CMakeFiles/test-convenience.dir/src/unit-convenience.cpp.o
[ 60%] Linking CXX executable test-convenience
[ 60%] Built target test-convenience
Scanning dependencies of target test-concepts
[ 61%] Building CXX object test/CMakeFiles/test-concepts.dir/src/unit-concepts.cpp.o
[ 63%] Linking CXX executable test-concepts
[ 63%] Built target test-concepts
Scanning dependencies of target test-readme
[ 64%] Building CXX object test/CMakeFiles/test-readme.dir/src/unit-readme.cpp.o
[ 66%] Linking CXX executable test-readme
[ 66%] Built target test-readme
Scanning dependencies of target test-constructor1
[ 67%] Building CXX object test/CMakeFiles/test-constructor1.dir/src/unit-constructor1.cpp.o
[ 69%] Linking CXX executable test-constructor1
[ 69%] Built target test-constructor1
Scanning dependencies of target test-pointer_access
[ 70%] Building CXX object test/CMakeFiles/test-pointer_access.dir/src/unit-pointer_access.cpp.o
[ 71%] Linking CXX executable test-pointer_access
[ 71%] Built target test-pointer_access
Scanning dependencies of target test-deserialization
[ 73%] Building CXX object test/CMakeFiles/test-deserialization.dir/src/unit-deserialization.cpp.o
/usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp: In function ‘void ____C_A_T_C_H____T_E_S_T____0()’:
/usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:72:18: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
j << ss;
^~
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:29:0:
/usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:129:34: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
CHECK_THROWS_AS(j << ss1, json::parse_error&);
^
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:29:0:
/usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:130:36: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
CHECK_THROWS_WITH(j << ss2,
^
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
/usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:532:18: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
j << s;
^
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
/usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:534:18: warning: ‘std::istream& nlohmann::operator<<(nlohmann::basic_json<>&, std::istream&)’ is deprecated [-Wdeprecated-declarations]
j << s;
^
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-deserialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:13119:26: note: declared here
friend std::istream& operator<<(basic_json& j, std::istream& i)
^~~~~~~~
[ 74%] Linking CXX executable test-deserialization
[ 74%] Built target test-deserialization
Scanning dependencies of target test-testsuites
[ 76%] Building CXX object test/CMakeFiles/test-testsuites.dir/src/unit-testsuites.cpp.o
[ 77%] Linking CXX executable test-testsuites
[ 77%] Built target test-testsuites
Scanning dependencies of target test-conversions
[ 78%] Building CXX object test/CMakeFiles/test-conversions.dir/src/unit-conversions.cpp.o
[ 80%] Linking CXX executable test-conversions
[ 80%] Built target test-conversions
Scanning dependencies of target test-element_access2
[ 81%] Building CXX object test/CMakeFiles/test-element_access2.dir/src/unit-element_access2.cpp.o
[ 83%] Linking CXX executable test-element_access2
[ 83%] Built target test-element_access2
Scanning dependencies of target test-inspection
[ 84%] Building CXX object test/CMakeFiles/test-inspection.dir/src/unit-inspection.cpp.o
[ 85%] Linking CXX executable test-inspection
[ 85%] Built target test-inspection
Scanning dependencies of target test-json_patch
[ 87%] Building CXX object test/CMakeFiles/test-json_patch.dir/src/unit-json_patch.cpp.o
[ 88%] Linking CXX executable test-json_patch
[ 88%] Built target test-json_patch
Scanning dependencies of target test-iterators1
[ 90%] Building CXX object test/CMakeFiles/test-iterators1.dir/src/unit-iterators1.cpp.o
[ 91%] Linking CXX executable test-iterators1
[ 91%] Built target test-iterators1
Scanning dependencies of target test-serialization
[ 92%] Building CXX object test/CMakeFiles/test-serialization.dir/src/unit-serialization.cpp.o
/usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp: In function ‘void ____C_A_T_C_H____T_E_S_T____0()’:
/usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp:71:18: warning: ‘std::ostream& nlohmann::operator>>(const nlohmann::basic_json<>&, std::ostream&)’ is deprecated [-Wdeprecated-declarations]
j >> ss;
^~
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:12933:26: note: declared here
friend std::ostream& operator>>(const basic_json& j, std::ostream& o)
^~~~~~~~
/usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp:80:18: warning: ‘std::ostream& nlohmann::operator>>(const nlohmann::basic_json<>&, std::ostream&)’ is deprecated [-Wdeprecated-declarations]
j >> ss;
^~
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:12933:26: note: declared here
friend std::ostream& operator>>(const basic_json& j, std::ostream& o)
^~~~~~~~
/usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp:91:18: warning: ‘std::ostream& nlohmann::operator>>(const nlohmann::basic_json<>&, std::ostream&)’ is deprecated [-Wdeprecated-declarations]
j >> ss;
^~
In file included from /usr/local/src/json-release-3.0.0/test/src/unit-serialization.cpp:31:0:
/usr/local/src/json-release-3.0.0/src/json.hpp:12933:26: note: declared here
friend std::ostream& operator>>(const basic_json& j, std::ostream& o)
^~~~~~~~
[ 94%] Linking CXX executable test-serialization
[ 94%] Built target test-serialization
Scanning dependencies of target test-constructor2
[ 95%] Building CXX object test/CMakeFiles/test-constructor2.dir/src/unit-constructor2.cpp.o
[ 97%] Linking CXX executable test-constructor2
[ 97%] Built target test-constructor2
Scanning dependencies of target test-iterators2
[ 98%] Building CXX object test/CMakeFiles/test-iterators2.dir/src/unit-iterators2.cpp.o
[100%] Linking CXX executable test-iterators2
[100%] Built target test-iterators2
Test project /usr/local/src/json-release-3.0.0/build
Start  1: test-algorithms_default
1/70 Test  #1: test-algorithms_default .............   Passed    0.01 sec
Start  2: test-algorithms_all
2/70 Test  #2: test-algorithms_all .................   Passed    0.01 sec
Start  3: test-allocator_default
3/70 Test  #3: test-allocator_default ..............   Passed    0.00 sec
Start  4: test-allocator_all
4/70 Test  #4: test-allocator_all ..................   Passed    0.01 sec
Start  5: test-capacity_default
5/70 Test  #5: test-capacity_default ...............   Passed    0.01 sec
Start  6: test-capacity_all
6/70 Test  #6: test-capacity_all ...................   Passed    0.01 sec
Start  7: test-cbor_default
7/70 Test  #7: test-cbor_default ...................   Passed    3.74 sec
Start  8: test-cbor_all
8/70 Test  #8: test-cbor_all .......................   Passed   46.73 sec
Start  9: test-class_const_iterator_default
9/70 Test  #9: test-class_const_iterator_default ...   Passed    0.01 sec
Start 10: test-class_const_iterator_all
10/70 Test #10: test-class_const_iterator_all .......   Passed    0.01 sec
Start 11: test-class_iterator_default
11/70 Test #11: test-class_iterator_default .........   Passed    0.01 sec
Start 12: test-class_iterator_all
12/70 Test #12: test-class_iterator_all .............   Passed    0.01 sec
Start 13: test-class_lexer_default
13/70 Test #13: test-class_lexer_default ............   Passed    0.01 sec
Start 14: test-class_lexer_all
14/70 Test #14: test-class_lexer_all ................   Passed    0.00 sec
Start 15: test-class_parser_default
15/70 Test #15: test-class_parser_default ...........   Passed    0.17 sec
Start 16: test-class_parser_all
16/70 Test #16: test-class_parser_all ...............   Passed    0.17 sec
Start 17: test-comparison_default
17/70 Test #17: test-comparison_default .............   Passed    0.02 sec
Start 18: test-comparison_all
18/70 Test #18: test-comparison_all .................   Passed    0.02 sec
Start 19: test-concepts_default
19/70 Test #19: test-concepts_default ...............   Passed    0.00 sec
Start 20: test-concepts_all
20/70 Test #20: test-concepts_all ...................   Passed    0.00 sec
Start 21: test-constructor1_default
21/70 Test #21: test-constructor1_default ...........   Passed    0.04 sec
Start 22: test-constructor1_all
22/70 Test #22: test-constructor1_all ...............   Passed    0.04 sec
Start 23: test-constructor2_default
23/70 Test #23: test-constructor2_default ...........   Passed    0.00 sec
Start 24: test-constructor2_all
24/70 Test #24: test-constructor2_all ...............   Passed    0.01 sec
Start 25: test-convenience_default
25/70 Test #25: test-convenience_default ............   Passed    0.00 sec
Start 26: test-convenience_all
26/70 Test #26: test-convenience_all ................   Passed    0.00 sec
Start 27: test-conversions_default
27/70 Test #27: test-conversions_default ............   Passed    0.03 sec
Start 28: test-conversions_all
28/70 Test #28: test-conversions_all ................   Passed    0.03 sec
Start 29: test-deserialization_default
29/70 Test #29: test-deserialization_default ........   Passed    0.01 sec
Start 30: test-deserialization_all
30/70 Test #30: test-deserialization_all ............   Passed    0.02 sec
Start 31: test-element_access1_default
31/70 Test #31: test-element_access1_default ........   Passed    0.02 sec
Start 32: test-element_access1_all
32/70 Test #32: test-element_access1_all ............   Passed    0.02 sec
Start 33: test-element_access2_default
33/70 Test #33: test-element_access2_default ........   Passed    0.02 sec
Start 34: test-element_access2_all
34/70 Test #34: test-element_access2_all ............   Passed    0.02 sec
Start 35: test-inspection_default
35/70 Test #35: test-inspection_default .............   Passed    8.41 sec
Start 36: test-inspection_all
36/70 Test #36: test-inspection_all .................   Passed    8.48 sec
Start 37: test-iterator_wrapper_default
37/70 Test #37: test-iterator_wrapper_default .......   Passed    0.01 sec
Start 38: test-iterator_wrapper_all
38/70 Test #38: test-iterator_wrapper_all ...........   Passed    0.01 sec
Start 39: test-iterators1_default
39/70 Test #39: test-iterators1_default .............   Passed    0.02 sec
Start 40: test-iterators1_all
40/70 Test #40: test-iterators1_all .................   Passed    0.03 sec
Start 41: test-iterators2_default
41/70 Test #41: test-iterators2_default .............   Passed    0.06 sec
Start 42: test-iterators2_all
42/70 Test #42: test-iterators2_all .................   Passed    0.06 sec
Start 43: test-json_patch_default
43/70 Test #43: test-json_patch_default .............   Passed    0.02 sec
Start 44: test-json_patch_all
44/70 Test #44: test-json_patch_all .................   Passed    0.03 sec
Start 45: test-json_pointer_default
45/70 Test #45: test-json_pointer_default ...........   Passed    0.01 sec
Start 46: test-json_pointer_all
46/70 Test #46: test-json_pointer_all ...............   Passed    0.01 sec
Start 47: test-meta_default
47/70 Test #47: test-meta_default ...................   Passed    0.00 sec
Start 48: test-meta_all
48/70 Test #48: test-meta_all .......................   Passed    0.00 sec
Start 49: test-modifiers_default
49/70 Test #49: test-modifiers_default ..............   Passed    0.01 sec
Start 50: test-modifiers_all
50/70 Test #50: test-modifiers_all ..................   Passed    0.01 sec
Start 51: test-msgpack_default
51/70 Test #51: test-msgpack_default ................   Passed    3.55 sec
Start 52: test-msgpack_all
52/70 Test #52: test-msgpack_all ....................   Passed   46.57 sec
Start 53: test-noexcept_default
53/70 Test #53: test-noexcept_default ...............   Passed    0.00 sec
Start 54: test-noexcept_all
54/70 Test #54: test-noexcept_all ...................   Passed    0.00 sec
Start 55: test-pointer_access_default
55/70 Test #55: test-pointer_access_default .........   Passed    0.01 sec
Start 56: test-pointer_access_all
56/70 Test #56: test-pointer_access_all .............   Passed    0.01 sec
Start 57: test-readme_default
57/70 Test #57: test-readme_default .................   Passed    0.00 sec
Start 58: test-readme_all
58/70 Test #58: test-readme_all .....................   Passed    0.01 sec
Start 59: test-reference_access_default
59/70 Test #59: test-reference_access_default .......   Passed    0.01 sec
Start 60: test-reference_access_all
60/70 Test #60: test-reference_access_all ...........   Passed    0.01 sec
Start 61: test-regression_default
61/70 Test #61: test-regression_default .............***Failed    8.50 sec
test-regression is a Catch v1.9.7 host application.
Run with -? for options

-------------------------------------------------------------------------------
regression tests
  issue #186 miloyip/nativejson-benchmark: floating-point parsing
-------------------------------------------------------------------------------
/usr/local/src/json-release-3.0.0/test/src/unit-regression.cpp:371
...............................................................................

/usr/local/src/json-release-3.0.0/test/src/unit-regression.cpp:385: FAILED:
  CHECK( j.get<double>() == 1.00000000000000022 )
with expansion:
  1.0 == 1.0

===============================================================================
test cases:   1 |   0 passed | 1 failed
assertions: 410 | 409 passed | 1 failed

      Start 62: test-regression_all
62/70 Test #62: test-regression_all .................***Failed    8.44 sec

test-regression is a Catch v1.9.7 host application.
Run with -? for options

regression tests
issue #186 miloyip/nativejson-benchmark: floating-point parsing
/usr/local/src/json-release-3.0.0/test/src/unit-regression.cpp:371
...............................................................................
/usr/local/src/json-release-3.0.0/test/src/unit-regression.cpp:385: FAILED:
CHECK( j.get() == 1.00000000000000022 )
with expansion:
1.0 == 1.0
===============================================================================
test cases:   1 |   0 passed | 1 failed
assertions: 410 | 409 passed | 1 failed
  Start 63: test-serialization_default

63/70 Test #63: test-serialization_default ..........   Passed    0.00 sec
Start 64: test-serialization_all
64/70 Test #64: test-serialization_all ..............   Passed    0.00 sec
Start 65: test-testsuites_default
65/70 Test #65: test-testsuites_default .............   Passed    0.09 sec
Start 66: test-testsuites_all
66/70 Test #66: test-testsuites_all .................   Passed    0.09 sec
Start 67: test-udt_default
67/70 Test #67: test-udt_default ....................   Passed    0.00 sec
Start 68: test-udt_all
68/70 Test #68: test-udt_all ........................   Passed    0.00 sec
Start 69: test-unicode_default
69/70 Test #69: test-unicode_default ................   Passed    0.01 sec
Start 70: test-unicode_all
70/70 Test #70: test-unicode_all ....................   Passed  405.85 sec
97% tests passed, 2 tests failed out of 70
Label Time Summary:
all        = 516.73 secproc (35 tests)
default    =  24.83 secproc (35 tests)
Total Test time (real) = 541.61 sec
The following tests FAILED:
61 - test-regression_default (Failed)
62 - test-regression_all (Failed)
Errors while running CTest
Best regards,
Tom

This is really strange, because we have a similar compiler running the tests successfully on Travis:

Compiler
Operating System
Version String

GCC 6.3.0
Ubuntu 14.04.5 LTS
g++-6 (Ubuntu/Linaro 6.3.0-18ubuntu2~14.04) 6.3.0 20170519

It seems that for some reason, your configuration decides to create a different representation for doubles. This is not critical, but strange. I hope this is fixed with #777 and #360.


test: converting a portion of tests from easymock to mockito

another portion of tests from EasyMock to Mockito

Codecov Report

Merging #22 into master will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #22   +/-   ##
=========================================
  Coverage     62.71%   62.71%
+ Complexity      554      553    -1
=========================================
  Files            31       31
  Lines          5023     5018    -5
  Branches        480      464   -16
=========================================
- Hits           3150     3147    -3
+ Misses         1708     1707    -1
+ Partials        165      164    -1

Impacted Files
Coverage Δ
Complexity Δ

...gle/cloud/storage/testing/RemoteStorageHelper.java
63.93% <0.00%> (-0.59%)
9.00% <0.00%> (ø%)

...e/src/main/java/com/google/cloud/storage/Blob.java
82.08% <0.00%> (-0.11%)
29.00% <0.00%> (-1.00%)

...ain/java/com/google/cloud/storage/StorageImpl.java
80.50% <0.00%> (+0.10%)
131.00% <0.00%> (ø%)

...main/java/com/google/cloud/storage/BucketInfo.java
81.18% <0.00%> (+0.13%)
84.00% <0.00%> (ø%)

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 ae0aa99...c1ba1b4. Read the comment docs.


Setting the target to a specific div instead the whole body

is it possibile to implement "containerId" option to let appera notification inside a div instead the whole body?

 Toaster is implemented as singleton so it does not have sense to create multiple toaster directives with different containterIds.

i tried it but the toast appears ever in the same position, top-right of the whole screen

you can define position of toasts by set up of "position-class" or "animation-class" properties. Take a look to this plunker: http://plnkr.co/edit/1poa9A

i solved using this css
#toast-container {
position: absolute;
z-index: 999999;
/overrides/
}
instead of
#toast-container {
position: fixed;
z-index: 999999;
/overrides/
}


Refactor rootston keyboard

Test plan: keybinds such as Ctrl+Shift+E shouldn't work anymore. Keybinds such as Ctrl+Shift+e and Ctrl+E should work. Check that switching VTs works.
Fixes #398

The keyboard command "close" should be seat aware. It should close the focused window for the seat of the keyboard device that executed the binding.

We should probably have a focus list per seat so things like "next_window" will work correctly. Would also affect reverting focus when the focused view is closed for a seat. (these are probably separate issues though).

Is there a good reason why keysym translation is a rootston responsibility? Why is this state not kept on wlr-keyboard itself?

Is there a good reason why keysym translation is a rootston responsibility? Why is this state not kept on wlr-keyboard itself?

The seat takes keycodes, not keysyms. Also, this whole story about using modifiers or not when getting keysyms from keycodes shows that this compositor should be able to customize how it handles keycodes.

Refactored a little bit more, this should address all comments.

👍 looks good.


Include a mention of other Swift 6 source breaking changes

Although the largest compatibility issue in moving to Swift 6 is certainly strict concurrency checking, some developers will encounter a variety of the other (hopefully rare) source breakages introduced in Swift 6.
The migration guide should mention these somewhere, since they are a part and potential stumbling bloc to migration to Swift 6 language mode.

hmmmmm, yes. I'll have to track down which proposals could introduce source breaking changes.
@hborla do you happen know?

Yep!
SE-0192: NonfrozenEnumExhaustivity
SE-0274: ConciseMagicFile
SE-0286 : ForwardTrailingClosures
SE-0337:  StrictConcurrency
SE-0352: ImplicitOpenExistentials
SE-0354: BareSlashRegexLiterals
SE-0383: DeprecateApplicationMain
SE-0384: ImportObjcForwardDeclarations
SE-0401: DisableOutwardActorInference
SE-0411: IsolatedDefaultValues
SE-0412: GlobalConcurrency
SE-0414: RegionBasedIsolation
SE-0418: InferSendableFromCaptures
SE-0423: DynamicActorIsolation
SE-0434: GlobalActorIsolatedTypesUsability

Ok, thank you!
I just looked through a bunch of proposals myself, and there were also source compatibility issues brought up in these:
https://github.com/apple/swift-evolution/blob/main/proposals/0413-typed-throws.md
https://github.com/apple/swift-evolution/blob/main/proposals/0431-isolated-any-functions.md
https://github.com/apple/swift-evolution/blob/main/proposals/0432-noncopyable-switch.md
https://github.com/apple/swift-evolution/blob/main/proposals/0436-objc-implementation.md
https://github.com/apple/swift-evolution/blob/main/proposals/0437-noncopyable-stdlib-primitives.md#source-compatibility
https://github.com/apple/swift-evolution/blob/main/proposals/0438-metatype-keypath.md
I guess if not gated by an upcoming feature flag they aren't enough of a concern?

https://github.com/apple/swift-evolution/blob/main/proposals/0413-typed-throws.md

FullTypedThrows will be an upcoming feature, but the implementation isn't complete and it is not an upcoming feature for Swift 6.

https://github.com/apple/swift-evolution/blob/main/proposals/0431-isolated-any-functions.md

The source compatibility issues mentioned here are outlined for completeness, but you can only really encounter them if you're referencing one of the concurrency library APIs unapplied, like let fn = Task.init, which we doubt anybody is actually doing in practice. Source compatibility issues caused by standard library changes also can't be staged in using upcoming features - upcoming features only control compiler behaviors. I don't think this potential source compatibility issue is worth mentioning in this guide.

https://github.com/apple/swift-evolution/blob/main/proposals/0432-noncopyable-switch.md

It seems this section of the proposal is out of date, thanks for pointing this out! We'll fix this in the proposal.

https://github.com/apple/swift-evolution/blob/main/proposals/0436-objc-implementation.md

My read of this section is that it does not have any source compatibility impact. Source Compatibility is just a standard section of evolution proposals that should always be filled out, even if it says there is no source compatibility impact.

https://github.com/apple/swift-evolution/blob/main/proposals/0437-noncopyable-stdlib-primitives.md#source-compatibility

This is a standard library change that can't be gated by upcoming features.

https://github.com/apple/swift-evolution/blob/main/proposals/0438-metatype-keypath.md

This feature is not for Swift 6.

Ok, so great, so those are nothing to worry about. Thank you!

https://github.com/swiftlang/swift-evolution/blob/main/proposals/0409-access-level-on-imports.md#default-import-access-level-in-swift-5-and-swift-6

In Swift 6 mode, an import is internal by default. This will align the behavior of imports with declarations where the implicit access level is internal. It should help limit unintentional dependency creep as marking a dependency public will require an explicit modifier. […] The Swift 6 change will likely break source compatibility for libraries.

What about SE-0409?

I made an attempt at this here: https://github.com/apple/swift-migration-guide/pull/106


Update ferc1_to_sqlite to migrate XBRL data to a second "raw" FERC 1 SQLite DB.

Background
The first step to integrating XBRL data into PUDL is being able to generate the raw SQLite DB from archived XBRL filings. The ferc1_to_sqlite script can be updated to handle this, as well as still producing the raw DB from the historical VFP based filings.
Design
There will be a separate settings object for managing XBRL data. This will allow the user to independently specify the years/tables they are interested in for both data formats. The script will then handle these accordingly, and produce both raw databases.

is this finished? i thiiink bc i used it :-)

Some issues I've had trying to use this:

I have an old DBF based ferc1.sqlite, and I want to create a new XBRL based ferc1_xbrl.sqlite. I commented out the years in the DBF settings, expecting that it would only run the XBRL conversion, but it complained about the old FERC 1 DB existing and not wanting to clobber it, even though it shouldn't have been in the way of the new DB.
After moving aside the DBF based DB, I tried to run it again, but then even though I had no years in the settings file for the DBF based conversion, it still attempted to extract DBF data, and failed.

It seems like it should be possible to run just the DBF or just the XBRL conversions, and not have them interfere with each other since they create two separate databases, and read from two different sets of inputs.  If there are only years (or tables) for one, then it should only do that conversion.

@zschira In the new settings file I see two separate sections for XBRL and DBF inputs, and then also two separate Settings objects internally, for XBRL and DBF sources. But the XBRL settings appear to be inverting what is specified in the DBF settings (and the EIA and other data source settings).  In the DBF settings we're saying what outputs we want to get (in terms of the PUDL tables and years of data) rather than what inputs we want processed (in terms of the FERC 1 SQLite tables and years).
It seems like it would be simpler to adopt the desired outputs as what is specified, and store the logic as to which SQLite tables need to be processed to generate those outputs within the extract / transform module logic.
That way the user doesn't need to to think about which data comes from which source, and we only have one kind of settings object to track. We'll already need to have logic that understands which source to go to for what years of data anyway.
Is there some other reason why the settings / params got flipped for XBRL that I'm not seeing?

See also #1830
@zschira if you want to subsume this issue inside that epic and close it that would be fine.


Unpin bluesky once all Ophyd devices used in plan_stubs are of appropriate type

Bluesky 1.13 contains changes to the plan_stubs exported from bluesky that they now required devices to comply to the protocols defined in bluesky. However, the devices in Ophyd do not comply to the bluesky protocols: see Ophyd issue.
If we can move the remaining devices- * that are used directly with bluesky plan_stubs, not with bluesky plans *- to Ophyd-async, or resolve the issue with Ophyd devices and type-checked Bluesky plan stubs, we can update to Bluesky 1.13
Acceptance Criteria
CI passes with Bluesky 1.13

Irrelevant due to #830


feat(vue-demo-store): customized product example

Description
closes: #209
see the docs: https://github.com/shopware/frontends/blob/79981745fc832bc20ec893085b0b2ddbcd2a24ac/apps/docs/src/resources/integrations/custom-products.md
Type of change

New feature (non-breaking change which adds functionality)

ToDo's

[x] Changeset file provided read more
[x] Documentation added/updated

Screenshots (if applicable)

Additional context

Is it planed to show the selected options in a cart/mini-cart or somewhere after the customer adds the product?

Is it planed to show the selected options in a cart/mini-cart or somewhere after the customer adds the product?

What about implementing it during https://github.com/shopware/frontends/issues/456 ? because it seems to be more complex task to avoid a lot of if statements for just one use case

Sure we can do it in a separate issue/task.

I guess we need to update the branch here :grinning:

let's move this to examples to avoid demo template complications

ok, it's moved now.


"Internal server error" with some endpoints

Found these endpoints that give "internal server error" when opening them on Risteys:

R18_SUDDEN_INFANT_DEATH_SYNDR
E4_LESCHNYMAN
NEONATAL_JAUND_DRUGS_TOXINS_TRANSMIT_MOTHER_GIVEN_NEWBO

Thanks for the report!
I am pretty sure this is a duplicate of #94 , so I will close this issue and leave the other open.
Though I am stilling your title because it's better :grimacing:


Added short assignment example.

It's probably worth to show different ways for declaring and assignment. Maybe it makes sense to show multiple assignment, also.

@cdarwin Ran go fmt and fixed spelling mistake.


JSON and rdsspy output

Parameter -x says

Output hex groups in the RDS Spy format, suppressing JSON output

But is it possible to have both in once without feeding it thru?

It could be possible as another option. It would make the output invalid JSON though.


[Feature] Fps Counter

I'm using:

Device: TV
OS: Android
Browser: Kiwi Browser

I want to suggest this feature:
... It would be interesting to have an fps or latency counter in the corner of the screen always

Double click on the stats bar and enable "Show stats when starting the game"

Thanks


Getting this error message with import

Final result of import  to TFS 2017 on prem says some thing like this:
[I][23:53:52] Import complete. Imported 2027 items, 20024 revisions (145 errors, 2053 warnings) in 01:06:11.
But got several of these same error messages while importing. Not sure if all the backlog items got imported, but here is the error message. I used config-scrum.json.

[E][23:53:51] Failed to update fields.
[Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionNotExistException] Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionNotExistException: TF26027: A field definition Microsoft.VSTS.Common.ClosedBy in the work item type definition file does not exist. Add a definition for this field or remove the reference to the field and try again.
at Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionCollection.get_Item(String name)
at Microsoft.TeamFoundation.WorkItemTracking.Client.FieldCollection.get_Item(String name)
at WorkItemImport.Agent.SetFieldValue(WorkItem wi, String fieldRef, Object fieldValue)
at WorkItemImport.Agent.UpdateWIFields(IEnumerable1 fields, WorkItem wi):    at Microsoft.TeamFoundation.WorkItemTracking.Client.FieldDefinitionCollection.get_Item(String name)    at Microsoft.TeamFoundation.WorkItemTracking.Client.FieldCollection.get_Item(String name)    at WorkItemImport.Agent.SetFieldValue(WorkItem wi, String fieldRef, Object fieldValue)    at WorkItemImport.Agent.UpdateWIFields(IEnumerable1 fields, WorkItem wi)
[W][23:53:51] ''ATL-2016', rev 4' - not all changes were saved.

@hoodwink we decided to treat this as an error since it cause data loss because the field in question does not have a definition for the target field for the specific work item type. The backlog item should be migrated but the missing fields will not.


The custom environment stops working when playing maps that modify the same environment.

Describe the bug
The custom environment stops working when playing maps that modify the same environment.
To Reproduce
Steps to reproduce the behavior:

I created a custom environment based on the Timbaland environment using Chroma.

In single-player mode, under the Mods > Chroma section on the left, I enabled "Use Custom Environment," selected the custom environment I made, and turned on both "Disable Environment Enhancements" and "Disable Note Coloring."

The custom environment works as expected for most maps. However, when playing maps that modify the Timbaland environment (e.g., !bsr 338af), my custom environment is overridden by the modified map environment and doesn't display.

My game version is 1.37.1.

Heck version: 1.6.3+1.37.1

Chroma version: 2.9.1+1.37.1

NE version: 1.7.0+1.37.0

Additionally, after testing on game version 1.34.2 with the following mod versions, I did not encounter this bug:

Heck version: 1.4.17
Chroma version: 2.7.19
NE version: 1.5.17

Expected behavior
I expect the custom environment not to be overridden by the map’s modified environment.
Additional context
The environment i modified
Timbaland - Estrella.zip

Additional context:
It seems that as long as the map's default environment uses Timbaland, whether it has been modified or not, my custom environment will be overridden.


Document const_hash is unfinalized

If #3074 merges replace const_hash in this issue with hash_unoptimized.
The Hash::const_hash function does not finalize the hash by inputting zero bytes as done in Hash::from_engine, is this a big deal, should it be documented in the function docs?

Yes, it is a big deal if const_hash is only computing a midstate and not actually producing a hash. Its name should be changed to reflect that.

Oh name change again? Not to hash_unoptimized but to something more outlandish like hash_unfinalized_unoptimised you mean?

To avoid confusion we have two const_hash methods. The one on Hash finalizes, the on on Midstate obviously doesn't. So we only need to change that one.
However I wander how do we reflect it naturally. pre_hash? hashing_slice? I think unfinalized is weird to have on Midstate but also the name could be slightly different, if not for other benefits, at least to avoid people having to mention which type it is. :)

I propose hash_unoptimized and compute_midstate_unoptimized .

Damn, I've just remembered I said the wrong thing. Midstate::const_hash has a parameter whether to finalize it or not (OK, that's quite weird) and is private. It really shouldn't be a method on Midstate with that argument but a free-standing one. We could add more methods to Midstate accepting slices of 64-byte arrays but that's probably not super important.


[Missing SNMP Polling Profile] NetApp H615C

Device Vendor: NetApp
Device Model: H615C
System Object Identifier (SysOID): .<IP_ADDRESS>.4.1.8<IP_ADDRESS>
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):

All the essential metrics which will come for Netapp
RACK-MIB
All agentInfo like (QunataStatusProbe,agentBMCVersion,agentBMCGuid,agentServerIdentify,agentChassisStatus,agentPowerControl,agentSystemMA,agentBMCIP,agentBMCMAC,agentBMCIPSource)
All SystemStatus like (voltageStatusOverall,voltageStatusList,fanStatusOverall,temperatureStatusOverall,temperatureStatusList, fanStatusList,powerSupplyRedundancyetc.,)
All DeviceInfo like (ProcessorDeviceStatus, ProcessorDeviceInfoTableEntry, processorDeviceInfoLocationName, etc.,)
All Memory Device Table like (MemoryDeviceStatus, MemoryDeviceInfoTableEntry, etc.,)
All Fan Device Table like (FanDeviceInfoTableEntry, fanDeviceInfoTable, etc.,)
All Temperature Device Table like - TemperatureDeviceInfoTableEntry
All Voltage Device Table - VoltageDeviceInfoTableEntry
All FRU Device Table - FRUDeviceInfoTableEntry
All SEL Device

If there is a New Relic technical support case related to this request, please provide the case number: #00063097
Please provide a public gist with a sanitized (sensitive information removed) SNMP walk of the device. Providing MIB files is not a substitute for an SNMP walk and failure to provide one here will result in delays for closing this issue. The output of these commands shows the "true story" of what a device will respond to in SNMP and is used to ensure that our profiles are efficient and accurate for your devices.
Gist Link: snmpwalk uploaded to case 00063097

Example SNMP walk commands:
# v2c example
snmpwalk -v 2c -t 10 -On -c $COMMUNITY_STRING $IP_ADDRESS . >> snmp_walk.out

# v3 example
snmpwalk -v3 -t 10 -l authPriv -u $USERNAME -a MD5|SHA -A $AUTH_PASS -x DES|AES -X $PRIV_PASS -ObentU -Cc $IP_ADDRESS . >> snmp_walk.out

@BharathCtx
The walk you provided in the case does not have any of the OID's shown in your MIB documentation.  It's possible your walk timed out or was otherwise interrupted, or that you might have been trying to connect to the wrong interface on the appliance.
Further, the sysOID your devices present is the generic one for all net-snmp *nix servers, so the automatic discovery is always going to just assign a generic Linux profile.  For cases like that you would need to manually set the mib_profile attribute on your config file.  Right now it probably has something like
mib_profile: base
provider: Kentik-Default
and you'd need to edit the file like so to force it to use the Netapp profile instead of the automatic one.
mib_profile: "!netapp-hci"
provider: kentik-netapp-hci
Make sure you use the double quotes and ! to get the profile syntax correct.


Brew cask has been deprecated

Use brew install --cask now.

Thank you for spotting this!

Thank you for spotting this!


Adding a property to the DB with multiple values only stores the last property

Fixed by actually declaring the values property key data type as a LIST using the schema setup in index_setup.txt.


pagination-controls id="" causin issue.

=======
Angular 2 version: 2.3.1
ng2-pagination version: 2.0.0
Description of issue:
Spend a whole day figuring out why my pagination control doesn't work. It didn't show page numbering or a previous button. Only next button was there and it also did nothing.
Finally, I removed id="" from my pagination-controller and it works.
Steps to reproduce:
Use id="" like it's used in docs. Also tested this with your example plunker and it bugs there too.
Expected result:
Working pagination with an id.
Actual result:
Only next-button visible.
Any relevant code:
<pagination-controls  id="some_id"
                      (pageChange)="pageChanged($event)"
                      maxSize="9"
                      directionLinks="true"
                      autoHide="true"
                      previousLabel="Previous"
                      nextLabel="Next">
</pagination-controls>

Hi,
Did you try to set an id on the pagination controls without setting the corresponding id on the "paginate" pipe? If so, the docs do state the following:

id [string] If you need to support more than one instance of pagination at a time, set the id and ensure it matches the id attribute of the PaginationControlsComponent / PaginationControlsDirective (see below).

and

id [string] If you need to support more than one instance of pagination at a time, set the id and ensure it matches the id set in the PaginatePipe config.

So I do not think that a working pagination should necessarily be the expected result based on the above.
However, I fully agree that there should be some indication of what exactly is going wrong, along the lines of a console warning ("The PaginationControlsComponent has been assigned the id 'some_id' without a corresponding id being used with the PaginatePipe" or some such).
I'll add this to the next release.

That could be a good thing to add.
But for me, I made sure several times that I have a id: string on my pipe and id="string" on my control. I also tested this on your plunker and it didn't work there either.

If in the pipe you do id: some_id, then it will assume there is a component variable named "some_id". If none is defined, the id will be undefined (I guess).
If it is just a string, then the pipe should read id: 'some_id'. (note the quotes around the string).
Perhaps this is what you are running into with the plunker demo?

That was the reason for it not working. Not sure when I removed those quotes there because I had them before. :D Thanks.


add keylog support using SSL_CTX_set_keylog_callback

Motivation:

In order to debug QUIC with tools like Wireshark, we should have access to connection secrets.
BoringSSL/OpenSSL provides callback method to log keys. https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_keylog_callback.html

Modifications:

JNI functions and class BoringSSLKeylogCallback to support keylog callback
New SSL configuration keylog

Result:

Now it's possible to log SSL connection secrets with configuration keylog

A few more comments... Also did you sign our ICLA yet ? https://netty.io/s/icla

no yet. should I register one? BTW, all reviews are fixed.

Yes you need to sign the ICLA before we can merge this one

I just registered with nickname: lostk1ng


add job to update latest-dev-version file

Add a workflow that updates the latest-dev-version file and publishes it.
For background, we want to start publishing dev releases for pulumi/pulumi at every merge.  Users will be able to download them via get.pulumi.com, or the pulumi GitHub action.  To be able to do this, we need to know the latest version that has been merged and published to the S3 bucket that the get.pulumi.com script reads from.  We'll use the latest-dev-version file added here to do that, similar to how we use the latest-version file to download the latest pulumi version currently.
Related issues (optional)
https://github.com/pulumi/pulumi/issues/14623
https://github.com/pulumi/pulumictl/pull/78 is the corresponding PR to add a pulumictl command for this.

@cnunciato sure, sorry for being light on the details here.  I've updated the PR description to hopefully describe this better.  Also https://github.com/pulumi/home/issues/3010 is the internal issue for this, which also has a link to the design document for more details. I hope that helps, but let me know if you'd like any additional info.

@cnunciato thanks for the review!  I applied all your suggested changes.


is it possible to use Custom structure as Parameter in Program?

As you can see following code, I've use custom struct as Parameter.
It has no any issue in build. but if I try to test, it is shows error message.
IdlError: Type not found: {"type":{"defined":"Candidate"}}
so
node_modules/@project-serum/anchor/src/coder/borsh/idl.ts:94:19)
I've checked this part, and this module check type of parameters. looks don't support custom data type.
pub fn register_candidate(ctx: Context, candidate:Candidate) -> Result<()> {
let vote_account = &mut ctx.accounts.vote_account;
if vote_account.candidates.contains(&candidate) {
Err(ErrorCode::AlreadyRegistered.into())
} else {
vote_account.candidates.push(candidate);
Ok(())
}
}
#[account]
#[derive(PartialEq)]
pub struct Candidate {
pub name: String,
pub age: String,
pub photo: String,
}
is someone there to give me advice?
Best.

It's because the IDL take your Candidate struct as an account cause you have the attribute #[account] and not as a type.
Try to create another struct and just derive it with #[derive(AnchorSerialize, AnchorDeserialize, Clone, PartialEq)] so the IDL take it as a type and then you can use it correctly as a parameter

Please use discord for questions https://discord.gg/GVRw4kHB