Incompatible with 1.6.640

Could you please update the mod so it works with the new Skyrim version 1.6.640?
Thanks in advance!

It will be updated soon, it is just working out what to do with the 353 branch.

Could you please update the mod so it works with the new Skyrim version 1.6.640?

На самом деле, вы не должны использовать эту версию Skyrim, т.к. она просто будет несовместима с большинством модов, которые уже существуют. Используйте 1.6.353, и не выше.

Could you please update the mod so it works with the new Skyrim version 1.6.640?

На самом деле, вы не должны использовать эту версию Skyrim, т.к. она просто будет несовместима с большинством модов, которые уже существуют. Используйте 1.6.353, и не выше.

I know that, but hopefully most mods will be updated in the coming couple of weeks so it should work again.

It will be updated soon, it is just working out what to do with the 353 branch.

It may be worth looking into CommonLibSSE(-NG). Once upstream has updated to the newer game version, updating the mod should be relatively simple if/when a new version is released.
Obviously, it requires having another dependancy and possibly a decent amount of work to move over to it, but it could be a way to avoid worrying about inter-version compatibility.

The 640 update breakage is only sorta breakage, address library updated quickly, and however Arranz gets address mappings should also work. But some data structures in the game were changed, so plugins must now say that they either never depended on the layout of those structures or that they have updated their definitions

@Veradra
I've looked into CommonLibSSE-NG it downloaded over 70k+ worth of files which was around 5gig of data, I mean what!?. So no thankyou rather stick to Visual Studio unless I am making a multi-platform project then I would consider cmake. Feels like you need a degree to understand how cmake works.
@barcharcraz
The addresses were easy to fix and to be honest only a few needed updated. Just need to alter the way in which the universal side works reason for waiting and not being hasty is incase SKSE decided to do another mod breaking update.

Odd, my copy of CommonLib-NG is only 26MB total (including the git history). You need not convert your project to cmake to use CommonLib-NG btw, and actually, if you use it with vcpkg you don't really need to touch cmake at all, vcpkg integrates directly with msbuild/visual studio projects. Still, if you already have a cross-version thing going on I it might be easiest to just continue to do that!

The way I have it designed for Visual Studio 2019/2022 click on your relevant solution file and just build no fraffing around etc even your granny can build it without having to mess around with vcpkg and cmake! Only 1 prerequisite Windows 10 SDK 10.0.20348.0, as there is some form of bug with previous versions which prevents MinHook from building.

will there be an update for the GOG edition as well?

@Razordor
Time of writing this no as would need access to the binary to analyse and no doubt possible structure changes again with SKSE.

@ArranzCNL Do you need only the executable or the full game?
Do you have an email address or some other form of private communication? Thanks!
At this time this this mod pretty much the only major functionality I'm lacking for my GOG Skyrim AE copy :)

Well thanks to Noughtmare's tool we have the addresses for GOG now for Improved Camera at least.
The main reason for the delay of releasing is knowing what to do about SKSE or switch to CommonLibSSE. Due to SKSE doing architectural updates recently.

so, you can start updating it? Sounds great!

Eagerly anticipating the next update! So jarring to look down and just be floating.

I will say what the author perhaps does not want/can't say - feel free to fork the project and continue development. The license permits it.
Otherwise - wait. Tt will be updated or it will not be. Or you can downgrade Skyrim to ver. 353 and use the currently available version of the mod.
Sorry for butting in, but I can see it here as well as in other places (Nexus in particular) that people think they are somehow entitled to get updates simply because they want them.

feel free to fork the project and continue development.  The license permits it.

Non-starter, the mod is closed source. What the license says does nothing if it requires a full decomp anyways.

Sorry for butting in, but I can see it here as well as in other places (Nexus in particular) that people think they are somehow entitled to get updates simply because they want them.

The earlier paragraph is the response I'd rather hear from the author.
I also see those comments everywhere for all kinds of mods—that's a conversation I refuse to join. I'm not expecting an update, but am keeping track of it, so I've attempted to separate myself from those other commenters. Transparency is often a scarce resource and not for the right reasons. If progress is halted, I'd rather hear it directly that I should no longer expect any updates rather than come to that conclusion myself. That's my right to believe, but not something I should expect to be entitled to.
Basically, I recognize transparency is never itself a strict right, and only a privilege. But I think everyone else would be grateful to hear something rather than nothing.

feel free to fork the project and continue development.  The license permits it.

Non-starter, the mod is closed source. What the license says does nothing if it requires a full decomp anyways.

Ah you are right, got misled by the number of forks already in existence.

Source isn't available yet, it will be once released on Nexus under MPL 2.0 license.
I do apologise for lack of updates/news jist of it is the interface changed on SKSE which still needs resolving. Purposely waited to do anything for a couple of weeks due to anymore changes which there were as GOG version came out. Originally ImprovedCameraSE was two seperate repo's but managed to sort the projects out so they could co-exist without hassle under one repo. Then I just lost interest for a few weeks.
Currently testing and fixing the remaining com issues to do with the menu before moving on to getting 1.6.640 and 1.6.659 working. The other backend changes I need to do can wait for the release after.

@ ArranzCNL, is there any way to support you besides saying Thank You! I just updated to 1.6.640 and I didn't realize how important improved camera is to me until I was without it....please keep up the good work, looking forward to using improved camera again

Sorry for the spam, but I came by to say that this mod is easily one of the most amazing mods for Skyrim. I've recently updated my AE install to 1.6.640 and I sorely miss this mod. I'm eagerly looking forward to an updated release and I'd love to contribute in any way.

If you can test hotfix 3 that will be of great benifit. Hoping to have this out in the next few days since the worst part is over with! Contains significant changes for the migration and just plugin design in general imho.

when will hotfix 3 be released?

I have Skyrim AE 1.6.640, but am running SKSE at 1.5.97. Improved Camera 5 works just fine for me (except for a minor graphical glitch which I've reported separately as an issue, as I'm unsure if it's related to the Skyrim version or not).

Aye, I think you've got a boat load of testers ready and willing! Just post it somewhere (in releases?)

Will there be an update for 1.6.640? I thought this most recent update was going to be for 1.6.640 .

@Bulljump That's not possible - 1.5.97 won't work with 1.6.640

@grillzman work is on that now, hotfix 3 was the needed backend changes required for making porting as painless as possible.

No rush. Just making sure I wasn't a moron. Thanks for the reply.

So I saw that reshade is a requirement if I want the customization menu. Is there any way to still use an enb and get just the reshade menu?

@LoneWolf13778 not what this github issue is for, please don't ping everyone on the thread to ask about enbs

@cppcooper sorry never really used github before and wasn't sure where to ask or what to do and also wanted to say I wanted to test for the AE update

Just to give a brief update on progress:

Address ID's 1.5.97
Address ID's 1.6.353
Address ID's 1.6.640
Address ID's 1.6.659
CommonLibSSE-NG library
Drop support for VC16 (Visual Studio 2019)
C++ 20.
Look into crashing issues with menu, under certain conditions. (More important for GOG 1.6.659)

I'll cross off once things are done hoping to have all the address id's by the end of tonight.

Hi,
really impressed with your mod :) quick question - when will the new version release for 1.6.640?
Cheers,
Mark

Updates and checklists are no longer sufficient! GIVE US A LIVESTREAM OF YOUR LIFE!
/sarcasm

because of people not taking the time to read the thread and notice the checklist.
patience is a virtue
to read the thread is to be one with the gods

Oh yeah I see that. I've just been following all activity by email waiting for release.

same, but you weren't the one asking when the mod will be done

I mean, there are only two definite articles left on that list. (The bug sounds like it's probably difficult to reproduce)
For whatever it is worth:
I would hazard a guess that integrating commonLibSSE-NG will take the most time few hours?), as for C++20 I'm very curious what features are even desired.. But alas no source.

most mod authors will only tell people that it will release "Soon™" or "When it's done™" and give zero information on what is going on behind the scenes.
the especially petty ones will say that every time someone asks about the mod releasing, the release will be delayed by a day(some say week or even month)
we should count ourselves luck the we even got a checklist, and patiently wait for the author to let us know when it's done.

I just want to know how much time is left until it releases. I don't want to sound impatient but I can't really play without these type of mods and unfortunately, Joy of Perspective is super buggy and IFPV doesn't even have support anymore if I recall correctly, doesn't work properly either anyways. This one is pretty much the only option left 💀

