rules_scala + Bazel IntelliJ Plugin not breaking on breakpoints

We ran into an issue in which Bazel's IntelliJ Plugin and rules_scala does not seem to be hitting breakpoints set in IntelliJ.
From IntelliJ you can run the test and it passes.

When you set a breakpoint and debug the test, the breakpoint is never hit. This happens when running the test in debug mode from both the gutter and the "Run" menu.

From the Bazel console output inside IntelliJ, it looks like it is setting up a debug port:
Listening for transport dt_socket at address: 5005
Connected to the target VM, address: 'localhost:5005', transport: 'socket'

It then runs the test and disconnects without ever stopping at the breakpoint
Disconnected from the target VM, address: 'localhost:5005', transport: 'socket'
Time: 0

I created a simple repro example here: https://github.com/lucidsoftware/rules_scala_intellij_debug_example
You should be able to import that entire repo into IntelliJ and repro the above. If anyone runs into issues reproducing this please let me know.
Curious if this is a known issue, if I'm doing something wrong, or if anyone has any thoughts on why this is happening.
Thanks for the help!

No idea since we’re not scala test users but I can tell you that this works
for (most) specs2 use-cases.
I’d suggest closing this one and opening one on the IntelliJ side
On Tue, 6 Mar 2018 at 5:23 James Judd<EMAIL_ADDRESS>wrote:

We ran into an issue: Bazel's IntelliJ Plugin and rules_scala does not
seem to be hitting breakpoints.
From IntelliJ you can run the test and it passes. This happens from the
gutter and the "Run" menu.
https://camo.githubusercontent.com/72dd6622ea3b73f2624d40a0ec18a096f2fc8b6f/68747470733a2f2f692e696d6775722e636f6d2f5a3366416e35702e706e67
When you set a breakpoint and debug the test, the breakpoint is never hit.
https://camo.githubusercontent.com/dd2581c6f91f019f829db5581f04274062732bc2/68747470733a2f2f692e696d6775722e636f6d2f566570364135682e706e67
From the Bazel console output, it looks like it is setting up a debug port:
Listening for transport dt_socket at address: 5005
Connected to the target VM, address: 'localhost:5005', transport: 'socket'
It then disconnects without ever stopping at the breakpoint
Disconnected from the target VM, address: 'localhost:5005', transport: 'socket'
Time: 0
I created a simple repro example here:
https://github.com/lucidsoftware/rules_scala_intellij_debug_example
You should be able to import that entire repo into IntelliJ and repro the
above. If anyone runs into issues reproducing this please let me know.
Curious if this is a known issue, if I'm doing something wrong, or if
anyone had any thoughts on why this is happening.
Thanks for the help!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFyw4PDYcX5iUtgbruP42zEqb0tUNks5tbgEcgaJpZM4SeC3l
.

Interesting. I created specs2 and scala test examples in that repo and neither of them worked.
I'll look into this more and open an issue with the IntelliJ side.

I didn’t actually tested your repo but just today I debugged a test which
seems identical to your specs2 example
On Wed, 7 Mar 2018 at 22:11 James Judd<EMAIL_ADDRESS>wrote:

Closed #437 https://github.com/bazelbuild/rules_scala/issues/437.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#event-1509743001,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFydbRvZh93fO90Z9CWYFFpQRbW-Sks5tcD7agaJpZM4SeC3l
.

Very interesting. I wonder if it's something on our end.

Do you use your own fork of rules_scala? Latest plugin version I assume?
2017.3 IntelliJ?
On Wed, 7 Mar 2018 at 23:11 James Judd<EMAIL_ADDRESS>wrote:

Very interesting. I wonder if it's something on our end.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-371284009,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFzBwOJredJxdnY_X2UWotRqehBVbks5tcEtSgaJpZM4SeC3l
.

The example uses rules_scala master branch. I just updated it to the latest commit and it still doesn't hit the breakpoints.
Bazel 0.11.1
Latest Bazel plugin
IntelliJ 2017.3.4
Ubuntu
I'm digging into it tonight. Hopefully I can find something. If not, I'll open an issue with the IntelliJ plugin repo.
Thanks for your help! It's good to know that it works for others.

I updated my example and have some more info. I can hit some breakpoints, but not others.
In this test
class ExampleSpecs2Test extends SpecificationWithJUnit {
  def bar() = {
    1
  }

