[$1000] Not Allowed sign is not shown when dragging attachments on Archived rooms

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open any Archived Room
Drag the attachment on The Archived Room

Expected Result:
The not Allowed sign is shown when dragging attachments on Archived rooms
Actual Result:
Copy sign is shown when dragging attachments on Archived rooms
Workaround:
unknown
\
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.50-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43995119/1996f0dd-0a00-4d3f-b4ae-d0fb0256b1ec
https://github.com/Expensify/App/assets/43995119/ec80a070-ceee-4ee9-ab3e-557e1dfb8cb8
Expensify/Expensify Issue URL:
Issue reported by: @daveSeife
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690837081412469
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01340b7f14e5ffd467
Upwork Job ID:<PHONE_NUMBER>227458048
Last Price Increase: 2023-08-17

Added the external label.

@allroundexperts This seems like a duplicate of https://github.com/Expensify/App/issues/22218 as the problem is the same  This should be handled there as well!

Hi,
I tried a lot on this issue, what I came to know is there are 4 possible values to the drop effect and in case of archived room I have used 'none' for the cursor drop effect. I also passed additional param for checking archive rooms to drag drop component.
Please check this video link and let me know if this work for you
https://www.loom.com/share/17278877c8794e17a3754b98d327538d?sid=f0389e05-e68f-41c5-9e3f-76cc417b2e44

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01e4d32778f98872aa

Hi,
I have tried a lot on this issue, to my knowledge i can only find 4 possible values to dropeffect. And In case of archive rooms I have set this to 'none'. I also pass additional param to dragndrop component to check whether it is archive room or not
Please look at this video and share your thoughts
https://www.loom.com/share/17278877c8794e17a3754b98d327538d?sid=967c6a31-bb4c-4478-87bc-4aa9085a2a87

This is how fixed code performs in a window os
https://github.com/Expensify/App/assets/95413216/4564a938-9e29-4a9f-9ea9-8059a3486aa6

@noahroman please take your concern here to #22218.
cc: @flaviadefaria this is on hold for #22218

@Santhosh-Sellavel Should I start working to that issue too?

@flaviadefaria please add hold to the title and remove help wanted label thanks!

On hold

Still on hold

Still on hold.

Still on hold

@Santhosh-Sellavel https://github.com/Expensify/App/issues/22218 has been closed does this mean that this issue is fixed?

Removed the hold so that we can take action and either close or fix (in case there's something still tobe fixed).

@Santhosh-Sellavel #22218 should solve this. We might want to put this one on hold for that.

@allroundexperts Is this solved now?

Seems it's not solved yet?
https://github.com/Expensify/App/assets/85645967/f14ee4fc-31dd-4a4e-92d4-55a09d90c847

@Santhosh-Sellavel we should still look for proposals here, right?

Proposal
Please re-state the problem that we are trying to solve in this issue.
Not Allowed sign is not shown when dragging attachments on Archived rooms.
What is the root cause of that problem?
https://github.com/Expensify/App/blob/562f9d8ff66d1e90285df088fa785c9638aa3861/src/pages/home/ReportScreen.js#L412
Currently, we only disallow drag/drop if the report is not ready for display.
So the copy sign is still shown when dragging attachment on archived room.
https://github.com/Expensify/App/blob/562f9d8ff66d1e90285df088fa785c9638aa3861/src/pages/home/report/ReportActionCompose/ReportActionCompose.js#L412-L420
Although drag/drop is allowed, we can't drop file on archived room anyway.
Because archived room doesn't have the composer, which means the report screen doesn't have ReportDropUI component to handle drop event.
As a result, we can't drop file on archived room but copy sign is shown while dragging attachment.
What changes do you think we should make in order to solve the problem?
<DragAndDropProvider isDisabled={!isReportReadyForDisplay || ReportUtils.isArchivedRoom(report)}>

We should disallow drag/drop in the report screen if the report is archived.
As a result, the not-allowed sign will be shown when dragging attachment on archived room.
What alternative solutions did you explore? (Optional)
N/A

From #24191 (comment)

@Santhosh-Sellavel #22218 should solve this. We might want to put this one on hold for that.

@allroundexperts Is this solved now?

Bump @allroundexpertsm how did this one get missed?

22218 is for disabling drag and drop (show disallow cursor) by default

Where do we show a disabled cursor, I don't see any disabled cursor at all. I just see an Arrow cursor is that what is expected at the other PR?

@Santhosh-Sellavel Are you testing on Mac? It doesn't show a disabled cursor on Mac. But on Windows, it shows disabled cursor.

Yeah, I'm testing on mac!

@garrettmknight  I'm officially no longer in the BugZero team so reassigning this as it will not close until tomorrow.

@Santhosh-Sellavel just catching up on this one. Is this a good summary of where we're at?

This was on hold for another fix
The other fix was finally completed
This issue still exists, but only on Macs
We're waiting for proposals

Yeah pretty much,

This issue still exists, but only on Macs

This exists on both platforms. But confused about the other issue fix which is expected to show a disabled cursor on mac but it's not!
Waiting for @allroundexperts to answer this or @ginsuma

22218 is for disabling drag and drop (show disallow cursor) by default

Where do we show a disabled cursor, I don't see any disabled cursor at all. I just see an Arrow cursor is that what is expected at the other PR?

bump @ginsuma or @allroundexperts

So, if we were to fix this, we'd likely be adding a fix for MacOS only. Is that right @Santhosh-Sellavel ?
I noticed there isn't any error thrown so if you do this on a mac you're just dropping without any failure indication.

@hungvu193's proposal here looks good to me!
C+ Reviewed
🎀 👀 🎀
@garrettmknight

So, if we were to fix this, we'd likely be adding a fix for MacOS only. Is that right @Santhosh-Sellavel ?

Not exactly, seems platforms handle things in their own way. Seems the current behaviour with Mac seems to be expected as per this comment. So we will be consistent and address this missing case too!

Deployed to production last week.

Summary of payments:

Reporter: @daveSeife $50 paid via upwork
Contributor: @hungvu193 $1000 paid via upwork
Reviewer: @Santhosh-Sellavel $1000

Upwork job: https://www.upwork.com/jobs/~01340b7f14e5ffd467

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@Santhosh-Sellavel ] The PR that introduced the bug has been identified. Link to the PR:
[ ]  [@Santhosh-Sellavel ] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ]  [@Santhosh-Sellavel ] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ]  [@Santhosh-Sellavel ] Determine if we should create a regression test for this bug.
[ ]  [@Santhosh-Sellavel ] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@Santhosh-Sellavel can you complete the checklist and request payment?

.@garrettmknight The reporter's payment should be $250. This matter was raised prior to the deduction occurring.

@daveSeife fair - updated payment.