As I updated the checklist to include Sledgehammer wording, that is what I shall be doing initially with CommonLibSSE-NG. Imagine CLibNG is a square and IC only has a circle slot, yeah... however you can thank gottyduke to get the parts I require. Address ID's would have taken the longest to acquire and this stage now to get the library inside and building.
Once the library is inside and building correctly, should be a 1-2 days to switch the codebase over. It won't be a full release on nexus yet as I will want to redo the CLibNG library and shall release that separately over here as well. (Flatrim with no cmake useless fluff)

Is it almost ready for 1.6.640?

Is it almost ready for 1.6.640?

With love to all, I am coming here to ask everyone to stop posting to heckle the author regarding updates and finishing their gift to the community and to instead prefer silent appreciation and Patreon donations.
GitHub and especially issues is not the place for this type of discourse. These sorts of comments may bury relevant issue discussion and I urge folks to keep the space clean so the author may work and focus at their own pace.
Unfortunately, I'm guilty too. I may be entirely out of place, but I appreciate what this author has given to the community. Let's respect their gift and return it with patience, donations, and workspace cleanliness. I urge using other platforms such as Reddit or Twitter for these sorts of questions and comments.

Is it almost ready for 1.6.640?

With love to all, I am coming here to ask everyone to stop posting to heckle the author regarding updates and finishing their gift to the community and to instead prefer silent appreciation and Patreon donations.
GitHub and especially issues is not the place for this type of discourse. These sorts of comments may bury relevant issue discussion and I urge folks to keep the space clean so the author may work and focus at their own pace.
Unfortunately, I'm guilty too. I may be entirely out of place, but I appreciate what this author has given to the community. Let's respect their gift and return it with patience, donations, and workspace cleanliness. I urge using other platforms such as Reddit or Twitter for these sorts of questions and comments.

I just asked a question, of course I appreciate the author, I would donate to him no problem if I had extra money too, he is one of the few that I would, people are aloud to be curious, he doesn't owe us anything, I know this as a game designer and Modder this whole topic is about it not working with 1.6.640 so I thought I would ask, it is aloud.
have a good day :D

Is it almost ready for 1.6.640?

With love to all, I am coming here to ask everyone to stop posting to heckle the author regarding updates and finishing their gift to the community and to instead prefer silent appreciation and Patreon donations.
GitHub and especially issues is not the place for this type of discourse. These sorts of comments may bury relevant issue discussion and I urge folks to keep the space clean so the author may work and focus at their own pace.
Unfortunately, I'm guilty too. I may be entirely out of place, but I appreciate what this author has given to the community. Let's respect their gift and return it with patience, donations, and workspace cleanliness. I urge using other platforms such as Reddit or Twitter for these sorts of questions and comments.

While I agree with you wholeheartedly I can also see why people would get impatient. As I stated before some time ago, this is the only first person mod that could work for most people, as the other options (JoP and IFPV) are well... Not very functional.
I just hope we, users of 1.6.640 get a working release soon. Specially us with OCD that can't play with these types of mods

Just to give an brief update I am having major issues linking to the library at present, don't know when it'll be fixed as I only have finite free time.

i figured it was finally time to update to 1.6.6 and start fresh.  i was wrong as this mod is essential for first person players :(

awe man im late to the party, but still no update for the 1.6.640??

awe man im late to the party, but still no update for the 1.6.640??

yet.

What is C++ 20 for?

What is C++ 20 for?

Game updated with the Anniversary update, this changed the C++ standard that was used by the game

Ahh, so it is just about being ABI compatible, not using any new features. Thanks for that info =)

If I may ask, if we play without improvedcamera dll now on 1.6.640., will it be possible to add it mid game later on?

If I may ask, if we play without improvedcamera dll now on 1.6.640., will it be possible to add it mid game later on?

In general, you can add/remove .DLL mods mid playthrough.

eagerly waiting for this

checking it everyday ':)

"I am so excited for version 1.6.460, can't wait! 😍😍😍😍

I just want to say to the author that you should not overload yourself because of the impatience of people. If you stick to your pace, it will be better for everyone. The main thing is that the mod turned out to be stable, and the process does not destroy your psyche. People will wait as long as it takes.

yep, please take your time. I'm just glad its going to come out.

Just to give a brief update on what is going on since I have been silent over the past week or so.
Project file is broken (VS project) don't know why. This is easily fixable but it will mean the current released build will be locked to VS 2022 for compilation as I have no intention to get VS 2019 working with it once fixed. (All released binaries are built using VS 2022 anyhow). Mentioning this as source code will be released so it is off the dev branch which can focus solely on NG, this will happen when NG release occurs.
As for the initial NG release it will be sledgehammered in as previously mentioned. Some issues/errors need fixing with NG and also with mINI library (trivial). Fixed initial linking error with NG which was kind of my bad not reading the header files but then again why not name the interface for plugins properly! Source code to this version will be released once I get CommonLib converted to VS 2022 without cmake and vcpkg which is completely pointless imho adding an extra layer of unnecessary complexity to modding a single game just for Windows.
I cannot give a reasonable eta currently as I have a family member in hospital hence my absence.

Completely understandable. Please send them our love and stay safe yourself.

Clion is a thing, and relies soley on cmake. So I wouldn't say completely pointless, given how well clion works. Vcpkg though, that seems extra to me.. Like whats wrong with extern/ submodules?? Works great

Somebody else did already a port to VS 2022:
https://github.com/SkyrimScripting/SKSE_Templates
I can work very well with this port, it is pretty easy to use.

once I get CommonLib converted to VS 2022

Somebody else did already a port to VS 2022:
https://github.com/SkyrimScripting/SKSE_Templates
I can work very well with this port, it is pretty easy to use.

@ArranzCNL ^^^

@siaccarino That isn't a port to VS 2022 but it doesn't not matter as what I currently have works, once the next release is out I'll fix up what I have done and release the source files. It will be up to Po3 and/or CharmedBaryon if they want to include although I'll have the rendition over here.
The purpose in what I am/will be doing with this is to make it as beginner friendly as possibly, I know @cppcooper mentioned Clion which is fine but they are obviously more competent than a beginner. My philosophy is to KIS (keep it simple), average user should just be able to install Visual Studio 2022 and compile code not screw around with other build systems, there is a time and place to use different build systems but I'll reiterate on what I mentioned previously, 1 single game which is Windows only is not one of them!

Just a brief update the sledgehammer approach is completed at least until I run into any other issues.
Implemented a logging system via spdlog (thanks to CLib) which is quite nifty, I won't lie I was cussing at it for a few hours as the syntax is rather weird. End user will only get to experience the file logging side of it. (you won't see a difference)
Next on the agenda is to get the hooks back in place and do up some form of dumper to check addresses are pointing to where they should for various skyrim versions. Once this is completed it is just a case of switching the remaining code to CLib.
Screenshot is from 1.6.640... so soon, can't say how soon other than soon!

Glad to hear we’re almost there! Thank you for all your hard work!On Apr 18, 2023, at 19:22, ArranzCNL @.***> wrote:
Just a brief update the sledgehammer approach is completed at least until I run into any other issues.
Implemented a logging system via spdlog (thanks to CLib) which is quite nifty, I won't lie I was cussing at it for a few hours as the syntax is rather weird. End user will only get to experience the file logging side of it. (you won't see a difference)
Next on the agenda is to get the hooks back in place and do up some form of dumper to check addresses are pointing to where they should for various skyrim versions. Once this is completed it is just a case of switching the remaining code to CLib.
Screenshot is from 1.6.640... so soon, can't say how soon other than soon!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

@ArranzCNL Glad to hear that it's almost ready, thank you for all the work you've put into it. I was wondering though, will the update be put into the ImprovedcameraSE or AE file?

@ArranzCNL Glad to hear that it's almost ready, thank you for all the work you've put into it. I was wondering though, will the update be put into the ImprovedcameraSE or AE file?

I'm assuming you mean the ImprovedCameraSE and ImprovedCameraAE repositories? In that case, it'll most likely be here, since the AE repository has been deprecated in favor of the SE repo. Afaik, everything will be released here for both SE and AE.

@LoneWolf13778 That is a good point I should remove the AE repo! I was thinking of creating NG but decided against it so it will be hosted under SE (here) which makes sense.
I'll do my best to try and make it less confusing as I believe Preview Release 5 final will be under releases and NG under tags. The reason for this is due to source code being released for PR5 which will be on the main branch until I am ready to release NG's source code in which case that will take over main branch, it'll be released on Nexus anyway then as v<IP_ADDRESS>71.
For those not too savvy on github when v<IP_ADDRESS>71 is released, this will be under main branch, preview release 5 will have it's own branch and there will be a dev branch for upcoming updates to main branch - so bleeding edge additions/crashes/fixes. Just to note I will accept pull requests where it makes sense for PR5 as the architecture is similar until <IP_ADDRESS>71 source is released.
I'll update again when I know the hooks are working 100% then it should be 1-3 days for release.

