Added some documentation on how to set up the hook

Please check that understand properly. Thanks.

Hi @danielmbarlow, thanks for your contribution. I have left a few comments on the changeset, hope I don't come off as defensive. How is your direnv experience so far ? I'm interested in getting general feedback too.
Cheers,
zimbatm

Yeah, profile loading is a bit of a mess and I've seen little in the way of clear guidance for newbies on the matter.
My preference is to put things like direnv or path modifications in my .profile (which bash will read) and then enable run command as login shell in my terminals.

.bashrc is run whenever bash starts interactively, including if you happen to invoke bash from bash (which you might do via tmux or screen), it will re-do the environment modifications even though they are already present. Whilst not necessarily harmful to re-do environment modifications, I've seen this lead to some confusion (and for example cause it to destroy .bash_history unders some configuraitons).

In fact, I have one thing in my .bashrc, and it's shopt -s histappend, which prevents the history from being destroyed. In my .profile I also have export HISTFILE=~/.my_bash_history which means if a bash instance starts up which doesn't have histappend set, it won't have HISTFILE set either and so it can't possibly destroy ~/.my_bash_history.

That's why direnv is best configured in the .bashrc, it is only needed for interactive bash sessions. The bash extension mechanism happen to depend on an environment variable (PROMPT_COMMAND) but it really is a bash configuration like shopt.

Closing as it no longer merges


integration: wait for ReadyNotify in Issue3699 test

Fixes #5147

LGTM. thanks.

The integration tests failed with leaking routines. I restarted a few times, but still not working. Probably we need to investigate into it before merging this pr.

@xiang90 the rafthttp transport stops before the peer http server stops. A new connection goes through the http server which creates a new pipeline via AddRemote. Since the transport is already stopped it won't be stopped again and so the pipeline goroutines leak.
I added a panic to AddRemote so it fails fast but it looks like the golang http server recovers it away (but it fixes the leak at least).

the rafthttp transport stops before the peer http server stops. A new connection goes through the http server which creates a new pipeline via AddRemote.

If the transport is stopped, we should not reply to the request and thus should not create the pipeline?

@xiang90 yes. Once the transport is stopped, nothing should call into it again. However, if the http server is still active, it'll still try to call into it via rafthttp.ServeHTTP.

However, if the http server is still active, it'll still try to call into it via rafthttp.ServeHTTP.

This is the receiver side of the rafthttp, right? Once it receives a message, it might deliver that into raft and then raft will generate output. But at that point, the sender side, which is the transporter should be stopped. No messages should be accepted I think.

A new connection goes through the http server which creates a new pipeline via AddRemote

Also it seems like etcdserver will only call addRemote during initialization? After that etcdserver should not call addRemote.

@xiang90 I don't understand what you're getting at. The problem is that rafthttp has no control over the http server / listener lifetime. The http handler streamHandler isn't bound to a connection so even if the transporter is stopped, if a new connection is established, the handler would see there is no remote and try to create a new pipeline via AddRemote and leak it.
rafthttp calls AddRemote because of the X-PeerURLs header which was a fix so a node could communicate with members that were added while it was down.

@heyitsanthony Oh. Now I understand it. I thought it was the etcdserver that add the remote back, but it is the streamHandler actually.

lgtm


Changing the "sent" checkbox causes the EDCT time to vanish

Will be fixed with #83

This is fixed


Consolidated BOM

Do you think it'd be possible to add a consolidated BOM somewhere? Most of the large non-printed parts, like the major electronic components, are mentioned in the README or in the videos, but there are still some things I'm not sure what / where to buy, such as:

the springs for the base suspension
the casters
the vertical timing belt (and maybe some other components to the vertical drive that I missed)
fasteners (I know use use 2.9mm self tapping threads in a few places, but it seems there's at least one other kind of fastener)
the bearings (though I could probably figure this out at least)

I know it might be a bit tedious, especially with the fasteners, but I think it'd be a big help to people trying to recreate this project.
If you want to send me a CSV / spreadsheet / Google Sheet link, I can also help format the BOM as a Github Markdown table if you'd like, perhaps in the README.
Thanks!

I've added the vertical belt details to the readme.
The springs I have are actually too tight - they were just some springs I bought off eBay, so you'd be better trying some experimentation here.
The casters are some 50mm ones I had in my spares box, the CAD shows placeholders for the envelope so again, you'd need to see what you can find locally and potentially modify the design to the height correct.
There are a few M4 socket cap bolts in it, but that's about it?
Wheel bearing sizes are shown in the CAD.

I've added the vertical belt details to the readme.
The springs I have are actually too tight - they were just some springs I bought off eBay, so you'd be better trying some experimentation here.
The casters are some 50mm ones I had in my spares box, the CAD shows placeholders for the envelope so again, you'd need to see what you can find locally and potentially modify the design to the height correct.
There are a few M4 socket cap bolts in it, but that's about it?
Wheel bearing sizes are shown in the CAD.


Add parallelization support to preprocessing script

There are also some other parallelization opportunities in the rest of the code, but I wasn't sure if there are any dependencies or race conditions involved. If you're interested in more parallelization here, could you tell me what parts of the code depend on each other? For example, are calls to process_metadata_file in create_VCTKmix_from_metadata.py safe to parallelize?

Thanks a bunch for the PRs !
Have you seen this one? https://github.com/JorisCos/LibriMix
There is even more chance to parallelize there :smile:

Haha, yes, but not really interested in using that at the moment. I can give it a try to parallelize but I don't have any hardware with fast enough internet connection and enough disk space at the moment.


I am trying to set up forward search for tex and zathura using texlab, and instructions from https://texlab.netlify.app/docs/reference/configuration. (It is mentioned to check this out in the instructions about texlab nvim-lsp config).
I have the following in my init.vim:
lua << EOF
local lspconfig = require'lspconfig'
lspconfig.texlab.setup{
  settings = {
    latex = {
      build = {
        onSave = true;
      },
      forwardSearch = {
        executable = "zathura",
        args = {"--synctex-forward", "%l:1:%f", "%p"},
        onSave = true;
      }
    }
  }
}
EOF

Build-on-save works, but I do not get forward synctex. Zathura does not even start. Checkhealth shows no problems, and I get no complaints, just nothing happening in terms of forward search. Using NVIM v0.5.0-dev+950-g5ce328df4. Any ideas?

Can you paste a log? Add vim.lsp.set_log_level("debug") your the lua portion of your config and upload $HOME/.local/share/nvim/lsp.log.

Sure - take a look at the attached.
lsp.log

There aren't any errors, I'm wondering if this is a client-side deficit (as in, it specifies we need to support SyncTeX?). Can you explain briefly what forward search is and what is currently missing? I use emacs for LaTeX (and have used a vimtex in the past), so I'm not super familiar with the built-in capabilities. Can you provide a minimal init.vim and tex document?

Forward search should be able to take you to the part of the pdf that your cursor is when you save/build your tex file. This is the purpose of synctex. In principle it can also do backwards search, double clicking in the pdf should take you to the file, but it is more complicated.
You can use any plain vanilla init vim and tex file - just put the lsp support (as I have) and try to test it. Just for info: vimtex is able to do both backwards and forward search. The page at https://texlab.netlify.app/docs/reference/configuration shows how to implement this (I followed the ideas), but I guess it pertains to vs code (seeing how it is written)...

ok, I have changed my setting a bit to:
local lspconfig = require'lspconfig'
vim.lsp.set_log_level("debug")
lspconfig.texlab.setup{
  settings = {
    latex = {
      rootDirectory = ".",
      build = {
        args = { "-pdf", "-interaction=nonstopmode", "-synctex=1", "-pvc" },
        forwardSearchAfter = true,
        onSave = true
      },
      forwardSearch = {
        executable = "zathura",
        args = {"--synctex-forward", "%l:1:%f", "%p"},
        onSave = true
      }
    }
  }
}

This now opens the pdf upon build, but I cannot do anything about forward Search. But I did notice that only the function

TexlabBuild: Build the current buffer
is implemented. There are more functions implemented in the description at the Texlab page. I guess ForwardSearch has not been implemented yet? Who should I reach out to for this?

There's an open PR implementing forward search https://github.com/neovim/nvim-lspconfig/pull/420

ok, thanks, I have put a comment there to hopefully get some attention.

right, so with the latest nightly (v0.5.0-dev+975-ga58c5509d) there is not even plain building with TexlabBuild. A "Build success" returns, but nothing happens.

I would file another issue, as it's unrelated to this one, but I don't see any changes that would affect it. In general I would recommend checking the log, and then doing a git bisect to nail down which commit caused the issue.

hmm, ok, but is there noone else using this? Have you tried it yourself?

I'm going to close this issue as it was closed by #420, and open another issue tracking the problem (I've identified it)

hmm, ok, but is there noone else using this? Have you tried it yourself?

should be like this :
lua << EOF
local lspconfig = require'lspconfig'
lspconfig.texlab.setup{
settings = {
texlab = {
build = {
onSave = true;
},
forwardSearch = {
executable = "zathura",
args = {"--synctex-forward", "%l:1:%f", "%p"},
onSave = true;
}
}
}
}
EOF


Optimize Bit-Shift Operations for FPGA Implementation

Hi everyone,
I have investigated the possibility to optimize the bit-shift operation on FPGA targets by using Multipliers to incorporate the logic. I have drafted two versions of this. 'NoFlatten' and 'Rebuilt' refer to the FLATTEN_HIERARCHY synthesis attribute used when generating the results.

ibex_alu_dspshift.sv
Two 16x16 multiplier units describe left shifts. The resulting upper and lower bit arrays are reordered using the shift amount MSB. Concatenation is handled via addition, using one more DSP.
DSP Utilization: 3
Total LUT Utilization: 2478 / 2334 (NoFlatten / Rebuilt)

ibex_alu_circulardspshift.sv
Cyclic barrel shifter, using 4 8x16 bit multipliers. The two MSB of shift_amt are used for the byte ordering MUX. Right shifts are done by shifting by 32-shift_amt. The results are generated using a bitmask for shifted-out bits. Idea from: Implementing Barrel Shifters Using Multipliers

DSP Utilization: 4
LUT Utilization: 2440 / 2339 (NoFlatten / Rebuilt)

The baseline implementation's resource utilization is:
Total LUT Utilization: 2486 / 2339

We can see a slight improvement when we prohibit hierarchy flattening during synthesis. However by when synthesising with the default settings, no improvements are observed.
I suggest to not persue the issue further.

Thanks @ganoam for reporting your findings here. I also think it is not worth to explore further in this direction.

I am closing this issue. The conclusion here is to not investigate further.


Legend plate missing texture

In the latest version of pixelmon the legend plate has a missing texture

