Issue exporting .desktop file that's a link to a file in /opt

I was doing an export, and I got this:
$ HOME_DIR=$HOME/Documents/container/conty $HOME/.local/bin/conty.sh -d --bind $HOME/Games $HOME/Games --bind $HOME/Storage $HOME/Storage --bind $HOME/Documents $HOME/Documents --bind $HOME/Downloads $HOME/Downloads --bind $HOME/Pictures $HOME/Pictures
Exporting...
/home/fenglengshun/.local/bin/conty.sh: line 854: discord.desktop: No such file or directory
 Desktop files have been exported

/usr/share/applications/discord.desktop is a link to /opt/discord/discord.desktop.

Should be fixed now.

Can confirm that this is fixed, thanks!


Quick fix ide

Improve debugging in VSCode IDE. Also update README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 9 (33.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-6.7%) to 77.273%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/conftest.py
3
9
33.33%

Totals

Change from base Build<PHONE_NUMBER>:
-6.7%

Covered Lines:
34

Relevant Lines:
44

💛  - Coveralls

@JosePizarro3 Applied your comments. I will be merging then. This is just supposed to be a quick update.
This won't be the last time we update the README, anyhow.


Exception thrown on mergesolutions

upon comparing  two solutions (that do load properly) I get an exception, see attached image.
Attachments
exception.JPG
MUSE7.sln
MUSE7.sln
CommonAncestor.sln
This work item was migrated from CodePlex
CodePlex work item ID: '450'
Vote count: '1'

[UnknownUser@4/9/2009]

[camvet@4/9/2009]
I am also attaching the two solution files.

[UnknownUser@4/9/2009]

[camvet@4/9/2009]
also adding commonancestor.sln

[camvet@4/9/2009]
Found that solution file had same dependency listed twice for one project.  I believe you would be safe to detect this situation and simply ignore the duplicate dependancy, then the file gets written out, the duplicate ends up removed.

[UnknownUser@4/9/2009]

[camvet@4/9/2009]
here is the other solution

[UnknownUser@4/9/2009]
Resolved with changeset 5923.

[UnknownUser@5/16/2013]

[UnknownUser@2/14/2013]


Fix SlackMessage.Clone does not clone all properties

Update the Message.Clone to include all properties. This also addresses the missing Message.Blocks #73.

Good spot! thank you!


add support for an env variable setting a TMPFS build dir

add support for an env variable setting a TMPFS build dir, to speed up build tasks and save SSD lifetime.

standard TMPDIR is known to work


Invalid Link for TensorFlow Keras Official Documentation

URL with the issue:
https://www.tensorflow.org/guide/keras
https://colab.research.google.com/github/tensorflow/docs/blob/master/site/en/guide/keras.ipynb
https://github.com/tensorflow/docs/blob/master/site/en/guide/keras.ipynb
Description of issue (what needs changing):
The last two links are directed to 404, which means they don't exist with valid colab files or gitlab files.

Thanks for the report. We're in the process of moving the docs around for the TF2 RC.
Those docs now live here in github:

https://github.com/tensorflow/docs/blob/master/site/en/r1/guide/keras.ipynb
https://colab.sandbox.google.com/github/tensorflow/docs/blob/master/site/en/r1/guide/keras.ipynb

But, really, they should point to the r2.0rc branch to avoid this: https://github.com/tensorflow/docs/blob/r2.0rc/site/en/guide/keras.ipynb

Links in TF1 guides and tutorials have been updated to point to the r2.0rcbranch:

https://colab.research.google.com/github/tensorflow/docs/blob/r2.0rc/site/en/guide/keras.ipynb
https://github.com/tensorflow/docs/blob/r2.0rc/site/en/guide/keras.ipynb


Add rendering percentage

Can't easily be added because the list of geometry to render is generated as-needed.


minor: Test for rust-lang/rust-analyzer in the release workflow

bors r+

bors r-

bors r+

bors r-


Telegram icon

Icon Request

Icon name: telegram
Tags of this icon: messenger, logo
Use case: telegram logo
Screenshots of similar icons: see telegram website

search telegram in our website, you'll find it~


jboss-interceptor-api dependency not resolved

Hi guys,
Doesn't anyone else hit this issue?:
> sbt updateSbtClassifiers
[info] Loading project definition from /Users/joangoyeau/Code/test/project
[info] Updating {file:/Users/joangoyeau/Code/test/project/}test-build...
[info] Resolving org.fusesource.jansi#jansi;1.4 ...
[info] Done updating.
[info] Set current project to test (in build file:/Users/joangoyeau/Code/test/)
[info] Resolving org.jboss.interceptor#jboss-interceptor-api;1.1 ...
[warn] problem while downloading module descriptor: https://repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom: invalid sha1: expected=453b712ff6cda3a3f10f46a9ab9b9a42fc9bc021 computed=56da14e5a3e7e5656fe2ed1942d9fc0c1f3b054b (31ms)
[warn] 	module not found: org.jboss.interceptor#jboss-interceptor-api;1.1
[warn] ==== typesafe-ivy-releases: tried
[warn]   https://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[warn] ==== sbt-plugin-releases: tried
[warn]   https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[warn] ==== local: tried
[warn]   /Users/joangoyeau/.ivy2/local/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[info] Resolving org.codehaus.plexus#plexus-classworlds;2.5.2 ...
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::          UNRESOLVED DEPENDENCIES         ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
	at sbt.IvyActions$.sbt$IvyActions$$resolve(IvyActions.scala:313)
	at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:191)
	at sbt.IvyActions$$anonfun$updateEither$1.apply(IvyActions.scala:168)
	at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:156)
	at sbt.IvySbt$Module$$anonfun$withModule$1.apply(Ivy.scala:156)
	at sbt.IvySbt$$anonfun$withIvy$1.apply(Ivy.scala:133)
	at sbt.IvySbt.sbt$IvySbt$$action$1(Ivy.scala:57)
	at sbt.IvySbt$$anon$4.call(Ivy.scala:65)
	at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:93)
	at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:78)
	at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:97)
	at xsbt.boot.Using$.withResource(Using.scala:10)
	at xsbt.boot.Using$.apply(Using.scala:9)
	at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:58)
	at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:48)
	at xsbt.boot.Locks$.apply0(Locks.scala:31)
	at xsbt.boot.Locks$.apply(Locks.scala:28)
	at sbt.IvySbt.withDefaultLogger(Ivy.scala:65)
	at sbt.IvySbt.withIvy(Ivy.scala:128)
	at sbt.IvySbt.withIvy(Ivy.scala:125)
	at sbt.IvySbt$Module.withModule(Ivy.scala:156)
	at sbt.IvyActions$.updateEither(IvyActions.scala:168)
	at sbt.IvyActions$.transitiveScratch(IvyActions.scala:228)
	at sbt.Classpaths$$anonfun$sbtClassifiersTasks$9$$anonfun$apply$74.apply(Defaults.scala:1375)
	at sbt.Classpaths$$anonfun$sbtClassifiersTasks$9$$anonfun$apply$74.apply(Defaults.scala:1373)
	at sbt.Classpaths$$anon$2.call(Defaults.scala:1403)
	at sbt.Classpaths$$anon$2.call(Defaults.scala:1400)
	at xsbt.boot.Locks$GlobalLock.withChannel$1(Locks.scala:93)
	at xsbt.boot.Locks$GlobalLock.xsbt$boot$Locks$GlobalLock$$withChannelRetries$1(Locks.scala:78)
	at xsbt.boot.Locks$GlobalLock$$anonfun$withFileLock$1.apply(Locks.scala:97)
	at xsbt.boot.Using$.withResource(Using.scala:10)
	at xsbt.boot.Using$.apply(Using.scala:9)
	at xsbt.boot.Locks$GlobalLock.ignoringDeadlockAvoided(Locks.scala:58)
	at xsbt.boot.Locks$GlobalLock.withLock(Locks.scala:48)
	at xsbt.boot.Locks$.apply0(Locks.scala:31)
	at xsbt.boot.Locks$.apply(Locks.scala:28)
	at sbt.Classpaths$.withExcludes(Defaults.scala:1400)
	at sbt.Classpaths$$anonfun$sbtClassifiersTasks$9.apply(Defaults.scala:1373)
	at sbt.Classpaths$$anonfun$sbtClassifiersTasks$9.apply(Defaults.scala:1364)
	at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
	at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
	at sbt.std.Transform$$anon$4.work(System.scala:63)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:228)
	at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
	at sbt.Execute.work(Execute.scala:237)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:228)
	at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
	at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
[error] (*:updateSbtClassifiers) sbt.ResolveException: unresolved dependency: org.jboss.interceptor#jboss-interceptor-api;1.1: not found
[error] Total time: 7 s, completed 10-Feb-2017 12:30:34

I tried in an empty project with only this plugin in plugins.sbt.

I think I solved it by adding that to the begging of plugins.sbt
resolvers += "JBoss" at "https://repository.jboss.org"

This looks like a workaround tho.

Yup...same problem here.  Adding the jboss repo worked for me as well.

How does this relate to sbt-assembly?

@eed3si9n This is 100% related to sbt-assembly.
You can set an empty project and with just sbt-assembly in there and you will see that JBoss is not resolved.
Can we reopen this prematuredly closed issue?

@joan38 Are you saying that sbt-assembly introduces dependency to org.jboss.interceptor:jboss-interceptor-api:1.1? As far as I know sbt-assembly has not direct or transitive dependency to it.

Yes that's what's happening.
I think it's not a direct transitive but in lower levels