I have Received the payment. Thank You! @garrettmknight

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@Santhosh-Sellavel ] The PR that introduced the bug has been identified. Link to the PR: N/A It was there right from
[x]   [@Santhosh-Sellavel ] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[x]   [@Santhosh-Sellavel ] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x]   [@Santhosh-Sellavel ] Determine if we should create a regression test for this bug. N/A Minor UI
[x]   [@Santhosh-Sellavel ] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[x]   [@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

$1,000 payment approved for @Santhosh-Sellavel based on this comment.


Bump dependencies

Bump outdated dependencies where possible

related https://github.com/gbif/ipt/issues/1346


Add "Musical Suit' and "FederAPI" to the mod list,

Hello!
I have recently released 2 of my mods:

Musical Suit: Adds a new suit (Notes ♪). with new jokers, tarot, and blind.
FederAPI: An API library mod that allows to register vouchers, blinds, tarots, sounds, etc.

I would love if you could add them to the list.
Thanks!

Here's a link to the mods:
https://github.com/itayfeder/MusicalSuit
https://github.com/itayfeder/FederAPI-Balatro

Thank you for your contribution. Next time, you can directly submit a pull request to make changes to the list.


TBDGen: Introduce option to emit API descriptor as supplementary output

An "API descriptor" file is JSON describing the externally accessible symbols of a module and metadata associated with those symbols like availability and SPI status. This output was previously only generated by the swift-api-extract alias of swift-frontend, which is designed to take an already built module as input. Post-processing a built module to extract this information is inefficient because the module and the module's dependencies need to be deserialized in order to visit the entire AST. We can generate this output more efficiently as a supplementary output of the -emit-module job that originally produced the module (since the AST is already available in-memory). The new -emit-api-descriptor flag can be used to request this output.
The output of -emit-api-descriptor differs from the output of swift-api-extract run on an existing module in a couple of important ways:

The value for the file key in the descriptor JSON is now the path to the source file that defines the declaration responsible for the symbol. In swift-api-extract mode, the value for this key is the path to the module or swiftinterface which is unavailable during an -emit-module job since the module is usually not being emitted to its final installed location.
Some additional symbols may be included in the API descriptor JSON because more of the AST is available when emitting the module.

Resolves rdar://110916764

Do you have ideas of roughly what are the kinds of these additional symbols that were not available from serializing the module? I see in the test case one additional symbol for method lookup function for a class.

Yeah, the method lookup function is the example that prompted me to call this out. I haven't identified other examples, but that was enough to indicate to me that there could also be other examples that the test cases don't demonstrate.

See https://github.com/apple/swift-driver/pull/1460 for the driver.


Feat(eos_designs): Only require 'virtual_router_mac_address' when using VARP or anycast IP on SVIs

Change Summary

Only require 'virtual_router_mac_address' when using VARP or anycast IP on SVIs
Related Issue(s)
Fixes #2473
Component(s) name
arista.avd.eos_designs
Proposed changes

Remove static requirement for virtual_router_mac_address
Update docs
Add check for mac during rendering of SVIs and emit errors accordingly
Update molecule group_vars under eos_designs_unit_tests to only set the virtual mac where needed.

How to test

Removed the mac from the unit test groups vars where not strictly required. Still works.
Tested with removing the mac from some of the remaining unit test group vars and saw the errors being raised.

Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

@ClausHolbechArista  - FYI pushed a PR on your branch: https://github.com/ClausHolbechArista/ansible-avd/pull/24


Customise the list of ciphers for sshd service (Rocky 8 and above)

In RHEL 8 system-wide crypto policy is used, hence modifying sshd_config doesn't do anything for ciphers.
It is handled in /etc/crypto-policies/back-ends/ - but the latter shouldn't be changed.

We modify the /etc/ssh/sshd_config file with Ansible by default, however, it does not take effect unless a system-wide crypto policy usage is disabled in /etc/sysconfig/sshd:
CRYPTO_POLICY=


[TYPO] Mispelling of Label "Sing up" -> "Sign up"

Is coming with version 0.4.0

Is fixed in the current Release


ERROR! couldn't resolve module/action 'community.general.ufw'

I'm getting this after installing the galaxy role just now.
ERROR! couldn't resolve module/action 'community.general.ufw'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/mdf/.ansible/roles/weareinteractive.ufw/tasks/service.yml': line 3, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Configuring service state
  ^ here

My ansible is v2.95 on Ubuntu Focal

Are you using Ansible >= 2.10 as stated in the README?
If you're version is lower, use the 1.x releases.

As stated in my original message, I am using v2.95.
Is that not >= 2.10?

actually I'm wrong it's 2.9.6. I will upgrade my ansible now.
Thanks.

hola, una consulta encontraste la solucion?

hello, a query did you find the solution?
ERROR! couldn't resolve module/action 'community.general.ufw'

@ysmaelferradas you need to update you ansible version if you want to use the lastest version of this role.

Hey guys, what could be a problem on Ansible 2.10?

ansible-galaxy collection install community.general
This was missing. Can this be defined as an explicit dependency?

@kbcz1989 check your ansible version:  ansible --version

the actual problem was that community.general collection was not installed:
ansible-galaxy collection install community.general

FWIW installing the community.general using:
ansible-galaxy collection install community.general

was only required on a ansible 2.9.27 and not on ansible [core 2.13.7].

FTR I had the error. EEs are a new concept to me: it turned out collections are loaded from a Docker container rather from the local filesystem, as it was the case with ansible-playbook. For now my workaround is to install collections into ./collections (as documented here: ansible-galaxy collections install community.general -p ./collections) but I'll probably end up building an EE.


Abort from Clearing not possible

The Parent response abort is not possible in state clearing.

Both the SubModuleMonitor and ComponentMonitor do not allow the abort command defined in the PackML model.

Thank you Mr Kirkegaard for your input to our repository.  We take in all issues and discuss them as a team.
On the issue that the SubmoduleMonitor and ComponentMonitor do not take the parentResponse in clearing and directly go to Aborting is done because we use Clearing to reset safety and other alarms. If we responded to them before being cleared, we would end up in a race condition.   So, we would usually have a timeout in Clearing and if the devices did not reset, we would send state engine to Aborting.
We feel that the framework follows PackML and our implementation of the Framework gives you the flexibility to do what you need.

Hi Keith
Thank you for the feedback.
Is there a possibility that you can clarify this in the SPT Framework documentation, that ParrentResponseDefinition deliberately has no effect in state clearing?
Is it possible to add a Transition State Timeout function in FB_PackML_BaseModule?
I have had to Extended the FB_PackML_BaseModule to implement a Transition state timeout in all my Equipment Modules and the Unit.


No documentation on how to setup proxies for other environment

There is are examples on how to mock responses but not any examples how to point to actual services.

should be closed with https://github.com/Availity/availity-ekko/releases/tag/v0.2.0


[5pt] ESIP Sample Inputs

In ESIP, we have as folder that covers all inputs required for just one HUC 12090301, so a user can download just that folder, rename it as "inputs" on their local machine and have a quicker way to do some experiments. The folder was created a number of months back and is 744 MG, and by using this one, they don't have to pull down the over 1 TB inputs directory to do some simple experiments.
It exists in ESIP at s3://noaa-nws-owp-fim/hand_fim/sample_inputs/  and also on OWP Servers on our fim share... "sample_inputs" beside "inputs".
Two things need to be done.

Our FIM README.md was never updated to tell folks that this simpler test set was available.
With the recent addition of pre-clip, the sample inputs will need to be updated.  Was there any other new ones or adjustments since the summer?  Files for ras2fim calibration maybe? rating curve input data? not sure but we need to look into it.

Duplicate. Task partly done already in Issue 936


Clarify which password make release is requesting

The make process has this piece:
Releasing
DOCKER_ORG=expediadotcom, DOCKER_IMAGE_NAME=haystack-adaptive-alerting-metric-router, QUALIFIED_DOCKER_IMAGE_NAME=expediadotcom/haystack-adaptive-alerting-metric-router
BRANCH=, TAG=, SHA=
Password:
Error response from daemon: Get https://registry-1.docker.io/v2/: unauthorized: incorrect username or password
make[1]: *** [release] Error 1
make: *** [release] Error 2

Please clarify which password is being requested in the prompt to avoid people sending incorrect credentials to docker.io.

Done


Added delegate API to get details of providers who have set rule

delegate can call API to get details of providers who have permitted
them to serve as delegates on their behalf
401 if not a delegate, 404 if no providers have given access
added tests

Update Postman collections with new APIs and the updated APIs


Rerun if "Tile upload incomplete " and "Cloud probability data missing"

Is your feature request related to a problem? Please describe.
empty_asset_list can contain "Tile upload incomplete " and "Cloud probability data missing". So if we rerun a specific date, we need to check that the missing clouds and tiles are still not available
Describe the solution you'd like
if not in the available asset list ,check if in empty_asset_list as in https://github.com/swisstopo/topo-satromo/blob/9ed1b93fc1c6c804ab83a1dc254edea4b7bf9409/step0_functions.py#L91 then try to rerun it if "Tile upload incomplete " and "Cloud probability data missing" and if successful remove  it from empty_asset_list
Describe alternatives you've considered
delete manually available asset list and then rerun

Fixed with https://github.com/swisstopo/topo-satromo/commit/2da69eb6edfedc83802b7265cb926d98140155d2
-> run with command promt


change edit credential to patch operation

Signed-off-by: James Talton<EMAIL_ADDRESS>

Issue Ref: https://github.com/open-cluster-management/backlog/issues/12196

/lgtm


LAB 2B : Prateek Bashista (Worked with Joyendra Roy Biswas)

Added links to parts completed.

Updated config files and added feedback before friday( 10 AM)


No questions are selected

Here is what I do:
git clone git@github.com:certificationy/certificationy-cli.git
cd certificationy-cli/
composer install

php certificationy.php start
Starting a new set of 0 questions (available questions: 274)

php certificationy.php start --number=10
Starting a new set of 0 questions (available questions: 274)

php -v
PHP 7.0.18-0ubuntu<IP_ADDRESS> (cli) (built: Apr 26 2017 23:59:48) ( NTS )

It works now, thank you!


ref/reduce eval nix interface

ref: reduce eval.nix contract
ref: reduce eval.nix contract forther
ref: reduce eval.nix contract even further
ref: transparent eval.nix contract

Thanks! I'll make a decision about a public eval interface in a bit.


Some way to simulate &mut reborrows in user code

@carllerche wanted a way to make a newtyped &mut that would reborrow in the same implicit way that reborrows do today. That is, with an &mut, foo(ptr) is roughly equivalent to foo(&mut *ptr), but if ptr is MyRef<'a>(&'a mut ...), then this will not coerce from MyRef<'a> to MyRef<'b> (where 'a:'b).

In one of the designs for rust-cpython that I explored; I ran into a similar issue:
I had a zero-sized struct (newtype around PhantomData<&mut 'p ()>), which could not be Copy (unsafe code relied on the fact that user code had access to at most one instance of the struct at a time).
But this struct still had to be passed around between function calls; which needs something like re-borrowing to avoid the code becoming unwieldy.
In my case, I ended up going with a different design where the struct could be Copy instead. (although there were more reasons for that than the lack of reborrowing)

+1. Commenting to track.

We could handle this similarly to unsizing coercions - see Rc's CoerceUnsized impl, which "only" require that it has a single field also implementing CoerceUnsized, and this repeats all the way down to the primitive impls (specified in #982).
So if we generalized, impl<T: ?Sized, U: ?Sized> Coerce<Rc<U>> for Rc<T> would require that *mut T: Coerce<*mut U> which can be satisfied with an T: Unsize<U> bound.
And impl<'a, 'b> Coerce<MyRef<'b>> for MyRef<'a> would require 'a: 'b and borrowck would treat it as a reborrow.
Should it work on multiple fields, including mixed coercions, e.g. one unsizing and one reborrowing, in different fields?
FWIW, we currently kind of support reborrowing combined with unsizing due to the way the CoerceUnsized impls for &T and &mut T are generic over both input and output lifetimes, so impl CoerceUnsized<MyRef<'b, U>> for MyRef<'a, T> would work, but borrowck may not understand it as a reborrow.

@eddyb In my case, my type has multiple fields. If I understand your comment, then implementing CoerceUnsized wouldn't work?

@carllerche implementing CoerceUnsized doesn't work unless you have an unsizing and it doesn't even result in a reborrow.
I'm talking about extending the mechanism to allow all coercions to happen inside user-defined types, with opt-in at the definition site.
Personally, I think Option<&mut T> having reborrows would be quite handy.

Personally, I think Option<&mut T> having reborrows would be quite handy.

Yes, please. In one piece of code that really should have used Option<&mut HashSet<Name>> I’ve ended up using &mut Option<HashSet<Name>> in order to get re-borrows.

cc me

This is sort of possible today. Consider the following (messy, off-the-top-of-my-head, borderline embarrassing) associated-type-encoded-HKTs-based formulation:
pub trait Reborrowable<'a> {
    type Result;
}
pub trait ReborrowMut<'self_>: for<'a> Reborrowable<'a> + Reborrowable<'self_, Result=Self> {
    fn reborrow<'reborrow>(&'reborrow mut self)
        -> <Self as Reborrowable<'reborrow>>::Result
        where 'self_: 'reborrow;
}

This can be used as so: https://gist.github.com/anonymous/4aa1bfddaf5efdb53b15 (sans the type-identity trait bound to ensure Reborrowable is well-behaved; I believe that particular bit not working is merely a bug rather than a missing feature).
I'm not saying that this is a solution - far from it. Still, it's possible to within a single function call on a trait (which is just about what the Deref trait does with autoref'ing).

This is part of what I was getting at in http://dwrensha.github.io/capnproto-rust/2014/12/27/custom-mutable-references.html

Ran into a need for this today.

I've run into this twice now.

This would also be super helpful for iovec which is used heavily as part of Mio / Tokio / the bytes crate, etc... for vectored operations.

Ran into it too. It's really annoying since the workarounds are very verbose and hard to understand.

I've also run into it.
Is there a reason why a simple Reborrow marker trait would not work? For compiler it can behave as Copy, but with additional restriction on having two copies at the same time.

Not to bikeshed, but what about (an incredibly verbose) &re T & &re mut T?

@newpavlov I would honestly recommend just using a reborrow method for now, like this one:
impl<'a, DS: DrawSharedImpl> DrawIface<'a, DS> {
    /// Reborrow with a new lifetime
    pub fn reborrow<'b>(&'b mut self) -> DrawIface<'b, DS>
    where
        'a: 'b,
    {
        DrawIface {
            draw: &mut *self.draw,
            shared: &mut *self.shared,
            pass: self.pass,
        }
    }
}

