what annoys me the most as a cyber weapons dev with this lib

sure its great and all but do you REALLY have to put
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

sure i get you want protection beleieve me i do to but it hurts when some people are trying to control the output for our own uses, i think you should remove it. it makes it a very annoying module to work with and something i just dont want to use. i would at this point just remake the module :-1:

Hello @ArkAngeL43
The Notice and Terms are NOT something that I put into, Its return by the domain registry VeriSign.
Anyway, If you want to control the output as structed data, please try: https://github.com/likexian/whois-parser

If you think this repository is helpful, please share it with friends, thanks.


the dkms amdgpu kernel module does not have powerplay option to disable

Hi, I'm a Radeon R9 390X user there (GFX7, Hawaii/Grenada XT) on Ubuntu 18.04. README said “full support is not guaranteed” but at least the OpenCL stuff seems to work and the issue I talk about is not in the "ROCm" part neither the amdkfd one but in the amdgpu kernel provided with.
So, the Radeon R9 R90X is known to not be very stable under Linux, see FreeDesktop#91880. To get my R9 390X running stable I have to disable the amdgpu.powerplay option. This is my usual kernel command line:
radeon.cik_support=0 amdgpu.cik_support=1 amdgpu.modeset=1 amdgpu.dc=1 amdgpu.powerplay=0 amdgpu.dpm=1

After having installed ROCm and rebooted, I instantaneously noticed that my system was behaving the same way it behaved months before, before I disabled powerplay: wrong screen brightness on plymouth stage (brightness is ok once X11 starts by the way), weird lm-sensors related to sensors it fails to parses (probably a lm-sensors issue)… and worst than that, I now got random crashes like I had before disabling powerplay: suddenly the screens go black, the GPU stops to send any picture to the screen, the keyboard buttons like “Shift Lock” or “Num Lock” are not able to switch related led state anymore when pressed, and if there was a sound application (video, music player…) running the background sound continue to play for some minutes before getting silent.
Hopefully I'm able to play the magic SysRq dance to sync, umount and reboot to avoid a cold reboot.
So, ROCm itself seems to work on my end but the provided amdgpu kernel can't be configured to provide a stable environment so ROCm can't be used.

I'm not sure what kernel or driver version you were running before, but as far as I can tell, the powerplay modparm never did anything for Hawaii. It was used for Tonga and Fiji for a while, and was used for Carrizo and Stoney Ridge up through its removal from the kernel during a refactor of the powerplay code between Linux 4.10.17 and 4.11.0.
However, powerplay was (as far as I can tell) never enabled on Hawaii.
That said, most of the powerplay features are now controllable at a much finger granularity in these new drivers through the modparm ppfeaturemask. This is a bitmask, and the bits are defined in the driver code. You may want to try something like this to "disable" most of the powerplay features your GPU may run (if any):
radeon.cik_support=0 amdgpu.cik_support=1 amdgpu.modeset=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.ppfeaturemask=0

If that works, you could slowly start adding back in powerplay features until you run into your problems.

Before upgrading to Ubuntu Cosmic I tried to build rocm dkms without amdgpu by removing any amdgpu reference in dkms.conf (i.e. building all others dkms modules but amdgpu), that fixed graphical and stability issues but made rocm opencl unworkable. Since update to Ubuntu Cosmic 18.10 with 4.18 kernel I don't experience graphical neither stability issue since I'm still using the amdgpu upstream module, but rocm opencl now works. I have not yet tried to build the amdgpu module with rocm-dkms, I have not tried yet to use rocm opencl without rocm-dkms just by relying on upstream.
At this point I will probably not spend time to investigate why non-upstream amdgpu module is faulty when upstream one is good enough. Btw, thanks for the knowledge about ppfeaturemask, I will probably find other uses cases to experiment with. :smiley:
I'm surprised you said powerplay never did anything for hawaii, I noticed disabling it leads to stability improvement and a visible change on userland : for example I noticed that not disabling powerplay has an effect on available sensors, basically I have to disable some unknown sensors parsing in lm-sensors to not get a broken lm-sensors output if powerplay is not disabled.
chip "amdgpu-pci-*"
	# powerplay
	ignore in0
	ignore power1

And the weird thing is that both graphical, stability, and sensors issues were there with the dkms without option to disable powerplay, exactly like the behavior I get with an upstream amdgpu module without disabling it.
In any way, is there a way to disable amgpu compilation in the rocm-dkms package without rewriting the dkms.conf file by hand?

GCN 1.1 switched to powerplay around back then https://github.com/torvalds/linux/commit/3120e2a390a9322a8247d7e9b8be52a7efc26dab

Even GFX9 is not even possibly supported anymore by now, so..

The GFX7 support was never fixed before being removed to begin with (it only worked a couple of months years ago).


Migrate Aura authorship-detection to Pre-runtime digests

The inherent-based approach used before is now obsolete. See #2929 as an example of how to use PreRuntime digests in the runtime to compute authorship info.
This should be accompanied with a FindAuthor<u32> implementation.

Are inherents obsolete at this point?

@DemiMarie-parity for this use-case. Not for others.

This is needed for staking to reward its validator, shouldn't it be Milestone 2.0-K ?


Tweaks from Sprint Review

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Asteroids DoD document to see any additional details for the items below

