Android build of clean sample project fails during dependency resolution

Description
When I setup a fresh project as per the docs using:
npx react-native@latest init RNTestApp

And then try to run it using:
 npx react-native run-android

I get this error:
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not determine the dependencies of null.
   > Cannot query the value of this provider because it has no value available.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

React Native Version
0.72.0
Output of npx react-native info
info Fetching system and libraries information...
System:
  OS: macOS 13.2
  CPU: (10) arm64 Apple M1 Pro
  Memory: 72.66 MB / 32.00 GB
  Shell:
    version: 5.8.1
    path: /bin/zsh
Binaries:
  Node:
    version: 18.12.1
    path: ~/.nvm/versions/node/v18.12.1/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v18.12.1/bin/yarn
  npm:
    version: 8.19.2
    path: ~/.nvm/versions/node/v18.12.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /Users/daniel/.rvm/gems/ruby-3.0.0/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK:
    API Levels:
      - "26"
      - "28"
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
    Build Tools:
      - 28.0.3
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
    System Images:
      - android-31 | Google APIs ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
    Android NDK: 23.1.7779620
IDEs:
  Android Studio: 2022.2 AI-222.4459.24.2221.10121639
  Xcode:
    version: 14.3.1/14E300c
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.1
    path: /usr/bin/javac
  Ruby:
    version: 3.0.0
    path: /Users/daniel/.rvm/rubies/ruby-3.0.0/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.0
    wanted: 0.72.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Steps to reproduce

npx react-native@latest init RNTestApp
cd RNTestApp
 npx react-native run-android

Snack, code example, screenshot, or link to a repository
Above reproducible is available at cnixbtc/RNTestApp.

Steps to reproduce

npx react-native@latest init RNTestApp
cd RNTestApp
 npx react-native run-android

I'm sorry but I cannot reproduce this issue.
Is this happening for every React Native version you try?

Hi @cortinico, thanks for the quick reply. Let me double check with other versions of React Native. I'll also give it a try on a second machine. Will report back.

maybe it's because your Java version is 17 and not 11?

@cnixbtc yes please try to build with Java 11 and report back. I'm not aware of any incompatibilities between Java 17 and React Native 0.72, but this could be one.

@cnixbtc yes please try to build with Java 11 and report back. I'm not aware of any incompatibilities between Java 17 and React Native 0.72, but this could be one.

will retry later this week and report back.

I'm having the same problem with Java 17 and React Native 0.72. I downgraded to Java 11, but got the same error.

Could you share your error messages created while building YOUR_PROJECT/android with android studio?

Facing the same issue here.
If I use Java 11, I'm getting below error
* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.android.internal.application'.
   > Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
      Your current JDK is located in<EMAIL_ADDRESS>      You can try some of the following options:
       - changing the IDE settings.
       - changing the JAVA_HOME environment variable.
       - changing `org.gradle.java.home` in `gradle.properties`.

And if I go with Java 11 then it results in
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':react-native:packages:react-native:ReactAndroid:bundleLibCompileToJarDebug'.
> Could not create task ':react-native:packages:react-native:ReactAndroid:compileDebugJavaWithJavac'.
   > Failed to calculate the value of task ':react-native:packages:react-native:ReactAndroid:compileDebugJavaWithJavac' property 'javaCompiler'.
      > No matching toolchains found for requested specification: {languageVersion=11, vendor=any, implementation=vendor-specific}.
         > No locally installed toolchains match (see https://docs.gradle.org/8.0.1/userguide/toolchains.html#sec:auto_detection) and toolchain download repositories have not been configured (see https://docs.gradle.org/8.0.1/userguide/toolchains.html#sub:download_repositories).

Hey @cnixbtc is your problem solved?

I am having the same error with Java 11 & react native 0.72.3
System:
  OS: macOS 12.2.1
  CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
  Memory: 336.00 MB / 16.00 GB
  Shell:
    version: "5.8"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.16.0
    path: ~/.nvm/versions/node/v18.16.0/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/local/bin/yarn
  npm:
    version: 9.5.1
    path: ~/.nvm/versions/node/v18.16.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.11.3
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 21.4
      - iOS 15.5
      - macOS 12.3
      - tvOS 15.4
      - watchOS 8.5
  Android SDK:
    API Levels:
      - "28"
      - "29"
      - "31"
      - "33"
    Build Tools:
      - 28.0.3
      - 29.0.2
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
    System Images:
      - android-33 | Google APIs Intel x86_64 Atom
    Android NDK: Not Found
IDEs:
  Android Studio: 2020.3 AI-203.7717.56.2031.7583922
  Xcode:
    version: 13.4.1/13F100
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.20
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /Users/lohungwai/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.3
    wanted: 0.72.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Closing as @cnixbtc is unresponsive. If you folks have similar problem, please open a new issue

System:
OS: Windows 10 10.0.22621
CPU: "(16) x64 AMD Ryzen 7 4800H with Radeon Graphics         "
Memory: 5.13 GB / 15.42 GB
Binaries:
Node:
version: 16.16.0
path: C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm:
version: 8.11.0
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK:
AllowDevelopmentWithoutDevLicense: Enabled
IDEs:
Android Studio: AI-223.8836.35.2231.10406996
Visual Studio: Not Found
Languages:
Java: 11.0.20
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.4
wanted: 0.72.4
react-native-windows: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
I have installed the sdk and have set the environment , but then also it shows sdk is not installed? Can you help me with this

I have a problem...
I try to run it using:
yarn android
I get this error:

`PS C:\Windows\System32\aaa\AwesomeProject> yarn android
yarn run v1.22.19
$ react-native run-android
info JS server already running.
info Installing the app...
5 actionable tasks: 5 up-to-date
info 💡 Tip: Make sure that you have set up your development environment correctly, by running react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.

Could not determine the dependencies of null.
Cannot query the value of this provider because it has no value available.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 6s
error Failed to install the app.
info Run CLI with --verbose flag for more details.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
PS C:\Windows\System32\aaa\AwesomeProject> `

Same it is one issue after another but I am not able to solve this one


Improved documentation

Improved the comprehensibility of documentation.
Assuming DEVELOP.md files are the same for all Godot plugins.

LGTM, thanks mate 👍


the proxy is down

@rickroll2222 Indeed, but you can use many other community proxies or try my proxy: proxy.mcraft.fun which has 100% uptime ref and supports authentication ;)

Yes my server is down. I'll fix it in next days
On Wed, Jun 26, 2024, 00:07 Vitaly @.***> wrote:

@rickroll2222 https://github.com/rickroll2222 Indeed, but you can use
many other community proxies or try my proxy: proxy.mcraft.fun which has
100% uptime ref
https://github.com/zardoy/minecraft-web-client/issues/3#issuecomment-2010987530
and supports authentication ;)
—
Reply to this email directly, view it on GitHub
https://github.com/PrismarineJS/prismarine-web-client/issues/371#issuecomment-2190052015,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437VOTSWNBOJQC5QL6TLZJHSY5AVCNFSM6AAAAABJ4L7EBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJQGA2TEMBRGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I'll fix it in next days

Please make sure it's updated with the latest net-browserify, thx!


Add patch that removes setting If-Match headers

Backports https://codereview.chromium.org/2714583002 to Chrome 56.
Refs https://bugs.chromium.org/p/chromium/issues/detail?id=689989
This does not affect Chrome 58 (Electron 1.7.x) so it is only being backported to Chrome 56 (Electron 1.6.x)
/cc @deepak1556 @CharlieHess

Tested this out on macOS using http://clips.vorwaerts-gmbh.de/big_buck_bunny.webm and scrubbing quickly before the video fully loads, appears to be working now as expected, below is the network timeline for 1.6.10 vs. this branch
1.6.10

This branch


proposal: for loop of multiple variables allow join statements in increment

Proposal
We should allow the use i++, j++ as increment for multiple variable for loops.
Right now, the following code in go is not allowed
for i := 0, j := 1; i < 10; i++, j++ {...}

The following code in go is also not allowed
for i := 0, j := 1; i < 10; i+=1, j+=1 {...}

The only code that works is this:
for i, j := 0, 1; i < 10; i, j = i+1, j+1 {...}

We should allow multiple statements like i++, j++. What do you guys think?

I think it would be odd to only allow a change like this in a for loop increment statement. I could see an argument for some syntax allowing for multiple increment statements, but I don't think it's a common enough issue to justify complicating the syntax for the loop.

Agreed, generalize the proposal to allow the stmt standalone
a++, b--

a, b = a+1, b+1 // less readable

@gopherbot add Go2

All the given examples appear equally convoluted and incomprehensible to me. I don't think this style should be encouraged.

You can already do something like this with a slightly different syntax:
for i, j := 0, 0; i < 10; i, j = i+1, j+1 {
	...
}

https://play.golang.org/p/j_y3wryh8Wy
Ok, you can't use ++, but I think the + 1 is clear enough.  So seeing you can already do what you want, I'd say there is no need to change the language for this.

May be thisWay?
https://play.golang.org/p/63fRqztyrm6
	for i, j := 0, 0; i < 10; func(){i++;j++}() {
             ...
	}

I will write to following way if I get this problem.
https://play.golang.org/p/mOAKMvjrbYv
        i:=0
        j:=0
	for {
		if (i<10 && j <10)==false{
	        	break;
		}
                  ....
		i++
		j++
	}

Yes, an anonymous function is possible, or why not,  a named function?
func Inc(args ...*int) {
	for _, ip := range args {
		*ip = *ip + 1
	}
}
...
for i, j := 0, 0; i < 10; Inc(&i, &j) {
	...
}

I would say a function like Inc  or Increment is even more readable than ++, for programmers who are unfamiliar with C.
https://play.golang.org/p/my0PJMa1SpR

Thanks guys. Really appreciate all the information. I will close this now.

@mingwho, none of the people who responded are Go team members.
It's common for proposals here to get criticism from random gophers. I don't think you should give up yet. You've pointed out a legitimate inconsistency in the language. Let the Go team read the issue.