Do you have any global plugins?
Here's the full external dependency classpath from sbt-assembly, most coming from sbt itself.
[info] * Attributed(/org.scalactic/scalactic_2.10/bundles/scalactic_2.10-3.0.1.jar)
[info] * Attributed(/scala-2.10.6/lib/scala-library.jar)
[info] * Attributed(/scala-2.10.6/lib/scala-reflect.jar)
[info] * Attributed(/org.pantsbuild/jarjar/jars/jarjar-1.6.3.jar)
[info] * Attributed(/org.apache.ant/ant/jars/ant-1.9.6.jar)
[info] * Attributed(/org.apache.ant/ant-launcher/jars/ant-launcher-1.9.6.jar)
[info] * Attributed(/org.apache.maven/maven-plugin-api/jars/maven-plugin-api-3.3.3.jar)
[info] * Attributed(/org.apache.maven/maven-model/jars/maven-model-3.3.3.jar)
[info] * Attributed(/org.codehaus.plexus/plexus-utils/jars/plexus-utils-3.0.20.jar)
[info] * Attributed(/org.apache.maven/maven-artifact/jars/maven-artifact-3.3.3.jar)
[info] * Attributed(/org.eclipse.sisu/org.eclipse.sisu.plexus/eclipse-plugins/org.eclipse.sisu.plexus-0.3.0.jar)
[info] * Attributed(/javax.enterprise/cdi-api/jars/cdi-api-1.0.jar)
[info] * Attributed(/javax.annotation/jsr250-api/jars/jsr250-api-1.0.jar)
[info] * Attributed(/javax.inject/javax.inject/jars/javax.inject-1.jar)
[info] * Attributed(/org.eclipse.sisu/org.eclipse.sisu.inject/eclipse-plugins/org.eclipse.sisu.inject-0.3.0.jar)
[info] * Attributed(/org.codehaus.plexus/plexus-component-annotations/jars/plexus-component-annotations-1.5.5.jar)
[info] * Attributed(/org.codehaus.plexus/plexus-classworlds/bundles/plexus-classworlds-2.5.2.jar)
[info] * Attributed(/org.ow2.asm/asm/jars/asm-5.2.jar)
[info] * Attributed(/org.ow2.asm/asm-commons/jars/asm-commons-5.2.jar)
[info] * Attributed(/org.ow2.asm/asm-tree/jars/asm-tree-5.2.jar)
[info] * Attributed(/org.scala-sbt/sbt/jars/sbt-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/main/jars/main-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/actions/jars/actions-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/classpath/jars/classpath-0.13.13.jar)
[info] * Attributed(/Users/eugene/.sbt/boot/scala-2.10.6/lib/scala-compiler.jar)
[info] * Attributed(/org.scala-sbt/interface/jars/interface-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/io/jars/io-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/control/jars/control-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/launcher-interface/jars/launcher-interface-1.0.0-M1.jar)
[info] * Attributed(/org.scala-sbt/completion/jars/completion-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/collections/jars/collections-0.13.13.jar)
[info] * Attributed(/jline/jline/jars/jline-2.13.jar)
[info] * Attributed(/org.fusesource.jansi/jansi/jars/jansi-1.11.jar)
[info] * Attributed(/org.scala-sbt/api/jars/api-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/classfile/jars/classfile-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/logging/jars/logging-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/process/jars/process-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/compiler-integration/jars/compiler-integration-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/incremental-compiler/jars/incremental-compiler-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/relation/jars/relation-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/compile/jars/compile-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/persist/jars/persist-0.13.13.jar)
[info] * Attributed(/org.scala-tools.sbinary/sbinary_2.10/jars/sbinary_2.10-0.4.2.jar)
[info] * Attributed(/org.scala-sbt/compiler-ivy-integration/jars/compiler-ivy-integration-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/ivy/jars/ivy-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/cross/jars/cross-0.13.13.jar)
[info] * Attributed(/org.scala-sbt.ivy/ivy/jars/ivy-2.3.0-sbt-2cf13e211b2cb31f0d3b317289dca70eca3362f6.jar)
[info] * Attributed(/com.jcraft/jsch/jars/jsch-0.1.50.jar)
[info] * Attributed(/org.scala-sbt/serialization_2.10/jars/serialization_2.10-0.1.2.jar)
[info] * Attributed(/org.scala-lang.modules/scala-pickling_2.10/jars/scala-pickling_2.10-0.10.1.jar)
[info] * Attributed(/org.scalamacros/quasiquotes_2.10/jars/quasiquotes_2.10-2.0.1.jar)
[info] * Attributed(/org.json4s/json4s-core_2.10/jars/json4s-core_2.10-3.2.10.jar)
[info] * Attributed(/org.json4s/json4s-ast_2.10/jars/json4s-ast_2.10-3.2.10.jar)
[info] * Attributed(/com.thoughtworks.paranamer/paranamer/jars/paranamer-2.6.jar)
[info] * Attributed(/org.spire-math/jawn-parser_2.10/jars/jawn-parser_2.10-0.6.0.jar)
[info] * Attributed(/org.spire-math/json4s-support_2.10/jars/json4s-support_2.10-0.6.0.jar)
[info] * Attributed(/org.scala-sbt/run/jars/run-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/task-system/jars/task-system-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/tasks/jars/tasks-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/tracking/jars/tracking-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/cache/jars/cache-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/testing/jars/testing-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/test-agent/jars/test-agent-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/test-interface/jars/test-interface-1.0.jar)
[info] * Attributed(/org.scala-sbt/main-settings/jars/main-settings-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/apply-macro/jars/apply-macro-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/command/jars/command-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/template-resolver/jars/template-resolver-0.1.jar)
[info] * Attributed(/org.scala-sbt/logic/jars/logic-0.13.13.jar)
[info] * Attributed(/org.scala-sbt/compiler-interface/jars/compiler-interface-0.13.13.jar)

No I don't have any global plugins.
This issue appeared quiet recently. I suspect some repo changed.
This issue appeared first on our CI that is rebuilding a docker image with the SBT cache every WE.

Steps to reproduce:
mkdir test
cd test
mkdir project
echo "addSbtPlugin(\"com.eed3si9n\" % \"sbt-assembly\" % \"0.14.4\")" > project/plugins.sbt
rm -rf ~/.ivy2
sbt updateSbtClassifiers

ok. I was able to reproduce the error.
$ sbt -Dsbt.ivy.home=/tmp/test/ivy2/ -Dsbt.global.base=/tmp/test/global debug updateSbtClassifiers

I'm not sure what's causing it to resolve. Perhaps I can exclude dependency to maven-plugin-api if that's getting pulled in via Jar Jar Links.

this is a particularly nasty one because the sha 453b712ff6cda3a3f10f46a9ab9b9a42fc9bc021 on maven central doesn't match the pom file, yay!

workaround is to install with
addSbtPlugin("com.eed3si9n" % "sbt-assembly" % "0.14.4" exclude("org.apache.maven", "maven-plugin-api"))

(this wiped me out for a full day at scalasphere because the sha mismatch took down our CI, so hopefully this helps somebody nail it down)

Thank you, Fommil - yes, that fixes the IDEA bug.  (SBT always compiled the project fine -- it was just a recent IDEA import bug).

@brentsony this is unrelated to Idea, you can reproduce the issue by doing sbt updateSbtClassifiers as I showed in my first message.

@joan38 Yes, thank you for noting that there is a way to break SBT outside of IDEA. However, IDEA is broken by the bug and does not offer a workaround. All the usual workarounds have no effect. That is, ReBuild All, Invalidate Caches and Restart, Deleting the target dir and building, ... IDEA is so broken that it cannot even display syntax highlighting in build.sbt and gives completely misleading compilation error messages in perfectly valid Scala source files. All the while, "sbt clean compile" works great from the command line.

