gofmt and ineffassign uses go version 1.17 on 1.18-beta1

I have a public module that uses Go v1.18BETA1 but the checks are made using an older version (I am guessing 1.17) on gofmt and ineffassign which gives error related to generics syntax.
Example gofmt:
either/right.go
Line 5: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)
maybe/maybe.go
Line 6: expected ';', found '|':1::warning: file is not gofmted with -s (gofmt)
Line 9: expected '}', found 'type':1::warning: file is not gofmted with -s (gofmt)
Line 20: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)
Line 26: expected declaration, found 'if':1::warning: file is not gofmted with -s (gofmt)
either/either.go
Line 5: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)
Line 27: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)
either/either_test.go
Line 127: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 149: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 165: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 179: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 197: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 217: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 239: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
Line 261: expected ']' or ':', found ',':1::warning: file is not gofmted with -s (gofmt)
result/result.go
Line 5: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)
Line 22: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)
Line 29: expected declaration, found 'return':1::warning: file is not gofmted with -s (gofmt)
either/left.go
Line 5: expected ']', found any:1::warning: file is not gofmted with -s (gofmt)

I can confirm gofmt on v1.18 does not return any issues.


JDL comments in DTO's

Overview of the feature request
Domain objects receive javadoc and swagger annotations derived from JDL comments by default, which is awesome, yet generated DTO's don't.
Motivation for or Use Case
It is awesome that there's a single place to add all the relevant information about an API.
Especially the swagger annotations are darn useful when working with external parties or different departments. Copy-pasting those from the domain objects to the DTO's seems wrong, once regenerating them and all the hard work is gone.

[x] Checking this box is mandatory (this is just to show you read everything)

+1
And if you can include remove from entities the swagger annotation when using DTO's would be owesome.

I'd love to level-up from end-user to contributor one day. Sadly in 2018 there won't be any such day, given all the stuff that's going on. Hope your colleague can pick it up.

@jdubois @deepu105 Since with GitHub any repo's admin (and org too I guess) can move issues around projects, can any of you guys try to move it to the generator?

I tried but I don't see the option. I guess only owner can do, so may be
Julien
On Mon, 19 Nov 2018, 11:09 pm Mathieu ABOU-AICHI<EMAIL_ADDRESS>wrote:

@jdubois https://github.com/jdubois @deepu105
https://github.com/deepu105 Since with GitHub any repo's admin (and org
too I guess) can move issues around projects, can any of you guys try to
move it to the generator?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jhipster/jhipster-core/issues/287#issuecomment-440059533,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDlFyLjH45o-17FshnuSu3ABv7Ht8HEks5uwyv7gaJpZM4YpEje
.


Error executing Deutsch-Jozsa with different QuantumInstances

Informations

Qiskit Aqua version:

{'qiskit-terra': '0.11.1',
'qiskit-aer': '0.3.4',
'qiskit-ignis': '0.2.0',
'qiskit-ibmq-provider': '0.4.5',
'qiskit-aqua': '0.6.2',
'qiskit': '0.14.1'}

Python version:

Executing on IBM Q Experience Jupyter Notebook Server

Operating system:

Executing on IBM Q Experience Jupyter Notebook Server
What is the current behavior?
If you run Deutsch-Jozsa first on the qasm-simulator and then on the statevector-simulator you get an 'IndexError: list index out of range' error.
If you run Deutsch-Jozsa first on the stavector-simulator and then on the qasm-simulator you get an
'No counts for experiment' error.
Steps to reproduce the problem
****** For the first error:
from qiskit import *
from qiskit.aqua import *
from qiskit.aqua.components.oracles import *
from qiskit.aqua.algorithms import *
oracle = TruthTableOracle("0101")
dj = DeutschJozsa(oracle)
backend = Aer.get_backend('qasm_simulator')
quantum_instance = QuantumInstance(backend)
result = dj.run(quantum_instance)
print(result)
backend = Aer.get_backend('statevector_simulator')
quantum_instance = QuantumInstance(backend)
result = dj.run(quantum_instance)
print(result)
****** For the second error:
from qiskit import *
from qiskit.aqua import *
from qiskit.aqua.components.oracles import *
from qiskit.aqua.algorithms import *
oracle = TruthTableOracle("0101")
dj = DeutschJozsa(oracle)
backend = Aer.get_backend('statevector_simulator')
quantum_instance = QuantumInstance(backend)
result = dj.run(quantum_instance)
print(result)
backend = Aer.get_backend('qasm_simulator')
quantum_instance = QuantumInstance(backend)
result = dj.run(quantum_instance)
print(result)
What is the expected behavior?
Both experiments should run without problems (I've tried with other algorithms, for example Grover, and the issue doesn't seem to exist).
Suggested solutions

To have this work you should re-create the algorithm (DJ) and components (oracles in this case) for each experiment. Consider that after construction and when run the algorithm/components are "consumed" by the experiment to produce the end result. I.e. internal variables may be updated as part of the run in producing the result (only in construction of the new instance are such variables set to defaults). So the object instances used in the 2nd experiment may have internal state left over after the first run and may not work as expected if re-used.
Now depending on the algorithm/components you might find that re-running, i.e. re-using the same instances, is possible however this is not guaranteed at all as the design/implementation did not require instance re-use across experiments. This is something we are presently re-evaluating for other reasons such that re-use would be part of the basic design and required.
But for now something like this works (i.e. create identical new instances for use in 2nd experiment/run)
from qiskit import *
from qiskit.aqua import *
from qiskit.aqua.components.oracles import *
from qiskit.aqua.algorithms import *

oracle = TruthTableOracle("0101")
dj = DeutschJozsa(oracle)

backend = Aer.get_backend('statevector_simulator')
quantum_instance = QuantumInstance(backend)
result = dj.run(quantum_instance)
print(result)

oracle = TruthTableOracle("0101")  # 2nd experiment, now using qasm
dj = DeutschJozsa(oracle)

backend = Aer.get_backend('qasm_simulator')
quantum_instance = QuantumInstance(backend)
result = dj.run(quantum_instance)
print(result)

Thank you. I had found a similar workaround, but thought you might be interested in knowing about the problem. Glad that you are onto it and thanks again for the response!

Sure, you're welcome. Evidently instance re-use can require much more careful implementation and testing to ensure things all work, but as I mentioned we are re-evaluating this aspect for other reasons. So in the future what you had tried to do may become possible but for now each experiment should have new instances. If you do this you should not have this problem.

Understood, thank you!


Ability to deploy using an Azure DevOps Release Pipeline

Is your feature request related to a problem? Please describe.
I cannot use Azure Static Web Sites because I have an application I'd like to run but have different environments to run it with. I would like to be able to deploy an application into Azure Static Web Sites in a DevOps Release Pipeline as opposed to a build pipeline so that I can modify certain files based upon the environment I am deploying to.
Describe the solution you'd like
I would like to have a task available to me in a release pipeline instead of a build pipeline that allows me to unzip a previously built artifact, do any work on it like modifying any files as part of the release pipeline, and then finally a step that allows me to upload a folder of files into Azure Static Web Sites.
Describe alternatives you've considered
I tried using the Azure DevOps Build Pipeline option, but it will not work for me as I need to be able to deploy to multiple environments like DEV, STAGING, and PROD.
Additional context
It feels odd to me that a build pipeline should be deploying bits somewhere as opposed to a release pipeline. This feature seems to rely heavily on the idea that you are using GitHub as your source control repository. Well, we are using a Git repository on Azure DevOps instead, and that makes this feel like it is only half baked when I can't do what I'd like using DevOps as opposed to a Github Action.

We are working on a feature that'll allow you to deploy to named pre-production environments. Too early for an ETA but it should enable your scenario.

I'd like to second this. I want to use it in our enterprise environment with DevOps. As much as I like GitHub, I feel like it's not really used that much in serious business environments when compared to DevOps.

Same scenario as @stephajn.
I've tried to use the task in an Azure DevOps Release Pipeline with a pre-built react app (and extracted it to $(System.DefaultWorkingDirectory)/app in the previous task) and log output is below (invalid characters are copied as-is from DevOps):
2021-08-06T18:17:42.5407717Z App Directory Location: '/home/vsts/work/r1/a/app' is invalid. Could not detect this directory. Please verify your workflow reflects your repository structure.
2021-08-06T18:17:43.0097949Z
2021-08-06T18:17:43.0099559Z For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
2021-08-06T18:17:43.0101398Z If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/

Task details:
2021-08-06T18:17:06.1764859Z Task         : Deploy Azure Static Web App
2021-08-06T18:17:06.1765212Z Description  : [PREVIEW] Build and deploy an Azure Static Web App
2021-08-06T18:17:06.1765488Z Version      : 0.187.1
2021-08-06T18:17:06.1765730Z Author       : Microsoft Corporation
2021-08-06T18:17:06.1766032Z Help         : https://aka.ms/swadocs

A task that's just for deployment would be great, I have the Skip app build toggled on too.
steps:
- task: AzureStaticWebApp@0
  displayName: Deploy
  inputs:
    app_location: '$(System.DefaultWorkingDirectory)/app'
    output_location: ./
    skip_app_build: true
    azure_static_web_apps_api_token: '$(deployment_token)'

We have an update coming to the DevOps task that will improve the experience for release pipelines. It should be deployed in the next few weeks. https://github.com/microsoft/azure-pipelines-tasks/pull/14807
It's important to note that the app_location must be relative to the working folder. Currently, the task uses a working directory location that is incompatible release pipelines. https://github.com/microsoft/azure-pipelines-tasks/pull/14807 will fix this.

We have the same use case: deploy from a release pipeline. Today we deploy to Azure BLOB storage, linked to a CDN. It would be nice to replace that part.

Hi all,
We got this working quite ok for now. Not saying this is a long-term solution but it at least allowed us to use SWA in a way we like a bit more. Consider this inspiration 😎
So in our projects, we put these two steps in our azure-pipelines.yml. We do this after compiling the application. Please not that we leave the api as-is as the release pipeline always builds this and therefore needs source code.
- task: PublishBuildArtifacts@1
  inputs:
    PathtoPublish: '$(Build.SourcesDirectory)/dist'
    ArtifactName: 'dist'
    publishLocation: 'Container'
  displayName: 'Publish dist folder'

- task: PublishBuildArtifacts@1
  inputs:
    PathtoPublish: '$(Build.SourcesDirectory)/api'
    ArtifactName: 'api-dist'
    publishLocation: 'Container'
  displayName: 'Publish api dist folder'

