Detect Ansys Student version

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
The Student versions are installed under:
C:\Program Files\ANSYS Inc\ANSYS Student

PyMAPDL should be able to find them and use them.
Steps To Reproduce
N/A
Which Operating System are you using?
Windows
Which Python version are you using?
3.7
Installed packages
NA

It seems that the student version does not successfully check the license. See #1330


Is this project alive? January 2019

I wasn't able to get this from rubygems.org 😞

@Alxzu Sorry about that, I never published the gem and have been using it my own project directly from github. I can try to release it to rubygems sometime soon. I haven't been actively working on it lately, but the core functionality seems to get the job done and contributions are always welcome!

after getting another request to release this on ruby gems, I finally got around to it. https://rubygems.org/gems/magic-link


[feature request] Add to AUR repos

[feature request] Add to AUR repos
That'd be really nice and shouldn't be a biggie hopefully!

Sorry, what is "AUR"?


handshake error: bad "Connection" header

Thank you for publishing this example. I get this error after running bin/chat on Mac OS X terminal, after successfully running Make.
2020/01/21 19:44:11 [::1]:3333 > [::1]:58202: upgrade error: handshake error: bad "Connection" header

> $ ./chat                                                                                [±master ●●] 2020/08/16 20:10:38 websocket is listening on [::]:3333 2020/08/16 20:11:01 [::1]:3333 > [::1]:52065: upgrade error: EOF 2020/08/16 20:11:21 <IP_ADDRESS>:3333 > <IP_ADDRESS>:52069: upgrade error: handshake error: bad "Connection" header


EgressNetworkPolicy cannot be created?

Type of question
Help
Question
What did you do?
I am trying to create NetworkEgressPolicy objects.
What did you expect to see?
I expected the object to be created.
What did you see instead? Under which circumstances?
I'm using the sample project, listening for changes on a custom resource which works fine, and then modifying the handler function to execute this code:
func newEgressNetworkPolicy (cr *v1alpha1.App) *networkapi.EgressNetworkPolicy {
	addedElement := []networkapi.EgressNetworkPolicyRule{
		networkapi.EgressNetworkPolicyRule{
		networkapi.EgressNetworkPolicyRuleAllow,
		networkapi.EgressNetworkPolicyPeer{CIDRSelector: "<IP_ADDRESS>/32"},
	}}

	return &networkapi.EgressNetworkPolicy{
		TypeMeta: metav1.TypeMeta{
			Kind:       "EgressNetworkPolicy",
			APIVersion: "network.openshift.io/v1",
		},
		ObjectMeta: metav1.ObjectMeta{
			Name:      "default",
			Namespace: cr.Namespace,
		},
		Spec: networkapi.EgressNetworkPolicySpec{
			Egress: addedElement,
		},
	}
}

Result is this:
time="2018-10-26T14:08:46+02:00" level=error msg="failed to create egress rule : EgressNetworkPolicy \"\" is invalid: metadata.name: Required value: name or generateName is required"

Environment

operator-sdk version: 0.0.6

Kubernetes version information:

openshift v3.10.0+91d44f1-52
kubernetes v1.10.0+b81c8f8

@mojsha Thanks for the report! From what I can tell the resource seems valid, e.g. has a name. If you create the same EgressNetworkPolicy resource by hand (e.g. with oc create -f enp.yaml) does it succeed?

@LiliC I believe so:
$ oc create -f enp.yaml
egressnetworkpolicy.network.openshift.io "default" created
$ cat enp.yaml
kind: EgressNetworkPolicy
apiVersion: v1
metadata:
  name: default
spec:
  egress:
  - type: Allow
    to:
     cidrSelector: <IP_ADDRESS>/32

@mojsha Thanks! Just pinging others if they have any more ideas.
cc @hasbro17 @AlexNPavel

I was able to get the same error from the command line by not setting ObjectMeta.Name. Any chance you could double check the object before you attempt to create it?

@shawn-hurley Not sure what you want to gain from that? The problem at hand is basically that I think I am setting the name and it still fails. If I don't set the name, it is a given that it won't work?

@mojsha I think what @shawn-hurley is to doublec check the name is not empty before passing it to create. If it is not empty than the problem most likely is in the Create. So right before you call Create(egp) do a check like if egp.ObjectMeta.Name == "", egp being the object you  get from newEgressNetworkPolicy.

@mojsha Hello, just checking back, did you manage to resolve your problem?


Documentation: "getting-started" link on the Getting Started page is broken

On the Getting Started page, in the "What isn’t Route?" section, there is a link to "getting-started" - this link is broken. I was going to PR a fix but I can't actually figure out what section you intended to link to, as we are already on the Getting Started page, so it wouldn't be super helpful to link to the same page. I would be happy to do a PR to simply remove this sentence if it's left over from a different version of the docs maybe?

Fixed in #200


[WFLY-15586] Upgrade spullara.mustache.java 0.9.10

Fixes https://issues.redhat.com/browse/WFLY-15586

@boris-unckel sorry another merge conflict.

@fl4via Could you check this PR, please?
@darranl fyi merge conflict is resolved

Thanks, @boris-unckel


Build better production bundles

Added/configured:

production build of React
strip non-english locales for moment.js
uglify
gzip

The result is:

bundle.js went from 2.3MB to 163kB gzip'ed
style.css went from 36KB to to 5.3kB gzip'ed

Just an FYI I was reading in the express js docs on compression:

For a high-traffic website in production, the best way to put compression in place is to implement it at a reverse proxy level (see Use a reverse proxy). In that case, you do not need to use compression middleware. For details on enabling gzip compression in Nginx, see Module ngx_http_gzip_module in the Nginx documentation.

i.e. if you've got nginx or another web server in front of your app, then enable gzip there instead of in express.

Yes, you're totally right.  I was just trying to keep it simple.
I would also like to split the config files, but wanted to keep the diff sufficiently small to make it manageable.
Note also that the JSON payloads  for a long running app (big assumption!), can dominate the total network activity. In that case, the mere 2 static assets above might just disappear in the wash.

Cool just thought I'd mention it after I did a little research on the compression package you added. That said I think it's a good addition.
Also the devtool change in the webpack configure from eval to source map made a HUGE impact on reducing the size of the bundle.  I don't know the difference in the different options for that, but the app works either way so that's a nice change. My app that's based on 3ree was almost 4MB in size and that change brought it down to 1MB.

Thank you for this PR @vwong. The introduction of UglifyJS and use of compression is great for demonstrating to people, with minimal set-up to how the development bundle can shrink ~15x. Thank you for this change!
Whilst I would tend to use nginx to handle compression of responses, as @snobear pointed out, in a production environment I think the simplicity of this for demo purposes is great, and a good addition.
Merging!


Problems with element finding on frames without name or id

Steps to reproduce
Tell us about your environment:

Puppeteer version:v1.8.0
Platform / OS version: Windows 10
URLs (if applicable): not possible, internal.
Node.js version: 8.11.2

What steps will reproduce the problem?
const frame = await page.frames();
const result = await frame.every(f => f.waitForXPath('eegdfgdfggdfg', { timeout: 10000 }));
console.log(result);
When I lunch this code on the page, which contain iFrame without name or ID, as result I receive "true". Same happens when XPath is valid, but doesn't exist on page.
What is the expected result?
false, because XPath is wrong
What happens instead?
I receive true.

The true result is valid because Array.prototype.every method returns true for empty array:
[].every(item => false) === true

But array of frames is not empty, I have at least one iFrame on page and when I output frame array, I see data there.

I think that
frame.every(f => f.waitForXPath('eegdfgdfggdfg', { timeout: 10000 }))

doesn't return promise, so await before is irrelevant. On the other hand
f.waitForXPath('eegdfgdfggdfg', { timeout: 10000 })

returns Promise object, which is treated as truthy value.
Consider simplified statement:
[1, 2, 3].every(f => Promise.resolve(false))

It is also calculated to true.


Add tillerless nginx ingress(es)