Thanks for letting me know!  Reproduced, fixed, and uploaded v1.1.2 with the fix.


Inquiry About the Frame Rate

This article is really great, and I would also like to know how many frames per second it is. Thank you for your generous explanation.

Hi, thanks for your interest! We use an FPS of 2.


Add Dockerfile COPY support

addFile (...) and such are not very helpful when all you really want to do is add a tar.gz file into the container without expanding it. Please consider adding a copyFile method that adds a docker "COPY" statement to the Dockerfile.

This is fixed in master and will be part of upcoming version 1.3


Set Swagger API response cache control header

API responses currently don't set a caching policy. This causes weird behaviour in some browsers where they return a cached response which is different from expected. See VSTS #3971 which was a result of this.
I don't think there's ever a scenario where we want the browser to cache these values, so we should be able to set the Cache-Control header to no-cache to prevent this happening.

have you seen this?
https://docs.microsoft.com/en-us/aspnet/core/performance/caching/middleware?view=aspnetcore-2.2
in the example you'd see how to setup header using dotnet classes

@rowandh Can you confirm that is working as expected? Also, just confirm that you have done a quick random check to some other API endpoints to see that all is as expected.

to clarify my comment above, I mean that the middleware (implicit in this case, without having a class for that, but I'm not against an explicit middleware) can be something like
app.Use(async (context, next) =>
            {
                // For GetTypedHeaders, add: using Microsoft.AspNetCore.Http;
                context.Response.GetTypedHeaders().CacheControl =
                    new Microsoft.Net.Http.Headers.CacheControlHeaderValue()
                    {
                        NoCache = true,
                        NoStore = true
                    };

                await next();
            });

@fassadlr I've tested a few endpoints, core wallet, and the same browser that caused the problems. It all appears to be working.
@MithrilMan that just looks like a different way to achieve the same thing. Only benefit I see is perhaps the strong typing.


Feat/update template

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Layer kwarg ignored for fiona.open with Bytes files

Expected behavior and actual behavior.
Expected: Opening a Bytes stream with fiona.open and a specific named layer returns a collection for the named layer.
Actual: Returns the first (default layer) as specified by fiona.listlayers
Steps to reproduce the problem.
# Where afile is any file and mylayer is NOT the default layer
with fiona.open('afile', layer='mylayer') as f:
    print(f.name)

with open('afile', 'rb') as f:
    with fiona.open(f, layer='mylayer') as ff:
        print(ff.name)

Operating system
Linux: 5.2.1-arch1-1-ARCH
Fiona and GDAL version and provenance
Fiona==1.8.6 via pip 19.0.3

I can reproduce this and have found a solution. Putting together a PR.

So fast! Looks like a quick fix. I'll test locally tomorrow

Sorry for replying on a long-closed issue, but is this ever going to make it into a released version? The latest release (1.8.20) still doesn't pass the args to memfile.open.


Daily Digest

allow people to sign up to receive the top products of the day via email

+1

@jacquescrocker i'd be happy to lend a hand with this - templates / ideas / etc. I run the Devpost weekly newsletter + Git@Me (my own about open source projects)

@nealrs thanks!

via hn https://news.ycombinator.com/item?id=10762846
"Don't do daily... or atleast let people sign up for daily/weekly/monthly. The PH daily emails were too much.

email subscription (for daily) is now deployed
we'll do the daily one first, then add an option for weekly later

I agree. Weekly should be easy after daily is setup, it's just about gathering the appropriate buckets for the week.
The daily digest preparation is done, will be moving on to the 'send' part today.


3044 menu button style audit button variations

Closes #3044
Summary
Fixed the styling remarks from #3044 and also fixed some additional RTL issued. In order to understand the changes it is easiest to go through the commits one by one.
Change List (commits, features, bugs, etc)

Fixed button and menu item sizes according to the spec  + unit tests
Added button variations (kind) according to the spec + unit tests
Fixed the shadow from the menu that was incorrectly dropping in the button (complex fix needed) + unit tests
Fixed additional RTL issues

Acceptance Test (how to verify the PR)
Start by reading the spec.

Go to https://deploy-preview-3185--carbon-addons-iot-react.netlify.app?path=/story/2-watson-iot-experimental-☢-menubutton--single-menu-button and use the size knob to verify that the sizes renders according to spec. Note, we use "default" instead of large until carbon v.11

Repeat step 1 for https://deploy-preview-3185--carbon-addons-iot-react.netlify.app?path=/story/2-watson-iot-experimental-☢-menubutton--split-menu-button and https://deploy-preview-3185--carbon-addons-iot-react.netlify.app?path=/story/2-watson-iot-experimental-☢-menubutton--icon-only-menu-button

Verify that https://deploy-preview-3185--carbon-addons-iot-react.netlify.app?path=/story/2-watson-iot-experimental-☢-menubutton--single-menu-button renders the different kinds of buttons available in the kind knob and that the button and the menu looks as expected. Compare to the spec.

Verify that https://deploy-preview-3185--carbon-addons-iot-react.netlify.app?path=/story/2-watson-iot-experimental-☢-menubutton--split-menu-button renders the different kinds of buttons available in the kind knob and that the button and the menu looks as expected. Compare to the spec.

Go to https://deploy-preview-3185--carbon-addons-iot-react.netlify.app?path=/story/2-watson-iot-experimental-☢-menubutton--auto-positioning-example and for all COMBINATIONS of positions, sizes and RTL-mode for the IconOnlyButton verify that:
a) the shadow from the menu does not fall on the button (for any state of interaction)
b) the blue focus border of the menu is intact
c) the blue focus border of the button is intact (to test this click the button to open the menu and then press down on the button with the mouse again but move the cursor outside the button before releasing)

Regression Test (how to make sure this PR doesn't break old functionality)

All stories work as before except for the changes described by the spec.

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

This looks great. The only question I'm uncertain about is the extra space at the top and bottom of a menu item (It's easily visible when hovering "Delete" or "Publish"). It doesn't seem to be part of the spec, but it's hard to know for certain.

I don't know either. It was not introduced by these changes, it is the standard carbon padding on the surrounding bx-menu element so it is only available above the first item and below the last item. The carbon bx--menu-divider also has  top-bottom padding which is what we seen in the screenshot.
@dianatran18 Should we remove the padding for the bx--menu and bx--menu-divider?

This looks great. The only question I'm uncertain about is the extra space at the top and bottom of a menu item (It's easily visible when hovering "Delete" or "Publish"). It doesn't seem to be part of the spec, but it's hard to know for certain.

I don't know either. It was not introduced by these changes, it is the standard carbon padding on the surrounding bx-menu element so it is only available above the first item and below the last item. The carbon bx--menu-divider also has top-bottom padding which is what we seen in the screenshot. @dianatran18 Should we remove the padding for the bx--menu and bx--menu-divider?

Let me confirm with the Carbon folks because that was a change I saw more recently too. I don't know if they're moving towards having padding on the bottom like that, but I know there's padding between divider lines now, which is new from before.

This looks great. The only question I'm uncertain about is the extra space at the top and bottom of a menu item (It's easily visible when hovering "Delete" or "Publish"). It doesn't seem to be part of the spec, but it's hard to know for certain.

I don't know either. It was not introduced by these changes, it is the standard carbon padding on the surrounding bx-menu element so it is only available above the first item and below the last item. The carbon bx--menu-divider also has top-bottom padding which is what we seen in the screenshot. @dianatran18 Should we remove the padding for the bx--menu and bx--menu-divider?

Let me confirm with the Carbon folks because that was a change I saw more recently too. I don't know if they're moving towards having padding on the bottom like that, but I know there's padding between divider lines now, which is new from before.

@bjornalm I confirmed with the Carbon designer that for overflow menus and combo/menu buttons there will be no padding. It is only for the Carbon context menu where there is padding.

Lauren Rice:rice:  12:19 PM
The context menu will have the padding, but the combo button / menu button / overflow menu will not have the padding.