  "a specs2 test" should {
    "be debuggable in IntelliJ" in {
      val a = bar
      val b = 3
      val c = a + b
      println("specs2: statement 1")
      println("specs2: statement 2")
      println("specs2: statement 3")
      success
    }
  }
}```

I can set a breakpoint inside `bar` and it is hit. I cannot hit a breakpoint set inside the `"be debuggable in IntelliJ" in {` block. My hunch is that it has something to do with Scala's anonymous classes and functions.

I hooked the test up to `jdb` by doing `bazel test //src/test:ExampleSpecs2Test --java_debug` and then `jdb -attach 5005`.

I can set a breakpoint at `foo.ExampleSpecs2Test.bar()` and things stopped. To set a breakpoint for the test body, I have to set a breakpoint for `foo.ExampleSpecs2Test$$anonfun$1$$anonfun$apply$1.apply()`.

My guess is that `foo.ExampleSpecs2Test$$anonfun$1$$anonfun$apply$1.apply()` is somehow not working with the IntelliJ bazel plugin. I don't know of a good way to see what the IntelliJ debugger is doing under the hood.

I imagine that others should be able to reproduce this. If they cannot, maybe I'm missing some javac or scalc options.

James,
If you remove the “bar” call and put a breakpoint in one of the println
calls, does it stop?
Because the one case we see a problem with breakpoints is in specs2 tests
which have a “scope” and then they stop at the “scope” but not in the test
itself. If you inline the scope then the breakpoints work
On Fri, 9 Mar 2018 at 7:28 James Judd<EMAIL_ADDRESS>wrote:

I updated my example and have some more info. I can hit some breakpoints,
but not others.
In this test
class ExampleSpecs2Test extends SpecificationWithJUnit {
def bar() = {
1
}
"a specs2 test" should {
"be debuggable in IntelliJ" in {
val a = bar
val b = 3
val c = a + b
println("specs2: statement 1")
println("specs2: statement 2")
println("specs2: statement 3")
success
}
}
}```
I can set a breakpoint inside bar and it is hit. I cannot hit a breakpoint set inside the "be debuggable in IntelliJ" in { block. My hunch is that it has something to do with Scala's anonymous classes and functions.
I hooked the test up to jdb by doing bazel test //src/test:ExampleSpecs2Test --java_debug and then jdb -attach 5005.
I can set a breakpoint at foo.ExampleSpecs2Test.bar() and things stopped. To set a breakpoint for the test body, I have to set a breakpoint for foo.ExampleSpecs2Test$$anonfun$1$$anonfun$apply$1.apply().
My guess is that foo.ExampleSpecs2Test$$anonfun$1$$anonfun$apply$1.apply() is somehow not working with the IntelliJ bazel plugin. I don't know of a good way to see what the IntelliJ debugger is doing under the hood.
I imagine that others should be able to reproduce this. If they cannot, maybe I'm missing some javac or scalc options.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-371717538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFyShK5lDFR71W0AsLMQZEy98PsOpks5tchL2gaJpZM4SeC3l
.

When I change the test to look like this
class ExampleSpecs2Test extends SpecificationWithJUnit {
  "a specs2 test" should {
    "be debuggable in IntelliJ" in {
      println("specs2: statement 1")
      println("specs2: statement 2")
      println("specs2: statement 3")
      success
    }
  }
}

I can set breakpoints on all of the println lines and it doesn't stop on any of them.
I can set breakpoints on "a specs2 test" should and "be debuggable in IntelliJ" in { and both of those are hit.

This is looking like a Scala IntelliJ plugin issue. I've updated the project to support sbt, imported the project into IntelliJ using sbt, and I still can't hit the breakpoints. I'll file an issue over with Scala IntelliJ plugin.

I'm getting a few people around the office to try importing it and seeing if they run into the same issue.
I swear debugging specs2 tests like this used to work.

It works for some people in the office and not others. Definitely not a rules_scala problem, but we're working on tracking down what the issue is :)

Yeah, I think a colleague also reproduced it with maven.
If you can write here the tracking issue over in scala IntelliJ it will
probably help others
On Fri, 9 Mar 2018 at 20:41 James Judd<EMAIL_ADDRESS>wrote:

It works for some people in the office and not others. Definitely not a
rules_scala problem, but we're working on tracking down what the issue is :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-371907642,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF3QAcTd5JnMAN_4AVlrIla2rTQhfks5tcszGgaJpZM4SeC3l
.

We've tracked down what versions work and which don't.
IntelliJ 2017.2 and the Scala plugin from the 2017.2 track hit the breakpoints using both Scala 2.11 and 2.12
IntelliJ 2017.3 and that Scala plugins on the 2017.3 track hit the breakpoints with only Scala 2.12.

Great!
We actually saw cases of the latter which don’t stop.
Did you open an issue yet?
If so we’ll try next week to add there a repro with2.12 /2017.3
On Fri, 9 Mar 2018 at 23:37 James Judd<EMAIL_ADDRESS>wrote:

We've tracked down what versions work and which don't.
IntelliJ 2017.2 and the Scala plugin from the 2017.2 track hit the
breakpoints using both Scala 2.11 and 2.12
IntelliJ 2017.3 and that Scala plugins on the 2017.3 track hit the
breakpoints with only Scala 2.12.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-371952237,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIFzuVs6Ocx9UJLNZfsx6qYDZJ1S53ks5tcvYFgaJpZM4SeC3l
.

Issue has been filed: https://youtrack.jetbrains.com/issue/SCL-13461

@hmemcpy can you please update it with our ”Scope” use case?
On Sat, 10 Mar 2018 at 1:16 James Judd<EMAIL_ADDRESS>wrote:

Issue has been filed: https://youtrack.jetbrains.com/issue/SCL-13461
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-371972539,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF3lGNTRLZMmSisnteptL3y_szJvvks5tcw0wgaJpZM4SeC3l
.

I added the comment about the Scope parameter to the issue on YouTrack, they are related. Seems that it causes breakpoint to.... break 😂

But James reported that even a simple test without Scope didn’t work. Were
you able to verify that on the simple case specs2 does stop?
If so I think it’s important to also report that since it might help triage
where things still work
On Sun, 11 Mar 2018 at 17:05 Igal Tabachnik<EMAIL_ADDRESS>wrote:

I added the comment about the Scope parameter to the issue on YouTrack,
they are related. Seems that it causes breakpoint to.... break 😂
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-372122111,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF6qbAjVvgo0263EXRLHfru94TYfBks5tdT0dgaJpZM4SeC3l
.

@ittaiz yes, it (where it == breakpoint in the test) didn't work for me when running with scala 2.11 (set in sbt) on the 2018.3 plugin. When I switched to Scala 2.12, I was able to place a breakpoint, but after adding Scope, it didn't work again.
So I believe those two issues are a) related b) not related to bazel

Thanks!
On Sun, 11 Mar 2018 at 20:06 Igal Tabachnik<EMAIL_ADDRESS>wrote:

@ittaiz https://github.com/ittaiz yes, it (where it == breakpoint in
the test) didn't work for me when running with scala 2.11 (set in sbt) on
the 2018.3 plugin. When I switched to Scala 2.12, I was able to place a
breakpoint, but after adding Scope, it didn't work again.
So I believe those two issues are a) related b) not related to bazel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-372135605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF1DO2wiRnBRV-JYU2vrG7sn-J0T2ks5tdWengaJpZM4SeC3l
.

I'm now able to hit these breakpoints in the latest version of the Scala plugin: 2017.3.15

Glad to hear. Should we close it?
On Mon, 19 Mar 2018 at 20:20 James Judd<EMAIL_ADDRESS>wrote:

I'm now able to hit these breakpoints in the latest version of the Scala
plugin: 2017.3.15
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_scala/issues/437#issuecomment-374314694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABUIF_bTJAdZfx1jay5y5rsmB-HMXogGks5tf_bRgaJpZM4SeC3l
.

I'm double checking with people around the office that it is fixed for them. If it is, I will close the issue in just a bit.

@hmemcpy had a comment on that issue. Does the update fix your use case as well?

Thanks for the update! I'll check it first thing tomorrow and update!

Hey @jjudd! I just checked, and can confirm that Scala plugin v2017.3.15 solves my issue as well! /cc @ittaiz
Thanks for reporting it to JetBrains, I'll update there as well!


Failed to run the notebook in colab

hello,
Thanks for develop the cpa software.
But I cannot run the provided notebook in colab due to the failed installation of CPA.
Could you help with this problem ?
Thanks !!!

Hi @bitcometz,
Can you please try now with the latest CPA version (v0.3.3)?

Thanks and sorry for late reply，I will try ！！！
Best


add Android instrumentation test

Add an Android instrumentation test. It is similar to flutter_gallery__transition_perf but does not require a host machine to run. We can run this test on off-the-shelf test infrastructures, such as Firebase Test Lab or AWS Device Farm.


Can't easily get values from config after 1.0.0

Background
Sometimes I like to import my Tailwind config and use the values from it to ensure consistency across the board. One example would be media queries using Tailwind screen sizes when using styled-components:
import tailwind from '../../tailwind'
// ...
export default styled(Component)`
// some css...
@media screen and (min-width: ${tailwind.screens.md}) {
  // more css...
}
`

Problem
With the new 1.0 approach to merging the user config with the default config, it's not as simple as single import within the project. The configs have to have their function keys resolved and then be merged.
Solution
So I made a little package using resolveConfig() under the hood to merge and resolve the user's config with the default config.
You can use it like:
import tailwind from 'tailwind-config'

const { theme, variants, ...etc } = tailwind.config('./path/to/tailwind.config')
/* or */
const { colors, screens, spacing, ...etc } = tailwind.theme({ ...configObject })

Here's the package: davecalnan/tailwind-config
Include this in tailwindcss?
This could be added as a first-party feature with some sort of API like:
import { config } from 'tailwindcss'

const { theme, ...etc} = config('./path/to/tailwind.config')

Any thoughts? If it seems like a worthwhile addition I'd be happy to make the PR @adamwathan /@reinink. Otherwise I'll just leave it as the tailwind-config package as an opt-in for anyone who would like to use it.

This is keeping us from upgrade to version 1.0.
The import method before 1.0
import tailwind from '../../tailwind'

was very simple and straightforward.
import { config } from 'tailwindcss'

const { theme, ...etc} = config('./path/to/tailwind.config')

I think the path for the config file should be specified only one time

import { config } from 'tailwindcss'

const { theme, ...etc} = config('./path/to/tailwind.config')

I think the path for the config file should be specified only one time

Just to be clear, the above code sample is a suggestion for how things might work in a future version of Tailwind. It won't work if you run it as it doesn't currently exist.

If you are using a version of Tailwind >= 1.0.0 and want to access values from the resolved config, you can use the package I mentioned to easily do that.
npm install tailwind-config

import tailwind from 'tailwind-config'
const config = tailwind.config('../../tailwind')

Bear in mind this is a separate package to tailwindcss. Full usage guide on the package documentation.
Does that help clear things up at all?

Yes, thanks for creating this package

For use outside of js it would also be useful to me if it would spit out a json.
maybe tailwind export-config

@brasilikum https://github.com/dobromir-hristov/tailwindcss-export-config/ already exports to CSS preprocessors, I could also add a JSON output too.
I am going to use @davecalnan package, until we have something official to resolve the configs.

For that reason, it feels like the safest way to reference your Tailwind config in JS is to split your theme section into a separate file so you can import it without carrying around any other dependency baggage.
Or alternatively, we could make it possible to register plugins in your Tailwind config without actually using a require statement, so that you can import your config elsewhere without those dependencies actually being resolved, sort of like how you can do it in a postcss.config.js file — basically just making the file a static object with no dependencies, even if you are pulling in plugins.
Either way we would probably expose our resolveConfig function as public API so people could get the final values.
Anyone have any other ideas on the best way to make this possible while not forcing people to bundle build dependencies into the JS they serve to the client?

For that reason, it feels like the safest way to reference your Tailwind config in JS is to split your theme section into a separate file so you can import it without carrying around any other dependency baggage.

While that would work if you were to copy the entirety of Tailwind's colors and your custom colors to said separate file, what about if you're only using the extends part of the config to add your custom colors (or sizes or spaces, etc.)?

+1 for exposing the resolveConfig or another function publicly to get the config object. Couple of use cases I'm running into are wanting access to theme values such as colors and screen sizes in React components dealing with charts and css in js where I'm unable to use classes or variants.

I haven't personally had the need to reference anything in my Tailwind config that wouldn't be in the final resolved config object so I'm not sure what people might be looking for there.
I agree exporting resolveConfig or a helper function would be great. That's what I did in the small package I made (davecalnan/tailwind-config) and I like the api.
Enabling usage like:
import { config } from 'tailwindcss'

const config = config('path/to/config')
/* or */
const config = config({ ...importedConfigObject })

Giving you a plain JS object to get your keys from solves all my use cases I've come across, is straightforward to explain, and requires minimal changes to the framework. I'd be happy to make the pull request and make my package irrelevant!

PR'd a basic implementation of this:
https://github.com/tailwindcss/tailwindcss/pull/877
Likely will add support for a require-less plugins key syntax to make it "safe" to import your config in your front end bundle without carrying a bunch of unneeded dependencies but can come after 1.0, not really a big deal.

Merged that PR so this will be possible in the next beta.

Is this available in v1.0.0-beta.7?

It was available with v1.0.0-beta.6, but I would suggest beta.7 because of the bug extending the margins.

Like @adamwathan, I noticed that using the recommended resolveConfig was adding ~200kb into my bundled file.
I just needed the breakpoints used by Tailwind, so what I did was creating a Gulp task to generate a breakpoints.json file and then use only that in my JS.
If anyone end up here looking for a way to improve their bundle file size, here is my task:
import resolveConfig from 'tailwindcss/resolveConfig';
import tailwindConfig from './tailwind.config';
import fs from 'fs';

function breakpoints(done) {
  let json = {};

  const fullConfig = resolveConfig(tailwindConfig);

  Object.keys(fullConfig.theme.screens).forEach(key => json[key] = parseInt(fullConfig.theme.screens[key]));

  fs.writeFile(`${paths.src}/breakpoints.json`, JSON.stringify(json), done);
}

BTW, I'm using Gulp 4 with ES6, so all of this is in a gulpfile.babel.js.

I am having similar bundle issues due to resolveConfig usage. Is there already a plugin that helps with this situation?  👀

Likely will add support for a require-less plugins key syntax to make it "safe" to import your config in your front end bundle without carrying a bunch of unneeded dependencies but can come after 1.0, not really a big deal.


i can׳t change image after i uploaded one

Hi,
i am trying to change image twice, but when i click on some effect i get the previous image(before i made the changed).
i am using through jquery.
second thing, i have few images that needs to get the effect, but it work only for one image, even if i define it for another variable.

any response ?

???

Regarding your first question:
You need to call apply in between to make the second effect to be applied on top of the first one. You can check vintagejs.com to see that it works to change the applied effect. vintagejs.com uses the latest version of this plugin.
Regarding your second question:
Can you give me some more information on how you try this. If you visit http://rendro.github.io/vintageJS/ you see that it is possible to apply effects to different images. Looks like it is an issue with your implementation rather than the plugin isself.

Thanks for your redsponse, if fixed the problem
On Apr 24, 2015 12:22 PM, "Robert Fleischmann"<EMAIL_ADDRESS>wrote:

Regarding your first question:
You need to call apply in between to make the second effect to be applied
on top of the first one. You can check vintagejs.com to see that it works
to change the applied effect. vintagejs.com uses the latest version of
this plugin.
Regarding your second question:
Can you give me some more information on how you try this. If you visit
http://rendro.github.io/vintageJS/ you see that it is possible to apply
effects to different images. Looks like it is an issue with your
implementation rather than the plugin isself.
—
Reply to this email directly or view it on GitHub
https://github.com/rendro/vintageJS/issues/27#issuecomment-95867009.


Custom function doesn't support net.IP type

I was trying to fake data for type net.IP (go net package) and hence created and registered below custom function.
package main

import (
	"fmt"
	"math/rand"
	"net"

	"github.com/brianvoe/gofakeit/v6"
)

type Foo struct {
	IPString string `fake:"{ip}"`    // working
	IP       net.IP `fake:"{ip}"`    // <nil>
}

func main() {
	var f Foo
	gofakeit.AddFuncLookup("ip", gofakeit.Info{
		Category:    "custom",
		Description: "Random IPv4 Address of type net.IP",
		Example:     "<IP_ADDRESS>",
		Output:      "net.IP",
		Generate: func(r *rand.Rand, m *gofakeit.MapParams, info *gofakeit.Info) (interface{}, error) {
			data := net.IPv4(byte(r.Intn(256)), byte(r.Intn(256)), byte(r.Intn(256)), byte(r.Intn(256)))
			fmt.Printf("data: %s - %T\n", data, data)
			return data, nil
		},
	})
	gofakeit.Struct(&f)
	fmt.Printf("%s - %T\n", f.IPString, f.IPString)
	fmt.Printf("%s - %T", f.IP, f.IP)                         // <nil>
}

Custom handler function defined above returns interface{} type but somehow it is just able to return string data type and doesn't work for  net.IP type.

I understand the issue. I havent figured out a way to make that work at the moment. But i am looking for people that can help with that part. If you cant think of a solution I am open to prs.

When I look at the error code of the gofakeit.Struct(&f) it shows that there is a parse error strconv.ParseUint: parsing "<IP_ADDRESS>": invalid syntax This is because the net.IP type is actually a byte array which makes gofakeit populate the byte array by calling the custom function for each member of the slice. Since the custom function returns a net.IP (= []byte) instead of a single byte, we get the parse error.
I tried a hack that checks the reflect.Name() of the field. The result is the custom type ("IP") when you are using that instead of the byte array. If that is the case and if you have a custom method defined, I will return the result of the custom function instead of populating a slice with some random values.
Feel free to merge it or rewrite it.

I made some updates but i think in general what you found makes sense. v6.17.0


I cant start Windows Defender

I have disabled windows defender before, but it cannot be enable  now

same issue

This isn't even the same program


UI Occlusion - manually edit ROIs

Recommend launching an additional window for editing ROIs.

Moved ROI drawing to layer below help text


[tests-only][full-ci] Bump core commit id for the tests (master)

Description
Bump core commit id for the tests
Related Issue
part of https://github.com/owncloud/QA/issues/747

https://drone.cernbox.cern.ch/cs3org/reva/7657/10/6
and
https://drone.cernbox.cern.ch/cs3org/reva/7657/16/7
runsh: Total unexpected failed scenarios throughout the test run:
apiFavorites/favorites.feature:115
apiFavorites/favorites.feature:116
apiFavorites/favorites.feature:141
apiFavorites/favorites.feature:142
apiFavorites/favorites.feature:267
apiFavorites/favorites.feature:268

Notice: Undefined offset: 1 in /drone/src/tmp/testrunner/tests/acceptance/features/bootstrap/WebDav.php line 5291
It looks like something needs to be adjusted in the core test suite to stop the code crashing. Then we might see what really happens.

Testing the fix PR


Add DDP client plugin

I'm recently playing around with some LED controllers (e.g. LedFx).
How about adding a DDP client plugin?
This is a very rough sketch to illustrate and as POC.
There are some discussion points:

should we strictly check the DDP header?
should we support other pixel formats than RGB (e.g. Grayscale)?
is it better to use MAX(R, G, B) as brightness than AVG(R, G, B)?
would (minimal) code to allow discovery be useful?

This is battle-tested now and works very well.
On an ESP32 I thoroughly tested the interaction between network on Core 0 and drawing on Core 1, I was expecting some tearing maybe but nothing is visible -- we need not care if onScreenTimer's SPI writing reads the renderBuffer while a DDP update is only partially written.
No need to invest in checking the protocol headers. All tools (and renderes) I had a look at just write (and assume) valid (non-extended) RGB DDP frames. There is no harm in reading broken frames (or even garbage UDP data), the display might look funny that's all.
I changed the loops to properly use COLS and ROWS for forward compatibility and also updated two other places to use the constants.
This is ready for review and merge now.


No error message if unknown categories are fed for predictions

If unknown categories are fed for predictions, the API will treat them as missing.
This may be a unwanted action.
Ex:
import pandas as pd
from pandas.api.types import CategoricalDtype
var_type = CategoricalDtype(categories=[1,2], ordered=True)
df = pd.DataFrame({'A': [3,2,3], 'B': [2,2,1]})
df

Out:
        A      B
0	3	2
1	2	2
2	3	1

df['A'].astype(var_type)

Out:
0    NaN
1      2
2    NaN
Name: A, dtype: category
Categories (2, int64): [1 < 2]

Two things can be done:

Leave like that but warn the user
Throw an error

Solved via 7732582


cellxgene_VIP deploying with Heroku

Hi,
I would like to deploy the cellxgene VIP result with Heroku
and would like  to know how to modify the "Dockerfile" provided by cellxgene
Here is my modified version and I'm getting this error

FROM ubuntu:bionic
ENV LC_ALL=C.UTF-8
ENV LANG=C.UTF-8
RUN apt-get update &&
apt-get install -y build-essential libxml2-dev python3-dev python3-pip zlib1g-dev python3-requests &&
apt-get install git -y
git clone https://github.com/interactivereport/cellxgene_VIP.git
COPY . .
RUN pip install -r requirements.txt
RUN conda env create -n VIP -f VIP.macOS.yml
RUN conda init bash
RUN conda activate VIP
RUN echo "Make sure flask is installed:"
RUN python -c "import flask"
COPY run.py .
RUN ./config.macOS.sh
ENTRYPOINT ["cellxgene"]

and getting below errors
E: Unable to locate package clone
E: Unable to locate package https://github.com/interactivereport
E: Couldn't find any package by glob 'https://github.com/interactivereport'
E: Couldn't find any package by regex 'https://github.com/interactivereport'
The command '/bin/sh -c apt-get update &&     apt-get install -y build-essential libxml2-dev python3-dev python3-pip zlib1g-dev python3-requests &&     apt-get install git -y     git clone https://github.com/interactivereport/cellxgene_VIP.git' returned a non-zero code: 100
▸    Error: docker build exited with Error: 100
Thanks,

I would love to see how this works

Dear @skim245, @FADHLyemen and cellxgene_vip developer,
I am a PhD student at CNAG-CRG evaluating right now the potential use of cellxgene/cellxgene_VIP for 3TR (https://www.3tr-imi.eu/)
Since I am also struggling with setting up a functional Dockerfile I thought it could be beneficial to share what I tried so far in your issue. So we could help each other.

I've been trying to deploy cellxgene_VIP with Heroku using below codes
git add heroku.yml
git commit -m "Add heroku.yml"
git push heroku master
and getting an error code below
remote: =!= There were problems parsing your heroku.yml. We've detected the following issues:
remote:
remote: build.docker.web references a Dockerfile that does not exist
any thoughts or suggestion?
Thanks,

@skim245
without seeing your heroku.yml and knowing your folder structure I cannot help you with that.
But my random guess is that you have specified the wrong path inside build.docker.web
If your heroku.yml is in the root directory and the Dockerfile is e.g. inside a folder named app:
build:
  docker:
    web: app/Dockerfile

If the heroku.yml and the Dockerfile are in the same folder:
build:
  docker:
    web: Dockerfile

@IvoLeist
here is my heroku.yml
build:
docker:
web: Dockerfile
run:
web:
command:
- cellxgene launch  --host localhost --port 5050 --disable-annotations --verbose 042221_scRNA_data.h5ad
and both of my heroku.yml and the Dockerfile are in the same folder.
and do you know which extension to use for Dockerfile ?

I saw the discussion about Dockerfile in this issue, so I'm sharing my Dockerfile here too.
Half of the file is copied from https://github.com/jupyter/docker-stacks/blob/master/base-notebook/Dockerfile and half of the file is from @IvoLeist. I failed to use conda to solve the R dependencies directly, I got the same errors written in @IvoLeist 's Dockerfile. Instead, I followed the Jupyter Notebook Dockerfile and used Mamba to solve the dependencies. It worked pretty well.
I didn't try deploying to Heroku but I managed to deploy on Google Cloud Run. I believe they work in the same way.
FROM debian:bullseye

# ref: https://github.com/jupyter/docker-stacks/blob/master/base-notebook/Dockerfile

# Install all OS dependencies for notebook server that starts but lacks all
# features (e.g., download as all possible file formats)
# - tini is installed as a helpful container entrypoint that reaps zombie
#   processes and such of the actual executable we want to start, see
#   https://github.com/krallin/tini#why-tini for details.
# - apt-get upgrade is run to patch known vulnerabilities in apt-get packages as
#   the ubuntu base image is rebuilt too seldom sometimes (less than once a month)
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update --yes && \
    apt-get upgrade --yes && \
    apt-get install --yes --no-install-recommends \
    git cpio build-essential python3 python3-pip cmake libhdf5-dev cmake llvm npm nodejs jq \
    tini wget ca-certificates sudo locales fonts-liberation && \
    apt-get clean && rm -rf /var/lib/apt/lists/* && \
    echo "en_US.UTF-8 UTF-8" > /etc/locale.gen && \
    locale-gen

# Configure environment
ENV CONDA_DIR=/opt/conda \
    SHELL=/bin/bash \
    LC_ALL=en_US.UTF-8 \
    LANG=en_US.UTF-8 \
    LANGUAGE=en_US.UTF-8
ENV PATH="${CONDA_DIR}/bin:${PATH}"

# Install conda as jovyan and check the sha256 sum provided on the download site
WORKDIR /tmp

ARG PYTHON_VERSION="3.8.12"

# CONDA_MIRROR is a mirror prefix to speed up downloading
# For example, people from mainland China could set it as
# https://mirrors.tuna.tsinghua.edu.cn/github-release/conda-forge/miniforge/LatestRelease
ARG CONDA_MIRROR=https://github.com/conda-forge/miniforge/releases/latest/download

# ---- Miniforge installer ----
# Check https://github.com/conda-forge/miniforge/releases
# Package Manager and Python implementation to use (https://github.com/conda-forge/miniforge)
# We're using Mambaforge installer, possible options:
# - conda only: either Miniforge3 to use Python or Miniforge-pypy3 to use PyPy
# - conda + mamba: either Mambaforge to use Python or Mambaforge-pypy3 to use PyPy
# Installation: conda, mamba, pip
RUN set -x && \
    # Miniforge installer
    miniforge_arch=$(uname -m) && \
    miniforge_installer="Mambaforge-Linux-${miniforge_arch}.sh" && \
    wget --quiet "${CONDA_MIRROR}/${miniforge_installer}" && \
    /bin/bash "${miniforge_installer}" -f -b -p "${CONDA_DIR}" && \
    rm "${miniforge_installer}" && \
    # Conda configuration see https://conda.io/projects/conda/en/latest/configuration.html
    conda config --system --set auto_update_conda false && \
    conda config --system --set show_channel_urls true && \
    if [ ${PYTHON_VERSION} != "default" ]; then mamba install --quiet --yes python="${PYTHON_VERSION}"; fi && \
    mamba list python | grep '^python ' | tr -s ' ' | cut -d ' ' -f 1,2 >> "${CONDA_DIR}/conda-meta/pinned" && \
    # Using conda to update all packages: https://github.com/mamba-org/mamba/issues/1092
    conda update --all --quiet --yes && \
    conda clean --all -f -y && \
    rm -rf "/home/${NB_USER}/.cache/yarn"

# install R dependencies
RUN mamba install --quiet --yes \
    'r-base' \
    'r-cairo' \
    'r-ragg' \
    'r-ggrastr' \
    'r-arrow' \
    'r-biocmanager' \
    'r-foreign' \
    'r-ggpubr' \
    'r-rmarkdown' \
    'r-seurat' \
    'r-tidyverse' \
    'r-viridis' \
    'r-ellipsis' \
    'r-processx' && \
    mamba clean --all -f -y

WORKDIR /

RUN git clone https://github.com/interactivereport/cellxgene_VIP.git

WORKDIR /cellxgene_VIP

# install Python depdendencies
ADD vip_requirements.txt /cellxgene_VIP/vip_requirements.txt
RUN pip install -r /cellxgene_VIP/vip_requirements.txt

RUN bash config.sh

# install cellxgene Python dependencies if any
RUN pip install -r /cellxgene_VIP/cellxgene/server/requirements.txt

The following is the vip_requirements.txt used in the Dockerfile, extracted from the VIP.yml in this repo.
aniso8601==8.1.1
anndata==0.7.4
attrs==20.3.0
batchglm==0.7.4
bleach==3.2.3
boto3==1.14.39
botocore==1.17.44
brotli==1.0.9
cffi==1.14.4
chardet==4.0.0
click==7.1.2
cycler==0.10.0
dask==2021.1.1
defusedxml==0.6.0
diffxpy==0.7.4
docutils==0.15.2
entrypoints==0.3
fastobo==0.9.3
flask==1.1.2
flask-compress==1.8.0
flask-cors==3.0.10
flask-restful==0.3.8
flask-server-timing==0.1.2
flask-talisman==0.7.0
flatbuffers==1.12
flatten-dict==0.3.0
fsspec==0.7.4
get-version==2.1
gunicorn==20.0.4
h5py==2.10.0
idna==2.10
iniconfig==1.1.1
itsdangerous==1.1.0
jinja2==2.11.2
jmespath==0.10.0
joblib==1.0.0
jsonschema==3.2.0
jupytext==1.6.0
kiwisolver==1.3.1
legacy-api-wrap==1.2
llvmlite==0.35.0
markdown-it-py==0.5.8
markupsafe==1.1.1
matplotlib==3.3.4
mistune==0.8.4
natsort==7.1.1
nbconvert==5.6.1
nbformat==5.1.2
networkx==2.5
numba==0.52.0
numexpr==2.7.2
numpy==1.19.5
packaging==20.9
pandas==1.2.1
pandocfilters==1.4.3
pathlib2==2.3.5
patsy==0.5.1
pillow==8.1.0
plotly==4.8.1
pluggy==0.13.1
py==1.10.0
pyarrow==1.0.1
pycparser==2.20
pyparsing==2.4.7
pyrsistent==0.17.3
pytest==6.2.2
pytz==2020.5
pyyaml==5.4.1
requests==2.25.1
retrying==1.3.3
rpy2==3.3.5
s3fs==0.4.2
s3transfer==0.3.4
scanpy==1.6.1
scikit-learn==0.24.1
scipy==1.6.0
seaborn==0.11.1
setuptools-scm==5.0.1
sinfo==0.3.1
sparse==0.11.2
sqlalchemy==1.3.22
statsmodels==0.12.1
stdlib-list==0.8.0
tables==3.6.1
testpath==0.4.4
threadpoolctl==2.1.0
tiledb==0.7.7
toml==0.10.2
toolz==0.11.1
tqdm==4.56.0
tzlocal==2.1
umap-learn==0.4.6
urllib3==1.25.11
webencodings==0.5.1
werkzeug==1.0.1


ENH: define_app decorator propagates docs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 91.316%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
177728

Relevant Lines:
194630

💛  - Coveralls


linux sysfs pin export race

The linux sysfs gpio interface has a race:
root@honeybee:/sys/class/gpio>echo 84 > export ; echo out > gpio84/direction
bash: echo: write error: Device or resource busy

ghci> writeFile "export" "89" >> writeFile "gpio89/direction" "out"
*** Exception: gpio89/direction: hClose: failed (Unknown error 517)

It takes some short time for the export to complete, before that the directory for the pin may not yet exist, or the kernel may be unprepared to handle requests made there.
This seems like the kind of thing that users of hpio, at least the cross-platform part of it, should not need to worry about. I'm only just reading the documentaton for hpio, and have not checked it in the real world to see if it can crash in such a situation.
But, looking at the code of exportPin and System.GPIO.Linux.Sysfs.Monad, I don't see any indications that it tries to deal with this race. A good way to deal with it might be a brief busy-wait on exporting the pin for the pin directory to be created and the direction file to be readable.

Thanks for the report. I don't think I've seen this is actual use, but I'll take a look at the code.
What is the platform you're using to produce this race in bash?

I've seen the race on a cuietruck running debian testing with the stock
debian kernel (4.15.11).
However, the bash example is wrong; I forgot that gpio pin 84 was
actually already enabled, and the double-enable is what failed there,
thus the "busy". Sorry for the bad example.
The haskell example does demonstrate the race. I've not seen it fail in
hClose like that before; all the times I can remember before when I
dealt with this race the gpioXX directory didn't exist yet immediately
after exporting the pin.
--
see shy jo


Variable Liveness At

We already have HighLevelILFunction.is_ssa_var_live, which returns whether a variable is ever used in a function.  We should also have the more complete/correct version of liveness for at a given IL instruction.

Added in 2.4.3078-dev as HighLevelILFunction.is_var_live_at and HighLevelILFunction.is_ssa_var_live_at.


Cleanup attributes

Enable rules

CA1018: Mark attributes with AttributeUsageAttribute
CA1813: Avoid unsealed attributes

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues
Fixes #10119

You can test this PR using the following package version. 11.0.999-cibuild0029446-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

Part of #8944

You can test this PR using the following package version. 11.0.999-cibuild0029452-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


feat: configurable flagd metrics port

This PR

adds a configuration option for the flagd metrics port via the featureflagconfiguration crd

Related Issues

#113
Notes

Follow-up Tasks

How to test

This is a nice addition, something i think I removed in the initial addition

https://github.com/open-feature/open-feature-operator/issues/113


change the null reference to empty object in UrlMappingPattern.java

Motivation
change the null reference to empty object in UrlMappingPattern.java    issue#4136
Modifications
change return null to a empty map
Documentation
No

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@heliang666s The target branch you merge this PR into should be master instead of develop. By then you should be able to pass CI.
Developing with a branch that corresponds to a single issue minimizes the chance that you'll run into any Git difficulties.
By the way, kindly refer to the standard title format used in other PRs.
@mxsm How about delete this outdated develop branch?

@heliang666s Please resolve conflicts.
@mxsm The The base branch was changed. comment was a automatic message sent by GitHub.


[BUG]Post upgrade to 2.7.1 unable to open or install helm charts in clusters

Rancher Server Setup

Rancher version: 2.7.1
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE2

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.24.4
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:

Describe the bug
We have upgraded the rancher version from 2.6.8 to 2.7.1 we are unable to install helmcharts from cluster tools in downstream cluster. Post click on install getting blank page for all helmcharts.
To Reproduce
click on install or edit the existing charts will get blank screen
Result
Blank screen
Expected Result
Should give parameters to select for install.
Screenshots

Additional context

We had this issue on 2.7.0 too, seems to be a known issue
https://github.com/rancher/dashboard/issues/7808


fix io_uring error

from the debug info below , we know the io_uring error is caused by the unalignment of offset
$3 = (iomgr::drive_iocb) {
  _vptr.drive_iocb = 0x55555a4a5908 <vtable for iomgr::drive_iocb+16>,
  static inlined_iov_count = 4,
  iodev = 0x55555ae71e00,
  iface = 0x55555acd7720,
  op_type = iomgr::DriveOpType::WRITE,
  size = 1024,
  offset =<PHONE_NUMBER>5,
  unique_id = 0,
  iovcnt = 1,
  result = -22,
  completion = std::variant<> [no contained value],
  resubmit_cnt = 0,
  part_read_resubmit_cnt = 0,
  initiating_reactor = 0x0,
  iocb_id = 2,
  op_start_time = {
    __d = {
      __r =<PHONE_NUMBER>7526470
    }
  },
  op_submit_time = {
    __d = {
      __r = 0
    }
  },
  user_data = std::variant<std::array<iovec, 4>, std::unique_ptr<iovec[]>, char *> [index 0] = {{
      _M_elems = {{
          iov_base = 0x55555c3e2400,
          iov_len = 1024
        }, {
          iov_base = 0x0,
          iov_len = 0
        }, {
          iov_base = 0x0,
          iov_len = 0
        }, {
          iov_base = 0x0,
          iov_len = 0
        }}
    }}
}

closed , and this change will be included in #381

closed , and changes in this PR will be made in #381


line break function failure

line break function for scrolled panels always uses the last letter at the beginning of the next line again.

Bug is caused by the string.rsplit() function which is used to split words which stack over the right border. string.rsplit() silently strips whitespaces away which never appear again. This is acceptable at the end of words, but is a big problem for long words which happen to stand alone on one line. The former line ends without a space, so the next line has to start with one. string.rsplit(None, 1) with one single word which starts with a whitespace returns exactly that word, but without a whitespace. That causes truncline() to return a length which is valid, because it is the same length as the word which is displayed, but is also wrong, because it lacks the whitespace(s) at the beginning, which will later on be stripped away but result in single letters as left-overs. The more long words one text contains, the more letters will be repeated over time.


Add multithreaded Shuffle test [databricks]

This fixes https://github.com/NVIDIA/spark-rapids/issues/7530
Added Multithreaded shuffle test as part of CI's integration tests run for both DB and non-DB Spark versions.
Targeting it to  23.02 as it only impacts tests. Please let me know if it needs to be moved to 23.04

build

build

build

I see that databricks build is invoking multihreaded shuffle and the tests are failing. Not sure if there is any other configs to set here.
[2023-02-03T01:09:54.365Z] + rapids_shuffle_smoke_test
[2023-02-03T01:09:54.365Z] + echo 'Run rapids_shuffle_smoke_test...'
[2023-02-03T01:09:54.365Z] Run rapids_shuffle_smoke_test...
[2023-02-03T01:09:54.365Z] + PYSP_TEST_spark_rapids_shuffle_mode=MULTITHREADED
[2023-02-03T01:09:54.365Z] + PYSP_TEST_spark_rapids_shuffle_multiThreaded_writer_threads=2
[2023-02-03T01:09:54.365Z] + PYSP_TEST_spark_rapids_shuffle_multiThreaded_reader_threads=2
[2023-02-03T01:09:54.365Z] + PYSP_TEST_spark_shuffle_manager=com.nvidia.spark.rapids.spark312db.RapidsShuffleManager
[2023-02-03T01:09:54.365Z] + SPARK_SUBMIT_FLAGS=
[2023-02-03T01:09:54.365Z] + TEST_PARALLEL=1
[2023-02-03T01:09:54.365Z] + bash /home/ubuntu/spark-rapids/integration_tests/run_pyspark_from_build.sh -m shuffle_test --runtime_env=databricks --test_type=nightly
[2023-02-03T01:09:54.365Z] +++ dirname /home/ubuntu/spark-rapids/integration_tests/run_pyspark_from_build.sh

build

build

Thanks @gerashegalov for helping in debugging it further and thanks @abellina for providing the fix for the test failures. Tests are passing now.

build


1.12.x TNT becomes PrimedTNT, fizzles, and disappears immediately when triggered by specific scenarios of redstone energy

TNT will prime, flash, make a fizzle sound and disappear when powered by SOME configurations of being powered by redstone energy, just POOF out of existence.
All versions of 1.12.2 SpongeForge and SpongeVanilla and likely further back through 1.12s
Default sponge configs, plus or minus Panda redstone, Panda settings=no difference.

Specific observations generalized from test scenarios suggest 0/1/2 redstone tick differences, easily reproduced:

If TNT is placed by the player into a location that is powered, no matter how, when placed->POOF
If TNT is pushed by a piston into a powered location, it is normal (flashes and explodes=BOOM)
If piston pushes a block of redstone, or completes a circuit that powers the tnt block adjacent to the final position (ie, push wool over a redtorch or between a powered repeater and tnt) -> POOF
A redtorch placed beside TNT, or offtorch beside tnt that becomes powered -> BOOM
An unpowered repeater/comparator aimed at tnt, when powered -> BOOM
Placing a redwire between a on-torch and tnt-> POOF
Placing a redtorch onto a powered block results in the redtorch flicker before going off, but that is sufficient to prime adjacent tnt->POOF

--
To further complicate things, the oldest forge tested seemed to actually have explosions even though invisible for some tests, and some of those destroyed the blocks when making the noise, while some of the others sounded the blast but did not damage any blocks (until logout/login).  (Have not tested older SV)
==
I realize now this bug was likely present for a while, as I was encountering a lot of oddities related to these scenarios while porting a tnt-regulating plugin prior to cause/context versions; but do not know how earlier, as it was only then discovering that my handlers were not responding to their BlockSnapshot root filters, having been changed to LocatableBlocks causes some time sooner.

Can confirm.


SPAPT/mvt source annotation error

This annotation would cause the parser fail.
https://github.com/brnorris03/Orio/blob/3e35c3e3d51cb94539164df9609b3fe0178ec737/testsuite/SPAPT/mvt/mvt.ancc.src1.c#L49
It seems the file spec grammar is defined here:
https://github.com/brnorris03/Orio/blob/3e35c3e3d51cb94539164df9609b3fe0178ec737/orio/main/tspec/pparser.py#L126
Not sure why it fails. One easy fix is to move the let stmt into the def block as a statement to parse but not sure if that's what we want here.

If SIZE is an input parameter, then it should be moved to input_params just below -- not sure why it was left outside of a section, this must be old obsolete syntax. There shouldn't be things like that outside of sections.

Ok. I will make a PR to fix it. Thanks!


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>
I can't open the spyder program, the truth is that it's been 3 hours and it's a little frustrating, I had an environment to run a code that I had on another computer, it should be noted that the code ran fine on the other computer, the code entered a bug, force close and now I can't open it.

Hey @Rimpelio, thanks for reporting. It seems you're using a very old Spyder version (3.2 or 3.3), which is not supported anymore. Please update to our latest version (5.5.1 in Anaconda, 5.5.5 outside it) and try again.
Let us know if it works for you.

Closing due to lack of response.


Workflows are referencing vulnerable actions

Hello, there!
As part of the university research we are currently doing regarding the security of Github Actions, we noticed that one or many of the workflows that are part of this repository are referencing vulnerable versions of the third-party actions. As part of a disclosure process, we decided to open issues to notify GitHub Community.
Please note that there are could be some false positives in our methodology, thus not all of the open issues could be valid. If that is the case, please let us know, so that we can improve on our approach. You can contact me directly using an email: ikoishy [at] ncsu.edu
Thanks in advance

The workflow release-notes.yml is referencing action gittools/actions/gitversion/setup using references v0.9.9. However this reference is missing the commit 90150b4 which may contain fix to the vulnerability.
The workflow release-notes.yml is referencing action gittools/actions/gitversion/execute using references v0.9.9. However this reference is missing the commit 90150b4 which may contain fix to the vulnerability.

The vulnerability fix that is missing by actions' versions could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider updating the reference to the action.
If you end up updating the reference, please let us know. We need the stats for the paper :-)

@igibek thanks for the heads-up. This is only a remnant in master. develop already points to the current 0.9.11 release.
The next time that specific workflow will run will be after a merge from develop to master, so by then the reference will be updated.


[Bug][chunjun-connector-pgwal] pgwal does not support uppercase schema or uppercase table

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

What you expected to happen
1
How to reproduce
通过postgresql客户端
1.创建schema语句：create schema "LWJDB"
2.创建表：
CREATE TABLE "LWJDB"."test"(
COL1            INT ,
COL2        INT
);
Anything else
No response
Version
master
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

PR merged. #1273


localResource: false positives!

A false positive error, or in short a false positive, commonly called a "false alarm", is a result that indicates a given condition exists, when it does not.
MissingLocalResourceChecker delivers too many false positives, e.g. the URL
/examples

is marked nonexisting, even if a file
/examples.html

exists

started writing some better Specifications for it...

First: thanks, this looks really promising! Now, also in reference to the "start local webserver to improve checks": No! There lies madness this way. A webserver can be configured to apply the craziest transformations on the static pages. Finding the index file is the simplest one. There is the Apache spelling correction plugin for example: Apache finds a file, if the request is for a similiarly named one. Is it therefore a false positive, if there are only small deviations between href and file name?!? I suggest to not make htmlSanityCheck too smart/too forgiving. Now about these indexes: by default, I would not apply some Apache index file search (default) logic. I would make it a configurable how the index file is found for a directory. You could even offer the option that finding a directory is sufficient: after all, there is also the Apache index generation plugin that generates an index file for a directory on the fly (disabled most of the time for security reasons).


trust-manager and Kubernetes version compatibility

Hello,
I want to use trust-manager but on previous K8s versions like 1.19 and 1.21. I ran through previous releases of trust-manager and your compatibility matrix looks like:

trust-manager version
kubeVersion

latest (v0.7.0)
>= 1.25.0-0

v0.6.0
>= 1.22.0-0

v0.5.0
>= 1.22.0-0

v0.4.0
>= 1.22.0-0

v0.3.0
no kubeVersion in Chart.yaml

My questions are:

Do you remember what was behind introducing requirement kubeVersion >= 1.22.0-0 in v0.4.0?
Was this requirement also valid in previous releases, but simply not included in Chart.yaml? In other words, do you think we can try to use v0.3.0 for kubeVersion=1.19?

@kichel98 The K8s requirements were introduced in https://github.com/cert-manager/trust-manager/commit/57f6cdfc5974865bddd3eb3536a38cdaaed6f225, and I am not sure why 1.22 was chosen as the minimum K8s requirement. Trying out trust-manager 0.3.0 on your legacy clusters is probably worth a try. But you should really consider upgrading to newer Kubernetes. These versions have been EOL for a long time now: https://endoflife.date/kubernetes

Thank you, I'll try. Could you send me a link to docs for this version?

I don't think we have docs for such old versions available anymore. I suggest you upgrade to a supported version of trust-manager.
/close


Make all settings overwritable

By adding a !default to the _settings.scss file. Now only just one was enabled to be overwritten.

I was just about to PR the same thing.  This is a great idea and is common in other variable configured scss components like those in bootstrap-sass.

@yuvilio, !default settings are added in  https://github.com/dimsemenov/Magnific-Popup/blob/master/src/css/main.scss#L34 , `_settings.scss if ile for you to modify. See PR https://github.com/dimsemenov/Magnific-Popup/pull/78/files

Wow. Glossed over that. Thanks @dimsemenov.


Throw for incorrect variable names

I accidentally did this:
query Artist($slug: String!) {
  artist($slug: $slug) # notice the incorrect dollar sign $slug on the left

  # it should be artist(slug: $slug)
}

There's an unnecessary $ in the variable name. I'd expect this to turn red, as the $slug variable name doesn't exist for artist(slug)

This bug seems specific to graphql as a function invocation 😅 just works for the normal template literals, just researching atm

Published in 0.11.2, thank you so much for helping me dog-food this and reporting the issue!

Of course! Always want to support what you guys do.
Thanks for the quick fixes.


Fix a comment in a sample

Can one of the admins verify this patch?

@tensorflow-jenkins test this please

Merged. Thanks.


get_product_fees_estimate_for_asin endpoint multi currency crash

We are unable to submit the marketplace_id for endpoint "get_product_fees_estimate_for_asin". If we enter "MXN" as the currency, amazon returns an error because by default it searches the Americas marketplace, but to send "MXN" we have to set the marketplace to Mexico.
My Code
    product_fee_response = ProductFees(credentials=credentials).get_product_fees_estimate_for_asin(         marketplace_id=Marketplaces.MX.marketplace_id,         asin=request.asin,         price=1080,         currency="MXN",         is_fba=True,     )
Amazon Return
{"FeesEstimateResult":{"Status":"ClientError","FeesEstimateIdentifier":{"MarketplaceId":"ATVPDKIKX0DER","IdType":"ASIN",
Result:
I send MX marketplace_id but amazon return US marketplace_id

Hi,
Can you please try to run with the marketplace passed to the client: ProductFees(credentials=credentials, marketplace=Marketplaces.MX)

Hi,
Can you please try to run with the marketplace passed to the client:
ProductFees(credentials=credentials, marketplace=Marketplaces.MX)

I got this error. message
AttributeError: 'Marketplaces' object has no attribute 'region'

That's quite unlikely if you're using Marketplaces from sp_api.base. I've added a commit that allows to pass a marketplace_id as a parameter to the method. Please check out v0.12.3 in a couple of minutes.
However, I'd suggest to use `ProductFees(marketplace=Marketplaces.MX, credentials=credentials)

I'm sorry The auto import, import Marketplaces from mws. I changed it to sp_api.base and my problem was fixed. Thanks.


Add cabal new-build-based wrapper script

This PR depends on #192 (and includes that commit)

Could you explain what cabal new-build is doing? I did a quick search for it yesterday, but couldn't find any documentation. If you've got a link, please share it.

@snowleopard Sadly, it's still undocumented, but this will probably change very soon. cabal new-build (together with the cabal.project-feature) is the entry point to the bleeding edge tech-preview of the new nix-store based cabal UI. It's still very rough, and lacks some needed UI porcelaine.
Also, the code still lives in a Git branch that's frequently synced up to master but not yet merged into Cabal's master branch, but I hope @dcoutts will soon merge...
However, it's already usable enough for me that I'm able to dogfood new-build myself for almost everything I work on, and I'm quite excited about it... :-)

Thanks for the clarification!


Cosmetic changes to the notebooks

Here is a listing of necessary corrections/checks:

[x] Use concatenation consistently.
[x] Use consistent notation for concatenated trajectories.
[x] Use stride more effectively in cluster_kmeans() to prevent long execution times.
[ ] Check all variables names for consistency.
[ ] Use consistent sizes when plotting figures.
[x] Check that all exercises are correctly set up.
[x] Rename/sort the notebooks.
[ ] Prevent or hide warnings.
[ ] Check that all wrapping up sections are complete.
[x] Check all LaTeX strings and replace non-LaTeX strings where applicable.

Feel free to extend this list.

Warnings:
I've tested all the NBs with the latest pyemma devel version and find the following:
Featurization.  Concerns notebooks 01, 02, 05.

16-07-18 14:59:00 pyemma.coordinates.data.featurization.featurizer.MDFeaturizer[23] WARNING  The 1D arrays input for add_distances() have been sorted, and index duplicates have been eliminated.
Check the output of describe() to see the actual order of the features

16-07-18 15:00:22 pyemma.coordinates.data.featurization.featurizer.MDFeaturizer[28] WARNING  Using all residue pairs with schemes like closest or closest-heavy is very time consuming. Consider reducing the residue pairs

Another class of warning messages appears in certain CK-tests in notebook 06 [20, 21, 29]:
/home/mi/thempel/mystorage/software/pyemma/pyemma/util/statistics.py:60: UserWarning: confidence interval for constant data is not meaningful
warnings.warn('confidence interval for constant data is not meaningful')
The same warning occurs in and in 07 [21, 22] because sample_conf() is called for msm.correlation() which returns a tuple of times and correlations.
Any ideas on that? The confidence interval warnings are not wrong, but not very useful either...
Notebook 08 naturally comes with some warnings.

Another class of warning messages appears in certain CK-tests in notebook 06 [20, 21, 29]:
/home/mi/thempel/mystorage/software/pyemma/pyemma/util/statistics.py:60: UserWarning: confidence interval for constant data is not meaningful
warnings.warn('confidence interval for constant data is not meaningful')

The same warning occurs in and in 07 [21, 22] because sample_conf() is called for msm.correlation() which returns a tuple of times and correlations.

This part is still not resolved and probably requires some changes in pyEMMA.


Finish implementing tip-name and tip-description

tip-description needs implemented on minimap and category menus.
tip-name needs implemented on category menus.

This has been completed.
https://blishhud.com/docs/markers/attributes/tip


Support for package cleanup.

A menu option labelled "Clean packaged addins" should be added.
This will delete any .mrep and .mpack files for the project.

Support added in 96093da84112545eeea434d1985750ba458512d5


Cannot delete items from quest success mail.

Deleting items from the recieve mail stash(quest accept items and quest success items. Havent had time to test gifts/other ways to recieve mail) doesnt actually delete them.
Repo steps: Make bear dev account. delete items in mail reload client still remain.

Originally written by Kaeno

Fixed with: https://dev.sp-tarkov.com/SPT-AKI/Server/commit/bea44621552bf7c78b67c931923eb0bd4282a213

Originally written by chomp


chore(tests): remove various redundant python-request mocks

They are not needed now that scheduler uses a request mock in the background

Current coverage is 81.80%

Merging #547 into master will decrease coverage by -0.04% as of a906570

@@            master   #547   diff @@
=====================================
  Files           36     36
  Stmts         2303   2303
  Branches       331    331
  Methods          0      0
=====================================
- Hit           1885   1884     -1
- Partial        115    116     +1
  Missed         303    303

Review entire Coverage Diff as of a906570

Powered by Codecov. Updated on successful CI builds.


allow fetch to work with arbitrary tag formats

This is a PR according to the specifications designed in issue https://github.com/gruntwork-io/fetch/issues/16

I am unable to run test. I see the following error.
ERROR: These tests require that env var GITHUB_OAUTH_TOKEN be set to a GitHub Personal Access Token.
See the tests cases to see which GitHub repos the oAuth token needs access to.
exit status 1
FAIL	_/home/amir/git/amirhammad/gocode/fetch	0.003s

Could you help?

As the error message says, you need to set the GITHUB_OAUTH_TOKEN environment variable. Follow these instructions to get a token. Expose it as an env var as follows:
export GITHUB_OAUTH_TOKEN=(your token)

Then run the tests.
Note that the tests that access private GitHub repos in the gruntwork-io repo will fail; you can ignore those.

Thank you for your help. I added two commits. Output of the command go test is:
--- FAIL: TestDownloadReleaseAsset (0.62s)
	github_test.go:191: Failed to download asset %!s(int=1872521) to /tmp/test-download-release-asset839253382 from GitHub URL https://github.com/gruntwork-io/fetch-test-private due to error: 401 - Received HTTP Response 401 while fetching releases for GitHub URL https://github.com/gruntwork-io/fetch-test-private. Full HTTP response: {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
--- FAIL: TestGetGitHubReleaseInfo (0.63s)
	github_test.go:155: Failed to fetch GitHub release info for repo aa33a due to error: 401 - Received HTTP Response 401 while fetching releases for GitHub URL https://github.com/gruntwork-io/fetch-test-private. Full HTTP response: {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
--- FAIL: TestGetListOfReleasesFromGitHubRepo (0.91s)
	github_test.go:29: error fetching releases: 401 - Received HTTP Response 401 while fetching releases for GitHub URL https://github.com/gruntwork-io/fetch-test-private. Full HTTP response: {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
--- FAIL: TestDownloadGitBranchZipFile (0.78s)
	file_test.go:80: Failed to download file: 500 - Failed to download file at the url https://api.github.com/repos/gruntwork-io/fetch-test-private/zipball/sample-branch. Received HTTP Response 401.
--- FAIL: TestDownloadGitTagZipFile (0.56s)
	file_test.go:46: Failed to download file: 500 - Failed to download file at the url https://api.github.com/repos/gruntwork-io/fetch-test-private/zipball/v0.0.2. Received HTTP Response 401.
--- FAIL: TestDownloadGitCommitFile (1.70s)
	file_test.go:145: Failed to download file: 500 - Failed to download file at the url https://api.github.com/repos/gruntwork-io/fetch-test-private/zipball/676cfb92b54d33538c756c7a9479bfc3f6b44de2. Received HTTP Response 401.
FAIL
exit status 1
FAIL	_/home/amir/git/amirhammad/gocode/fetch	2.330s

If the CI tests pass, I'll create a new release of fetch, and you'll be able to grab new binaries there.

Maybe using some CI tool, you can at least show status of those tests here in github pull requests. TOKEN can be stored encrypted in the repository and then decrypted by the CI to run tests (shippable, travis, other?).
Thank you for a great tool

Looks great, guys. Just don't forget to update the README.md to clarify that fetch now supports downloading a specific tag.

https://github.com/gruntwork-io/fetch/releases/tag/v0.0.10


Iconsets: Author credits and periodic icon change

Small update:

Adds credits for who added each icon set

Sources for each iconset in our tracker are actual game sprites/portraits so don't know if we need to explicitly credit those anywhere, not sure where there'd be room to do so (could maybe be in README and/or one of the wiki pages if we wanted them?)

Adds an interval at which the icon randomly changes, in addition to being able to click to cycle them

Interval is currently set to effectively every 180 frames, after accounting for the current screen redraw interval (30 frames)
Could maybe remove the click functionality if wanted, kept it in if you wanna spam-click to view a bunch in a row lol

This screen is now looking a little cramped tbh lol tried to space it out best I could
Don't think we're planning to add new settings here soon anyways (and can deal with the space at that time)
One suggestion I have, if we ever make any new add-ons, would be to have the tracker add-ons be a separate menu screen on the tracker options (either accessed from the setup menu or the navigation menu)

changes made, also made it reset on changing the pokemon icon by clicking it too (so any of the three existing iconset buttons) so you have time to view the one you clicked and got it changed to


When updating an entry that contains a matrix field that has an asset field, the entire matrix field is deleted

I am running an import on a section of entries for a locale other than the default. The import is set to update only and matching on existing element ID. I have also tried matching on the slug and see the same result.
All of the entries have a Matrix Field that contains an Asset Field. I have the Matrix Field set to "Do Not Import". When running the import, the Matrix Field is deleted from each entry. I ran a test where I removed the asset field from the Matrix Field before running the import. I then re-ran the same import and the Matrix Field was not deleted.
In addition, I am now seeing the issue again where all entries that have been updated are enabled for the locale, even if they were not enabled for that locale before running the import. I have the status set to "Do Not Import".

I'll investigate the Matrix issue, as it acts differently to most other elements - compounded by Locales.
For the Locales, do you have Default Entry Status for the section set to disabled?

Thank you for looking into the issue. I have default entry set to enabled for en_us and disabled for the other 5 locales. When running the import on any of the locales they are enabled regardless of their previous state. It's possible they are inheriting the en_us status.
The deletion of the Matrix Field only seems to happen when it contains an asset field.

On Feb 14, 2017, at 3:40 PM, Josh Crawford<EMAIL_ADDRESS>wrote:
I'll investigate the Matrix issue, as it acts differently to most other elements - compounded by Locales.
For the Locales, do you have Default Entry Status for the section set to disabled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, I had the same issue with Feedme 2 beta 2. It deleted matrix fields with asset field even if it was set to "Don't import". My entries are by default enabled in the 3 languages.
Thanks

The Matrix/Asset issue should now be fixed in the latest master. The issue was element options (Assets, Entries, etc) were still being passed to Matrix, despite no data being present. This cause the Matrix field to think there was content to import.
The locale enabling issue has also been resolved. It previously forced a locale to be enabled, and will now simply leave as-is.

I have confirmed this is Update is working perfectly after several rounds of imports, thank you for the update!

On Feb 17, 2017, at 4:23 AM, Josh Crawford<EMAIL_ADDRESS>wrote:
Closed #158.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


End-to-end beginner walkthrough link is broken

https://docs.chain.link/docs/example-walkthrough

This link was replaced with https://docs.chain.link/docs/user-guides/
All of the guides that were included in that link are included in this section for quite a while now.


Allow log format to be configured from profiles.yml

Describe the feature
Allow the following in profiles.yml config log_format: text|json
Additional context
Allows this to not need to be set for multiple commands in a single run, while also being disabled in one location for development.
Who will this benefit?
Devs, people with custom pipelines
Might see if I can land this myself over the weekend :)

cool idea @elexisvenator :)


PHP-7 compatible dependencies?

While I was working on packaging of php7cc to introduce it to Debian it came to my attention that php-pimple (direct dependency of php7cc) is not compatible with PHP-7.
Debian is dropping PHP-5 so I wonder if php7cc could switch to PHP-7 compatible alternative of Pimple? The latter FTBFS with PHP-7...

I'm not familiar with the Debian packaging process. Why does it require building the Pimple C extension from source? Why isn't the pure PHP implementation sufficient?

Everything is built from source in Debian. Please forgive my PHP illiteracy but I don't know whether pure PHP implementation is sufficient. I suppose that would be question to maintainer or to Pumple developer(s)...

Pimple has 2 independent interchangeable implementations: the pure PHP one and the C extension. The latter, which is incompatible with PHP 7, can be used in environments having high performance requirements, but it is completely optional. The former, on the other hand, seems to be compatible with PHP 7. Its tests pass on PHP 7.0.6-dev. And php7cc only depends on the pure PHP implementation. In fact, it was never even tested against the C extension. So I don't see why a dependency on Pimple is an issue.

Thank you for explanation. Pimple is currently an issue because it FTBFS (at least its C extension part). I'll see if I can address that...

Thanks again for helpful hints. For now we won't build Pimple C extension due to incompatibilities with PHP-7. Pimple class seems OK and that should do as php7cc dependency. :)


Rerun examples and add aio deploy_local/remote

Reruns examples and recreated markdown with cell contents
Add conda.yaml files to git where needed
Update asyncio for new options and deply local/remote

Looks good, just added two comments, as may be worth leaving the outputs for the MAB notebook, as well as the KFServingOptions variable

Merging - we can update the kfserving options separate


Problem with generics in Signatures

I'm providing glint support for ember-element-helper tildeio/ember-element-helper#107
Here are the types based on the ones from Dan (in tildeio/ember-element-helper#102):
export type ElementFromTagName<T extends string> = T extends keyof HTMLElementTagNameMap
  ? HTMLElementTagNameMap[T]
  : Element;

type Positional<T extends string> = [name: T];
type Return<T extends string> = typeof EmberComponent<{
  Element: ElementFromTagName<T>;
  Blocks: { default: [] };
}>;

export interface ElementSignature<T extends string> {
  Args: {
    Positional: Positional<T>;
  };
  Return: Return<T> | undefined;
}

export default class ElementHelper<T extends string> extends Helper<ElementSignature<T>> {}

Using the helper works straight away:
<template>
  {{#let (element 'div') as |Tag|}}
    <Tag id="lalala" ...attributes>Hello there!</Tag>
  {{/let}}
</template>

Going a bit more dynamic and allowing a @tag to be passed in, works when the type is made explicit:
import { type ElementSignature } from 'ember-element-helper';

interface ElementReceiverSignature{
  Element: HTMLDivElement; // 1: explicit element here
  Args: {
    tag: ElementSignature<'div'>['Return']; // 2: explicit tag name here
  };
  Blocks: {
    default: [];
  };
}

export default class ElementReceiver extends Component<ElementReceiverSignature> {
  <template>
    {{#let @tag as |Tag|}}
      <Tag id="content" ...attributes>{{yield}}</Tag>
    {{/let}}
  </template>
}

... of course those explicit types do not make sense, when we want to have any element being passed in. Making it generic makes the problem visible:
import {
  type ElementFromTagName,
  type ElementSignature
} from 'ember-element-helper';

interface ElementReceiverSignature<T extends string> {
  Element: ElementFromTagName<T>;
  Args: {
    tag: ElementSignature<T>['Return'];
  };
  Blocks: {
    default: [];
  };
}

export default class ElementReceiver<T extends string> extends Component<
  ElementReceiverSignature<T>
> {
  <template>
    {{#let @tag as |Tag|}}
      <Tag id="content" ...attributes>{{yield}}</Tag>
    {{/let}}
  </template>
}

This reveals two locations where glint throws both times the same error:

<Tag and
...attributes

Wit the error message being:
Argument of type 'NonNullable<ElementFromTagName<T>> extends never ? unknown :
ElementFromTagName<T>' is not assignable to parameter of type 'Element'.

  Type 'unknown' is not assignable to type 'Element'.glint(2345)

As to my understanding, the types for the signature are correct, but the error message is wrong. The ElementFromTagName will always return a valid type, in either explicit HTMLElementTagNameMap[T] or generic Element which should be accurate inside the component (typing the unknownigly character of @tag).
Is this a valid problem with glint? Or are my typings wrong?

It might work to change this line:
https://github.com/typed-ember/glint/blob/3d4e0685523853702c4b4e54f76dcb726fe89a32/packages/template/-private/signature.d.ts#L48
to something like ? Element extends null
But I don't have the capacity right now to verify that that doesn't adversely affect some other area of inference, so someone else will need to take a look. We should have decent test coverage for this.


Add wholesale rename in the MultiQC report

@MatthiasZepper noted in https://github.com/nf-core/rnaseq/pull/1308 that running UMItools extract resulted in inconsistent sample naming in the multiqc report.

This is because if a sample does not have technical replicates, the input fastq files go to the umitools extract process without ever going through a process that applies a suffix, and the relevant MultiQC module effectively uses the input file name to derive a sample name.
One fix we should definitely apply is to have MultiQC use the output (possibly prefixed) file name as the source of identifier: https://github.com/MultiQC/MultiQC/pull/2698.
However it probably also makes sense to be defensive, and tell MultiQC to rename any other related occurrences that come up in future. That's what this PR does, using the sample sheet to derive a set of replacements to pass to multiqc via --replace-names (to be clear this is also an immediate fix for the umi tools issue until if/ when it's fixed in MultiQC).
PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@MatthiasZepper - it probably was a little arcane (I blame Friday afternoon head) - simplified a bit now

@MatthiasZepper

ch_fastq.single is of course the wrong channel (since it containes the unpaired samples and not those with just one pair)

No, you were right first time :-). ch_fastq.single contains all those samples with a single ([read1] or [read1, read2]) tuple after the groupTuple(), so ch_fastq.single is the right way to go!

Thanks @MatthiasZepper , all good :-).


[DS-6988][MasterServer] add cache manager for workflow

#6988
Brief change log

add the cache annotation to mapper instead of cache processor, more easily.
add the cacheEvictAspect to handle the @cacheEvict logic for apiServer.
unified processing cache evict in CacheProcessor for masterServer.

@caishunfeng  Does this issue merged will close #6988, if so please use keyword fix: #issue_id or close: #issue_id or closes: #issue_id in your PR describe(not title, jus desc)


Fix module prefixing for type names

Description
Through a bit of debugging I learned that string(Type) will include the parentmodule(Type) as a prefix in some contexts and not others (😢). This affects the hash of types (at least until #55 merges) and therefore affects pretty much any hash value (since they all hash their type). This PR checks for the parentmodule prefix in string(Type) to make sure that the downstream output is consistent.
I opted to fix this bug only for a new hash version=3 because it is entirely possible that existing uses of the older hash versions depend on the old, broken behavior. Indeed, some of the reference tests I wrote depend on it.

To always get the prefix printed, you can do sprint(print, T; context=(:module=>nothing,)):
julia> using LinearAlgebra

julia> import Distributed

julia> string(Cholesky)
"Cholesky"

julia> string(LinearAlgebra.Cholesky)
"Cholesky"

julia> string(Distributed.RemoteChannel)
"Distributed.RemoteChannel"

julia> sprint(print, Cholesky; context=(:module=>nothing,))
"LinearAlgebra.Cholesky"

julia> sprint(print, Distributed.RemoteChannel; context=(:module=>nothing,))
"Distributed.RemoteChannel"

To always get the prefix printed, you can do sprint(print, T; context=(:module=>nothing,)):
julia> using LinearAlgebra

julia> import Distributed

julia> string(Cholesky)
"Cholesky"

julia> string(LinearAlgebra.Cholesky)
"Cholesky"

julia> string(Distributed.RemoteChannel)
"Distributed.RemoteChannel"

julia> sprint(print, Cholesky; context=(:module=>nothing,))
"LinearAlgebra.Cholesky"

julia> sprint(print, Distributed.RemoteChannel; context=(:module=>nothing,))
"Distributed.RemoteChannel"

Having looked into doing this a bit: this adds a bit of complexity to the implementation, because the problem here is that I assume that the module is not appended when using string. I don't think there is a context in which the module is never used to qualify the values. At the end both nameof and string get the module appeneded, which is why I had the bug where sometime the parent module was added twice. I'd have to write two separate implementations for the qualified_name and qualified_type. Given that this is just supposed to fix things in the short-term while the better fix in #55 gets worked out, I don't know if it's worth refactoring to make this approach work well.


[RESTEASY-3412] Migrate the resteasy-links module to JUnit 5

https://issues.redhat.com/browse/RESTEASY-3412

@jamezp Could I get a review on this?


Plugin Template Does Not Pass Build

These are tiny issues that I might be able to fix via a PR but just wanted to call these out incase anyone else could get to these before I could.
To Reproduce:

Run npx create-payload-app@latest -t plugin -n my-new-plugin
Runyarn build
Observe build fails

The build fails for 2 reasons:

The package.json needs a devDependency of webpack added yarn add webpack --dev
The onInitExtension.ts file is using payload.logger(err) and that is no longer a callable method. Need to update to payload.logger.error(err)

P.S. also if I'm in there I might add a simple watch command for the template package.json something like:
...
"scripts": {
    "build": "tsc",
    "watch": "tsc --watch",
...
}
...

Any thoughts on this appreciated.


[Deprecate]: please check camptocamp/openssl

Deprecated module
camptocamp/openssl
Replacement module
puppet/openssl
What authority do you have for making this request?
It's my module. (github username matches repo owner or contact info provided for verification), I am a Vox Pupuli PMC member, The repository has already been transferred
More information
Hi,
https://forge.puppet.com/modules/camptocamp/openssl/readme has been transferred to https://forge.puppet.com/modules/puppet/openssl/readme. The old one is already deprecated but doesn't point to the new module. Can you update that please?

camptocamp-openssl has been marked as deprecated in favor of puppet-openssl!
Hence closing the same.


Parser treats minus sign as subtraction in negative context

Expected Behavior

a = -3 + 3 should yield 0 (zero).

Actual Behavior/Symptoms

Operator - is always treated as a subtraction token (CCT_TOKEN_SUB). This can cause a stack underflow event and segmentation fault.

How to Reproduce Behavior/Symptoms

Run concoct and input: a = -3 + 3

Concoct Version

0.1.0

Compiler Version

Any

Operating System

Any

Output/Screenshot(s)
> a = -3 + 3
[1] a : Identifier
[1]  : =
[1]  : -
[1] 3 : Int
[1]  : +
[1] 3 : Int
New line ()
  = ()
    Identifier (a)
    + ()
      - ()
        Int (3)
      Int (3)
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090409) +/-2.731624] - Queue initialized with 256 slots.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090456) +/-0.000047] - Object of type number created with value: 3
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090471) +/-0.000015] - Object of type number added to object store at slot 0.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090474) +/-0.000003] - push() called on stack for object of type number. Stack now contains 1 objects.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090477) +/-0.000003] - Object of type number created with value: 3
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090480) +/-0.000003] - Object of type number added to object store at slot 1.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090482) +/-0.000002] - push() called on stack for object of type number. Stack now contains 2 objects.
Instruction: OP_SUB (0x32)
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090489) +/-0.000007] - pop() called on stack for object of type number. Stack now contains 1 objects.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090492) +/-0.000003] - pop() called on stack for object of type number. Stack now contains 0 objects.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090505) +/-0.000013] - Object of type number created with value: 0
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090510) +/-0.000005] - Object of type number added to object store at slot 2.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090513) +/-0.000003] - push() called on stack for object of type number. Stack now contains 1 objects.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090519) +/-0.000006] - peek() called on stack for object of type number. Stack currently contains 1 objects.
0
Instruction: OP_ADD (0x00)
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090530) +/-0.000011] - pop() called on stack for object of type number. Stack now contains 0 objects.
Stack underflow occurred!
Operand 1 is NULL during ADD operation.
Debug: [08/08/2023 20:20:00 EDT<PHONE_NUMBER>.090536) +/-0.000006] - peek() called on empty stack!
[1]    23491 segmentation fault