[ ] Any net new LWC work has Sa11y tests & 50% or above lines JEST test coverage
[ ] CRUD/FLS is enforced in Apex
[ ] Permission sets are updated to account for CRUD|FLS|Tab|Classes
[ ] Field sets are updated to account for new fields
[ ] UX approval or UX not necessary
[ ] Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name (https://github.com/SalesforceFoundation/PMM/pull/303)
[ ] All acceptance criteria have been met

[ ] Developer
[ ] Code Reviewer
[ ] QA

[ ] PR contains draft release notes
[ ] QE story level testing completed

W-8595069

Thanks for catching that @bethbrains and for the quick feedback @lbeller - the capitalization has been fixed.


Plotting won't work after introducing Fix #525

What steps will reproduce the problem?
I experienced the same problem as reported in issue #13275 after installing Spyder 4.1.4. The fix proposed in #525 got rid of the flush of warning in the console, but plotting became very slow (interactive zooming etc. takes forever) and the plot windows mostly stay in the background. I tried differnt things, like changing the backend and reinstalling Anaconda but finally found that commenting out the lines of code that were proposed in fix #525 was the only thing that fixed the plotting issue. But then I get the warnings back.
This can be reproduced by plotting anything, like e.g. x = [1,2,3,4,5], plt.plot(x) (matplotlib.pyplot)
What can I do? Thanks!

Hey @AlgDevK, please update to ipykernel 5.3.4. This problem is fixed in that version.

Thanks! I tried to update the ipykernel but it won't work. conda install ipykernel will always install/keep 5.3.2.

You need to run
conda update ipykernel


Run JSBin Locally - unable to save

When I edit the HTML or JS I get the following red error message at the top:
"I think there's something wrong with your session and I'm unable to save. Refresh to fix this, you will not lose your code." Clicking refresh doesn't help.
JS console shows "POST http://<IP_ADDRESS>:3000/save 403 (Forbidden)".
Server log, same, forbidden:
<IP_ADDRESS> - - [Sun, 25 Jan 2015 00:59:43 GMT] "POST /save HTTP/1.1" 403 2982 "http://<IP_ADDRESS>:3000/?html,js,output" "Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.99 Safari/537.36"

Setting the session secret didn't help.
Production or development doesn't make a difference.
Setting logger to "dev" in config.local.json didn't give any more output.
Fixing timezone didn't help.
Any tips for how to debug it?

Found the error in the request response:

It works in IE but not in Chrome.

Tried it on a public facing web host and there it worked, also in Chrome.
Other than that, node binaries were 32-bit on this working server, only other difference I know.

so answer is needing on a public facing web host ? today, I having the same error in Chrome  59.0.3071.104, and  I am on a public facing web host, even  though I having some doubts about meaning of  the  'public facing web host '?

I don't remember much about this, but I think the JSBin site had to be accessed through a public domain name (or maybe public IP address was enough?). Sorry, I don't remember.


Update index.html

_ No description provided. _

Provide a description to imply what changes are being made along with the issue you're solving

Make another Pull Request


Add Tomopy to VisTrails

Added tomopy to auto-import list.

Modified scraper to be able to handle return parameters without names.

Fixed the output port bug when there is no return value.

@sameera2004 rebased. Please check and merge. Thanks.

@celiafish This works fine, tomopy is working fine in VisTrials,
Only this coverage issue?

@tacaswell Any suggestion about this?

Coverage issue is tiny (-0.02%). Looks good -- merging.


Add support for custom commit messages

This PR fixes #32 by adding these options:

signed-commit-message is the commit message when a new contributor signs the CLA in a PR
signed-empty-commit-message is the commit message when a new contributor signs the CLA (empty)
create-file-commit-message is the commit message when a new file is created

Usage example:
jobs:
  CLAssistant:
    runs-on: ubuntu-latest
    steps:
      - name: "CLA Assistant"
        if: (github.event.comment.body == 'recheckcla' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request'
        uses<EMAIL_ADDRESS>        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          path-to-signatures: 'signatures/version1/cla.json'
          signed-commit-message: 'chore(cla): $contributorName has signed the CLA in #$pullRequestNo'
          create-file-commit-message: 'chore(cla): Creating file for storing CLA Signatures'

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Now that I think about it, it would also be nice if we add support for a intro message by changing this line: https://github.com/cla-assistant/github-action/blob/master/src/pullRequestComment.ts#L34.

Hi @AnandChowdhary, Thank you very much for your contribution. I really appreciate it ..

Now that I think about it, it would also be nice if we add support for an intro message by changing this line:

Yep sure, even I thought about it. Please go ahead and feel free to do it 😄 . Then we can also support dynamic pull request comments.
The only thing you need to ensure is that I have read the CLA Document and I hereby sign the CLA content shouldn't be changed as we are recognizing this content as a signature. I'd like to keep this content as static.

Please go ahead and feel free to do it

On it!

The only thing you need to ensure is that I have read the CLA Document and I hereby sign the CLA content shouldn't be changed as we are recognizing this content as a signature. I'd like to keep this content as static.

Yep, agreed, let's keep this static.

Two new options have been added:

signed-comment-message is the message when everyone has signed, defaults to **CLA Assistant Lite** All Contributors have signed the CLA.
request-comment-message is the message when a user is requested to sign the CLA, defaults to **CLA Assistant Lite:** <br/>Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that $you sign our [Contributor License Agreement]($pathToCLADocument) before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

Forgot to add docs here, can you please add the new options to README?

Sure, no worries. I will do it :).

This works great!

For people using Gitmoji, this is our configuration:
signed-commit-message: ":wrench: @$contributorName has signed the CLA in #$pullRequestNo"
signed-empty-commit-message: ":wrench: @$contributorName has signed the CLA"
create-file-commit-message: ":wrench: Creating a file for storing CLA signatures"
all-signed-comment-message: "✍ All contributors have signed the CLA"
request-comment-message: "Thanks for your submission! We ask that $you sign our [Contributor License Agreement]($pathToCLADocument) before we can accept your contribution. You can sign the CLA by adding a comment below using this text:"

Awesomee!!.. I also tested yesterday. It works great 💯 ...
I am just curious. How did you get custom avatar for kojbot?  Is it a GitHub App or GitHub Action ?

No, it's a GitHub account with a personal access token being used instead of the default GITHUB_TOKEN: https://github.com/KojBot


Add PyData Madrid 2016

Travis CI build machine still have the "slug bug" of https://github.com/pytube/pytube/issues/159

Hmm, I'll have to take a look at this bug again. In the meantime can you strip source_url from the video blobs. Otherwise, this looks great!

source_url stripped.

Moved to https://github.com/pytube/data/pull/133


Support: Byte Array DataType and Operations

This PR addresses [Issue]

New data type: ByteArray

Introduced a length property inside ByteArray to be used whenever we call len().
Clearing the data of ByteArray if we decrease its size! [Example]

Commands like SETBIT/GETBIT/BITCOUNT/BitOp

With unit Test cases.
With benchmark test cases.

Note:

I have not addressed the BITOP operation in this PR because it is already quite large.

@yashs360, need your help here. I am in a dilemma.
Given Redis is in C, strings are essentially bytes. In Go, strings are strings and any byte level operation becomes costly.
I was thinking that we diverge from Redis here and offer bit operations on only ByteArray type that you introduced and raise error in case someone is doing it on other data type.
What do you think?
FYI @JyotinderSingh

Hey @arpitbbhayani / @JyotinderSingh / @yashs360
I have added support for:

New data type: ByteArray
Commands like SETBIT/GETBIT
ByteArray usage inside evalBITCOUNT

Doubts:

Should we support the string data type for SETBIT/GETBIT commands?
ByteArray:

Should I introduce a length property inside ByteArray to be used whenever we call len()?

This property would be maintained whenever we increase the array size.

Do we need to clear the data of ByteArray if we decrease its size?

For example, when reducing the size of the array, should we explicitly clear the truncated data?

SETBIT k 7 1
SETBIT K 23 1
SETBIT K 23 0

So while doing SETBIT K 23 0, should we free up the memory, they are doing in Redis -> Code Reference: This

@arpitbbhayani @MohitVachhani

offer bit operations on only ByteArray
I think its fine as long as we document it. We should be able to diverge from redis as long as we have the capability covered by a different syntax.

Okay @yashs360 , I will try to add in the comments itself and also will throw different error if any bit operations are done on strings 👍🏾

Nice change @MohitVachhani . Dropped a few comments.

Hey @yashs360 / @JyotinderSingh,
Could you please let me know the next steps here ? I’m looking this task.
Thanks 🙇🏾

@MohitVachhani Overall the he change looks good, but the rewrite of Set/Get Bits doesn't make sense to me. If there are concerns with existing functions we should modify the existing code to address that instead of creating new functions.
Could you please look at that.

Sure will update the existing function and let you know soon @yashs360

Hey @yashs360 I have updated the code, as per the above comments. Please can you check it out.
Thanks 🙇🏾

@MohitVachhani please fix the linter issues. Also added a minor comment.

Thanks for addressing the comments and working on this large PR, merged!


Want more customizability with themes

Feature Suggestion
We want to be able to load custom material UI themes including custom fonts (Gotham etc.), and custom colors and title for backstage.
Also, It'd be ideal if the header could be configured (using material App should be able to allow for the header to be swappable. We want to show custom colors and Roku name in the header.
Possible Implementation
backstage/packages/theme/src/index.ts
There should be a way to load a theme for export like this;
export rokuTheme from './rokuTheme';

allow for the theme to be selectable from a list. And settable to local storage.
import theme from 'themes'
const themeKeys = Object.keys(themes)
...
themeKeys.map(theme => <List>...onClick={theme => onSelectTheme(theme)}... />
onSelectTheme(theme => localStorage.set('theme', theme))

And update the ThemeContext function from:
function toggleTheme() {
to
function setTheme(themeName) {```

and allow for overrides of the default theme:
    default:
     const defaultTheme = localStorage.get('defaultTheme')
      if (!window.matchMedia) {
        backstageTheme = defaultTheme;
        break;
      }
      backstageTheme = defaultTheme;

Context
We want to add Roku Branding including themes, styling, and colors to the backstage app without having to write custom css and components.

We've already designed for this with the theme package and type. It's possible to provide your own theme in the app, and you can use createTheme from the @backstage/theme package to create your own theme using a palette, or creating your completely custom theme by using the lower level functions.
The piece that's a bit wonky atm is the theme switcher in the app. Ideally that'd be an API or component in core that gets reused in the app, but right now the entire implementation is shipped with the example app.
If you scaffold your own app you'd replace the theme that is being imported here with your own.

createTheme doesn't seem to let me use custom fonts... unless I am missing somehting.

Yep, but createThemeOptions and createThemeOverrides are exported, so you can use those to create your own theme with the same overrides.

Agreed! Going far back in the history of this project we experimented with some ideas of how common parts of a plugin page like the header could be replaced at the app level.
Some stuff here: https://github.com/spotify/backstage/blob/00f1d9d8e89dbe2f98f9756971ff0086946ed4d0/frontend/packages/core/src/components/DefaultEntityPage/DefaultEntityPage.tsx#L15
And here: https://github.com/spotify/backstage/blob/4d58971e2b5e604335bb9473c637eeccedcc08b1/frontend/packages/core/src/api/entityView/EntityPageBuilder.tsx#L8
We'll likely revisit that or something similar at some point, exactly for this kind of use-case.

Alright if I close this issue as I think the original question is resolved?

Yes, thanks. However, being able to use the switcher for multiple themes is something we would like.

@Rugvip I would suggest making this more clear in our docs before closing the issue.

Fix the the configurability issues in the app in https://github.com/spotify/backstage/pull/876


Added License, manifest, attributes to setup.py, Mike as Author

Added some last minute packaging additions.
Test package was successfully uploaded here: https://test.pypi.org/project/fair-identifiers-client/

Built with:
python setup.py bdist_wheel
twine upload -r pypitest dist/fair_identifiers_client-0.3.0.dev*-py3-none-any.whl


Nginx container is not starting

Runnig docker-compose up on a just cloned repo give me this error on the wp-local-docker_nginx_1 container.
ERROR: for nginx  Cannot start service nginx: driver failed programming external connectivity on endpoint wp-local-docker_nginx_1 (df6489b1d02353c44134d10de72162c67e01f743433e4eab265d7406fb65188d): Error starting userland proxy: Bind for <IP_ADDRESS>:443: unexpected error (Failure EADDRINUSE)
ERROR: Encountered errors while bringing up the project.

Any help?

You have something else already bound to port 443. If you have other docker containers running that bind 443, you need to stop them. Alternatively, it could be another local development environment running.


When migrating content entries, migration version returned is erroneous if one of the migration entry was created manually

How to reproduce the bug

Init migrations on new environments called environment1 and environment2 using content storage as a method to track migrations. You can use a source environment to duplicate from for both of the environments if you want.
Create a migration and apply it to environment1.
Manually create a migration content entry in environment2 using the Contentful UI.
Run npx migrations content --verbose --diff --source-environment-id environment1 --dest-environment-id environment2
You should see an error like this one: Different migration states detected. environment1<PHONE_NUMBER>544) !== environment2 (2)

Explanation of the issue
While the ID of the migration in environment1 is accurate<PHONE_NUMBER>544), the ID of the migration in environment2 isn't (2) and is the outcome of this line of code:
https://github.com/jungvonmatt/contentful-migrations/blob/bfdca950c60f6012cecf99a82173926b98e2fef0/lib/backend.js#L297
parseInt(item.sys.id, 10) converts the ID of the migration to a number in order to compare them across environments. However, if the migration entry was created manually, the ID is not a number but a string generated automatically by Contentful, like this one: 2txYqBZB1wAHVjtHmvzbcA. It seems like parseInt in this particular case only keeps the 2 and this is what the CLI interprets as the ID of the manually-created migration when comparing migrations between the environments.
Suggestions on how to solve the issue

Add logic to avoid using parseInt on IDs that are not numbers. Consequently, Math.max should not occur when comparing IDs that are not both numbers since it would result in NaN:
https://github.com/jungvonmatt/contentful-migrations/blob/bfdca950c60f6012cecf99a82173926b98e2fef0/lib/backend.js#L347
There is probably more to this since a string ID is not a timestamp and won't really compare with number IDs. The upside of this approach is that the ID of the migration could still surface in the error displayed from the migration content command (for example: Different migration states detected. environment1<PHONE_NUMBER>544) !== environment2 (2txYqBZB1wAHVjtHmvzbcA)), which would hint at the fact that there are IDs that were manually created. The downside is that manually-created migrations might be considered as legitimate as a result of this change, which might not be a good idea.
Warn the user of the CLI that a manually-created entry was found and stop the content-migration process.
It might be possible to use a blend of both approaches, where the ID of the migration is displayed even if the entry was created manually but a warning is also shown to the user to tell them that they shouldn't do that.

@bezoerb @tharders Do you have thoughts about this bug?

Hey @yvesgurcan,
thanks for looking into this.
It is intended that the content migrations only work if the content model is identical in both environments. Thats why i check if the same migrations ran on both environments. The migrations content type was intended more as a kind of private list and ideally no entries should be added within the contentful backend, as these always refer to an associated migration file.
But I realize that the current implementation is not super robust ;)
Maybe we could do something like this:

The version field should be of type number (this is required to stay compatible with the managed by tag strategy)
One could add a help text that says that the entries should not be created manually
After fetching the migration entries, we could filter out all without a corresponding migration file (and show a warning/note)


[c#] Fix metrics tests.

Previously, the tests were failing, but the failure exceptions were getting
swallowed by an async void function. Additionally, this increases the length of
the pause for metrics to settle.

LGTM, I'll merge when the CI ends.


Capture metadata files

This (small) PR adds:

capture metadata.yml files produced by simtools.
corrects the URLs to testing files (pointed to an old branch)
adds a developer notes section to the README, where hints on the peculiar behavior of cwltools can be collected

Tiny comment about unclear text. Also, I can only trust that adding [] after File is necessary, I know very little about cwl to be able to review that.

File[] stands for a list of files: this way we can return log and metadata files at the same time (glob: ["$(inputs.name).log", "simtools-output/*.metadata.yml"].

OK, looks good, thanks!


Fixed nil dereference in core client request function

There is a nil dereference I've encountered after my code has been running for very long periods of time (> 24 hours). Pasted the panic dump I get below. Ultimately traced it back to that line checking the status code, and the only dereference happening in that line is on res, so I treated that same as a 429.
PS - I used two separate clauses for the purposes of clarity, as I thought short-circuiting might make the point less obvious. But short-circuiting is certainly the more concise way to go :)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x12e605e]

goroutine 22215 [running]:
github.com/preichenberger/go-gdax.(*Client).Request(0xc420096140, 0x14dfe4e, 0x3, 0xc42001a960, 0x1e, 0x0, 0x0, 0x1420a00, 0xc4209c6f80, 0x3, ...)
	/Users/jasonvictor/go/src/github.com/preichenberger/go-gdax/client.go:45 +0x13e
github.com/preichenberger/go-gdax.(*Client).GetBook(0xc420096140, 0xc4207af160, 0x7, 0x2, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/jasonvictor/go/src/github.com/preichenberger/go-gdax/product.go:166 +0x1d0
github.com/jwvictor/routefire.(*GDAXUserHandler).OrderBook(0xc420096190, 0xc4206e3f60, 0x3, 0xc4206e3f64, 0x3, 0x0, 0xc4201ca5a0, 0x20002, 0xc420084828)
	/Users/jasonvictor/go/src/github.com/jwvictor/routefire/gdax.go:59 +0x10f
github.com/jwvictor/routefire.GetOrderBookAsync(0x1712d40, 0xc420096190, 0xc4206e3f60, 0x3, 0xc4206e3f64, 0x3, 0xc4200767e0)
	/Users/jasonvictor/go/src/github.com/jwvictor/routefire/consolidatedob.go:28 +0x86
created by github.com/jwvictor/routefire.GetConsolidatedOrderBookConcurrent
	/Users/jasonvictor/go/src/github.com/jwvictor/routefire/consolidatedob.go:56 +0x1047

EDIT: panic dump pasted above


feature/all_jobs_or_only_sidekiq_status_workers

Changes to support having Sidekiq::Status only track the status of jobs specifically including Sidekiq::Status::Worker for use where only the status of certain jobs matter and to reduce the Redis memory usage.

@brampey - Thank you for your PR, I will review these changes and merge if any issues let you know.

@brampey - Can you resolve conflicts?

@pramodshinde :  Yes.  Thought I had already.  I'll take a look at this tomorrow.

@brampey any updates on this?

No updates.  Conflicts resolved?
Bill Rampey
815-353-6494
On Sun, Sep 11, 2016 at 11:34 AM, Pramod Shinde<EMAIL_ADDRESS>wrote:

@brampey https://github.com/brampey any updates on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/utgarda/sidekiq-status/pull/81#issuecomment-246186506,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYV93iL-oAyHZoeIcaQFwmcgjLLySdTks5qpB9qgaJpZM4IJ5Bv
.

@brampey merge conflicts are not resolved yet.

Closing in favor of #113 as the more up-to-date PR


{Packaging} Trim all SDKs instead of biggest SDKs

Description

Trim all sdk in trim_sdk.py. This should save 5M disk space.
Before:

After:

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Packaging improvement


Move travis environment processing into guarded scripts

Propagate Stack id, major, minor, patch versions into build
artifacts in the project (Dockerfile), and in the project templates (pom.xml)
Linter will accept image
Signed-off-by: Erin Schnabel<EMAIL_ADDRESS>Checklist:

[X] Read the Code of Conduct and Contributing Guidelines.

[X] Followed the commit message guidelines.

N/A Stack adheres to Appsody stack structure.

Modifying an existing stack:

[ ] Updated the stack version in stack.yaml

Contributing a new stack:

Describe how application dependencies are managed:

Explain how Appsody file watcher is utilized:

Describe other Appsody environment variables defined by the stack image:

Describe any limitations and known issues:

Related Issues:

This  looks OK from a Kabanero perspective. Slight merge conflict wit h the collections code but that is expected. The travis build seems to work OK. Happy for this to be merged.


balance Explosive Technology

balance ExplosiveTechnology

About the PR

changed Explosive Technology to tier 2 and made the price higher
Why / Balance

Explosive Technology is too strong for tier 1 and 8500 price.Due to the fact that this technology is so easy to learn, 30 explosive charges are being crafted each nuke. This is too unbalanced technology for tier 1
Technical details

changed Explosive Technology to tier 2 and made the price 10000## Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:
-tweak: Explosive Technology changed to tier 2 arsenal and the cost has increased to 10 000

perhaps move the riot control tech down to t1 so that the lower tiers have more items in them. it feels strange to have equal amounts in both.

Explosive tech is needed for tier 1 machines, might need more basic grenade tech for igniters instead or actually why not roundstart?

perhaps move the riot control tech down to t1 so that the lower tiers have more items in them. it feels strange to have equal amounts in both.
that sounds reasonable.

Explosive tech is needed for tier 1 machines, might need more basic grenade tech for igniters instead or actually why not roundstart?

might just make sense at that point to put igniters in autolathe or something with similar parts.

perhaps move the riot control tech down to t1 so that the lower tiers have more items in them. it feels strange to have equal amounts in both.

should I make this a separate pr or redo this one?

just push commits to same branch

should I make this a separate pr or redo this one?

same pr is fine

honestly explosive technology has a lot of stuff that should really be autolathe.  Should be stated in the cl


Building the website

Right now the base page is bcaven.github.io
So the site is stored at bcaven.github.io/creativity-optional-website

[ ] make a different url

[ ]  this might mean making a github user called creativity-optional or something similar

instead of trying to change the url, why don't we just build the website on the original repo?

vue's recommended deployment method
is to have the vue project in one repo and deploy the /dist folder to a second repo. Github pages just displays the second repo.
This will end up looking like this:
we have three repos: creativity-optional, creativity-optional-vue, and creativity-optional-website
creativity-optional is the actual project
creativity-optional-vue is the vue project
creativity-optional-website is effectively just the /dist folder from creativity-optional-vue
Of course, deployment will be automated so as far as we are concerned there are only two repositories to care about: creativity-optional and creativity-optional-vue

End result:
this repository holds the vue source project
to build the project, run ./deploy.sh
the deployed project can be found in this project.
The github pages site is here
for future reference:
we can clean up the deployment process (by making it use npm) as seen in this tutorial but that is the subject of a different discussion.


Add Run button in tools/workflow

It should be a dropdown (just as download). Add test values: A,B,C

OBC sends:
POST request URL: /run
type: workflow or tool
name: string
edit: int

Should receive:
status: ok


Add integration to dynamic db

@ageorgievg thanks for the PR!
Please also add the needed changes for the CF release as well.
Also it seems that releng/sap-kyma/xsk-modules-basis-datasource-0.4.0-SNAPSHOT.jar was added as part of the commit, should it be deleted?

Well no it should be there as currently we are requesting dependencies from this jar and if it is not there the build will fail.

@ageorgievg How about the following, instead of adding the *.jar file as part of the source code, let's reuse what was build in the target folder of the xsk-modules-basis-datasource, so it will be:
COPY ../../modules/basis/basis-datasource/target/*.jar $CATALINA_HOME/lib/

PS: Double check whether /../../*.jar is the correct format for copying all jar files from the target directory.


[Map Pack] Redeem Your Space UT 451b English

Um ... this is a real mess.
It has the 7 Bullets campaign and default UT maps mixed in with RyS (plus odd default UT files like Engine.u, etc).  Not sure what else to say beyond that.

URL: https://unrealarchive.org/mappacks/unreal-tournament/single-player/R/redeem-your-space-ut-451b-english_aa48ba75.html
Hash: aa48ba75f481168d36027508c149cba3165c96e5
Current name: Redeem Your Space UT 451b English

I see this was already brought up. I guess this can be removed since there's already an working 227 version anyway

Hmm, I see it contains BP4 and a bunch of stuff too.
Removing. If anyone wants to try to sort out what the actual pack is supposed to contain, feel free to resubmit.


Dev Stopwatch app

Added a the "Dev Stopwatch" app.
This is a simple stopwatch application supporting 5 laps (cyclically replaced) and reset.
Folder: devstopwatch.

Thanks!


Error initializing dendron: {}

Describe the bug
When I open the dendron workspace, three notifications pop up:

Dendron is active

error initializing dendron: {}

{"ctx":"query","err":"{"message":"gray-matter engine \"id: d40cc1b3-e716-4049-bb9e-493a15887bdf\" is not registered","stack":"Error: gray-matter engine \"id: d40cc1b3-e716-4049-bb9e-493a15887bdf\" is not registered\n\tat e.exports (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:17:80840)\n\tat e.exports (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:302:1068)\n\tat c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:17:16864\n\tat Object.h [as default] (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:17:17124)\n\tat Object.t.mdFile2NodeProps (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:29903)\n\tat t.FileParser.toNode (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:60523)\n\tat c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:61933\n\tat Array.map ()\n\tat t.FileParser.parse (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:61849)\n\tat l.files2Notes (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:56668)\n\tat l._getNoteAll (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:57085)\n\tat l.query (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:57975)\n\tat h.query (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:52612)\n\tat h.init (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:283:50015)\n\tat processTicksAndRejections (internal/process/task_queues.js:94:5)\n\tat async o.execute (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:17:77729)\n\tat async c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:11:80760\n\tat async K.reloadWorkspace (c:\\Users\\User\\.vscode\\extensions\\dendron.dendron-0.11.4\\dist\\extension.js:11:86486)"}"}

The dendron tree view stays empty and the lookup command only suggests creating a new note, ignoring any existing notes.
I tested version 0.11.4, 0.11.5 and 0.11.9, the issue is present in all of those. I created the dendron workspace yesterday without any issues.
To Reproduce
Steps to reproduce the behavior:

Open the dendron workspace.

Expected behavior
Only a notification that dendron is active and all baisc features working.
Desktop (please complete the following information):

OS: Win10
Version

VS Code: 1.49.1
Dendron: 0.11.9

Dendron Log file
{"level":50,"time":1600595791602,"pid":8688,"hostname":"User-PC","name":"dendron","ctx":"query","err":"{\"message\":\"gray-matter engine \\\"id: d40cc1b3-e716-4049-bb9e-493a15887bdf\\\" is not registered\",\"stack\":\"Error: gray-matter engine \\\"id: d40cc1b3-e716-4049-bb9e-493a15887bdf\\\" is not registered\\n\\tat e.exports (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:17:80840)\\n\\tat e.exports (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:302:1068)\\n\\tat c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:17:16864\\n\\tat Object.h [as default] (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:17:17124)\\n\\tat Object.t.mdFile2NodeProps (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:29903)\\n\\tat t.FileParser.toNode (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:60523)\\n\\tat c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:61933\\n\\tat Array.map (<anonymous>)\\n\\tat t.FileParser.parse (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:61849)\\n\\tat l.files2Notes (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:56668)\\n\\tat l._getNoteAll (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:57085)\\n\\tat l.query (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:57975)\\n\\tat h.query (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:52612)\\n\\tat h.init (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:283:50015)\\n\\tat processTicksAndRejections (internal/process/task_queues.js:94:5)\\n\\tat async o.execute (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:17:77729)\\n\\tat async c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:11:80760\\n\\tat async K.reloadWorkspace (c:\\\\Users\\\\User\\\\.vscode\\\\extensions\\\\dendron.dendron-0.11.4\\\\dist\\\\extension.js:11:86486)\"}"}

can you find the note with the following id using vscode regular search? d40cc1b3-e716-4049-bb9e-493a15887bdf
this error appears because the frontmatter of that note is invalid.

It seems like this file is missing (do I interpret correctly that there should be a file with  d40cc1b3-e716-4049-bb9e-493a15887bdf in the name?). Should I reinitialize the workspace? And if I'd do so, can I do that in the current directory or would my existing notes be deleted?

This error is saying that a file with the id of d40cc1b3-e716-4049-bb9e-493a15887bdf has bad frontmatter. you can fix this by opening the file and either fixing it or deleting it. another solution is to initialize a new workspace on a new path

Oh, I could fix the file. I think it would be good, if dendron does not break from one incorrect markdown file.
Anyway, thanks for your help and your work to make note taking better!


LR Sinkhorn improvements

Here are the implementations of the update for the lr-sinkhorn algorithm:

New init using  kmeans
Rescaling of the gamma
New stopping criterion
New implementation for the update of the cost matrices

@meyerscetbon @marcocuturi you can both review it now, there some TODOs left for me, but not critical

Codecov Report

Merging #111 (cb2d89c) into main (2bd0054) will decrease coverage by 6.12%.
The diff coverage is 87.55%.

:exclamation: Current head cb2d89c differs from pull request most recent head 9393e29. Consider uploading reports for the commit 9393e29 to get more accurate results

@@            Coverage Diff             @@
##             main     #111      +/-   ##
==========================================
- Coverage   89.08%   82.96%   -6.13%
==========================================
  Files          45       46       +1
  Lines        4307     4438     +131
  Branches      470      480      +10
==========================================
- Hits         3837     3682     -155
- Misses        358      622     +264
- Partials      112      134      +22

Impacted Files
Coverage Δ

ott/core/quad_problems.py
86.97% <ø> (-3.73%)
:arrow_down:

ott/core/initializers_lr.py
80.17% <80.17%> (ø)

ott/core/sinkhorn_lr.py
92.97% <94.21%> (+0.39%)
:arrow_up:

ott/core/initializers.py
100.00% <100.00%> (ø)

ott/core/sinkhorn.py
94.07% <100.00%> (-0.80%)
:arrow_down:

ott/tools/k_means.py
92.54% <100.00%> (-3.08%)
:arrow_down:

ott/core/discrete_barycenter.py
15.58% <0.00%> (-70.13%)
:arrow_down:

ott/tools/segment_sinkhorn.py
43.75% <0.00%> (-56.25%)
:arrow_down:

ott/tools/sinkhorn_divergence.py
71.42% <0.00%> (-28.58%)
:arrow_down:

ott/tools/soft_sort.py
69.90% <0.00%> (-25.25%)
:arrow_down:

... and 21 more


new plugin: infobox

As discussed in the call with @schul-cloud last week, a plugin for an infobox is desired.
We thought about two possible design ideas that we would like to discuss. As we need the Slate Plugin for editing capabilities these two ideas came to our mind:

Wrap the Slate Plugin in our infobox plugin (i.e. <infobox><Slate /></infobox>)
Extend the Slateplugin with an extra button to toggle the infobox style

How do you feel about these suggestions?
@jprberlin @Knorrke

Hey @FWirtz, thanks for looking into this! I think wrapping the Slate Plugin is ok, but maybe this could also be solved with a Layout Plugin in the ory editor, they already provide a way to wrap other cells and plugins :) see the description in the User Guide for more reference: https://ory.gitbooks.io/editor/content/#how-it-works
Maybe looking at a plugin we wrote a while ago for spoilers will help you: https://github.com/serlo-org/ory-editor-spoiler/tree/master/src
(I want to merge this plugin into this new repository, just didn't get to it yet)

Thanks so much, very helpful!
We will work on that.

So we gave it our best but can't seem to be getting any further based on the docs:
We copied the BlackBorder Layout Plugin, built it and even managed to import it after a couple of tries.
Once we drag it into the ory-editor however it instantly disappears.
We believe that this might be due to a missing createInitialChildren function. We attempted to grab it from the spoiler plugin you suggested but this just causes different errors.
@Knorrke Can you maybe suggest how to implement createInitialChildren properly or even tell us if the immediate disappearing is due to that? That would be really nice 😏

Hey @Blubl good catch, the docs aren't complete there. Probably there was a breaking change, that layout plugins are removed if they're empty... I'll update the docs later this week! Sorry for the inconvenience :-)
As for your question: The way we handled the initialChildrens is, that we initialize the layout plugin with a defaultPlugin as child. So instead of
export default {
  //... plugin definition here
}

it should be
export default ({ defaultPlugin }) => ({
  //... plugin definition here
 createInitialChildren: () => ({
    id: uuid(),
    rows: [{
      id: uuid(),
      cells: [{
        content: { plugin: defaultPlugin, state: defaultPlugin.createInitialState() },
        id: uuid(),
      }]
    }]
  })
})

This makes sense, so the slate plugin can be initialized with additional settings if needed, without changing the infobox plugin.
In order to use the plugin, you have to add it in the example to the layouts and pass it the defaultPlugin like the following:
const plugins = {
  content: [
    //... content plugins here
  ],
  layout: [
    infobox({ defaultPlugin: slate() })
  ]
}

Hope this helps, if you have any trouble getting this to run please feel free to ask! :-) Also it would be great if you document where you have problems with creating a plugin or understanding and running the docs, so we can improve the guides! Thanks for your work

Thanks @Knorrke, we are on it.
Another question: If we take a look at the spoiler plugin, why is there a mismatch between the package.json and the meta section in src/index.js of the plugin regarding the version? One states 0.0.0 and the other states 0.0.1. Are both versions used or can we omit one?
Also, why do the names differ?
In the package.json it's called ory-editor-plugins-infobox, in the title of the src/index.js meta section it's called ory/editor/core/layout/spoiler.
Is the naming in the src/index.js important and according to some conventions or is this irrelevant?
We find this slightly confusing.

Don't know why the versions missmatch, i think keeping these versions the same does make sense. However they (as well as the name) have a different purpose in the package.json and in index.js:
the package.json defines version and name for npm publishing and follows that conventions (the spoiler plugin sn't published atm, so they don't really matter).
The name and version in the index.js however are for the editor itself, so it can serialize and deserialize the plugins. I think there's no convention for this name but it should be possible to include the plugin without name collisions in any website using the ory editor.
So the names and versions in index.js and package.json are not dependent on each other. This means you need both but it doesn't matter if they are the same or not.
Also as a side note: its possible to have multiple plugins in one repo, so you don't have a package.json for each of them. But the way we do it here one can add each plugin individually through npm like having a repo for every one of them

Can I get a Screenshot ...

You sure can @jprberlin, just have a look at the PR. ☺


[WIP] Info bundle command

Add alluxio bundle [OPTION] command  to Alluxio command line. This command will collect information on every host in the Alluxio cluster, tarball the information into a local tarball file, then gather all the tarballs back to where the command is issued.
This command is designed to help troubleshooting and collect information from Alluxio clusters. The collected information include logs, config files and it also executes a set of commands on each of the hosts and include outputs in the tarball.

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/7217/
Test FAILed.

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/7231/
Test FAILed.

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/7264/
Test FAILed.

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/7300/
Test FAILed.

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/7886/
Test FAILed.

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/7887/
Test FAILed.

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/7970/
Test FAILed.

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/7971/
Test FAILed.

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/7973/
Test FAILed.

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/8002/
Test FAILed.

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/8007/
Test FAILed.

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/8008/
Test FAILed.

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/8043/
Test FAILed.

Please ignore the conflict with HEAD now. I will rebase once we settle on the reviews.

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/8070/
Test FAILed.

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/8079/
Test FAILed.

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/8080/
Test FAILed.

Edit: Slightly improved the command names
infoBundle -> collectInfo
infoBundleAll -> collectInfoAll
runAlluxioCheck -> collectAlluxioInfo

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/8081/
Test FAILed.

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/8102/
Test FAILed.

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/8103/
Test FAILed.

AlluxioTestDirectory moving change has been reverted. One potential concern is I had to implement similar temp directory logic in InfoCollectorTestUtils#createTemporaryDirectory.
Another alternative was moving all these tests into integration tests under alluxio/tests. But I would say most of the tests involved are closer to unit tests.

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/8105/
Test FAILed.

@jiacheliu3 have you considered having a single command , and just using an option like --local for just collecting the local info? It is confusing to have 2 commands collectInfo and collectInfoAll

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/8129/
Test PASSed.

AlluxioTestDirectory moving change has been reverted. One potential concern is I had to implement similar temp directory logic in InfoCollectorTestUtils#createTemporaryDirectory.
Another alternative was moving all these tests into integration tests under alluxio/tests. But I would say most of the tests involved are closer to unit tests.

Can we use Files.createTempDir() instead?

AlluxioTestDirectory moving change has been reverted. One potential concern is I had to implement similar temp directory logic in InfoCollectorTestUtils#createTemporaryDirectory.
Another alternative was moving all these tests into integration tests under alluxio/tests. But I would say most of the tests involved are closer to unit tests.

@jiacheliu3 Can we use Files.createTempDir() instead?

@bf8086 AlluxioTestDirectory#createTemporaryDirectory is deleting the temp directory when the JVM exits. That is the reason it works well for tests. I'm adding this logic to InfoCollectorTestUtils#createTemporaryDirectory so it equals Files.createTempDir() + delete temp dir.

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/8142/
Test PASSed.

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/8144/
Test PASSed.

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/8149/
Test FAILed.

@jiacheliu3 have you considered having a single command , and just using an option like --local for just collecting the local info? It is confusing to have 2 commands collectInfo and collectInfoAll

Good idea. Now CollectInfoAll has been merged into CollectInfo and added a --local option as the switch. @gpang PTAL at the new logic now. I may add more unit test coverage tmr.

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/8150/
Test FAILed.

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/8151/
Test PASSed.

@jiacheliu3 Thanks! Can you update the PR title and description with the updated syntax?

@jiacheliu3 Thanks! Can you update the PR title and description with the updated syntax?

This is done. Thanks for the catch!

@ns1123 PTAL now the CollectJvmInfoCommand attempts sudo.

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/8187/
Test FAILed.

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/8188/
Test FAILed.

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/8189/
Test PASSed.

@bf8086 @ns1123 if you have great ideas on improvements that are not low-hanging fruits (like a smarter extra command option), I would propose we leave a mark there and I can address it in the phase 2 improvement on this command. This PR is getting a little too long to keep track and keep focused on all aspects.

LGTM. Thanks @jiacheliu3 for doing this! looking forward to getting to use it.

alluxio-bot, merge this please.


Removed hardcoded grouping.

Description of Work
Fixes #138
Removed hardcoded NIST grouping and restructured the problem directory.
Testing Instructions
Run example_runScripts and see if the right output is given.

Pull Request Test Coverage Report for Build 366

24 of 24 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 64.878%

Totals

Change from base Build 358:
0.3%

Covered Lines:
532

Relevant Lines:
820

💛  - Coveralls

Running is completing on Windows.
One question. I get the warnings:
C:\Midlertiddig\fitbenchmarking\fitbenchmarking\fitting\scipy\nist_def.py:1: RuntimeWarning: overflow encountered in exp  """
C:\Midlertiddig\fitbenchmarking\fitbenchmarking\fitting\scipy\nist_def.py:1: RuntimeWarning: invalid value encountered in add
  """
C:\Midlertiddig\fitbenchmarking\fitbenchmarking\fitting\scipy\nist_def.py:1: RuntimeWarning: overflow encountered in multiply
  """
C:\Midlertiddig\fitbenchmarking\fitbenchmarking\resproc\numpy_restables.py:70: RuntimeWarning: All-NaN slice encountered  min_chi_sq = np.nanmin(accuracy_tbl, 1)
C:\Midlertiddig\fitbenchmarking\fitbenchmarking\resproc\numpy_restables.py:71: RuntimeWarning: All-NaN slice encountered  min_runtime = np.nanmin(time_tbl, 1)

Do you where the nist_def.py:1 warnings originates from?

@Anders-Markvardsen Not sure about the first three warnings, I believe they are there because of minimizers just "failing" in some problems and producing nonsensical values. The last two are due to the fact that all minimizers fail(i.e. they cannot make any progress and produce any values) and return Nan. Hence, a row in the final table will have only Nans.

thanks for removing this hardcoded dependency


pip install fail on Mac M1 Max with Python 3.10.2

I am not able to install the dss_python using pip.
System:
MacBook Pro
Apple M1 Max
macOS Monterey 12.1
pip 22.0.4
Python 3.10.2
Error:

M1 ARM is not supported yet.
We can build for ARM64 Linux already, but we don't have any machines or CI with M1 support, AFAICT.

I just adjusted the build scripts for DSS C-API to include aarch on macOS in the next release PR at https://github.com/dss-extensions/dss_capi/pull/109
I imagine building the Python wheel won't be much harder, but still there is the lack of testing. We could release it anyway and just add a warning to the release notes, but people rarely read those.

I added a cross-compiled wheel:
pip install dss-python==0.12.0b2

Untested, but should work.

The build steps are now integrated in the workflow for GitHub Actions, so wheels for macOS ARM64 are prepared with the rest.

Hi @PMeira, thanks for working on the M1 architecture. I just tested with macOS 12.0.1 on M1 w/ Python 3.9.10 virtualenv, but received an `ImportError:
pip install dss-python==0.12.0b3
python
>>> import dss
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "~/.pyenv/versions/testodd/lib/python3.9/site-packages/dss/__init__.py", line 5, in <module>
    from .v7 import *
  File "~/.pyenv/versions/testodd/lib/python3.9/site-packages/dss/v7.py", line 9, in <module>
    from ._dss_capi import ffi, lib
ImportError: dlopen(~/.pyenv/versions/testodd/lib/python3.9/site-packages/dss/_dss_capi.abi3.so, 0x0002): tried: '~/.pyenv/versions/testodd/lib/python3.9/site-packages/dss/_dss_capi.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_dss_capi.abi3.so' (no such file), '/usr/lib/_dss_capi.abi3.so' (no such file), '~/.pyenv/versions/3.9.10/envs/testodd/lib/python3.9/site-packages/dss/_dss_capi.abi3.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/_dss_capi.abi3.so' (no such file), '/usr/lib/_dss_capi.abi3.so' (no such file)

@charraig Thanks for testing it! Please retry with pip install dss-python==0.12.0b4. A compiler flag was missing in the previous one, so the output libs resulted in mixed architectures.

@PMeira Thanks! I tested the new version and it worked perfectly.


Do Career Path Full-Stack Engineer / 05. Setting Up Your Dev Environment / 05.2 Command Line for Building Websites

Closes in 2b751575163d5372eb8f6902062962e6197ee40d


CU-85zryv83p_Solve-javaS5786-code-smells-in-AppUserDetailsServiceTestjava

CU-85zryv83p - Solve java:S5786 code smells in AppUserDetailsServiceTest.java

Task linked: CU-85zryv83p Solve java:S5786 code smells in AppUserDetailsServiceTest.java


[Admin] Add a group is not working (when no group is configured)

Create a workspace
delete the unique group
try to create a new one => error

duplicate of #96


wgpu base changes

Base changes without adding any wgpu sources:

Remove BGFX
Remove graphics tests & things that depend on it (input/imgui/gizmos)
Bump submodules
Some minor workflow/code changes

I'd rather not merge that PR since it removes some files. And as we are working on the documentation, it will create conflicts between the merge of this PR and before the merge of the final one.

@Kryptos-FR I tried to split up removing BGFX from adding the new code. Thinking we can squash this later.
This might make it a bit easier to review the other PR as there are less removed file changes

@Kryptos-FR I tried to split up removing BGFX from adding the new code. Thinking we can squash this later. This might make it a bit easier to review the other PR as there are less removed file changes

In that case, what we can do is retarget PR #162 to be merged on this branch instead of devel. That way, it will "ignore" all the commits that are here (since that will be the new base) and "hide" the removed files. That will hopefully make it easier to review.
Then when everything is ready, we either retarget again to devel or we first merge into that PR's branch and merge that PR as a final step. In a sense, it is like having an "epic" PR/branch.

@Kryptos-FR I kept the files that have documentation (imgui/input/XR/gizmos) in this PR so it should not cause tree conflicts later on.

@sinkingsugar @Kryptos-FR Will mark these as reviewed and merge to wgpu-stable if you approve.

Good for me, XR files are preserved right?
Also I see some failures in CI.

Yeah, they're all left as-is but disabled until they get fixed up to work with the new graphics.


[2.3] Add node-name param to the end of nodecommand

https://github.com/rancher/rancher/issues/28907

@superseb Yeah we agreed we don't need this fix anymore in 2.3.x. @maggieliu do we still need this?

Ok, I didn't know we no longer need this fix anymore. @kinarashah can you close the PR and the issue and comment on it that it's no longer needed?


[Admin]: To do before next course

Things that need to be done before the next course:

[ ] try out MS teams breakout rooms
[ ] set up Miro board
[ ] set up Teams call with registered participants
[ ] send out email to registered participants with link to prerequisites slide
[ ] split up topics for presentation, esp. consider Simon's former topics "State Management" and "Styling"

We should set up a preparation session for these points