Incorrect package duplicate error when using/missing .git extension

Incorrect package duplicate error when using/missing .git extension
Issue description
dbt seems to treat packages as not identical (but with duplicate name) if one reference has the .git file extension and another does not. This is problematic when adding a dependency that uses a package a project already includes.
Results
I had a project that was pulling the dbt-utils package. When I set up the dbt-event-logging package, despite pulling the same version/release, dbt returned the following error:
Found duplicate project dbt_utils.
This occurs when a dependency has the same project name as some other dependency.

My packages.yml looked like:
packages:
  - git: "https://github.com/fishtown-analytics/dbt-utils"
    revision: 0.1.12

  - git: "https://github.com/fishtown-analytics/dbt-event-logging.git"
    revision: 0.1.5

The package.yml file in dbt-event-logging looks like:
packages:
  - git: "https://github.com/fishtown-analytics/dbt-utils.git"
    revision: 0.1.12

The problem was resolved by adding the .git suffix to the dbt-utils package in my project.
System information
The output of dbt --version:
installed version: 0.10.1
   latest version: 0.11.1

The operating system you're running on: Windows
The python version you're using: 3.6.0

Thanks for the report @DylanBaker!

There are a couple ways we can fix this:

strip the .git from all URLs passed to GitPackage. That does seem to work fine for both https:// and git:// URLs on github, though I'm not sure how correct that is in the strict protocol sense. I'd feel pretty bad if that only works for github.
override PackageListing's __contains__/__getitem__/__setitem__ to treat these almost-collisions as collisions.
either of the above, but with per-protocol handling of whether to strip or add the .git (strip on https://, add on git://?)

I think the problem with no text munging at all is that you could two different packages that use different syntaxes of a shared package's URL and it wouldn't be in your control to change it unless you forked the repo.
i.e. I use Package A and Package B in my project. Package A uses dbt-utils with a trailing .git. Package B uses dbt-utils without a trailing .git. There's no easy recourse for me as the end-user to fix that (particularly for less technical users). Even if the error is more descriptive, it's probably not immediately useful.

@DylanBaker check out the discussion in the PR too: https://github.com/fishtown-analytics/dbt/pull/1428
I think that rather than text munging, we might be able to identify when two stated git urls point to the same repo, and then just pick one of them. The effectively does some amount of "munging" for us, but it changes the paradigm from "dbt will remove your .git suffix" to "dbt will resolve conflicts by picking a winner".
I'm just not 100% certain that every git server out there supports cloning git urls both with and without a .git  suffix, and I'd prefer that we keep dbt deps as git-provider-agnostic as we can!


tbCreateTable msg and subsequent updateTable msg with the same _msgid does not "persist" updated data at the dashboard client side

Maybe this is a kind of a edge case, but here goes:
Consider the following  attached flow

When the upper most inject node is activated a tbCreateTable command is send and,  delayed  300 ms, a subsequent updateTable is send  - and the table looks like this:

The data in Id and Text column is sent together with tbCreateTable command and the data in the Text2 column is sent with the updateTable command.
If the dashboard is then refreshed by the browser the updated data disappear:

However, if the data update is initiated by the second inject node the updated data survives a browser refresh.
Also if a "dummy" update with no data is send (the third inject node) the updated data survives a browser refresh.
As far I have found out the reason seems to be because the tbCcreateTable and the updateTable messages share the same _msgid because they are chained by the delay node.

You are correct in your analysis.
When the table is in Shared (not multi-user) mode, the latest table data image is cached in a Node-red datastore, to allow restoring the table after browser refresh or upon opening a new client. Whenever the table is updated, it shows the update and also updates the table image in the datastore.
The way Node-red dashboard works, a message from a server node (e.g. inject) is broadcasted to all open clients, hence each client will attempt to update the datastore. Since the table can hold a large amount of data, I collapse these attempts by msg._msgid and only update the datastore once. BTW, I do the same for table responses, otherwise if you had three open clients and issued a getData command from a server node, you would have received 3 identical responses.
I could perhaps add some heuristics to distinguish between messages, but the scenario you describe (sending consequent messages with same _msgid) seems uncommon. Do you have any specific use-case where this is needed?

Thank you for the explanation – it makes sense.
Knowing the behavior, it is not very difficult avoid it.
My “use-case” is quite close to my example. It is taken from an initialization procedure when node-red is restarted or when the flow is redeployed. In the example the table is constructed with data in the two first columns (id and text) – we could call these data “master data” (data which are rarely changed) and then I update the third row (text2) with the “actual” or “dynamic” data which may or may not be persisted by node red since the restart. The first inject node is - in my real case - set to “inject once after..” to initiate the table construction shortly after restart and I then naturally chained in the update part via a delay node and then the “problems” began 🙂. Knowing the behavior, it could easily be solved by having an extra inject node like this:

I was even looking for a way to change the _msgid which is impossible (I think 🤔) to do without “leaving the scope” of Node red. I came up with this solution:

I'll stick to my initial “hunch” that this is a kind of edge case or behavior.

A simpler approach (which avoids timing dependencies) would be to pass the delayed msg through a function or change node which deletes its msg._msgid property. When the Node-red framework sees that a sent msg has no Id, it automatically gives it a new Id. This is how you can create & send a new msg from a function node
let newMsg = {payload:"hello"}; // no msgid. will be assigned automatically by Node-red
return newMsg;.

I don't think it does, try this flow:

And by the way, why not set the table's "master data" as part of the table's initial configuration?

Even though they are "master data" I want to be able to upload them from the dashboard, so I have them stored in the flow context which can be updated by a file upload node from the dashboard.

Interesting. It seems to be remembering the input msg Id.
However, this works:

Now that we understand each other... :-)
closing the issue


[Dependency Scanning][NFC] Associate single-shot scanner service lifetime with the owning compilation instance's ASTContext

Resolves rdar://131388478

@swift-ci test

preset=asan
@swift-ci please test with preset macOS platform


node_icon.diag assumes a network connection and Debian system

