Rewrite the readme and maintainers agreement, shorter, simpler, encodes existing practice slightly better

Best to look at the end results rather than the diff. For the README I've pulled out the bit most people care about (how do I add my package) to the top, and pushed the technical details of adding into the maintainers agreement - better put them in a document they are required to read anyway.
For the maintainers agreement, I've simplified it a lot, and changed some of the time limits gently to follow what I think you are really doing. I've said basically 3 days for anything, unless it's a major version bump, in which case you have 3 days to say you need more time. The result is about 1/3rd shorter and I included some friendly "we're not a police state" type cuddly language at the bottom, which is what I see going on in practice, but was actually missing from the original doc.

I made some minor comments on things that could be improved, which actually all applies to the current text being out-of-date. As for the maintainers agreement itself, I'm mostly in favor of the changes. Some thoughts:

We may want to clarify that while PVP upper bounds are not encouraged or required, they also aren't discouraged, since people seem to like to make large flamewars out of the language around that.
It's worth adding a new piece of advice: if your library depends on a C library, add a note to your pull request about the Ubuntu library name, or even better edit the debian-bootstrap script directly
I'm not sure how realistic 3-day turnaround will be in practice. I'm OK with changing the language, though.

Do any other curators have feedback on this? (Pinging @bergmark, @DanBurton, @juhp).

I've toned down the PVP language (which was already toned down from what is currently there). Agreed, not the place for a flamewar.
C language remarks seem sensible.
For 3 day turnaround, note that the current document says 24 hours for some things, which I certainly think is unreasonable. I'd be OK with making every instance of 3 days into 1 week, which adds some flexibility about work-week vs calendar-week should it be required, and supports weekend-only coders.

I'm OK with one week, and definitely reflects reality more closely (we've allowed far more than a one-week turnaround in the past).

1 week sounds like a good guideline to me.  I think some people get scared away by the apparent high expectations (including PVP) set by the "Maintainers Agreement": good will and trust are important too for keeping Stackage moving smoothly with the community. :-)

I've switched to 1 week minimum.

