Fix for issue #68 by using self._log_debug instead of this._log.debug

This PR fixes #68 .

An alternative of using self (which is set to this) is using an arrow function in this case but we have self available so this is perfectly fine I guess

My bad I forgot to run the regression tests before pushing new package. Merging and will push new package within the hour


Adding catalog id cookie

Adding the new cookie in Dynamics commerce platform for maintaining catalog id selection. Updating the public documentation as per privacy review guidelines.
Work item : https://msazure.visualstudio.com/D365/_workitems/edit/16759780

:white_check_mark: Organization membership check passed
Requester is not a member of the MicrosoftDocs organization.


Create actions to build when pushed

It create one combined executable file.
Sorry, I don't have a mac, so I haven't been able to verify that one.

ありがとうございます！マージしますー


Can't deploy the operator without cert-manager

Right now we seem to treat cert-manager as optional, depending on whether ENABLE_OPERATOR_WEBHOOK is true. The problem is - ENABLE_OPERATOR_WEBHOOK is true by default, which makes make deploy break.
We should do one of the following:

Make ENABLE_OPERATOR_WEBHOOK false by default.
List cert-manager as a mandatory requirement in the readme.

In any case, we should walk through the readme and ensure all "paths" are working (e.g. deploying in default mode, deploying using custom images etc.).

can we close this issue as #149 is merged now ?

Closing.


The "go link already exists" message should add a link to the target

Sometimes I mistype a go/ link and land on the page to create one.
But then I correct the link in the go/[ text form ].
And I get a message like:
That go link already exists. go/foo points to https://foo.bar/baz
I would love it if https://foo.bar/baz was an actual link!

The browser extension has been updated to show that any duplicative go links already exist and it is clickable/an actual link. Users can still create the duplicative go link if desired


[keyvault] keyvault-admin: Migrate to new recorder

Packages impacted by this PR

@azure/keyvault-admin

Issues associated with this PR

Resolves #18002

Describe the problem that is addressed by this PR
Migrates keyvault-admin to the new recorder.

API change check
API changes are not detected in this pull request.


[WIP] adding support of all data channels types in cov

motivation from data by @annesodub

... also might conflict with #4808 that has been MRG for a while, so it would be better to get that one in first.

