Hadoop 17048

Revert "HADOOP-16126. ipc.Client.stop() may sleep too long to wait for all connections."
Revert "HADOOP-16127. In ipc.Client, put a new connection could happen after stop."

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
18m 52s
trunk passed

+1 :green_heart:
compile
19m 18s
trunk passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
compile
16m 53s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
0m 53s
trunk passed

+1 :green_heart:
mvnsite
1m 25s
trunk passed

+1 :green_heart:
shadedclient
16m 41s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 42s
hadoop-common in trunk failed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.

+1 :green_heart:
javadoc
1m  3s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+0 :ok:
spotbugs
2m 10s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m  9s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 49s
the patch passed

+1 :green_heart:
compile
18m 48s
the patch passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javac
18m 48s
the patch passed

+1 :green_heart:
compile
16m 55s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
16m 55s
the patch passed

-0 :warning:
checkstyle
0m 53s
hadoop-common-project/hadoop-common: The patch generated 3 new + 102 unchanged - 0 fixed = 105 total (was 102)

+1 :green_heart:
mvnsite
1m 27s
the patch passed

-1 :x:
whitespace
0m  0s
The patch has 6 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shadedclient
14m 14s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 44s
hadoop-common in the patch failed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.

+1 :green_heart:
javadoc
1m  3s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
2m 16s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 33s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 54s
The patch does not generate ASF License warnings.

148m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2090

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux c7185a28cf9b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 201d734af39

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/artifact/out/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/artifact/out/whitespace-eol.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/artifact/out/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/testReport/

Max. process+thread count
2754 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@arp7 @szetszwo Can you please help review and approve this PR? I will create a follow up jira/PR to make the value configurable with default as 100ms.

As stated in the JIRA comment (https://issues.apache.org/jira/browse/HADOOP-17048?focusedCommentId=17139883&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17139883), there are two problems for reverting the JIRAs

For HADOOP-16126, we do observe a 10x improvement for some Hive jobs as stated in the JIRA –

In the code above, the sleep time is 100ms. We found that simply changing the sleep time to 10ms could improve a Hive job running time by 10x.
I guess we may get a better performance for one kind of job but degrade the performance for some other jobs.

For HADOOP-16127, the bug is

getConnection(..), running can be initially true but becomes false before putIfAbsent.
Reverting it (i.e. removing the lock) has a better performance since it just ignores the synchronization bug. Why not fix the synchronization bug in a better way?

Making the value configurable could address Problem 1.
How about Problem 2?  It is a more serious bug on correctness.

@szetszwo I will address the config change for the hadoop sleep in the jira https://issues.apache.org/jira/browse/HADOOP-17161. Can you please help us address the second issue on the correctness. With HADOOP-16127 included, we see lock issues and the queries get hung as mentioned in the https://issues.apache.org/jira/browse/HADOOP-17048.

@szetszwo  I will have to wait for this pull request to merge in order to address the issue in https://issues.apache.org/jira/browse/HADOOP-17161.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 36s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
23m 19s
trunk passed

+1 :green_heart:
compile
23m 46s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
19m 18s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
0m 52s
trunk passed

+1 :green_heart:
mvnsite
1m 34s
trunk passed

+1 :green_heart:
shadedclient
18m 43s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 38s
hadoop-common in trunk failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 56s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+0 :ok:
spotbugs
2m 29s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 27s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s
the patch passed

+1 :green_heart:
compile
28m  8s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
28m  8s
the patch passed

+1 :green_heart:
compile
22m 27s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
22m 27s
the patch passed

-0 :warning:
checkstyle
0m 55s
hadoop-common-project/hadoop-common: The patch generated 3 new + 102 unchanged - 0 fixed = 105 total (was 102)

+1 :green_heart:
mvnsite
1m 35s
the patch passed

-1 :x:
whitespace
0m  0s
The patch has 6 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shadedclient
17m 26s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 45s
hadoop-common in the patch failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 58s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
2m 40s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
10m 43s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  3s
The patch does not generate ASF License warnings.

183m 46s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2090

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 5c07a944049b 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 026dce5334b

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/artifact/out/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/artifact/out/whitespace-eol.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/artifact/out/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/testReport/

Max. process+thread count
2695 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2090/2/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
19m 52s
trunk passed

+1 :green_heart:
compile
22m 37s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
17m 58s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
0m 50s
trunk passed

+1 :green_heart:
mvnsite
1m 28s
trunk passed

+1 :green_heart:
shadedclient
16m 31s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 36s
hadoop-common in trunk failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
1m  0s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+0 :ok:
spotbugs
2m 18s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
2m 16s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 54s
the patch passed

+1 :green_heart:
compile
21m  7s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
21m  7s
the patch passed

+1 :green_heart:
compile
17m 27s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
17m 27s
the patch passed

-0 :warning:
checkstyle
0m 48s
hadoop-common-project/hadoop-common: The patch generated 3 new + 102 unchanged - 0 fixed = 105 total (was 102)

+1 :green_heart:
mvnsite
1m 22s
the patch passed

-1 :x:
whitespace
0m  0s
The patch has 6 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
shadedclient
14m  6s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 41s
hadoop-common in the patch failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
0m 59s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
2m 28s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
10m  4s
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

156m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2090

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux a2e0201c8e0f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 05b3337a460

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/artifact/out/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

checkstyle
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

whitespace
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/artifact/out/whitespace-eol.txt

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/artifact/out/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/testReport/

Max. process+thread count
2416 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2090/3/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@szetszwo Hi Nicholas, Can you please help me on this? I am depending on this PR to be merged to address the config change needed.


Backwards Pass w/Output Gradients

Can caffe2 run a backward pass with externally provided output gradients? I have a loss function that can't be defined in caffe2, but I have the gradients of that loss w.r.t. the output of a net I can define, and want to compute the gradient of the loss w.r.t. the network's input.
As a concrete example, in pytorch I would do something like
gz = th.autograd.grad(net_out, net_in, external_grad)

I looked through the API and tutorials but couldn't seem to find a gradient op that would allow this.

+1


Remove unused credit card/stripe code and dependencies

Addresses https://github.com/rancher/dashboard/issues/9096
Remove the stripe and ember-credit-card dependencies and some unused code around billing.

@mantis-toboggan-md Can we merge this one as well?


Create test for inserting data to [BigQuery]

Cocoon backend is now inserting data to [BigQuery], but missing tests.
We need to add corresponding tests to cover this feature.

Added fakeTabledataResourceApi, and merged in #512. Closing this issue.


add together.xyz (WIP)

the text input doesnt actually work yet. not sure how to get the text event simulation working.

@seanoliver together now allows llama2-32k https://twitter.com/togethercompute/status/1685048832168714240
want to take a stab?

ok this is ready

its late, just merging


Ignore: Update branch text layout

I remaked this in https://github.com/GabrielBRDeveloper/MasterUI/commit/a7ce7ba99a21ffb6475c4873b03ce2d3b169dbc8


ENYO-1654 : moon.ProgressBar needs a tooltip to show current progress.

Issue
moon.ProgressBar needs a tooltip(popup) to show current progress.
Fix
I extracted popup components and made PopupSupport.  Also, I organized slide and progressbar to apply this change.
WIth this change, app developer can use popup support in progresbar.
If user sets "popup:true", then popup will be shown.
Enyo-DCO-1.1-Signed-off-by: Suhyung Lee<EMAIL_ADDRESS>

You have the right idea to pull the popup-related code out of Slider but I don't think a mixin is the right home. As it exists now, it's too specialized to be reused in another context so instead let's move it into ProgressBar and ensure that Slider has the necessary opportunities to override methods or configure members to customize the popup.

@ryanjduffy , I have changed my PR following your comment. I removed mixin and put popup-related code into progressBar. Please review it, Thanks,


Unable to select suitable driver for this board

More details here: http://forum.dexterindustries.com/t/grove-dht-and-golang-in-general/3187
Do you think it's my code or your library?
i2cdetect returns the expected result!

Hi. It's probably the library. When starting up, the library needs to select an appropriate driver for the board. Different boards support different hardware. There is a raspberry pi driver, but it looks in /proc/cpuinfo for the presence of BCM2708 or BCM2709. Chances are you've got a newer raspberry pi that uses a different chip set. Can you post the contents of /proc/cpuinfo from your raspberry pi? And what model of raspberry pi do you have?

Raspberry Pi 3
processor	: 0
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 1
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 2
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 3
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 38.40
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

Hardware	: BCM2835
Revision	: a02082
Serial		: 00000000ade634d8

I've added
if strings.Contains(s, "BCM2708") || strings.Contains(s, "BCM2709") || strings.Contains(s, "BCM2835")

And it seems to work, I'll test it a bit more to be sure and will provide updates.

Ok sweet. I don't have a board to test it on. The Raspberry Pi driver firstly detects if it applies (the test you've amended), but it also contains a function createPinData() that selects configuration for boards, since the raspberry pis sometimes change their hardware with each revision. The default case in that function is for a rasppi B+. From what I can see online, the 3 model has the same pinouts as the B+, so the B+ config should work. Just be aware that there can be differences.
Do you want to create a pull request for that change, or would you like me to apply that?
M