Hey guys,
This PR introduces a dual ingress, plus an updated cert-manager deployment, all without utilizing helm. (For a tiller-less deployment).
I've marked it as WIP because there's an issue with the certmanager validation webhook / admission controller, which I'm still trying to pin down.
Why 2 ingresses? The idea being that an operation may want to separate out public ingress from internal ingress. The second ingress (which I've called "nginx-external") is disabled by default, and enabled by toggling a parameter.
I'll remove the WIP tag once I sort out the validating webhook :)
Cheers!
D

No longer a WIP because the front-proxy-ca bug is fixed (https://github.com/digitalrebar/provision-content/pull/296)


Add CSS normalizers

This removes the forced color on the body element too, since it would clash otherwise.
Part of the work on #8.

You would need to adjust the current hack in generate_graph in gamedata.py, which forces embedded graphs to have the same background color. I think that can probably be safely removed for now, but would need adapting so they remain transparent!

Just remove line 132 in gamedata.py: value = value.replace('"axesbg": "#FFFFFF"', f'"axesbg": "{config.website_bg}"'), otherwise that's fine!


Cannot access ports in devel.yaml

It seems that #117 raised yet another issue: cannot access ports in devel.yaml.
I opened https://github.com/moby/moby/issues/36174 to track it, docker-side.
For now, the fastest workaround would be to set internal: false in devel.yaml and then docker-compose down and docker-compose up -d again.
I'll investigate a better workaround when I have time.

I'm thinking that maybe for devel.yaml we should just default to a normal network. Installing packages and so on could be more common than restoring a database in localhost. In such cases, one should be warned about temporarily changing  the internal flag.
Another option would be bundling a small tcp proxy container that is the only one with external access and redirects ports to other containers in the stack.

Questions for this:

Removing internal, are we losing Mailhog?
What about wdb?

Removing internal in devel.yaml (setting it to a normal network), what you loose is the isolation from the www, useful mainly to restore production databases and have no fear on outside world pollution.
By adding the proxy instead of that, we lose no features isolation.
In both cases, mailhog and wdb will be still available.
In any case it's just a workaround for moby/moby#36174 that I hope gets fixed soon.

Let's see if they say something. For now, let's use the workaround.

Upstream is still deciding if this is a bug, a missing feature or a design decision. Should we start working in a downstream fix?

Can we?

tl;dr: yes.
We'd need a proxy container that is connected to both networks. Pretty similar to what is done in test.yaml, where the traefik proxy is connected to both internal and external networks.
Odoo, mailhog, wdb, and all containers in the stack would be in a internal-only network. The proxy would be in that one and in a normal network too, and would be the door to access internal services. This way we have whitelisted isolation.
The same principle would be applied to whitelist some external services in test.yaml, such as google fonts for reports, etc.

OK, let's work in a prototype then.

Fixed in #126


code not running again. deprecation issues

Is there anyway it can be fixed?
Can you pls update the repo?
from optimization.shared import fed_avg_schedule as fed_avg
File "/root/.cache/bazel/_bazel_root/c7ece203b2af4e157a2badc0dd99ed5f/execroot/main/bazel-out/k8-fastbuild/bin/optimization/main/federated_trainer.runfiles/main/optimization/shared/fed_avg_schedule.py", line 37, in
ModelBuilder = Callable[[], tff.learning.Model]
AttributeError: module 'tensorflow_federated.python.learning' has no attribute 'Model'. Did you mean: 'models'?
from utils import training_utils
File "/root/.cache/bazel/_bazel_root/c7ece203b2af4e157a2badc0dd99ed5f/execroot/main/bazel-out/k8-fastbuild/bin/optimization/main/federated_trainer.runfiles/main/utils/training_utils.py", line 83, in
) -> Callable[[tff.learning.ModelWeights], Dict[str, Any]]:
AttributeError: module 'tensorflow_federated.python.learning' has no attribute 'ModelWeights'

fix


For labels

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change

[ ] Added a new machine learning frameworks, libraries or software.
[ ] Documentation update

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

@sanjay-kv
I have not made any changes
As you said for raising direct PRs in this issue https://github.com/GSSoC24/Contributor/discussions/511#discussioncomment-10120256
This is for
https://github.com/hasmithagunda123/ALL_INDIA_HACKATHON/pull/34#issuecomment-2206822626
https://github.com/hasmithagunda123/ALL_INDIA_HACKATHON/pull/46#issuecomment-2206816019


4.x

NetflixOSS » denominator » denominator-pull-requests #82 FAILURE
Looks like there's a problem with this pull request

I'm assuming this was a mistake


Add integration tests

I just realized https://github.com/thiagokokada/nix-alien/pull/88 that nix-ld and Flakes codepaths was broken for a long time (they would not even eval correctly). This was caused by a clear lack of testing in the code.
Also testing even the main code is boring because I need to find a binary that is not static linked (babashka is generally my choice), running the commands and checking the output. There should be a better way to do this.
I think it should be viable to add some integration tests by:

Having some way to skip the interactivity from FZF, by auto-selecting the correct choice

--additional-packages flag is almost what I want, but it is dumb right now and doesn't appear as a candidate for the selecting lib logic. Should be a quick fix
Optionally create a new flag to fill this part

In checks.nix, add new checks. They should download a binary, run nix-alien/nix-alien-ld and call the resulting binary with --help or something to show it is working

Can we call nix builders inside nix though?
Also, we need to make sure that all dependencies are in the /nix/store, otherwise the test may fail because we will not have network access

As an alternative, we can always use GitHub Actions and create some test scripts that are not written in Nix.
Not ideal, but should work quickly.

https://nixos.org/manual/nix/unstable/contributing/experimental-features.html#xp-feature-recursive-nix
Recursive nix seems to be what we want here. Sadly this may mean that this should be put outside of #checks, or anyone that is calling nix flake check in this repo would need to add recursive-nix as an optional feature.


InvalidArgumentError (see above for traceback): No OpKernel was registered to support Op 'MklConv2DWithBias' with these attrs.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): debian 8
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.1.0
Python version: Python 2.7.13
Bazel version (if compiling from source): 0.4.2
GCC/Compiler version (if compiling from source): gcc version 4.9.2 (Debian 4.9.2-10)
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

tf_env_collect.sh:
== cat /etc/issue ===============================================
Linux 4be8a8788f34 4.9.60-linuxkit-aufs #1 SMP Mon Nov 6 16:00:12 UTC 2017 x86_64 GNU/Linux
VERSION_ID="8"
VERSION="8 (jessie)"

== are we in docker =============================================
Yes

== compiler =====================================================
c++ (Debian 4.9.2-10) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

== uname -a =====================================================
Linux 4be8a8788f34 4.9.60-linuxkit-aufs #1 SMP Mon Nov 6 16:00:12 UTC 2017 x86_64 GNU/Linux

== check pips ===================================================
intel-numpy            <IP_ADDRESS>
numpy                  1.14.5
protobuf               3.6.0
tensorflow             1.1.0

== check for virtualenv =========================================
False

== tensorflow import ============================================
tf.VERSION = 1.1.0
tf.GIT_VERSION = v1.1.0-0-g1ec6ed5
tf.COMPILER_VERSION = v1.1.0-0-g1ec6ed5
Sanity check: array([1], dtype=int32)

== env ==========================================================
LD_LIBRARY_PATH /code/:/code//lib:/usr/local/lib
DYLD_LIBRARY_PATH is unset

== nvidia-smi ===================================================
/tensor/tensorflow/tools/tf_env_collect.sh: line 105: nvidia-smi: command not found

== cuda libs  ===================================================

Describe the problem
I posted a stackoverflow issue: https://stackoverflow.com/questions/51530592/invalidargumenterror-see-above-for-traceback-no-opkernel-was-registered-to-su
How to Generate the problem
I found a way to reproduce this problem.

download tensorflow zip and unzip.
https://drive.google.com/file/d/1k616LEvgTUXpHuX6Fz7EDXukaG5tGZwQ/view

mount tensorflow folder to container:
docker run --rm -it -v $(pwd):/code econtal/numpy-mkl  bash

create the test script:

$ cd /code
$ vi test_conv2d.py

# demo from https://www.jianshu.com/p/a70c1d931395
import tensorflow as tf
import tensorflow.contrib.slim as slim
import numpy as np

x1 = tf.ones(shape=[1, 64, 64, 3])
w = tf.fill([5, 5, 3, 64], 1)
# print("rank is", tf.rank(x1))

# x1 = tf.cast(x1, tf.float32)
w = tf.cast(w, tf.float32)

print('-----debugging-----')
print(type(x1))
print(x1.dtype.base_dtype)

print(type(w))
print(w.dtype.base_dtype)
print('-------------------')

# x1 = tf.cast(x1, tf.float16)

y1 = tf.nn.conv2d(x1, w, strides=[1, 1, 1, 1], padding='SAME')
y2 = slim.conv2d(x1, np.float32(64.0), np.array([5.0, 5.0], dtype=np.float32),
weights_initializer=tf.ones_initializer, padding='SAME')

with tf.Session() as sess:
    sess.run(tf.global_variables_initializer())
    y1_value,y2_value,x1_value=sess.run([y1,y2,x1])
    print("shapes are", y1_value.shape, y2_value.shape)
    print(y1_value==y2_value)
    print(y1_value)
    print(y2_value)

run the test script

$ python test_conv2d.py

Can anyone give some advice on how to find the problem? Thanks.

Any chance for you to bump your TF version?
I tried TF v1.8.0 built with "--config=mkl" and I did not encounter this issue.

ping @wei-v-wang

Nagging Assignee @poxvoculi: It has been 17 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Yes, thank you for trying TF v1.8.0.


Fix link to docs/small-factor-devices.md

The README's link to small-factor-devices.md is broken, as that document is in the docs/ directory

@dotnet-policy-service agree


Add KawaseBlurFilter

It's a more faster blur algorithm than Gaussian Blur.
more details at :  https://software.intel.com/en-us/blogs/2014/07/15/an-investigation-of-fast-real-time-gpu-based-image-blur-algorithms
P.S. : @bigtimebuddy  , I don't add any document about it , because it's too hard to me in this filter...
And I think this filter is not for junior user ,  if an user  wants to use it well , he/she needs to understand the algorithm.
After this PR be merged , I will update AdvancedBloomFilter , make it support KawaseBlurFilter

About performance , you could see this :  http://finscn.github.com/pixi-filters/index.html
try <fish> Blur filter (pixi.js) & <fish> KawaseBlur filter , you will see KawaseBlur is faster.
And in some cases , it's more than 4x faster , and in some cases it's less than 2x.
But whatever , it's always faster.


Unable to detect quotes

While using your tagger, I am getting good results.
However, when it comes to quotes, such as inch-symbols and quoted text, the tagger is completely ignoring the quotation marks, making it difficult for me to work with these cases.
Is there a way to make sure that the quotes are tagged as quotes, like in stanfordparser?

To add onto this, is there a way for the perceptron tagger to tag all punctuation? For example, can it tag periods, question marks, quotes, and all text it comes across? Would be a really big help. Currently second best that does punctuation is NTLK tagger but yours is much better.

