Namespace error on Package Manager Import

like in Issue 25
I am getting namespace errors on import through UPM.

Running Unity 22.3.9f1 with JigglePhysics 7.0.2

Hmmm. I'm not sure how that's possible. 84b7dc is the correct hash-- I copied your setup and it works on my system (though I used 2022.3.10f1).
What happens if you install https://github.com/naelstrof/UnityJigglePhysics.git#v7.0.2 rather than the upm branch?

I realize you're importing through UPM, I haven't actually tested that installation in a long time. I usually just put the git URL I need within the unity package manager. Let me know if that has a different result, I haven't changed how I publish upm content, but their package manager could have a bug!

What happens if you install https://github.com/naelstrof/UnityJigglePhysics.git#v7.0.2 rather than the upm branch?

same issue
https://github.com/naelstrof/UnityJigglePhysics/assets/54823358/6dd16d05-e2d5-4306-8a33-802ed22653e8

I usually just put the git URL I need within the unity package manager.
I'm sorry im not sure any other way of importing through UPM...  Is that not how you normally do it?

You installed it correctly. I still have no idea why you're getting those errors. It's saying JiggleRigBuilder is missing. It's right there. It's in the same folder under the same namespace. My only thought is maybe they're getting compiled into separate dlls? Though the assembly definition is also just right there.
It doesn't help that it works fine on my system.
Can you verify that in your Packages/Jiggle Physics/Scripts that the two files belong to the same dll?
https://github.com/naelstrof/UnityJigglePhysics/assets/1131571/d8745684-78db-4658-8b99-e53cea84954d

OH. YOURE. YOU'RE NOT USING IT FOR GAME DEV

You don't need to install jiggle physics directly, you already have it installed with the model sdk!!!

The jiggle physics is embedded directly into the sdk, as that's how it gets pack-ratted into Lethal Company without introducing extra dependencies. The original jiggle physics is not compatible with the packratted version. Just uninstall it! (You'll still have jiggle rig builders available!)

OML it worked im crying
tysm <3


Medians missing with pip.ado

Hi all,
I'm in the process of preparing our annual data submission for SDG 10.2.1 (share living below half the median) and noticed that there are a few missing medians returned through the pip.ado
pip, country(all) year(all)
keep if missing(median)
Most of these were also missing in povcalnet.ado. In noticed that Argentina has missing medians now, though, which it didn't before. It would be nice not to have any missings, but perhaps this is not the greatest problem on your to-do list.

Hi @randrescastaneda
Could there be a reason why median are missing for chn, gnb, gtm, guy, idn, ind, nam, sle, and slv at national level estimates? I noticed that the median estimates are calculated for rural/urban level for the specified years.
Tefera

But how can we calculate poverty rates for the countries where the estimates of the regressions are invalid?

Fair question. Following the old practice of Povcalnet, PIP selects distributional stats and poverty stats with different but complementary algorithms. In the case of SLV 1989, for instance, the algorithm says that neither of the Lorenz parametrizations is valid for dist stats. Yet, only the Lorenz Beta is used for poverty Stats because it meets normality, whereas the quadratic does not meet normality. This is why we have estimates for poverty but not for distribution. It is an old practice that I am not sure if it should be revisited.
The functions of the algorithm can be found in the gd_select_lorenz.R file of the {wbpip} package. In production, we use the function prod_gd_select_lorenz, which uses the function retrieve_poverty(). If you want, we could talk about it in detail over Teams.
Feel free to close the issue if you think my answer is enough to leave it at this point.
Best,


Improve JUnitXmlTestRunResultProcessor's URL generation

The processor that generates JUnit-compatible XML reports attempts to generate an URL to the specifications that are under test.
Input used for these URLs should be properly escaped.
Links should be generated not only for XEP-specifications, but also for RFCs.
If a link can't be created, prevent the report generation from crashing. Instead, just generate a report without a link.
fixes #21

They prove the method works when its been through that normalisation method, but is that true in the normal execution?

You might be right. I assumed it was, but on a closer look, I believe that Smack only normalises when it applies the enabled/disabled-specification configuration.
I'm thinking that it would be kind of nice if Smack's output would actually contain normalized references, as that would potentially prevent a lot of follow-up issues. I'll see if I can add that to Smack.


[action] add :binary_files to slather action to handle multiple files

Fixes #14747
Description

:binary_file used to except any type (which is not great for doc and for Fastlane.swift)

A previous PR fixed this but introduced a regression (which was undocumented) but allowing only a String

Introduced both a new :binary_files and binary_basenames which accepts arrays
Put a deprecation notice in binary_basename when an Array is passed in to start migrating to :binary_basenames

Closing because going to allow for configuration options to allow for multiple types


Use Remote URL without use of File downloading?

Is it possible to use the remote URL without downloading and saving to external?
So instead of downloading and saving the file into storage, instead hold that response html content and have it in memory. Using that memory buffer, put it into the PDFViewPager for loading.

Hello,
the library can only read PDF files that are located somewhere in your internal storage or SD card. Reading from another sources is not its purpose, sorry


Connection is closed. with default settings

Hi,
We are using ioredis in cluster mode with the default settings (Not overriding anything).
I went over the code and the only time where a Connection is closed. error is returned is when this.status === end, which is only being set here:
https://github.com/luin/ioredis/blob/master/lib/cluster.js#L146
But this line should never be executed because this will always return true: https://github.com/luin/ioredis/blob/master/lib/cluster.js#L138
So how come we are receiving these errors:
Error: Connection is closed.\n    at Cluster.sendCommand (/xxx/ioredis/lib/cluster.js:404:20

That's strange. Does enabling debug info DEBUG=ioredis:* node yourapp help?

Unfortunately its not consistent at all, it happened on 1 server out of 50, and once we restarted it it was working again.
I think it somehow got into a bad state that caused him to stay in a Connection Closed mode.

I'm closing this issue since ioredis v2 is released and there're many code changed. Reopen it if the error still exists.


No longer active?

Is this project dead? there hasn't been any updates in a long while?

Yes, it is :) See forks )

Project not dead, because i don't have time to support project now. Make PR if you can. Sorry ;(


NAV-RELPOSNED

Hi,
Firstly, I want to say thank you for making this libary. It is easy to understand the code but I have problem with reading data.
I would like to get messages from NAV-RELPOSNED but in the libary there are no code for that.
I tried to code it for myself but I faild and you seem a much better programmer than me so please tell me how is it possible te get the position from that. I would be really helpfull for me and also for my half-year homework.
I send you what i have programmed yet but it is not that much :D
I am waiting for your reply and thank you.
import serial
import math
import ubx
x = ubx.UbxStream(serial.Serial(port='COM6', baudrate=19200, timeout=1))
x.enable_message(0x01, 0x3c)
navigation_position = x.read()
print(navigation_position.lat)
#print(navigation_position.clsID)

Hi!
Thank you for the input ^_^  The next couple of days I'm a bit busy, but I'll try to squeeze support for that specific message in asap.

Thank you for your answer. It would be an enormous help and would make my project far easier.

I just pushed a new branch with the defined message in there. Unfortunately I don't have a device that supports that specific message (only with High Precision GNSS products) so I couldn't test it; could you verify that it works?
Thanks in advance :)

Thank you I will test it on monday. I hope it will work :)

I don't know why but it is doesn't work. I am using pyCharm.
This is the message that I get when I run the code
Transmitting
06 00
Transmitting
Traceback (most recent call last):
06 01
File "C:/Users/user/PycharmProjects/RTK/GPS.py", line 12, in
print(navigation_position.relPosN)
AttributeError: 'UbxMessage' object has no attribute 'relPosN'
Receiving
05 01
Acknowledged. CLS:0x6 ID:0x0
Receiving
05 01
Process finished with exit code 1

Hmm.. Could you share the code / what device are you exactly using? Then I have more to go on :)

Of course! I am using C94 M8P modul in moving baseline and the code:
import serial
import ubx2
x = ubx2.UbxStream(serial.Serial(port='COM8', baudrate=19200, timeout=1))
x.enable_message(1, 0x3c)
navigation_position = x.read()
print(navigation_position.relPosN)
#print(navigation_position.clsID)
but I changed the Class and Message ID and also the same result. So if I try to do this:
x = ubx2.UbxStream(serial.Serial(port='COM8', baudrate=19200, timeout=1))
x.enable_message(1, 2)
navigation_position = x.read()
print(navigation_position.lat)
#print(navigation_position.clsID)
I get the same error.

There's two issues:

When you read a message you should check for the ubx_class and ubx_id to make sure the message you read is indeed the one you're interested in. Not all messages have the same variables.
Secondly I forgot to say that I pass in an integer to the enable_message() function; I guess I should put a nicer check in those functions and do a possible conversion. But for now could you try: python x.enable_message(1, 60)?

Hmm sorry; seems that you're already sort of checking for the msgID..
I'm starting to think it might also be a race condition; could you add something like this:
import time
import serial
import ubx2

x = ubx2.UbxStream(serial.Serial(port='COM8', baudrate=19200, timeout=1))
time.sleep(5) # give the UbxStream object a second to instatiate itself; this involves sending/
x.enable_message(1, 60)
navigation_position = x.read()
print(navigation_position.relPosN)

Yes. I spent a lot of hours today with trying to solve the problem. I don’t remember correctly but maybe I tried the x.enable_message(1,60) and it didn’t work.
Should I edit the main script? Beacuse ‘3c’ is written to _ubx_NAV_RELPOSNED or not? There is another message type marked with ‘60’ something(__ubx_aopstatus)

Hi :) 3c in hex is 60 in decimal so we're still talking about the same message. I will try to do a conversion there as well; but for now try it with the 60.
The problem comes with the UbxStream instantization which sets the baudrate but doesn't check for the confirm message. Then you immediately enable a message and waits for the confirmation, which it gets because the first confirmation message to set the baudrate just arrived. Whatever you read then is probably either a ACK or NACK message which doesn't have either lat or relPosN attribute.
Or that's my working theory atm :p please add that sleep there to see if I'm not entirely incorrect. I'll add some of these things to the code to make it work better for future users as well. Thanks again for putting in the time btw :)

