trouble downloading seqspark and I cant find seqspark.jar

I am having trouble downloading and building seqspark. The error I keep getting is SeqSpark.jar is not found. So If you can send me the file that would be great. Or let me know what I am doing wrong.
this is the error:
./install --prefix ~/software/seqspark --db-dir /jamesdh/691_project/seqspark
Use of uninitialized value $prefix in string eq at ./install line 34.
Use of uninitialized value $prefix in concatenation (.) or string at ./install line 43.
Use of uninitialized value $prefix in concatenation (.) or string at ./install line 53.
Will install into , database files will be downloaded to /jamesdh/691_project/seqspark
Building seqspark ...
sh: sbt: command not found
Finished building seqspark.
Cannot find target/scala-2.11/SeqSpark.jar, compiling failed? at ./install line 84, <$fh> line 48.
[jamesdh@dc01 seqspark]$ ./install seqspark-db
Use of uninitialized value $ENV{"USR"} in concatenation (.) or string at ./install line 48.
No db-dir specified, will use /user//seqspark.
Building seqspark ...
sh: sbt: command not found
Finished building seqspark.
Cannot find target/scala-2.11/SeqSpark.jar, compiling failed? at ./install line 84, <$fh> line 48.
[jamesdh@dc01 seqspark]$ ^C
[jamesdh@dc01 seqspark]$ dnf reinstall sbt
-bash: dnf: command not found
[jamesdh@dc01 seqspark]$ which sbt
which: no sbt in (/usr/local/sbin:/usr/local/bin:/usr/bin:/lab/bin:/opt/cuda/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)

Hi @dhynasah
I saw two problems here.
First, you don't have sbt on your machine. Could you please download it here: https://www.scala-sbt.org/
Second, the $prefix not initialized issue. May I know what OS/Distro and version are you using? The install script is just a perl script. Could you show me the perl version: perl --version.
Di

I am running this on my school account virtually through putty and I simulated a cluster through the school machines.  and I was just following your tutorial. https://statgenetics.github.io/seqspark/.
so are you saying I should use a different version of the script?

I mean I am not sure if the OS or the Perl version cause the $prefix issues. The script should work on most Linux distros with any Perl 5. So I want to know if you are using a mainstream Linux and Perl 5.
If you're working on a school cluster, you can ask the admin about the system/Perl versions, and if they can help you install the prerequisites.

Ok Finally I got someone to reply at my school The problem was they did not have sbt installed on the global system. They added it and then I was able to install seqspark. I did get a few warnings when it was installing because of the prefix errors. They didn't really answer my questions about that. but I think for the most part it's fine. thanks for the help!

Hi. So I am having trouble again. I had to skip over a few of the things in the tutorial. The reason in that my school doesn't have Hadoop installed. They have a "hadoop like system". in order to run my files on all of the spark nodes I launch spark first, and then run the file. But I am having trouble because I cannot use the Seqspark commands. I am in the directory where the demo.conf file is. So is there a way for me to configure my environment to have these commands? Any help you could provide will be greatly appreciated.

Have you added this line to your ~/.bashrc:
export PATH=~/software/seqspark/bin:$PATH
After doing this, execute bash or re-login.

Thanks! I definitely got somewhere. The commands are being recognized.  But I am now getting another error.
Error: seqspark no longer takes run mode option, please check the latest document.
Usage: seqspark conf [opts]
conf -- File containing the parameters
opts -- Spark options
what do I do in this situation?

Sorry about that. I guess you are trying to run the SingleStudy mode here. Just remove SingleStudy from the command line. I'll update the doc accordingly.

Thanks. That helped. I was able to get a little bit further. Although I keep running into more problems.
This is the error I am getting now:
[jamesdh@dc01 seqspark_files]$ seqspark demo.conf
conf file:       demo.conf
spark options:
19/04/05 12:27:49 WARN util.NativeCodeLoader: Unable to load native-hadoop libra                          ry for your platform... using builtin-java classes where applicable
19/04/05 12:27:49 WARN internal.Logging$class: Local jar /home/jamesdh/seqspark/                          SeqSpark.jar does not exist, skipping.
19/04/05 12:27:49 WARN internal.Logging$class: Failed to load org.dizhang.seqspa                          rk.SeqSpark.
java.lang.ClassNotFoundException: org.dizhang.seqspark.SeqSpark
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at org.apache.spark.util.Utils$.classForName(Utils.scala:238)
at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubm                          it$$runMain(SparkSubmit.scala:810)
at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:167                          )
at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:195)
at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:86)
at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scal                          a:924)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:933)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
it doesn't make sense because the SesSpark.jar file is here. Should I specify the path or something...although im not sure how to do that.
and then the org.dizhand.seqspark.SeqSpark...i dont know what that error means. im not sure if that is supposed to be a file, or if its something else... i looked for it and couldn't find it.

I noticed an extra space between ${SPARK_HOME} and SeqSpark.jar. Could you check the seqspark script? It is a bash script located at ${SPARK_HOME}/bin. If you are not certain, run this command and paste the output: ```cat `which seqspark````

#!/usr/bin/env bash
Usage() {
echo "Usage: seqspark conf [opts]                  "
echo "  conf -- File containing the parameters     "
echo "  opts -- Spark options                      "
}
if [[ -z $1 ]]
then
echo "Error: you must specify the conf file"
Usage
exit
fi
if [ "$1" == "SingleStudy" ] || [ "$1" == "MetaAnalysis" ]
then
echo "Error: seqspark no longer takes run mode option, please check the latest document."
Usage
exit
fi
Conf=$1
shift
Opts=$@
if [ -z $SEQSPARK_HOME ]
then
SEQSPARK_HOME=$(dirname $(dirname $0))
fi
CONFDIR=${SEQSPARK_HOME}/conf
echo "conf file:       $Conf"
echo "spark options:   $Opts"
spark-submit --driver-class-path $CONFDIR
--class org.dizhang.seqspark.SeqSpark $Opts
$SEQSPARK_HOME/SeqSpark.jar $Conf
exit 0

Looks fine. This script does nothing but prepares the classpath for java. Could you try to run the command manually like this:
spark-submit --driver-class-path /home/jamesdh/seqspark/conf --class org.dizhang.seqspark.SeqSpark /home/jamesdh/seqspark/SeqSpark.jar demo.conf

I tried it and I am still getting the same error. should I reinstall spark? maybe that's the problem. Also I moved my spark into the seqspark directory because the spark submit commands were not recognized in that directory. and then I added this to my bash file:
export PATH=~/seqspark/spark/bin:$PATH
but this was before I had the current error.

I'm not sure if you can move around Spark. Also, Spark should be installed and configured on both the master node and the worker nodes. If all you want is to find the spark-submit, you can just add the Spark bin to PATH like this: export PATH=/path/to/spark/bin:$PATH.
For seqspark, could you check this: ls /home/jamesdh/seqspark/SeqSpark.jar. Or cd /home/jamesdh/seqspark and ls to check if the SeqSpark.jar file is still there.

Are you using this on a single machine or in a cluster? I'll try to build a docker image for testing purposes later.

oh, shoot ok. I'll move spark back to its original location. it's on a cluster.  with 24 nodes. Ok let me try some of the things you suggested. and I will get back to you.

ok. so i am getting no such file or directory for the SeqSpark.jar file. and Then I decided to just check spark to see if its running properly. and im not sure that it is... I dont think so. I ran this wordcount.py script i wrote for a homework assignment a while ago. But I think moving around the directory might have screwed things up.   An error occurred while calling None.org.apache.spark.api.java.JavaSparkContext....definitely something is wrong here. And it ended up shutting itself down without printing out the output.

I did ls /home/jamesdh/seqspark/target/scala-2.11
seqSpark.jar is in this directory.... so im not sure whats going on. and why i couldn't find it earlier.

Have you successfully run the install script? You cannot use the source code directory as the prefix.
The source code and the installed software must be in different places.
If you git cloned seqspark to /home/jamesdh/seqspark, you must use another place for the prefix, and add the installed place to PATH.
For exmaple, if you install --prefix /home/jamesdh/software/seqspark ..., you should export PATH=/home/jamesdh/software/seqspark/bin:$PATH

Trying to run the seqspark script in the source code directory will lead to the SeqSpark.jar Not Found error. And It will be invoked if you accidentally exported the source code bin directory to PATH.

Have you successfully run the install script? You cannot use the source code directory as the prefix.
The source code and the installed software must be in different places.
If you git cloned seqspark to /home/jamesdh/seqspark, you must use another place for the prefix, and add the installed place to PATH.
For exmaple, if you install --prefix /home/jamesdh/software/seqspark ..., you should export PATH=/home/jamesdh/software/seqspark/bin:$PATH

Yes. I did run the install script. After the admin added sbt.
second, I created a directory called seqspark_files. its not directly in the source code directory but it is in the seqspark directory.  /home/jamesdh/seqspark/seqspark_files. Where should I run it instead?

You mean you've used --prefix /home/jamesdh/seqspark/seqspark_files? Then you need to export PATH=/home/jamesdh/software/seqspark/seqspark_files/bin:$PATH. The script seqspark will just try to find the SeqSpark.jar in its parent folder.

no matter what I do I still get the same error. if i use export PATH=~/seqspark/bin:$PATH or if i use export PATH=~/home/jamesdh/seqspark/bin:$PATH.
when I use the latter the seqspark command is not recognized.  I can run it in the parent directory or in any subdirectories and I still get the same error.
I tried placing export PATH=~/home/jamesdh/seqspark/target/scala-2.11:$PATH into my bash file. and I still get the same error.
I also tried export PATH=~/seqspark/target/scala-2.11:$PATH. that didn't work either.
Thanks for all of your help. Honestly, I appreciate it.

I also added export PATH=~/seqspark:$PATH.

So I added export PATH=~/seqspark/bin:$PATH
this is what i get back when I echo $PATH
/home/jamesdh/seqspark:/home/jamesdh/spark/sbin:/home/jamesdh/spark/bin:/home/jamesdh/seqspark/bin:/home/jamesdh/seqspark/target/scala-2.11:/home/jamesdh/spark/sbin:/home/jamesdh/spark/bin:/home/jamesdh/seqspark/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/lab/bin:/opt/cuda/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

