Configure multiple people

Add an option (view) to configure a multi-person chat:

Number of people (at least two)
Give people a name, avatar (from pre-selection) and color
Rework compositor/ text field and make it easy to decide who from the people posts given message

done in #4


Optimize setup of WebGl state variables

device.js contains multiple functions of this format:

there are multiple conditions followed by settings state if any of these fail.
I would suggest to follow newer graphics APIs and create objects wrapping groups of these various settings. As an example, we can create RasterizerState object (pseudo code with random properties - needs design)
class RasterizerState {
    blendEquation;
    blendAlphaEquation;
    separateAlphaEquation;
    cullMode;
    depthTest;
    depthWrite;
}

when these settings are set up on material, inside material.Update() we will look up dictionary of these RasterizerObjects, and assign a single of them to Material.
While rendering, we'd only need one test to see if RasterizerState changes, instead of many tests.
We could also store transition data for when device is transitioning between these RasterizerState objects, allowing us to pre-evaluate what needs to change on gl device (for example going from RasterizerState A to B, only cullMode needs to change)
so the equivalent function would look like this:
setRasteriserState: function (state) {
    if (this.rastState !== state) {   // compare by pointer
        this.rastState = state;

        // apply changes on GL
       gl.setAlphaState(...);
       gl.setDepthState(...);
    }
}

Ideally, these state objects would correspond to how WebGPU manages these, to allow for easier transition to that API.

I'll close this as both the DepthState and BlendState are done, and we have no need for additional states for now.


Finished all the other errors new error says No module named pkg_resources

root@deabian:~/Desktop/evillimiter# evillimiter
Traceback (most recent call last):
File "/usr/local/bin/evillimiter", line 6, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
root@deabian:~/Desktop/evillimiter#

evillimiter
Traceback (most recent call last):
File "/usr/local/bin/evillimiter", line 6, in
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

I can't really figure out the issue if there is no background information given (OS, Python Version, ...).
Are you sure you have setuptools installed for your python version you are trying to execute the script with?


[BACKLOG-21239] Adding support for case where log object deregistered

...while logging is in-flight.
When viewing a referenced subtrans object, if you close the tab
it causes the object to be deregistered, which was formerly causing
an NPE in Slf4LoggingEventListener when a log event is received
for the no-longer registered object.

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -Dsurefire.runOrder=alphabetical -B -fn -f 'pom.xml' -pl 'core' -P '!assemblies' -amd clean install && mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd site

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/logging/Slf4jLoggingEventListener.java
  core/src/test/java/org/pentaho/di/core/logging/Slf4jLoggingEventListenerTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: <0.1% (click to expand)
org.pentaho.di.core.injection.bean.BeanInjector

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change: -3.3% :small_red_triangle_down:
Line Change: -3.9% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.9% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.googleanalytics.GaInputStepMeta

Branch Change: -1.9% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

@pentaho/ackbar


TracingPolicy examples: use conventional syscall function names in comments

@mtardy  no worries, I thought you might have missed these. I am not very sure, to be honest, the example comments aren't very consistent at the moment, it'd be good if these could be automated somehow. Perhaps an IDE plugin would be better, so you can bring together policy manifests with docs from C headers or man pages.

Closing this since it has not seen updates from quite some time. @errordeveloper feel free to reopen it if you think it still makes sense. Thanks!


Compatibility with pika

This may be a stupid question as I'm new to AMQP, but is there any reason this wouldn't work with pika? Is there likely a better option?
Thank you!

I get some handshake errors when trying to get pika to talk to amqp-mock.
https://github.com/gitpushdashf/amqp-testing
amqp-testing % pipenv run python consume.py
INFO       2021-07-08 09:12:24,861 pika.adapters.utils.connection_workflow start                                179 : Pika version 1.2.0 connecting to ('::1', 5672, 0, 0)
ERROR      2021-07-08 09:12:24,861 pika.adapters.utils.io_services_utils _on_writable                         349 : Socket failed to connect: <socket.socket fd=8, family=AddressFamily.AF
_INET6, type=SocketKind.SOCK_STREAM, proto=6, laddr=('::1', 52603, 0, 0)>; error=61 (Connection refused)
ERROR      2021-07-08 09:12:24,861 pika.adapters.utils.connection_workflow _on_tcp_connection_done              375 : TCP Connection attempt failed: ConnectionRefusedError(61, 'Connectio
n refused'); dest=(<AddressFamily.AF_INET6: 30>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('::1', 5672, 0, 0))
ERROR      2021-07-08 09:12:24,861 pika.adapters.utils.connection_workflow _report_completion_and_cleanup       291 : AMQPConnector - reporting failure: AMQPConnectorSocketConnectError:
ConnectionRefusedError(61, 'Connection refused')
INFO       2021-07-08 09:12:24,862 pika.adapters.utils.connection_workflow start                                179 : Pika version 1.2.0 connecting to ('<IP_ADDRESS>', 5672)
INFO       2021-07-08 09:12:24,862 pika.adapters.utils.io_services_utils _on_writable                         345 : Socket connected: <socket.socket fd=8, family=AddressFamily.AF_INET, t
ype=SocketKind.SOCK_STREAM, proto=6, laddr=('<IP_ADDRESS>', 52604), raddr=('<IP_ADDRESS>', 5672)>
INFO       2021-07-08 09:12:24,864 pika.adapters.utils.connection_workflow _on_transport_establishment_done     428 : Streaming transport linked up: (<pika.adapters.utils.io_services_uti
ls._AsyncPlaintextTransport object at 0x10bfee220>, _StreamingProtocolShim: <SelectConnection PROTOCOL transport=<pika.adapters.utils.io_services_utils._AsyncPlaintextTransport object at
 0x10bfee220> params=<ConnectionParameters host=localhost port=5672 virtual_host=/ ssl=False>>).
ERROR      2021-07-08 09:12:39,866 pika.adapters.utils.connection_workflow _on_overall_timeout                  334 : Timeout while setting up AMQP to 'localhost'/(<AddressFamily.AF_INET
: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('<IP_ADDRESS>', 5672)); ssl=False
INFO       2021-07-08 09:12:39,866 pika.connection                close                                1295: Closing connection (320): "Timeout while setting up AMQP to 'localhost'/(<Add
ressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('<IP_ADDRESS>', 5672)); ssl=False"
INFO       2021-07-08 09:12:39,866 pika.connection                close                                1300: Connection.close() is terminating stream and bypassing graceful AMQP close, s
ince AMQP is still opening.
INFO       2021-07-08 09:12:39,866 pika.adapters.utils.io_services_utils abort                                731 : Aborting transport connection: state=1; <socket.socket fd=8, family=Ad
dressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('<IP_ADDRESS>', 52604), raddr=('<IP_ADDRESS>', 5672)>

Hi!
Thanks for example https://github.com/gitpushdashf/amqp-testing
async def run() -> None:
    async with create_amqp_mock() as mock:
        input()

You used a blocking call input() inside asyncio loop. If you change to a non-blocking wait, your example will work:
import asyncio

from amqp_mock import create_amqp_mock

async def run() -> None:
    async with create_amqp_mock():
        await asyncio.Future()

asyncio.run(run())

I added the missing example to the documentation

However, amqp-mock does not emulate real amqp broker (it does not transfer messages). The purpose of amqp-mock is to test the system in a controlled environment.
Example with pika:
test publish
from pprint import pp

import pika
import requests
from amqp_mock import Message

HTTP_SERVER_URL = "http://localhost:80"
AMQP_SERVER, AMQP_PORT = "localhost", 5672
EXCHANGE_NAME = "exchange"

parameters = pika.ConnectionParameters(AMQP_SERVER, AMQP_PORT, heartbeat=0)
connection = pika.BlockingConnection(parameters)
channel = connection.channel()

# reset mock
requests.delete(HTTP_SERVER_URL)

# publish message
channel.basic_publish(exchange=EXCHANGE_NAME, routing_key="", body=b"<message>")

# get history
response = requests.get(f"{HTTP_SERVER_URL}/exchanges/{EXCHANGE_NAME}/messages")
history = [Message.from_dict(msg) for msg in response.json()]
pp(history)

test consume
import pika
import requests
from amqp_mock import Message

HTTP_SERVER_URL = "http://localhost:80"
AMQP_SERVER, AMQP_PORT = "localhost", 5672
QUEUE_NAME = "queue"

parameters = pika.ConnectionParameters(AMQP_SERVER, AMQP_PORT, heartbeat=0)
connection = pika.BlockingConnection(parameters)
channel = connection.channel()

# reset mock
requests.delete(HTTP_SERVER_URL)

# publish message
message = Message("message")
response = requests.post(f"{HTTP_SERVER_URL}/queues/{QUEUE_NAME}/messages", json=message.to_dict())

# consume
def callback(ch, method, properties, body):
    print("callback", body)

channel.basic_consume(queue=QUEUE_NAME, on_message_callback=callback)
channel.start_consuming()


mask from zbuffer

tri_map_2d, mask_i = ZBuffer_Rendering_CUDA_op_v2_sz224(vertex2d_i, tri_const, visible_tri_i)
the mask_i is 224*224 , shape is (-1,);
masks.append(mask_i)
masks = tf.stack(masks)
return images, masks
where the mask shape is wrong ,that
G_images_300W_mask = tf.multiply(input_masks_300W, tf.expand_dims(G_images_300W_mask, -1))
G_images_300W = tf.multiply(G_images_300W, G_images_300W_mask) + tf.multiply(input_images_300W, 1 - G_images_300W_mask)

Can you elaborate on your question?

the G_images_300W_mask .shape  is wrong, should be 32224224*3 that can multiply with input_masks_300W

The shape is batchsize * 224 * 224 * 1, which is ok for the multiplication.

@tranluan Hello， could you please tell how to render the generated image with only face part? Or how to obtain the index of those vertices of face which doesn't include the neck and ear? The mask from Z-buffer includes neck, which is not expected. Thank you !


Define pinned nix shell environments for the CI to properly handle our collection of tools

In GitLab by @perarnau on Apr 15, 2020, 16:47
The gitlab-ci.yml file contains several nix-run commands that are just ugly, and we are starting to have some issues with the definition/versioning of tooling like clang-format, whose configuration format is heavily dependent on its version.
The proper solution should be to define nix environments or collection of packages that we can use to launch commands easily.

In GitLab by @freuk on Apr 21, 2020, 10:15
my $2:

large collection of nix expressions are hard to maintain. for this reason I suggest that such large collections only consist of buildable packages (so nix expressions can be checked in CI jobs), and that "user shells" or "CI shells" be defined nearer to their use site. Imo that is a sane frontier between "code that should always work" and "code that I can change fast when I need to"
launching ci jobs locally is always possible using gitlab-runner, but that has two drawbacks, namely you can't run them on a dirty repository (you have to create a local commit with changes first), and you need to provision the gitlab-runner binary. For that reason, I'm now using a makefile: https://xgitlab.cels.anl.gov/argo/hnrm/blob/master/Makefile that is called either manually, or via the .gitlab-ci.yml, which calls make <target>. The Makefile defines the environments.