Alright. I am going to try tommorow what you said. I am so excited about it. I hope we solve it finally.:)

Unfortunately it didn't work. I think the problem is that the messages I get through serial port contains a lot of information or some kind of data which is useless for me and I can't filter them so when I try to read these I get an error. I send you some of my attempts to make this work and I send the result also.
                                                                      FIRST:

CODE:
import serial
import time
import ubx2

x = ubx2.UbxStream(serial.Serial(port='COM9', baudrate=19200, timeout=1))
time.sleep(5) # give the UbxStream object a second to instatiate itself; this involves sending a cfg message to setup the baudrate
x.enable_message(1, 60)
navigation_position = x.read()
print(navigation_position.relPosN)

ANSWER:
Transmitting
06 00
Transmitting
06 01
Receiving
05 01
Acknowledged. CLS:0x6 ID:0x0
Receiving
27 00
Traceback (most recent call last):
print(navigation_position.relPosN)
AttributeError: 'UbxMessage' object has no attribute 'relPosN'
                                                                      SECOND:`

CODE:
import serial
import time
import ubx2
x = ubx2.UbxStream(serial.Serial(port='COM9', baudrate=19200, timeout=1))
time.sleep(5) # give the UbxStream object a second to instatiate itself; this involves sending a cfg message to setup the baudrate
x.enable_message(1, 60)
navigation_position = x.read(reset=False)
print(navigation_position.relPosN)

ANSWER:
Transmitting
06 00
Transmitting
06 01
Receiving
05 01
Acknowledged. CLS:0x6 ID:0x0
Receiving
04 02
Traceback (most recent call last):
print(navigation_position.relPosN)
AttributeError: 'UbxMessage' object has no attribute 'relPosN'
                                                                      THIRD:

CODE:
import serial
import time
import ubx2
x = ubx2.UbxStream(serial.Serial(port='COM9', baudrate=19200, timeout=1))
time.sleep(5) # give the UbxStream object a second to instatiate itself; this involves sending a cfg message to setup the baudrate
x.disable_NMEA()
x.enable_message(1, 60)
navigation_position = x.read(reset=False)
print(navigation_position.relPosN)

ANSWER:
Transmitting
06 00
Transmitting
06 01
Receiving
05 01
Acknowledged. CLS:0x6 ID:0x0
Transmitting
06 01
Receiving
04 02
Receiving
04 02
......(lot of 04 02 message)
Receiving
04 02
Receiving
04 02
Receiving
0a 11
Unsuported message class
I think the device or the software is not compatible with the libary you made. I can't even acces any message type at all.(e.g: lat or lon in th NAV_POSLLH can't be reached with x.enable_message(1,2) or the year from NAV_PVT with x.enable_message(1,7) )
So if you have any idea please tell me. :)

GOOD NEWS. I solved the problem. I can get every value of any class. This libary is awesome. I have problem with the drivers so after the reinstalling it the program worked perfectly.
I have one problem to solve but it is nothing compare to the previous's one.

Ah; that's good to hear :D What's the remaining issue?
P.s. I'll merge the code and try to add some of the things I mentioned earlier then. :)

The remaining issue is when the code runs down and I try to run it again I get an error (AttributeError: 'UbxMessage' object has no attribute 'relPosN'). The reason of the error is that somehow it disable the message-RELPOSNED and also set the protocol out an protocol in to UBX+NMEA. So every time I want to run get data via serial communication I have to set these protocol in to RTCM3 and protocol out to NONE.

Hmm, well about the UBX+NMEA, this is very much possible because the initialization of the UbxStream object also sets/overwrites the baudrate and inProtoMask / outProtoMask in a CFG-PRT message. It enables RTCM as well as the UBX+NMEA but not RTCM3. Here I have to bail on knowledge on the underlying systems though; this is meant for high precision corrections presented to the module through some sort of base station that sends these RTCM3 messages to it right? Or is your module supposed to be the base station sending the corrections?
Also I'm pretty sure these masks set which protocols you can communicate to/from the module with over that serial connection. As in; you're trying to disable the ubx protocol through u-center and then reading messages sent using the ubx protocol? I could misunderstand this though :)
In any case I can set the bitmasks more permissive (or give an option) to set these flags so that by default these are enabled as well if you're sure. :)
In the meantime are you also sure you don't have any other messages enabled? I would recommend a more secure read just in case that you have:
import serial
import ubx

def run():
  x = ubx.UbxStream(serial.Serial(port="/dev/ttyUSB0", baudrate=9600,timeout=1))
  x.disable_NMEA()
  x.enable_message(1,2)
  x.enable_message(1,60)

  while True:
    y = x.read(reset=False)
    if y.ubx_class is '01' and y.ubx_id is '02':
      print(y.lat)          # Message lat not part of RELPOSNED and should work
      #print(y.relPosN)     # This should give an error
    if y.ubx_class is '01' and y.ubx_id is '3c':
      print(y.relPosN)      # Message relPosN not part of POSLLH and should work
      #print(y.lat)          # This should give an error

if __name__ == '__main__':
  run()

Let me know how it goes and good luck ^_^


Jdk9 support

Incorporates and supersedes #398. Fixes #390 .

@javabrett - thanks so much for your work on this! I'm not sure that this is ever going to be merged though as I'm not sure Gretty is still alive. Would you consider forking it and releasing to Maven Central?

@boris-petrov we should hear from @akhikhl who is BDFL.  Are you looking for additional collaborators on the project?  I typically do not favour creating forks.

@javabrett - I also hate using forks but in this case I don't see any other way. @akhikhl is not responding to any of the issues or pull-requests here so we can assume he isn't going to help with this project any time soon. A lot of people are depending on Gretty so the wisest thing to do is someone else to continue supporting it.
Actually the same happened an year or so ago - Gretty was unsupported and we started using another fork of it (which had releases in Maven) and then we switched back to the original when it was resurrected. I see nothing wrong with that - the most important thing is that this project is kept alive.

Noone has heard from @akhikhl since Jun 27 2017 ( https://github.com/akhikhl/gretty/issues/375#issuecomment-312020390 ), so I'm in support for a fork as well.

And the fork should also integrate https://github.com/akhikhl/gretty/pull/415 in order to work with Gradle 4.6.

Hmm, somehow gretty fails for JDK8 now, while JDK9 works.  It's groovy related:
Error: Could not find or load main class
Exception in thread "Thread-235" org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1
        at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:389)
        at org.gradle.process.internal.DefaultJavaExecAction.execute(DefaultJavaExecAction.java:36)
        at org.gradle.api.internal.file.DefaultFileOperations.javaexec(DefaultFileOperations.java:183)
        at org.gradle.api.internal.project.DefaultProject.javaexec(DefaultProject.java:1077)
        at org.gradle.api.internal.project.DefaultProject.javaexec(DefaultProject.java:1072)
        at org.gradle.api.Project$javaexec$14.call(Unknown Source)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
        at org.akhikhl.gretty.DefaultLauncher.javaExec(DefaultLauncher.groovy:89)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
        at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:384)
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
        at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:69)
        at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:52)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:154)
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:166)
        at org.akhikhl.gretty.LauncherBase$_launchThread_closure4.doCall(LauncherBase.groovy:256)
        at org.akhikhl.gretty.LauncherBase$_launchThread_closure4.doCall(LauncherBase.groovy)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
        at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
        at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
        at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
        at groovy.lang.Closure.call(Closure.java:414)
        at groovy.lang.Closure.call(Closure.java:408)
        at groovy.lang.Closure.run(Closure.java:495)
        at java.lang.Thread.run(Thread.java:748)

Hmm, somehow gretty fails for JDK8 now, while JDK9 works. It's groovy
related:

Error: Could not find or load main class
Exception in thread "Thread-235" org.gradle.process.internal.ExecException: Process 'command '/Library/Java/ JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1
at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:389)
at org.gradle.process.internal.DefaultJavaExecAction.execute(DefaultJavaExecAction.java:36)
at org.gradle.api.internal.file.DefaultFileOperations.javaexec(DefaultFileOperations.java:183)
at org.gradle.api.internal.project.DefaultProject.javaexec(DefaultProject.java:1077)
at org.gradle.api.internal.project.DefaultProject.javaexec(DefaultProject.java:1072)
at org.gradle.api.Project$javaexec$14.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at org.akhikhl.gretty.DefaultLauncher.javaExec(DefaultLauncher.groovy:89)

@henrik242 do you have a simple test-case for that?
On 22 February 2018 at 01:18, henrik242<EMAIL_ADDRESS>wrote:

Hmm, somehow gretty fails for JDK8 now, while JDK9 works. It's groovy
related:
Error: Could not find or load main class
Exception in thread "Thread-235" org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/java'' finished with non-zero exit value 1
at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:389)
at org.gradle.process.internal.DefaultJavaExecAction.execute(DefaultJavaExecAction.java:36)
at org.gradle.api.internal.file.DefaultFileOperations.javaexec(DefaultFileOperations.java:183)
at org.gradle.api.internal.project.DefaultProject.javaexec(DefaultProject.java:1077)
at org.gradle.api.internal.project.DefaultProject.javaexec(DefaultProject.java:1072)
at org.gradle.api.Project$javaexec$14.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at org.akhikhl.gretty.DefaultLauncher.javaExec(DefaultLauncher.groovy:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:384)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:69)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:52)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:154)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:166)
at org.akhikhl.gretty.LauncherBase$_launchThread_closure4.doCall(LauncherBase.groovy:256)
at org.akhikhl.gretty.LauncherBase$_launchThread_closure4.doCall(LauncherBase.groovy)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:294)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at groovy.lang.Closure.call(Closure.java:414)
at groovy.lang.Closure.call(Closure.java:408)
at groovy.lang.Closure.run(Closure.java:495)
at java.lang.Thread.run(Thread.java:748)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/akhikhl/gretty/pull/417#issuecomment-367340114, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABDWdfIuXvsZNJZYwY3b7ueJS5g2PfILks5tXCWdgaJpZM4SLoA8
.

@javabrett I quickly deleted that comment, it was an error in my config :)

Fork it @javabrett, you're our only hope!  You gotta come up with a really good name though.  How about Bretty?  :)

@henrik242 OK that will teach me to reply via email :).  Deleted that comment too.

Fork it @javabrett, you're our only hope! You gotta come up with a really good name though.

No need to change the name IMHO.  But there's a lot of activity on gretty now, so we should just decide on someone to maintain a fork before all the enthusiasm dwindles...

@woldie @henrik242 @akhikhl I'm not especially interested in taking-up sole-maintainer role of a fork, but obviously happy to contribute.  A GitHub Organization seems like a better choice ... and then looking for others to join the cause.
@gretty is already taken as a username and is active.  Names?  gretty-gradle-plugin?
Perhaps dependent on that naming, a new plugin Maven package name is required, also assuming @akhikhl can't join and/or yield the current eponymous plugin package-name.

@javabrett @henrik242 @akhikhl I agree that a github organization makes sense.  Would be good to share the load and to enable a maintainer to transition ownership to other invested parties once they need to fall off.
Yes, I think a rename makes sense - more importantly, I think abandoning Gretty makes sense, and I move that we agree to do this.  "Bretty" is just a fun riff on the old name and keeping the name similar would be an indication to users that Gretty was superceded.  And if you found the Github organization, then you should get dibs on the name anyhow.  :)
Being serious for a moment though, it is tremendously healthy to have a BDFL on these types of projects to point everyone at the architectural north star.  Naming after yourself is a good way to establish your turf from the get-go and yet keep it light-hearted.  Please consider this.  Of course others like myself would be willing to pitch in on approving PR's and be a part of your organization, so you will not be on your own.  But, if you wanted to be the front-man, manage releases, and otherwise delegate the work, that could be arranged given how large the community of users is.
If fun isn't what we're looking for in a name, then the new name should be very bureaucratic and descriptive.  "Tomcat Gradle Plugin" and "Jetty Gradle Plugin", or TGP and JGP.  And yes, I'm also suggesting that we separate Gretty into two plugins.  This codebase seems a bit tortured at times trying to support both vendors.
Once the new plugin is published, we should move ASAP to sunset mentions of gretty in the gradle docs and on plugins.gradle.org in favor of our new plugin.

We can continue the fork discussion at https://github.com/akhikhl/gretty/issues/423
Or at https://github.com/gretty-gradle-plugin/gretty, obviously :)

Hello Guys, Is this change available now?
Thanks a lot for the support!


Using RealSense D400 series cameras

Hi,
I wanted to inquire if LiveScan3D-Hololens would work with the Realsense D400 series cameras ?
Thanks and Best Regards

Hi, what the code in this repo does is it allows for streaming the point cloud from LiveScan3D (my other project) to a Unity app, for example on HoloLens. It is agnostic to the type of sensor used, unlike LiveScan3D itself.


Flip Y-axis

Is it possible to flip the Y-axis? I need a graph showing ranks (standings in a league table) during a time span. Rank 1 should be the top value of the Y-axis.
Y-axis
1
2
3
4
etc. Date 1,  Date 2, Date 3 etc. -> X-axis

It's currently not possible but you can mimic this behaviour as discussed here: #382

Thanks for quick reply. Will try to mimic the behaviour.


IntegrationTest - ensure tests in priority dir are priority tests indeed

In current state, this PR is expected to fail.
Raised by https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3436#discussion_r161375420 .
We do have integration tests. What for ?
Sometimes we are not sure how 2+ fixers would play together, so we do make an integration test between them.
Integration test runner is smart enough to double check priorities:

if priorities are the same, the expected outcome must be the same regardless of order that fixers would be applied,
if priorities are different, we don't care.

Now the same, but from fixed code point of view:

if $fixedInputCode === $fixedInputCodeWithReversedFixers, then priorities doesn't matter,
if $fixedInputCode !== $fixedInputCodeWithReversedFixers, then priorities have to be different.

This is all what matters for end-user.
This is all that's needed to be stable, and whenever 2+ fixers becomes priority-related or stop being one, the tests are checking they are still running together.
This is all that is needed for devs writing custom rules.

Now, at this repo we went one step forward.
We do know by heart that some of the fixers have priority conflicts and we created auto review for them that checks explicit priority and fact that priority itest exist, as addition to itest itself (ref \PhpCsFixer\Tests\AutoReview\FixerFactoryTest).
It was super important at beginning (and still important, yet not that much), when we basically didn't have any itest at all. This explicit priority comparison was the only point when we were checking the order of fixers is what we assumed, even when it was not tested by itest.
Now, theoretically, we could drop distinguishes between misc and priority itests, then we shall reject this PR, or we could keep it and finish this PR.
There is a lot of boilerplate added in this PR that allows itests to be extended even more, yet don't focus on the implementation yet, first let us discuss the idea behind this PR.
To ease what is a real change, I assumed we are using tests\test as external package that have to be generic, and adjust project-specific tests in our IntegrationTest directly. I also added 2 notes to put focus on that few lines that are project-specific.
Also, keep in mind that apparently not all of priority tests are passing new check, what is proving that they (the few that are not passing) are not priority tests in the end...

thanks @keradus :D


jenkins: 2.93 -> 2.94

Motivation for this change
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I wonder if it would be better if nixpkgs tracked Jenkins LTS releases. Currently we're tracking the weekly releases in both NixOS master and release-17.09, and it feels like a bit too much (IMHO). LTS releases get major updates every 12 weeks, followed by bug and security fixes.
https://jenkins.io/download/
Thoughs?

I'm fine with that, although I would want to make sure that LTS updates include all the latest security patches, which come frequently.
Is there anything bad about frequent updates to the Jenkins derivation, other than it feels noisy and costs PR review time?

Yes, LTS is supposed to get security fixes.
I get the feeling that the weekly updates also introduce bugs and security issues. (Just skimming through the changelogs.)

@bjornfor See #34948 for switching to LTS.

A good solution to this issue is one where the last 50 releases of Jenkins can be installed via a binary method and every git version could be built from source by simply passing an optional parameter to the package. Since new versions come out each week, the only way to support this is if some daemon would push updates to the Jenkins expression automatically to nixpkgs.
Jenkins upstream cannot be trusted to consistently produce versions that are usable in production.
Once that infrastructure is in place, we can do automated upgrades of Jenkins that don't require any human in the loop anymore.
The current approach in which a single version is sanctioned as being the best for every user of Jenkins does not match real world operations.
This PR is just a symptom of not having enough options. Instead of removing an option (the last weekly release), please do PRs which add options and expand capabilities.

every git version could be built from source by simply passing an optional parameter to the package

As a start, I think this should be doable via a combination of #30588 and a package override.


chore(internal): consolidate preview rendering logic

This PR aims to

consolidate preview rendering logic of web and local extension. More info: [[Change Preview Rendering Logic on Local Ext|task.2022.11.08.change-preview-rendering-logic-on-local-ext]]
adds an abstract method renderNote in EngineV3Base and implemented in DendronEngineV3Web. Removed INoteRenderer and PluginNoteRenderer files created for the same.

Fixing test cases


Update mockito-core to 3.5.13

Updates org.mockito:mockito-core from 3.5.7 to 3.5.13.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito", artifactId = "mockito-core" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #118 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #118   +/-   ##
=======================================
  Coverage   57.83%   57.83%
=======================================
  Files          20       20
  Lines         287      287
  Branches        4        4
=======================================
  Hits          166      166
  Misses        121      121

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 d954c43...0f3a679. Read the comment docs.


Flesh out provider's copy function spec

While move is great, we also need the ability to simply copy within a provider.

Copy implementation spec (v1)
## copy(uris, target_uri, cache) -> Table
- Version Added: 0.2
- `uris`
    - Type: [Table]()
    - Details: The table of string [`URIs`](#uri) to copy
- `target_uri`
    - Type: [String]()
    - Details: The string location to move the URIs to. Consider this a "parent" location to copy into
- `cache`
    - Type: [Table]()
    - Details: The provider cache as provided by the API
- Returns: [Table]()
    - Details
        - A table should be returned with the following key/value pairs (**some are optional**)
            - success: boolean
                - This should be a true or false to indicate if the copy was successful or not
            - error: table (optional)
                - This should be provided in the event that you have an error to pass
                    to the caller.
                    The contents of this should be a table with a single `message` attribute (which houses a string)
                    EG: `error = { message = "SOMETHING CATASTROPHIC HAPPENED!" }`

This needs to be added to the api doc...

This has been added to the apidoc for v1.1. It wont be visible on the wiki until I get that updated to v1.1 as well :upside_down_face:


Error with Redux connect

I am trying to use cra-universal in my project but I am getting this error on server side :
Invariant Violation: Could not find "store" in either the context or props of "Connect(App)". Either wrap the root component in a <Provider>, or explicitly pass "store" as a prop to "Connect(App)".
My code looks like this
export class App extends Component {

render() {
//code here
}
}
function mapStateToProps(state) {
//code here
}

export default connect(mapStateToProps)(App);

My code is working fine on the browser.
How I can fix this issue?
Thanks

https://github.com/antonybudianto/cra-universal/wiki/Integrate-React-Router
it's for React router, but similar way, you need to custom the universal handler

I tried the following code,based on the code you provide but I am getting another error:
[nodemon] starting `node build/bundle.js`
1 handle Universal Render log
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.

Check your code at app.js:22.
/Users/yousef/Documents/PWA/ssr/server/build/bundle.js:194
  var stream = ReactDOMServer.renderToNodeStream(React.createElement(

ReferenceError: ReactDOMServer is not defined

Here is my code
const ReactDomServer = require("react-dom/server");
const path = require("path");

const React = require("react");
const { createReactAppExpress } = require("create-react-app-express");

const App = require("../../src/App");
const store = require("../../src/store");
const clientBuildPath = path.resolve(__dirname, "client");

function handleUniversalRender(req, res) {
  const context = {};
  const stream = ReactDOMServer.renderToNodeStream(
    <Provider store={store}>
      <App />
    </Provider>
  );

  return stream;
}
console.log("1 handle Universal Render log ");
console.log(handleUniversalRender(<App />));
console.log("2 handle Universal Render log ");
const app = createReactAppExpress({
  clientBuildPath,
  universalRender: handleUniversalRender(<App />)
});

module.exports = app;

Thanks

const app = createReactAppExpress({
  clientBuildPath,
  universalRender: handleUniversalRender
});

this one is wrong
const app = createReactAppExpress({
  clientBuildPath,
  universalRender: handleUniversalRender(<App />)
});

Yeah , my mistake. sorry for asking too much, I'm new to React.
Now, Im getting this error:
[HPM] Proxy created: /  ->  http://localhost:3000
Connected to CRA Client dev server
CRA Server listening on port 3001!
/Users/yousef/Documents/PWA/ssr/server/build/bundle.js:194
    Provider,
    ^

ReferenceError: Provider is not defined

here is my function
function handleUniversalRender(req, res) {
  const stream = ReactDOMServer.renderToNodeStream(
    <Provider store={store}>
      <App />
    </Provider>
  );

  return stream;
}

Thanks
it is working
Here is the code, maybe someone will need it
import { renderToNodeStream } from "react-dom/server";
import path from "path";
import { Provider } from "react-redux";
import React from "react";
import { createReactAppExpress } from "create-react-app-express";

import App from "../../src/App";
import configureStore from "../../src/store/index.js";
const clientBuildPath = path.resolve(__dirname, "client");

function handleUniversalRender(req, res) {
  const initialState = {};
  const store = configureStore(initialState);
  console.log(store);
  const stream = renderToNodeStream(
    <Provider store={store}>
      <App />
    </Provider>
  );

  return stream;
}
const app = createReactAppExpress({
  clientBuildPath,
  universalRender: handleUniversalRender
});

module.exports = app;

Thank you for sharing. I'll put it on the wiki for reference 👍 .


bug: counters in ordered lists not in sync

Hey,
so I noticed the start counters don't always stay in sync:
https://user-images.githubusercontent.com/10279942/218972777-c34e2ab7-2dae-4cbc-bbf7-ade32e434edd.mov

https://user-images.githubusercontent.com/24715727/219040457-a202b675-82f2-4dfb-8a07-5c9b67f68ad1.mp4
It seems that Chrome has bug for counter-reset CSS rule. The counter before C.C sometimes become incorrect in the video above. This could be a tricky bug.

This is indeed a Chrome bug. I can reproduce it without ProseMirror.
I'll try to find a workaround for it.

Huh, well that's something. I think you should just wait until it's fixed. Maybe this is related https://bugs.chromium.org/p/chromium/issues/detail?id=1408703&q=counter-reset&can=2

I'll wait for now since I couldn't find any workaround after some quick tries.

has any way to solve


Move & Update .env.example for Clarity

Moved .env.example to the correct directory where you would create the .env file
Added addition .env requirements
Give example of what the .env elements should look like


GH-39863: [C++]  Thirdparty: Bump google benchmark to 1.8.3

Rationale for this change
Bump benchmark to 1.8.3
What changes are included in this PR?
Bump benchmark to 1.8.3
Are these changes tested?
Already has testing
Are there any user-facing changes?
no

Closes: #39863

@ursabot please benchmark lang=C++

@austin3dickey The wording of the conbench summary at https://github.com/apache/arrow/runs/21102698059 is a bit unexpected, might this be due to the changes in this PR?

@pitrou Thanks for bringing that to my attention - that's unrelated to this PR. I recently upgraded conda on the machine that ran your benchmarks, and it seems to have put a break in Conbench history since the -isystem path changed. I will fix this so new benchmarks can be compared to old benchmarks.
In the meantime, you can check this link for comparisons: https://conbench.ursa.dev/compare/runs/97f46fae7b544173b9bfdc9962cf8051...e2a595b8ca9d41d4916b309b6c4ec42b/
(Sorry that page takes so long to load; I will fix that problem soon.)

I fixed the broken history in Conbench and manually reviewed the comparison I linked above. It looks good to me. I don't think this change has much of a performance effect on any of the benchmarks.

@ursabot please benchmark lang=C++

@Cerdore Could you rebase on main?

@Cerdore Could you rebase on main?

Already rebased

@ursabot please benchmark lang=C++

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g cpp


Can we have a better api for other jvm language, such as java/kotlin/clojure?

I think now the api is Main class, but it is a scala code. We can simple use the scala api in other jvm language. So I want to give a java api to wrap the scala code, so other jvm language can have a better experience to embed the ammonite repl in the application. How do you think about the idea
@alexarchambault  @lihaoy ? If you think this will be a good idea, I will give a try.

I write a basic java wrapper for self use https://github.com/lihaoyi/Ammonite/pull/1071. The usage is
@SpringBootApplication
public class DemoApplication implements CommandLineRunner {
	@Autowired
	private ApplicationContext context;

	@Autowired
	private TestController testController;

	public static void main(String[] args) {
		SpringApplication.run(DemoApplication.class, args);
	}

	@Override
	public void run(String... args) {
		System.out.println("run ammonite repl");
		JavaMain repl = new Builder().build();
		repl.runWithWatch(new JavaBind<?>[]{
				new JavaBind<>("context", context),
				new JavaBind<>("controller", testController)
		});
	}
}

This is out of scope for the Ammonite codebase, but feel free to publish it as a separate module


Bulk cherry pick v0

Cherry picking the following to V0:
#2476
#2457
#2399
#2382

Is it possible to add https://github.com/Microsoft/pxt/pull/2478 to your batch?

Sure thing

Added


Create TestStack.Seleno.Mvc

[ ] Pull out MVC specific things like the route registration and controller expression overloads
[ ] Remove MVC dlls from core project
[ ] TestStack.Seleno.Mvc4 with a dependency on MVC4 package
[ ] TestStack.Seleno.Mvc5 with a dependency on MVC5 package

Making good progress on this are you @robdmoore :stuck_out_tongue:
It's really quite annoying that you need to reference the MVC NuGet packages in Seleno when you're not using MVC (I'm using Seleno to automate a SPA that has no MVC at all).

:P agreed.
I actually have a WIP branch on my computer with 50% of it done


[Enhancement] Disable HDFS hedged read by default

It may occur HDFS open file failed / JVM oom / broker load slowly and timeout
So we need to disable it by default util we figure out this problem.
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[ ] 2.5
[ ] 2.4

@Mergify backport branch-3.1 branch-3.0


Fix dependency test: update deps-output.yaml test output file.

This PR addresses issues with the dependency test in the GitHub Actions workflow by updating the deps-output.yaml file. The changes ensure that the generated output file aligns correctly with the test file for accurate comparison.
This new structure of YAML is introduced in the dependent PR of analyzer-LSP: https://github.com/konveyor/analyzer-lsp/pull/566

@kthatipally thank you for the fix! Can you please sign-off your commit?

@kthatipally you will need to sign all the previous commits

@kthatipally just fyi, test failure doesn't look like its related to your change, I am looking into it

@kthatipally Ok so I just spoke with @eemcmullan we are going to merge your PR right now and address this failure in a follow up right away. Thank you!


deriving json

Djinni should be able to autogenerate json parsing and serialization code for records/enums.

Made a stub for deriving (json11).
Do you have any recommendations about architecture of the feature inside Djinni (e.g. how to modularize the codegen? Which parts of need to be updated?) or in generated C++ code (e.g. what API there shall be for parsing and providing Json)?

I might try to implement this, after https://github.com/dropbox/djinni/pull/308 got merged.

@4brunu
Would be really useful to have it done on the Scala side automatically. Any update ?

Sorry but I didn't get time to work on this, and I'm not sure if I will have.
If you want to give it a try, it should be somehow related to https://github.com/dropbox/djinni/pull/308.

I tried to look at it once but it wasn't so straightforward modifying the Scala sources, there is no "official" way of extending the generator. I reckon looking at what you did to automatically generate Parcelable might be a good start. Will need to find the time to do that.


TypeError exception on Device.disconnect() for Sphero BB-8 on OS X

Built off from one of the example scripts to connect with a Sphero BB-8 toy, list its advertised BLE services, and disconnect. On calling disconnect(), I see this error:
Traceback (most recent call last):
  File "<my project dir>/src/test.py", line 58, in <module>
    provider.run_mainloop_with(main)
  File "build/bdist.macosx-10.11-intel/egg/Adafruit_BluefruitLE/corebluetooth/provider.py", line 265, in run_mainloop_with
  File "/Library/Python/2.7/site-packages/PyObjCTools/AppHelper.py", line 182, in runConsoleEventLoop
    if not runLoop.runMode_beforeDate_(mode, nextfire):
  File "/Library/Python/2.7/site-packages/PyObjCTools/AppHelper.py", line 41, in call_
    func(*args, **kwargs)
  File "build/bdist.macosx-10.11-intel/egg/Adafruit_BluefruitLE/corebluetooth/provider.py", line 274, in _user_thread_main
  File "<my project dir>/src/test.py", line 53, in main
    bb8.disconnect()
  File "build/bdist.macosx-10.11-intel/egg/Adafruit_BluefruitLE/corebluetooth/device.py", line 73, in disconnect
  File "build/bdist.macosx-10.11-intel/egg/Adafruit_BluefruitLE/corebluetooth/gatt.py", line 59, in list_characteristics
  File "build/bdist.macosx-10.11-intel/egg/Adafruit_BluefruitLE/corebluetooth/metadata.py", line 63, in get_all
TypeError: 'NoneType' object is not iterable

My test scripts are here: https://gist.github.com/wolfteeth/9baf0133c582fc08e518
I'm not sure if I'm doing something wrong, or if there's something unusual about the device that the library wasn't ready for.

Was investigating similar task (and resulting error) and just found that this error gets thrown when DeviceInformation.discover hasn't been run before disconnect is called. The disconnect method seems to consider it an exception throw if it doesn't see pre-existing metadata...interrogating the device service before calling disconnect cleared up the error for me:
In your gist, this may fix the exception..
`
bb8.connect()
print 'Connected: ' + str(bb8.is_connected)
print 'Advertised services: ' + str(bb8.advertised)
print('Discovering services...')
DeviceInformation.discover(bb8)