Having an official trait for this and having it used automatically might be nice but isn't a big deal.
BTW we ran into it years ago with the Rand project (something to do with passing R: Rng where &mut Rng impls Rng I think, but don't remember the details).
@ShadowJonathan I don't see the point of special syntax. As far as I'm concerned the point is to make the usual syntax for reborrows work for "reference wrappers" so that users don't have to think about it.

A major use case for this is fat pointers that aren’t dyn traits or slices. For example: bit arrays (pointer, number of bits, offset in first byte) or rectangular slices of 2D arrays (pointer, width, height, distance between rows). This is a scenario that certainly caused me to run into this issue several times.
/// Borrowed 2D pixel map rectangular slice.
pub struct PixelMapRef<'a> {
    _slice: PhantomData<&'a [Pixel]>,
    pixels: *const Pixel,
    pitch: usize,
    width: usize,
    height: usize,
}

/// Mutably borrowed 2D pixel map rectangular slice.
pub struct PixelMapMut<'a> { /* just like the above */ }

There’s a few problems with these “custom reference types”:

You don’t get the nice &mut-like semantics. This is what this issue is mainly about, but there are other problems too:
You need to define both immutable and mutable versions.
They don’t work nicely with AsRef, AsMut, Borrow, BorrowMut, Deref, and DerefMut. These traits work only with & and &mut-style references.
They don’t automatically convert mutable versions to immutable versions (like &mut T would to &T).
They don’t automatically get lifetimeless (pointer) variants.

There’s a new Pointee trait, which I think could be adapted to provide a nice solution to the custom fat pointer problem. If it were possible to write custom impls for the Pointee trait (currently prohibited), then you could define custom metadata for your fat pointers, whilst piggybacking on all the existing reference infrastructure. And you would no longer need to write custom reference-like types, alleviating all the problems listed above.
Hypothetical code example:
/// Custom opaque type.
extern "C" { type PixelMapSlice; }
impl Pointee for PixelMapSlice {
    type Metadata = (usize, usize, usize);
}

// now you can do stuff like this:
fn f(&mut PixelMapSlice) { }
let slice: &mut PixelMapSlice = ...;
f(slice); // no move!
f(slice); // no Copy!
let pixel_map = PixelMap::new(); // owned
let slice = Borrow::borrow(&pixel_map); // Borrow impl
let no_lifetimes: *const PixelMapSlice = slice; // pointer type

Granted this wouldn’t cover other cases of &mut-like semantics; just custom fat pointers.

If it were possible to write custom impls for the Pointee

This is custom DSTs. I believe there’s a lot more language design involved than "just allow Pointee impls". Multiple RFCs have attempted to define this already, as you probably know.
Please let’s keep this issue about re-borrowing of existing types like Option<&mut Foo>. If and when custom DSTs are added, whatever is done here should apply too.


Improve controller template when no action

Fix for https://github.com/rspec/rspec-rails/issues/2375
A generated file looks like this:
require 'rails_helper'

RSpec.describe "Posts", type: :request do
  describe "GET /index" do
    it "returns http success" do
      pending "add some scenarios (or delete) #{__FILE__}"
    end
  end
end

Made with @tsleal29, @yann120, @fwuensche and @musait


New npm version ?