We can then setup 2 release pipelines that both first download the artifacts created in the build pipeline (app and api). In a second step we run a bash script. This is quite a heavy beast but what it is basically doing is run the same docker image as the build pipeline step while providing configuration settings. As you can see below, with different settings you can create/update a staging slot or update your production slot. Please note that we did not find a way to detect closed pull requests so staging slots need to removed by hand.
RELEASE to PRODUCTION
docker run
--entrypoint "/bin/staticsites/StaticSitesClient"
--volume "$(System.DefaultWorkingDirectory)/$(Release.TriggeringArtifact.Alias)":/root/artifacts
-e "IS_PULL_REQUEST=false" -e "BASE_BRANCH=$(Build.SourceBranchName)"
-e "DEPLOYMENT_PROVIDER=DevOps"
-e "REPOSITORY_URL=https://yournamehere@dev.azure.com/yournamehere/$(System.TeamProject)/_git/$(Build.Repository.Name)"
mcr.microsoft.com/appsvc/staticappsclient@sha256:fc9db23777aea0ee404885f29ebc56305d016304b9ec07a3cd823d132016288b upload
--skipAppBuild true
--app /root/artifacts/dist
--api /root/artifacts/api-dist
--apiToken $(deploy_token)

RELEASE to STAGING
docker run
--entrypoint "/bin/staticsites/StaticSitesClient"
--volume "$(System.DefaultWorkingDirectory)/$(Release.TriggeringArtifact.Alias)":/root/artifacts
-e "IS_PULL_REQUEST=true"
-e "BASE_BRANCH=$(Build.PullRequest.TargetBranchName)"
-e "DEPLOYMENT_PROVIDER=DevOps"
-e "REPOSITORY_URL=https://yournamehere@dev.azure.com/yournamehere/$(System.TeamProject)/_git/$(Build.Repository.Name)"
-e "PULL_REQUEST_ID=$(Build.PullRequest.Id)"
-e "PULL_REQUEST_TITLE=$(Build.PullRequest.Id)"
-e "HEAD_BRANCH=$(Build.PullRequest.SourceBranchName)"
mcr.microsoft.com/appsvc/staticappsclient@sha256:fc9db23777aea0ee404885f29ebc56305d016304b9ec07a3cd823d132016288b upload
--skipAppBuild true
--app /root/artifacts/dist
--api /root/artifacts/api-dist
--apiToken $(deploy_token)

We can then setup 2 release pipelines that both first download the artifacts created in the build pipeline (app and api). In a second step we run a bash script. This is quite a heavy beast but what it is basically doing is run the same docker image as the build pipeline step while providing configuration settings. As you can see below, with different settings you can create/update a staging slot or update your production slot. Please note that we did not find a way to detect closed pull requests so staging slots need to removed by hand.
RELEASE to PRODUCTION
docker run
--entrypoint "/bin/staticsites/StaticSitesClient"
--volume "$(System.DefaultWorkingDirectory)/$(Release.TriggeringArtifact.Alias)":/root/artifacts
-e "IS_PULL_REQUEST=false" -e "BASE_BRANCH=$(Build.SourceBranchName)"
-e "DEPLOYMENT_PROVIDER=DevOps"
-e "REPOSITORY_URL=https://yournamehere@dev.azure.com/yournamehere/$(System.TeamProject)/_git/$(Build.Repository.Name)"

We use Azure App Configuration to store our configuration externally. This allows us to use the AAC task https://marketplace.visualstudio.com/items?itemName=AzureAppConfiguration.azure-app-configuration-task to pull configuration into build pipeline variables. Next we use the variables in a File Transform task, https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/file-transform?view=azure-devops, which updates the config file with the deployment settings. This approach might replace your complex docker step.

Any updates on this?

There are a couple of updates coming in the next few months to address this.

A skip_api_build flag that allows you to deploy build artifacts without the task rebuilding the app. Waiting for https://github.com/microsoft/azure-pipelines-tasks/pull/15996. This is the tracking item: #343
Support for named pre-production environments. Work in progress, no date to share yet.

We've just added support for named preview environments using Azure DevOps. Please give it a try and let us know if you have any feedback.

Thanks @simonaco! Will do!

Hey @simonaco
I've taken named preview environments for a spin.  Seems to work - I've a bunch of questions:

am I right in thinking that named preview environments can't be renamed once created?
nothing cleans up a named preview environment I think?  They live as long as your default branch lives?
how many named environments could you have with an SWA?   Based on my usage it seems like only one is possible - is that right?

The repo I've been testing it on this (the blog post mentioned in the README is old - so ignore that):
https://dev.azure.com/johnnyreilly/azure-static-web-apps/_git/azure-static-web-apps
You don't need to look at it; I just share for context

I've written up my experiences in this blog: https://blog.johnnyreilly.com/2022/05/07/static-web-apps-azure-devops-named-preview-environments
Do let me know if there's any issues with it!

We've just added support for named preview environments using Azure DevOps. Please give it a try and let us know if you have any feedback.

Why is this called "preview" and not "staging" like normal terminology in release pipelines and Azure resources?

We've just added support for named preview environments using Azure DevOps. Please give it a try and let us know if you have any feedback.

The feature can now pick up a build artifact in a release pipeline. In a typical scenario you still want some config to be modified in the static website build artifact. Staging might need different back end URI's for instance. As I mentioned earlier we use Azure App Configuration to rewrite specific keys in a config.json file we use in the build artifact. Unfortunately the AAC release task can't deal with JSON values to replace keys even though AAC supports JSON values at runtime together with Microsoft.Extensions.Configuration perfectly. It would be nice to team up with the AAC task owners and create a smooth experience to deploy a reconfigured build artifact.

I hope to see the update for this ticket soon.

Static website builders in particular often use dynamic content and do other shenanigans with external dependencies during build and so have a more fragile build process.
Hence separating build from release makes much more sense for static web apps than for regular ones.
I need a separation here more than I need one for my .NET apps.

This feature is much needed. Without this, the stages and approval flows have to be done in build pipelines (using yaml) and that doesn't scale if you have multiple build pipelines on multiple repos, working in tandem with a singular release pipeline.

Static website builders in particular often use dynamic content and do other shenanigans with external dependencies during build and so have a more fragile build process.
Hence separating build from release makes much more sense for static web apps than for regular ones.
I need a separation here more than I need one for my .NET apps.

Hi @jtheisen ,
Could you please elaborate what exactly are you looking for here? As @anthonychu mentioned in this comment, we do have support for splitting build and release between different stages, thus letting you run the build once in the building stage, and then using skip_app_build:true in the other stages, sourcing it from the build stage. For more details you can check out the doc here.

Ok, I didn't look too closely at that.
Some minor question about that: AzureStaticWebApp@0 doesn't do only the build and I need to run the build with other tasks, right?

Closing the issue.


Configuring user agent(s) in importers

I recently ran into an issue where I could not import content from a particular RSS feed because the server kept giving me 429s. The provider told me my user agent was probably not unique enough. I tried changing the user agent naively down in the feed importer code, and sure enough, that worked. I'm thinking this kind of thing might come up again, and so some general http client configuration in the importers would be handy.

Reddit has this issue


provide single runner script

@joelvarunvasanth I could not find the single runner script in the repo for the release. Once the merge request #1 is merged, can you also push the single runner script?

This is 'train_marl.py' if I understand correctly what you mean by runner script?

Is it also the one that is used for the deterministic runner? (Ie without exploration noise?)

No that is not the one for the deterministic runner, I will push that to your repo and then we can merge it.

Perfect :) . Let me know here / point me to it when it is ready :) .

Looks good (I will not have time to run it tonight, but will try later on :) ). Feel free to close, if I have further questions I will open new issues.

Checked now, seems a few things are broken (and I guess running this out of the box will anyways require adding the dump of the trained model etc):
(shenfun) Singularity> python3 deterministic.py
Traceback (most recent call last):
  File "deterministic.py", line 27, in <module>
    from MARL_env import Environment2D
ModuleNotFoundError: No module named 'MARL_env'