Ok, awesome, thanks.
Yep, I can make a PR tonight when I'm back home.


How Do I Run a Simple GAN without any conditioning?

How Do I Run a Simple GAN without any conditioning?
I have downloaded the source code and ran net_gan, which uses gan_application.py and obtained the following error:
CRITICAL:niftynet: Reader requires task input keywords ('conditioning',), but not exist in the config file.
Available task keywords: ['noise_size', 'image', 'n_interpolations', 'conditioning', 'name']
Traceback (most recent call last):
File "net_gan.py", line 8, in
sys.exit(main())
File "/Users/kan7792/NiftyNet/niftynet/init.py", line 141, in main
app_driver.initialise_application(system_param, input_data_param)
File "/Users/kan7792/NiftyNet/niftynet/engine/application_driver.py", line 167, in initialise_application
data_param, app_param, self.data_partitioner)
File "/Users/kan7792/NiftyNet/niftynet/application/gan_application.py", line 69, in initialise_dataset_loader
data_param, task_param, file_list) for file_list in file_lists]
File "/Users/kan7792/NiftyNet/niftynet/io/image_reader.py", line 142, in initialise
raise ValueError
ValueError
It makes perfect sense because it is looking for a conditioning field in my config, which does not exist because I'm using the generic gan (simple_gan.py) without any conditioning.

Did you find out how to do it, chinokenochkan?

@carlpe my apologies for the late reply. I've switched to other source codes (not niftynet) for simple gan.

@chinokenochkan
May I ask which one you have been most successful?


Tutorial for editing the code in the theme

Hello Ema,
I am having quite a bit of trouble understanding how to edit the code of the theme, I do not have problems with updating the content using contentful but instead the very code of the theme. I understand going to the node_modules and changing the code in the src wont help cause when deploying the changes will be erased, and I tried editing it in the src in the main and all i got are errors after errors.
Could you please make a tutorial on how to accomplish this please.

Hi @kanlanc I decided to expand the documentation of the project and improve the current customization section. Could you please take a look at this PR #725 and tell me if that solved your problem. Also, please feel to leave any comment on it 😄


Digital Clock

Is your feature request related to a problem? Please describe.
We don't have a digital calculator.
Describe the solution you'd like.
I want to add a digital calculator with awesome css effect.
Describe alternatives you've considered.
I will add digital calculator to this project.
Add any other context or screenshots about the feature request here.

issue assigned @Areebah03

Hi there! I would like to work on this issue. Can you assign this to me? I have really good and responsive designs....

@navyasharma0203 the issue is assigned and PR is also open hence can't assign you the same issue :(


jssmut.weebly.com still has 5.2.0 release, please update

The main website is still hosting an outdated version of the JSS MUT.
Also, it would be convenient to have a download for v4 on the same site.
Thanks!

Man, I miss having you as our ESE.
Looking forward to v6.
Cheers,
Brad
—Sent from my iPhone

On Oct 8, 2021, at 9:12 PM, Mike Levenick @.***> wrote:

Hey Brad, good catch. One downside to having MUT in so many places is I forget to update them all.. github releases, app store, jamf marketplace, weebly, etc. This has been rectified.
As for v4, I'm working on v6 right now which will have the same group update method as v4 (who says regression is a bad thing!), hopefully as a failover if it detects errors with the bulk upload, and will probably sunset "Classic" altogether at that point.
I don't actually think I have a notarized copy of Classic around anymore at this point to upload to the weebly..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.


removed unnecessary gpu and cpu data movements

I also added some example JSON deserialization code (commented out) the dependencies for which ship with Unity


migrate publish pipeline to ESRP release

We won't be able to publish any @microsoft scope package past March 31st.
The ADO pipeline for this package needs to be migrated to ESRP release instead of using a token.
here is the documentation to do so.

For information the first steps to register ESRP release in our ADO org are under way, all that will be left here is to change the pipeline to use the new tasks https://github.com/microsoftgraph/typespec-msgraph/issues/472


Can't connect to p2p network - Ubuntu 20.04

Description
After following each step of the installation & setup guide for Ubuntu 20.04 the 4GB file was created, but after I start the application I'm getting after a few minute the red alert: "Can't connect to p2p network"
Port 7153 is forwared in the router.
Environment
Please complete the following information:

OS: Ubuntu 20.04
App Version (if applicable):  Latest

Testnet 129 is officially dead.

@GreatV Oh what does it mean exactly?

@GreatV Oh what does it mean exactly?

Just wait for new Testnet release, and try again.

same here
it connects, stay online some minutes and then goes offline

it seems working with Testnet 132 Build v0.1.38, but it's at the same point since 48h (1894/2572) and no log / messages of what it's doing


Callback not firing

Hi,
Thanks for the code.
when I'm trying to run your code always default callback is executing. Can you please help me on this?
Thanks.

Hi,
I have downloaded and tested my latest release from git(Builded on Xcode7.3.1). But couldn't repeat your case.
Could you please offer more infos?
For example. Is it always executing default callback on the Swift side or on the other side?
Snapshots will be more helpful : ]
By the way, If you just call methods sending data  between Swift and Javascript rather than call registered handlers, that will only trigger default handler since handler is used to deal with 'designated job' and for which you don't designate will be passed to default handler.
Thank you

Hi,
Thanks for the quick update.
I am using Version 7.2.1 (7C1002).
Please find the attachment.

Thanks.

IMO, I think you did build and run the project, but you didn't click other buttons to call handler registered on both Swift and Javascript side.
The only reason why return default handler every time is this statement in ViewDidLoad method.
self.bridge.sendDataToJS(["msg": "Hello JavaScript, My name is 小明", "gift": ["100CNY", "1000CNY", "10000CNY"]])