@ArranzCNL thank you for letting me know. I just wasn't sure if the new update and coding would work on SE like AE so was just curious on which repo it would be in. Again thank you for your response and all the work you have put into this mod I know a lot of us appreciate it.

Any update on the progress for updating it to 640?

Everyone: kindly stop replying to this GitHub open issue with shallow comments. For those subscribed, the messages amount to spam. For those unsubscribed, they return to productive conversations nested within unnecessary fluff. This is not a forum thread.
But, I guess any others concerned might as well “watch” only for releases like @K4sum1 has done.

Everyone: kindly stop replying to this GitHub open issue with shallow comments. For those subscribed, the messages amount to spam. For those unsubscribed, they return to productive conversations nested within unnecessary fluff. This is not a forum thread.
But, I guess any others concerned might as well “watch” only for releases like @K4sum1 has done.

Surely you recognise the irony in posting this 3 days after the last comment?

But, I guess any others concerned might as well “watch” only for releases like @K4sum1 has done.

There's also this option, but beware after making new comments it reverts to a regular subscription.

Cheers for this, makes things much simpler.

Surely you recognise the irony in posting this 3 days after the last comment?

No, not at all. Don't think you're so smart with your rhetorical question. It'd be worse if you were subscribed like 40 of us yesterday because you can still see the reply posted 2 hours before my last one, still copied word-for-word in your inbox.
Kind reminder: Deleting your comments is always an option on Github.

Everyone: kindly stop replying to this GitHub open issue with shallow comments. For those subscribed, the messages amount to spam. For those unsubscribed, they return to productive conversations nested within unnecessary fluff. This is not a forum thread.
But, I guess any others concerned might as well “watch” only for releases like @K4sum1 has done.

Bruh i just want improved camera on 1.6.640 Lmao

new ETA?

I have a quick question. I was looking into the mod and found its .ini file. Inside it was a version. I tried changing the version but the mod keep insisting it was the other version. I was wondering if the skyrim version the mod can run on was baked into the mod and not just the .ini file.

I have a quick question. I was looking into the mod and found its .ini file. Inside it was a version. I tried changing the version but the mod keep insisting it was the other version. I was wondering if the skyrim version the mod can run on was baked into the mod and not just the .ini file.

The version in the ini is the minimum and maximum version that .dll supports. Don't change it, not because it'll necessarily do any harm, but because it's utterly pointless.

I have a quick question. I was looking into the mod and found its .ini file. Inside it was a version. I tried changing the version but the mod keep insisting it was the other version. I was wondering if the skyrim version the mod can run on was baked into the mod and not just the .ini file.

The version in the ini is the minimum and maximum version that .dll supports. Don't change it, not because it'll necessarily do any harm, but because it's utterly pointless.

Yeah, I figured that out. I was just hoping for a way to change the version so I could still use it. While waiting on the next version.

Is the update coming in today? Literally held up playing Skyrim today, cuz I've heard the mod update is coming.

Is the update coming in today? Literally held up playing Skyrim today, cuz I've heard the mod update is coming.

Same here :)

Unlikely as I do want to check out the newest CLib-NG and I'm still not quite finished getting some hooks back in place. I do also want to correct some mistakes mainly naming ex. GetSitSleepState should be GetInteractiveState as the states are nothing to do with sitting etc. (They are but cover much more than just sitting!)
I might do a release on discord for testing purposes for the events as this is a very time consuming process.

Unlikely as I do want to check out the newest CLib-NG and I'm still not quite finished getting some hooks back in place. I do also want to correct some mistakes mainly naming ex. GetSitSleepState should be GetInteractiveState as the states are nothing to do with sitting etc. (They are but cover much more than just sitting!)
I might do a release on discord for testing purposes for the events as this is a very time consuming process.

Apologies to bother you, but what discord server would that be on if you do a test release? Could I possibly get a link?

Unlikely as I do want to check out the newest CLib-NG and I'm still not quite finished getting some hooks back in place. I do also want to correct some mistakes mainly naming ex. GetSitSleepState should be GetInteractiveState as the states are nothing to do with sitting etc. (They are but cover much more than just sitting!)
I might do a release on discord for testing purposes for the events as this is a very time consuming process.

Is your discord server private? would like to join and test too!

I would like to join the Discord server too 👀

Me too.

me too

Discord Link I think this is correct.
I am swaying to do a beta release as it is a pain testing various events under certain conditions. If I do... it'll be released on discord and I'll close this thread along with notable changes.

Beta 1 is available via discord.

Discord Link I think this is correct.
I am swaying to do a beta release as it is a pain testing various events under certain conditions. If I do... it'll be released on discord and I'll close this thread along with notable changes.

Sorry to be a bother but I tried joining the discord link and the discord says invalid. So could open a new discord link and could I also have an ETA on release for IMprovedCameraSE which will be compatible with <IP_ADDRESS>.0 Thank you.

@ChrisPC991 discord link is working fine just tested it in my browser. As for official release date cannot give an eta, currently fixing bugs users are finding or that I already know with base game initially. Currently on beta3, should have beta4 out late this evening.


Fix Calls FAQ section

Summary
Somehow the use of sub-subsections (^^^^^^) prevented the questions from getting displayed.
Screenshots

@streamer45 - Isn't RST format FUN!?!? :) When formatting headings, all headings need to follow the same approach across the doc set, otherwise, headings disappear.
Titles are denoted with ====
h1's are denoted with ----
h2's are denoted with ~~~~
h3's are denoted with ^^^^
If levels are skipped, the docs aren't parsed as intended.

Oh wow, thanks @cwarnermm :raised_hands: I definitely experienced that first hand :D

Argh! Sorry all, I was a bit enthusiastic and merged this. LMK if I can revise/redo anything.

@justinegeffen All good, just needed an approval really :)


Update operator-best-practices-advanced-scheduler.md

YAML Syntax corrections

@anantvardhan04 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Create new prototype script (or similar) to test new Class object

[x] Recreate the output of one of the models in the existing prototype.py script
[x] Recreate the output of both of the models in the existing prototype.py script
[x] Clean up our repo by deleting the original prototype.py script once we have completed our changes

Created demo.py


Add documentation for azure service annotations

Azure cloud provider supports a lot of annotations: https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/azure/azure_loadbalancer.go#L36-L83, we should document them.
Also refer https://github.com/kubernetes/website/issues/8154

LGTM


restartBrowserBetweenTests command is skipping retry logic

Hi,
I tried to use the below command in the config file. Retry logic is impacted after adding this command.
Can you please help me to understand what is causing this failure
restartBrowserBetweenTests: true,