Per a recent (8/8/2023 02:43 ET) Discord conversation with @Bamalot:

"As far as the negative sign, the lexer has no way of knowing if it’s a binary or unary operation so it can only output one token type. In the node tree right now, the only way to tell the difference is that the unary negative has one child, and subtraction has 2 children. I can totally add a new token type to the parser to distinguish the two though."


PropertyValueInvalid localization

#In the old ASP.NET MVC we could add App_GlobalResources with PropertyValueInvalid to overwrite the localization for The value '{0}' is invalid (see, e.g., https://stackoverflow.com/questions/1538873/how-to-replace-the-default-modelstate-error-message-in-asp-net-mvc-2)
What's the new way to do that in ASP.NET MVC Core? I cannot find a way in the docs :(

In ASP.NET Core MVC there's a new ModelBindingMessageProvider abstract base class that has all the various messages on it. You can use its default implementation, DefaultModelBindingMessageProvider, to set a function that generates a custom message, for example, one that retrieves a localized value.
You can do all this easily in MVC's "options" configuration in Startup.cs, like so:
     services.AddMvc(options =>
    {
        options.ModelBindingMessageProvider.SetAttemptedValueIsInvalidAccessor((v, p) => $"The value '{v}' is not valid for {p}.");
    });

BTW I wrote this without testing it, so give it a shot, and let me know if it's a bit wrong 😄