Hi,
Thanks for your details.
I tried both end. but, still the callback is not firing.
I am receiving message and responseId in data, but, when check if let responseId = swvbMsg["responseId"] as? String { it's failed.
Can you please guide on this?
Thanks,
Sabari.

Hi,
Try on these steps to see if program will run to this statement below
return self.messageHandlers[handlerName]

Set up two break points firstly

Then, click one of these buttons

Since calling this method SwiftWebViewBridge.callSwiftHandler("printReceivedParmas", data, null) from the Javascript will send a message carried this infos.
The handlerName, 'printReceivedParmas', is the name of handler registered on Swift side
{
        callbackId = "cb_1_JS_1470057761845";
        data =         {
            age = 6;
            name = "\U5c0f\U660e";
            school = GDUT;
        };
        handlerName = printReceivedParmas;
}

A More quickier way, just set up a break point at this line and test if Xcode will break in there


Core: Card insides

Description
How should a card insides look like?
Example:  https://tango.info/JuanaDarie
Preliminary task
Create the design of the card insides in mockoverflow software tool

@Vujicic98 Implement the idea discussed, and create a new PR for next meeting.


TS typing of continuous/geneExpression/histo-related

TS typing fixes added to categorical components:

[ ] client/src/components/continuous
[ ] client/src/components/brushableHistogram
[ ] client/src/components/geneExpression
[ ] client/src/components/miniHistogram
[ ] client/src/components/rightSidebar

will type these next time we touch the files!


Remove unneeded partitioning

Speeds up the integration tests

Looks like some tests are failing due to number of partitions being hardcoded in tests
=========================== short test summary info ============================
FAILED tests/integration/test_reads.py::test_pyarrow_deletes[session_catalog_hive] - assert [4, 5, 6] == [1, 2, 3]
  At index 0 diff: 4 != 1
  Full diff:
  - [1, 2, 3]
  + [4, 5, 6]
FAILED tests/integration/test_reads.py::test_pyarrow_deletes[session_catalog] - assert [4, 5, 6] == [1, 2, 3]
  At index 0 diff: 4 != 1
  Full diff:
  - [1, 2, 3]
  + [4, 5, 6]
FAILED tests/integration/test_reads.py::test_pyarrow_deletes_double[session_catalog_hive] - assert [10] == [5]
  At index 0 diff: 10 != 5
  Full diff:
  - [5]
  + [10]
FAILED tests/integration/test_reads.py::test_pyarrow_deletes_double[session_catalog] - assert [10] == [5]
  At index 0 diff: 10 != 5
  Full diff:
  - [5]
  + [10]
= 4 failed, 812 passed, 8 skipped, 2859 deselected, 2 warnings in 286.99s (0:04:46) =

Looks like modifying provision.py to include this part is what we need. I double checked by running integration tests locally.
spark = (
    SparkSession
        .builder
        .config("spark.sql.shuffle.partitions", "1")
        .config("spark.default.parallelism", "1")
        .getOrCreate()
)

from https://github.com/apache/iceberg-rust/pull/826/files#r1892947712

@kevinjqliu Nice one! The partitioning would shuffle all the records based on year, so they would fall into the same bucket. I think the config is much cleaner, thanks @kevinjqliu! 🙌


review/refactor sampler and estimator scaling tutorials [ HIGH PRIORITY ]

[ CURRENTLY UNDER PRODUCT REVIEW IN QTE REPO]
This tutorial is based on a summit demo but uses Estimator instead of Sampler. It is a new notebook created by Saki and Pedro on Nate's team, please work with them on this issue.

[ ] move source file into this repo
[ ] review and refactor if needed. currently only works well with estimator v1 but not v2. Address any feedback from product review

update: this issue is now also covering the sampler scaling notebook too:
This tutorial is based on a summit demo and was refactored by Ritajit on Nate's team, please work with him on this issue.

[ ]  move source file into this repo
[ ]  review and refactor if needed. Address any feedback from product review in QTE repo

The original notebooks were designed for a Summit presentation. The needs of a tutorial on the learning platform are a bit different, and I'd like to make a few changes for pedagogical reasons:

Replace usage of MBL circuit and operators with EfficientSU2 and random operators. Using a circuit included in Qiskit's circuit library allows the tutorial to focus on the learning goal, which is to teach how to use error mitigation with Qiskit Runtime.
Use different simulation strategies for the two notebooks, to reduce duplicated content:

Keep mirror circuits for estimator tutorial.
Use Cliffordization for sampler tutorial.

For the sampler tutorial, omit computation of expectation values, and just treat the bitstring distribution as the outcome. This avoids potential confusion about the purposes of each primitive, since the Estimator is recommended for expectation values.


Admin page is broken

Issue only affects production app, seems to be caused by some changes in how I store users in the DB.


kool self-update insists on elevated permission when not necessary

Describe the bug
When kool is installed in a location writable by the current user, kool self-update should not require elevated privileges.
Kool version and environment
kool version 1.13.2
Ubuntu 21.04
To Reproduce
$ curl -fsSL https://kool.dev/install | BIN_PATH=$HOME/bin/kool bash
$ kool self-update
[error] Updating kool version
you need to use 'sudo' to perform this task
$

Expected behavior
Since $HOME/bin/kool is writable by the current user, I would expect kool self-update to update itself.

Thanks for the ticket @magne !
We have added that because the usual installation under Linux does require it... we can improve it to really check the "writeability" of the current user on the binary, hence only showing the alert when really necessary.

PR ready #381 - should go into next release.

This has been implemented within our latest release 1.15.0.


ChatLiteLLMRouter ignores specified model selection (overrides it by taking the 1st)

I've encountered an issue with ChatLiteLLMRouter where it ignores the model I specify. Instead, it defaults to using the first model in its list (which can be even with a wrong type). This behavior seems tied to the invocation of:
self._set_model_for_completion()

Here's what's happening: I set up the router with my chosen model like this:
chat = ChatLiteLLMRouter(model="gpt-4-0613", router=LiteLLMRouterFactory().router())

And then, when I attempt to process messages:
message = HumanMessage(content="Hello")
response = await chat.agenerate([[message], [message]])

It ignores my model choice. The culprit appears to be the line that sets the model to the first item in the model list within _set_model_for_completion:
https://github.com/langchain-ai/langchain/blob/5d220975fc563a92f41aeb0907e8c3819da073f5/libs/community/langchain_community/chat_models/litellm_router.py#L176
because of:
 def _set_model_for_completion(self) -> None:
        # use first model name (aka: model group),
        # since we can only pass one to the router completion functions
        self.model = self.router.model_list[0]["model_name"]

Removing the mentioned line corrects the issue, and the router then correctly uses the model I initially specified.
Is this intended behavior, or a bug that we can fix?
If in some cases that setting is still needed, it can be fixed like this:
if self.model is None:
    self.model = self.router.model_list[0]["model_name"]

System Info
langchain==0.1.12
langchain-community==0.0.28
langchain-core==0.1.32
langchain-experimental==0.0.49
langchain-openai==0.0.8
langchain-text-splitters==0.0.1

@bburgin Is it possible to have your comment on this?

Hello, @yuriykuzin @m-revetria ,
Still the issue present, But this has been closed as stale. Any workaround or plans for fixing this issue from the Langchain team?


docs/dev-proc/versioning.md: add DSE releases

Oops, I didn't notice @macpijan reviewer, sorry...

Reverted and added @macpijan as rviewer here: https://github.com/Dasharo/docs/pull/498


Easings float operator

An operator similar to [Spring] and [Damp]
We can select the easing function and set the duration.
This operator creates transitions between changing input values, perfect for animating any step change.
Note: The input value should evolve in steps (e.g., sudden changes) to fully utilize the easing effect.
Easing functions source: https://easings.net/

love this and long overdue 🙏 - i'd definitely want the type selection to be Enum-based though
If you can, pls define the enum in a separate .cs file to avoid issues when duplicating operators
It might also make things simpler on the user end to remove the Strength slot if we can live without it? since it only affects a couple of them, it would confuse me

Thanks a lot for your feedback.
I will start working on the separate .cs file now.
It's true that the Strength is not necessary since for more granular controls we have the Spring operators and they allow to reach the same kind of animation.

oh, i didnt mean separate the easing functions into a separate file! But I would happily take that change bc these functions could be useful for the editor >:) or the core math library! hell, the whole functiion float East(float val, EasingType type) could be a really nice to have as an editor/core math function. But we can pull that out when these ops get merged into main
what I meant was to make an enum instead of a switch statement on an integer (which you've done!) and have that in a separate file, so the input Ease would be
InputSlot<EasingType> Ease = new();
Seems like you're already in the process of doing so, just wanted to clarify bc i feel bad if I encouraged you to do more work than you needed to 😅
I also say this not knowing how well the editor supports just adding an enum slot like that though... 🤷♂

I think the way I did it is okay. I have the enum and functions in [EasingFunctions.cs] So I can use them in any operator like Easings or EasingsVec3. Creating EasingsVec2 will be straight forward.
About InputSlot<EasingType> Ease = new(); , I have no idea how I could do that, I'm just following how it's done in the other operators, with an interger.
[Input(Guid = "9ef45ff9-9d59-44b7-b03d-37a1be40a776", MappedType = typeof(EasingFunctions.EasingType))]
        public readonly InputSlot<int> Ease = new();

Right now the only way to see the dropdown menu with the enums in the parameters window of an operator is to add , MappedType = typeof(EasingFunctions.EasingType) and the enums to the cs file of an operator.
Thus, duplicating such operator within the editor will give a int and won't show a dropdown menu.

This how the parameter window looks like


French - Basics/Containers

Related to #9
Just started - only intro for the moment

Far from perfect but review and feedback are welcome, please and thanks in advance :smile: :pray:

Thanks a lot @Ptival, I'm going to manage all of your comments as soon as possible 👍

@Maeevick To answer your question in Slack, yes I feel it is necessary for now to pause the containers translation until it has reached stability and that you won't have to regularly check it before publishing the French content. You and @Ptival will be notified when the French translation will be mergeable. :)

@Maeevick To answer your question in Slack, yes I feel it is necessary for now to pause the containers translation until it has reached stability and that you won't have to regularly check it before publishing the French content. You and @Ptival will be notified when the French translation will be mergeable. :)

Thanks @Kleidukos, in consequence I will update with @Ptival 's suggestions when notified 👍


Ignore lightweight tags

close #180
referencing #127 also

Codecov Report

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

@@           Coverage Diff           @@
##             main     #183   +/-   ##
=======================================
  Coverage        ?   83.05%
=======================================
  Files           ?       16
  Lines           ?     1475
  Branches        ?        0
=======================================
  Hits            ?     1225
  Misses          ?      250
  Partials        ?        0

Continue to review full report at Codecov.

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


missing connection_name in output

I want to use connection_name for cloud_sql_proxy, but this module doesn't output this basic value

The example shows how to construct the connection name, we should definitely make this an output variable of the module.

Fixed by #21.


Check availability for assets not working

A user came by on a Galaxy S8 and the check availability functionality for assets was not working. The text changed to checking availability..., but then changed back. And there was no green / red indication of availability.

Do you have more information about this?


[Bug]Checkpoint does not update automatically

Search before asking

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

Java Version
1.8.0_311
Scala Version
2.12.x
StreamPark Version
2.1.5
Flink Version
1.17.0
deploy mode
yarn-application
What happened
I found that the checkpoint is not automatically updated and saved, occasionally it works, but most of the time it doesn't work and won't automatically update and save the checkpoint. Currently, I am using Flinksql and submitting in yarn application mode. Could you please help me take a look? What could be the possible reason?

Error Exception
There are no obvious errors in the log, only the alarms related to the database are as follows. Will this alarm have any impact? How to eliminate this alarm?

Screenshots

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!(您是否要贡献这个PR?)

Code of Conduct

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

This is a known bug that has been fixed in version 2.1.5. Please refer to this issue


Plutus v2 delegation with reference script build raw

points to discuss:
*tx_raw_output.withdrawals and [s.txout for s in tx_raw_output.script_withdrawals] have the same tx
db_withdrawals = sorted(response.withdrawals) have just one (not duplicated)
the fee calculated by calculate_tx_fee is returning very low values, to the tests works I have to double it.


Add a destination integration test

Description
I've added a destination integration test.
Quick checks:

[x] I have followed the Code Guidelines.
[x] There is no other pull request for the same update/change.
[x] I have written unit tests.
[x] I have made sure that the PR is of reasonable size and can be easily reviewed.

@voscob Doesn't it make sense to add a simple docker-compose file to run along with the tests?

@voscob Doesn't it make sense to add a simple docker-compose file to run along with the tests?

It is good idea, but I think it is not necessary for current moment


Add ReactNode to Toast description prop type

Add ReactNode to Toast description prop type.
Needed to provide a progress bar to the transaction toast.

nitpick: in string | ReactNode, the string | part could be removed

Just curious, why is it preferred?


[FEATURE REQUEST] The mechanism for combining units

Describe the feature
The function refers to #45
The function refers to #46
The function allows officers to independently unite in a paired unit.
When combined, two units receive a common callsign according to the formula specified in the settings
What should an officer do?

Find a partner in the list of units

Click on the corresponding button (or the functionality of the right mouse button)

units will be combined into a paired unit.

In the general callsign for $callsign2$, the value of the officer who merged the records is taken
For pair units, the department and division are not displayed because they can be differs.
Status becomes shared
The control button changes the status for the general unit, i.e. for two officers at once and separates the units back

Additionally, a paired unit can be shown visually in the table.
Additional Context
No response

This could be released by Friday :)