21:57:53 [chrome latest Windows 7 #01-3] [21:57:53] I/runnerCli - Cannot read property 'specs' of undefined
21:57:53
21:57:53 [21:57:53] I/testLogger -
21:57:53
21:57:53 [21:57:53] I/launcher - 0 instance(s) of WebDriver still running
21:57:53 [21:57:53] I/launcher - chromelatest #01-5 passed
21:57:53 [21:57:53] I/launcher - chromelatest #01-4 passed
21:57:53 [21:57:53] I/launcher - chromelatest #01-1 failed 2 test(s)
21:57:53 [21:57:53] I/launcher - chromelatest #01-2 passed
21:57:53 [21:57:53] I/launcher - chromelatest #01-0 passed
21:57:53 [21:57:53] I/launcher - chromelatest #01-3 failed 2 test(s)
21:57:53 [21:57:53] I/launcher - overall: 4 failed spec(s)

HI @premkh9
Lemme try to reproduce this and will back to you with my findings
Thanks

Hi, Do you have any update on findings

Hi Amro, can you please take a look at it

unfortunately the logic we use to detect the failed test and do the retry is not supporting the config that uses  restartBrowserBetweenTests

Duplicates #18.

Any solution for this ?


Feature/4962 433 update js docs

Fixes # BLUI-4962 #433

Changes proposed in this Pull Request:

Added js doc for Hero and Emptystate components
Deleted progress bar and badge wrapper components

Screenshots / Screen Recording (if applicable)

To Test:

https://github.com/etn-ccis/blui-react-native-component-library/blob/release/md3/components/src/core/EmptyState/EmptyState.tsx
https://github.com/etn-ccis/blui-react-native-component-library/blob/release/md3/components/src/core/hero/hero.tsx

Any specific feedback you are looking for?

change looks good; didn't run locally.


NetworkPolicy status support - Feature Request

Describe the problem/challenge you have
Kubernetes v1.24 will start supporting condition status in Network Policy API (alpha and feature gate'd)
It would be great if Antrea supports this field to provide feedback for users whether the Network Policy could be parsed, and if not the reason (lack of feature, some error, etc)
Describe the solution you'd like

Update client-go to v1.24 when it's released
Provide feedback on the Network Policy parsing as part of the policy status

Anything else you would like to add?

We have upgraded client-go to v0.24, so if someone wants to work on that issue, it should be straightforward

I see that the plan is to undo this in upstream K8s: https://github.com/kubernetes/enhancements/issues/2943#issuecomment-1372532289
So we probably do not want to implement this at this time. cc @Dyanngg

Yes that's correct. We are undoing this in upstream.
Thanks @antoninbas


Module 1.4 Assignment

👋 Hi @stmichael, in case you'd like to try it again, the goal for 1.4 is to go to http://git-school.github.io/visualizing-git/ and to re-create the image that Eric has created here: https://github.com/github-campus-advisors/Campus-Advisor-Training/blob/master/Module 1/Module 1.4 Assignment.md

Hi @arelia, if that's fine with you I'd leave it at that.
I assume that this assignment was to test my understanding of the branch handling. I've been using git for many, many years now in my life as a developer. I've done far more complex stuff than what is asked in this assignment. I'm used to creating branches, rebasing them (interactive, onto other branches), merging, cherry picking, resetting, bisecting. I know about git internals, how the hashes are being generated. I'd be very happy to not have to do the assignment again :smiley:

Hi @stmichael that's fine! The instructions may not have been clear for this assignment and I've since updated them. If you haven't already, the next step is for you to schedule an interview here: https://calendly.com/arelia/campus-advisor-interview


Drop tip uses offset from bottom

This PR adds Pipette._drop_tip_offset, which is used as a default Z offset when doing a drop_tip(). This is needed to give room for the drop-tip mechanism on pipettes.

Coverage increased (+0.03%) to 94.782% when pulling d6186cbf3f1f78fb3fec7015c66693a566453c46 on drop-tip-uses-offset-from-bottom into 2741bc6f9eaa4e558acf6ef4b8a083c71fbb96b8 on master.


Remove apt cache to reduces image size

Background
We need to update the apt cache during the setup of the EC-2 instance. Maybe we could decrease the size of the final VM files by cleaning up the apt cache at the end.
Acceptance Criteria
Run:

ansible.builtin.apt:
clean: yes
become: yes

ansible.builtin.file:
path: /var/lib/apt/lists/
state: absent

at the end of the setup
See also https://askubuntu.com/questions/1050800/how-do-i-remove-the-apt-package-index
Here a measurement on our image
$ docker run -it exasol/data-science-sandbox:0.1.0-dev-1 bash
root@9fed5334f0a2:/# du -sh  /var/lib/apt/lists/
46M	/var/lib/apt/lists/

Alternatively we could check sudo rm -rf /var/lib/apt/lists/*

For ansible.builtin.apt option become: yes seems to not be supported.

Before: Built Docker image exasol/data-science-sandbox:0.1.0 size 193.95 MB in 0:00:30.
After: Built Docker image exasol/data-science-sandbox:0.1.0 size 178.19 MB in 0:00:39.

For ansible.builtin.apt option become: yes seems to not be supported.

fatal: [ds-sandbox-1700486283]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (ansible.builtin.apt) module: become.

Supported parameters include:
* force

* clean

* allow_downgrade (allow-downgrade, allow-downgrades, allow_downgrades),

* allow_change_held_packages

* purge

* install_recommends (install-recommends)

* policy_rc_d

* cache_valid_time

* package (name, pkg)

* update_cache (update-cache)

* update_cache_retry_max_delay

* force_apt_get

* only_upgrade

* fail_on_autoremove

* lock_timeout

* default_release (default-release)

* upgrade

* update_cache_retries

* allow_unauthenticated (allow-unauthenticated)

* deb

* dpkg_options

* state

* autoremove

* autoclean

@ckunki This seems to be an indentation issue, because become is not a parameter of the command, but of the general task definition.
https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_privilege_escalation.html#become-directives


Move color splash modal, Popover, Chip to react-ions

 (2) React-ions: Move color splash modal, Popover, Chip to react-ions


fix an offense against the style guide.

Refer to API objects without saying “object,” unless omitting “object” leads to an awkward construction.

/assign @bradtopol

Hi @ptux thank you for your contribution. Can you fix the Pod object as well that is right above for consistency? See my inline comment.  Thanks

Actually, @ptux looking at the context I believe leaving in object helps to clarify the association between Pod and Deployment being object types. So I am inclined to leave in object as it provides clarity.

In that kind of meaning, we should change the style guide.

It's a borderline case but it reads ok with with object removed. So let's go with the style guide. I'll merge it. Great job!
/lgtm
/approve

@bradtopol
Thank you.
In my opinion, in the Kubernetes world, user should understand Pod without object.

Agreed!


Update aws-java-sdk-core to 1.12.488

About this PR
📦 Updates com.amazonaws:aws-java-sdk-core from 1.12.481 to 1.12.488
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

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

Superseded by #544.


shovel-config-ts: update types to match documentation

I was attempting to use @indexsupply/shovel-config to make a shovel config in TypeScript but was running into type errors.
Upon further investigation, it appeared that the TypeScript types in the shovel-config-ts subproject were out of date with the current version of the shovel indexer in the repo. Specifically:

Some of the block data options in dig.go were not present in the BlockDataOptions type in Typescript (e.g. tx_contract_address, tx_max_priority_fee_per_gas):
https://github.com/indexsupply/shovel/blob/cb9264ec081c598c1ceee65ff08485e304b111a2/dig/dig.go#L896-L962
https://github.com/indexsupply/shovel/blob/cb9264ec081c598c1ceee65ff08485e304b111a2/shovel-config-ts/src/index.ts#L52-L73

The FilterOp type was missing the filter ops corresponding to a config with filter_arg, as outlined in the docs under the "Filter Fields" section: https://indexsupply.com/shovel/docs/#filter-fields

To fix this, I added the missing options to the TypeScript types. I also added the bun install command to the build instructions, as the build was failing when I initially cloned the repo to test locally since I hadn't installed any of the dependencies.
When testing my shovel config with the updated types in this PR, the type errors were no longer present.

@nathanhleung thank you!

<EMAIL_ADDRESS>https://jsr.io/<EMAIL_ADDRESS>


StakeUpdated event monitor only logging

Having just updated the stake of one of my nodes, I noticed that the event was logged, but the new stake didn't show up in All Players.   The StakeUpdated event monitor is not passing the information through to game.stakeUpdated yet.   This may be covered in the update to capture and process more of the staking events in chronological order.

Possibly trumped by #5


item_by_path not  working as intended on v2.0.0-beta.0

Describe the bug
graph.drive(DRIVE_ID).item_by_path(PATH) is not formatting the URL appropriately.
To Reproduce
Steps to reproduce the behavior:
let graph = Graph::from(&confidential_client_application);
let res = graph
    .drive("<MY_DRIVE>")
    .item_by_path("/path/to/some/folder")
    .list_children()
    .send();

This generates the following URI:
/v1.0/drives/<MY_DRIVE>/root/path/to/some/folder/children

While it should generate the following URI:
/v1.0/drives/<MY_DRIVE>/root:/path/to/some/folder:/children

Error code is a 400 invalid request or 404 not found.
Expected behavior
A successful response when PATH points to an existing file or folder on the drive.
Desktop:

Windows 11
Rust nightly
VSCode

Additional context
Trying to make a backup service for a client using this crate.

Hi,
I'm using this crate for a similar project and if I remember correctly you have to add the colons yourself.
I believe the download file example specifies this in the instructions
download file example
Hope this helps!

Whoops, if it's in the examples, then this is not a bug! Thanks for the info, that is indeed how I do it right now.

Whoops, if it's in the examples, then this is not a bug! Thanks for the info, that is indeed how I do it right now.

Thanks @buhaytza2005 for clearing that up.
@samvv Sorry about that. It is actually something the sdk did do for you in a earlier version but it ended up just better for the caller to specify due to differences whether its for the root folder (top-most level folder) vs any other folder or file. For root you have to specify ":/" if you just want the metadata for only the root and for nested folders its ":/folder:". I think there were other issues but I can't remember off the top of my head right now.
There are ways to do it through different checks of couse. Id be interested to see what Microsoft's SDKs are currently doing for path based items to be honest. Possibly a feature to look at in the future.


Test Clean-Up necessary

The Test
atomic/files.rs
    #[test]
    fn multiple_version_files() {

leaves the artifact {}_cellphoneID in the tmp folder.
Correct Behavior: It should be cleaned up after the test.

Related conversation: https://github.com/ARK-Builders/arklib/pull/72#discussion_r1481248129


Add table plugin

Changes copied to https://github.com/serlo/frontend/pull/1445 so that we can implement it directly in the new design.


Add field flavor when updating the service policy

Add filed flavor_name in ServicePolicyUpdateRequest to support updating the flavor of the service policy.

I will take it.


Conditional modes

I'm interested in using this project for a slightly different purpose.  I'm okay if the car charges off the grid, so long as there is grid power -- the joy of net metering.  What I want is for the limitation to kick in when the power is off, to ensure that the car is never siphoning from the Powerwall.  So:

If grid is up, full power is permitted.
If grid is down:

Do not charge / provide minimum allow current until Powerwall recharges to X%
Track green energy until power is restored

Both of these policies seem to be possible in the current setup, but there's no grid-up/grid-down discrimination.  Is there interest in adding different policies for grid states?

Should be do-able. You will have to do a few things

query the different sources for their 'state': grid on/off and consumption; solar generation; powerwall state
change the TrackGreenEnergy function to implement your policy and provide a singular 'available Amps for charging'.

I did a (slightly less complex) thing to track my home consumption and give my chargers (2) the remainder of the available amps as to now blow my main fuse.

@MikeBishop if you don't have much luck with this, you can feel free to drop an issue on my fork at https://github.com/ngardiner/TWCManager, I've done quite a bit of modularisation of the TWCManager code including a module for Powerwall, it wouldn't take much to track grid status from the Powerwall API and use it as a condition - however not having a Powerwall myself I'd need your help testing it out.

Thanks for pointing to your fork, @ngardiner!  I realized after posting the issue that the base repo doesn't have any Powerwall-specific code and had found the TMC post that contained some, but I hadn't found your fork.
After a cursory look at your new "charging policy" code, I think this fits pretty well.  The "track green energy" path should be fine when running off-grid -- consume nothing if the PW battery is below target charge, consume excess solar output once the PW is charged.  The simplest change would be to make the "scheduled charging" function always say "not scheduled" if the grid is down.  Perhaps in a generic sense, it would make sense for the EMS modules to have a "veto scheduled charging" function?  That would even let you have the option of using "non-scheduled charging" to control what power draw you think is sustainable when running on battery.
My install isn't likely to be for another few months; I'm just figuring out what pieces I'll need to have to automate it.  Happy to try things out with you once I have hardware!


small fixes for svc.yaml and values.yaml

The two main goals of this commit are to simplify the port configuration by adding the missing service port value to the values.yaml with a default value of 80, and also removing the hardcoded port 80 in the service template and replacing it with the $svcPort variable thats used in the ingress allowing the service port to be changed more easily.

Hey!
I had actually done it this way as I saw it used in the ingress.yaml, but I have since learned this was due to the range operations further down in the yaml before the service port section (TIL).
I added another commit that simply sets this to:
{{ .Values.service.port }}
as recommended!

I think it was actually in my update to the NEWS.md for rstudio-pm. Tried a new commit that I think removes the trailing space.


Cannot edit link name when undefined

From a new note (with no search seed title):

Press TITLEBAR (displaying "Untitled").
NOTECONFIG opens.
Press "Edit Link"
Type in link name, hit DONE
Edit Link window still open. Must press "CANCEL"
NOTECONFIG opens. No TITLEBAR change.

Note, if any text is in the note, the edit link is prepopulated with some slug, and has a similar workflow where the only option is to cancel, but then going back to the note, the prepopulated slug is set.

Related to #1034


Fix bug with deploying to heroku when an entry exists with no project

Story: https://www.pivotaltracker.com/story/show/168900055
When a user adds a time entry to Noko and forgets to tag it with a project, it blocks the rake task and Pecas cannot upload that time entry to time.ombulabs.com.

@ercohen14 looks like your last changes broke codeclimate. Would you like to take a look? Thanks.

Closing this PR because it seems unnecessary. I was unable to find any entries that met the criteria for the bug. So I assume it was something else.
I did some digging in production and found this:
irb(main):024:0> start_date
=> Wed, 28 Nov 2018
irb(main):025:0> end_date
=> Thu, 28 Nov 2019
irb(main):026:0> missing_projects = []
=> []
irb(main):027:0> (1..20).each do |page|
irb(main):028:1*   result = client.get_entries(from: start_date, to: end_date, per_page: 1000, page: page)
irb(main):029:1>   result.each do |entry|
irb(main):030:2*     if entry.project.nil?
irb(main):031:3>       missing_projects << entry
irb(main):032:3>     end
irb(main):033:2>   end
irb(main):034:1> end
=> 1..20
irb(main):035:0> missing_projects.size
=> 0
irb(main):036:0> missing_projects = []
=> []
irb(main):037:0> (1..50).each do |page|
irb(main):038:1*   result = client.get_entries(from: start_date, to: end_date, per_page: 1000, page: page)
irb(main):039:1>   result.each do |entry|
irb(main):040:2*     if entry.project.nil?
irb(main):041:3>       missing_projects << entry
irb(main):042:3>     end
irb(main):043:2>   end
irb(main):044:1> end
=> 1..50
irb(main):045:0> missing_projects.size
=> 0


Windows Defender Identifies Release 3.0.1 As Compromised

Describe the bug
When attempting to run GS Studio 3.0.1 on Windows 10, Windows Defender will claim that it is compromised with "PUA:Win32/Puamson.A!ml".
To Reproduce
Steps to reproduce the behavior:

Install GB Studio 3.0.1 via "GB Studio 3.0.1 for Windows 64-bit (With Installer)"
Open GB Studio
Create a default project with no changed settings
Attempt to playtest the default project
Nothing will happen, and Windows Defender will shortly pop up a notification that gbspack.exe has been quarantined because "PUA:Win32/Puamson.A!ml" has been detected.

Expected behavior
The user should be able to playtest their project without triggering their antivirus.
Platform (please complete the following information):

OS: Windows 10
App version 3.0.1

Additional context
According to people in the GB Studio Discord, this does not happen with 3.0.0; I have not been able to verify this.
I have a strong suspicion that #898 is related to this bug.

Verified that uninstalling version 3.0.1 and installing version 3.0.2 of GB Studio fixes this issue, so closing it out.


Ready case studies page for vanilla Docsy

Align how we style the case studies page to work more the way Docsy expects it to.
The way this works is to set menu front matter that Docsy would display in a reasonable way. This change does not change the way the current site displays or, at least, that's what I intend.
Current case studies section index | Preview case studies section index
/area web-development
Helps with issue https://github.com/kubernetes/website/issues/41171

/lgtm
Thanks.


fix: avoid None object de-reference

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area crawler
/area ci
What this PR does / why we need it:
Avoid a None object de-reference in rpm crawler; moreover, bump python docker image to 3.10.
Which issue(s) this PR fixes:
Hopefully fixes test-infra prow job :/
https://prow.falco.org/view/s3/falco-prow-logs/logs/update-kernels/1592034626627440640
Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, maxgio92
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,maxgio92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: f1d52d998ee0517aebbf1b7ab28983aeaa7a24f1


docs: add blog post for migrating to WebContentsView

Publishes proposed doc for migrating from BrowserView to WebContentsView
@electron/docs

Fixed up the lint issues, think this should be good to go!

Looks like the latest deploy failed btw. You can't see the Cloudflare Pages logs online (I think access is restricted), but I see a warning when building locally:
[WARNING] Docusaurus found broken links!

Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.
Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.

Exhaustive list of all broken links found:
- Broken link on source page path = /blog:
   -> linking to ./migrate-to-webcontentsview (resolved as: /migrate-to-webcontentsview)
- Broken link on source page path = /blog/tags/release:
   -> linking to ./migrate-to-webcontentsview (resolved as: /blog/tags/migrate-to-webcontentsview)

The "Check Blog Links" failure is a false positive since it's a link to this blog post which obviously isn't published yet.

Ah ok, gonna switch back to using the full link. @erickzhao , I saw the summer of code pr used a relative path to a new post being introduced in that pr. Did you do anything special to get that to pass?

Did you do anything special to get that to pass?

Ah nvm, I just needed to include .md in the file path


Gives Lawyers Security Headsets

About the PR
they probably deserve it
saul goodman
Screenshots

Changelog

:cl:

fix: Lawyers now have security headsets.

This is the norm on TG and a few other forks as well.
Up to maintainer approval, but I'd get it merged if I could!

It's expected and never seen it be an issue elsewhere, I like this change.

Seconded.
Lawyers already have sec access, so walking in and taking a headset for themselves is just piss easy.


mocha config lacks tools to use localstorage in jsdom

I can no longer check if session storage exists or not using mocha. The root cause is a jsdom update that now throws a security exception when accessing window.sessionStorage
since jsdom 11.12.0 (released in the past june) test runners need to explicitly set a url for jsdom in order to use localstorage or sessionstorage otherwise an exception is thrown:
SecurityError: localStorage is not available for opaque origins
Details on the jsdom release can be found here: https://github.com/jsdom/jsdom/issues/2304
Jest has patched the same issue by adding a letting a field 'testURL' be defined in the config:
https://github.com/facebook/jest/issues/6766
I am currently navigating around this issue by locking my jsdom package to 11.11.0 but this is not a viable long-term solution.
Please let me know if there is a fix for this in the pipeline, or if one already exists that I have overlooked.
Thanks!
PS - steps to reproduce:
it should be possible to make the following test pass with the latest jsdom installed:
mocha --exit --require ts-node/register --require jsdom-global/register ./app/test/*.ts
  @test public async sessionStorate() {
    try {
      if(window && window.localStorage) {
        //have access
        assert.ok("does not break control flow");
      } else {
        //dont have access
        assert.ok("does not break control flow");
      }
    } catch {
      assert.fail("breaks control flow");
    }
  }

@domenic ping!
Fail to see how this is a Mocha problem. You'll need to explain further how we're preventing you from using whatever version of the JSDom package. I see this in one of their unit tests, being run by old version of Mocha unchanged...
  describe("storageQuota", () => {
    describe("not set", () => {
      it("should be 5000000 code units by default", () => {
        const { localStorage, sessionStorage } = (new JSDOM(``, { url: "https://example.com" })).window;
        const dataWithinQuota = "0".repeat(4000000);

        localStorage.setItem("foo", dataWithinQuota);
        sessionStorage.setItem("bar", dataWithinQuota);

        assert.strictEqual(localStorage.foo, dataWithinQuota);
        assert.strictEqual(sessionStorage.bar, dataWithinQuota);

        const dataExceedingQuota = "0".repeat(6000000);

        assert.throws(() => localStorage.setItem("foo", dataExceedingQuota));
        assert.throws(() => sessionStorage.setItem("bar", dataExceedingQuota));
      });
  });

https://github.com/Zirro/jsdom/blob/20ea035bf53911e7b67a680f9bdf09a53f0b8110/lib/jsdom/browser/Window.js#L252-L262

Mocha is using jsdom behind the scenes to mock out window.* globals.
The issue remains, however, that mocha seems to be the one newing up the jsdom object...

Take a look at "package.json". Notice the lack of any "jsdom" package. In other words, we have nothing to do with jsdom...
Attn: @rstacruz
And "jsdom-global" package already has an issue for this problem.
What you want as a longterm fix is for the "jsdom-global" package to interpret the object from the key jsdom-global in your "package.json" as the JSDom ctor's options argument. See example if you don't follow what I wrote.
Full Disclosure: Never used (or seen) either "jsdom" or "jsdom-global" package before.
This is how I would attempt to workaround the problem.
The relevant portion of "jsdom-global" package is the exported function.
Follow their instructions and put the advanced section part in a file named "setup.js". The before hook does the setup (the exported function wraps the "jsdom" ctor), and the after hook does the teardown.
So change the before hook to this:
  var html;    // Unsure what _your code_ needs here -- using `undefined` to trigger default value
  var options = { url: http://localhost/ };
  this.jsdom = require('jsdom-global')(html, options);

Now run Mocha as such:
$ mocha --require ts-node/register --require jsdom-global/register --file "./app/test/setup.js" --exit  "./app/test/*.ts"

Good luck...

Thank you for your insight.
After looking into it, you are (of course) correct. You do not 'new up jsdom' as I initially expected, you simply require() any packages placed in the command line --require flags. The difference is subtle but ultimately mocha works on required libs in such a generic way it would open up a 'pandoras box' of scope creep if you were to make exceptions and begin passing parameters down to required libs.
I will do what you suggest and try importing jsdom-global in my test runner, where I can pass parameters in on initialization.


Deploy fails: An error occurred while installing nokogiri (<IP_ADDRESS>)

$ ./bosh-install-osx azure --name bosh --azure-public-ip xxxx --azure-vnet xxxx --azure-subnet xxxx --azure-subscription-id xxxx --azure-tenant-id xxxx --azure-client-id xxxx --azure-client-secret xxxx --azure-resource-group xxxx --azure-storage-account xxxx --azure-security-group xxxx --azure-ssh-pub-key xxxx --azure-ssh-user xxxx --azure-private-key-path xxxx
deploying your bosh
Deployment manifest: '/var/folders/t3/tm8byt691s31cyz7mswht3pm0000gp/T/bosh-init-deployment012647099'
Deployment state: '/var/folders/t3/tm8byt691s31cyz7mswht3pm0000gp/T/bosh-init-deployment012647099-state.json'

Started validating
  Downloading release 'bosh'... Finished (00:01:33)
  Validating release 'bosh'... Finished (00:00:00)
  Downloading release 'bosh-azure-cpi'... Finished (00:00:19)
  Validating release 'bosh-azure-cpi'... Finished (00:00:00)
  Validating cpi release... Finished (00:00:00)
  Validating deployment manifest... Finished (00:00:00)
  Downloading stemcell... Finished (00:02:47)
  Validating stemcell... Finished (00:00:01)
Finished validating (00:04:42)

Started installing CPI
  Compiling package 'ruby_azure_cpi/0ff57807d95663458f87004d36fa2142fa26e3dc'... Finished (00:00:54)
  Compiling package 'bosh_azure_cpi/66f0454920685dd1289cf5cbaa1204fa3bb43b1c'... Failed (00:00:03)
Failed installing CPI (00:00:57)

Command 'deploy' failed:
  Installing CPI:
    Compiling job package dependencies for installation:
      Compiling job package dependencies:
        Compiling package:
          Running command: 'bash -x packaging', stdout: 'Installing addressable 2.3.8
Installing multipart-post 2.0.0
Installing mini_portile2 2.0.0
Installing json 1.8.3 with native extensions
Installing mime-types 2.99.1
Installing systemu 2.6.5
Installing thor 0.19.1
Installing bit-struct 0.15.0
Installing little-plugger 1.1.4
Installing multi_json 1.11.2
Installing semi_semantic 1.1.0
Installing membrane 1.1.0
Installing httpclient 2.4.0
Using bundler 1.11.2
Installing faraday 0.9.2
Installing nokogiri <IP_ADDRESS> with native extensions

Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi/vendor/bundle/ruby/2.2.0/gems/nokogiri-<IP_ADDRESS>/ext/nokogiri
/Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/bin/ruby -r ./siteconf20160519-47329-ptxv8h.rb extconf.rb
checking if the C compiler accepts ... yes
checking if the C compiler accepts -Wno-error=unused-command-line-argument-hard-error-in-future... no
Building nokogiri using packaged libraries.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/bin/$(RUBY_BASE_NAME)
        --help
        --clean
        --use-system-libraries
/Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- openssl (LoadError)
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/2.2.0/net/https.rb:22:in `<top (required)>'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi/vendor/bundle/ruby/2.2.0/gems/mini_portile2-2.0.0/lib/mini_portile2/mini_portile.rb:3:in `<top (required)>'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi/vendor/bundle/ruby/2.2.0/gems/mini_portile2-2.0.0/lib/mini_portile2.rb:2:in `<top (required)>'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:55:in `require'
        from extconf.rb:397:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi/vendor/bundle/ruby/2.2.0/extensions/x86_64-darwin-15/2.2.0-static/nokogiri-<IP_ADDRESS>/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi/vendor/bundle/ruby/2.2.0/gems/nokogiri-<IP_ADDRESS> for inspection.
Results logged to /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi/vendor/bundle/ruby/2.2.0/extensions/x86_64-darwin-15/2.2.0-static/nokogiri-<IP_ADDRESS>/gem_make.out
Installing macaddr 1.7.1
Installing vhd 0.0.4
Installing logging 1.8.2
Installing faraday_middleware 0.10.0
An error occurred while installing nokogiri (<IP_ADDRESS>), and Bundler cannot
continue.
Make sure that `gem install nokogiri -v '<IP_ADDRESS>'` succeeds before bundling.
', stderr: '+ set -e -x
+ BOSH_PACKAGES_DIR=/Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages
+ cp -a bosh_azure_cpi/Gemfile bosh_azure_cpi/Gemfile.lock bosh_azure_cpi/bin bosh_azure_cpi/lib bosh_azure_cpi/vendor /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi
+ export BUNDLE_CACHE_PATH=vendor/package
+ BUNDLE_CACHE_PATH=vendor/package
+ export BUNDLE_WITHOUT=development:test
+ BUNDLE_WITHOUT=development:test
+ bundle_cmd=/Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/bin/bundle
+ cd /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/bosh_azure_cpi
+ /Users/dwallraff/.bosh_init/installations/2935aab8-4578-491b-6350-0fab4a78b303/packages/ruby_azure_cpi/bin/bundle install --local --no-prune --deployment
':
            exit status 5

this seems like a stemcell issue.
it is defaulting to 3169. the latest on bosh.io is 3232.5 (https://bosh.io/stemcells/bosh-azure-hyperv-ubuntu-trusty-go_agent)
you can change the default by using --go-agent-ver & --go-agent-sha
ill try it out locally too, see if that is indeed the resolution.
side note: i should probably change those flags to stemcell-{sha,ver}


Vulnerability roundup 112: imagemagick-6.9.12-26: 2 advisories [7.5]

search, files

[ ] CVE-2021-3610 CVSSv3=7.5 (nixos-21.11, nixos-unstable)
[ ] CVE-2021-3596 CVSSv3=6.5 (nixos-21.11, nixos-unstable)

CVE details
CVE-2021-3610
A heap-based buffer overflow vulnerability was found in ImageMagick in versions prior to 7.0.11-14 in ReadTIFFImage() in coders/tiff.c. This issue is due to an incorrect setting of the pixel array size, which can lead to a crash and segmentation fault.
CVE-2021-3596
A NULL pointer dereference flaw was found in ImageMagick in versions prior to 7.0.10-31 in ReadSVGImage() in coders/svg.c. This issue is due to not checking the return value from libxml2's xmlCreatePushParserCtxt() and uses the value directly, which leads to a crash and segmentation fault.

Scanned versions: nixos-21.11: efea022d6fe; nixos-unstable: 710fed5a248.
Cc @erictapen

See also: #147882

For CVE-2021-3610 the fix is available since 6.9.12-14 (https://github.com/ImageMagick/ImageMagick6/commit/b307bcadcdf6ea6819951ac1786b7904f27b25c6), see the following oss-sec thread for reference: https://www.openwall.com/lists/oss-security/2023/06/05/1
CVE-2021-3596 was fixed in 6.9.11-31 (https://github.com/ImageMagick/ImageMagick6/commit/27f314e2e6eb44b661e65008ce1ce46b85a5628b)


add README.md to the discharge rata for the Enertech cells

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (1266)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[x] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ flake8
[x] All tests pass: $ python run-tests.py --unit
[x] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

Sorry that I cannot push to pybamm main repository, so I made another pull request here.

That's fine, thanks!


[Routing] Initial public API proposal.

🎉 Initial public API proposal for routing
Part of #543
Summary
Provides the main API proposal which is expected to remain immutable or easier to extend with minimal impact.
This PR aims to:

Validate the API is expressive enough and can be extended to satisfy the use cases we try to implement.
Provide later on a set of base functionality for the different implementations.

Please take a look at this gist for a basic initial consumption of this API. I need to expand on how the agents should consume the route once computed. There I would require more input from the reviewers.
Test it
Via gtest.

[ ] To be implemented.

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if it affects the public API)

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

This change is

A driving set of golden examples would be really useful to have.

Here are some. Please open those with draw.io
routing_golden_examples.drawio.zip

Gently pinging @stonier @liangfok @andrewbest-tri for wrapping up the reviews here as this PR blocks other PRs that go on top :rocket:


mopidy service requires configuration option, prints confusing error message when not present

Issue description
Sorry if I'm missing something obvious, thanks in advance for the help!
I got the titular error message after configuring Mopidy as follows:
  services.mopidy.enable = true;

Here's the trace:
(init)code/bayesian-methods-for-hackers > sudo nixos-rebuild switch --show-trace
building Nix...
building the system configuration...
error: while evaluating the attribute ‘config.system.build.toplevel’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/activation/top-level.nix:246:5:
while evaluating ‘fold’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:29:19, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/activation/top-level.nix:127:12:
while evaluating ‘fold'’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:32:15, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:36:8:
while evaluating ‘showWarnings’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/activation/top-level.nix:93:18, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/activation/top-level.nix:100:16:
while evaluating ‘fold’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:29:19, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/activation/top-level.nix:93:23:
while evaluating ‘fold'’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:32:15, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:36:8:
while evaluating the attribute ‘warnings’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:199:44:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:74:45, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:199:52:
while evaluating the attribute ‘value’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:287:9:
while evaluating the option `warnings':
while evaluating the attribute ‘isDefined’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:319:5:
while evaluating ‘filterOverrides’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:391:21, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:303:18:
while evaluating ‘concatMap’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:79:18, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:397:8:
while evaluating ‘concatMap’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:79:18, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:298:17:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:298:28, called from undefined position:
while evaluating ‘dischargeProperties’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:361:25, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:299:62:
while evaluating the attribute ‘value’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:199:48:
while evaluating the attribute ‘config.warnings’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/boot/systemd.nix:630:5:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:224:10, called from undefined position:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/boot/systemd.nix:630:51, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:224:16:
while evaluating ‘optional’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:175:20, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/system/boot/systemd.nix:631:7:
while evaluating the attribute ‘serviceConfig.Type’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:199:44:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:74:45, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:199:52:
while evaluating the attribute ‘value’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:287:9:
while evaluating the option `systemd.services.mopidy.serviceConfig':
while evaluating the attribute ‘mergedValue’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:314:5:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:314:32, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:314:19:
while evaluating ‘merge’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/types.nix:140:20, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:317:8:
while evaluating ‘mapAttrs’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:198:17, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/types.nix:141:9:
while evaluating ‘filterAttrs’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:115:23, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/types.nix:141:35:
while evaluating ‘concatMap’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:79:18, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:116:18:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:116:29, called from undefined position:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/types.nix:141:51, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:116:62:
while evaluating the attribute ‘ExecStart’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:329:7:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/types.nix:141:86, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:329:15:
while evaluating the attribute ‘optionalValue’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:321:5:
while evaluating ‘filterOverrides’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:391:21, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:303:18:
while evaluating ‘concatMap’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:79:18, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:397:8:
while evaluating ‘concatMap’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/lists.nix:79:18, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:298:17:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:298:28, called from undefined position:
while evaluating ‘dischargeProperties’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:361:25, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:299:62:
while evaluating the attribute ‘value’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/types.nix:146:55:
while evaluating the attribute ‘ExecStart’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/nixos/modules/services/audio/mopidy.nix:80:9:
while evaluating the attribute ‘text’ of the derivation ‘mopidy.conf’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/pkgs/build-support/trivial-builders.nix:10:14:
while evaluating the attribute ‘configuration’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:199:44:
while evaluating anonymous function at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:74:45, called from /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/attrsets.nix:199:52:
while evaluating the attribute ‘value’ at /nix/store/j9j7zrrj13gh8cz7wdj39c92j295jl9i-nixos-16.09pre85931.125ffff/nixos/nixpkgs/lib/modules.nix:287:9:
while evaluating the option `services.mopidy.configuration':
The option `services.mopidy.configuration' is used but not defined

Steps to reproduce

Put the above stanza in your configuration.nix
nixos-rebuild switch

Technical details

System: 16.09pre85931.125ffff (Flounder)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: same as nixos version

I'm happy to make a PR if someone can point out what's going wrong.

My guess is that services.mopidy.configuration is mandatory and that the NixOS module lacks an assertion that can provide users a more friendly message than the current situation.

@bjornfor Looks like that is the case, I was able to successfully run mopidy after adding
configuration = "[core]";

Does anyone know of a nix function to require an attribute?

For NixOS modules, the most appropriate mechanism is "assertions" (AFAIK). See example here: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/misc/redmine.nix#L125-L129

I'm working on a PR now.
@bjornfor How can I test changes to a module? I've only ever created packages before.

Change directory to your nixpkgs git clone and run nixos-rebuild -I nixpkgs=. build.

@bjornfor Thanks so much for your help!

@bjornfor Not to be particular, but that command takes a very long time to run... is there a way to do it faster? To only test what I've changed, rather than build a whole new nix system configuration?

@siddharthist: Not like a build flag or anything like that. What you do is base your changes on the nixpkgs of your current system. That will minimize building.
$ nixos-version
16.09.git.c7860ca (Flounder)
$ cd nixpkgs
$ git co -b my-feature c7860ca
[... edit, test, commit, push to github...]

@bjornfor Thanks again! PR is tested & in.

I don't use mopidy, but another solution to this issue is to simply set a default value (empty string, "") for services.mopidy.configuration. Whether that makes sense for mopidy is another question :-)

If a default value of empty string works, that would be preferable.

Anyway, it's bad style to not have default values for NixOS options, so we should add a default value anyway. Either null or "".

@bjornfor Nice thinking, I added a default vaulue of "".

@siddharthist: Does mopidy work with that empty configuration?

@bjornfor Mopidy will just use default values. My initial config was just that empty header.


minor fix in dcgan example

Originally indicated by; https://github.com/sony/nnabla-examples/issues/62

Thanks @TE-TakuyaYashima.Thanks for pointing the error @stevevista.


Firefox Autocomplete FIX

Please change from type="password" to type="text" at line 78 this fixes firefox autocomplete

👌 Thanks for submit the issue!
I dont want to show the password in plane text, so I've hidden an input to "fool" browsers.
Try it now and tell me if the issue is fixed.
Tested on Firefox Quantum 69.0.1 (64-bit) Windows
Tested on Google Chrome 77.0.3865.90 (64 bits) Windows

I will close the issue because it is considered fixed.


Add copy/cut and paste cells/sheets between USHEET / XLSX within Obisidian

Problem
You cannot paste cells or entire sheets into another USHEET or XSLX file within Obsidian.
It also does not allow copying cells or sheets from external files such as Google Spreadsheets, CSV or XSLX
Solution
Add the ability to copy and paste cells or sheets between files within Obsidian as external files from Google Spreadsheets, XLSX, CSV
Additional details
No response

Yes, and add the ability to just import a xlsx or libreoffice spreadsheet into univer. Also export from univer to xlsx and/or libreoffice

Yes, and add the ability to just import a xlsx or libreoffice spreadsheet into univer. Also export from univer to xlsx and/or libreoffice

We will provide this function in the next version, just hold a second.


Add Rubinius 2.5.8

Please, can anyone take a look at this PR #773 as well? Thanks!

@deepj Thanks always. I merged #773 too.

@hsbt Thanks!


UI readability followup

Followup of #397.
What can be further improved:

[ ] Transaction details panels are not aligned on mobile:

[x]  Name details special pointers tooltips are not left aligned:

[ ] Name details special pointers are not aligned to the name details panel:

[x]  On mobile token events have a typo "arguemnts":

[x]  Oracle events tooltips are not left aligned:

[x]  Token details page links do not have spacing:

The PR is still open there https://github.com/aeternity/aescan/pull/717
Should I implement it in there? @michele-franchi

@janmichek I will have a final look at #717, merge it and then proceed with this followup otherwise #717 becomes very huge and hard to check (which is already).

Name details special pointers are not aligned to the name details panel:

I am no quite sure what you mean by this. I cannot see it from the attached image

Transaction details panels are not aligned on mobile:

Well this is the screenshot from the mobile view where the column width is decided automatically


Ability to include/exclude devices by type

Is your feature request related to a problem? Please describe:
Although I can have (nearly) all devices in HomeKit, often I trust and use YoLink's native applications for certain things like temperature sensors and alerts via email/SMS, etc.
Thus, I would like to exclude some categories of devices from HomeKit to keep things tidy and clean, and also reduce any overhead in manual refreshes, etc.
This might also make sense for the SpeakerHubs themselves, since having them in HomeKit seems to not add functionality.
Describe the solution you'd like:
It would be nice to be able to exclude devices by type (e.g., model number) instead of having to add each ID and hide them. In my situation for example, I would exclude the TS8003-UC (Temp Humidity Sensor).
Describe alternatives you've considered:
The only other method that makes sense to me is what is there today, the ability to exclude by exact device ID.
Additional context:

Interesting idea.  I'll think about it.  The model number is not available through the API, but a "type" is.  Currently I recognize the following types...
  Hub
  SpeakerHub
  VibrationSensor
  MotionSensor
  LeakSensor
  Manipulator
  THSensor
  DoorSensor
  Siren
  Switch
  Outlet
  SmartRemoter
  MultiOutlet
  GarageDoor
  Finger
  Lock

We could exclude based on those type words.

I suppose they choose something that is a bit more human readable than a model number as it is also embedded into the event name as the first part. So if a new revision comes out but shares the same data model, probably would share the same event (e.g., THSensor.Report). That makes sense.

@wojo please try version 1.2.9 and note new excludeTypes and includeTypes config options (best set from the config UI).

@wojo please try version 1.2.9 and note new excludeTypes and includeTypes config options (best set from the config UI).

Works perfectly. My house temperatures no longer show 0 degrees to 108 degrees! I have a lot of THSensor units for fridges, freezers, under sink instant water heater, etc so this is fantastic.
Bonus is that the device overrides work, so I can exclude all THSensor units except one for example. Very nice! 💯

Bonus is that the device overrides work, so I can exclude all THSensor units except one for example. Very nice! 💯

Yup, that is by design.  Thanks for testing.


Ethereum gas limit set to 0 for spending limit tx

Title/Description
Ethereum gas limit set to 0 for spending limit tx -> tx marked as "This transaction will most likely fail. "
Environment

Browser: Firefox
Safe:  https://rinkeby.gnosis-safe.io/app/#/safes/0xaE3c91c89153DEaC332Ab7BBd167164978638c30/
Wallet: MM
App Version: 3.1.2
Environment:

production (rinkeby)

Steps to reproduce
I have a one time ETH spending limit set up for one of the Safe owners.

Send funds
Select EH
Review tx

Expected result
Gas estimation >0 and tx not marked as "most likely" to fail
Obtained result
Eth gas estimation =0 and tx is marked as "most likely" to fail.
(After execution it does indeed not fail.)
Screenshots

This might be fixed by #2040 (?)

I am a little confused: The dialog mentions the Safe nonce and safeTxGas are parameters of a Safe transaction but if I understand it correctly we are executing a Spending limit transaction. To estimate a Spending limit transaction we need to apply different logic then for a Safe transaction, so it is unlikely that #2040 will help in any way.

This wasn't completely addressed in #2040. For a good solution we should face it as a feature. Currently after #2040 changes the advanced parameters form in a spending limit transaction is not shown anymore. Also the warning message is only shown if the transaction is going to fail, so we are behaving consistently (can't be considered a bug)
I created this ticket to plan to resolve this in future releases #2150


my eureka server cluster have a exception

2016-08-08 17:18:08.999 DEBUG 12076 --- [nio-7001-exec-7] o.a.coyote.http11.Http11NioProcessor     : Error parsing HTTP request header
java.io.EOFException: Unexpected EOF read on the socket
at org.apache.coyote.http11.InternalNioInputBuffer.fill(InternalNioInputBuffer.java:152) ~[tomcat-embed-core-8.0.33.jar:8.0.33]
at org.apache.coyote.http11.AbstractNioInputBuffer.parseRequestLine(AbstractNioInputBuffer.java:190) ~[tomcat-embed-core-8.0.33.jar:8.0.33]
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009) ~[tomcat-embed-core-8.0.33.jar:8.0.33]
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672) [tomcat-embed-core-8.0.33.jar:8.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1502) [tomcat-embed-core-8.0.33.jar:8.0.33]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1458) [tomcat-embed-core-8.0.33.jar:8.0.33]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_40]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.0.33.jar:8.0.33]
is it normal?

Hi @lijunyong what environment (tomcat version etc) are you trying to run the server under? Thanks.

@qiangdavidliu tomcat 8.0.33

Hi @lijunyong we do have tomcat8 servers running as well, but I have not been able to repro this issue. Are you still seeing the problem? It might also be worthwhile asking this in the google group to see if the community has any idea. Thanks.


Add title to misc

This PR adds title transcript to the misc directory.

It seems that you submitted this through the website, but this is not a valid transcript. Not sure what happened there.


Documentation for Transaction.deleteRows() does not match behavior

Docs claim that if a callback is omitted, a Promise is returned (see: https://googlecloudplatform.github.io/google-cloud-node/#/docs/spanner/0.1.0/spanner/transaction?method=deleteRows).
When invoked without a callback, nothing is returned. See: https://github.com/GoogleCloudPlatform/google-cloud-node/blob/7ba12d080b499e5461ba51f9e08d559d6c41aaaa/packages/spanner/src/transaction-

Thanks for catching this and reporting. It looks like those docs could use a sweep, as transaction.deleteRows() doesn't do anything asynchronously, it just queues the delete request until transaction.commit() is called. I've sent #2009 with the fixes. Sorry for the confusion.