# Once service discovery is complete create an instance of the service
# and start interacting with it.
dis = DeviceInformation(device)

bb8.disconnect()
`
/may the force be with you/

Is there a way to reconnect after disconnecting? I'm running into an issue where I connect to a device, start discovery, create an instance of the service, disconnect, but then if I call connect on it again it fails to connect.

This library has been deprecated. Please update to use this new library:
https://github.com/adafruit/Adafruit_Blinka_bleio
If you continue to have this issue, please open a new issue in that repo.


Add support for ServiceMeshPolicy and ServiceMeshRbacConfig: MAISTRA-630

Note this PR is going to have a significant impact in Kiali.
MeshPolicies and ClusterRbacConfig are resources managed by Kiali.
MeshPolicies are also used to validate mTLS configuration.
With these changes, we need to add support for these two objects (if I understand correctly) and change the logic of calculation when we are in Maistra vs Istio upstream.
Also the UI should be changed to only show these objects.

@knrc can we discuss/study if there is a possibility to have this PR's logic, but maintaining Istio upstream naming for compatibility ?

@knrc can we discuss/study if there is a possibility to have this PR's logic, but maintaining Istio upstream naming for compatibility ?

To retain the upstream name it would need to remain cluster scoped.  We actually tried that last week but there were security issues since information leaked between the meshes.
Since we need the scope to change we need to change the name of the CRD.

Note this PR is going to have a significant impact in Kiali.
MeshPolicies and ClusterRbacConfig are resources managed by Kiali.
MeshPolicies are also used to validate mTLS configuration.

@lucasponce This is surprising since we have been discussing this change for some time during our weekly multi-tenant calls.  We were lead to believe the change would be relatively straight forward since the contents remain the same and it's only the name of the resource (and being namespaced) which is changing.

With these changes, we need to add support for these two objects (if I understand correctly) and change the logic of calculation when we are in Maistra vs Istio upstream.

+1

Also the UI should be changed to only show these objects.

How much effort do you think this would require?

@lucasponce This is surprising since we have been discussing this change for some time during our weekly multi-tenant calls. We were lead to believe the change would be relatively straight forward since the contents remain the same and it's only the name of the resource (and being namespaced) which is changing.

Yes, but we discussed several scenarios, IIRC, one maintain the API, but adding them namespace scoped, and other renaming them. The last would take more effort as basically Kiali will need to support Maistra specific objects, meanwhile, maintaining the same naming, the code base will remain intact.

From https://issues.jboss.org/browse/MAISTRA-630 description:

There are two alternative solutions

Keep the upstream names but make their CRDs namespaced
Replace these resources with alternatives such as ServiceMeshPolicy and ServiceMeshRbacConfig
The first would likely be simpler to implement but lead to clashes with upstream installations whereas the second would be a more invasive change for ourselves and likely also the Kiali team

Which is the case, in the first scenario, Kiali codebase would be compatible, but the second will require some days-effort to adapt it and prepare it.

From https://issues.jboss.org/browse/MAISTRA-630 description:

There are two alternative solutions

Keep the upstream names but make their CRDs namespaced

We tried to do this last week.  We couldn't make them namespaced as this would clash with the upstream istio definition however we tried to rename them so the resource would share the name of the service mesh control plane namespace.  The filtering didn't work and was leaking information to other meshes.

Replace these resources with alternatives such as ServiceMeshPolicy and ServiceMeshRbacConfig
The first would likely be simpler to implement but lead to clashes with upstream installations whereas the second would be a more invasive change for ourselves and likely also the Kiali team

Which is the case, in the first scenario, Kiali codebase would be compatible, but the second will require some days-effort to adapt it and prepare it.

The first solution would likely also require changes, either to namespaced resources (breaking upstream) or resource names (still cluster wide but filtered).  We tried but rejected those solutions.

I've squashed the commits into one

Please @knrc , how I can deploy this PR in a local 3.11 version that I can use to propagate these changes into Kiali ?
Could you describe us some steps ?
Thanks.

The latest PR squashes the commits in preparation for merging.


Code coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c28894e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #120   +/-   ##
=========================================
  Coverage          ?   70.60%
=========================================
  Files             ?       51
  Lines             ?      966
  Branches          ?        0
=========================================
  Hits              ?      682
  Misses            ?      284
  Partials          ?        0


Error in 'Get started with primitives'

URL to the relevant documentation
https://docs.quantum.ibm.com/guides/get-started-with-primitives
Select all that apply

[x] typo
[x] code bug
[ ] out-of-date content
[ ] broken link
[ ] other

Describe the fix.
In the section "Get started with Estimator" ,  running the 127-qubit circuit of the example on the backend returned from the least_busy method , that is 'ibm_sherbrooke', I got the following error on the IBM Quantum Platform
Status details
Status
Failed
error icon
Job not valid. '48921 2-qubit gates exceeds the system limits by 389.210% in combination with the option configuration. -- Split circuits or PUBs into multiple jobs. See Run jobs in a batch <https://docs.quantum.ibm.com/guides/run-jobs-batch#partition>__ for an example. -- https://ibm.biz/error_codes#1520'
which is different from the output in the documentation.
In the section "Get started with Simulator" the output is a 4-qubit circuit's one  while the example uses a 127-qubit circuit.

@lucachiese25 the new example on the Get started with primitives page should work now. Thank you!


Update methodology to more closely match real-world workloads

That is very interesting @isaacs. Thank you very much. It makes me wonder whether I should drop my array backing for storing values in favor of entries containing key,value,pointer_index directly into my maps to catch up on get performance (since I need an additional lookup into the value storage array). I would need to keep the entries into a static pool as usual to avoid GC and all but maybe this is worthwhile.

@Yomguithereal Yeah, I've been messing with lru-cache a bit the last few weeks.
Eventually when I got performance to be comparable, I took a look at how mnemonist-map was working, and it's almost identical, but our heads and tails are swapped, which I found amusing :)

Is your folder available somewhere? I would love to take a look at all those implementations you tried.

Eventually when I got performance to be comparable, I took a look at how mnemonist-map was working, and it's almost identical, but our heads and tails are swapped, which I found amusing :)

Head or tail in doubly-linked lists is always a matter of opinion it seems :) Did you perchance try the old lru cache implementation trick that enable you to only keep pointer storage for forward or backward direction by storing the pointer to previous or next as value of the hashmap? I did not try it because it is a bit convoluted and I think it requires two hashmap lookup (which is probably slower) but I wonder if this could be efficient in JS for some reason. I think I mentioned this trick somewhere here: https://yomguithereal.github.io/posts/lru-cache

id you perchance try the old lru cache implementation trick that enable you to only keep pointer storage for forward or backward direction by storing the pointer to previous or next as value of the hashmap?

I did try that, actually.  It makes the initial set() performance significantly better, but get() performance drops, so it's only a good fit if you're caching things you never want to get back out, and in that case, you're better off just not caching.  I only did a rough cut of it, so it's possible that some work could be done to make it faster, but it seems any extra Map.get calls really hurts.
If you can get away with knowing that your keys will always be integers within some reasonable range, you can get it going crazy fast by using an array as the key map.  But that's probably too limiting to be useful.  I tried using an object until a key is encountered that wouldn't perform well with an object (ie, a number that's not an integer, or a string over 256 chars, or any non-string/non-number), but the type checking was too costly to be worth it, and it added a lot of complexity.  I think we're at a local maximum here.
https://gist.github.com/isaacs/c1fb014371902ed937a210135cf6a1c4

Oh! Another surprising thing, it seems like at least in relatively recent versions of v8, there's really no difference in performance between an typed Uint##Array and a normal Array() that only contains ints within that range.  I was thinking it might be fun to be able to use the same linked list in both compiled and JS code, somehow.
You wouldn't be able to maintain strict LRU semantics, but you could do something like lru-cache's isStale() to just drop deleted items as they are encountered, based on a flag in the typed array.  I imagine writing into the key map or value/key lists would be tricky to do in a performant way though, because of the C++/JS boundary tax, so again that really limits the functionality if you're storing anything that can't be expressed as raw bytes.

Oh! Another surprising thing, it seems like at least in relatively recent versions of v8, there's really no difference in performance between an typed Uint##Array and a normal Array() that only contains ints within that range.

I had noticed indeed that in earlier versions, the more you go towards a Float64Array, the less you gain performance by relying on a byte array, which makes sense since the engine is probably able to use the same underlying structure to store relevant numbers. This said, it's cool to know the engine is now able to infer more about the contained numbers and optimize further. Another thing that should be tested is memory usage. In my experience, CPU time does not suffer too much, but there is still a memory cost to use a plain array vs. a byte array.

Another thing that should be tested is memory usage. In my experience, CPU time does not suffer too much, but there is still a memory cost to use a plain array vs. a byte array.

Ah, that does make sense, since it has to be prepared to switch from int[] mode to object mode at any time.
I've found that for most cases in JS where you'd want to use an LRU, the most relevant concern is the time to fetch an object from a slow upstream source, so as long as memory can't expand indefinitely just "using a lot" is typically fine.  (I note this is your reason for not bothering with the single-link-list-and-map approach; pointer space isn't really the issue.)  If you don't have a ton of memory to spend on the performance and flexibility of an optimizing JIT, JS is not the language to use lol

If you don't have a ton of memory to spend on the performance and flexibility of an optimizing JIT, JS is not the language to use lol

Clearly yes :) But if you are in the browser the choice is often made for you (you can try webassembly but if you need to interact with the cache from JS, the communication cost remains too high to enhance performance. What's more, if you need to work outside of v8 (Firefox notably), using byte arrays and avoiding dynamic allocation and GC is able to yield spectacular perf boost since the engine does not need to think very much to optimize the runtime.

@Yomguithereal Here's a gist with all the many index-*.js files, if you feel like poking around in there.  It's mostly bad though 😅

Thanks @dominictarr I will peruse this with care :)

@dominictarr do you need any help with reviewing/merging this PR?

@Yomguithereal By the way, idk if you've been continuing to test this, but in benchmarking a major refactor of lru-cache, I found that mnemonist's Map-based LRUMapWithDelete appears to be somewhat faster overall than LRUCacheWithDelete (the object-based one), in addition to being safe with non-string keys.  Might be worth updating the docs to suggest using the Map version instead.
int: just an integer
| name               | set   | get1  | update | get2  | evict | score  |
|--------------------|-------|-------|--------|-------|-------|--------|
| mnemonist_0.39_map | 16949 | 41667 | 25000  | 31250 | 9174  | 386019 |
| lru-cache_CURRENT  | 12500 | 40000 | 14706  | 28571 | 9091  | 348016 |
| mnemonist_0.39_obj | 37037 | 12821 | 11364  | 12346 | 17857 | 274916 |

strint: stringified integer
| name               | set   | get1  | update | get2  | evict | score  |
|--------------------|-------|-------|--------|-------|-------|--------|
| mnemonist_0.39_map | 17857 | 76923 | 40000  | 50000 | 18868 | 650823 |
| lru-cache_CURRENT  | 18182 | 66667 | 35714  | 47619 | 13889 | 579619 |
| mnemonist_0.39_obj | 30303 | 12821 | 11364  | 11765 | 16129 | 249903 |

str: string that is not a number
| name               | set   | get1  | update | get2  | evict | score  |
|--------------------|-------|-------|--------|-------|-------|--------|
| mnemonist_0.39_map | 11628 | 32258 | 24390  | 27778 | 8850  | 327560 |
| lru-cache_CURRENT  | 11905 | 33333 | 23256  | 21739 | 7576  | 293640 |
| mnemonist_0.39_obj | 13889 | 11236 | 10101  | 10309 | 7246  | 159362 |

The set() time for the object version is faster for short strings, especially short integer strings, but in all other paths, it falls short considerably.

@isaacs nice to know v8 is finally optimizing Maps properly. I have two questions though:

are you observing that the object version "lost" performance, or just that the map ones are just faster now?
did you test the not WithDelete versions also?  The WithDelete versions must maintain a stack of free pointers and should consume O(n) more memory and should have a little performance overhead vs. the regular versions.

Might be worth updating the docs to suggest using the Map version instead.

I should do so indeed. Can you tell me from which node version the Map version seems to win?

@Yomguithereal I haven't compared it exhaustively across Node versions.  (My goal is to track performance across lru-cache versions within a given Node version.)  But from my limited testing, the object version seems to still be about the same as it was (ie, exceptional with short integer strings, good with short non-numeric strings, ok with long strings, utterly abysmal with floats or float numeric strings), and lru-cache and mnemonist/lru-map-with-delete seem to have both gotten faster across the board.  For some reason, recent LRUCache versions are getting slightly better performance than mnemonist LRUMapWithDelete with mixed type keys, but just slightly worse everywhere else, with the difference being pretty much only in set() and especially evict().  Afaict, the main difference between our implementations is that I do the eviction in a separate method and return this from the set() method, whereas mnemonist returns the evicted value, and lru-cache is doing a few boolean checks to see if TTL/size tracking/etc are enabled.  I can see that the evict() method is being inlined, so it shouldn't be affecting performance, but even when I remove the feature checks, it still does about the same. 🤷 VMs are weird.
I haven't tested the no-delete version.  Since lru-cache includes deletion, I tried to test against implementations with as close to feature parity as possible.  But I don't think the free pointer tracking is a significant performance cost either, and the memory overhead is pretty minimal.

Can you tell me from which node version the Map version seems to win?

This was found testing with Node.js v18.latest.

@Yomguithereal Lol, the results on GitHub Actions' linux VMs is quite a bit different from on my laptop :joy: https://isaacs.github.io/node-lru-cache/benchmark/

This was found testing with Node.js v18.latest.

Ok, I'll indicate this as the tipping point on the docs. (I think I tested v16 and did not observe this shift yet).
That's the first time I think about the mixed return type of a collection method tanking the perf but it makes a lot of sense unfortunately. Maybe a method not returning the evicted value could help but is this worth it?

I have no idea why that would be in these cases, but empirically, there it is.

I would expect this with a finely crafted hashmap implementation that does not need to handle all the corners cases a JavaScript POJO has to keep in mind. Especially with contents that actually need a hashmap (not a struct-like content). V8 just required a little bit of time to make it happen I guess. That's good news :)

That's the first time I think about the mixed return type of a collection method tanking the perf but it makes a lot of sense unfortunately. Maybe a method not returning the evicted value could help but is this worth it?

Ah, yes, I see, the issue is probably that the returned object shape is different between each call.
I think in practice, most caches have consistently structured data with a single key type, so the fact that lru-cache does better there actually reflects some mis-appropriated optimizations on my part.


Skylar-mobile-check

checks if user is on mobile and throws an error

I believe I'm waiting on a cypress test of this before we merge? Does it seem like a straightforward thing to do, or will it be a lot of work?

The test has been added and updated to pass!

Ok, I think this should be good to go, let me know if you find anything else!


Metadata update

This PR updates the format of the metadata file saved by recorder. The main motivation was to add a field for logging LC voltages (and not just retardance), and to round float numbers before saving. In the process, I updated the structure of the metadata dictionary, adding the Calibration field (in addition to Summary, Notes, and Microscope parameters), changed some entries to more sensible naming (e.g. Calibration scheme instead of Acquired Using), and to more consistent capitalization (e.g. Extinction ratio instead of  Extinction Ratio).
Saving LC voltage in the metadata file will be implemented in calibration_data_class_v2 branch, which will be tested and merged soon.
If we like this updated metadata file we should make sure to update recon pipelines that rely on it accordingly, keeping backward compatibility, if possible. @talonchandler, @Soorya19Pradeep, @mattersoflight let me know what you think.

The old format metadata looks like this
{
 "Summary": {
  "Timestamp": "2022-05-25 18:37:38.910646",
  "recOrder-napari version": "recOrder-napari 0.1.1.dev1+g148b9c3",
  "waveorder version": "waveorder 1.0.0b0",
  "Acquired Using": "5-State",
  "Swing (fraction)": 0.1,
  "Wavelength (nm)": 532,
  "BlackLevel": 144.91,
  "Extinction Ratio": 254.22,
  "ChNames": [
   "State0",
   "State1",
   "State2",
   "State3",
   "State4"
  ],
  "[LCA_Ext, LCB_Ext]": [
   0.30634075285030704,
   0.5834
  ],
  "[LCA_0, LCB_0]": [
   0.20634075285030704,
   0.5834
  ],
  "[LCA_45, LCB_45]": [
   0.3063,
   0.4952139933415637
  ],
  "[LCA_90, LCB_90]": [
   0.3984260299461079,
   0.5834
  ],
  "[LCA_135, LCB_135]": [
   0.3063,
   0.6532008989501689
  ],
  "Swing0": 0.1,
  "Swing45": 0.08818601607486636,
  "Swing90": 0.09208527709580083,
  "Swing135": 0.06980091084682555,
  "ROI Used (x, y, width, height)": [
   0,
   0,
   1232,
   1026
  ],
  "Instrument_Matrix": [
   [
    1.0,
    0.0,
    0.0,
    -1.0
   ],
   [
    1.0,
    0.5877852522924731,
    0.0,
    -0.8090169943749475
   ],
   [
    1.0,
    0.0,
    0.5877852522924731,
    -0.8090169943749475
   ],
   [
    1.0,
    -0.5877852522924731,
    0.0,
    -0.8090169943749475
   ],
   [
    1.0,
    0.0,
    -0.5877852522924731,
    -0.8090169943749475
   ]
  ]
 },
 "Notes": "",
 "Microscope Parameters": null
}

The new metadata format looks like this
{
 "Summary": {
  "Timestamp": "2022-05-31 20:14:30.027134",
  "recOrder-napari version": "recOrder-napari 0.1.1.dev1+g148b9c3",
  "waveorder version": "waveorder 1.0.0b0"
 },
 "Calibration": {
  "Calibration scheme": "5-State",
  "Swing (waves)": 0.1,
  "Wavelength (nm)": 532,
  "Black level": 119.73,
  "Extinction ratio": 237.08,
  "ROI (x, y, width, height)": [
   0,
   0,
   2448,
   2048
  ],
  "Channel names": [
   "State0",
   "State1",
   "State2",
   "State3",
   "State4"
  ],
  "LC retardance": {
   "LCA_ext": 0.30566,
   "LCB_ext": 0.5789,
   "LCA_0": 0.20566,
   "LCB_0": 0.5789,
   "LCA_45": 0.3057,
   "LCB_45": 0.48902,
   "LCA_90": 0.40126,
   "LCB_90": 0.5789,
   "LCA_135": 0.3057,
   "LCB_135": 0.64786
  },
  "LC voltage": {},
  "Swing_0": 0.1,
  "Swing_45": 0.09,
  "Swing_90": 0.096,
  "Swing_135": 0.069,
  "Instrument matrix": [
   [
    1.0,
    0.0,
    0.0,
    -1.0
   ],
   [
    1.0,
    0.58779,
    0.0,
    -0.80902
   ],
   [
    1.0,
    0.0,
    0.58779,
    -0.80902
   ],
   [
    1.0,
    -0.58779,
    0.0,
    -0.80902
   ],
   [
    1.0,
    0.0,
    -0.58779,
    -0.80902
   ]
  ]
 },
 "Notes": "",
 "Microscope parameters": null
}

Thanks @ieivanov! I think these are big improvements in clarity, and I really like the tightened getattr writers.
I have two questions:
1 - Since these files are the only record of the calibration, is rounding the right move here? You're keeping five digits of retardance and three digits of swing. My intuition says that that should be more than enough, but I don't have enough experience with the reconstructions to be sure without testing. Is there any chance that the fifth digit matters when you're on the steepest part of the voltage-retardance curve?
I know you're prioritizing readability here---maybe we should save all digits to file then round only during saving and loading?
2 - Can you update/remind me what you expect the advantages of voltage-space calibration will be? IIRC you're hoping to perform the optimization in voltage space (seems like a clear advantage to me) and avoid the interpolation errors by changing to a closed-form voltage-retardance mapping (again, seems like a clear advantage).
Do these changes necessitate saving in voltage space, though? Could we get away with saving in retardance space for simplicity+backwards compatibility reasons?

Great! Thanks for the specs on the number of digits we can control...makes complete sense.
Thanks for the clarification on saving voltage. If I understand correctly, you're planning to always save the calibration result in both retardance and voltage space? Are you planning to save the voltage-retardance mapping as well (in the form the closed-form fit parameters you mentioned)?
These questions are low priority and not that relevant to this PR. Approving now...

@talonchandler I'm finished working on this PR and I think it's ready to be merged, but it's still failing some of the checks. Can you please help me troubleshoot it? I just ran it again, but I'm expecting it to fail.

Thanks for looking into this! Merging...


ios: Update "SPEC CHECKSUMS" for DoubleConversion and glog

These checksums appear on running pod install (or yarn, which
causes pod install to run), if I run it after removing
"ios/Pods/Local Podspecs". That's the case at current main, and
also at the recent RN v0.65 upgrade commit 72583b13c, but not just
before that commit.
Probably a4e941fe0 is related, and I should have remembered to try
clearing "Local Podspecs" when I did the RN upgrade. That would've
brought this to light at the time, and the new checksums would've
made it into the upgrade commit, where they belong.

Ah good catch, thanks. That sure is an annoying CocoaPods issue. :-/ Merging.
I guess we should consider clearing "Local Podspecs" to be part of the procedure for RN upgrades, in light of this.

Thanks!


ios-deploy path issue

When trying to run tests on the device I noticed the installedInstallers contained absolute paths to ios-deploy which failed the switch evaluation.  Small fix to use a regex.

Thanks for checking this out! This code has languished for a bit while we
wait to see if it can be replaced by simctl.
I think the error might be elsewhere however; we shouldn't be passing a
path to specificMethod. I am traveling now but can look at it afterwards.
On May 1, 2015 2:16 PM, "Travis Meisenheimer"<EMAIL_ADDRESS>wrote:

When trying to run tests on the device I noticed the installedInstallers
contained absolute paths to ios-deploy which failed the switch evaluation.
Small fix to use a regex.
You can view, comment on, or merge this pull request online at:
https://github.com/paypal/Illuminator/pull/51
Commit Summary

Fixed issue when the installedInstallers contains the absolute path
to the installer and not just the basename. -Travis/Musa

File Changes

M gem/lib/illuminator/device-installer.rb
https://github.com/paypal/Illuminator/pull/51/files#diff-0 (2)

Patch Links:

https://github.com/paypal/Illuminator/pull/51.patch
https://github.com/paypal/Illuminator/pull/51.diff

—
Reply to this email directly or view it on GitHub
https://github.com/paypal/Illuminator/pull/51.

I had the same thoughts when looking at the code with regard to what 'specificMethod' was being passed.  If someone passes in an actual 'specificMethod' (from whoever calls installOnDevice) it may bomb out entirely if it isn't in the path.  It would probably need to try and find the path of the executable that represents the specific method and then execute that instead of trying to execute whatever specificMethod is.  If simctl could be used then I guess it would just use that.  That would be easiest then no need for strategies since it comes from the device/os vendor.

Our original goal was to support whatever installation method(s) might
exist on the user's machine, but as you can see we're a little behind in
the architecture for now. We are in somewhat of a holding pattern, to see
if new features for this are going to be announced at WWDC.
@kviksilver can probably weigh in on whether this PR is the short term fix
we need until then.
On May 1, 2015 3:17 PM, "Travis Meisenheimer"<EMAIL_ADDRESS>wrote:

I had the same thoughts when looking at the code with regard to what
'specificMethod' was being passed. If someone passes in an actual
'specificMethod' (from whoever calls installOnDevice) it may bomb out
entirely if it isn't in the path. It would probably need to try and find
the path of the executable that represents the specific method and then
execute that instead of trying to execute whatever specificMethod is. If
simctl could be used then I guess it would just use that. That would be
easiest then no need for strategies since it comes from the device/os
vendor.
—
Reply to this email directly or view it on GitHub.

Your suggestion sounds reasonable.  As iOS developers we're pretty beholden to whatever Apple does.  I haven't had luck with simctl pushing to an actual device but that doesn't mean anything.  If I can extract these strategies out better I will submit another pull request.  I think it is a good idea to support both sim and device testing (those are my needs anyway).  Thanks for the feedback.

Yes @tmeisenh you are probably right, simctl will hardly be able to do anything with device, but we might get something in few weeks... Thanks for the contribution it is appreciated...


hotfix cache upload image

💻 变更类型 | Change Type

[ ] feat
[x] fix
[ ] refactor
[ ] perf
[ ] style
[ ] test
[ ] docs
[ ] ci
[ ] chore
[ ] build

🔀 变更说明 | Description of Change

📝 补充信息 | Additional Information

Summary by CodeRabbit

New Features

Introduced a new utility for consistent JSON response handling in the app.

Bug Fixes

Improved the upload and remove functionalities for better response formatting and clarity.

fixed #5074


delimiter option not working on most android 7.x browers

it is working with Firefox and Puffin tho. It also works with Safari on Iphones.

Hey @schynsal if I find a moment in my daily job I'll try to investigate. Of course feel free to provide any feedback why it happens. ;)


Some assertions fail while testing on device

The new version 1.0.3 has added some assertions. The assertion 'version_code" is throwing an error while testing on my device. I downgraded  to 1.0.2 which does not have that issue.

Hi @aswinmohanme,
Could you give an example of the app without the version code ?

It was an issue with my code, fixed it :relaxed:


Extract components from Skills component

Currently, the Skills component feels cluttered. It'd be clever to extract components out of the implementation

Fixed by 3eb38517188abb0500cdb4d49dda4f5c2bb3e81d


Add markercluster, closes #14

I solved the issue #14. I've added the library leaflet.markercluster and replace the normal layer by a makerCluster.
Now if there are more than one event in a certain area a number will shown. By clicking on it, the will map zoom in or on a high level the marker will spread over the map so you can choose one.

Thanks @britiger ! 👍
I'll make a new release in a few minutes.


DX: Add GPT module and command-line interface

This commit adds the GPT module to the project and implements a command-line interface for generating commits and summaries for pull requests.
Commits

Added 'OpenAIStream.js'
Added 'ai.js'
Added 'commit.js'
Added 'file.js'
Added 'generate.js'
Moved 'gpt.js' to 'gpt/gpt.js'
Added 'index.js'
Added 'markdown.js'
Added 'pull-request.js'

The 'index.js' file implements a command-line interface with two options: '--pr' and '--commit'. The '--pr' option generates a summary of all pull requests in the repository, while the '--commit' option generates a commit message using the GPT model.

Subscribed to follow this thread and understand how you make it 👀 thanks for the Linkedin post x


Twitter In node question

Hi.
I'm using twitter in node for the first time and probably there's something I haven't fully got about receiving tweets coming from user I follow filtered by expression.
Indeed, it seems that despite specifying something like "@user,#hashtag" in filter expression while using "tweets from users I follow" option, I get a message for every message in timeline.
Is there any explanation for this behavior?
Thanks!

Hi,
sorry this has sat unanswered for so long. The mailing list is often a better starting point for this sort of question.
The twitter api docs for what is possible to filter is here.
In short, if you want to restrict to the tweets of a specific user, you will need to pick the 'tweets of a specific user' option, and then filter the content in your flow.


Don't work create account

What talent are you looking for?
None
What you need to be done?
create account
Tags
No response
Deadline
No response
Currency
USDC.e
Amount
No response
KYC

[ ] Use KYC Verification

I try create account:

@tverdoy with latest version of CLI you should be able to use short syntax with default configuration, it works just fine
near create-account your-name-here.testnet --useFaucet

my config
explorer_transaction_url: "https://explorer.testnet.near.org/transactions/"
  fastnear_url: null
  faucet_url: "https://helper.nearprotocol.com/account"
  linkdrop_account_id: "testnet"
  meta_transaction_relayer_url: null
v near_social_db_contract_account_id: "v1.social08.testnet"


SSR issue: server side state

I am encountering a small issue with your lib when used with Remix
https://github.com/clauderic/dnd-kit/blob/56d11cceec27fe5a03dc74a802b4f4be3e59b2f6/packages/utilities/src/hooks/useUniqueId.ts#L3 this variable "survives" refreshes on the server, which results in the ids just keeping counting up. Whilst the client always starts from scratch. This results in the following error from react-dom: Warning: Prop aria-describedby did not match. Server: "DndDescribedBy-13" Client: "DndDescribedBy-0"
this can be solved by not using any level of global variable (neither in modules nor app-wide).
I don't really know how to patch this and therefor I have no PR for you, obviously you do need to store the ids state, just not as a global.

I was able to get this to work by switching from using a global variable to using a ref inside of the hook. I tested this on my end and it is working but not sure if it would cause any other issues. I can submit a PR if this seems like a reasonable solution.
import {useMemo, useRef} from 'react';

export function useUniqueId(prefix: string, value?: string) {
  const ids = useRef<Record<string, number>>({})

  return useMemo(() => {
    if (value) {
      return value;
    }

    const id = ids.current[prefix] == null ? 0 : ids.current[prefix] + 1;
    ids.current[prefix] = id;

    return `${prefix}-${id}`;
  }, [prefix, value]);
}

Passing an id prop to the DndContext as suggested in this previous issue appears to have resolved this same issue for me.
https://github.com/clauderic/dnd-kit/issues/285#issuecomment-853974128


Introduction missing for Basic JavaScript section (Beta site)

Section Name

Beta site Basic JavaScript
Issue Description

The Basic JavaScript section needs a landing page with introductory text to start the section.

Can I get assigned this if it's still open?


Add view meta

Description
This PR brings the idea of view meta as some apps do not rely on URLs but rather on "views".
There is a "default" view that it set by the web-sdk and it can be changed similarly to how we do it with the session meta.
Checklist

[x] Tests added
[x] Changelog updated
[x] Documentation updated

@domasx2 - yup! Should we hold merging this until collector implements support for view? AFAIK the collector will just drop the view meta.
cc: @rlankfo @kpelelis


Doctor doesn't find ruby-build after Debian-based install

Steps to reproduce:

sudo apt install rbenv (install rbenv)
ruby-build --version (confirm ruby-build also installed)
which ruby-build (confirm ruby-build location)
Run rbenv-doctor

What should happen:

ruby-build returns version & location
Doctor results all "OK", including ruby-build

What happens instead:

ruby-build returns version 20170726
which ruby-build returns /usr/bin/ruby-build
Doctor returns:

Checking for `rbenv' in PATH: /usr/bin/rbenv
Checking for rbenv shims in PATH: OK
Checking `rbenv install' support: not found
Unless to plan to add Ruby versions manually, you should install ruby-build.
Please refer to https://github.com/rbenv/ruby-build#installation

Counting installed Ruby versions: none
  There aren't any Ruby versions installed under `/home/user/.rbenv/versions'.
  You can install Ruby versions like so: rbenv install 2.2.4