@networkimprov Sorry, but as I pointed out, it is not an inconsistency, but it is by design. The reason the form  i++, j++ does not work is because in Go, unlike in C, the ++ is a statement and not an operator. Furthermore, the , operator, which exists in C, and allows to concatenate expressions   in that language, does not exist in Go in that form. Go may be similar to C, but the languages are different from each other in may subtle ways.  But seeing the history of Go, which I have been following for 10 years when Go first began, I feel that too is by design.
@mingwho
But yes, don't let me discourage you.  I think your proposal is valuable because it points out that there are subtle differences between C (or C++) and Go that may be confusing or surprising. Please listen to what the Go team members have to say about it. Perhaps we should improve the documentation here: https://github.com/golang/go/wiki/GoForCPPProgrammers as well as the Go FAQ to clarify these differences more.

v++ is merely a familiar convenience for v = v+1; it's an assignment statement.
If it was "by design" it's one of several disappointing design decisions ;-)

Actually, in C, assignments are also expressions, so you can do if a = b ,
which is normally a bug. The C language allows too many things to be
expressions, which is a frequent source of bugs. In Go, the conscious
decision was made not to allow this and make them statements, to prevent
such common bugs.
Op do 14 mrt. 2019 20:36 schreef Liam<EMAIL_ADDRESS>
v++ is merely a familiar convenience for v = v+1; it's an assignment
statement.
If it was "by design" it's one of several disappointing design decisions
;-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/30811#issuecomment-473027010, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEWeay2YuF9K1ySY-oa_qaueASMbuXTks5vWqTZgaJpZM4bvgP3
.

Actually, in C, assignments are also expressions, so you can do if (a = b) { ... }  ,
which is normally a bug. The C language allows too many things such as assignment or the ++ and -- operators to be expressions, which is a frequent source of bugs. In Go, the conscious
decision was made not to allow this and make them statements, to prevent
such common bugs.
EDIT: A multiple assignment in go is a single statement. You might call that an inconsistency, but since ++ and assignments are both statements in Go, the only way to have them on one line is to separate them by ;.  So perhaps, for statements and if statements could be extended to allow any number of extra statements that are executed on every iteration in stead of just one now, like so:
for i, j := 0, 0; i < 10; i++ ; j++ {
   ...
}

That would be the least invasive, most backwards compatible way to augment Go to cover this issue.

@ianlancetaylor, I'd like this issue to be considered; it was closed by the author. Should I file a new issue?

@networkimprov Yes, please open a new issue.  Please explain precisely what is being permitted, perhaps as a modification to the EBNF in the language spec.  Is the suggestion to literally permit just { IncDecStmt "," } in the PostStmt of a ForClause?


Report NamespaceNotFederated in propagation status

Previously a namespaced resource whose containing namespace was not federated (i.e. did not contain a FederatedNamespace resource) would report a healthy propagation status.  This has been changed to reporting unhealthy propagation status with reason NamespaceNotFederated.
Fixes #951