It should tag all punctuation, but it'll have trouble with unicode entities.
I'm not supporting this code unfortunately anymore --- I'm working full
time on spaCy, which is now under the MIT license too ( http://spacy.io ).
SpaCy handles non-ascii characters appropriately, and is both faster and
more accurate.
NLTK have recently agreed to use this tagger. However, I dont know how well
they support unicode punctuation.
On Thursday, October 15, 2015, LeavesBreathe<EMAIL_ADDRESS>wrote:

To add onto this, is there a way for the perceptron tagger to tag all
punctuation? For example, can it tag periods, question marks, quotes, and
all text it comes across? Would be a really big help. Currently second best
that does punctuation is NTLK tagger but yours is much better.
—
Reply to this email directly or view it on GitHub
https://github.com/sloria/textblob-aptagger/issues/2#issuecomment-148368732
.


Using Roboto .ttf leads to "PDF document is damaged"

Bug Report
Description of the problem
Using the open Roboto .ttf font is not working as expected. It renders the PDF document as damaged. I tried all different ways of registering it. Via Buffer / string (path) / with .registerFont before or directly. It's always the same result.
Code sample
const pdf = new PDFDocument;
pdf.registerFont("Roboto", "assets/Roboto/Roboto-Regular.ttf");
pdf.font("Roboto").fontSize(11).lineGap(3);
pdf.text("HI");
pdf.end();

Your environment

pdfkit version: 0.11.0
Node version: v12.16.1
Browser version (if applicable): not applicable
Operating System: Linux

The fonts are downloadable from https://fonts.google.com/specimen/Roboto


new function shorten

shorten function let you short your URL with tinyurl !

Due to @KarimX32 request, this RP will be closed due to him implementing it in his api


Avoid long delay during SSH login

Hi, may I suggest to add the following line to the dockerfile to disable DNS reverse lookup at SSH login time?
echo "UseDNS no" >> /etch/ssh/sshd_config
Regards,
R

I am not sure about the consequences if I add this line. I will take some time to look it up. Thanks for sharing anyway.

the issue is annoying but probably only in private datacenters with no DNS setup (such as ours). I've solved my problem creating my own dockerfile, of course based on yours - https://github.com/raffaeleguidi/dockerized-oracle-xe
Many thanks for the great job

+1


shiva[core]:x64-windows build failure - python config failure: Python is 32-bit, chosen compiler is 64-bit

Host Environment

OS: [Windows 10 - 1903 - Build 18362.239]
Compiler: VS2017 - Tools: MSVC 14.16.27023 Redist: MSVC 14.16.27012
VS2019 - Tools: MSVC 14.21.27702 Redist: MSVC 14.21.27702

To Reproduce
Steps to reproduce the behavior:
./vcpkg install shiva[core]:x64-windows
Failure logs
VS2017 Community:
SYSTEM@ANDROMEDA 07/24/2019 19:23:32 D:\Git\vs2017
->vcpkg install shiva[core]:x64-windows
The following packages will be built and installed:
shiva[core]:x64-windows
Starting package 1/1: shiva:x64-windows
Building package shiva[core]:x64-windows...
-- Using cached D:/Git/vcpkg.downloads/Milerius-shiva-1.0.tar.gz
-- Using source at D:/Git/vs2017/buildtrees/shiva/src/1.0-2860004d47
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:58 (message):
Command failed: ninja -v
Working Directory: D:/Git/vs2017/buildtrees/shiva/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
D:\Git\vs2017\buildtrees\shiva\config-x64-windows-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:290 (vcpkg_execute_required_process)
ports/shiva/portfile.cmake:13 (vcpkg_configure_cmake)
scripts/ports.cmake:74 (include)
Error: Building package shiva:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: shiva:x64-windows
Vcpkg version: 2019.07.18-nohash-external
Additionally, attach any relevant sections from the log files above.
VS2019 Community:
SYSTEM@ANDROMEDA 07/24/2019 19:24:53 D:\Git\vs2019
->vcpkg install shiva[core]:x64-windows
The following packages will be built and installed:
shiva[core]:x64-windows
Starting package 1/1: shiva:x64-windows
Building package shiva[core]:x64-windows...
-- Using cached D:/Git/vcpkg.downloads/Milerius-shiva-1.0.tar.gz
-- Using source at D:/Git/vs2019/buildtrees/shiva/src/1.0-2860004d47
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:58 (message):
Command failed: ninja -v
Working Directory: D:/Git/vs2019/buildtrees/shiva/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
D:\Git\vs2019\buildtrees\shiva\config-x64-windows-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:290 (vcpkg_execute_required_process)
ports/shiva/portfile.cmake:13 (vcpkg_configure_cmake)
scripts/ports.cmake:74 (include)
Error: Building package shiva:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: shiva:x64-windows
Vcpkg version: 2019.07.18-nohash-external
Additionally, attach any relevant sections from the log files above.
-Please attach any additional failure logs mentioned in the console output.
vs2017_buildtrees_shiva_config-x64-windows-out.log
vs2019_buildtrees_shiva_config-x64-windows-out.log
Additional context

I can rename the ./downloads/tools/python/python2 (version 2.7.16 32-bit downloaded and installed by vcpkg) folder to ./downloads/tools/python/python2-32-bit and download the 64-bit version of python 2.7.16 and put it in a new ./downloads/tools/python/python2  folder and reissue the .\vcpkg.exe install shiva[core]:x64-windows command in both VS2017 and VS2019 and it will install correctly.
Looking at the logs, starting at bottom and counting 14 lines up there is the following error line:
-- Found PythonInterp: D:/Git/vcpkg.downloads/tools/python/python2/python.exe (found version "2.7.16")
CMake Error at D:/Git/vs2019/installed/x64-windows/share/cmake/pybind11/FindPythonLibsNew.cmake:122 (message):
Python config failure: Python is 32-bit, chosen compiler is 64-bit
I'm not sure how making this change will affect/effect other installed packages or packages to be installed in the future?
Should we create both a python2-32 and python2-64 folder and have vcpkg look in the appropriate folder depending of whether you're compiling something 32 or 64 bit in windows?

Thank you for any guidance and assistance.

remove pybind11
install pybind11 // python x64
?

What do you mean by "install pybind11 // python x64"?

When pybindll is installed, it was installed via command line ".\vcpkg.exe install pybind11[core]:x64-windows".
So I tried the following:
SYSTEM@ANDROMEDA 07/24/2019 20:10:14 D:\Git\vs2019
->vcpkg remove pybind11 --recurse
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
The following packages will be removed:

coolprop:x64-windows
pybind11:x64-windows
Additional packages (*) need to be removed to complete this operation.
Removing package coolprop:x64-windows...
Removing package coolprop:x64-windows... done
Purging package coolprop:x64-windows...
Purging package coolprop:x64-windows... done
Removing package pybind11:x64-windows...
Removing package pybind11:x64-windows... done
Purging package pybind11:x64-windows...
Purging package pybind11:x64-windows... done

SYSTEM@ANDROMEDA 07/24/2019 20:10:30 D:\Git\vs2019
->vcpkg install shiva[core]:x64-windows
The following packages will be built and installed:

pybind11[core]:x64-windows
shiva[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: pybind11:x64-windows
Building package pybind11[core]:x64-windows...
-- Using cached D:/Git/vcpkg.downloads/pybind-pybind11-v2.2.4.tar.gz
-- Using source at D:/Git/vs2019/buildtrees/pybind11/src/v2.2.4-c609b9e396
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: D:/Git/vs2019/packages/pybind11_x64-windows/share/pybind11/copyright/LICENSE
-- Performing post-build validation
-- Performing post-build validation done
Building package pybind11[core]:x64-windows... done
Installing package pybind11[core]:x64-windows...
Installing package pybind11[core]:x64-windows... done
Elapsed time for package pybind11:x64-windows: 10.5 s
Starting package 2/2: shiva:x64-windows
Building package shiva[core]:x64-windows...
-- Using cached D:/Git/vcpkg.downloads/Milerius-shiva-1.0.tar.gz
-- Using source at D:/Git/vs2019/buildtrees/shiva/src/1.0-2860004d47
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:58 (message):
Command failed: ninja -v
Working Directory: D:/Git/vs2019/buildtrees/shiva/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
D:\Git\vs2019\buildtrees\shiva\config-x64-windows-out.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:290 (vcpkg_execute_required_process)
ports/shiva/portfile.cmake:13 (vcpkg_configure_cmake)
scripts/ports.cmake:74 (include)
Error: Building package shiva:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: shiva:x64-windows
Vcpkg version: 2019.07.18-nohash-external
Additionally, attach any relevant sections from the log files above.
But shiva still fails as pybind11 is installing the 32-bit version of python2 disregarding the x64-windows triplet.

Did some research - .\scripts\vcpkg_find_acquire_program.cmake has hard coded urls to download the 32-bit versions python-2.7.16.msi and python-3.7.3-embed-win32.zip.

Maybe there is a need to have vcpkg evaluate the bitness and install a version of the 32-bit and 64-bit versions of python accordingly?
This may also need to be done for Strawberry Perl, Aria2, nuget and other 32 versus 64 bit tools/utility packages also?
Also would it be possible to have vcpkg search the %PATH% variable for things like doxygen, 7zip, wix, etc and use the installed versions if they are correct and/or compatible instead of downloading and installing a version in the downloads\tools folder?
Thank you much all for the hard work!!!
Tim

vcpkg install shiva[*]:x64-windows
The following packages will be built and installed:
  * nlohmann-json[core]:x64-windows
    shiva[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: nlohmann-json:x64-windows
Building package nlohmann-json[core]:x64-windows...
-- Using cached E:/tools/vcpkg/downloads/nlohmann-json-v3.6.1/CMakeLists.txt
-- Using cached E:/tools/vcpkg/downloads/nlohmann-json-v3.6.1/LICENSE.MIT
-- Using cached E:/tools/vcpkg/downloads/nlohmann-json-v3.6.1/nlohmann_json.natvis
-- Using cached E:/tools/vcpkg/downloads/nlohmann-json-v3.6.1/cmake/config.cmake.in
-- Using cached E:/tools/vcpkg/downloads/nlohmann-json-v3.6.1/single_include/nlohmann/json.hpp
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing: E:/tools/vcpkg/packages/nlohmann-json_x64-windows/share/nlohmann-json/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package nlohmann-json[core]:x64-windows... done
Installing package nlohmann-json[core]:x64-windows...
Installing package nlohmann-json[core]:x64-windows... done
Elapsed time for package nlohmann-json:x64-windows: 43.09 s
Starting package 2/2: shiva:x64-windows
Building package shiva[core]:x64-windows...
-- Downloading https://github.com/Milerius/shiva/archive/1.0.tar.gz...
-- Extracting source E:/tools/vcpkg/downloads/Milerius-shiva-1.0.tar.gz
-- Using source at E:/tools/vcpkg/buildtrees/shiva/src/1.0-2860004d47
-- Configuring x64-windows
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Performing post-build validation
-- Performing post-build validation done
Building package shiva[core]:x64-windows... done
Installing package shiva[core]:x64-windows...
Installing package shiva[core]:x64-windows... done
The package shiva:x64-windows provides CMake targets:

    find_package(cmake CONFIG REQUIRED)
    target_link_libraries(main PRIVATE ${ModuleAlias} ${RealModuleName})

    find_package(shiva CONFIG REQUIRED)
    # Note: 15 target(s) were omitted.
    target_link_libraries(main PRIVATE shiva::pp shiva::dll shiva::ecs shiva::lua)

python 32 bit

Another thought, is I've compiled vcpkg with the -win64 option when running .\bootstrap.bat to create a 64 bit version of vcpkg.exe, where most would not bother to add this option which would default to a 32 bit version of vcpkg even on a 64 bit machine.
I'm not sure if this plays into the issue I'm having or not.
Thanks for any information you can provide on this subject!
Have a wonderful day.

vcpkg install shiva[*]:x64-windows <<-- [*]

try to install with all dependencies, it seems to me that this function does not always work correctly

Whether one uses an "asterisk", "core", or "nothing" as there are no additional options for package shiva, nonetheless here is the results:

** Visual Studio 2017 Developer Command Prompt v15.9.14
** Copyright (c) 2017 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x64'
SYSTEM@ANDROMEDA 07/25/2019 13:04:07 D:\Git\vs2017
->.\vcpkg.exe install shiva[*]:x64-windows
The following packages will be built and installed:
shiva[core]:x64-windows
Starting package 1/1: shiva:x64-windows
Building package shiva[core]:x64-windows...
-- Using cached D:/Git/vcpkg.downloads/Milerius-shiva-1.0.tar.gz
-- Using source at D:/Git/vs2017/buildtrees/shiva/src/1.0-2860004d47
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:58 (message):
Command failed: ninja -v
Working Directory: D:/Git/vs2017/buildtrees/shiva/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
D:\Git\vs2017\buildtrees\shiva\config-x64-windows-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:290 (vcpkg_execute_required_process)
ports/shiva/portfile.cmake:13 (vcpkg_configure_cmake)
scripts/ports.cmake:74 (include)
Error: Building package shiva:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: shiva:x64-windows
Vcpkg version: 2019.07.18-nohash-external
Additionally, attach any relevant sections from the log files above.
config-x64-windows-out.log
It wants a 64 bit python not the 32 bit installed by vcpkg that is hard coded in  .\scripts\vcpkg_find_acquire_program.cmake

Hi @timautry, thanks for reporting this issue!
We added python 64-bit support just now, please update vcpkg and rebuild shiva.
Thanks.


Checksum is case sensitive and should be in upper case

I ran into this issue myself recently and noticed others having the same problem: https://github.com/dustindclark/homebridge-envisalink/issues/3

@pakerfeldt sorry that took so long for me to get to.  Thanks for the PR!

@entrocode , any chance we can get this published so the I can upgrade and close my bug downstream?  Thanks!

@dustindclark I merged this on December 10th

@entrocode I believe @dustindclark is referring to the npm package that still hasn't been bumped.
https://www.npmjs.com/package/nodealarmproxy

@dustindclark @pakerfeldt I ran publish the other day... lost track it, sorry about that

@martzcodes thank you!


Document removed WrappedValue[T] in 1.0 changelog.

Problem
I upgraded to 1.0 and I got hundreds of " not found: type WrappedValue" compiler errors. I couldn't find anything in the 1.0 changelog that WrappedValue[T] is now unnecessary.
@getquill/maintainers

@olafurpg thanks! :)


Investigating incompatibility with Caprover using Port 80 in container

I am investigating an issue where I am forced to use any other port than 80.
The upstream Nginx container exposes port 80 which works fine until I deploy to Caprover and I get a 502 error due to the app not being reachable.
This is a high-priority item that should be addressed within a day or two because this project is built as an example and base for many projects that are deployed to Caprover.

The problem has been solved. I will fix this tomorrow here.

This has been resolved. The trick was re-deploying Caprover app from scratch after updating the image manually on the server and then leaving "Container Port" blank.


Added agenta's logo in the favicon and set a title

fixed issue,  Add agenta's logo in the favicon and set a title #230. Noticed that logo to be used at any point depends on the the app theme so i added a new hook useLogo to get the logo and this can be used through out the app also.

@witehound thank you for PR 🙌
I checked it out and it looks like it's working only on the main page.
If we go the one of the subpages we get the oldest value.
Also the logo is invisible and not clear.

okay ill do well to take a look

so i updated the favicon with the one you sent thanks, also works on all pages

@all-contributors add @witehound for code and ui

Thanks @aakrem, @mmabrouk


Error in path localization

From @regme on April 18, 2016 6:36

VSCode Version: 1.0.0-insider (0.35.6)
OS Version: Windows 10 Pro (Russian)

Steps to Reproduce:

Create Windows user with russian chars in name
Install .Net Command Lite Tools (1.0.0-beta-001598)
Open some .sln in VS Code
Wait until installation of .Net Debugger finish
Open Error Log

Андрей --> РђРЅРґСЂРµР№
Error: Response file 'C:\Users\РђРЅРґСЂРµР№.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\obj\Debug\netstandardapp1.5\dotnet-compile.rsp' doesn't exist.

log  : Restoring packages for C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\project.json...
info : Committing restore...
log  : Restore completed in 5170ms.

NuGet Config files used:
C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\NuGet.config

Feeds used:
https://www.myget.org/F/dotnet-core/api/v3/index.json
https://api.nuget.org/v3/index.json
https://www.myget.org/F/coreclr-debug/api/v3/index.json
Publishing dummy for .NETStandardApp,Version=v1.5/win7-x64
Project dummy (.NETStandardApp,Version=v1.5) will be compiled because expected outputs are missing.
C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\bin\Debug\netstandardapp1.5\dummy.dll
C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\bin\Debug\netstandardapp1.5\dummy.pdb
C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\bin\Debug\netstandardapp1.5\win7-x64\dummy.dll
C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\bin\Debug\netstandardapp1.5\win7-x64\dummy.pdb

Compiling dummy for .NETStandardApp,Version=v1.5
Running C:\Program Files\dotnet\bin\dotnet.exe compile-csc @C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\obj\Debug\netstandardapp1.5\dotnet-compile.rsp
Process ID: 9248
Error: Response file 'C:\Users\РђРЅРґСЂРµР№.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\obj\Debug\netstandardapp1.5\dotnet-compile.rsp' doesn't exist.

Error: C:\Program Files\dotnet\bin\dotnet.exe compile-csc @C:\Users\Андрей.vscode-insiders\extensions\ms-vscode.csharp-1.0.3-rc2\coreclr-debug\obj\Debug\netstandardapp1.5\dotnet-compile.rsp returned Exit Code 1

Compilation failed.
0 Warning(s)
0 Error(s)

Time elapsed 00:00:00.6875176

Published 0/1 projects successfully
dotnet exited with error code 1

Copied from original issue: Microsoft/vscode#5430

From @dbaeumer on April 18, 2016 9:30
@jrieken do you know where to move this? Looks like OmniSharp.

From @regme on April 18, 2016 10:10
temporary solution for this case
C:\Users>mklink /D РђРЅРґСЂРµР№ c:\Users\Андрей
symbolic link created for РђРЅРґСЂРµР№ <<===>> c:\Users\Андрей

Thanks for reporting this @jrieken. This is a bug in the .NET CLI -- https://github.com/dotnet/cli/issues/2486. We are tracking the issue here with #186 (in case we have any additional problems after the CLI issue is resolved).


Release 3.5.1rc2

Coverage remained the same at 77.757% when pulling b2ae7ac8af05137ebe05795d5a65d33f6c2f43e4 on czpython:release/3.5.1rc2 into 7fbb344766d9377cca196b416405345085d06226 on divio:develop.


Update python.md

Added information about endless commercial support for Python from TuxCare.

@pawlak77 it might be better to raise an issue for discussions before these PRs. Closing for now.


[1.5] Reproducer for #973 Http2Exception: Flow control window exceeded for stream: 0 when sending a ~64 KiB attachment

No need to merge, this PR was just for the sake of studying #973


Suport parameter files

Fixes zalando/lizzy#174.

Coverage increased (+0.4%) to 93.689% when pulling a8229b00a7665c2113087585966b09f96f94eff9 on parameter-files into 2a5ab64e9dde8dd044593b2694c4105b6b555293 on master.

Coverage increased (+0.4%) to 93.689% when pulling 14d8a13e8de6a7a773170d0f7ccc19ac585b9261 on parameter-files into 2a5ab64e9dde8dd044593b2694c4105b6b555293 on master.

👍

:+1:


test: move 07-tendermint client state testing to use light client module entry points

Description

partially closes: #6001
addresses the 07-tendermint client state testing functions, uses expErr instead of expPass.
One test is remaining (for the Initialize function) but review can start on the other files already!

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/).
[ ] Added relevant godoc comments.
[ ] Provide a conventional commit message to follow the repository standards.
[ ] Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
[ ] Re-reviewed Files changed in the GitHub PR explorer.
[ ] Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

Bug Fixes

Improved error handling in ClientState validation and delay period verification.

New Features

Added a new error code for invalid trust levels in light client operations.

Refactor

Enhanced test suite for light clients with new test functions and scenarios, focusing on client status, timestamp retrieval, and membership verification.

Tests

Introduced comprehensive tests for various functionalities including client initialization and membership verification.

Documentation

Updated error messages for better clarity and context.

looking at cov locally, lgtm. I'm guessing plan is for follow up for some others?

hmm good call on the code cov. I took a look and it looks like the methods:   UpdateStateOnMisbehaviour,  UpdateState, CheckForMisbehaviour, VerifyClientMessage are not tested from the light client module, but from the client state. As the LCM module is not really doing any extra logic besides fetching the client state and then using the client state methods, I would err on leaving the tests on the client state in update.go -- but I could add some tests in a followup PR just to see if the CS is fetched? wdyt?


Part 3 of RFC2906 - Add support for inheriting license-path, and depednency.path

Tracking issue: #8415
RFC: rust-lang/rfcs#2906
Part 1
Part 2
This PR focuses on adding support for inheriting license-path, and depednency.path:

To adjust the relative paths from being workspace-relative to package-relative, we use pathdiff which cargo-add is also going to be using for a similar purpose
ws_path was added to InheritableFields so we can resolve relative paths from  workspace-relative to package-relative
Moved resolve for toml dependencies from TomlDependency::<P> to TomlDependency

This was done since resolving a relative path should be a string
You should never inherit from a .cargo/config.toml which is the reason P was added

Remaining implementation work for the RFC

Relative paths for readme
Path dependencies infer version directive
Lock workspace dependencies and warn when unused
Optimizations, as needed
Evaluate any new fields for being inheritable (e.g. rust-version)

r? @ehuss
(rust-highfive has picked a reviewer for you, use r? to override)

r? @epage

Thanks!
@bors r+

:pushpin: Commit 3d07652c3810e38776f9c0e04c8e32f25fc1380e has been approved by epage

:hourglass: Testing commit 3d07652c3810e38776f9c0e04c8e32f25fc1380e with merge b36cc6ed419e809774e6e051dc340473c67a5cbb...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing b36cc6ed419e809774e6e051dc340473c67a5cbb to master...


Create warning directive page

Fixes #4703

@TylerMSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[CultureUnplugged] Add new extractor

For #7954, adding extractor for CultureUnplugged. May add additional metadata in the future, but testing looks good.

Made some changes. I used Charles to rewrite and intercept the JSON response to check for null values and all passed successfully (just entered null as value in the JSON file). How are we looking?


image/gif: "not enough image data" on gif that works in browser

There are images which browsers can render but which image/gif chokes on.
The following runs successfully for most gifs:
import (
    "fmt"
    "image/gif"
    "os"
)

const example = "sample.gif"

func main() {
    fmt.Println("attempting to read gif")

    file, err := os.Open(example)
    if err != nil {
        fmt.Println("Can't open this file:", err)
        return
    }

    img, err := gif.Decode(file)
    if err != nil {
        fmt.Println("Can't decode this as a gif:", err)
        return
    }

    _ = img.Bounds()

    fmt.Println("gif decoded")
}

But when trying to run it on a particular gif (below), this happens:
$ go run main.go
attempting to read gif
Can't decode this as a gif: gif: not enough image data

Here’s the offending gif

While my browser does indeed display it, that image is definitely corrupted and or invalid; imagemagick says:
$ curl -s -o img.gif https://user-images.githubusercontent.com/12746710/81430635-5412ea80-9192-11ea-9a62-80208204bf45.gif
$ identify -verbose img.gif
identify-im6.q16: corrupt image `img.gif' @ error/gif.c/DecodeImage/513.
identify-im6.q16: corrupt image `img.gif' @ error/gif.c/ReadGIFImage/1384.

and my system's image viewer also refuses to open it.
This is similar to #9856, when image/gif was fixed to handle bad gifs a little better.
cc @nigeltao

To read this image, there need to be two changes to the gif decoder. I have made these changes in a modified reader.go (see below), which fix the problem, but the solution needs a more-refined implementation that I don't have time to implement.
(1) Allow the lzw reader to encounter short reads in the stream.
https://github.com/golang/go/blob/4f65fb3b309050f26d41885243df99f917727a53/src/image/gif/reader.go#L427
Example:
https://github.com/as/goissues/blob/173a03c197057be2f0fd7a842ddb4542e7b2e1e3/38958/image_gif_reader.go.txt#L430
(2) Handle zero-bytes sandwiched inside parts of the image.
https://github.com/golang/go/blob/4f65fb3b309050f26d41885243df99f917727a53/src/image/gif/reader.go#L243-L258
Example:
https://github.com/as/goissues/blob/173a03c197057be2f0fd7a842ddb4542e7b2e1e3/38958/image_gif_reader.go.txt#L252-L255
After this, the author's test program correctly decodes the image.
cp /go/src/image/gif/reader.go /go/src/image/gif/reader.go.old
curl https://raw.githubusercontent.com/as/goissues/master/38958/image_gif_reader.go.txt > /go/src/image/gif/reader.go

Handle zero-bytes sandwiched inside parts of the image.

Coincidentally,
https://go-review.googlesource.com/c/go/+/232057
is in review. Does patching in that change fix it?

@nigeltao That patch is necessary to fix it, but alone isn't sufficient. The LZW reader case (1) also needs to be handled.

This is another sample which browsers also can render but which image/gif chokes on, but something is different.
$ go run main.go
attempting to read gif
Can't decode this as a gif: gif: reading image data: lzw: invalid code

The above image is even-more problematic. It contains a byte interpreted as an invalid LZW code (0x66) instead of (0x00) like the first image. To fix that, I had to elide almost all error checks and then ignore the 0x66 byte.
Perhaps other decoders silently ignore garbage input entirely and march forward hoping to eventually draw a valid-looking image. Which encoder produced these?


pulseaduio not starting on raspberry pi 3

hello,
I am following your guide on a raspberry pi 3. NO Mic hat. and getting these errors on step 9 of installing the snapclient:
Jan 21 20:05:41 raspberrypi pulseaudio[390]: Home directory of user 'pulse' is not '/var/run/pulse', ignoring.
Jan 21 20:05:41 raspberrypi pulseaudio[390]: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Jan 21 20:05:41 raspberrypi pulseaudio[390]: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Jan 21 20:05:43 raspberrypi pulseaudio[390]: Failed to find a working profile.
Jan 21 20:05:43 raspberrypi pulseaudio[390]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="platform-3f902000.hdmi" card_name="alsa_card.platform-3f902000.hdmi" namereg_fail=false tsched=yes fixed_latency_range>
Jan 21 20:05:44 raspberrypi pulseaudio[390]: Failed to open cookie file '/var/run/pulse/.config/pulse/cookie': No such file or directory
Jan 21 20:05:44 raspberrypi pulseaudio[390]: Failed to load authentication key '/var/run/pulse/.config/pulse/cookie': No such file or directory
Jan 21 20:05:44 raspberrypi pulseaudio[390]: Failed to open cookie file '/var/run/pulse/.pulse-cookie': No such file or directory
Jan 21 20:05:44 raspberrypi pulseaudio[390]: Failed to load authentication key '/var/run/pulse/.pulse-cookie': No such file or directory
Jan 21 20:05:44 raspberrypi systemd[1]: Started PulseAudio system server.
● snapclient.service - Snapcast client
Loaded: loaded (/etc/systemd/system/snapclient.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2024-01-21 20:05:47 CST; 3min 19s ago
Docs: man:snapclient(1)
Main PID: 576 (code=exited, status=1/FAILURE)
CPU: 43ms
Jan 21 20:05:47 raspberrypi systemd[1]: snapclient.service: Scheduled restart job, restart counter is at 5.
Jan 21 20:05:47 raspberrypi systemd[1]: Stopped Snapcast client.
Jan 21 20:05:47 raspberrypi systemd[1]: snapclient.service: Start request repeated too quickly.
Jan 21 20:05:47 raspberrypi systemd[1]: snapclient.service: Failed with result 'exit-code'.
Jan 21 20:05:47 raspberrypi systemd[1]: Failed to start Snapcast client.
guessing it is most likely my error but wondering if you know how to fix it?
Thank you again for all this amazing work!

never mind I walked through the steps again and it worked the second time.


Support PlusCal procedures

Summary
This started out as a quick fix when I noticed we were failing to parse macros that did not take any arguments. It turned out to include fixes for a number of issues I found along the way:

Macros that take no parameters are now correctly parsed and compiled;
Procedures that take no parameters are now correctly parsed and compiled;
We now actually generate a Go function for each PlusCal procedure (they were previously being ignored);
We now perform macro expansion within procedures (previously, macro expansion happened only within processes);
Small fixes in the type system when calling procedures (they were failing when TLA+ identifiers were used as arguments, and also with numerical literals).

TODO

Make sure macros and procedures in P-syntax work as well.
I suspect the type system currently fails for other types of arguments when calling procedures. I'll take a closer look at that soon.

In the meantime, please take a look at the changes (@mrordinaire let me know if I'm missing something on my type system changes, as I'm not too familiar with the codebase).

Forgot to mention: currently, the Procedures.tla spec I added to test these changes produce the expected output, but panics with a double Unlock error at the end. I did not investigate the issue yet.


fix handle ReplicaWriteException in BDBJEJournal.write

When BDBJEJournal.write meet ReplicaWriteException, we should not retry. Because at the monment the bdbje node state is REPLICA (not MASTER) if we still retry write, at the same time trigger election, the orgin REPLICA node may transfer to MASTER and will cause incorrect journalId

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Add string validation functions

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines, including the relevant style guides.
[x] Read and understand the Code of Conduct.
[x] Read and understood the licensing terms.
[x] Searched for existing issues and pull requests before submitting this pull request.
[x] Filed an issue (or an issue already existed) prior to submitting this pull request.
[x] Rebased onto latest develop.
[x] Submitted against develop branch.

Description

What is the purpose of this pull request?

This pull request:

contains a function to test whether a value is a lowercase string
contains a function to test whether a value is a uppercase string
contains a function to test whether a value is a capitalized string

Related Issues

Does this pull request have any related issues?

No.
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

@stdlib-js/reviewers

Current coverage is 88.5469% (diff: 100%)

Merging #84 into develop will increase coverage by 0.0057%

@@            develop        #84   diff @@
==========================================
  Files          2307       2313     +6
  Lines         30195      30219    +24
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          26735      26758    +23
- Misses         3460       3461     +1
  Partials          0          0

Diff Coverage
File Path

•••••••••• 100%
<EMAIL_ADDRESS>

•••••••••• 100%
new<EMAIL_ADDRESS>

•••••••••• 100%
new<EMAIL_ADDRESS>

•••••••••• 100%
new<EMAIL_ADDRESS>

•••••••••• 100%
new<EMAIL_ADDRESS>

•••••••••• 100%
new<EMAIL_ADDRESS>

•••••••••• 100%
new<EMAIL_ADDRESS>

Powered by Codecov. Last update ef23207...2bd009d


hidden="{{!value}}" not binding properly

The docs specifically call this out as a valid usage :cry:
With required: Boolean defined inside of properties (also tried renaming the property to necessary)

  <template>

        *
        {{name}}:
  ...

  <text-field name="username" required></text-field>
  <text-field name="phone number"></text-field>
  <text-field name="zip" required></text-field>
  ...

* username
* phone number
* zip

workaround

<template>

      *
      {{name}}:
...

...


Feature Request: Add Adapter to iobroker.notifications

Add Adapter to iobroker.notifications, please.
See https://github.com/foxriver76/ioBroker.notification-manager/issues/4#issuecomment-1637652942

Changes have been implemented as far as possible. Unfortunately, in initial tests it was not possible to receive messages from Notification Manager because the instance crashed.
-->  In clarification

New features are working. Specially the Notification-Manager integration is required to work with JS controller >=5.0.8 !

[x] Pipeline green
[ ] Final tests before release
(Pending)
[x] Release version candidate specified
(v.1.3.0)

@Ilovegym66 The integration was implemented and tested. To have a user defined way to send data from the Notification-Manager to the Synology chat, message templates were introduced. Please have a look in the Readme for details and let me know any finding.

Well done!


Get capsize in the Text component.

Wondering if you would consider native support for this in the  component? (works with RN Web too). Am trialing it already with Dripsy to success, but native support would be a win i think.
https://github.com/tienphaw/react-native-capsize

I don't really know enough about this to weight in honestly. Is it a bit too high-level to have built into dripsy? What does your usage look like?

Reading through the docs, my first instinct is that this might be best applied in theme.text, and that it could be documented when we close #5 as its own section. Does that seem like it makes sense?

@samburgers did you ever figure out how to use Capsize with Dripsy? Looking into this myself, but I'm not very familiar with how capsize works.


⚠ Bofrost.be has degraded performance

In c9602fe, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1771 ms

Resolved: Bofrost.be performance has improved in d29670c.


Manual Task fails to execute the 2 actions, Complete Successfully and Unsuccessfully

Describe the bug
Adding a Manual Task in a workflow, when it is executed, it fails when taking any of both actions:
When either option is selected, Complete Successfully or Complete Unsuccessfully, it quickly shows the image below, then reloads the page and brings you back to the workflow.

What project does this issue relate to?
Boomerang Flow
To Reproduce
Described above
Environment
Flow: 3.8.0
Browser: Firefox
Additional Contenxt
No response

@BenjaminRuby Do you or someone else on the team have any cycles to look at this?

@morarucostel I tried to reproduce this using the latest webapp and workflow service tags, and I couldn't get it to occur.
Could you retry?

Resolved as working in 3.10.0


MM - update LDP1 derived tables for Orchid data model changes

https://folio-project.slack.com/archives/C210RP0T1/p1672757167354339
https://issues.folio.org/browse/MODQM-276
We have derived tables for both subjects and series
The current tables should still work, since they unpack the arrays; actually pulling the fields out of the new objects would be an extra step

I think instance_series was resolved by commit b096e38, and instance_subject was resolved by 64032cf, so perhaps this can be closed?

Fine with me! I see these tables only extract the value field and not authorityId, but I'm fine closing this issue.


Add shared Hessian tracer à la Walther

I think this PR should be merged before #131
Source

[x] Add the shared type parameter to HessianTracer, signifying that the Hessian part is shared between all scalar quantities
[x] Modify 1-to-1 and 2-to-1 Hessian overloads to leverage shared Hessians and avoid creating new objects
[x] Add a create_tracers routine which broadcasts create_tracer except when the Hessian needs to be shared

Tests

[x] Add one shared HessianTracer to the test loops
[x] Adjust tests to take dead ends into account when the Hessian tracer is shared

Questions
Should myempty be defined for HessianTracer{G,H,true}?

NO: The only meaningful Hessian tracer will be constructed at the start by create_tracers, and if we make another it means we screwed up somewhere and it may result in incorrect behavior / bad performance.
YES: I think it's correct (but still suboptimal performance-wise) to have empty tracers appear along the function, because the overloads take care to ensure consistency between tracers through this line
https://github.com/adrhill/SparseConnectivityTracer.jl/blob/3a1df201c6864d50b73359473db058df9b8271d2/src/overloads/hessian_tracer.jl#L116

Codecov Report
Attention: Patch coverage is 97.67442% with 1 line in your changes missing coverage. Please review.

Project coverage is 82.72%. Comparing base (34e6bec) to head (c7a3413).

Files
Patch %
Lines

src/overloads/hessian_tracer.jl
93.75%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #135      +/-   ##
==========================================
- Coverage   87.23%   82.72%   -4.52%
==========================================
  Files          31       31
  Lines        1363     1360       -3
==========================================
- Hits         1189     1125      -64
- Misses        174      235      +61

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

Awesome! Did you already compare the performance to existing set types?

Awesome! Did you already compare the performance to existing set types?

No, nor did I include it in the benchmarks.
Depending on what we decide for myempty, the performance might be rather different.

Should myempty be defined for HessianTracer{G,H,true}?

For mutable sets absolutely.

NO: The only meaningful Hessian tracer will be constructed at the start by create_tracers, and if we make another it means we screwed up somewhere and it may result in incorrect behavior / bad performance.

I think carrying around smaller sets instead of needlessly large ones could actually increase the performance of the tracing. Needless to say, the sparse AD pass will also be much faster due to increased sparsity.

For mutable sets absolutely.

We don't have a static handle on which set types are mutable and which are not.

I think carrying around smaller sets instead of needlessly large ones could actually increase the performance of the tracing.

You might be misunderstanding my question. I'm not saying we should get rid of the "non-Walther" mode. I'm saying that in the "Walther" (shared) mode, we still allow the creation of empty Hessians, and I'm not sure it's necessary or even a good idea.

Sorry, my review and my comment on myempty were written before understanding the role create_tracers plays (https://github.com/adrhill/SparseConnectivityTracer.jl/pull/135#discussion_r1650754725). The crux is that only one tracer is ever created, indeed making them analogous to Walther's approach.
This does make the question on empty tracer construction interesting. Maybe the solution is to add methods
myempty(h::HessianTracer{G,H,true}) where {G, H} = t
myempty(::T) where {T<:AbstractTracer} = myempty(T)

if we truly just want to have a single tracer instance.

Don't merge, the benchmarks show an epic slowdown in the shared version compared to the individual one. I'll investigate

Don't merge, the benchmarks show an epic slowdown in the shared version compared to the individual one.

It also looks like there is a minor regression on non-shared Hessians. It could just be noise, but that looks like a pattern: all of them appear on Conv.
I don't consider this blocking, but it's worth investigating.

I took a look at the flame graph for one of the instances where runtime and memory consumption exploded in shared mode. There are no unexpected copies, in fact the total number of allocations has gone down as expected. However, we spend the majority of the time in push! and sizehint! for the Hessian tracer: those operations are more expensive because each 2d set involved is much bigger.
I suggest we keep this PR on the backburner for now, I'll open another one for a sparse matrix representation and we'll see whether that improves things. I'll also try to think about clever representations for a 2d set that only grows and never shrinks.

I'll also try to think about clever representations for a 2d set that only grows and never shrinks.

Depending on the problem, it might actually be reasonable to use "dense" BitVectors and BitMatrices.

I'd like to see this merged soon.
It's a correct implementation of an undocumented feature and adds useful tests. The performance can be improved in a follow-up.

The hessian_tracer_1_to_1_inner call still needs meaningful tests on is_der1_zero && !is_der2_zero and is_der1_zero && is_der2_zero (https://github.com/adrhill/SparseConnectivityTracer.jl/pull/135#discussion_r1658223111).

The hessian_tracer_1_to_1_inner call still needs meaningful tests on is_der1_zero && !is_der2_zero and is_der1_zero && is_der2_zero (https://github.com/adrhill/SparseConnectivityTracer.jl/pull/135#discussion_r1658223111).

I've added the missing test for is_der1_zero && is_der2_zero.
The required local overloads on to hit the is_der1_zero && !is_der2_zero case on 1-to-1 functions don't exist yet. I've added a comment documenting this.


Backstage Refactor

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Is there any issue related to this PR in other repository? (such as dojot/dojot)
dojot/dojot#2331 dojot/dojot#2301 dojot/dojot#2342

Other information:

Still has one unit test broken :. For Deep clone, I would suggest don't retrieve the certificate from device object (and adding it as a comment to be updated when the feature arrives).


400011: Bad request publishing any multi-table .hyper

I always receive 400011: Bad request when using tableauserverclient.Server.datasources.publish() with a multi-table extract.
For the purpose of demonstrating the issue, I've used Tableau Desktop to create multi-table .hyper extracts, and then TSC to try to publish them. Initially I thought the hyper extract api was malforming the multi-table extracts; by using Desktop to create the extract I'm almost certain that TSC or the rest API itself is at fault.
Tableau Server Version: 2018.3.1 (20183.18.1128.2033) 64-bit Linux
tableauserverclient==0.8.1
code
# single-table hyper extract succeeds
single = tsc.DatasourceItem(tableau_project_id, name='single')
single_published = TABLEAU_SERVER.datasources.publish(single, '/tmp/single.hyper', 'Overwrite')
# succeeds

# This is a multi-table hyper extract generated by Tableau Desktop and saved locally.
multi = tsc.DatasourceItem(tableau_project_id, name='multi')
multi_published = TABLEAU_SERVER.datasources.publish(multi, '/tmp/multi.hyper', 'Overwrite')
# fails, traceback below.

traceback
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/endpoint.py", line 116, in wrapper
    return func(self, *args, **kwargs)
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/endpoint.py", line 154, in wrapper
    return func(self, *args, **kwargs)
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/endpoint.py", line 154, in wrapper
    return func(self, *args, **kwargs)
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/datasources_endpoint.py", line 202, in publish
    server_response = self.post_request(url, xml_request, content_type)
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/endpoint.py", line 91, in post_request
    content_type=content_type)
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/endpoint.py", line 54, in _make_request
    self._check_status(server_response)
  File "/home/mstoute/.local/share/virtualenvs/pandleau-fxW5vhPf/lib/python3.7/site-packages/tableauserverclient/server/endpoint/endpoint.py", line 68, in _check_status
    raise ServerResponseError.from_response(server_response.content, self.parent_srv.namespace)
tableauserverclient.server.endpoint.exceptions.ServerResponseError:

	400011: Bad Request
		There was a problem publishing the file 'multi.hyper'.

Does anyone have any ideas? Or perhaps I've missed something obvious. I can't find anything in the server logs to indicate what it doesn't like about my 'multi.hyper'.

I'm opening a support ticket with Tableau as it seems more likely it's the REST API than TSC at this point.

Tableau support tells me that the REST api does not support multi-table extracts. Disappointing but it confirms the issue is not with tableauserverclient.

Did you find a solution? I am experiencing this same issue with a single-table hyper extract... same code, same error... maybe lack of support was extended to all extracts using TSC
Tableau Server Version: 2019.4.4 (20194.20.0221.0754) 64-bit Windows
tableauserverclient=0.10
Regards,
@gitmstoute

@drewsmith9 not at my computer, but from memory you have to name the tables now, even for a single table (in case you hadn't). I never had any problem with single table extracts, though.


.empty() method is not working

I'm trying to empty the contents of a select dropdown menu and it seems like it only works when the first item is selected.
Here's the example
When the second or third value is selected in the dropdown and the button is pressed to empty the contents, it clears out the selection. However if you click on the dropdown again, all of the values are still there.
If the 1st value of the dropdown is selected and the button pressed, then it seems to work fine.

I had this issue, but using the non-minified version in the repo instead solved this...

Released in v1.13.0!

/move to bootstrap-select


fix(ffe-buttons-react): invalid markup

A button tag must have phrasing content children.

Still looks good..

https://files.slack.com/files-pri/TN04X3213-FP3HNS1A7/image.png

Coverage remained the same at 81.459% when pulling a4472328c9cd365a890e74a007d1033bee701cef on develop_ogyldig-markup-loader-button into<PHONE_NUMBER>eb003da78e18efa03544749b4cf3bc on develop.

What exactly was invalid about this markup?

Oh right, child content rules. I wouldn't mind if that was in the changelog (I know I'm sounding like a broken record here but I often check the changelog before updating and it's a lot of extra work hunting down the commits compared to just writing what's fixed in the commit message).

@ivarni, this is the commit message. It will end up in the change log? Is not clear enough?
fix(ffe-buttons-react): invalid markup

button tag must have phrasing content child elements.

@pethel Ah, no that's good, I was fooled by the github UI then :)


etcd config: handle decode err,  defaultkv option to avoid Read() err

ignore decode err in watch
put /${prefix}/default "{}" to avoid Read() err

Yes , I Have tested this also locally and make sure everything works correctly.


DefaultDynamicLinqCustomTypeProvider Issue

Here is what to include in your request to make sure we implement a solution as quickly as possible.
1. Description
We recently upgraded this package from version 1.3.12 to 1.4.3, and suddenly started getting the below exception.
2. Exception
If you are seeing an exception, include the full exception details (message and stack trace).
Exception while parsing expression `true` - Method not found: 'Void
System.Linq.Dynamic.Core.CustomTypeProviders.DefaultDynamicLinqCustomTypeProvider..ctor(Boolean)'.

3. Fiddle or Project
Otherwise, make sure to include as much information as possible to help our team to reproduce the issue.
4. Any further technical details
It appears to be part of this commit possibly -
https://github.com/zzzprojects/System.Linq.Dynamic.Core/commit/852434ce03e318a45b4fb5fd0a656e7d9bab989c#diff-59a013aa11deb1923983dd1185ff649c2c327d2841621d18dff2991ebbef6d6d
It looks like in version 1.4.3, a constructor parameter was added for a parsing config object. Is there a way for you to make this nullable or optional, or to use an empty default assembly helper like before, if no parsing config is passed in?
But we were hoping that since we didn't have issues with the previous version that we wouldn't have to make a change on our side, beings this is not a major version upgrade in the package. Do you happen to have any capacity to address this please?
Thank you.

I can try to make the config a nullable argument.
However I wonder why you get this exception? I would expect that you get a an error at build-time?

Upon looking at things closer on my side, we are using the SLDC package through the RulesEngine package. We are running version 5.0.3 of that. That version states that it requires an SLDC dependency >= 1.3.7. What's strange is it works with version 1.3.12, but it throws that exception above when we upgrade to SLDC version 1.4.3. I would think RulesEngine should still work using SLDC 1.4.3?

I would think RulesEngine should still work using SLDC 1.4.3?

I do not think so, can you create an issue on the RulesEngine repo?

Yes sure thing. Thank you.

There still is the issue that the latest SLDC has a breaking change in the DefaultDynamicLinqCustomTypeProvider class. I think it would be beneficial to allow consumers to keep using the old constructor with the understanding it's deprecated. It just makes for a sub-optimal experience when a breaking change is introduced when it's not expected. Great library and thank you!

https://github.com/zzzprojects/System.Linq.Dynamic.Core/pull/833
I think this PR should fix it. Can you verify the code?

Thanks @StefH that did resolve the issue .


[ADD]: Typing Speed Test Using JAVA

Describe the project you want to add with tech stack
A simple Java app to measure a user's speed of typing
Expected behavior

This application is a cross of a personal testing/training software and a game.

@MohitGupta121 @TusharKesarwani Can you assign me this issue.


Fix Watchlist.md docs

Bad indentation.
Rich diff

@sanko The indentation is still off. You don't want to merge?

No.


FALCON-1897 Extension Job Management: CLI support

Note: There is a bug to run Falcon CLI after the code refactoring. @sowmyaramesh has the patch to fix this and will send a pull request. Tested all the CLI methods with her fix patch.

👍  for the code Ying, please add a few positive/negative tests in FalconCLIIT and I will commit the patch.

@bvellanki Thanks for review. Since there are 10 rest apis and 10 cli commands, the IT tests for all of them will be handled in a separate jira: https://issues.apache.org/jira/browse/FALCON-1905. I'll add both positive and negative tests there. Thanks for your reminder.

That sounds good to me. If there are no other comments from community, I will commit the patch tomorrow.


Exited Code 132

I've searched existing issues and couldn't find a duplicate.

[X] I confirm this is not a duplicate.

Operating System
Docker Cluster on Ubuntu 24.04
Server Software Version/Commit
ghcr.io/snowiiii/pumpkin:master
What happened?
Using Docker, my Docker cluster, I pulled the most recent master image and spun up a container. I then logged in using the publicly assigned IP address. I was kicked one but the log only shows an accepted connection. no other errors. I login again and the server allows me in I disconnect and now the server refuses to connect and crashes with exited Code 132
To Reproduce
If you need me to host the server so you can see this problem, I'd be happy to, as I haven't had this happen on my local network, so I'm not sure what the underlying issue may be as of yet.
Expected behavior
The server should allow players to log in without any connection issues or the server crashes with no errors recorded.

Correction to this connecting to the image from docker either over Local or Public server breaks and exits the server with the same error code.

I just encountered this same issue on my server by using the container image from ghcr.io/snowiiii/pumpkin:master.
Exit code 132 seems to imply the container attempted to execute an illegal instruction, my guess is that the following happened.
Github's Action Runners have CPU's with quite a lot of instruction sets available which not everyone may have, one of the modules/packages in Pumpkin is making use of this unusual instruction.
One temporary solution ofcourse is to clone the repository locally and then deploy it from there however that may be a few steps too many for some that'd rather just pull it straight from the Github registry.

Can you please test again after the latest commit
https://github.com/Snowiiii/Pumpkin/commit/febbfd89e6c647f11612721c3f8a1b4cc7fad9cc

Issues are resolved. Docker seems to not throw exited code 132 anymore after testing. Both locally and on cluster production servers.


Data browser filter for empty

Implements:

https://github.com/code-kern-ai/refinery/issues/222
https://github.com/code-kern-ai/refinery/issues/219
https://github.com/code-kern-ai/refinery/issues/221

PRs:

https://github.com/code-kern-ai/refinery-ui/pull/114
https://github.com/code-kern-ai/refinery-gateway/pull/105

IS NULL only works for completley missing fields

it should also work for empty strings.
This did it for me
if operator == SearchOperators.EQUAL:
    if attribute_item.data_type in [
        DataTypes.INTEGER.value,
        DataTypes.FLOAT.value,
        DataTypes.UNKNOWN.value,
    ]:
        return f"{search_column} IS NULL"
    return f"({search_column} IS NULL OR {search_column} IN ('',' '))"
else:
    return ""

[ ] resolved


Fix #513: Add forceUpdate() to Component d.ts

ComponentLifecycle seemed like the right place to put this.

Coverage remained the same at 97.707% when pulling 3bb762dda43932410fa00dd2108b95b7a08806c6 on mseddon:add-forceupdate into 99ad1f3dd2fb0161f382971e5cfe16d3d298b413 on developit:master.

@mseddon happy to have this added!  I wonder if this spot might be more appropriate though?  forceUpdate() is semantically paired with setState().

@developit okidokie, let's put it there then! :)

Coverage remained the same at 97.707% when pulling ce664eaba838d1db7c9b63dac34c4b48c3ddb481 on mseddon:add-forceupdate into 99ad1f3dd2fb0161f382971e5cfe16d3d298b413 on developit:master.

Coverage remained the same at 97.707% when pulling 8dabb1a798353e4e589a92642bc96ab82f25c847 on mseddon:add-forceupdate into 99ad1f3dd2fb0161f382971e5cfe16d3d298b413 on developit:master.


message-bus stale subscriber issue

When used from message-host, at some point the subscriptions become stale, they stop receiving messages from nats.
There are no relevant errors or logging info available.
The message-bus should log the error events coming from both transport connection and transport subscription. Should also verify other unhandled transport events.
When SubscriptionOptions.STREAM_PROCESSOR is set the underlying subscriptions options should be set:

opts.setMaxInFlight(1)
opts.setManualAckMode(true)

See https://github.com/nats-io/stan.js/blob/master/examples/stan-worker.js
The underlying transport options should be overridden through environment variables

Fixed by #7


Package Request: Ada Language Server & Related Tooling

Project description
The Ada programming language is severely lacking in packaging for Nix. A good early target is to get the Ada Language Server running, since it allows development in Ada on NixOS and provides a baseline set of things to package (Alire also needs to be packaged at some point, but that’s for a future issue).
Metadata

homepage URL: https://github.com/AdaCore/ada_language_server
source URL: https://github.com/AdaCore/ada_language_server
license: GPL 3.0
platforms: unix/linux/darwin

I have been trying to package this but I have ran into issues packaging langkit, which is a python package. I am not familiar with python to get a round the problem I am hitting.


Unable to get access token after upgrade from 3.18.1 to 3.19.0

Hello,
Last week, I saw that a new NuGet package was published. As such, I upgraded from 3.18.1 to 3.19.0 in order to get the refresh token fix from #264. However, after this upgrade, exchanging an authorization token for an access token using the GetToken() method on the RemoteAuthenticationClient class will now return nothing. Downgrading back to 3.18.1 fixes this particular issue.
I have yet to look into this deeply, but as there have been very little changes since 3.18.1, my best guess after a quick glance is that the issue could be hidden in #260. Any thoughts?

Hi! Yes, this can very well be caused by the #260 change.
The OAth endpoints needed to be upgraded, so I did and I tried to follow the documentation and do all the changes. But I don't have a working sample app anymore.
The Q42.HueApi.RemoteApi.Sample included in this repository just gives a blank screen, with both the old and new endpoints. So I have no way of properly testing these changes.
Is it possible that you include the source code in your project, debug it and see what's wrong? Thanks a lot!

Fair enough, and curious to what has changed to break the sample app. As soon as I have a free moment I will take a closer look and debug the changes, and if I manage to get it working I'll do a PR. I may also do another PR later to add PKCE support to compliment the API updates, which is already working in my project with your library via additional info I pass to the method parameters that play nice with the different url builders.

Thanks for looking into it and happy to include your contributions!

I found the reason and created a PR. The Hue docs state that form parameters should be used for the code and grant_type parameters. #267

Thanks for the fix. The code fromy our PR is released with version 3.19.1 https://www.nuget.org/packages/Q42.HueApi/

Added another PR to fix refresh token and JSON deserialization of the token response #268

Thanks! Merged and it's being uploaded to NuGet

Added another PR to fix refresh token and JSON deserialization of the token response #268

Nice work @teilmeier, can't wait to try out the changes. @michielpost Thanks for publishing the changes so fast.
@teilmeier Regarding #268, I haven't tested it to confirm, but based on the change, the expected behavior here is possibly impacted. If we look at the below change:
public async Task <string ?> GetValidToken() {
    if (_lastAuthorizationResponse != null) {
        if (_lastAuthorizationResponse.AccessTokenExpireTime() > DateTimeOffset.UtcNow.AddMinutes(-5)) {
            return _lastAuthorizationResponse.Access_token;
        } else {
            var newToken = await this.RefreshToken(_lastAuthorizationResponse.Refresh_token).ConfigureAwait(false);

            return newToken?.Access_token;
        }
    }
    throw new HueException("Unable to get access token. Access token and Refresh token expired.");
}

We no longer have the check on the refresh token to see if it expires, which is like 112 days if memory serves me, which I fixed in #264 as it was treated as expired when valid. By removing this check, we lose the fail fast logic which drops to the exception thrown below, and instead we will always try to request a new token along with any error that would be thrown there that might not be as clear as the one below. I would recommend adding back the check instead of the else.
Just some food for thought, but I guess this isn't the right thread for this.

@StevenJDH I got your point. Actually I don't use that method because I wrote my own refresh logic for my use case (https://github.com/teilmeier/azure-functions-hue).
The issue is that the current Remote Auth API does not return an expiry date anymore. If Signify confirms that refresh tokens are valid for x seconds we could calculate the expiry date by using the creation time of the token and add a constant value.
The current Hue developer docs do not mention anything about the token lifetimes. So I assumed refresh tokens do not expire. I'd contact Signify and ask for a statement why they removed the refresh token lifetime from the response and what the actual lifetime is.
I hope to get a good guidance.
Philip

@teilmeier Thanks for the info. In taking a similar approach to using my own implementation for the remote authentication API, I can see they did indeed drop the refresh_token_expires_in field. Let's see if the documentation gets updated with something concrete around its expiration.
@michielpost I think we can close this issue as I've tested the changes with 3.19.1, and all the token workflows along with the needed modifications for the latest auth api are working for me.

Great to hear and thanks for the PRs to fix this @teilmeier and @StevenJDH


Can't format remote buffers

If I open a TRAMP buffer to a remote .rs file, rustic-format-file fails with an error like:
Error: file `/ssh:<remote>:<path>/src/main.rs` does not exist

rustic-format-buffer works fine.
Unsure why, but rustic-before-save-hook uses rustic-format-file instead of rustic-format-buffer. This leads to many annoying popups on remote buffers, since I have formatting configured to run on each save.
A quick solution is to replace rustic-format-filewith rustic-format-buffer in rustic-before-save-hook.

Unsure why, but rustic-before-save-hook uses rustic-format-file instead of rustic-format-buffer

The reason is that rustic-format-buffer doesn't always work reliable in terms of buffer position and users prefered rustic-format-file in the past.
I actually never used rust on a remote host. Does this work for you ?
modified   rustic.el
@@ -1192,11 +1192,13 @@ This handles multi-line comments with a * prefix on each line."
 (defun rustic-before-save-hook ()
   "Don't throw error if rustfmt isn't installed, as it makes saving impossible."
   (when (and (rustic-format-on-save-p) (not (rustic-compilation-process-live t)))
-    (condition-case nil
-        (progn
-          (rustic-format-file)
-          (sit-for 0.1))
-      (error nil))))
+    (if (file-remote-p (buffer-file-name))
+        (rustic-format-buffer)
+      (condition-case nil
+          (progn
+            (rustic-format-file)
+            (sit-for 0.1))
+        (error nil)))))
        (error nil)))))

