difference with pkgs/cudatoolkit?

From the README it's not clear to me what the difference is between this package and cudatoolkit from the main Anaconda channel. Are they the same (just providing different versions at the moment), or is this a superset?

@rgommers, as stated in README file

The toolkit includes GPU-accelerated libraries, debugging and optimization tools, a C/C++ compiler and a runtime library to deploy your application. This package consists of a post-install script that downloads and installs the full cuda toolkit (compiler, libraries, with the exception of cuda drivers).

So, when you install cudatoolkit-dev, in addition to libraries; you get the compiler (nvcc), the profiler (nvprof), etc. .  In other words, you get the exact outcome as what you would get when installing cudatoolkit by following installation steps from https://developer.nvidia.com/cuda-downloads.
On the other hand, when you install cudatoolkit from the main Anaconda channel all you get is a set of pre-packaged libraries (no compiler, no profiler, etc).

Thanks @andersy005!
It would be helpful to add that to the README. Especially given that https://anaconda.org/anaconda/cudatoolkit doesn't have any README or docs link, it's not obvious that "all you get is a set of pre-packaged libraries" from cudatoolkit.

Great! I will make sure to update the README for cudatoolkit-dev.

I am updating the readme (https://github.com/conda-forge/cudatoolkit-dev-feedstock/pull/37)  with your comment here @andersy005


Mapping Docker folder to custom local folder on separate partition

For boot2docker on OSX, I overrode the boot2docker command to mount the volume in the Dockerfile (/data) to a custom partition that is case sensitive.
Would it be possible to add this as a feature in Kitematic?

+1

Anyone know if this is getting anywhere?

That should be covered with the PR https://github.com/kitematic/kitematic/pull/1202. Please, take a look to make sure that's the same behavior that you want to.

This is now available using Docker for Mac/Windows


Automate swagger ui services

Hi,
I would like to know if there are any tools available to automate the services exposed by swagger-ui
which could be integrated with the build process

Don't even know what this question means?

I wanted to know if there is any tool that can read the swagger spec file.. and automatically populate  the input params, fire and test if the services work.

There might be. I'm not to sure. Have you looked at Postman?

That seem like an independent tool. I would like something that could be integrated with the Maven build.


Merge master into docs

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7335/
Test FAILed.

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/7338/
Test PASSed.

alluxio-bot, merge this please

alluxio-bot, feature-merge this please


ViewCoordinates does not change 3D Handedness

Describe the bug
The ViewCoordinates docs suggest that the global handedness of the coordinate space can be changed via logging ViewCoordinates to the root entity ala:
rr.log("/", rr.ViewCoordinates.RIGHT_HAND_Y_UP, static=True)

or
rr.log("/", rr.ViewCoordinates.LEFT_HAND_Y_UP, static=True)

However, both of these settings yield exactly the same final scene coordinates, as if the coordinate definition is only changing the orientation of the root object, and not also its scale.
Expected behavior
Setting the ViewCoordinates should cause all aspects of the 3D visualization to adhere to the new coordinate system formalisms, in terms of both handedness and orientation.
Screenshots
Setting rr.ViewCoordinates.RIGHT_HAND_Y_UP

Setting rr.ViewCoordinates.LEFT_HAND_Y_UP

Desktop (please complete the following information):

OS: Windows 11

Rerun version
0.18.2
Additional context
Working with OpenCV's coordinate systems is painful enough without having to swizzle everything back and forth for visualization 💀

Rerun doesn't yet support left-handed coordinate system… though I notice our docs doesn't mention that 🤦
Sorry for the confusion. I'll update the docs right away. In the meantime, this is the issue for tracking left-handed coordinate system:

https://github.com/rerun-io/rerun/issues/5032

Right now our ViewCoordinates are generally quite confusing. We have a ticker for improving things:

https://github.com/rerun-io/rerun/issues/2663

Docs updated in

https://github.com/rerun-io/rerun/pull/7690

Additional context
Working with OpenCV's coordinate systems is painful enough without having to swizzle everything back and forth for visualization 💀

Doesn't OpenCV use a right handed coordinate system?

Additional context
Working with OpenCV's coordinate systems is painful enough without having to swizzle everything back and forth for visualization 💀

Doesn't OpenCV use a right handed coordinate system?

Heheh, funny you mention that...
Shortly after making this issue, I got enough visualization in to discover that my points were being triangulated behind the cameras instead of in front of them.   Eventually I pinned it down to dealing with the inverse of the position/rotation, causing my rays to converge behind the cameras, giving me mirror-universe triangulations.  Inverting the transforms gave me good, right-handed universe points and now everything lines up.
So the "need" for a left-handed system was my fault after all, and rerun saved my butt for debugging 😅.
Thank you for looking at this and keeping me honest, and I look forward to using rerun more as time goes on 👍

@zalo: Awesome to hear that you ended up solving the issue! In prior lives I've spent so many hours debugging coordinate system transforms and projections it makes me shiver thinking about it.
Btw, very unsolicited but still, my hardest won advice on this topic (other than visualize all the things): always name any transform variable in your code with the scheme a_from_b, where a and b are the names of coordinate spaces. For example, don't call it intrinsics, call it image_hom_from_camera (or similar). Adopting this scheme and sticking to it very strictly has saved me so much time.
Please do feel encouraged to keep opening issues when you find something a bit off (or even just annoying) or if there is something you think we could add that would make a difference for your use case.

That's great advice... so much so, that I already had the intermediate matrix named cam_to_world... but my sleep deprivation when parsing the calibration json was stronger 😄
Should any unfortunate soul find themselves in this thread after running into a similar issue (more likely than I think 💀 ), don't be fooled by the rvec/tvec arguments in the projectPoints function; here is a magic incantation to use OpenCV's rvec's, tvec's, and fisheye module to project points from the origin coordinate space to the camera-image coordinates that you got from calibration:
def rtvec_to_matrix(rvec=(0,0,0), tvec=(0,0,0)):
    "Convert rotation vector and translation vector to 4x4 matrix"
    rvec = np.asarray(rvec)
    tvec = np.asarray(tvec)

    T = np.eye(4)
    (R, jac) = cv2.Rodrigues(rvec)
    T[:3, :3] = R
    T[:3, 3] = tvec.squeeze()
    return T

def matrix_to_rtvec(matrix):
    "Convert 4x4 matrix to rotation vector and translation vector"
    (rvec, jac) = cv2.Rodrigues(matrix[:3, :3])
    tvec = matrix[:3, 3]
    return rvec, tvec

cam_to_world = rtvec_to_matrix(cam_rvec, cam_tvec)
cam_pts = (points_3d @ cam_to_world.T)[:,:3] # Put the points into the local space of the camera
image_space_points = cv2.fisheye.projectPoints(cam_pts.reshape(1, -1, 3), np.zeros((3)), np.zeros((3)), camera_matrix, dist_coeffs)[0].squeeze()


experiment results

I try to reproduce the exp results on M4 datasets, but I get pretty bad performance, it's far away from the performance in the paper .I just simply run the short-term forecasting scripts for M4 datasets, so I want to ask there is something wrong in your scripts or how can I get the right results

Which subset and which model did you get bad performance? We have just tested our model from our Github repository, and the result is:

Can you paste your running log for detailed analysis?

I run the Informer model on the M4 dataset by your scripts, here is the results. I run the scripts twice ,and get the same performance. Although I know the Informer model may be worse than TimesNet, the results are so ridiculous

M4 dataset include various patterns of time series. Some sub-dataset have large mean and variance, so it might be difficult for some models to learn the representation.
In our latest published version, we use nomalization methods proposed by Non-stationary Transformer to improve these baselines, including Informer, Pyraformer and Reformer.


how to get  CASIA NIR-VIS 2.0 dataset?

thanks for sharing your work.Can you share your train dataset  of " CASIA NIR-VIS 2.0" ?thx!

You can find the dataset from https://github.com/ZhaoJ9014/face.evoLVe.PyTorch#Data-Zoo. Thank you for your interest in our work.


Repository not tracking remote origin when creating new local branch based on existing remote branch

User story
As a developer
When I clone a remote branch I expect it to automatically enable remote tracking and pull the remote changes
so that I can start working on and committing to the remote branch as simply as possible
Observed behavior
When I click on a remote branch that does not exist locally, a new local branch is created, but the local filesystem does not match the remote filesystem. Also, the local branch does not seem to be tracking the remote branch.
Expected behavior
When clicking a remote branch, a new local branch of the same name would be created. The locak branch will be set to track the remote branch, and all files/changes in the remote branch will be pulled into the newly created local branch.

:+1:

Yes, I have the same problem ! - I'm pretty sure this used to work flawlessly about 6 month ago .. !?

Hey all, I added the --track flag in a pull request. Please test and let me know if it works for you.

The --track, or -t, flag was the recommended solution as per the following sources:

http://stackoverflow.com/a/10358772/1191545
http://stackoverflow.com/a/14436240/1191545

As a convenience, --track without -b implies branch creation
If no -b option is given, the name of the new branch will be derived from the remote-tracking branch
https://git-scm.com/docs/git-checkout

So, the basic command for checking out a remote branch and setting up tracking seems to be:
git checkout --track remote/branch


[typescript][02.echo with counter] Fixed minor typos for README

Proposed Changes

Minor changes to typos and minimal structural changes.
Changed & to && since only one ampersand makes the commands run asynchronously thus fail due to npm start being executed before npm i can finish installing the dependencies.

@dfavretto The section has been implemented.

Closed due to #663


Fix crash in ssl3_finish_mac

This should fix issue #2113
I think not having a return code for ssl3_init_finished_mac
is the root cause of the problem, together with the fact
that s->s3->handshake_buffer is used as a status flag
everywhere.

Yes, the patch is against 1.0.2, and is still current.
In 1.1.0 and master the finish_mac function has a return value; so it looks
as if it was fixed there in a similar way and was not back-ported yet.

Ping. Needs a second team review.

Merged. 348681ff2b30453eb03ce2d83022ef069d86877d

@levitte - did you push?

@levitte - did you push?

Errr, yes

And now for real!


Update interested-technical-writers.md

Add Lion's Way.

@googlebot I signed it!

@googlebot I signed it!
On Tue, Mar 30, 2021 at 6:04 AM google-cla[bot] @.***>
wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgoogle%2Fseason-of-docs%2Fpull%2F105
for more info.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/season-of-docs/pull/105#issuecomment-809910868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIAG7VEL47NPLOT67HUARZ3TGFLWXANCNFSM4Z4GBX2Q
.

@googlebot I signed it!

Hey @CynthiaPeter I am not clear how you got onto this pull request, but since there is a bot that needs to confirm who is on the contributor license agreement (CLA) it is holding up our ability to get it accepted! I think that what you need to do is to make your own fork from the main (just editing the original will start that process). I am pretty determined to get this done tonight so I am looking into just closing this PR and opening a new one.


Change flexbox spacing between the child divs of the Home component

There is no space between "INDIA COVID-19 TRACKER" and "STATISTICS BY STATE" titled div in laptop view
To Reproduce
Steps to reproduce the behavior:

Go to 'https://www.covid19india.org'

Expected behavior
There should be space between above mentioned two divs
Screenshots

It should be like this

I am also adding pull request to solve the same

This issue is resolved right?


fix: unexpected scroll

Fixes in this PR:

[x] The Main sticky container was skipping the verticalScrollbarWidth
[x] unexpected scroll bar issue
[x] adjuster hit area displacement issue (it was not considering the verticalScrollbarWidth)

https://github.com/qlik-oss/sn-pivot-table/assets/29652890/19631b3f-542f-4220-b5ac-6975768560ce

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


css fixes

So i was trying to use it a bit more for a styleguide and there're a lot of css quirks that have to be adressed. Not sure if they should go into xplorer theme and then backported or not, so feel free to close if not relevant @FinalAngel

LGTM


test_linearizer_failures: add failing kernel from GPT2 CUDA

this bisects to #3530 which I think caused the uops to be incorrect on all platforms

@patosai could you take a look at this regression and see what fix can be implemented?


feat: Add trib.al to trackers

Fixes (Links to issues fixed by this PR): None
Description: Adds trib.al to tracker list
Checklist:

[x] I made sure there are no unnecessary changes in the code*
[x] Tested on Chromium- Browser OS
[x] Tested on Firefox

Unshorten.me supports both, @1fexd please re open this PR for MV-3

This has a lot of conflicts it would be easier to close this PR and open a new one with the changes

Hm, does the tracker list make sense at all? Aren't there these huge lists out there?

We bypass tracker short links which lead somewhere not google adsense stuff. Tracker links show a page like this when clicked on


Some Struggles

I have read the read me text, yet I still don´t know how to add a song :‹

Its pretty simple. If you already have a song pack, just drop it in the USTs folder in the ULTRAKILL folder, otherwise copy the template and replace the parts you want in template.ust . Here is a working one if you want to look at. It replaces the song in 0-1
Example.zip
Your .ust file should never be called template.ust, otherwise USTManager will ignore it. Also you don't need an icon but you can add one anyway, just make sure it's called icon.png


A suggestion about elpa repositories.

Hello Purcell. I would like to make a suggestion but the government blocked internet. So the Twitter is not available. So I had to say here...I'm sorry for my reckless and very poor English...
Saving your presence, I think you should completely disable using  http and should use https. Because http is very fragile. So http is vulnerable to network attacks.
Just yesterday, our company was attacked by MITM, all GNU elpa (using http by default) packages were replaced with the wrong data. We reinstalled emacs and your configuration, the results have not changed anything. All GNU elpa packages are not available. but all melpa packages (using https) are not affected in anyway...
Until we solved the attack, these packages are all available.
So I think the http is also very insecure even as a download link now. I hope you can completely disable http in your configuration.
As far as I know, the computer / OS without ssl almost does not exist now.
For Windows users, I think you should let them solve their own problems. It is not difficult anyway.
The above is my advice. I just hope that everything is safer. If I created some useless advice for my ignorance, please forgive me. And...
Pardon me my offence!
Thank you very much.

Makes sense, done. Ideally, Emacs would make "https" the default for this.

The org repository is not use ?
But you still only force use ssl for gnu  ... ...
Well, thank you very much.

The org repository is not use ?

Ah yes, that seems to work too. Updated.

Well……Thanks.
Do you write the code in this way for compatibility?
Finally ask you a question:
Before I get your suggestions , I am dealing with this:
Delete:

...
;; We include the org repository for completeness, but don't normally
;; use it.
(add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/"))

(defconst sanityinc/no-ssl (and (memq system-type '(windows-nt ms-dos))
                                (not (gnutls-available-p))))

;;; Also use Melpa for most packages
(add-to-list 'package-archives
             `("melpa" . ,(if sanityinc/no-ssl
                              "http://melpa.org/packages/"
                            "https://melpa.org/packages/")))

...

Add:

...
;; We include the org repository for completeness, but don't normally
;; use it.
(add-to-list 'package-archives `("org" . "https://orgmode/elpa/"))

;;; Also use Melpa for most packages
(add-to-list 'package-archives `("melpa" . "https://melpa.org/packages"))

...

Will be there anything wrong with that?
Thank you very much !

@purcell
Yes. The org-mode's official https repository is not unreliable at all ! I’m using the emacs-china repositories now, so I forgot it...
I'm sorry to have trouble you...
And...
Would you like to answer the above comment question?
Will there be any problem "Completely abolish" http support like me ?

Will there be any problem "Completely abolish" http support like me ?

Yes, in general, but it's unlikely to be a problem for you. On certain Windows systems, Emacs does not support https. Those "if" conditions were added for that reason.

Thanks

Well...I want to do it (As in the above forced to abolish http) in my fork, and will write some warnings like “For Windows users, I think you should can solve ssl problems by yourself, It is not difficult anyway.”,
and add your link:
http://חנוך.se/diary/how_to_enable_GnuTLS_for_Emacs_24_on_Windows/index.en.html
in my README.org.
I am very disgusted with Windows. So I DO NOT want to support Windows and its users.
Did this infringe your copyright ?

You can do what you want in your own fork: licence is BSD. https://github.com/purcell/emacs.d/blob/master/LICENSE

And....

The emacs-china https repositories I using are very reliable.
but the gnu and org-mode’s official https repositories are unreliable...
Don't know why, the GNU Project doesn’t seem very welcome https.
Probably because of “Freedom is not Free”...
I’m so sorry to have trouble you...


Use browser instead WebView to avoid entering login/password

Hi, I'm not deep in Oauth theme, so maybe I misunderstand something.
It would be cool if app can authenticate without entering login/password (if they were entered before) - just press Agree button.
As I understand it's not possible because WebVew's have not access to browser sessions/cookies, but we can use OS browser instead.
So, why to use WVs but not browser?
Thanks,
Victor

i really have this problem.!!!!
PLEASE SOLVE THIS ISSUE


[feature_request] Additional options for Ariston Velis

Hi, if it's possible add options for Velis version:

set number of "showers" (if I understand correctly it's number of people who use boiler)
enable "program_mode" - when boiler activated by day/time
enable "boost" option

thank you =)

Hi.

You can not set the number of showers. This only means that how many people can have a shower with the current water temperature. See the official phone app.
I don't want to enable the program_mode (you can already choose this mode from the operation list, but you can not program it). Because it is complicated and you can create an automation for the same behavior with HA.
My Velis don't have boost option. I do not know how to do that.

Is it possible to have a "climate" entity for velis?


Add ability to have plugins exist in a directory besides /mods

Mumfrey wants me to post these things here rather than on the main forums. So. As I have already discussed here:
https://forums.spongepowered.org/t/omg-youre-getting-rid-of-plugins/10689/49
The file/directory locations and launch mechanism changes for this Sponge project vs what came before seem to have been largely unnecessary.
Yes, Sponge is a mod. So what? Both MCPC and Cauldron were mods too, and they worked just fine as a launch wrapper loading before Forge.
The semantic argument for these drastic changes vs Cauldron does not hold any water for me, if it introduces unnecessary complexities for modpack server admins.
So how much work would it take, to go back to the old Cauldron directory structure, so that ONLY modpack data occupies /mods and /config, to once again allow extremely easy delete and replace modpack upgrades?

Changing your title as, unlike you like to imply, there is no conspiracy here against providing the option of a plugins directory.
Regardless of what you may think, we've heard your feedback and will act upon it. Mumfrey has said this and now you have confirmation from a Sponge Leader. Be patient.

Yes, Sponge is a mod. So what? Both MCPC and Cauldron were mods too, and they worked just fine as a launch wrapper loading before Forge.

A mod is defined by the mechanism loading it. Cauldron wasn't loaded by FML, it was just a file modification of the game. SpongeForge is different...without Forge SpongeForge will never be loaded. While we'll get that plugins directory added, this part isn't changing: you install Forge and put SpongeForge in the mods directory.

I already started working on this and it works fine. Just haven't merged yet since I've been busy with other things. I will get to it when I have a spare second.
Also, I would have thought that the take-away from the forum discussion would be that being less combative is more productive. Please try to remember we're all people on the other end of the screen; we are on the side of server admins, and don't just make implementation decisions out of spite.

I'm talking about full separation as it was before, including moving sponge out of the mods directory completely. Is there a way to tell forge to look somewhere else for mods within Forge itself, and without involving Sponge? I am not a programmer so I cannot answer these things.
"Forge, look for additional mods during startup in here:"  /root/Sponge/
Put sponge.mod in /root/Sponge/Sponge.mod

No, forge does not support that. The required information is inside the Sponge mod. You would need some mod to tell forge that.

In the old system where Cauldron was launched first, how did Forge know where/when to inject Cauldron's mods? Is it possible to do that again? Is Forge itself significantly changed from the 1.7 days to now, that the old launch Sponge first model is now impossible?

@DMahalko: You keep referencing 'the old system', and 'how it was before'. I wanted to clear something up:
While some of the Sponge developers have worked on projects such as Cauldron before, Sponge is a new, separate project - it's not a "successor" in any sense. Things like using the mods dir for both plugins and mods are not the result of a deliberate decision to do things differently than other projects. Rather, it's the result of the fact that Forge/FML treats plugins like mods, for the most part. Differences between the handling of plugin and mods are usually the result of deliberate action by Sponge, not inaction.

I'm talking about full separation as it was before, including moving sponge out of the mods directory completely. Is there a way to tell forge to look somewhere else for mods within Forge itself, and without involving Sponge? I am not a programmer so I cannot answer these things.
"Forge, look for additional mods during startup in here:" /root/Sponge/
Put sponge.mod in /root/Sponge/Sponge.mod

I already pointed out on the forum thread that yes, you can put mods wherever you like and specify them to forge on the command line. In your scenario, you can put the sponge jar wherever you want and load it explicitly. Since this is already supported natively by FML, we won't be altering this behaviour.

In the old system where Cauldron was launched first, how did Forge know where/when to inject Cauldron's mods? Is it possible to do that again? Is Forge itself significantly changed from the 1.7 days to now, that the old launch Sponge first model is now impossible?

I'm going to keep saying this until it sinks in: I **already wrote functionality to do this but it's not merged yet. Since it was already agreed several days ago that this would be added, I honestly do not understand what the problem is???

In the old system, Cauldron was the server, so it was in charge of everything, and did not use Forge for loading plugins. Now, Forge is the server, and it is in charge of everything, including loading plugins. This is a decision that was made long ago and is not likely to change.
N.B.: Obviously none of this applies to SpongeVanilla. That should prove easier to change.

Mumfrey: Ah, I did not realize you were talking about being able to move the Sponge.mod itself. I thought that discussion was in regard to moving the PLUGINs for Sponge to another location so Forge can still find them.

Mumfrey: Ah, I did not realize you were talking about being able to move the Sponge.mod itself. I thought that discussion was in regard to moving the PLUGINs for Sponge to another location so Forge can still find them.

I showed you the other day on the forum thread that moving mods elsewhere is already fully supported by FML, you just have to specify them explicitly using the --mods command line argument or use the maven-style declaration. What you can't do is add extra "search locations" (such as the mods folder) where jars can be indiscriminately dumped and automatically loaded.
So, if you don't want to put the sponge jar in the mods folder, the simplest solution is just load it on the command line, then with the feature I've added which gives you a configurable plugins folder as an additional search location (mods is still processed as normal) you dump all your plugin jars nice and separate from your mods and Robert is your father's brother.

Okay. So, in summary, full isolation will now be possible?
/root/minecraft.jar
/root/Forge.jar
/root/Sponge/Sponge-1.0-RELEASE.jar
/root/Sponge/Sponge.cfg
/root/Sponge/plugins/
/root/Sponge/plugin-configs/

For the record, this isn't ever going to be "the same as Bukkit", because this isn't Bukkit. However what it does provide, is a nice clean separation for those that want it, and the time-honoured "dump everything in mods for those who don't. There is just no distance in doing things the way Bukkit did because it had its own collection of problems and we - by virtue of starting a whole new project - have an opportunity to correct that.

/root/Sponge/plugin-configs/

Plugin configs go in sub-folders under config, there's not really any organisational issue with that so creating a new folder just seems redundant. Configs are intrinsically easier to organise as they're much less volatile in nature than mods. It's also a bit late in the day to change this one since it's not an additive change (like adding the extra search folder) and thus can't be made backward compatible.
The argument for moving the configs just isn't as compelling as the one for adding an extra plugins search folder.

Oh and further, there's still absolutely nothing stopping you using the maven-style layout for both mods and plugins, which would be superior to pretty much all other solutions full stop, so there's that.

I also want to point out that SpongeForge will always go into mods. It is a mod, it is loaded by Forge, it is not a wrapper like Cauldron was.

I also want to point out that SpongeForge will always go into mods.

It doesn't have to though, that's the point. If you specify it on the command line it can go literally anywhere you want.

@Mumfrey
There was no discussion changing where SpongeForge is installed. We only discussed where plugins go.
That is another but related issue altogether.

@Mumfrey
There was no discussion changing where SpongeForge is installed. We only discussed where plugins go.
That is another but related issue altogether.

This isn't up to us, it's just built right into FML, no changes are required. If someone wants to put the SpongeForge jar somewhere else, they can.

@Mumfrey
Ah, completely forgot about that. Great point! Can you put the line here to specify it so @DMahalko can use that to put SpongeForge where-ever he wants?

All the docs are available here: https://github.com/MinecraftForge/FML/wiki/New-JSON-Modlist-format This includes details on the maven-style mod format.

we might want to put some info on that format on our docs site

The compelling reason for separating plugin configs from mod configs is that when you do modpack upgrades the best thing to do is nuke /config from orbit and install the new one from the modpack upgrade.
Which I explained here:
https://forums.spongepowered.org/t/omg-youre-getting-rid-of-plugins/10689/47
We cannot simply nuke /config if we now have to pick through 30 plugin config subdirectories mixed in with the mod configs.

We cannot simply nuke /config if we now have to pick through 30 plugin config subdirectories mixed in with the mod configs.

I'm pretty sure the plugin configs just go under /config/Sponge though, so it's only one folder. I don't see the issue with that.

/config/sponge/my_plugin
Unless a mod is now putting their configs under sponge subdirectory, you should be fine :P

Why not /config-Sponge though? Or /Sponge/config? How seriously painful is that to implement?
How do plugins know where to put their configs? Do they do that directly themselves following a spec, or is Sponge telling them that when it loads them?

@DMahalko: Plugins can use a number of different annotations with a Guice injection (such as DefaultConfig, ConfigDir, or ConfigRoot). Sponge's guice module provides the config location for the plugin being injected into.

Why not /config-Sponge though? Or /Sponge/config? How seriously painful is that to implement?
How do plugins know where to put their configs? Do they do that directly themselves following a spec, or is Sponge telling them that when it loads them?

They specify it when declaring their configuration in the plugin. Honestly it's one folder under config, I don't see an update workflow that can't include a single folder under config being a simple case to deal with. config is a universal standard and it makes sense to adopt it.

It makes management easier for server admins, having all these things separated. Not everyone setting up servers is a programming or operation system professional. Often it's some 12 year old trying to throw something together, with some help from someone else. The less complicated it is for them to deal with modpack upgrades, the easier life will be for everyone.
And anyway I'm not asking you to change it as the default location for plugin configs. I am just asking that you make it CONFIGURABLE by server admins, with an optional entry in the sponge.cfg.

@DMahalko
Now THAT is a reason for it (not the combative attitude yet again). I see no reason we couldn't let you set the config root to a folder of your choosing for plugins. Sponge's configs itself would still go into /config/sponge FYI.

@Zidane +1

Copy config/sponge/ out.
Nuke config/.
Create config/.
Copy config/sponge/ in.

Is this too hard?

facedesk  Okay, make this a command line option for sponge.jar then

sponge.jar is still a forge mod though, so it makes sense that its config goes with the rest of the forge mod configs.

Is there not some simple way to make this work easily to have optional full isolation?
Code:
IF a sponge.cfg is found in /root/sponge  use it.
Otherwise look for it in /root/config/sponge/ as usual.
If it doesn't exist, create /root/config/sponge/ as usual, and write the default config.
To enable alternate functionality the admin merely needs to do this after first run of Sponge:
Move /root/config/sponge   /root/.

Asking for the Docs:

We will support relocating/using an alternate /plugin folder?
We will support relocating/using an alternate /config folder for plugins?
Relocation of sponge.jar is already possible via FML?

@DMahalko
That should be a Forge issue as SpongeForge still is "just" a Forge Coremod.

1 /root/minecraft.jar
2 /root/Forge.jar
3 /root/Sponge/Sponge-1.0-RELEASE.jar
4 /root/Sponge/Sponge.cfg
5 /root/Sponge/plugins/
6 /root/Sponge/plugin-configs/
No 3 - Alternate single mod location specified via forge command line
No 4 - Alternate path via sponge.jar looking for its own config at startup
No 5 - Specified in Sponge.cfg or this alt location is auto-used if found
No 6 - Specified in Sponge.cfg or this alt location is auto-used if found

Forge mandates the location of mod configs.

SpongeForge is a forge core mod which can run on BOTH client and server. The config belongs where it is. Stop trying to relate it to MCPC/Cauldron.

And so spaketh the actual author of Cauldron :smile:
Summary on this issue:

I will add the configurable additional plugins dir as mentioned above, this basically just needs merging anyway.
I will make the base shared config dir for plugins configurable in the same way as per @Zidane's suggestion above.
Sponge config stays where it is because it's simple, deterministic, in keeping with general policy for mods and the argument for relocating it just simply isn't strong enough to overcome the advantages (standardisation, etc.) of leaving it where it belongs.
Pretty much everything else is achievable via the --mods command line argument so we can liaise with @tzky and @Inscrutable on getting that added to our docs


[FEATURE REQUEST] NCRFC Surface Temperature and QPE

NCRFC (POCs: Eric Novotny-MVP) - from the Kansas City Regional office LDM feed:Temps
TODO

[x] msr-coe-1hrT--NCRFC_hourlyFcstT_2021092212.tar.gz
[x] msr-coe-1hrT--NCRFC_RTMA_Obs_1hrT_2021092217z.grb
[x] MSR_mpe-lx_2021092218z.grb
[x] LDM connection push to Cumulus bucket

Commit USACE/ldm-config@eaebb50e81755f26dc763b04361f84731ccd976d closes this issue.
Tasks to include these products are complete but LDM on EC2 continues to become more unstable.


Goal

A goal is a specific and measurable objective that someone aims to achieve within a given timeframe. Goals can be short-term or long-term, and can relate to any area of life, such as career, health, relationships, or personal growth

[x]  Goal feature
[x]  Goal CASL
[ ]  Goal unit test

what config do I need?
@wawahuy


chore: add topics and disposable token code snippets for dev docs

Addresses #453 by adding code snippet for GenerateDisposableToken that will be pulled into the dev docs. This snippet can be used here and here.
Addresses #459 by adding code snippets for instantiating a topic client, publishing to a topic, and subscribing to a topic. These examples will be used on this page.

This LGTM! I think @nand4011 should take a look at the Topic examples before you merge, and if he's good with it, :shipit:


Collapse not showing.

Hi,
I installed collapse, and it is shown in vue-tools, but not appear on the website.

I don't know what i am doing wrong. Any suggestion?
Regards

I don't know why is happening this to me, but is something that has to be with css.
.collapse {
    display: none;
}

So i put scoped styles on the component
.collapse {
  display: block;
}

But then i got a custom style on the card-content class:
element.style {
    height: 0px;
    opacity: 0;
}

This is my code.


Finalize Profile Skills page

Resolves #4859.
Unfortunately, a bunch of stuff got folded into this one PR.
Primary changes

Collects the Explore Skills modal and the Applicant Skills accordions on one page.
Creates the route for the new page, with correct permissions, and sets up the correct API interactions.
Some minor style changes to Skills List component.

Related changes

Client side Skill type now includes skill_category_ids, as is returned by the skills api endpoint. Changed some logic in List and FindSkillsModal components to use this to group skills.
indexResourceHook now accepts a keyFn, which allows for mapping items by something other than id. This allows collecting Experiences (which include different types of experience, with overlapping ids) into one indexResourceHook.
Created a new endpoint for all ExperienceSkills belonging to an applicant, so they can be retrieved with an indexResourceHook. (Previously they could only be retrieved along with the applicant experiences api endpoint.)
Deleted some old Controller code for processing form post requests to update Degrees, Courses and WorkExperiences (deprecated).

The titles a bit to big, I think setting the h2 heading property to h3 would look better.

Done 👍

The hover effect on the dialog trigger isn't working properly.

It looks okay to me. What behavior are you expecting that isn't there now?

It's hard to know that the skill accordions are accordions until you click on it. Maybe we could add a box-shadow effect with the H2 card property.

They did have card props, but they stopped working with an h2 update. 😆 I've replaced them with with the new data-h2-shadow="b(medium" prop, and spaced them out slightly more.

Nice work @tristan-orourke. This time around, I noticed a missing null state for skills when sort by alpha, so I've added that as well. Otherwise, all of the issues I've mentioned have been addressed.

The hover effect on the dialog trigger isn't working properly.

Like @tristan-orourke, I couldn't figure out what wasn't working properly. @yonikid15, could you elaborate or if the issue has resolved itself, let us know? After that, I can approve this to be merged.

Seems to be working now 👍


8.4.1/3.0.3 login hostname not updating

CC ver = 8.4.1
Slurm project ver = 3.0.3
ISSUE:
Login nodes do not update hostname to cluster-prefix value defined in cluster when use_node_as_hostname is enabled.  In same cluster the scheduler and execute node hostnames are updated as expected.
INFO:
jmorey@8fgxl000001:~$ sudo -i jetpack config hostname
8fgxl000001

jmorey@8fgxl000001:~$ sudo -i jetpack config slurm.node_prefix
jm-cryo

EXPECTED BEHAVIOR:
hostname should be set to jm-cryo-login-1 not 8fgxl000001

the install.py  file calls the set_hostname function for execute nodes.  Should it also call it for login?
    if args.mode == "execute":
        set_hostname(settings)
        setup_slurmd(settings)

Yes we should do that. Ryan has a fix WIP for this.

Closed in previous login fix, 4e28b1e83a117d046a40b81780226f6d14ca91f3


Flow fails if you go through too fast

BUG:
DESCRIPTION
Steps to reproduce:

Go through the app (fresh instance) and get to the slack page very quickly (before slack users are fetched)

Expected behaviour:
-App should wait until slack users are fetched and then display them
Observed behaviour:

App fails

Appears fixed, tested and found it does re-render when the response is processed.


[Tracking issue] CDI Support

Background

https://github.com/NixOS/nixpkgs/pull/284507 introduces CDI support in the form of virtualisation.containers.cdi.{dynamic,static} options;
https://github.com/NixOS/nixpkgs/pull/290979 proposes to remove these options before 24.05 in favour a more modest and specific hardware.nvidia-container-toolkit; the alternative, designing a consistent generic interface, might be too time consuming;

Tasks left
<...>

[ ] Remove the generic interface and introduce an nvidia-specific interface (WIP in https://github.com/NixOS/nixpkgs/pull/290979).

[ ] Nvidia: unbreak: we're currently mounting incomplete closures; need to use exportReferencesGraph.

[ ] Nvidia: unbreak EGL, https://github.com/NixOS/nixpkgs/issues/297537.

[ ] Nvidia: Introduce options to mount FHS bin/lib paths in containers.

[ ] Nvidia: Only seems to work with podman, not with docker_25, https://github.com/NixOS/nixpkgs/issues/305312

[ ] ...

[ ] Verify that Nixpkgs programs that expect addDriverRunpath.driverLink (/run/opengl-driver/lib) work out of the box

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/breaking-changes-announcement-for-unstable/17574/47

Since https://github.com/NixOS/nixpkgs/pull/306337 merged, we can mark the 'Nvidia: Only seems to work with podman, not with docker_25' checkbox too :)


Linear response time on services query in elasticsearch

Getting some reports of eventual timeouts on service and span name queries on elasticsearch. Ex at 80GB/day you eventually will time out (reported by @pauldraper)
Ultimately one big issue is the shape of the json, which requires nested queries to access the service name of a span. The new reporting format (#1499) will allow us to eventually fix this part, but we can't pin to a span format-based implementation to fix a performance problem!
In cassandra3, we started with a materialized view, but had to switch to manual indexing for similar performance reasons (#1374). The downside is that it amplifies writes and also is less straightforward for those who might be simply writing json to ES (as opposed to via a collector).
Regardless of what we do, it would be nice to have a perf test which can showcase evidence of linear latency patterns on service or span name queries. This would catch any system having indexes which aren't ideal.
We have some next steps to consider...

firstly, properly diagnose the issue. As ES is primarily a cache, maybe there's some tuning of the index template to help with nested queries on service and span names
next, see what needs to be done in the collector directly vs somewhere else. For example, if we have to do manual indexing we could consider an ES pipeline stage to compose that.

cc @openzipkin/elasticsearch

another thing I thought of is that we should collect notes about what sort of data they are putting into zipkin. For example, historically spans had very few tags and people used sampling. Particularly OpenTracing tend to put a lot of tags (each of which ends up in the subquery for service names). It will be interesting to know how many spans and how big they tend to be when users experience problems.

There are some statistics about our "bad" experience:

~6 Gb of traces in each of daily indices (keeping 5 last indices)
~1 Kb per span
3-4 tags per span

( - running on m3.medium.elasticsearch in AWS, if it matters)
The main workload is writing and some users accidentally come to a web-interface for looking their traces.

Thanks very interesting. You have very few but large tags. Is it safe to do
math to extrapolate span count from this?
On 10 Apr 2017 11:42 pm, "Semyon Slepov"<EMAIL_ADDRESS>wrote:

There are some statistics about our "bad" experience:

~6 Gb of traces in each of daily indices (keeping 5 last indices)
~1 Kb per span
3-4 tags per span

( - running on m3.medium.elasticsearch in AWS, if it matters)
The main workload is writing and some users accidentally come to a
web-interface for looking their traces.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/1526#issuecomment-292989310,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD615yRdvh0JxcWakH5BoLoEb4AkJwrks5ruk3lgaJpZM4MKsNW
.

I have been thinking about this and believe adding a new index for service and span name is the best option. This would be just like cassandra where we keep a separate document for service/span lookup:
CREATE TABLE IF NOT EXISTS zipkin3.span_name_by_service (
    service_name text,
    span_name    text,
    PRIMARY KEY (service_name, span_name)
)

Backfilling this index would be relatively simple and could be done a myriad of ways. Unlike adding new data to the span index, this approach doesn't risk people accidentally clobbering their spans to support it. It also doesn't depend on any specific span representation (current or future).
In implementation, easiest would be a daily index like we use for dependency links. We could set the document ID to service and span name so that the data doesn't grow unbounded.  If daily is too course granularity, we could make the ID naming convention include the hour of the day or minute of the hour and still significantly bound the data size.
We could make the read side look at both, and only execute the slow nested query when the ideal index contains no data. This means users don't have to do anything to start using it.
Operationally, I like this approach as being similar to cassandra means less cognitive overhead for cross-storage maintainers.
@openzipkin/elasticsearch @semyonslepov wdyt?

This sounds great! A couple of questions:

When is this new index populated? Is it when a span is written to storage?
Having the ability to set the granularity of the index name would be awesome. So, it would be nice to set the granularity to weekly or monthly also. That way, we may not need to clean up this index if we so desire.

When is this new index populated? Is it when a span is written to
storage?

yes when written, although we can also provide a script to apply to old
data

Having the ability to set the granularity of the index name would be
awesome. So, it would be nice to set the granularity to weekly or monthly
also. That way, we may not need to clean up this index if we so desire.

It is important to note that all of this assumes the index is the same as
the others.. this is just another document type in the existing index
(another beyond span and dependencyLink). The current strategy for cleaning
up any daily index would be curator or similar, and through that you can
choose to retain as much as you like (caveat being performance will
eventually degrade)

So the naming pattern I'm referring to is on the document id .. and doing
something different would only be needed if we want less than a day
granularity on queries.
ex. The proposal is that inside the zipkin-2017-04-18/serviceSpan
index/type, there would be documents with ids like.. accounting|get-users
accounting|update-users (this is the exact approach used for dependencyLink)
If this is good enough, we should leave it at that. If for some reason less
than daily is needed, we could add a timestamp, though it will make query
more complex and also visually looking at the data will be annoying. In
case you don't know.. I don't like this option :)
ex. for hourly
00-accounting|get-users,
01-accounting|get-users,  01-accounting|update-users,
02-accounting|get-users, ... 23-accounting|get-users
* to do this, we'd need to store a timestamp in the json, too, which
would make the query a bit more expensive because if we go daily we don't
need to do anything except grab everything in the daily bucket.

Thanks for the explanation. +1 in this case.
I was asking a longer term index since it would mean cleaning up one more index when we purge the data. But, if this is added an additional index type on the daily zipkin index, daily granularity is an awesome solution.

np and thanks for your feedback! will wait for other feedback before
heading towards impl.

Is it safe to do
math to extrapolate span count from this?

Yes, it's fair enough. Actual counts may differ, but it's correct on average.
About indexes: sounds good and transparent for users. Am I right that we will use the same index for spans' names lookup and it's going to be faster too?

About indexes: sounds good and transparent for users. Am I right that we
will use the same index for spans' names lookup and it's going to be faster
too?

yes this index will support both. basically the query will be a lot
simpler, so it should be much faster. What won't be faster are trace
queries, as they still use nested stuff.
I won't be able to benchmark as I don't know how besides laptop test which
isn't likely very realistic.. hopefully you can help let us know how much
better it goes. is that ok?

So, we still don't have huge enough data, but of course, I will run some measurements on current and new versions and post the results.

+1 for a new index, but is there any payload that is from existence check when persisting service/span names?

+1 for a new index, but is there any payload that is from existence check
when persisting service/span names?

yes, there would have to be a payload so we can do the span name query. it
would be a document including the service name and the span name
ex. for id = accounting|update-users
the document would be:
{ "serviceName": "accounting", "spanName": "update-users" }
That way, when we do a span name query, we can retrieve the spanName keys
with a term query where serviceName is the input.
This is needed because you cannot do a query against an id field.
make sense?

Great, this improvement on service/span name query will greatly improve user experience.

ok moving to impl as no one is against. thx for feedback, folks

will take a bit to refactor properly, but the more important code change at query time will look something like this...
service name query
-    SearchRequest.Filters filters = new SearchRequest.Filters();
-    filters.addRange("timestamp_millis", beginMillis, endMillis);
-    SearchRequest request = SearchRequest.forIndicesAndType(indices, SPAN)
-        .filters(filters)
-        .addAggregation(Aggregation.nestedTerms("annotations.endpoint.serviceName"))
-        .addAggregation(Aggregation.nestedTerms("binaryAnnotations.endpoint.serviceName"));
+    SearchRequest request = SearchRequest.forIndicesAndType(indices, SERVICE_SPAN)
+        .addAggregation(Aggregation.terms("serviceName", Integer.MAX_VALUE));

span name query
-    SearchRequest.Filters filters = new SearchRequest.Filters();
-    filters.addRange("timestamp_millis", beginMillis, endMillis);
-    filters.addNestedTerms(asList(
-        "annotations.endpoint.serviceName",
-        "binaryAnnotations.endpoint.serviceName"
-    ), serviceName.toLowerCase(Locale.ROOT));
-    SearchRequest request = SearchRequest.forIndicesAndType(indices, SPAN)
-        .filters(filters)
-        .addAggregation(Aggregation.terms("name", Integer.MAX_VALUE));
+    SearchRequest request = SearchRequest.forIndicesAndType(indices, SERVICE_SPAN)
+        .term("serviceName", serviceName.toLowerCase(Locale.ROOT))
+        .addAggregation(Aggregation.terms("spanName", Integer.MAX_VALUE));

https://github.com/openzipkin/zipkin/pull/1560 is ready, just looking to make a backport script or at least pseudocode for adding "servicespan" into old indexes

If I can get a shipit or change requests on #1562 and #1560, I will release the newly optimized stuff tomorrow.

@semyonslepov @tramchamploo @mansu @devinsba can any of you try zipkin 1.23? I'd like to get someone to use it in real life before propagating to other projects.

if any of you do get a chance, along with response time on /api/v1/services and /api/v1/spans please also report back any differences in storage usage, too. A lot of mapping options are now turned off, so it should be less though I don't know what percentage real life usage will end up as.

I'll need to update the zipkin-aws image to be based off this in order for me to try it

@devinsba try 0.2.2 :)

There are some result from my tests:
/api/v1/services (1 RPS):
Test 1, ~1000000 documents in index, ~250 service names with 1 span name for each:
zipkin 1.21.0:
98% - 200 ms
50% - 150 ms
zipkin 1.23.0:
98% - 50 ms
50% - 20 ms
Test 2, ~1500000 in index, ~450 service names with 1 span name for each:
zipkin 1.21.0:
98% - 250 ms
50% - 200 ms
zipkin 1.23.0: (same as Test 1)
98% - 50 ms
50% - 20 ms
When data amount increases, this difference becomes more.
/api/v1/spans (10 RPS):
(one test, something about ~5000000 documents in index, ~250 service names, 1-2 span names for each service)
zipkin 1.21.0:
98% - 150 ms
50% - 50 ms
zipkin 1.23.0:
98% - 50 ms
50% - 20 ms
I saw no significant difference in storage usage for these types of requests with my test conditions.
But there is significant change of CPU usage on Zipkin-hosts: I made two tests with writing 300 spans per second on free-tier AWS t2.micro instances and got ~25% CPU load with 1.21.0, with 1.23.0 at some point (after 3-4 minutes from test beginning) it was 100% with request dropping (ok, it's not correct enough - I set 10s timeout for requests, so my test-tool didn't get any answers after 10s).

@semyonslepov thanks for the feedback! fair to say overall better? :)
yeah I wouldn't expect zipkin CPU to go down based on this change, though I would expect elasticsearch's CPU to go down. zipkin is actually doing slightly more, but if its CPU load when consuming becomes an issue we can probably profile a bit.

Made some more test today to prove earlier theories.
Yes, we can say that service names query is much better (span names query too, but not so significant). And it's awesome!
(ES CPU goes to top on more than 3-4 /api/v1/services queries per second on our setup. Taking into account the fact of existing browser cache for service names, we don't have so many requests from our users to this API handler. But anyway we have to keep it in mind)
Regarding ES CPU, I don't see that it's going down with 1.23.0 release. Even more, in my tests it's going up on the same workload (sending ~1500 spans per second) (I'm not sure about the cleanness of my tests, maybe there is a noise, but I have done them twice for each release. Will be fine to hear something from another users). On the same ES configuration I saw something about 50-55% load of ES CPU with 1.21.0 release and 70% on 1.23.0 (70% vs 95% on another test).
Actually, Zipkin CPU doesn't increase so fast on more powerful configurations (m3.large instance with 2 CPU cores and 7.5GB RAM) and  as it was in my yesterday tests (t2.micro instance with 1 CPU core and 1GB RAM, today CPUs are slighlty more powerful). So, this difference is not so critical.

For contrast, at ~800 RPS peak for our ES cluster I am seeing no discernible change in the CPU usage (maybe 1% increase, likely just increased load). And none on the app either.
We are ES 2.3 with 5 m3.large data nodes

Ahh.. i think i know what might increase the load on ES. It is probably
less about finer tuned indexing on spans, rather more about having to index
service and span name separately as it wasnt before. If this becomes an
issue or we just want to sort it out.. we can employ a deduping approach
used in cassandra. Essentially we dont write the same names twice from the
same node (rather than overwriting). If your tests are clean enough (as
they seem to be) we could test that deduping brings load back down..


Make setValue optional for TapToEdit

If it's not editable we'd never use setValue.

Good call, added that check.


Setup instrumented tests

Description
Running on Bitrise CI to a better preview of test results
Related issue
#23 Setup instrumented test

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

Project coverage is 0.00%. Comparing base (14aca6d) to head (d785b4b).
Report is 30 commits behind head on main.

Additional details and impacted files
@@          Coverage Diff          @@
##            main     #24   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          3       4    +1
  Lines         21      31   +10
=====================================
- Misses        21      31   +10

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


TQL: bug fix in TraverserBuilder

The TQL TraverserBuilder prevented any traversal of Templates. This was due to the way stats are setup into templates as Option[Seq[Stat]], which was not handled by the previous version of TQL. This is now corrected and the Obey test case passes as usual.

Correcting ObeyRuleSuite for TQL: we can't compare source code as strings directly, due to formatting differences between the source code and the prettyprinter output. The test now checks if the raw of the trees are equals. A small case was also added for testing purposes.

This is the continuation of https://github.com/begeric/TQL-scalameta/pull/2.

Merged as https://github.com/scalameta/scalameta/pull/120


Documentation for mocking module

This fleshes out the mocking documentation as well as upstreams some improvements to the mocking infra we have made internally the last few months.

@gpeal I have bumped the kotlin version and some other dependencies, and removed jetifier (which should speed up builds)
I also did all of the mvrx -> mavericks renames for the mocking and launcher modules (besides the package names), and renamed install to initialize for MockableMavericks


Add Neural networks code from scratch in RUBY programming language

Add neural network code from scratch using ruby programming language.
[Hint]: You can take help from the python code. Your code should do the same thing as neuralNetwork0.py in ruby

Only 1 file is implemented in rb, hence this issue remains open


confWriter

would be useful to have eventually. i have encountered a situation where this would have been useful for converting between formats

there is already an issue for this, not sure how i never noticed


Swift result

The library defines a Result type but it's not necessary as Swift standard library already offers a Resulttype which has more functionality.
This simple change just uses Swift's Result instead.

@MaximFischuk Please assign someone capable of reviewing this.


The post request in the "workflow/status_tracer_decorator.py"

Hello,
When running the "run_toy_example_cluster.sh" which will invoke the "workflow/toy_example_workflow/secure_add_host_workflow.py ", the run() function inside the latter file is decorated by the status_tracer_decorator.status_trace which will invoke the call_back() function.
And this call_back() function will send a post request to a url "http://<IP_ADDRESS>:9380/job/jobStatus/test0/host/0" where "test0" is a jobid and the last "0" is the Partyid.
I am confused that which file is act to start this server service? As for the task-manager service, it is not associated with the jobid.

the code is quite confusing...... I also encounter this problem!

The url is used to post-back job status to task-manager and the task-manager use jobid to identify the unique job. What's more,  we use task-manager to start and control the jobs in real scenario, so jobs need to callback job status to task-manager to life cycle management of the job, status_tracer_decorator is also for this.
run_toy_example_cluster.sh or other run_$algorithm_cluster.sh scripts are just help us to be quickly familiar with Fate and for self-debugging too. If you want to know how to start task by task-manager,  have a look at this link: https://github.com/WeBankFinTech/FATE/tree/master/examples/task_manager_examples


Adding readme, reformating codebase, added copyright header

Fixes #30

merged, fixed url to uri as it's going to be that. per https://github.com/spring-cloud/spring-cloud-dataflow-metrics-collector/commit/21270df234c2c26611c6283dff962e7e6a92d2b1


OSIO: Call WIT's codebase/create after importing a repository or launching a booster

Following the discussion over https://github.com/fabric8-services/fabric8-wit/pull/1925#issuecomment-374505275, the launcher-backend should invoke the WIT API to create the codebase.
/osio/import should also validate if the build config already exists (see https://github.com/fabric8-services/fabric8-wit/pull/1925#issuecomment-374959071)
Endpoint documentation: http://swagger.goa.design/?url=github.com%2Ffabric8-services%2Ffabric8-wit%2Fdesign#!/codebase/codebase_create
/cc @corinnekrych @aslakknutsen

According to @aslakknutsen, this is the payload that needs to be sent to POST /spaces/{spaceID}/codebases
{
  "data": {
    "attributes": {
      "stackId": "java-centos",
      "type": "git",
      "url": "https://github.com/fabric8-ui/fabric8-runtime-console.git"
    },
    "type": "codebases"
  }
}


Solve #72 - Add bas dependencies to config file

Closes #72
Description
On this PR the gem dependencies were added to the specification file. This will allow another project to install the gem dependencies when the bas gem is installed.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.612%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2309

Relevant Lines:
2318

💛  - Coveralls


Reusability hint to improve reuse performance when composite components are present.

The purpose of this change is pretty much summed up in the documentation for Renderable.makeReusabilityHint(using:).
The design is inspired by how Hashable handles nested hashing.
Do also note that implementing makeReusabilityHint(using:) does not imply that a composite component no longer needs to handle type mismatch in view hierarchy.

I actually realise when answering Sergey’s questions about walking the hierarchy, that we need to generate the reuse identifier with not only , but brackets that indicate containment. Otherwise, A([A([B(), C()])]) would resolve to the same symbol as A([A(), B(), C()]) which has a rather different view hierarchy.
That’s also reiterate the value of closing off custom reuseIdentifier, because who knows what surprises you could have when you have components from different authors. 👻

Need to think about how this should integrate with #162.


Use consisten placeholder names for client_id and resourceId

The Starter Pack uses ProxyIdentityExperienceFrameworkAppId and IdentityExperienceFrameworkAppId in the
login-NonInteractive TP. Please use same names in the ResourceOwnerPasswordCredentials-OAuth2 TP on this page rather than 0000... I use automation to replace these with the correct ids for my tenant, which the change in naming breaks.

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

ID: c21f5240-6fe2-41ec-293a-2e3b33522706
Version Independent ID: 095c2d6b-8691-74b6-99d5-db0ee1017194
Content: Configure the resource owner password credentials flow with custom policies - Azure AD B2C
Content Source: articles/active-directory-b2c/ropc-custom.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@mrochon Thanks for your comment! We will review and provide an update as appropriate.

@mrochon Thanks for your feedback. I have updated the document with ProxyIdentityExperienceFrameworkAppId and IdentityExperienceFrameworkAppId instead of 00000000-0000-0000-0000-000000000000. Changes might take upto 24 hrs to reflect.


Binder: /usr/bin/python3: No module named pip

Binder fails to load with the above message

Needed to install pip with Docker build as it doesn't seem to be included in base image anymore. Better solution would be to cache a base image with pip installed to save time.


Exports whose names aren't explicit in the file being transformed

Input:
import {promisify} from 'bluebird';
const foo = promisify(bar);

Using the npm and commonjs plugins, I get the error:
Module ~/code/foo/node_modules/bluebird/js/release/bluebird.js does not export promisify (imported by ~/code/foo/foo.js)

Here's the contents of that bluebird.js file:
"use strict";
var old;
if (typeof Promise !== "undefined") old = Promise;
function noConflict() {
    try { if (Promise === bluebird) Promise = old; }
    catch (e) {}
    return bluebird;
}
var bluebird = require("./promise")();
bluebird.noConflict = noConflict;
module.exports = bluebird;

...and here it is after commonjs transformed it:
import require$$0 from './promise';

var bluebird = (function (module) {
var exports = module.exports;
"use strict";
var old;
if (typeof Promise !== "undefined") old = Promise;
function noConflict() {
    try { if (Promise === bluebird) Promise = old; }
    catch (e) {}
    return bluebird;
}
var bluebird = require$$0();
bluebird.noConflict = noConflict;
module.exports = bluebird;
return module.exports;
})({exports:{}});

export default bluebird;

I guess the problem is the file doesn't actually mention the name promisify so there's no way for this plugin to know that the module actually does (in commonjs terms) export the name promisify.
A workaround is to change the importing file like this:
import _bluebird from 'bluebird';
const {promisify} = _bluebird;
const foo = promisify(bar);

But it would be nicer if there was some way rollup could handle this scenario. For example, could rollup try to recover from the "Module X does not export [name]" error like this: check if the module has a default export, and if so, include that whole default in the bundle and then add some code that just grabs the relevant property off it (var promisify = _ref.promsify;)? Behind a config option maybe?

Actually, this might be a better solution (as it might also be a good workaround for #9): Add a new config option for this plugin, allowing me to manually specify, per file, any extra names that the file should export.
  {
    npm({jsnext: true, main: true}),

    commonjs({
      include: ['node_modules/**'],

      addExports: {
        'node_modules/bluebird/js/release/bluebird.js': ['promisify', 'coroutine']
      }
    })
  }

The addExports option would instruct the plugin to add some extra export lines at the end of the transformed code, e.g. export const promisify = _ref.promisify; (where _ref is whatever the default export is).
Would that work?

Sorry for delay. This is a brilliant idea! And obvious when you mention it. Have implemented it in #18, with just a minor tweak (addExports -> namedExports)

Released in 2.1.0

namedExports is sometimes ignored or doesn't work.