@Eilon It's very cool that ASP.NET Core MVC now has a real extension point for this!
However, it would be even cooler if that code went through localization by default ;)

@Eilon : Thanks for your helpful answer! However, I'd too love to see those messages go through the localization infrastructure like @fschmied pointed out.

Oh, and furthermore, it doesn't seem to work at all :( Just tried it...
Attached you find a repro sample based upon the Visual Studio ASP.NET MVC Core template. Go to the contact page, I've added a form there, make sure to clear the input field and press Submit -> it should either give "LOL LOL LOL" or "ROFL ROFL ROFL" (see Startup), however, it still displays the standard "The value '' is invalid." message.
Any ideas?
ModelBindingMessageProvider.zip

@SteveSandersonMS - you've worked in this area before, can you help @drauch out? Apparently my previous code example was incorrect.

Found the problem -> if there is no value given, the ValueMustNotBeNullAccessor is used instead of the AttemptedValueIsInvalidAccessor!

Glad you solved that. Apologies for missing the preceding message asking for help!

@SteveSandersonMS : There is still the issue on why those do not run through the localization infrastructure by default. Everybody has to do that themselves now...

There is still the issue on why those do not run through the localization infrastructure by default.

The localization infrastructure is opt-in, requiring e.g. calls to IMvcBuilder or IMvcCoreBuilder extension methods. It may have been possible to use an IStringLocalizerFactory when available, but that's rather complicated. Which keys would we use? What resources should be referenced?
One possible setup:
    public class SomeMvcOptionsSetup : IConfigureOptions<MvcOptions>
    {
        private readonly IStringLocalizerFactory _stringLocalizerFactory;

        public SomeMvcOptionsSetup()
        {
        }

        public SomeMvcOptionsSetup(IStringLocalizerFactory stringLocalizerFactory)
        {
            _stringLocalizerFactory = stringLocalizerFactory;
        }

        public void Configure(MvcOptions options)
        {
            options.ModelBindingMessageProvider.SetMissingKeyOrValueAccessor(() =>
            {
                if (_stringLocalizerFactory == null)
                {
                    return Resources.KeyValuePair_BothKeyAndValueMustBePresent;
                }

                var stringLocalizer = _stringLocalizerFactory.Create(typeof(Startup));
                return stringLocalizer[Resources.KeyValuePair_BothKeyAndValueMustBePresent];
            });
        }
    }