Checking RubyGems settings: OK
Auditing installed plugins: OK

Notes:
Operating system: PureOS 8 (~= Debian testing)
$ which rbenv
/usr/bin/rbenv
$ rbenv --version
rbenv 1.1.1

However, the following commands work:

rbenv install -l
rbenv install 2.4.1

However, the following commands work:

Thank you for reporting! That is interesting. Are you able to locate where rbenv-install executable was placed by debian packages?

/usr/bin/rbenv points to /usr/lib/rbenv/libexec/rbenv
And rbenv-install is amongst other files in /usr/lib/rbenv/libexec...
/usr/lib/rbenv/libexec $ ls
rbenv*              rbenv-exec*    rbenv-hooks*    rbenv-local*   rbenv-root*       rbenv-sh-shell*   rbenv---version*          rbenv-version-file-write*  rbenv-versions*
rbenv-commands*     rbenv-global*  rbenv-init*     rbenv-prefix*  rbenv-shims*      rbenv-uninstall*  rbenv-version-file*       rbenv-version-name*        rbenv-whence*
rbenv-completions*  rbenv-help*    rbenv-install*  rbenv-rehash*  rbenv-sh-rehash*  rbenv-version*    rbenv-version-file-read*  rbenv-version-origin*      rbenv-which*

@kwill Thanks for looking that up! Perhaps we should amend rbenv-doctor to include the location of {rbenv-install-location}/libexec/ when searching for rbenv-install. PR welcome!