So it should be like this (let me know if this makes sense and if I've missed any other areas)

@dianatran18
An update on the left menu item indentation:
I went through the carbon code for the menu to make sure I didn’t write a workaround for something that already existed, and it turns out that only if there are any selectable menuItems (MenuSelectableItem) then the indentation element showing the icon will be added.

So this means:

a list without any indentation and icons will be automatically created by using only “normal” menu items (MenuItem)

if we want custom icons on the left side like in our stories we also have to include at least one MenuSelectableItem

@JordanWSmith15 is number 2 ok with you

LGTM!


How to use CSS Variables?

What are you trying to do?
Use CSS variables with the custom angular material theme.
What troubleshooting steps have you tried?
I can successful get css variables working except the opacity doesn't apply correctly.
As stated in this comment.
https://github.com/angular/components/blob/25665dcc219fbbb76d0ba7f79982672500f78644/src/material/core/theming/_theming.scss#L79-L84
We used to be able to overwrite the function but not sure how now that scss modules @use are implemented.
See angular-material-css-vars
Reproduction
A great library for css variables that works with Angular 11:
angular-material-css-vars
I created a simple example in Angular 12:
material-css-vars
Environment

Angular: 12
CDK/Material: 12
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

This is somehow connected to #4352 - if you can use MDC components, they should work with CSS vars.
That said, I think there is a very simple solution for Angular to support this case right now. As pointed out, the theming core already checks if the resolved value is an SCSS color. Angular could also check if it is an SCSS function, and if yet call it:
@if (meta.type-of($color) == function) {
  @return meta.call($color, $opacity, $hue);
}

Then a library like angular-material-css-vars can just pass functions as palette elements that do the necessary work of creating the right CSS expressions.

I retract my previous statement that you can use MDC components with CSS variables. The current implementation on Angular's side does things like:
mdc-theme-color.$on-primary:      if(mdc-theme-color.contrast-tone(mdc-theme-color.$primary) == 'dark', #000, #fff);

This obviously won't work with variables in the theme. I'll try to make a PR that implements the approach I described previously.

Partial duplicate of #22822 and #4352
For the time being, we don't explicitly support theming via css variables. Some people have had success putting css variables in the values of a palette, but we unfortunately can't explicitly support this because, going forward, MDC Web will be doing compile-time calculations of provided values to produce styles.
That said, now that we're dropping IE11 support in v13, we're looking at how we can explicitly support css variables.


support for other isoform quant methods?

This is a nice contribution. Have you considered supporting other isoform quant methods such as kallisto, RSEM, or sailfish? I notice only cufflinks/fpkm and mmseq are supported currently.

We tried RSEM when the manuscript was being prepared. Unfortunately I
couldn't find the option of outputting estimation uncertainty from RSEM
(maybe I overlooked something...) I have not yet used the alignment-free
methods such as kallisto or sailfish, and I'm not entirely sure whether I
can get them to output the standard deviation of their estimates, but I
will try to add them to the future release if it's possible. Also, I think
I can get Salmon (a sailfish relative I believe) to work. Currently I'm
working on a different project so the support might be a bit delayed, but
it will make it into the next release. :] Thanks for pointing that out!!
Cheng Jia
Ph.D. Candidate Department of Biostatistics
Perelman School of Medicine, University of Pennsylvania
503 Blockley Hall
423 Guardian Drive
Philadelphia, PA 19104
Phone: +1(215)760-7845|Fax: +1(215)573-1050
On Fri, Nov 20, 2015 at 6:42 PM, kkdang<EMAIL_ADDRESS>wrote:

This is a nice contribution. Have you considered supporting other isoform
quant methods such as kallisto, RSEM, or sailfish? I notice only
cufflinks/fpkm and mmseq are supported currently.
—
Reply to this email directly or view it on GitHub
https://github.com/jiach/MetaDiff/issues/1.


Make Modal for incident viewer

This is a potential solution to not unselect ISPs but still allow users to interact with those that have incidents.
If MLab doesn't have a Modal component, React Bootstrap has one we can build off of:
https://react-bootstrap.github.io/components/modal/


Can not run test (on Windows 10)

Thanks for this awesome project help me to save the time.
And as title, it's working well on Windows using npm start, but when I try to run the test using npm test, it just fails with the error message:
E:\Projects\aqua>npm test

><EMAIL_ADDRESS>test E:\Projects\aqua
> lab -t 99 -S -T ./test/lab/transform ./test/lab/client-before.js ./test/client/ ./test/lab/client-after.js ./test/server/ ./test/lab/server-after.js ./test/misc/

Warning: Invalid argument supplied to oneOfType. Expected an array of check functions, but received undefined at index 2.
E:\Projects\aqua\test\client\pages\admin\components\filter-form-fixture.jsx:26
            <div>
            ^

SyntaxError: Unexpected token <
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at ....

I also try it on my Mac, and it can run all tests(although there are some tests fail).
Does somebody meet the same situation? Could fix this problem? Thanks.

SyntaxError: Unexpected token <

Sounds like something isn't setup properly. Possibly related to babel and/or jsx not being parsed correctly.

I've decided to archive this project. Thank you for your interest and contributions.
https://github.com/jedireza/aqua#no-longer-maintained


Improvement: Update hygen to have camel case in domain entity

Updated the hygen templates to follow camel case naming in domain entity and dtos
Updated the add property templates to have camel case in domain entity and dtos
Updated the mappers to accordingly

Looks good. Hopefully we have tested as well by creating the CRUDs and adding properties etc.

Looks good. Hopefully we have tested as well by creating the CRUDs and adding properties etc.

Yes it's tested by creating resources and adding properties.

awesome, will be merged, as per the timelines shared in the audio note on slack

should we update all the existing resources as well to camel cases as well. Just to be in sync with this approach. Omer and Hassan has updated them in the MOTAC project. We can ask them to update here as well


Organization logo#241

I also thought to make all the saving logic in the create organization endpoint, but it turned out to be quite messy, the JSON will be oversaturated with an encoded image + organizationDTO. I think its better this way, while we maintain implicit connection through organization name, we have a decomposed logic for logo saving.


Allow specifying different noise equations for different Y-values within a biome.

Rework the noise-equation key within biomes to allow specifying different noise equations for different heights. Also rename the key to generation
New configuration example:
generation:
  68: "((-((y / base)^2)) + 1) + |(noise2(x, z) / 3) + 0.1|"

Would use the equation ((-((y / base)^2)) + 1) + |(noise2(x, z) / 3) + 0.1| at Y=68 and below, otherwise would default to 0.
Noise values would still be lerped, allowing basic blending between different equations. Blending would not be as advanced as inter-biome blending.
The special constant top would be a valid key, specifying the highest point of the world.
This would specifically allow for significant performance boosts, especially with 1.17 around the corner, using configs such as:
generation:
  68: "((-((y / base)^2)) + 1) + |(noise2(x, z) / 3) + 0.1|"
  54: "1"

This configuration would only calculate noise for Y=54-68, and use the constants 0 or 1 for everything else. This would grant significant performance boosts, especially with 1.17's 384-block tall worlds.
When doing this, we should also make a simple pack conversion utility, that just removes the noise-equation line from configs it is present in, grabs the equation, and inserts
generation:
  top: <equation>

This utility would be very simple to make, and would make updating packs a super simple process.

World gen glitches are normally good and often should stay.


Move GitHub project to Terraform Cloud

This allows us to use Terraform Cloud to plan and apply the Terraform to conifgure GitHub instead of doing it locally.

Oops sorry both, didn't see you'd already assigned a reviewer!

@sengi no problem! Which CKAN vars did you mean?


Update our company logo

We should replace the OIs logo with TNX. Is this repo cloned somewhere on O:? I can copy the .png and commit it to update the README.md

Hi Kai,
We can update text and images within the repo, but the web address cannot be changed. Therefore, it would stay https://github.com/CancerDataNet-OIS/CDN-OIS-Resources/
Since there is not so much in this repo so far, I propose to create a new organisation including TNXO as a name.

I think that's fair. It shouldn't be too difficult to copy over the wiki, otherwise there isn't much here.


Generated Widgets section take space when empty.

Will be fixed with https://github.com/wso2/analytics-apim/issues/810


feat: adding local variables in banner, chart and contextualbar

create local vars for chart: padding-x and padding-y of chart will predefined by variables
refine custom background image for banner and contextualbar

@adenvt conflict was resolved.


Update protobuf install to use correct repository

The protobuf repository is under the protocolbuffers org
NOTE: The Github redirect which was being used before seems to have broke

I opened #5804 before seeing this one! Can you update the download links in BUILDING.md as well?

I opened #5804 before seeing this one! Can you update the download links in BUILDING.md as well?

Maybe use/re-open #5804 with just the change commit for BUILDING.md so we can get this merged quickly to get CI back in operation?

Since the Windows failure is a common flaky test and we have CI down, I'm going to merge given the pulls from the new location worked for protobuf


[HUDI-1792] Fix flink-client query error when processing files larger than 128mb

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
fix flink-client query error when processing files larger than 128mb
Use the flink client to query the cow table and report an error. The error message is as follows:
Caused by: org.apache.flink.runtime.JobException: Creating the input splits caused an error: org.apache.hadoop.fs.HdfsBlockLocation cannot be cast to java.lang.Comparable 	at org.apache.flink.runtime.executiongraph.ExecutionJobVertex.<init>(ExecutionJobVertex.java:260) 	at org.apache.flink.runtime.executiongraph.ExecutionGraph.attachJobGraph(ExecutionGraph.java:866) 	at org.apache.flink.runtime.executiongraph.ExecutionGraphBuilder.buildGraph(ExecutionGraphBuilder.java:257) 	at org.apache.flink.runtime.scheduler.SchedulerBase.createExecutionGraph(SchedulerBase.java:322) 	at org.apache.flink.runtime.scheduler.SchedulerBase.createAndRestoreExecutionGraph(SchedulerBase.java:276) 	at org.apache.flink.runtime.scheduler.SchedulerBase.<init>(SchedulerBase.java:249) 	at org.apache.flink.runtime.scheduler.DefaultScheduler.<init>(DefaultScheduler.java:133) 	at org.apache.flink.runtime.scheduler.DefaultSchedulerFactory.createInstance(DefaultSchedulerFactory.java:111) 	at org.apache.flink.runtime.jobmaster.JobMaster.createScheduler(JobMaster.java:345) 	at org.apache.flink.runtime.jobmaster.JobMaster.<init>(JobMaster.java:330) 	at org.apache.flink.runtime.jobmaster.factories.DefaultJobMasterServiceFactory.createJobMasterService(DefaultJobMasterServiceFactory.java:95) 	at org.apache.flink.runtime.jobmaster.factories.DefaultJobMasterServiceFactory.createJobMasterService(DefaultJobMasterServiceFactory.java:39) 	at org.apache.flink.runtime.jobmaster.JobManagerRunnerImpl.<init>(JobManagerRunnerImpl.java:162) 	at org.apache.flink.runtime.dispatcher.DefaultJobManagerRunnerFactory.createJobManagerRunner(DefaultJobManagerRunnerFactory.java:86) 	at org.apache.flink.runtime.dispatcher.Dispatcher.lambda$createJobManagerRunner$5(Dispatcher.java:478) 	... 4 more Caused by: java.lang.ClassCastException: org.apache.hadoop.fs.HdfsBlockLocation cannot be cast to java.lang.Comparable 	at java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:320) 	at java.util.ComparableTimSort.sort(ComparableTimSort.java:188) 	at java.util.Arrays.sort(Arrays.java:1246) 	at org.apache.hudi.table.format.cow.CopyOnWriteInputFormat.createInputSplits(CopyOnWriteInputFormat.java:212) 	at org.apache.hudi.table.format.cow.CopyOnWriteInputFormat.createInputSplits(CopyOnWriteInputFormat.java:64) 	at org.apache.flink.runtime.executiongraph.ExecutionJobVertex.<init>(ExecutionJobVertex.java:247) 	... 18 more
The reason is that the implementation object of FileSystem is hadoop, and the BlockLocation implementation class of the getFileBlockLocations method to obtain the block does not implement the compare method. Here, the Arrays.sort method is used for sorting. When the number of blocks is greater than 1, the comparison will report an error. I think the CopyOnWriteInputFormat class imitates FileInputFormat for block fragment acquisition and sorting. The FileInputFormat class implements HadoopBlockLocation to obtain fragmentation information for sorting, and HadoopBlockLocation implements the compareTo method. Here modify the implementation of the incoming inner class to do sorting.
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@hj2016 Since this fix is hard to write test. Did you test it in your local env?

of course.
Before fixing the problem:

After fixing the problem:

of course.
Before fixing the problem:

After fixing the problem:

Great!


CASMINST-3171 Add necessary binary, cut

@heemstra , when this merges we can just fast-forward release/csm-1.0 to main (they are linear and up-to-date):
[551]rusty@C02F43JEMD6P:~/gitstuffs/cray-shasta/dracut-metal-mdsquash>     git push --set-upstream origin bugfix/CASMINST-3171-missing-cut
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 12 threads
Compressing objects: 100% (4/4), done.
Writing objects: 100% (5/5), 447 bytes | 447.00 KiB/s, done.
Total 5 (delta 3), reused 0 (delta 0)
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote:
remote: Create a pull request for 'bugfix/CASMINST-3171-missing-cut' on GitHub by visiting:
remote:      https://github.com/Cray-HPE/dracut-metal-mdsquash/pull/new/bugfix/CASMINST-3171-missing-cut
remote:
To github.com:Cray-HPE/dracut-metal-mdsquash.git
 * [new branch]      bugfix/CASMINST-3171-missing-cut -> bugfix/CASMINST-3171-missing-cut