In GitLab by @perarnau on Apr 21, 2020, 10:20
Are you suggesting that we just define proper packages in argopkgs in move the shells elsewhere (this repo). I'm okay with that, but we still need to maintain a pinning strategy between the package builds definitions and what we test in CI.

In GitLab by @freuk on Apr 21, 2020, 10:23
Since those CI shells rely on argopkgs, and argopkgs is pinned, those CI shells are pinned.
BTW my comment is not in contradiction with code factorisation at the package level; useful package targets, like the one you added, I think can reasonably be moved to the package repository: it would be easy to for instance, to define git-clang-tools=pkgs.llvmPackages_7.clang-unwrapped.python.

In GitLab by @freuk on Apr 21, 2020, 10:23
re: your edit: yes.

In GitLab by @perarnau on Apr 21, 2020, 10:26
Sounds reasonable. Keep the real package definitions in argopkgs, and move the shells elsewhere. It will probably be easier to deal with non-nix environments too.

In GitLab by @perarnau on May 6, 2020, 15:36
Fixed by !132.

In GitLab by @perarnau on May 6, 2020, 15:36
closed


August Analytics Report

Type

🚑 Health report

Needs

[x] Analytics and/or component tracking

Report will be published on trustnet in the digitial engagement group.

Report published on trust net on 5th Sept in digital engagement group.


test: use t.Setenv to set env vars in tests

This PR replaces os.Setenv with t.Setenv. Starting from Go 1.17, we can use t.Setenv to set environment variable in test. The environment variable is automatically restored to its original value when the test and all its subtests complete. This ensures that each test does not start with leftover environment variables from previous completed tests.
Reference: https://pkg.go.dev/testing#T.Setenv
func TestFoo(t *testing.T) {
	// before
	os.Setenv(key, "new value")
	defer os.Unsetenv(key)

	// after
	t.Setenv(key, "new value")
}

@Juneezee thank you so much for all your contribution, we really appreciate it! That's a nice improvement, and the code looks cleaner.

@Juneezee: I would love to send you some swag to thank you for your first PR to Kubefirst. If it's something that is interesting to you, can you fill that form please

@Juneezee: I would love to send you some swag to thank you for your first PR to Kubefirst. If it's something that is interesting to you, can you fill that form please

@fharper I have submitted the form. Thank you so much for the gift! :smiling_face_with_three_hearts:


Fix argument to require() must be a string literal

Fixes Webpack warn that require argument should be string

We're not going to insert the first instance of eval into our codebase to fix an external tool's warning.


HelpText.AutoBuild throws unhelpful exceptions if certain assembly attributes are blank

I added the Command Line library to one of my programs today, and I found that when the program called HelpText.AutoBuild(), it threw a TargetInvocationException whose inner exception was an ArgumentException with the message "programName".
After stepping into the method using Reflector, I found that the crux of where the errors occurs is here:
HelpText text = new HelpText {
    Heading = (string) HeadingInfo.Default,
    Copyright = (string) CopyrightInfo.Default,
    AdditionalNewLineAfterOption = true,
    AddDashesToOption = !verbsIndex
};

If the assembly's AssemblyTitle attribute is present but has a blank string value, then HeadingInfo.Default throws an exception at this line in the HeadingInfo contstructor:
if (string.IsNullOrWhiteSpace("programName")) throw new ArgumentException("programName");

If the AssemblyCopyright attribute is present but blank, then the HelpText.Copyright set accessor throws an exception.
It seems that there is fallback logic for the case where these attributes are absent, but not for when they are blank. It would be nice if the fallback logic were used when they are blank, or if the library at least gave a helpful error message when they are.