Response status code does not indicate success: 401 (PermissionDenied) on Bot Framework Emulator

When I follow steps 1 to 9 of Add language understanding data and conditions, the bot fails to connect to LUIS and all I get is Response status code does not indicate success: 401 (PermissionDenied).
Is there some step missing from the guide?

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

ID: c55e6920-2987-2b78-66b7-3dee92ab8689
Version Independent ID: 5d9f5e75-ee25-cc5d-bdd5-594712badf63
Content: Tutorial: Add language understanding to bot - Bot Composer
Content Source: composer-docs/tutorial/tutorial-luis.md
Service: bot-composer
GitHub Login: @WashingtonKayaker
Microsoft Alias: kamrani

With some help I got to that a call is being made to westus.api.cognitive.microsoft.com with my key from eu.luis.ai and the Azure resource group is in westeurope.
Looks like composer is assuming westus when it shouldn’t.
By the way, the conversation app was published by the composer to eu.lui.ai.

Thanks for your report and apologies for the late response.
There are additional configurations required if you publish your bot to regions other than "westus". We will contact our developers for details so that we can add the required content.
Will keep you posted. Thanks a lot!


detailed supported documents wanted

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

where is the more detailed supported documented about how it works and what features it supports and how to use it.

If you want to know the features which FATE support, you can read the RELEASE.md file.
In the example module,  we give some examples and documents which told how to use.
In the federatedml modules，we also add some READEME.md file in some algorithms sub-modules.
If you have any other confusions, please tell us.
thanks