Branch 'bugfix/CASMINST-3171-missing-cut' set up to track remote branch 'bugfix/CASMINST-3171-missing-cut' from 'origin'.
[552]rusty@C02F43JEMD6P:~/gitstuffs/cray-shasta/dracut-metal-mdsquash> git checkout main
Switched to branch 'main'
Your branch is up to date with 'origin/main'.
[553]rusty@C02F43JEMD6P:~/gitstuffs/cray-shasta/dracut-metal-mdsquash> git pull
git mergeAlready up to date.
[554]rusty@C02F43JEMD6P:~/gitstuffs/cray-shasta/dracut-metal-mdsquash> git merge --ff release/csm-1.0
Already up to date.

Note: also merging this into main (fast-forward merge from release/csm-1.0 to main).

issue will still exist in main, so this fix will patch both branches.


Add latency suppor to Resque via an extension / plugin / monkey-patch

Queue latency is a much better metric to perform scaling on, but Resque
doesn't have a built-in way of calculating that, only the depth / size
of a queue is provided.
This extends Resque to track a new "timestamp" attribute with each job
enqueued / pushed to the queue, and use that timestamp information from
the oldest job present in the queue when we ask for the latency of that
queue, which is essentially the time difference between now and that
oldest job timestamp.
This will allow Judoscale to better handle scaling for Resque workers,
as well as make Resque work like the other libraries that already
provide latency and scale based on that.
I have not removed queue depth metric tracking here, but this is
something that may happen in the future.
Samples

@adamlogic I pushed a second commit adding some tests to the latency extension: https://github.com/judoscale/judoscale-ruby/pull/100/commits/754ab11b655006b5883c3e89e03649f52b39c1cd, I created a small redis stub object that Resque will use in place of the Redis instance, which should allow this to run without redis while still ensuring the Resque extension bits we are interested in are working.


Kiosk-Friendly Display Mode with Credential Passing and Auto-Hide Notifications

📑 I have found these related issues/pull requests
This feature request aims to enhance Uptime Kuma's usability in kiosk environments, commonly used for support and monitoring displays, by allowing credential passing through URLs and implementing auto-hiding notifications for resolved downtimes.
🏷 Feature Request Type
Dashboard
🔖 Feature description
Problem Statement: In many support and monitoring scenarios, displays are set up in a kiosk mode, which limits their ability to interact with input devices and retain credentials across sessions. Currently, there's no straightforward way to maintain an authenticated session without manual re-login, making it less practical for kiosk use. Additionally, notifications for resolved downtimes persist on the screen until manually cleared or the device is restarted, which isn't feasible without direct interaction capabilities.
Impact: Enhancing Uptime Kuma for kiosk use would significantly benefit organizations that rely on real-time monitoring dashboards displayed across various locations without direct human interaction for each display. It would improve the visibility of system health and reduce the maintenance overhead for managing these displays.
Implementing these features would make Uptime Kuma more adaptable to a wider range of monitoring scenarios, especially in environments where displays are not directly managed but need to stay informative and current with minimal setup and maintenance.
✔ Solution
URL Credential Passing: Introduce a secure method to pass credentials through URLs or a token-based authentication mechanism that can be embedded in the URL. This approach would allow kiosk screens to automatically authenticate and display the dashboard without manual login, respecting security and privacy standards.
Auto-Hiding Notifications: Implement a feature where notifications, especially those indicating resolved downtimes, automatically disappear after a configurable duration. This ensures that the display remains clean and relevant, focusing on active issues without manual intervention.
❓ Alternatives
No response
📝 Additional Context
Security Considerations: Highlight the importance of implementing the URL credential passing feature in a way that does not compromise security, such as expiring tokens or encrypted parameters.
User Experience: Emphasize the importance of a seamless experience for displays running in kiosk mode, where manual intervention is minimal to none.
Configuration Flexibility: Suggest the ability for users to configure the auto-hide duration for notifications, catering to different preferences and needs.

usability in kiosk environments

Why not use a status page for this?

Auto-Hiding Notifications

This is configurable in the upcoming v2.0 release.
See #3441

URL Credential Passing

From a security perspective, I don't think this is a good idea.
You likely would leak credentials to users.
Counsider disabling auth instead.

I am going to close this as resolved, as

the auth part of the issue is covered by disabling auth and status pages
Auto-Hiding Notifications is covered by https://github.com/louislam/uptime-kuma/pull/3441

We can reopen if an argument is made why this is not resolved ^^


Fix the date formatting when user hovers Mina price chart

Current
Date is formatted with a 3 letters month abbreviation and one digit of a month's day. (Jul 0)
Expected
Date formatted with a 3 letters month abbreviation and one or two digits of month's day. (Jul 30)
Screenshot

@mrcnk I'd be happy to take a look at this. Re: the bounty label, are there any details on how to get set up with your bounty program for payout?

/price 50

Hey @quiqueg, we'll post more info about the bounty program tomorrow on https://x.com/pallad_. Please check it tomorrow to learn how to get it for implementing it.

@mrcnk Please assign me this issue?


Is it possible to make this installation error more precise?

When I went to install the extension, I got this error:

I'm not actually sure what that means. Is my kubectl too old/new? Is it trying to connect to my cluster and finding something it doesn't like?
I'm wondering if the error could at least say "requires version(s) $RANGE for $WHAT"
For reference:

kubectl is 1.10.0 (which is the newest)
Kubernetes is 1.9.0

@evanlouie will take care of this

@technosophos what version of vscode are you currently running? As of late 2016, vscode should be emitting errors that look like Extension is not compatible with Code 1.21.1. Extension requires: ^1.22.0. when attempting to install unsupported extensions.

@technosophos Can you confirm the version of VS Code where you're seeing this?


Create a leaderboard page and add a button to it in homescreen

Add a leaderboard with good ui and names of all projects with images, create a column for rating as well done by Admins.

Hi @Shreyaar12 I would like to work on this issue under GSSoC

@ManasaKaza Assigning you this issue, kindly complete within 10 days

hey @Shreyaar12, I would like to work on this issue.


Resolves Langchain issues appearing in Flowise

Anchoring initial Langchain version to the latest version as default. This commit will fix below issue(s).
https://github.com/FlowiseAI/Flowise/issues/1206

thanks, will do a regression test on the latest ver of langchain


Bundle http-sync

This decouples us from http-sync releases when the next version of node comes around.
For .travis.yml changes see: https://github.com/travis-ci/travis-ci/issues/4771

I guess there's a good reason for not keeping http-sync?
Also, do we need to include its tests as well?

@khoomeister Since we are not exposing it, I think our current test coverage should be enough. I'd rather delete features from it we don't need than adding the test suite. The reason for this change is that each time we needed something like the nan upgrade, the blocking factor was release delays in http-sync. Which means that each time testium wasn't compatible with the latest node version, this was the critical path was the culprit.

Have we tried asking for commit & publish privileges to the repo?  Just make a case (we depend on it heavily) and see whether he's willing to trust you?

:shipit:

I agree with @khoomeister. Can we try to get contributor access to http-sync instead?

I'm currently cleaning up the code. I'm deleting what feels like 80% of it. I'd much rather maintain the subset we care about than all of http-sync.

If it's really that small, then yeah, let's see what that looks like.

See here: https://github.com/groupon/webdriver-http-sync/pull/31

published in 1.2.0


Report a couple of options that are incompatible with --awsvpc

Make it easier for the user to see what is wrong.

LGTM.

Tests have passed: https://circleci.com/gh/weaveworks/weave/6243


Remove the featureDiscoveryServiceRef from the plugin api alpha subpath

Code reference:
https://github.com/backstage/backstage/blob/7c5f3b02972b1ce53e39f0dd04f6fce4e5511c43/packages/backend-plugin-api/api-report-alpha.md?plain=1#L17-L22

Pull Request: https://github.com/backstage/backstage/pull/26203


Add nicknames package to xpanse-ml-ev2 image

Status
In Progress
Related Content Pull Request
Related PR: not yet open
Description
This is my first contribution to this repo. This PR aims to add the nicknames package as a dependency to the xpanse-ml-ev2 docker image. This dependency is required for an upcoming update to an automation in the CortexAttackSurfaceManagement pack.
Test plan: build development image using CI/CD on PR, reference dev image locally in tests for updated automation, then merge if tests pass?

Hi @JudahSchwartz , do you know if there's a way to use the development image that was published by CI/CD while running demisto-sdk lint locally for a particular automation? cc @ShacharKidor

yeah you can run
curl -L "https://output.circle-artifacts.com/output/job/b81274b1-def6-4c6c-bc0e-81ab17918e43/artifacts/0/docker_images/devdemisto_xpanse-ml-ev2:<IP_ADDRESS>079.tar.gz" | gunzip | docker load
This command you can find in the end of the build under the build images step
it should print the tag you added, copy that tag and set the dockerimage tag in the yml to that tag. let me know if you need help along the way

I did that but it fails with
Failed to get python version from docker hub for image devdemisto/xpanse-ml-ev2:<IP_ADDRESS>858: Failed to get docker image digest: {"errors":[{"code":"MANIFEST_UNKNOWN","message":"manifest unknown","detail":"unknown tag=<IP_ADDRESS>858"}]}

It seems like it's looking for the tag in the dockerhub but I think because I'm contributing via an external fork it's not published there

@kball-pa what failed? Lint or installing the docker?
@dorschw looks like a devbug

@kball-pa thanks, theres a bug open to take care of this. In the meantime, we can merge to a branch so that an image gets uiploaded to dockerhub, which will solve the issue, or we can merge to master if youre confident in the changes in dockerfiles

great, thanks @JudahSchwartz! I feel confident about the changes, we can merge to master.

@JudahSchwartz @dorschw can we merge to master?

Actually I decided to close this PR for now -- for the sake of simplicity/time constraints, I can move forward with the existing docker image and just have slightly reduced functionality on the content side.
We can come back to this PR later as follow-up work. Thanks all for the help!


Add a CODEOWNERS file.

After this we can enforce that reviews must be approved by people on this list.
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

LGTM


Add support for installing on Windows

While the main development effort is taking place in Ubuntu. Some of the simphony plugins can be used on Windows (e.g simphony-common and simphony-mayavi). So it is would be nice to have a batch file that will simplify installing a part of the simphony-framework that is windows friendly

:+1:  and simphony-nCAD