When you use AutoBuild (if I'm not wrong the behaviour is similar in both stable and pre-rel), you're requesting an automatic help screen generation with a Convention-Over-Configuration pattern.
If you call AutoBuild Both attributes you quoted must be defined and if you define these, you've to declare a content string <> string.Empty.
E.g.: if you use AutoBuild and omit these attributes an exception is raised: this is an intended behaviour.
When not satisfied with this standard behaviour, HelpText could be configured in full freedom.
Thank you for your interest in this project!

I have no complaints about the requirements for using the AutoBuild feature. If those two attributes need to be non-blank, that's fine with me.
The issue I was raising was about how the error is reported because when I encountered this error I had to do quite a lot of digging to figure out what I was doing wrong. The error that's thrown when AssemblyTitle is blank is an ArgumentException for a constructor that I'm not actually calling, and when AssemblyCopyright is blank, the error is an ArgumentNullException for a set accessor that I'm not actually setting.  So my suggestion would be to make the error handling a bit more friendly.

I had this same issue, but the only message I was given was "value". It took me several hours to figure out that you have to fill out all the assembly information or this AutoBuild does not work. It doesn't appear to be documented that these attributes are required. It would be helpful in the examples of using this method that these assembly attributes are required.


Adding stopAdvertise() and stopBrowse()

I added the ability to stop advertising and stop browsing.
Someone probably wants to validate my obj-c as I didn't really know what I was doing. I just copied, pasted, and modified the standard advertise() and browse() methods. FWIW, it has worked well for me.

Closing PR as I will have some more changes coming down the pipeline.


Data Loading error solving in pyspark

Loading into Pandas DF
gam_charge_item_df = pd.read_scv(path)

Creating a PySpark dataFrame
spark_df = spark.createDataFrame(df)

Adding schema to createDataFrame might help
newDF = spark.createDataFrame(parallelizedRows, schema)

What is the issue in code?


load_dict fails when looking up keys with periods in them

Your environment
SDK Version: 1.2.0

installed via pip install onepasswordconnectsdk
Connect Server Version:
OS: Ubuntu 20.04
Python Version: 3.8.10

What happened?
Using load_dict against a key with a period in it generates an error: onepasswordconnectsdk.config.InvalidFieldPathException
What did you expect to happen?
Retrieval of value matching that key
Steps to reproduce
Attempt to retreive a value matching a key with a . in it.
My case has been part of a Section.
`
from onepasswordconnectsdk.client import (
Client,
new_client_from_environment,
new_client
)
from onepasswordconnectsdk import (
load_dict
)
client: Client = new_client_from_environment()
<EMAIL_ADDRESS>creds = load_dict(client, {
"pass": {
"opitem": "My Account",
"opfield": "Main Login." + account
}
})
`
Notes & Logs
Traceback (most recent call last):
File "test.py", line 45, in
creds = load_dict(client, {
File "/home/dev1/.local/lib/python3.8/site-packages/onepasswordconnectsdk/config.py", line 80, in load_dict
_set_values_for_item(client=client,
File "/home/dev1/.local/lib/python3.8/site-packages/onepasswordconnectsdk/config.py", line 185, in _set_values_for_item
raise InvalidFieldPathException(
onepasswordconnectsdk.config.InvalidFieldPathException: Invalid field path format for                 pass
It's understandable that the '.' is normally chaining fields to get one field deeper but keys with email addresses are common and keys with ip addresses are not uncommon in our particular setup.
I would expect either an attempt to look for keys with '.'s in them if it fails or a way to wrap it to escape the '.'s

Hey @Joe-Still,
Currently the way load_dict works for the opfield is based on the following syntax: section.field. Therefore, having one or more dots in your field's name would throw an error in your case.
I do understand your use case and I've raised this with my team. We will update you when we make a new release with this fix.
Thank you for your patience 😄


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1892

Questions ?
Please refer to the Backport tool documentation


upload to LTR builds qgis_ltr label

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixes https://github.com/conda-forge/qgis-feedstock/issues/425.
@ocefpaf is this what you meant?
Do I have to add a conda config --env --add channels qgis_ltr to the post install? Or is that not necessary?

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@ocefpaf is this what you meant?

Yep.

Do I have to add a conda config --env --add channels qgis_ltr to the post install? Or is that not necessary?

That is not needed. The error here is unrelated to the PR. Something broken in the CIs configuration but I believe it was already fixed. Restarting the CIs here to check.

Thanks @ocefpaf. Looks all good now. How will we publicize this change?
Are you happy with this @SrNetoChan @petrushy ?

Many thanks! Looks good!

How will we publicize this change?

I guess that is the hardest part. We do have a blog for announcements but I doubt that will reach qgis conda users.

What's the difference? How do we install qgis ltr now? I can update my blog post about it. I also wanted to add conda installation procedure on qgis website, maybe that's the perfect time for it.

Will it be?
conda install -c conda-forge/label/qgis_ltr qgis ?
How about the update procedure? We will need to add the channel again?
conda update -conda-forge/label/qgis_ltr qgis

Is there a way  make qgis_ltr label the default for and environment?
This means that if I want to install a particular version of QGIS, that happens to have been a LTR, I will need to know it beforehad, otherwise it won't be available using the normal install (main label)?

Will it be?
conda install -c conda-forge/label/qgis_ltr qgis ?

That should work but I prefer,
conda install conda-forge/label/qgis_ltr::qgis

because it mimics how one adds it to an environment.yaml file.
However, I'm not sure that works in all conda's flavors, like micromamba, etc. So maybe it is safer to stick with your CLI there.

How about the update procedure? We will need to add the channel again?
conda update -conda-forge/label/qgis_ltr qgis

That should work.

Is there a way make qgis_ltr label the default for and environment?

Yes, one can add that to a .condarc. Something like:
channels:
  - conda-forge/label/qgis_ltr
  - conda-forge

Should ensure that the LTR is preffered over the version in the main channel.

This means that if I want to install a particular version of QGIS, that happens to have been a LTR, I will need to know it beforehad, otherwise it won't be available using the normal install (main label)?

Yes. You need to search, install, etc from the LTR label. A label is like a channel, just a trick to keep it under the same org name.

@SrNetoChan - merge this if/when you are happy

I have no strong feelings about this. But if others feel it's useful, why not? I wonder if we could/should add this conda-forge/label/qgis_ltr line in our post-install process. That way, from that point on, the update would be in line with the "normal" install.
Sent with Shortwave https://www.shortwave.com?utm_medium=email&utm_content=signature&utm_source=c2VuaG9yLm5ldG9AZ21haWwuY29t
On Thu May 16, 2024, 04:52 AM GMT, Sam Gillingham @.***> wrote:

@SrNetoChan https://github.com/SrNetoChan - merge this if/when you are happy
—
Reply to this email directly, view it on GitHub https://github.com/conda-forge/qgis-feedstock/pull/430#issuecomment-2114024190, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3QU6KT3GEAN632J67INCLZCQ3QXAVCNFSM6AAAAABHTMYKZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJUGAZDIMJZGA.
You are receiving this because you were mentioned.Message ID: @.***>

Although, can the .condarc be edited for a specific environment?

I am merging this. Let's see how it works. Thanks @gillins and @ocefpaf

Ok. This worked pretty well. I did it this way:
mamba create -n qgis_ltr
mamba activate qgis_ltr
conda config --env --add channels conda-forge/label/qgis_ltr
mamba install qgis

the qgis packages was picked from the qgis_ltr label and all the rest from conda-forge.

Works very well, I removed the qgis, added conda config --env --add channels conda-forge/label/qgis_ltr   and got the ltr version as expected.
Now conda update --all works (keeps the LTR version).
Many thanks for this feature!


Taxonomy cleanup

Tested that this doesn't result in any changes to the stacks, this is all just internal changes.  The taxonomy may change again, but this is super helpful already.


Deployment's api version in 'oracle.db.yaml' should be changed to 'apps/v1' for K8S version 1.18.x

Hi,
Creating a Database deployment using the file "weblogic-kubernetes-operator/kubernetes/samples/scripts/create-oracle-db-service/common/oracle.db.yaml" throws below error on K8S version 1.18.x.
ERROR:
error: unable to recognize "/scratch/sbattagi/workdir/weblogic-kubernetes-operator-2.6.0/kubernetes/samples/scripts/create-oracle-db-service/common/oracle.db.yaml": no matches for kind "Deployment" in version "extensions/v1beta1"
As per the K8S 1.18 release notes shown below, we have to use "apps/v1" instead of "extensions/v1beta1".
"daemonsets, deployments, replicasets resources under extensions/v1beta1 - use apps/v1 instead"
https://kubernetes.io/docs/setup/release/notes/#kube-apiserver-1
Please review and fix the issue.
Thanks
Samba

This issue is seen in operator 2.6.0 release branch.

Fixed in 3.0.


Draft player search should search all active players, not just those in value set

This could leave out unvalued players, such as prospects, and is in general simply incomplete. Challenges may be keeping retired players out of the list, but perhaps we simply favor players with values in the returned list?

Favor players in values, followed by players with salary information. Checkbox to search entire db possibly


chore(deps): upgrade angular in examples/supply chain app

Fixes #2002
Signed-off-by: aldousalvarez<EMAIL_ADDRESS>

Hello @petermetz fixed the merge conflict that you said. And now all checks have passed. Thank you

@petermetz Already done. Thank you

Depends on #2096

@aldousalvarez Please put the dependency declaration to the PR description next time. The bot doesn't scan the PR comments for it.

@aldousalvarez Please fix the merge conflicts and then LGTM.

@petermetz Fixed the merge conflicts and now all checks have passed.

@aldousalvarez Please put the dependency declaration to the PR description next time. The bot doesn't scan the PR comments for it.

My apologies on this one. Should I put it on the commit message with the fixes and signed-off-by?

@aldousalvarez It still shows that the conflicts are there =>
This branch has conflicts that must be resolved
 to resolve conflicts before continuing.
Conflicting files
yarn.lock

My apologies on this one. Should I put it on the commit message with the fixes and signed-off-by?

@aldousalvarez Yes, that works best. I usually have the Fixes line and then right below it the depends on line

@aldousalvarez It still shows that the conflicts are there =>
This branch has conflicts that must be resolved
 to resolve conflicts before continuing.
Conflicting files
yarn.lock

my apologies on that one,
as of now all checks have passed and all conflicts have been resolved


Bug: Link not opening

I been using link eye for past two days, The launching is skipped when opening links from a particular application.
The issue can be fixed by opening and closing link eye.
application I am having issue with - NekogramX a telegram client

https://user-images.githubusercontent.com/38587581/163201439-ce844c1f-3758-4111-94ba-40fa483bfd98.mp4

do you have same issue with other apps at open?
brave and/or chrome is working as expected or not?

do you have same issue with other apps at open? brave and/or chrome is working as expected or not?

no so far I didn't noticed same issue in other apps.
none of the intents are working

please test this and inform me.
link_eye.zip

yeah this is working as expected, I will report back any issues after using it for one day.

i will send update to fdroid in few days and it will updated in next week probably.
you can use github version until fdroid update ( available at releases ).

i will send update to fdroid in few days and it will updated in next week probably.
you can use github version until fdroid update ( available at releases ).

got say its working as a charm. thanks for the fix, much appreciated.

Hi !
I've encountered this issue on Twitter. I have l.-e. since 2 weeks, and I can't open any link in there.
Once I've taped to open it or share it, nothing happen. Tho, Links are added to the history. 🤔

Hi ! I've encountered this issue on Twitter. I have l.-e. since 2 weeks, and I can't open any link in there. Once I've taped to open it or share it, nothing happen. Tho, Links are added to the history. thinking

are you using the latest version?

v1.0 from F-Droid, yes

v1.0 from F-Droid, yes

check the github release, v1.1 is released with the fix.


Update e2e:modified script

When running yarn e2e:modified locally, I received an error fatal: ambiguous argument '/develop': unknown revision or path not in the working tree.. As a result, all e2e tests would run rather than the new ones being tested in a given PR.
Changing /develop to develop fixes this, but I have no idea why, or why it was just me in the first place.

Coverage remained the same at 31.49% when pulling cb40227c392841ecd22deff8eaa159e0db8a1b1e on Jskobos:update-e2e-modified into c5c4512d9bf4bd3674363aba9ccbcfa336cce566 on linode:develop.


CSS not loading?

CSS and icons not loading with example?

`
import Nestable from 'react-nestable'
render(){
const items = [
  { id: 0, text: 'Andy' },
  {
    id: 1, text: 'Harry',
    children: [{ id: 2, text: 'David' }],
  },
  { id: 3, text: 'Lisa' },
]

const renderItem = ({ item }) => {
  return item.text
}

return(<Nestable
  items={items}
  renderItem={renderItem}
/>)

}`

Hello, this may be an issue of your settings.
Try to setup a blank project (e.g. with create-react-app) and add all your setting to it one by one.


Undocumented / Orphaned CSS Classes

The following classes are used in the latest bootstrap CSS, but not explained in the documentation: .navbar-nav & .nav-divider
It makes me wonder if there are more undocumented / orphaned classes...

Undocumented, probably. There area number of classes / mixins which aren't meant for external / public API use but are for internal use. Also remember V4 is coming out shortly so I wouldn't expect the V3 public API to be expanded

Shouldn't private classes be on a separate stylesheet from the core bootstrap css? Will these classes be documented in v4?
Likewise, the effects of .navbar-default are not explained. It seems to me that .navbar should have all the default styles? Is navbar-default the opposite of navbar-inverse?

I doubt that every class will be documented and it doesn't make sense to make internal component classes a separate spreadsheet. It just adds complexity for no reason. Default is light color and inverse is dark coloring.

Navbar holds the common styles for all navbars of any colors.

Is navbar-default the opposite of navbar-inverse?

Yes.

The following classes are used in the latest bootstrap CSS, but not explained in the documentation: [...] .nav-divider

.nav-divider is extremely deprecated, hence why it's not documented:
https://github.com/twbs/bootstrap/blob/3487898a6af8c1d5b12f7b040d30e71b19e34923/less/navs.less#L56

Thanks to both of you. Navbar-Nav is even used in the BS Example code. What does that do?

As shown in the examples, it's used for the list of links in the navbar.

Punting on any changes here—I think the existing docs are getting the job done.


Update translation

Not sure about line 202 and line 204 so I mark "# {change}".

Wow! Awesome, @lazydogP :+1:


BF: MXKEventFormatter: MD swallows leading #'s even if there are less than 3

https://github.com/vector-im/vector-ios/issues/423

lgtm


Implemented list.insert()

The match is quite messy with some BigInt to/from usize conversion. Any suggestion on how to make it more readable is very welcome.

(Forget about the previous comment)
@windelbouwman
I did some experiment and cpython seems to only handle index within SSIZE_T, which equals to i64 on my platform. So I simplify the logic to use i64 only.

I did some experiment and cpython seems to only handle index within SSIZE_T, which equals to i64 on my platform. So I simplify the logic to use i64 only.

If cpython uses ssize_t, then shouldn't you use an isize, that being rust's equivalent?

I updated the patch using isize and use the correct OverflowError from #347 . If anyone can kindly review I'd appreciate it.

I wondered if it made more sense to use usize instead of isize, especially since RustPython must eventually always cast it to usize for indexing anyway.
CPython, in PEP-353 justifies its usage of ssize_t with two reasons:

Python allows negative indexes in many contexts anyway (so, I believe, using isize here might make arithmetic with them easier),
the CPython codebase has many places where it depends on indexing variable being signed (for loops checking the variable being non-negative, possibly also some error handling by returning -1) – this does not concern RustPython.

The documentation requires sys.maxsize constant with the maximal value of the Py_ssize_t type, but it does not require it to be any particular value on any architecture.
Anyway, doing the same thing as CPython (so using isize for Py_ssize_t) probably is the right choice for eventual compatibility with C-based FFI…

But current sys.maxsize in RustPython requires usize:
ctx.set_attr(&sys_mod, "maxsize", ctx.new_int(std::usize::MAX));


If code is selected and file is saved, it replaces entire document with selection

Hi there, I've started to have an issue where if I happen to have something selected and I save the file, it will replace the entire file with just the code that is selected. Had a coworker try it on their machine and they had the same problem. Removed the extension and the problem went away, added it back and the problem returned. Any ideas for how to solve?

Formatting code selection is not working properly. I'd try to look at it till the end of the week.

Thanks for fixing that so fast! It's adding a paragraph now whenever code is selected, but that is a whole lot better than replacing the entire document and I can live with it

I found out that I fixed it wrong :) I will fix properly in some short time.

@benzdouglas I think now everything should be fine. v0.1.1 was already published in VSCode marketplace, so you should be able to check if it's working. Happy coding ;)

Works! Thanks again!


Site refers to setup.sh instead of setup.sql

On the walkthrough under Step 1 it talks about setup.sh when it should be setup.sql. Might be confusing to some who are blind typers and don't pay attention (like me!).

Well spotted @astoellis! Thanks for the heads up, I've fixed the mistake :smile:


Clean up hostname + port assignment for alert server

Merge w/ https://github.com/pipelinedb/pipelinedb/issues/1437

Log error if alert server post already in use rather than assertion failure #1437


Low Priviledge users (Handle denied access to WMI query)

Tested the sample project running under the Guest account and got the same exception as #24, so it looks like this could be the problem.
The library should now report on exceptions running as low privilege user (tested with Guest Account).

Perfect!


Update disease synonyms FE due to endpoint changing in API

Context
Due to the increased granularity of information on the disease synonyms endpoints the FE logic needs to be updated, otherwise the application will crash.
The API currently returns an array of strings when querying the synonyms endpoint:
query diseasePheno{
  disease(efoId: "MONDO_0021251") {
    id
    name
    isTherapeuticArea
    synonyms
  }
}

{
  "data": {
    "disease": {
      "id": "MONDO_0021251",
      "name": "endometrium neoplasm",
      "isTherapeuticArea": false,
      "synonyms": [
        "endometrial tumor",
        "neoplasm of the endometrium",
        "tumor of the endometrium",
        "neoplasm of endometrium",
        "endometrium tumor",
        "endometrial neoplasm",
        "endometrium neoplasm (disease)",
        "tumor of endometrium"
      ]
    }
  }
}

When updated, the API will display more granular information including relation and terms:
query diseasePheno{
  disease(efoId: "MONDO_0021251") {
    id
    name
    isTherapeuticArea
    synonyms {
      relation
      terms
    }
  }
}

{
  "data": {
    "disease": {
      "id": "MONDO_0021251",
      "name": "endometrium neoplasm",
      "isTherapeuticArea": false,
      "synonyms": [
        {
          "relation": "hasExactSynonym",
          "terms": [
            "endometrial tumor",
            "tumor of endometrium",
            "neoplasm of endometrium",
            "endometrium tumor",
            "endometrium neoplasm (disease)",
            "tumor of the endometrium",
            "endometrial neoplasm",
            "neoplasm of the endometrium"
          ]
        },
        {
          "relation": "hasRelatedSynonym",
          "terms": [
            "endometrial neoplasm"
          ]
        }
      ]
    }
  }
}

Currently working API query
There are 4 types of relationships that can be returned by the API attending to different levels of specificity of the synonyms
Action
We want to update the disease synonyms logic in the FE using the same UI and provide the relation(s) when on-hovering the chips.
In order to achieve this there is one consideration to make. In cases like the example above in which endometrial neoplasm can be in more than one category, we want the term to appear once in the UI but listing both categories (hasExactSynonym, hasRelatedSynonym) when on-hovering the chip.
Please @andrewhercules and @LucaFumis feel free to raise any question or suggestion

Ticket closed as work completed and merged into beta


provisioner: add support for Azure multi AZ, having dedicated subnet per zone

Description
Changes proposed in this pull request:

.spec.networking.nodes is configured provider specific way, as per suggestion from Gardener documentation. For Azure, it's the same as the VNET CIDR. For AWS, it's the VPC CIDR. For GCP, it's the Worker CIDR from GardenerConfig, which is used to configure the regional VPC subnet.
GardenerConfigInput is extended to support specifying multiple Azure zones, using the dedicated subnet per zone config which also enables zone redundant NAT Gateway. API change is backwards compatible with the current model, so both the old config input (single AZ zoned cluster) and the new config input (multi-AZ zoned cluster) is supported.
Gardener config model code was adjusted to support both current and new (multi-AZ with subnets per zone) Azure configuration scheme

Related issue(s)

When testing the PR I have noticed that cidr string for each azure zone can be edited in the provisioner database during Shoot Upgrade operation. In the same time Gardener rejects this change and reports this field as immutable.
I think we should not allow for that this - just prevent this immutable field in the database form update.

/retest-required


Unused files in repo

The only files used in Bails/bin/ are:
bails-menu which is out-dated and needs an update
bails-wallet which creates the wallet and an update will help make it useful to run stand-alone
bitcoin-qt-wrapper which ensures bitcoin starts with correct parameters and occasionally shows a donation invitation
chainstate-preload which helps Bitcoin sync faster after a restart
install-core which installs bitcoin core persistently
persistent-setup which guides the user thru setting up their Tails Persistent Storage
The others are not used or have been deprecated by Tails adding the functionality they used to provide and can be deleted once it is clear which features will be in the Beta 1.0 release. (L1 from design scope)

Let's close this after #81 , #7 , #170 and #58 . I forget which of those files are helpful to closing those issues and which aren't.


Added populate to Google sheets feature

Here's the first attempt through a pull request to add the populate to Google sheets feature.

before merging into the main code, maybe clone my repo first and see if you can get it working with a new Google Sheet and associated credentials - I added basic instructions to the README.   Reach out if you have any questions.

before merging into the main code, maybe clone my repo first and see if you can get it working with a new Google Sheet and associated credentials - I added basic instructions to the README. Reach out if you have any questions.

Will do, it might take me a few days, but I will get it.  I will need to get familiar with sheets too.  Appreciate your work.


TEST add smoke test to CI

Codecov Report

Merging #15 (b8e23aa) into main (e81a850) will increase coverage by 5.11%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #15      +/-   ##
==========================================
+ Coverage   50.23%   55.34%   +5.11%
==========================================
  Files           5        5
  Lines         215      215
==========================================
+ Hits          108      119      +11
+ Misses        107       96      -11

Impacted Files
Coverage Δ

giga_auto_qc/run.py
93.75% <100.00%> (+68.75%)
:arrow_up:


Bump Ballerina version

Purpose

$subject

Codecov Report

Merging #20426 into release-stage will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release-stage   #20426   +/-   ##
==============================================
  Coverage          15.21%   15.21%
==============================================
  Files                 50       50
  Lines               1341     1341
  Branches             208      208
==============================================
  Hits                 204      204
  Misses              1121     1121
  Partials              16       16

Continue to review full report at Codecov.

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


it would be nice if the device lab tasks could be run directly

To run a devicelab task locally for testing, I do:
dart bin/run.dart -t commands_test

When I try and run a task directly (dart bin/tasks/commands_test.dart ), I see:
SEVERE: 2017-07-27 08:39:49.239191: Task did not start in 0:00:10.000000.

I'm not sure why it doesn't work when run directly, but this would be a nice feature to have when iterating locally on a task.
@yjbanov

dart bin/run.dart -t bin/tasks/commands_test.dart

Just to be clear, this issue wasn't about using run.dart -t, but executing the the test script directly (dart bin/tasks/commands_test.dart).

Ah, I misunderstood. Unfortunately, there are no plans to support it due to the way devicelab infra works.


question for Testing by using user's data

Thank for your master work, but one question: In the test process, good result for the data you offer, but when I test my private data, the result is poor, can you kindly give me some advice?
PS: I had assign the eyes' location of my private data when testing

how do i test with my private data?


Improve Improvers

Improvers are constraining.
For eg: Improving reference id to reference URL, improving vuln data (not an advisory).
The problem is with both interesting_advisories and get_inferences where both of them expect AdvisoryData.
Improvers cloud be split in

A condition which checks if this improver runs or not
then a handling thing.

TOCTOU conditions are also present, we check at interesting_advisories and use the value at get_inferences. Could do https://docs.djangoproject.com/en/4.0/ref/models/querysets/#select-for-update to avoid TOCTOU closer where things are going to change. This would mean returning a QuerySet from interesting_advisories might not be an ideal case.
Current implementation could become a subclass which is a advisory based improver.
(via: https://github.com/nexB/vulnerablecode/wiki/WeeklyMeetings#meeting-on-tuesday-2022-04-19-at-1000-utc)

Current problem

Inference class is not very scalable for different types of improvements

Eg: Improver to figure out CVE from a given set of references by their urls.

There exists a TOCTOU condition over the entire QuerySet passed

Proposed solution

Eliminate intermediate Inference class and allow improvers to implement their own process method which talks to the database directly.
Improvers should be idempotent
After getting a QuerySet, iterate over each element -> select_for_update one element -> update -> repeat
Following is the proposed python pseudocode

class Improver:

    @classproperty
    def qualified_name(cls):
        """
        Fully qualified name prefixed with the module name of the improver used in logging.
        """
        return f"{cls.__module__}.{cls.__qualname__}"

    @property
    def interesting_queryset(self) -> QuerySet:
        """
        Return QuerySet for the advisories this improver is interested in
        """
        raise NotImplementedError

    def improve(self, args) -> isImproved?:
        """
        Generate and return Inferences for the given advisory data
        """
        raise NotImplementedError

    def process(self, args) -> isProcessed?:
        """
        Entrypoint for the improver. Consume ``interesting_queryset`` and use ``improve`` to
        process improvement.
        """
        raise NotImplementedError

class AdvisoryImprover(Improver):

    def process(record):
        """
        An atomic transaction that updates both the Advisory (e.g. date_improved)
        and processes the given inferences to create or update corresponding
        database fields.

        This avoids failing the entire improver when only a single inference is
        erroneous. Also, the atomic transaction for every advisory and its
        inferences makes sure that date_improved of advisory is consistent.
        """
        # This is somewhat the same method that exists currently in the framework for processing all improvers
        # Although, it takes care of TOCTOU as stated above
        ...

Now different improvers can be written by implementing the AdvisoryImprover method by providing bodies for improve and interesting_queryset
This way we have a concrete design for improvers, independent ways of handling different kinds of improvements (via the process method)
(via: )

Related: https://github.com/nexB/vulnerablecode/issues/1068


KAFKA-9971: Error Reporting in Sink Connectors

Implementation for KIP-610: https://cwiki.apache.org/confluence/display/KAFKA/KIP-610%3A+Error+Reporting+in+Sink+Connectors
This PR adds the ErrantRecordReporter interface as well as its implementation - WorkerErrantRecordReporter. The WorkerErrantRecordReporter is created in Worker and brought up through WorkerSinkTask to WorkerSinkTaskContext. An integration test and unit test has been added.

ok to test

retest this please

ok to test

retest this please

ok to test

retest this please

retest this please

Retest this please.

ok to test

Closing to try to fix builds; will reopen shortly.

ok to test

retest this please

retest this please.

retest this please

Not sure what's happening, but here are some finally-running builds from previous commit (0e40):

https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/2548/
https://builds.apache.org/job/kafka-pr-jdk11-scala2.13/6569/
https://builds.apache.org/job/kafka-pr-jdk14-scala2.13/708/

Three green builds of commit 126b04:

https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/2552/
https://builds.apache.org/job/kafka-pr-jdk14-scala2.13/710/
https://builds.apache.org/job/kafka-pr-jdk11-scala2.13/6571/

@aakashnshah, let's get fixes for @kkonstantine's suggestions. Thanks!

ok to test

retest this please

retest this please

2/3 builds are green. Merging now to allow for other PRs to resolve conflicts sooner rather than later, if needed.


Reduce pin-depends

This PR removes two unneeded pin-depends entries.
Both sexplib0 and ppxlib are now available in the alpha repository.

Rebased this PR as things are starting to turn more green lately...


Debugger raising TypeError

Debugger does not start and logs:
Traceback (most recent call last):
  File "/home/lucas/.config/sublime-text/Packages/Debugger/modules/debugger.py", line 69, in get
    instance = Debugger(window, skip_project_check=skip_project_check)
  File "/home/lucas/.config/sublime-text/Packages/Debugger/modules/debugger.py", line 90, in __init__
    self.on_session_output = core.Event[dap.Session, dap.OutputEvent]()
  File "./python3.8/typing.py", line 261, in inner
  File "./python3.8/typing.py", line 897, in __class_getitem__
  File "/home/lucas/.config/sublime-text/Lib/python38/typing_extensions.py", line 2691, in _check_generic
    raise TypeError(f"Too {'many' if alen > elen else 'few'} {things}"
TypeError: Too many parameters for <class 'Debugger.modules.core.event.Event'>; actual 2, expected 1

Where are you getting typing_extensions library from because that seems like a bug in the implementation to me

I didn't do anything special so it must be shipped with ST oder package control.

LSP added typing_extensions this Friday as a dependency -> https://github.com/sublimelsp/LSP/releases/tag/4070-2.0.1
So I would assume that this is the origin how LDAP got typing_extensions

https://github.com/python/typing_extensions/issues/126 is the feature that is missing.
Anyone doing something similar by trying to import typing_extensions when its available (such as doing type checking) and uses a feature this library doesn't support is going to break (probably only this package tbh).

Is there a quick workaround since I need currently both LSP and Debugger?

@daveleroy
If you want I could revert the last LSP release for the time being(until a fix for this is found)?

This should be fixed in 0.11.3


Altered the unpack function to deal with datasets that have different…

… number of covariates. Function will now unpack and stack all covariates no matter how many different number of covariates there are. The column names of the returned dataframe are x1_label, x1_value, x2_label, x2_value, etc. If covariates from one dataset do not have x number of key:value pairs then there is an NA for the label and value.

I ended up using stringr with this function, not sure if that's loaded in the namespace for popler.

Nope not installed, but i like it.
That's just a tiny change - we are using the tidyverse anyway!
On Feb 3, 2017 12:39 PM, "Andrew Bibian"<EMAIL_ADDRESS>wrote:

I ended up using stringr with this function, not sure if that's loaded in
the namespace for popler.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AldoCompagnoni/popler/pull/5#issuecomment-277326723,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE7BQEAaDkTD48oBjhEcwRC7FYsRhuRmks5rY3RIgaJpZM4L2orx
.

nice!
On Fri, Feb 3, 2017 at 12:53 PM, Aldo Compagnoni<EMAIL_ADDRESS>wrote:

Merged #5 https://github.com/AldoCompagnoni/popler/pull/5.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AldoCompagnoni/popler/pull/5#event-948527524, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMATlp3RDnlhtpxhECv-x4uD-EFyB99Bks5rY3eXgaJpZM4L2orx
.

--
Andrew Bibian
Data Analyst
Rice University
<EMAIL_ADDRESS>805.204.8149 (cell)


gollvm: BackendArrayStruct.cpp:783:42: error: no matching function for call to ‘Llvm_backend::global_variable(const char [3], const char [3], Btype*&, bool, bool, bool, Location&)’

Hi.
GCC's version is

(Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
.

Was able to track down (at least) two errors:

/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/bridge/go-llvm.h:258:14: note:   candidate expects 5 arguments, 7 provided
/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/unittests/BackendCore/BackendArrayStruct.cpp: In member function ‘virtual void {anonymous}::BackendArrayStructTests_TestStructFieldAddressExpr_Test::TestBody()’:
/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/unittests/BackendCore/BackendArrayStruct.cpp:783:42: error: no matching function for call to ‘Llvm_backend::global_variable(const char [3], const char [3], Btype*&, bool, bool, bool, Location&)’
783 |                                       loc);
|                                          ^

/home/runner/work/gollvm_build_process/gollvm_build_process/gollvm_build_process/llvm-project/llvm/tools/gollvm/unittests/BackendCore/BackendArrayStruct.cpp:783:42: error: no matching function for call to ‘Llvm_backend::global_variable(const char [3], const char [3], Btype*&, bool, bool, bool, Location&)’

Archived logs:
https://github.com/advancedwebdeveloper/gollvm_build_process/suites/3361391333/logs
Raw logs:
https://github.com/advancedwebdeveloper/gollvm_build_process/commit/f5c21ee02bcc876c4993c37d607bfbe44e797881/checks/3192098762/logs
@thanm

Thanks. Sent https://go-review.googlesource.com/c/gollvm/+/338571 with a fix.

Resolved.
Thanks


v1.1: Adding ignore_error flag

Adding ignore_error flag (#159)
Sourced from v1.1 release page.

Self-assigning this issue.


Check xr policy

Fixes #6692
Checks if the WebXR API is allowed to be used before using it (navigator.xr.isSessionSupported).
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

I believe this will break access to WebXR features for users that have not yet granted permission for it per origin. As allowsFeature returns false if it was either denied or were not requested by origin (by default it will false).
While "support" detects if WebXR is supported on the platform, not necessary allowed.
So this PR will break WebXR for pretty much all new users.


API State Change Flow Problem when reject the workflow request

Description:

If configured a workflow for API state change[1] and It is working fine when approved the request for API State change action(Published or Blocked) by the admin user other states changing or action will working fine such as "deploy as a prototype", "Demote to Created" and "Deprecated".
However if we "Rejected" any workflow requests regarding state changing(Published or Blocked) before doing any other actions like deprecated, demote or deploy as a prototype, those actions update will fail and show the below UI error. But we cannot see any other error from the backend side of APIM or BPS.

Suggested Labels:

BUG
Suggested Assignees:

Affected Product Version:
APIM 2.2.0
OS, DB, other environment details and versions:
Steps to reproduce:

Configure the workflow for API state changing[1]
Created an APi and tried to publish the API, then it will send workflow request to admin
Visit to Admin portal and reject it
Back to Publisher UI and instead of trying to publish, change the action as "Deploy as a Prototype"
Then you can see the above UI error and check both backends from APIM and BPS, there are no errors appearing.

[1]. https://docs.wso2.com/display/AM220/Adding+an+API+State+Change+Workflow

Fixed


ROX-16426 / ROX-14418: Get ENP up and running

FIXME: After review, before merging, remove the dry-run flag from the production run-and-upload step here.
This PR updates and extends the workflow.
It introduces two separate steps as follow ups to the build step:

run-dry-run: Runs the binary in dry-run mode. This will automatically run on PRs and can be manually triggered on the "Actions" tab
run-and-upload: Runs the binary in production mode where it writes to the GCP bucket defitions.stackrox.io. This will be run daily on 10.30 AM UTC and can also be triggered manually on the "Actions" tab (by unchecking the dry run option)

There are mail notifications that are being sent out if a job fails, but maybe you have a different mechanism in mind?
My gut feeling tells me something like a Slack bot posting to acs-nightly-ci-runs or acs-test-failures might also not be a bad idea. WDYT?

From https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs:

Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.

Mail notifications to a user (who might or might not read their emails, leave the organization, ...) sounds like a single point of failure to me. I'll leave the decision to you and give you a LGTM already.

@tommartensen I have added Slack notifications for a team Maple channel. Please feel free to take another look here.
@vikin91 I've renamed the workflow and added a download of the current networks and checksum before overwriting them. They will show up in the artifacts tab of a run and will be cached for 60 days. Example here (see "Artifacts" at the bottom).

@Maddosaurus - Slack notification LGTM


Fix improvement_found condition in Grover Optimizer

Summary
A minor fix on improvement_found condition of GroverOptimizer module.
Details and comments
v = int_v is the current Hamiltonian value Q(x). A new threshold value is found when Q(x)-y < 0, where y is the current threshold or optimum_value.
The condition for improvement_found = True is Q(x)-y < 0 (i.e.int_v < optimum_value), which is the condition of the outer if statement. Hence, the removed if statement is not needed.
Note that, condition of the removed if statement is also wrong because v < 0 means Q(x) < 0, however, the desired condition is Q(x)-y < 0.

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

Closing this since it has been included in #1448 (with Co-authorship of @pat-phattharaporn) 🙂


20220211 beacons

Addresses issues:

Beacon IDs page is confusing #611

Radio buttons used for expanding/collapsing #610

Non-descriptive title "IDs" #609

I'm going to go ahead and merge this now and get it deployed since ETHDenver starts in a few hours. I will leave the branch as active and can make changes very quickly if needed.


Add zoomage_ before all attrs

Resolves #17

oh dude awesome!

I think this would probably need a minor (1.0 -> 1.1) or perhaps major (1.0 -> 2.0) version update since it's a sizable API change. What do you think?

Yeah it will be a part of the next version, whatever number it ends up being. 2.0 might be a good idea since it's a breaking change.


UNHANDLED_ERROR - status 404

The script encountered an unhandled error and exited unexpectedly.
Please re-run the script by executing './setup_init.sh rerun'.
And raise a issue on GitHub if its not already existing:
https://github.com/mohankumarpaluru/oracle-freetier-instance-creation/issues
And include the following error message to help us investigate and resolve the problem:
status: 404
code: NotAuthorizedOrNotFound
message: Authorization failed or requested resource not found.
Please help me, i really need that machine. Thx in advance.

Duplicate of #17
please try by pulling the code from the branch LimitExceeded-false-positive-fix and let me know if you are still facing the issue

Resolved by PR #20


AMBARI-25228 add a second HiveServer2Interactive Button Missing in Ambari UI is there is config group for Hive Service (asnaik)

AMBARI-25228 add a second HiveServer2Interactive Button Missing in Ambari UI is there is config group for Hive Service (asnaik)
What changes were proposed in this pull request?
The Add HiveServer2Interactive Button was missing in ambari UI due to script error which happens if there exists config group defined for hive service.
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)
Please review Ambari Contributing Guide before opening a pull request.

Hi @hiveww  ,
Can you please help me review this PR .
this is related to AMBARI-25228

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5088/
Test PASSed.


OVER_QUERY_LIMIT

How to solve this error ?

Means  you are not giving correct APi key just check from google developer console


Horovod training permission error because of hardcoded "/" path

When training using horovod, all processes that are not "on_worker" are being given a hardcoded experiment_dir_name = "/" in training, see https://github.com/uber/ludwig/blob/10aac398edb8655a527e3d650f1b5f263eb364eb/ludwig/train.py#L206. This leads to permissions errors when write permission for this directory are not given to the user.

We definitely need to fix this, but the non-master workers should not write anything to disk this should not be a problem. If they are writing something, that's actually what we have to fix. Can you please provide the error you get so that we can identify where the workers are writing?
As a temporary workaround I suggest you to replace "/" with "." and you can set writing permissions to the current working directory.

Hey @w4nderlust,
The actual path that the workers are attempting to use is /model. We temporarily fixed this by just creating this directory. The workers will not write anything into this directory, but they will attempt to create it nevertheless. If the directory already exists, no exception occurs.
I don't have access to a multi-GPU machine right now, but I think the error stems from this line: https://github.com/uber/ludwig/blob/10aac398edb8655a527e3d650f1b5f263eb364eb/ludwig/models/model.py#L402
There is no is_on_master guard that protects this line from non-master workers.


Report: hide some columns by default

Could you add a comment saying the names of the columns?

Could you add a comment saying the names of the columns?

Done!


[FEATURE] Output chat directly to file in simple, plain text (no metadata)

Is your feature request related to a problem? Please describe.
I'm using Windows 10's CMD to run Chat Downloader. Because Windows is terrible, that thing has some problems with Unicode characters. They don't display properly in the CMD window, and attempts to redirect the output using > causes any Unicode characters to disappear completely from the file they are being redirected to. I am able to copy and paste the chat from the CMD window into a text file which then displays the characters correctly, but this is always cumbersome and for very active chats on long streams it is impossible due to line limits with CMD.
Describe the solution you'd like
I'd like an option for the output that this program already supports to write to a file directly the exact same thing it already prints to the console. As in, I don't care about properly formatted and labeled metadata about each chat message that can be processed by me, I just want what the chat message, name of the user, and the time it was sent, much like you would see in the stream's actual chat.
Describe alternatives you've considered
It's very possible that somewhere documentation exists on how to get CMD to do this, and I'm sure it isn't a problem for almost any other operating system. If anyone has those solutions, feel free to post them here, but maybe also include a reference to that in documentation for Chat Downloader. Alternatively, if this feature already exists, point me in the direction of documentation for it so that I may use it, but perhaps display this documentation more prominently since I imagine it would be a common use case.

Sure I can add something like this 😃👍

I found that post as well and it didn't solve my issue. I wish I knew why it didn't solve my issue since it seems like it should, but that's neither here nor there. Thank you for considering this feature request.

While I add this feature to the command line, you could use the following python program to do what you want:
from chat_downloader import ChatDownloader

url = 'https://www.youtube.com/watch?v=5qap5aO4i9A'
chat = ChatDownloader().get_chat(url)                   # create a generator

with open('output.txt', 'a+', encoding='utf-8') as output_file:
    for message in chat:                                # iterate over messages
        formatted_message = chat.format(message)
        print(formatted_message)
        print(formatted_message, file=output_file)      # write to a file

This functionality has been added in latest versions. 👍
Using --output text.txt will now output exactly as shown in the console. For example,
chat_downloader https://www.youtube.com/watch?v=5qap5aO4i9A --output chat.txt

will output something like:
2021-07-01 17:41:22 | shiny saji: @k.s😂
2021-07-01 17:41:22 | Steph Glz: 15
2021-07-01 17:41:23 | Xx_burro_pixel_lolplayer: potooooooooooooooooo
2021-07-01 17:41:24 | Mikasa Ackerman: im very concerned
2021-07-01 17:41:24 | Adidas Nature: awesome music love it man ❤😘 and feels alone 🥺
2021-07-01 17:41:25 | Oifil 1: 21
2021-07-01 17:41:26 | Kaulo Soldaat: 20
2021-07-01 17:41:31 | Morse Code: can't believe that girl is writing for a year! I would've died writing that much.

Let me know if you have any further questions.

Finally got a chance to test this. Works exactly as I expected it to. Thank you very much!


Add tests for MANIFEST.in

I was looking in to finishing #610, but found that there were no tests for MANIFEST.in that I could find. As setuptools customises the FileList a little bit, and #610 customises it some more, some tests for this would be sensible.
I wrote some tests that work much like setuptools/tests/test_sdist.py, by creating some files and running with various MANIFEST.in files.
I also copied the FileList tests from distutils, modifying them slightly to fit with py.test and the setuptools environment.
This way, it will be easy to verify that any modifications done to setuptools retain compatibility with distutils.

OK, got the tests passing. Compatibility across so many versions and platforms is apparently tricky!

Awesome. Thanks!


Question about Compilation Time

Hello there!
 We have a few structs with a relatively large number of fields, and their old @type t definitions fully specified each field. Upon changing these to @type! and implementing a few @spec!s on functions that used them, we quickly found that our compilation time rose to 3–4 minutes.
For reference, the rough setup is:
A.t() :: %A{...[16 fields]...}
B.t() :: %B{...[8 fields]...}
C.t() :: %B{a: A.t(), b: B.t()}

With six function specifications on module C that reference all three types in various combinations.
So, the question: is this expected? I can imagine that the sheer number of fields on each struct, especially when nested, creates an explosion of code generation. In the documentation you mention:

In the case of for instance a large collection or a deeply-nested 'tree of structs' [runtime checks] might still be too slow.

Could this be true for compile time as well?
More generally, do you have any recommendations on strategies for type-checking structs? Perhaps the full specification of each field would make sense on a constructor function, but the canonical t type should stop at %__MODULE__{} with no fields.
Thanks for your work! Excited for more people to see it at ElixirConf EU.

:thinking: Compilation time being affected this badly is not something that is expected nor intended.
My best guess as to what causes it, is that the current approach of fully inlining the type-check at each of the places where it is used combines badly with having nested structs containing many fields.
A potential solution would then be to add an option to TypeCheck to not inline certain kinds of checks. But before looking into this, we first need to find out whether this indeed is the problem.
One thing you could try, is to compare the difference in compile times between enabling/disabling runtime checks in the various modules, to see whether the problem indeed originates from the runtime checks being generated (but I'm quite certain that it does).
One more thing you could try, just to test the difference in compile-time, is to see how fast/slow compilation is with version 0.9.x of the codebase (vs the current, 0.10.4 version): Because we want to support type-checking passed-in functions, a number of the type-checks that are generated were rewritten to more complex forms in 0.10.x (and I have not gotten around to switch between the two based on whether there actually is a function value inside).
This would be an interesting datapoint, but I don't recommend using version 0.9.x in production because there are a number of bugfixes (only) in newer versions.
And besides this, I'll try to come up with a minimal example as a separate public repo, so it's easier to profile and reason about.
As for the general strategy w.r.t. type-checking 'large' structs: I think that 'check them fully everywhere' is a good default. Being able to override it is however important for performance (moreso runtime performance, but as we see now, likely compile-time as well). For many structs in our codebases we can (up to a point) guarantee that they are only constructed by e.g. a MyModule.new as you also mention. It might make sense to allow people to configure 'check depth' between:

Check all structs everywhere
Only perform the full check on %MyModule{} when passing them to functions of MyModule. Otherwise only check whether their struct key is MyModule.
Perform shallow checks everywhere (and allow this to be overridden locally for e.g. MyModule.new.

Even nicer might be to perform checks based on the opaqueness of a type's typespec. Unfortunately, in practice this leads into a mire where Dialyzer and Elixir's defaults don't work well together as checking whether a value even is a particular struct is strictly speaking not allowed on opaque types. (c.f. https://github.com/elixir-lang/elixir/issues/8463).
Some discussion about this also happened in the past in the ElixirForum topic, but it was not the only thing we talked about, so it might be a difficult to look through the conversation.

Which Elixir and OTP versions are you using by the way?

Apologies for the delay (CodeBEAM travel, etc.). I was on OTP 24.3.3 with Elixir 1.12.3 for the original test. Haven't yet tested the items you mentioned, but will put it in my mental queue.

I created a smaller test case repository at aj-foster/type_check_example.
With it, here are some test results:
TypeCheck Compilation Benchmarks
(mix clean; time mix compile)

0.12.0 with default settings

mix compile  27.02s user 1.75s system 103% cpu 27.925 total
mix compile  26.98s user 1.78s system 103% cpu 27.881 total
mix compile  26.88s user 1.70s system 103% cpu 27.723 total

0.12.0 with runtime checks disabled for main module

mix compile  0.79s user 0.63s system 139% cpu 1.016 total
mix compile  0.82s user 0.73s system 156% cpu 0.994 total
mix compile  0.80s user 0.72s system 163% cpu 0.932 total

0.12.0 with runtime checks disabled for struct modules

mix compile  29.43s user 1.84s system 102% cpu 30.466 total
mix compile  27.72s user 1.81s system 103% cpu 28.639 total
mix compile  26.95s user 1.65s system 101% cpu 28.061 total

0.12.0 with runtime checks disabled for all modules

mix compile  0.82s user 0.72s system 154% cpu 0.992 total
mix compile  0.80s user 0.72s system 151% cpu 1.005 total
mix compile  0.79s user 0.65s system 158% cpu 0.907 total

0.9.0 with default settings

mix compile  10.02s user 1.55s system 105% cpu 10.962 total
mix compile   9.83s user 1.51s system 106% cpu 10.630 total
mix compile   9.69s user 1.51s system 106% cpu 10.556 total

0.9.0 with runtime checks disabled for main module

mix compile  0.76s user 0.70s system 167% cpu 0.872 total
mix compile  0.75s user 0.70s system 163% cpu 0.889 total
mix compile  0.73s user 0.63s system 151% cpu 0.899 total

All of these tests were run on Elixir 1.13.3 and OTP 24.3.2.

Thank you for this example! I can reproduce the slow compilation times on my machine.
This is indeed unsustainably slow, and something that we'll look to improve.

Leaving this here for myself to continue debugging later.

I'm very curious how much the current optimizations already help on computers that are newer than my 8-year-old laptop.

Here's another round of tests, first on latest master and second on compilation_performance3 (commit SHAs listed for clarity).
The main module in the example is egregious in terms of the density of its type specifications, but probably normal in terms of the total number of references to the struct types. While the 10 seconds would add up across multiple such modules, I'd have no problem turning it on, for example, in CI while running tests. Less problematic modules could easily stay on in all environments.
TypeCheck Compilation Benchmarks
(mix clean; time mix compile)

154fd80c with default settings

mix compile  21.87s user 5.34s system 113% cpu 23.983 total
mix compile  21.47s user 5.15s system 114% cpu 23.148 total
mix compile  21.93s user 5.27s system 114% cpu 23.844 total

154fd80c with runtime checks disabled for main module

mix compile  0.80s user 0.75s system 168% cpu 0.913 total
mix compile  0.80s user 0.73s system 161% cpu 0.948 total
mix compile  0.79s user 0.73s system 165% cpu 0.916 total

154fd80c with runtime checks disabled for struct modules

mix compile  21.55s user 5.21s system 115% cpu 23.218 total
mix compile  21.27s user 5.13s system 115% cpu 22.906 total
mix compile  20.94s user 5.60s system 108% cpu 24.508 total

154fd80c with runtime checks disabled for all modules

mix compile  0.80s user 0.70s system 154% cpu 0.966 total
mix compile  0.79s user 0.67s system 128% cpu 1.128 total
mix compile  0.81s user 0.72s system 135% cpu 1.129 total

---

c99981ce with default settings

mix compile  9.93s user 0.98s system 106% cpu 10.221 total
mix compile  9.86s user 1.03s system 107% cpu 10.156 total
mix compile  9.89s user 0.98s system 106% cpu 10.167 total

c99981ce with runtime checks disabled for main module

mix compile  0.77s user 0.69s system 153% cpu 0.955 total
mix compile  0.81s user 0.77s system 162% cpu 0.974 total
mix compile  0.79s user 0.71s system 162% cpu 0.920 total

c99981ce with runtime checks disabled for struct modules

mix compile  9.89s user 1.03s system 106% cpu 10.221 total
mix compile  10.18s user 1.03s system 106% cpu 10.554 total
mix compile  9.87s user 1.00s system 107% cpu 10.134 total

c99981ce with runtime checks disabled for all modules

mix compile  0.81s user 0.73s system 146% cpu 1.054 total
mix compile  0.81s user 0.74s system 152% cpu 1.018 total
mix compile  0.78s user 0.69s system 157% cpu 0.934 total

All of these tests were run on Elixir 1.13.3 and OTP 24.3.2.


Date and Time not correct

The date and time don't seem to be correct in the container. It seems to be the UTC time.
I have added /etc/localtime to the docker run command.
I think it is missing the tzdata package in the container. After installing it in the container the local date and time worked.
I have also added TZ=Europe/Amsterdam as variable to the docke run command but I am not sure if this is also necessary.

Interesting, I do not experience this issue.
What does your docker run/docker compose look like?

This is the docker run command:
docker run -d --name='Viseron' --net='br0' --ip='<IP_ADDRESS>' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -v '/mnt/user/Cameras/Viseron':'/recordings':'rw' -v '/mnt/user/appdata/Viseron':'/config':'rw' -v '/etc/localtime':'/etc/localtime':'ro' --device=/dev/dri:/dev/dri 'roflcoopter/viseron-vaapi:latest

Hmm strange. I will add in the tzdata package. Thanks for figuring it out!


Include the prime factors for RSA private keys

I'm intending to use ironclad for generating private/public key pairs, which will then be encoded as OpenSSH private and public keys.
The RSA primes p and q are also part of the binary blob for OpenSSH private keys, so in order to properly encode a private key in OpenSSH format I need to have these as part of the RSA-PRIVATE-KEY class.
This MR adds p and q primes to RSA-PRIVATE-KEY class and also exports their readers -- RSA-KEY-PRIME-P and RSA-KEY-PRIME-Q respectively.

Thanks.


Column size calculation needs to be user adjustable.

It looks like there are some heuristics in the code that computes column sizes when rendering the HTML to an image. The following MWE shows the issue I'm running into:
import dataframe_image as dfi
import pandas as pd

text = '{"Eval 21":{"pipe":"BAS+SC","bas_pxl.model.channels":"(L8,PD,S2,WV):BGR","bas_pxl.package_fpath":"Drop8_Median10GSD_allsensors_<tuned>_V7_epoch187_step2632","bas_poly.thresh":0.35,"bas_poly.time_thresh":0.8},"Eval 21b":{"pipe":"BAS","bas_pxl.model.channels":"(L8,PD,S2,WV):BGR","bas_pxl.package_fpath":"Drop8_ARA_Median10GSD_allsensors_pointannsv1_v1_epoch56_step4788","bas_poly.thresh":0.39,"bas_poly.time_thresh":0.75}}'
df = pd.read_json(text)
fpath = 'foo.png'
dfi.export(
    df.style,
    fpath,
    table_conversion='matplotlib',
    fontsize=12,
    max_rows=-1,
    dpi=None,
)
import subprocess
subprocess.call(f'eog {fpath}', shell=True)

This results in a column being cutoff:

If I mess with the fontsize I can get it to work reasonably well. But it would be nicer to either fix the heuristics to work in this case (which may not be possible, I've glanced at them, but haven't seen if they attempt to always well-size the columns), or give the user some means to adjust the multiplier used on each column or something like that.
I'd like to put in a fix for this, but I need feedback on what the right API should be.

If you mean the second cell of index column is cutoff, I think you could refer this fix https://github.com/dexplo/dataframe_image/pull/90
I fix bold column header width but I'm not should if it applied to all cell.


docs: remove travis "master" build status

Description
Removed the travis "master" build status from readme as we will not be using that branch.
Fixes #53
Type of Change:

Documentation

How Has This Been Tested?
Checked readme
Checklist:
Delete irrelevant options.

[x] My PR follows the style guidelines of this project

[x] I have performed a self-review of my own code or materials

[x] I have made corresponding changes to the documentation

Code/Quality Assurance Only

[x] My changes generate no new warnings

Although this branch will become active once we start putting this in production @Techno-Disaster , right?

Although this branch will become active once we start putting this in production @Techno-Disaster , right?

Not sure abt that. but it seems right. keep developing on develop and push to master when we want to release an update


Disconnect behavior and status endpoint

Disconnect behavior
We should have the library implement a couple of disconnect behaviors: (1) retry on disconnect; (2) exit on disconnect.
A reasonable default could be to retry and check an env variable to change the behavior to exit ?
Status endpoint
Somewhat related is sending a report status on some standard topic (e.g. scene_topic/p/<program-id>/status). Essentially just reporting if the program is alive and some status/data that could be useful for debugging (list of users/objects, ...) ?
These could be periodic or triggered by a message on the topic.

Added a way to reconnect in f8e5a7e, but need to add an option to disable reconnects and add status endpoint.


Long Shadow and Score?

The long shadow and score effects appear to do nothing.
http://romannurik.github.io/AndroidAssetStudio/icons-launcher.html#foreground.type=clipart&foreground.space.trim=1&foreground.space.pad=0&foreground.clipart=res%2Fclipart%2Ficons%2Faction_account_balance.svg&foreColor=607d8b%2C0&crop=0&backgroundShape=square&backColor=ffffff%2C100&effects=shadow

Seems to be working for me - you can easily see the shadow in the top left. Try increasing the padding around the icon

Hi...
I think long shadow is a little too pale. it would be nice to have an option to adjust it.
thanks

Yes, I also think long shadow is too pate, On my phone, almost nobody can find it got shadow there.


892 latest main branch is not building the frontend image correct

The typo is causing the build failure.
To test:

build a test image cd frontend && docker run -it clowder/clowder2-frontend:test-build /bin/sh
point the frontend in docker-compose.yml to this image image: "clowder/clowder2-frontend:test-build"
docker compose up

Some helpful command e.g. get into the built image to check nginx folder
docker run -it clowder/clowder2-frontend:test-build /bin/sh
You should see all the bundles there

I built the docker image with
 docker build -t clowder/clowder2-frontend:test-build .
and then used that image in the docker-compose file for frontend and it is now working.
and i am seeing all the bundles inside
/usr/share/nginx/html

I built the docker image with  docker build -t clowder/clowder2-frontend:test-build .
and then used that image in the docker-compose file for frontend and it is now working.
and i am seeing all the bundles inside
/usr/share/nginx/html

Yes I updated my description of the PR. I made some typo there. Thank you for sharing how to correctly build the image.


OTEL - kubernetes demo -  Images pulling issue for singlenode kind cluster

Team,
we are trying to deploy the OTEL kubernetes demo inside single node kind cluster following the documentation
https://opentelemetry.io/docs/demo/kubernetes-deployment and while performing step  "kubectl apply --namespace otel-demo -f https://raw.githubusercontent.com/open-telemetry/opentelemetry-demo/main/kubernetes/opentelemetry-demo.yaml" , we are unable to pull images and attached the error .
"Service": rpc error: code = Unknown desc = failed to pull and unpack image "ghcr.io/open-telemetry/demo:1.5.0-shippingservice": failed to resolve reference "ghcr.io/open-telemetry/demo:1.5.0-shippingservice": failed to do request: Head "https://ghcr.io/v2/open-telemetry/demo/manifests/1.5.0-shippingservice": tls: failed to verify certificate: x509: certificate signed by unknown authority"
This is happening for all images and images name referenced below

Please let us know any fix for this.

Looks more like a cluster CA availability issue rather than the demo problem. Check the your kind node certs. Also what kind provider do you use - docker/podman? What is the OS environment?

@gajavallisantosh are you still have issues with this and the latest release?


add pxe, efi, and other files from syslinux-6.0.3

https://app.wercker.com/#build/54c8582cf95931eb6a163dfa is clean
:ship:


Upgrade to go-jsonnet v0.16.0

v0.17.0 has some backward compatibility issues.


Solar mode using grid energy

Describe the bug
I am testing evcc and during my first charge using the Solar mode, I noticed it was using not only my solar excess but also consuming energy from the grid. At the time my panels were generating ~9.8Kw and evcc was charging the vehicle with the maximum capacity of my my charger, 11.6kW (see screenshot below).

Other times it was ignoring the energy consumed in my house and still using more energy than produced by my solar:

At the end of the charging, roughly 10% of the energy used was from the grid instead of the my solar, despite the whole time evcc was running on "Solar" mode.

I am not sure if this is a configuration problem, if this is expected, or if this could be a bug.
Steps to reproduce

Charge car using Solar mode and check if grid energy was also used during charging.

Configuration details
# trial token, valid until 2024-11-14
sponsortoken: ...

# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: ...

interval: 30s # control cycle interval

chargers:
- type: template
  template: twc3
  host: <IP_ADDRESS>
  name: wallbox1

loadpoints:
- title: Garage
  charger: wallbox1
  mode: pv

site:
  title: My home
  meters:
    grid: ha.grid
    pv:
      - ha.pv

meters:
  - name: ha.grid
    type: custom
    power:
      source: http
      uri: http://<IP_ADDRESS>:8123/api/states/sensor.sa_import_export_power
      method: GET
      headers:
        - Authorization: Bearer ...
      insecure: true
      jq: .state|tonumber
      timeout: 2s
  - name: ha.pv
    type: custom
    power:
      source: http
      uri: http://<IP_ADDRESS>:8123/api/states/sensor.sa_generation_power
      method: GET
      headers:
        - Authorization: Bearer ...
      insecure: true
      jq: .state|tonumber
      timeout: 2s

vehicles:
  - name: mycar
    type: template
    template: tesla
#    title: # Will be displayed in the user interface (optional)
    accessToken: ...
    refreshToken: ...
#vin: W... # Required if you own multiple vehicles of the same brand (optional)

Log details
Sorry, I didn't saved the logs at the time of the charging.

What type of operating system are you running?
Linux
Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version
0.131.4

see documenation for getting a log file
https://docs.evcc.io/en/docs/faq#how-do-i-create-a-log-file-for-error-analysis

I have the same issue with my evcc setup. I am running on  latest Home Assistant OS, and evcc addon. PV, Grid, Battery are setup and providing correct readings. The Tesla Wall Connector 3 is implemented and connected. I have a Tesla Model 3, for which the virtual key is set up, the API keys are generated and added to evvc.yaml.
I have checked the configuration several times and re-setup each element from scratch, including revoking virtual key and API key.  EVCC receives all PV, grid, battery, and car telemetries, but I cannot mapulate the loadpoints i.e. charge plans and max current/charge rates are ignored, and loadpoint charge states do not have any effect to the actual charging.
Cheers.
EVCC:
Current version: 0.131.4
Hass.IO/Home Assistant:
Core: 2024.11.0
Supervisor: 2024.11.2
Operating System: 13.2
Frontend: 20241106.0
EVCC Config:
`network:
schema: http
port: 7070
interval: 30s # control cycle interval
log: debug
levels:
cache: error
plant:
site:
title: Zuhause
meters:
grid: grid
pv: pv
battery: battery
tariffs:
currency: EUR
grid:
type: fixed
price: 0.375
feedin:
type: fixed
price: 0.08
co2:
type: grünstromindex
zip:
mqtt:
broker: <IP_ADDRESS>:1883
topic: evcc
clientid: evcc
user: evcc
password: ''
meter definitions
meters:

name: grid # Net Grid Power (import - export)
type: custom
power: # Current Load (W)
source: mqtt
topic: homeassistant/energy/grott/pv/netgridpower
timeout: 310s
scale: 0.1
energy: # Energy Total (kWh)
source: mqtt
topic: homeassistant/energy/grott/pv/elocalload_tot
timeout: 310s
scale: 0.1
currents:

source: mqtt
topic: homeassistant/energy/grott/pv/pvgridcurrent
timeout: 310s
source: mqtt
topic: homeassistant/energy/grott/pv/pvgridcurrent2
timeout: 310s
source: mqtt
topic: homeassistant/energy/grott/pv/pvgridcurrent3
timeout: 310s

name: pv
type: custom
power:
source: mqtt
topic: homeassistant/energy/grott/pv/pvpowerin
timeout: 310s
scale: 0.1  # Convert from payload value to W
energy:
source: mqtt
topic: homeassistant/energy/grott/pv/epvtotal
timeout: 310s
scale: 0.1  # Convert from payload value to kWh

name: battery #Net Batttery Power (discharge - charge)
type: custom
power:
source: mqtt
topic: homeassistant/energy/grott/pv/netbatpower
timeout: 310s  # Optional
scale: 0.1  # Convert from payload value to kWh
energy:
source: mqtt
topic: homeassistant/energy/grott/pv/eharge1_tod
timeout: 310s  # Optional
scale: 0.1  # Convert from payload value to kWh
capacity: 10.2 # Capacity (kWh)
soc: #Battery SOC (%)
source: mqtt
topic: homeassistant/energy/grott/pv/soc
timeout: 310s  # Optional

#- name: charge-meter
#type: charger
#power:
#source: mqtt
#topic: homeassistant/energy/grott/pv/p1charge1e
#timeout: 30s  # Optional
#energy:
#source: mqtt
#topic: homeassistant/energy/grott/pv/eharge1_tod
#timeout: 30s  # Optional
#scale: 1  # Convert from payload value to kWh
chargers:

type: template
template: twc3
host: <IP_ADDRESS>
name: charger_garage

type: template
template: twc3
host: <IP_ADDRESS>
name: charger_carport

loadpoints:

title: Garage
charger: charger_garage
mode: pv
vehicle: vehicle_1

title: Carport
charger: charger_carport
mode: off
#meter: charge-meter
vehicle: vehicle_2

vehicles:

name: vehicle_1
icon: car
type: template
template: tesla
title: Tesla Model 3
accessToken:
refreshToken:
vin:
capacity: 73.5

name: vehicle_2
icon: car
type: template
template: offline
title: Smart ForTwo EQ

name: vehicle_3
type: template
template: offline
title: Cube Kathmandu Hybrid
icon: bike
capacity: 0.5

name: vehicle_4
type: template
template: offline
title: Cube Reaction Hybrid
icon: bike
capacity: 0.75`

Unfortunately your report is missing a detailed log file. Without log, we don‘t have the information for diagnosing the issue described. See https://docs.evcc.io/docs/faq#wie-kann-ich-ein-logfile-zur-fehleranalyse-erstellen.

Hi Andi,
thanks for your quick response. Since I  can export logs via the EVCC ui, which of these would ou require, debug or trace? If it is trace logs, I can redact sensitive information before sharing.
Thanks in advance.

Debug is sufficient. It must show the issue, please check the pv mode calculations in the log for the relevant time stamps.

I guess I have found the "issue"... Since I was still in the setup and testing phase of the evcc installation, I had not set up a sponsorship now. Adding this fixed the "issue". While I am waiting for my own sponsorship token, I have found the trial token in the documentation.
Thanks for the effort though, and this awesome project. ;)

So there was an error message in the log.
Could we show such messages in UI also?
This would reduce support requests for sure.

I found an error indicating the missing sponsorship token in the trace logs, but as andig said, it is in the trace logs as well. The error message was produced when I switched the charging state to "off" while the car was being charged. After adding the trail token, it is now working as intended. I will replace the trail token as soon as I have my own.
You can find the trail token here: https://docs.evcc.io/en/docs/sponsorship
Log excerpt from my debug logs:
[site ] DEBUG 2024/11/08 15:22:41 pv power: 300W
[site ] DEBUG 2024/11/08 15:22:41 battery soc: 33%
[site ] DEBUG 2024/11/08 15:22:41 battery power: -18W
[site ] DEBUG 2024/11/08 15:22:41 grid power: 0W
[site ] DEBUG 2024/11/08 15:22:41 grid currents: [7 7 7]A
[site ] DEBUG 2024/11/08 15:22:41 battery has priority at soc 33% (< 75%)
[site ] DEBUG 2024/11/08 15:22:41 site power: 100W
[lp-1 ] DEBUG 2024/11/08 15:22:41 charge voltages: [231 232 232]V
[lp-1 ] DEBUG 2024/11/08 15:22:41 detected connected phases: 3p
[lp-1 ] DEBUG 2024/11/08 15:22:41 detected active phases: 3p
[lp-1 ] DEBUG 2024/11/08 15:22:41 charger status: C
[lp-1 ] DEBUG 2024/11/08 15:22:41 soc estimated: 39.27% (vehicle: 39.00%)
[lp-1 ] DEBUG 2024/11/08 15:22:41 vehicle soc: 39%
[lp-1 ] DEBUG 2024/11/08 15:22:41 vehicle soc limit: 60%
[lp-1 ] DEBUG 2024/11/08 15:22:41 vehicle range: 180km
[lp-1 ] ERROR 2024/11/08 15:22:41 charger disable: sponsorship required, see https://github.com/evcc-io/evcc#sponsorship
[site ] DEBUG 2024/11/08 15:23:07 ----
[lp-1 ] DEBUG 2024/11/08 15:23:07 charge power: 11218W
[lp-1 ] DEBUG 2024/11/08 15:23:07 charge currents: [16.1 16.2 16.1]A

charger disable: sponsorship required, see https://github.com/evcc-io/evcc#sponsorship

This looks a bit confusing but comes from the fact, that the Tesla cloud proxy (for the vehicle!) requires sponsorship.


SELECT index predis

Hi,
we played around with dynomite and would like to use it in our application.
We are using the predis client. Predis sends a initial SELECT 0 which breaks the connection to dynomite. Our application only uses the redis database 0 and we would like to return OK / ignore the select and continue. I am not that familiar with C. Can anyone give me a hint what we have to change to achieve that?
Best regards

Yeah, Lettuce does this, too, I'm afraid. More about it here: https://github.com/Netflix/dynomite/issues/551

You could just add the SELECT command in the following parser and should be fine. If you plan to do that just add a comment with the corresponding limitations.

We are having similar issues. Tried to use Dynomite along with 3Scale and Select Index failed.


"TypeError: allocator undefined for Proc" after upgrading of rails to 4.2

expect(Car.method :open).to be_delayed(car.id) raises TypeError: allocator undefined for Proc exception.
It happened with rspec-sidekiq 2.0.0 and upgrading to 2.2.0 hasn't resolved the issue.

Backtrace:
     # /rspec-sidekiq-2.2.0/lib/rspec/sidekiq/matchers/be_delayed.rb:61:in `block in find_job'
     # /rspec-sidekiq-2.2.0/lib/rspec/sidekiq/matchers/be_delayed.rb:60:in `each'
     # /rspec-sidekiq-2.2.0/lib/rspec/sidekiq/matchers/be_delayed.rb:60:in `find'
     # /rspec-sidekiq-2.2.0/lib/rspec/sidekiq/matchers/be_delayed.rb:60:in `find_job'
     # /rspec-sidekiq-2.2.0/lib/rspec/sidekiq/matchers/be_delayed.rb:34:in `matches?'

It happened because we passed AR objects as parameters to jobs


Release 0.6 preparations

Looks good to me. I went back over the changelog, and I've noticed that #182 and #173 are API breaks, so I wonder should they be moved to the Changes section.

👍

bors r=bpfoley,CAD97
No strong opinion about moving those sections in the changelog, we can follow-up :)

Bors is unable to wait for tests for some reason:

Status: Clippy: stable (Succeeded) Format: stable (Succeeded) Tests (Running)

Not sure why...

I'll take another look at bors later today, see if I can fix that.


Feat distance array

@hmacdope I've started on distance array.  Looking at the dispatch mechanism, does it make sense to have one dispatcher for each family of functions, or a dispatcher that sets all pointers?

@hmacdope I've started on distance array. Looking at the dispatch mechanism, does it make sense to have one dispatcher for each family of functions, or a dispatcher that sets all pointers?

You could have a dispatcher that sets all functions but you would need to guarantee that it is called before any function otherwise segfault.  eg on the python side it would have to behave kind of like np.import_array.  This is complicated on the C++ side as there is no main(){} or entry point for running anything.
I think it is possibly better to just have each function do its own dispatching?


#v0.4.17，#win10，can not get into the application

In the Windows 10 system, when I double-click on the icon and stay on this interface.
What should I do to solve this problem?

I tried uninstalling and reinstalling, but it still didn't work.

#v0.4.17，#mac intel，I also encountered this problem

Closing this as it is a duplicate of https://github.com/BloopAI/bloop/issues/917


New roles are created in a folder too deep.

Run ansible-dev role new namespace.name and the role is created in ./roles/namespace.name/namespace.name when you would expect the role to be created in ./roles/namespace.name

seems to be a decrepensy in the way that the path is generated by the ansible init sub-command, unlike other Ansible commands, it doesn't honor the roles_path from the ansible.cfg file and always uses the current directory. The init-path should be the same value as the role path from the configuration file.