Ok, I ended up moving the SeqSpark.jar to the main seqspark directory and out of the target/scala_2.11 directory. and now it seems to work a little better.
now I'm getting this error:
Exception in thread "main" com.typesafe.config.ConfigException$Parse: reference.                                  conf: 5: Key 'dbDir_unset' may not be followed by token: 'annotation' (if you intended 'annotation' to be part of the value for 'dbDir_unset', try enclosing the                                   value in double quotes)
it will still run, but I am not getting an output folder.
I am assuming this means I did something wrong in the demo.conf file. I will double check that and make sure I didn't miss something from the tutorial.

Sorry for not being clear enough. Could you please tell me where your source code is and what you used for --prefix? The problem is the seqspark script in the source code bin folder should never be called directly.
Then could you try to start over again?

Clear the PATH, remove the lines you did for seqspark and re-login;
Make sure the source code of seqspark is in some folder. e.g. ~/software/seqspark
run the install script with some --prefix. This prefix shouldn't be the source code path. That means if your source code is in ~/software/seqspark, you must use another path for the prefix which will become your $SEQSPARK_HOME. e.g. ~/seqspark
Export the PATH env variable: export PATH=~/seqspark/bin:$PATH if your prefix is ~/seqspark.

Notes:

Do not use the source code path as the prefix. Actually, you'll see error messages if you do so.
If you installed the source code to the prefix without a problem, you don't need to move the built jar file around. The install script does something else (sets up the conf) besides copy the jar and bash script to the prefix.
Remove the source code bin dir from PATH.

Let me know if you still have any difficulties.

yes. I remember. last time I downloaded this I didn't use --prefix because --prefix was not one of the available options. I can't remember exactly how I did it. But I think I just skipped that and used install and only one path. Now I understand where I went wrong. That's been the source of all of my problems.
These are the options given for install:
`This install program copies files (often just compiled) into destination
locations you choose.  If you want to download and install a ready-to-use
package on a GNU/Linux system, you should instead be using a package manager
like yum(1) or apt-get(1).
In the first three forms, copy SOURCE to DEST or multiple SOURCE(s) to
the existing DIRECTORY, while setting permission modes and owner/group.
In the 4th form, create all components of the given DIRECTORY(ies).
Mandatory arguments to long options are mandatory for short options too.
--backup[=CONTROL]  make a backup of each existing destination file
-b                  like --backup but does not accept an argument
-c                  (ignored)
-C, --compare       compare each pair of source and destination files, and
in some cases, do not modify the destination at all
-d, --directory     treat all arguments as directory names; create all
components of the specified directories
-D                  create all leading components of DEST except the last,
or all components of --target-directory,
then copy SOURCE to DEST
-g, --group=GROUP   set group ownership, instead of process' current group
-m, --mode=MODE     set permission mode (as in chmod), instead of rwxr-xr-x
-o, --owner=OWNER   set ownership (super-user only)
-p, --preserve-timestamps   apply access/modification times of SOURCE files
to corresponding destination files
-s, --strip         strip symbol tables
--strip-program=PROGRAM  program used to strip binaries
-S, --suffix=SUFFIX  override the usual backup suffix
-t, --target-directory=DIRECTORY  copy all SOURCE arguments into DIRECTORY
-T, --no-target-directory  treat DEST as a normal file
-v, --verbose       print the name of each directory as it is created
--preserve-context  preserve SELinux security context
-Z                      set SELinux security context of destination
file and each created directory to default type
--context[=CTX]     like -Z, or if CTX is specified then set the
SELinux or SMACK security context to CTX
--help     display this help and exit
--version  output version information and exit
The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX.
The version control method may be selected via the --backup option or through
the VERSION_CONTROL environment variable.  Here are the values:
none, off       never make backups (even if --backup is given)
numbered, t     make numbered backups
existing, nil   numbered if numbered backups exist, simple otherwise
simple, never   always make simple backups
GNU coreutils online help: https://www.gnu.org/software/coreutils/
Full documentation at: https://www.gnu.org/software/coreutils/install
`

i tired:
install -t ~/software/seqspark --db-dir /home/jamesdh/seqspark
--db-dir is not recognized either.

So, I ended up just completely starting over. When you say, make sure the source code is in the same folder, what do you mean? the same folder as what?
then i should run the install script with some prefix. so should i run it as :
seqspark$ ./install --prefix ~/software/seqspark --db-dir /home/jamesdh/seqspark
because when I do this it says seqspark$ command not found...
if i do just ./install --prefix ~/software/seqspark --db-dir /home/jamesdh/seqspark
then it says install: no such file or directory.
Is it possible for me to give you my login so you can figure it out? I can give you my email address.
I am really desperate to just have this working properly.

It's "some" folder not "same".
no problem, I can help you install it.
But make sure just email me a temporary login cred so that you can change after I finish.
zhangdi.devel[at]gmail.com

I sent you an email. my email is<EMAIL_ADDRESS>


Limit name length to 50 characters

Updated the ParserUtil to check if the name length is longer than 50 characters.
Throws a ParserUtil if so.

LGTM


No Shared Framework Schemes via Carthage Install

Keep getting the following when trying to build via Carthage
Dependency "mixpanel-iphone" has no shared framework schemes
If you believe this to be an error, please file an issue with the maintainers at https://github.com/mixpanel/mixpanel-iphone/issues/new

It looks like Mixpanel 2.8.3 with Carthage support is not officially out yet.  You'll need to use the branch syntax in your cartfile until 2.8.3 is released, like so:
github "mixpanel/mixpanel-iphone" "master"
The following syntax is the release syntax, which looks in the official releases, which is only 2.8.2 so far.
github "mixpanel/mixpanel-iphone"

@simX thanks for helping out on this one. We'll get a proper release out this week!

@katoree @simX New release (2.8.3) is out.


Change sig-docs-xx-reviewers to -reviews in docs

Although (owners, reviews) is weird to me, it's the current group name.
In k/org GitHub teams:

sig-docs-leads
sig-docs-en-owners
sig-docs-en-reviews
sig-docs-zh-owners
sig-docs-zh-reviews

In k/website OWNERS_ALIASES:

sig-docs-leads
sig-docs-en-owners
sig-docs-en-reviews
sig-docs-zh-owners
sig-docs-zh-reviews
sig-docs-blog-owners
sig-docs-blog-reviewers

This PR looks very practical

/lgtm
/approve


Heating climate without data

The climate.luxtronik2_domestic_water entity shows this nice graph ❤

Unfortunately, the climate.luxtronik2_heating entity looks like being without data 😢

Don't you please know what could be wrong? Also, please note that all the statuses (e.g. sensor.luxtronik2_status) and temperatures get the right data.

Just a note, the above merge request does not fix it for me, I have roughly the same issue with something weird on the heating target temperature after updating the integration:

I've just noticed that now instead of picking up the set temperature (in my case 21 degrees) it now picks the temperature correction. This is visibile also directly from the entity climate.luxtronik_heating which no longer displays the wanted temperature:

I've just noticed that now instead of picking up the set temperature (in my case 21 degrees) it now picks the temperature correction. This is visibile also directly from the entity climate.luxtronik_heating which no longer displays the wanted temperature:

Previously, you could change the heating target temperature with the climate control, but it didn't actually change anything on the Luxtronik. In order to get to a real climate-control, I needed to pick a sensor that controls the temperature of the heatpump. For me, the main sensor to choose was therefore the temperature correction.
Do you know another sensor that can be used to control the heating behavior of the heatpump, but better 'reflects' the heating target temperature?

Just a note, the above merge request does not fix it for me

The "heating current temperature" will show the value of the sensor that you configured.
In your graph, no "Heating current temperature" line is visible. My hypothesis would be that you did not configure which sensor to display.
What sensor did you enter when you select "configure" on the integration?
I used sensor.luxtronik2_room_temperature to use the RBE room temperature sensor. If you don't have a RBE wall unit, you must select another sensor that reflects the current room temperature.

Previously, you could change the heating target temperature with the climate control, but it didn't actually change anything on the Luxtronik. In order to get to a real climate-control, I needed to pick a sensor that controls the temperature of the heatpump. For me, the main sensor to choose was therefore the temperature correction. Do you know another sensor that can be used to control the heating behavior of the heatpump, but better 'reflects' the heating target temperature?

Ok I was not aware of this, I did not change the target temperature since integrating the Heat Pump in home assistant, so I never noticed it did not do anything. I understand the point but is now completely confusing. In my opinion it was better before.
I've added the room sensor id to the configuration, so of course now I get this:

And the "-1" is both the adjustment temperature and the "target temperature", which does not match at all with the description. It looks like the temperature being read is just wrong. In both current and previous case you could still adjust with luxtronik2_heating_temperature_correction.

I agree the naming now is confusing.
To reduce the confusion we should rename "Heating targer temperature" into "Heating target correction".
Do you have an RBE wall-unit that allows you to set the target room temperature?