ok, thanks.


Fix Circular Reference Issue and Ensure Correct Path for Chromium Build

@r0-negative
Please resolve the Change request


Menssages

Subject: Menssages
Description:
When I write, the message despairs and is not delivered.
Results:
Backend version: develop-d6739683
Frontend version:
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/messages/request/39584
User: yanara824 (25356)

can't repro


Trash dir

Hi,
I was recently looking for a way to locate the user’s trash directory and noticed that some issues here mentioned trash, but that this didn’t seem to be present in this library. However, it seems that trash_dir is still in lib.rs, just that it is commented out. Assuming that this was once provided by this library, would it be possible to restore this feature?
Thanks.

Hi Aramis,
the problem is that Windows' trash folder doesn't have a "real" path that we can return to the user, see: https://github.com/soc/directories-rs/issues/18
As there doesn't seem to be a consistent way to return this directory on all supported platforms (and there is usually not a per-user trash directory, but a per-disk one), the decision was made to not offer this API here.

Since this library returns Optionss of values, couldn’t you return None on those platforms that don’t support locating trash? Or is it that all supported platforms don’t support locating trash.
AFAIK and FWIW trash on macOS is always $HOME/.Trash, and on (some?) Linux distros it’s $XDG_DATA_DIR/Trash. This is just from a quick Google and you’ve probably done way more research than me on this though.