Then, add the following to your Startup.ConfigureServices(...) method:
services.TryAddEnumerable(
    ServiceDescriptor.Transient<IConfigureOptions<MvcOptions>, SomeMvcOptionsSetup >());

Note Startup and Resources are sample classes from the application, not MVC.


No longer saving attention mask, option for TTS percentages

No longer saving the attention mask leads to marginal improvements in storage. TTS allows you to specify exact percentages for your splits

Do not merge yet... need to update H5 datasets to read in the attention_mask if it exists or create it if it doesn't. Not there yet

Going into develop_resolve branch, sorry I messed up 😬.


New version: vim.vim version 9.0.1240

Pull request has been automatically created using 🛫 WinGet Releaser.


read rave_dim, sample_rate and stereo where possible

Some small changes to read settings from RAVE models when possible, so to avoid unnecessary cli arguments.
The only other thing I would like to do in this direction is to read the minimum latent_size of a trained diffusion model, so that we could only provide length_mul, but I couldn't figure out how.

rave_dims: read from model, remove argument
Read rave_dims from RAVE model, like nn_tilde does (rave.decode_params[0]).

generate.py: read sample_rate from rave by default if supported (rave v2)
RAVE v2 models store their sample_rate as rave.sr. Since it doesn't make sense to choose a different one, read sample_rate from rave if possible, otherwise require the --sample_rate argument