Ensure Tests are Run and Pass Before Deployment

User Story(s):
As product owner, I want code to flow through my pipelines in a manner that ensures quality and reliable output for my users.
Description: Tests must pass for code to reach Prod deployment.

all our tests are passing on the github action playwright workflow


Where can I download the dev version?

Where can I download the dev version?

A link to the CI where you can download the dev version is over here https://github.com/Frederikam/Lavalink#server-configuration

thx you, you mean this:
https://ci.fredboat.com/viewLog.html?buildId=lastSuccessful&buildTypeId=Lavalink_Build&tab=artifacts&guest=1

as you can see if you click this is a direct link to latest master.

as you can see if you click this is a direct link to latest master.

But this is dev version? It looks like lastest official version

ok and where is the dev version?

I have problems with lavalink. I play a track and lavalink skipped this instant.

stop spamming this issue latestcdev version does not have a fix for this yet
pr is made & we are waiting for fred to merge it

No its not the dev version its the latest version

https://ci.fredboat.com/viewLog.html?buildId=8762&buildTypeId=Lavalink_Build&tab=artifacts&branch_Lavalink=refs%2Fheads%2Fdev

https://ci.fredboat.com/viewLog.html?buildId=8762&buildTypeId=Lavalink_Build&tab=artifacts&branch_Lavalink=refs%2Fheads%2Fdev

https://ci.fredboat.com/viewLog.html?buildId=8762&buildTypeId=Lavalink_Build&tab=artifacts&branch_Lavalink=refs%2Fheads%2Fdev

This is the latest?

yes its latest dev??

Ok sry I clicked on close

Can yiu help me pls whats wrong?

https://github.com/Frederikam/Lavalink/issues/463#issuecomment-811741538
https://github.com/Frederikam/Lavalink/pull/464

#463 (comment)
#464

Ok thx but nothing worked as everything was described

You're getting that error on an old lavaplayer version.
Update to the latest lavalink (either master or dev)


Okuribito does not correspond to question mark operator