Unfortunately no. Bought this house in 2020, heatpump was already installed. I updated the firmware myself, reconfigured stuff, tuned, brought network to the Luxtronik controller. etc. but it's still far from being manageable.
Rant mode on
The included web interface is a joke, very limited, the frontpage-inspired heatpump24 portal is just terrible, the app sucks. In these 3 different interfaces I can configure different things but not everything in one place. At this point, I would say this home assistant integration lets me do more than these 3 combined, barring for schedule (with negative schedule on the controller for warm water, but not reflected in the app/heatpump24, go figure)
Rant mode off
This friday I have appointment with a technician for a check and I will ask if I can upgrade the controller to something less stupid, a room sensor and let me check power consumption through the home assistant integration (https://github.com/BenPru/luxtronik/issues/18) as I'm trying to squeeze in the consumption with my Tesla powerwalls / Enphase solar installation.

My hypothesis would be that you did not configure which sensor to display. What sensor did you enter when you select "configure" on the integration? I used sensor.luxtronik2_room_temperature to use the RBE room temperature sensor. If you don't have a RBE wall unit, you must select another sensor that reflects the current room temperature.

Can we have the maybe-installed RBE sensor as the default pre-filled in the field when configuring the integration? Or in the text above.

My hypothesis would be that you did not configure which sensor to display. What sensor did you enter when you select "configure" on the integration? I used sensor.luxtronik2_room_temperature to use the RBE room temperature sensor. If you don't have a RBE wall unit, you must select another sensor that reflects the current room temperature.

Can we have the maybe-installed RBE sensor as the default pre-filled in the field when configuring the integration? Or in the text above.

I have added this as pre filled default.

Many thanks!

I think the current HA thermostat implementation is not suitable for heating systems where you can only adjust the control loop. It expects a target temperature, not a correction.

Hello, please note I have the same issue as @rhammen , so after updating to the latest version of HA integration, the Heating target temperature went to 0 😢

Hello, please note I have the same issue as @rhammen , so after updating to the latest version of HA integration, the Heating target temperature went to 0 😢

To be clear: I changed this in the code, and on purpose 😃
I did this because previously you could change the value, but it did not change anything on the heatpump.
That felt like not being really usefull... 😄
In the current implementation, if you change it to a value > 0, the heatpump will (should?) increase the water tempeature.
And similarly it will (should?) decrease the water temperature if you change it to a value < 0.
So now the "dial" does function, but as a "temperature correction", not as a "target temperature".
I agree this is different as before and confusing,  and I will try to turn it into a functioning thermostat, based on a "target temperature".
I hope to have something for a "beta-test" in the next couple of weeks.
If you want to comment / discuss its implementation, let's do it in issue #3

So if I understand it correctly, the thermometer panel for heating is not finished yet, and will be finished as part of #3, so we could close this issue, right?

So if I understand it correctly, the thermometer panel for heating is not finished yet, and will be finished as part of #3, so we could close this issue, right?

I understood this Issue as being: "Heating current temperature" line does not show, and "Heating heating" does not show.
That has both been fixed, BUT...
.. you need to configure which temperature sensor to show!
In your graph there is still no line for "Heating current temperature" and "Heating heating", which suggest you didn't configure a temperature sensor.
You need to go to Settings-->Devices-->Integrations, and press "Configure" on the Luxtronik tile. There you enter the sensor to use as "Room temperature sensor". If you have a wall-unit, you can use 'sensor.luxtronik2_room_temperature' (without '''). If you don't have a wall-unit, you will have to enter another sensor temperature sensor.
Once configured, the graph should be similar to the domestic heating graph you showed in your first post.
Because this part has been fixed, I think this issue can be closed.
The "Heating target temperature" does show, but is currently implemented as "Heating correction"., which is confusing.
I intend to change that in the future as part of #3

Thank you very much, I wasn't aware of this option. I entered there sensor.luxtronik2_flow_out_temperature_target (because I don't have a room temperature sensor yet) and its value is shown on the panel, and also the Heating heating is shown 🎉


Plugin settings broken.

My env

Obsidian version: 1.0.0
OS: macOS 12.6

Issue

selecting plugin does not work.
selecting command does not work.

Sadly this seems to be the case with many plugins. I can't complain too much. After all, there are a lot of new features and fixes, albeit many of the new features have introduced other, new bugs, but it's not the end of the world. As for me, I'm just going to uninstall and install 0.15.9 again, then wait till 1.0.0 is more "stable". But yeah, doubleshift is by far one of my favorite plugins, so I hear you. Of course, it's not our homie Qwyntex' fault; he rocks. But thx for adding the issue so it can be resolved. And knowing Qwyntex, it will be resolved real soon. :D

I have just tried it and it seems to be working alright. If the issue consists please provide more information on how to recreate it. Otherwise just close the issue

Sorry, I should have elaborated more on reproducing bug.

The issue should now be fixed. Please update to the newest plugin version. Should any new issues arise due to me updating to a new API version please report them.

As always, you are my HERO, Qwyntex! Thanks for everything! 👍🏻

For what it's worth: I had to fully uninstall and reinstall doubleshift plugin in order to fix absence of plugin-specific commands in doubleshift settings.
Note that I had updated the plugin today, and verified the above was not functioning, prior to my reinstallation of doubleshift.
Thanks for the plugin btw 😃


Fix version bump to support also #patch (and #major?)

The release workflow seems to ignore the version level tags.
v1.2.0 should have been v1.1.1

The version string (#major, #minor, #patch, #none) need to go into commit messages, not into the PR description.
Although I would have also preferred the latter, the GitHub action we use to compute the new version does not have any settings to change that.
One benefit of the current solution is that it allows to change versions in each commit of a PR and the action will combine these into a single version bump using some logic.
It's not 100% what we want but I'd say it is good enough, therefore I will close this issue.


move page from user-data to main message

fixing issue AGPUSH-1143

Hey Erik, how can I test this? Is it possible to verify that a quickstart works as expected?

Yeah that will be enough after 'clicking' the notification the app should launch the specified page... e.g. "page": "/MainPage.xaml"

:eyes:

Hey Erik, sorry for the verification taking so long, I'm back to it now.
I have tried it with Cordova app and it works, I've just observed this (potentially wrong) behavior:

when I send the message from the UPS console, it is sent with "page: null" - when I open the notification from the notification bar on WP8.1, the cordova app opens (no notification is delivered to the app), but when I send another push message, notification is handled correctly and shown in the list of incoming messages

but when I specify "page: cordova", first message that I send opens the cordova app; second notification closes it. here is the full message body:

{
    "message": {
        "alert": "wef",
        "sound": "default",
        "badge": -1,
        "page": "cordova",
        "action-category": null,
        "content-available": false,
        "user-data": {},
        "simple-push": "version=1422466229679"
    },
    "criteria": {
        "categories": null,
        "variants": null,
        "alias": null,
        "deviceType": null
    },
    "config": {
        "ttl": -1
    }
}

So on windows the notification received when the app is in the background only wakes up the app. What you can do is specify which page to start when the app is woken up with and additionally you can give some launch parameters. So to have a unified experience I've added this page parameter to the message. It will invoke your page and create launch param with the entire message, in case of cordova the plugin has a special page that will invoke the JavaScript once it's been loaded. So the behavior you describe in point one is completely expected.
I'll test the second one that seems wrong.

@lfryc fixed the second part. It was sending a launch param that was null, that crashed the app only in foreground.

Awesome, thanks Erik, I'll take a look later at the evening as I get to
win-enabled box..
On Thu, Jan 29, 2015 at 1:27 PM, Erik Jan de Wit<EMAIL_ADDRESS>wrote:

@lfryc https://github.com/lfryc fixed the second part. It was sending a
launch param that was null, that crashed the app only in foreground.
—
Reply to this email directly or view it on GitHub
https://github.com/aerogear/aerogear-unifiedpush-server/pull/462#issuecomment-72016276
.

@lfryc can this get merged into master ?

:eyes:  looking at the fixes

Okay, cordova helloworld works fine, now. Thanks for a fix @edewit
I haven't verified this PR with a native WP8 app though.

Tested on the native HelloWorld :+1:

Thanks for checking @sebastienblanc , merging...

merge to master in progress

Merged: https://github.com/aerogear/aerogear-unifiedpush-server/commit/6d3c4b14816837c90dc980d45f1743f3f01659a5


Fix Ch4 Ex3 instructions to match solution

I tried matching as {"IS_DIGIT": True, "OP": "?"} but this was not accepted. Also, {"IS_DIGIT": True} is the pattern pre-filled for the following exercise.

Thanks! Can't believe I missed this!


Trailing Slash For Directories

Thanks for this plugin!
I think it is good/best practice to add a trailing slash to entries which denote a directory. Would be cool if this would be done automatically.

PRs are welcome :)
Don't know what the modman 'spec' says or what is the expected behavior?

Will see if I have the time, but does not look good at the moment :/
I think there is no official statement regarding this, but I think it is best practice, because then you see what entry is supposed to be a directory. From what I see, most people stick to that rule.


what's the training resource？

Can you explain the training resource? It seems omitted in the paper.

The data are introduced in Appendix A. I will introduce more details about this part in a revised version (maybe updated in two days).

Can you explain the training resource? It seems omitted in the paper.

We collected about 30 million text-image pairs from multiple channels, and built a 2.5TB new
dataset (after the data was processed into tokens, the size becomes about 250GB). The data are an
extension of project WudaoCorpora
About 50% of the text is in English, including Conceptual
Captions [42]. They are translated into Chinese by machine translation. In addition, we did not
remove the watermarks and white edges in the dataset even though they affect the quality of generated
images, because we think it will not influence the conclusions of our paper from the perspective of
research.

Hi @gaopengcuhk. We have updated the introduction of data in the Appendix A of the paper, which is also quoted by @johnpaulbin .


Add Decimal256 sqllogictests for SUM and MEDIAN aggregate expressions

Which issue does this PR close?

Closes #7888.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

should we also add tests for AVG, MIN/MAX, COUNT?

Yea, they are already added.

Oh, count isn't. I just added it.

Thanks @viirya

Thank you @Dandandan @alamb @comphead


feat(CI): introduce

Description
Introduce CI to allow us to see if all things is correct.
I had add a new label. Why ? it's allow us to trigger the ci when we need it instead of each commit push.
Documentation about CI is missing.
Validation
CI should represent what is expected. And CI should pass
Related Issues
No related Issues
Check List

[X] I have formatted using npx turbo format
[X] I have checked the types using npx turbo type-check
[X] I have tested the build using npx turbo build

will it work ???

Cross the finger 🤞


bdist_nuitka: Allow passing extra nuitka options from setup.py

Adds the ability to pass any extra options to nuitka when used in bdist_nuitka.
Eg:
setup.py
from setuptools import setup

setup(
    name='mypackage',
    packages=['mypackage']
    options={
        'nuitka': {'recurse-not-to': ['mypackage.ui.assays'],
                   'plugin-enable': ['qt-plugins'],
                   'no-pyi-file': None}
    },
    build_with_nuitka=True
)

TODO: Documentation update is still required

So I assume this is generic, so key, value -> --key=value unless value is None. Maybe it is worth, to reconsider how to handle booleans. Having --pyi-file and --no-pyi-file both in nuitka/Options and them working together, could allow to handle booleans like "py-file" : True in a generic way. For False we would prefix the name with "no" simply.
The one thing I really miss most about this is tests though. Like a hello world setuptools program and module, and we show the use cases. It will take creating a virtualenv, running setup.py with and without build_with_nuitka=True and having a minimal thing work, and a show off thing work. Like something that inject an option to the nuitka key in setup.py and then shows it has intended effect or not.
I am willing to work on adding that myself though, shouldn't be all that much effort to get that started, then once I am happy with the interface, I think we should document it.

Yes I'm pretty sure you're understanding the logic the way it's intended, key=val or boolean.
I'm not sure there's a problem with how booleans are handled already, either they're added for true or omitted for false. Having to write None in the options block to signify a (true) boolean value is a bit ugly though, I'd be open to a more positive readable format to use.
Perhaps simply allowing the arg to be listed as True (instead of None) and still treat as boolean (as opposed to a string  to to treat as key/val). In this case if you set it to False the arg would be omitted.
You're absolutely right about the lack of tests.... sorry I'm terrible at rushing through functionality and not making the effort on tests if I'm not forced to.  I really do believe in the value of them, just not in the best of habits.
Stupid me often demonstrates the function working so don't get allowed the time to go and clean up / add tests.... again, bad habits.
Everything I've contributed recently has been like this, I should have taken this as the warning it was: https://github.com/kayhayen/Nuitka/pull/58
I should be able to make a first pass at a test today, perhaps we can build up coverage from there.

Hello Andrew,
can you rebase this, it is in conflict with other changes I made.
Yours,
Kay

I don't know where now, not too easy to  oversee, but you had asked if I wanted the other changes as well, I am fine with rebasing only.

Oh, I made the changes, should be all fixed and rebased.

Seems I missed the release :-( oh well, I've rebased again (cherry picked)

I am about to merge this, putting it through my tests. Hope you are OK if I squash the 2 commits of yours for noise reduction keeping your authorship intact though.
I will use this ones description to make another distutils test that indeed uses a plugin. The qt-plugin is a bad one, as it's not for compiled modules yet. I will try to find something more light weight, but actually I don't know what yet.

That sounds great thanks.
Yeah sorry I didn't figure out the test system enough to add a suitable unit test for any of these bdist features. If you can get something in place I'll certainly aim to add coverage to it for any related features.

If I am not mistaken, I actually merged this a while ago, sorry to keep it open for no reason.
No docs, no test though, I am lazy too.

Yes , I did see it merged thanks.
I've moved my ci away from git install to released version, working great!

I'm actually not. As much as I love the idea the couple of times I tried it I ran into difficulties fitting it into my CI workflow. I use gitlab-ci for everything, with different python versions running in parallel jobs. Eg. https://gitlab.com/alelec/hello_briefcase/blob/master/.gitlab-ci.yml


NIFI-6325 Adds support for AWS KMS Sensitive Property Provider.

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
The code in this change-set introduces a second Sensitive Property Provider called AWSKMSSensitivePropertyProvider that queries the AWS KMS API to encrypt and decrypt property values.  Noteworthy:

AWS SDK version bump to support KMS API
changes to support encryption scheme selection at run-time
minor package reorganization for better hierarchy
follow-on changes for encryptconfig, toolkits will happen with NIFI-6363

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

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

For code changes:

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

For documentation related changes:

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

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

Closing in favor of #3542.


PHP blade syntax produces error after format "->" becomes "- >"

Operating System (+Version): Windows 10
VS Code Version: 1.30.1
beautify Version: 1.4.7

NOTE: Please provide code snippets instead of screen shots. Your issue needs to be replicated, and we need the failing code (text) to do this.
Provide the settings you use:
(VS Code workspace and user settings, .jsbeautifyrc, .editorconfig)
eg.:
VS Code:
{
	"editor.formatOnSave": true
}

.jsbeautifyrc
{
	"max_preserve_newlines": 2,
	"preserve_newlines": true,
	"end_with_newline": true,
	"brace_style": "collapse-preserve-inline",
}

Action performed
Format html file with HookyQR.beautifyFile command
F1 + Beautify file + HTML
Expected results
Expected ... to ...
@foreach($employee -> services as $service) // Before: the blade php code in html template
Actual results
Details of what happened ...
@foreach($employee - > services as $service) // After: Blade php syntax error..

Try with the latest version. Seems to workout fine now. ;)

WOMM and no response from Issue opener.


chore: Remove aggregate-service-spi and move result classes to core-spi

What this PR changes/adds
Removes aggregate-service-spi and moves ServiceResult and ServiceFailure to core-spi`
Why it does that
Simplifies the dependency graph.
Linked Issue(s)
Closes #3577

We're currently processing your upload.  This comment will be updated when the results are available.


tea.Print[f/ln] does not wrap to a new line

When using tea.Print[f/ln] the text is too long and the terminal does not wrap to a new line.
The same string, fmt.Println output is normal, but this problem occurs when tea.Println is used for output

go env

GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/charlie/Library/Caches/go-build"
GOENV="/Users/charlie/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/charlie/dev/environment/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/charlie/dev/environment/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.19.1/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.19.1/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.19.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/charlie/dev/go/transerver/cli/go.mod"
GOWORK="/Users/charlie/dev/go/transerver/go.work"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/29/61lvvzb95pq774dthcv3rhnh0000gn/T/go-build1132523527=/tmp/go-build -gno-record-gcc-switches -fno-common"

OS: macOS 12.6
Terminal: kitty / mac's own terminal
type model struct {
	spinner spinner.Model
	done    bool
}

func (m *model) Init() tea.Cmd { return nil }

func (m *model) Update(tea.Msg) (tea.Model, tea.Cmd) {
	if m.done {
		return m, tea.Quit
	}
	return m, nil
}

func (m *model) View() string {
	if m.done {
		return ""
	}
	return m.spinner.View() + " Loading..."
 It means that you can build and ship to your users a binary that already has all the necessary files from your hard drive. So, there is no need to ship them separately and place them at a certain location on the computer. And the next time you move the binary to another directory, you do not need to update the paths to these files."
	style := lipgloss.NewStyle().MarginLeft(2).Bold(true).Underline(true).Foreground(lipgloss.Color("#B22222"))
	txt = style.Render(txt)
	s := spinner.New()
	s.Spinner = spinner.Points
	s.Style = SpinnerStyle
	m := &model{s, false}
	pg := tea.NewProgram(m)
	go func() {
		pg.Println(txt)
		m.done = true
	}()
	_ = pg.Start()

	println()
	fmt.Println(txt)
}

kitty's output:

mac's own terminal output:

@meowgorithm @muesli @Charliego93 I would like to work on this as part of Hacktoberfest 2022

@amoghrajesh Go ahead!

The one may be better left as an exercise to the user as “managed” Bubble Tea output doesn’t wrap by default. It’s fairly simple to look at WindowSizeMsg and wrap lines yourself if desired with Lip Gloss or Reflow.

Sure. Can you assign the issue to me?

@meowgorithm not very clear still. Can you elaborate?


Mistral

Hi,
Thank you for releasing this implementation! Do you have any plans to add support for Mistral 7B?
Thanks!

No plans but I can definitely try to, will let you know how it goes -- hopefully this week!

Thanks!

I attempted to add support for CausalLM models from HuggingFace which would include Mistral-7B on a separate branch (probably need to do some testing or wait till people try it out themselves).
I ran over a subset of the pg19 val set to verify, and found that the same 9 layers were deemed least important (different order). You can check that out here.
Hopefully this is what you were looking!

Cool! Thanks!


Follow latest pinning API

For rustc 1.30.0-nightly (20dc0c507 2018-09-19) and later.

Thanks, this looks great!

Note for anyone who lands here because futures-preview stopped compiling even with your old pinned nightly:
futures-preview does not pin its dep to exactly 0.1.0-alpha.2, so merging this change and releasing it as 0.1.0-alpha.3 does unfortunately break any user of futures-preview even if they'd pinned their rust toolchain to nightly-2018-09-19 (the last one before the std::future changes that broke pin-utils and futures-preview).
You have to pin the toolchain and your lockfile (after a cargo update -p 'pin-utils' --precise '0.1.0-alpha.2'). Such is nightly life, I suppose :)


How to handle async data

Hey awesome library.
Im wondering if theres a way to handle this as I can't see anything in the demo's sorry if its there.
Im fetching data from an api and populating the fields with that data.
An issue Im running into is because the data is not set instantly.
It does not update the values in the form making them invalid
so for example here the name should have the company name value

Is there a way to force an update after fetching from the Api

thank you!
no worries, It's probably still missing from the examples
Here are some suggestions

Cheers thanks for the response
I'll have have a play around and see if somethings works
I'll close this issue


NTR:  cAMP relay during early sorocarp development

I would like to add a child to the new Dicty term
GO:0140582 adenylate cyclase-activating G protein-coupled cAMP receptor signaling pathway
I would like to add a child that describes the cAMP relay
cell: cAMP biosynthetic process - > cAMP export to extracellular - > binds to cAMP receptor of other cells, which then activates adenylate cyclase to produce more cAMP and the signal is relayed, visible as waves in dark field microscopy; excited cells undergo a refractory period, also external PDE breaks down cAMP. All this generates 6 minute cAMP oscillations during aggregation.
GO:0140582 adenylate cyclase-activating G protein-coupled cAMP receptor signaling pathway
----  New term: cAMP relay during early sorocarp development (or cAMP signal relay...)
Def: cAMP induces other cells to produce cAMP which is part of 6 minute cAMP oscillations during aggregation in early sorocarp development.
sensu Dictyosteliia
thanks!

Hi @pfey03
The definition doesn't work- GO describes the function of gene products, this is phrased to describe the function of cAMP.
Isn't the cAMP relay a part of the 'adenylate cyclase-activating G protein-coupled cAMP receptor signaling pathway' ?
The new term is requested as a child of  GO:0140582 adenylate cyclase-activating G protein-coupled cAMP receptor signaling pathway, as if it was a type of adenylate cyclase-activating G protein-coupled cAMP receptor signaling pathway, but I think it's a part?
(We should chat at some point to resolve your open tickets).
Thanks, Pascale

Hi @pgaudet,
I know it's difficult and yes it's part of this signaling. Some of this is driven because I work a lot in UPHenO, and need to patternize all our phenotypes. I have already changed the pheno ontology so much, but some phenotypes I don't want to obsolete or change as phenotypes do describe these things in detail and the researchers do. And not all can be solved by new patterns. I have a new pattern to keep 'development arrests at developmental stage' (created stage ontology), as this also helped others.
It's super challenging so I sometimes try to get a new GO term that would retain the phenotypes, but often I have to change them and obsoleted a lot that were compound processes. I'm also planning to add extensions to phenotypes in new database but it's a not coming so soon. Just so you know where I'm coming from.
Thanks, Petra

@pgaudet what about 'cAMP wave formation' and something about relay in the def?

@pgaudet is this still going anywhere? there is no equivalent terms really as it's not simply the extracellular cAMP signaling and researchers differentiate

@pgaudet I don't think this is going anywhere I'm now trying to solve it otherwise. closing issue

The definition doesn't work- GO describes the function of gene products, this is phrased to describe the function of cAMP.

The biological processes @pfey03 is asking for involve the action (function) of multiple gene products.  They also involve physical processes, such as the diffusion of small molecules (cAMP), but don't many GO BPs?  The overall process is more than just signalling - that ignores the oscillations within single cells and the relay between cells and the gene product activity that underly them (https://www.youtube.com/watch?v=LJ98bkWZA40).

@dosumis - Yes of course it involves several gene products. And yes, it's signal and response to signal.
So then let's do a pattern that would help.

Lets keep it open then. (Sorry @pfey03 I have on my to-do list to answer to your tickets - I'm on ATPases this week, if I cannot answer today I'll do it Monday.
Thanks, Pascale

@pgaudet, thank you!

+[Term]
+id: GO:0140676
+name: cAMP oscillatory signaling
+namespace: biological_process
+def: "Fluctuation in the extracellular cAMP levels due to the alternate activation of adenylate cyclase, which produces cAMP, and phosphodiesterase, which degrades it. Occurs in Dictyostelium during early sorocarp development. Oscillation in signaling result is directional chemotaxis of cells towards the center of the aggregate."


Removed go1.3.3 support

fix #12549
Signed-off-by: Lorenzo Fontana<EMAIL_ADDRESS>

can you change your comment to fix # so it closes the ticket

@jfrazelle Yes no problem, I thought you wanted to keep it open to investigate further

ya no worries we can open a new one if so

LGTM ping @tianon

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove-go1.3.3-support" git@github.com:fntlnz/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

can you squash your commits into 1

https://docs.docker.com/project/review-pr/#update-an-existing-pull-request

@jfrazelle Done :)

LGTM


Missing resource flow_horizontalSeparator

Build Output:
AAPT: error: resource attr/flow_horizontalSeparator (aka com.google.samples.apps.sunflower:attr/flow_horizontalSeparator) not found.

    Android Studio 3.6 Canary 7
    // Sdk and tools
    compileSdkVersion = 28
    minSdkVersion = 19
    targetSdkVersion = 28

    // App dependencies
    appCompatVersion = '1.1.0-beta01'
    constraintLayoutVersion = '2.0.0-beta1'
    coreTestingVersion = '2.0.0'
    coroutinesVersion = "1.3.0-M2"
    espressoVersion = '3.1.1'
    fragmentVersion = '1.1.0-alpha09'
    glideVersion = '4.9.0'
    gradleVersion = '3.6.0-alpha07'
    gsonVersion = '2.8.2'
    junitVersion = '4.12'
    kotlinVersion = '1.3.41'
    ktlintVersion = '0.30.0'
    ktxVersion = '1.0.2'
    lifecycleVersion = '2.2.0-alpha01'
    materialVersion = '1.0.0'
    navigationVersion = '2.0.0'
    recyclerViewVersion = '1.1.0-alpha05'
    roomVersion = '2.1.0'
    runnerVersion = '1.0.1'
    truthVersion = '0.42'
    testExtJunit = '1.1.0'
    uiAutomatorVersion = '2.2.0'
    workVersion = '2.1.0'

@kamilj Thank you for the reported issue. After a little research I found this https://github.com/android/views-widgets-samples/issues/37

This is the relevant issue in the Google tracker https://issuetracker.google.com/issues/136103084
The recommendation for now is to either:

Downgrade Android Studio (3.6 alpha 2 works fine for me, alpha 3 creates this issue with ConstraintLayout 2 or any other library that uses attrs the old way)
Add the attrs that are missing to your project. When another version of ConstraintLayout library is released with the attrs included you'll have to remove them from your project.

I believe this issue should now be resolved if you're using Android Studio Arctic Fox


Always package whole Cargo project

In https://github.com/multiversx/mx-sdk-rust-contract-builder/pull/44, we allow one to optionally package the whole Cargo project. In the near future, we should forbid the alternative.
Impact: the packaged source code would be larger (with respect to the size of the codebase), but the dependencyDepth hints can be used by downstream applications to filter out some files. E.g. MultiversX Explorer already leverages dependencyDepth to filter files on the Verified Contract / Code tab.

Fixed by:

https://github.com/multiversx/mx-sdk-rust-contract-builder/pull/53 (V6)
https://github.com/multiversx/mx-sdk-rust-contract-builder/pull/52 (V5 LTS)
https://github.com/multiversx/mx-sdk-rust-contract-builder/pull/46 (V4 LTS)

Fixed by #61.


Add link to node.js extension

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks for contributing!


Create issue via email

Another Gitlab EE feature that would be nice to have in Gitea: https://docs.gitlab.com/ee/administration/incoming_email.html
This feature is blocking the service desk feature: #6219

I'd deploy is as a separate unit, and just create a support for creaing issues via API. Rationale is there can be a lot of sources to create an issue, and coupling the gitea with email recieving functionality seems unnesessarily specific. Consuming emails is a tricky thing, and it worth being a separate unit - maybe there is something we could utilize already.
Altough, I'm new here and I don't know how things are done.

As can be seen in the timeline, Gitea does now handle incoming emails. Though currently with the restriction "existing users replying to existing issues".
But it does mean it's now a much smaller step towards also accepting messages from addresses that don't belong to a registered user, and to have a repository-wide address that creates new issues/pull requests when messaged.
Running a single-user instance where I would like to be able to accept contributions without having to deal with registered users, I would love to see this.


How should I configure for this package running on different server?

I'm trying to figure out a way to make laravel-websockets work with Laravel Vapor. As of now, the only solution seems to be spinning out a new server in the same VPC as that of Vapor and make a connection to it.
So it will look like
--------VPC-----------------
[Main Server] ---WS---> [ Websockets Server ]
-----------------------------

The websockets server, in this case would need a new Laravel Installation running this package.
I'm wondering what are the configuration changes I'll have to make on the main server so that WS works as expected?
OR - is there any better approach?

Did you get it to work with Vapor?

Did you get it to work with Vapor?

The only appropriate way is to use a separate instance with the WebSocket server.


[dropdown] The shadow is no longer showing on the dropdown menu.

On a white background it looks like the menu items are not contained.

This should be fixed without me having to do anything new due to another issue. I'm going to get the site to redeploy and see

Hello 👋🏼 is there a particular version we should upgrade to for this fix?


Support calculate field for heatmap

Hi, in newer versions of Grafana if you want to use the Heatmap from Prometheus histogram you need to set the heatmap to "calculate": true, otherwise it does not work.
Could it be added to the heatmap options? :pray:

See documentation https://grafana.com/docs/grafana/latest/visualizations/heatmap/#calculate-from-data


Add a few more ArtifactBelongingTest tests

As @garath recommended in !34577, we could use an ArtifactBelongingTest confirming all vs2022 queues have the same VS workloads installed. (vs2017 and vs2019 queues seem to distinct VS workloads and we probably don't need to change that.)
In addition, we could enforce a few more consistencies between the VS queues in general.

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[x] Internal Infrastructure Improvements

Release Note Description
Added a few tests to ensure our VS workloads remain consistent going forward.

added in !34726. test-only and therefore not part of a rollout


fix: build error on fresh yarn.lock file

fix: this PR resolves the build error on fresh yarn.lock file.
some sub/deps might not be strictly following semver)
We may also .gitignore yarn.lock (optional)
Resolves #377

Sorry but we recently upgraded to the conventional commits standard. Please recommit the message according to the standard.

Sorry but we recently upgraded to the conventional commits standard. Please recommit the message according to the standard.

updated @pavlovcik

Sorry but we recently upgraded to the conventional commits standard. Please recommit the message according to the standard.

updated @pavlovcik

The CI checks the commit message not the PR name lol

Sorry but we recently upgraded to the conventional commits standard. Please recommit the message according to the standard.

updated @pavlovcik

The CI checks the commit messages not the PR name lol

Also updated the description as per the commit editor
I'm relatively new to conventional tooling :)

https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message

replacing this PR with another one.

delete this PR to avoid cluttering (#405 takes precedence)
@pavlovcik

delete this PR to avoid cluttering (#405 takes precedence) @pavlovcik

I'm not sure how to delete


Know a friend online simply

Description
I want to know who is online on my list friend( same steam friend), and i can invite him play game with me.
Context

[x] Unity
[ ] Unreal
[ ] Other

This was added in the 1.4.0 release.
You can now check the LastOnlineAt timestamp to see if it's non-zero. It will indicate whether the user is online. This is added to friends, group members, and bulk fetch of user records.


POKEMON_NAMES with FR

bug in names.py, when FR selected there is no POKEMON_NAMES values. Can't start web.py.

Sorry about that, fixed in 8a3b610c90eb9fc82b754bd1df82ab02c1e42ee7.


Quickbuy after scroll on product

Is your feature request related to a problem? Please describe.
There is no problem, just to convert more.
Describe the solution you'd like
If client pass through buy button, like he is going to saw a description, can show to him a block fix in the bottom with a small image, name, price and a button to buy, if has variation or can direct to product or show slot of variations too. But this in desktop. In mobile, i think that we have to show only a buy button.
Here is an example:
Mobile

Desktop

Esse aqui tinha na colcci e agora vi nesse aqui da vtex, esse é bala mesmo


Import issues on python > 3.7

For some reasons, using python > 3.7 makes abba fails on
from abba_python import abba
I do not know why.

I think this issue is not up to date anymore, I've had report than abba python runs well until python 3.10


Code redundancy g.imputeTimegaps and read.myacc.csv

Both g.imputeTimegaps (primarily used for ActiGraph) and read.myacc.csv (primarily used for ad-hoc csv formats) try to impute time gaps in the raw acceleration data.
It would be good if we avoided this code redundancy.

Great! Should we replace the c(0, 0, 1) for the last known value recorded in the previous chunk of data? That way the imputation method is consistent throughout the process.
And another question, in lines 39:43 of the same function, there is a normalization of the imputed data:
#  normalise last known value to 1
      i_normalise = which(x$gap != 1)
      if (length(i_normalise) > 0) {
        x[i_normalise, xyzCol] = x[i_normalise, xyzCol] / sqrt(rowSums(x[i_normalise, xyzCol]^2))
      }

Should this be done? The last recorded value is already a plausible value. When normalising it, we get many non-meaningful decimals and the dataset changes a bit (e.g., we get different results from processing an actigraph gt3x and an actigraph csv file). Should we avoid this step?

Great! Should we replace the c(0, 0, 1) for the last known value recorded in the previous chunk of data? That way the imputation method is consistent throughout the process.

Which line are you referring to? If it is the first sample in the recording then there is no previous chunk of data. So, make sure this also works when processing the first chunk in the recording.

Should this be done? The last recorded value is already a plausible value. When normalising it, we get many non-meaningful decimals and the dataset changes a bit

I did this because if there is large time gap then gravity must equal to 1 during that entire period (complete absence of movement). If the last recorded value does not have vector 1 then that is a plausible for imputing a longer time period.

(e.g., we get different results from processing an actigraph gt3x and an actigraph csv file).

Where do the differences come from? If it is an inconsistency in our own code then we need make this consistent such that both use the normalised value.

Which line are you referring to? If it is the first sample in the recording then there is no previous chunk of data. So, make sure this also works when processing the first chunk in the recording.

Yes, in case it occurs in the first chunk of data, then c(0, 0, 1) is still used.

Where do the differences come from?

Regarding the normalization, what I've found in my data is that the last epoch is always very close to 1 (e.g., EN=0.999585), which likely relate to calibration error. Actilife exports the csv dat with these gaps already imputed (copying the last recorded value). GGIR does not identify the idle sleep periods in the csv files because they are already imputed. So, if I process the csv file and the gt3x file of the same recording, the csv would not be normalised while the gt3x would be normalised.

ok, I see the problem. I think what we do is easier to justify.
I see two solutions:

Contact Actigraph and ask them to update their software.
Update GGIR as follows: Impute by last value => Check whether vector is less than 0.005 g different from 1 g (5 m_g_)
=> If yes, then normalise => If not, keep as it is. This assures that large errors are addressed.

Ok, I will contact ActiGraph and implement the point 2 as a temporary solution, does it sound good?

An update on this: I already solved the code redundancy and everything work fine. I was testing it in different files and found something I would like to discuss. When calibrating the signal, g.imputeTimegaps is used on ActiGraph csv files ro remove the zeros in the file in order not to affect the calibration. Now that GGIR uses the last observation carried forward, g.imputeTimegaps does not find the zeroes and the periods with the idle sleep mode are used in the calibration process. To be consistent with the gt3x files or any file with time gaps in which these periods are not imputed, we could:

Find periods with repeated values for more than 1 second in actigrap csv files and remove them to be reimputed in GGIR (g.calibrate would not re-impute them). I have tried this and in my files the calibration process run the "recalibration attempted but possibly not good enough" message (example file: cal error before = 0.02152, after: 0.00375).
OR reimpute the timegaps prior calibration with g.imputeTimegaps, but I'm not sure if this approach is reasonable. I have also tried this, and g.calibrate run the "recalibration done, no problems detected" message (example file: cal error before = 0.0171, after: 0.0046)

My understanding is that g.imputeTimegaps does not impute the time gaps in g.calibrate.R, because argument impute = FALSE. It should only removes zeros. Therefore, I am not sure the data are imputed before it arrives in the g.calibrate. Within GGIR the time gaps are only imputed in g.getmeta.R, but that is after the calibration procedure. The scenarios where we will encounter imputed raw data in g.calibrate is when the data is exported to csv from Actilife or for some ad-hoc .csv format data.
So, if you want to work on this then I think we can limit our effort to .csv data only. Agree?
A possibly faster solution is to let GGIR just search for all non-movement periods in the data as it is, and then at the end of that process we check whether many of the calibration sphere data points are identical (not similar but exactly the same for all decimal places). If we find many duplicated points then we can remove them. Computationally this may be faster then scanning the raw data for idle.sleep.mode and again for non-movement periods. To avoid risking to bias the data from other sensor brands we could limit this step to .csv data only.

I have been looking at this today, I applied the two possible solutions, below the results.
In brief, the current GGIR master github branch produces quite different calibration output if loading a gt3x or an actigraph csv (exported from actilife with the last observation carried forward). If we try to detect when the idle sleep mode has been activated and remove these points from the raw signal, we get very close calibration output to the gt3x file (but it takes longer, +6.5 vs 2.8 minutes). If we remove duplicates from the sphere as you suggested, the calibration output is still close enough to the gt3x file (and the processing time is not that different, 3.8 vs 2.8 min).
Any preferred approach?

 In that case let's go for option 2:

If we remove duplicates from the sphere as you suggested, the calibration output is still close enough to the gt3x file (and the processing time is not that different, 3.8 vs 2.8 min).

The differences may then come from the fact that GGIR tries to read 72 hours in total, which are different dependent on whether timegaps are included or excluded.

Heads-up: I just merged master branch into branch issue573_imputeTimeGaps.

@jhmigueles I am going through your progress, nice work. A few comments:

You used accelerometry::rle2 in g.imputeTimegaps. Would it be possible to replace this by the normal rle() function from R base? In that way we avoid having to add another package dependency.
I see you are exploring an alternative imputation approach with zoo::na.locf(x). If it works then good, but please keep an eye on processing speed. The way I implemented it was primarily because I could not find an alternative way to do the computation fast.
In files with many and/or large timegaps GGIR will struggle with memory. So, once the work in this branch is merged with master I think the next step could be to modify the code to skip gaps longer than 90 minutes, and only mark them for imputation at the metric (epoch) level. For example, we could do this by passing on the x$gap column to g.getmeta.

Thanks @vincentvanhees!

I tried this with the base rle function but I couldn't do it. Anyway, if we go for option 2 as you suggest we do not need the accelerometry::rle2. Sorry I have this option 2 only in a local branch in my computer, I will get it in github today.
Great, I will test the processing speed for that chunk of code in master and this branch and will use the fastest.
That sounds great, this will be the next step.


net45 dll contains net452 dll in nuget package

When I install the latest nuget package (2.0.1) I get an warning that my .net 4.5 project references a newer dependency (which is the NLog.Targets.ElasticSearch.dll). I've verified the path and it points to the net45 in the nuget Package.
C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3274: The primary reference "NLog.Targets.ElasticSearch" could not be resolved because it was built against the ".NETFramework,Version=v4.5.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.5".
The project file contains
<Reference Include="NLog.Targets.ElasticSearch">
    <HintPath>..\..\Packages\NLog.Targets.ElasticSearch.<IP_ADDRESS>\lib\net45\NLog.Targets.ElasticSearch.dll</HintPath>
    <Private>True</Private>
</Reference>

Thanks mistake from last upgrade. Corrected in 2.0.3, now live on Nuget


add how to Contribute

What changes were proposed in this pull request
Issue Number: close #3146

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

cc @wolfboys @RocMarshal

Prevent contributors from finding PR specifications at the beginning


Could you add an option to trimming polyT from the 5'?

Hello,
Could you add an option to trimming polyT from the 5'? I think it is useful for filtering polyT stretches coming from polyA tails in unstranded RNA-seq data.
Thanks,
Haibo

Hello,
I think you can try to filter these reads by the parameter, --low_complexity_filter.


"When a build validation policy is enabled, a new build queue when a new pull request is created"

Should this be:
When a build validation policy is enabled, a new build queue is created when a new pull request is created
kinda hurts my brain reading that sentence.

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

ID: 7cd986e0-608c-1d8c-6faf-ecdb12e10bc6
Version Independent ID: d60c996e-187e-dd6b-7f3a-dd056a1603f4
Content: Protect your Git branches with policies - Azure Repos
Content Source: docs/repos/git/branch-policies.md
Product: devops
Technology: devops-code-git
GitHub Login: @apawast
Microsoft Alias: sdanie

@Spaceman1861 Thank you for the feedback, sorry for the confusion.
The documentation has been changed and is pending review.

No worries all good


RestAssuredMockMvc miss effective way to set header accept()

RestAssured.given() returns RequestSpecification which has accept(...) method. But RestAssuredMockMvc returns MockMvcRequestSpecification which does not have accept(...) method. This method is effective way to set accept header. Otherwise I have to set manually.

Thanks for reporting.

Fixed


Story not stopped upon first MVC request

Hello,
I'm experiencing some odd behaviour in an MVC application in ASP.NET 4.6.1 with OWIN.
I'm starting a story in the homepage like so:
public async Task<ActionResult> Index()
{
    return await Storytelling.Factory.StartNewAsync("Index", async () =>
    {
        await Task.FromResult(0);
        return View();
    });
}

I've registered the OwinMiddleware in your example, so all stories are under the context of a "Request" story. I'm registering the middleware like so:
app.Use(typeof(StoryMiddleware));
I've also registered a story handler for NLog:
public class NLogStoryHandler : StoryHandlerBase
    {
        private readonly IStoryFormatter storyFormatter;
        private static NLog.Logger logger = LogManager.GetCurrentClassLogger();

        public NLogStoryHandler(string name, IStoryFormatter storyFormatter = null)
            : base(name)
        {
            this.storyFormatter = storyFormatter ?? StoryFormatters.GetBasicStoryFormatter();
        }

        public override void OnStop(IStory story)
        {
            string str = this.storyFormatter.FormatStory(story, this.Name);
            logger.Info(str);
        }
    }

Finally, I'm setting up the factory like this:
Storytelling.Factory = new FileBasedStoryFactory(ConfigurationManager.AppSettings["StoryRulesetPath"],
                () => new object[] {
                    new NLogStoryHandler("NLogHandler")
                });

What is happening is that the first request made to ASP.NET is only logging the "Request" story. I put a breakpoint on the OnStop method, and the story should contain the "Index" story as a child, but it doesn't.
After the first request, the OnStop method is called twice. For both, the story is "Request", and one of them contains the "Request/Index" story as a child, but the second time it has no children.
I've included a sample so you can try it out for yourself. The log is being written under the logs folder, and you have to change the path in web.config for the RuleSet(is there a way to provide a relative path?).
WebApplication9.zip
I'd appreciate any insight into this problem.
Thanks

I looked into it a bit more, and it seems the reason those "Request" stories exist is because of the browser link feature VS has, which is sending those requests. But the first request is still not being logged as a structured story.

We'll take a look into this.

Hi @amitapl ,
Could you come up with any solutions to the above thread?
Thanks,


fix non-square preview data issue

Think the preview window assumes data are square (they aren't necessarily, of course)..

https://github.com/bcgov/bcws-psu-research/commit/c69ff6b80465fc65f78a72c38eaf06b12db5095c
x and y coordinates were misplaced. Fixed!


Remove white and blacklist

Because this matters to me: http://mckay.pub/2015-01-07-allowed/

Good post; good idea. :+1:  :heart:

The whitelist change was reverted in https://github.com/mozilla/addons-server/pull/3904 since it broke -dev. The env file needs updating in tandem with this change and then the revert can be reverted.

Next need to fix up a couple of external process.


Feature/channel value playground

Fixes 3502 .

Changes proposed in this Pull Request:

Update channelValue playground
Fix copy all button from playground snippet

Screenshots:

To Test:

http://localhost:3000/components/channel-value/playground

unitSpace is actually not required. Would you update both API Table and Playground to reflect this?
Things look good otherwise.

We have this prop inside channelValue component. https://github.com/brightlayer-ui/react-component-library/blob/dev/components/src/core/ChannelValue/ChannelValue.tsx#L57. Any specific reason to remove it from API docs and playground?

Not to remove it, but to update the API table so that it does not say unitSpace is required

Not to remove it, but to update the API table so that it does not say unitSpace is required

Oops now I understand . Let me update.

https://blui-react-docs--pr530-feature-channel-valu-om8r7o61.web.app

Done.

unitSpace is actually not required. Would you update both API Table and Playground to reflect this?
Things look good otherwise.

Merged this story.


Trigger rebuild due to CVE-2016-2177 CVE-2016-2178

openssl was updated so we need trigger a rebuild

this fixes #192


local_auth plugin wrongfully reports available methods when they're not enabled on the device.

Steps to Reproduce

Create an Android Pixel device and DO NOT initialize the fingerprint sensor.
Download the local_auth example code and run it
Click the get methods listing, you will get fingerprint method available (which is not true since is not initialized by the user on the device yet)
Click the button to Authenticate - exception.

Expected results:
Getting available methods listing should be empty since as the name implies it's available methods and the device currently has NO methods readily available. Currently, it basically lists hardware device capabilities as methods.
Actual results:
I get the fingerprint method as available.

Logs
[        ] 💪 Running with sound null safety 💪
[+16590 ms] I/flutter (10813): PlatformException(NotAvailable, Required security features not enabled, null, null)

Hi @TahaTesser I would like to work on this issue.
I was thinking of this approach to solve this issue.
Keeping the getAvailableBiometrics() the same which returns the hardware supported features,
there could be another function getEnrolledBiometrics()  which can return the list of enrolled biometrics.
I wanted to use Androidx Biometric library to get whether the user has enrolled or not. But the problem with using this library is we can only determine that user has enrolled and also whether device supports to either BIOMETRIC_STRONG etc.. So should the function return the type of biometrics enrolled or the different levels of security that device has been enrolled in.
For api<27 we can use FingerprintManager to to check whether there is a fingerprint enrolled but the api is deprecated.
Please let me what should be done. Thanks.

Can I open PR for the changes I have made?

Hi @TahaTesser I would like to work on this issue.
I was thinking of this approach to solve this issue.
Keeping the getAvailableBiometrics() the same which returns the hardware supported features,
there could be another function getEnrolledBiometrics() which can return the list of enrolled biometrics.
I wanted to use Androidx Biometric library to get whether the user has enrolled or not. But the problem with using this library is we can only determine that user has enrolled and also whether device supports to either BIOMETRIC_STRONG etc.. So should the function return the type of biometrics enrolled or the different levels of security that device has been enrolled in.
For api<27 we can use FingerprintManager to to check whether there is a fingerprint enrolled but the api is deprecated.
Please let me what should be done. Thanks.

Actually, the getAvailableBiometrics is intended to return the valid (enabled) methods. This is reflected also in the iOS implementation. It will return the method such as faceid only after the user has enabled it.
Would be very nice to have a different function to retrieve a list of the platform supported methods although this is outside the scope of this ticket.

Actually I scraped the idea of creating another function and modified getAvailableBiometrics to retrieve only those which are enabled.

Hi there, is there a timeline for when this might be made available in a release?

Duplicate of https://github.com/flutter/flutter/issues/45497


allow embedder to control the execution and error handling of callbacks

For effecient use in neovim we would need a bit of control how luv executes callbacks.
Primarily we need to take control of handling of errors. Currently luv prints errors in callbacks directly to stderr which messes up the internal screen of nvim. But we would also like to set a flag around the execution of the callback, as some lua API functions in nvim need to behave differently inside a luv callback (to avoid nested event loop for instance).
My suggestion is to add a "hook" function that a C embedder can set in a similar way to setting the event loop. Then the embedder is responsible for executing the callback and dealing with errors, including potential formatting of tracebacks etc. https://github.com/neovim/neovim/pull/10316/commits/aa78c74b74c6a0e3595b76d02f674dacabd6e092 is an example of usage.
Does this seem reasonable? if so I can clean up the patch, and add docs etc.

I guess a concern could be too many small userdata like both luv_loop_key and luv_cb_hook_key. A refactor could be to instead have a single userdata with a struct of the "global" luv state of a lua state.

Primarily we need to take control of handling of errors. Currently luv prints errors in callbacks directly to stderr which messes up the internal screen of nvim.

How a about generate a error with lua_error

My suggestion is to add a "hook" function that a C embedder can set in a similar way to setting the event loop.

I have no good idea,  want to hear the voices of others.

How a about generate a error with lua_error

How would this work? lua_error only works inside a cfunction called from lua, and here we are outside any lua stack.

Do you mind if I re-implement this feature? That will break the API you defined. @bfredl

The API was only a suggestion, Yours also handles return values, so it is better.


Bring more clarity on JDK version requirements

Currently the jextract-swift section of the USER_GUIDE tells us that it needs JDK 22 to utilise "Project Panama".
Upon further inspection, I realised that the Java2Swift Program doesn't compile at all if the JDK version is lesser than 21. This is due to the fact that we hardcoded the vmArgs.version to JNI_VERSION_21 while instantiating a JavaVirtualMachine object.
This JNI_VERSION_21 is a preprocessor constant which is only available in JDK 21 or later.
If this is the intended behaviour, It will be better to update the USER_GUIDE to let people know that Java2Swift will need a JDK that is 21 or later. However, if this is not the intended behaviour, then replacing the hardcoded JNI version with a JNI version which corresponds to the user's JDK would be better.

I'm not an expert in this context, but making an assumption that a lot of current enterprises (who would like to move their tech stack from JVM to Swift) need not be running their software in JDK 21 or later would be more realistic. Thus, I believe trying to support older JDKs instead of supporting only JDK 21 or later (unless mandatory such as "Project Panama") will be better for this project. Feel free to correct me if I'm wrong.
Edit: Realised the gradle files also specify JDK 22 to be a requirement.

This is documented more in https://github.com/swiftlang/swift-java/pull/14
Long story short: we'll support both eventually, 22+ with the panama mode, and old versions with just JNI. JavaKit is just JNI and would work with old Java versions.
We need to make the build "smart enough" to survive this eventually.
Today, for ease of development / bootstrapping we're just requiring the latest supported JDK which has Panama.
In the end the required JDK will depend on which feature you're intending to use.
We're not at a phase of "cleanup and publishing" yet, so yes, for now we're just developing with the latest JDK.

Long story short: we'll support both eventually, 22+ with the panama mode, and old versions with just JNI. JavaKit is just JNI and would work with old Java versions.

I expected this would be the case as well.

We're not at a phase of "cleanup and publishing" yet, so yes, for now we're just developing with the latest JDK.

I totally understand that, I just think that eventhough we are in early stages of development, the project should be such that, someone can follow the instructions in the Guide and be like "wow, this works" and the JDK requirements not being specified beforehand may not let them reach that point.
For example, running the tests as suggested in README failed for me. The reason being that I'm using a x86_64 device. It would have been nice if this had been specified in the README itself like "This project is under development and for the sake of it, we are currently using JDK 22 & arm64 device"
Most people will be happy to see the code run and fail than to not see the code run at all due to environment setup issues.

This is due to the fact that we hardcoded the vmArgs.version to JNI_VERSION_21 while instantiating a JavaVirtualMachine object.

I don't think anything in JavaKit or the Java2Swift direction needs JDK 21. Setting the meta-points of the discussion aside, I think we can replace this with an older constant after a quick review of whether we're using anything that was introduced into newer versions of the JDK.

With https://github.com/swiftlang/swift-java/pull/50, we can support much older JDK versions. I set it at 1.6 (the oldest JNI version that supports the APIs we need).


Implement history components in Esteemer candidate message rankings

History component processing needs to be completed.

infrastructure rewritten to dataframe processing, with further graph model improvements may need to be rewritten entirely to be graph based.

Left to do with this implementation strategy:

[ ] Incorporating the message/measure recency terms with scoring math
[ ] esteemer loguru changes

[ ] log level set by settings.py instead of hardcoded trace
[ ] adding additional log statements for debug and dev

We are considering creating an annotation function that will accept Information Content of the type MessageHistory and extract Motivating Information of the type MessageRecurrence, with properties like recency and count.
The MessageReccurence and its properties (moderators) would then be inputs to the esteemer function which could be used by Esteemer when evaluating the Motivation Potential of a candidate message.
This would roughly parallel the handling of performance-related information content (i.e. the number block) for message-related information content (i.e. the JSON history object).
This does not imply exactly where the annotation function and the esteemer function should be invoked!. For example, BitStomach is focused on performance information content; it is not clear that message-related information content should be processed in BitStomach.


knext builder报错

(openspg_venv) root@docker-desktop:/code/python/knext/knext/examples/supplychain# knext builder execute TaxOfCompanyEvent
2024-08-19 08:28:44,506 [] [] [main] ERROR c.a.o.b.r.l.LocalBuilderMain - unknown exception.
java.lang.ClassCastException: java.lang.String cannot be cast to com.antgroup.openspg.core.schema.model.type.ProjectSchema
at com.antgroup.openspg.builder.runner.local.LocalBuilderMain.getProjectSchema(LocalBuilderMain.java:164)
at com.antgroup.openspg.builder.runner.local.LocalBuilderMain.run(LocalBuilderMain.java:132)
at com.antgroup.openspg.builder.runner.local.LocalBuilderMain.main(LocalBuilderMain.java:69)

Server and Python version mismatch. Please provide your local environment configuration, openspg-server and openspg-python. Installation Instructions : https://openspg.yuque.com/ndx6g9/nmwkzz/xht6kkegvs33cwwr

I'm using the latest Docker image, released August 19

Whether openspg-server is started from source or docker? Please provide the docker version information

Thanks for your feedback. Due to the docker network problem, the previous image cannot be obtained. Please follow the  document to fetch the latest openspg-python image again
https://openspg.yuque.com/ndx6g9/nmwkzz/xht6kkegvs33cwwr


Resizing window doesn't properly resize message graphs

The box drawn around the graph resizes with the window, but the line in the graph extends beyond the box to its full length. Either both should resize, or neither

Resolved


Update Recommendation Text in Section I.3.1

The 2023 Errata paper made a very slight change to the recommendation text in the above section (i.e., change "squamocolumnar junction is visible " to "squamocolumnar junction is fully visualized". See below
DISPLAY For patients with a diagnosis of histologic HSIL (CIN 2) whose concerns about the effects of treatment on a future pregnancy outweigh their concerns about cancer, either observation or treatment is acceptable provided the squamocolumnar junction is fully visualized and CIN 2+ or ungraded CIN is not identified on endocervical sampling (CII). For patients 25 years or older, observation includes colposcopy and HPV-based testing with cotest or primary hrHPV testing at 6-month intervals for up to 2 years.

This is addressed in PR: https://github.com/ccsm-cds-tools/ccsm-cds-with-tests/pull/81. Can be closed here.


Who is maintaining this repo?

As stated in the README of Calendso, the docker repo is a community project and not officially supported by the Calendso team.
However, it is unclear how one can contribute here and who is actively maintaining this repo.
Also getting write permissions needs an invite from the Calendso team again which might not be that easy. It would be great to have some instructions how one can contribute here.
Currently there are several issues with the current state of the repo and I fear that this repo becomes outdated if no action is taken.

hey @pat-s, yeah i agree this has been very confusing. any recommendations? do you want to contribute to it? We can make a new team that has some writing authority over this repo

hey @pat-s we've given this topic a much higher priority inside of the team and will find a better solution for this! 🎉  until then, you can make PRs at any time and we'll merge them accordingly


fix(properties-utils): fix decimiter units

Obvious error in units factors
What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Woops, thanks a lot!


Extension should be .ts

Trump Script -> .ts extension makes the most sense.

On second thought I guess it would cause confusion with TypeScript.

We mentioned that before


[parallel] Currently unable to support display label

[x] I am using English in this issue. 在这个 Issue 中我使用了英文（强烈建议）。

General Questions

[x] Required: I have read the document and examples and tried to solve it by myself. （必填）我读过了文档和教程，并且曾试图自己解决问题。
[x] Required: I have searched for similar issues and that didn't help. （必填）我搜索过 issue 但是没有帮助。
[x] Required: I have tried with the latest version of ECharts and still have this problem. （必填）我试过最新版本的 ECharts，还是存在这个问题。

In this issue, I have provided information with: 在这个 issue 中我提供了以下信息：

[x] Required: issue type；（必填）issue 类型
[x] Required: one sentence description in issue details；（必填）一句话的问题描述
[x] Required: demo；（必填）能反映问题的例子（如果你想提问或报 bug）
[x] Required: ECharts version；ECharts 版本

Issue Type

[x] I have a question to ask about how to use ECharts to ...；我想提问如何使用 ECharts 实现某功能
[ ] I have a bug to report；我想要报 bug
[ ] I have a feature to request, e.g.: I'd like a new feature that ...；我需要一个新功能
[ ] I have a feature to enhance, e.g.: The current feature should be improved in the way that ...；我希望改进某个功能
[ ] There's something wrong with the documents；文档有些问题
[ ] Others, or I'm not sure which issue types to choose here；其他，或我不知道应该选什么类型

Issue Details

The style setting in the parallel coordinate system where you want to implement the intersection of the polyline and the axis and the text description of this point.
[平行坐标系中想要实现折线和轴线交叉点的样式设置以及这个点的文字描述说明]
Similar to the role of the following code in the line chart.
[类似折线图以下代码的作用]
itemStyle:{
                normal:{
                    color:'#f17a52',
                    shadowBlur: 40,
                    label:{
                        show:true,
                        position:'top',
                        textStyle:{
                            color:'#f17a52',

                        }
                    }
                }
            },

Expected Behavior

Current Behavior

Online Example

Topics

[ ] Legend
[ ] Tooltip
[ ] Event
[ ] Performance
[ ] SVG
[ ] Map
[ ] ECharts GL
[ ] Third-party libraries, e.g.: Vue.js, React

Anything Else We Need to Know

Environment

ECharts version；ECharts 版本: {DESCRIBE_HERE}

[ ] It happens only on certain browsers or operating systems. 对于特定浏览器或操作系统才会出现的问题，请提供相应环境信息：{BROWSER_VERSION_OR_OS_INFORMATION_HERE}

Please describe your question in detail. An example will be great


Update app-insights-code-sample-export-telemetry-sql-database.md

Updated the run interval explanation

Hi @antonfrMSFT, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Configure which notification statuses trigger callbacks

Value Statement
As  a VANotify client
I want to configure which notification statuses trigger callbacks
So that I can only get responses I am interested in e.g. permanent failures
Business use case: VEText is sending KMIs (700k emails), but is not interested in successes. However! They should be interested in permanent failures, because they should remove addresses from their list.
Acceptance Criteria
GIVEN a service with a callback
WHEN I configure callback for specific statuses (see assumption for full status list)
AND a notification for that service enters one of those specified statuses
THEN VANotify will execute the callback
GIVEN a service with a callback
WHEN I configure callback for specific statuses (see assumption for full status list)
AND a notification for that service enters a status that was not specified
THEN VANotify will not execute the callback
GIVEN a request to create or update a service callback
WHEN that request does not contain any statuses
THEN that request should be rejected as invalid (400), and should provide a helpful message
Checklist

[x] Update service callback DB model to include list of statuses
[x] Update endpoints to update/create service callbacks
[x] Add conditional logic to wherever the callback is triggered

Assumptions

Notification statuses: sending, sent, technical failure, permanent failure, temporary failure)

Additional Info/Resources
app/service/service_callback_api_schema.py
app/service/callback_rest.py
https://webhook.site/ - a handy site for testing webhooks or https://httpreq.com/fragrant-thunder-5i8ao36t as it doesn't check whether bearer token is valid
Use AWS Email Simulator to test those different statuses?
Out of Scope

Open Questions

verified it is working in dev using:
https://httpreq.com/fragrant-thunder-gi8ao36t
PS: the url in service call back should be https://httpreq.com/fragrant-thunder-gi8ao36t/record

[https://app.zenhub.com/files/257953872/8b9050b4-41ca-4f5f-baa9-71c71696d751/download]
Manual Exploratory Test Scenarios that were executed are attached.
All Acceptance Criteria have been met. Closing ticket.


EventEmitter is not a constructor

I just start a project on React and found this error on muy console. Any idea how to fix it?
core.js:9 Uncaught TypeError: EventEmitter is not a constructor
    at node_modules/jsforce/lib/core.js (core.js:9:32)
    at __require2 (chunk-U3TMEWQO.js?v=601c5caa:19:44)
    at node_modules/jsforce/lib/browser/jsforce.js (jsforce.js:3:15)
    at __require2 (chunk-U3TMEWQO.js?v=601c5caa:19:44)
    at dep:jsforce:1:16

Here's the dependencies on package.json
  "dependencies": {
    "axios": "^0.25.0",
    "eslint-plugin-jest": "^25.7.0",
    "jsforce": "^1.11.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "styled-components": "^5.3.3"
  },

Thanks

@elchiconube Any luck resolving this? I'm seeing the same thing in a svelte project.
https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility

@elchiconube Any luck resolving this? I'm seeing the same thing in a svelte project.
https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility

Nop but I've created new projects with last versions and it's fixed.


vet: failure to load fmt"

@alandonovan are you going to add something describing the bug, or is this a mistake?

I have no idea what this is.  Closing...


Add option to disable automatic apiManager registration for KubeApi

If KubeApi is used by e.g. an extension, it usually shouldn't be registered to apiManager. This PR adds an option for disabling the automatic registration.

If it is a bug, wouldn't it be better to just remove that line and add the calls to all the places we call the constructor?

Fair enough, I don't think that we should register during a call of forCluster anyway...