Let me know when you push something updated (and test it on your end before pushing, following the methodology described in https://github.com/KTH-FlowAI/DeepReinforcementLearning_RayleighBenard2D_Control#recommended-using-our-singularity-sandbox so that I just do a "double checking" :) ).


How can I set up Max Value to 100 in Y axis in bar chart

Make sure max data point is 100

Make sure max data point is 100

ridiculous solution


Added is identity comparison for numpy records and added tests as is_comparison_tests.py

Hello!
I have added the workaround to numba/np/arrayobj.py and have created test cases for the same.
Please let me know if any more changes are required
regards,
Kamakshi

Thanks for making changes. For future changes - please could you avoid force-pushing as this tends to confuse the Github review interface - many thanks in advance!

Having skimmed over the latest revision, I'm not going to be able to spend more time reviewing this PR in its current form - I think it would be helpful for you to receive additional mentorship to fill in some of the conceptual gaps here, and that's not something I have enough time to do.
If you'd like to proceed with the PR, I would suggest making a post on the Numba Discourse (https://numba.discourse.group) describing what you're trying to achieve with the PR, and requesting if there's anyone with sufficient time and experience to help shepherd the PR closer to completion and being ready for another round of review.

Hey,
I want to proceed with the PR and will connect with someone to help me complete it. Thanks!

I have made the corrections as pointed out by @guilhermeleobas . Sorry for the delay 🙂

Thanks for the help @guilhermeleobas .
I have made changes please let me know if there are any more problems.
I had to from np.arrayobj import record_is    in test_array_methods.py  since all the checks were failing without it

Thanks @guilhermeleobas ! I have tried a different approach for record_is_impl function. I hope this works!! Please update me on any needed changes🙂

I have changed it back as requested. Please take a look

Thank you @guilhermeleobas and @gmarkall  for all your help!! All the tests have successfully passed. I hope this fixes the issue🙂

@gmarkall and @guilhermeleobas  I have made all changes as well as added documentation. Please let me know if anything else I required further since the PR hasn't been merged yet. 🙂


create docker-compose config

Compose is a tool for defining and running multi-container Docker applications.
https://docs.docker.com/compose/
for easy connecting to the dgraph ip instead of jq etc...

The Docker Compose tool is also installed in the Docker enabled environment. https://docs.travis-ci.com/user/docker/#Using-Docker-Compose

here is a nice example: https://github.com/celrenheit/sandglass/blob/dev/docker-compose.yml
and how it can be used in travis:
https://github.com/celrenheit/sandglass/blob/dev/.travis.yml


The length of render data does not match the limit option setting

There is a logic in dataset.js. I have made some comments.
 function async(suggestions) {
               suggestions = suggestions || [];
               if (!canceled && rendered < that.limit) {
                     that.cancel = $.noop;
                     rendered += suggestions.length;
                     that._append(query, suggestions.slice(0, that.limit - rendered));  // The length of suggestion list will be wrong. It will cause the length of render does not match the limit option setting

                     that.async && that.trigger("asyncReceived", query);
               }
}

I think it is better to change the code like this
 function async(suggestions) {
               suggestions = suggestions || [];
               if (!canceled && rendered < that.limit) {
                     that.cancel = $.noop;
                     that._append(query, suggestions.slice(0, that.limit - rendered));
                     rendered += suggestions.length;

                     that.async && that.trigger("asyncReceived", query);
               }
}

seems fixed in other issue


No typecheck of .vue file properties when imported into a .tsx (JSX) file.

Given the default vite vue typescript template, if we change the app file to an app.tsx:
import { defineComponent, ref } from "vue";
import HelloWorld from "./components/HelloWorld.vue";
import {HelloWorldJSX } from "./HelloWorldJSX " // another jsx component

export const App = defineComponent({
  components: {
    HelloWorld,
  },
  setup() {
    return () => (
      <>
        <img alt="Vue logo" src="./assets/logo.png" />
        <HelloWorldJSX wrongProp="Hello Vue 3 + TypeScript + Vite" /> <!-- will error :D -->
        <HelloWorld wrongProp="Hello Vue 3 + TypeScript + Vite" /> <!-- won't error :( -->
      </>
    );
  },
});

It seems as if properties from other TSX files are imported ok, but those from .vue files are not.

It's should works, have you enabled TS plugin?

yes I have

Please provide a repro case by https://github.com/johnsoncodehk/volar-starter.

Apparently I did something wrong before, because after cloning the template and making the same changes it now seems to work. Closing the issue. Sorry to waste your time!


[Feature Request] Cookies

So I was messing around with the python FDK and I noticed that there's no inbuilt wrapper around cookies. This isn't a huge problem because python's http lib deals with them swimmingly, but that generates some fluff code. Would it be possible to add a way to set and access cookies in the same way as http headers (ctx.Cookies() and return response.Response(ctx,"returned data", headers={"header1":"foo"},cookies={"cookie1":"bar"}) perhaps?) I originally opened a similar issue on the python fdk, and I was recommended to open one here so that if such a feature were to become supported it would be on all languages, not just python.
I reckon a fair few people would be using cookies anyway. If python supports them so well, I can't see node or ruby being far behind. Would this be possible? Would it be worth your time?

Cookies can be fairly easily extracted from the cookie header in the HTTP gateway context
Originally we tried to strike a balance between a low level HTTP/event binding and a fully fledged HTTP SDK.
PRs are welcome here

Parsing them isn't the issue. that can be achieve in two lines and one of them is an import. The problem is sending them to the user in the first place. A small problem to be sure, but a nasty one. Python has a builtin module called http (at least I think its builtin). this has a submodule called cookies and that submodule is how python developers deal with cookies to my knowledge. problem is this. when you run str(cookies) it generates a list of headers to send to the client. this works great in a cgi environment because you send headers directly in that case. problem is it generates a list of headers all with the same name. something like 'Set-Cookie: bar=foo\r\nSet-Cookie: foo=bar'. wheras your implementation would expect 'bar=foo,foo=bar' (or something to that effect). now this is the fault of python for making such a convenient module that no one has felt the need to write a better one (to my knowledge). also adapting the former to the latter is not rocket science. a for loop and str replace could solve the problem it two lines.
in short it's a pet peave not an deal breaker. it still annoy's me though.
enough about why I want the feature though. I might make a pull request. I do believe the philosophy of do it yourself if you want it done right (or at all). No promises though. And if I do it will specifically be for python, because you know, that's what I use.

So after a mornings reading RFC6265 and stack overflow, I might have uncovered a genuine issue. You cannot set multiple cookies in a single set-cookie header. The way it's meant to be is "set-cookie: foo=bar,bar=foo,tra=la" with cookies sepperated by coma. However, google chrome does not seem to implement this spec. Having manually set the headers to this format using cgi-bin scripts and python http, only the first cookie on the list is accepted (if any of them are). from what I can tell the only way to set more than one cookie at once is to send multiple set-cookie headers. the problem is that only one of each header may be sent using the present way of doing things (to my knowledge, correct me if I'm wrong). for reference, currently the headers are stored as a dictionary (a map of one value to another) which cannot store duplicate keys (header is key, header content is value). not sure if cookies are the only time that you'd want to send two headers with the same name, but now you know.
still not a big issue. it can probably be worked around. bit worse than a pet peave now though.


wasm-engines:  terminate benchmarking if a benchmark fails to build

Rebased on top of (but does not strictly depend on): https://github.com/ewasm/benchmarking/pull/34

@jwasinger I think you included these in #43?


fix(ComponentRelation): fix visualization on details page

Fixes

https://issues.redhat.com/browse/KFLUXBUGS-1106
Description

fix component relation visualization on components details page
Type of change

[ ] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

The arrow position seems little off in chrome, it works fine in firefox though.

The arrow position seems little off in chrome, it works fine in firefox though.

@karthikjeeyar should be fixed now

/approve
/lgtm


Remove towncrier, and add support for rust-native feature notes

When a :flamingo: is ready to cut our first official "alpha release"...

[ ] Run towncrier once, to compile the existing newsfragments into a release note
[ ] Remove all support for towncrier & related tooling
[ ] Add support for a rust-native release notes
[ ] Make sure that the compiled newsfragments release notes (or at least the important parts) get included into the rust-native release systme
[ ] Update the discord channel that commits now need to follow the conventional commit format.
[ ] ...

closing for #824


Desktop. Native distribution. intallationPath doesn't work if dirChooser = false

from https://github.com/JetBrains/compose-multiplatform/issues/4862#issuecomment-2129026290

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


[WIP] Add name and expectedSize in FileInput

This is great 👍We already implemented this feature for S3 input plugin as experimental but, better to improve Embulk SPI itself.
ref: https://github.com/embulk/embulk-input-s3/pull/68

@muga Thanks for your comment. IIUC the feature in S3 input is just listing the files, but I expect the addition in this PR may allow to recognize the filename(-like) information in Decoders/Parsers.

Closing this as #1066 has been merged.


docs(Button): update contentColor description

Description
Updated description of contentColor prop to clarify its purpose and usage

Sanity Tests Execution Failed.

Sanity Tests Execution Failed.


WIP Fix for Mosek interface with SDP + power cone

Description
Fix for SDP + power cone.
Issue link (if applicable): #2128
Type of change

[ ] New feature (backwards compatible)
[ ] New feature (breaking API changes)
[x] Bug fix
[ ] Other (Documentation, CI, ...)

Contribution checklist

[ ] Add our license to new files.
[ ] Check that your code adheres to our coding style.
[ ] Write unittests.
[ ] Run the unittests and check that they’re passing.
[ ] Run the benchmarks to make sure your change doesn’t introduce a regression.

@dcajasn I think this fixes the bug. Can you test and elaborate this PR with a simple test case that fails without the fix and works with it? I don't have more time to work on this right now.


Step to step guide on setting up go server

Not sure if this is the best format for submitting a minimal setup guide, if @supersonictw thinks it's not appropriate then I will close it anyway
Required docker images:
Popcat server require redis for cache and mysql for stats aggregation so you will these image other than the popcat image.
docker pull supersonictw/popcat-echo
docker pull redis
docker pull mysql:5.7

docker run -p 6379:6379  -d redis:latest
docker run -p 3306:3306 -e  MYSQL_ROOT_PASSWORD=<Your password> -d mysql:5.7

Setup MYSQL
Use the initialize.sql script to setup your MYSQL database schema. You may need to connect to your database before this.
Execute image
Setup docker environment variable file according to .env.sample
I find this DSN format working under my own setup ( under Linux environment you will need to change docker.for.mac.localhost to the docker IP )
MYSQL_DSN=<mysql user>:<password>@tcp(docker.for.mac.localhost:3306)/<your database name>?charset=utf8

Execute popcat server
docker run -p 8013:8013 --env-file <your environment variable file> supersonictw/popcat-echo

You should be able to access popcat server at localhost:8013 !

Excellent! Thank you for your contribution.
By the way, there are some scripts available on https://github.com/supersonictw/popcat-echo_deploy.

Hi, I'm really new to databases. Can you explain more details on how to create, connect to the database, deploy the script and DSN, .env kinda stuff? Thanks in advance!

there are some scripts available on https://github.com/supersonictw/popcat-echo_deploy.

By the way, the deploy script is not working for me, what am I missing? It's showing a ERROR 1045 (28000): Access denied for user '-p'@'localhost' (using password: NO) error.
Seems like it can't understand the $MARIADB_... variables.

It didn't work but still thank you! We solved it by making our own backend lol

The application already refactor, so the guide might be not working. The new one is here.
git clone https://github.com/supersonictw/popsenzawa-echo-deploy.git
cd popsenzawa-echo-deploy
sh initialize_mmdb.sh
docker-compose up -d


[text-translation] Integration test broken due to missing variable

Internal pipeline link: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3710403&view=logs&j=efd63400-1b36-5c22-495f-5e04b5698008&t=4d436ef9-74aa-529e-00cf-860ebe15a4d4
Failure is related to Error: TEXT_TRANSLATION_AAD_REGION is not defined
This variable was recently introduced by https://github.com/Azure/azure-sdk-for-js/pull/29145
I believe it has to be declared in test-resources.json

@MikeyMCZ is there a better owner for this issue?


At least one user was mislead by the "--apply-changes" flag

cc @devoncarew
Talking to one of our early users, they ran dartdev migrate on a test package. After running the tool, they did not realize that there was a preview or that the preview was important. Instead they saw the advice "rerun with --apply-changes" and did that instead, and missed out on the main benefits of the tool.
We should rewrite the output to point users to the web preview more heavily, like even maybe something as extreme as:
*beep boop beep*: If you are a computer in an automated workflow, you can rerun
with --apply-changes. If you are a human, use the interactive web view to review,
improve, or apply the results:

Open URL http://.....:82340/....

It may be enough to print the preview page url in an ansi bold style?

Playing with the verbiage sounds good also (use the interactive web view to review, improve, or apply the results), you just may want to steer away from specific computer / human guidance.

Some work for this is here: https://dart-review.googlesource.com/c/sdk/+/138480 (modulo launching in a browser).

This has been improved--the new behavior is that by default, the migration tool starts up the preview server.  But if --no-web-preview is supplied, the tool still says To apply these changes, re-run the tool with --apply-changes.  I still think we should consider improving the verbiage, e.g. as suggested in https://github.com/dart-lang/sdk/issues/40881#issuecomment-594879258.

Mike also points out that when --no-web-preview is not supplied, the tool still tells you about --apply-changes.  Probably we shouldn't explicitly point the user to this option since we want to discourage its use.  They can find it in --help if they really need it.

This issue should be defined more concretely. It looks like the AIs are:

Launch the browser (and add a flag, --[no]launch-browser?).

If the web preview is served, do not print text about --apply-changes.

The current text is awkward:
View migration results:
Visit:

  http://localhost:54770/Users/srawlins/code/dart-csslib?authToken=...

to see the migration results. Use the interactive web view to review...