@brentsony You see this issue in idea because the command ran by Idea in SBT is:
;reload; */*:dumpStructureTo /private/var/folders/4_/0czwjnyn1tb8slhkcvcl3tjc0000gp/T/sbt-structure.xml download resolveClassifiers resolveSbtClassifiers

You can see that resolveSbtClassifiers is in this list of tasks.

Also hit this. I'm using coursier and get this error:
[trace] Stack trace suppressed: run last *:coursierSbtClassifiersResolution for the full output.
[error] (*:coursierSbtClassifiersResolution) coursier.ResolutionException: Encountered 1 error(s) in dependency resolution:
[error]   org.jboss.interceptor:jboss-interceptor-api:1.1:
[error]     not found:
[error]       https://repo.typesafe.com/typesafe/ivy-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       /Users/shildrew/.ivy2/local/org.jboss.interceptor/jboss-interceptor-api/1.1/ivys/ivy.xml
[error]       https://repo.typesafe.com/typesafe/releases/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error]     wrong checksum: /Users/shildrew/.coursier/cache/v1/https/repo1.maven.org/maven2/org/jboss/interceptor/jboss-interceptor-api/1.1/jboss-interceptor-api-1.1.pom
[error] Total time: 3 s, completed 20-Apr-2017 15:14:12

So at least the root cause of an invalid checksum is clear when coursier is enabled.

Some discussion of this issue on Stackoverflow
http://stackoverflow.com/questions/41966066/jboss-interceptor-api-1-1-not-found-when-added-as-sbt-dependency

If anyone tried opening the issue on the correct project maybe it wouldn't have taken 5 months to fix: https://issues.sonatype.org/plugins/servlet/mobile#issue/MVNCENTRAL-2461

@eed3si9n fyi it's fixed now: you can close the issue.

@graingert I don't see it being fixed. It's still broken for me. Maybe you have the correct dependency in your ~/.ivy2 now, or a custom dependency resolver, @graingert ?
@eed3si9n can sbt-assembly explicitly remove jboss-interceptor-api from its dependencies? After all, everything works when using addSbtPlugin("com.eed3si9n" % "sbt-assembly" % "0.14.4" exclude("org.apache.maven", "maven-plugin-api")) (as suggested by fommil).

@vn971 no it's definitely fixed. Read the discussion on https://issues.sonatype.org/browse/MVNCENTRAL-2461

@graingert indeed, the issue is fixed now. One has to clean up jboss-related files from ivy cache (~/.ivy2 or ~/.coursier) in order for things to work. Thank you.
@eed3si9n is there actually any reason to keep sbt-assembly dependent on jboss-interceptor-api at all? Is it really used? Because everything works fine when using addSbtPlugin("com.eed3si9n" % "sbt-assembly" % "0.14.4" exclude("org.apache.maven", "maven-plugin-api")) (as suggested by @fommil).

With coursier, this should be ok since 1.0.0. sbt-coursier was generating an update report for plugins which was lacking some exclusions, which later made updateSbtClassifiers try to pull too many things, including some jboss stuff with wrong checksums (which should have been excluded).
This is specific to coursier, so I don't know about the cases where this was happening without it…

@eed3si9n fyi it's fixed now: you can close the issue.

@graingert Thanks!


Add UniversalX

What changed? Why?
UniversalX has been added to the Base ecosystem page.
Notes to reviewers
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@TABASCOatw
Heya! Thanks for building on Base!
We require that defi apps linked to from base.org include a terms of service / terms and conditions page for users. It doesn't appear that this is present on the linked page. In order to continue the review, could you all please update and resubmit?


setup onion service url for the CCS

ofrnxmr noted in -site that https://ccs.getmonero.org does not have an onion link and is behind cloudflare. lets fix that and allow people to obtain donation addresses anonymously from a trusted source
assigning myself

[x] reach out to backend admin to setup onion service
[ ] confirm onion service is up / running (automatically redirecting if possible)
[ ] update onion.txt with the new URL signed by binaryFate

Perhaps can just KISS and use the existing onion by config nginx so these have proper endpoints
ccs.monerotoruzizulg5ttgat2emf4d6fbmiea25detrmmy7erypseyteyd.onion
repo.monerotoruzizulg5ttgat2emf4d6fbmiea25detrmmy7erypseyteyd.onion

Bump


Fails when installing in a repo using Tailwind PostCSS plugin: cannot read config from undefined

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
Cannot start/build docusaurus classic template
Tried with node@14/node@16/node@17
Steps to reproduce
Waiting for npx create-docusaurus@latest web classic to complete
cd web
yarn start

Expected behavior
Client compiled
Actual behavior
❯ yarn start
yarn run v1.22.17
$ docusaurus start
[INFO] Starting the development server...
[SUCCESS] Docusaurus website is running at http://localhost:3000/.

✖ Client
  Compiled with some errors in 3.01s
[...]
TypeError: Cannot read properties of undefined (reading 'config')
TypeError: Cannot read properties of undefined (reading 'config')
TypeError: Cannot read properties of undefined (reading 'config')
TypeError: Cannot read properties of undefined (reading 'config')
client (webpack 5.68.0) compiled with 88 errors

Your environment
new.docusaurus codesandbox bad gateway.
new.docusaurus stackblitz all ok

Docusaurus version used: 2.0.0-beta.15
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node.js 14/16/17
Operating system and version (e.g. Ubuntu 20.04.2 LTS): darwin 21 (arm64)

Reproducible demo
My project

pnpm i to setup the project deps
cd docs/web
yarn
yarn start
See the errors in console without stack trace

You could remove the docs/web directory and create a docusaurus yourself

rm -rf docs/web
cd docs
npx create-docusaurus@latest
web for the project name
classic for the template
use typescript
cd web
yarn start
See the errors in console without stack trace

Self-service

[ ] I'd be willing to fix this bug myself.

Without a reproduction we can't do anything. You must be doing something wrong with your website's code, possibly referencing a variable that doesn't exist. Please don't use the GitHub issue tracker for your question; and even if you do, questions without literally any code can't get you help.

Did you read my issue description or is this an automatic message?
This is totally the code that comes from the result of the create-docusaurus command.
There is no reproduction repo because it comes from the template itself.

This might be because the new docusaurus project is in a subdirectory of a pnpm project (docusaurus project dependencies has been installed via yarn).
project/docs/web <- this directory is docusaurus.
When creating outside, everything works.

I create new projects almost every two days (for repro purposes) and we have E2E tests that scaffold new websites on every PR, so it's hard for me to conclude that there's something wrong with the init template. That's why I'm asking you to provide a repro. And you seem to concede that

new.docusaurus stackblitz all ok

which means it must be your local setup. How do you expect me to reproduce it?

This might be because the new docusaurus project is in a subdirectory of a pnpm project (docusaurus project dependencies has been installed via yarn).

That sounds better, but I still need more details than that if you still believe it's a bug and not something wrong with your setup or some misunderstanding about how Docusaurus works.

Note that we don't support installing dependencies with PNPM yet, so if you are managing a monorepo, you'd rather want to install with --skip-install and manually run pnpm install in your repo's root.

I'll link my repo with a docusaurus inside of it to a commit that failed. I tried dependencies with yarn, npm, and pnpm. All same result. After spending time to fix this, I tried outside of the project, and it worked.
Despite the docusaurus is installed (and deps) with yarn (so no conflict with pnpm as it is a new node_modules dir), the build failed.

You are also missing stack traces in your error. In order for me to investigate, I would need the stack trace and a reproduction demo. I seldom use PNPM and neither do I have a working PNPM repo set up.

So, I updated the main post. There is now a repro branch of my project.

Note that mixing package managers in the first place is a bad idea, especially with PNPM which has a different node_modules assembling strategy.

Yes I know! But I used yarn here because:

docusaurus force you to install deps with yarn at the first place (please remove auto install... 😅)
docusaurus is not officially supported by docusaurus.

I already tried installing the deps with pnpm too, but same thing happened.

docusaurus force you to install deps with yarn at the first place (please remove auto install... 😅)

This is because we have far more users that aren't aware of package managers and even an additional npm install step for them is overwhelming😅 I know it's super annoying for you and me, but if you've been helping in the community for a while, you understand it's better if we can do more under the hood. You can use the --skip-install flag if you just want the template.

[PNPM] is not officially supported by docusaurus.

We have an E2E test for installing new projects with PNPM and it had successfully caught a few incompatible changes (most recently #6604), so I'd say it's at least supported for normal use-cases. But for more complicated situations we absolutely recommend Yarn so you can be sure to be on the same page as us.

BTW, the stack traces are retrievable in the overlay:
ERROR in<EMAIL_ADDRESS>
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
TypeError: Cannot read properties of undefined (reading 'config')
    at getTailwindConfig (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/node_modules/.pnpm/tailwindcss@3.0.18_ef48b3b8837f8a23677bffe8f9cd866d/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:81:62)
    at /Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/node_modules/.pnpm/tailwindcss@3.0.18_ef48b3b8837f8a23677bffe8f9cd866d/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:124:92
    at /Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/node_modules/.pnpm/tailwindcss@3.0.18_ef48b3b8837f8a23677bffe8f9cd866d/node_modules/tailwindcss/lib/processTailwindFeatures.js:43:11
    at plugins (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/node_modules/.pnpm/tailwindcss@3.0.18_ef48b3b8837f8a23677bffe8f9cd866d/node_modules/tailwindcss/lib/index.js:20:104)
    at LazyResult.runOnRoot (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/postcss/lib/lazy-result.js:339:16)
    at LazyResult.runAsync (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/postcss/lib/lazy-result.js:393:26)
    at LazyResult.async (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/postcss/lib/lazy-result.js:221:30)
    at LazyResult.then (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/postcss/lib/lazy-result.js:206:17)
    at processResult (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/webpack/lib/NormalModule.js:753:19)
    at /Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/webpack/lib/NormalModule.js:855:5
    at /Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/loader-runner/lib/LoaderRunner.js:399:11
    at /Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/loader-runner/lib/LoaderRunner.js:251:18
    at context.callback (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/loader-runner/lib/LoaderRunner.js:124:13)
    at Object.loader (/Users/joshcena/Desktop/work/Tech/Projects/repros/papyrus-compiler-app/docs/web/node_modules/postcss-loader/dist/index.js:142:7)

It seems some unwanted code is being visited

@Kiyozz I have concluded that it has nothing to do with PNPM, but rather about your PostCSS config. Because we use PostCSS, the loader will read the postcss.config.js file. However, this looks suspicious to me: https://github.com/Kiyozz/papyrus-compiler-app/blob/139-docusaurus/postcss.config.js
The tailwindcss plugin expects a configOrPath argument, but it received undefined. Does this config actually work for you outside Docusaurus?

Thanks you Joshua.
It feels strange that postcss loader is searching recursively for a postcss config. Does having a postcss config in the template disallow the loader to search recursively?

It feels strange that postcss loader is searching recursively for a postcss config.

That's typical behavior with most loaders. E.g. Babel loader will recursively look for a babel.config.js afaik.

Does having a postcss config in the template disallow the loader to search recursively?

Adding a docs/web/postcss.config.js with module.exports = {} does seem to fix it. We probably won't add it to the template, but I think it's a good enough solution for your case.

Is this docusaurus should be aware (maybe in a faq or something?) or is this only for my use case?

I don't think anyone has stumbled upon it (although I do know a few sites that use Tailwind + Docusaurus, or Docusaurus in a repo that also uses Tailwind) and it's ultimately just a workaround. Preferably, we should be able to fix it, but given my limited knowledge in either PostCSS or Tailwind, I'll let @slorber to make the decision

I don't think anyone has stumbled upon it

During manual migration I faced the same issue. Not sure why. But when I removed all changes and tried migration for the second time I didn't get the issue. Our repo doesn't use tailwind css. I used yarn both time.

Adding a docs/web/postcss.config.js with module.exports = {} does seem to fix it. We probably won't add it to the template, but I think it's a good enough solution for your case.

I fixed it by creating tailwind.config.js file and adding basic default tailwind config 😄
module.exports = {
  content: [],
  theme: {
    extend: {},
  },
  plugins: [],
}

@Kiyozz Do you use M1 mac by any chance?

@Kiyozz Do you use M1 mac by any chance?

Indeed

It worked on my intel MacBook pro and throws config error in m1 mac 😅 .

Can reproduce on a fresh install on an M1 machine. The commands I ran was
npx create-docusaurus@latest docs classic
cd docs
yarn start

Fixed by following @harish-sethuraman 's advice, creating a tailwind.config.js with default configs in the root of docusaurus folder.
yarn version: 1.22.5
node version: v16.13.2

So the init template (on which Tailwind is not installed) fails to start? Are you sure it's the full repro steps? 🤷♂

So the init template (on which Tailwind is not installed) fails to start? Are you sure it's the full repro steps? 🤷♂

Yes I can confirm.
npx create-docusaurus@latest docs classic
cd docs
yarn start

starts throwing errors
TypeError: Cannot read properties of undefined (reading 'config')
client (webpack 5.68.0) compiled with 88 errors

I have an M1 pro and can't reproduce this issue with those 3 commands 🤷♂

Do you need any other details? It got replicated when I ran those three steps. Maybe I can help you get the necessary details.

I don't know, try to provide anything that may be relevant and we'll try to reproduce with same env or compare with other users having similar setups

Also I was in v16.13.1 node version when this happened

@slorber You need to have Tailwind installed and configured through postcss.config.js and/or tailwind.config.js in your parent directory.

I'm having the same issue.  The docusarus project works fines as an independent project.  The moment I moves it to a subdir under another project with postcss.config.js in the parent dir, docusarus yarn build will fail.
root_project (next.js + tailwind)
   | package.json
   | postcss.config.js. <--- Test: rename this file and the error will go away
   ...
   | --- docs (docusaurus)
         ...

Workaround:

As suggested above, create tailwind.config.js in docs dir with the following content

module.exports = {
  content: [],
  theme: {
    extend: {},
  },
  plugins: [],
}

I hope this helps.

Another workaround if your docusaurus site does not use TailwindCSS:

Add an postcss.config.js under the docusaurus folder(e.g: websites) (https://github.com/nvh95/jest-preview/commit/d4ec48344d0c244140491007136763a69305cf96):

// website/postcss.config.js
module.exports = {};

This is postcss-loader's default behavior. You will see the same result if you have a babel.config.js (which we just happen to already have one by default).

This is postcss-loader's default behavior. You will see the same result if you have a babel.config.js (which we just happen to already have one by default).

I see. But is there anything we can do to mitigate this unexpected behavior? As a docusaurus user, I don't want to care about "its parent folder has a postcss.config.js file". A normal user thinks docusaurus folder should be in isolation. For example: I don't even use postcss/ tailwindcss for my docusaurus project, but when I "accidentally" put it as a child folder to a folder contains postcss.config.js, the app fails to build.
Again, if that how postcss-loader behaves, can we do anything to avoid the confusion for some users (who have already had this issue and who are going to have this issue)? Some of my initiatives:

Somehow isolate/ encapsulate the docusaurus project, so it does not read postcss.config.js from parent folder.
Note somewhere in the documentation so when encountering this bug, they can easily google it.

I think documenting this is fine, because sometimes projects do want to have a monorepo-wide CSS config (not sure if it works anyway). Still waiting for @slorber to decide if there's something obviously wrong with our config (I can't see any), or if this is working as intended and we just need to document it.

Yeah. Thank you @Josh-Cena. I think documentation and if possible, trying to catch the error and show some meaningful error message would be wonderful.

I'm here for a Sanity Studio V3 adding an empty tailwind.config.js fix the issue.

Just encountered a similar issue where locally everything builds fine, but for whatever reason in CI (same node version, same yarn version) I get Error: Cannot find module 'autoprefixer'. That is because one level up there is a postcss.config.js file that expects autoprefixer. Adding the postcss.config.js file with module.exports = {} in it did fix it.
Since it seems that nesting docusaurus inside of a directory of an active project is fairly common practice, perhaps docusaurus can try to pre-emptively solve these issues by scanning the parent directory for these common config files and if they exist, create dummy ones?

Hi, is there any update on this feature?

I think I found the solution.
According to postcss-loader documentation, we can specify the format in:

["package_name", { parameter_key: "parameter_value" }]

where parameter_key and parameter_value are config and "path/to/tailwindcss.config.json" respectively by referencing to tailwindcss documentation.
Thus, the final code should be:
plugins: [
      async function myPlugin(context, options) {
        return {
          name: "docusaurus-tailwindcss",
          configurePostCss(postcssOptions) {
            // Appends TailwindCSS and AutoPrefixer.
            postcssOptions.plugins.push(['tailwindcss', {config: "apps/{project_name}/taildwind.config.js"}]);
            postcssOptions.plugins.push(require("autoprefixer"));
            return postcssOptions;
          },
        };
      },
    ],

I fix this issue, only install and config tailwindCss, how @Josh-Cena said.


ccrewrite produces an incorrect type name in IteratorStateMachineAttribute with some generic types

This is related to #47. Now that parsing of escaped type names in attributes had been fixed, ccrewrite fails to escape it back when producing the rewritten assembly. It seems to have no runtime effect, but it causes problems if this assembly is referenced by another assembly that is also rewritten. ccrewrite attempts to parse the referenced assembly and fails due to an incorrect type name encoded in the attribute.
Pull request with a fix will follow as soon as I figure out how to add a unit test for it.

Could you provide a concrete example? Then I'll try to repro this in tests and will put some notes here how to add tests for such cases.

The way I discovered it is by having two projects, both of which have ccrewrite enabled.
Library.cs => Library.dll
using System;
using System.Collections;
using System.Collections.Generic;

namespace Library
{
    public class Utility : IEnumerable<Tuple<string, string>>
    {
        IEnumerator<Tuple<string, string>> IEnumerable<Tuple<string, string>>.GetEnumerator()
        {
            yield break;
        }

        IEnumerator IEnumerable.GetEnumerator()
        {
            yield break;
        }
    }
}

Application.cs => Application.exe
namespace Application
{
    class Program
    {
        static void Main(string[] args)
        {
            new Library.Utility();
        }
    }
}

When compiling the Application project, you get
2>  Reading assembly 'Library' from 'C:\Projects\Test\Library\bin\Release\Library.dll' resulted in errors.
2>  	Illegal characters in path.
2>ccrewrite : error : Rewrite aborted due to metadata errors. Check output window

And the reason for this is the iterator type name which was not properly escaped: <System-Collections-Generic-IEnumerable<System-Tuple<System-String,System-String>>-GetEnumerator>d__0. Parsing it stops at the comma assuming that everything that follows is the assembly specification, hence the "Illegal characters in path" error when it tries to look up that assembly.
For a unit test, I was thinking it may be easier just to compile the code in Library and parse it back somehow. This doesn't follow the typical build-rewrite-run approach in Foxtrot unit tests, that's why I needed a bit more time figuring out how to best structure it.

Thanks a lot! I'll try to add the test now.

Faced similar issue today. Thanks for fixing it!


move global functions to a namespace

motivation: namespaced code is good code
changes: move global funcitons in the XcodeProject module to a namespace

this got in the way of https://github.com/apple/swift-package-manager/pull/4173, but doing a separate PR to keep scope down

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test Linux


Cleanup ownership mixin specs

Remove unnecessary lets now that we have a better setup.
Extract out the common value into lets to DRY up the specs.

@chrisarcand Please review.

Thanks @bdunne !

@Fryguy @bdunne @chrisarcand euwe/yes or euwe/no?

Euwe Backport conflict:
$ git cherry-pick -e -x -m 1   290cac3
error: could not apply 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'

$ git status
On branch euwe
Your branch is up-to-date with 'upstream/euwe'.
You are currently cherry-picking commit 290cac3.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)

	both modified:   spec/support/examples_group/shared_examples_for_ownership_mixin.rb

$ git diff

diff --cc spec/support/examples_group/shared_examples_for_ownership_mixin.rb
index 7a3410e,e6a182e..0000000
--- a/spec/support/examples_group/shared_examples_for_ownership_mixin.rb
+++ b/spec/support/examples_group/shared_examples_for_ownership_mixin.rb
@@@ -1,19 -1,62 +1,24 @@@
 -shared_examples_for "OwnershipMixin" do
 -  context "includes OwnershipMixin" do
 +shared_examples "miq ownership" do
 +  # THIS TOP LEVEL CONTEXT IS REQUIRED because tests that include are database
 +  # state dependent and require a clean DB.  When used with `include_examples`,
 +  # the before(:context) and after(:context) in this are run on the same level
 +  # as the `include_example`'s current context, so more likely than not, it
 +  # will be included in other tests that aren't part of this example group.
 +  context "includes mixin:  miq ownership" do
      include Spec::Support::ArelHelper

 -    let(:user) do
 -      FactoryGirl.create(:user,
 -                         :userid     => "ownership_user",
 -                         :miq_groups => FactoryGirl.create_list(:miq_group, 1))
 -    end
 -
 -    let(:user2)  { FactoryGirl.create(:user) }
 -    let(:group)  { user.current_group }
 -    let(:group2) { FactoryGirl.create(:miq_group) }
 -
 -    let(:factory) { described_class.to_s.underscore.to_sym }
 -
 -    let!(:in_ldap)     { FactoryGirl.create(factory, :name => "in_ldap",     :miq_group => group) }
 -    let!(:not_in_ldap) { FactoryGirl.create(factory, :name => "not_in_ldap", :miq_group => group2) }
 -    let!(:no_group)    { FactoryGirl.create(factory, :name => "no_group") }
 -    let!(:user_owned)  { FactoryGirl.create(factory, :name => "user_owned",  :evm_owner => user) }
 -    let!(:user_owned2) { FactoryGirl.create(factory, :name => "user_owned2", :evm_owner => user2) }
 -
 -    describe ".user_or_group_owned" do
 -      let(:user_other_region) do
 -        other_region_id = ApplicationRecord.id_in_region(1, MiqRegion.my_region_number + 1)
 -        FactoryGirl.create(:user, :id => other_region_id).tap do |u|
 -          u.update_column(:userid, user.userid) # Bypass validation for test purposes
 -        end
 -      end
 -
 -      context "only with a user" do
 -        it "in this region" do
 -          expect(described_class.user_or_group_owned(user, nil)).to eq([user_owned])
 -        end
 -
 -        it "with same userid as another region" do
 -          user_owned.update!(:evm_owner => user_other_region)
 -          expect(described_class.user_or_group_owned(user, nil)).to eq([user_owned])
 -        end
 -      end
 -
 -      it "only with a group" do
 -        expect(described_class.user_or_group_owned(nil, group)).to eq([in_ldap])
 -      end
 -
 -      context "with a user and a group" do
 -        it "in this region" do
 -          expect(described_class.user_or_group_owned(user, group)).to match_array([in_ldap, user_owned])
 -        end
 +    let(:user) { User.where(:userid => "ownership_user").first }

 -        it "with same userid as another region" do
 -          user_owned.update!(:evm_owner => user_other_region)
 -          expect(described_class.user_or_group_owned(user, group)).to match_array([in_ldap, user_owned])
 -        end
 -      end
 +    before(:context) do
 +      build_ownership_users_and_groups
      end

++<<<<<<< HEAD
 +    describe ".owning_ldap_group" do
++=======
+     describe "#owning_ldap_group" do
+       let(:column) { :owning_ldap_group }
++>>>>>>> 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
        before { User.current_user = user }

        context "when miq_group is in the ldap group" do
@@@ -33,7 -74,8 +36,12 @@@
        end
      end

++<<<<<<< HEAD
 +    describe ".owned_by_current_ldap_group" do
++=======
+     describe "#owned_by_current_ldap_group" do
+       let(:column) { :owned_by_current_ldap_group }
++>>>>>>> 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
        before { User.current_user = user }

        it "usable as arel" do
@@@ -86,7 -122,8 +88,12 @@@
        end
      end

++<<<<<<< HEAD
 +    describe ".evm_owner_name" do
++=======
+     describe "#evm_owner_name" do
+       let(:column) { :evm_owner_name }
++>>>>>>> 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
        before { User.current_user = user }

        context "when has a user" do
@@@ -106,7 -141,8 +111,12 @@@
        end
      end

++<<<<<<< HEAD
 +    describe ".evm_owner_userid" do
++=======
+     describe "#evm_owner_userid" do
+       let(:column) { :evm_owner_userid }
++>>>>>>> 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
        before { User.current_user = user }

        context "when has a user" do
@@@ -126,7 -160,8 +134,12 @@@
        end
      end

++<<<<<<< HEAD
 +    describe ".evm_owner_email" do
++=======
+     describe "#evm_owner_email" do
+       let(:column) { :evm_owner_email }
++>>>>>>> 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
        before { User.current_user = user }

        context "when has a user" do
@@@ -146,62 -179,10 +157,68 @@@
        end
      end

++<<<<<<< HEAD
 +    describe ".user_or_group_owned" do
 +      let(:factory) { described_class.name == "Vm" ? :vm_vmware : described_class.table_name.singularize }
 +      let(:owned_resource) { FactoryGirl.create(factory) }
 +      let(:owning_user) {
 +        FactoryGirl.create :user, :userid => "user_owner", :miq_groups => FactoryGirl.create_list(:miq_group, 1)
 +      }
 +
 +      context "by user in this region" do
 +        it "returns resource owned by user" do
 +          owned_resource.evm_owner = owning_user
 +          owned_resource.save!
 +
 +          expect(described_class.user_or_group_owned(owning_user, nil)).to eq([owned_resource])
 +        end
++=======
+     describe "#owned_by_current_user" do
+       let(:column) { :owned_by_current_user }
+       before { User.current_user = user }
++>>>>>>> 290cac3... Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs
 +
 +        it "returns resource owned by user or group" do
 +          owned_resource.evm_owner = owning_user
 +          owned_resource.save!

 +          expect(described_class.user_or_group_owned(owning_user, owning_user.current_group)).to eq([owned_resource])
 +        end
 +      end
 +
 +      context "by user in a remote region" do
 +        let(:remote_owning_user) { FactoryGirl.create :user, :id => remote_id, :userid => "user_owner" }
 +        let(:remote_id) do
 +          my_region_number =  ApplicationRecord.my_region_number
 +          remote_region_number = my_region_number + 1
 +          ApplicationRecord.region_to_range(remote_region_number).first
 +        end
 +
 +        it "returns resource owned by user" do
 +          owned_resource.id = remote_id
 +          owned_resource.evm_owner = remote_owning_user
 +          owned_resource.save!
 +
 +          expect(owned_resource.evm_owner_id).not_to eq(owning_user.id)
 +          expect(described_class.user_or_group_owned(owning_user, nil)).to eq([owned_resource])
 +        end
 +
 +        it "returns resource owned by user or group" do
 +          remote_owning_user.current_group = remote_owning_user.miq_groups.first
 +          remote_owning_user.save!
 +
 +          expect(described_class.user_or_group_owned(owning_user, owning_user.current_group)).to eq([owned_resource])
 +        end
 +      end
 +
 +      context "by user in a remote region" do
 +        let(:remote_owning_user) { FactoryGirl.create :user, :id => remote_id, :userid => "user_owner" }
 +        let(:remote_id) do
 +          my_region_number =  ApplicationRecord.my_region_number
 +          remote_region_number = my_region_number + 1
 +          ApplicationRecord.region_to_range(remote_region_number).first
 +        end
 +
 +        it "returns resource owned by user" do
 +          owned_resource.id = remote_id
 +          owned_resource.evm_owner = remote_owning_user
 +          owned_resource.save!
 +
 +          expect(owned_resource.evm_owner_id).not_to eq(owning_user.id)
 +          expect(described_class.user_or_group_owned(owning_user, nil)).to eq([owned_resource])
 +        end
 +
 +        it "returns resource owned by user or group" do
 +          remote_owning_user.current_group = remote_owning_user.miq_groups.first
 +          remote_owning_user.save!
 +
 +          owned_resource.id = remote_id
 +          owned_resource.evm_owner = remote_owning_user
 +          owned_resource.save!
 +
 +          expect(owned_resource.evm_owner_id).not_to eq(owning_user.id)
 +          expect(described_class.user_or_group_owned(owning_user, owning_user.current_group)).to eq([owned_resource])
 +        end
 +      end
 +    end
 +
 +    describe ".owned_by_current_user" do
 +      before { User.current_user = user }
        it "usable as arel" do
          userid = user.userid.downcase
          sql        = <<-SQL.strip_heredoc.split("\n").join(' ')

Looking at this and will correct, but I don't understand why there's a conflict:

The describe line wasn't changed and this is a simple addition, so...why the conflict? Odd.

Nevermind, @jrafanie 's got it sorted out here

After backporting #11993 and #12088, this PR backports cleanly.
Euwe Backport details:
$ git log -1
commit 967b08adbe6370cf7401549354788bc62855b543
Author: Brandon Dunne<EMAIL_ADDRESS>Date:   Fri Oct 21 16:31:07 2016 -0400

    Merge pull request #12108 from Fryguy/cleanup_ownership_mixin_specs

    Cleanup ownership mixin specs
    (cherry picked from commit 290cac365583a3b279f3e257912092ccd13de047)

Thanks @chessbyte !


bug: E5108: Error executing lua ...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:16: attempt to index local 'ret' (a nil value) stack traceback:

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.10.0-dev
Operating system/version
wsl
Describe the bug

Steps To Reproduce
E5108: Error executing lua ...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:16: attempt to index local 'ret' (a nil value)
stack traceback:
...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:16: in function <...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:13>
vim/shared.lua: in function 'tbl_map'
...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:13: in function 'get_signs'
...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:98: in function <...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:87>
Expected Behavior
open lazyvim，，have follow error：
E5108: Error executing lua ...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:16: attempt to index local 'ret' (a nil value)
stack traceback:
...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:16: in function <...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:13>
vim/shared.lua: in function 'tbl_map'
...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:13: in function 'get_signs'
...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:98: in function <...t/.local/share/nvim/lazy/LazyVim/lua/lazyvim/util/ui.lua:87>
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Duplicate of #2039

Hello @wxzvim,
Could you close this issue?
Best regards!


No proper rendering in a modal when launched a second time

I have a modal with some bootstrap-select in it.
The first time I launch the modal, the dropdowns are rendered properly and I can use them. If I dismiss the modal (hide it) and reopen the modal, the dropdowns are rendered properly and then disappear after less than 1 second.
I need to refresh the whole page to get the dropdowns to work again.
I can see the options with Dev Tools in the right place, but nothing is shown.
When I launch the modal first time, this is what is shown:

It works fine!
However when I launch the modal a second time, I get this:

The drop down is not rendered even though the select/options are there.
The reason  is that the select is not inside this div

// ******************* SELECT TAG HERE ********************

          <button type="button" class="btn dropdown-toggle bs-placeholder btn-link"
                       data-toggle="dropdown" role="button" data-id="districtID" title="Select a district..">
                ::before

Select a district..

         </button>

                <input type="text" class="form-control" autocomplete="off" role="textbox" aria-label="Search">

For some odd reason, that div disappears when I dismiss the modal and launch it a second time.

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via Plunker, jsFiddle, CodePen or JS Bin, and report back with your link, Bootstrap version, bootstrap-select version, and specific browser and OS details.


Highlighting incorrect row when selecting while sorted

System information:

Windows 10 version 20H2, build 19042.928
DBeaver version: <IP_ADDRESS>105021514

Connection specification:

Database name and version: MySQL 5.1.44
Driver name: MySQL
Do you use tunnels or proxies (SSH, SOCKS, etc)? SSH Tunnel

Describe the problem you're observing:
When selecting rows while script results are sorted, the associated data row is highlighted instead of the expected/selected cell's row
Steps to reproduce, if exist:
Run script to output some results
Select a cell in the result panel, observe the full row is highlighted
Sort the results on a column
Select another cell, observe that the row data highlighted is the row that would be in the selected location without the sorting

In this instance, AIins01 is the first row without sorting, so when the sorting is active, selecting a cell on the first row, the AIins01 row is highlighted
Also observed in regular table browsing, but noticed initially in Script results.

Hello @ralius18
Thanks for the bug report.
We fixed this problem here: https://github.com/dbeaver/dbeaver/issues/12286
Fix will be available in DBeaver 21.0.5 on 2021-05-17
or you can test it in Early Access version https://dbeaver.io/files/ea/


Summarization subpackage baseline

superclass/subclass structure like Estimator()
may call Estimator() subclasses
"dummy" method would be stacking results of a given Estimator() subclass
also include one easy SOM-based direct-from-colors method [make a separate issue]
maybe include qit-based CHIPPR implementation if scalable

@johannct made a good point about Summarizer subclasses that want posteriors output by Estimator subclasses instead of just input photometry from Creator subclasses. Rather than letting those summarizers have a method that calls an estimator, it should instead have keywords in its config file that specify what estimator it wants to run (and where to find its config file) and/or the path to the estimated posteriors it wants to read in. This would kind of be analogous to the estimator subclasses that take completely different inputs from one another. The advantage is that no estimators are hidden in summarizers.

@AngusWright This would be a good opportunity to wrap your SOM_DIR code as a Summarizer() subclass, which would have the added bonus of being the first example of RAIL calling underlying R code.

Maybe what makes sense is for a Summarizer() superclass to live in rail.estimation so something like The WiZZ or a SOM can inherit from both Summarizer() and Estimator().

I've been thinking about this a bit and two conclusions I've come to:

the variety in what summarizers take as inputs is very large; this means the super classes will end up very thin, I think only for configuration stuff. Possibly you could add some high level methods like __init__, train, run or something
I'd suggest summarizers that need a PDF input explicitly take that input, rather than trying to run an estimator internally.
we should think of post-burner processes (like some variants of CC) as an additional that mutates an existing n(z), rather than a standard Summarizer step.

My main suggestion is that we get the code in place first before trying to push things under a single superclass.

@joezuntz Just caught this while catching up on a GitHub notification backlog, sorry! I think we discussed this offline, but in case I'm mistaken, or just for completeness, I'll also reply to your above comment here.
The plan is now to restructure the rail.estimation subpackage to have a three-tier superclass/subclass structure in which there is an Estimator() superclass that contains the I/O interface and most general methods (i.e. the __init__, train, estimate, etc. steps you cited) with a pair of subclasses for estimating per-galaxy photo-z information (named something like PZEstimator()) and population-level redshift information (named something like NZEstimator()) that themselves have subclasses for what we currently think of as estimators and summarizers; the wrappers of methods that produce both per-galaxy and ensemble-level redshift information would then be able to inherit from both of the superclasses. This plan addresses your three points above:

We'd minimize the redundant of overhead for the shared I/O of flexible data types, which has the added boon of further reducing the number of files to modify if the I/O API changes in the future.
It would be no more difficult to have summarizers accept PDFs as input than under the original design, and it enables wrapping methods to derive either/both population-level and per-galaxy redshift information in exactly the same way as described above (of possible interest to @biprateep @brettandrews @janewman-pitt-edu for per-galaxy photo-z posterior estimation methods like that of Bordoloi+10).
And, again, it would be no more difficult for any wrapped Estimator() sub-subclasses to accept estimates of an ensemble redshift distribution.

But it totally makes sense to draft up some individual methods before solidifying a top-level structure! It seems to me like proto-wrapping the guts of TXPipe's DIR pipeline stage LSSTDESC/TXPipe#193 would be low-hanging fruit (along with the others listed under "Development of n(z) estimators" in the overall plan for the nz-band-sensitivity project LSSTDESC/nz-band-sensitivity#1), but perhaps I'm behind on the status of the standalone SOM summarizer.

overtaken by events


⚠ Bofrost.at has degraded performance

In 4362d3c, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1325 ms

Resolved: Bofrost.at performance has improved in 4be679c after 10 minutes.


Spaceship::Tunes::SandboxTester.create -> {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Not Found"], "info"=>nil}, "statusCode"=>"ERROR"}

New Release Candidate Issue Checklist

[x] Updated fastlane to the latest release candidate version (2.150.1)
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I can't create sandbox user using Spaceship::Tunes::SandboxTester.create. I am getting following error:
{"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Not Found"], "info"=>nil}, "statusCode"=>"ERROR"}
Complete output when running fastlane, including the stack trace and command used

bundler: failed to load command: fastlane (.rbenv/versions/2.4.2/bin/fastlane)
Spaceship::UnexpectedResponse: [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Not Found"], "info"=>nil}, "statusCode"=>"ERROR"}
  .rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.150.1/spaceship/lib/spaceship/client.rb:717:in `parse_response'
  .rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.150.1/spaceship/lib/spaceship/tunes/tunes_client.rb:1469:in `create_sandbox_tester!'
  .rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/fastlane-2.150.1/spaceship/lib/spaceship/tunes/sandbox_tester.rb:46:in `create!'
   A lot of stuff in Spaceship::Tunes needs to get migrated to Spaceship::ConnectAPI and looks like I forgot that one ☹ I will see if I can get that out today for you

@polok PR here for you 👉 https://github.com/fastlane/fastlane/pull/16742
I will get this released later today

@joshdholtz Wow, so fast :D Thank you!

I am still getting this issue.
🔗  You can ⌘ + double-click on links to open them directly in your browser. Traceback (most recent call last): 	25: from /usr/local/bin/fastlane:23:in '
24: from /usr/local/bin/fastlane:23:in load' 	23: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/bin/fastlane:23:in <top (required)>'
22: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off' 	21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/commands_generator.rb:41:in start'
20: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/commands_generator.rb:352:in run' 	19: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!'
18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!' 	17: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command'
16: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run' 	15: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call'
14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run' 	13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane' 	11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/runner.rb:45:in execute'
10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/runner.rb:45:in chdir' 	 9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/runner.rb:49:in block in execute'
8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/fastlane/lib/fastlane/lane.rb:33:in call' 	 7: from app_store_core.rb:230:in block (2 levels) in parsing_binding'
6: from app_store_core.rb:70:in version_valid_for_build' 	 5: from app_store_core.rb:31:in get_live_version_number'
4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/spaceship/lib/spaceship/tunes/application.rb:131:in edit_version' 	 3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/spaceship/lib/spaceship/tunes/app_version.rb:291:in find'
2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/spaceship/lib/spaceship/tunes/tunes_client.rb:447:in app_version' 	 1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/spaceship/lib/spaceship/tunes/tunes_client.rb:456:in app_version_data'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/spaceship/lib/spaceship/client.rb:718:in `parse_response': [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["Not Found"], "info"=>nil}, "statusCode"=>"ERROR"} (Spaceship::UnexpectedResponse)
rkr@MacBook-Pro iOS_Aura %
rkr@MacBook-Pro iOS_Aura %
rkr@MacBook-Pro iOS_Aura %
rkr@MacBook-Pro iOS_Aura % fastlane -v
fastlane installation at path:
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.157.2/bin/fastlane
[✔] 🚀
fastlane 2.157.2
rkr@MacBook-Pro iOS_Aura % `

@ravichandra-ayla It looks like you are still using stuff in Spaceship::Tunes 🤔 You need to use the things in Spaceship::ConnectAPI. There are examples in this PR - https://github.com/fastlane/fastlane/pull/16742

@joshdholtz I saw the examples in the given PR and is still using below API's.
Spaceship::Tunes.login(email)
Spaceship::Tunes.select_team(team_name: team_name)
I am also using those API for login. Let me know how to use connectAPI for login and I will try to modify. Thanks.

@ravichandra-ayla Can you try this? 👇
Spaceship::ConnectAPI.login(email, team_name: team_name

But can you also send me what your Fastfile looks like too? That might help me get a better understanding of what’s going on!

@joshdholtz I tried  Spaceship::ConnectAPI.login for login and it's working fine as expected, along with I was also using Spaceship for getting current App Store version string unfortunately I suppose to get it in app.edit_version, where now with new API it's broken.
sample code
app = Spaceship::ConnectAPI::App.find(bundle_id) puts "app = #{app}" puts "app.bundle_id = #{app.bundle_id}" puts "app.name = #{app.name}" version = app.edit_version
Response:-
[15:30:24]: app = #Spaceship::ConnectAPI::App:0x00007f99f18c1bc0
[15:30:24]: app.bundle_id = com.companyname.xyz
[15:30:24]: app.name = X Y Z
[!] undefined method `edit_version' for #Spaceship::ConnectAPI::App:0x00007f99f18c1bc0 (NoMethodError)
where as I thought method name has been changed, so double configured with fastlane-master/spaceship/docs/AppStoreConnect.md README file that method name is same as mentioned in updated doc
Line #97 from the AppStoreConnect.md README file.
app.live_version # the version that's currently available in the App Store
app.edit_version # the version that's in Prepare for Submission mode
It would be great if I can get right API to get edit_version string.
Thanks.

@joshdholtz  any update on this? Our build process is struck now. Would be great if you can help to resolve this issue.

I use the edit_version to release what I have pending for developer for release, and I found this here that might work for me: https://github.com/fastlane/fastlane/blob/76f9fc411118d51c2b715152d6926d273978e3dc/spaceship/lib/spaceship/connect_api/models/app.rb#L233
There is also another method above that something that seems like the edit_version: https://github.com/fastlane/fastlane/blob/76f9fc411118d51c2b715152d6926d273978e3dc/spaceship/lib/spaceship/connect_api/models/app.rb#L204
Have not tried yet to see if it works

@andrewclaus great thanks. I got an API where I can get edit version string. Thanks.
latest_app_version = app.get_app_store_versions.first.version_string
Anyway connect API uses get_app_store_versions API inside get edit version API so I am directly using it to get version string.


Add link issue on Safari

Add link does not work in Safari Version 11.1 (136<IP_ADDRESS>.4). It opens the popup, you insert the url and link title, you press insert, and it does not appear in the editor.
Also tested on Google Chrome Version 66.0.3359.181 and on Firefox 60.0.1 and it works without any problem.

anyone working on this? Any suggestions or workarounds to fix this problem on Safari ? thanks!


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210727093315797 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210727093315797 to main with localized lcls

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 remained the same at 42.48%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26761

Relevant Lines:
57070

💛  - Coveralls


Add key to validation Failure Result

It looks like check returns the key at which the type checking failed, so it was helpful (for my own uses) to have validate do the same. This way, user feedback with validate can be more specific and helpful.

Coverage remained the same at 99.149% when pulling 1edcd1b5bacdee49d6fe111f5c0ab1eb876836d3 on ismcodes:master into 3385f5e3a3e4d206029c565533d13b3f8c8619b1 on pelotom:master.

@pelotom thoughts?


add AnyResolver

This PR adds an AnyResolver enum, which allows libraries to abstract the resolver type without using generics.

Even more important: feature-gated enums work really badly in practice. Just put the whole module behind a feature gate and let the enum contain both options.
Also, the enum should be #[non_exhaustive].

Thanks for the suggestions. I've applied almost all requested changes but I cannot derive Clone and Debug because the inner enums (electrum::Resolver and esplora_blocking::Resolver) don't and can't.

Even more important: feature-gated enums work really badly in practice. Just put the whole module behind a feature gate and let the enum contain both options.

In this case they don't work bad, I've tried this enum and it works good, both selecting both features (electrum and esplora_blocking) or selecting only one. Multiple features in this case are useful because they allow lib users to define features in their libraries to allow selecting esplora, electrum or both. With a single feature this wouldn't be possible and users would be forced to have several unnecessary dependencies. And by adding more resolvers in the future this would get even worse.

they always break compilation downstream once anybody changes the set of features

This can be true in many cases, if I change features it's very likely that code will need to be updated. I don't see this as a strong argument in this specific case. Also, the Resolvers will not change that often.
For example, also bdk uses this pattern, see their AnyBlockchain enum.

I see no single argument for having them here - and a strong argument against (the above). If someone does not need one of them, they would not need this enum, thus feature gates add no value here.

You're missing the argument that if I want to write a library that allows me to choose between just one or both indexers based on features, then I cannot use this AnyResolver, because I would be forced to have all indexers' dependencies (so features would be pointless). I don't see any value in adding this enum without feature-gates, if I want to depend on both indexers unconditionally then I can just turn on both features and use the 2 Resolvers independently. So if you really don't want to merge this as it is let's just close this PR, I will implement the AnyResolver in my library (even if I think this could have been useful also for other libraries).

Can you pls make this against master so we can check the CI?

In the master branch the electrum resolver is missing. If you merge the v0.11 branch into master then I can make this against master

We had this discussion years ago in rust-bitcoin, and the consensus was to avoid feature-gated enum variants at all cost: they always break compilation downstream once anybody changes the set of features. Simply, they are incompatible with any semantic versioning system.

They certainly are orthogonal and provide an additional dimension of complexity, but unfortunately they're unavoidable if targeting different architectures where certain functionality is simply unavailable and features depending on it cannot be compiled in. But in general, I agree with you when this is not the case.


Document nested block comments and add more intra docs links

Fixes #439 and helps with #377.
* [ ] I've included my change in CHANGELOG.md

@ModProg could you perhaps take a look at the grammar changes - it's unfortunately been a while since I last wrote some EBNF :)

Codecov Report
Patch coverage has no change and project coverage change: +3.12 :tada:

Comparison is base (d15bacc) 84.52% compared to head (4f8d3a5) 87.64%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #440      +/-   ##
==========================================
+ Coverage   84.52%   87.64%   +3.12%
==========================================
  Files          59       59
  Lines        7470     7204     -266
==========================================
  Hits         6314     6314
+ Misses       1156      890     -266

Impacted Files
Coverage Δ

src/de/mod.rs
76.92% <0.00%> (+6.35%)
:arrow_up:

src/options.rs
49.57% <0.00%> (+6.28%)
:arrow_up:

src/parse.rs
92.39% <ø> (+19.69%)
:arrow_up:

src/ser/mod.rs
72.70% <0.00%> (+2.02%)
:arrow_up:

src/value/mod.rs
55.87% <0.00%> (-11.61%)
:arrow_down:

src/value/raw.rs
88.65% <0.00%> (-11.35%)
:arrow_down:

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add check for dsc status and utility types to check serving platform availablity

Closes #1946
Description

Add check for dsc status and utility types to check serving platform availability
How Has This Been Tested?

You can check the status of the cluster adding this effect into any component in the dashboard

  React.useEffect(() => {
    fetchClusterStatus().then((status) => {
      const { kServeAvailable, modelMeshAvailable } = checkPlatformAvailability(status);
      console.log(kServeAvailable);
      console.log(modelMeshAvailable);
      console.log(checkKserveFailureStatus(status));
    });
  }, []);

Test Impact

Unit testing the cluster status
Request review criteria:

Self checklist (all need to be checked):

[X] The developer has manually tested the changes and verified that the changes work
[X] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@uidoyen @accorvin @DaoDaoNoCode This is the last piece of the foundational work, this should help us to detect wether the platform are available in the cluster and if there's an issue with either kserve or modelmesh (for the error pages)

/approve


extract_dict and extract_regex_tok should return TokenSpanArray, not DataFrame

For legacy reasons, the functions extract_dict() and extract_regex_tok() in spanner/extract.py return single-column DataFrames. These functions should return TokenSpanArray objects instead. Users who want a DataFrame can construct one on top of the returned array.
In addition to the testing code in test_extract.py, there is some downstream code in the notebooks that will need to be modified to deal with this API change.

hello @frreiss I can fork the project and take a look at the issues if you don't start yet.

Thanks for your interest, @lvntky! We'd be happy to have you work on this issue. You may want to wait for the pull request https://github.com/CODAIT/text-extensions-for-pandas/pull/207, which contains other changes to spanner/extract.py, to be merged.

Update: PR #207 is merged now; this issue should be unblocked.

sorry for the delay @frreiss i cant look the GitHub for the two days I was very busy at the job. but if there anything that I can help please inform me. I really like the project. Best wishes!

@lvntky we welcome contributions of all sizes. We've prepared a list of small changes that would make a good first issue for new contributors. Here's a link: https://github.com/CODAIT/text-extensions-for-pandas/issues?q=is%3Aissue+is%3Aopen+label%3A"good+first+issue"

@frreiss thank you for your friendly approach I really thank you I will hunting the issues at repo :smile:


fix: add an napi handle scope for the callback

Required for Electron 10 where the memory-leak-handle-scope was removed
cc @deepak1556

@alexdima for context, what @MarshallOfSound is referring to is https://github.com/electron/electron/pull/22531 where electron previously had a global handle scope installed which allowed for memory leaks.

published<EMAIL_ADDRESS>I noticed that this generates a warning:
> node-gyp rebuild

  CXX(target) Release/obj.target/keymapping/src/string_conversion.o
  CXX(target) Release/obj.target/keymapping/src/keymapping.o
  CXX(target) Release/obj.target/keymapping/src/keyboard_mac.o
../src/keyboard_mac.mm:184:21: warning: unused variable 'scope' [-Wunused-variable]
  napi_handle_scope scope;
                    ^
1 warning generated.

That is OK for me if it avoids a crash, but it would be nice if we could avoid the warning :).

@alexdima Fixed that warning and actually made this fix work (whoops) over here --> https://github.com/microsoft/node-native-keymap/pull/23


[macOS] Add flutter_view example.

The flutter_view example was unimplemented and benchmark tests that ran the example as a part of a task could not depend on it. This PR implements the flutter_view example for the purpose of

enriching the documentation
bringing up more tests

https://user-images.githubusercontent.com/44445638/189462751-f5ca71cb-03ca-4c7c-9192-7e3dce276020.mov
Fixes https://github.com/flutter/flutter/issues/110538
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] All existing and new tests are passing.

This PR can't have any meaningful tests from the macOS-side since there are no UI updates to the macOS application after a message roundtrips through the message channel.

There could be unit tests to test whether the message can roundtrip, but those tests should be in the engine already.

Dropping android build failure fix and widget tests in favor of perf tests. Integration tests will be available on https://github.com/a-wallen/flutter/tree/macos_flutter_view_example_with_integration


Fixed issue with installing dependencies for suse systems

Fixed issue with installing dependencies for suse linux systems.
Previously agent relied on ID_LIKE property from /etc/os-release file - to determine if current os is suse. This field does not always present for such system, here's some info.
Extended this logic - considering ID field also (values like "sles" and "sles_sap"). Removed exact package version for libicu package, updated dependncy for libopenssl and SLES.
Related docs for OpenSUSE and SLES support (Net core).
Local testing: tested that script works as expected and picks up OS_TYPE properly on SLES.

Hey, there's problem in the installdependencies.sh file, around line 217 there's an "if" without a "then", this is forbidden in shell script.

We've tried to update the version from 2.190.0 to 2.191.0, and the error below appeared:

Hey, there's problem in the installdependencies.sh file, around line 217 there's an "if" without a "then", this is forbidden in shell script.

We've tried to update the version from 2.190.0 to 2.191.0, and the error below appeared:

Nice catch, thanks!
Created PR to fix, we are going to quickly roll it out soon.

Broken link:

@rogerdmorales could you please try it now? It works fine for me - https://vstsagentpackage.azureedge.net/agent/2.191.1/vsts-agent-linux-x64-2.191.1.tar.gz

It worked now, thank's.

Verified with the version 2.191.1, still not works

The code is using ID to determine the SLES os, but it returns 2 lines:

@Johnny-spec current issues don't seem to be related to installdependencies script. It's up to customer to make sure that zypper is installed, necessary providers are available, and there is no conflicts between dependencies - since installdependencies.sh script just installs dependencies per net core documentation.


DataScience v1

First pass through data science exercise. Focused on separating logic into concise methods while keeping it highly readable.

Good first iteration.  Take a look at the comments, refactor and resubmit.  Think more about what classes should have which responsibilities.  Also focus heavily on the public interface.  What should be publicly accessible?  What shouldn't?
Let me or @katieschilling know if you have any questions.


Update frontend and graphql-api CI to run on dependency updates

Updates the frontend and graphql-api github CI yml files to also trigger a run when either the 'package.json' or 'yarn.lock' files are edited.
The primary purpose is to have CI run when dependabot opens PRs that update javascript dependencies, however I think it's also probably good in general to run the test suite whenever any PR wants to update javascript dependencies.

Makes sense to me! What are those top level lock/package files actually used for? Are these dependencies that are shared between the browser and API?

Yeah mostly, also there's a lot of dev dependencies that are tied up in the top level package.json, prettier jest, eslint etc. So dev dependencies that are shared between the frontend and the api seems to be a big use case of it. That seems to make sense to me, but not sure how other places do it.


Bridge: Disable Sequence abort button for a sequence which has not started

Environment

Client OS (e.g., Linux, macOS, Windows): any
Keptn Version (keptn version): 0.9.2
Kubernetes Cloud Provider (e.g., GKE, AKS): any
Kubernetes version (kubectl version): any

Affected Component

[ ] Docs
[ ] CLI
[ ] Kubernetes Integration
[ ] Openshift Integration
[ ] Helm
[ ] Istio
[x] Bridge
[ ] Approval
[ ] Datastore
[ ] REST API
[ ] eventbroker / distributor
[ ] jmeter

Describe the bug
The Abort button for sequences is enabled although the shipyard-controller does not allow to abort sequences that have not been started.
To Reproduce

Have multiple queued sequences
Try to abort a sequence, which has not started yet.

Expected behavior
Pause and abort button should not be enabled for sequences which have not yet been started.

Closing in favor of #5472


Integrate new commands to *GenericCommandParser

Codecov Report
Base: 64.33% // Head: 64.35% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (b7e5d66) compared to base (f9e0d37).
Patch coverage: 72.72% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #295      +/-   ##
============================================
+ Coverage     64.33%   64.35%   +0.01%
- Complexity      883      887       +4
============================================
  Files           173      173
  Lines          3502     3512      +10
  Branches        393      395       +2
============================================
+ Hits           2253     2260       +7
- Misses         1136     1138       +2
- Partials        113      114       +1

Impacted Files
Coverage Δ

...ninurse/logic/parser/EditGenericCommandParser.java
50.00% <44.44%> (-13.64%)
:arrow_down:

...n/java/seedu/uninurse/logic/parser/ParserUtil.java
81.00% <91.66%> (+0.30%)
:arrow_up:

...in/java/seedu/uninurse/logic/parser/CliSyntax.java
94.44% <100.00%> (+0.32%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


What is a reentrancy attack?

A vulnerability where a contract allows repeated calls to itself, potentially causing loss of funds.


could not open USB device (insufficient permissions)

I created a simple container with installed sane-utils package
containers:
  base:
    setup:
      - !Ubuntu yakkety
      - !Install [sane-utils]

commands:
  bash: !Command
    container: base
    run: |
      bash

Then inside container I run command "sane-find-scanner" which outputs
  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not open USB device 0x05e3/0x0716 at 002:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 008:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
...

checking permissions with "ls -la /dev/bus/usb/001/" shows
total 0
drwxr-xr-x  2 nobody nogroup     60 Nov  3 09:24 ./
drwxr-xr-x 12 nobody nogroup    240 Nov  3 09:24 ../
crw-rw-r--  1 nobody nogroup 189, 0 Nov  3 09:24 001

How can I fix the "insufficient permissions" ?
Thanks for your advice

I think you can do sudo chown your_user /dev/bus/usb/001/* (on a host system). If that works you can make an udev rule so that you don't need to do chown on plug-in/plug-out of a scanner (picking a random link from google: this link)

Creating an udev rule on the host which sets MODE="0777" for my scanner resolved the permission issue.
First I tried the wrong way by adding the udev rule inside the container.
Maybe adding a hint to chapter "Tips and Tricks" in the docs might help other users too.
Still I have another issue as "simple-scan" is crashing with a segfault. But original issue is resolved for me.
Thanks for your quick help.

I'm glad it worked!

Maybe adding a hint to chapter "Tips and Tricks" in the docs might help other users too.

Would you like making a PR? This sounds promising, but I'm not sure how to make statement useful enough.

Just to complete info on remaining 'simple-scan crash' issue.
Looks like simple-scan tried to create some files in home folder and crashes in case it's not possible.
Adding environment variable HOME fixed it and now everything works as expected. I can scan from inside my container.

This sounds promising, but I'm not sure how to make statement useful enough.

Me too. At least this specific use case might be an example for others and guide them in the correct direction. I can try to phrase something.


可以期待一下开源吗？

非常期待！

Hi our code is released. We are releasing our dataset.

Hi our code is released. We are releasing our dataset.


MBL-1673 [Android 15] Update Views to be compatible with edge to edge enforcement

📲 What
Modify all the screens to be compatible with Android edge to edge.
🤔 Why
Android 15 introduced edge to edge view enforcement for apps targeting the version (sdk 35).  We need to update some views to look normal in this new context.
🛠 How
For the screens that use composable fixed with Modifier.systemBarsPadding(),
For the others screens a utility was created WindowInsetsUtil
Story 📖
[Android 15] Update Views to be compatible with edge to edge enforcement

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 11.11111% with 56 lines in your changes missing coverage. Please review.

Project coverage is 67.66%. Comparing base (c28b488) to head (cb1cd88).

Files with missing lines
Patch %
Lines

...arter/ui/activities/compose/ReportProjectScreen.kt
0.00%
36 Missing :warning:

...ain/java/com/kickstarter/utils/WindowInsetsUtil.kt
0.00%
11 Missing :warning:

.../ui/activities/compose/projectpage/AddOnsScreen.kt
0.00%
3 Missing :warning:

...vities/compose/projectpage/RewardCarouselScreen.kt
0.00%
3 Missing :warning:

...rter/ui/activities/compose/ChangePasswordScreen.kt
0.00%
1 Missing :warning:

...ckstarter/ui/activities/compose/FormularyScreen.kt
0.00%
1 Missing :warning:

...i/activities/compose/projectpage/CheckoutScreen.kt
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                          Coverage Diff                           @@
##             feat/jpulido/MBL-1739/Android-15    #2131      +/-   ##
======================================================================
- Coverage                               67.78%   67.66%   -0.13%
  Complexity                               2226     2226
======================================================================
  Files                                     368      369       +1
  Lines                                   22851    22903      +52
  Branches                                 3280     3280
======================================================================
+ Hits                                    15490    15497       +7
- Misses                                   5597     5642      +45
  Partials                                 1764     1764

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Tested a bunch of the screens i pointed out in the ticket as having issues with edge to edge on the branch and I still see the issues.  Many of the top bars cant be interacted with now as they are behind the notification bar

In what device are you testing, @matthewfamularo ? I test on an emulator targeting Android 15 and it works


[feat] Introduce the date display?

Just like this.

@li0817 Thank you for your request.
It seems possible.
I'll try it and comment when I've done it.

@li0817 I've made some changes that allow you to customise the date, time, and delimiters to be inserted.
Therefore, after updating to the latest version (0.8.0), if you set it up as follows, you should be able to display it as shown in the example.
Please give it a try.

@li0817 I've made some changes that allow you to customise the date, time, and delimiters to be inserted.
Therefore, after updating to the latest version (0.8.1), if you set it up as follows, you should be able to display it as shown in the example.
Please give it a try.

Thanks! That's very helpful.


Reference API DF support

Description
Takes missing dates from API dataframe, and supplements it with test data for days before the checking date. Useful for non-daily updates (or large batch updates in event of outages)
Changelog
Itemize code/test/documentation changes and files added/removed.

dynamic.py

Fixes

Fixes #(issue)

@nmdefries


bug: Update readme.md file

readme.md file needs an update.
the setup for code locally is not clear enough I think and needs an update.
because as per the instructions followed from readme.md file the setup is giving continuous error,
it would be helpful if it provides what all is required on local machine to setup,
for eg : does it require a visual studio, which node version is required etc.. and many dependencies are depreciated.
sample picture of the error is as follows, please provide guidance on it.

Hi @Junaid-Mohamed, can I work on this issue. Kindly assign this issue to me, and also can you add hactoberfest-accepted tag to this issue.


x/net: How should net http handler behave when Content-Length header is incorrect?

What version of Go are you using (go version)?

$ go version
1.15.11

Does this issue reproduce with the latest release?
maybe
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/zangw/Library/Caches/go-build"
GOENV="/Users/zangw/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/zangw/go/pkg/mod"
GONOPROXY="github.com/Zentertain"
GONOSUMDB="github.com/Zentertain"
GOOS="darwin"
GOPATH="/Users/zangw/go"
GOPRIVATE="github.com/Zentertain"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/Users/zangw/go115/go1.15.11"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/Users/zangw/go115/go1.15.11/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/zangw/go/src/test/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/x3/bcr5s9sj1jqcxd19w9fk4j1c0000gn/T/go-build269433144=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

For server codes
import "net/http"

func defaultHandler(w http.ResponseWriter, r *http.Request) {
	bodyBytes, _ := ioutil.ReadAll(r.Body)
	fmt.Printf("Get request body %+v", string(bodyBytes))
	fmt.Fprint(w, "Hello Golang")
}

http.HandleFunc("/", defaultHandler)
http.ListenAndServe(":8080", nil)

Post HTTP packet with incorrect Content-Length through curl
time curl -v -X POST -H "Content-Type: application/json" -H "Content-Length: 1000" -d '{"key": "value"}' 'http://localhost:8080/'
Output
* TCP_NODELAY set
* Connected to localhost (::1) port 8080 (#0)
> POST / HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.54.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 1000
>
* upload completely sent off: 16 out of 16 bytes
^C
curl -v -X POST -H "Content-Type: application/json" -H "Content-Length: 1000"  0.01s user 0.01s system 0% cpu 26.100 total

Server log output:
Get request body {"key": "value"}

Through Wireshark packet capture, we can see response OK is given from server in line 11. IMO, since the client send TCP segment of a reassembled PDU (line 5), server should NOT handle it in defaultHandler until the whole packet is received. However, server handle this partial packet. Is it correct behavior?
What did you expect to see?
The server should not give a 200 OK response
What did you see instead?
 What happens if you consult the error?

@davecheney
Add error handling codes as
func defaultHandler(w http.ResponseWriter, r *http.Request) {
	bodyBytes, err := ioutil.ReadAll(r.Body)
	if err != nil {
		fmt.Printf("defaultHandler with err %+v \n", err)
		w.WriteHeader(400)
		return
	}
	fmt.Printf("Get request body %+v", string(bodyBytes))
	fmt.Fprint(w, "Hello Golang")
}

Now the HTTP code 400 is captured in WireShark.

@richzw in the issue title you mentioned x/net, but the code snippets above uses the net/http package. Does your code use golang.org/x/net packages? Which package do you think the issue is in? Thanks.

@cherrymui the net/http is used in my test code. Sorry for misleading you.

@richzw is there anything left to do in this ticket? It seems that if the error from io.ReadAll(r.Body) is checked the truncated request body is not an issue.

@davecheney It is not an issue after checking the error from io.ReadAll, it is my bad not checking this error. I will close it.


Backport PR 49508

Backports http://github.com/JuliaLang/julia/pull/49508 to RAI Julia.

This should go to v1.8.2+RAI.

thanks. fixed


screen readers, ARIA, folks with slow internet connections.

We should probably start thinking of how we can build the site to be fairly flexible for all types of people.
Good reading: http://a11yproject.com/
I know very little about how to tackle this properly, and how to implement it specifically with RoR. I can definitely do more research though.
We should at least set up a framework so that it's super easy to build on top of it.

@m3talsmith Are you still interested in doing this?

we should let tota11y loose on our site: https://khan.github.io/tota11y/