This works. Thanks for the fast fix!

Let's leave this open until we have merged it.

Should be working now.


Cakeshop not working as intended with external quorum nodes

Description of problem
Trying to connect Cakeshop with a Quorum node
Expected behavior
Cakeshop works like the standalone dockerized version.
Actual behavior
Not all of the functionalities are working. A lot of RPC errors.
Steps to reproduce the behavior
in application.properties
change the following
geth.auto.start = false
geth.auto.stop = false
geth.url = 'url of external rpc node'

System information
Cakeshop version or commit hash: v0.9.1
Geth
Version: 1.5.0-unstable
Git Commit: 82a140abbb3ca706b5cdc95d63b345fdc115a3a9
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.6.2
OS: linux
GOPATH=/home/ubuntu/work
GOROOT=/usr/lib/go-1.6

Cakeshop OS & Version: Windows/Linux/OSX
Ubuntu 16.04
Browser OS & Version: Windows/Linux/OSX MSIE/Chrome/Firefox/Safari
Firefox, Chrome both latest version
Backtrace/logs
Gist url
Extra info
The node which cakeshop connects to is started with the following command
geth --datadir quorum-data --permissioned --voteaccount "0x6c5ec8b0ac92bc4900e46428169c26fc2b7c7817" --votepassword "" --ipcdisable --rpc --nodiscover --rpcaddr "<address removed>" --rpcapi eth,web3,personal --blockmakeraccount "0x6c5ec8b0ac92bc4900e46428169c26fc2b7c7817" --blockmakerpassword "" --verbosity 6 console