/Users/ym/works/okuribito/lib/okuribito.rb:28:in `instance_variable_set': `@following?_i_called' is not allowed as an instance variable name (NameError)
        from /Users/ym/works/okuribito/lib/okuribito.rb:28:in `define_patch'
        from /Users/ym/works/okuribito/lib/okuribito.rb:80:in `block (3 levels) in patch_okuribito'
        from /Users/ym/works/okuribito/lib/okuribito.rb:79:in `module_eval'
        from /Users/ym/works/okuribito/lib/okuribito.rb:79:in `block (2 levels) in patch_okuribito'
        from /Users/ym/works/okuribito/lib/okuribito.rb:71:in `each'
        from /Users/ym/works/okuribito/lib/okuribito.rb:71:in `block in patch_okuribito'
        from /Users/ym/works/okuribito/lib/okuribito.rb:70:in `class_eval'
        from /Users/ym/works/okuribito/lib/okuribito.rb:70:in `patch_okuribito'
        from /Users/ym/works/okuribito/lib/okuribito.rb:42:in `block in apply'
        from /Users/ym/works/okuribito/lib/okuribito.rb:41:in `each'
        from /Users/ym/works/okuribito/lib/okuribito.rb:41:in `apply'

Corresponded!


Improve periodicity of channel bathymetry

Needed for experiments vopikamm/dino-experiments#1 . When choosing a less steep Scottia-arc, differences between the western and eastern channel bathymetry become bigger, violating a smooth periodicity.
Idea: Use the central gauss-ring profile (western boundary) to taper the entire channel --> periodic bathymetry

Fixed by tapering all boundaries towards a flat bottom everywhere and specifically the Scottia-Arc towards the easter (and western when periodic) boundary. Only works when the channel is located at the southern boundary.


[Todoist] Allow a user to schedule a task for a specified duration

Extension
https://www.raycast.com/doist/todoist
Description
First of all, thank you for this great extension; it has significantly improved my workflow.
Currently, when creating a new task, the following fields are available:

Title
Description
Due date
Priority
Project
Labels
File
Parent Task

Users cannot specify how long they want to schedule the task.
Additionally, when editing a task, the following fields can be modified:

Title
Description

Users are unable to edit the due date or duration of the task after it has been created.
This limitation is inconvenient because users must either make these changes through the Todoist app or recreate the task with the updated fields.
Who will benefit from this feature?
All users
Anything else?
No response

The duration field appears only when you've selected a date with time, so it's already possible to do so 🙂


Add Sapho Chart

@k8s-bot ok to test

Thanks for the submission @lodotek!
Can you remove the vendored mysql in the charts/ directory? You should be able to use helm dep update to pull in the packaged mysql chart which will be ignored in git. The CI will automatically do this when packaging the chart for the repository.
Also, AFAICT this meets the requirements to be included in the stable repo, so you can move this to the stable folder :).

I have made the requested changes, please test again.
Thank you!

@prydonius I'd love to demo this soon - any chance this is ready to go?

Anything else needed from me to get this PR approved?

@lodotek MySQL was failing for me due to ERROR 1396 (HY000) at line 1: Operation CREATE USER failed for 'root'@'%' when persistence is enabled. Both MySQL and Sapho started up fine for me when I removed the mysqlUser: root setting from values.yaml and re-enabled persistence.
If you're having issues with PVCs getting bound, does your cluster support dynamic provisioning?

@lodotek is there any reason you want to keep this in incubator? I would move it to stable since it meets the requirements.

@prydonius Thank you for all you help and suggestions.  Regarding your comment about why am I keeping this in incubator. I thought this PR needs to be approved first, no?

@lodotek no worries! As long as a chart meets the requirements listed in CONTRIBUTING.md it can be submitted in the stable repo. The incubator repo is for charts that don't meet these requirements (for example, using k8s alpha features), but can be improved on until they are ready to be moved into stable.
So since this already meets the requirements, it can be submitted directly to stable. Sorry for the confusion there.

@viglesiasce this worked for me, can you check again if you're seeing the same issue you had before?

Im still seeing the same issue as before when installing in a fresh cluster. This is likely due to the MySQL image being pulled for the first time and taking a while to come up.
Caused by: java.net.SocketTimeoutException: connect timed out
        at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_111]
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_111]
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_111]
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_111]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_111]
        at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_111]
        at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:211) ~[mysql-connector-java-5.1.39.jar:5.1.39]
        at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:300) ~[mysql-connector-java-5.1.39.jar:5.1.39]
        ... 63 common frames omitted
00:11:59.735 [localhost-startStop-1] ERROR s.s.SaphoServletContextListener -

********************************************************************************

Cannot start Sapho:
- Sapho context cannot be started. Missing injection context.
Error creating bean with name 'entityManagerFactory' defined in class path resource [spring-sapho-database.xml]: Cannot resolve reference to bean 'dataSource' while setting bean property 'dataSource'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [spring-sapho-database.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.zaxxer.hikari.HikariDataSource]: Constructor threw exception; nested exception is com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

Eventually the pod was restarted due to failing its liveness check. At that point it came up fine.
@lodotek can you add something to the NOTES.txt that instructs user to be patient as the app and db come up?

@k8s-bot e2e test this


Kompendium does not respect naming strategy

I do not know if the issue is something Kompendium can solve, but here is an outline of the issue:
For the Json serializer a naming strategy can be specified:

This allows the serialization and deserialization of keys in different casing. For example the schema

would serialize to

Though, Kompendium generates this spec without applying the naming strategy:

interesting, i had no idea that kotlinx serialization supported across the board naming strategies.
definitely a feature we should implement.  thanks for reporting!


HTTP/1.1 parser fix, when response contains empty reason

Sometimes response can come w/o reason-phrase.
Changes made according to the rfc2616 (6.1.1): The client is not required to examine or display the Reason- Phrase.

@Lukasa thanks for the advice! Fixed according to the RFC and PEP


Allow for custom nginx configuration for streams in WebUI

Is your feature request related to a problem? Please describe.

NPM streams does not have an 'advanced' tab for custom nginx configuration similar to nginx proxies. There are some use cases where this would be handy. See here:
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3619
Describe the solution you'd like

Allow for nginx custom configuration on streams through the WebUI
Describe alternatives you've considered

Manually editing the files which could break NPM's relationship to the configuration file based upon the stream template
https://github.com/NginxProxyManager/nginx-proxy-manager/blob/d40f9e06fc25acbf6906663edcef462a1a902cdf/backend/templates/stream.conf
EDIT: I just found the advanced documentation which says to do what I mentioned above, and this will technically allow for custom configs to not break NPM's generation of configs
Additional context

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3619

I've just done a fresh  install in an test environement and added a stream on port 3306, but I notice that
# Files generated by NPM
include /data/nginx/stream/ is empty.

After checking it's my entire /data that's empty, no files, just the folder structure.
I do have persistent data after deleting the container.
So I'm going to wait for the WebUI modification to enable load_balancing.

bumping

Bump


python3Packages.pylast: 4.1.0 -> 4.2.0

Motivation for this change
Update to latest upstream release 4.2.0
Change log: https://github.com/pylast/pylast/blob/master/CHANGELOG.md#420---2021-03-14
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.


Improve dev, eslint and Jest experience

Caches are currently a problem; is also bit slow.

Things I haven't done:

Enable something like Browsersync (not as simple as when serving static files, as we want to reload when the app has reloaded rather than when the file has changed)
Disable Jest/ESlint caches (seeing if the changes here improve it)

In fact, wanted to try and remove Jest's runInBand and set the testEnvironment to Node.

runInBand removal in https://github.com/libero/prc/commit/74ea70b34a3770b6c052c3e54630a7402ec0d797.


[Infra] Remove explicit Ruby versioning from workflows

Context
Following #9921, we no longer have to specify the ruby version for each job as it will be inferred from the .ruby-version file at root.
Done by piping all workflows into a sed where the two lines after the pattern are removed.
find .github/workflows -name '*.yml' | xargs sed -i '' -e '/setup-ruby/{n;N;d;}'

You can see it in action in the GHA below: example
cc: @granluo, @dellabitta, @sunmou99 for GHA related improvement
#no-changelog

inappmessaging / quickstart (pull_request) had a failure... I'm investigating whether it is a regression caused by #9829.

CI failures will be addressed by #9924


[GH-218] Add Node specific configuration options using CLI.

https://github.com/input-output-hk/cardano-shell/issues/218

On the other hand, having a separate file for the Partial types is a good hint at what exactly we should derive/generate automatically.
Ideally we should get this functionality with no structural duplication / "for free".


FancyZone settings on multi-desktops change on reboot

Microsoft PowerToys version
0.78.0
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
FancyZone settings on multi-desktops change on reboot
I'm using two multi-desktops.
I've specified a checkerboard arrangement of 6 on multidesktop A and a vertical row arrangement of 3 on multidesktop B.
After rebooting, the settings on Multidesktop A have changed to 3 vertical rows.
I'd like to be able to reboot and still have the FancyZone settings persist.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/bugreport


Update git-repos extension

Description

Changed the find command for Git Repos so it can handle paths containing unreadable subdirectories
This was happening for me as I have a Volume specifically for projects, and the existing find command was failing due to Apple's magic folders such as .Trashes

Screencast
N/A: contribution to the excellent https://www.raycast.com/moored/git-repos
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Cool, I assume it works, but could you also add and test the same fix to the worktree find function?

@cameronsstone could you look into above comment

I don't use git worktrees much, but this seems to work for them.

Thanks! I think it's good to go

It looks good. Thanks, @cameronsstone, for your contribution.

🎉 🎉 🎉
Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@cameronsstone). Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.

Thanks! I have now connected my raycast account to my github.

Awesome, the bot will automatically reward you 🙂


Reduce memory footprint

After using Pyroscope to analyze the memory usage of the operator, we can see that there's a few places where we're consuming a lot of memory and this needs to be investigated to reduce the amount of memory usage in the operator.

This will be the starting point

This was handled in a set of other issues


ImageOptim: losslessly compress all images

LGTM as there doesn't seem to be any noticeable change in quality. Also I noticed that loading.gif doesn't use the official logo as the background?

LGTM as there doesn't seem to be any noticeable change in quality.

Yes, it's lossless compression. No loss in quality. ImageOptim is great!

Also I noticed that loading.gif doesn't use the official logo as the background?

Yep, intentional. It's the installer spalsh screen, so it's meant to look "half finished" 😉


Adding backend rounding function to HourGroupManager summaries method

The InvoiceDetail view's billable_totals and nonbillable_totals make use of the summaries method on the HourGroupManager. This serves up a sum of all hours values on a bundle of entries by calling the SUM function in the DB.
We want the hours in the (non)billable_totals to reflect the rounding of those hours to two decimal places. Since the summation is happening on the backend, it makes sense to do the rounding there, too.
This change to the summaries function performs that rounding on the backend values. It applies the db function Sum not to the raw hours value but to the result of Func(F('hours'), Value(2), function='ROUND').
Since summaries is only used in that one view, and since there are no tests for it, this change is self-contained and, in theory, complete.

:green_apple:


DOC tutorial on feature handling

What type of documentation

tutorial (examples)

What needs to be documented?

load_annotations()
cogent3.core.sequence.Sequence
cogent3.core.alignment.SequenceCollection
cogent3.core.alignment.Alignment

(The middle two clearly have overlap.) Important issues to identify. User created features are added to a special table, but bulk features are better obtained from gff or genbank.

We will do this for the next release


[Snyk] Security upgrade nginx from 1.21 to 1.26.1

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

web-server/Dockerfile

We recommend upgrading to nginx:1.26.1, as this image has only 93 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Out-of-bounds Write SNYK-DEBIAN11-GLIBC-5927133
  829

Out-of-bounds Write SNYK-DEBIAN11-LIBWEBP-5893094
  829

Resource Exhaustion SNYK-DEBIAN11-NGHTTP2-5953384
  829

Off-by-one Error SNYK-DEBIAN11-LIBTASN16-3061097
  714

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Resource Exhaustion

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Clarification on the statement This component is still actively under development! for policy controller docs

Question

was taking a look at the documentation for Policy Controller and noticed this blurb that says This component is still actively under development! https://github.com/sigstore/docs/blob/main/content/en/policy-controller/overview.md?plain=1#L17. we are looking to implement this controller in production so I just want to confirm what is meant by that statement. I figured it means that new features are actively being added but clarification would be helpful. thanks!

I know folks are using it in their production. We should probably revisit the wording there.


Allow any keys by explicitly coercing them into strings

I notice the internal hashing function is as follows: https://github.com/mattbierner/hamt/blob/88d054a27008976708f76c0ccb4e630e631e4b62/lib/hamt.js#L115-L125
This can be improved by explicitly converting any non-string keys into strings, which result in more representative hashes that otherwise hash to 0:
const hash = str => {
    if (typeof str === 'number')
        return str;

    str = typeof str === 'string' ? str : String(str);
    let hash = 0;
    for (let i = 0, len = str.length; i < len; ++i) {
        const c = str.charCodeAt(i);
        hash = (((hash << 5) - hash) + c) | 0;
    }
    return hash;
};

console.log(hash({})); // -1074417128
console.log(hash(Symbol())); //<PHONE_NUMBER>

Damn, wrong change list number in the commit there. Will reopen.


categorizing and prioritizing the methods, classes etc..

I m trying to prioritize the methods or classes in the typedoc. So far i couldnt find any helpfull solution. would it be possible to prioritize the methods, classes, interfaces etc.. I mean is it possible to change the  view structure without touching the library ?

Could you please provide some examples?

for classes simply putting all the important modules at the top of the document and unimportant modules at the bottom. I mean some kind of grouping the modules and methods.
let me explain it with methods:
lets say i have 3 methods
@priorty = 3  fillDays() {     for (let index = 1; index <= 31; index++) {       this.days.push(index);     }   }   @priorty = 1   fillYears() {     for (let index = this.yearToStart; index <= this.yearToEnd; index++) {       this.years.push(index);     }   }   @priorty = 2   changeDate(_day:number, _month:number, _year:number) {     this.buildDate(_day, _month, _year);   }
and i want to shown in the doc exactly in this order (fillYears, changeDate, fillDays) . so i can highlight the important methods and group them, and unimportant methods at the bottom of the class (like setters and getters etc..).

Partially related is #112


how to connect to µTorrent Server 3.3? (is it possible?)

this is my µTorrent Server 3.3 running on my local network, as seen from my firefox on my laptop.
this is my setup

and this is the error I get when I try to add a magnet link

it is possible that I have setup something wrong... any suggestions to what I can try next?

Ah, okay. So, the host isn't a URL, it's a hostname. You just want <IP_ADDRESS> in that field. I've yet to implement any useful error handling. I should probably validate those fields too.


Update user guide to include borrow command

Coverage remained the same at 92.033% when pulling 2a8a0b55ab5792a91a33268431217d2bb95d1926 on jelneo:update_user_guide into 5e5307d0f302268e5b5954c95e90b9b06c17f51a on CS2103AUG2017-T17-B1:master.


REP-001: Serve Pipeline API

Summary - Serve Pipeline
General Motivation
Production machine learning serving pipelines are getting longer and wider. They often consist of multiple, or even tens of models collectively making a final prediction, such as image / video content classification and tagging, fraud detection pipeline with multiple policies and models, multi-stage ranking and recommendation, etc.
Meanwhile, the size of a model is also growing beyond the memory limit of a single machine due to the exponentially growing number of parameters, such as GPT-3, sparse feature embeddings in recsys models such that the ability to do disaggregated and distributed inference is desirable and future proof.
We want to leverage the programmable and general purpose distributed computing ability of Ray, double down on its unique strengths (scheduling, communication and shared memory) to facilitate authoring, orchestrating, scaling and deployment of complex serving pipelines under one set of DAG API, so a user can program & test multiple models or multiple shards of a single large model dynamically, deploy to production at scale, and upgrade individually.
Key requirements:

Provide the ability to author a DAG of serve nodes to form a complex inference graph.
Pipeline authoring experience should be fully python programmable with support for dynamic selection, control flows, user business logic, etc.
DAG can be instantiated and locally executed using tasks and actors API
DAG can be deployed via declarative and idempotent API, individual nodes can be reconfigured and scaled indepenently.

Should this change be within ray or outside?
main ray project. Changes are made to Ray Core and Ray Serve level.
Stewardship
Required Reviewers
The proposal will be open to the public, but please suggest a few experience Ray contributors in this technical domain whose comments will help this proposal. Ideally, the list should include Ray committers.
@ericl, @edoakes, @simon-mo, @jiaodong
Shepherd of the Proposal (should be a senior committer)
To make the review process more productive, the owner of each proposal should identify a shepherd (should be a senior Ray committer). The shepherd is responsible for working with the owner and making sure the proposal is in good shape (with necessary information) before marking it as ready for broader review.
@ericl
Design and Architecture
Example - Diagram
We want to author a simple diamond-shaped DAG where user provided inputs is send to two models (m1, m2) where each access partial or idential input, and also forward part of original input to the final ensemble stage to compute final output.
               m1.forward(dag_input[0])
            /                          \
    dag_input ----- dag_input[2] ------ ensemble -> dag_output
            \                          /
               m2.forward(dag_input[1])

Example - Code
Classes or functions decorated by ray can be directly used in Ray DAG building.
@ray.remote
class Model:
def __init__(self, val):
    self.val = val
def forward(self, input):
    return self.val * input

@ray.remote
def ensemble(a, b, c):
    return a + b + c

async def request_to_data_int(request: starlette.requests.Request):
    data = await request.body()
    return int(data)

# Args binding, DAG building and input preprocessor definition
with ServeInputNode(preprocessor=request_to_data_int) as dag_input:
    m1 = Model.bind(1)
    m2 = Model.bind(2)
    m1_output = m1.forward.bind(dag_input[0])
    m2_output = m2.forward.bind(dag_input[1])
    ray_dag = ensemble.bind(m1_output, m2_output, dag_input[2])

A DAG authored with Ray DAG API should be locally executable just by Ray Core runtime.
# 1*1 + 2*2 + 3
assert ray.get(ray_dag.execute(1, 2, 3)) == 8

A Ray DAG can be built into an serve application that contains all nodes needed.
# Build, configure and deploy
app = serve.pipeline.build(ray_dag)

Configure individual deployments in app, with same variable name used in ray_dag.
app.m1.set_options(num_replicas=3)
app.m2.set_options(num_replicas=5)

We reserve the name and generate a serve ingress deployment that takes care of HTTP / gRPC, input schema validation, adaption, etc. It's our python interface to configure pipeline ingress.
app.ingress.set_options(num_replicas=10)

# Translate to group_deploy behind the scene
app_handle = app.deploy()

# Serve App is locally executable
assert ray.get(app_handle.remote(1, 2, 3)) == 8

A serve pipeline application can be built into a YAML file for structured deployment, and configurable by the Ops team by directly mutating configurable fields without deep knowledge or involvement of model code in the pipeline.
deployment.yaml = app.to_yaml()

# Structured deployment CLI
serve deploy deployment.yaml

Compatibility, Deprecation, and Migration Plan
An important part of the proposal is to explicitly point out any compability implications of the proposed change. If there is any, we should thouroughly discuss a plan to deprecate existing APIs and migration to the new one(s).

Ray Core

Serve Pipeline is co-designed with Ray Unified DAG API, where each DAG is always authored using Ray DAG API first.
The only new API introduced is .bind() method on ray decorated function or class.

Ray Serve

Serve Pipeline DAG is transformed from Ray DAG where classes used are replaced with serve Deployment and class instances with deployment's RayServeHandle for better compatibility, deprecation as well as migration.

Breaking Changes: Ray Serve

All args and kwargs passed into class or function in Serve Pipeline needs to be JSON serializable, enforced upon build() call.
We need to introduce and abstract out an Ingress component for serve pipeline.

Deprecation

Existing Serve Pipeline Alpha API will be deprecated in favor of Ray Unified DAG API as well as Serve Pipeline Beta.

Migration Plan: Ray Serve

New concepts and API introduced will be applied to Serve Pipeline Beta launch first to minimize compatibility risks. We can expect existing deployment implementation will migrate to Ingress and Serve App APIs later on.
Existing multi-model pipeline using Alpha API or raw deployment handle is expected to be migrated to Pipeline Beta API over time.

Test Plan and Acceptance Criteria
The proposal should discuss how the change will be tested before it can be merged or enabled. It should also include other acceptance criteria including documentation and examples.

Unit and integration test for core components
Benchmarks on common multi-model inference workload
Documentation with representative workload, covered by CI.

(Optional) Follow-on Work

Performance optimizations for multi-model inference, such as communication, multiplexing, scale-to-zero, etc.
UX and UI improvements for better user experience
Exploration of large model Distributed Inference on Serve Pipeline where each node represents a shard of a large model.

Thanks @jiaodong ! Assigning to @edoakes @ericl @simon-mo for reviews

@zhe-thoughts for the process, should this be a PR as well? Or the already merged #3 counts.

@simon-mo : We should use PRs to finalize a REP (so it should mainly be the proposer and the shepherd working on the PR). Then we merge the PR, and the REP becomes a shepherded design proposal.
Then we use the issue to comment on the design proposal. How does it sound? Do you think it's easier to comment on the proposal as a PR?
It's still early in the process and we should iterate

I would imagine the comment process involves proposer iterating on the content to incorporate feedback from the reviewers as well.

We've gotten feedback the separate issue thing is quite confusing. I think we should just stick to routing comments to the main PR, whether or not it's merged. I pushed a change to the README to direct readers to do that.

Thanks @ericl , the process change sounds good to me. @simon-mo also gave that feedback. I think the only downside is that for Markdown, the experience of reviewing the PR could be a bit suboptimal. But overall I agree with making the change.


ERROR OCCURED WHEN RUN "pod install"

I get this error after installing react-native-google-places. It happens when I try running "pod install"
Question
[!] CocoaPods could not find compatible versions for pod "GoogleMaps":
In Podfile:
GoogleMaps
react-native-google-maps (from `../node_modules/react-native-maps`) was resolved to 0.27.1, which depends on
  GoogleMaps (= 3.5.0)

react-native-google-places (from `../node_modules/react-native-google-places`) was resolved to 3.1.2, which depends on
  GoogleMaps (~> 3.1.0)

There are various issues related to react-native-google-places, try some solutions offered there.
I'll close this as it's duplicate


Consider modeling open editors in terminal tabs

By using groups for the splits

We considered this and decided against it, however we will be calling what was "Terminal Tabs" before "Terminal Groups" since tabs refer to single instances now.


Add RTFMVDR module

Add a new design of MVDR module.
The RTFMVDR module supports the method based on the relative transfer function (RTF) and power spectral density (PSD) matrix of noise.
The input arguments are:

multi-channel spectrum.
RTF vector of the target speech
PSD matrix of noise.
reference channel in the microphone array.
diagonal_loading option to enable or disable diagonal loading in matrix inverse computation.
diag_eps for computing the inverse of the matrix.
eps for computing the beamforming weight.
The output of the module is the single-channel complex-valued spectrum for the enhanced speech.

Docs: https://output.circle-artifacts.com/output/job/1fef7f01-57e0-4220-a503-5dc5bd5ab6ee/artifacts/0/docs/transforms.html#rtfmvdr


RLE and Caesar encryption

Student, group: Sargsyan Erik, 3530901/90203
URL: https://github.com/prdumbledore/FirstLabPI
Git approach: git-flow

`+