My concern is that it would confuse the reasons why one might get a None.
Without trash, it's basically "this OS does not have this dir"; if we added trash, it would add "the OS might have this dir, but we can't give you a path to it" as a second reason to return None.

Ah, I see now. Thanks. Should I close this issue?

I'd propose we keep this open for a week and figure out whether we can collect additional pros/cons; after that I'll make a decision based on hopefully more information. :-)

Sounds good 👍


App will not execute if could via the terminal

I already add the golang workspace bin director to my environment variable. Then executing it on the cmd or powershell will work as expected but using this terminal will cause ObjectNotFound.
Please the uploaded image

BTW I am just starting learning using the atom editor.
Thanks

sorry for my ignorant I just restarted my laptop and everything seem to work fine.


Re-implementation of unsupervised saliency detection

Hi, thanks for the interesting work!
I can not gain the results of "TokenCut + BS" as reported in the paper.
E.g., I gain "ECSSD: IoU (0.621), Acc (0.891), F-max (0.751)" , which are much lower than ones claimed.
As for "TokenCut", I have gained the same results, so I guess the problems may occur at "bilateral solver". Could you please check and update the codes?
Thanks in advance!
Best,

Hi Jun Pu,
Thank you for your interest. I have rechecked the current version. Here is the results that I get:
(tokencut)TokenCut/unsupervised_saliency_detection$ python get_saliency.py --out-dir ECSSD --sigma-spatial 16 --sigma-luma 16 --sigma-chroma 8 --nb-vis 1 --vit-arch small --patch-size 16 --dataset ECSSD
Namespace(dataset='ECSSD', img_path=None, nb_vis=1, out_dir='ECSSD', patch_size=16, sigma_chroma=8.0, sigma_luma=16.0, sigma_spatial=16.0, tau=0.2, vit_arch='small', vit_feat='k')
Loading weight from /dino/dino_deitsmall16_pretrain/dino_deitsmall16_pretrain.pth
Load small pre-trained feature...