@snoyberg - do you want me to make those edits about C packages, Travis use etc, or do you want to do it? (I'm happy to, but don't really know much beyond what you've said above, so you might be able to make it clearer/better.)

If you can add it here, even as just a TODO for future expansion, that would be great. Once it's merged in, we can always work on improving it.

For getting new packages added a very common problem is that test modules are missing from other-modules. multi-ghc-travis may check this but I think it's worth mentioning this explicitly anyway. To check this locally do cabal sdist && cabal unpack dist/package-*.tar.gz && cd package-* && cabal install --enable-tests && cabal test.
I think a week is reasonable as well but it may also mean a lot of packages will get kicked out. That will mainly punish users that depend on these packages. So far we've usually only excluded packages when unupdated packages get us into dependency hell.
One idea I had is to include certain packages in LTS only. These maintainers will then only need to update their packages every N months. Currently we don't have an easy way to do this afaict.
Another thing I'd stress but I don't think we should require: If library maintainers make sure to support at least two major versions of all dependencies we would lessen the cascading effects of a major release.

Note that the requirement in the new document isn't 1 week then kicked out - it's 1 week, and then if it's causing problems elsewhere, maybe kick it out. Once something is causing issues you have to upset someone, and it's not really fair to upset the person working hard.
For the requirement to sdist/unpack, I already do that in my travis scripts, one approach would be to introduce a stack travis target that did exactly that, or a --from-sdist flag to test.
You guys are certainly in charge of Stackage, but as a user, my 2p on LTS: I don't think LTS adds any value (unless you believe in upgrading without testing your code and think 0.0.1 bumps are blessed with goodness while 0.1 bumps attack you while you are sleeping), so having packages in LTS but not nightly costs people using nightly, which I think should be everyone. If you didn't have all the packages in nightly then producing an LTS would also be significantly more work. My experience of having lots of packages on Stackage is that I get pinged less often than there is an LTS, so I'm not sure it's even a time saving for maintainers.
For supporting more versions, testing on older versions of every package induces an O(n^2) problem. If supporting older versions requires CPP, then it's probably a bad trade-off to make. I'm not sure there is any great scope to do better than people already do by default - but concrete tips might help (perhaps there's a blog post of advice from Stackage admins to Stackage maintainers - or a separate document from the maintainer guide).

All the suggestions from @snoyberg are now applied, apart from perhaps directing people to Stack more forcefully - I still think the stackage project should direct people to the stackage website, and then let the Stackage website do whatever user-facing pointers is required. In future, I suspect the stackage website and stack tool probably want their web presences integrating in some way.

I'm good with this. Let's wait till Tuesday afternoon my time to give a full 24 hours of this PR being open before merging, in case any other curators or interested parties want to comment. Thanks for doing this cleanup!

Hearing no objections, so merging. Thanks!


Does not support extensions

I'm using nested extensions to simulate polymorphic messages as decribed here: http://www.indelible.org/ink/protobuf-polymorphism/
It would be great if beefcake could support them, right now it just ignores the extensions.
Thanks

Thank you for the feedback. The Beefcake codebase is simple and easy to extend, a few others have shown this to be true, and we always appreciate patches. If you can slip one our way, we would love to see it.
Sincerely,
-The beefcake team
On Nov 20, 2011, at 1:22, Jim<EMAIL_ADDRESS>wrote:

I'm using nested extensions to simulate polymorphic messages as decribed here: http://www.indelible.org/ink/protobuf-polymorphism/
It would be great if beefcake could support them, right now it just ignores the extensions.
Thanks

Reply to this email directly or view it on GitHub:
https://github.com/bmizerany/beefcake/issues/17

Any chance to support extensions?

@noff This library is effectively unmaintained at this point. If you want to fork it and build the feature yourself, that'd be excellent, but that's probably the only way it's going to get added.


Deployer doesn't pick up cached binaries

Deployer: 6.4.6
OS: Ubuntu 18.04 LTS
npm: 5.6.0
node: 8.11.4
Hello, when deploying with deployer my npm install takes 157s, but when I tried to recreate that step when ssh'ed (with the same user) it took 13~s when node_modules are in place, when not(30s) and during deployer's npm install I have the node_modules present.
it seems that the issue is some kind of cache not working when using deployer.
when doing manually:
npm install

><EMAIL_ADDRESS>install /var/www/site/releases/4/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/deployer/.npm/node-sass/4.8.3/linux-x64-57_binding.node

when using deployer:
➤ Executing task npm:install

[dev] > cp -R /var/www/site/releases/6/node_modules /var/www/site/releases/7/node_modules
[dev] > cd /var/www/site/releases/7 && npm install
[dev] < ><EMAIL_ADDRESS>install /var/www/site/releases/7/node_modules/node-sass
[dev] < > node scripts/install.js
[dev] < Downloading binary from https://github.com/sass/node-sass/releases/download/v4.8.3/linux-x64-67_binding.node
[dev] < Cannot download "https://github.com/sass/node-sass/releases/download/v4.8.3/linux-x64-67_binding.node":
[dev] < HTTP error 404 Not Found
[dev] < Hint: If github.com is not accessible in your location
[dev] <       try setting a proxy via HTTP_PROXY, e.g.
[dev] <       export HTTP_PROXY=http://example.com:1234
[dev] < or configure npm proxy via
[dev] <       npm config set proxy http://example.com:8080

when doing manually it picks up the cached binary and when doing via deployer it doesn't - not sure why this happens - is it possible am I missing some environment variables when deploying with deployer?

I guess I should have mentioned that my deployer is running remotely on a jenkins CI server
Also,  looks like the problem and possible solutions are discussed here:  https://github.com/sass/node-sass/issues/2133

@antonmedv Can I close this issue since @neorganic isn't responding?

Sure.


⚠ Bofrost.de has degraded performance

In fd91134, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1219 ms

Resolved: Bofrost.de performance has improved in 97e9d41 after 7 minutes.


Content: How to migrate from Node-RED to FlowFuse device

Description
As a customer it might be great to learn how to migrate a self-managed and self-hosted Node-RED to a FlowFuse managed Node-RED and how that flow works for both edge devices and remote instances.
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate

cc @sumitshinde-84 @Hasmin-AC


Spatial scale bar units incorrect

Describe the bug
When zooming, the units in the spatial scale bar are not updating correctly.
To Reproduce
Steps to reproduce the behavior:

go to https://portal.hubmapconsortium.org/browse/dataset/b1b4493122e8965e3684b0a7a5dd270a
zoom in or out enough to jump to a new unit

Expected behavior
The unit suffix nm should change to pico- or micro-meters after zooming sufficiently
Screenshots
If applicable, add screenshots to help explain your problem.

Environment:

Release or git hash: v1.1.17
Browser: Firefox developer edition
Browser version: 95.0b10

Ok this seems like a vitessce issue genuinely. Just tried opening this in avivator and had no issue.

Ah ok, I see the issue.  Too many digits being trucated.....

Not sure if this is related, but I noticed the values are missing in http://vitessce.io/#?dataset=neumann-2020

Seems like the issue is localized to only the vitessce.io page since the issue isn't present anywhere else like here for example or the data portal

Fixed by https://github.com/hms-dbmi/viv/pull/694


Fix libseccomp not working in travis

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>Lets see if this fixes travis ci.

Wait, how did this fix it? We run the Travis tests in containers, so why does having libseccomp on the host matter?

Wait, how did this fix it? We run the Travis tests in containers, so why does having libseccomp on the host matter?

@mheon The dests passed on travis.

bot, retest this please

@mheon This is failing during the build phase not in the test phase.  Doesn't this happen outside of the container.

@rhatdan I think everything on Travis that is not lint and gofmt should be running in a container

@jlebon @cevich Any idea what the
Fedora fedora/27/cloud Podman — An internal error occurred.

is all about?

@rhatdan CI infra has the hiccups this morning.

@rhatdan what jlebon said.  Those status messages come from the underlying tooling, so in this case papr (or it's executor) literally posted that it back to github.


finished the suggestion form component

Added in the suggestion form component. Currently, the button causes an alert to display at the top of the screen and clears out the two input boxes on the component. It may need a bit more work with the CSS overall to make it look nicer if we want to.

I think it looks good. Thanks for fixing up the code since for some reason my laptop refuses to go on light mode now so I can't really check that

No problem, I was able to switch to dark mode on windows by searching dark mode in settings then changing dark mode for apps, if you need a fix but not sure.


[Question] LoadBalanced user-info-uri

Hi, I'm giving a try on Brixton.M1 and just get stuck on SSO.
At Angel.SR3 version I was able to get User info using loadbalancer with the following configuration:
spring:
  oauth2.resource:
    userInfoUri: http://security/user
    loadBalanced: true

In the Brixton.M1 I've tried the following:
security.oauth2.resource:
  user-info-uri: http://security/user

Looking at ResourceServerProperties class I didn't found the loadBalanced property, will it no longer be available, or am I missing something?

I'm closing this issue because it was a misconfiguration.


Restoring: better handling of snapshots/volumes if PV already exists

If a PV already exists in the cluster, trying to create a volume from the snapshot will succeed, but we won't be able to create the PV. We need better handling of this situation.

From a discussion, we talked about the following new behavior when a snapshot exists:

Before executePVAction check if PV already exists before attempting restore. Error/log if it exists and continue.
PVC won't be present in the pvsToProvision.

Closed by #1002, #1011


Modify BuilderExtensions.UseMvc to not add any routes by default

Fixes #1879

:shipit: after minor fixes

Updated

:shipit:


UP-4703 Updated security.properties to use ${environment.build.cas.context}

https://issues.jasig.org/browse/UP-4703

Coverage decreased (-0.002%) to 22.869% when pulling cbd60a2a72e130be3c7781529535290bf017c864 on jonathanmtran:UP-4703 into 47247bdb315d3715b5a9f9c840d25ac87af56332 on Jasig:master.

@jonathanmtran : This is already done in this PR #688

@jgribonvald I'll close this and note your pull request in UP-4703. Thanks!


[test client] New 0.15.0 test_client fails to fetch URL

Hi,
My tests began to fail when using 0.15.0.
I've got a routing rule:
<Rule '/users/action/<name>/<pk>' (OPTIONS, HEAD, GET) -> UserDBModelView.action>

but test_client returns 404:
client = self.app.test_client()
rv = client.get('/users/action/resetmypassword/1', follow_redirects=True)
...

When using 0.14.1 the test succeeds
Can you help?

Hi,
I think this linked with the redirection now returning a 308 code instead of 301 in version 0.15..
For us, it seems that redirect code 308 generate an error with request done with urllib2 while code 301 (returned in version 0.14) is handled with a redirection.

No, I get a 404 not found

I cannot reproduce this issue as described. Be sure to include a minimal example demonstrating an issue when reporting it.
from werkzeug.routing import Map, Rule
from werkzeug.wrappers import Request, Response
from werkzeug.test import Client

url_map = Map([Rule("/users/action/<name>/<pk>", endpoint="users.action")])

@Request.application
def app(request):
    adapter = url_map.bind_to_environ(request.environ)
    endpoint, view_args = adapter.match()
    return Response(endpoint)

c = Client(app, Response)
rv = c.get("/users/action/resetmypassword/1", follow_redirects=True)
assert rv.status_code == 200


Remove container border

I've dug around quite a bit, but it appears Structurizr won't allow us to remove a container border. Is that true?
https://structurizr.com/dsl
https://github.com/structurizr/dsl/blob/master/docs/language-reference.md#styles
I might be using the DSL wrong, but I'm trying to share components between views, so I want to remove the border for that purpose.
If there's a better way, I'm all ears.

I'm not quite sure what you mean by "remove a container border" ... can you elaborate, perhaps with an example of what you're trying to achieve?

Sure thing, I'm looking to set the border length to zero on this dotted line represented by this code.
        3Dto2DRenderer = softwareSystem "3D to 2D Renderer" "" "customization,tools3d,solution" {
            3Dto2DRenderingSolutionHubble = container "3D to 2D Rendering Solution (Hubble)" "" "" "Customization,Customization Tools and 3D,Solution" {
                GPUOptimizedInstances = component "GPU Optimized Instances" "Either G4dn (NVIDIA), g5 (NVIDIA), G4ad (AMD) instances. - Amazon has stated that the G5 instance is cheaper with better performance." "" "Customization,Customization Tools and 3D,Vendor,AWS"
                ...more code...

I'm guessing this is a component diagram for the "3D to 2D Rendering Solution (Hubble)" container ... so that dark dotted line represents the container boundary, and cannot be removed. It's possible to remove the light grey dotted line, but that doesn't seem to be what you're asking, as I don't see it represented in the code fragment you posted.

Thanks for confirming that it's not possible to remove the border.
I haven't seen an example of model reuse that works for my use case.
Can we scope relationships so they only show up in specific views?
I'm looking at this issue, which is an interesting example of includes, but it's not meeting my use case. My use case may not exist based on Structrizr's current design.
Please bear with me, as I still have a limited understanding of the Structurizr DSL and the C4 Model.
To describe what I'm looking for as simple as I can, here is some code:
workspace "Reuse model with different relationships?" "Incorrectly Demonstrate Model Reuse, is something like this possible?" {

    model {
        customer = person "Customer" "Customer" "Customer"
        website = softwareSystem "Website" "Website" "Website"

        system1 = softwareSystem "system1" "" "" {
            customer -> website "Relationship scoped to system1"
        }

        system2 = softwareSystem "system2" "" ""  {
            website -> customer "Relationship scoped to system2"
        }
    }

    views {
        systemContext system1 {
            include customer
            include website
            autoLayout
        }

        systemContext system2 {
            include customer
            include website
            autoLayout
        }
    }
}

As it stands, the relationships show up in both systemContext views, and I want them to only show up on one of them.

You could just exclude the relationships, either by identifier (as in the example below), or by tag.
workspace "Reuse model with different relationships?" "Incorrectly Demonstrate Model Reuse, is something like this possible?" {

    model {
        customer = person "Customer" "Customer" "Customer"
        website = softwareSystem "Website" "Website" "Website"

        system1 = softwareSystem "system1" "" "" {
            rel1 = customer -> website "Relationship scoped to system1"
        }

        system2 = softwareSystem "system2" "" ""  {
            rel2 = website -> customer "Relationship scoped to system2"
        }
    }

    views {
        systemContext system1 {
            include customer
            include website
            exclude rel2
            autoLayout
        }

        systemContext system2 {
            include customer
            include website
            exclude rel1
            autoLayout
        }
    }
}

Thank you!


terraform validate should not require an api_key

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version
Terraform v1.2.4
on darwin_arm64
+ provider registry.terraform.io/cloudflare/cloudflare v3.19.0

Affected resource(s)
the cloudflare provider
Terraform configuration files
provider "cloudflare" {}

Debug output
n/a
Panic output
No response
Expected output
Success! The configuration is valid.

Actual output
│Error: Invalid combination of arguments
│
│  with provider["registry.terraform.io/cloudflare/cloudflare"],
│  on versions.tf line 11, in provider "cloudflare":
│  11: provider "cloudflare" {
│
│"api_key": one of `api_key,api_token` must be specified

Steps to reproduce

Define the cloudflare provider with any env var and api key
Run terraform validate

Additional factoids
Terraform validate is used to check the syntax of terraform files, and should not require an api key or token to run. It was not the case until v3.19.0 and it's not the case for all the other providers that we use.
References
No response

thanks for the issue but I'm afraid the validation is here to stay for now. it is intentionally cleaning up use cases where people are providing incorrect or mismatching credentials resulting in hard to diagnose issues with their setups.
if you'd like to noop the validate, you can provide fake credentials either in the provider block or via the environment variables for the keys.

This is the only provider with this behavior, and we use a lot.
We had to do a special case just for cloudflare so I'm betting this behavior will lead to more new issues open than you hope to prevent.

:wave: So I have the same issue with validate, but for a different reason.
Per the docs, api_key is deprecated, and api_token should be used instead (https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs), but validate fails even if I've specified the provider as documented:
    new cloudflare.CloudflareProvider(this, "cf", {
      email: Fn.lookup(Fn.jsondecode(cfToken.secretString), "email", ""),
      apiToken: Fn.lookup(Fn.jsondecode(cfToken.secretString), "token", "")
    });

When I validate this, I get:
Error: Missing required argument
│
│   with provider["registry.terraform.io/cloudflare/cloudflare"],
│   on cdk.tf.json line 115, in provider.cloudflare[0]:
│  115:         "email": "${lookup(jsondecode(data.aws_secretsmanager_secret_version.token.secret_string), \"email\", \"\")}"
│
│ "email": all of `api_key,email` must be specified

My TF synthesizes and applies fine, but validation is broken in 3.19
Initializing provider plugins...
- Reusing previous version of hashicorp/random from the dependency lock file
- Reusing previous version of hashicorp/aws from the dependency lock file
- Reusing previous version of cloudflare/cloudflare from the dependency lock file
- Using previously-installed hashicorp/random v3.3.2
- Using previously-installed hashicorp/aws v4.20.0
- Using previously-installed cloudflare/cloudflare v3.19.0

see #1768


Chocolatey Package Scanning takes long time

WIN 1909
Latest Chocolatey
Tested Reinstall of application not working.
My list of chocolatey apps is only around 15.

Duplicate of #248
Before a fix is available you can turn off chocolatey scan in settings.


Register/Update didcomm resolver

Looks like we need to rebase on main; 41e0ff9..cee6b67 should already be present -- I'm kinda confused why it's showing up in this branch's history. Might be because you branched from the test/demo?

Hmmm I don't know why it is happening. However, I think the best option is to close this PR and cherry-pick my commits into other PR (PR18)


feat: Add handling for Swift Testing Only Parallelization

Related to this Tuist issue
Short description 📝
This PR introduces XcodeProj Parallelization handling for the new Swift Testing option. This will enable us to expose the option to Tuist TestingOptions allowing users to specify the option they need, as the default handling in Xcode 16 for Parallelization is going to benefit the few users who have adopted Swift Testing.
I also removed two dead links from the References section as I was going through the reading material.
Solution 📦
From changing the values manually in a real project, I gathered:

Parallelization off in Xcode ->"parallelizable" : false,
Parallelization on in Xcode ->"parallelizable" : true,
Parallelization Swift Testing Only in Xcode -> no value.

With guidance from @fortmarek , I updated the handling of the attributes to cover each individual case.
I've set it as draft as I need guidance on how to prove this handling outside of unit tests. Please let me know what I could be missing and how to verify the output. Thanks.
Implementation 👩💻👨💻

[x] Introduce enums to cover the three unique cases
[x] Add handling for each case from.
[x] Update tests to handle each case.

@kelvinharron we can merge this one once the CI is green ✅

Anything preventing us from moving forward? Would love to have swift-testing at our disposal :D
@kwridan @fortmarek

This looks good! I'd wait with the merge until the Tuist PR counterpart is approved as well: tuist/tuist#6898

Thanks Marek. I still haven't found a way to reliably prove out the tests for that PR meaning its a non starter. @freak4pc care to look at the PR and see if you have any ideas? Some more context on Slack here.

Thanks Marek. I still haven't found a way to reliably prove out the tests for that PR meaning its a non starter. @freak4pc care to look at the PR and see if you have any ideas?

I don't have extra ideas apart from what I posted. Feel free to simplify the acceptance test if needed.
However, I think we can merge this one without having a Tuist acceptance test in place once the CI is ✅

@kelvinharron your changes are now part of XcodeProj 8.25.0


Migrate InstrumentedHandler to Scala

It's a direct port from Java, so not pretty.
There is little idiomatic Scala, let me know if you want less null and more nice.

I'd say more nice or more package protected, and would lean toward the latter.  I can live with the nulls, but I'd like to hide our shame from public API.

I could update the var null to be  :
private lazy val requests:Timer = registry.timer(registryName(prefix, "requests"))
If we define prefix to be  private lazy val prefix = _prefix.fold( registryName(getHandler().getClass(), name) )(p => registryName(p, name))
where _prefix is the case class val.
It would be nice to know where and when name is set.
On 26 June 2015 at 13:29, Ross A. Baker<EMAIL_ADDRESS>wrote:

I'd say more nice or more package protected, and would lean toward the
latter. I can live with the nulls, but I'd like to hide our shame from
public API.
—
Reply to this email directly or view it on GitHub
https://github.com/http4s/http4s/pull/317#issuecomment-115489102.

Looks like it can be called optionally before the lifecycle method doStart is invoked.

:+1:


Innovation Engine Port & API (WIP)

This PR is a port & expansion of the innovation engine to support our desired usecases.
Changes included are:

Rewrite innovation engine from python -> golang.
Better output formatting for executing scenarios.
Makefile for centralizing build & deployment steps.
An API for spawning runners to carry out the execution of scenarios.
Docker files & Kubernetes configurations for infrastructure.

At the time of this comment environment variables are not handled which means none of the scripts work as expected. There is a test for this, output below. To repro:

./bin/ie execute testScripts/variableHierarchy.md
Expected output is that the environment variables are set and echoed
Actual output (see below) is that environment variables are not set and echo is not executed.

$ ./bin/ie execute testScripts/variableHierarchy.md
INI file exists. Loading:  testScripts/variableHierarchy.ini
Setting MY_VARIABLE_NAME=VariableFromIni
Setting MY_RESOURCE_GROUP=SetInINI
Found HTML block with the content: <!---
```variables
export MY_RESOURCE_GROUP=setInComments
export MY_VARIABLE_NAME=commentVariable

Found variable: MY_RESOURCE_GROUP=setInComments
Found variable: MY_VARIABLE_NAME=commentVariable
Found scenario: The following will now declare variables locally which will overwrite comment variables
The following will now declare variables locally which will overwrite comment variables
1.
✔ echo $MY_RESOURCE_GROUP
echo $MY_VARIABLE_NAME
4. The following will now declare variables locally which will overwrite comment variables
✔ export MY_RESOURCE_GROUP=RGSetLocally
export MY_VARIABLE_NAME=LocallySetVariable
✔ echo $MY_RESOURCE_GROUP
echo $MY_VARIABLE_NAME
---Generated script---
export MY_VARIABLE_NAME="commentVariable"
export MY_RESOURCE_GROUP="setInComments"

echo $MY_RESOURCE_GROUP
echo $MY_VARIABLE_NAME
The following will now declare variables locally which will overwrite comment variables
export MY_RESOURCE_GROUP=RGSetLocally
export MY_VARIABLE_NAME=LocallySetVariable
echo $MY_RESOURCE_GROUP
echo $MY_VARIABLE_NAME


Add docker

subj

Is this to run a graph-node in a docker and to test it locally? Does it working?

@leonprou  Yes, I tested it and it works.


Set up CI and lint rules to taste

There should probably be some autoformatting and linting in this repo. As a setup task, the incoming interns should define the rules they would like to have in the CI flow and for running locally.

Look to see if Jennifer has already set something up. Phillip is DMing her on slack to ask

finished this past week


Dual URL function is unreachable

At line 184, Dual URL must be checked before Playlist url

I'd be happy to make Pull Request after confirmation of the issue.

I'm trying your script for the first time using all defaults. Initial run results in the following error:
param : The term 'param' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At D:\Scripts\yt-dlp\youtube-dl Easy Script.ps1:51 char:1
+ param (
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (param:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

After choosing option 1, I'm seeing this error:
I see this everytime, regardless of option chosen...
yt-dlp.exe : WARNING: [youtube] Skipping player responses from android clients (got player responses for video "aQvGIIdgFDM" instead of "K0v9hnn24y8")
At D:\Scripts\yt-dlp\youtube-dl Easy Script.ps1:216 char:5
+     & .\$downloader_exe --list-formats $URL
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (WARNING: [youtu... "K0v9hnn24y8"):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

I'm also seeing the script hang up here everytime:
[Metadata] Adding metadata to "Outputs\11 Cool Command Line Programs You Need to See.webm"
I noticed the Year property was populated with 55238
One other thing to note is that I have to close PowerShell after each test, as the download option never returns. It just downloads based on the option number I chose the first time.
Here we see the last line of options, and then it immediately starts downloading...
308     webm  2560x1440   60    |  421.48MiB  4403k https | vp<IP_ADDRESS>  4403k video only          1440p60, webm_dash

Running Command:   .\yt-dlp.exe  https://www.youtube.com/watch?v=K0v9hnn24y8 '--%' --no-mtime --add-metadata --ffmpeg-location "ffmpeg.exe" --output "Outputs\%(title)s.%
(ext)s" --ffmpeg-location "ffmpeg.exe" --output "Outputs\%(title)s.%(ext)s"
[youtube] Extracting URL: https://www.youtube.com/watch?v=K0v9hnn24y8
[youtube] K0v9hnn24y8: Downloading webpage
[youtube] K0v9hnn24y8: Downloading ios player API JSON
[youtube] K0v9hnn24y8: Downloading android player API JSON
yt-dlp.exe : WARNING: [youtube] Skipping player responses from android clients (got player responses for video "aQvGIIdgFDM" instead of "K0v9hnn24y8")
At D:\Scripts\_WIP\yt-dlp\youtube-dl Easy Script.ps1:248 char:1
+ & .\$downloader_exe $format $URL '--%' $options #Final full command u ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (WARNING: [youtu... "K0v9hnn24y8"):String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

[youtube] K0v9hnn24y8: Downloading m3u8 information
[info] K0v9hnn24y8: Downloading 1 format(s): 308+251
[download] Destination: Outputs\11 Cool Command Line Programs You Need to See.f308.webm

[download]   0.0% of  421.48MiB at  580.53KiB/s ETA 12:23

I've tried clearing the following variables at the beginning of the script, but that didn't solve the issue with auto-downloading.
$choice = ''
$ffmpeg_location = ''
$output_location = ''
$downloader_exe = ''
$other_options = ''

Thanks...


Traefik - Ingress weights not respected

Do you want to request a feature or report a bug?
Bug
What did you do?
I launch Traefik on K8S as Ingress controller on minikube and on Docker For Mac
I create 2 services (serviceA, serviceB) (with 3 replicas on each service)
I create 1 ingress with the following annotation
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    traefik.ingress.kubernetes.io/service-weights: |
      servicea: 30
      serviceb: 70
  name: ingress
spec:
  rules:
  - host: myhost.com
    http:
      paths:
       - backend:
          serviceName: servicea
          servicePort: 80
         path: /
       - backend:
          serviceName: serviceb
          servicePort: 80
         path: /

What did you expect to see?
Traffic should be forwarder to both services with a weight.
What did you see instead?
Traffic is only routed to the service that has more than 50% as weight. No traffic is routed to the other one. If put 50% on each service, traffic is routed to both services.
I can see on the Dashboard that weights are well configured.

Server | Weight
http://<IP_ADDRESS>:8080 | 10000
http://<IP_ADDRESS>:8080 | 10000
http://<IP_ADDRESS>:8080 | 10000
http://<IP_ADDRESS>:8080 | 23333
http://<IP_ADDRESS>:8080 | 23333
http://<IP_ADDRESS>:8080 | 23333

I tested also with one replicas for each service and I don't have the issue (weights are ok).
Output of traefik version: (What version of Traefik are you using?)
Tested on Traefik version 1.7.9 and 1.7.7
Kubernetes 1.13.2 (for minkube)

I'm getting the same issue too:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
spec:
  rules:
  - host: v1.local
    http:
      paths:
      - backend:
          serviceName: hello-v1-svc
          servicePort: 80
  - host: v2.local
    http:
      paths:
      - backend:
          serviceName: hello-v2-svc
          servicePort: 80

I'm putting 51% for v1 and I'm not getting a single request going to v2.

@pablokbs the annotation ingress.kubernetes.io/service-weights has been added in v1.7, before the annotation was ignored.

Gotcha, so it was balancing it 50/50 without me noticing, good to know. But basically it doesn't work since it was published (at least in my tests)

Is there any workaround for above issue?
I am also able to reproduce to issue for traefik:v1.7.11-alpine but it's still very intermittent. Out of 10 only once this issue has been occurred for me.

Hi @nagendra547 , there is no known workaround for now. We are working on this, but as the version 2.0 of Traefik is currently worked on, we have to wait :)

@dduportal Thanks so much for you reply. I have hit the same issue again.
Could you please provide some tips where are the things I can debug for root cause? So far I have been checking following
Traefik Dashboard
Traefik Ingress
Traefik  console Logs
but things are looking okay in all the above. Is there any way, I can put in debug mode to enhance the logging?

Able to reproduce in traefik:v1.7.9 too.

Hi @nagendra547 , as said earlier, the only way to fix this is to wait for Traefik v2.0 to be released.

Activating the issue again after five months. Routing respects the most weighted service in v1.7.
I was expecting to see an update about this issue on this page: https://docs.traefik.io/migration/v1-to-v2/ but it seems there aren't any.
@dduportal

Hi @Hmerac , could you try with the v2.1 RC please (https://docs.traefik.io/v2.1/ - Docker image traefik:2.1 which is RC2 currently)? This version introduced the CRD TraefikService (ref. https://docs.traefik.io/v2.1/routing/providers/kubernetes-crd/#services) which allows o define weighted loadbalancers  (ref. https://docs.traefik.io/v2.1/routing/services/#weighted-round-robin-service) ?

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
I have to close this one because of its lack of activity :disappointed:
Feel free to re-open it or join our Community Forum.

version: 1.7.24

I tried to reproduce and used the above modification to fix this problem。
Although the ratio is no longer accurate, there will be no traffic situation。
@dduportal  Can this be a workaround for v1.7.x ？thanks :)


Add default icons in font format

Add font family of core icons to allow for simple changing of color.

We could do something like this (based on Google's Material Icons):
const MaterialIcon = ({type}) => (
  <i className='material-icons'>
    { type }
  </i>
)

export const Icon = styled(MaterialIcon)`
  color: ${({color, theme}) => theme.palette[color] || color};
`

And used like so:
<Icon type='menu' />

But maybe <Icon> is better implemented at application-level, rather than in the library?


Added support for debian package

Changed pom to build a debian package

Consider adding a post install to remove it :)
Also, I would just put the directly into the into the plugin directory

awesome work, :+1:


IMAP

Hi all,
I would like to use the IMAP-module. I configured all the parameters and the emails are imported in the database. But I am not able to store the body of the email in the database.
Can someone give me please a hint how to do this.
thank you in advance
Roland

thanks @robreuer. Working on this now, unfortunately it's not completely trivial to implement but there would be an option for this next week

with the latest release (0.1.2 i think) of the IMAP module you now have plaintext and HTML body fields

thank you!
I really appreciate your efforts!
Roland


sov: init at unstable-2022-04-26

Description of changes
Sov - Sway overview. Its super neat: https://www.reddit.com/r/swaywm/comments/ubsw9a/swayoverview_is_released/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

nix-shell -p nixpkgs-review --run "nixpkgs-review pr 170459"
[xxx@xxx:~/projects/nixpkgs]$ NIX_PATH="nixpkgs=./" nix-shell -p nixpkgs-review --run "nixpkgs-review pr 170459"
$ git -c fetch.prune=false fetch --no-tags --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0 pull/170459/head:refs/nixpkgs-review/1
From https://github.com/NixOS/nixpkgs
 + 8d43c4ad900...ab35e3e6139 refs/pull/170459/head -> refs/nixpkgs-review/1  (forced update)
$ git worktree add /home/xxx/.cache/nixpkgs-review/pr-170459-1/nixpkgs 1c99518c6f804c0d23ff82a20904768f18512909
Preparing worktree (detached HEAD 1c99518c6f8)
Updating files: 100% (30304/30304), done.
HEAD is now at 1c99518c6f8 Merge pull request #170444 from mdlayher/mdl-corerad-120
$ nix-env --option system x86_64-linux -f /home/xxx/.cache/nixpkgs-review/pr-170459-1/nixpkgs -qaP --xml --out-path --show-trace
$ git merge --no-commit --no-ff ab35e3e6139426146291319a2c4128b90833faba
Auto-merging pkgs/top-level/all-packages.nix
Automatic merge went well; stopped before committing as requested
$ nix-env --option system x86_64-linux -f /home/xxx/.cache/nixpkgs-review/pr-170459-1/nixpkgs -qaP --xml --out-path --show-trace --meta
1 package added:
sov (init at 2022-04-26)

warning: ignoring the user-specified setting 'system', because it is a restricted setting and you are not a trusted user
$ nix --experimental-features nix-command build --no-link --keep-going --option build-use-sandbox relaxed -f /home/xxx/.cache/nixpkgs-review/pr-170459-1/build.nix
warning: ignoring the user-specified setting 'sandbox', because it is a restricted setting and you are not a trusted user
building '/nix/store/i7md3aqvl6wy49jc17vwjga7akiqwybs-sov-unstable-2022-04-26.drv'...
building '/nix/store/bdzkcq046ylyaczq7yfcq8vfyz1ysz47-review-shell.drv'...

Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/170459

1 package built:
sov

$ nix-shell /home/xxx/.cache/nixpkgs-review/pr-170459-1/shell.nix

Hmmm not sure whats up with aarch64-darwin - this is Linux so that should be skipped?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/1016/13

Result of nixpkgs-review pr 170459 run on x86_64-linux 1

1 package built:

sov

Heads up just merged version 0.71 of this

#174492


FLW-650 Update background and Splash screen

Good job!
Here the list we still need to fix:

On the account list screen: fix table view bottom inset and font of the action button (it should be bold)
On the account info screen: fix action button font
On the network management screen (Settings -> Profile -> Network): replace actions button as we did for account list screen;
Action button in the wallet's send flow: located in the WalletSingleActionAccessoryView.xib
Also I think it will be consistent to replace colorHighlightedBlue for new accent highlighting color. Current I see use case only for DetailsTriangularedView


The term 'Get-SsasSourceConnectionString' is not recognized as a name of a cmdlet,

Calling the Publish-Cube
The term 'Get-SsasSourceConnectionString' is not recognized as a name of a cmdlet, function, script
| file, or executable program. Check the spelling of the name, or if a path was included, verify that
| the path is correct and try again.
Looks it is only being called on Update-AnalysisServicesConfig.ps1, should this reference be something else?

One partial work around it appears would be to delete the .configsettings file.... if you just want to have the script run

I found the missing script from the library and added it to my copy of the module here was the link https://www.powershellgallery.com/packages/DeployCube/<IP_ADDRESS>68/Content/public\Get-SsasSourceConnectionString.ps1


Don’t register multiple times

self.registeredCollectionViewCellReuseIdentifiers was being set up and checked for an existing cell reuse identifier, but we never added the identifier to the collection to stop us registering multiple times.

@spotify/objc-dev

👍

Codecov Report

Merging #278 into master will increase coverage by -0.02%.

@@            Coverage Diff             @@
##           master     #278      +/-   ##
==========================================
- Coverage   93.46%   93.44%   -0.02%
==========================================
  Files          72       72
  Lines        5046     5047       +1
==========================================
  Hits         4716     4716
- Misses        330      331       +1

Impacted Files
Coverage Δ

sources/HUBViewController.m
89.06% <100%> (+0.01%)
:white_check_mark:

sources/HUBUtilities.h
78.26% <ø> (-1.09%)
:x:

Continue to review full report at Codecov.

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


feat: add withHeader story

Closes #2520
Description
I noticed that the 'withFooter' story already exists, so I only added the 'withHeader' story.

feat: add withHeader story

Current behavior (updates)
https://github.com/user-attachments/assets/d1ca21e7-0c07-4298-9315-30dccb8623d1
New behavior

Is this a breaking change (Yes/No):

Additional Information

I seem to have misunderstood! I will correct it.

Close the current PR and submit a new one.


Fix missing esm dist

This issue occurs when using Rollup as it uses the module field in package.json, which points to a non existing path.
I think the build step was missing the esm build which I just added.
Furthermore, I removed @typings in favour of @types.
Note that I left the version intact as I did not know for sure how the package is published.

@dwieeb do you think we could get this merged in and published to NPM?

@rolandjitsu I took one of your commits but I found out typings isn't actually required to build anymore, so I made a few commits of my own in the spirit of yours.
Thanks so much! I published 0.10.0. Let me know if you have any more issues.

I'll give it a try and let you know.


py312 whl support

hi，currently there's no python3.12 wheel
released, will you  consider release the official build?

This is a good point.
I'll see if we can have a python3.12 wheel in the next release.

Support for Python 3.12 was added in ydf 0.4.3.
The linux wheel was released today. The windows and wheels will follow.


Basic Docs

[x] update README.md
[x] move documentation readthedocs.org
[x] issue templates
[ ] add tutorial

Will update README tomorrow, removing experiment info and commenting on limitations (primarily DHT ones). Feel free to add our change when I'm done.

Created a branch with updated README.

Master branch currently has all the technical stuff that's required for documentation. We can now accumulate the actual content for documentation, tutorials, templates, etc.
I'm closing this issue and distributing what's left to more specific ones (e.g. about quickstart tutorial, about templates, etc.)


[Event Request] Codeunit 90 "Purch.-Post" – New Event “OnBeforeInsertReturnShipmentLine”

[Event Request] Codeunit 90 "Purch.-Post" – New Event “OnBeforeInsertReturnShipmentLine”
Could we please have an new publisher “OnBeforeInsertReturnShipmentLine” with Handled Pattern at the very beginning of the procedure InsertReturnShipmentLine in Codeunit 90 "Purch.-Post"?
The publisher should be modelled like the existing publisher "OnBeforeInsertReceiptLine".

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Emojipedia Sample Images (Request)

Hello,

could you add Emojipedia Sample Images as a font in the future? I’d love to use them instead of Apple emojis.

Back to the original request, where did you get the Emojipedia emoji images?

Just to let you know that Emojipedia doesn't contain the old emojis from 2015 onwards, so you'll probably need to keep some old emojis along with Emojipedia Sample Images, Emojipedia is responsible for releasing previews of new emojis ahead of the Android, iOS and Windows operating systems.

You can swipe to see emojis from other periods, click on them and then press to open the image in a new URL and the image will be downloaded in 512x512.
Here you go: https://emojipedia.org/en/emojipedia

Emojipedia started releasing emojis with its own design in 2016


Add a page for collectors to guide

A thorough explanation of:

What are collectors?
How collectors work?
Types of collectors

Message collectors
Reaction collectors

Appropriate scenarios where collectors are suitable
An example command utilizing collectors

If you are interested in taking this, please leave a comment.

Is there any place to find this information? Even if not in a proper documentation format, but somewhere I could read some code or conversation regarding it?

There is no documentation about Collectors. Also Discordeno Collectors are more a boilerplate thing so the code is there: https://github.com/discordeno/boilerplate/blob/master/src/utils/collectors.ts If you have any other questions feel free to join our discord server: https://discord.gg/5vBgXk3UcZ


Enable worldwide access to apps in prod/stage

What
This PR allows worldwide router access on Staging and Prod so tenants can actually have non-GDS people use them. Staging is exposed so that we have an identical environment to Prod being tested before changes are deployed in Prod.
How to review
Ugh. Modify your terraform/dev.tfvars file to have the same web_access_cidrs = "<IP_ADDRESS>/0" line that is now in staging.tfvars and prod.tfvars, then deploy your environment with it.
Push an example application such as the one in our tests.
From a host external to the GDS office curl the application and check that it works. If you don't have something to SSH to or a VPN you can use, go to a coffee shop.
Who can review
No @HenryTK or @jonty.

works


Add option for single-isolate

Add an option to not spawn a new isolate on every new message, but instead re-use the existing main isolate

I think fixing this would also fix #3. I'll try to get it working.

(original: https://github.com/karmanyaahm/flutter_unified_push/issues/6)

It should be fixed now. It uses the main isolate until the app is destroyed and then goes to a new callback isolate

It should be fixed now. It uses the main isolate until the app is destroyed and then goes to a new callback isolate


Include install-crd as a prerrequisite of install-cr make command

Closes #127

i am pretty sure there is a reason I did not do this when I originally wrote that. Let me look and see why. Do not merge yet.


Correct Neuroconv Schema Inconsistency

This PR extends #406 to see if we could get a successful conversion to run by fixing the GUIDE's interpretation of the returned schema. Transforming the schema so the anomalous properties field in a array type is transformed into the items fields works to allow conversions.
Note: The NWB Inspector doesn't like the resulting file, though, as the following error is thrown:
[main-process]: [2023-09-29 11:59:28,094] ERROR in app: Exception on /neuroconv/inspect_file [POST]
Traceback (most recent call last):
  File "/Users/garrettflynn/Documents/Github/nwb-guide/pyflask/apis/neuroconv.py", line 150, in post
    list(
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/nwbinspector/nwbinspector.py", line 555, in inspect_nwbfile
    validation_errors = pynwb.validate(io=io)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/utils.py", line 648, in func_call
    return func(**pargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/pynwb/validate.py", line 132, in validate
    validation_errors = _validate_helper(io=io, namespace=namespace or CORE_NAMESPACE)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/pynwb/validate.py", line 29, in _validate_helper
    return validator.validate(builder)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/utils.py", line 644, in func_call
    return func(args[0], **pargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 250, in validate
    return validator.validate(builder)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/utils.py", line 644, in func_call
    return func(args[0], **pargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 425, in validate
    errors.extend(self.__validate_children(builder))
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 451, in __validate_children
    yield from self.__validate_child_builder(child_spec, child_builder, parent_builder)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 500, in __validate_child_builder
    yield from child_validator.validate(child_builder)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/utils.py", line 644, in func_call
    return func(args[0], **pargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 425, in validate
    errors.extend(self.__validate_children(builder))
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 451, in __validate_children
    yield from self.__validate_child_builder(child_spec, child_builder, parent_builder)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 500, in __validate_child_builder
    yield from child_validator.validate(child_builder)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/utils.py", line 644, in func_call
    return func(args[0], **pargs)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 388, in validate
    dtype = get_type(data)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/hdmf/validate/validator.py", line 129, in get_type
    return get_type(data[0])
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/h5py/_hl/dataset.py", line 831, in __getitem__
    selection = sel.select(self.shape, args, dataset=self)
  File "/opt/anaconda3/envs/nwb-guide/lib/python3.9/site-packages/h5py/_hl/selections.py", line 82, in select
    return selector.make_selection(args)
  File "h5py/_selector.pyx", line 282, in h5py._selector.Selector.make_selection
  File "h5py/_selector.pyx", line 151, in h5py._selector.Selector.apply_args
IndexError: Index (0) out of range for empty dimension

I too see that error in the dev console, but it ought to be caught by the inspector and rendered back as a ERROR type of inspector message

I can confirm this is still a problem with something regarding the NWB GUIDE modifying the default metadata of that interface
Running the conversion gallery: https://neuroconv.readthedocs.io/en/main/conversion_examples_gallery/segmentation/caiman.html
produces a file without validation issues (or errors)
My idea for the quick fix was just to pop Ophys from the metadata schema that gets returned to the front-end, and deep update what the front-end does succcessfully handle right now to the defaults during the run conversion step

Fixed. Just for our future reference, this was throwing an error on pynwb.validate because TwoPhotonSeries was auto-populated to have an empty array—of which the 0th index was attempting to be accessed (despite the schema not having a minItems entry).

Works great now!


Frequent Error Messages

Which OS are you using?
Windows
Expected Behaviour
I don't expect to see an error popup.
Actual Behaviour
Error popup appears citing text completion unavailable.
I also see the following error:
Retrieved Log
#### STARTUP ####
[2023-03-08 13:37:11] |   DEBUG   |     Filesystem     | Created directory at "/C:/Users/William/AppData/Roaming/Code/User/globalStorage/sumneko.lua/addonManager"
#### STARTUP ####
[2023-03-08 13:37:15] |   DEBUG   |     Filesystem     | Created directory at "/C:/Users/William/AppData/Roaming/Code/User/globalStorage/sumneko.lua/addonManager"
[2023-03-08 13:37:27] |   ERROR   |         Git        | Failed to checkout repo!
[2023-03-08 13:37:27] |   ERROR   |         Git        | fatal: unable to access 'https://github.com/LuaLS/LLS-Addons.git/': Could not resolve host: github.com

Reproduction steps
This error happens frequently and seems to occur when I am editing existing code.
It seems to be linked to breaking Lua syntax while editing.  For example, when this instance of the error occurred, I was removing files from a "sandbox" project because they were no longer needed.  Doing so caused a number of namespace globals to vanish, which caused the error.
Additional Notes
To be clear, this is an annoyance at worst.  I am posting this report in an effort to support your plugin, which is find to be invaluable.  Thank you for your hard work!
Log
STARTUP
[2023-03-08 13:37:11] |   DEBUG   |     Filesystem     | Created directory at "/C:/Users/William/AppData/Roaming/Code/User/globalStorage/sumneko.lua/addonManager"
STARTUP
[2023-03-08 13:37:15] |   DEBUG   |     Filesystem     | Created directory at "/C:/Users/William/AppData/Roaming/Code/User/globalStorage/sumneko.lua/addonManager"
[2023-03-08 13:37:27] |   ERROR   |         Git        | Failed to checkout repo!
[2023-03-08 13:37:27] |   ERROR   |         Git        | fatal: unable to access 'https://github.com/LuaLS/LLS-Addons.git/': Could not resolve host: github.com

It seems you are reporting two issues here. The log file is from the addon manager, which cannot connect to LLS-Addons. This is maybe just a temporary disruption, or some other networking issue. I have added some commits that make simple connection issues less dramatic, which should be released soon.
The error of completion becoming unavailable is likely related to https://github.com/LuaLS/lua-language-server/issues/1978

@sumneko can you make a new release of the extension, when possible, please 🙂

@sumneko can you make a new release of the extension, when possible, please 🙂

Today

Facing the same issue on Mac OS 12.6.
For past few days , the addon fails to load.
#### STARTUP ####
[2023-03-09 06:38:33] |   DEBUG   |     Filesystem     | Created directory at "/Users/shriharip/Library/Application Support/Code/User/globalStorage/sumneko.lua/addonManager"
[2023-03-09 06:38:33] |   ERROR   |         Git        | Failed to checkout repo!
[2023-03-09 06:38:33] |   ERROR   |         Git        | fatal: not a git repository (or any of the parent directories): .git

@shriharip please see https://github.com/LuaLS/vscode-lua/issues/81. Also, the extension should still be loading, the addon manager is the only thing throwing an error.

This should be fixed in 3.6.17 🙂 Could you please confirm?

VS Code may be installed somewhere else, it can be at either the user or system level. The directory in use should be listed in your log file.
Good to hear! I'll close this then 🙂

No longer an issue for me after updating to 3.6.17.  Haven't seen a single error in an entire morning of work.  Thank you for your quick response and hard work!


Deploying JonMon in an Azure VM - Research Notes 🤖

As promised, I wrote a quick document (it could have been a small blog post 😅) sharing my notes on how to test JonMon in an Azure VM. I used Blacksmith resources and the document in this PR points to all of them 😎.
Basic Idea here:

Deploy an Azure VM (Windows Server) and enable Hyper-V via Azure Resource Manager (ARM) template
Create an ISO for Win10 via MediaCreationTool
Create a VM in Hyper-V

Set Firmware via Hyper-V PowerShell commands and disable secure boot

Start VM -> Set TESTSIGNING on -> Reboot
Enable Internet access to VM
Run a PowerShell script directly from Blacksmith to install JonMon from the latest release (always)

I hope this helps those that might want to run some of their tests in the cloud and did not know how to set up the infrastructure to host JonMon.
Congratulations on the new project 🎊! Amazing work as always and very happy seeing you sharing your research and people in the community recognizing all your hard work! 🙏🍻

Amazing PR @Cyb3rWard0g. Thank you so much for taking the time to do this!!


Properly dispose of default rendering pipeline in the postProcessRend…

…erPipelineManager.
Related forum issue: https://forum.babylonjs.com/t/how-to-dispose-rendering-pipeline-added-via-inspector/39611

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13698/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13698/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13698/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13698/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13698/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13698/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13698/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13698/merge#BCU1XR#0


Whats the status of SpringRoll?

Pull request #150 by @bigtimebuddy shows a substantial amount of work made in the 'next' branch attempting to modernise the framework. Any plans for this to go anywhere?

Great question! More than likely, we won't be merging Matt's PR as it stands. We're currently working on a 2.0.0 release but we do not have a branch pushed. In the meantime, I can at least give you an idea of where we see the framework going:

Greater focus on accessibility, and providing tooling for making games more accessible with less work from devs (Captions, Text-to-speech, Color Blindness testing)
Reduced focus on renderer and loader system, which should allow developers to use whatever rendering/loading/sound framework they want. However, we'll continue to provide examples on custom integrations
Continued support for Iframe/Bellhop/Container communication layer
Modern build process (ES6 modules, probably Rollup for bundling core, no more bower), along with an updated template.

A lot of this functionality is already ready in our local copies, and we should hopefully be pushing everything up shortly for others to peek at.
Also: If you come back and still haven't seen any action, feel free to ping me here and I'll keep you posted 👍
Thanks!

Chip - thanks very much for the response 👍
I'll be sure to keep my eyes on this repository. The modern build process would be a very welcome addition and sounds great, along with all the other elements you mention.
Once again thanks for the update.


Documentation Link Broken

When I click on the Documentation link provided in README it takes me to a 404 page
http://flysystem.thephpleague.com/caching/
Any idea where can I find the docs?

They're here https://flysystem.thephpleague.com/docs/advanced/caching/
I'll update the link.


Add M1 homebrew dylib dir

This seems to fix installation problems on M1 chips with libheif installed with M1 brew.
The dylib location has changed with the M1 native brew.
Procedure to install pyheif on M1 mac
brew install libffi libheif
pip install git+https://github.com/carsales/pyheif.git

Hi @guillaumegenthial, i was trying to install the package based on your fix but it seems that the problem remains.
    build/temp.linux-aarch64-3.8/_libheif_cffi.c:570:15: fatal error: libheif/heif.h: No such file or directory
          #include "libheif/heif.h"
                   ^~~~~~~~~~~~~~~~
    compilation terminated.
    error: command 'gcc' failed with exit status 1

This works great, review this please!

Does https://github.com/carsales/pyheif/pull/42 solve this?

hi @homm, unfortunately, it's not solved by 0.6.0.
The issue remains.

@panosangelopoulos Could you run in terminal:
$ echo $HOMEBREW_PREFIX

I still see this issue as of pyheif==0.7.0
      generating cffi module 'build/temp.macosx-12.3-arm64-3.8/_libheif_cffi.c'
      creating build/temp.macosx-12.3-arm64-3.8
      building '_libheif_cffi' extension
      creating build/temp.macosx-12.3-arm64-3.8/build
      creating build/temp.macosx-12.3-arm64-3.8/build/temp.macosx-12.3-arm64-3.8
      clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include -I/usr/local/include -I/usr/include -I/opt/local/include -I/opt/homebrew/include -I/Users/pranjal/.pyenv/versions/3.8.13/envs/real38/include -I/Users/pranjal/.pyenv/versions/3.8.13/include/python3.8 -c build/temp.macosx-12.3-arm64-3.8/_libheif_cffi.c -o build/temp.macosx-12.3-arm64-3.8/build/temp.macosx-12.3-arm64-3.8/_libheif_cffi.o
      build/temp.macosx-12.3-arm64-3.8/_libheif_cffi.c:570:15: fatal error: 'libheif/heif.h' file not found
           #include "libheif/heif.h"
                    ^~~~~~~~~~~~~~~~
      1 error generated.
      error: command 'clang' failed with exit status 1
      [end of output]

Tried pip install git+https://github.com/guillaumegenthial/pyheif.git today on my M1, I got the compilation error above. I have libheif installed via brew, and I have the header file:
ls /opt/homebrew/include/libheif/
heif.h		heif_cxx.h	heif_plugin.h	heif_version.h

I don't understand what's wrong. Anyone have any ideas?

aha! My bad. The correct incantation for pip is:
pip install git+https://github.com/guillaumegenthial/pyheif.git@m1-support
I can confirm this PR works on m1 macs no problem.

I found this workaround to install this patched version of pyheif in M1 chips mac only since installing this version failed in other systems.
Hope this helps whoever struggling with the same problem 👍
pyheif= [
    {version = "^0.5.1", markers = "sys_platform != 'darwin'"},
    {git = "https://github.com/guillaumegenthial/pyheif.git", rev = "m1-support", markers = "sys_platform == 'darwin'"} # For m1 mac support. ref: https://github.com/carsales/pyheif/pull/45#issuecomment-1130056328
]

Could this PR be merged and a new version of the lib be released? It's quit annoying 🥲

Any help we can give on this issue?

for me $HOMEBREW_PREFIX seems unset.

You don't have homebrew properly installed in your system. The final step of installation should be adding brew shellenv in your environment.
Try this:
$ eval "$(/opt/homebrew/bin/brew shellenv)"

$ pip install git+https://github.com/carsales/pyheif.git@master#egg=pyheif
Collecting pyheif
Building wheels for collected packages: pyheif
  Building wheel for pyheif (setup.py) ... done
  Created wheel for pyheif: filename=pyheif-0.7.1-cp39-cp39-macosx_10_9_universal2.whl
Successfully built pyheif
Installing collected packages: pyheif
Successfully installed pyheif-0.7.1

$ ipython
Python 3.9.6 (default, May  7 2023, 23:32:44)

In [1]: import pyheif

In [2]: pyheif.__version__
Out[2]: '0.7.1'

Could anyone try to install from the following branch to solve this problem:
$ pip install git+https://github.com/uploadcare/pyheif.git@read-transformations


"Import private key" says it will import to connected zcash node?

When you select "Import private key" the window warns you that it will import it into the connected zcash node. This is problematic if the zcash node isn't fully trusted. I thought the ability to connect to a remote node was part of the usefulness of this wallet (while keeping all keys local)?
Is this a problem with the text or is the text accurate and this is something that can be improved by keeping all keys local?

The text is accurate. Because of various limitations in zcashd, zec-qt-wallet can’t yet manage your private  keys, and relies on zcashd to manage the keys. Therefore, all private keys are imported into zcashd.
The good news is that here is some work underway to enable light wallets, and I think you should see light wallet clients in about 3 to 6 months.

The good news is that here is some work underway to enable light wallets, and I think you should see light wallet clients in about 3 to 6 months.

That's great news! Is that work being done as part of this repo or a different project? If a different project, is it available for testing?

It's the zcash reference wallet: https://z.cash/blog/zcash-reference-wallet-design/
It's a different project, and I think they've not released a testable version yet, but it should come in Q1 2019 I believe.

As a temporary workaround until then, how can one delete the private key(s) for either t-addrs or z-addrs from the running node?


SurfaceKhr Constructor Visibility

One of the main advantages of a library such as GLFW or SDL is that the library can transparently handle the platform-specific code associated with Surface creation, so that you don't need to implement per-platform code C#-side.
Currently, VulkanCore doesn't publically expose the SurfaceKhr(Instance parent, ref AllocationCallbacks? allocator, long handle) constructor. This means that even though you can access the Instance handle (via the VulkanHandle superclass) to create the surface via these libraries, you can't represent the Surface as a VulkanCore object without creating an instance via reflection of the internal constructor.
The simplest solution would be to just make the constructor public, but there's definitely room for other solutions.

Public constructor sounds reasonable. I guess in case the handle for the surface is obtained elsewhere, it doesn't even make sense to pass Instance and AllocationCallbacks args to SurfaceKhr. Perhaps we should simply add a new public constructor which only accepts a handle.

You need to pass in the Instance and AllocationCallbacks because they're also used in the vkDestroySurfaceKHR call - I'll submit a PR for the visibility change shortly.

See #31

Ah okay - I thought the entire lifetime of the surface (including destroying it) was managed externally. The PR is now merged.


Start Azurite once before performance tests

Was seeing some issues with Azurite getting stuck and causing the performance tests to fail in the pipeline. So to fix that we start up Azurite once before all the tests run (the tests will still each try to start up Azurite but then fail because the ports are in use, but this is fine as long as the first one is running because we currently don't actually check that it started up successfully)
This is just a temporary workaround while I investigate the root cause and other solutions

Going to further investigate the test failure separately - doesn't seem related to this change (and is a failure I've seen before)


core dependencies update

Updated pyproject.toml with missed dependencies.
Several dependencies are missed in the pyproject.toml. They are explicitly imported in code.
I listed the files and code lines below.
Those packages are still presented in the poetry.lock. So, those missed dependencies do not break anything.
This update is for consistency. Every explicitly imported package should be presented in the dependency configuration.
Note: poetry.lock is updated because anyio version here (=>4.0 - from poetry.lock) conflicts with langchain version (<4.0)

langchain_core/language_models/llms.py:
langchain_core/prompts/base.py:
langchain_core/prompts/loading.py:
import yaml
langchain_core/output_parsers/base.py:
from typing_extensions import get_args
langchain_core/runnables/base.py:
from typing_extensions import Literal, get_args
langchain_core/runnables/config.py:
langchain_core/runnables/router.py:
from typing_extensions import TypedDict
langchain_core/utils/iter.py:
from typing_extensions import Literal
langchain_core/tracers/langchain_v1.py:
langchain_core/utils/loading.py:
import requests
langchain_core/utils/utils.py:
from requests import HTTPError, Response
langchain_core/tracers/log_stream.py:
from anyio import create_memory_object_stream
langchain_core/utils/utils.py:
from packaging.version import parse

Great catches! He's adding them


add better messages

This message "Authentication failed. Please check your credentials and try again." is also apear if I set wrong mail or if I set wrong password. I think user would like to know what was wrong set.

Yeah, but most site don't return what is wrong. Most often it is something like "email and password don't fit"

This message "Authentication failed. Please check your credentials and try again." is also apear if I set wrong mail or if I set wrong password. I think user would like to know what was wrong set.

and it is another thing. Api don't return what is wrong, just return 401 - unauthenticated.


Make SymbolServerType to be explicitly selected (#5204)

@arunkm,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add Optlaser ST2000-RGB fixture

Here's the product page for this laser: https://www.optlaser.com/st_models/ST-Outdoor.html#md3
The only documentation I've got was sent to me by the manufacturer regarding the DMX control:
ST2000-RGB manual.docx

Sorry but this is undocumented Chinese stuff.
Will not drag it into the library.


lsd: 0.15.1 -> 0.16.0

Motivation for this change
https://github.com/Peltoche/lsd/blob/master/CHANGELOG.md#0160---2019-08-02
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @marsam

Thanks!


Double proxies?

It appears that you use two proxies in this configuration. The Traefik proxy, which is set up to run in an external container to the hub; and the normal inbuilt configurable-http-proxy which runs inside the JupyterHub container and manages all the internal routing. Is this by design? it seems strange to me to have both proxies in the same system

They play two different roles. If you want to use Traefik for both, see https://discourse.jupyter.org/t/introducing-traefikproxy-a-scalable-and-highly-available-proxy-for-jupyterhub/445


UMD Wrapping for Javascript and package.json

Employed a simple UMD wrapper for rison.js making it loadable using AMD, CommonJS (browserify, node), or includable using a <script src="js/rison.js"></script> tag.
I also took the liberty of creating a package.json file and publishing the module to NPM.
If you're interested I would love to add you as owner of the npm package, just drop me your NPM username :)
Btw, the example page is down, perhaps we should make a static one and host it on github pages, so it won't go away...

If you'd like to provide the UMD wrapping as part of a build step, I do that in my fork. Check this part to see how it works. Useful for doing this as part of a publish workflow for npm, bower, or whatever other package manager.

ty


Bump dependency on node-postgres to pg@7

Sequelize had a strict dependency on pg@6 until recently. We should bump it to pg@7 now.

Fixed in #322


Incorrect error reported

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I have a class defined as:
class A2L_Singleton:
__instance = None
@staticmethod
    def getInstance():
        """ Static access method. """
        if A2L_Singleton.__instance == None:
            A2L_Singleton()
        return A2L_Singleton.__instance

    def __init__(self):
        """ Virtually private constructor. """
        if A2L_Singleton.__instance != None:
            raise Exception("This class is a singleton!")
        else:
            A2L_Singleton.__instance = self
            self.InitObjects()

    def InitObjects(self):
        self.A2L_INST = A2L()

I have some additional code/class build around the class mentioned above. There in some line. it throws error as mentioned below:

AttributeError: 'A2L_Singleton' object has no attribute 'A2L_INST'

The error is quite misleading and makes it difficult to figure out the exact issue in my code.
What steps reproduce the problem?
Not sure why this error occurs
What is the expected output? What do you see instead?
No error/ the precise location of the error
Paste Traceback/Error Below (if applicable)

runfile('D:/_Code/python3/SIPConfigurator/_CodeRestructure/CanoeConfigGeneratorData.py', wdir='D:/_Code/python3/SIPConfigurator/_CodeRestructure')
Traceback (most recent call last):

  File "D:\_Code\python3\SIPConfigurator\_CodeRestructure\CanoeConfigGeneratorData.py", line 507, in <module>
    SIPConfigObj.Inst.ParseA2L()

  File "D:\_Code\python3\SIPConfigurator\_CodeRestructure\CanoeConfigGeneratorData.py", line 121, in ParseA2L
    self.A2L_INST.A2L_INST.Init(self.A2LFile)

AttributeError: 'A2L_Singleton' object has no attribute 'A2L_INST'

Versions

Spyder version:  4.1.3
Python version: Python 3.7.3 64-bit
Qt version: Qt 5.9.6
PyQt version: PyQt5 5.9.2
Operating System name/version: Windows 10

Dependencies

# Mandatory:
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.4.1 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.13.0 (OK)
jedi =0.15.2                   :  0.15.2 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
paramiko >=2.4.0               :  2.7.1 (OK)
parso =0.5.2                   :  0.5.2 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=0.25                  :  2.5.2 (OK)
pyls >=0.31.9;<0.32.0          :  0.31.10 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.4 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.4 (OK)
sphinx >=0.6.6                 :  3.0.4 (OK)
spyder_kernels >=1.9.1;<1.10.0 :  1.9.1 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  18.1.1 (OK)

# Optional:
cython >=0.21                  :  0.29.17 (OK)
matplotlib >=2.0.0             :  3.1.3 (OK)
numpy >=1.7                    :  1.18.1 (OK)
pandas >=0.13.1                :  1.0.3 (OK)
scipy >=0.17.0                 :  1.4.1 (OK)
sympy >=0.7.3                  :  1.5.1 (OK)

After my analysis, I figured out the issue.
`
import re
import os
import hashlib
import json
from zipfile import ZipFile
""" Class to contain all relevant information for the A2L file """
class A2L:
# Initialize with the a2l file name
def init(self, A2LFile=''):
self.Init(A2LFile)
# Initialization function
def Init(self, A2LFile):
    # Set the a2l file full path
    self.A2LFile = A2LFile
    # Update file checksum
    self.UpdateChecksum()
    # Update workspace directory
    self.SetWorkspaceDir()
    # Initialize the regular expression
    self.Init_Regex()
    # Initialize the dictionaries associated with data types
    self.Init_DataTypeDict()
    # Initialize the dictionary to hold the parsed a2l information
    self.Init_A2LDataDict()
    # Initialize the dictionary to hold the comment information
    self.Init_BlockCommentDict()
    # Initialize the list of block types for which data needs to be processed
    self.Init_BlockListToProcess()
    # Initialize flag to 0 to indicate a2l file has been initialized but not processed
    self.ProcessDataEna = 0

def UpdateChecksum(self):
    """ Function to get the a2l file content checksum """
    self.FileChecksum = hashlib.md5(open(self.A2LFile, 'rb').read()).hexdigest()

`
When the function  A2L.UpdateChecksum() was called, self.A2LFile was not set to any file. So there was error in the call of hashlib.md5. But instead of showing this error, Python threw some other error (as mentioned in the error description). This is undesired.

Closing as not related with Spyder


NIFI-6662: Adding Kudu Lookup Service

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Adds lookup service for Apache Kudu
https://issues.apache.org/jira/browse/NIFI-6662
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ X ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ X ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ X ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ X ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ X ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ X ] Have you written or updated unit tests to verify your changes?
[ X ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ X ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@pvillard31 given you reviewed the PutKudu changes from a NiFi perspective, would you be interested in reviewing this one too?

the travis build does not work
[ERROR] Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 308.977 s <<< FAILURE! - in org.apache.nifi.controller.kudu.TestKuduLookupService
[ERROR] specific_return_columns(org.apache.nifi.controller.kudu.TestKuduLookupService)  Time elapsed: 62.203 s  <<< ERROR!
java.io.IOException: failed to start masters: Unable to start Master at index 0: /tmp/kudu-binary-jar7895089695673237087/kudu-binary-1.10.0-linux-x86_64/bin/kudu-master: process exited on signal 6 (core dumped)
[ERROR] multi_key(org.apache.nifi.controller.kudu.TestKuduLookupService)  Time elapsed: 61.457 s  <<< ERROR!
java.io.IOException: failed to start masters: Unable to start Master at index 0: /tmp/kudu-binary-jar1462651242343971495/kudu-binary-1.10.0-linux-x86_64/bin/kudu-master: process exited on signal 6 (core dumped)
[ERROR] invalid_key(org.apache.nifi.controller.kudu.TestKuduLookupService)  Time elapsed: 61.494 s  <<< ERROR!
java.io.IOException: failed to start masters: Unable to start Master at index 0: /tmp/kudu-binary-jar676288773884896782/kudu-binary-1.10.0-linux-x86_64/bin/kudu-master: process exited on signal 6 (core dumped)
[ERROR] row_not_found(org.apache.nifi.controller.kudu.TestKuduLookupService)  Time elapsed: 61.568 s  <<< ERROR!
java.io.IOException: failed to start masters: Unable to start Master at index 0: /tmp/kudu-binary-jar7704379724866569711/kudu-binary-1.10.0-linux-x86_64/bin/kudu-master: process exited on signal 6 (core dumped)
[ERROR] single_key(org.apache.nifi.controller.kudu.TestKuduLookupService)  Time elapsed: 61.856 s  <<< ERROR!
java.io.IOException: failed to start masters: Unable to start Master at index 0: /tmp/kudu-binary-jar2657807676209969593/kudu-binary-1.10.0-linux-x86_64/bin/kudu-master: process exited on signal 6 (core dumped)
So this need to be fixed.  Otherwise this looks ready to go to me excluding perhaps that I'm surprised there are no L&N considerations for the lookup nar.  But I've not confirmed if this is just part of the kudu nar yet.

The Travis build for Java 8 EN succeeded, but the others failed due to a check-style issue in nifi-shell-authorizer (src/test/java/org/apache/nifi/authorization/ShellUserGroupProviderIT.java). This check-style issue was fixed in NIFI-6400.

👍 LGTM


Services used? [URL Unshortener] ...

Extension
https://www.raycast.com/SebDanielsson/url-unshortener
Description
You mention that security and privacy will be improved with this extension, except, it isn't mentioned anywhere what service you are using to expand the URLs. If we are just doing it with fetch, then thats useless and not very private. If it is using a dedicated service that expands it serverside, then that is private
If you DO find a service that does it free serverside, then please update this extension, and please add it to the readme. Thank you so much!
Who will benefit from this feature?
No response
Anything else?
No response

@sebdanielsson you should use unshorten.me api. recently discovered it

No. That wouldn't be good for privacy.
https://unshorten.me/privacy-policy


Update_traces_on_the_archive_Peter_Carty.html

Traces on the archive included editing changes by Peter Carty

This issue was moved to consortium/hybrid-publishing-research#52


Ansible deployment and related

This contains the playbooks and roles for deploying Duffy in a single node configuration (i.e. PostgreSQL database, Redis service, Duffy services on one machine).
Done:

New release 3.0.0a3 with latest changes around configuration and dependencies (we were missing asyncpg for postgresql, pyone for OpenNebula, uh-oh!).
SystemD unit files
SELinux labelling of the virtualenv /srv/duffy
Custom SELinux module so Duffy (as started by systemd) can actually talk to Redis and PostgreSQL

Hey @t0xic0der, the latest push contains the necessary changes so Duffy processes started by systemd can actually talk to Redis and PostgreSQL – I ran the playbook against n23 and everything seems to start up and not complain :wink:. Would you please review?

Silence is assent! 😁


[0.18.0-rc] class properties now needs a semicolon but packager throws a cryptic error

class A {
  foo = () => console.log("ooo")
}

this used to work, but now in 0.18.0-rc
TransformError: .../index.js: Cannot read property 'error' of null
Do we need to explicitely add some babel plugin now for this? or is it a bug?

answer is you must use a semicolon now, so:
class A {
  foo = () => console.log("ooo");
}

But the error is not straightforward, this shouldn't break like this in packager

I think you need a semicolon after the arrow function, babel changed this in 6.4.0
babylon: #3225 throw parse error if class properties do not have a semicolon.

From my looking around last night, there is no plugin that removes this check

https://github.com/babel/babel/pull/3225 Is breaking everyone's RN apps if they re-install node modules. I sort of agree with their reasoning for the broken change but it is annoying that it was transparently upgraded if the react-native module is reinstalled without even upgrading RN itself.

@benjreinhart what do you mean "if they re-install node modules" ? is there a cache somewhere? Because i've rm -rf node_modules multiple time already

Yeah.. that's why you're getting the error. When you reinstall the react-native module it is upgrading a babel transform which contains the commit in that link I provided that throws those syntax errors.
So the fact that it is throwing errors isn't a bug. It was a bug that that code worked in the first place, at least according to the pull request I linked to above.

I can confirm this in 0.18-rc. I noticed the same error as @gre: TransformError: [some file]: Cannot read property 'error' of null but didn't know what caused it. After downgrading back to 0.17 I was confronted with the class properties error @benjreinhart mentions, although in 0.17 the babel error message was shown instead of the cryptic packager one, so I could fix it.
I don't have a problem with babel's behavior here (I don't care if I have to put semicolons after class properties) but the error that the transformer throws in 0.18-rc should definitely be classified as a bug. It gives no help in solving the problem.

@benjreinhart oh yeah I see.
Thanks @toadums for pointing the error cause, this is going to be a pain for everyone using this feature as the error message is totally not straightforward, but hopefully when people will search for this they might fall here.
I wish there were a migration tool – or at least a deprecated message logged when they break things like this.

@gre I would leave this open; packager should report the babel failure so the bug can be fixed (as it does in 0.17). I think this is a bug in packager.

@corbt sorry I thought you meant it was a bug in babel, opened :)

@gre There's no official migration tool but I made a PR for JSCS to add autofix for class properties for the requireSemicolons rule real quick for this. https://github.com/babel/babel/pull/3225#issuecomment-169676621. I'l try to get a new version out later today, otherwise follow the steps I mention. Also we will add a deprecation message next time.

@gre @corbt Probably should open another issue about Packager not showing Babel errors.

@satya164 , i've updated the title and added a better description, would that work?

@gre The issue with Packager is not specific to class properties, is it? Does it show errors for other kinds of issues?

@satya164 good question. I don't know that's the only error I had so far. if not, probably open a new generic issue as you said

I found it occurring for two related babel issues:
class A {
  static propTypes = {
    style: React.PropTypes.object,
  } // need a semicolon here

  onChange = () => {

  } // need a semicolon here

}

Here is a discussion about the change es class fields and static properties. I found jeffmo's explanation helpful.

@toadums Both of these are class properties though.

Fair enough, those are just the two syntax' that I had the error occur on :)

I had the same issue today, transpiling with webpack and babel. This is a 'spec compliancy' update in babylon https://github.com/babel/babel/pull/3231 but breaks all arrow functions in a class.
My solution eventually was to just refactor to normal functions, and bind 'this' where necessary.
will post at the normal React git as well, found this one on google. Babel is not very clear about this and it seems to be hurting a lot of people at the moment.

You just need to add semi-colons. No need to change them to function and bind this manually.

Ok, I've had a chance to install the RC and take a look at this again. It looks like the packager isn't passing through any babel errors. Example errors from removing the closing bracket of a function:
React Native 0.17
uncaught error Error: SyntaxError: /Users/kyle/proj/chimera/app/actions/auth.js: 'import' and 'export' may only appear at the top level (22:0)
  20 |
  21 |
> 22 | export function logOut() {
     | ^
  23 |   return {type: LOG_OUT};
  24 | }

React Native 0.18-rc
uncaught error Error: TypeError: Cannot read property 'error' of null
    at index.js:117:20
    at tryCallOne (/Users/kyle/proj/chimera/node_modules/react-native/node_modules/promise/lib/core.js:37:12)
    at /Users/kyle/proj/chimera/node_modules/react-native/node_modules/promise/lib/core.js:123:15
    at flush (/Users/kyle/proj/chimera/node_modules/react-native/node_modules/promise/node_modules/asap/raw.js:50:29)
    at doNTCallback0 (node.js:428:9)
TransformError: /Users/kyle/proj/chimera/app/actions/auth.js: Cannot read property 'error' of null
See logs /var/folders/j4/wct0sgyx0p9803_1nkhm3pzm0000gn/T/react-packager.log
    at SocketClient._handleMessage (SocketClient.js:139:23)
    at BunserBuf.<anonymous> (SocketClient.js:53:42)
    at emitOne (events.js:77:13)
    at BunserBuf.emit (events.js:169:7)
    at BunserBuf.process (/Users/kyle/proj/chimera/node_modules/react-native/node_modules/bser/index.js:289:10)
    at /Users/kyle/proj/chimera/node_modules/react-native/node_modules/bser/index.js:244:12
    at doNTCallback0 (node.js:428:9)
    at process._tickCallback (node.js:357:13)

@corbt thanks :) let's close this and focus on your generic issue

Since this morning I'm having this issue again, anybody else?
transforming [========================================] 100% 613/614Error while persisting cache: SyntaxError /Users/matteo/dev/react-native-starter/src/containers/login.js: A semicolon is required after a class property (24:3)

class LoginModal extends React.Component {
  static propTypes = {
    error: PropTypes.string,
    isLoading: PropTypes.bool.isRequired,
    login: PropTypes.func.isRequired,
  } // <-- needs semicolon now

My .babelrc:
{
  "presets": ["react-native"],
  "plugins": ["transform-decorators-legacy"]
}

P.S.: The repo is here

This shouldn't be an issue anymore since the change was reverted a while back in 6.5.2 https://github.com/babel/babel/releases/tag/v6.5.2 - I would probably clear/reinstall node_modules?

I already tried with:

npm cache clean, rm -f ~./npm, rm -f ./node_modules
./node_modules/react-native/packager/packager.sh start --reset-cache
without any success...

Thank you anyway hzoo, I also asked on stackoverflow, because it seems it's an issue only on my setup and/or is better discussing it there.

It is so weird, I can confirm I'm still having the issue, tried with both React-Native 0.20 and 0.21 on two different repositories (on both Ubuntu and OSX).
Tomorrow I'll add semicolon back on every single class property and I'll give it another try in the future.

Fixed on 0.22.0-rc, 0.21.0 was using babel < 6.5.2


Multi bus mapping issue

I'm fighting with a issue:
I added this into the tests: https://github.com/jorge07/tactician-bundle/commit/2bb12cba91060cf176c9b8d7ae5ed8f12726cadc
And I'm having:
1) League\Tactician\Bundle\Tests\Integration\BasicCommandAndBusMappingTest::testHandleCommandOnSpecificBus
League\Tactician\Exception\MissingHandlerException: Missing handler for command League\Tactician\Bundle\Tests\EchoText

If someone could help me to debug this issue or bring me some light about how to resolve that bug I'll submit the PR ASAP.
Thanks

Hello,
I just let a comment on your commit