[Sandbox] Perses

Application contact emails
<EMAIL_ADDRESS>Project Summary
Perses is a dashboard tool to visualize observability data from Prometheus/Thanos/Jaeger.
Project Description
Perses aims to tackle multiple goals:

Become a standard dashboard visualization tool for Prometheus and other datasources. It will focus on being GitOps-compatible and thus enabling a smooth Dashboard-as-Code workflow, via a new and well-defined dashboard definition model.

Provide different npm packages, so that anyone that would like to embed charts and dashboards in their own UI could benefit from the work achieved here. For example, these packages might be used in the future to improve the display of the data in the Prometheus UI.

Offer a Kubernetes-native mode in which dashboard definitions can be deployed into and read from individual application namespaces (using CRDs). For more information you can take a look at the doc which would give you an idea of how it would work.

To be friendly to Dashboard-as-Code users, by providing a complete static validation of the dashboard format. That means you will be able to validate your dashboards in a CI/CD using the Perses CLI (named percli)

Support plugins, to allow users to extend the capacities natively provided.

Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/perses
Project repo URL in scope of application
https://github.com/perses/perses
Additional repos in scope of the application

https://github.com/perses/common
https://github.com/perses/website
https://github.com/perses/helm-charts
https://github.com/perses/perses-operator

Website URL
https://perses.dev
Roadmap
https://github.com/perses/perses/blob/main/ROADMAP.md
Roadmap context
No response
Contributing Guide
https://github.com/perses/perses/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/perses/perses/blob/main/CODE_OF_CONDUCT.md
Adopters
No response
Contributing or Sponsoring Org
No response
Maintainers file
https://github.com/perses/perses/blob/main/MAINTAINERS.md
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
I think it makes sense such a project is part of the CNCF as it is designed to provide dashboard visualization for the graduated projects Prometheus and Jaeger as well as for the incubating project Thanos. Besides, CNCF doesn’t provide any dashboarding solution in the Observability area, so Perses aims to fill this gap.