we can also setup appveyor (http://www.appveyor.com) test the framework

In a first step I'm writting a very simple batch file for Windows following the same philosophy as we have now to accomplish this, I will tell you guys when it's ready and it's all tested with simphony-nCAD :+1: And also to see if any other code that can run on Windows wants to be added to the script.


Fix broken link

Fix broken links in api reference page

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66712686c8500faf606bb66a--harness-developer.netlify.app


Suppressing errors when updating from 2.0.0 to 2.0.1

Did you read the migration guide?

[X] I have read the whole migration guide

Is there an existing issue that is already proposing this?

[X] I have searched the existing issues

Potential Commit/PR that introduced the regression
https://github.com/nestjs/event-emitter/commit/f84ed00af252f9e0e8e5487571071f1117dfde15
Versions
2.0.0 > 2.0.1
Describe the regression
The following unit test should pass for the new 2.0.1 version.
Minimum reproduction code
class FakeSuccessfulEvent {
  constructor(readonly name: string) {}
}

class FakeFailedEvent {
  constructor(readonly name: string) {}
}

@Injectable({ scope: Scope.DEFAULT })
class FakeService {
  successCalled = false;
  failCalled = false;
  processed = false;

  constructor(private readonly publisher: EventEmitter2) {}

  async success(name = "fake"): Promise<void> {
    await this.publisher.emitAsync(FakeSuccessfulEvent.name, new FakeSuccessfulEvent(name));
    this.processed = true;
  }

  async fail(name = "fake"): Promise<void> {
    await this.publisher.emitAsync(FakeFailedEvent.name, new FakeFailedEvent(name));
    this.processed = true;
  }

  @OnEvent(FakeSuccessfulEvent.name)
  async handleSuccess(_event: FakeSuccessfulEvent): Promise<void> {
    this.successCalled = true;
  }

  @OnEvent(FakeFailedEvent.name)
  async handleFail(event: FakeFailedEvent): Promise<void> {
    this.failCalled = true;
    throw new Error(`Failed to handle event ${event.name}`);
  }
}

describe("EventEmitter", () => {
  let app: INestApplicationContext;
  let service: FakeService;

  beforeEach(async () => {
    const module = await Test.createTestingModule({
      providers: [FakeService],
      imports: [
        EventEmitterModule.forRoot({
          wildcard: true,
          delimiter: ".",
          verboseMemoryLeak: true,
        }),
      ],
    }).compile();

    app = await module.init();
    service = app.get(FakeService);
  });

  it("should successfully handle event", async () => {
    await service.success();
    expect(service.successCalled).toBe(true);
    expect(service.failCalled).toBe(false);
    expect(service.processed).toBe(true);
  });

  it("should fail when event isn't processed", async () => {
    await expect(service.fail("failed")).rejects.toThrow("Failed to handle event failed");
    expect(service.successCalled).toBe(false);
    expect(service.failCalled).toBe(true);
    expect(service.processed).toBe(false);
  });

  afterEach(async () => {
    await app.close();
  });
});

Expected behavior
To pass both unit tests (like it is when using v2.0.0). If suppressing errors is the new behavior, maybe the right way to go could be creating a minor/major version (to avoid breaking changes in a patch)
Other
No response

Thrown errors where causing the host application to crash, which is clearly a bug and an unexpected behavior, that's why it wasn't published as a new minor/major version.


create config file from defaults if missing.

Now uses defaults if no config file is present. Snapshot 1.2.


Getting started

Hi,
I just imported the JARs and attempted to read from a Dynamo DB, using the provided code snippet:
dynamoDf = spark.read.option("twitter").format("dynamodb").load() #table name is twitter
dynamoDf.show(100)
I get the following error msg: TypeError: option() missing 1 required positional argument: 'value'.
How do I check if indeed Dynamo is connected to Spark via AudienceProject? Do you have a small example of how to set it up on PySpark?
Thanks for the good work!

Hi
You are missing an argument to the tablename option. The line should read:
dynamoDf = spark.read.option("tableName", "twitter").format("dynamodb").load()


Feat/add settings to write (#2)

Support ClickHouse insert settings for table writes (#369)

Enable custom ClickHouse insert settings when writing to tables.
Add support for spark.clickhouse.write.settings.* configuration.
Ensure settings are applied to the INSERT INTO ... SETTINGS ... SQL command.
Update documentation to describe usage of write settings.
Add unit tests to validate behavior.

Closes #369

bad pull requests.


Crash when using v1.Security.AddCertificate()

Describe the bug
I'm trying to use v1.Security.AddCertificate() as part of  atlassian/terraform-provider-artifactory#38 and I'm either doing something wrong or there's a bug here.
To Reproduce
My provider code looks like this:
func resourceCertificateUpdate(d *schema.ResourceData, m interface{}) error {
        c := m.(*artifactory.Artifactory)

        pem, err := os.Open(d.Get("path").(string))
        if err != nil {
                return err
        }
        defer pem.Close()

        _, _, err = c.V1.Security.AddCertificate(context.Background(), d.Id(), pem)
        if err != nil {
                return err
        }

        return resourceCertificateRead(d, m)
}

v1.Security.AddCertificate() wants the certificate passed as an *os.File hence I assume I just open the file and pass it in like this? The file is open successfully and if I read it, there's clearly PEM data there.
Expected behavior
I would expect the call to succeed.
Log Output
There is a lot of Terraform log, but the top-most bits are:
2019-05-09T16:28:39.942+0100 [DEBUG] plugin.terraform-provider-artifactory: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xd0f3ca]
2019-05-09T16:28:39.942+0100 [DEBUG] plugin.terraform-provider-artifactory:
2019-05-09T16:28:39.942+0100 [DEBUG] plugin.terraform-provider-artifactory: goroutine 58 [running]:
2019-05-09T16:28:39.942+0100 [DEBUG] plugin.terraform-provider-artifactory: github.com/atlassian/go-artifactory/artifactory/transport.(*BasicAuth).RoundTrip(0xc00013d2c0, 0xc000458600, 0xc00013d2c0, 0x0, 0x0)
2019-05-09T16:28:39.942+0100 [DEBUG] plugin.terraform-provider-artifactory:     .../work/src/github.com/atlassian/go-artifactory/artifactory/transport/basicauth.go:44 +0x19a

It's crashing on this line:
https://github.com/atlassian/go-artifactory/blob/dc978cf4e4520147647dfdee47340c88039225db/artifactory/transport/basicauth.go#L44
req.GetBody() is nil. I added some debug to print the request before it gets sent, and this is what it looks like:
&{POST https://artifactory.example.com/artifactory/api/system/security/certificates/test HTTP/1.1 1 1 map[Accept:[application/json] Content-Type:[text/plain] User-Agent:[go-artifactory]] 0xc0000ad2d0 <nil> 0 [] false artifactory.example.com map[] map[] <nil> map[]   <nil> <nil> <nil> <nil>}

GetBody() is the <nil> following the 0xc0000ad2d0 address following the http.Request struct.
Desktop (please complete the following information):

OS: Linux, go version go1.12.4 linux/amd64

Additional context
Incidentally, v1.Security.AddCertificate() calls client.NewClient() which wants an io.Reader instead of a *os.File; using the former everywhere instead would mean you could feed in a stream of bytes for the PEM from a string rather than always having to reference an existing file on the disk, assuming I've got the API right.

If I make the following change:
diff --git a/artifactory/v1/security.go b/artifactory/v1/security.go
index cc8d749..9cf5b53 100644
--- a/artifactory/v1/security.go
+++ b/artifactory/v1/security.go
@@ -5,10 +5,11 @@ import (
        "context"
        "encoding/json"
        "fmt"
-       "github.com/atlassian/go-artifactory/v2/artifactory/client"
+       "io"
        "net/http"
-       "os"
        "strings"
+
+       "github.com/atlassian/go-artifactory/v2/artifactory/client"
 )

 type SecurityService Service
@@ -1035,7 +1036,7 @@ func (s *SecurityService) GetCertificates(ctx context.Context) (*[]CertificateDe
 // Adds an SSL certificate.
 // Since:5.4.0
 // Security: Requires an admin user
-func (s *SecurityService) AddCertificate(ctx context.Context, alias string, pem *os.File) (*client.Status, *http.Response, error) {
+func (s *SecurityService) AddCertificate(ctx context.Context, alias string, pem io.Reader) (*client.Status, *http.Response, error) {
        path := fmt.Sprintf("/api/system/security/certificates/%s", alias)
        req, err := s.client.NewRequest("POST", path, pem)
        if err != nil {

and then use strings.NewReader() with the PEM content like this in my Terraform resource:
func resourceCertificateUpdate(d *schema.ResourceData, m interface{}) error {
        c := m.(*artifactory.Artifactory)

        _, _, err := c.V1.Security.AddCertificate(context.Background(), d.Id(), strings.NewReader(d.Get("content").(string)))
        if err != nil {
                return err
        }

        return resourceCertificateRead(d, m)
}

it works fine. It's down to something to do with specifically passing a file. Any ideas?

I've created PR #17 to change the signature of AddCertificate() as I think it's a useful change anyway and shouldn't break backwards compatibility given one is the interface of the other.

Awesome, thanks for finding and fixing this!

Sorry, I think there's a misunderstanding here; there's still a crash if you pass an open file even with the change applied, just with that change in place the PEM data can at least be passed by some other means that doesn't explode.

Oh no worries, I'll check this out hopefully early next week.


safer reissue, fix celery sync job

Coverage decreased (-0.04%) to 60.611% when pulling 50761d9d3b1603dc2780ea5c11acd7ed26056bef on castrapel:safer_reissue into f824f76d9cb0f146b2529e831b0176500e287061 on Netflix:master.


change spec %2.3.2 cx_imm to conform to I-type op-imm instructions such as addi

Per https://github.com/grayresearch/CX/issues/27#issuecomment-2026645068, we should replace
imm[7:0] cf_id[3:0] rs1[4:0]   000[2:0] rd[4:0] custom1[6:0]   cx_imm
with
imm[11:0]           rs1[4:0] cf_id[2:0] rd[4:0] custom1[6:0]   cx_imm (I-type)
which is much more regular, provides 4 more immediate bits, and will shave unnecessary operand muxes in any CXU-LI compatible CPU, especially since it also conforms to the layout of CSRR* instructions with insn[31:20] = csr[11:0].
Against the significant upside, the downside of this is: 1) it only handles 8 CF_IDs, not 16 CF_IDs, and 2) it surrenders the present design's future opcode reservation in the func3 field. That's fine, we have mcx_selector.version, as well as uncommitted custom3, for near and long term future CX custom instruction formats. And no doubt, plenty of enthusiastic redesign of the whole thing if/when we get to reopening that can of worms within a CX TG.

Completed in PR #36.


Enable Python3 for mail notifications hook

Hi @n-rodriguez Would you consider bumping the mail notifications hook to Python3?
This is a naïve PR to do that - I've simply changed the #! line and modified the print statement in one file, and copied over the latest version of the other file from the original repository.
I don't know if the changes worked - I have only know that the first file now prints multimailhook is disabled rather than not finding python2 - I haven't setup mail yet.

Checks seem to be failing on a database issue that I haven't touched!


Example from eye directory doesn't work

Example from eye directory doesn't work
My Cargo.toml:
[dependencies]
eye = "0.4.1"
eye-hal = "0.1.0"
glium = "0.31.0"

Error, that I recieve:
error[E0432]: unresolved import `eye::colorconvert::Device`
 --> src/main.rs:5:5
  |
5 | use eye::colorconvert::Device;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `Device` in `colorconvert`
  |
help: consider importing one of these items instead
  |
5 | use eye::prelude::Device;
  |     ~~~~~~~~~~~~~~~~~~~~
5 | use eye::traits::Device;
  |     ~~~~~~~~~~~~~~~~~~~
5 | use eye_hal::platform::Device;
  |     ~~~~~~~~~~~~~~~~~~~~~~~~~
5 | use eye_hal::traits::Device;
  |     ~~~~~~~~~~~~~~~~~~~~~~~

error[E0609]: no field `uri` on type `std::string::String`
  --> src/main.rs:29:46
   |
29 |     let dev = ctx.open_device(&dev_descrs[0].uri)?;
   |                                              ^^^ unknown field

warning: unused import: `Stream`
 --> src/main.rs:7:50
  |
7 | use eye_hal::traits::{Context as _, Device as _, Stream as _};
  |                                                  ^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: unused import: `Device`
 --> src/main.rs:7:37
  |
7 | use eye_hal::traits::{Context as _, Device as _, Stream as _};
  |                                     ^^^^^^

Some errors have detailed explanations: E0432, E0609.
For more information about an error, try `rustc --explain E0432`.

Please, fix your example

Which OS is this? Could you please retry using the latest release (0.5.0)? I just ran it on macOS to confirm it works fine.

It was my mistake, I didn't use features


Can't use custom protocols in generator.

Type of issue
[Doesn't support custom protocols ("protocol://api") ] Bug
Expected Behavior

"protocol://api" should redirect to corresponding app, if there is not any, should show an error page in Safari (or in other browser)
Current Behavior

"protocol://api" redirects to "{default search engine}.com/?q=protocol://api"
Possible Solution (optional)

Create a custom variable type to initilaize it as URL
Steps to Reproduce (for bugs)

qrCodeData = qrGenerator.CreateQrCode("protocol://api", QRCodeGenerator.ECCLevel.Q);
Your Environment

.NET 4.6.1
Win 7 x64
READER => iOS 12 (camera app)

This is not the fault of QRCoder. It encodes exactly the string, which is given to it.
The logic to open an app can't be handled by a QR code at all. It everytime the task of the scanner app.
So your request...

"protocol://api" should redirect to corresponding app, if there is not any, should show an error page in Safari (or in other browser)

...can't be handled within the specs of QR code.
Nevertheless it's possible to launch apps via QR code. But it works only, if the given uri scheme (protocol://api...) is registered in the iPhones plist. https://stackoverflow.com/questions/47636662/how-to-open-an-app-with-the-ios11-integrated-qrcode-reader
If it's not registered (app not available) the iPhone won't launch the app, but start a search. This is the standard behaviour.


ValueError when tracing website

Hi all (specifically @remram44),
I was trying to pack up my website build on the Nikola static site generator as a new way to make archival backups, and got this really weird error:
(venv) vicky@steevesv:~/Downloads/Nikola-Site$ reprozip trace nikola build
Scanning posts......done!
[REPROZIP] 14:32:02.564 WARNING: Some files were read and then written. We will only pack the final version of the file; reproducible experiments shouldn't change their input files
Traceback (most recent call last):
  File "/home/vicky/.local/bin/reprozip", line 11, in <module>
    sys.exit(main())
  File "/home/vicky/.local/lib/python2.7/site-packages/reprozip/main.py", line 364, in main
    args.func(args)
  File "/home/vicky/.local/lib/python2.7/site-packages/reprozip/main.py", line 188, in trace
    overwrite=False)
  File "/home/vicky/.local/lib/python2.7/site-packages/reprozip/tracer/trace.py", line 283, in write_configuration
    files, packages = identify_packages(files)
  File "/home/vicky/.local/lib/python2.7/site-packages/reprozip/tracer/linux_pkgs.py", line 221, in identify_packages
    manager.search_for_files(files)
  File "/home/vicky/.local/lib/python2.7/site-packages/reprozip/tracer/linux_pkgs.py", line 140, in search_for_files
    package = self._create_package(pkgname)
  File "/home/vicky/.local/lib/python2.7/site-packages/reprozip/tracer/linux_pkgs.py", line 169, in _create_package
    p.communicate()
  File "/usr/lib/python2.7/subprocess.py", line 792, in communicate
    stdout = _eintr_retry_call(self.stdout.read)
  File "/usr/lib/python2.7/subprocess.py", line 476, in _eintr_retry_call
    return func(*args)
ValueError: Mixing iteration and read methods would lose data

This might bear looking into. Cheers!

I think I know what this is, e6f560e7 should fix this. I thought it was a good idea 😅


Breaking change to StringFieldSerializer - Check for empty value after trim, this means a string like " " now fails update/create

PHP Version
8.1
Shopware Version
<IP_ADDRESS>
Expected behaviour
The StringFieldSerializer should not fail the trim check until at least 6.5 as this is actually a breaking change, as I cannot store " " anymore. Sure in most cases this is not a good value to store anyway but as we import data where either first name or last name can be empty (not both), as a workaround for the Required check, we stored a space, until the data was fixed by the customer later on.
In order to avoid a breaking change:

Remove trim check from customer  and add it to the registration validation as that was why it was added in the first place.
And add a feature flag to trim it in the value in the string field serializer, with a deprecation information regarding 6.5 and disable it for now.

Actual behaviour
Trying to store a space for firstName / lastName in the customer entity now fails, which did not before and therefore this is a breaking change.
How to reproduce
see above.

Hey @AndreasA,
I was looking at the issue and came across the following commit
Here, we added a trim() in the StringFieldSerializer, which fixed a bug in the validation of the AllowEmptyString. Since it is not intended by the developer to support an empty string for these fields, we have implemented the trim check here, since we had not considered it in the initial commit (2020).
I will revert the change with the next version

@OliverSkroblin It isn't that huge a breaking change and as mentioned it definitely makes sense as a feature flag, but it should probably be avoided as it can have some impacts elsewhere.

https://github.com/shopware/platform/commit/1b6cfe5db53019943bb1c4da9e6bdb56b2933b26


Allow indirect modifications of overloaded properties when using MongoDB

Take for example this data structure saved in a MongoDB database:
_id: '3456345b6serbts34sdfbtsdf',
type: [
    "admin",
    "client"
],
personal_info: {
    name: 'Bob',
    surnames: ['', '', '', ''....],
    bday: ISODate(....),
},
credentials: {
    email<EMAIL_ADDRESS>    pass: '123123',
    salt: '2345c2345v345wq'
}

Getting the entire document is easy, $person = Person::find(["_id" => "....."]);
But modifying any subdocument values is not possible:
var_dump($person->credentials);  // <--- works
var_dump($person->credentials['password']); // <--- works
$person->credentials["password"] == "new password"; // fails with "Indirect modification of overloaded property"

This patch fixes this and, as far as I'm aware of, it doesn't introduce any bugs or any API breaks.

See explanation at #4899: such change will cause more trouble then it solves.


Installation problems on Windows 10

Hi everyone,
I have some problems with the installation of SuperElastix on Windows 10 (I don't know if this is the right place to ask questions). I followed the guide on http://superelastix.readthedocs.io/en/latest/GettingStarted.html#superbuild-on-windows . Points 1 to 7 have no problems and all the tests have passed. Problems start with the 8 point. I searched the "\SuperElastixApplications-build\CommandlineProgram\ " folder everywhere but I couldn't find it.
I tried to keep going the same with the commandline tool(Demo Experiments): "http://superelastix.readthedocs.io/en/latest/CommandlineTool.html"
I launched all the script cited in the tutorial . They produce .MHD , .RAW, .dot, .dot.png files, but I don't know how to open them (I had installed for this purpose Fiji distribution of ImageJ).
I want to ask you if SuperElastix is correctly installed and how to see the images that it produces.

Hi @LukeMay35  Thanks for your elaborate report! The location mentioned at point 8 appears outdated, indeed. It should say "Applications-build\CommandLineInterface\Release". Does that work for you? Otherwise, do you find "SuperElastix.exe" anywhere else on your build directory?
Anyway, I think we should update the documentation! So this is the right place, as you found a bug!

Hi @N-Dekker . I can find the command line tool in 2 places:
\Applications-build\Demo
\Applications-build\CommandLineInterface\Release (as you say)
Seems to be the same application.
If possible, I want to ask you where I can find documentation on SuperElastix components. On the guide is said only how to write blueprint files (not which component to use and which component are mandatory). Anyhow, thank for your help.

Hi @LukeMay35 , yes this is the same application. For historical reasons this executable is built twice.
Documentation on the SuperElastix components is indeed still missing :) . In the functions MeetsCriterion the parameters of the blueprint are passed to the wrapped components; this may help. For example https://github.com/SuperElastix/SuperElastix/blob/develop/Modules/Components/itkImageRegistrationMethodv4/include/selxItkImageRegistrationMethodv4Component.hxx -> ::MeetsCriterion.
Cheers, Stefan

For the record: The exe path is fixed at https://github.com/SuperElastix/SuperElastix-Documentation/commit/cf6c12b9eb0778ba4e6523dab7300f9181b63dbc


s390x: fix restoring of SIGILL action

Constructor wrongly restores SIGILL action with old SIGFPE action.
Even with storing/restoring application signal handlers there could still be a race .. libraries better leave signal handlers alone. So i think about changing the try-catch behavior to just using getauxval for master.

Tried to cherry-pick to 1.1.1 but commit doesnt apply cleanly due to one different line of context.
Do i formally need to open a new PR for 1.1.1 or its okay to resolve the conflict and push the cherry pick ?

ping @openssl/omc

Nobody objected so i assume your okay with me pushing this also to 1.1.1.

Hmmm, this is really a judgement call.  If you feel uncertain, it's usually better to make a separate PR for 1.1.1.

No, im certain. Question was just if its formally required.

Merged to

master https://github.com/openssl/openssl/commit/c17d60ea293746d7cd06a910ced446edbb6c1eba
1.1.1 https://github.com/openssl/openssl/commit/0f6fd6145924ad5fbddb96570877d36f1e077707


[Question] how to use EmbedsMany with existing record?

Hi today i have a question I have try to use EmbedsMany i have done on the follow documentation but on the model Book can't get any records of reverse data, i also try to create a record on Book model and save with instance but not thing append to User embed record is that bug or i missing something?

i same.
https://github.com/jenssegers/laravel-mongodb/issues/2035


[WIP] Add IPADDRESS and IPPREFIX and corresponding functions

IPADDRESS/IPPREFIX
Types
IPADDRESS (HUGEINT)
All IPs are stored as IPV6. IPV4 is converted to IPV6 with a form of
0x 0000 0000 0000 0000 0000 FFFF XXXX XXXX

IPPREFIX ({HUGEINT, TINYINT})
Stored as a an opaque type of struct
{ int128_t ip, int8_t prefix}

Functions
NOTE: We cannot apply IPV4 operations on an IPV4 converted IPV6 address.
Ex. We can apply a length 100 prefix on an IPV4 converted address. So we need
to always convert IPV6 to IPV4 if possible.
cast(ipaddress as varchar) → varchar
memcpy int128_t from ipaddress type into boost byte array.
If we are loading from a little endian system we need to flip

the bytes since it needs to be in network byte order.
We then check if it is a v4 mapped address so we can make
the correct boost ipV4/V6 object to print correctly.

All error handling done by the boost library.

cast(ipaddressString as IPADDRESS) → IPADDRESS
Create IP address boost object with the string. Check the object,
if its V4 then convert to V6. Extract the bytes and flip if we are on

a little endian system. Copy back into the int128_t for the result.
All error handling done by the boost library.

cast(ipprefix as VARCHAR) → VARCHAR
Same as ipaddress, except we create a network with the IP

cast(ipprefixString as IPADDRESS) → IPPREFIX
Find the last occurance of '/' creating a boost IP address object
with whatever comes before it. If there are two '/' IP object creation will fail
if there is no slash ex. an IP without any prefix we will continue
but fail at a later point.

Use the address object to see if we have an IP V4 or V6 network
and create the V4/V6 network with the original string. Network
creation will fail if the IP is not parseable.

If we have an IPV6 object, there is a chance that they entered an
IPV4 formatted as an IPV6 so we need to create an IPV4 network
to properly get the canonical address and check prefix validity.

Use the network to get the canonical address, flipping the bytes
if necessary before putting it in the IPPREFIX ip variable.

Copy over the prefix from prefixBits argument.

ip_prefix(ipaddress, prefix_bits) → IPPREFIX
If ipaddress is a varchar, use same logic as cast to convert to
ip address and call with ipaddress type.

Create boost v6 ipaddress object with the ipaddress type passed in.
Create corresponding v4/v6 boost network and pass in the prefix_bits
converting it to uint8_t since the presto type is int8_t.

Get the canonical ip address from the network object as a byte array,
flipping if on little endian to prepare for placing in the HUGEINT type.

IP Parsing and prefix size restriction error handling is all done in boost.

ip_subnet_min(ipprefix) → IPADDRESS
Return the canonical IP address already stored in the IP Prefix object.
It is the smallest IP we could have.

ip_subnet_max(ipprefix) → IPADDRESS
We want to set all non prefix bits to 1. For IPV4 thats max 32 bits, for IPV6
thats max 128. Subtract prefix from the max and do some bit manipulation
to flip that many bits.

EX. Prefix is 25 on an IPV4. So we want to flip the 7 LSBs.
1 << 7 = (1,0,0,0,0,0,0,0)
(1,0,0,0,0,0,0,0) - 1 = (0,1,1,1,1,1,1,1);

We then OR this with IPPREFIX's canonical IP to set them all to 1.

Note, for ipprefix = 0 in IPV6 we should be able to overflow then subtract one
from a bit standpoint but it does not work. So added a special case.

ip_subnet_range(ipprefix) → [IPADDRESS, IPADDRESS]
Just return ip_subnet_min and ip_subnet_max in an array.

is_subnet_of(ipprefix, ipaddress) → BOOLEAN
We just need to make sure that the prefix of IPADDRESS is equal to the ip
of IPPREFIX when subject to the prefix length of IPPREFIX.
To do this we do a similar bit operation. However we flip the bits to get the prefix
side and AND them together to extract the prefix bits from the IP.
We then compare to check if the prefix are equal.

Note, for ipprefix = 0 in IPV6 we should be able to overflow then subtract one
from a bit standpoint but it does not work. So added a special case.

is_subnet_of(ipprefix1, ipprefix2) → BOOLEAN
Just call is_subnet_of(ipprefix, ipaddress) however with an additional condition
to make sure that the prefix of ipprefix2 is longer or equal to that of ipprefix1.
If its shorter than there is no way for ipprefix1 to contain all of ipprefix2.

Closed for now. Merge into fork first then pushing up to OSS at a later point.


Tailwind course

Hi! I have paid you for a course of tailwind at betterdev.com. But now I receive an error "404 page not found° . Is any chance to get it back? Thanks in advance.

hey i moved the course over to gumroad
@internetbug256 can you send me twitter message and i'll get you access? https://twitter.com/chris__sev


Crash traceback should use conf-dir

cosmetic:
This error message
"""    Briefly describe what you were doing, and include the last 20 lines from .coda-config/coda.log."""
should reflect the actual conf dir.
.coda-config is DEFAULT conf dir, but if you use a different name, the string is the same.

Closing this issue as it is stale for a long time.


Update jest from 27.5.1 to 29.4.3

Fixes #8460
This PR updates jest from 27.6.1 to 29.4.3. Jest 28 updated their package.json exports support so that environment globals are fully supported. This means dependencies that resolved before potentially won't anymore and vice-versa depending on their exports when jest attempts to automatically find an export based off of "browser" and "require" globals (with a bad path giving us an ES module thus breaking). The following dependences were affected:

axios - previously we had to manually map it, but it appears to work naturally now
rest-hooks and @rest-hooks/* - requires manual map (this is potentially not an issue in their current versions but we're in the process of deprecating this dependency so its version is intentionally out-of-date)
msw/lib/node - requires manual map

Ejected scripting from CRA needed updates to support the newer jest. Two test modules were updated to fix test bugs causing a false failure.
Some minor update bumps were made to:

cypress
eslint
@typescript-eslint/*
jest-watch-typeahead
msw

Some peer dependencies were added to cease warnings from yarn.

Going to need a sanity check on the error GH is getting. Context: after the dependency updates a test for DeliveriesTable was failing because the output from new Date("01-01-2000").toISOString() changed from "2000-01-01T00:00:00.000Z" to "2000-01-01T06:00:00.000Z". I was able to verify this output in a browser console. My assumption is that the jest updates made expected changes to how the browser environment is simulated and date behavior was modified. However, GH is throwing an error because it is still getting the previous output somehow. I have flushed my node_modules to make sure this wasn't a local package manager bug but the test still passes. Can someone check this out locally and confirm?


Symbolic links not marked as such in the explorer

Type: Bug
Symbolic links are not marked as such in the explorer when they were normal files or folders before.
When creating a file, deleting it and then creating a symbolic link with the same name, the link is shown as if it were a normal file until VSCode is restarted.
Reproduction (Linux)
Reproduction setup:
touch testfile

For a symbolic link which looks like a regular file in the VSCode explorer, run this:
touch foo
rm foo
ln --symbolic testfile foo

For the opposite (a regular file that looks like a symbolic link), run this:
ln --symbolic testfile bar
rm bar
touch bar

This also happens with directories (replace touch with mkdir).
VSCode version: VSCode 1.77.3
OS version: Linux x64 5.15.0-70-generic
Modes:
Sandboxed: No

System Info

Item
Value

Process Argv
--ms-enable-electron-run-as-node --no-sandbox --disable-extensions

Screen Reader
no

Extensions disabled

\duplicate https://github.com/microsoft/vscode/issues/167146


don't attempt to connect from when callback returns :stop

I'm guessing attempting to connect from the {:stop, reason, state} handler was a copy + paste error? Attempting to do so actually causes a crash, at least from an already-connected process.

Good catch, thanks! We could use a test for this, but I'll look into it myself.


OCPBUGS-13973: bump k8s modules to 0.27.2

Bump of<EMAIL_ADDRESS><EMAIL_ADDRESS>bump was mandatory as it's the first version supporting k8s api >=0.27.x.
Changes related to<EMAIL_ADDRESS>
Manager options changed:

NewClient changed the signature and the cache handling
Namespace is deprecated now, Cache field was used instead

WithStatusSubresource method has to be used in the fake client if the status is expected to be updated
source.Kind is not public anymore
sigs.k8s.io/controller-runtime/pkg/envtest/printer package has been removed

Also golangci-lint (part of verify job) forced the following changes:

k8s.io/apimachinery/pkg/util/sets deprecated type specific sets in favor of a generic Set
https://pkg.go.dev/k8s.io/apimachinery/pkg/util/wait deprecated a lot of PollX methods in favor of the context aware alternatives.
k8s.io/utils/pointer deprecated all the methods with Ptr in the name in favor of the methods without it

/lgtm


Replace FindcuFile with upstream FindCUDAToolkit support

CMake's FindCUDAToolkit has supported cuFile since 3.25. Use this support and remove the custom FindcuFile module.

/merge


Use optional devEnabled[targetName/buildTypeName] configuration from …

Allow enabling/disabling development mode for custom Android build types. Useful for example when building a CI artifact which require custom build type setting differing from the release build type.
Follows the same API as bundleIn<buildType>, jsBundleDir<buildType> and resourcesDir<buildType>.
Backwards compatible with current implementation and behaviour (will default to false if targetName contains release).

CLA signed

duplicate of #11438 which was just imported


3.3.5 broke GetPreSignedURL

reopening #587 . please don't prematurely close issues. the message it sends, quite clearly is "we don't care about your feedback. go away".
the format of the URL generated by GetPreSignedURL was changed in release 3.3.5.
the new style of URL no longer work against S3 - it returns a "SignatureDoesNotMatch" error.
pre-3.3.5 generated URLs that looked like this:
https://mybucket.s3-us-west-2.amazonaws.com/mykey?AWSAccessKeyId=<MyKeyID>&Expires=1489619417&Signature=<Signature>&x-amz-meta-download=140&branch=development&machine=something

post-3.3.5 URLs look like this:
https://mybucket.s3-us-west-2.amazonaws.com/mykey?X-Amz-Expires=86400&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=<Signature>%2F20170314%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20170314T231800Z&X-Amz-SignedHeaders=host%3Bx-amz-meta-download&X-Amz-Signature=<Signature>&x-amz-meta-download=140&branch=development&machine=something

notice how the parameters passed are completely different.

Reopened issue #587. As this is clearly a duplicate, resolving in favor of 587.


Adapter throws errors in log

(22797) Create state error = ReferenceError: initialise is not defined

Would also be fixed with https://github.com/DrozmotiX/ioBroker.wled/pull/190 because there's a variable which has a typo in it one or two times.

will fix bij next release with socket implementation, as usual... don't install from git this error is only on git version not official release....

fixed release v0.5.7


Chart email schedules not delivering

A clear and concise description of what the bug is.
I have scheduled a report with cron tab frequency every 15 min. It is throwing an error saying slices.id is not found. I have check the chart creation and slice.id in slices table as well. everything looks fine. Please suggest any ideas here. Thanks.
Expected results
Worker log:
[2020-04-22 00:18:46,794: ERROR/ForkPoolWorker-7] Task email_reports.send[2fd14c5c-2df8-4130-a5da-2af92e0d5068] raised unexpected: NoSuchColumnError("Could not locate column in row for column 'slices.id'",)
Traceback (most recent call last):
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/celery/app/trace.py", line 385, in trace_task
R = retval = fun(*args, **kwargs)
File "/obi/ApacheSuperset/superset_36/Superset/superset/app.py", line 114, in call
return task_base.call(self, *args, **kwargs)
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/celery/app/trace.py", line 650, in protected_call
return self.run(*args, **kwargs)
File "/obi/ApacheSuperset/superset_36/Superset/superset/tasks/schedules.py", line 714, in schedule_email_report
deliver_slice(schedule)
File "/obi/ApacheSuperset/superset_36/Superset/superset/tasks/schedules.py", line 677, in deliver_slice
email = get_slice_visualization(schedule)
File "/obi/ApacheSuperset/superset_36/Superset/superset/tasks/schedules.py", line 636, in get_slice_visualization
slc = schedule.slice
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", line 286, in get
return self.impl.get(instance_state(instance), dict)
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", line 722, in get
value = self.callable(state, passive)
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", line 750, in _load_for_state
session, state, primary_key_identity, passive
File "", line 1, in
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", line 840, in _emit_lazyload
session.query(self.mapper), primary_key_identity
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/ext/baked.py", line 615, in load_on_pk_identity
result = list(bq.for_session(self.session).params(**params))
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances
cursor.close()
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in exit
exc_value, with_traceback=exc_tb,
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise
raise exception
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances
rows = [proc(row) for row in fetch]
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in
rows = [proc(row) for row in fetch]
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/loading.py", line 525, in _instance
tuple([row[column] for column in pk_cols]),
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/orm/loading.py", line 525, in
tuple([row[column] for column in pk_cols]),
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/engine/result.py", line 686, in key_fallback
replace_context=err,
File "/obi/ApacheSuperset/superset_36/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise
raise exception
sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'slices.id'"
what you expected to happen.
Actual results
what actually happens.
Screenshots
If applicable, add screenshots to help explain your problem.
How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Environment
(please complete the following information):

superset version: superset version
python version: python --version
node.js version: node -v
npm version: npm -v

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Resolved.


Popup window is sticking out.

          +---- Only padding space is sticking out now.
--------+ |
        | v
 +---------+
 |popup    |
 |window   |
 +---------+
        |
        |
        |

before

after

I'll add test.

The popup can extend beyond the right of the screen if needed.  Depending on the options.
I do notice that for computing the text width and position the border and padding on the left is not taken into account.  I'll fix that.  I'm not sure anything else is needed.  Perhaps an extra option to avoid the popup being cut off?

The popup can extend beyond the right of the screen if needed. Depending on the options.
I see.

I do notice that for computing the text width and position the border and padding on the left is not taken into account. I'll fix that.
Isn't right_extra also?

https://github.com/vim/vim/commit/51c313104096c7af5024aebbf295f7f03486874b#diff-7d2ae970f06481cdd82cece2a74b6c8cR591

I saw Test_popupwin_20.dump and understood the specifications.

I'm not sure anything else is needed. Perhaps an extra option to avoid the popup being cut off?

I think the extra option is unnecessary.

The popup can extend beyond the right of the screen if needed. Depending on the options.
I see.

I do notice that for computing the text width and position the border and padding on the left is not taken into account. I'll fix that.
Isn't right_extra also?

I think it's OK that the right padding and border is not visible.
Apparently we have run out of space, thus sacrificing those to show more
text makes sense.
--
hundred-and-one symptoms of being an internet addict:
202. You're amazed to find out Spam is a food.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


Adapting Mock ListView to new ListView properties.

General items:

[ ] I have updated the relevant documentation files under docs/
[x] My code follows the:

[x] Google Java style guide (for .java files)
[ ] Google JavaScript style guide (for .js files)

[x] ant tests passes on my machine

If your code changes how something works on the device (i.e., it affects the companion):

[ ] I branched from ucr
[ ] My pull request has ucr as the base

Further, if you've changed the blocks language or another user-facing designer/blocks API (added a SimpleProperty, etc.):

[ ] I have updated the corresponding version number in YaVersion.java
[ ] I have updated the corresponding upgrader in YoungAndroidFormUpgrader.java (components only)
[ ] I have updated the corresponding entries in versioning.js

For all other changes:

[x] I branched from master
[x] My pull request has master as the base

What does this PR accomplish?

**Added support for all ListView properties to the designer view. Replaced all instances of the deprecated DOM.setStyleAttribute() method in MockComponentUtil.java. Added support for alpha transparency channel for colors in the designer, previously it only supported full transparency. **

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test


neurogenesis inconsistencies

There is a bit of inconsistency in the definitions of terms in the "neurogenesis" arm of BP.  The definiton of "neurogenesis" (GO:0022008) is: Generation of cells within the nervous system.  That definition makes the following example #1 a reasonable child of "neurogenesis", until you come across example #2 which has a more narrow definition of "neurogenesis" which is inconsistent with the term and definition in example #1.  I suggest a review of the definition of "neurogenesis" and its children.
EXAMPLE #1 CHILD OF NEUROGENESIS: "gliogenesis" (GO:0042063) DEFINITION: The process that results in the generation of glial cells. This includes the production of glial progenitors and their differentiation into mature glia.
EXAMPLE #2 CHILD OF NEUROGENESIS: "regulation of neurogenesis" (GO:0050767) DEFINITION: Any process that modulates the frequency, rate or extent of neurogenesis, the origin and formation of neurons.

If no comments against, I am going to relax the definition of the regulation term.

Hi @ukemi I agree it makes sense to relax the definition of the regulation term to fit with that of the parent.

perhaps this was relaxed too far "cells in the nervous system" includes endothelial cells in blood vessels, epithelial cells of the CP, etc.
Also, I am not an expert but I am not familiar with the term "neurogenesis" being inclusive of glial cells. I bet when curators directly annotate to neurogenesis they are assuming neurons. This means that we have many annotations that are more general than they should be (a quick sample seems to confirm this). And in fact many of those seem like they are better placed under a more specific term like neuron differentiation.
The definitions are still inconsistently worded:
id: GO:0042063
name: gliogenesis
def: "The process that results in the generation of glial cells. This includes the production of glial progenitors and their differentiation into mature glia." [GOC:dgh, GOC:jid]
id: GO:0022008
name: neurogenesis
def: "Generation of cells within the nervous system." [GO_REF:0000021, GOC:cls, GOC:curators, GOC:dgh, GOC:dph, GOC:jid]
The gliogenesis definition better hints at the start and end but neurogenesis is very open to interpretation
I wish we had made some of these do not annotate from the outset.


Update environment variables for manual and auto instrumentation

Right now we have our own environment variables to enable logging or enable disable signals.
We want to normalise this to fall in line with the OpenTelemetry upstream conventions across the board (including our proprietary agent).
Also relates to: https://github.com/elastic/apm-agent-dotnet/pull/2371

Closed by both #132 and  #129


Using this like Alert in React Native?

Hey there,
I just came across this Module and I have some questions.
I am building a RN App and I want to use Expo Web. Expo Web currently does not support the Alert Module from React Native thats why I want to code a workaround.
I was hoping I can use this to achieve this. I tried the SandBox and noticed that the "alert" here is just a little hint popping at the bottom of the screen. Is it possible to make it pop in the middle of the screen and only disappear if the user clicks 1 of 2 buttons build in the alert?
Like a Close button to dismiss the alert and a Edit button to for example Navigate to another page.
Or should I just use a Modal for this ? like react-modal which I am about to use to replace ReactNatives Modal component.
Thanks ~Faded.

Any guidance or tips on this?

Hi @yesIamFaded

Is it possible to make it pop in the middle of the screen - yes, it's positions.MIDDLE
You should try to write your own AlertTemplate with custom onClick events on the buttons
I hope, that it would work for you

Alright thanks @besLisbeth :)


Add human agents in the simulator

Hi, I would to like if OmniGibson can also add human agents in the simulator and also control their behavior, just like the iGibson. The paper show a an example: https://www.youtube.com/watch?v=aFwbK-hpyjk&t=176s.
I have checked the document, and nothing about the multi-agent config has been found. if there is a method, please let me know, great thanks!!

Hi @ConnerQiu, yes OG currently supports multi-agent. You can specify more than one robot in the robot config, and for env.step(action), you will pass in an action dict. We will incorporate Behaviorbot (just like iGibson) in the near future where you can use this method to add and control multiple humanoid robot in a scene.
There is another omniverse human animation extension where you can add human character into scenes. We don't have an immediate plan to integrate this but might be able to do so in the second half of this year.

Hi, @wensi-ai Thanks for your quick response! So, once the Behaviorbot is incorporated in OG, we can the current method of adding multiple robots to add multiple humanoid robots. Can we can add self-define robots? So that I can define some humanoid robots, and then add them in the environment. Or do you have a schedule about incorporating the Behaviorbot, since I plan to start my project in OG recently. Maybe there is some way we can corporate to avoid some redundant work.

We are finetune the Behaviorbot and will be releasing it next month. Meanwhile you can also add your self-defined robot into OG by writing a custom robot class that inherits BaseRobot. For that you can take a look at the robot classes under omnigibson/robots folder


Nuget package is a trainwreck

This is packaged in Nuget as a library but the Nuget package has the entire source code embedded in it and tries to compile the docusign client in the build. While it works on my local machine, it crashes hard on the build server we use because it's trying to reference DLLs in a /bin  folder whereas these are in /bin/Release on our build server.
I had to create my own version of the package locally to get this to work, by creating a new repository with the source code and a nuget package that only contains the DocuSign.eSign.dll, and references to the two dependencies in the .nuspec file

@conficient Sorry for the inconvenience. We have resolved the issue you have mentioned with version 2.1.4. Please try that and reopen this issue if it still an problem.


Integration Test - Release - 2018/11/16 16:38:53

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest2 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.