https://github.com/yuzutech/blockdiag/blob/ce37f0c18dc7f88caab3d3b24aac4f3f066b793c/src/blockdiag/tests/diagrams/node_icon.diag#L1-L6
These cause problems for us in Nixpkgs, as we of course don’t have a Debian logo lying around on the filesystem and our build and testing environment cannot access external network resources.
I see that the Debian logo is already present in‐tree, so hopefully that could be changed to a local reference. I’m not sure if the URL is critical to the functionality being tested here, but I thought I’d raise it anyway.
(Copied from https://github.com/blockdiag/blockdiag/issues/184.)

I'm not even sure that this file is used in the test suite. Could you please provide which command is failing while creating the Nix package?

 See https://setuptools.pypa.io/en/latest/pkg_resources.html
    import pkg_resources

src/blockdiag/tests/rst/test_blockdiag_directives.py::TestRstDirectives::test_align_option1
  /nix/store/3r2canscw43dabd5mym6acqwkbiprqfw-python3.12-reportlab-4.2.2/lib/python3.12/site-packages/reportlab/lib/rl_safe_eval.py:12: DeprecationWarning: ast.NameConstant is deprecated and will be removed in Python 3.14; use ast.Constant instead
    haveNameConstant = hasattr(ast,'NameConstant')

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================
FAILED src/blockdiag/tests/test_generate_diagram.py::test_generate_with_separate[/private/tmp/nix-build-python3.12-blockdiag-3.0.0.drv-0/source/src/blockdiag/tests/diagrams/node_icon.diag-svg-options92] - AssertionError: Caught error
=========== 1 failed, 712 passed, 1 deselected, 2 warnings in 21.61s ===========

Thanks!
Indeed, test_generate_diagram.py will convert any file found in tests/diagrams (except a few) 😬
I guess we want to make sure that BlockDiag can resolve an icon from an absolute path and/or from an URL.
One way would be to copy an image to the OS temporary directory and use that destination as an absolute path. We could also start an HTTP server to serve an ico/image (or just mock the HTTP client).
I will take a deeper look in order to make the tests more portable.

Thanks for considering this! Those all sound like reasonable solutions to me. Note that downstream packages like {seq,act,nw}diag reuse the fixtures, so something like a local HTTP server may require some fiddling to plumb in to those test suites. We need to patch them to handle your existing test suite migration changes anyway, though, so I understand if worrying about that is out of scope for you.

Note that downstream packages like {seq,act,nw}diag reuse the fixtures, so something like a local HTTP server may require some fiddling to plumb in to those test suites.

If the HTTP server is started as part of the test suite (in a dedicated thread) it should work right? In other words, the test suite won't assume that a HTTP server is running. We could use something like: https://pytest-httpserver.readthedocs.io/en/latest/

Right, I just mean that downstream projects use the blockdiag test generators that work with these fixtures, e.g. test_generat_diagram.py in seqdiag (our patch), so the test generator would have to set up the HTTP server fixture in a way that works with downstream tests like that. I’m not too familiar with pytest (despite leading the nose clean‐up effort in Nixpkgs!), so it’s possible this would Just Work.


Add support for pandas 1.4.0

Looks like the root cause may be that converting a nullable type to Categorical preserves the nullable types in the pandas Categorical categories. On the top is the latest pandas and on the bottom is 1.3.4 pandas.

This causes np.asarray calls in our imputers to introduce the new pandas null value place-holder, <NA> which throws off sklearn:

Originally posted by @freddyaboulton in https://github.com/alteryx/evalml/issues/3272#issuecomment-1020261986
This change in behavior breaks tests in three places:

In our simple imputer, we convert NaturalLanguage to Categorical in order to support imputing natural language via the most_frequent strategy. (test_simple_imputer_supports_natural_language_constant)
In our imputer tests, we test running the imputer on a dataframe that had a nullable int column converted to categorical (test_imputer_woodwork_custom_overrides_returned_by_components)
In our tests for EmailFeaturizer, and URLFeaturizer, this causes the categorical features created from Email and URL logical types to have nullable types in the categories because the physical type for Email and URL is text. See (test_ft_transform_primitive_components.py::test_component_fit_transform[component1-make_data_email_fit_transform_missing_values-make_answer_email_fit_transform_missing_values-make_expected_logical_types_email_fit_transform_missing_values])

Additionally:

There is a warning being emitted by xgboost using pd.Int64Index in data.py (https://github.com/dmlc/xgboost/blob/v1.5.0/python-package/xgboost/data.py#L250). This causes test_xgboost_catch_warnings_label_encoder to fail.

Xgboost issue may be fixed here: https://github.com/dmlc/xgboost/issues/7593

I'm going to have to pick this up to satisfy support for nullable types, @dsherry !  Just FYI, moving to this sprint.

@chukarsten Just a heads up, Featuretools doesn't yet fully support pandas==1.4.0 either. It might work for you though, but no guarantees at this point.
https://github.com/alteryx/featuretools/issues/1865

Ultimately, the problem here is that sklearn can't recognize pd.NA as a type of missing value.  When the imputer looks for a missing value, it generates a mask of the dataframe, where it can recognize None and np.nan, but running the new pandas.NA through that same function returns a simple boolean instead of a similarly shaped array with boolean values in it, with True in the cells for nan values.
I think in the long term, we should submit an issue for sklearn and perhaps a PR to fix this in sklearn.  The function that they have in place for trying to root out NaN values in an array with a dtype of "object" is pretty simple and could use some love/tests.
def _object_dtype_isnan(X):
    return X !=  X

Still working on a short term fix that makes sense.

Looks like the XGBoost warnings are remedied, per https://github.com/dmlc/xgboost/pull/7595!  Just need to wait for a release from XGBoost.


Change flag "--private-key-location" to "--private-keys-directory"

In
https://github.com/antoniomika/sish/blob/main/deploy/gcloud.md
and
https://github.com/antoniomika/sish/blob/main/deploy/docker-compose.yml

Thanks! Updated just now!


New version of the website

PR to update the website with the newest changes.
Most of the updates here are just style. This site is still running on ml5 0.0.4 and is missing docs for the newest methods
Not ready to merge yet

I finished the image classification drag drop iframe example (https://ml5js.github.io/ml5-homepage-demo/).
I added a file uploader, made the image responsive, hide the whole iframe when window.width < 200px, added font and some other styles.
It looks like this on the website. I tested it with uploading images in different size, uploading non-image file. Please let me know if you notice any responsiveness issues.

We are very close! please let me know if there is anything that I can do.

Pushed #44 to this branch.


Poseidon rework / Make it better for Starks

Poseidon is not working for the Stark Prover, since it doesn't have the correct constants.
It needs to have the proper constants to hash 1 and 2 elements.
Using generics to pick the field is going to break our design, so instead of it being generic over the field to fix the constatns, it needs to be generic over the field just for the operations, and keep the paramaters as an input when it's called as a new. Files with constants should be imported as a Rust constant

Done


Error on calling save button

There is a problem on saving data. Following screenshot when I click on Save button it give an error. The error screen shot is following the form.

here is the error.

That can be anything. Looks like your Project has a file missing.
Do you have this with every save (it occurs with different Tables) or only with one?
If it is with all, please re-create your Project with the newest serenity template and copy over from your existing Project all your Program logic.
If it is only with one table, delete all corresponding files for this table under /modules and re-create this particular module with sergen.
With Kind regards,
John

Thanks


Add glslViewer path configuration

Adds the ability to change the executable to run via require('glslView').setup{}.

Oh, my goodness. I just noticed this today. I've never had anyone make a pull-request for one of my projects. I just started this thing for myself.
Thanks! I'll review and merge these asap.


Automatically generate faster-whisper, ggml models from HF whisper model

Implement a utility that will automatically generate both models from a HF whisper model.

Is your feature request related to a problem? Please describe.
Currently, generating faster-whisper and GGML models from an HF whisper model requires manual steps, which can be time-consuming and error-prone. Automating this process would streamline model generation and reduce the potential for mistakes.
Describe the solution you'd like
Implement a utility that automatically generates both faster-whisper and GGML models from an HF whisper model. This utility should be able to take an HF whisper model as input and produce the corresponding faster-whisper and GGML models with minimal user intervention.
Describe alternatives you've considered
An alternative solution could be to create detailed documentation and scripts that guide users through the manual process of generating these models. However, this would not be as efficient or user-friendly as an automated utility.
Additional context
Automating the model generation process will require changes to the backend infrastructure to support the conversion and generation of these models. This feature will significantly improve workflow efficiency and ensure consistency in model generation.


how to set recipient id to mail agent dynamically ?

I need to send a notification mail to different users  based on events ,Any possibility with huginn to do it .

Hey @muneesmajid, with PR #1227 that I just made, recipients option should allow Liquid formatting, so you could set it to {{ email }} (for example) to send email to the address in the incoming Event's email key.

Does that solve your question?

Tried same ,but not worked to me

Sorry ,it was due to my mistake ,my request body has unwanted spaces .Working fine now and thank you for this great job.

Great!

Is this feature available with  Email Digest Agent  ?

Yes, I believe so.

ok fine ,Thank you @cantino


Pass '--expert' and '--chain' cmd-line arguments to enumerate() functions

These arguments are currently discarded/ignored for the enumerate command.  Pass them through to the per-hw enumerate() calls.
In the Jade client, use the 'chain' parameter to enable testnet-configured Jade units to enumerate successfully.

Thanks for this. For the maintainer, this came about because I was trying to set up Jade to use with Sparrow on testnet/signet, but having trouble with the Jade returning JadeError: -32003 - Network type inconsistent with prior usage (Data: None). That was the case even though the Jade was properly previously initalized for testnet using the Blockstream Green Desktop client first.
We had a long discussion about it here: https://github.com/Blockstream/Jade/issues/13#issuecomment-1334089833. You can safely ignore anything above this part of the thread as not being relevant. Then the breakthrough realization here about why Sparrow was finding an error when enumerating devices after clicking 'Scan': https://github.com/Blockstream/Jade/issues/13#issuecomment-1334380743.

We could then only probe for 'simulators' if '--expert' was passed, and make sure the test framework passes that option.

ACK f4091f47d92ead716b0b0ce53ed61b567a8fc22e


Embed a common Status duck type.

Following knative/serving#3444
This embeds duckv1alpha1.Status (knative/pkg#324) in
all of our resource's status in place of having each independently define
ObservedGeneration and Conditions. The point of doing this is that Conditions
alone are insufficient to truly assess readiness because we also must make sure
that the generation that those conditions reflect (the observed generation)
matches the current generation of the resource (the metadata generation).
Release Note
NONE

/assign @vaikas-google
/cc @mattmoor

/assign grantr

/hold
wait for knative/eventing-sources#258

/hold cancel
pkg docs updated.

Looks like you need to rerun codegen, which is odd because you just did that

/lgtm


Cannot build anymore on Erlang 23.0.2 and Elixir 1.10.3

Hi there,
We're slowly upgrading our application to Erlang 23.0.2 and Elixir 1.10.3. The only library that won't comply is keccakf1600.
The compilation log looks like this:
===> Compiling keccakf1600
make: Entering directory '/home/doodloo/Documents/Professional/TT/tt-api-v2/deps/keccakf1600/c_src'
 LD     keccakf1600.so
/usr/bin/ld: cannot find -lerl_interface
collect2: error: ld returned 1 exit status
make: *** [Makefile:141: /home/doodloo/Documents/Professional/TT/tt-api-v2/deps/keccakf1600/c_src/../priv/keccakf1600.so] Error 1
make: Leaving directory '/home/doodloo/Documents/Professional/TT/tt-api-v2/deps/keccakf1600/c_src'
===> Hook for compile failed!

I have the same problem. That library erl_interface is not in the tree anymore when I build erlang from source either.

+1

+1

Please try https://github.com/tzumby/ex_keccak - it's a Rust Nif. It works with OTP 23

There's also ex_sha3 for a pure Elixir implementation that is much slower.

@ayrat555 Very nice suggestion that might work for some users. Thanks.
In our case, we're using many other functions though, so it might not be enough.

@hickscorp can you please create an issue in ex_keccak with the function that you want. if they're available in https://github.com/debris/tiny-keccak, the wrappers for NIF can be written in a couple of hours.

@ayrat555 sorry, this slept under tons of things. I'll see if I can do that.


load more thread replies when there are more to load

We currently cap the thread depth to avoid making to
many recursive calls on the backend when decorating
the comment tree for the thread page.
This adds a "see more" button that will fetch the
subcomments under the last node in a reply thread
if it has more replies to load.
screenshot:

demo:
https://user-images.githubusercontent.com/7357287/150913155-71dcdbf9-def8-4d1c-bb52-e7efb93b37c0.mov
loading state screenshot:

this one was merged with https://github.com/diamond-app/frontend/pull/148


Changing the 'title' property of a tooltip element does not change the tooltip

How to reproduce this bug:

Create an element with a tooltip.
Change the title property of the element.
Hover over the element for the tooltip.

What should happen:
The new title should be used for the tooltip.
What happened instead:
The old title is used for the tooltip.
Browser(s) and Device(s) tested on:
Primarily Chrome, although this seems like the defined behavior rather than a browser specific bug.
Foundation Version(s) you are using:
Using version 6. This is a new project so it is a fresh download.
Test case link:
https://codepen.io/tedivm/pen/KQpxLd

@tedivm this should be a pretty easy thing to fix. When the plugin initializes it retrieves the tooltip text from the title element and stores it. We need to have it update that value before the tooltip is shown, or add a reflow method that you would call on the element to update it in your JS after the DOM change.

I ran into this issue as well. @colin-marshall your proposed fix sounds good to me.
A hacky workaround (this uses internals, shouldn't be counted on to keep working over time): Assuming el is the element you want to update the title for, you can force the tooltip to change by adding an additional line of code:
var $el = $(el);
$el.attr('title', 'My New Title');
$el.data().zfPlugin.template.text($el.attr('title'));

@kball , thanks a lot, saved my day, have been searching a lot to find how to update the tooltip text, this worked for me. i am on Foundation version 6.4.3


Nested queries using transaction

Hello,
I'm having some issues with transaction, I'm trying to do nested query withing a transaction, so if any of my query fails, the transaction should rollback all the query already done. But when forcing an error on the last transaction, even executing the transaction.rollback, the querys already done aren't rolled back.
Any ideas on how to make nested transactions with transaction management?
My code is like this:
// I have an array of promises for my querys
var promises = [];

transaction.begin(function(err) {
    // I make some querys then I push them promises to that array

    // Call all the promises
    Promise.all(promises).then(function(value) {
        transaction.commit(function(err, records) {
            callback({ message: 'Exclusão realizada com sucesso!', error: false });
        });
    }, function(err) {
        transaction.rollback(function(err) {
            callback({ message: err.message, error: true });
        });
    });
});

Thanks for your time.

Your sample code is missing the part where you're creating a Request. It's important to pass transaction to a request as described in this docs. Requests that do not get an instance of a Transaction object are not bound to any transaction.


bgpv2: removing v2Enable feature flag

BGPv2 development was done behind feature flag bgp-v2-api-enabled. Since development is now in parity with BGPv1 feature set, removing this flag. BGPv2 APIs are available for configuring BGP control plane, enabling BGP control plane is enough to start BGP control plane operator and agent sub-systems.

/test

ci-gke: https://github.com/cilium/cilium/issues/32710 ( opened new issue )

ci-e2e-upgrade : https://github.com/cilium/cilium/issues/32689

/test

To clarify, this flag was never shipped, correct? So there is no need to mention this in the upgrade docs

Yes, @gandro. It was never released. Purpose of this flag was mainly to feature gate bgpv2 development.

/test


Panic when method doesn't exist is confusing

EDIT: As discovered by @shurcooL, this was because getReader is not implemented on my version of Firefox. Changing the bug title to reflect the error message.
I've been playing around with the Fetch API using the new Callbacks, and I ran into the following unexpected panic:
panic: JavaScript error: `target` argument of Reflect.get must be an object, got (void 0) wasm_exec.js:59:6
wasm_exec.js:59:6
goroutine 6 [running]: wasm_exec.js:59:6
syscall/js.Value.Call(0x0, 0x1e8e7, 0x9, 0x0, 0x0, 0x0, 0xc01e058) wasm_exec.js:59:6
	$GOPATH/src/github.com/neelance/go/src/syscall/js/js.go:143 +0x7 wasm_exec.js:59:6
main.main.func1(0xc01e058, 0x1, 0x1) wasm_exec.js:59:6
	$GOPATH/src/github.com/johanbrandhorst/wasm-experiments/bug/main.go:15 +0x4 wasm_exec.js:59:6
syscall/js/callback.callbackLoop() wasm_exec.js:59:6
	$GOPATH/src/github.com/neelance/go/src/syscall/js/callback/callback.go:77 +0x8 wasm_exec.js:59:6
created by syscall/js/callback.init.0 wasm_exec.js:59:6
	$GOPATH/src/github.com/neelance/go/src/syscall/js/callback/callback.go:50 +0x2 wasm_exec.js:59:6
exit code: 2 wasm_exec.js:47:6

I've written a minimal example that reproduces the issue:
// +build js,wasm

package main

import (
	"syscall/js"
	"syscall/js/callback"
)

func main() {
	wait := make(chan struct{})
	promise := js.Global.Call("fetch", "https://api.github.com")
	promise.Call("then", callback.New(func(args []js.Value) {
		response := args[0]
		b := response.Get("body")
                r := b.Call("getReader") // <-- Panic here
		r.Call("read")
		close(wait)
	}).Value)
	<-wait
}

This is happening for me on Firefox 61b4.
Example source: https://github.com/johanbrandhorst/wasm-experiments/blob/master/bug/main.go

Did you check if the same functionality in JavaScript works?
Does that version of Firefox support streams API by now? https://caniuse.com/#search=ReadableStream Last time I checked (some time ago), it didn’t. Have you tried it in Chrome or other browsers?
Call is documented to panic if the method doesn’t exist. Can you try checking it’s not the case?
 b := response.Get("body")
+if b == js.Undefined || b == js.Null {
+    // handle no body
+}
+if gr := b.Get("getReader"); gr == js.Undefined || gr == js.Null {
+    // handle no getReader
+}
 r := b.Call("getReader")

Yeah, just checked latest Firefox Nightly, and Streams API is simply not supported (with default settings). Compare Firefox Nightly (62.0a1):

Versus stable Chrome (66.0.3359.139):

@shurcooL ah of course! Can't believe I didn't think of that. Good thinking again!

I'll leave this open for @neelance to decide whether something should or should not be done.

For other Firefox users; I turned this on by toggling dom.streams.enabled and javascript.options.streams prefs in about:config.


[BUG] Some Text Not Showing as Should

Describe the bug
When pressing the fire button, at the bottom "Clear All Tabs..." appears but the "Close" part does not appear.
Also on certain websites bits of text does not appear, for example on dominos the amount in the basket doesn't appear. I don't know whether these are related but this is what happens.
Thank you
How to Reproduce
This happens whenever the app is opened
Expected behavior
Close at the bottom missing but should appear
Environment
- DDG App Version:5.94.3
- Device:Pixel 5
- OS:GrapheneOS

Thank you for reporting that issue. We already fixed it, and it's available in our latest release. Please update your app and that bug should be gone. 🦆


USB gamepad

i Try it at https://cloudretro.io/
usb gamepad work in normal screen but automatic config keys and lag controls
not remap, not work on full screen

@discordfar
If I understood you correctly, gamepad bindings do not work in the fullscreen mode?
Could you clarify what is lag controls?
I'll try to look at this problem when I have time.

@sergystepanov
Exactly, usb gamepad not working in fullscreen mode
and lag, delay on d-pad

Ah, I see.
The fullscreen stuff is probably a bug. Will look and fix later.
Button remap is not supported for controllers atm and just hardcoded here https://github.com/giongto35/cloud-game/blob/master/web/js/input/joystick.js#L98.
And about d-pad delay. Do you mean it only lags on gamepad and does not on the keyboard controls? Even now?
Otherwise cloudretro.io may be slow with some games, and there is a bug that I'm currently trying to fix which causes severe slowdowns on cloudretro.io.

d-pad delay on usb gamepad
ty nan


Add SonarCloud

Use https://sonarcloud.io during CI to prepare and push the analysis.
This tool will give us further information about code quality, bugs, vulnerabilities and history reports.
@amiorin @mithmatt

@pmbrull Thanks for this. I created the organization in SonarCloud https://sonarcloud.io/project/configuration?id=open-metadata_OpenMetadata. You should've access too. But post that I need some help on setting this up.

Yay, I can indeed access it, and the integration with git looks alright!
What we could do as follow-up steps is:

merge the PR to see the status on the main branch (that should update the main dashboard)
run the sonar job after the tests (we could even try to set up a project for the backend and another for the ingestion)
iterate on the pom and sonar properties to pass the coverage information

But looks like main ingredients are done, so thanks a lot!

Re removing the CI sonar pipeline: It is currently working because by default the Sonar + Git integration is configured to run the analysis automatically for us. This can be OK for some time, but we will be missing all coverage related information.
A more generic and complete process would be:
Run mvn build + tests, storing junit.xml and coverage info in the agent
Configure sonar.properties pointing to those paths
Run the sonar analysis directly in the CI, which will have all the project info
Push the results to SonarCloud

@pmbrull I think we are running into issues where PRs coming from contributors the build is not running for some reason
let me know which way you prefer and we can add that

@pmbrull I think we are running into issues where PRs coming from contributors the build is not running for some reason let me know which way you prefer and we can add that

Hi @harshach, is it regarding https://github.com/open-metadata/OpenMetadata/issues/1908? I can take a look. Having the token in the secrets and passing that should be enough 🤔

@pmbrull I think we are running into issues where PRs coming from contributors the build is not running for some reason let me know which way you prefer and we can add that

Hi @harshach, is it regarding #1908? I can take a look this afternoon. Having the token in the secrets and passing that should be enough 🤔

Sonar coverage report from mvn was failing due to authorization issues.
#1908 has the snippet of logs I captured.
I think the token works for some cases -- I presume it works for collaborators/members of organization but not contributors -- I haven't configured my hypothesis yet. Stopped investigating here to look into other issues earlier today.

@pmbrull I think we are running into issues where PRs coming from contributors the build is not running for some reason let me know which way you prefer and we can add that

Hi @harshach, is it regarding #1908? I can take a look this afternoon. Having the token in the secrets and passing that should be enough 🤔

Sonar coverage report from mvn was failing due to authorization issues. #1908 has the snippet of logs I captured.
I think the token works for some cases -- I presume it works for collaborators/members of organization but not contributors -- I haven't confirmed my hypothesis yet. Stopped investigating here to look into other issues earlier today.

From my past experience with sonar, the usual security process is to have a "service account" (in this case I assume it is harsha's) creating the Token and storing it. Then, any process should be able to pick it up and run the analysis. As the auth happens with the token, it is as if everyone would be the same service account.
I cannot see the settings of the org, but we could take a look together @harshach


Add unit tests for the MessageFormatter class

Relates-To: OLPEDGE-1237
Signed-off-by: Kirill Zhuchkov<EMAIL_ADDRESS>

Please, add more details into description of the PR and commit message (according to our commit message template)

@borzun, what do you suggest adding extra that is not mentioned in the subject?


Disable features of markdown-it on import

Hi,
Thanks for this awesome markdown plugin for vue-js.
Is there a way to disable on import some of the markdown features?
Because right, I don't use neither TOC nor Katex, and those ones depend on:
for TOC: uslug + unorm = 50kb + 36kb = 86kb (gzipped)
for katex: katex = 30kb (gzipped)
So disabling those two features on import, will save 116kb, that is 40% of the size of my app.
Thanks.

It's indeed a question I also have considered before.
I have been trying to solve this problem, but there is no viable solution until now.
I will continue to work hard fix it ~

I noticed this same issue, any updates or workarounds?


Add explicit encoding in title print to fix crash

For issue #3

Thanks. Will clean up those print statements as well.


Computer Setup Script

Can we revisit that app that I wrote and get it cleaned up and sussed out so that we can remove 90% of this complexity?

https://github.com/codefellows/computer-setup

Let's discuss this  next week


where is the sharding-transaction-spring-boot-starter module?

Hi, guys. I got shardingsphere and shardingsphere exmaples from github. the version is 4.0.0.RC1. But when I ran sharding-exmaple-proxy module, I found it can't download  sharding-transaction-spring-boot-starter 4.0.0.RC1 module. However, I didn't find this model in shardingsphere project. Could u give any suggestion? thank you.

please see https://github.com/sharding-sphere/shardingsphere-spi-impl

please see https://github.com/sharding-sphere/shardingsphere-spi-impl

thanks, cherry. I just wonder why not put it in the incubator-shardingsphere repository.

we'd like to move it after sharding-transaction-spring-boot is statable. currently id depends on hibernate library for integrating with Sharding-proxy of jpa, we're trying to provide a spi to make it light enough.

we'd like to move it after sharding-transaction-spring-boot is statable. currently it depends on hibernate library for integrating with Sharding-proxy of jpa, we're trying to provide a spi to make it light enough.

got it. thanks, cherry.

Can you close the issue if problem is resolved?


Fix agent icon for messages and header

Closes: https://github.com/WideChat/Rocket.Chat/issues/1177

@bhardwajaditya this works great!  I tested the two tab scenario as well and saw no issues.  Thanks.  @Shailesh351 can you review please?

great catch...  @Shailesh351 no, that is not expected.  Thanks.

@Shailesh351 @bhardwajaditya I will also test this....  but Shailesh, are you maybe seeing the WebSocket vs. RESt issue that was meant to be fixed in the other PR?  https://github.com/WideChat/Rocket.Chat.Livechat/pull/150
@bhardwajaditya is this PR currently up to date with that fix?

I tested and it looks good to me.....  all working as designed.


Prototype pollution attack

Version: 2.8.0
Platform: Node v12.3.0
Description: Proof of concept: https://github.com/mostafa/js-pp-poc

Thank you for pointing this out! The behavior is caused by converting arguments to strings needs to invoke #toString() on each argument.
For now, however, I couldn't think of any way a hacker can take advantage of this behavior without having the write permission to the code (simply JSON.parse() won't get an object with a function value property, so it's impossible for hackers to construct malicious strings as input for your application that can be parsed into objects with toString() property).
Did I miss anything?

But you can still keep them away by just disabling any overridden function from the __proto__.

@mostafa I got your point. However, there are many ways to achieve this behavior without __proto__. For example:
class A {
  toString() {
    return 'hi'
  }
}

And both __proto__ and the usage above are pretty normal that we've been used for years and they shouldn't be forbidden.
Since #toString() will be invoked every time when String() is called, and String(), developers take responsibility for their code. They shouldn't delete files in #toString(), just like they shouldn't delete files in any other places.
Given that, I'm closing this issue for now. Anyway, Thanks for reporting this. We take security issues very serious, so feel free to let me know if there are other issues.


Add types and import windows-process-tree properly (via import)

@bpasero I copied what's done with windows-foreground-love as the module is windows only, is there a better way of doing this when the module doesn't get downloaded for non-Windows?

@Tyriar true, we have more places where we follow this ugly pattern.
I was referring to this pattern (code):

Sure I can try using a dynamic import like how vscode-xterm is being loaded, should work fine 👍


Watersettings are missing

Hi,
i use your integration and i´m getting all the informations as described but the water temp settings are missing.
I´m on a Elco Aerotop Split with the Ariston Mini Gateway. In the app and on the ariston homepage i can set the watertemp.
what are i´m doing wrong?
Thanks for any help

I still cannot see the water settings


Resolves #1083 - add hemisphere and spot lights

spot lights are a little problematic so left them out of the presets list

lgtm


added path to JRE 8

I think there's a better way to get a path the JRE, but I don't know one at the moment (perhaps a regular expression). I came across this error after downloading the latest JRE. Hope this helps someone else who might run into this same problem.

Scout-App 2 (2016) no longer relies on Java. Closing this PR. Thank you for your fix though. If we had instructions on how to set up the development environment for Scout-App 1, I would have been happy to merge this in. But unfortunately we have no means to do a new build of the 2012 app. If you are interested in pursuing updating the 2012 version of the app further, please let me know.


As of Side Menu, transition to the SecondView?

As of Side Menu, component react-native-side-menu, to make the transition to the SecondView?
import SecondView from './secondview'
export default class Menu extends Component {
  render () {
    return (
      <ScrollView scrollsToTop={false} style={styles.menu}>
        <Text style={styles.name}>Game</Text>
        <Text
          onPress={() => this.props.onItemSelected('OneView')}
          style={styles.item}>
          Submenu1
        </Text>
        <Text
          onPress={() => this.props.onItemSelected('SecondView')}
          style={styles.item}>
          Submenu2
        </Text>
      </ScrollView>
    )
  }
}

Hi @gHashTag, could you be so kind to rephrase the question?

react-native-router-flux :)

I think you're asking for an example here. I'm currently out of time to make it. Probably, somebody from the community would like to pick it up

@gHashTag news?
https://github.com/react-native-community/react-native-side-menu/issues/301

@rochapablo
Thanks
Now working on this  https://github.com/react-community/react-navigation/


[modify] translate tool part : support non ajax part

Coverage: 82.998% (-0.003%) from 83.001% when pulling 430690524aa0c549aed1294df9c5e40e6fb4840c on fix-translate-tool-part into fa6e637b0523868cf7f5228a684199ff7c6a5fed on master.


Dropdown Menu does not close after outside click

Describe the bug
Dropdown Menu doesn't close when clicking outside of the menu.
To Reproduce
Steps to reproduce the behavior:
Go to https://flowbite-react.com/dropdown
Click on any Dropdown Menu
Click outside of the Menu
Note that Menu isn't closed after the click
Expected behavior
The Menu closes after the click outside of the menu, see the original flowbite dropdown menu https://flowbite.com/docs/components/dropdown/
System information:
Device: Macbook Pro
OS: macOS Ventura 13.0.1
Browser: Chrome
Version: 108.0.5359.124

It looks like the issue only happens in the first example if you click on some dropdown item before clicking outside it. I recorded a video to demonstrate it, and I can also confirm that it doesn't seem to be browser-related.
https://user-images.githubusercontent.com/191027/211885837-72fe0953-c1ce-45ca-8449-7b5064a58f3f.mov

Same problem, next js flowbite react

Any solution?

Any ideas to fix the problem?

Nope. But if someone wants to investigate and submit a PR, it would be super welcome.

Hi, I would like to work on this issue.

Solved by #840


Error compiling with rwpi relocation model.

For research purpose, I'm trying to build an image for my cortex-m4 microcontroller with rwpi relocation model. However, during linking stage, lld throws me the error:
rust-lld: error: SBREL relocation to __sbss without static base

Below is an easy way to reproduce this error. This follows the tutorial in The Embedded Rust Book.

cargo install cargo-generate to install an handy tool.
cargo generate --git https://github.com/rust-embedded/cortex-m-quickstart to download the example code.
cd into the cloned directory. Modify .cargo/config. Add "-C", "relocation-model=rwpi" to rustflags.
Run cargo build.

The example code in main.rs uses the cortex-m-rt crate, which during compile time will generate a link script for the linker. The generated link script can be found at ./target/thumbv7m-none-eabi/debug/build/cortex-m-rt-xxxxxxxxxxxxxxxx/out/link.x. I suppose that some information is missing for the linker. What should I do to resolve the error?
The same question is asked on Stackoverflow here.

Unfortunately rwpi is not fully supported by Rust on ARM at the moment. It turns out to be quite complicated; ARM contributed support to LLVM a while back of which some was merged but I don't believe anything has made it into Rust yet. If I remember correctly, I think anything static or any vtables won't work because they need to be moved into sdata instead of sbss and relocated correctly, but are not. There was some earlier discussion of this on the rust-embedded Matrix chat here too.
It would be nice to have, but right now it's not something we can do anything about in this crate. If you find out anything more, please update this thread!

I successfully built and ran an OS binary image with rwpi. The code is here: https://github.com/Acciente717/mini-cortex-m4-os
Most of the code in boot.rs is copied from cortex-m-rt. I made some hack to the Reset() function to get it compile. The key to resolve this problem is to find out a way to read the linker script defined symbols.
Although the correct way of using, e.g., the __sbss symbol is to first declare it in the Rust source file and then take the address of it, it doesn't compile in this way. Instead, I tried using inline assembly
unsafe extern "C" fn Reset() -> ! {
    extern "C" {
        // These symbols come from `link.x`
        static mut __sbss: u32;
        static mut __ebss: u32;
        static mut __sdata: u32;
        static mut __edata: u32;
        static __sidata: u32;
    }

    asm!(
        "ldr r9, ={sdata}",   // load static base
        "ldr r0, ={sbss}",
        "ldr r1, ={ebss}",
        "bl  {memzero}",      // zero out bss section
        "ldr r0, ={sdata}",
        "ldr r1, ={edata}",
        "ldr r2, ={sidata}",
        "bl  {memcopy}",      // initialize data section in RAM
        "bl  {main}",         // jump to main
        sbss = sym __sbss,
        ebss = sym __ebss,
        sdata = sym __sdata,
        edata = sym __edata,
        sidata = sym __sidata,
        memzero = sym memzero,
        memcopy = sym memcopy,
        main = sym main
    );

    loop {}
}

Magically, this compiles. From the disassembly, we can see that these symbols get allocated in ROM(flash).
08000400 <Reset>:
 8000400:       b580            push    {r7, lr}
 8000402:       466f            mov     r7, sp
 8000404:       f8df 9018       ldr.w   r9, [pc, #24]   ; 8000420 <_stext+0x20>
 8000408:       4806            ldr     r0, [pc, #24]   ; (8000424 <_stext+0x24>)
 800040a:       4907            ldr     r1, [pc, #28]   ; (8000428 <_stext+0x28>)
 800040c:       f000 f8a5       bl      800055a <_ZN17mini_cortex_m4_os4boot7memzero17h719c1bc8e3de9fd9E>
 8000410:       4806            ldr     r0, [pc, #24]   ; (800042c <_stext+0x2c>)
 8000412:       4907            ldr     r1, [pc, #28]   ; (8000430 <_stext+0x30>)
 8000414:       4a07            ldr     r2, [pc, #28]   ; (8000434 <_stext+0x34>)
 8000416:       f000 f8b5       bl      8000584 <_ZN17mini_cortex_m4_os4boot7memcopy17h28a08465ccbd97e2E>
 800041a:       f000 fa85       bl      8000928 <_ZN17mini_cortex_m4_os4main17ha05f5ee7bef82e53E>
 800041e:       e7fe            b.n     800041e <Reset+0x1e>
 8000420:       20000000        .word   0x20000000  ; this is __sdata
 8000424:       20000004        .word   0x20000004  ; this is __sbss
 8000428:       20000130        .word   0x20000130  ; this is __ebss
 800042c:       20000000        .word   0x20000000  ; this is __sdata again
 8000430:       20000004        .word   0x20000004  ; this is __edata
 8000434:       08004da4        .word   0x08004da4  ; this is __sidata

I don't know exactly why it works. It seems that we should always take the address of a compiler defined symbol, which doesn't compile, but should not read it as a variable, which does compile. Wierd. Any explanation on this is greatly appreciated.


Move giles to testing

Since giles isn't part of an application per se, but rather a way to simulate an input source and an output destination, it should move to testing.
Perhaps rename giles-sender and giles-receiver to testing/sender and testing/receiver (perhaps to go along with Fallor as testing/decoder).
cc @SeanTAllen @jtfmumm , @JONBRWN, this will probably impact Wallaroo-Documentation.

@nisanharamati @SeanTAllen is this still something we need to do or can we close this issue? Right now giles is an integral part of our examples and documentation, so I don't think we could characterize it as being just for testing.

@aturley agreed. we can close for now.


Publishing!

Hey @aaronpowell, caught your comment over here: https://github.com/apollographql/apollo-server/issues/6032#issuecomment-1373199073.
Sorry for the delay.
I sent you an invite to the NPM org and added you to the azure-functions team. You should be able to generate an automation token and add it to the repository secrets here: https://github.com/apollo-server-integrations/apollo-server-integration-azure-functions/settings/secrets/actions (under NPM_TOKEN). This will allow changesets to start publishing to NPM.
Bug me here or send me an email if you have any questions, and let me know when you publish!

Thanks, I've joined and will see about publishing soon

@trevor-scheer - I just went to setup publishing but I'm not an admin of the repo, so I can't add the secret to GitHub Actions. Can you grant that permission to me?

@aaronpowell done!


Complete Overhaul and Rename

Here is my proposal for a complete overhaul and renaming. Please look this over.

New tests are building now. My local testing succeeded after addressing two problems.

The utils helper package for testing used basestring which isn't a type in Python3.
max_file_size was being initially set to a str value of 5 MB and never getting converted to bytes with bitmath.

Per our conversation earlier, I have combined start_from* into start(), and removed the old option for verbose_level since it is now irrelevant. All documentation/unit tests were rewritten to reflect both changes.

Done.


Remove returns dependency

Removes Returns as a dependency. Its still too early in development. And is more suited to be used in an actual application with business logic and not in a package like this.
Does nothing with the existing callable object vs normal functions stuff.
Thats for a different PR and likely to change depending on if we want to support multiple storage types like S3 and others

Codecov Report

Merging #46 (08f5217) into master (e76b01f) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #46   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          183       124   -59
  Branches        10        10
=========================================
- Hits           183       124   -59

Impacted Files
Coverage Δ

storage_bucket/client.py
100.00% <100.00%> (ø)

storage_bucket/create.py
100.00% <100.00%> (ø)

storage_bucket/delete.py
100.00% <100.00%> (ø)

storage_bucket/delete_file.py
100.00% <100.00%> (ø)

storage_bucket/download_file.py
100.00% <100.00%> (ø)

storage_bucket/get.py
100.00% <100.00%> (ø)

storage_bucket/list.py
100.00% <100.00%> (ø)

storage_bucket/list_files.py
100.00% <100.00%> (ø)

storage_bucket/upload_file.py
100.00% <100.00%> (ø)

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 e76b01f...08f5217. Read the comment docs.

@ChameleonTartu will you have time to look at this or should i just merge it?

Yes, I will try to look at it today. It was in my to-do list :-)
On Tue, Nov 2, 2021, 09:30 Borgen @.***> wrote:

@ChameleonTartu https://github.com/ChameleonTartu will you have time to
look at this or should i just merge it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thomasborgen/storage-bucket/pull/46#issuecomment-957210116,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADH5QFYUZBR6IHGM7SNACNLUJ6OTBANCNFSM5GHATPDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Add certificate management for calico and minimal enterprise clusters.

First draft of certificate management

@rene-dekker as discussed, k8s CSR integration for Calico pods should be OSS first and then Enterprise to follow.

@rene-dekker as discussed, k8s CSR integration for Calico pods should be OSS first and then Enterprise to follow.

@rene-dekker You might wanna check the build :
et: pkg/render/typha_test.go:228:80: too few arguments in call to render.Typha

@rene-dekker You might wanna check the build :
et: pkg/render/typha_test.go:228:80: too few arguments in call to render.Typha

merging based on @caseydavenport and @asincu review.
/merge-when-ready delete-branch

merging based on @caseydavenport and @asincu review.
/merge-when-ready delete-branch


Format url

Thanks for contributing to the repository! ❤
Checklist

[ ] No duplicate
[ ] The pull request is not against the Contributing Guidelines
[ ] No CodeQL Error

@2Lost4This you can merge after the checks


tutorials fail

On tutorial stage 1, using py2app as a freezer, the built app will fail to launch because fcntl isn't found.  I have this failure both on OSX 10.10.5 and OSX 10.11.6.

Thanks for reaching out.  Unfortunately this project is no longer actively maintained, so I'm going to move it into archive mode:
https://rfk.id.au/blog/entry/archiving-open-source-projects/


Minor fixes to task

check that min and max are > 0 and max >= min;
use orders_scope in the orders loop;
correct line item totals calculation;
remove duplicate content in docs;
update help link;

 Update "Auto-tag customers within a purchase range"

 Update "Auto-tag customers within a purchase range"


go/importer: GOARCH=386 can't find import: "crypto/tls"

What version of Go are you using (go version)?
go version go1.10.2 linux/amd64

Does this issue reproduce with the latest release?
Yes. Tried it with cf2c2ea89d.
$ cd $HOME && $HOME/go-master/bin/go version
go version devel +cf2c2ea89d Mon Jun 4 17:32:17 2018 +0000 linux/amd64

~ $ GOARCH=386 $HOME/go-master/bin/go run main.go
can't find import: "crypto/tls"

What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/gyuho/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/gyuho/go"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build230277318=/tmp/go-build -gno-record-gcc-switches"

What did you do?
package main

import (
	"fmt"
	"go/importer"
)

func main() {
	_, err := importer.Default().Import("crypto/tls")
	if err != nil {
		fmt.Println(err)
	}
}

$ GOARCH=386 go run main.go
can't find import: "crypto/tls"

What did you expect to see?
No error.
What did you see instead?
$ GOARCH=386 go run main.go
can't find import: "crypto/tls"

I believe that this is working as expected.  The docs for importer.Default say that it returns an Importer for the compiler that built the binary, which in this case is "gc".  The docs for Importer.For say that for "gc" it returns an importer that works on installed packages.  You presumably haven't installed the "crypto/tls" package for 386.
You should either use importer.For("source") or run GOARCH=386 go install crypto/tls.
Closing because I don't think there is anything to fix.  Please comment if you disagree.

@ianlancetaylor Makes sense. Thanks for explanation! Please feel free to close it!

importer.For("source") worked :)


Changing to a new project after successful co-simulation is not able to co-simulate

When you start co-simulation for such a new project you get: Starting simulation: FAILED...

Actually it looks like this behaviour is also caused by being able to select variables that cannot be viewed in the graph. I suggest that it should not at all be possible to select such variables.

I cannot reproduce the first part of this bug. I can run co-sims, open or create new projects and run more co-sims.
What do you mean by "variables that cannot be viewed in the graph"

You can only view variables that are plain numbers in the graph (as far as I understand it), so if you for example for the line-following robot select one of the positions you will get the error I reported. My suggesting is that only variables that are numbers (and thus can be viewed in the graph) can be selected.

@pglvdm , can you confirm if this is still present in the 2.0.0 version?

I can confirm that this seems to be fixed now.

Great. Closing


ALD contract regress on macOS build

** (Mix) Could not compile dependency :plasma_contracts, "cd /Users/distiller/project/apps/omg_eth/../../deps && solc openzeppelin-solidity=openzeppelin_solidity plasma_contracts/plasma_framework/contracts/src/framework/PlasmaFramework.sol plasma_contracts/plasma_framework/contracts/src/vaults/verifiers/EthDepositVerifier.sol plasma_contracts/plasma_framework/contracts/src/vaults/verifiers/Erc20DepositVerifier.sol plasma_contracts/plasma_framework/contracts/src/vaults/EthVault.sol plasma_contracts/plasma_framework/contracts/src/vaults/Erc20Vault.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentStartStandardExit.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentChallengeStandardExit.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentProcessStandardExit.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentStartInFlightExit.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentPiggybackInFlightExit.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentChallengeIFENotCanonical.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentChallengeIFEInputSpent.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentProcessInFlightExit.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/controllers/PaymentChallengeIFEOutputSpent.sol plasma_contracts/plasma_framework/contracts/src/exits/registries/SpendingConditionRegistry.sol plasma_contracts/plasma_framework/contracts/src/exits/registries/OutputGuardHandlerRegistry.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/outputGuardHandlers/PaymentOutputGuardHandler.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/PaymentTransactionStateTransitionVerifier.sol plasma_contracts/plasma_framework/contracts/src/exits/utils/TxFinalizationVerifier.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/PaymentExitGame.sol plasma_contracts/plasma_framework/contracts/src/exits/payment/spendingConditions/PaymentOutputToPaymentTxCondition.sol plasma_contracts/plasma_framework/contracts/mocks/transactions/eip712Libs/PaymentEip712LibMock.sol --overwrite --abi --bin --optimize --optimize-runs 1 -o /Users/distiller/project/apps/omg_eth/../../_build/contracts && cd /Users/distiller/project/apps/omg_eth" command failed. You can recompile this dependency with "mix deps.compile plasma_contracts", update it with "mix deps.update plasma_contracts" or clean it with "mix deps.clean plasma_contracts"

Solved by @unnawut


deletePage() does not update pagesContext properly

deletePage() did not update pagesContext, so page dimensions were off (if they weren't already all the same)
   var doc = new jsPDF( { orientation: 'landscape',
                           format: [ 216, 140 ] } ) ;
    doc.text("some text on the first page", 20, 20);
    doc.addPage('letter', 'p');
    doc.text("some text on the second page", 30, 30);
    doc.deletePage(1);

This worked okay in 1.4.1; broken in current git

Disregard, I screwed up and used the wrong branch.  I will resubmit a clean PR.


Content Suggestion: Lightning Puzzle

Link to Content: https://www.lightningpuzzle.com/
Briefly Describe Content: Solve puzzles and win lightning prizes
Suggested Section: Spend Bitcoin -> Fun & Play

Great idea and implementation!
Merged


update Go documentation link

Problem
Existing link was moved https://github.com/golang/go/wiki/Modules

Solution
Changed to current link
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Infrastructure change (CI configs, etc)
[X] Non-code change (docs, etc)
[ ] None of the above: (explain here)

Test Plan
N/A

Great change! Let's wait until @austin-denoble gets back to merge, since CI is failing due to a missing API key (which is strange b/c it should be all set in GH). Hold tight!

Update: figured it out. The fork made for this request does not contain the necessary CI secrets. Author will open a branch (not a fork) and re-issue this PR.


WIP: Find correspondences across several datasets

This is a work in progress, do not merge.
Things to do:

[ ] The code currently relies on a hard coded list of datasets, and fakes the lexicore interface. This is a temporary way to not be dependent on the timeline for lexicore. Instead, replace by actual lexicore.
[ ] Implement alternatives to genera to find sub-groups in each family
[ ] Use a better cognate detection method
[ ] Maybe implement something to have a coarser sound classification than BIPA

How do I call the code, can you give an example?

Sure, it is pretty similar to what you originally wrote:
cldfbench lexitools.correspondences --model asjp --cutoff 2 --threshold 1 --concepts Holman-2008-40

--model can be "asjp" or "bipa" (this is used to downscale phonemes)
--concepts limits to a list of concepts. Here using Holman-2008-40
--cutoff lets you pick how many times a correspondence must appear to be kept
--threshold is the similarity threshold between pairs of words

This will run on several datasets. To run on a single dataset:
cldfbench lexitools.correspondences --model asjp --cutoff 2 --threshold 1 --concepts Holman-2008-40 --dataset asjp

I think "asjp" is the only case where we may want to run it on a single dataset.

Okay, now the question: "several datasets": what are these datasets, all
those that are installed? or how do you determine them?

As I said above, this is what simulates "lexicore" (the --dataset argument defaults to "lexicore"). I implemented this before lexicore was ready, and needed something which would more or less run on the same set of datasets, and be easily swappable with the real lexicore interface once lexicore is ready. This is not code that is intended to stay, it is merely a work around to make sure the sound correspondence work can go forward as much as possible without waiting for the technical details of lexicore. As soon as lexicore is ready I can very easily swap it in.
The list I have currently is the below, which I got from the google sheet. Some datasets do not install/read properly.
["aaleykusunda", "abrahammonpa", "allenbai",
                        "backstromnorthernpakistan", "bdpa", "beidasinitic",
                        "birchallchapacuran", "bodtkhobwa", "bowernpny", "cals",
                        "castrosui", "castroyi", "chaconarawakan",
                        "chaconbaniwa", "chaconcolumbian", "chenhmongmien",
                        "chindialectsurvey", "clarkkimmun", "dravlex",
                        "dunnaslian", "galuciotupi", "halenepal",
                        "hantganbangime", "housinitic", "hsiuhmongmien",
                        "hubercolumbian", "ivanisuansu", "joophonosemantic",
                        "lieberherrkhobwa", "listcognatebenchmark",
                        "liusinitic", "marrisonnaga", "mcelhanonhuon",
                        "mitterhoferbena", "mortensentangkhulic",
                        "naganorgyalrongic", "northeuralex", "robinsonap",
                        "sagartst", "savelyevturkic", "sohartmannchin", "suntb",
                        "tppsr", "transnewguineaorg", "tryonsolomon",
                        "vanbikkukichin", "walworthpolynesian", "wangbai",
                        "wichmannmixezoquean", "wold", "yanglalo",
                        "zgraggenmadang", "gerarditupi", "polyglottaafricana",
                        "peirosaustroasiatic", "deepadungpalaung", "zhaobai"]

I think, @XachaB, you can also just merge this for now, I'd then later check quietly and provide updates and other suggestions. The current solution you propose for cloning is okay, I'd say.


Enhancing JSON index to provide free text search on string value space

I tried the JSON index support in the latest apache-pinot-0.7.0and observed that I was not able to do a free text search on json value space.
As shown in the below example, I was able to do an equality search as in Q1. But, I was not able to do the text_match kind of search as in Q2.
Table = json_doc_example
Example data with 3 rows:
id_col, json_doc_col
"1234", {"message": "too many retries"}
"1235", {"message": "error sql timeout"}
"1236", {"message": "too large filter"}

Query Q1: returns -> [1236]
select * from json_doc_example JSON_MATCH(json_doc_col, 'message=''too lareg filter''')

Query Q2: returns empty result (was expecting it to return : [1234, 1236])
select * from json_doc_example JSON_MATCH(json_doc_col, 'message=''too''')

Can we add similar text_match support on json value space ? or
is it recommended to use both text index + json index for such use case on that column?

Json index only supports exact match. In order to do text match, you need to use jsonExtractScalar, e.g. select ... where jsonExtractScalar(json_col, '$.message', 'STRING') like 'too.*'. The performance might not be very good because we have to scan and reconstruct the json from the json string. You can add text index on the json string column, but that will treat the json string as regular string. For the example above, extracting message` field as a separate column will give much better performance.

Regexp like is supported with #12568


Why don't brokers store zk nodes under --storage of scheduler?

When I start the scheduler with --storage zk:/kafka-mesos it creates and uses that node. But after I start brokers they create nodes at the root:
/controller
/controller_epoch
/brokers
/admin
/consumers
/config
Am I missing some configuration that would keep these under the --storage node?
[kafak-mesos v<IP_ADDRESS>]

You have to set the --zk flag for this.

The zk flag on scheduler?
--zk                 Kafka zookeeper.connect. Examples:
                      - master:2181
                      - master:2181,master2:2181

I do set that when starting the scheduler, but its the host:port of zookeeper. What does that have to do with the node hierarchy/namespace?

--zk host:port/path

So set the --zk host:port/path on broker add?
$ ./kafka-mesos.sh broker add --zk host:port/path 0
Or do you mean just add the /path the --zk of the scheduler along with --storage ?

Ok, got it:
--zk host:port/path  defines the top level node for the scheduler and brokers
--storage  defines the node under above for just the scheduler
thanks!!


Reading BTNextgen spectra

indices corrected

Jeeh! The first pull request for species :)!
Would you mind checking if the correct indices are used in data.btsettl? There the data is read in a similar way.

Done. It seems correct! The reading is very similar but overall the indices were already swapped :)


[Event Request] Recreate: Table 11400 CBG Statement - ProcessStatementASGenJournal (Dutch localisation)

Hello,
Re: https://github.com/microsoft/ALAppExtensions/issues/3901
This event was marked as "already exists", but when checking BC15.2, it does NOT exist.
Could you please make sure it's reintroduced again?
Thanks,
Peter

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Update movie load progress in intervals rather than on video timeupdate

Load progress should be updated regardless of the timeupdate event, seeing as when the user pauses the video, load progress is halted as well.

This issue was fixed in the 1.4.5 update.


merge from template-browser-ava

package.json

chore(scripts): add npm run lint:docs && npm run lint:tsc (scripts.lint)

.gitignore

chore: add  ()

README.md

docs(README): update from template

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.11%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
913

Relevant Lines:
985

💛  - Coveralls


bruegel ?

I wonder what's the painting - which i find very pretty, and probably a good model for puzzles :)

I think it's by Charles Euphrasie Kuwasseg.
Absolutely. I can totally see this as a jigsaw puzzle 😄

Wonderful painter ! Never heard of him, and it's not easy to find books on him.
Thank you for that :)

No problem! Cheers 🍻


mistake in _cluster_patches

Hi, while looking at the code I have found that in _cluster_patches in kernels.py, the array 'patches' is allocated too small -- (M x patch_length) instead of (M*samples_per_inducing_point x patch_length) -- and then the following loop preserves only the first M samples instead of all of them (the indexing is done in such a way that unfortunately no index out of bound error is emitted). This leads to a commonly displayed error that not enough cluster centers were found. Obviously, also the clusters are not initialized correctly and who knows what is the consequence for the training...
Anyway, a great paper and a piece of code! Thanks a lot for sharing it!

Good call. Just pushed a fix https://github.com/kekeblom/DeepCGP/commit/2247aa6f3d9ce696606930413d0a06ccce9cad70 for this issue.
It seems on mnist this warning still sometimes appears when using a lot of inducing points (e.g. 384) even when a lot more patches than inducing points are sampled.

Btw, why 384? I haven't been able to find any formula which would give me this number. Is there any reason for this particular value?

It's a multiple of 32 which is the amount of threads on one cuda warp. The computational burden will increase as the number of inducing points increase so it's a trade-off between cost and accuracy.
You can set it to whatever value you want.


Add custom data types

Introduce the ability to declare custom data types with the directive %type.
Under the hood, it will work as C struct; it will allocate space in memory for all the fields and return the pointer to the structure (the first field).
%type MyType {field1, field2, field3}

Custom data types can be simulated using memory with word keyword.
See struct.casm for an example.


Stop stripping and LTO

Stop stripping:
Stripping symbols here is bad, because it makes the binary completely opaque and undebbuggable, should something ever go wrong. The binary size benefit is very minor, this program is supposed to run on desktop computers with tons of disk space. The tradeoff is bad.
Stop LTO:
The same binary size non-concerns as stripping apply. Also, speed basically doesn't matter here. Meanwhile, we want this program to be cargo install-able, so compile times matter. Again, the tradeoff is bad.

If anyone cares about sacrificing things for 4 megabytes like in #157 they can always manually override the setting for their builds, this is just the default.

@oli-obk you have approved the other pr


feat(contributor): display more author data in a table

Main commit

Close #37
Based on forked repo used across the SaltStack Formulas organisation, e.g.:

https://github.com/saltstack-formulas/template-formula/blob/master/AUTHORS.md

Extra commit: style(contributor): display descending in emphasised text
Only a suggestion, I can remove it from this PR if it isn't appropriate.

Extra commit: refactor(helper): update Footer to reformat layout

Prevent issue with heading appearing in "Table of Contents" when automatically converting to display on "Read the Docs" (or similar)
Other minor reformatting

Again, this commit can be removed if not appropriate.  We have been testing automatically converting this file to Read the Docs and removing the heading in this commit improved that process.  For example (this may not be a permanent link):

https://template-formula.readthedocs.io/en/latest/AUTHORS.html

You're welcome.


system_fingerprint is None

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug
Per the documentation here, the OpenAI API should return a system_fingerprint. However, when calling any model that is not gpt-3.5-turbo-1106 or gpt-4-1106-preview, the system_fingerprint is always None.
The link above doesn't mention any model requirement.
To Reproduce
copy and paste notebook here
change this line to an older model:
GPT_MODEL = "gpt-3.5-turbo-1106"
For example:
GPT_MODEL = "gpt-3.5-turbo-0613"
the system_fingerprint returned is None
Code snippets
No response
OS
Ubuntu
Python version
Python v3.10
Library version
openai v1.6.1

Note this is the same issue as reported here, but I wasn't able to re-open the issue.
I am reporting again because the API is not behaving as documented in the API reference. The API reference has no beta flags on it.

Thank you.
This repo is for SDK issues, not API or API documentation issues. I'll raise this again with the API team, but in the future, https://github.com/openai/openai-openapi would be a better place for this kind of thing.

for the record, elisa-abridge reported here: https://github.com/openai/openai-openapi/issues/167


Reduce windowsservercore image size

This changes reduce the mongo image size for all windowsservercore images.

Remove second RUN command to set the PATH, saves about 30-50 MB
Remove all *.pdb files in mongodb\bin folder, saves about 240 MB
Remove the MSI from install cache, saves about 100 MB

I did some research back in February commented in https://github.com/StefanScherer/dockerfiles-windows/issues/1 where you can find more details.

A docker pull then shows only about 52 MB instead of about 300 MB in its progress bars.

This is really neat :smile: :+1: :heart:

Have you seen the next Windows update layer for eg. microsoft/windowsservercore? Download size is appr. 880MByte. Needs some optimizations as well 😄


Content duplication

Click the page number button from the first page to the second page, and the content is repeated, for example, the last three items on the first page are also displayed on the second page.
page 1

page 2

Fixed  pagination calculation logic error


Don't perform conversion for the format itself

Idea below:
...
doc.markdown = 'some markdown here...'
doc.markdown # should probably show 'some markdown here...' directly. instead it tries to perform the conversion via pandoc!

I think that's exactly what it should do :)


Can you share the machine configuration for running this project?

I have run this project with 32 GB GPU Configuration machine, so it is taking 7 min to produce output.
I am looking forward to reduce this time. How much GPU will reduce the time from 7 min to 2 min?

i also feel the speed is too slow. a video of 13s length need 520s to produce!
my hardware is 4090 24G

@byixi2023 I am having trouble getting it running on my 4090, by any chance, could you share the installation steps you took?

Setting Up Rerender_A_Video on Windows: A Comprehensive Guide

from pytorch_lightning.utilities.distributed import rank_zero_only
C:\Users\bryan\Rerender_A_Video\deps\ControlNet\ldm\models\diffusion\ddpm.py

https://github.com/williamyang1991/Rerender_A_Video
1. Pre-requisites:
Ensure you have a Windows machine with an NVIDIA GPU that supports CUDA.
2. Initial Setup:

Python:

Download and install Python 3.11.5 (64-bit version).
Ensure the Python and Pip paths are correctly set in your environment variables.
Confirm your Python version and architecture with:python --version
python -c "import platform; print(platform.architecture()[0])"

CUDA:

Download and install CUDA 12.2. This is necessary for GPU support with PyTorch.

Git:

Download and install Git for Windows.

Visual Studio:

Download and install Visual Studio 2022. Ensure you include the "Desktop development with C++" workload during installation to get the necessary build tools and Windows SDK.

GitHub SSH Setup:

Set up an SSH key and link it to your GitHub account using this guide.

3. Cloning the Repository:
Navigate to the directory where you want to clone the repository and run:
git clone git@github.com:williamyang1991/Rerender_A_Video.git --recursive
cd Rerender_A_Video

4. Setting Up the Python Environment:

Install the necessary Python libraries listed in the requirements.txt file:

pip install -r requirements.txt

5. Compiling Dependencies:
Run the installation script to build and compile necessary components:
python install.py

This step will download the required models into the ./models directory.
6. Downloading Additional Models:
If the project requires additional .safetensors models, download them as per the project's instructions and place them in the models directory.
7. Configuring the Model:
Update the JSON config file (e.g., real2sculpture.json) to point to the correct model checkpoint in the models directory.
8. Running the Rerender Script:
Before you proceed, ensure that you have the right dependencies. There are known compatibility issues:
Note: Numba requires NumPy version 1.24 or less. If you encounter an error related to this, resolve it by downgrading NumPy:
pip install numpy==1.24
Once all dependencies are set:

Navigate to the project's directory.
Execute the following command:

python rerender.py --cfg config/real2sculpture.json
This will start the rerendering process using the configuration provided in config/real2sculpture.json.
9. Troubleshooting:

Python Architecture Issues:

Ensure you're using a 64-bit version of Python, as 32-bit versions can cause compatibility issues.

Rust and Tokenizers Library Issue:

If encountering an error related to Rust and mismatched architectures, set up the correct Rust target with rustup:rustup target add x86_64-pc-windows-msvc

Visual Studio Build Tools:

If you encounter errors related to missing link.exe, ensure your PATH environment variable includes the path to the Visual Studio build tools.

CUDA-Related Issues:

Make sure your NVIDIA drivers are up-to-date.
Ensure the PyTorch version is compatible with your installed CUDA version.

PIP and Python Environment:

If pip is not recognized, you might have to reinstall it or adjust your PATH.
Use ensurepip if pip isn't installed:python -m ensurepip --default-pip

Summary:

Initial Setup: Cloning the repository and getting the basic tools ready.
Python Environment: Ensured the right Python version (64-bit) and architecture.
Python Libraries: Installed required libraries using pip.
Rust & Tokenizers Issue: Addressed architecture mismatch.
Visual Studio Build Tools: Addressed missing link.exe and ensured the necessary tools were in the PATH.
Compiling Dependencies: Ran the provided installation script.
PyTorch & CUDA: Addressed CUDA availability in PyTorch.
Downloading Additional Models: Downloaded and placed additional model checkpoints in the appropriate folder.
Configuring & Running the Model: Updated the JSON config and ran the rerender script.
Troubleshooting:

Addressed Python architecture issues.
Fixed Rust and tokenizers library issue.
Ensured the correct PATH for Visual Studio Build Tools.
Handled pip-related issues.

Using Additional Models with Rerender_A_Video:
1. Download Additional Models:

Acquire the required model checkpoints. For our journey, the model realisticVisionV51_v20Novae.safetensors was essential.
You can typically find these models on the project's GitHub page or associated links. Sometimes, they're hosted on third-party websites like CivitAI.

2. Place Models in the Correct Directory:

Once downloaded, move the model checkpoints to the ./models/ directory of the Rerender_A_Video project.

3. Configure the Model for Use:

Navigate to the configuration files (typically JSON files) in the project.
Update the JSON config to point to the new model. For instance:{
  "sd_model": "models/realisticVisionV51_v20Novae.safetensors",
  ...
}

Adjust any other relevant parameters in the config as needed.

4. Run the Rerender Script with the New Model:

Once everything is set up, navigate to the Rerender_A_Video project directory in your terminal.
Use the rerender.py script with the updated config to run

the model:
bash      python rerender.py --cfg config/your_updated_config.json
5. Review the Output:

After the script completes, review the output video or images.
Adjust parameters in the config and re-run if necessary to get the desired results.

Remember, using deep learning models can be an iterative process. Sometimes, you may need to adjust parameters, prompts, or even use different models to achieve the desired output.
Notes & Troubleshooting:
Essential Software Components:

Python: Use Python 3.11.5 (64-bit version). Ensure the Python and Pip paths are correctly set in your environment variables.
CUDA: Download and install CUDA 12.2 for GPU support with PyTorch.
Git: Download and install Git for Windows.
Visual Studio: Download and install Visual Studio 2022. Ensure you include the "Desktop development with C++" workload during installation to get the necessary build tools and Windows SDK.

SSH Setup for GitHub:

Check for existing SSH keys:dir %USERPROFILE%\.ssh\

If files named id_rsa.pub or id_ed25519.pub are present, you already have an SSH key.
If you don't see the SSH key files, generate an SSH key and link it to your GitHub account.

Python Environment Setup:

If pip isn't recognized, you might need to reinstall or adjust your PATH. Alternatively, use ensurepip:python -m ensurepip --default-pip

PyTorch & CUDA Compatibility:

PyTorch and CUDA must have compatible versions.
Install a PyTorch version without specifying the CUDA version:pip install torch torchvision torchaudio

Check PyTorch's CUDA version:python -c "import torch; print(torch.version.cuda)"

Visual Studio Build Tools:

Install Visual Studio Build Tools. During installation, select the "Desktop development with C++" workload and the "Windows 10/11 SDK" component.
Ensure the Visual Studio Build Tools' path is included in your system's PATH.

Rust Setup:

Some Python packages have components written in Rust. If there are issues with Rust, ensure you're using the stable Rust toolchain:rustup default stable

Compiling Issues & Solutions:

If facing issues related to link.exe, ensure your PATH environment variable includes the path to the Visual Studio build tools.
In case of issues with Rust and mismatched architectures, set up the correct Rust target:rustup target add x86_64-pc-windows-msvc

Checking GPU Status:

Use NVIDIA's System Management Interface (SMI) to check the status of your GPU:nvidia-smi

General Tips:

Always ensure you're using the appropriate software architecture (64-bit is recommended for this setup).
Backup essential data before starting the setup, especially when making significant changes.
Check for library updates regularly and ensure all dependencies are up-to-date.
If encountering issues, consult the project's official documentation and community forums for assistance.

System Configuration and Versions

Python Environment:

Python Version: Python 3.11.5
Note: Ensure you're using a 64-bit version of Python. You can confirm this with:
python --version
python -c "import platform; print(platform.architecture()[0])"

CUDA & GPU Configuration:

CUDA Version: 11.8 (As detected by nvcc)

PyTorch's CUDA Version: 2.0.1+cu118

NVIDIA Driver Version: 537.34

GPU Model: NVIDIA GeForce GTX 1080
Note: It's crucial that the CUDA version in PyTorch (torch.version.cuda) matches the system's CUDA version. To check GPU status, use nvidia-smi.

Git Configuration:

Git Version: git version 2.42.0.windows.2
Note: Ensure you've set up an SSH key and linked it to your GitHub account for secure and password-less interactions with GitHub repositories.

Rust Configuration:

Rust Version: rustc 1.72.0
Note: Some Python packages might be written in Rust, requiring Rust tools for compilation. Ensure you're using the stable Rust toolchain (rustup default stable).

Python Libraries:

PyTorch Version: 2.0.1+cu118

Tokenizers Version: 0.12.1

Transformers Version: 4.19.2

(And many others as listed in versions.txt)
Note: Ensure that library versions are compatible with your project. PyTorch's CUDA version should match the system's CUDA version.

Additional Notes & Troubleshooting:

Visual Studio & Build Tools: Ensure you've installed Visual Studio with the "Desktop development with C++" workload. The absence or misconfiguration of this toolchain can hinder the compilation of various projects.
PATH Considerations: Some errors might arise if certain executables (like link.exe from MSVC) aren't in the system's PATH. Ensure directories for tools are added to your system's PATH variable.
Python Package Managers: Always ensure pip is up to date. If a particular Python package isn't installing correctly, it's helpful to check for updates or try installing it separately.
SSH Key Authentication: If cloning repositories using SSH URLs, it's essential to have the correct SSH key added to your GitHub account.

C:\Users\bryan\Rerender_A_Video>python -m xformers.info output

A matching Triton is not available, some optimizations will not be enabled.
Error caught was: No module named 'triton'
xFormers 0.0.16rc425
memory_efficient_attention.cutlassF:               available
memory_efficient_attention.cutlassB:               available
memory_efficient_attention.flshattF:               available
memory_efficient_attention.flshattB:               available
memory_efficient_attention.smallkF:                available
memory_efficient_attention.smallkB:                available
memory_efficient_attention.tritonflashattF:        unavailable
memory_efficient_attention.tritonflashattB:        unavailable
swiglu.fused.p.cpp:                                available
is_triton_available:                               False
is_functorch_available:                            False
pytorch.version:                                   2.0.1+cu118
pytorch.cuda:                                      available
gpu.compute_capability:                            6.1
gpu.name:                                          NVIDIA GeForce GTX 1080
build.info:                                        available
build.cuda_version:                                1108
build.python_version:                              3.11.5
build.torch_version:                               2.0.1+cu118
build.env.TORCH_CUDA_ARCH_LIST:                    None
build.env.XFORMERS_BUILD_TYPE:                     None
build.env.XFORMERS_ENABLE_DEBUG_ASSERTIONS:        None
build.env.NVCC_FLAGS:                              None
build.env.XFORMERS_PACKAGE_FROM:                   None
source.privacy:                                    open source

Hello @BryanHarrisScripts
I dont understand your comment, how is this related to video retalking whereas its installed withing a SEPARATE conda environement no??? What did you mean by all these explanations?

i also feel the speed is too slow. a video of 13s length need 520s to produce! my hardware is 4090 24G

@KeystoneScience  Hey keystone, please please take the time to answer me, did you find how to make it work faster on a 4090? Please tell me.

**byixi2023 ** c

Hello @pr-agati  please please telle me, did you find how to make it work faster on your card?? How to make it use GPU ?

Glad to see you, I was just on your profile then youtube channel earlier and was like: he did not make a video since a 3 months (or weeks dont remmeber) and he should not stop haha.
Ok my question is how much faster? I just did a 10 minutes video in 21 minutes (step6) + the others smaller steps.
Although I am using a powerful card. But I think it's related to RAM and not to GPU look:
(I have another question under the image please look at it)

Question 2: If you installa  new version of cuda and torch etc inside your conda env, does that require to RE RUN install requiremen line?
Or is it just : update pytorch -> you can immediately start using retalker again?
Thanks
I am really frustrated with this. Also, did you use others tools?

Not sure how to see that But I am sure there is on windows a tool that would do that, but how could it help me?  I mean the GPU is like 0 usage ..
also.. I noticed that amd cards were very slow for some AI types, maybe linux is also slowing you down!
Yeah please report any update you find.
Here is the requirement file:
addict
future
librosa==0.7.0
lmdb
numba==0.48
numpy
opencv-contrib-python>=<IP_ADDRESS>
opencv-python
Pillow
pyyaml
requests
scikit-image
scipy
tb-nightly
torch>=1.3
torchvision
tqdm
yapf

What are all the lines you would recommand commenting and instead installing myself?
Yeah it's so tiring the install try delere retry.. I have 0 energy for that.
lastly, did you use other tools? I am trying lip2sync HD but Got stuck with installation (some problem about (ERROR: Failed building wheel for llvmlite)), wonder if you tried other stuff?

Ok @KeystoneScience  I might had that wrong, I don't think it was 10 minutes video in 21 minutes, I might had read something wrong, I think it was a ONE minute video.
In any case, today it was :
1 MINUTE video for 1H11 I believe
Do you believe that? I might have a big problem somewhere,
Because now I am geting out of memory for another repo but I hadnt have it yesterday, any advice? I am so lost, this is so maddening lol


support for the require function

Hi,
I have some nodes that needs the require function. If I am not mistaken, it is not yet supported.
http://docs.puppetlabs.com/references/latest/function.html#require
Cheers,

For information, the issue is now mitigated with 50be703f9dcab9961521389a626e99b05bd233da


DropConnect wrapped model could not be parallelized

Describe the bug
While using the baal.bayesian.MCDropoutConnectModule wrapper, it is impossible to train the model with multiple GPUs.
One gets the following error:
RuntimeError: Expected tensor for argument #1 'input' to have the same device as tensor for argument #2 'weight'; but device 1 does not equal 0 (while checking arguments for cudnn_convolution)
To Reproduce
Simple training with PyTorch DataParallel and at least 2 GPUs.
Expected behavior
A possible solution would be to remove the dynamic forward method re-assignment for Conv and Dense layers. This issue is described here: https://github.com/pytorch/pytorch/issues/8637

Hello,
Thank you for submitting this issue!
I'll look into it on Monday. We are also open to contributions if you already have a fix working.


Pillow dependencies to image processing libraries  are not mentioned in installation documents

Pillow dependencies to image processing libraries are not mentioned in installation documents:
http://docs.getlfs.com/en/latest/introduction/installation.html
See chapter External dependencies on: http://pillow.readthedocs.org/en/latest/installation.html
In Ubuntu 14.04.1 LTS I issued the following command to get support for JPG and PNG:
$ sudo apt-get -y install libjpeg8-dev zlib1g-dev

I think this would be better to mention in a new External Dependencies chapter in LFS installation guide. The same chapter could also include the content of http://docs.getlfs.com/en/latest/misc/trouble_shooting.html#trouble-shooting-installation.

Fixed. 9fc0a23accadd73ccf8c1cde33a4c3898e7c1202


add new plugin for handyvertrag.de

Adds a new plugin to download invoices and connection-reports from handyvertrag.de
What linter and style-checker should be used with which settings?

Adds a new plugin to download invoices and connection-reports from handyvertrag.de

Awesome! Thank you very much.

What linter and style-checker should be used with which settings?

I'd suggest flake8 without settings (and inline overrides containing a reason for the override). Maybe globally allowing >80 char lines. I'm not sure, yet. I'll setup CI - can still be modified later.

Adds a new plugin to download invoices and connection-reports from handyvertrag.de

Awesome! Thank you very much.

What linter and style-checker should be used with which settings?

I'd suggest flake8 without settings (and inline overrides containing a reason for the override). Maybe globally allowing >80 char lines. I'm not sure, yet. I'll setup CI - can still be modified later.
EDIT: maybe pylint would be better suited
EDIT2: I've setup pylint + flake8 CI for pushes and pull-requests. I'll happily merge this PR when the issues above are fixed.


Add upgrade steps to the wiki

It would be great for the full upgrade steps that are posted to the blog to be added to the wiki. This way all the upgrade steps are located in one section.

I am about to start the daunting task of migrating from 0.9.1 to the lastest so the AWS emr service will keep running :-(  Something like this would be super helpful.  Even a page with all of the release blogs posts would give me a starting point.

A couple of tips:

Upgrade just to R64 as that's the one with IAM role support
You'll have to upgrade to Hadoop Enrich 0.14.1 for compatibility with the latest EmrEtlRunner
You'll have to upgrade from Redshift 0.3.0 straight through to 0.6.0

Hope that helps

Try this handy link for a list of releases without digging through the
blog.
http://snowplowanalytics.com/categories.html#releases
On Fri, 26 Jun 2015 09:20 Eric Zimmerman<EMAIL_ADDRESS>wrote:

I am about to start the daunting task of migrating from 0.9.1 to the
lastest so the AWS emr service will keep running :-( Something like this
would be super helpful. Even a page with all of the release blogs posts
would give me a starting point.
—
Reply to this email directly or view it on GitHub
https://github.com/snowplow/snowplow/issues/1136#issuecomment-115428160.

Also, the translation of old config properties to new is super helpful here: https://groups.google.com/d/msg/snowplow-user/1k6DIpRHKwA/DIoXhMH7ZmMJ  If there are other places to help navigate the config file aka: history file that would also be very helpful!

Ok...upgraded and running normally again.
Couple notes on Migrating from 0.9.2 --> r64

Update to r64 codebase
Migrate Postgres from 2-->3-->4-->5 with scripts in storageloader s
Update cloudfront collector pixel.
Update config file based on the link I added above to Alex's translations of old config
Add --skip shred since I am using postgres and it doesn't seem to do anything with the emr processed shred files.
Change out all buckets to remove any periods in their names.
Success :-)

Great to hear it! Thanks for taking the time to document this Eric.
Alex
On 30 Jun 2015 11:15 pm, "Eric Zimmerman"<EMAIL_ADDRESS>wrote:

Ok...upgraded and running normally again.
Couple notes on Migrating from 0.9.2 --> r64

Update to r64 codebase
Migrate Postgres from 2-->3-->4-->5 with scripts in storageloader s
Update cloudfront collector pixel.
Update config file based on the link I added above to Alex's
translations of old config
Add --skip shred since I am using postgres and it doesn't seem to
do anything with the emr processed shred files.
Change out all buckets to remove any periods in their names.
Success :-)

—
Reply to this email directly or view it on GitHub
https://github.com/snowplow/snowplow/issues/1136#issuecomment-117360244.

@alexanderdean - Added the page locally. For now it covers releases r65 through r76. Will add earlier releases soon.

Pushed: https://github.com/snowplow/snowplow/wiki/Upgrading-Steps
This is great - keep it coming @ihortom !

I wouldn't go past v0.9.0 - diminishing returns

@alexanderdean - Added releases r60 - r64 and slightly updated the layout as discussed as well as renamed the page

Thanks - pushed!

@alexanderdean - Added releases v0.9.5 - v0.9.14.

Thanks, I've repushed your local copy

@alexanderdean - Added the remaining agreed releases v0.9.0 - v0.9.4. Could be closed now.

Great job, closing


Refactor to avoid completion handler being called more than once in failure paths

In balance check code paths this is used with checked continuations which crash when completion is called more than once. This rewrites the code to be a bit more straightforward (in the SSL error case, the completion was called 3 times). I also enabled the assertForOverFulfill flag on the expectations, so the tests will catch regressions here.

We incorporated these changes into #195. Thanks for doing this, Colton!!


Update documentation for PR's

Documentation Request Type

Please choose one of the following:

[ ] New documentation
[x] Documentation needs enhancement or clarification
[ ] Documentation is broken, inaccurate, or out of date

What needs to be done
There are several suggestions made for updating ancillary documentation when making a PR at https://github.com/AgPipeline/.github/pull/6#pullrequestreview-440402450. Some of these suggestions can be incorporated into the PR template itself
Result
Better documentation around PR expectations and how-to.

It's expected that OSF pages and READMEs will be updated as well as the PR template itself (the latter as needed)

https://github.com/AgPipeline/.github/pull/8