Being part of the CNCF will provide the project with more visibility, advertising, booth at KubeCon, and the possibility to have a lightning talk during the KubeCon to give some updates.
Benefit to the Landscape
It will provide the end users with an alternative to vendor visualization observability like Grafana or OpenObserve.
It’s really focused on the GitOps aspect and should ease the dashboard creation using the “Dashboard as Code” feature natively provided by the project, which is not really the case with other concurrent projects.
Cloud Native 'Fit'
It should go in the Observability zone along side of Prometheus/Jaeger/Thanos
Cloud Native 'Integration'
It will provide Dashboard visualization to Prometheus, Thanos, Cortex and Jaeger. This way they won’t depend anymore on vendor projects like Grafana.
Cloud Native Overlap
N/A
Similar projects
Grafana
Landscape
No
Business Product or Service to Project separation
N/A
Project presentations
There is no presentation to a TAG but just in case we made a general presentation at PromCon 2023: https://www.youtube.com/watch?v=7G_0TCrcVyg
Project champions

Eric D. Schabell (CNCF Ambassador) (@eschabell)
Dotan Horovits (CNCF Ambassador)
Bartlomiej Plotka (CNCF TAG Observability TL) (@bwplotka)

Additional information
The project is already part of the Linux Foundation, so the move should be smooth :)

Looks like this is part of coredash community - https://github.com/coredashio/community and i see @geekygirldawn @caniszczyk as contributors in that repo ... though https://coredash.io/ seems to be AWOL

We had some ideas for the coredash community that never materialized, so I think it's pretty much dead. The only interesting thing under coredash was Perses, so I'm excited to see them applying for Sandbox :)
@caniszczyk what needs to happen within the LF to spin down / archive the rest of it?

@geekygirldawn once the project decides to move to CNCF and none of the Coredash folks want to keep that existing community running, we can simply archive it at the LF. The assets are easy to transfer over since they are already in the LF (to CNCF).

TAG Contributor strategy has reviewed this project and found the following:

The contributor guide is average.
The governance is a maintainers council also details how people can become team members
The roadmap lists a few major features and hasn't been updated since it was created 5 months ago
There are 10 maintainers, who work for Amadeus IT Group and Chronosphere

This review is for the TOC’s information only.  Sandbox projects are not required to have full governance or contributor documentation.

Observability TAG Review Results

/check-vote

/check-vote

/check-vote

/check-vote

/check-vote

/check-vote

Welcome and congrats on getting accepted as a CNCF Sandbox project!
You can get started on your on-boarding checklist here: https://github.com/cncf/toc/issues/1411
and if you have any questions, please don't hesitate to reach out!

With https://github.com/cncf/toc/issues/1411 created we can go ahead and close this out :)
Congrats again!


Remove erroneous sideEffects in package.json

This unfortunately entirely breaks tree-shaking of the library, but pending resolution of vuejs/rollup-plugin-vue#401 that's not something we can really fix on our end. This takes the approach that working-but-too-big is at least better than not working at all.
I'll explore options for directly using the .vue files from the src directory, but currently the @→src alias makes them break in dependent projects.

Any chance this will get merged soon @brlodi ? Currently using the library and would rather have the entire bundle than none at all.

Any chance this will get merged soon @brlodi ? Currently using the library and would rather have the entire bundle than none at all.

I don't have write access, so it's up to @rektdeckard

I don't have write access, so it's up to @rektdeckard

Hey y'all, apologies for the radio silence. Day job really took over. Merged and going live today.


TabCoordinatable does not deinit when parent coordinator changes its root

This behavior can be observed in the example app. The logout button on the profile screen calls:
AuthenticationService.shared.status = .unauthenticated

which trips the observation in the maincoordinator:
@ViewBuilder func sharedView(_ view: AnyView) -> some View {
        view
            .onReceive(AuthenticationService.shared.$status, perform: { status in
                switch status {
                case .unauthenticated:
                    self.root(\.unauthenticated)
                case .authenticated(let user):
                    self.root(\.authenticated, user)
                }
            })

    }

However, on switching the root, the AuthenticatedCoordinator does not deinit and neither do any of its children.
Furthermore, it appears as if Stinsen attempts to redraw the TabCoordinatable as the root is switched. This causes odd behavior like task and onAppear closures being called on the views that were brought into the view hierarchy. To reproduce do the following:

Add a task like so to the TodosScreen

@ViewBuilder var content: some View {
        ScrollView {
            #if !os(iOS)
            button
            #endif
            if todosStore.all.isEmpty {
                InfoText("You have no stored todos.")
            }
            VStack {
                ForEach(todosStore.all) { todo in
                    Button(todo.name, action: {
                        todosRouter.route(to: \.todo, todo.id)
                    })
                }
            }
            .padding(18)
        }
        .navigationTitle(with: "Todos")
        .task {
            print("here at the wall")
        }
    }

Launch the app

Tap "Login" and then navigate to the Todos tab. Note: you will see here at the wall printed in Xcode console.

Navigate to the profile tab and tap "logout"

Observe: "here at the wall" is printed again after the root has been switched to unauthenticated

turns out this might not have anything to do with Stinsen https://developer.apple.com/forums/thread/719521?login=true and https://forums.developer.apple.com/forums/thread/718738


Automatic GSSOC23 Assignment and Redesigned Issue Template ✨

Issue Overview:
Currently, during the GSSOC23 event, there is a need for a streamlined process to assign issues to participants based on their skill levels and interests automatically. This will help ensure a fair distribution of tasks and encourage participants to contribute effectively. Additionally, the current issue template lacks certain essential details, making it harder for participants to understand the problem at hand.
Proposed Solution:
We propose implementing a system that automatically assigns GSSOC23 participants to issues based on their skill levels and interests when they create an issue using the designated issue template. This will enhance the overall experience of participants and promote a more efficient contribution process.
Implementation Details:

Define skill levels: Create a list of relevant skill levels (e.g., Beginner, Intermediate, Advanced) that participants can choose when creating an issue using the template.
Interest tags: Introduce predefined interest tags (e.g., UI/UX, Backend, Frontend) in the issue template that participants can select to specify their area of interest.
Assign script: Develop a script that runs automatically when a new issue is created using the template. The script will analyze the provided skill level and interest tags and assign the issue to the most suitable participant or maintainers.
Notify assignees: Automatically notify the assigned participant about their new task and provide relevant details.

Redesigned Issue Template
Why the Redesign?
The redesigned issue template includes explicit sections for skill levels and interest tags to ensure a better understanding of participants' capabilities and areas of expertise. This will streamline the automatic assignment process during GSSOC23 and enable participants to take up tasks that align with their proficiency and interests, leading to more productive contributions.

Hey @Vaishnavi-Patil2211  Please assign me this issue its impertinent issue


Lap4 se 144 -  Styled Profile Page and Implemented Grid Display for Skills Component

Description
This PR includes styling updates and layout improvements for the profile page, according to the provided hi-fi wireframes. The main changes are:
Profile Page Styling:
Styled the profile page to match the hi-fi wireframes, ensuring consistency with the design.
Skills Component Grid Display:
Implemented a grid display for the skills component.
The layout now displays 4 skills per row. If there are more skills, a new row is created, keeping the design clean and organized.
Modal Header and Footer:
The header and footer within the modal are now fixed, making the body content scrollable.

Approved. It looks great so far based on the description. There are still some styling details which I believe are going to be updated later.


Onehic.py: list index out of range

Hi, when I used "onehic.py", I got the error "IndexError: list index out of range". I am unsure what the "list index" refers to.
genome size: 3.3 Gb, hic size: 4.7 Gb.
"slurm-3620847.log" provides more details.
slurm-3620847.log

Can you also send me the running command? It is best if you share the hic and assembly files with me and I can help you solve the problem locally. @mushroomOK

From the preliminary judgment of the log, it seems that you used the genome.fasta file as the input of assembly

Thank you for your prompt response! After further investigation, I have confirmed that I used "genome.fasta" as the input for the "-asy" parameter, which was the root cause of the problem.


Support regex-less relabling