generate.py: split stereo only if rave is stereo
RAVE stores rave.stereo = True if exported with --stereo. Check this value before splitting decoded audio in left and right, so that the model can work also with mono RAVE models.

generate: more informative progress bar and messages
Instead of a progress bar with 1 step, show the progress bar from sample, which shows diffusion steps. In my opinion it gives a more meaningful sense of progress through the task.

Hey!
Thanks for this contribution, I'll test this and the other PR in the coming days and merge.
Looks quite useful.
Best,
M


Dataset for chapter 2

In chapter 2, we are supposed to download a dataset by running a file named "download.py," but a lot of pics from it are unavailable. Can you please create an archive with this dataset and post a link?

There's a closed issue related to this - with a link to a zip file:
https://github.com/falloutdurham/beginners-pytorch-deep-learning/issues/13#issuecomment-602217738

I really appreciate that the author provides an update and available dataset! It helps me to get rid of being stuck in "download.py"


Prevent error on uncategorized channel.

If the channel is not part of a category, channel.category will be
None, and the check would fail with an AttributeError.

Thanks!

No, thank you!


Shinigami

Source information
Shinigami
Source language
Indonesia
Source new URL
https://shinigami.ws/
Other details
No response
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I will fill out all of the requested information in this form.

Oke bg

Up sir