Hi @nottherealbatman, there are a number of errors in the log, some are admin related since it looks like you didn’t pass the admin API on startup. The default APIs consumed by cakeshop are: admin,db,eth,debug,miner,net,shh,txpool,personal,web3. You can see them in the default applications.properties file. Some other issues being logged have been addressed on the Quorum upgrade fork or you may try the v0.10.0 pre-release.

Hi Ty. I am running into similar issues trying to attach cakeshop to a network of 3 nodes that I have set up using Coenie's Quorum Network Manager. Have followed the step in the wiki and above closely. ran into soem strange Text file busy errors ,but must have been my own fault. However, I have now found the correct RPC url to use for connection, but am still getting a strange error:
GethHttpServiceImpl - RPC call failed - EOFException: \n not found: size=0 content=...
[INFO ] 2017-06-06 10:01:14.346 [main] BlockchainInitializerTask - Contract registry address not found
[INFO ] 2017-06-06 10:01:14.346 [main] BlockchainInitializerTask - ContractRegistry not found on chain
[INFO ] 2017-06-06 10:01:14.350 [main] BlockchainInitializerTask - Deploying ContractRegistry to chain
[ERROR] 2017-06-06 10:01:20.469 [main] GethHttpServiceImpl - RPC call failed - EOFException: \n not found: size=0 content=...
[ERROR] 2017-06-06 10:01:20.470 [main] ContractRegistryServiceImpl - Error deploying ContractRegistry to chain: RPC call failed
com.jpmorgan.cakeshop.error.APIException: RPC call failed