(will probably conflict with MRG-state #4799, too)

we could make them default to 0.1
anything else?

Yes the picking etc. needs to be updated in mne/viz/*.py where whitening is supported, and tests added that e.g. whitened ECoG data can actually be plotted (my guess is that you'll get an error on this PR)


Add the ability to render content as full pages

This includes:

being able to select a specific (rails) layout for each content
being able to tie a content page to any URL, with a sensible default
being able to preview the content if given the permission

This is covered by Spree::SolidusContentController#show, except for previewing which has no explicit support (I'll extract it to another issue).


Download error

`(python-facereco) mohamad@raspberrypi:~/MMM-GmailFeed $ npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN audit No fix available for request@*
npm WARN audit Updating xml2js to 0.6.2, which is a SemVer major change.
changed 1 package, and audited 51 packages in 4s
2 packages are looking for funding
run npm fund for details
npm audit report
request  *
Severity: moderate
Server-Side Request Forgery in Request - https://github.com/advisories/GHSA-p8p7-x288-28g6
Depends on vulnerable versions of tough-cookie
No fix available
node_modules/request
tough-cookie  <4.1.3
Severity: moderate
tough-cookie Prototype Pollution vulnerability - https://github.com/advisories/GHSA-72xf-g2v4-qvf3
No fix available
node_modules/tough-cookie
2 moderate severity vulnerabilities
Some issues need review, and may require choosing
a different dependency.     `

PR #9 will fix this issue. However, the module should still work despite these warnings.

Yeah it is working after I moved the module to modules folder ,but first I tried without doing that as it didn't stated that in the readme and I am kinda new to MMM it is working pretty good other than those two:it shows null for a secound when updating the email and the width is as much as it could be
Thanks

it shows null for a secound when updating the email

I think that should be fixed with my fix as well.

the width is as much as it could be

I don't really understand what you mean by that. Can you describe it in more detail?

The width of the mudele is the from screen left edge to right one unless there is other models that block the way then it looks good and the width is okay

@killua173 Okay, I can imagine the behavior at position: bottom_bar. Do you have that? Please try position: bottom_center.


Boundary F-score calculation

Hi,
Is the implementation of the boundary F-score calculation that's used in the paper included in the repo?
Thanks!

Not in this repo. We directly used the code released by SegFix (https://github.com/openseg-group/openseg.pytorch).

Great, thanks!


Camera offline

Thumbnail are working fine, but if i click for live view it shows "camera offline"
Is there a quick fix?

Having the same issue with Blink outdoor cameras

Same here, I have had this problem for some time now but, none of the fixes have worked for me. Debug logs do not appear to show any errors, so very difficult to pin down what the issue might be. The last time I had this working was on an older version, 3.7 and Homebridge was on older version as well.

Hi !
Same issue here, I was able to collect an error when bridging the plugin.
homebridge/node_modules/homebridge-blink-for-home/src/blink.js:307
        const data = await this.blink.getUrl(thumbnailUrl.replace(/\.jpg|$/, '.jpg'));
                                                          ^
TypeError: Cannot read properties of null (reading 'replace')
    at BlinkCameraHAP.getThumbnail (/volume1/homebridge/node_modules/homebridge-blink-for-home/src/blink.js:307:59)
    at BlinkCameraDelegate.handleSnapshotRequest (/volume1/homebridge/node_modules/homebridge-blink-for-home/src/homebridge/blink-camera-deligate.js:77:47)
    at /volume1/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/controller/CameraController.ts:1030:23
    at new Promise (<anonymous>)
    at CameraController.handleSnapshotRequest (/volume1/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/controller/CameraController.ts:1009:12)
    at Bridge.Accessory.handleResource (/volume1/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1936:18)
    at HAPServer.emit (node:events:513:28)
    at HAPServer.handleResource (/volume1/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:1054:12)
    at IncomingMessage.<anonymous> (/volume1/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:430:11)
    at IncomingMessage.emit (node:events:513:28)

Hello! I am having this issue as well.
Has anyone found a fix for this issue?


Temporary disk path assumes mode=slurm, fails on local mode

A number of rules in workflow/rules/somatic_snps.common.smk use a custom temporary directory based on the slurm job id set in config/config.json. This assumes users only run these jobs on slurm, not in local mode. But for testing, users may initially submit it as a slurm job, then run in local mode on an interactive node to debug any errors -- but these jobs fail in local mode with:
mktemp: failed to create directory via template ‘/lscratch/6463377/tmp.X
XXXXXXXXX’: No such file or directory

Could we use snakemake's temp() function instead of this custom temp file scheme?
https://github.com/CCBR/XAVIER/blob/37d46f700ee381d36d8be899f2c0f0d838b75d30/workflow/rules/somatic_snps.common.smk#L85-L89
And/or refrain from using bash variables in the configfile that assume you're on a particular HPC?
https://github.com/CCBR/XAVIER/blob/37d46f700ee381d36d8be899f2c0f0d838b75d30/config/config.json#L14
(this was initially added here: https://github.com/CCBR/XAVIER/blame/321adaafd64c07da80be1922b85cb062c48b3413/config/config.json#L14)

When requesting interactive node, need to request lscratch space:
sinteractive --mem=120g --time=12:00:00 --gres=lscratch:256 --cpus-per-task=8

(This doesn't solve the issue of being able to run outside of a slurm environment.)

Fix idea from @kopardev

Idea: make this if/else chunk a snakemake global variable in triple quotes, use it wherever tmpdir is needed.

More long-term fix: use resources with different tmpdir path options for biowulf, frce, or local https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#default-resources

This fix appears to work on an interactive node, but a problem arises when testing on my mac:
mkdir: /dev/shm: Operation not permitted

Is there a better default value we should use when not on slurm/biowulf? @kopardev

to test:
checkout the branch tests_iss-32, cd into tests, and run snakemake with test_tmp_disk1 as the target:
git pull
git switch tests_iss-32
cd tests/
snakemake -c 1 test_tmp_disk1


FPHS 694

Only wipe local data if logging back in w/ a different username. If relogging as the same user the Results and other data should remain so that the Progress tab is still populated.

looks good


k8s deployment

I use harbor on  k8s cluster.
But current harbor repository doesn't have  adminserver's yaml file.
I know 'k8s deployment' is now under development, but we want sample or PoC.
see #3010

Coverage increased (+0.02%) to 54.703% when pulling f9480b92b59bdf7bb71ba553ca24d345eac18443 on m-masataka:k8s-deploy into 8a1b10ad7e81e8ff738e9857a7e72c2db22038f4 on vmware:master.


Allow Roles/Privileges

endpoints need to have ROLES and Privileges associated with them. Since tokens and security are always part of the architecture and will be included at all points of the architecture (proxy, MQ, API server), they will also need to be checked at all places the Open Api is checked.
You need to provide something similar to 'I/O State that can be shared and syncronized:
        "URI": {
            "list":{
             	"METHOD":"GET",
            	"DESCRIPTION":"List Hook",
            	"ROLES":["ROLE_ADMIN","ROLE_ARCH"],
            	"BATCH":["ROLE_ADMIN","ROLE_ARCH"],
                "REQUEST": {
                    "permitAll":[]
                },
                "RESPONSE": {
                	"permitAll":["id","version","user","name","url","format","service"]
                }
            },

Operations that are security using OAuth2 can have scopes assigned to them.  This is similar to privileges, if I understand your model correctly.  Having pre-defined roles might be something that is useful for services to define but I'm not sure it is in scope of the OpenAPI spec.

It should be. At RestFest, I pointed this out as a shortcoming of the OpenAPI project and how it fails in a distributed architecture as a result because it can fall out of sync, escalate privileges, etc.
Allowing privileges to be set (even permitAll) allows for a framework for that data. Not even having a framework means their is a severe hole in OpenAPI in which data associated with endpoints is not being set.
Roles/Privileges are associated with endpoints; they are data as much as 'Get, Put, Post, Delete' or even the path (ie 'get/post'). But by not having this, you are not consolidating the I/O data that needs to be synchronized at the PROXY, MQ, API Server, etc.
Thus you are helping to create an architectural cross cutting concern.
https://developers.redhat.com/blog/2017/10/12/new-api-pattern/

Luckily there is an extension mechanism in OpenAPI that allows you to add on whatever metadata you wish in order to support your choice of framework for building distributed applications.
And you are correct that roles/privileges are data just like HTTP methods.  The difference is that roles and privileges are not standardized in the HTTP specification.  We are not in the business of creating a meta data description for a generalized distributed application framework.  We are in the business of describing HTTP APIs using the semantics described by the HTTP specification and those related to it.
You have our encouragement and support to build a better distributed computing framework and use OpenAPI and extensions to drive it.  If in the future it becomes a ubiquitous standard, as HTTP is, then we will be happy to update the core spec to follow it.

It doesn't need to be standardized. It's just data. You merely pass the roles. This is something API Blueprint and RAML are already doing and have incorporated.
For example:
"show": {
"METHOD":"GET",
"DESCRIPTION":"Show Hooks",
"ROLES":["ROLE_ADMIN","ROLE_ARCH"],
"BATCH":["ROLE_ADMIN","ROLE_ARCH"],
"REQUEST": {
"permitAll":[]
"ROLE_ADMIN":["user_id"]
},
"RESPONSE": {
"permitAll":["id","version","user","name","url","format","service"]
}
},
The above example shows upon REQUEST, 'permitAll' states users do not need to send an ID (because it will use the id from their token) but 'ROLE_ADMIN' states those with that role need to send a user_id (even if it is their own) to do this lookup.
This way this one CACHED resource can be use different ways depending on the ROLE without changing the functionality.
And this data can be shared and synchronized in all services in the architecture thus avoiding the architectural cross cutting concern and guaranteeing 100% uptime.

So, does this work for you?

openapi: 3.0.0
paths:
  /show:
    get:
      description: Show hooks
      x-roles: ["ROLE_ADMIN","ROLE_ARCH"]
      x-batch: ["ROLE_ADMIN","ROLE_ARCH"]
      x-request-permitAll: []
      x-request-ROLE_ADMIN: ["user_id"]
      responses:
        200:
          description: List of hooks
          x-permitAll: ["id","version","user","name","url","format","service"]

Perhaps you can show how this is represented in Blueprint or RAML because to be honest, I really don't understand the semantics of the example you are giving.

No. The point is to have a single file in which all data can be
SYNCHRONIZED for the endpoints. Data separate from function.
This data needs to be the same and synchronized across all services that
share the I/O (request/response). If you send via the header, you can
EASILY push bad data that doesn't synchronize with the 'central version of
truth' which in this case is the API Server (where the request/response
meet). The DATA associated with the endpoints may not sync with the data
being pushing with the headers.
You need ONE SINGLE version of truth that can be synchronized to all
services. So if OpenAPI intends to be that DATA, it needs to act like it.
Right now as is, it acts like a centralized architecture approach... not a
distributed approach. Because it cannot be synchronized, it does not secure
its endpoints... it still pushes the architectural cross cutting concern in
the original API pattern rather than trying to separate DATA from FUNCTION.
Owen Rubel
<EMAIL_ADDRESS>On Mon, Nov 13, 2017 at 9:25 AM, Darrel<EMAIL_ADDRESS>wrote:

So, does this work for you?
openapi: 3.0.0paths:
/show:
get:
description: Show hooks
x-roles: ["ROLE_ADMIN","ROLE_ARCH"]
x-batch: ["ROLE_ADMIN","ROLE_ARCH"]
x-request-permitAll: []
x-request-ROLE_ADMIN: ["user_id"]
responses:
200:
description: List of hooks
x-permitAll: ["id","version","user","name","url","format","service"]
Perhaps you can show how this is represented in Blueprint or RAML because to be honest, I really don't understand the semantics of the example you are giving.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OAI/OpenAPI-Specification/issues/1411#issuecomment-343993121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQxTIcEhRrBedguZN1Ck7ZEZfHLWmKpks5s2HumgaJpZM4Qa_Ab
.

Those are not header definitions, those are Specification Extensions as defined by the spec. @darrelmiller simply translated your example to something that can be represented with OAS3.

@webron My apologies. Thats right. I'm thinking xref and this is for frontend javascript usage.
Still, you wouldn't need a frontend specific designation since this wouldn't be checking ROLES on the frontend; frontend is final output once roles have been checked

Not really sure how we got to talk about frontend now.

@webron Also keep in mind, just as you allow for one cached resource to be requested different ways through doifferent ROLES, you will also want to return it different ways via the ROLE as well
"REQUEST": {
"permitAll":[]
"ROLE_ADMIN":["user_id"]
},
"RESPONSE": {
"permitAll":["id","version","name","url","format","service"]
"ROLE_ADMIN":["user"]
}
},
Above implies everyone gets returned ["id","version","name","url","format","service"] but only ROLE_ADMIN gets returned 'user'
This allows for ONE OBJECT/RESOURCE to be requested/returned a variety of ways and to built functionality only ONE WAY (ie grab,cache, parse object). ROLE merely tells you:

who has access
what data to expect
what data to return from cached object.

@webron The 'x-variable' specification is commonly used for passing variables in javascript is it not??? I have never seen this anywhere else.

No, it's just a way to extend a specification. It can be used by the front end, back end, nothing at all, everything. It's just extra metadata that's not directly supported by the specification. We've seen various examples of those out there.
As for what you're suggesting, that won't get in before we solve the issue of filtering fields from models in general. It also seems that you're trying to describe a very specific implementation and this is not a general solution used across by various API producers out there (unlike known authorization schemes). As @darrelmiller mentioned before, this does not make it a good candidate to be incorporated directly into the specification.

@webron Ok well I've never had to use it until Node. Python, Ruby, Java, Perl, PHP don't need this
I would have to say, you are choosing the delivery mechanism for the end user rather than just defining data; if you want the platform the remain generic, don't do that.
A generic platform leaves the options open for people to implement.

Again, no idea what you're referring to.

@webron I'm doing my best to explain, bear with me.
Above in your declaration, you are stating this has to be used as a mimetype and declared using the naming convention:
  x-roles, x-batch, x-request-permitAll, x-request-ROLE_ADMIN

Should there be overlap, they do not have options.
Should they not wish to use a mime-type, they do not have options.
Should they wish to transfer data using the default framework/language methodology, they don't have the option.
You are forcing the delivery mechanism for the data upon them.
Does that make more sense?
With the following:
"ROLES":["ROLE_ADMIN","ROLE_ARCH"],
"BATCH":["ROLE_ADMIN","ROLE_ARCH"],
"REQUEST": {
"permitAll":[]
"ROLE_ADMIN":["user_id"]
},
All thats being stated is:

these are the declared role data
this is the request data associated the the role data
this is the response data associated with the role data

There is no formatting declared like you have. I don't declare JSON, XML or a MIME-TYPE; that is functionality/formatting... not data.

@webron Its not a specific implementation. This is one that APIGee, Mulesoft, Apple, Google, AWS, and 90% of enterprises support everyday. Its the API in a distributed architecture. Most of those I just listed called me in to help with these issues and Redhat and others have asked me to write about it.
So I'm struggling the best I can to explain this and I'm at a loss for why a the synchronization of I/O state in a distributed architecture is something that is not understood since thats what this file is meant to do.
UNLESS... Swagger intends this specification simply for centralized architectures. Then it makes sense.

@webron well I guess thats the issue then. This may be a bit over your head

@orubel Thank you for making this community an unsafe place for people.
I've been amazed at how level-headed the team has been trying to work with you, and now you've opted to be just plain insulting.
I understand that it is frequently challenging to make oneself understood, I have that problem often. But the onus is on you to be understandable when proposing enhancements.

@nelz9999 excuse me? Since when is someone upvoting 'Again, no idea what you're referring to' level headed.
And please explain how I made this (in your words) "unsafe"?

Since when is someone upvoting 'Again, no idea what you're referring to' level headed. That's upvoting passive aggression.

I am the one who upvoted that (I just checked to make sure no one else had).  I did so because I am also confused and wanted to indicate that more people who are reading this thread may be confused.  I did not have anything worth saying on the actual thread so I did not say anything.  And my name is on it either way, so I am accountable whether I post a comment or not.
And in that vein, if such an upvote was against community standards or preferences, then I apologize for not considering that beforehand.  I'm leaving it there so the conversation continues to make sense, but I am also happy to remove it or address any problems in whatever way is preferred by the project.  Also, I am fine with the admins deleting this comment if they wish as it does not contribute to the primary discussion.
However, since my upvote was called out, I felt that I should explain my intent, even if it did not land as intended.

Regardless, explaining an architectural cross cutting concern is 'unsafe'.
  In an online world it is never easy to convey sentiment, therefore we must "assume the best" when interpreting every comment.
@orubel We've had this conversation before.  I am convinced you have a lot to contribute to this community, but you need to find a way to communicate your ideas in language that your target audience can grok.  I have repeatedly tried to parse what you are saying and I have failed.  That may be completely my fault, but we both lose if you cannot convey your ideas successfully.
What is not acceptable is making belittling comments such as "This may be a bit over your head".  Everyone in this community is held to a higher standard than that.
I'm going to close this issue so that this whole thread can be relegated to the past.   If you wish to start a fresh one about how you feel an authorization framework could be layered on top of OpenAPI, you are welcome to do so.  However, before you do so, could you spend a bit more time familiarizing yourself with how OpenAPI works, as your comments on the x- extensions seem to indicate that you have misunderstood what they are.

Wasn't meant as belittling. Some people do have issue with understanding
the paradigm. Others don't. This was what was meant and nothing more.
Talking about this to Netflix, AWS team and at multiple conferences, I have
seen the confusion caused by people who cannot get past the API pattern as
it was originally written for centralized architectures and binds
communication logic to business logic causing a crass cutting concern in
the architecture (a AOP principle).
If this is over your head, don't take insult. Try to understand rather than
tell the person they create an 'unsafe' environment
Truly the subject matter does go over people's heads
On Nov 13, 2017 6:01 PM, "Darrel"<EMAIL_ADDRESS>wrote:
@handrews https://github.com/handrews Your upvote of a comment declaring
a failure to understand is perfectly acceptable response in my opinion. In
an online world it is never easy to convey sentiment, therefore we must
"assume the best" when interpreting every comment.
@orubel https://github.com/orubel We've had this conversation before. I
am convinced you have a lot to contribute to this community, but you need
to find a way to communicate your ideas in language that your target
audience can grok. I have repeatedly tried to parse what you are saying and
I have failed. That may be completely my fault, but we both lose if you
cannot convey your ideas successfully.
What is not acceptable is making belittling comments such as "This may be a
bit over your head". Everyone in this community is held to a higher
standard than that.
I'm going to close this issue so that this whole thread can be relegated to
the past. If you wish to start a fresh one about how you feel an
authorization framework could be layered on top of OpenAPI, you are welcome
to do so. However, before you do so, could you spend a bit more time
familiarizing yourself with how OpenAPI works, as your comments on the x-
extensions seem to indicate that you have misunderstood what they are.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OAI/OpenAPI-Specification/issues/1411#issuecomment-344121406,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQxTI2ZdOQuuHUGptqhSUhvnQpiLGGSks5s2PRegaJpZM4Qa_Ab
.

I stepped away from the computer for a while, and got back to this.
@handrews while may seem biased, there's nothing wrong with your upvote nor your comment. I do wish you didn't have to write the comment, but completely understand why you felt the need to do so.
There's something to be said about code of conduct and how people treat each other in a community. In fact, we're working on formalizing and adding a code of conduct to this projects to set some basic expectations.
As a community, we all make mistakes, some more severe than others. I'd be the first to admit of making such mistakes and will probably make them again.
@orubel - you were jumping to conclusions with regard to what was suggested to you. You assumed you understand what we're talking about, and went to completely wrong directions. So yes, when we're talking about the ability to declare model field filtering inside the spec, and you jump to talk about specific development languages (even though the spec is language-agnostic), you should expect people to not follow. My question wasn't passive-aggressive. Given that you repeatedly jumped between things, I thought it was pretty clear that it's difficult to follow.
You obviously also didn't take time to read the spec and see what it offers. This is based on your suggestions and reactions to our suggestions. Now, you can claim that we didn't take the time to read the ideas you provided in the link that you provided. You'd be right, except it is you who are trying to introduce something new to this spec, and not the other way around. As such, if you bring up an idea, which we very much appreciate, it is on you to explain it. Sure, I'd go and read the link at some point, but maybe I don't have time to do that right now (and I don't). You want to continue the discussion? That's fine. Take the time to make sure your message is clear.
You are not doing us a favor by suggesting new features. If you want to help the community, then do it. Our (the TSC's) job is to go through feature suggestions, read feedback from users, try to make proposals ourselves and decide whether it fits and makes sense to put into the spec based on some criteria. It is not our job to be experts in all-things-API.
Now, as much as I'd rather we all be nice, I don't see that as a requirement. I don't mind when people provide terse responses that may seem rude. I don't mind when people challenge my opinions/suggestions (and yes, I've been wrong numerous times). However, there are lines that should not be crossed. and you crossed it. I'm sorry if you don't see, but it's obvious that others on this thread did. This is not because your comment was directed at me (because, let's face it, you don't even know me to be able to make such a comment). I would have closed the ticket just like @darrelmiller did, if it were directed to anyone else.
I had a hard time deciding whether to write this at all or let it go. However, I believe there's room to take a clear stance on these things. All of us who work here, whether the TSC or the community itself, do so voluntarily and there's absolutely no reason to accept such interactions.
I'm going to do something I generally avoid doing, and lock this thread. I do encourage people to think about these things, and fully accept not everyone is going to agree with what was said, by either side. However, further active discussion here may lead to more toxicity which should be avoided.
If anyone wants to bring up the same issue at the original post and have a productive discussion, please file a new ticket and we can start over.


⚠ Processors has degraded performance

In c611973, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 76 ms

Resolved: Processors performance has improved in 850537c.


[Feature] Implementation of Docker Containerization for the Application

Description:
Proposal:  Docker Containerization Implementation
Objective:
Implement Docker containerization to streamline deployment, enhance scalability, and improve portability across different environments.
Benefits:
Streamlined Deployment: Consistent deployment across platforms reduces issues.
Improved Portability: Facilitates migration between environments.
Simplified Maintenance: Easier management and updates without system impact.

I want to work on this!! Please assign this to me! Please add GSSoC'24 label in this issue.

I'd love to take on this task! Could you please assign this issue to me? Additionally, I kindly request adding the "GSSoC'24" label to this issue.
I have extensive experience in creating projects similar to this in the past. You can check out my GitHub profile (https://github.com/prajna321) here as proof of my experience.
Looking forward to contribute!

Hey @Sarthak027, once we done with some feature then we can add docker file

Hey @Sarthak027, how do you planning to implement this, could you explain your approach like it would be single docker file or multiple, etc. ?

Hey @abhijeetnishal ,
Thank you for your question! Here’s a detailed plan for implementing Docker containerization for the URL Shortener App:
Approach:

Frontend Container: A Dockerfile for the  frontend.

Backend Container: A Dockerfile for the  backend.

MongoDB Container

A "docker-compose.yml" file in the root directory for defining services for the frontend,backend and Monodb, setting up networking to allow communication between containers.
Benefits:

Streamlined Deployment: One command to build and start all services.

Improved Portability: Consistent environment setup across different systems.

Also can you please update level 2 for this feature.

Hey @Sarthak027, the approach is right. But docker related issues will be level1, level2 issues will be major code changes.

Hey @abhijeetnishal ,Got it! I'm working on it and will raise a PR soon.

Great @Sarthak027, also update the readme, how to run application using docker.

Hi, I would like to take up this issue! I have experience working with Docker and containerizing applications. I can create a Dockerfile to build the application and a docker-compose.yml to manage multi-container setups if needed. Could you please assign this issue to me?


Merge develop into master with sections A and B of the curators handbook almost complete.

Oops, created the pull request the wrong way round.


DO NOT MERGE! Fast Forward stable to 652be10fe0a6e001bf19993e4830365cf8018963.

This PR will be merged automatically once checks are successful.

This change is

Jenkins job mixer/postsubmit passed


[Doc] add tutorials for level 3 and 4

Summary
Please take a look at http://<IP_ADDRESS>:7041/build/html/docs/level-up/basic_skills/03_dataset_import_export.html
and http://<IP_ADDRESS>:7041/build/html/docs/level-up/basic_skills/04_detect_data_format.html#level-4-detect-data-format-from-an-unknown-dataset for references.

How to test

Checklist

[ ] I have added unit tests to cover my changes.
[ ] I have added integration tests to cover my changes.
[ ] I have added the description of my changes into CHANGELOG.
[ ] I have updated the documentation accordingly

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below).

# Copyright (C) 2023 Intel Corporation
#
# SPDX-License-Identifier: MIT

Codecov Report
Patch coverage has no change and project coverage change: -0.02 :warning:

Comparison is base (89b2111) 78.87% compared to head (fba2adf) 78.85%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #920      +/-   ##
===========================================
- Coverage    78.87%   78.85%   -0.02%
===========================================
  Files          210      215       +5
  Lines        25145    25202      +57
  Branches      5036     5043       +7
===========================================
+ Hits         19832    19874      +42
- Misses        4178     4192      +14
- Partials      1135     1136       +1

Flag
Coverage Δ

macos-11_Python-3.8
?

ubuntu-20.04_Python-3.8
78.85% <ø> (-0.01%)
:arrow_down:

windows-2019_Python-3.8
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 49 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Layout isn't adapted after orientation change 0.31 -> 0.32

Issue Description
Layout isn't adapted after orientation change
Steps to Reproduce / Code Snippets

react-native init TestOrientation
change device orientation

View.onLayout isn't called either.
Same behaviour on device using release build.
Issue not present in 0.31
Expected Results
Orientation change should adapt the layout automatically
Additional Information

React Native version: 0.32
Platform(s): iOS only
Operating System (macOS, Linux, or Windows?): macOS

commit https://github.com/facebook/react-native/commit/f35b372883a76b5666b016131d59268b42f3c40d#diff-cadfa6950646cbf0bfb278da8607a1fb
does resolve the issue :)


Indices of mk_*_arena can be used in other arenas

//! ```compile_fail
//!# use compact_arena::mk_nano_arena;
//! mk_nano_arena!(a);
//! mk_nano_arena!(b);
//! let i = a.add(1usize);
//! let j = b.add(1usize);
//! let _ = b[i];
//! ```

---- src/lib.rs -  (line 43) stdout ----
thread 'src/lib.rs -  (line 43)' panicked at 'test compiled while it wasn't supposed to', src/librustdoc/test.rs:300:13
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

Continuation of https://github.com/llogiq/compact_arena/pull/17#issuecomment-487170121
cc @RalfJung

The problem is that this compiles:
use std::marker::PhantomData;

#[derive(Copy, Clone)]
struct Inv<'a>(PhantomData<fn(&'a ()) -> &'a ()>);

impl<'a> Inv<'a> {
    fn new(_: &'a mut ()) -> Inv<'a> {
        Inv(PhantomData)
    }

    fn check(self, _other: Inv<'a>) {}
}

pub fn main() {
    let mut tag1 = ();
    let i1 = Inv::new(&mut tag1);
    let mut tag2 = ();
    let i2 = Inv::new(&mut tag2);
    i1.check(i2);
}

This means that the two borrows created for the two tags somehow have the same lifetime. I am not sure if there is a way to prevent the borrow checker from doing that.

Perhaps if tag2 gets its own scope (like with the in_arena! macro?

No, that doesn't work either. It seems both the crate barrier and unsafe code are necessary to keep the lifetime checker from unifying the lifetimes. This may be an interesting case for the unsafe code WG?

I don't think crate barrier makes a difference, but function barrier will. That's why the closure-based approach works.
Cc @matthewjasper

Then again that's what the indexing crate does and the limitation with recursive functions led me to adopt the scheme we have in compact_arena now.

What is puzzling to me is that we didn't get the same result in our initial tests. Perhaps some change between 1.33 and 1.34?

What is puzzling to me is that we didn't get the same result in our initial tests. Perhaps some change between 1.33 and 1.34?

I don't think we tried this particular "exploit". Are you collecting these counterexamples as a test suite somewhere?^^

the limitation with recursive functions led me to adopt the scheme we have in compact_arena now.

That's basically hoping that it is possible to have a sound implementation without closure. I think that's far from clear at this point.

Something like this could work:
use std::marker::PhantomData;

#[derive(Copy, Clone)]
struct I<'a>(PhantomData<fn(&'a()) -> &'a ()>);
struct D<'a>(&'a I<'a>);
impl Drop for D<'_> {
    fn drop(&mut self) {}
}

// Using `I` as the return type to save me from writing another struct
fn new<'a>(tag: I<'a>) -> I<'a> { I(PhantomData) }

macro_rules! mk_unique_lt {
    ($a:ident) => {
        let tag = I(PhantomData);
        let tag_lb;
        let $a = new(tag);
        if false { // Allow the drop to be optimized away in MIR
            tag_lb = D(&tag);
        }
    };
}

fn dont_error_in_general() {
    mk_unique_lt!(a);
    mk_unique_lt!(b);
    std::mem::swap(&mut {a}, &mut {a});
    std::mem::swap(&mut {b}, &mut {b}); // OK
}

fn are_unique() {
    mk_unique_lt!(a);
    mk_unique_lt!(b);
    std::mem::swap(&mut {a}, &mut {b}); // ERROR
}

@matthewjasper Thank you! That basically boils down to my solution for all but the non-uninit Tiny- and NanoArenas, because the latter did not impl Drop. I'm currently writing some compile tests and will try to introduce a drop and see if we can get the cases to fail for the right reasons.

I guess we can close this now that compiletests show that it works. If you don't think so, please reopen.

See #22 (didn't see this issue originally): NLL lets the lifetimes unify.

I just pushed https://github.com/CAD97/generativity which I believe uses @matthewjasper 's trick to allow for closure-less unique lifetimes.
I know for sure that the closure generativity works, and rustc isn't going to introduce some full-program lifetime analysis to "fix" it. I'm unsure whether the impl Drop(&'id Invariant<'id>) is enough to guarantee resilience against future lifetime checker improvements, however.

Wait, I thought this crate had implemented @matthewjasper's trick and that's what closed this issue...?

It seems all that was changed was tests and comments.

I have reasoned myself that the @matthewjasper technique used in CAD97/generativity is sound over in https://github.com/CAD97/generativity/issues/1. I'm going to publish generativity such that crates that want unique lifetimes (such as this one or indexing[-str]) can use it. I just need to get CI set up and automatically testing on nightly often so we'll know when something breaks.


importing the json loader causes execution to fail silently!

I think this is a bug but may be I am wrong?? If I do something like:
import 'json'

the page loading (systemjs loading import file) stops somewhere in between and there is no error message. I once waited really long to get a timeout but have not been able to reproduce this. I don't know what other helpful information I can provide...
I already import css and html like this without problems. The reason I am doing this is that I want to keep some json files outside the bundle which the user can configure by hand before loading the page (I am using nwjs, so the user has access to the files).
JSPM 0.16.53

Odd, SystemJS 0.19 did have some unfixed race conditions in the pipeline, so this may somehow be triggering one of those. Unfortunately I'm no longer personally maintaining SystemJS 0.19, so while I know it's highly inadequate, I'd suggest trying to find a loading order that can work for you here.

:(, But Thanks for letting me know!!!!!!!! At least I know that I am not making a mistake.
I have found a way around it by loading a dummy json for now but it is not a good solution in the long run.
I am reluctant to upgrade to jspm 0.17 immediately (maybe in a next few months or perhaps when you can reach a RC), as I otherwise functional code which I am reluctant to disturb it.
One request that I have (which is much to ask when one is already getting a free lunch) is that if you can please provide good documentation on best way to deal with breaking-changes when you do come to the RC. For example, it is unclear (at least to me) if there are different strategies to deal with depreciated path wildcards other than explicit listing or how to map paths and deal with overrides in multi-repo setups in 0.17/0.20.


Deflaked test of semaphore concurrency

Multiple acquisition was the result of 1 command finishing before the last had been invoked.  Increasing the time spent in the command should eliminate this condition

NetflixOSS » Hystrix » Hystrix-pull-requests #392 SUCCESS
This pull request looks good


Add support to display git branch

I'd like to keep this simple (as in it doesn't have to be done via a plugin) but i want ot be able to show the git branch in dirs/folders that have a .git folder in it

https://github.com/Xmetalfanx/zshSetup/commit/8f8c0382a61625b1337eece22a0d2a7a2c02bd97
i may have adjusted the way it shows theme wise but this commit has the intial code that helps displays the branch


Change the type of block sizes to np.int32

They don't need to be that big
Breaks cgen on 32 bit machines

This is expected to fix #213

Pretty sure this is gonna break Julia. I'll have to check.

For the future maybe we want tests to make sure we don't break the Julia interface by mistake.

Merging after verbal sign-off


Radar bugs: grenades stays on map forever, wrong trajectory for flash

Issues:

smokes stays on radar forever (not always)
molotovs stays on radar forever (looks like all molotovs)
flashes thrown from empty map location (not always)

My observations:
The radar "breaks" as soon as there are more than one grenade from the same type on the map.
For example if two molotovs used almost simultaneously, the molotovs will remain on the map.
These images way after roundEnd and even after a new round started:

Errors I see in the console:
Warning: Encountered two children with the same key, `[object Object]_859_low`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
    at div
    at Radar (http://localhost:1349/dev/src/HUD/Radar/LexoRadar/LexoRadar.tsx:197:3)
    at div
    at LexoRadarContainer (http://localhost:1349/dev/src/HUD/Radar/LexoRadar/LexoRadarContainer.tsx:51:3)
    at Radar (http://localhost:1349/dev/src/HUD/Radar/Radar.tsx:19:3)
    at div
    at RadarMaps (http://localhost:1349/dev/src/HUD/Radar/RadarMaps.tsx:23:3)
    at div
    at Layout (http://localhost:1349/dev/src/HUD/Layout/Layout.tsx:37:3)
    at SettingsProvider (http://localhost:1349/dev/src/API/contexts/actions.tsx:61:3)
    at App (http://localhost:1349/dev/src/App.tsx:28:27)

Warning: Each child in a list should have a unique "key" prop. See https://reactjs.org/link/warning-keys for more information.
    at Bomb (http://localhost:1349/dev/src/HUD/Radar/LexoRadar/LexoRadar.tsx:86:3)
    at div
    at Radar (http://localhost:1349/dev/src/HUD/Radar/LexoRadar/LexoRadar.tsx:197:3)
    at div
    at LexoRadarContainer (http://localhost:1349/dev/src/HUD/Radar/LexoRadar/LexoRadarContainer.tsx:51:3)
    at Radar (http://localhost:1349/dev/src/HUD/Radar/Radar.tsx:19:3)
    at div
    at RadarMaps (http://localhost:1349/dev/src/HUD/Radar/RadarMaps.tsx:23:3)
    at div
    at Layout (http://localhost:1349/dev/src/HUD/Layout/Layout.tsx:37:3)
    at SettingsProvider (http://localhost:1349/dev/src/API/contexts/actions.tsx:61:3)
    at App (http://localhost:1349/dev/src/App.tsx:28:27)

CS2 HUD version: 1.0.2
HUD Manager version: 4.8.2

any fixes?

Added a new pull request with a fix

@borzaka Cant reproduce that issue, can you send over the demo that it happens on?

Fixed with https://github.com/lexogrine/cs2-react-hud/commit/d9ecd182739a7a9893edecd9e790b2c5a39bb85e


Product data changes not geting properly synced to Sanity if there's another product with same slug

In scenario where there's two products with an identical slug field present in Sanity Studio, changing product data in Shopify doesn't update (any of) the auto-synced product data in Sanity. This seems strange because the update API takes into consideration product's id, which is of course different.  At the same time, the functions log in Vercel shows successfully sync message every time.
If there's a new brand new product added (that doesn't have a duplicate) sync works as expected, which suggests the issue is specifically related to there being a duplicate slug field:

The yellow-marked part is a console-log is from product-update.js, checking the "URL Handle" Shopify field :

api/shopify/product-update.js (line 78)

console.log(handle, '**** Current handle ****')

The handle that's printed is in fact the correct, newly edited URL Handle from Shopify. However, it doesn't get reflected in Sanity:

I than tried making some changes the API to force a change for the slug field, in :
// api/shopify/product-update.js

 const slugField = {
    slug: {
      current: handle,
    }
  }

  // patch (update) slug, missing or not
  stx = stx.patch(`product-${id}`, (patch) => patch.set(slugField))

// Add to productCompare set:
  const productCompare = {
    ...product,
    ...productFields,
    ...slugField,
    ......
  }

That didn't work so I tried to unset the field:

 // unset slug field

 const slugField = ["slug"];
 stx = stx.patch(`product-${id}`, (patch) => patch.unset(slugField))

which didn't work either.
As to why there are products with duplicate slug values, it's a result of switching to different Shopify store which had cloned all product data from previous store, so now there's duplicate products with duplicate slugs, neither of which can be deleted, and the new products can't be published either because of the duplicate slug validation error.

I've managed to "remove" the duplicate product by adding this to product-delete.js API:
  stx = stx.patch(product-${idNew}, (patch) => patch.set({ wasDeleted: true }))
The product is now marked as "removed" in Sanity but the document is still there, and still giving the same "slug in use" warning:

Because of this slug conflict error the client still can't publish the proper product.

Hey there @ansmlc by default Sanity checks for uniqueness on slug fields for documents.
This is why it's not updating anything in Sanity when the sync function occurs. You can actually see the error message after the sync starts in your first screenshot:

You'll need to either delete the previous documents (and remove all references to those elsewhere first), or you can try overriding the default validation for the product slug fields in your schema to allow it to create product documents with the same slug values.
Let me know if that helps! 🤘

is there any way to check the localhost sanity error log? mine is not syncing

@Raqibnur please open a separate issue with more details about what you are experiencing, instead of commenting on other people's issues that are still open 🤘

@ndimatteo This has been resolved by rolling back to an older dataset backup and avoiding having same-slug documents.


IMPRO-1403: Update usage of convert_distance_into_number_of_grid_cells

Name change
The name change is in the second to last commit so easily undoable
renamed convert_distance_into_number_of_grid_cells to distance_to_number_of_grid_cells
distance_to_number_of_grid_cells

Moved the checking of the size of the radius against the distance into its own function.

part of "circular_kernal.py"
called check_radius_against_distance

Simplified the error checking
Renamed int_grid_cells to return_int for clarity
Moved axis to the end of the function arguments
max_distance_in_grid_cells=MAX_DISTANCE_IN_GRID_CELLS is first kwarg and called positionally where needed with the obvious constant name

Elsewhere

Circular Kernel

Renamed fullranges to full_ranges to conform to python snake case standards
No longer takes a tuple of "x" and "y" as they were always the same.
calculate area the use later in the function.

Square Kernal

_pad_and_calculate_neighbourhood now takes a number of grid cells

x and y were always the same

_remove_padding_and_mask now takes a number of grid cells

x and y were always the same

Renamed minimum_value to min_value

only ever used one
function call no longer running onto other lines
still just as clear

Spatial

Renamed variable xdiff  to x_diff to conform to python snake case standards
Renamed variable SpatialWeightsPlugin plugin to conform to variable standards
Refactor process to iterate for x and y` rather than duplicated lines

Typos
Importing only required function from librarys

Test Changes

Changed fro mtuple to int eg. (1, 1) to 1 when axis length requred as int rather than tuple
grid_cells_x = grid_cells_y = 1 to grid_cells = 1
Moved test_single_point_range_0 from test_GeneratePercentiles.... to convert_distance_into_number_of_grid_cells
Moved test_error_range_greater_than_domain_size from distance_to_number_of_grid_cells  to new check_radius_against_distance tests

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

Clones removed
==============
+ improver_tests/wind_calculations/wind_direction/test_WindDirection.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

Clones removed
==============
+ improver_tests/wind_calculations/wind_direction/test_WindDirection.py  -2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/nbhood/circular_kernel/test_check_radius_against_distance.py  2

Complexity decreasing per file
==============================
+ improver/utilities/spatial.py  -2

Clones removed
==============
+ improver_tests/wind_calculations/wind_direction/test_WindDirection.py  -2

See the complete overview on Codacy


Enhance : Ui of the testimonial section.

Is your feature request related to a problem? Please describe.
i would like to change the ui of the testimonial section .

Describe the solution you'd like.
I would like to change  testimonial sections by improving their cards ui.
Describe alternatives you've considered.
I also want to add some hover effects on the cards of the testimonial section.
Add any other context or screenshots about the feature request here.
No response

Sure @Pragati-3003

please assign me this issue


New devices

Hello:
I wonder if I have other models that I have already configured the commands, could you add them to your configurations?

You can create a new codeset .json file and for your AC and create a pull request for it. Light is not supported yet 😩

For the air command, could you tell me which of the definitions that have already been made I could base myself on?

For the lights, could you guide me?


New logo for BookLibrary

I wanted to contribute to BookLibrary. I designed a logo for it. If you like it, I'll send you files and pr.
is there anything you want ?

Thank you. I sent pr. Please check.
https://github.com/hufan-akari/BookLibrary/pull/4

Here are all the files.
https://drive.google.com/drive/folders/1mnTI_GYMDTiSGovzFM3C2BNnmMStQlXI
If you have a problem, you can contact me.


Workshop 5 results change when recomputed

Results in the workshop 5 solution were not matching the results we get when working through the workshop now. When pulling up the solution, this is what the results are initially:

When you compute the scenarios again, you get this (which matches what we get when we work through now):

I'm assuming this is just due to changes in the way the model does the computations.

@BrittCorley I would expect that if the results changed a little like they did here, that results would change a little across all of the workshops. Did the results in all workshops change?
I would also expect that without-project condition EAD in Workshop 5 matches without-project condition EAD in Workshop 4. Does without-project condition EAD match between Workshop 4 and Workshop 5?


Question: Will this package support OpenSearch or Elasticsearch or both?

For those that are unaware, there's been a bit of 'contention' around Elasticsearch's license lately which has lead to Amazon creating a fork of Elasticsearch 7.10 called OpenSearch:
https://aws.amazon.com/blogs/opensource/introducing-opensearch/
Given the code paths may diverge at some point, is the intention of this package to support Elasticsearch, OpenSearch, or both? Or will we cross that bridge when we come to it?
This is a great library that I've been using personally for a number of years without any issues whatsoever. Looking for a productive discussion about the future direction of this code. Please do let me know if there is a better venue for such a discussion, I am not trying to start a holy war.
Thanks :)

Hi Dylan! I replied to a similar question here. Maybe that already answers your question?

... My personal view on this is that this library should benefit the community. To best serve the community, my goals for this library are 1) to be stable, 2) to limit the amount of breaking changes during minor versions, and 3) work on as many Elasticsearch versions and distros as possible.
My take on the future of this library is written down in #1240. I'd like to apologize for currently not being very active in working on this library. Day-time work related issues are more important to me right now. I see quite a number of very useful contributions in the form of PRs, but on the other hand I've not seen too many things that actively prevent people from using the library. Having said that, I really hope to pour in some days and work on the queue of PRs and issues that's already there, and even add some more stuff that I have on my list.


Unclear statement in "How Local Cache changes the behavior of App Service"

In "How Local Cache changes the behavior of App Service" there's a statement:
"D:\Home points to the local cache." but across the doc ("How Local Cache changes the behavior of App Service", "Change the size setting in Local Cache" and "How can I tell if Local Cache applies to my web app?") it's said that "the local cache is a copy of the /site and /siteextensions folders of the web app".
So it's not totally clear whether the whole D:\Home is cached or D:\home\site and D:\home\siteextensions.

Could you please correct that to be more precise?
If it's D:\home\site and D:\home\siteextensions only cached - can we still use D:\home\MySpecialFolder for read/write relying on the fact that this MySpecialFolder is on Azure Storage and shared between the instances?

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

ID: 3875bb58-b3bb-d12c-9e8f-6a60ac7fb49b
Version Independent ID: 9bb25e56-90de-4a2f-389d-40e983a1e5c1
Content: Azure App Service Local Cache overview
Content Source: articles/app-service/app-service-local-cache-overview.md
Service: app-service
GitHub Login: @SyntaxC4
Microsoft Alias: cfowler

@yar-shukan Thank you for the valuable feedback,we are investigating the issue.

@yar-shukan Thank you for your feedback. We can definitely address this feedback. I will work with the product team to make sure we also have the most up-to-date data. Tracking this enhancement internally 1221205

@yar-shukan We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[https://r.myadx.net/img/22/C507F8.png][https://r.myadx.net/img/06/AEBF82.png][https://r.myadx.net/img/1D/334E9E.png][https://r.myadx.net/img/99/72DA6A.png]😜❤💕💗😵😆😰😇😊✌😱👏😈👿💩💝💌😝😘😨😭Mr.Sirichai Lordsin
ส่งจาก myMail สำหรับ iOS
วันอังคารที่ 4 กันยายน 2018 0 นาฬิกา 28 นาที +0700 จาก kobulloc-MSFT<EMAIL_ADDRESS>Closed #6423https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F6423&data=02|01||f6b6d7ffa3a84a8ff40808d611c2a6ef|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636715925044659640&sdata=qdt8OyYQj3YdKqgWFRY5Kac%2FfQ3HAP9IAr4zTkmQQJs%3D&reserved=0.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F6423%23event-1823885968&data=02|01||f6b6d7ffa3a84a8ff40808d611c2a6ef|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636715925044659640&sdata=V7M%2B3gRxVvhdTZ1nBu34OrYsz5ucvMx5F10hFXA%2BY4o%3D&reserved=0, or mute the threadhttps://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAgUakjV2hziEjxa43E60YdeAYacUHOSLks5uXWa3gaJpZM4S_EOy&data=02|01||f6b6d7ffa3a84a8ff40808d611c2a6ef|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636715925044659640&sdata=P0U2kmWJWNwaB6QLkvpu4LQoLlzcDcM3wXHwsEl0%2Ff4%3D&reserved=0.


Theme switching requires reload of profile

When switching themes using the configuration utility, expected behaviour is for the theme to switch immediately.
However, relaunch of desktop, or re-selection of user profile, is required to trigger the application of the new theme.

Minor bug, fixed in 2d801cb.
Resolution: After clicking the "Save" button in the Theme Selector window, a call was made to save the setting to the current user profile, but no call was made to load the theme into memory. Added this call, tested.


Refactor TypeInfo + Use TypeInfo Visitor for Ext Type Resolution

Things that were refactored:

TypeInfo's name and type property weren't being used correctly. Now type will always be set, and name may not be set if for example you're defining a new ObjectDefinition (ex: type CustomType { ... }).
Type names no longer contain the required modifier within them. Previously, an optional type was prefixed with a "?" within the type name. This ended up creating more problems than it solved. Instead we will only use the required property on TypeDefinitions.
The Schema Composer's resolve logic has been refactored to use the TypeInfo visitor / transformer.

Additional changes:

Added support for "Boolean" GraphQL type.
Removed unnecessary GraphQL Schema parsing within WasmWeb3Api invoke function.

Hey @mpetrun5, it should be unblocked. I'll do a little investigation to make sure this is possible in another branch. Will DM you.

Hey @mpetrun5, it should be unblocked. I'll do a little investigation to make sure this is possible in another branch. Will DM you.

I ended up not having to expand upon the @imports & @imported directives, which I think is for the best.

I ended up not having to expand upon the @imports & @imported directives, which I think is for the best.


enhancement: serialization / deserialization

enhancement
serialization / deserialization of the tree

some research on an approach:
https://github.com/QwertyManiac/cassandra-cdh4/blob/master/src/java/org/apache/cassandra/utils/IntervalTree.java


[TACHYON-640] Detect error response correctly in tcp remote reader

https://tachyon.atlassian.net/browse/TACHYON-640
Use the correct status condition for the rpc response.

+1 LGTM

+1 LGTM, thanks for the fix!

+1 LGTM, great catch and fix, aws online tests are running smoothly now!


Insert buffer converters for TypedImperativeAggregate

Current PR addresses the last task of #2916, supporting the aggregation buffer conversion between CPU and GPU format for TypedImperativeAggregate functions. With the ability to insert buffer converters, we can handle TypedImperativeAggregate functions running across CPU and CPU in runtime. It indicates that we don't need to fallback the entire Aggregate stack to CPU once one stage need to fallback when the Aggregate contains TypedImperativeAggregate functions.
The general idea is to create buffer converters and bind them to certain physical plans during preColumnarTransitions. And integrate these buffer converters into RowToColumnar/ColumnarToRow transitions as pre-processing/post-processing projections during postColumnarTransitions. And this idea works even when AQE is on. To adapt AQE, we leverage TreeNodeTag to cache temporary information, including: buffer converters, and some meta data.
For better understanding, let's walk through the entire procedure of inserting buffer converters:

binding buffer converters to certain plans (preColumnarTransitions)
1.1 collecting all stages of Aggregation which contains TypedImperativeAggregate functions
The binding procedure is triggered in GpuTypedImperativeSupportedAggregateExecMeta.tagPlanForGpu if wrapped plan
is the final stage. At first, we collect all stages as what we do for associated fallback.
1.2 filtering stages who need buffer converters to fill the data gap with their child
1.3 creating buffer converters with filtered stages
We add two new interfaces on GpuTypedImperativeSupportedAggregateExecMeta: createCpuToGpuBufferConverter and createGpuToCpuBufferConverter.
1.4 binding buffer converters into certain plans
The plans who carry the buffer converters are the CPU plans (can not be replaced) located right before/after the potential R2C/C2R transitions.
materializing RowToColumnar/ColumnarToRow transitions with buffer converters (postColumnarTransitions)
We add extra field preTransitions/postTransitions to GpuRowToColumnar/GpuColumnarToRow, in order to insert projections like buffer converters for TypedImperativeAggregate.

build

it looks like this is missing the databricks shim updates for GpuColumnarToRowTransitionExec. If you are touching all the shims please think about the databricks ones as well.

I'll put up pr to fix

Sorry it looks like this may have just been in my branch with various build changes, apologize


Avoid disposing already disposed cancellation token source

Fixes https://github.com/Azure/azure-sdk-for-net/issues/30553

/azp run net - servicebus - tests

API change check
API changes are not detected in this pull request.


remove old files, move airflow scripts

remove old files that are not needed anymore
move airflow scripts up to /release which is the correct place for it

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

Needs approval from an approver in each of these files:

release/OWNERS [rkpagadala]

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

/test e2e-mixer-no_auth

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

Needs approval from an approver in each of these files:

release/OWNERS [rkpagadala,yutongz]

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

@rkpagadala: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


add noTLSVerify for cloudflared self-signed cert by let-encrypt

getting this error message
ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: failed to verify certificate: x509: certificate signed by unknown authority" connIndex=0 event=1 ingressRule=1 originService=https://ingress-nginx-external-controller.network.svc.cluster.local/

solution:
change bootstrap_cloudflare.acme.production to true in config.yaml, suggested by https://github.com/onedr0p/cluster-template?tab=readme-ov-file#-certificates


Uncaught SyntaxError: Unexpected token <

this error is caused by having script tags in index.html for 3rd party libraries and rewrites first introduced by  https://github.com/mgechev/angular2-seed/pull/1330.
error is gone after changing back to:
middleware: [require('connect-history-api-fallback')({ index: ${this.APP_BASE}index.html })]

What is the URL of the script tag?

http://localhost:5555/lib/abcjs_editor_2.3-min.js

Yes, you'll have to modify browser-sync's configuration:
In tools/config/project.config.ts, you should:
// ...
constructor() {
    PLUGIN_CONFIGS['browser-sync'] = {
      middleware: [require('connect-history-api-fallback')({
        index: `${this.APP_BASE}index.html`,
        rewrites: [
          {
            from: /^\/lib/.*$/,
            to: (context:any) => context.parsedUrl.pathname
          },
          {
            from: new RegExp(`^${this.NPM_BASE}.*$`),
            to: (context:any) => context.parsedUrl.pathname
          },
          {
            from: new RegExp(`^\/${this.BOOTSTRAP_DIR}\/.*$`),
            to: (context:any) => context.parsedUrl.pathname
          },
          {
            from: new RegExp(`^${this.APP_BASE}${this.APP_SRC}\/.*$`),
            to: (context:any) => context.parsedUrl.pathname
          },
          {
            from: new RegExp(`^${this.ASSETS_SRC.replace(this.APP_SRC, '')}\/.*$`),
            to: (context:any) => context.parsedUrl.pathname
          },
          {
            from: new RegExp(`^${this.CSS_DEST.replace(this.APP_DEST, '')}\/.*$`),
            to: (context:any) => `/${slash(join(this.APP_DEST, context.parsedUrl.pathname))}`
          }
        ],
        disableDotRule: true
      })],
      port: this.PORT,
      startPath: this.APP_BASE,
      open: argv['b'] ? false : true,
      injectChanges: false,
      server: {
        baseDir: `${this.DIST_DIR}/empty/`,
        routes: {
          [`${this.APP_BASE}${this.APP_SRC}`]: this.APP_SRC,
          [`${this.APP_BASE}${this.APP_DEST}`]: this.APP_DEST,
          [`${this.APP_BASE}node_modules`]: 'node_modules',
          [`${this.APP_BASE.replace(/\/$/, '')}`]: this.APP_DEST
        }
      }
    }
}
// ...

Keeping the rewrites is the only way to force BrowserSync to work with non-hash paths which contain ".".


IMS Operator failed in VSI environment

`TASK [ims_common : Issue /DIS ACT command] *************************************
task path: /opt/ansible/playbooks/roles/ims_common/tasks/main.yml:74
{"level":"info","ts":"2023-11-03T15:35:21Z","logger":"logging_event_handler","msg":"[playbook task start]","name":"example-tmdb","namespace":"ibm-zmodstack-cloudbroker","gvk":"suboperator.zoscb.ibm.com/v1minor2patch0, Kind=TMDB","event_type":"playbook_on_task_start","job":"3984381870911430584","EventData.Name":"ims_common : Issue /DIS ACT command"}
{"level":"info","ts":"2023-11-03T15:35:22Z","logger":"proxy","msg":"Read object from cache","resource":{"IsResourceRequest":true,"Path":"/apis/suboperator.zoscb.ibm.com/v1minor2patch0/namespaces/ibm-zmodstack-cloudbroker/tmdbs/example-tmdb","Verb":"get","APIPrefix":"apis","APIGroup":"suboperator.zoscb.ibm.com","APIVersion":"v1minor2patch0","Namespace":"ibm-zmodstack-cloudbroker","Resource":"tmdbs","Subresource":"","Name":"example-tmdb","Parts":["tmdbs","example-tmdb"]}}
--------------------------- Ansible Task StdOut -------------------------------
TASK [Issue /DIS ACT command] ********************************
fatal: [zvsi]: FAILED! => {
"changed": false,
"ims_output": [
{
"command_return": {
"ctl.rc": "0200000C",
"ctl.rsn": "00003004",
"ims_member_messages": [
{
"Mbr_name 1 ": "IMJS",
"cmderr rc": "00000010",
"rsn": "00004000",
"styp": "DBDC",
"type": "IMS"
}
]
},
"err": "Refer to IMS return codes.",
"msg": "Non-zero return code returned.",
"spoc_api_return": {
"imsrc": "00000000X",
"reason": "00000000X"
}
}
],
"invocation": {
"module_args": {
"batch": null,
"command": "/DIS ACT",
"plex": "PLXJS",
"route": [
"IMJS"
]
}
},
"msg": ""
}
...ignoring
{"level":"error","ts":"2023-11-03T15:35:24Z","logger":"logging_event_handler","msg":"","name":"example-tmdb","namespace":"ibm-zmodstack-cloudbroker","gvk":"suboperator.zoscb.ibm.com/v1minor2patch0, Kind=TMDB","event_type":"runner_on_failed","job":"3984381870911430584","EventData.Task":"Issue /DIS ACT command","EventData.TaskArgs":"","EventData.FailedTaskPath":"/opt/ansible/playbooks/roles/ims_common/tasks/main.yml:74","error":"[playbook task failed]","stacktrace":"github.com/operator-framework/operator-sdk/internal/ansible/events.loggingEventHandler.Handle\n\t/workspace/internal/ansible/events/log_events.go:111"}
{"level":"info","ts":"2023-11-03T15:35:24Z","logger":"proxy","msg":"Read object from cache","resource":{"IsResourceRequest":true,"Path":"/apis/suboperator.zoscb.ibm.com/v1minor2patch0/namespaces/ibm-zmodstack-cloudbroker/tmdbs/example-tmdb","Verb":"get","APIPrefix":"apis","APIGroup":"suboperator.zoscb.ibm.com","APIVersion":"v1minor2patch0","Namespace":"ibm-zmodstack-cloudbroker","Resource":"tmdbs","Subresource":"","Name":"example-tmdb","Parts":["tmdbs","example-tmdb"]}}
{"level":"info","ts":"2023-11-03T15:35:25Z","logger":"logging_event_handler","msg":"[playbook task start]","name":"example-tmdb","namespace":"ibm-zmodstack-cloudbroker","gvk":"suboperator.zoscb.ibm.com/v1minor2patch0, Kind=TMDB","event_type":"playbook_on_task_start","job":"3984381870911430584","EventData.Name":"ims_common : IMS cold start"}
--------------------------- Ansible Task StdOut -------------------------------
TASK [ims_common : Issue /DIS ACT command] *************************************
task path: /opt/ansible/playbooks/roles/ims_common/tasks/main.yml:91
{"level":"info","ts":"2023-11-03T15:35:27Z","logger":"logging_event_handler","msg":"[playbook task start]","name":"example-tmdb","namespace":"ibm-zmodstack-cloudbroker","gvk":"suboperator.zoscb.ibm.com/v1minor2patch0, Kind=TMDB","event_type":"playbook_on_task_start","job":"3984381870911430584","EventData.Name":"ims_common : Issue /DIS ACT command"}
{"level":"info","ts":"2023-11-03T15:35:27Z","logger":"proxy","msg":"Read object from cache","resource":{"IsResourceRequest":true,"Path":"/apis/suboperator.zoscb.ibm.com/v1minor2patch0/namespaces/ibm-zmodstack-cloudbroker/tmdbs/example-tmdb","Verb":"get","APIPrefix":"apis","APIGroup":"suboperator.zoscb.ibm.com","APIVersion":"v1minor2patch0","Namespace":"ibm-zmodstack-cloudbroker","Resource":"tmdbs","Subresource":"","Name":"example-tmdb","Parts":["tmdbs","example-tmdb"]}}
--------------------------- Ansible Task StdOut -------------------------------
TASK [Issue /DIS ACT command] ********************************
fatal: [zvsi]: FAILED! => {
"changed": false,
"ims_output": [
{
"command_return": {
"ctl.rc": "0200000C",
"ctl.rsn": "00003008",
"ims_member_messages": [
{
"Mbr_name 1 ": "IMJS",
"cmderr rc": "00000014",
"rsn": "00005050",
"styp": "DBDC",
"type": "IMS"
}
]
},
"err": "Refer to IMS return codes.",
"msg": "Non-zero return code returned.",
"spoc_api_return": {
"imsrc": "00000000X",
"reason": "00000000X"
},
"type_1_response": [
{
"Mbr_name 1": "IMJS",
"msg_data": [
"DFS142 10:35:56 NRESTART IN PROGRESS, CANNOT PROCESS COMMAND"
]
}
]
}
],
"invocation": {
"module_args": {
"batch": null,
"command": "/DIS ACT",
"plex": "PLXJS",
"route": [
"IMJS"
]
}
},
"msg": ""
}
{"level":"error","ts":"2023-11-03T15:35:29Z","logger":"logging_event_handler","msg":"","name":"example-tmdb","namespace":"ibm-zmodstack-cloudbroker","gvk":"suboperator.zoscb.ibm.com/v1minor2patch0, Kind=TMDB","event_type":"runner_on_failed","job":"3984381870911430584","EventData.Task":"Issue /DIS ACT command","EventData.TaskArgs":"","EventData.FailedTaskPath":"/opt/ansible/playbooks/roles/ims_common/tasks/main.yml:91","error":"[playbook task failed]","stacktrace":"github.com/operator-framework/operator-sdk/internal/ansible/events.loggingEventHandler.Handle\n\t/workspace/internal/ansible/events/log_events.go:111"}
{"level":"info","ts":"2023-11-03T15:35:30Z","logger":"proxy","msg":"Read object from cache","resource":{"IsResourceRequest":true,"Path":"/apis/suboperator.zoscb.ibm.com/v1minor2patch0/namespaces/ibm-zmodstack-cloudbroker/tmdbs/example-tmdb","Verb":"get","APIPrefix":"apis","APIGroup":"suboperator.zoscb.ibm.com","APIVersion":"v1minor2patch0","Namespace":"ibm-zmodstack-cloudbroker","Resource":"tmdbs","Subresource":"","Name":"example-tmdb","Parts":["tmdbs","example-tmdb"]}}`

Fixed in the next update. The problem was the /ERE or /NRE completed quickly causing the /DIS ACT to fail because IMS is not yet fully active.


Chore/update master

Description
В мастер в uploadcare можно только через PR.
Checklist

[ ] Tests (if applicable)
[ ] Documentation (if applicable)
[ ] Changelog stub (or use conventional commit messages)

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@decffd3). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   81.83%
=========================================
  Files             ?       33
  Lines             ?     1123
  Branches          ?        0
=========================================
  Hits              ?      919
  Misses            ?      204
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update decffd3...f961008. Read the comment docs.


authoring: Saving data with correct unitplayer version

When sending data to the itemdb-application, the unitplayer version is still 7

should be working correctly now :)


Updated routing docs

Updated routing docs to show all supported types as defined within https://github.com/huge-success/sanic/blob/3685b4de85ff9c6803b789d245366684765e2551/sanic/router.py#L18
Added example code for all examples besides regex
Added examples of queries that work with that type and ones that would not
Created PR on recommendation from @ahopkins from this issue https://github.com/huge-success/sanic/issues/1606

"squash and merge"?
And thanks 👍


Sort remove operations alphabetically and numerically by path index

Relates to: https://github.com/appscode/jsonpatch/issues/1#issuecomment-375754162

This should be fixed by https://github.com/appscode/jsonpatch/pull/6 . Thanks for the bug report and pr.


Segfault when testing test.python.quantum_info.operators.channel

Information

Qiskit Terra version: master
Python version: 3.5 and 3.7
Operating system: MacOS

What is the current behavior?
When testing test.python.quantum_info.operators.channel I'm getting a Segmentation fault: 11, speficically when test.python.quantum_info.operators.channel.test_kraus.TestKraus.test_circuit_init is being executed. Notice that I have not errors when executing only that test:
$ python -q -X faulthandler -m unittest  -v test.python.quantum_info.operators.channel.test_kraus.TestKraus.test_circuit_init
test_circuit_init (test.python.quantum_info.operators.channel.test_kraus.TestKraus)
Test initialization from a circuit. ... ok

----------------------------------------------------------------------
Ran 1 test in 0.058s

OK

Steps to reproduce the problem
 python -q -X faulthandler -m unittest  discover -v test.python.quantum_info.operators.channel
....
test_circuit_init (test.python.quantum_info.operators.channel.test_kraus.TestKraus)
Test initialization from a circuit. ... Fatal Python error: Segmentation fault

Current thread 0x0000000111c5c5c0 (most recent call first):
  File "/Users/lucianobello/repos/qiskit-terra/venv/lib/python3.5/site-packages/scipy/linalg/decomp.py", line 432 in eigh
  File "/Users/lucianobello/repos/qiskit-terra/qiskit/quantum_info/operators/channel/transformations.py", line 211 in _choi_to_kraus
  File "/Users/lucianobello/repos/qiskit-terra/qiskit/quantum_info/operators/channel/transformations.py", line 81 in _to_kraus
  File "/Users/lucianobello/repos/qiskit-terra/qiskit/quantum_info/operators/channel/kraus.py", line 144 in __init__
  File "/Users/lucianobello/repos/qiskit-terra/test/python/quantum_info/operators/channel/test_kraus.py", line 64 in test_circuit_init
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/case.py", line 605 in run
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/case.py", line 653 in __call__
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/suite.py", line 122 in run
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/suite.py", line 84 in __call__
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/suite.py", line 122 in run
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/suite.py", line 84 in __call__
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/suite.py", line 122 in run
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/suite.py", line 84 in __call__
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/runner.py", line 176 in run
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/main.py", line 256 in runTests
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/main.py", line 95 in __init__
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/unittest/__main__.py", line 18 in <module>
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/runpy.py", line 85 in _run_code
  File "/Users/lucianobello/.pyenv/versions/3.5.6/lib/python3.5/runpy.py", line 193 in _run_module_as_main
Segmentation fault: 11

Suggested solutions
No idea...

I have also had this happen before.... Additionally when run with python debugging the stack it doesn't occur PYTHONMALLOC=debug python3 -m unittest discover -s test/python -v

Found the problem! (and the solution).
For future reference:
The first line in the call stack is from scipy. I noticed that requirements.txt says scipy>=1.0. However, my envs has scipy-1.3.0. Therefore, pip install scipy==1.0 did the trick.
It seems that we are not compatible (in a very ugly way) with new versions of scipy.

Could you add this to the requirements.txt?

as a comment?

What does this say? scipy.__config__.show()

13:01 $ pip show scipy
Name: scipy
Version: 1.2.0
Summary: SciPy: Scientific Library for Python
Home-page: https://www.scipy.org
Author: None
Author-email: None
License: BSD
Location: /Users/lucianobello/repos/qiskit-terra/venv3.7/lib/python3.7/site-packages
Requires: numpy
Required-by: qiskit-terra

scipy.__config__.show()
lapack_mkl_info:
  NOT AVAILABLE
openblas_lapack_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
lapack_opt_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
blas_mkl_info:
  NOT AVAILABLE
blis_info:
  NOT AVAILABLE
openblas_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
blas_opt_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]

numpy.__config__.show()
  NOT AVAILABLE
blis_info:
  NOT AVAILABLE
openblas_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
blas_opt_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
lapack_mkl_info:
  NOT AVAILABLE
openblas_lapack_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
lapack_opt_info:
    libraries = ['openblas', 'openblas']
    library_dirs = ['/usr/local/lib']
    language = c
    define_macros = [('HAVE_CBLAS', None)]

So I have not experienced this error and am using SciPy 1.2.1.  The fact that it segfaults, and is doing so in the eigh function leads me to believe that it is an error in the BLAS function provided by whatever version of openblas you are running, or something in the interface.  I am using MKL.

Running SciPy 1.3.0 with whatever crappy BLAS implementation it is picking from conda-forge also works fine.

Travis breaks with scipy-1.1.0 https://travis-ci.com/Qiskit/qiskit-terra/jobs/216504908

Locally updating openblas to 0.3.6, via brew, allowed my to use scipy 1.3.0. However, the CI env issue is still there and I cannot reproduce it.

I'm trying to debug this... but it's one of those tests in which we have random... this is just painful.

FWIW, this is something we started hitting fairly consistently in the macOS testing in azure pipelines when using macOS 10.14. I had to workaround it in: https://github.com/Qiskit/qiskit-terra/pull/2905 by downgrading to macOS 10.13.

@1ucian0 which version of macOS are you using when you hit this? I'm wondering if it could be an issue related to a system library version in mojave that scipy or whatever BLAS you're using is linking against causing this.

@1ucian0 which version of macOS are you using when you hit this?
10.14.6

@1ucian0 also what version of openblas is installed locally when you hit this? Just trying to get a handle on all the versions installed that come into play here. There was also a recent openblas release: https://github.com/xianyi/OpenBLAS/releases/tag/v0.3.7 , it's probably worth trying that too just to see if it fixes things.

I cannot reproduce this issue in my current setting and, since this seems like an openblas/numpy issue, I'm closing it.
For the record, my current setting is:

MacOS 10.15.1
Python 3.7.2
SciPy 1.4.1
NumPy 1.18.0
OpenBlas 0.3.6_1

If somebody else has this issue with a current env, please reopen.

I managed to reproduce the issue just to confirm that https://github.com/Qiskit/qiskit-terra/pull/3884 fixes it. Thanks @nonhermitian !


Compiling on Debian without Docker

Hi,
I want to create a package for my NAS server on a Debian Buster (10.x) with no docker on it.
I cloned the gitlab repo and then use the entrypoint.sh script directly with the correct VERSION variable set.
The following error occurs when compiling the sources. Any idea how to solve this ?
# export VERSION="v0.5.0"

# ./entrypoint.sh
+ BRANCH=v0.5.0
+ DEBIAN_FRONTEND=noninteractive
++ nproc
+ DEB_BUILD_OPTIONS=parallel=12
++ sed 's/\..*//' /etc/debian_version
+ OS_VERSION=10
+ TARGET=/usr/local/src/scaphandre-debian
+ export DEBIAN_FRONTEND DEB_BUILD_OPTIONS
+ main
+ dependencies
+ apt update
Get:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
...
Fetched 74.5 kB in 1s (59.2 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
+ apt install -y devscripts equivs git
Reading package lists... Done
Building dependency tree
Reading state information... Done
devscripts is already the newest version (2.19.5+deb10u1).
equivs is already the newest version (2.2.0).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ '[' 10 = 11 ']'
+ get_sources
++ mktemp -d
+ cd /tmp/tmp.cbBka5yaVD
+ git clone -b v0.5.0 https://github.com/hubblo-org/scaphandre.git scaphandre
Cloning into 'scaphandre'...
remote: Enumerating objects: 6621, done.
remote: Counting objects: 100% (1292/1292), done.
remote: Compressing objects: 100% (412/412), done.
remote: Total 6621 (delta 910), reused 1123 (delta 852), pack-reused 5329
Receiving objects: 100% (6621/6621), 8.22 MiB | 5.36 MiB/s, done.
Resolving deltas: 100% (4145/4145), done.
Note: checking out '7feb260cd397e6c0e9c3524cd736c6e93cccba45'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

+ cd scaphandre
+ build
+ cp -a /usr/local/src/scaphandre-debian/debian .
+ yes
+ mk-build-deps --install
dh_testdir
dh_testroot
dh_prep
dh_testdir
dh_testroot
dh_install
dh_installdocs
dh_installchangelogs
dh_compress
dh_fixperms
dh_installdeb
dh_gencontrol
dh_md5sums
dh_builddeb
dpkg-deb: building package 'scaphandre-build-deps' in '../scaphandre-build-deps_0.5.0-1_all.deb'.

The package has been created.
Attention, the package has been created in the current directory,
not in ".." as indicated by the message above!
(Reading database ... 116371 files and directories currently installed.)
Preparing to unpack scaphandre-build-deps_0.5.0-1_all.deb ...
Unpacking scaphandre-build-deps (0.5.0-1) over (0.5.0-1) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up scaphandre-build-deps (0.5.0-1) ...
+ dpkg-source --before-build .
+ debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Entering directory '/tmp/tmp.cbBka5yaVD/scaphandre'
cargo build --release
   Compiling libc v0.2.112
   Compiling autocfg v1.0.1
   Compiling cfg-if v1.0.0
   Compiling proc-macro2 v1.0.24
   Compiling unicode-xid v0.2.1
   Compiling syn v1.0.65
   Compiling cc v1.0.67
   Compiling pkg-config v0.3.19
   Compiling log v0.4.14
   Compiling memchr v2.3.4
   Compiling serde_derive v1.0.130
   Compiling once_cell v1.7.2
   Compiling lazy_static v1.4.0
   Compiling serde v1.0.130
   Compiling pin-project-lite v0.2.6
   Compiling futures-core v0.3.13
   Compiling bytes v1.0.1
   Compiling itoa v0.4.7
   Compiling tinyvec_macros v0.1.0
   Compiling matches v0.1.8
   Compiling fnv v1.0.7
   Compiling version_check v0.9.3
   Compiling ryu v1.0.5
   Compiling percent-encoding v2.1.0
   Compiling serde_json v1.0.64
   Compiling encoding_rs v0.8.28
   Compiling cache-padded v1.1.1
   Compiling spin v0.5.2
   Compiling crossbeam-utils v0.8.5
   Compiling slab v0.4.2
   Compiling curl v0.4.38
   Compiling bitflags v1.2.1
   Compiling futures-io v0.3.13
   Compiling smallvec v1.6.1
   Compiling ppv-lite86 v0.2.10
   Compiling scopeguard v1.1.0
   Compiling proc-macro-hack v0.5.19
   Compiling untrusted v0.7.1
   Compiling base64 v0.13.0
   Compiling fastrand v1.4.0
   Compiling getrandom v0.1.16
   Compiling parking v2.0.0
   Compiling event-listener v2.5.1
   Compiling openssl-probe v0.1.2
   Compiling isahc v1.5.0
   Compiling hashbrown v0.9.1
   Compiling waker-fn v1.1.0
   Compiling const_fn v0.4.6
   Compiling crc32fast v1.3.0
   Compiling mime v0.3.16
   Compiling pin-utils v0.1.0
   Compiling linked-hash-map v0.5.4
   Compiling adler v1.0.2
   Compiling futures-sink v0.3.13
   Compiling foreign-types-shared v0.1.1
   Compiling regex-syntax v0.6.23
   Compiling openssl v0.10.36
   Compiling protobuf v2.22.1
   Compiling httparse v1.5.1
   Compiling futures-task v0.3.13
   Compiling k8s-openapi v0.13.0
   Compiling unicode-width v0.1.8
   Compiling dtoa v0.4.8
   Compiling strsim v0.10.0
   Compiling remove_dir_all v0.5.3
   Compiling try-lock v0.2.3
   Compiling httpdate v1.0.1
   Compiling ansi_term v0.11.0
   Compiling ansi_term v0.12.1
   Compiling strsim v0.8.0
   Compiling hex v0.4.3
   Compiling match_cfg v0.1.0
   Compiling vec_map v0.8.2
   Compiling byteorder v1.4.3
   Compiling tower-service v0.3.1
   Compiling instant v0.1.9
   Compiling tracing-core v0.1.17
   Compiling futures-channel v0.3.13
   Compiling tinyvec v1.1.1
   Compiling unicode-bidi v0.3.4
   Compiling form_urlencoded v1.0.1
   Compiling http v0.2.4
   Compiling concurrent-queue v1.2.2
   Compiling lock_api v0.4.2
   Compiling rustls-pemfile v0.2.0
   Compiling num-traits v0.2.14
   Compiling num-integer v0.1.44
   Compiling indexmap v1.6.2
   Compiling tokio v1.11.0
   Compiling miniz_oxide v0.4.4
   Compiling foreign-types v0.3.2
   Compiling yaml-rust v0.4.5
   Compiling futures-util v0.3.13
   Compiling standback v0.2.17
   Compiling time v0.2.26
   Compiling textwrap v0.11.0
   Compiling sluice v0.5.4
   Compiling async-channel v1.6.1
   Compiling unicode-normalization v0.1.17
   Compiling want v0.3.0
   Compiling futures-lite v1.11.3
   Compiling aho-corasick v0.7.15
   Compiling quote v1.0.9
   Compiling http-body v0.4.3
   Compiling socket2 v0.4.2
error: attributes are not yet allowed on `if` expressions
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/socket2-0.4.2/src/sys/unix.rs:879:5
    |
879 |     #[cfg(not(any(target_os = "haiku", target_os = "openbsd")))]
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

error: could not compile `socket2`.
warning: build failed, waiting for other jobs to finish...
error: build failed
make[1]: *** [debian/rules:10: override_dh_auto_build] Error 101
make[1]: Leaving directory '/tmp/tmp.cbBka5yaVD/scaphandre'
make: *** [debian/rules:4: build] Error 2

Thanks.

Hi,
What version of  rustc are you using? Pretty sure scaphandre 0.5.0 requires a relatively recent version.

Hi,
Thanks for your answer. I gonna check that.
But I just have noticed that scaphandre needs a linux 5.11 kernel to work with an AMD Ryzen 3600 CPU (which is my case), and Debian Buster only comes with 5.10 in the backport channel.
So, at the end, it seems to be a no go for me :(

I see. I'll close this issue for now, don't hesitate to reopen it or create a new one if needed.


Close more intermittent bugs more frequently

Otherwise we will catch up too slowly.
Checklist

[ ] Type annotations added to new functions
[ ] Docs added to functions touched in main classes
[x] Dry-run produced the expected results
[ ] The to-be-announced tag added if this is worth announcing

"The Hitchhiker's Guide to the Galaxy"


Fix ebi downloads

Should actually fix downloading EBI datasets. URLs for tables and count matrices had changed, and this PR fixes that.
This is a bit of a band-aid, since we should probably be accessing these files through the FTP and we should be checking that already downloaded datasets are current.
I've also only done a spot check on this, and tested it with a couple datasets. It's probably worth testing with a larger set.

Did some more spot checks, seems to work.


Clickable buttons

When I make the window smaller, the menu buttons 'Save', undo etc are not clickable anymore

@StellaCh do you have a specific example? I tested it in all browsers (Chrome, Firefox, Safari) and I couldn't reproduce this issue.

I just tried a few examples, some of them worked and some didn't. It's tricky because it doesn't happen regularly, try make the window smaller eg.833x440 in https://inspirehep.net/editor/holdingpen/2541187
You can not click on Save or Undo or (!)

Which browser did you use?

Chrome

@StellaCh thanks for the details.


v2ray is detected by isp

v2ray is detected by my isp and vps ip is blocked. i use the default configuration of v2ray. what is the solution? should I enable https?

lmao, it's not the v2ray's fault if you are the one messed up, the project is not intended to be an once for all - fool proofing solution it's just a tool, there are people who have been using shadowsocks and doing fine and people who get blocked the moment they filled in google.com in the obfs option..... it's still possible to mess up if you can't comply to common guild-lines and not careful about your footprints like webRTC ip leaks and faulty proxy rules stuffs like that


Auto corrected by following Format Ruby Code

Auto corrected by following Format Ruby Code
Click here to configure it on awesomecode.io

Coverage decreased (-0.1%) to 80.751% when pulling 0c3802de7c35bdbb14470422fe9bb870a889e59e on awesomecode-format-ruby-code-48236 into ed40b1d9634eccd994a408834183ce70271b7d5b on master.


ceph luminous rbd-provisioner flag redefined

I tried to use the official provisionner image but it's configured to use mimic.
I built a luminous image but i get :
/usr/local/bin/rbd-provisioner flag redefined: log_dir
panic: /usr/local/bin/rbd-provisioner flag redefined: log_dir

goroutine 1 [running]:
flag.(*FlagSet).Var(0xc0000b8120, 0x156f000, 0x215bed0, 0x138d8eb, 0x7, 0x13b6b7b, 0x2f)
        /usr/local/go/src/flag/flag.go:850 +0x4af
flag.(*FlagSet).StringVar(...)
        /usr/local/go/src/flag/flag.go:753
github.com/kubernetes-incubator/external-storage/vendor/k8s.io/klog.InitFlags(0x0)
        /go/src/github.com/kubernetes-incubator/external-storage/vendor/k8s.io/klog/klog.go:411 +0xa4
main.main()
        /go/src/github.com/kubernetes-incubator/external-storage/ceph/rbd/cmd/rbd-provisioner/main.go:46 +0x3f

After trying to fix the bug described in https://github.com/kubernetes-incubator/external-storage/issues/1120 with the solution that was merged in https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/commit/99ac517d9c047238af8b8a6c411084b9f7888a87

OK, if I understand correctly we need to update our dependency on sig-storage-lib-external-provisioner.
/assign

meet same bug

cephfs have same bug, how to solve

I try to fix this by https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/pull/25, but still not works

I fix by https://github.com/kubernetes-incubator/external-storage/issues/1120#issuecomment-460684760

I fix by #1120 (comment)

I fix by delete klog.InitFlags(nil) in ceph/rbd/cmd/rbd-provisioner/main.go
and it works

I fix by #1120 (comment)

can fix by deleteing klog.InitFlags(nil) in ceph/rbd/cmd/rbd-provisioner/main.go


Czech guides not updating from Fer 2023

Guide
https://iptv-org.github.io/epg/guides/cs/m.tv.sms.cz.xml
Description
https://iptv-org.github.io/epg/guides/cs/m.tv.sms.cz.xml
https://iptv-org.github.io/epg/guides/cs/mujtvprogram.cz.xml
there is no update from february on this czech guides. Are they tsill alive?
Thnx

#2017


GRG Widget - redesign gp tools do user does not have to edit python scripts to set the feature class

Widget
GRG
Version of widget
0.1.0
Bug or Enhancement
Currently the user is required to edit each Python script to set the path to the enterprise feature class where the output gridded reference grid features are written to.
Repo Steps or Enhancement details
Redesign the tools so that the user does not have to edit the Python scripts. One possibility is to add a tool parameter to store the path to this enterprise feature class; the path could then be set when the widget is configured. This would require that the widget design is modified to allow the user to set this path in the configuration page.
@adgiles FYI

@elinz Closing this since new GRG widget doesn't rely on GP services anymore.


Inconsistent track type determination on YouTube track

The video in question for this report is: https://www.youtube.com/watch?v=FLM2U9bAlgU which was a livestream at one point.
Previous to Lavaplayer 1.3.53, playing this direct url would return the FriendlyException of "YouTube WebM streams are not currently supported." but using a ytsearch as described below would work. Now, at 1.3.53, the direct url will play but the video returns<PHONE_NUMBER>67:07:12:56 for the length (the livestream length long of<PHONE_NUMBER>854775807).
Playing the track in this manner with a direct url returns a Track with this information:
{
    "author": "Aggressive Records",
    "id": "FLM2U9bAlgU",
    "length":<PHONE_NUMBER>854775807,
    "position": 0,
    "source": "youtube",
    "stream": false,
    "title": "ROOLER @ QAPITAL QONNECT 2020",
    "uri": "https://www.youtube.com/watch?v=FLM2U9bAlgU"
}

However, if a ytsearch: method is used for the song title "ROOLER @ QAPITAL QONNECT 2020" and the first result is enqueued, a different Track object is provided, with a sane length for the video:
{
    "author": "Aggressive Records",
    "id": "FLM2U9bAlgU",
    "length": 1865000,
    "position": 0,
    "source": "youtube",
    "stream": false,
    "title": "ROOLER @ QAPITAL QONNECT 2020",
    "uri": "https://www.youtube.com/watch?v=FLM2U9bAlgU"
}

Fixed in 1.3.54.


Avoid queuing signals if possible when executing a playbook

Default is to skip queues for better performance. It can be configured to queue every signal.
Job start and polling for status still rely on queue.

@miq-bot add_label enhancement
@miq-bot assign @gmcculloug
@mkanoor @tinaafitz @syncrou please review

@bzwei @syncrou
For now its just an internal flag, we dont want to expose it to anyone.

@mkanoor @syncrou I changed the setter to a private method.