TokenCut evaluation:
{'IoU': 0.7119671522730496, 'accuracy': 0.9178118275292217, 'F_max': 0.8034312725067139}
TokenCut + bilateral solver evaluation:
{'IoU': 0.7720177292864828, 'accuracy': 0.9341852449579164, 'F_max': 0.8735781311988831}

Perhaps there is an incompatible library version on your environment? Can you share your conda environment?
Best,
Yangtao

Ohlala~thanks so much for the quick reply and for reminding the environments! I have upgraded the "scipy" package from version 1.7.3 to version 1.9.2, and the problem has been solved! Note that I am using anaconda3.
Originally, I gained:
/home/yzhang1/anaconda3/bin/python3.8 /home/yzhang1/PythonProjects/TokenCut_bilateral/get_saliency.py
Namespace(dataset='ECSSD', img_path=None, nb_vis=1, out_dir='ECSSD', patch_size=16, sigma_chroma=8,
sigma_luma=16, sigma_spatial=16, tau=0.2, vit_arch='small', vit_feat='k')
Loading weight from /home/yzhang1/PythonProjects/TokenCut_bilateral/dino_pretrains/dino_deitsmall16_pretrain.pth
Load small pre-trained feature...
ECSSD
args.out_dir: ECSSD, img_name: 0001.jpg

100%|██████████| 1000/1000 [05:27<00:00,  3.05it/s]
TokenCut evaluation:
{'IoU': 0.7129746048355009, 'accuracy': 0.918353023160249, 'F_max': 0.8046749234199524}

TokenCut + bilateral solver evaluation:
{'IoU': 0.6214015735024441, 'accuracy': 0.891019322630018, 'F_max': 0.7509733438491821}
Process finished with exit code 0

After upgrading "scipy" package to the newest version, I gained:
TokenCut evaluation:
{'IoU': 0.7119671522730496, 'accuracy': 0.9178118275292217, 'F_max': 0.8034312725067139}

TokenCut + bilateral solver evaluation:
{'IoU': 0.7720177292864828, 'accuracy': 0.9341852449579164, 'F_max': 0.8735781311988831}

Thanks so much for the work!
Best,
Jun-Pu

To supplement, I have also conducted some little adjustments according to your pseudo-codes
The results upon "ECSSD" are as follows:
TokenCut evaluation:
{'IoU': 0.7125319285520818, 'accuracy': 0.9178285121507943, 'F_max': 0.804131031036377}

TokenCut + bilateral solver evaluation:
{'IoU': 0.7725453542884497, 'accuracy': 0.934181008453481, 'F_max': 0.8743699193000793}

Again, thanks so much for the interesting & insightful work!
Best,
Jun-Pu


Avoid the pagerduty drill on bank holidays

Would the drill still start if https://www.gov.uk/bank-holidays.json isn’t available?

I'd hope so. I added the logic regarding bank holidays as a guard clause, rather than making creating the file conditional on the day not being a bank holiday for this reason.
Thanks for taking a look Bill :)