Could you enlighten me as to what I've managed to muck up this time? ;)

Hi @andytudhope - can you confirm:

is this on the pre-release or current cakeshop release?
the RPC APIs that the node was started with? Per my comment above, the Quorum node needs to be started with the following apis:  admin,db,eth,debug,miner,net,shh,txpool,personal,web3

Pre-release
--rpc --rpcaddr <IP_ADDRESS> --rpcapi admin,db,eth,debug,miner,net,shh,txpool,personal,web3,quorum so may need to remove the last there? Might also be that rpcaddr now that I think about it...

It's this script that gets run by the Network Manager to start the BM and BV nodes: https://github.com/ConsenSys/QuorumNetworkManager/blob/master/startQuorumBMAndBVNode.sh

As requested in slack, the application.propoerties file:
cakeshop.database.vendor=hsqldb
cakeshop.hibernate.hbm2ddl.auto=update
cakeshop.hibernate.jdbc.batch_size=20
cakeshop.jdbc.pass=sdk
cakeshop.jdbc.user=sdk
cakeshop.mvc.async.pool.queue.max=2000
cakeshop.mvc.async.pool.threads.core=250
cakeshop.mvc.async.pool.threads.max=1000
contract.poll.delay.millis=5000
contract.registry.addr=
endpoints.actuator.enabled=true
geth.auto.start=false
geth.auto.stop=false
geth.block.maker=0xca843569e3427144cead5e4d5999a3d0ccf92b8e
geth.bootnode.address=
geth.bootnode.key=
geth.bootnodes.list=
geth.cors.enabled=false
geth.cors.url=
geth.cred1=admin
geth.cred2=$2a$10$dbGiTnfK/w8MhcpIj3XgROYXRsFMlEYJRWoUYArkr8aSPypUFV25G
geth.datadir=/home/bc_admin/data/local/ethereum
geth.db.enabled=true
geth.identity=bc_admin
geth.log=/logs
geth.mining=true
geth.networkid=91351
geth.node.port=30303
geth.params.extra=
geth.rpcapi.list=admin,db,eth,debug,miner,net,shh,txpool,personal,web3
geth.url=http\://<IP_ADDRESS>\:20000
geth.verbosity=
geth.vote.account=0x0fbdc686b912d7722dc86510934589e0aaf3b55a
geth.vote.contract.addr=0x0000000000000000000000000000000000000020
management.context-path=/manage
management.security.enabled=false
security.basic.enabled=false
security.ignored=/**
server.compression.enabled=true
server.compression.mime-types=application/json,application/xml,text/html,text/xml,text/plain
spring.main.banner-mode=off
spring.mvc.view.prefix=/WEB-INF/jsp/
spring.mvc.view.suffix=.jsp


Error with

Describe the bug
When i wrap my app in the provider i automatically get an error message
I'm on nextJS 12
export default function MyApp({ Component, pageProps }) {
return (

<Component {...pageProps} />

);
}
Here is the error :
Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object.
at HubspotProvider (file:///Users/pierre/Documents/GitHub/projetc/node_modules/next-hubspot/lib/HubspotProvider.js:17:28)
at AuthProvider (webpack-internal:///./lib/auth.tsx:26:19)
at MyApp (webpack-internal:///./pages/_app.tsx:25:18)
at StyleRegistry (/Users/pierre/Documents/GitHub/projetc/node_modules/styled-jsx/dist/index/index.js:671:34)
at AppContainer (/Users/pierre/Documents/GitHub/projetc/node_modules/next/dist/server/render.js:415:29)
at AppContainerWithIsomorphicFiberStructure (/Users/pierre/Documents/GitHub/projetc/node_modules/next/dist/server/render.js:447:57)
at div
at Body (/Users/pierre/Documents/GitHub/projetc/node_modules/next/dist/server/render.js:715:21)

If you have any idea or recommandation :)

Context Providers should be added to the _app file and not to the _document
Support for Next.js version before 13 is not guaranteed

Context providers are used to manage global state or authentication state that needs to be accessed by various components across different pages. Placing them in the _app.js file ensures that they are initialized once and are available to all pages in your application.
Context providers are not typically added to the _document.js file because the _document is only concerned with the initial server render and the static HTML structure. Context providers, being components that manage state, are more relevant to the client-side rendering and need to be part of the React component tree, which is managed by the _app file for global application state.

Relevant docs:
https://nextjs.org/docs/pages/building-your-application/routing/custom-app

Thanks, the context provider is in _app.tsx, as you can see here : at MyApp (webpack-internal:///./pages/_app.tsx:25:18)
I guess there is something with next 12 compatibility :) I'll try to upgrade


Chart Components - Linegraph, Progress Bar, Pie chart

Description
Create React components for a Linegraph, Progress Bar, and Pie chart as shown in the Figma:

The "Donate now" buttons should redirect to a link passed in by the user.
Ensure that the components behave correctly while resizing.
Please make use of vanilla D3 and avoid making use of 3rd party component libraries.
You should only create the component within the collapsible boxes. i.e. the component you will create should not be collapsible or have any frame around them.

[ ] Line Graph
[ ] Proggress Bar
[ ] Pie Chart

I just added the components to the modal when you click on any provider from the map view. I left my testing components and their info in "map/index", if you wanted to see for yourself, but lmk and I can just remove the test data and the components.


WhichOneOf return value should be Optional

Currently mypy-protobuf marks WhichOneof as returning a Literal containing only the string names of the fields under the oneof. It should also include None, which is returned by WhichOneof when none of the fields inside the oneof are populated

great find! Thanks for the report. This should allow for better typing - avoiding bugs where the dev does not consider the unpopulated case.
There may be new errors reported with the new version of mypy-protobuf with the fix - since previously the return type would match str, but now it won't (will match Optional[str], or will require an assert x is not None).


fix return type and ensure proper handling of Wei in formatWei function

What changed? Why?

Changed: The formatWei function was updated to properly handle bigint values for Wei.
Reason: Previously, the function returned a number or a string ('...') when the wei parameter was undefined, but it didn’t properly handle the conversion from Wei to Ether and then back to Wei. The update ensures that the function returns the correct parsed Ether value after formatting Wei.

Notes to reviewers

This change modifies the return type of the formatWei function. Please pay special attention to the handling of edge cases, especially when the wei parameter is undefined.
Ensure the precision and rounding of the values are handled correctly when converting from Wei to Ether and back to Wei.

How has it been tested?

Manually tested with various values for wei, including both defined and undefined cases.
The function has been validated to ensure that for defined wei values, the output is a properly formatted number, and for undefined, it returns '...'.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@viktorking7
Happy holidays :) Thank you for the bump, the team will review this as soon as they have a chance.
Confirming it is in the backlog. 👍


issue on .topic reaction

Description
When bot adds reaction  to .topic , and then user tries reacting happens on it. If moderator reacts to reaction, then it works.
Steps to Reproduce

Use .topic without any mod role
Click the reaction
Nothing happens

Expected Behaviour

On reaction bot should refresh the topic.
Actual Behaviour

When non moderator reacts to message the bot does not refresh anything.
Known Impacted Platforms

[ ] Web
[x] Desktop
[x] Android App
[ ] iOS App

Would you like to implement a fix?
Note: For high-priority or critical bugs, fixes may be implemented by staff.

[ ] I'd like to implement the bug fix
[x] Anyone can implement the bug fix

@TizzySaurus has said he'd like to work on this

While you're doing this, could you also have the bot remove the user's reactions after it's refreshed the topic?