Jejak lah


Demo code doesn't turn the pumps from the Enviro Grow kit on / off.  Written custom code to resolve issue.

The published Enviro Grow scripts doesn't have any code to control the three pumps.  I've solved this by writing some custom code.  Details as follows...
Created a new folder on the Pico called "custom".  Created two new files within the custom folder: "pumps.py" and "water_plants.py".
pumps.py
`import time
from breakout_bme280 import BreakoutBME280
from breakout_ltr559 import BreakoutLTR559
from machine import Pin, PWM
from enviro.board import i2c
bme280 = BreakoutBME280(i2c, 0x77)
ltr559 = BreakoutLTR559(i2c)
#Water pump GPIO settings
Pump_A = Pin(12, Pin.OUT)
Pump_B = Pin(11, Pin.OUT)
Pump_C = Pin(10, Pin.OUT)
def Pump_1(run):
Pump_A.value(1) # Turns pump on
print ('Pump A on')
time.sleep(run)
Pump_A.value(0) # Turns pump off
print ('Pump A off')
def Pump_2(run):
Pump_B.value(1) # Turns pump on
print ('Pump B on')
time.sleep(run)
Pump_B.value(0) # Turns pump off
print ('Pump B off')
def Pump_3(run):
Pump_C.value(1) # Turns pump on
print ('Pump C on')
time.sleep(run)
Pump_C.value(0) # Turns pump off
print ('Pump C off')
#Testing
#Pump_1(run)
#Pump_2(run)
#Pump_3(run)
`
water_plants.py
`import time
import custom
from custom import pumps
import enviro
from enviro.boards import grow
#Pump running time (seconds)
#run = 2 #For testing
run = 10 #For testing
#Dry sensor value
dry = 70
#Initiate sensor values for testing
#sensor1 = 0
#sensor2 = 0
#sensor3 = 0
#sensor2 = 100 # For testing.  To stop pump 2 from running
#sensor3 = 100 # For testing.  To stop pump 2 from running
#Initial sensor sensors
sensor_a = round(grow.moisture_readings(2000)[0],2)
sensor_b = round(grow.moisture_readings(2000)[1],2)
sensor_c = round(grow.moisture_readings(2000)[2],2)
#Checking to see if there is a sensor attached
if sensor_a == 0:
sensor_a_state = 'off'
else:
sensor_a_state = 'on'
if sensor_b == 0:
sensor_b_state = 'off'
else:
sensor_b_state = 'on'
if sensor_c == 0:
sensor_c_state = 'off'
else:
sensor_c_state = 'on'
print ('Sensor A state = ', sensor_a_state, '. Reading: ', sensor_a)
print ('Sensor B state = ', sensor_b_state, '. Reading: ', sensor_b)
print ('Sensor B state = ', sensor_c_state, '. Reading: ', sensor_c)
while (sensor_a_state == 'on' and sensor_a <= dry) or (sensor_b_state == 'on' and sensor_b <= dry) or (sensor_c_state == 'on' and sensor_c <= dry):
if sensor_a_state == 'on' and sensor_a <= dry:
    pumps.Pump_1(run)
    time.sleep(5)

if sensor_b_state == 'on' and sensor_b <= dry:
    pumps.Pump_2(run)
    time.sleep(5)

if sensor_c_state == 'on' and sensor_c <= dry:
    pumps.Pump_3(run)
    time.sleep(5)

#sensor = enviro.get_sensor_sensors()
sensor_a = round(grow.moisture_readings(2000)[0],2)
sensor_b = round(grow.moisture_readings(2000)[1],2)
sensor_c = round(grow.moisture_readings(2000)[2],2)

print ('Sensor A: ', sensor_a, ', ', sensor_a_state)
print ('Sensor B: ', sensor_b, ', ', sensor_b_state)
print ('Sensor C: ', sensor_c, ', ', sensor_c_state)

# For testing
#sensor_a = sensor_a+1
#sensor_b = sensor_b+1
#sensor_c = sensor_c+1

print ('All plants are well watered')
`
I also amended the main.py file as follows:
import custom from custom import water_plants
Inserted just above the enviro.sleep line.
# water the plants custom.water_plants
I hope this helps.