CI failure was a flake of the walkthrough test (#952), and tests affected by this PR appear to be otherwise passing.

I need to update the test to wait for the condition.

CI failure due to #962.  I don't think this PR is the cause.

LGTM

Rebased

Rebased on #973

Rebased and ready for review again

Updated to address comments.  I'm using fixup commits to address comments with the intention of squashing before merge, and have accordingly put a hold on the PR to avoid merging before squash.

Thanks @marun! LGTM

Also looks like a legitimate CI failure.

Rebased and addressed the test failure.
Also, I remember why I like using struct pointers with slices. This message has brought to you by the winning combination of pass-by-value and append.

Rebased

@font I've stripped this down to the bugfix.  I'll submit unrelated cleanup separately to avoid blocking this further at this time.

Rebased

@marun This needs a conflict resolution.

LGTM. @marun please rebase. Thanks!

Rebased

/lgtm


Gene->Pathway->Gene error?

I call /bioentity/gene/{id}/pathways/ with id = HGNC:5013
This gives me a list of pathway identifiers.
I can then call /bioentity/pathway/{id}/genes with each pathway identifier, and I think I should get HGNC:5013 as one of the returned genes.
But for REACT:R-HSA-168256, HGNC:5013 doesn't appear to be one of the genes returned.
Is this an error, or is the situation more complicated than I thought?

I think "immune system" is associated with a large number of proteins and genes: https://reactome.org/PathwayBrowser/#/R-HSA-168256&DTAB=MT
If you up the result count or page over the data HMOX1 should be there, for example:
https://api.monarchinitiative.org/api/bioentity/pathway/REACT%3AR-HSA-168256/genes/?rows=3000&fetch_objects=true

Oh that makes sense. Thanks.


Consider adding meta tag to zoom out in mobile devices

@SKOLZ Consider adding <meta name="viewport" content="width=device-width, initial-scale=1.0">

@SKOLZ

@epintos I thought we had the "fake responsive" meta tag which makes the page look really small and allows the user to zoom in. This is not ideal but It's a basic solution for pages that don't have responsiveness implemented. What should we do?

Add the responsive meta tag?
Add the fake responsive zoom out meta tag?

@SKOLZ I'm not sure which one is in the app. Which one you recommend?

While it was probably a good idea in 2017, we decide to move the bootstrap to an API only version, so I'm closing this issue.


SA1008 false positive on cast in lambda in right-hand side of null coalescing op

I pass in a lambda expression (mb, ex) calling a method Write having arguments LogLevel.Info and null coalescing operator.
On null coalescing operator argument, a function is passed in mb and a parenthesed lambda. This parenthesed lambda returns a parenthesed value (string concatanation).
(mb, ex) => Write((int)LogLevel.Info, mb ?? (_ =>_ ("Exception during " + myName))

Most likely this example can be simplified, as I suspect the culprit is in the parenthesed string concat as return from a shorthand lambda.

Where do you get SA1008?
Why do you think this is a false positive?
Assuming that _ is a Action<string> or a Func<string, string>, this looks correct to me, because _ ("Exception during " + myName) is  a method invocation and there should be no space before its opening parenthesis.

@generateui, if you still thinks this is a bug, please answer the questions above and provide a compilable example so it is possible to understand your code.

Closing this one as by design (detail in https://github.com/DotNetAnalyzers/StyleCopAnalyzers/issues/3449#issuecomment-1117729579)


Chore: first pass at new *Transform.operation() naming

Module or class has type in the name. e.g., RedLinkTransform,
ReferenceTransform. I've also taken the liberty of dropping the
plural on RedLinks since a more terse style was wanted and the other
transforms were singular.

Rename some of the class / module methods to be more terse. This still
needs a bit of work. e,g., RedLinkTransform.hide(),
ReferenceTransform.opacity(.5). I changed
CollapseTableTransform.collapseTables() to just .transform() since
what it really does is enable tables to be collapsed and the default
state happens to be collapsed.

ElementUtilties looked like it was aready in pretty good shape.

Add . prefix to method test cases.

Since this is a large and very breaking patch. Please focus on
eliminating unwanted changes and fixing consistency bugs rather than
requesting features and enhancements.
todo: update changelog with list of API changes once agreed on.

@montehurd, please review as soon as you can. This has a ton of the breaking API changes wanted.

@niedzielski Hey sorry I didn't have a chance to look at this earlier! I left a couple quick comments.

Either as part of this PR or a new PR, please rename all camelCase and shish-kebab CSS symbols to snake_case.

I'm willing to reconsider isolating each transform + helper classes to a distinct subdirectory in light of the size of the lazy load and footer transforms. We'll need to decide on a "every directory has an index.js" vs some redundancy in the module names.


[Feature]: Add support for passing function definitions from eval thread to main thread

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
The users would like to specify function definition for echarts configuration in the property pane like this. At the moment, there is ability to pass only evaluated values of a function to main thread. There is a requirement to pass function definition rather than function return value for ECharts
Why should this be worked on?
This enables the user to use ECharts inside Appsmith. Without this feature, we won't be able to release Custom ECharts to our users. This is a blocking issue.

@bharath31 would love to see this. I currently use echarts in appsmith but I am exactly missing this functionality. Thanks

@satbir121 could we estimate the effort here?

@dustinrecko
Thanks for reaching out.
Can you please give us an example of how are you using ECharts in Appsmith right now ? This will help us understand your use case better. Thanks!
cc : @somangshu @dilippitchika

@rajatagrawal , basically as described in this issue. For many axis label formatting requirements it is needed to pass a function to echart's formatter option because otherwise it's quite limited.

@dustinrecko can you let me know the following?

Are you using e-charts via iframe? Have you installed the echarts library using our custom JS libs feature?
Is there a reason you are using e-charts? Did fusion charts not work for you?

hi @dilippitchika ,

no, I'm using the native solution that is currently in progress as far as I understand (I accidentally stumbled upon the fact that I can use CUSTOM_ECHART as chart type value and then it works in appsmith cloud)
I just remember that I had an issue with fusion charts so I started some research and during that research I figured out that you are currently working on a migration to echarts so I stopped with fusion charts :)

@dustinrecko thanks for letting me know, can you suggest which chart are you using from custom_echart?

@dilippitchika , what do you mean exactly?  this is how it looks for me:

Is this being worked on? Would love to be able to pass functions in the echart option config object.

This is already implemented and available with ECharts in Chart Widget. Can you please check it out @cch264 ?


Don't encode secret when signing request

According to the Acquia HTTP HMAC spec, the secret shouldn't be base64 encoded when signing the request. https://github.com/acquia/http-hmac-spec#secret-key

I tried to explain some of that when Robert and I worked on this. In theory here it does not matter because we just pass the HMAC key and secret into this Postman script but some anecdotal testing suggested this script worked with Journey and/or Lift. So I approve this change, but I'm not sure how it affects those other apps. In my previous conversations with Robert I was confused as to how Journey and Lift handle the encoding (or not) of the secret.

merged into 1.1.4 branch

Thanks @robert-burden 👍


url_title not detecting some special characteres

Hey, it's so nice to participate in an improvement for this spectacular framework.
Yesterday I commit a change to a client system. When he try to create a resource all seems to be fine, but i used the url_title to slugify the title to url and save it to the database.
The problem is that did not detected some special characteres like ç,~,`

Try like this
function url_segment(string $text) : string
{
	$text = url_title($text, '-', true);
	helper('text');
	$text = convert_accented_characters($text);
	return $text;
}

@natanfelles is absolutely correct. For a deeper explanation the HTTP spec (RFC-3986) does not allow characters outside of the US-ASCII as part of a URI, unless it's been encoded.
That being said, I'm wondering if we should incorporate that into the url_title() helper method itself, or just make a note of it in the docs. I'm leaning toward docs because otherwise it might be a surprise to developers.
@natanfelles @MGatner @michalsn what do you guys think?

The convert_accented_characters should be incorporated.

Thank you.
It would be nice if the functionality of convert_accented_characters is implemented in url_title

I remember many discussions about this one in the past. Personally, I would love to see url_title() handling accented characters under the hood, but at this point, it's too late for that since developers may rely on produced results heavily.
Another option would be to introduce yet another parameter to url_title() function, but idk if I would like to see this.
If I gonna need this functionality I will probably write a simple helper for that, just like I always did in CI3.

I think a good solution would be to create a new helper function in the url_helper: mb_url_title.
Thoughts? Anyone want to submit a PR?

Resolved via #3086


Appstudio update test-component-pac-rzww

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-rzww-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
30 seconds
build-container

✅ Succeeded
20 seconds
sanity-inspect-image

✅ Succeeded
24 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
41 seconds
clamav-scan

✅ Succeeded
16 seconds
sbom-json-check

✅ Succeeded
8 seconds
sanity-label-check

✅ Succeeded
6 seconds
sanity-optional-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-rzww-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
32 seconds
clone-repository

✅ Succeeded
55 seconds
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
36 seconds
clamav-scan

✅ Succeeded
16 seconds
sanity-optional-label-check

✅ Succeeded
16 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary

Pipelines as Code CI/test-component-pac-rzww-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
32 seconds
clone-repository

✅ Succeeded
55 seconds
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
12 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
36 seconds
clamav-scan

✅ Succeeded
16 seconds
sanity-optional-label-check

✅ Succeeded
16 seconds
sanity-label-check

✅ Succeeded
6 seconds
show-summary


Add VISION.md

[x] add vision file
[x] add vision explanation (nice to scope and direct to on closing out of scope PRs/Issues)

Fixed by: ec342e9da9058e4f8656043e6da03d96b89dd76a


Minor performance improvement in bezier.py with preallocating array.

Just some minor updates to the mathematics.
And changing the clear function in opengl mobject because it doesn't need to keep the array.

@MrDiver is this now a draft or ready to be merged? :-)

If you deem it as ready you can merge it

Alright, was just asking because of the commit message of 0c177ad.
Thank you!


Cert error on https://alpha.html5test.com/

IF one goes to the HTTPS version of the site, it generates a cert error, blocking the page: https://alpha.html5test.com/index.html
(http://html5test.com will auto forward to HTTPS, so I hit this when editing URL to go to alpha version. It may be an issue which goes away when the alpha version moves to the bare www URL)

This is a known issue. I can't use Let's Encrypt yet on this server and I don't think paying for a certificate for this temporary location makes much sense at this stage.


Couple of changes to fix logs

Changing logs to be printed with (level)w instead of (level)f - Closes #57
Changing the path to store logs - Closes #58

Signed-off-by: Yash Oza<EMAIL_ADDRESS>

fixed #58


Add metadata support - cherry picked from sbauch PR

@sbauch I cherry picked this bit to get this going.  @kshnurov, can you have a quick look?

@spovich LGTM


[idyntree] Update to 9.0.0

Furthermore, remove irrlicht feature from default features as since version 9.0.0 idyntree requires irrlicht compiled with SDL support on Windows, and that is not available in irrlicht compiled by vcpkg, see https://github.com/robotology/idyntree/releases/tag/v9.0.0 .

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

When I test the feature irrlicht of x64-linux, I get the following error:
CMake Error at /home/vliumonica/i/scripts/buildsystems/vcpkg.cmake:853 (_find_package):
  By not providing "Findglfw3.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "glfw3", but
  CMake did not find one.

  Could not find a package configuration file provided by "glfw3" with any of
  the following names:

    glfw3Config.cmake
    glfw3-config.cmake

  Add the installation prefix of "glfw3" to CMAKE_PREFIX_PATH or set
  "glfw3_DIR" to a directory containing one of the above files.  If "glfw3"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  src/visualization/CMakeLists.txt:75 (find_package)

-- Configuring incomplete, errors occurred!

Should it be added as a dependency of the feature irrlicht?

When I test the feature irrlicht of x64-linux, I get the following error:
CMake Error at /home/vliumonica/i/scripts/buildsystems/vcpkg.cmake:853 (_find_package):
  By not providing "Findglfw3.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "glfw3", but
  CMake did not find one.

  Could not find a package configuration file provided by "glfw3" with any of
  the following names:

    glfw3Config.cmake
    glfw3-config.cmake

  Add the installation prefix of "glfw3" to CMAKE_PREFIX_PATH or set
  "glfw3_DIR" to a directory containing one of the above files.  If "glfw3"
  provides a separate development package or SDK, be sure it has been
  installed.
Call Stack (most recent call first):
  src/visualization/CMakeLists.txt:75 (find_package)

-- Configuring incomplete, errors occurred!

Should it be added as a dependency of the feature irrlicht?
Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review". That way, I can be aware that you've responded since you can't modify the tags.

You are right, I forgot about that. I fixed this now and I tested the irrlicht feature locally and it works fine, thanks!

Feature assimp are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static
x64-linux

Feature irrlicht are tested successfully in the following triplet:
x64-linux
The usage test passed (header files found):
The package idyntree provides CMake targets:

    find_package(iDynTree CONFIG REQUIRED)
    target_link_libraries(main PRIVATE iDynTree::idyntree-core iDynTree::idyntree-model iDynTree::idyntree-modelio iDynTree::idyntree-modelio iDynTree::idyntree-high-level iDynTree::idyntree-estimation)


update cluster-manager rbac

Description
update the clusterrole of cluster-manager.
Related Issue
https://issues.redhat.com/browse/ACM-10667
Changes Made
Provide a clear and concise overview of the changes made in this pull request.
Screenshots (if applicable)
Add screenshots or GIFs that demonstrate the changes visually, if relevant.
Checklist

[x] I have tested the changes locally and they are functioning as expected.
[x] I have updated the documentation (if necessary) to reflect the changes.
[x] I have added/updated relevant unit tests (if applicable).
[x] I have ensured that my code follows the project's coding standards.
[x] I have checked for any potential security issues and addressed them.
[x] I have added necessary comments to the code, especially in complex or unclear sections.
[x] I have rebased my branch on top of the latest main/master branch.

Additional Notes
Add any additional notes, context, or information that might be helpful for reviewers.
Reviewers
Tag the appropriate reviewers who should review this pull request. To add reviewers, please add the following line: /cc @reviewer1 @reviewer2
Definition of Done

[x] Code is reviewed.
[x] Code is tested.
[x] Documentation is updated.
[x] All checks and tests pass.
[x] Approved by at least one reviewer.
[x] Merged into the main/master branch.

/assign @dislbenn

/lgtm


(Bug) Transaction in feed not showing amount

A lot of transactions show -.-- in the amount

txs seem to have the receipt data but for some reason amount is not saved to feed item, the value field is empty
also there seems to be an issue with the logging the information, the log {from: "UserStorage"} "formatEvent: parsed data" always have empty data in the fields to, from, counterpartydisplayname etc...

{id: "0x4b8d08ff856144adb595e207fd26c724d527fd104c6835cab5afbc6604913961", type: "receive", to: "", counterPartyDisplayName: "", from: "", …}
id: "0x4b8d08ff856144adb595e207fd26c724d527fd104c6835cab5afbc6604913961"
type: "receive"
to: ""
counterPartyDisplayName: ""
from: ""
receiptData: {name: "Transfer", from: "0x5f65867f6d1bc897d5ba5103717b1fadbdc75ee5", to: "0x0f28fcd41a3ca4d1e15a8a92d851f3d64018f5c9", value: "6000"}
address: "0x5f65867f6d1bc897d5ba5103717b1fadbdc75ee5"
initiator: ""
initiatorType: undefined
value: "6000"
displayName: "Unknown"
message: ""
proto: Object

@sirpy
I tried to reproduce this issue locally and on gooddev without success. Could you provide the passphrase (mnemonic) for the account where this issue appears (from where you get the screenshot)?

Will be checked after release on Prod

The issue isn't reproduce on the eWallet v0.16
I used the same account that had this issue.
Video: https://www.dropbox.com/s/tsj8rgxfhx8fxoq/transaction amount.mp4?dl=0


Installed extensions don't appear as tabs on your management dashboard

Installed extensions don't appear as tabs on your management dashboard
https://docs.microsoft.com/en-us/sql/azure-data-studio/extensions?view=sql-server-2017
Using version 1.0.0 connecting to SQL 2016 Standard (13.0.5201.2), installed and enabled SQL Server Agent 0.33.0 & Server Reports 0.1.3.
This is a fresh install of Azure Data Studio after uninstalling SQL Ops Studio.
Issue: There is not a + sign when managing the connection to open dashboard extensions menu.
The developer tools do not have any errors, only 4 SimpleKeybinding warnings.

setting "workbench.enablePreviewFeatures": true

that was it, thanks.

Closing based on above replies.  We're looking at how to make the preview feature switch more obvious.


Group configuration cannot be re-opened

Describe the bug
After initial configuration and a restart of Obsidian the group tab in the configuration menu cannot be opened
To Reproduce
Steps to reproduce the behavior:

Go to '3D graph'
Click on the cog wheel
Click on "Group"
Configure paths and colors
Close Obsidian
Open Obsidian
Go to '3D graph'
Click on the cog wheel
Click on "Group"
Nothing happens

Desktop (please complete the following information):

OS: Windows 10
Obsidian Version [1.1.16]

Screenshot

Additional information
I have UTF8 symbols in my path configuration:
🕮 Literatur-Notes/Pocket

Just adding some more findings to this, when looking at the html code it seems as though something in line is causing it to fail to generate "children" for the group settings tree, I am also seeing this error pop up in the console

, if I knew more about JS I would try and reverse engineer this but I work with python

Та же проблема.

I found a data type discrepancy between Obsidian sessions. When I make two groups in Obsidian, they are correctly stored as NodeGroup types for the remainder of the session. However, on closing and re-opening Obsidian, the same groups are no longer of type NodeGroup, instead resembling generic associative arrays.


hubble: Add "hubble-prefer-ipv6" option

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

This change adds an option to the Hubble Relay communication that allows to configure the previously hardcoded IPv4/IPv6 preference. When a node has mixed IPv4 and IPv6 addresses, but internal cluster communication is only IPv6-based, Hubble would announce wrong node addresses which would break communication to the agents. The previous IPv4 preference is kept as default.
Our specific use case for this is EKS with IPv6. When an instance is put into a public subnet and receives a public IP, this IP will be mapped as ExternalIP onto the node. Hubble will then announce that IP, even though no communication can happen on it. Instead, it should announce the IPv6 address the EC2 instance (like it does for nodes without public IP).
We've tested this changeset successfully in real IPv6 EKS clusters using a custom build of v1.12.2.
hubble: Add "hubble-prefer-ipv6" option

Hey @kaworu,
thanks for your remarks! I tried to integrate your proposals and pushed a new version. I was a bit insecure about where to put the AddressFamily types. I've now thrown them into the serviceoption package, but if you think there is a better place for them I'd appreciate a pointer.

Thank you for the hint @jibi! I've adapted the PR accordingly.

/test

/test-runtime

test-1.23-5.4 is failing due to https://github.com/cilium/cilium/issues/21735, ci-external-workloads is failing to provision the cluster (https://github.com/cilium/cilium/pull/21885 should fix it), all other required tests are green, marking as ready


Optimize Weighted Block Solver for Low # of classes

The current parallelization strategy is over classes, so in (e.g. binary classification) the weighted block solver is slow at scale.
cc @ericmjonas

Fixed by #228


Add a release task to package.json

Add npm run release to package.json that will do:

Build a package (npm run build)
Increment a version

I think there are some convenient commands provided by npm to bump versions

Commit and tag it

As you can make a new release easily on GitHub by just clicking around, this command seems unnecessary.


Backlight timeout

If possible I would ask about some little enhancement.
The first is about backlight timeout setting. Would it be possible to add more values betwen 20 seconds and 1 minute?
For example 30, 40 secs...

Hi,
Thank you for your message.
It's possible, off course, but the question is : why ? Have you got a typical use case ? Note that, you could use F + 8 to quickly switch backlight ON or OFF, on demand.
Armel F4HWN.

Ok. I looked at the code.
In the next version, you'll be able to set the value of BackLt to ON or OFF or for a duration ranging from 5 seconds to 5 minutes... by steps of 5 seconds. For example, you could choose 03min 15sec.
Enjoy.
Armel F4HWN.

Since there is a smooth brightening when turning on, it could be added at any time :D

Fixed in v2.5


Prevent adding invalid windows filenames

When I am on Linux, I can add files like "List?Trigger.sql".
This should actually be List_Trigger.sql, the "? to _ mixup" comes from keyboard-layout mixup.
When I commit changes to the git repo on Linux, this works.
When I want to pull the latest version from the git repo on Windows, this creates errors.
Rider should warn on pushing illegal windows filenames to a git repo.

@ststeiger, thanks for feedback. Could you please file this issue at https://youtrack.jetbrains.com/ ?

Going to close the issue in this repo for now.


Noticed an unnecessary expression within the hydration script while watching the stream

https://github.com/ryansolid/dom-expressions/blob/6021864cc1d521dcf3ae91b2d20f585557e9875c/packages/dom-expressions/assets/hydrationScripts.js#L4
Am I missing something or is that doubled && el in the expression doubled by mistake?

Hmm.. I wonder if I can make it shorter.. it's a sneaky way to return the element. We need to check that it exists up front but we also need to return it.

Maybe something like:
return el?.hasAttribute?.('data-hk') ?
  el :
  lookup(
    (el.host && el.host instanceof Node) ?
      el.host :
      el.parentNode
  );

Unless it's for golfing purposes because of transpilation inefficiency?

Yeah I've avoided optional chaining so far. This script doesn't go through transpilation and gets output directly so any assumptions I make here affect what browsers this runs in.

Yeah, makes sense. 👍


Feature safehtml

separate only the new property-type SafeHTML as a feature.
http://code.google.com/webtoolkit/doc/latest/DevGuideSecuritySafeHtml.html
in our opinion, the best practice from google and those of our security engineers, it is the best solution to use SafeHTML until the real DOM-apply happens. This means, avoid handling a potential dangerous String.
The same way that everbody recommends to keep a String as long as possible SafeHTML (== "not a String"), we try to avoid this in the other direction. This means for us: avoid having a String in any property where a developer has access to, but rather use SafeHTML from the very first response-interaction.
One of our security guys told us a very simple rule of thumb: every String that is not written in the sourcecode is potentially dangerous. Google tells the same thing when explaining appendHtmlConstant. Following that rule, the response of our own backend must not be safe and therefore must be protected by using SafeHTML.
I hope this helps explaining why bringing in SafeHTML to RestyGWT is a good decision.

won't


Match highlight.js GitHub style to GitHub.com

Followup from #1091
The CSS is minified atm, need to unpack, style, then minify again

https://github.com/isagalaev/highlight.js/blob/master/src/styles/github.css
Non Minified version ^^


Install script does not support Arch Linux

When running the default server install script, it incorrectly detects my system as ubuntu, and promptly fails on the first apt command.
Contents of my /etc/os-release:
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
VERSION_ID=TEMPLATE_VERSION_ID
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

Weird! We use os-release and grep for the ID line, which we have a case for arch.
In this csse you can use pacman directly to install atuin

This should be resolved, happy to reopen should it occur again


Lighting Application

Can I use this for my lightning application?
I want to utilizes the functionality but I don't know if the declarative lookup rollup summaries I create on my scratch org will come down through meta data. Is there a package version number to make it a dependency of a sfdx project

@brianbier yes you can define rollup rules and triggers in a scratch org and pull them in a scratch org. Just install the dlrs package in your scratch org.


Add boot/00-check-rtc-and-wait-ntp.sh to cidata

In vz, the VM lacks an RTC when booting with a kernel image (see: https://developer.apple.com/forums/thread/760344). This causes incorrect system time until NTP synchronizes it, leading to TLS errors. To avoid TLS errors, this script waits for NTP synchronization if RTC is unavailable.
This script does the following:

Exits with 0 if /dev/rtc0 exists.
Exits with 0 if systemctl is not available.
Enables systemd-time-wait-sync.service to wait for NTP synchronization at an earlier stage on subsequent boots.
Waits for NTP synchronization within the script for the first boot.

Log output during execution:
LIMA 2024-08-08T23:51:15+09:00| Executing /mnt/lima-cidata/boot/00-check-rtc-and-wait-ntp.sh
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-time-wait-sync.service → /usr/lib/systemd/system/systemd-time-wait-sync.service.
TimeUSec=Thu 2024-08-08 23:51:15 JST, Waiting for NTP synchronization...
TimeUSec=Thu 2024-08-08 23:51:16 JST, Waiting for NTP synchronization...
...
TimeUSec=Thu 2024-08-08 23:51:41 JST, Waiting for NTP synchronization...
TimeUSec=Thu 2024-08-08 23:51:42 JST, Waiting for NTP synchronization...
TimeUSec=Tue 2024-11-12 11:43:37 JST, NTP synchronization complete.
NTPMessage={ Leap=0, Version=4, Mode=4, Stratum=2, Precision=-25, RootDelay=991us, RootDispersion=259us, Reference=11FD1CFB, OriginateTimestamp=Thu 2024-08-08 23:51:43 JST, ReceiveTimestamp=Tue 2024-11-12 11:43:36 JST, TransmitTimestamp=Tue 2024-11-12 11:43:36 JST, DestinationTimestamp=Thu 2024-08-08 23:51:43 JST, Ignored=no, PacketCount=1, Jitter=0 }

Log output during execution:

It seems there is no pattern to the time spent waiting for NTP synchronization. Sometimes it waits for about 30 seconds, while other times it doesn't wait at all because it is already synchronized.

opened issue #2905 regarding the problem when using a kernel image with vz.

In vz, the VM lacks an RTC when booting with a kernel image (see: https://developer.apple.com/forums/thread/760344). This causes incorrect system time until NTP synchronizes it, leading to TLS errors.

Why do we get TLS errors? can we avoid them without waiting for NTP update?

Why do we get TLS errors? can we avoid them without waiting for NTP update?

The curl error message posted in #2905 is as follows:
[    6.489211] cloud-init[770]: + curl -fsSL https://get.docker.com
[    6.558633] cloud-init[770]: curl: (60) SSL certificate problem: certificate is not yet valid
[    6.558703] cloud-init[770]: More details here: https://curl.se/docs/sslcerts.html
[    6.558761] cloud-init[770]: curl failed to verify the legitimacy of the server and therefore could not
[    6.558834] cloud-init[770]: establish a secure connection to it. To learn more about this situation and
[    6.558926] cloud-init[770]: how to fix it, please visit the web page mentioned above.
[    6.559955] cloud-init[770]: LIMA 2024-08-08T23:51:16+09:00| WARNING: Failed to execute /mnt/lima-cidata/provision.system/00000002

The system time at that point was approximately 2024-08-08T23:51:16+09:00. Checking the certificate for https://get.docker.com shows:
$ curl -w '%{certs}' https://get.docker.com -o /dev/null | grep date
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 22115  100 22115    0     0  74788      0 --:--:-- --:--:-- --:--:-- 74966
Start date:Sep  2 00:00:00 2024 GMT
Expire date:Oct  1 23:59:59 2025 GMT
Start date:Aug 23 22:25:30 2022 GMT
Expire date:Aug 23 22:25:30 2030 GMT
Start date:May 25 12:00:00 2015 GMT
Expire date:Dec 31 01:00:00 2037 GMT

The certificate appears to be valid from Sep 2 00:00:00 2024 GMT, so the system judged it as "not yet valid," causing the connection to fail.
#2905 also includes logs from apt-get, though the details there are unclear.

curl -fsSL https://get.docker.com

Why not use -k to skip verification of the certificate? We don't really need to verify the server which we fully control.

Start date:Sep  2 00:00:00 2024 GMT
Expire date:Oct  1 23:59:59 2025 GMT
Start date:Aug 23 22:25:30 2022 GMT
Expire date:Aug 23 22:25:30 2030 GMT
Start date:May 25 12:00:00 2015 GMT
Expire date:Dec 31 01:00:00 2037 GMT

Who create the certificate? can we create it with start date in the distant past, and expire date in the distant future, to ensure that it is always considered valid, even when the guest clock is broken?

Ok, I see we fail to validate the remote certificate when accessing https://get.docker.com which we have no control of so we cannot avoid the verification.

Log output during execution:

It seems there is no pattern to the time spent waiting for NTP synchronization. Sometimes it waits for about 30 seconds, while other times it doesn't wait at all because it is already synchronized.

Adding unpredictable 30 seconds wait when starting is not great, but if this happens only when starting with kernel image I think we are fine.

Sometimes it waits for about 30 seconds

Not specific to NTP, but we have to have a method to show the progress information in limactl start CLI

but if this happens only when starting with kernel image I think we are fine.

As far as I know, /dev/rtc0 is only unavailable when using a kernel image with vz.

By adding a process to set the script's modification time as the system time on the first iteration of the loop waiting for NTP synchronization, the loop now completes in about 1 second each time. It no longer takes up to 30 seconds.

Thanks! 🙏🏻


chore: Turn off clippy on bors

Bors started having trouble with our clippy job.
Turn it off as it's not essential (we run it on github anyway).
This quickfix will buy us more time until we'll move away from bors.
context:
https://github.com/get10101/10101/pull/626#issuecomment-1542742519 (and other today's PRs, where clippy passes locally but fails on bors.

Actually, maybe it's not worth disabling that one, since others can also fail instantly.

This means that we can end up breaking main if we're not careful. But I agree that this is a good idea for now.

not sure whether this is enough if lint-commits failed too 😂

@luckysori I've opened #630 , which might need to do until we go with Github Merge Queue.


ARTEMIS-762 Reflect management changes in AMQP protocol

Was the commit of the log file intentional?

@tabish121 good catch

@tabish121 removed and added **/*.log to my gitignore :) cheers

The tests seem to be using sleep calls to determine connection closed which is not the best given that it might close long before, or not depending on the speed of the machine, I'd recommend using the Wait class that was pulled over from 5.x where you can do a "Wait.waitFor(new Wait.Condition() { return ....} );"  that way you can avoid adding a bunch of extra time to the tests unnecessarily

The remote close on the connection doesn't appear to provide any ErrorCondition to the remote to give it any indication of why it was closed which is less than ideal.  There's a couple different stock AMQP error conditions that could be used, in the case of the Queue being deleted you could for instance use the "amqp:resource-deleted" error to at least give the remote some hint to what happened.

@mtaylor  I have rebased the whole thing into my branch here:
https://github.com/clebertsuconic/activemq-artemis/tree/ARTEMIS-762
I was going to merge this, but I'm not sure about if this is ready to merge yet give @tabish121  comments. you want me to merge directly.. or you want to fetch my branch and rebase here?

@clebertsuconic please leave this I have made the changes locally, but need to modify the test client to handle disconnect errors.  Will update shortly.

@mtaylor is this ready now?

@clebertsuconic Yes this is ready to go.  Cheers


Search / Autocomplete / UX Guidelines are incorrect

https://mapzen.com/documentation/search/autocomplete/#user-experience-guidelines
There should be more accurate rate limits than a maximum of one or two requests per second. The Mapzen search demo does not throttle at all, and the API seems to support this just fine. If there is a rate limit, it should be lower than 500-1000ms, because that is very high for a typing speed.
Secondly, the requested_at parameter is not returned in the API response. There is a response.geocoding.timestamp attribute, but it does not seem to act in the same manner as requested_at in the docs.

Yeah, we need to at least tell people to use our current per second rate limit (6 RPS or 166ms between requests). I'd love to see us eventually raise our per second rate limits or switch to per minute rate limits so that we can support 10-20 requests per seconds. I think that should be sufficient for a good autocomplete experience. Our API performance isn't always up to <100ms response times for autocomplete either :( but we'll get there.
The requested_at timestamp was mentioned before and we somehow totally missed that. I think response.geocoding.timestamp is calculated right before the response is sent, and then cached, meaning it wouldn't help discover responses that come back out of order. Looks like mapzen.js (via leaflet-geocoder-mapzen) does its own tracking for responses. I don't want to have to tell people to do this, but with our current caching setup I don't see another way :(

updating this for the docs, @orangejulius should I just remove the info about 'requested_at'?


Azure powershell for role assignments on purview root collection

why is not possoible to assignment of Purview root collection roles via Powershell or azure CLI . only collection admin roleassignment is possoible with azure powershell, all other roles for ex. Data curator role to an identity has to be added manually from the purview portal. Nowhere in the documentation this is clearly mention if this is possible or not!

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

ID: 1bb9ad75-5aa1-af3d-9f59-073015190950
Version Independent ID: 467433dd-ade8-5109-eaa5-a2198146b769
Content: Understand access and permissions in the Microsoft Purview governance portal - Microsoft Purview
Content Source: articles/purview/catalog-permissions.md
Service: purview
Sub-service: purview-data-map
GitHub Login: @viseshag
Microsoft Alias: viseshag

@vivekharrai
Thanks for your feedback! We will investigate and update as appropriate.

Hi @vivekharrai
Please go through this below link for your reference. These are some commands used in Azure Purview to assign root collection admin.
https://learn.microsoft.com/en-us/cli/azure/purview/account?view=azure-cli-latest#az-purview-account-add-root-collection-admin

@vivekharrai
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#Please-close


Container is falsy in LayoutAnimation

Description
I have upgraded RN 0.63.2 to 0.64.0-rc.1, but getting error Container is falsy in LayoutAnimation, but when i upgrade from new project, it is working fine.
React Native version:
System:
OS: macOS 10.15.6
CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 3.09 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.18.3 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.6 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.1, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
Android SDK:
API Levels: 28, 29, 30
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.1
Android NDK: Not Found
IDEs:
Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
Xcode: 12.1/12A7403 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_262 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0-rc.1 => 0.64.0-rc.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce

Follow the step in https://react-native-community.github.io/upgrade-helper/?from=0.63.2&to=0.64.0-rc.1
Build & Clean the project
Build success
Error Container is Falsy in LayoutAnimation

Expected Results
No Error Container is Falsy in LayoutAnimation
Snack, code example, screenshot, or link to a repository:

I am facing the same problem upgrading from 0.60.4 to 0.64.0-rc.1.

@RobbyWH @RobbyWH
This error caused by optional chaining, you can fix it by patch LayoutAnimation.js and remove optional chaining
or
You can add babel plugin proposal optional chaining at your babelrc

@RobbyWH @RobbyWH
This error caused by optional chaining, you can fix it by patch LayoutAnimation.js and remove optional chaining
or
You can add babel plugin proposal optional chaining at your babelrc

@madox2 @RobbyWH
This error caused by optional chaining, you can fix it by patch LayoutAnimation.js and remove optional chaining
or
You can add babel plugin proposal optional chaining at your babelrc

@madox2 @RobbyWH
This error caused by optional chaining, you can fix it by patch LayoutAnimation.js and remove optional chaining
or
You can add babel plugin proposal optional chaining at your babelrc

Thanks @renopp 🙌
It works for me after update to 0.64.0-rc.2

Thanks @renopp 🙌
It works for me after update to 0.64.0-rc.2

I'm having the same problem but I don't understand why do we need to that extra plugin manually. I thought that was added by RN itself here (since 0.56):
https://github.com/facebook/react-native/commit/aa6f394c4236e5a4998c3be8ed61ec1bab950775

Adding the plugin manually doesn't fix the problem for us. Is there a way to debug what plugins are being used by babel?

The only workaround we've found is to manually remove all optional chaining from LayoutAnimation.js.
To do so we've created a patch:
https://gist.github.com/javiercr/6359af65d8578568d4bc7ed159744464
It can be automatically applied using patch-package (store it on ./patches/react-native+0.64.patch).

This seems to stem from metro-react-native-babel-preset not adding properly the @babel/plugin-syntax-optional-chaining plugin.
I'll report the issue on metro's repo.
You may fix this by adding the @babel/plugin-syntax-optional-chaining in your dev dependencies and as a plugin in your .babelrc config instead of using patch-package. Although I'm not sure of the consequences if you're building for Hermes engine, since this specific transform seems to be disabled by metro-react-native-babel-preset when Hermes is enabled.

I had this issue after upgrading my project from 0.63.3 -> 0.64.1 and was able to fix it without any patches or extra plugins.
After deleting my yarn.lock and reinstalling, the error went away, suggesting a stale dependency somewhere. Obviously deleting yarn.lock isn't the actual solution, so I reinstated my yarn.lock, then manually ran yarn upgrade metro-react-native-babel-preset and saw a bunch of changes in the lockfile, even though I had manually specified "metro-react-native-babel-preset": "^0.64.0" before running yarn originally.  I then relaunched the packager and the app loaded without issue.
Possibly related to the semver "magic 0" case, where 0.x.x deps don't follow the same rules as others? https://dev.to/malykhinvi/semver-0-x-x-46e7

@computerjazz yarn upgrade metro-react-native-babel-preset resolved the issue for me. Thanks! 😄


add logo

add logo

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.v_lixin18 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #513 into develop will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #513      +/-   ##
===========================================
- Coverage    53.36%   53.35%   -0.01%
===========================================
  Files          254      254
  Lines        23535    23535
===========================================
- Hits         12559    12557       -2
- Misses        9500     9502       +2
  Partials      1476     1476

Impacted Files
Coverage Δ

bfe_http2/server.go
71.50% <0.00%> (-0.17%)
:arrow_down:

bfe_spdy/server_conn.go
78.53% <0.00%> (ø)

Continue to review full report at Codecov.

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


Work around for NonUniformResourceIndex with non integral types.

Ignores NonUniformResourceIndex for non uint/int types. Was tested with float, to make sure generic was taken over (say) coercing into integral, and that appeared to work as expected.
Should probably issue a warning when it is elided in this manner. Look to add in future PR.

I guess we can just mark the method as deprecated so it will automatically trigger a warning.


How to draw a 'net.svg' like you?

I really like the picture you draw about your net because it can make parameters Visual.I want to know how you do it?Thank you.

The plotting code is in the section network visualisation in https://github.com/davidcpage/cifar10-fast/blob/master/bag_of_tricks.ipynb


Push.Send(push_notification)

Hi,
Please add a command to send pus notification from within the app without having to call the API to make it easier to send messages.
This can be something like this:
var push_notification = new PushNotification(
     Owner = ..................,
     AppName = .....................,
     Message = ........................,
     Sound = ................................,
     SendOn = [...Shcedule.....],
     Parameters = {param1 = ....., param2 = ........},
     SendTo = {device1, device2, ......},
);

var result = Push.Send(push_notification);

Thanks,
Jassim

@jrahma just to make sure I understand the request, you're look for a device to device push API in the SDK? Can you describe the app requirement for this?  I'm curious about the app you're building if this is a requirement. Most developers send notifications from their app backend, not from a device application.

@jwargo no app in my hand with this requirement but it's just a thought in case it can be done and if it's helpful for others

@jrahma Thank you very much for your feedback on App Center Push. We announced yesterday in a blog post that we’re retiring the Push service later this year and recommending customers transition to Azure Notification Hubs instead. The good news is that the same team operates both App Center Push and Azure Notification Hubs, so all customer feedback and feature requests have been transferred to the Azure Notification Hubs roadmap.


~/.tabby-client/config.toml not working as expected

I have been playing with Tabby from Neovim, and up until today have been specifying my endpoint url in my vim config with a line like this: vim.g.tabby_server_url = "http://<IP_ADDRESS>:8088". I see the docs now say to put this in ~/.tabby-client/agent-config.toml in a [server] key like this:
[server]
endpoint = "http://<IP_ADDRESS>:8088"

But :Tabby status now says "cannot connect to server"
I'm not sure how to get much more feedback from tabby via logs or anything so I'll try to provide anything helpful with some instruction!
Thanks!

Hi - there's a mistake on 1.0.0 documentation (which has been fixed in 1.0.1). The correct path of config.toml should be ~/.tabby-client/agent/config.toml
https://github.com/TabbyML/vim-tabby/commit/5430bcc44144fa362787b6629d2c39016dad7a32#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5

Thanks for the quick response - my issue actually had a typo. I do have my config in ~/.tabby-client/agent/config.toml but :Tabby status still showing "cannot connect to server". I've upgraded Tabby to 0.3.1 via brew and it works if I keep my vim setting as originally stated...
I'm on Mac if that matters, but I'd figure this is specific to an editor, not the hardware

Could you confirm your vim extension version and try v1.0.1 if possible?
Otherwise, please follow https://tabby.tabbyml.com/docs/extensions/troubleshooting#cannot-connect-to-tabby-server and share the error log from agent

Ope you got me - had to update the client!


External nested refs aren't being resolved

This test is failing.

This is currently being tracked in https://github.com/whitlockjc/json-refs/issues/80  The plan is to update the json-refs version in sway when this is fixed.

@whitlockjc I think this is a different issue, since json-refs resolves it fine:
$ json-refs resolve test/browser/documents/2.0/nested-refs/b.yaml
{
  "swagger": "2.0",
  "info": {
    "title": "test",
    "version": "0.0.0"
  },
  "paths": {},
  "definitions": {
    "x": {
      "type": "object",
      "properties": {
        "children": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              }
            }
          }
        }
      }
    }
  }
}
$ json-refs --version
2.1.6

Yes<EMAIL_ADDRESS>resolves it fine but swagger-tools isn't using that version.  That release fixes the issue but has a huge performance issue that I'm working on now.  As soon as<EMAIL_ADDRESS>comes out, or whatever its next version is, I'll update swagger-tools accordingly.

@whitlockjc thanks, and I'm sorry to bother you again: I just tried with<EMAIL_ADDRESS>and it resolved it fine, just like 2.1.6 did. So I think that maybe this issue is unrelated to json-refs. Can you confirm?

json-refs is the resolving library for sway and swagger-tools.  It is the only thing that is used for resolving references.  What version of json-refs is installed in your swagger-tools?  npm ls | grep swagger-tools

@whitlockjc I'm just using the json-refs git repo:
$ git checkout v2.1.5
HEAD is now at 9a84142... v2.1.5
$ npm install
(...)
$ ./bin/json-refs --version
2.1.5
$ ./bin/json-refs resolve ../sway/test/browser/documents/2.0/nested-refs/b.yaml
{
  "swagger": "2.0",
  "info": {
    "title": "test",
    "version": "0.0.0"
  },
  "paths": {},
  "definitions": {
    "x": {
      "type": "object",
      "properties": {
        "children": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              }
            }
          }
        }
      }
    }
  }
}

What I'm trying to say is that you reported an error with sway that has since been fixed in json-refs but that version of json-refs is not the one installed into your sway (likely).  So to figure out if I'm right, wherever your sway-based project is, run this: npm ls | grep json-refs and tell me the version.  (Sorry about the previous example referencing swagger-tools, that likely muddied the waters.)

I'm sorry @whitlockjc: the version of json-refs used in my project that depends on sway is 2.1.6, and it's failing there. Now that I've read https://github.com/whitlockjc/json-refs/issues/80, I understand that the issue happens when using "-I relative", and that makes sense. I agree with the solution proposed here: https://github.com/whitlockjc/json-refs/issues/80#issuecomment-188922814
We can continue the discussion over there.


Attempting to simply return an array in Express but always returning [] empty

Hi there, I am attempting to return "checkins_each" but it is returning a blank list [] every attempt at displaying it.  I think the checkins.list() is running in a new thread or something same with checkins.get() - is there a proper way to return checkins_each - it should have a few records in it?
// return data
    var checkins = nano.use(settings.COUCHDB_PREFIX+'checkins');
    var checkins_each = [];
    checkins.list(function(err, body) {
        if (!err) {
            console.log('hi proximity loop')
            body.rows.forEach(function(doc) {
                console.log(doc.id);
                checkins.get(doc.id, function(err,jsondoc) {
                    console.log(JSON.stringify(jsondoc));
                    if (jsondoc.profile_id != profile_id) {
                        console.log('appending checkin');
                        checkins_each.push(jsondoc);
                    }

                });
            });
            res.send({status: 'proximity', checkins: checkins_each});
        } else {
            console.log("error", err);
            res.send({status: 'fail', error: err});

        }

Hey @treeternity, because you have an async call inside your forEach you are getting only the original array, it is populated after the body is already sent.
If you need more help, I would suggest posting on stack overflow, as it is a better forum for getting these kind of questions answers.  There are alot more people there to help, as this is more geared toward express bugs and development.  Good luck!


Application doesn't display properly when running on a Mac

Application initially appeared to be entirely non-functional, opening with a black canvas.
I was able to get the application to function by dragging the corner to resize, then toggling between a normal window and fullscreen a couple of times. I then had an editor that was basically usable - I was able to write and execute code, Intellisense was working - but there were still places where the window wasn't being rendered quite right - see attached screenshot for an example.
MacOS Mojave 10.14.3 (Latest at time of issue creation)
.NET Core 2.2.105

places where the window wasn't being rendered quite right

Could you point me to those? Note that the cross-platform version is an Avalonia-based rewrite of the entire UI, so it's not quite as polished as the WPF version :)

See https://github.com/AvaloniaUI/Avalonia/issues/2363
Seems like it was fixed but not yet published. We'll have to wait for a newer version

Hello @aelij - was that bugfix released with v0.8.2
https://github.com/AvaloniaUI/Avalonia/releases/tag/0.8.2
It would be great if you could update Roslynpad.

Still active, I just decided to try it out today.

This should be fixed in the latest Avalonia


App closed unfortunately in Android 4

Hi,
i have tried to use your plugin on android 4 device but it broke the app with message 'App closed unfortunately'. This is a bug.
And in other device android, your plugin doesn't find my bluetooh printer.

@lucav90 Please send me the stack trace if you have one.
Re the bluetooh printer - if the plugin does not list the printer, then the system cannot find them.

Please re-open if needed.

Thanks katzer, but for me, not work.
Android 5.1.1
'App closed unfortunately'


Stackstorm action runner does not return / complete - hangs and process is defunct

When running an action that makes an internal HTTP call (from inside python with requests) that returns a lot of data. The called service is completing and returning HTTP payload over the network (we wiresharked). The action process (we think ?) (after about 15 seconds after the HTTP server returns its data) goes to "defunct" state. The parent process of the action process is the main action runner process.
The core.http action works for same call ; we cannot use it because it will publish the output to the workflow and that is too much data to be in the workflow context due to Mongo db driver/performance issues.
st2 3.4.1, on Python 3.6.8
Running in Docker & Kubernetes
OS is (cat/etc/os-release):
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"

We are having this same issue.

Related issue?  https://github.com/StackStorm/st2/pull/5220


 I took a look in the code and noticed the following:
Graphics.prototype._calculateBounds = function _calculateBounds() {
        // this.boundsDirty is 6188 & this.dirty is 6189, statement is true soo continues
        if (this.boundsDirty !== this.dirty) {
            this.boundsDirty = this.dirty;
            //this.boundsDirty = 6189, the boundsDirty gets set to this.dirty. So both are the same now.
            this.updateLocalBounds();

            this.dirty++;
            // this.dirty = 6190, but we still make the both values different after this line of code. A bug?
            this.cachedSpriteDirty = true;
        }
        // In the next frame the same thing happens, end again, end again. Endlessly.

        var lb = this._localBounds;

        this._bounds.addFrame(this.transform, lb.minX, lb.minY, lb.maxX, lb.maxY);
    };

Yep, looks like a serious bug.


Bug 1776665: Ignore most kube system events

Corrects issues that could arise from 4.1 clusters being upgraded through 4.5

Reverts #470
Ignores events from the kube-system namespace except for the cluster-config-v1 configmap

/cherrypick release-4.4

/cherrypick release-4.3

/assign @adambkaplan @dmage @bparees

/lgtm

/retest

/retest

Looks like I'll be creating manual pull requests for 4.3 & 4.4 :-1:


chore: Remove generated Markdown title for PNGs

Used a regex \.png\s+"\w*"\) to find/replace the placeholder title values. Since these are the same as the image file name, they don't add value

@nschonni : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@corob-msft - Would you review the proposed changes? Thanks.


Unable to install any language servers

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
ESLint is installed on startup, then when browsing different files (html, typescript, svelte) these begin to attempt to download but get stuck. These folders in ~/LibraryApplication Support/Zed/languages are empty.
Environment
System Software Overview:
  System Version: macOS 12.6.7 (21G651)
  Kernel Version: Darwin 21.6.0
  Boot Volume: Macintosh HD

Hardware:
  Model Name: Mac Studio
  Chip: Apple M1 Max
  Total Number of Cores: 10 (8 performance and 2 efficiency)
  Memory: 32 GB

If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
2023-08-17T04:49:37 [INFO] Node runtime install_if_needed
2023-08-17T04:49:37 [INFO] add connection to peer
2023-08-17T04:49:37 [INFO] waiting for server hello
2023-08-17T04:49:37 [INFO] got server hello
2023-08-17T04:49:37 [INFO] set status to connected (connection id: ConnectionId { owner_id: 0, id: 0 }, peer id: PeerId { owner_id: 197, id: 677823 })
2023-08-17T04:49:37 [INFO] set status on client 0: Connected { peer_id: PeerId { owner_id: 197, id: 677823 }, connection_id: ConnectionId { owner_id: 0, id: 0 } }
2023-08-17T04:49:38 [INFO] Node runtime install_if_needed
2023-08-17T04:49:39 [INFO] Node runtime install_if_needed
2023-08-17T04:49:39 [ERROR] invalid LSP message header ""
2023-08-17T04:49:39 [ERROR] Broken pipe (os error 32)
2023-08-17T04:49:39 [ERROR] server shut down
2023-08-17T04:49:39 [ERROR] failed to start language server "svelte-language-server": oneshot canceled
2023-08-17T04:49:39 [ERROR] crates/zed/src/languages/svelte.rs:124: no cached binary
2023-08-17T04:49:39 [INFO] About to spawn test binary
2023-08-17T04:49:39 [WARN] test binary failed to launch
2023-08-17T04:49:39 [WARN] test binary check failed
2023-08-17T04:49:39 [INFO] beginning to reinstall server
2023-08-17T04:49:39 [INFO] deleting server container

Hey @jyezy, can you let me know what version of Zed and what release channel (Preview / Stable).  Thanks.

Apologies, I read the environment stuff wrong.
I was able to produce this error on Zed 0.99.1, the latest preview (0.100.0), and an older version.
Strangely enough, it occurred on both my Desktop and Laptop, both M1 chips, it’s led me to believe it’s external factors (possibly internet missing a download which causes issues, or my general dev environment).

I got a similar error when  I tried to open typescript or json files. (also on m1 mac)
2023-08-20T13:30:39 [ERROR] crates/zed/src/languages/json.rs:175: no cached binary
2023-08-20T13:30:39 [INFO] About to spawn test binary
2023-08-20T13:30:39 [WARN] test binary failed to launch
2023-08-20T13:30:39 [WARN] test binary check failed
2023-08-20T13:30:39 [INFO] beginning to reinstall server
2023-08-20T13:30:39 [INFO] deleting server container
2023-08-20T13:30:39 [INFO] starting language server "json-language-server", path: "/Users/st2r/Projects/new-st2r-web", id: 1
2023-08-20T13:30:39 [INFO] Node runtime install_if_needed
2023-08-20T13:30:41 [INFO] Node runtime install_if_needed
2023-08-20T13:30:42 [INFO] Node runtime install_if_needed
2023-08-20T13:30:42 [ERROR] invalid LSP message header ""
2023-08-20T13:30:42 [ERROR] Broken pipe (os error 32)
2023-08-20T13:30:42 [ERROR] server shut down
2023-08-20T13:30:42 [ERROR] failed to start language server "json-language-server": oneshot canceled
2023-08-20T13:30:42 [ERROR] crates/zed/src/languages/json.rs:175: no cached binary

I just installed Zed (0.103.1) and I'm getting the same:
Language server error: TypeScript

failed to launch npm subcommand install subcommand

Jumping in as well. Also on an M1 Mac and getting the same with 0.103.1.

Same happened to me as well.
Machine: M1 Mac Mini (Sonoma 14.1)
Zed v0.108.2

This can be done by adding "features": {"copilot": false } to your settings.json.

I tried. still doesn't work.

Have you tried this approach?

Have you tried this approach?

This worked for me. Thanks @frenchbread


FIFO Capital Gains

So, I have a simple ledger:
@defaccount De Assets:Investments:UTrade           USD
@defaccount De Assets:Investments:UTrade:AAPL      AAPL
@defaccount De Expenses:Financial:Commissions
@defaccount De Assets:Cash                         USD
@defaccount Cr Income:Investments:Capital-Gains

2008-01-01 * Transferring money to brokerage account for better investment.
  Assets:Cash                        -10000.00 USD
  Assets:Investments:UTrade

2008-01-08 * Buy AAPL
  Assets:Investments:UTrade:AAPL    30 AAPL @ 100 USD
  Expenses:Financial:Commissions    9.95 USD
  Assets:Investments:UTrade

2008-01-08 * Buy More AAPL
  Assets:Investments:UTrade:AAPL    50 AAPL @ 120 USD
  Expenses:Financial:Commissions    9.95 USD
  Assets:Investments:UTrade

2008-02-28 * Sell off AAPL
  Assets:Investments:UTrade:AAPL    -40 AAPL @ 140 USD
  Expenses:Financial:Commissions               9.95 USD
  Assets:Investments:UTrade
  (Income:Investments:Capital-Gains)           BOOK AAPL

I expect the capital gain to be $1400 (30 shares sold at $40 profit each, 10 shares sold at a $20 profit each).  Instead, I get this:
Assets                                  : 40.0 AAPL, -3429.85 USD
Assets:Cash                             : -10000.00 USD
Assets:Investments                      : 40.0 AAPL, 6570.15 USD
Assets:Investments:UTrade               : 40.0 AAPL, 6570.15 USD
Assets:Investments:UTrade:AAPL          : 40.0 AAPL
Equity                                  :
Expenses                                : 29.85 USD
Expenses:Financial                      : 29.85 USD
Expenses:Financial:Commissions          : 29.85 USD
Income                                  : -1600.0 USD
Income:Investments                      : -1600.0 USD
Income:Investments:Capital-Gains        : -1600.0 USD
Liabilities                             :

So, it seems like the gain is calculated incorrectly.  Please advise.

Yes. It is wrong. Sorry I just noticed this post from 2013. Shame on me!

wow. this took 9 years but it is fixed now.

Fixed now


Cannot uninstall the plugin

Hello, I have a problem with Essentials Warp Gui plugin. I didnt read that it required Essentials when installing the plugin but it seemed to work without it (I could create a warp and i could also open the gui) so i wanted to edit the plugin but couldnt seem to find the plugin files (they didnt generate in plugins folder). So i decided to use a different plugin for warps, but after i removed the WarpGui.jar the command remained on the server and i could still create warps/open gui menu. I dont know how to fix this. In the console it doesnt show that the plugin is starting but i can still use it. Also i did uninstall the jar correctly and with the server off, restarted it a couple of times too. I will send the console log too.
Console Log: https://mcpaste.io/5c58285e13d7a336
Version: Mohist 1.20.1

Make sure to delete the correct jar file. PlugmanX may help you finding the name the file has within the plugins folder.

I dont think so and iam 100% sure i deleted the plugin correctly. Iam sending my plugin list.

This is what i get when i do /warps


Support reading properties from toml configurations via toml configs

Released ktoml and added it as a dependency to save


IGNITE-16453 Try to optimize IgniteLongList

https://issues.apache.org/jira/browse/IGNITE-16453

@ibessonov @sashapolo Guys please look again.


Feature/alterar lib mongodb

Codecov Report

Merging #43 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #43   +/-   ##
========================================
  Coverage    96.19%   96.19%
========================================
  Files            9        9
  Lines          342      342
========================================
  Hits           329      329
  Misses          13       13

Continue to review full report at Codecov.

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


reth-rpc-eth-types still brings boa from revm-inspectors even with the js-tracer disabled by default.

Describe the feature
I have a PR to update a big codebase to<EMAIL_ADDRESS>which includes the latest js-tracer optional fixes to try to remove the boa bloat in Cargo.lock since we don't want to build a whole JS interpreter every time we do cargo {build,check,test}.
Still somehow boa still shows up in the cargo tree. Here's the important parts:
├── reth-rpc-api v1.1.3 (https://github.com/paradigmxyz/reth.git?rev=v1.1.3#d97449da)
│   └── reth-rpc-eth-api v1.1.3 (https://github.com/paradigmxyz/reth.git?rev=v1.1.3#d97449da)
│       ├── reth-node-api v1.1.3 (https://github.com/paradigmxyz/reth.git?rev=v1.1.3#d97449da)
│       │   ├── reth-node-core v1.1.3 (https://github.com/paradigmxyz/reth.git?rev=v1.1.3#d97449da)
│       │   │   ├── reth-rpc-eth-types v1.1.3 (https://github.com/paradigmxyz/reth.git?rev=v1.1.3#d97449da)
│       │   │   │   ├── revm-inspectors v0.12.1
│       │   │   │   │   ├── boa_engine v0.19.1
│       │   │   │   │   ├── boa_gc v0.19.1 (*)

Now I am trying to find how did boa get into here.
It wasn't supposed to happen since:

git grep 'js-tracer' shows nothing
reth-rpc-api depends on reth-rpc-eth-api without the js-tracer feature

Which in turn calls reth-node-api which does not depend on revm-inspectors
Then calls reth-node-core that again does not depend on revm-inspectors.
Then calls reth-rpc-eth-types which also has feature-gated the js-tracer feature and not enabling by default

revm-inspectors has feature-gated boa dependency and not enabled by default for a while

Now I don't know if I need to change something in my codebase. Or if we need somehow to force reth-rpc-eth-types to not enable js-tracer feature in revm-inspectors by default.
Additional context
No response

could you please link or paste your Cargo.toml file with the git deps?


v2.3.1 (and up?) not connecting to hue v1 bridge

currently home assistant is using v2.3.1 of the aiohue library. When it used v2.1.0 all was working well with my v1 hue bridge. After the aiohue library is updated to v2.3.1 it's not connection anymore. It might have to do because the v1 bridge uses non https for the communication, but I am not sure of this. I manually rolled back to v2.1.0 for now. I tried 2.5.0 as well, but it doesn't connect either...

Do you have a log / stack trace with errors?
How do you use aiohue?

I tried to manually add my virtual lights configured in Node-Red, which should use the v1 API, to Home Assistant. He tries to get a missing key bridgeid from the root JSON response with a 12 characters length (discovery.py).  Verified with my real bridge and it returns this bridgeid key. Verified aiohue v2.1.0, the bridgeid came from the config.bridgeid.
File "/usr/src/homeassistant/homeassistant/components/hue/config_flow.py", line 71, in _get_bridge
    bridge = await discover_bridge(
  File "/usr/local/lib/python3.9/site-packages/aiohue/discovery.py", line 35, in discover_bridge
    bridge_id = await is_hue_bridge(host, websession)
  File "/usr/local/lib/python3.9/site-packages/aiohue/discovery.py", line 82, in is_hue_bridge
    return normalize_bridge_id(data["bridgeid"])
KeyError: 'bridgeid'

So that's a bug with Node Red not following the spec.

Maybe I wrong but I don't see in the v1 of the specs a bridgeid returned by the api endpoint /api/config. I verified on the developer website, and the JSON returned by Node Red is almost the same: https://developers.meethue.com/develop/hue-api/7-configuration-api/ (7.5.3 Sample Response).
In the mentioned v2.1.0, the bridge id came from the id in the response of the method  discover_nupnp() and the config was created from the config object. I think the bridge id came from the mac address on v1.
https://github.com/home-assistant-libs/aiohue/blob/2654b8bc00a87f403cb8b5f8c79684ff89ee0937/aiohue/discovery.py#L4-L13
This means that the method is_hue_bridge(host: str, websession: ClientSession | None = None) in discovery.py should only works with the v2 of the api and crash with v1 because the key bridgeid does not exists.
https://github.com/home-assistant-libs/aiohue/blob/6e8654af4dd1a61998f467e14fbb6afab576c7fb/aiohue/discovery.py#L67-L85

bridgeid is in fact part of the config object.
https://developers.meethue.com/develop/hue-api/7-configuration-api/#get-configuration
Can you explain what is the issue ?

Finally for me there is no issue, I understand where the problem came from. @kiss81 is your problem related to a physical Hue bridge v1 ?
I explain...
The module get the config from the endpoint: /api/config and should returns a response like this:
{
    "name": "Philips hue",
    "apiversion": "1.10.0",
    "swversion": "01028090",
    "mac": "00:17:88:20:01:0a",
    "bridgeid": "001788FFFE20010A",
    "replacesbridgeid": null,
    "factorynew": false,
    "modelid": "BSB001"
}

And not (like the Node Red module do):
{
   "lights": {},
   "groups": {},
   "config": {
       [...]
        "bridgeid": "001788FFFE20010A",
        "modelid": "BSB001"
   }
}

who is the full state from the endpoint /api/<username>
Sorry for the waste of time. After adding manually the missing keys Home Assistant added the virtual hub.
I just have a question, it is wanted  that there is no test on the existence of the key bridgeid and the log returns a full error traceback? On the one hand without this I will not catch where the problem was...

I think we can leave this one closed. The purpose of the aiohue library is connecting to REAL Hue bridges (V1 or V2). We will not add workarounds for virtual bridges. The virtual bridge should instead confirm to the api specs if it want to stay/be compliant.


test(connlib): handle overlapping DNS resources

The root cause of #5259 turned out to be an issue with overlapping IPs for DNS resources. In particular, it is triggered by the following sequence of events:

User sends an AAAA query for DNS resource foo.example.com.
We connect and return a proxy IP.
Internally, we also already assigned a proxy IP for all IPv4 addresses but the user doesn't know that.
User sends an A query for DNS resource bar.example.com
bar.example.com happens to resolve to the same IPv4 as foo.example.com. As a result, we invalidate the previously created but now invalid A entry for foo.example.com.
User sends an A query for foo.example.com. We now no longer have any records for that domain at all and return an empty response, i.e. no records.

User sends an AAAA query for DNS resource foo.example.com.

We connect and return a proxy IP.

Internally, we also already assigned a proxy IP for all IPv4 addresses but the user doesn't know that.

User sends an A query for DNS resource bar.example.com

bar.example.com happens to resolve to the same IPv4 as foo.example.com. As a result, we invalidate the previously created but now invalid A entry for foo.example.com.

User sends an A query for foo.example.com. We now no longer have any records for that domain at all and return an empty response, i.e. no records.

I think what is confusing about this behaviour is that, from the client's perspective, it never asked for an A record of foo.example.com before, yet the A record for bar.example.com takes priority.

User sends an AAAA query for DNS resource foo.example.com.
We connect and return a proxy IP.
Internally, we also already assigned a proxy IP for all IPv4 addresses but the user doesn't know that.
User sends an A query for DNS resource bar.example.com
bar.example.com happens to resolve to the same IPv4 as foo.example.com. As a result, we invalidate the previously created but now invalid A entry for foo.example.com.
User sends an A query for foo.example.com. We now no longer have any records for that domain at all and return an empty response, i.e. no records.

I think what is confusing about this behaviour is that, from the client's perspective, it never asked for an A record of foo.example.com before, yet the A record for bar.example.com takes priority.

I haven't tested this but I think there is additional, odd behaviour:
The invalidation of proxy IPs always happens, even if we've already handed those IPs out to the user. This means that, a AAAA query to a new resource may replace already returned A records to a completely different resource, simply because the new resource happens to resolve to the same IPv4 addresses. As a result, I believe that any traffic from the existing IP will now suddenly be routed to the new resource!

User sends an AAAA query for DNS resource foo.example.com.
We connect and return a proxy IP.
Internally, we also already assigned a proxy IP for all IPv4 addresses but the user doesn't know that.
User sends an A query for DNS resource bar.example.com
bar.example.com happens to resolve to the same IPv4 as foo.example.com. As a result, we invalidate the previously created but now invalid A entry for foo.example.com.
User sends an A query for foo.example.com. We now no longer have any records for that domain at all and return an empty response, i.e. no records.

I think what is confusing about this behaviour is that, from the client's perspective, it never asked for an A record of foo.example.com before, yet the A record for bar.example.com takes priority.

I haven't tested this but I think there is additional, odd behaviour:
The invalidation of proxy IPs always happens, even if we've already handed those IPs out to the user. This means that, a AAAA query to a new resource may replace already returned A records to a completely different resource, simply because the new resource happens to resolve to the same IPv4 addresses. As a result, I believe that any traffic from the existing IP will now suddenly be routed to the new resource!
Initially, one might think that this is okay because after all, both domains resolve to the same IP. However, the new resource might have a different access policy and might be part of a different site and IPs across sites may not be unique or point to the same physical server.

This isn't caught in the tests yet because we currently only ever connect to the same gateway but I am planning to add multiple gateways to the test soon.

What's the reason that an AAAA query allocates IPv4 proxy IPs in the first place? Is that if the user sends an AAAA query but the upstream DNS replies with both IPv4 and IPv6?

This happens regardless of the combination of A/AAAA queries right?

Initially, one might think that this is okay because after all, both domains resolve to the same IP. However, the new resource might have a different access policy and might be part of a different site and IPs across sites may not be unique or point to the same physical server.

The proxy IPs are based both on the real ip and the peer, so another peer could never replace the other one.
But it's very important that we lose the record because the ips coincide! We can just keep a map of resource -> ip instead of the other way around and then for PTR queries we just decide on a record. PTR queries aren't designed to be very reliable anyways.
Then the other problem is that we need to get the resource_id for the destination because we have to pick the peer based on that, but if both dns resources have the same ip both have the same peer id, so we could pick any of the resources ids.
This fix should be relatively easy to implement quickly so we have it working on main instead of waiting for #5049
(edited)

Or maybe even better keep a HashMap<IpAddr, HashSet<DnsResource>>, keep in mind this is a temporary solution until #5049

Thank you for the review @ReactorScram ! I think most of my code is unfortunately obsolete with @conectado 's fix in https://github.com/firezone/firezone/pull/5272.
Will close this in favor of that PR.


Store in a zipfile

I have and idea for Enhancement : store objects in a zip, to reduce size on phone

Any particular motivation to reduce files that are just a couple of KB? Is there really much of a gain? If you have a particular desire to have as small a footprint on the filesystem as possible, you could write a custom Convertor to take care of that.

Well in my case I have a lot of MB

I've been thinking about re-implementing Convertors for a while now, as they're pretty inflexible in their current state. (I'd really like to support Moshi).
In making them more flexible, that would allow for easy implementation of Convertors that can read and write from zipped streams. However, I'm not convinced this should be the default behaviour of any particular convertor. It's certainly something that could be provided in example code, but its requirement is niche enough that I don't want to include it in the main library.