I like the word "suggestions" used earlier in the output. Maybe something like:
View the migration suggestions by visiting:

  http://localhost:54770/Users/srawlins/code/dart-csslib?authToken=...

Use this interactive preview to review...

I've forked off the "launch a browser" idea into its own issue: https://github.com/dart-lang/sdk/issues/41809.


Fix #10454: Improve Search Relevancy, by adding functional scoring an…

…d add ngram analyzer; Fix #10452: Enable Table and Column search by BOTH name and displayName
Describe your changes :

I worked on the ..... because ...

Type of change :

[x] Improvement

[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

[ ] Documentation

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

I have set back the name of the example tables since it was breaking some tests. Apart of that I notice we stop showing why it is matching in the results like this:  Now it does not appear anything. Is it expected? do we want to handle this change in a different PR/issue?

@nahuelverdugo not understanding the use cases?

@nahuelverdugo searched for address_id and we do show it matches a column name

@harshach, if you create a table with name and display_name that are different when you search for the display_name, it does not show why the search matches the table.

@harshach Have verified the Cypress Failures, It's flaky and I will make them consistent over the time


Replace None checks in skipgram right padding

From #1070 and #1179, the None checks for the end of the inner skipgram loop is replaced with a sentinel object.

Thanks @alvations


Is this addon listed in the asset library?

Describe the bug
I can't find this addon in the Asset library, but I can find https://github.com/rakugoteam/Godot-Material-Icons
Runtime (please complete the following information):

Godot version 4.4

No, it isn't at AssetLib.
I used to use AssetLib in the past, but stopped because I was annoyed by how long it took them to approve a project/update and the fact that I couldn't change my username.

After will soon add it to AssetLib @manuelarte

Awesome


Problem with gulp-sass ? Or gulp-autoprefixer ? Or gulp-sourcemaps ?

Hi,
There is a lot of issue about mixing gulp-sass and/or gulp-autoprefixer with gulp-sourcemaps.
For example : https://github.com/dlmanning/gulp-sass/issues/106, https://github.com/sindresorhus/gulp-autoprefixer/issues/8
I just spend 2 hours debugging to find out where the problem come from, and still no success.
But I finally noticed something (but still don't know where the problem come from).
In source-map-generator.js @ Line 359, I watched the key value.
In this configuration:
gulp.task('css', function () {
    gulp.src('./assets/sass/style.scss')
        .pipe(sourcemaps.init())
        .pipe(sass())
        //.pipe(sourcemaps.write({includeContent: false}))
        //.pipe(sourcemaps.init({loadMaps: true}))
        .pipe(autoprefixer())
        .pipe(sourcemaps.write('.'))
        .pipe(gulp.dest('./public/css'))
});

The value of the key is $style.css, and it does not work
But in this configuration:
gulp.task('css', function () {
    gulp.src('./assets/sass/style.scss')
        .pipe(sourcemaps.init())
        .pipe(sass())
        .pipe(sourcemaps.write({includeContent: false}))
        .pipe(sourcemaps.init({loadMaps: true}))
        .pipe(autoprefixer())
        .pipe(sourcemaps.write('.'))
        .pipe(gulp.dest('./public/css'))
});

The value of the key is $style.scss, and it works
Because with the two configurations, _sourcemapContents in source-map-generator.js#360 has always a $style.scss key.
Hope this helps to resolve this issue, and to find if the problem come from sourcemap, sass or autoprefixer (or something else)

I'm not sure if I'm having the same problem. I've been looking into this for about 2 days now. I think gulp-autoprefixer is making a correct sourcemap between it's input/output css files. gulp-sourcemaps and gulp-sass don't seem to be the issue either. I've tried compiling my scss file with node-sass and it's sourcemap feature, it seems to output a broken sourcemap regardless of settings.
I've come across an excellent visualizer tool. It would seem that the mappings for the scss file are correct but the output css file is incorrect, everything maps to 0. So the issue is likely node-sass or libsass?
You can see the scss/css I've been using to learn the gulp-sass/autoprefixer workflow with sourcemaps in the visualizer tool here . Note the bottom content identifying the mappings, each mapping starts with 0->, and as you can see in the css content on the right, it's highlighting the first line only. Am I the only one getting a result like this? (autoprefixer aside).

I've looked further into this and am pretty sure the issue is related to libsass or node-sass with how they're producing a sourcemap. I've manually corrected the scss-css sourcemap mappings, then used gulp-autoprefixer, mappings appear to be working and chrome/firefox dev tools are reporting the correct lines to the scss. You can see the scss/autoprefixer sourcemap here
Raised an issue on node-sass here, and just been notified it's an issue with libsass which should be solved with libsass 3.2.

Thank-you @ByScripts, your solution worked great for me! (I'm using gulp-sass)

@ByScripts gulp-sass was updated recently, mappings aren't broken like before. If you're using gulp-ruby-sass you should be fine with the alpha release if using external sources, embedded don't seem to work. The only other issue with gulp-ruby-sass that prevents me using it is the file paths placed in sources of the sourcemap, I think this is only an issue with windows from what I've read.
I have code examples for both here

npm update gulp-sass fixed the problem for me. Now working with gulp-sass, gulp-autoprefixer, and gulp-sourcemaps.
gulp.task('styles', function() {
  return gulp.src('scss/*.scss')
    .pipe(sourcemaps.init())
    .pipe(sass({ style: 'expanded' }))
    .pipe(autoprefixer('last 2 version'))
    .pipe(sourcemaps.write())
    .pipe(gulp.dest('css'))
    .pipe(rename({suffix: '.min'}))
    .pipe(minifycss())
    .pipe(gulp.dest('css'))
    .pipe(connect.reload())
    .pipe(notify({ message: 'Styles task complete' }));
});

I think this can be closed. @ByScripts's sample tasks work identically with latest module versions.

I don't think having .pipe(sourcemaps.write({includeContent: false}))         .pipe(sourcemaps.init({loadMaps: true})) in between sass and autoprefixer is elegant.

@stevemao Then remove them :smile: Both tasks work now.

Thanks @heikki , for the reference web-starter-kit is already using this.
https://github.com/google/web-starter-kit/commit/8c356e1bb9bbd5218ec533780b035beb6d9b035e

Hi, i was reading that the new version fixed the problem, but i installed today
"gulp": "^3.9.1",
"gulp-autoprefixer": "^3.1.0",
"gulp-sass": "^2.3.1",
"gulp-sourcemaps": "^1.6.0",
And doesn't work if i do:
gulp.task('sass', () => {
  log('Compiling SCSS files...');
  return gulp
    .src('./src/app/**.*scss')
    .pipe(plumber())
    .pipe(sourcemaps.init())
    .pipe(sass().on('error', sass.logError))
    .pipe(autoprefixer({ browser: ['last 2 version', '> 5%'] }))
    .pipe(sourcemaps.write('.'))
    .pipe(gulp.dest('./.temp/'));
});

But if i added the @ByScripts two MAGIC LINES works
// THIS WORKS
gulp.task('sass', () => {
  log('Compiling SCSS files...');
  return gulp
    .src('./src/app/**.*scss')
    .pipe(plumber())
    .pipe(sourcemaps.init())
    .pipe(sass().on('error', sass.logError))
    .pipe(sourcemaps.write({includeContent: false}))
    .pipe(sourcemaps.init({loadMaps: true}))
    .pipe(autoprefixer({ browser: ['last 2 version', '> 5%'] }))
    .pipe(sourcemaps.write('.'))
    .pipe(gulp.dest('./.temp/'));
});

When this would be fixed to don't need that two lines... is like zero readable... :S

was facing the same issue, solutions by @HectorLS  solved my prob.

@HectorLS solution helped me too, but here
.pipe(autoprefixer({ browser: ['last 2 version', '> 5%'] }))
must be browserS

I had the same problem (autoprefixer not working), and the solution by @HectorLS didn't work for me. But what did work, was commenting out my lines implementing sourcemaps; then running my gulp task (which then allowed autoprefixer to work).
After that I was able to reinstate my sourcemaps config and they both worked nicely together.
Hope that might help someone.

@manorossa Could you share an example of your code?

Upgrading to 2.6.4 the problem does not persists anymore.
This is my task
function sass () {     const processors = [cachebuster({         cssPath: /dist/stylesheets, imagesPath: /dist/img`
}), rucksack];
return gulp.src('src/stylesheets/main.scss')
           .pipe($.sourcemaps.init())
           .pipe($.sass({includePaths: PATHS.sass}).on('error', $.sass.logError))
           .pipe($.autoprefixer({browsers: COMPATIBILITY}))
           .pipe($.if(PRODUCTION, $.cleanCss({compatibility: '*'})))
           .pipe(postcss(processors))
           .pipe($.if(!PRODUCTION, $.sourcemaps.write('.')))
           .pipe(gulp.dest(PATHS.dist + '/stylesheets'))
           .pipe(browser.reload({stream: true}))
           .pipe(notify({message: 'Css compilato correttamente', onLast: true}));

}`

doesnt work
.pipe($.autoprefixer({ browsers: ['last 5 versions', '> 1%'], cascade: true }))


Rename Committees Endpoint

I've referred to this sort of data as "Committees" for far too long when in all actuality it is a just a title for a group of memberships, events, and/or probably agenda items as I suggested in #8.  I would say the committees are actually just a subset of the data that this endpoint will actually be used for.
Just some examples of non-committees we've had in the past:
Freshman connection and Officers are examples of "Committees" in Scoreboard.
General is an example of a "Committee" in WTF.
President, VP, Treasurer, and Secretary will be "Committees" for agenda items

Rename to /groups?

Yeah that works for me.


Unable to push knative images to local registry

Expected Behavior
I have been trying to build images for knative release version 0.5 on Power architecture by cloning branch release-0.5. The image build succeeds with $ ./hack/release.sh --skip-tests --nopublish --notag-release command. However, when I try to run any of the images or push them to local registry, I am facing some git commit(kodata) related issue. Am I missing something here?
Actual Behavior
Trying to run docker run -it ko.local/github.com/knative/build/cmd/git-init:latest sh gives following output.(prettied the json up for readability)
{
"level":"warn",
"ts":1555319522.5300372,
"logger":"fallback-logger",
"caller":"logging/config.go:65",
"msg":"Fetch GitHub commit ID from kodata failed: \"ref: refs/heads/release-0.5\" is not a valid GitHub commit ID"
}
{
"level":"error",
"ts":1555319522.5588896,
"logger":"fallback-logger",
"caller":"git-init/main.go:52","msg":"Unexpected error running git [fetch --depth=1 --recurse-submodules=yes origin ]: exit status 128\nfatal: no path specified; see 'git help pull' for valid url syntax\n",
"stacktrace":"main.runOrFail\n\t/root/Shivani/knative-images/go/src/github.com/knative/build/cmd/git-init/main.go:52\nmain.main\n\t/root/Shivani/knative-images/go/src/github.com/knative/build/cmd/git-init/main.go:91\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"
}
{
"level":"error",
"ts":1555319522.5990245,
"logger":"fallback-logger",
"caller":"git-init/main.go:41",
"msg":"Error running git [pull --recurse-submodules=yes origin]: exit status 1\nfatal: no path specified; see 'git help pull' for valid url syntax\n",
"stacktrace":"main.run\n\t/root/Shivani/knative-images/go/src/github.com/knative/build/cmd/git-init/main.go:41\nmain.main\n\t/root/Shivani/knative-images/go/src/github.com/knative/build/cmd/git-init/main.go:95\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"
}
{
"level":"error",
"ts":1555319522.619067,
"logger":"fallback-logger",
"caller":"git-init/main.go:52",
"msg":"Unexpected error running git [checkout ]: exit status 128\nfatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths\n",
"stacktrace":"main.runOrFail\n\t/root/Shivani/knative-images/go/src/github.com/knative/build/cmd/git-init/main.go:52\nmain.main\n\t/root/Shivani/knative-images/go/src/github.com/knative/build/cmd/git-init/main.go:96\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"
}

Steps to Reproduce the Problem

mkdir -p ${GOPATH}/src/github.com/knative
cd ${GOPATH}/src/github.com/knative
git clone --branch release-0.5 https://github.com/knative/build.git
cd build
./hack/release.sh --skip-tests --nopublish --notag-release
docker run -it ko.local/github.com/knative/build/cmd/git-init:latest sh

Additional Info
Previously, we have been able to build and push images for Power architecture on dockerhub for version 0.3. However, we are facing some kodata related errors currently. It may be an environment setup issue. Any suggestions would be of great help.
/area test-and-release
/kind question

Any suggestions?


Removing last item from bookmarks doesn't return empty view

Search works as expected, though.

Gonna lean on #854 fixing this as well
Sent with GitHawk


ghost_head cleanup & debug statements

This adds 3 cleanup / minor change commits on top of the error handling PR #8982.

Adds a handful of debug statements, so it's easier to see where time is spent after rendering when in DEBUG mode.
Changes the layout of promises to always have the . on a newline, which makes it easier to read
Changes from using Promise.props to Promise.join, which allows us to remove a few lines of code that otherwise don't do much

It would be possible to squash and merge this instead of #8982, setting the commit message back to the error handling one.

I would squash these together and stick with the general commit message ghost_head cleanup & debug statements. The single commit messages are a bit too general e.g. Use join instead of props for less code - doesn't say where. If you want single commits, could you pls update the single messages? 🙃

It would be possible to squash and merge this instead of #8982, setting the commit message back to the error handling one.

This comment was if you merged this instead of #8982 as all 4 commits were here ;) Definitely squash this and give it a general message without an emoji!


Wiki request - rewrite and simplify explanation of String.split()

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/split

Wiki page for str.split() now exists.
https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/String.split()

Thanks!


Issue with k8s.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/

This is a...

[ ] Feature Request
[ X] Bug Report

Problem:
The link to view the Network Plugin interface in section Network Plugin Requirements is broken. It looks like the  code was moved as part of some refactoring?
Proposed Solution:
Fix the link
Page to Update:
https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/

Kubernetes Version: 1.11

This was fixed in #9298
/close


Excel like formula feature

I am trying to use formulas in the sheet. To do this I used to-text prop then executed the input if it starts with = symbol. Now I want to show the formula when the cell is double clicked (in the edit mode). Is there a way to do this?

No simple way to do this. I suggest you may try to toggle the visibility of 2 columns and add the onChange event to make necessary changes

I gave up on this idea and went with another solution. Here is what I did:
I used another json to keep the formulas and listened the cell-focus event. I found the corresponding formula when the cell-focus event (if there is one) then showed it in an input field above the actual table. This also makes it possible to edit the formula. If it is changed I execute it and write the outcome back to the data.
Thank you for considering adding new events I think it will be better.

Yes, you may also use get set variable in javascript. Will follow up about adding events


SnakeGame_VoiceContolled

Issue no. - #456
Click play button and allow microphone....

Control the game using voice commands...

@ranimanya Thank you for your contribution. Looking forward to more such amazing contributions 🥂


Stop hijacking ctrl+A when an input is focused

#10 introduced behavior to select text only in the modal, but it also made it such that when a user is in a text field (e.g. a username field) and wants to select the text they have entered with ctrl+a, it doesn't work as expected. Instead of selecting the text in the text field, it selects all of the modal text.
This tests to see if any input fields have focus before firing onSelectAll.

Thanks!


Cluster: Failed to refresh slots cache. when options.redisOptions.enableOfflineQueue = false

If I pass options to new Cluster with options.redisOptions.enableOfflineQueue = false, ioredis (3.2.2) fails to connect to the cluster.  If I remove setting that specific option, then everything is good (went through them one-by-one).
Below is sample code with the output when options.redisOptions.enableOfflineQueue = false.
Note that I also have set options.enableOfflineQueue = false - it is not entirely clear if both need to be set.  In my usage, I do NOT want commands to be queued when the cluster or the intended node is not available.
'use strict';

let Redis = require('ioredis');

function _retryStrategy(times) {
    let retry;

    if (times === 1) {
        retry = 1;  // immediate retry
    } else {
        retry = Math.min((times - 1) * 2000, 20000);
    }
    return retry;
}

const options = {
    // Cluster-level options
    // Override ioredis defaults.
    clusterRetryStrategy   : _retryStrategy,
    enableOfflineQueue     : false,                     // ioredis default is true
    scaleReads             : 'all',                     // ioredis default is 'master'

    // ioredis defaults - explicitly set for clarity.
    enableReadyCheck       : true,
    maxRedirections        : 16,
    retryDelayOnFailover   : 100,
    retryDelayOnClusterDown: 100,
    retryDelayOnTryAgain   : 100,

    // Per Server options
    redisOptions: {
        // Override ioredis defaults.
        enableOfflineQueue           : false,           // ioredis default is true   !!! THIS IS THE PROBLEM !!!
        connectTimeout               : 2000,            // ioredis default is 10000
        autoResendUnfulfilledCommands: false,           // ioredis default is true
        retryStrategy                : _retryStrategy,
        readOnly                     : true,            // ioredis default is false

        // ioredis defaults - explicitly set for clarity.
        family           : 4,
        path             : null,
        keepAlive        : 0,
        noDelay          : true,
        db               : 0,
        dropBufferSupport: false,
        enableReadyCheck : true,
        autoResubscribe  : true,
        lazyConnect      : false,
        keyPrefix        : '',
        stringNumbers    : false
     }
};

let startupNodes = [];
for (let i = 0; i < 3; i++) {
    startupNodes[i] = {
        host: '<IP_ADDRESS>',
        port: 6400 + (10*i)
    };
    console.log('Using startupNode %s:%d.', startupNodes[i].host, startupNodes[i].port);
}

let client = new Redis.Cluster(startupNodes, options);

client.on('ready', function() {
    console.log('Redis Cluster is Ready.');
});

client.cluster('info', function (err, clusterInfo) {
    if (err) {
        console.log('Redis Cluster is not yet ready. err=%j', err);
    } else {
        console.log('Redis Cluster Info=%j', clusterInfo);
    }
});

/usr/src/app# DEBUG=ioredis:* node clustertest.js
Using startupNode <IP_ADDRESS>:6400.
Using startupNode <IP_ADDRESS>:6410.
Using startupNode <IP_ADDRESS>:6420.
  ioredis:cluster status: [empty] -> connecting +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: [empty] -> connecting +3ms
  ioredis:redis status[<IP_ADDRESS>:6410]: [empty] -> connecting +2ms
  ioredis:redis status[<IP_ADDRESS>:6420]: [empty] -> connecting +0ms
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6410 +1ms
  ioredis:redis status[<IP_ADDRESS>:6400]: connecting -> connect +15ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:redis status[<IP_ADDRESS>:6410]: connecting -> connect +2ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:redis status[<IP_ADDRESS>:6420]: connecting -> connect +1ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6420 +3ms
Redis Cluster is not yet ready. err={}
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6400 +2ms
[ioredis] Unhandled error event: Error: Failed to refresh slots cache.
    at tryNode (/usr/src/app/node_modules/ioredis/lib/cluster/index.js:375:19)
    at /usr/src/app/node_modules/ioredis/lib/cluster/index.js:387:9
    at /usr/src/app/node_modules/ioredis/lib/cluster/index.js:591:14
    at run (/usr/src/app/node_modules/ioredis/lib/utils/index.js:153:16)
    at tryCatcher (/usr/src/app/node_modules/bluebird/js/release/util.js:16:23)
    at Promise.errorAdapter [as _rejectionHandler0] (/usr/src/app/node_modules/bluebird/js/release/nodeify.js:35:34)
    at Promise._settlePromise (/usr/src/app/node_modules/bluebird/js/release/promise.js:566:21)
    at Promise._settlePromise0 (/usr/src/app/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/usr/src/app/node_modules/bluebird/js/release/promise.js:689:18)
    at Async._drainQueue (/usr/src/app/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/usr/src/app/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/usr/src/app/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
  ioredis:redis status[<IP_ADDRESS>:6410]: connect -> ready +7ms
  ioredis:redis status[<IP_ADDRESS>:6420]: connect -> ready +2ms
  ioredis:redis status[<IP_ADDRESS>:6420]: ready -> close +1ms
  ioredis:connection skip reconnecting since the connection is manually closed. +0ms
  ioredis:redis status[<IP_ADDRESS>:6420]: close -> end +0ms
  ioredis:redis status[<IP_ADDRESS>:6410]: ready -> close +1ms
  ioredis:connection skip reconnecting since the connection is manually closed. +0ms
  ioredis:redis status[<IP_ADDRESS>:6410]: close -> end +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: connect -> ready +1ms
  ioredis:redis status[<IP_ADDRESS>:6400]: ready -> close +0ms
  ioredis:connection skip reconnecting since the connection is manually closed. +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: close -> end +1ms
  ioredis:cluster status: connecting -> close +0ms
  ioredis:cluster status: close -> reconnecting +1ms
  ioredis:cluster Cluster is disconnected. Retrying after 1ms +2ms
  ioredis:cluster status: reconnecting -> connecting +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: [empty] -> connecting +1ms
  ioredis:redis status[<IP_ADDRESS>:6410]: [empty] -> connecting +1ms
  ioredis:redis status[<IP_ADDRESS>:6420]: [empty] -> connecting +1ms
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6410 +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: connecting -> connect +3ms
  ioredis:redis write command[0] -> info() +1ms
  ioredis:redis status[<IP_ADDRESS>:6410]: connecting -> connect +0ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:redis status[<IP_ADDRESS>:6420]: connecting -> connect +1ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6420 +0ms
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6400 +1ms
[ioredis] Unhandled error event: Error: Failed to refresh slots cache.
    at tryNode (/usr/src/app/node_modules/ioredis/lib/cluster/index.js:375:19)
    at /usr/src/app/node_modules/ioredis/lib/cluster/index.js:387:9
    at /usr/src/app/node_modules/ioredis/lib/cluster/index.js:591:14
    at run (/usr/src/app/node_modules/ioredis/lib/utils/index.js:153:16)
    at tryCatcher (/usr/src/app/node_modules/bluebird/js/release/util.js:16:23)
    at Promise.errorAdapter [as _rejectionHandler0] (/usr/src/app/node_modules/bluebird/js/release/nodeify.js:35:34)
    at Promise._settlePromise (/usr/src/app/node_modules/bluebird/js/release/promise.js:566:21)
    at Promise._settlePromise0 (/usr/src/app/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/usr/src/app/node_modules/bluebird/js/release/promise.js:689:18)
    at Async._drainQueue (/usr/src/app/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/usr/src/app/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues (/usr/src/app/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)
  ioredis:redis status[<IP_ADDRESS>:6410]: connect -> ready +7ms
  ioredis:redis status[<IP_ADDRESS>:6410]: ready -> close +1ms
  ioredis:connection skip reconnecting since the connection is manually closed. +1ms
  ioredis:redis status[<IP_ADDRESS>:6410]: close -> end +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: connect -> ready +4ms
  ioredis:redis status[<IP_ADDRESS>:6420]: connect -> ready +1ms
  ioredis:redis status[<IP_ADDRESS>:6420]: ready -> close +0ms
  ioredis:connection skip reconnecting since the connection is manually closed. +0ms
  ioredis:redis status[<IP_ADDRESS>:6420]: close -> end +1ms
  ioredis:redis status[<IP_ADDRESS>:6400]: ready -> close +0ms
  ioredis:connection skip reconnecting since the connection is manually closed. +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: close -> end +0ms
  ioredis:cluster status: connecting -> close +0ms
  ioredis:cluster status: close -> reconnecting +1ms
^C

If I comment out the one line, then all is good:
/usr/src/app# DEBUG=ioredis:* node clustertest.js
Using startupNode <IP_ADDRESS>:6400.
Using startupNode <IP_ADDRESS>:6410.
Using startupNode <IP_ADDRESS>:6420.
  ioredis:cluster status: [empty] -> connecting +0ms
  ioredis:redis status[<IP_ADDRESS>:6400]: [empty] -> connecting +3ms
  ioredis:redis status[<IP_ADDRESS>:6410]: [empty] -> connecting +3ms
  ioredis:redis status[<IP_ADDRESS>:6420]: [empty] -> connecting +0ms
  ioredis:cluster getting slot cache from <IP_ADDRESS>:6420 +2ms
  ioredis:redis queue command[0] -> cluster(slots) +2ms
  ioredis:redis queue command[0] -> cluster(info) +2ms
  ioredis:redis status[<IP_ADDRESS>:6400]: connecting -> connect +6ms
  ioredis:redis write command[0] -> info() +1ms
  ioredis:redis status[<IP_ADDRESS>:6410]: connecting -> connect +2ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:redis status[<IP_ADDRESS>:6420]: connecting -> connect +0ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:redis status[<IP_ADDRESS>:6410]: connect -> ready +14ms
  ioredis:connection send 1 commands in offline queue +0ms
  ioredis:redis write command[0] -> cluster(info) +1ms
  ioredis:redis status[<IP_ADDRESS>:6400]: connect -> ready +1ms
Redis Cluster Info="cluster_state:ok\r\ncluster_slots_assigned:16384\r\ncluster_slots_ok:16384\r\ncluster_slots_pfail:0\r\ncluster_slots_fail:0\r\ncluster_known_nodes:6\r\ncluster_size:3\r\ncluster_current_epoch:3\r\ncluster_my_epoch:2\r\ncluster_stats_messages_ping_sent:7405\r\ncluster_stats_messages_pong_sent:6762\r\ncluster_stats_messages_meet_sent:1\r\ncluster_stats_messages_sent:14168\r\ncluster_stats_messages_ping_received:6758\r\ncluster_stats_messages_pong_received:7406\r\ncluster_stats_messages_meet_received:4\r\ncluster_stats_messages_received:14168\r\n"
  ioredis:redis status[<IP_ADDRESS>:6420]: connect -> ready +2ms
  ioredis:connection send 1 commands in offline queue +1ms
  ioredis:redis write command[0] -> cluster(slots) +0ms
  ioredis:redis status[<IP_ADDRESS>:6401]: [empty] -> connecting +11ms
  ioredis:redis status[<IP_ADDRESS>:6421]: [empty] -> connecting +1ms
  ioredis:redis status[<IP_ADDRESS>:6411]: [empty] -> connecting +0ms
  ioredis:cluster status: connecting -> connect +1ms
  ioredis:redis write command[0] -> cluster(info) +1ms
  ioredis:redis status[<IP_ADDRESS>:6401]: connecting -> connect +3ms
  ioredis:redis write command[0] -> info() +1ms
  ioredis:redis status[<IP_ADDRESS>:6421]: connecting -> connect +1ms
  ioredis:redis write command[0] -> info() +1ms
  ioredis:redis status[<IP_ADDRESS>:6411]: connecting -> connect +0ms
  ioredis:redis write command[0] -> info() +0ms
  ioredis:cluster status: connect -> ready +1ms
Redis Cluster is Ready.
  ioredis:redis status[<IP_ADDRESS>:6411]: connect -> ready +5ms
  ioredis:connection set the connection to readonly mode +0ms
  ioredis:redis write command[0] -> readonly() +1ms
  ioredis:redis status[<IP_ADDRESS>:6401]: connect -> ready +2ms
  ioredis:connection set the connection to readonly mode +2ms
  ioredis:redis write command[0] -> readonly() +0ms
  ioredis:redis status[<IP_ADDRESS>:6421]: connect -> ready +1ms
  ioredis:connection set the connection to readonly mode +1ms
  ioredis:redis write command[0] -> readonly() +0ms
^C

Same here;
Redis-logs are also printing  - Client closed connection Err

This is clearly a defect.  I'd try to root cause it and submit a PR, but I'm not familiar enough with the code and unfortunately don't have the time to figure it out.  While the obviously work around is to not set that option, it is not at all clear what the implications are as the both exists at both the cluster level and the individual server level.  At a minimum, the documentation needs to be updated to clarify the behavior of these options for a Redis Cluster.

Commenting to keep the issue open.

@luin Any chance this will be addressed?

unstale

Hey @ccs018, I took a look at your issue.
The problem is that currently, ioredis tries to refresh the slots map before actually connecting to the cluster, which causes it to fail and disconnect from the node before it managed to connect (Because you don't have the offline queue enabled).
From my understanding, the redisOptions.offlineQueue is not relevant for cluster mode because when the redis node will go offline it will also be removed from the cluster nodes list, so no commands will be sent to it when its offline.
One possible fix for this is to move the refreshSlotsCache call to only after at least one node has been connected. @luin ?

@shaharmor , thanks for taking a look at this.

the redisOptions.offlineQueue is not relevant for cluster mode

Thanks for clarifying.  The documentation is not clear which redis node options are applicable in cluster mode.  In my use case, queuing commands when offline would likely cause issues as I can have multiple clients attempting to update the same keys and if one client queued an update while its connection was down and another client was able to make another update, then when the first client reconnected it would incorrectly clobber the other client's update (the updates would be made out-of-order).

when the redis node will go offline it will also be removed from the cluster nodes list

I believe that this is incorrect behavior.  This can typically be a temporary event and ioredis should not be unilaterally removing the node from the cluster nodes list.  It should query the cluster for the topology since when the node recovers ioredis is not proactively adding the node back to the cluster nodes list.
Consider a rolling upgrade scenario.  As each node is taken down to be upgraded, ioredis is removing the node from the cluster nodes list.  Eventually, there will be none left.  Restarting clients is not an acceptable recovery when one is trying to design a zero-outage system - which includes upgrades.

Just saw the PR - Looks like this will fix a couple similar issues.  Though I still don't believe that when a node goes offline that it should be removed from the cluster nodes list.  Just mark it as offline and periodically attempt to reconnect.

The problem with this is that a cluster can sometimes have nodes that will never come up again, in cases such as auto scaling where a machine goes up, and when it goes down it will never return, which will cause ioredis to basically leak nodes.
I agree that there are fixes that should be done in the way we handle cluster nodes. I have talked with @luin and we will take a look at it next week. Sorry for the delay.
The "moved" event will cause ioredis to re-fetch the nodes list, and now with my PR it will do that periodically as well, but I agree that we should probably trigger it on a -node event as well.

any real workarounds?

I use ioredis 4.14.1, and node 12.13.0.
The error of ClusterAllFailedError: Failed to refresh slots cache. occured in only one of my cluster, the others worked ok.
Then I restarted the app with the problem, it  recovered from the error.

+1

+1


where to load the generated pseudo labels of target data?

First I run the generate_presudo_label.py, then when I run the train.py. I don't know how to load the generated pseudo labels of target data to became target_train_loader? could you please show me where this part of the code is?

Maybe set the parameter --path_soft can fix it, you can read parser_train.py for details.
https://github.com/microsoft/ProDA/blob/9ba80c7dbbd23ba1a126e3f4003a72f27d121a1f/parser_train.py#L36
https://github.com/microsoft/ProDA/blob/9ba80c7dbbd23ba1a126e3f4003a72f27d121a1f/parser_train.py#L80

Maybe set the parameter --path_soft can fix it, you can read parser_train.py for details.
https://github.com/microsoft/ProDA/blob/9ba80c7dbbd23ba1a126e3f4003a72f27d121a1f/parser_train.py#L36
https://github.com/microsoft/ProDA/blob/9ba80c7dbbd23ba1a126e3f4003a72f27d121a1f/parser_train.py#L80

Thanks for your reply. I just found it in def getitem(self, index):


Quality Assurance Projects - Sudoku Solver clearer instructions on logic

Describe your problem and how to reproduce it:
There are two major questions I had while I was doing this project, and it seems like other people also had similar issues.
1.) (There's a similar issue to this already here, but this question deals with conflicting row/column/region.)
Q: Do we need to indicate if the value at a coordinate is conflicting with the final solution or with what is currently on the board?
If something could indicate that you only need to figure out checkRow/Column/RegionPlacement in sudoku-solver.js with what is currently on the board rather than checking with the final solution, that would help immensely.
2.) Q: For the solve() method in sudoku-solver.js, does it need to check against solution logic provided elsewhere in the backend only on the test inputs, or do we need to provide the solve logic ourselves for ANY given puzzleString input?
I received several conflicting answers when I asked on Discord, but I believe the right answer is that I need to provide the logic myself? Making this clearer on the /learn page by saying that we need to return the solved string with our own logic in solve() would be helpful.
These are probably not the clearest answers, but these were sufficient in helping me answer my questions that I had about this.
Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/sudoku-solver

Do we need to indicate if the value at a coordinate is conflicting with the final solution or with what is currently on the board?

The check function should be validating against the current state of the board, not necessarily the final solution. Essentially, it is confirming that your number placement is valid when compared against the numbers currently present on the board.
Imagine implementing this as a sudoku helper - checking against the current state of the board would allow for things like highlighting numbers that conflict by row/column/region.

For the solve() method in sudoku-solver.js, does it need to check against solution logic provided elsewhere in the backend only on the test inputs, or do we need to provide the solve logic ourselves for ANY given puzzleString input?

You are expected to write the logic (and related tests) to handle solving the sudoku puzzle based on the given input. I do agree that this is not explicitly spelled out on the /learn page and would be more than open to suggestions for clarifying this piece.

Underneath "All puzzle logic can into /controllers/sudoku-solver.js", maybe add an indented bullet with this information:

The validate function should take a given puzzle string and check it to see if it has 81 valid characters for the input.
The check functions should be validating against the current state of the board.
The solve function should handle solving any given valid puzzle string, not just the test inputs and solutions. You are expected to write out the logic to solve this.

I still feel a bit iffy about my descriptions to add above (even though English is my native language, I'm not the best at clearly explaining things), and I have not submitted a pull request yet with the proposed changes. I'd like to discuss further to help make this clearer.

I think I am okay with this approach - I'll give others a chance to weigh in before opening this up. 🙂

I am fine with adding this as well.

Hi, I've opened my first PR in this repo for this issue. Please take a look when you have a chance!

Hi, I've opened my first PR in this repo for this issue. Please take a look when you have a chance!


CEL Interperter for Conditions

Continues on #254 in a way that is backward compatible.  To use cel based conditions, you must prefix your condition with cel:

Closing this in favor of #396 which drops support for all the legacy syntax altogether


Fix 'TangramWaterFlowLayout' layout overlap problem

When running the demo, I found that 'TangramWaterFlowLayout' did not work properly and all the items were stacked together

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


Reporting Inaccurate Affected Components in GHSA-7q8g-gpfp-v8gx

According to the advisory(https://nifi.apache.org/security.html#CVE-2020-1942) and patch in this advisory(https://github.com/apache/nifi/pull/4028/files) ,the affected component is org.apache.nifi:nifi-framework-core and org.apache.nifi:nifi-security-utils.
The affected versions should be rechecked.

Hey there @catch22out
https://nifi.apache.org/security.html#CVE-2020-1942
Calls out the versions we're using 👍
Many thanks for the the extra specificity on the packages. There's some weirdness with how you've made your PRs. We prefer to keep one GHSA edit to one PR and as is I'll have to close these without assigning you contribution credit. Let me know if that's a problem for you and we can see what we can make work on out side 😄


Introduce a new internal package

Introduce a new internal package in the server codebase and move all the files currently located in the root folder into it, except for the domain file portainer.go.

should the errors file move too?

@chiptus I think so, yes.

as errors refactor is a very big refactor (115 files) I'm separating into two prs


Update functional test's HTTP codes

Update functional tests codes, based on the on-http PR.
Depends on PR https://github.com/RackHD/on-http/pull/389
All functional tests with the on-http changes PASS locally.
@benbp @keedya @BillyAbildgaard @brianparry @dalebremner @RackHD/corecommitters @zyoung51 @jlongever

👍

:+1:

+1

👍


Following examples/lighting-app/nrfconnect/README.md fails in SDK installation

Problem
Following "Using Docker container for setup" in "Setting up the environment" guide in examples/lighting-app/nrfconnect/README.md fails in the 4th step when trying to initialize the SDK:
Updating nRF Connect SDK to recommended revision...
fatal: cannot change to '/var/ncs/zephyr/../nrf': No such file or directory
Command '['git', '-C', '/var/ncs/zephyr/../nrf', 'fetch']' returned non-zero exit status 128.

/var/ncs is empty, since the bind mounted directory ~/nrfconnect just got created...
How can the nRF Connect SDK initialized properly?
Proposed Solution

It seems that the following commands initialize the nRF Connect SDK
../ncs/
west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.9.0
west update
cd ../chip/

From https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_installing.html#get-the-ncs-code.
Then step 4 can be continued successfully.


Authentication fails after machine creation

$ sudo ./bin/salt-cloud -p ubuntu_rackspace salt-cloud-test
...........................................................................................................................................................................++
.......................................................................................++
Creating Cloud VM salt-cloud-test
There was an in wait_for_passwd: Authentication failed.
Traceback (most recent call last):
  File "./bin/salt-cloud", line 7, in <module>
    execfile(__file__)
  File "/home/pete/tmp/src/salt-cloud/scripts/salt-cloud", line 14, in <module>
    main()
  File "/home/pete/tmp/src/salt-cloud/scripts/salt-cloud", line 10, in main
    cloud.run()
  File "/home/pete/tmp/src/salt-cloud/saltcloud/cli.py", line 231, in run
    mapper.run_profile()
  File "/home/pete/tmp/src/salt-cloud/saltcloud/cloud.py", line 180, in run_profile
    self.create(vm_)
  File "/home/pete/tmp/src/salt-cloud/saltcloud/cloud.py", line 151, in create
    ok = self.clouds['{0}.create'.format(self.provider(vm_))](vm_)
  File "/home/pete/tmp/src/salt-cloud/saltcloud/clouds/rackspace.py", line 93, in create
    script=deploy_script.script)
  File "/home/pete/tmp/src/salt-cloud/saltcloud/utils/__init__.py", line 181, in deploy_script
    ssh.connect(host, port=port, username=username, password=password)
  File "/home/pete/tmp/lib/python2.6/site-packages/paramiko/client.py", line 332, in connect
    self._auth(username, password, pkey, key_filenames, allow_agent, look_for_keys)
  File "/home/pete/tmp/lib/python2.6/site-packages/paramiko/client.py", line 493, in _auth
    raise saved_exception
paramiko.AuthenticationException: Authentication failed.

I am seeing the same behavior in 2015.5.0
'''
root@saltmaster:/etc/salt# salt-cloud -l all --profile=default_profile test.example
[DEBUG   ] Reading configuration from /etc/salt/cloud
[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Including configuration from '/etc/salt/master.d/file_roots.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/file_roots.conf
[DEBUG   ] Including configuration from '/etc/salt/master.d/pillar_roots.conf'
[DEBUG   ] Reading configuration from /etc/salt/master.d/pillar_roots.conf
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: REDACTED
[DEBUG   ] Reading configuration from /etc/salt/cloud.providers
[DEBUG   ] Reading configuration from /etc/salt/cloud.profiles
[TRACE   ] None of the required configuration sections, 'logstash_udp_handler' and 'logstash_zmq_handler', were found the in the configuration. Not loading the Logstash logging handlers module.
[DEBUG   ] Configuration file path: /etc/salt/cloud
[TRACE   ] Trying pysss.getgrouplist for 'root'
[TRACE   ] Trying generic group list for 'root'
[TRACE   ] Group list for user 'root': []
[INFO    ] salt-cloud starting
[TRACE   ] 'parallels.avail_sizes' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad parallels.avail_sizes
[TRACE   ] 'parallels.avail_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded parallels.avail_locations
[TRACE   ] 'proxmox.avail_sizes' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded proxmox.avail_sizes
[TRACE   ] 'saltify.destroy' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.destroy
[TRACE   ] 'saltify.avail_sizes' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.avail_sizes
[TRACE   ] 'saltify.avail_images' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.avail_images
[TRACE   ] 'saltify.avail_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.avail_locations
[TRACE   ] 'rackspace.reboot' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded rackspace.reboot
[TRACE   ] 'openstack.list_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded openstack.list_locations
[TRACE   ] 'rackspace.list_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded rackspace.list_locations
[TRACE   ] 'parallels.avail_sizes' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad parallels.avail_sizes
[TRACE   ] 'parallels.avail_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded parallels.avail_locations
[TRACE   ] 'proxmox.avail_sizes' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded proxmox.avail_sizes
[TRACE   ] 'saltify.destroy' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.destroy
[TRACE   ] 'saltify.avail_sizes' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.avail_sizes
[TRACE   ] 'saltify.avail_images' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.avail_images
[TRACE   ] 'saltify.avail_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] Could not LazyLoad saltify.avail_locations
[TRACE   ] 'rackspace.reboot' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded rackspace.reboot
[TRACE   ] 'openstack.list_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded openstack.list_locations
[TRACE   ] 'rackspace.list_locations' has been marked as not supported. Removing from the list of supported cloud functions
[DEBUG   ] LazyLoaded rackspace.list_locations
[DEBUG   ] Using AWS endpoint: ec2.us-west-2.amazonaws.com
[DEBUG   ] AWS Request: https://ec2.us-west-2.amazonaws.com/?Action=DescribeInstances&Version=2014-10-01
[TRACE   ] AWS Request Parameters: {}
[INFO    ] Starting new HTTPS connection (1): ec2.us-west-2.amazonaws.com
[DEBUG   ] Setting read timeout to None
[DEBUG   ] "GET /?Action=DescribeInstances&Version=2014-10-01 HTTP/1.1" 401 None
[DEBUG   ] AWS Response Status Code: 401
[TRACE   ] AWS Response Text:
AuthFailureAWS was not able to validate the provided access credentialse4dc2731-66c5-40cb-b257-4b5d4ec5cffb
[ERROR   ] AWS Response Status Code and Error: [401 401 Client Error: Unauthorized] {'Errors': {'Error': {'Message': 'AWS was not able to validate the provided access credentials', 'Code': 'AuthFailure'}}, 'RequestID': 'e4dc2731-66c5-40cb-b257-4b5d4ec5cffb'}
[DEBUG   ] Failed to execute 'ec2.list_nodes()' while querying for running nodes: An error occurred while listing nodes: AWS was not able to validate the provided access credentials
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/salt/cloud/init.py", line 2247, in run_parallel_map_providers_query
cloud.cloudsdata['fun']
File "/usr/lib/python2.7/dist-packages/salt/cloud/clouds/ec2.py", line 3032, in list_nodes
nodes = list_nodes_full(get_location())
File "/usr/lib/python2.7/dist-packages/salt/cloud/clouds/ec2.py", line 2891, in list_nodes_full
return _list_nodes_full(location)
File "/usr/lib/python2.7/dist-packages/salt/cloud/clouds/ec2.py", line 2974, in _list_nodes_full
instances['error']['Errors']['Error']['Message']
SaltCloudSystemExit: An error occurred while listing nodes: AWS was not able to validate the provided access credentials
[DEBUG   ] Generating minion keys for 'test.example'
[DEBUG   ] MasterEvent PUB socket URI: ipc:///var/run/salt/master/master_event_pub.ipc
[DEBUG   ] MasterEvent PULL socket URI: ipc:///var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Sending event - data = {'_stamp': '2015-05-29T20:18:27.499650'}
[TRACE   ] get_event() received = {'tag': 'salt/event/new_client', 'data': {'_stamp': '2015-05-29T20:18:27.499650'}}
[DEBUG   ] Sending event - data = {'profile': 'default_profile', 'event': 'starting create', '_stamp': '2015-05-29T20:18:27.501392', 'name': 'test.example', 'provider': 'default:ec2'}
[INFO    ] Creating Cloud VM test.example in us-west-2
[DEBUG   ] MasterEvent PUB socket URI: ipc:///var/run/salt/master/master_event_pub.ipc
[DEBUG   ] MasterEvent PULL socket URI: ipc:///var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Sending event - data = {'_stamp': '2015-05-29T20:18:27.553621'}
[TRACE   ] get_event() received = {'tag': 'salt/event/new_client', 'data': {'_stamp': '2015-05-29T20:18:27.553621'}}
[DEBUG   ] Sending event - data = {'event': 'requesting instance', '_stamp': '2015-05-29T20:18:27.554473', 'location': 'us-west-2', 'kwargs': {'SecurityGroup.1': 'hdp_dev_default_security', 'ImageId': 'ami-65e8d755', 'KeyName': 'saltcloud', 'MaxCount': 1, 'Action': 'RunInstances', 'MinCount': 1, 'InstanceType': 'm1.large'}}
[DEBUG   ] Using AWS endpoint: ec2.us-west-2.amazonaws.com
[DEBUG   ] AWS Request: https://ec2.us-west-2.amazonaws.com/?Action=RunInstances&ImageId=ami-65e8d755&InstanceType=m1.large&KeyName=saltcloud&MaxCount=1&MinCount=1&SecurityGroup.1=hdp_dev_default_security&Version=2014-10-01
[TRACE   ] AWS Request Parameters: {}
[INFO    ] Starting new HTTPS connection (1): ec2.us-west-2.amazonaws.com
[DEBUG   ] Setting read timeout to None
[DEBUG   ] "GET /?Action=RunInstances&ImageId=ami-65e8d755&InstanceType=m1.large&KeyName=saltcloud&MaxCount=1&MinCount=1&SecurityGroup.1=hdp_dev_default_security&Version=2014-10-01 HTTP/1.1" 401 None
[DEBUG   ] AWS Response Status Code: 401
[TRACE   ] AWS Response Text:
AuthFailureAWS was not able to validate the provided access credentialse26c8e3b-06c4-4b08-9104-6f448ed55880
[ERROR   ] AWS Response Status Code and Error: [401 401 Client Error: Unauthorized] {'Errors': {'Error': {'Message': 'AWS was not able to validate the provided access credentials', 'Code': 'AuthFailure'}}, 'RequestID': 'e26c8e3b-06c4-4b08-9104-6f448ed55880'}
[ERROR   ] Error requesting instance: Errors
Error: There was a profile error: Failed to deploy VM
'''


how to install this plugin?

i first tried git clone https://github.com/TimeWarpEngineering/staruml-export-plantuml.git at C:\Users\<user>\AppData\Roaming\StarUML\extensions\user but StarUML's plugin manager didn't show this plugin.
This I tried moving timewarp-export-plantuml/ to C:\Users\<user>\AppData\Roaming\StarUML\extensions\user and deleting staruml-export-plantuml/, so that StarUML recognised this plugin.

However, when I clicked "export to PlaintUML" from the top menu bar, I only got
@startUML
@endUML

in the clipboard.

I had the same program. Turns out that your installation method works, it's just that the button doesn't do what we thought it did. It doesn't export the selected models; it exports the selected items in the model. You need to do Ctrl+A before exporting to select everything, and then it will work properly.

Hello I got the same problem even using ctrl+A...


Upgrading with start before stopping gets existing containers to unhealthy state since the new health check configs get applied to existing containers.

**Rancher versions: Build from 1.6 branch
Steps to reproduce the problem:

Create a stack with a service running nginx with a healthcheck on port 80.
Upgrade service with Start before Stopping selected and break the healthcheck (change to port 81)

Existing containers get to "unhealthy" state since the new incorrect healthcheck configs seems to be get applied to them.
Expected behavior:
Existing containers should continue to remain "healthy" state .

The issue is applicable to any upgrade; not just when start before stopping is used.

Tested with latest build from 1.6 branch and health check version - rancher/healthcheck:v0.3.4

Tested with v1.6.15-rc6.
Upgrading with new health check parameters (incorrect) does not result in existing containers to get unhealthy state anymore.


alisanli new intro

Checklists
General Checks

[ ] the branch is up to date with main/master
[ ] the code works when pulled and run locally
[ ] All CI checks pass
[ ] all conflicts are resolved (if any)
[ ] PR has a descriptive title
[ ] PR has appropriate labels and milestones for easy identification
[ ] PR it is assigned to the owner
[ ] reviewers are assigned
[ ] the PR contributes only one focused change
[ ] It is in the appropriate column in the project board (if necessary)
[ ] has short and clear description
[ ] is linked to an issue (if it is related)
[ ] feedback is addressed (if any and if it is appropriate feedback.)

Markdown

[ ] the markdown source is formatted
[ ] spelling and grammar is correct in all text
[ ] The markdown looks correct when you preview the file
[ ] all links and images work

HI, i am sorry ali, since the master branch was changed. You will have to clone the repo again and push your intro on the updated repo


Localization

Should we plan to use this app more widely?
Then we shouldn't limit ourselves to Czech. At least issues, TODO, code should be in English and interface should be i18n.

Yesterday we have talked about possible new course in English. It would be nice to have UI in English also.


 Can I continue scVelo proportion on my data.
scv.pl.proportions(adata,save="proportion.pdf")

The proportion of spliced and unspliced mRNA is 2:8, which  is just oppsite to the wanted condition of 8:2. Can I continue scVelo proportion on my data？
...

Hi @HuangDDU, is this single nucleus or single-cell data? It would be a very high proportion of unspliced reads in any case, but even more so for single-cell data. I wouldn't just continue but rather investigate whether something went wrong during alignment.

@Marius1311 Thank you for your reply! I got .loom file from .bam with velocyto and GENCODE reference mm10(https://www.gencodegenes.org/mouse/release_M1.html). I didn't use repeat.gtf, by which I can't run velocyto command successfully. Does repeat.gtf cause the worse condition,or can you tell me what's the function of repeat.gtf ? I appreciate it very much


Fix memory leak.

This changes the way message_ids are returned. Instead of being populated into the batch, they are returned sometimes (if a commit was triggered) in each publish.
Fixes #3505
This addresses the memory leak surfaced in: https://stackoverflow.com/questions/44542739/
This represents a backwards incompatible change, but I expect nobody was trying to read the message_ids since they were surfaced so poorly, and furthermore I am working on a client that supercedes this anyway.

The previous version stacked up a list with an ever-increasing list of strings on the class, so if you run a batch forever, the list keeps growing until you OOM.
This version returns the list, and if you do not actively store it yourself, then the garbage collector will eat it.

Note also that "run a batch forever" was not an intended usecase: PR #3157 (which added the max_size auto-commit) introduced that as a theoretical possibility, but it was never documented to be used so.

@lukesneeringer Shouldn't this be merged?

@dhermes it still lacks doc updates and test changes.

I am also not worrying about getting it in since we are trying to land an entirely new library this week that wipes it out anyway. Probably easier to close this than land it.


Suggestion: Longer (or more organized) note history

Hi! I have a suggestion that may actually be very difficult to implement and so might not be something you're interested in (as I realize that it's not necessarily what this plugin is meant to be good at), but I thought I'd give it a shot anyway and see if maybe other users are also interested in a feature like this.
The current way the file history is implemented, it keeps the last 100 revisions of a note. If you have your LiveSync set to sync with the server very frequently and you edit a note for a long time straight, though, this history doesn't actually span a very long amount of time, and usually will just contain all the changes from the last 30 minutes or so.
I know that the current implementation is mostly meant to allow automatic merging of file histories and the like, but I think it would be very nice to expand this feature to also allow a longer and more organized history for the user. Specifically, I was thinking something similar to the way Nextcloud handles its file history, which, by default, is as follows:

The versioning app expires old versions automatically to make sure that
the user doesn't run out of space. This pattern is used to delete
old versions:

For the first second we keep one version
For the first 10 seconds Nextcloud keeps one version every 2 seconds
For the first minute Nextcloud keeps one version every 10 seconds
For the first hour Nextcloud keeps one version every minute
For the first 24 hours Nextcloud keeps one version every hour
For the first 30 days Nextcloud keeps one version every day
After the first 30 days Nextcloud keeps one version every week

The versions are adjusted along this pattern every time a new version gets
created.

Obviously, LiveSync's version history doesn't have to use this exact pattern, but I think something similar would be very useful to people who might also be interested in keeping a log of the changes they have made to a file for a longer period of time.

Just another user here, I think the above is a good idea, and would also like to see unlimited history, if possible, just like git.
Would integration with something like obsidian-version-history-diff be possible?

It would be nice if seamless integration with obsidian-git (https://github.com/vrtmrz/obsidian-livesync/issues/232) is possible

Hi. Shouldn't that be a "backup"?
For example,

My "File recovery" setup is to keep a 45-day history every 5 minutes.

I also make backups several times a day for each desktop and mobile device, with generation management to HDD, FolderSync, etc. to cloud storage, etc.

Please also submit a Feature requests for the core plugin "File recovery" as well.
Latest Feature requests topics - Obsidian Forum
Since this topic is not related to Issues, it might be a good idea to move it to the Discussion section?

Hi. Shouldn't that be a "backup"?
For example,

My "File recovery" setup is to keep a 45-day history every 5 minutes.

I also make backups several times a day for each desktop and mobile device, with generation management to HDD, FolderSync, etc. to cloud storage, etc.

Please also submit a Feature requests for the core plugin "File recovery" as well. Latest Feature requests topics - Obsidian Forum
Since this topic is not related to Issues, it might be a good idea to move it to the Discussion section?

Is there a way in the interface to go back to a certain version of a note with the File Recovery plugin?


Fix QR card position

QR Code is overlapping with the landscape URL, see:

I moved the QR code and the text up, so they don't overlap. I've also tweaked the position of the elements so it looks like this now:

Looks great ty


Tweaks to connected apps docs

Follow-up to #902

And BTW we also need to add a doc page about the Connected Apps settings page

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

merging as i need to share it with a community member