Nice, can you submit this as a pull request?

Nice, can you submit this as a pull request?

@sgtwilko, what do you mean by "pull request"?  My IT jargon dictionary isn't that great.

Hiya @RedDogUK ,
A pull request is where you start the process to get your code merged into a git repository.
There's many guides online as to how to do this, but I basically boils down to:
You fork ( make a copy of the repo) here on GitHub.
You edit your copy to include the code you want to submit (normally this would be done on a separate branch, but if you're only submitting one thing you don't have to do this step)
You then open a pull request, this is basically you asking to have your code "pulled" and merged into the original repository.
Your pull request would then be reviewed by owner of the repo, and merged if they like it.
I hope that makes sense.
I was tempted to take some of your code and integrate it myself.

Ahoy both! Thanks for picking this up. There is auto watering optionally alert tone in https://github.com/pimoroni/enviro/commit/2d722218b8c71d1b94cd9a0ccf19818affec70d4
You can set a target moisture level in config.py and either enable or disable auto watering. If auto watering is disabled then Grow will make noise when channels are below the target moisture level. It will beep once, twice, or three times depending on which channel (or if multiple channels need watering each of their beep tones will play one after another with a space between).
This will be rolled into v.0.0.7 later today or tomorrow.

Hiya @lowfatcode
Damn, I was just about to submit a PR with auto-watering!
I must have forked just before this was merged.
Looks I've taken a different approach where I check the sensors again after watering.
Want to see my solution?


Enabling partial text matches in dashboard filters

I want to use the dashboard filters to use a value for LIKE queries. Currently, if I add a filter for a column of type "Value" to a dashboard, I can only select a full value from the dropdown. It isn't possible to enter anything for partial text matches.
More details in discussion: https://github.com/apache/superset/discussions/25358

Why was this closed? It is still a needed feature.

The linked discussion is the right place to hash out a feature idea and try to recruit around it. We're attempting to keep GitHub Issues for bugs. Contributions are still quite welcome, if anyone wants to volunteer for this effort. Just note that we'll need some form of configurability or RBAC control of this, since the implementation of this feature could cause performance and cost issues for many databases.