Afaict, the version on npm is dated from 2 years ago, do you consider publishing a new version (https://www.npmjs.com/package/ng-annotate-webpack-plugin)

I have $inject annotations in my project that break on the old 0.9.11 of ng-annotate your "latest" release targets. An updated release (which include your nice version bumps to ng-annotate and webpack-core) would be greatly appreciated.

Hey, I've done this. sorry about the delay.


opencv 3.3.0: python 3.5: ImportError: numpy.core.multiarray failed to import

I used berryconda to install opencv 3.3.0 into a python 3.5 virtual environment
but "import cv2" yielded this error:
ImportError: numpy.core.multiarray failed to import

I tried to replicate this on a Raspberry Pi 3 by creating a new environment using conda create -n opencv_test python=3.5 opencv.  I was able to import cv2 fine.
Can you provide some additional details on the environment where you are seeing this error?  How was berryconda installed, what hardware is being used, how was opencv was installed, what is the output of conda list in the environment with opencv.

Here's the precise history of what I did from my notes:
In an environment using python 3.5.4.
`pi@qacker:~/bitsy_gen3/dev-tools/qacker $ source activate qt
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ conda list
packages in environment at /home/pi/berryconda3/envs/qt:

ca-certificates           2<IP_ADDRESS>                   0
certifi                   2018.1.18        py35hd55c48c_0
ncurses                   5.9                           0
openssl                   1.0.2l                        0
pip                       9.0.1                    py35_0
python                    3.5.4                         0
readline                  6.3                           0
setuptools                38.4.0           py35he1abd54_0
sqlite                    3.15.0                        0
tk                        8.6.6                         0
wheel                     0.30.0           py35haa2052f_0
xz                        5.2.2                         0
zlib                      1.2.11                        0
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ conda search opencv
Fetching package metadata .......
opencv                       3.3.0            py36hb02bd27_0  defaults
3.3.0            py27h0ae2b19_0  defaults
3.3.0            py35hb6a5d43_0  defaults
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ conda install opencv
Fetching package metadata .......
Solving package specifications: .
Package plan for installation in environment /home/pi/berryconda3/envs/qt:
The following NEW packages will be INSTALLED:
bzip2:       1.0.6-0
ffmpeg:      3.2.4-h11ee089_0
giflib:      5.1.4-h3b1de47_0
hdf5:        1.8.17-0
jasper:      1.900.1-hb74bc11_4
jpeg:        9b-0
libgfortran: 3.0.0-0
libpng:      1.6.28-0
libtiff:     4.0.6-0
libwebp:     0.5.2-hcb3eeb6_7
numpy:       1.14.0-py35h0995c57_0
openblas:    0.2.19-0
opencv:      3.3.0-py35hb6a5d43_0
x264:        20131217-h754e1d8_0

Proceed ([y]/n)? y
numpy-1.14.0-p 100% |################################################################################################################################| Time: 0:01:40  77.20 kB/s
numpy-1.14.0-p 100% |################################################################################################################################| Time: 0:00:42 179.93 kB/s
opencv-3.3.0-p 100% |################################################################################################################################| Time: 0:01:08 219.59 kB/s
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ `
Immediately afterwards I got the the error when I tried to import python within this environment.
The python version defaulted to 3.5.4 when I created the environment by specifying 3.5.
I tried to build opencv from scratch using this
install guide
However, cmake gave me an error saying that it wanted python 3.5.3 instead:
-- Could NOT find PythonLibs: Found unsuitable version "3.5.3", but required is exact version "3.5.4" (found /usr/lib/arm-linux-gnueabihf/libpython3.5m.so) Traceback (most recent call last):   File "<string>", line 1, in <module>   File "/home/pi/berryconda3/envs/qt/lib/python3.5/site-packages/numpy/__init__.py", line 166, in <module>     from . import random   File "/home/pi/berryconda3/envs/qt/lib/python3.5/site-packages/numpy/random/__init__.py", line 99, in <module>     from .mtrand import * ImportError: /home/pi/berryconda3/envs/qt/lib/python3.5/site-packages/numpy/random/mtrand.cpython-35m-arm-linux-gnueabihf.so: undefined symbol: PyFPE_jbuf
I created a new environment with that version:
 $ conda create --name gui python=3.5.3
but cmake gave me a similar error
-- Found PythonLibs: /usr/lib/arm-linux-gnueabihf/libpython3.5m.so (found suitable exact version "3.5.3")  Traceback (most recent call last):   File "<string>", line 1, in <module>   File "/home/pi/berryconda3/envs/gui/lib/python3.5/site-packages/numpy/__init__.py", line 166, in <module>     from . import random   File "/home/pi/berryconda3/envs/gui/lib/python3.5/site-packages/numpy/random/__init__.py", line 99, in <module>     from .mtrand import * ImportError: /home/pi/berryconda3/envs/gui/lib/python3.5/site-packages/numpy/random/mtrand.cpython-35m-arm-linux-gnueabihf.so: undefined symbol: PyFPE_jbuf
The only way I was able to get opencv to build was to follow the author's instructions using virtualenv.
I hope this is helpful.

Was there any more of the error message?  Can you try running python -c "import numpy.core.multiarray"?

My apologies, but it looks like this might be my bad.
I had to reinstall opencv in the virtual environment, but that particular import works correctly after doing so.
`(qt) pi@qacker:~ $ python
Python 3.5.4 | packaged by rpi | (default, Aug  9 2017, 08:07:25)
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.

import cv2
import numpy.core.multiarray
quit()
(qt) pi@qacker:~ $ python -c "import numpy.core.multiarray"
(qt) pi@qacker:~ $ `

However, I am able to reproduce the error running my shell script.
Digging a little deeper it seems like the problem might be caused by having a different version of numpy in my PATH.
`(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ cat qacker-pi.sh
#!/bin/bash
export PYTHONPATH=".:/home/pi/bitsy_gen3/Shared:/usr/lib/python3/dist-packages:$PYTHONPATH"
export PYTHONPATH="/usr/local/lib/python3.5/dist-packages:$PYTHONPATH"
export PYTHONPATH="/usr/local/lib/python3.5/dist-packages/paho_mqtt-1.3.1-py3.5.egg:$PYTHONPATH"
python qacker-PyQt5.py
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ python
Python 3.5.4 | packaged by rpi | (default, Aug  9 2017, 08:07:25)
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.

import sys
print(sys.path)
['', '/home/pi/berryconda3/envs/qt/lib/python35.zip', '/home/pi/berryconda3/envs/qt/lib/python3.5', '/home/pi/berryconda3/envs/qt/lib/python3.5/plat-linux', '/home/pi/berryconda3/envs/qt/lib/python3.5/lib-dynload', '/home/pi/berryconda3/envs/qt/lib/python3.5/site-packages']
quit()

(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ export PYTHONPATH=".:/home/pi/bitsy_gen3/Shared:/usr/lib/python3/dist-packages:$PYTHONPATH"
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ export PYTHONPATH="/usr/local/lib/python3.5/dist-packages:$PYTHONPATH"
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ export PYTHONPATH="/usr/local/lib/python3.5/dist-packages/paho_mqtt-1.3.1-py3.5.egg:$PYTHONPATH"
(qt) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ python
Python 3.5.4 | packaged by rpi | (default, Aug  9 2017, 08:07:25)
[GCC 4.9.2] on linux
Type "help", "copyright", "credits" or "license" for more information.

import sys
print(sys.path)
['', '/usr/local/lib/python3.5/dist-packages/paho_mqtt-1.3.1-py3.5.egg', '/usr/local/lib/python3.5/dist-packages', '/home/pi/bitsy_gen3/dev-tools/qacker', '/home/pi/bitsy_gen3/Shared', '/usr/lib/python3/dist-packages', '/home/pi/berryconda3/envs/qt/lib/python35.zip', '/home/pi/berryconda3/envs/qt/lib/python3.5', '/home/pi/berryconda3/envs/qt/lib/python3.5/plat-linux', '/home/pi/berryconda3/envs/qt/lib/python3.5/lib-dynload', '/home/pi/berryconda3/envs/qt/lib/python3.5/site-packages']
import cv2
ImportError: numpy.core.multiarray failed to import
Traceback (most recent call last):
File "", line 1, in
ImportError: numpy.core.multiarray failed to import

`
I was not able to find a version of PyQt5 that could be installed via pip or conda, so I had to install via apt-get.
Similarly I was not able to find a working version of paho-mqtt for python 3.5 on raspbian, so I had to build externally and add to my path.
Interestingly, however, I can set the PYTHONPATH exactly the same in my virtualenv environment (where I built openCV from scratch) without getting this error.
So, It's still a bit of a mystery of why it works in virtualenv and not in berryconda.
(qacker_gui) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ export PYTHONPATH=".:/home/pi/bitsy_gen3/Shared:/usr/lib/python3/dist-packages:$PYTHONPATH"
(qacker_gui) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ export PYTHONPATH="/usr/local/lib/python3.5/dist-packages:$PYTHONPATH"
(qacker_gui) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ export PYTHONPATH="/usr/local/lib/python3.5/dist-packages/paho_mqtt-1.3.1-py3.5.egg:$PYTHONPATH"

(qacker_gui) pi@qacker:~/bitsy_gen3/dev-tools/qacker $ python
Python 3.5.3 (default, Jan 19 2017, 14:11:04)
[GCC 6.3.0 20170124] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print(sys.path)
['', '/usr/local/lib/python3.5/dist-packages/paho_mqtt-1.3.1-py3.5.egg', '/usr/local/lib/python3.5/dist-packages', '/home/pi/bitsy_gen3/dev-tools/qacker', '/home/pi/bitsy_gen3/Shared', '/usr/lib/python3/dist-packages', '/home/pi/.virtualenvs/qacker_gui/lib/python35.zip', '/home/pi/.virtualenvs/qacker_gui/lib/python3.5', '/home/pi/.virtualenvs/qacker_gui/lib/python3.5/plat-arm-linux-gnueabihf', '/home/pi/.virtualenvs/qacker_gui/lib/python3.5/lib-dynload', '/usr/lib/python3.5', '/usr/lib/python3.5/plat-arm-linux-gnueabihf', '/home/pi/.virtualenvs/qacker_gui/lib/python3.5/site-packages']
>>> import cv2
>>> import numpy.core.multiarray
>>> quit()

It is quite possible that the Python extension modules built with the system Python are not compatible with Berryconda.  Setting the PYTHONPATH variable to the system dist-/site-packages directory is trying to mix these two sets of extension modules.
I have a suspicion that this may be a result of the different configuration that were used to build Python for Berryconda and Raspian.  Specifically Raspian uses the --with-fpectl flag where as Berryconda does not enable this flag.  The resulting binaries have different ABIs, see bpo-29137.
My recommendation is to build anything not included by Berryconda from source using the Python provided by Berryconda.  I understand that this can be a difficult task but it seem to be the only method to insure binary compatibility.


:cucumberTest - Could not start process: Exception

Using 0.7 version of plugin. On windows 7, I got the following error:
Executing task ':cucumberTest' (up-to-date check took 0.0 secs) due to:
Task has not declared any outputs.
Could not start process:
java.io.IOException: Cannot run program "c:\jdk8\jre\bin\java": CreateProcess error=206, The filename or extension is too long
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at org.zeroturnaround.exec.ProcessExecutor.invokeStart(ProcessExecutor.java:931)
at org.zeroturnaround.exec.ProcessExecutor.startInternal(ProcessExecutor.java:910)
at org.zeroturnaround.exec.ProcessExecutor.execute(ProcessExecutor.java:860)
at org.zeroturnaround.exec.ProcessExecutor$execute$3.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
at com.commercehub.gradle.cucumber.JavaProcessLauncher.execute(JavaProcessLauncher.groovy:64)
at com.commercehub.gradle.cucumber.JavaProcessLauncher$execute$3.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
at com.commercehub.gradle.cucumber.CucumberRunner$_run_closure2_closure5.doCall(CucumberRunner.groovy:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at groovyx.gpars.pa.GParsPoolUtilHelper$_eachParallelPA_closure8.doCall(GParsPoolUtilHelper.groovy:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1019)
at groovy.lang.Closure.call(Closure.java:426)
at org.codehaus.groovy.runtime.ConvertedClosure.invokeCustom(ConvertedClosure.java:53)
at org.codehaus.groovy.runtime.ConversionHandler.invoke(ConversionHandler.java:105)
at com.sun.proxy.$Proxy75.op(Unknown Source)
at groovyx.gpars.extra166y.AbstractParallelAnyArray$OUPap.leafApply(AbstractParallelAnyArray.java:640)
at groovyx.gpars.extra166y.PAS$FJOApply.atLeaf(PAS.java:147)
at groovyx.gpars.extra166y.PAS$FJBase.compute(PAS.java:108)
at jsr166y.RecursiveAction.exec(RecursiveAction.java:148)
at jsr166y.ForkJoinTask.doExec(ForkJoinTask.java:305)
at jsr166y.ForkJoinWorkerThread.execTask(ForkJoinWorkerThread.java:575)
at jsr166y.ForkJoinPool.scan(ForkJoinPool.java:755)
at jsr166y.ForkJoinPool.work(ForkJoinPool.java:617)
at jsr166y.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:369)
Caused by: java.io.IOException: CreateProcess error=206, The filename or extension is too long
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.(ProcessImpl.java:386)
at java.lang.ProcessImpl.start(ProcessImpl.java:137)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 47 more
:cucumberTest FAILED
:cucumberTest (Thread[main,5,main]) completed. Took 0.4 secs.
Could you please help to resolve this issue?

@sharmasourabh
My guess is that you are running into a limit on the length of a command line in windows. The classpath for your tests are being written to this command line and is likely the cause. I don't have a clear idea for a fix. You might be able to work around this by trimming your classpath or reducing the average length of the paths to jars by storing them elsewhere.
If you come up with a novel way to reliably shorten the classpath portion of the command line programmatically, we would be open to adding it via a pull request.

@sharmasourabh : Add these flags in your build.gradle file
reports.junitXml.enabled = false
reports.html.enabled = false
and give a try . They are used to turn off the report generation as the longer names are not supported.

Thanks @RajAsapu. I tried it, still facing same issue.

@sharmasourabh do you have those flags in test task
eg:
test {
reports.junitXml.enabled = false
reports.html.enabled = false
}

I placed these flags in test {} only. Do I need to place in somewhere else?

@sharmasourabh : No it should be in test. You did it right . What is your task to run the cucumber tests ? Is it cucumberTests . You should place the above tags in which ever task you are running either test or any custom task. that should work, give it a try.

As this project is now deprecated, CommerceHub will not be contributing further on this ticket.  Please feel free to fork the project and work on it further yourself under the terms of the project license if desired.


Incorrect protoGenericType for fixed integer types

When using a protobuf message with fixed integer types like: sfixed32 fixed32 etc. they are matched to a protobuf type, e.g. Fixed32, SInt32:
https://github.com/apple/swift-protobuf/blob/c081bfef1fecd34f950740f100986155ab20acc3/Sources/protoc-gen-swift/Descriptor%2BExtensions.swift#L152-L175
but all the types are named with a Protobuf prefix, e.g. ProtobufFixed32, ProtobufSInt32:
https://github.com/apple/swift-protobuf/blob/c081bfef1fecd34f950740f100986155ab20acc3/Sources/SwiftProtobuf/FieldTypes.swift#L269

I've confused some things, it's not an issue.


State that CUDA Toolkit 8.0 required in docs

As per title - the required version did not seem to be stated explicitly anywhere in the documentation.

Thanks for the PR. I'm wondering if this can also be added to the conda recipe under run_constrained so as to make it impossible to install Numba from a conda channel with the wrong version of CTK?

Is that buildscripts/condarecipe.local that you are referring to?

Is that buildscripts/condarecipe.local that you are referring to?

yes

Also wonder if there's an easy runtime check that can be done?

Is that buildscripts/condarecipe.local that you are referring to?

yes

Do you run that just with conda build .? It's not finding numpy for the tests when I build it, but I may be doing something wrong locally.

Also wonder if there's an easy runtime check that can be done?

There is already the check for the libdevice version, which I believe gets run when you compile a CUDA kernel: https://github.com/numba/numba/blob/master/numba/cuda/cudadrv/nvvm.py#L277-L326
I was originally trying to clarify whether the version recommended by that check was still accurate, which lead to my question on gitter and then this PR.
Do you envisage another check as well?

Is that buildscripts/condarecipe.local that you are referring to?

yes

Do you run that just with conda build .? It's not finding numpy for the tests when I build it, but I may be doing something wrong locally.

Yes, it's just conda build . What are you seeing happen?

Also wonder if there's an easy runtime check that can be done?

There is already the check for the libdevice version, which I believe gets run when you compile a CUDA kernel: https://github.com/numba/numba/blob/master/numba/cuda/cudadrv/nvvm.py#L277-L326
I was originally trying to clarify whether the version recommended by that check was still accurate, which lead to my question on gitter and then this PR.
Do you envisage another check as well?

No, just didn't recall the original check :) I think the doc + recipe update should be fine.

Do you run that just with conda build .? It's not finding numpy for the tests when I build it, but I may be doing something wrong locally.

Seems I might have been affected by something like https://github.com/ContinuumIO/anaconda-issues/issues/10628, so I just tested the changes to the package with a different Python version (3.6 as opposed to 3.7), which seems to work.
As a more general question - is the buildscripts/condarecipe.local recipe the canonical recipe for building Numba packages, with the .local suffix being a hangover from when there was also condarecipe.jenkins etc.?

Yes, it's just conda build . What are you seeing happen?

TEST START: /home/gmarkall/miniconda3/conda-bld/linux-64/numba-0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707.tar.bz2
Renaming work directory,  /home/gmarkall/miniconda3/conda-bld/numba_1576842311964/work  to  /home/gmarkall/miniconda3/conda-bld/numba_1576842311964/work_moved_numba-0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707_linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done

## Package Plan ##

  environment location: /home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho

The following NEW packages will be INSTALLED:

    _libgcc_mutex:          0.1-main
    backcall:               0.1.0-py37_0
    binutils_impl_linux-64: 2.33.1-he6710b0_7
    binutils_linux-64:      2.33.1-h9595d00_15
    blas:                   1.0-mkl
    ca-certificates:        2019.11.27-0
    certifi:                2019.11.28-py37_0
    cffi:                   1.13.2-py37h2e261b9_0
    decorator:              4.4.1-py_0
    gcc_impl_linux-64:      7.3.0-habb00fd_1
    gcc_linux-64:           7.3.0-h553295d_15
    gxx_impl_linux-64:      7.3.0-hdf63c60_1
    gxx_linux-64:           7.3.0-h553295d_15
    intel-openmp:           2019.4-243
    ipython:                7.10.2-py37h39e3cac_0
    ipython_genutils:       0.2.0-py37_0
    jedi:                   0.15.1-py37_0
    jinja2:                 2.10.3-py_0
    ld_impl_linux-64:       2.33.1-h53a641e_7
    libedit:                3.1.20181209-hc058e9b_0
    libffi:                 3.2.1-hd88cf55_4
    libgcc-ng:              9.1.0-hdf63c60_0
    libgfortran-ng:         7.3.0-hdf63c60_0
    libstdcxx-ng:           9.1.0-hdf63c60_0
    llvmlite:               0.31.0dev0-py37hf484d3e_8                     numba
    markupsafe:             1.1.1-py37h7b6447c_0
    mkl:                    2019.4-243
    mkl-service:            2.3.0-py37he904b0f_0
    ncurses:                6.1-he6710b0_1
    numba:                  0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707 local
    numpy:                  1.11.3-py37h7e9f1db_12
    numpy-base:             1.11.3-py37hde5b4d6_12
    openssl:                1.1.1d-h7b6447c_3
    parso:                  0.5.2-py_0
    pexpect:                4.7.0-py37_0
    pickleshare:            0.7.5-py37_0
    pip:                    19.3.1-py37_0
    prompt_toolkit:         3.0.2-py_0
    ptyprocess:             0.6.0-py37_0
    pycparser:              2.19-py37_0
    pygments:               2.5.2-py_0
    python:                 3.7.5-h0371630_0
    readline:               7.0-h7b6447c_5
    scipy:                  1.3.2-py37h7c811a0_0
    setuptools:             42.0.2-py37_0
    six:                    1.13.0-py37_0
    sqlite:                 3.30.1-h7b6447c_0
    tbb:                    2019.8-hfd86e86_0
    tk:                     8.6.8-hbc83047_0
    traitlets:              4.3.3-py37_0
    wcwidth:                0.1.7-py37_0
    wheel:                  0.33.6-py37_0
    xz:                     5.2.4-h14c3975_4
    zlib:                   1.2.11-h7b6447c_3

Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
export PREFIX=/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho
export SRC_DIR=/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/test_tmp
INFO: activate-binutils_linux-64.sh made the following environmental changes:
+ADDR2LINE=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-addr2line
+AR=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-ar
+AS=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-as
+CXXFILT=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-c++filt
+ELFEDIT=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-elfedit
+GPROF=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-gprof
+HOST=x86_64-conda_cos6-linux-gnu
+LD_GOLD=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-ld.gold
+LD=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-ld
+NM=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-nm
+OBJCOPY=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-objcopy
+OBJDUMP=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-objdump
+RANLIB=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-ranlib
+READELF=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-readelf
+SIZE=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-size
+STRINGS=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-strings
+STRIP=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-strip
INFO: activate-gcc_linux-64.sh made the following environmental changes:
+CC=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-cc
+CFLAGS=-march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/numba-0.47.0dev0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix
+CMAKE_PREFIX_PATH=$PREFIX:$PREFIX/x86_64-conda_cos6-linux-gnu/sysroot/usr
+CONDA_BUILD_SYSROOT=$PREFIX/x86_64-conda_cos6-linux-gnu/sysroot
+_CONDA_PYTHON_SYSCONFIGDATA_NAME=_sysconfigdata_x86_64_conda_cos6_linux_gnu
+CPPFLAGS=-DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem $PREFIX/include
+CPP=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-cpp
+DEBUG_CFLAGS=-march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-all -fno-plt -Og -g -Wall -Wextra -fvar-tracking-assignments -ffunction-sections -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/numba-0.47.0dev0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix
+DEBUG_CPPFLAGS=-D_DEBUG -D_FORTIFY_SOURCE=2 -Og -isystem $PREFIX/include
+GCC_AR=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-gcc-ar
+GCC=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-gcc
+GCC_NM=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-gcc-nm
+GCC_RANLIB=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-gcc-ranlib
+LDFLAGS=-Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -Wl,--gc-sections -Wl,-rpath,$PREFIX/lib -Wl,-rpath-link,$PREFIX/lib -L$PREFIX/lib
INFO: activate-gxx_linux-64.sh made the following environmental changes:
+CXXFLAGS=-fvisibility-inlines-hidden -std=c++17 -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/numba-0.47.0dev0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix
+CXX=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-c++
+DEBUG_CXXFLAGS=-fvisibility-inlines-hidden -std=c++17 -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-all -fno-plt -Og -g -Wall -Wextra -fvar-tracking-assignments -ffunction-sections -pipe -isystem $PREFIX/include -fdebug-prefix-map=$SRC_DIR=/usr/local/src/conda/numba-0.47.0dev0 -fdebug-prefix-map=$PREFIX=/usr/local/src/conda-prefix
+GXX=$PREFIX/bin/x86_64-conda_cos6-linux-gnu-g++
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'
Traceback (most recent call last):
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/bin/pycc", line 7, in <module>
    from numba.pycc import main
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/__init__.py", line 30, in <module>
    from .decorators import (cfunc, generated_jit, jit, njit, stencil, jit_module)
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/decorators.py", line 14, in <module>
    from .targets import registry
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/targets/registry.py", line 5, in <module>
    from . import cpu
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/targets/cpu.py", line 14, in <module>
    from numba.targets import (
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/targets/codegen.py", line 15, in <module>
    from numba.runtime.nrtopt import remove_redundant_nrt_refct
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/runtime/__init__.py", line 3, in <module>
    from .nrt import rtsys
  File "/home/gmarkall/miniconda3/conda-bld/numba_1576842311964/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeho/lib/python3.7/site-packages/numba/runtime/nrt.py", line 12, in <module>
    from . import _nrt_python as _nrt
ImportError: numpy.core.multiarray failed to import
Tests failed for numba-0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707.tar.bz2 - moving package to /home/gmarkall/miniconda3/conda-bld/broken
WARNING:conda_build.build:Tests failed for numba-0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707.tar.bz2 - moving package to /home/gmarkall/miniconda3/conda-bld/broken
WARNING conda_build.build:tests_failed(2231): Tests failed for numba-0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707.tar.bz2 - moving package to /home/gmarkall/miniconda3/conda-bld/broken
TESTS FAILED: numba-0.47.0dev0-np1.11py3.7hf484d3e_ga3178260e_707.tar.bz2

Doing conda build . --python 3.6 made the error go away.

Do you run that just with conda build .? It's not finding numpy for the tests when I build it, but I may be doing something wrong locally.

Seems I might have been affected by something like ContinuumIO/anaconda-issues#10628, so I just tested the changes to the package with a different Python version (3.6 as opposed to 3.7), which seems to work.

hmmm, puzzling

As a more general question - is the buildscripts/condarecipe.local recipe the canonical recipe for building Numba packages, with the .local suffix being a hangover from when there was also condarecipe.jenkins etc.?

yes and yes

Doing conda build . --python 3.6 made the error go away.

ah yes, now you mention it I think you may have to tell it a python version and a numpy version still via flags to conda build, or use one of these https://docs.conda.io/projects/conda-build/en/latest/resources/variants.html#conda-build-variant-config-files

I see, by default I was getting an odd Python / Numpy combination - 3.7 + 1.11, which seems to have this trouble in the test environment created by conda-build - if I explicitly specify these versions I get the same failure.
I tried creating an environment with numba=0.46 python=3.7 numpy=1.11 and that seems to work OK though.

I think this is ready now (though please do let me know if there's something else to resolve :-) ).


Any plans to upgrade to YML?

+1.  I'm new to GitHub actions and, whilst this action appears to solve my needs (passing args to the docker build process), I have no clue how to actually use it in my action as the syntax in the examples isn't YAML and it is not apparent how to translate it to YAML


example from Step 3 Windows Server quick start does not work

docker run -it -p 80:80 microsoft/iis cmd
whoch loads image from repo and extracts but then stucks when running interactively by only showing "service w3svc started" instead of cmd.exe prompt.
Tried with different machines.
Entrypoint and running process seems to servicemonitor.exe
any idea?
exactly reproducable by quitting with ctrl-c and restarting with docker start name -a

meanwhile I can probably understand the sense of servicemonitor.exe (instead of ping to keep the IIS running) but there will be no interactive session possible as explained in the docs. probably docker images change too fast currently...

I have the same issue!

as I understood: the microsoft/iis images is build with a docker file that uses  ENTRYPOINT ["C:\ServiceMonitor.exe", "w3svc"] at the end. This is not overridable with the docker run, as it would be with dockerfile created with CMD instead of ENTRYPOINT. the exact purpose of choosing either way should be explained by more experienced experts.  I will put this as an issue/question in the repo of the docker image

to workout the next steps in the docs you can do it e.g. with docker exec <iis-container-ID> cmd del C:\inetpub\wwwroot\iisstart.htm

This entry covers another workaround http://stackoverflow.com/questions/40391896/cannot-launch-interactive-session-in-windows-iis-docker-container
docker run --entrypoint powershell -it -p 80:80 microsoft/iis

Yes @rs38 the documentation is still incorrect. I only found the solution at http://stackoverflow.com/questions/40391896/cannot-launch-interactive-session-in-windows-iis-docker-container
definitely not obvious for a docker newbie.

the according PR is open for many days and stuck for unknown reasons :(
https://github.com/Microsoft/Virtualization-Documentation/pull/458

Given that Docker containers for Server 2016 is still quite "bleeding edge", I don't mind the wait.

Closing this issue as the PR mentioned above has been merged. Please reopen if there is still something we can help with.


All output files into the ZIP

I noticed that the .ZIP file contains all the output files included the Bom.csv and the Positioning.csv, not only the Gerber files.
on JLCPCB is required that the ZIP contains only the Gerber and the other 2 ones are uploaded separately.
Uploading the ZIP with all the files in it (included the CSV) doesn't bring any benefit.

True, but I thought it is a good idea to include then anyways so it will be easy to distribute the entire artifact (i.e., to client).


ARROW-2184: [C++]  Add static constructor for FileOutputStream returning shared_ptr to OutputStream

Add constructors to return pointers to the base interface

Just rebased this, please
git fetch origin
git reset --hard origin/ARROW-2184

+1. Will merge once the build is green. Thanks!


URLs include for Django 2.0

The next version of Django is changing quite radically the way URLs are being included, by requiring an app name to be provided. One way to do it (and sometimes the only one) is to change the first parameter to a tuple.
It would be great if there could be a version of include in django-compat. It looks like the new syntax is available from 1.9, and the old syntax is no longer working from 2.0.
Would that be an acceptable change? I could try to put together a PR if so.

Django 2.0 has been released!


Add more extensive notes for SQL Injection in Bug Bounty

Assigned this to myself as it is my notes

Done and dusted.


https://github.com/github/docs/issues

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?

Additional information

https://github.com/github/docs/issues


xActiveDirectory: Fix various documentation issues

Pull Request (PR) description

Changes to xActiveDirectory

Style guideline cleanup.

All localized strings in the resources now has a string ID suffix (issue #419).
All schema properties description now ends with full stop (.) (issue #420).
Updated all types in the resources schema to use PascalCase.
Updated all resource read-only parameters to start the description
with 'Returns...' so it is more clear that the property cannot be
assigned a value.
The default value on resource parameters are now reflected in the parameter
descriptions in the schema.mof (so that Wiki will be updated) (issue #426).

Changes to xADServicePrincipalName

Minor change to the unit tests that did not correct assert the localized
string when an account is not found.

This Pull Request (PR) fixes the following issues

Fixes #419
Fixes #420
Fixes #426

Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in resource directory README.md.
[x] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #428 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #428   +/-   ##
===================================
  Coverage    92%    92%
===================================
  Files        20     20
  Lines      2536   2536
  Branches     10     10
===================================
  Hits       2347   2347
  Misses      179    179
  Partials     10     10

@PlagueHO If you have time, could you review this one? A lot of files, but small changes mostly. But might be a lot of grammar issues. 🙂 You can skip review the *help.txt files as I will generate them automatically again if there need to be changes done to the descriptions in the schema.mof.

Yep! On it straight after dinner (just eating now).

@PlagueHO Thank you so much for this and the grammar help! I added an issue to DscResource.Tests to get the change into the auto-doc (if possible).


get_user_model - Django 1.4 compatibility

In admin.py, function _user__username is not compatible with Django 1.4
File "/push_notifications/admin.py", line 7, in _user__username
     from django.contrib.auth import get_user_model
ImportError: cannot import name get_user_model

It can be fixed with something like :
try:
	from django.contrib.auth import get_user_model
except ImportError: # django < 1.5
	from django.contrib.auth.models import User
else: User = get_user_model()

I don't think USERNAME_FIELD exists on Django 1.

I don't think USERNAME_FIELD exists on Django 1.4 so this would just fail further down.

Yeah you're right, I actually also used return "user__username"
Thanks for the quick fix.


Improve article 2109.02101: xymatrix output cropped

See the proof of Lemma 3.2 in https://ar5iv.labs.arxiv.org/html/2109.02101v1: The commutative diagram gets cropped as if each object was just a single symbol wide/high, even if it is not. The diagram in question is pretty simple, so let me quote it here:
\[
\xymatrixcolsep{5pc}\xymatrix{
C \ar[r]^-{\Delta} \ar[d]^{\id} & C \otimes C \ar[d]^{\id \otimes \epsilon} \\
C & C \otimes \kk \ar[l]^-{\gamma}
}
\]

@darijgr for this example, I am seeing the PDF rendering:

and the HTML rendering (in Chrome):

Could you clarify what you see as the discrepancy? Could this be an article version issue?

Here is what I see on Brave:

(Brave on Windows. ScriptSafe active but *.arxiv.org allowed.)

Ah, it's a Dark Mode issue. Wow.

Perfect, that screenshot demonstrates the problem fully. The bounding box indeed needs to be larger, but one needs dark mode to get the broken rendering.

Noting that since the article was updated, this xymatrix example has disappeared, while the general problem of ensuring a larger bounding box remains in latexml.


fix issue that interface needs to work under promiscuous mode

Currently we use randomisation of address in admin-cli to obfuscate. Such that, all addresses including Ethernet MACs are randomised.
This would require interfaces to work under promiscuous mode so that we can properly talk to the FPGA
Maybe an issue?

found the issue, it's caused by dstMAC addressing to a specific MAC address, can do a script to autoreplace that line in the VHDL code, and possibly write a build script without Vivado GUI.


Fix more re-renderings

Description

Follows up on #8203 by making click events non-rendering in other key controls to work around the problem mentioned in #8151 and https://github.com/dotnet/aspnetcore/issues/53863.
How Has This Been Tested?

TBD
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

@ScarletKuro Thanks for identifying the fix for MudButton in #8203! Seemed to do the trick as seen below:
https://github.com/MudBlazor/MudBlazor/assets/7112040/ad7456e6-4c5e-4e80-8c79-b80dd631a4af
This PR will expand that effort to other controls. I use MudIconButton and MudMenuItem specifically.
It hasn't been tested at all and pretty sure it doesn't compile, but I'm waiting to see if the original fix has no side effects, as you mentioned, and if you're interested in seeing the effort continued :)

Thanks for the PR .  For the variable I prefer _navigating but it's not critical. @henon ?

@mikes-gh I think you reviewed the commit which Daniel made on his own repo/app ;)

@ScarletKuro test is failing with:
A total of 1 test files matched the specified pattern.
  Failed AddAndRemoveEventListenerWhenChangingColorPickerView [45 ms]
  Error Message:
   Bunit.Rendering.UnknownEventHandlerIdException : There is no event handler with ID '12' associated with the 'onclick' event in the current render tree.

This can happen, for example, when using `cut.FindAll()`, and calling event trigger methods on the found elements after a re-render of the render tree. The workaround is to use re-issue the `cut.FindAll()` call after each render of a component, this ensures you have the latest version of the render tree and DOM tree available in your test code.

which could be from the icon buttons?
https://github.com/MudBlazor/MudBlazor/blob/5b3757a4c881e4b69b4f8eead488e22c1280d905/src/MudBlazor/Components/ColorPicker/MudColorPicker.razor#L12-L21

Yes, we unfortunately have a lot of these stale references in the tests.

Yes, this is why I had to do change the ToggleGroupTests.cs
I mentioned this issue here https://github.com/MudBlazor/MudBlazor/discussions/8151#discussioncomment-8501991
and as henon said its incorrectly made unit tests.

@ScarletKuro Think it's about ready if you want to check it out. Hopefully not too big. I am stuck on the last failing test though:
// MenuTests -> OnClickErrorContentCaughtException
public async Task OnClickErrorContentCaughtException()
{
    var comp = Context.RenderComponent<MenuErrorContenCaughtException>();
    await comp.FindAll("button.mud-button-root")[0].ClickAsync(new MouseEventArgs());
    comp.FindAll("div.mud-popover-open").Count.Should().Be(1);
    comp.FindAll("div.mud-list-item").Count.Should().Be(1);
    await comp.FindAll("div.mud-list-item")[0].ClickAsync(new MouseEventArgs());
    var mudAlert = comp.FindComponent<MudAlert>();
    var text = mudAlert.Find("div.mud-alert-message");
    text.InnerHtml.Should().Be("Oh my! We caught an error and handled it!");
}

@* MenuErrorContenCaughtException *@
@namespace MudBlazor.UnitTests.TestComponents
<ErrorBoundary>
    <ChildContent>
        <MudPopoverProvider></MudPopoverProvider>
        <MudMenu Label="Open Menu">
            <ChildContent>
                <MudMenuItem @onclick="@HandleClickAsync">Throw error</MudMenuItem>
            </ChildContent>
        </MudMenu>
        <br/>
    </ChildContent>
    <ErrorContent>
        <MudAlert Severity="Severity.Error">Oh my! We caught an error and handled it!</MudAlert>
    </ErrorContent>
</ErrorBoundary>

@code {
    public async Task HandleClickAsync()
    {
        await Task.Delay(100);
        throw new Exception("Something went wrong...");
    }
}

 OnClickErrorContentCaughtException
   Source: MenuTests.cs line 242
   Duration: 111 ms

  Message:
Bunit.Rendering.ComponentNotFoundException : A component of type MudAlert was not found in the render tree.

  Stack Trace:
TestRenderer.FindComponent[TComponent](IRenderedFragmentBase parentComponent) line 181
RenderedFragmentExtensions.FindComponent[TComponent](IRenderedFragment renderedFragment) line 58
MenuTests.OnClickErrorContentCaughtException() line 249
GenericAdapter`1.BlockUntilCompleted()
NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)
AsyncToSyncAdapter.Await[TResult](Func`1 invoke)
TestMethodCommand.Execute(TestExecutionContext context)
DelegatingTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)

I don't think it's capturing the exception properly due to the async click handler but I could be wrong. Not sure where to go from here. Adding a Comp.Render() in before searching for the Alert will throw the "Something went wrong..." exception.

I'm slightly confused why are we modifying the examples from Docs, they are not related to the Unit test area.
If it's only for testing purpose then they shouldn't be pushed to remote.
Otherwise I would refrain from bloating the docs, like the alert with button count has no value, same  as the added snackbar to the badge click.
Maybe I'm wrong, @henon can correct me.

@ScarletKuro @henon Should be ready except for the last failing test:

I will try to look on weekends when I get time, for now I'm busy with other PRs.

List item was reverted because the expand toggle wasn't working. Could be looked into further but I don't need it for what I'm doing and it seems to have wide-reaching consequences. Fixes the failing test and simplifies the PR significantly through SelectTests not needing the changes made.
Overlay was reverted too bc I'm not comfortable with the consequences of that either considering a Render had to be added to the test to make it work. Similar for SwipeArea.

@ScarletKuro PR has been trimmed down and all tests are passing 🎉
Two docs added: NavMenuOnClickExample and ChipClickableExample. Will delete if that's preferred!

@danielchalmers can you please post screenshots of the new examples?

OK, I think we can keep these examples.

Thanks @danielchalmers


[PE-D][Tester E] Error output message for delete command missing puncutation

There is a missing full stop and space in the last line in the screenshot above.

Labels: severity.VeryLow type.FunctionalityBug
original: vansh284/ped#5

Thank you for pointing out! Fixed in latest. There should be an enter after IRREVERSIBLE


Error attempting to locate Jupyter

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.69.2
OS Version: macOS Monterey (12.4 (21F79))

VS Code does not recognize correctly installed Jupyter packages in conda environments. Jupyter Notebooks in the browser can be launched successfully from the activated environment. When attempting to run a notebook in VS Code, an error is thrown:

info 12:44:44.504: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd0ec1689aadfb31809087390f003aaaf48945ecfc3bbda01b3082716ecd7919b65./opt/miniconda3/envs/menv/python./opt/miniconda3/envs/menv/python.-m#ipykernel_launcher' (Python Path: /opt/miniconda3/envs/menv, EnvType: Conda, EnvName: 'menv', Version: 3.10.5) for '/Users/myuser/Downloads/Untitled.ipynb' (disableUI=true)
info 12:44:44.504: Checking for server existence.
info 12:44:44.504: Checking for server usability.
info 12:44:44.506: Server not usable (should ask for install now)
info 12:44:44.509: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
> /opt/miniconda3/envs/menv/bin/python -c "import jupyter"
info 12:44:44.510: Process Execution: > /opt/miniconda3/envs/menv/bin/python -c "import notebook"
> /opt/miniconda3/envs/menv/bin/python -c "import notebook"
warn 12:44:44.610: Error occurred while trying to start the kernel, options.disableUI=true [i [Error]: Jupyter cannot be started. Error attempting to locate Jupyter: Running cells with 'Python 3.10.5 ('menv')' requires jupyter package.
	at S.startServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:98875)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async S.createServer (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:97995)
	at async l.connect (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:75175)
	at async g.create (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:95736)
	at async p.createJupyterSession (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:160545)
	at async p.start (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154488)
	at async Function.wrapKernelMethodImpl (/Users/myuser/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:336119)] {
  category: 'jupyterinstall'
}

Any attempt to proceed by clicking "install" ends with:
info 12:59:11.118:
# All requested packages already installed.

Steps to Reproduce:

install miniconda (M1)
create a new virtual environment (python 3.9) and install jupyter
install VS Code (M1)
install the Jupyter extension
select the conda environment as kernel

/extJupyter

It looks like this is caused by the Jupyter extension. Please file the issue to the Jupyter extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Lowercase the user name

Close: https://github.com/quipper/quipper/issues/26344

Test
chaspy@gate-a01.qs.manage:~$ sudo cp /usr/local/bin/kex /usr/local/bin/kex.org
chaspy@gate-a01.qs.manage:~$ sudo vi /usr/local/bin/kex
chaspy@gate-a01.qs.manage:~$ diff /usr/local/bin/kex.org /usr/local/bin/kex
122,123c122,123
<   # ref: https://github.com/kubernetes/kubernetes/pull/65884
<   runner = ENV['SUDO_USER'] || ENV['USER'] || "UNKNOWN"
---
>   # ref: https://github.com/kubernetes/kubernetes/pull/6588
>   runner = ENV['SUDO_USER'].downcase || ENV['USER'].downcase || "UNKNOWN"
chaspy@gate-a01.qs.manage:~$ sudo su MITSUBOSHI
MITSUBOSHI@gate-a01:/home/chaspy$ sudo kubectl-production console -- api bin/rails c
Switched to context "qs-quipper-production-app-admin".
Context "qs-quipper-production-app-admin" modified.
shell(#<Th:0x0000560bb267cb68 run>): /home/kubernetes-app-admin-production/bin/kubectl create -o json -f -
Created pod: api-56756d48b6-kex-mitsuboshi-6jmll
Waiting for the pod to start..
Executing the specified command 'bin/rails c' on 'api-56756d48b6-kex-mitsuboshi-6jmll'...
(This container will terminate automatically in 3600 seconds.)
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
DEPRECATION WARNING: Including LoggerSilence is deprecated and will be removed in Rails 6.1. Please use `ActiveSupport::LoggerSilence` instead (called from include at /vendor/bundle/gems/rails_stdout_logging-0.0.5/lib/rails_stdout_logging/rails.rb:3)
MONGODB | Removing server mongodb-02.qs.production:27000 because it reported itself as mongodb-f03.qs.production:27000
MONGODB | Removing server mongodb-01.qs.production:27000 because it reported itself as mongodb-f01.qs.production:27000
Loading production environment (Rails <IP_ADDRESS>)
quipper-api-rails(prod)>

👍


Remove bounds for #1689

Funny, I was about to do that. Thanks :)

Looks like we've still got some bounds issues in place:
servant-0.8.1 (Haskell Servant<EMAIL_ADDRESS>is out of bounds for:

[ ] language-puppet-1.2 (==0.7.*). Simon Marechal<EMAIL_ADDRESS>@bartavelle. @bartavelle
[ ] servant-lucid-0.7.1 (==0.7.*). Haskell Servant<EMAIL_ADDRESS>@SoenkeHahn @jkarni
[ ] servant-yaml-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.8). Oleg Grenrus<EMAIL_ADDRESS>@phadej. @phadej

servant-client-0.8.1 (Haskell Servant<EMAIL_ADDRESS>is out of bounds for:

[ ] language-puppet-1.2 (==0.7.*). Simon Marechal<EMAIL_ADDRESS>@bartavelle. @bartavelle

servant-server-0.8.1 (Haskell Servant<EMAIL_ADDRESS>is out of bounds for:

[ ] servant-yaml-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.8). Oleg Grenrus<EMAIL_ADDRESS>@phadej. @phadej

Did appropriate edits for servant packages. Language-puppet was restricted also elsewhere, will push new commit when all-cabal-files is updates

Language-puppet 1.3.1 is already servant-compatible, why is 1.2 picked here ?

bartavelle, because it's holded by http-client-0.5 not in the nightlies yet

For the record, I'm itching to pull the trigger on including http-client, though the fallout will be big.

@bartavelle @snoyberg I tried to build language-puppet's master with http-client with --constraint=http-client==<IP_ADDRESS>. It succeeded. If @bartavelle makes a relaxing revision, this should be ok.
No strong opinion on http-client-0.5. I'd let servant-0.8 to go in first.

Thanks @phadej ! I merged your PRs and pushed new versions on hackage.


Go-auto-instrumentation failling

Describe the bug
I am trying to add Go auto instrumentation to Rancher project , currently running in HA mode with 3 replicas.
Environment

Kubernetes 1.25
Go Version: 1.18
Version: v0.10.0-alpha

To Reproduce
Steps to reproduce the behavior:

Install OpenTelemetry Operator using this values.yaml

manager:
  image:
    repository: ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator
    tag: v0.90.0
  collectorImage:
    repository: otel/opentelemetry-collector-contrib
    tag: 0.90.1
  autoInstrumentationImage:
    go:
      repository: "otel/autoinstrumentation-go"
      tag: "v0.10.0-alpha"
  featureGates: "+operator.autoinstrumentation.go"
  certManager:
    enabled: true

Install the collector

apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: rancher
  namespace: cattle-system
spec:
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
          http:
    processors:
      memory_limiter:
        check_interval: 1s
        limit_percentage: 75
        spike_limit_percentage: 15
      batch:
        send_batch_size: 10000
        timeout: 10s

    exporters:
      debug:

    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: []
          exporters: [debug]

Install Instrumentation Go

apiVersion: opentelemetry.io/v1alpha1
kind: Instrumentation
metadata:
  name: rancher-instrumentation
  namespace: cattle-system
spec:
  exporter:
    endpoint: http://rancher-collector-headless.cattle-system.svc.cluster.local:4317
  propagators:
    - tracecontext
    - baggage
    - b3
  sampler:
    type: parentbased_traceidratio
    argument: "0.25"
  go:
    env:
      # Required if endpoint is set to 4317.
      # Go autoinstrumentation uses http/proto by default
      # so data must be sent to 4318 instead of 4317.
      - name: OTEL_EXPORTER_OTLP_ENDPOINT
        value: http://rancher-collector-headless.cattle-system.svc.cluster.local:4317

Adding annotations

template:
    metadata:
      creationTimestamp: null
      labels:
        app: rancher
        release: rancher
      annotations:
        instrumentation.opentelemetry.io/inject-go: 'true'
        instrumentation.opentelemetry.io/otel-go-auto-target-exe: /usr/bin/rancher
        sidecar.opentelemetry.io/inject: 'true'

Results
Instrumentation container is failing and restarting with a reason of "OOMKilled - exit code: 137" but in logs there is no error :
{"level":"info","ts":1705920290.1872249,"logger":"go.opentelemetry.io/auto","caller":"cli/main.go:94","msg":"building OpenTelemetry Go instrumentation ...","globalImpl":false} {"level":"info","ts":1705920292.1887016,"logger":"Instrumentation.Analyzer","caller":"process/discover.go:69","msg":"found process","pid":53}
Also somehow this is affecting the main Rancher container that shows this logs:
2024/01/22 10:44:55 [ERROR] Failed to connect to peer wss://<IP_ADDRESS>/v3/connect [local ID=<IP_ADDRESS>]: websocket: bad handshake 2024/01/22 10:44:57 [INFO] Removing peer <IP_ADDRESS>
Additional context
How can i verify if it's possible to add auto-instrumentation or this is a case where manual instrumentation with SDK is the only option ?

Can you please attach the entire log?

Sure @RonFed ,
This is the log of instrumentation sidecar and it just keeps restarting with same logs each time:
{"level":"info","ts":1705995691.3306305,"logger":"go.opentelemetry.io/auto","caller":"cli/main.go:94","msg":"building OpenTelemetry Go instrumentation ...","globalImpl":false}
{"level":"info","ts":1705995693.3312767,"logger":"Instrumentation.Analyzer","caller":"process/discover.go:69","msg":"found process","pid":53}

This is the logs of Rancher container:
...
2024/01/23 07:41:28 [INFO] Shutting down rbac.authorization.k8s.io/v1, Kind=RoleBinding workers
2024/01/23 07:41:28 [INFO] Shutting down rbac.authorization.k8s.io/v1, Kind=ClusterRole workers
2024/01/23 07:41:28 [INFO] Shutting down /v1, Kind=ServiceAccount workers
2024/01/23 07:41:28 [INFO] Shutting down apiregistration.k8s.io/v1, Kind=APIService workers
2024/01/23 07:41:28 [INFO] Starting cluster controllers for local
2024/01/23 07:41:28 [INFO] Starting /v1, Kind=Secret controller
2024/01/23 07:41:28 [INFO] Starting /v1, Kind=ServiceAccount controller
2024/01/23 07:41:28 [INFO] Starting cluster agent for local [owner=false]
2024/01/23 07:41:28 [INFO] Starting /v1, Kind=Namespace controller
2024/01/23 07:41:28 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=RoleBinding controller
2024/01/23 07:41:28 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding controller
2024/01/23 07:41:28 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=Role controller
2024/01/23 07:41:28 [INFO] Starting rbac.authorization.k8s.io/v1, Kind=ClusterRole controller
2024/01/23 07:41:31 [INFO] Adding peer wss://<IP_ADDRESS>/v3/connect, <IP_ADDRESS>
2024/01/23 07:41:31 [ERROR] Failed to connect to peer wss://<IP_ADDRESS>/v3/connect [local ID=<IP_ADDRESS>]: websocket: bad handshake
2024/01/23 07:41:34 [INFO] Removing peer <IP_ADDRESS>

And that's it there is no direct error giving any clue about why instrumentation is failing.

I had the same problem with OOMKilled.


Latest cert-manager-acmesolver docker image contains arm binary

Describe the bug:
Apparently the latest version of the image comes with a binary compiled for arm instead of amd64 as previous versions did, hence breaking compatibility.
I have verified it by running the image locally in my laptop and by inspecting the image using dive.
I'm not familiar with the build process using bazel so I have not gone further. Have been running cert-manager during months without problem and apparently the last push to quay.io/jetstack/cert-manager-acmesolver updated the canary tag 20h ago and introduced this breaking change according to quay.
Expected behaviour:
The docker image should contain a amd64 binary.
Steps to reproduce the bug:
Run the following command from a amd64 machine:
$ docker run --rm -ti quay.io/jetstack/cert-manager-acmesolver:canary bash
standard_init_linux.go:190: exec user process caused "exec format error"

Anything else we need to know?:
Environment details::

Kubernetes v1.9
Cloud-provider/provisioner: AWS/kube-aws
cert-manager version (e.g. v0.4.0): stable/0.5.0
Install method: Helm

/kind bug

Thanks for the report - I have confirmed this and tracked it down to only the latest image tag:
$ docker run --entrypoint=uname --rm -ti quay.io/jetstack/cert-manager-acmesolver:2e95421d -a
Linux 9d97cb920973 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 Linux

$ docker run --entrypoint=uname --rm -ti quay.io/jetstack/cert-manager-acmesolver:a06d888a -a
Linux ff55648c09bf 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 armv7l Linux

It appears the build job in question failed after pushing the acmesolver image, which seems highly suspect (https://storage.googleapis.com/jetstack-logs/logs/post-cert-manager-release-canary/1124363456384864256/build-log.txt)
We've been working on a new release tool in time for v0.8 that recently merged, and there are clearly some issues still at the moment.
For the time being, please use a versioned release of cert-manager - I'll put a patch together to fix this up shortly!
/priority critical-urgent
/milestone v0.8

I've tracked the issue here down and fixed it in #1639 😄


ati-drivers: update to Catalyst 15.7 and fix building with recent kernels

Fixes #2912.

/cc maintainers @MarcWeber, @offline, @geerds.

I'll test these changes this evening

Looks like my fix for 3.18 broke 3.14. I'm working on adding a conditional compilation to fix this...

Just to clarify in case someone is waiting on me: commit d7443ffb892be6c61eb71a20ae19e2da23f29dc8 fixes the problem mentioned in my previous comment, and to the best of my knowledge this should be ready to merge. I've been running it on my system for the past week.

I re-tested it's building at least, on both 64-bit and 32-bit, kernels 3.14, 3.18, 4.1.

I cannot rebuild my system with kernel 4.2 and ati drivers.
Maybe I post another issue for this.


Improve UI for Environment Variables

Description

Under the Launch Application tab you can list environment variables for your application. May I suggest these improvements:

It should be possible to maximize the environment variables window. By default it opens with a small size, which is annoying when you are editing long values (e.g. PATH). Also, the window does not remember its previous size.
Environment variables should be able to include and expand other environment variables e.g.

 ANOTHER_PATH   Set     someFolder
 PATH           Append  %ANOTHER_PATH%

For PATH to be correctly set, I had to expand  ANOTHER_PATH manually. That is unexpected behaviour.

In the UI, it should be possible to append multiple values to the same var:

  PATH Append   someFolder
  PATH Append   anotherFolder

Environment

RenderDoc version: 1.13
Operating System: Windows 10
Graphics API: OpenGL

I appreciate that the environment variables editor is quite basic and these would be good improvements, but it's intended for simple setups only and the value in having a complex editor seems low to me. There are additional complexities to handle such as when nested environment expansions happen that are not trivial to resolve. I'd accept a pull request if someone else wanted to implement these changes, but this is low priority enough that it's effectively not something I would ever implement myself so I'm going to close the issue.
Instead I would recommend that if your program requires a complex environment setup that you create a wrapper batch file or other script, and then launch that with child process capture enabled. That way you can do whatever setup you like with the full flexibility of a script/shell language.


feat(scheduled-tasks): add delete, list, listRepeated & get methods

Adds 4 new methods:

delete: Deletes/removes a job.
list: Lists jobs based on the type provided.
listRepeated: Lists repeatable jobs.
get: Get's a job of the id provided.

This won't actually work because container.tasks.strategy has the type of the base thing we implement. Instead these methods should be implemented in the ScheduledTaskHandler which then call the methods in the strategies.

@all-contributors please add @FC5570 for code


#question SELECT_VOICE_CHANNEL implementation

It doesn't appear that this wrapper has any of the SELECT_VOICE_CHANNEL RPC implementation in place. Is this correct or am I missing something. Will this be coming soon? Just curious! Awesome work, I have this wrapper working just doesn't have the feature I'm looking for. (which is obviously the one above.) ;)

Hey @djrisc! This repo only handles commands around Rich Presence, wrapped in our SDK. It does not touch the rest of our RPC commands, which require whitelisting to a program for which we are not currently accepting developers. Apologies for the confusion.


Weird https issue

Hi!
I installed this and it worked good on my dev, but ofc when i deployed it to production i stucked on https and http issue when clicking on a link:
Uncaught SecurityError: Failed to execute 'replaceState' on 'History': A history state object with URL 'http://***.com/category' cannot be created in a document with origin 'https://***.com'.

The links are just /category and such, so i don't know it is trying to go to http://. Do you guys know?

Changed to turbolinks and it works. sad, because i want to use this with partial, and turbolinks 3.0's partial is still a bit buggy.

Can you create a reproducible app? That would be really helpful


Remove the need to manually install NodeJS to build the Quarkus project

It would be nice to have DevServices kick in, pull NodeJS and build the project, when a local Node JS is not installed. Some back-end developers don't have NodeJS/NPM installed locally, so when you clone a repo with Quinoa, you don't have to go through the installation process: a simple mvn quarkus:dev would build and run the entire thing.

I see Quinoa as the glue between Quarkus and a NodeJS project, but I don't see it as a replacement.
I believe that when dealing with Frontend development (even from a Backend framework as a backend developer), you should have NodeJS installed on your local machine:

You might need to work (build, test, ...) on the frontend only directly in the frontend directory
Your IDE might needs NodeJS when working on the frontend part
It's quicker to directly call NodeJS than having to start a docker service and copy/mount all the files to build (and docker needs to be running)

Still I think having a solution where we don't need to manually install it would be nice. Here are two other solutions we could explore:

having a wrapper similar to mvnw for NodeJS, but I didn't find anything yet (maybe we should find the reason why it doesn't exist).
Another possibility to explore would be to use GraalVM NodeJS.

Found this: https://www.bradcypert.com/simple-npm-wrapper-using-nvm/

@ia3andy if you only have NodeJS projects, why would you use Quarkus and Quinoa ? If you use Quinoa it's because you are used to Quarkus, and you are used to having mvn quarkus:dev do everything for you (i.e. DevServices)
In the Quarkus workshop, to build the front end, we use a multistage Dockerfile build. Very handy as it does everything for you :
https://github.com/quarkusio/quarkus-workshops/blob/main/quarkus-workshop-super-heroes/super-heroes/ui-super-heroes/src/main/docker/Dockerfile.build-native#L13
It is a manuel process (not triggered by DevServices), it build a Docker image at the end (which we don't want here), but it's very useful when non-front-end developers need to, at least, build the project.

@ia3andy Noone prohibits you from having npm installed locally, too. Though I can't much imagine running the frontend without a backend (but hey, I am a backend developer...).
But all builds will use the same version (I build using quarkus.container-image.*) and if someone is to try your project, they won't have to investigate an error for missing a package manager. Self-containment of all dependencies is a big plus for me.

https://github.com/quarkiverse/quarkus-quinoa/discussions/114


Version bump, add 9.6 contrib, add plperl support

Bump the version numbers to reflect current point releases.
Add a 9.6-contrib image; note that mysql and tds foreign data wrappers are not included. Releases of these extensions exist, but are not available via the pgxn installation method at this time.
Add support for plperl and plperlu procedural languages, per customer request.

LGTM 👍