Hi,
not feeling too strongly about it but definitely a nice to have which arguably would be less complex to manage as a a user than the regex we have right now. It think I never had an actual need for an regex.
We should support action: replace without a regex, which would simply make all labels available in the replacement. This could be look like this:
- action: replace
  target_label: new_label
  replacement: "foo/${__meta_foo}/${__address__}/bla/${__meta_bar}"

Alternatively we could keep source_labels and just map them 1:1 to position args in replacement:
- action: replace
  source_labels: [ __meta_foo, __address__, __meta_bar ]
  target_label: new_label
  replacement: "foo/${1}/${2}/bla/${3}"

Might need to be a new action though since the current behavior is different.
Feel free to close this if it seems out of scope but I believe it makes one of the most mind bending parts of the prometheus config much easier to understand.

The question I would ask is what does this allow that relabelling already doesn't?
I've seen very few cases where such syntactic sugar would help, and having more than one way to do things is rarely a win for users. Particularly for something like relabelling.

Heh, funny, we just ran into a limitation of relabel rules (as mentioned in #2545) which could be solved by interpolation of labels in other fields. This would make it possible to configure k8s discovery only with relabel rules.
- action: keep
  source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_ports] # comma separated list of ports for example
  regex: "(^|,){{ __meta_kubernetes_pod_container_port_number }}($|,)"
- action: replace
  source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
  target_label: __address__
  regex: '(.+?)(?::\d+)?;(\d+)'
  replacement: $1:$2

The second rule could then also be rewritten as follows, close to @discordianfish suggestion:
- action: replace
  target_label: __addess__
  replacement: {{ __meta_kubernetes_pod_ip }}:{{ __meta_kubernetes_pod_container_port_number }}

That's a bit of a different feature again, and you've yet to demonstrate that what you want to do isn't already possible with relabel rules.
I note that the Go regex library does not support what's being requested here.

My intention wasn't to support something that isn't possible yet. My goal would be to make Prometheus more accessible by making relabing more readable ultimately reducing support efforts and drive adoption.

How often does this pattern come up? As I've said I believe replace actions that'd benefit from this are quite rare (e.g. there's none in the k8 example, and that's on the complex side as relabelling goes; nor does it help with the blackbox/snmp pattern).
To add what is basically another templating language to Prometheus, I think we'd want something like this to be very common to balance against the complexity&confusion that an additional language and syntax would cause.

@wjoel That is unrelated to this issue.

Per the bug scrub this is not something that is currently desired, so I'm going to close this off.


Contributing doc on serving Keras model via REST API

Hi Keras team - I'm interested in contributing documentation on serving trained Keras models via REST API with bentoml/BentoML and deploying the model server to Kubernetes. BentoML is an open-source tool I've been working on, for high-performance model serving.
I'm thinking of contributing a guide similar to the documentation we are adding for FastAI here, and it will be based on one of the BentoML's Keras example notebooks: https://docs.bentoml.org/en/latest/examples.html#tensorflow-keras, e.g. the BentoML Keras example project: Movie Review Sentiment with BERT https://github.com/bentoml/gallery/blob/master/tensorflow/bert/bert_movie_reviews.ipynb
I noticed this is not something in the "call for contributions" list, so before I started, I would love to understand if the topic "model deployment / productionizing trained model" is something Keras team would be interested in adding to https://keras.io/guides/ and if so, where does it fit best in there.

You can refer the document for contributing details here https://github.com/keras-team/keras-io/blob/master/call_for_contributions.md


Adding title props in both backIconButtonProps and nextIconButtonProps

Hello, guys. This is my first Github contribution. I noticed that the textLabel for 'next' and 'previous' were not being applied in the titles for the 'nex't and 'previous' buttons in the pagination area. Only the aria-label were being applied. So, I made this correction to add both titles. Please, let me know if you need anymore information on this PR.

Coverage remained the same at 83.778% when pulling 9a905b7702571f970cddf09c58342d357e7411e8 on Ruriel:bugfix/issue-1247-next-page-and-previous-page-titles into d50ff23334c28035a244233b844501f89afddf7e on gregnb:master.

Thank you for your contribution, I'll merge it in for the next release (should be within the next hour or so).

@Ruriel @patorjk Thanks for helping support this library.
May I know if there's a way to directly access the nextIconButtonProps?
I want to be able to override the 'disable' attribute for it. As one of my use cases is that I want to disable the pagination forward button when data is being fetched, this way I am not allow triggering of additional api calls until the initial call has returned.
Thank you for your time.


Not able to skip tls check when dealing with https rest

Hello
Is there a way to skip tls check , in order to be able to deal with https rest witch is using an auto signed certificate
With https i'am getting net::ERR_CERT_AUTHORITY_INVALID
NB : tls check disabled is already implemented in other plugins
Thanks

Hi @abenbouz
do you have an example of other plugins not using TLS checks?
This plugin runs completely in on the browser/client so there is less flexibility available.

I have the same need.
For some reason I have to call an api rest on another url than his real one and the certificate doesnt fit.
it coulb be a good thing to be able to skip tls check.
Skip tls his present on all datasources of grafana I think.
It s an ehancement that we can find on many development.

As far as this Plugin goes, it is mostly a browser enforced thing.
And to be clear: This plugin intentionally uses the browser to trigger the URL, not the backend (as for what my use case is)


[Feature][wip] add signin to navbar

Purpose
Add sign in functionality to the OSF navbar
Changes
Users can log in via the navbar
Side Effects
Componetize the navbar viewmodel similar to the wiki-one-page
Notes
Depends-on-PR: #1728
Closes-issue: #1648
Build will fail until dependency is merged.
Need review
[skip ci]

@HarryRybacki could you get this PR up to date with current develop?

Will do.
On Fri, Mar 6, 2015 at 9:44 AM, Steven Loria<EMAIL_ADDRESS>wrote:

@HarryRybacki https://github.com/HarryRybacki could you get this PR up
to date with current develop?
—
Reply to this email directly or view it on GitHub
https://github.com/CenterForOpenScience/osf.io/pull/1865#issuecomment-77569189
.

--
Harry Rybacki - Developer, Center for Open Science
Research: http://scinet.osf.io
Blog: http://rybacki.io
[image: http://github.com/harryrybacki]
http://github.com/HarryRybacki [image:
https://twitter.com/HarryRybacki] https://twitter.com/HarryRybacki [image:
http://www.linkedin.com/in/HarryRybacki/]
http://www.linkedin.com/in/HarryRybacki/ [image:
https://plus.google.com/+HarryRybacki]
https://plus.google.com/+HarryRybacki

Remove "Signin" here.

The hover state of "Forgot password" looks different from the other buttons in the navbar.

@sloria I remember seeing that odd hover thing now. I looked at it but had no clue -- @caneruguz any initial thoughts?

1st pass finished. :sunny: Looking good.

The hover will only apply if the structure of that link is the same as the others. You need to check how the css and html hierarchy is formed.

Now that JS tests, are on develop, can you please add unit tests for the ViewModel?

Pass finished. :vhs:

@sloria ready for second pass


Highlight hovered line

resolves #3265
In the diff page i added a top and bottom border around the line instead of background.

will have a look tomorrow. Conceptually look fine, but I think colors could be better. And also the highlight method (background in repo and borders in diff - I think should be unified)

I added the borders not to clash with the diff colors, but it never occurred to me to go back and use borders everywhere. Will try.

Maybe use just bottom border to underline hovel line (but I'm not sure it is a good idea)
or maybe add a shadow effect to "rise" the hover item above the table
or just use the color but with opacity so that diff main color is tinted but not lost completely

Without visual test I think that the last could be the best.

just in case, adjusting the font (e.g. bold) would be bad idea because of element size change. Color of font is also not an option as there are these icon-like things

pending @FreHu ?

Will do some experiments in the evening.

no hurry, just getting an overview of what the status is

In the end i decided not to add highlight for the diff

a border does not look good in the old browser, the borders always look very rough, if you compare to vscode's border.

effects are nice to play around with (increasing font size is fun) but the result is way too jumpy like scbcgua said.
a background color can clash with both syntax highlighting and diff colors, so i think it's too much.

The yellow was changed to a less aggressive color

yellow and yellow ... hmmm.
let me look at it tomorrow. I have one idea to check. otherwise I'll approve.

I am known for liking bright colors way more than other people, so I'll go with your suggestion.

Also fixing some syntax errors in the dark theme css.

@FreHu please update/rebase the branch to master, I cannot click the "update branch" button for some reason


[WIP] Handling of phase transitions

Codecov Report

Merging #123 into master will decrease coverage by 0.54%.
The diff coverage is 60.41%.

@@            Coverage Diff             @@
##           master     #123      +/-   ##
==========================================
- Coverage   86.79%   86.25%   -0.55%
==========================================
  Files          15       16       +1
  Lines        2083     2131      +48
==========================================
+ Hits         1808     1838      +30
- Misses        275      293      +18

Impacted Files
Coverage Δ

biorbd_optim/phase_transition.py
53.65% <53.65%> (ø)

biorbd_optim/__init__.py
100.00% <100.00%> (ø)

biorbd_optim/constraints.py
94.95% <100.00%> (+0.08%)
:arrow_up:

biorbd_optim/optimal_control_program.py
82.33% <100.00%> (+0.42%)
:arrow_up:

Continue to review full report at Codecov.

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

Good job!

This solves the #83, #94