Add base VAE template

Before submitting

[x ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ x] Did you read the contributor guideline, Pull Request section?
[x ] Did you make sure to update the docs?
[- ] Did you write any new necessary tests?

What does this PR do?
Adds a basic VAE template.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃
Yes!

Hello @annikabrundyn! Thanks for opening this PR.

In the file pytorch_lightning_bolts/models/vaes/__init__.py:

Line 1:66: W292 no newline at end of file

In the file pytorch_lightning_bolts/models/vaes/basic_vae/models.py:

Line 97:19: E221 multiple spaces before operator

In the file pytorch_lightning_bolts/models/vaes/basic_vae/vae.py:

Line 17:111: E501 line too long (112 > 110 characters)
Line 59:32: E226 missing whitespace around arithmetic operator
Line 99:111: E501 line too long (121 > 110 characters)
Line 151:111: E501 line too long (151 > 110 characters)
Line 153:111: E501 line too long (122 > 110 characters)
Line 154:111: E501 line too long (124 > 110 characters)

Do see the Hitchhiker's guide to code style

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   71.89%   71.89%
=======================================
  Files           5        5
  Lines         274      274
=======================================
  Hits          197      197
  Misses         77       77

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 80836ef...80836ef. Read the comment docs.


rxcpp::debounce not working as expected

Hi,
I want to receive some messages from the network and apply a debounce filter.
I wrote this simple code:
	auto received_messages = Rx::range(1, Rx::observe_on_new_thread()) |
		Rx::map([&](int) { return client.Receive(); }) |
		Rx::debounce(std::chrono::milliseconds(800), Rx::observe_on_new_thread());

I'm receiving tons of messages, but the subscriber seems to be called on random moments. What I'm doing wrong?
Thanks!

Did you want debounce or sample?

Sorry, silly mistake! Thanks!


LEGO: Pull request from lego/hb_839_20181018214037171 to master

LEGO: Pull request from lego/hb_839_20181018214037171 to master with localized lcls

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

Closing due to conflicts.


Removal of dependencies on cuda v10

Hi there,
cuda v10 has been EOL for some time, however it appears there are still several references to it in various places in the project.
Are there any plans to remove the cuda v10 dependencies in the pipeline?

@mamccorm yes there is.  The next release of DCGM will remove all references to CUDA v10.  Thanks!

Appreciate the reply @bmarchant, that's great to hear. Any ballpark timelines for when the next release may be due to land?

@mamccorm We are trying to get it released in the next week or two.

@mamccorm
I need to correct @bmarchant. The next major DCGM release will remove Cuda10, which is planned for later this year. However, the upcoming release in the DCGM 3.x branch will still provide Cuda10 plugins.
The DCGM policy is to support three major Cuda versions in each release.
Could you provide more details on the issues that you are facing with Cuda10?

Thanks @nikkon-dev for the follow-up, and much appreciated.
We're keen to leverage DCGM without a dependency on EOL software. Looks like CUDA v10 was added to the end-of-life section of GitLab ~9 months ago, and the binaries are also not redistributed anymore here.
Also cross-referencing some info from this doc:

https://docs.nvidia.com/deploy/cuda-compatibility/index.html

All CUDA releases supported through the lifetime of the datacenter driver branch. For example, R418 (CUDA 10.1) EOLs in March 2022
Branches R525, R515, R510, R465, R460, R455, R450, R440, R418, R410, R396, R390 are end of life and are not supported targets for compatibility

Hi @mamccorm,
I just wanted to clarify that the DCGM package doesn't rely on any Cuda packages. All the necessary components are linked or provided by the DCGM package itself and loaded at runtime based on the detected driver. It's important to note that the DCGM 3.x branch has been supporting drivers since R418, and even if Cuda10 is EOL, we cannot remove it from the package.

Thanks @nikkon-dev. So no cuda10 runtime dep, but the build process requires cuda10/11/12 to enable building of each plugin from source for their respective cuda versions?
The redist packages for cuda10 are no longer published, and outside of debian/ubuntu, there may be no existing pre-build cuda10 package to pull (which is issue we're facing when theres a buildtime dep in DCGM).
In any event this has been helpful and look forward to future releases

Cuda10 was removed from the OSS builds.


Defun broken: errors_impl.NotFoundError: Op type not registered

This code fails:
import tensorflow as tf
from tensorflow.python.framework import function

@function.Defun(tf.float32)
def custom_op(x):
    return x

x = tf.Variable(1, dtype=tf.float32)

sess = tf.Session()
sess.run(tf.global_variables_initializer())
print(sess.run(custom_op(x)))

sess.close()

Exception:
tensorflow.python.framework.errors_impl.NotFoundError: Op type not registered 'custom_op_da39a3ee'

The example is partly taken from #3710 although the bug reported there is probably a different one and was already fixed.

Version info?

Version 0.12.0.

Somehow running the init op breaks things. The code below works, but fails in the same way if you uncomment the init_op line
import tensorflow as tf
from tensorflow.python.framework import function

tf.reset_default_graph()

@function.Defun(tf.float32)
def custom_op(x):
    return tf.identity(x)

x = tf.placeholder(dtype=tf.float32)
sess = tf.Session()
#init_op = tf.global_variables_initializer()
sess.run(init_op)
x2 = custom_op(x)
print(sess.run(x2, feed_dict={x: 1.0}))

@zffchen78 must all the custom ops be created before the first session.run call? I didn't see this req in the docs

@albertz a work-around is to create your custom_op and save node before first run call

How do I save it before the first run call?

Ie in my example, you can change order of first  session run and creating init_op and it'll work

I see. So the workaround for my example:

import tensorflow as tf
from tensorflow.python.framework import function

@function.Defun(tf.float32)
def custom_op(x):
    return x

x = tf.Variable(1, dtype=tf.float32)
y = custom_op(x)
init_op = tf.global_variables_initializer()

sess = tf.Session()
sess.run(init_op)
print(sess.run(y))

sess.close()

But I think this is a bug then, right? Because I would suppose that this should work. Or is this hard to fix?

Yes, I think it was unexpected, I'll leave to @zffchen78 to comment if it's intended behavior or not

@albertz the behavior you see is explainable.
the line
sess = tf.Session()
effectively snapshots the default graph which includes the functions instantiated so far at that point.
If the function is instantiated (the line custom_op(x) after that point, so far, our implementation does not re-snapshot the graph. That might be feasible but may be a bit complex, too.


Update version in bower.json

To update the registered bower package, the upstream owner needs to update git tags:
git tag --annotate --force --message='0.4.1' v0.4.1 be3ea136af6219d544f50a61873db0b9687151d6
git push --tags
That should resolve the latest comment in #82.

Thanks so much!

@ryanlanciaux No problem. You still need to run those git commands to add the 0.4.1 tag though. (It doesn't seem possible to include them in pull requests.)


Telegram-like tabs

One user wrote he's willing to pay for this feature.
(We need to define what it means - TODO)

@ripper234 adding to next meeting agenda


update trait implementations for Uuart

Fixes compile errors now that embedded-hal-nb is updated

See #1336.

this should be fixed now https://github.com/rust-lang/cargo/issues/11939#issuecomment-1500841310


Add additional Notification: AuthenticationComplete

This would be fired just before returning from AuthenticateAsync and would be symmetric to OnMessageReceived. It would take the AuthenticationTicket that was produced.

Something like this?
https://github.com/aspnet/Security/blob/dev/src/Microsoft.AspNet.Authentication.Twitter/TwitterAuthenticationHandler.cs#L172

@Tratcher It is not clear what you are suggesting.
Line 172 is: var model = await AuthenticateAsync();


Need mechanism to keep dependencies up to date

We should be notified automatically when dependencies are out of date so we can update them without the need for external contributors discovering them and filing ad hoc issues.

We're working on this. It's tricky because it's not always true that dependencies should be upgraded. We're trying to define a consistent set of dependency versions across google-cloud-java.

This is done now that we have renovate.


replace I2C address selection headers with solder bridges

it might be an option to replace the headers with some solder bridges

Done in v0.4 of PoC.


Enable config outputs to be merged like other config sections

Users expect that when they load a module, its output is added to the site, and conversely when a module is unloaded, that its output is removed from the site (without also having to manually add or remove it from their outputs too).
For example, when users load a Netlify module they expect it to automatically output a headers file for Netlify, whereas when the module is unloaded, they expect it to automatically remove its headers output from the outputs config: https://github.com/wowchemy/wowchemy-hugo-themes/discussions/2800
However, currently Hugo does not allow outputs to be merged like other config sections: https://gohugo.io/getting-started/configuration/#merge-configuration-from-themes

So, that the outputs is missing from that list is a misconfiguration, not sure why that happened,  and we should certainly fix that, but even with that I'm not totally sure what we do with slices.
[outputs]
  home = ['HTML']
  page = ['HTML']

I don't think (for good reason) there are any way to add values to those slices from a theme (even if we got the config in order), but it should at least serve as a good default for people with nothing.

I don't think (for good reason) there are any way to add values to those slices from a theme (even if we got the config in order)

@bep Could you elaborate on this good reason? That might help to prepare a PR to resolve this issue.
It seems that both mediaTypes and outputFormats are merged explicitly in https://github.com/gohugoio/hugo/blob/c4f3a46ce6a4ce1890a26be31267838c6a065516/hugolib/site.go#L434 to
https://github.com/gohugoio/hugo/blob/c4f3a46ce6a4ce1890a26be31267838c6a065516/hugolib/site.go#L461
using
https://github.com/gohugoio/hugo/blob/c4f3a46ce6a4ce1890a26be31267838c6a065516/media/mediaType.go#L457
and
https://github.com/gohugoio/hugo/blob/c4f3a46ce6a4ce1890a26be31267838c6a065516/output/outputFormat.go#L303
So my first idea would be to merge outputs just like these in the same place as well. Do you have something in mind that would invalidate this approach?


Check Google Play Services Version

Please, while initializing the plugin add some code like this to check if Google Play Services is updated in the user device and case it is not start the problem resolution.

closing for cleanup, please re-open if this functionality is still desired


Example is wrong?

Hi,
I think that the example must have Chartist.plugins. before ctTargetLine
var chart = new Chartist.Line('.ct-chart', {
  labels: [1, 2, 3, 4, 5, 6, 7],
  series: [
    [1, 5, 3, 4, 6, 2, 3],
    [2, 4, 2, 5, 4, 3, 6]
  ]
}, {
  plugins: [
     Chartist.plugins.ctTargetLine({
      value: 1000
    })
  ]
});

Because if not, it is not defined

Fixed in https://github.com/htwyford/chartist-plugin-targetline/commit/6526ba5e0999ebf829410a80de184f5748bdaa1a. Thanks!


chore: rebuild sinker to address jan-2024 glibc updates for debian bookworm

related to: https://github.com/influxdata/tubernetes/issues/1567
changes:
rebuild sinker to address jan-2024 glibc updates for debian bookworm
#Remove setuid/setgid bits from executables. Also If the path is /proc, don't descend into it. This effectively excludes /proc from the search.
RUN find / -path /proc -prune -o -type f \( -perm -4000 -o -perm -2000 \) -exec chmod a-s {} \;

Updated the newly created image tested in k8s pods. Sinker pods seems to be running as usual.

@eumoh1601 thanks for working on this! :)


showAuthFailureReason support for email otp and totp authenticators

Is your suggestion related to an experience ? Please describe.
When showAuthFailureReason is enabled for basic authenticator and was showing respective error message to user since they get following parameters on the login page.
errorCode: 17003
lockedReason: MAX_ATTEMPTS_EXCEEDED
failedUsername: <username>
authFailure: true
authFailureMsg: login.fail.message

But if account locking is enabled for email otp and totp authenticators and requires the showAuthFailureReason support for them as well.
For TOTP, it is added in the master [1].
Moreover, showAuthFailureReason support is available for email OTP. But the parameters are not in the same pattern as basic auth.
authFailure: true
authFailureMsg: user.account.locked

It is good to return errorCode, lockedReason:, failedUsername parameters here as well to keep the consistency across the authenticators.
IS 5.11.0
[1] https://github.com/wso2-extensions/identity-outbound-auth-totp/pull/135

Related issue https://github.com/wso2/product-is/issues/15525

Checked the current behaviour in 5.11
Basicauth
Before locked
errorCode: 17002
failedUsername: <username>
authFailure: true
authFailureMsg: login.fail.message
remainingAttempts: <remaining_attempts>

When locked
errorCode: 17003
lockedReason: MAX_ATTEMPTS_EXCEEDED
failedUsername: <username>
remainingAttempts: 0


[SPARK-19507][SPARK-21296][PYTHON] Avoid per-record type dispatch in schema verification and improve exception message

What changes were proposed in this pull request?
Context
While reviewing https://github.com/apache/spark/pull/17227, I realised here we type-dispatch per record. The PR itself is fine in terms of performance as is but this prints a prefix, "obj" in exception message as below:
from pyspark.sql.types import *
schema = StructType([StructField('s', IntegerType(), nullable=False)])
spark.createDataFrame([["1"]], schema)
...
TypeError: obj.s: IntegerType can not accept object '1' in type <type 'str'>

I suggested to get rid of this but during investigating this, I realised my approach might bring a performance regression as it is a hot path.
Only for SPARK-19507 and https://github.com/apache/spark/pull/17227, It needs more changes to cleanly get rid of the prefix and I rather decided to fix both issues together.
Propersal
This PR tried to

get rid of per-record type dispatch as we do in many code paths in Scala  so that it improves the performance (roughly ~25% improvement) - SPARK-21296
This was tested with a simple code spark.createDataFrame(range(1000000), "int"). However, I am quite sure the actual improvement in practice is larger than this, in particular, when the schema is complicated.

improve error message in exception describing field information as prose - SPARK-19507

How was this patch tested?
Manually tested and unit tests were added in python/pyspark/sql/tests.py.
Benchmark - codes: https://gist.github.com/HyukjinKwon/c3397469c56cb26c2d7dd521ed0bc5a3
Error message - codes: https://gist.github.com/HyukjinKwon/b1b2c7f65865444c4a8836435100e398
Before
Benchmark:

Results: https://gist.github.com/HyukjinKwon/4a291dab45542106301a0c1abcdca924

Error message

Results: https://gist.github.com/HyukjinKwon/57b1916395794ce924faa32b14a3fe19

After
Benchmark

Results: https://gist.github.com/HyukjinKwon/21496feecc4a920e50c4e455f836266e

Error message

Results: https://gist.github.com/HyukjinKwon/7a494e4557fe32a652ce1236e504a395

Closes #17227

Test build #79116 has started for PR 18521 at commit d7f6778.

Test build #79116 has finished for PR 18521 at commit d7f6778.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79116/
Test PASSed.

cc @ueshin and @holdenk who were reviewing it and, @dgingrich the author of that PR.

cc @cloud-fan who I believe reviewed my related few PRs before and @davies who I believe is used to this code path.

Test build #79128 has started for PR 18521 at commit 5b80a8b.

Test build #79128 has finished for PR 18521 at commit 5b80a8b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79128/
Test PASSed.

Merged build finished. Test PASSed.

Test build #79131 has started for PR 18521 at commit 9ee8d03.

Test build #79134 has started for PR 18521 at commit 420b4bf.

Test build #79131 has finished for PR 18521 at commit 9ee8d03.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DataTypeVerificationTests(unittest.TestCase):

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79131/
Test PASSed.

Test build #79134 has finished for PR 18521 at commit 420b4bf.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79134/
Test FAILed.

Merged build finished. Test FAILed.

Test build #79140 has started for PR 18521 at commit 15c575f.

Test build #79141 has started for PR 18521 at commit 826dcfd.

Test build #79140 has finished for PR 18521 at commit 15c575f.

This patch fails PySpark pip packaging tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79140/
Test FAILed.

Test build #79141 has finished for PR 18521 at commit 826dcfd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79141/
Test PASSed.

@cloud-fan, I believe it is ready for another look.

LGTM, merging to master!


Issues with connect to another service

Connection to another login service needs review.

fixed in 7eb3fd6fd13b66589b5fc5635c25b7da3558c253

fixed with 9597929


[Event Request] Table 5900 - OnValidate Payment Terms Code OnValidatePaymentTermsCodeOnBeforeValidateDueDate

Hi, we need event in table 5900 On Validate Payment Terms Code, we have modification to change Due Date only when it is 0D...

Publisher:
[IntegrationEvent(false, false)]
local procedure OnValidatePaymentTermsCodeOnBeforeValidateDueDate(ServiceHeader: Record "Service Header";var IsHandled:Boolean)

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.


1998 - Fixing Coral3 checkbox storing json value as string instead of…

Fixes bug #1998

Pull Request Test Coverage Report for Build 4870

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 54.124%

Totals

Change from base Build 4866:
0.0%

Covered Lines:
14180

Relevant Lines:
26199

💛  - Coveralls


pointer-events css property is removed correctly

As per http://api.jquery.com/css/#css2 a property will be cleared when setting its value to emptry string.

Thanks for submitting this. I will not merge this in because v2.0.0 no longer has the same approach internally and shouldn't have this same problem.


Installing erlang@latest!-1 fails

Describe the bug
Installing a previous version of Erlang (using the latest!-1 version) fails.
To Reproduce

Run rtx install erlang@latest!-1

Expected behavior
Erlang 25 should be installed (since as of 2023-08-24 Erlang 26 is the latest version).
rtx doctor output
rtx version:
  2023.8.6 macos-arm64 (a0f759b 2023-08-23)

build:
  Target: aarch64-apple-darwin
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Wed, 23 Aug 2023 00:12:35 +0000
  Rust Version: rustc 1.71.1 (eb26296b5 2023-08-03)
  Profile: release

shell:
  /opt/homebrew/bin/fish
  fish, version 3.6.1

rtx data directory:
  /Users/user/.local/share/rtx

rtx environment variables:
  RTX_SHELL=fish

settings:
  {"always_keep_download": "false", "always_keep_install": "false", "asdf_compat": "false", "disable_default_shorthands": "false", "disable_tools": "[]", "experimental": "true", "jobs": "4", "legacy_version_file": "true", "legacy_version_file_disable_tools": "[]", "log_level": "INFO", "missing_runtime_behavior": "warn", "plugin_autoupdate_last_check_duration": "10080", "raw": "false", "trusted_config_paths": "[]", "verbose": "false", "yes": "false"}

config files:
  /Users/user/.config/rtx/config.toml

plugins:
  bun      (core)
  deno     (core)
  elixir   https://github.com/asdf-vm/asdf-elixir.git#a4c42e1
  erlang   https://github.com/asdf-vm/asdf-erlang.git#6744df7
  go       (core)
  java     (core)
  node     (core)
  python   (core)
  ruby     (core)

toolset:
  erlang@latest erlang@latest!-1 erlang@latest!-2, elixir@latest, node@latest, python@latest

No problems found

Additional context
$ RUST_BACKTRACE=full RTX_DEBUG=1 rtx install erlang@latest!-1
[DEBUG] rtx::config: Files: ~/.config/rtx/config.toml
Installed Plugins: elixir, erlang
[DEBUG] rtx::cli: rtx install erlang@latest!-1
[DEBUG] rtx::toolset::builder: erlang@latest erlang@latest!-1 erlang@latest!-2, elixir@latest, node@latest, python@latest
installing
[DEBUG] rtx::cmd: $ /Users/user/.local/share/rtx/plugins/erlang/bin/install
Error:
   0: ~/.local/share/rtx/plugins/erlang/bin/install exited with non-zero status: exit code 1

Location:
   /rustc/eb26296b556cef10fb713a38f3d16b9886080f26/library/core/src/convert/mod.rs:717

Version:
   2023.8.6 macos-arm64 (a0f759b 2023-08-23)

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 3 frames hidden ⋮
   4: <rtx::plugins::external_plugin::ExternalPlugin as rtx::plugins::Plugin>::install_version::{{closure}}::h9b54e62a5a644424
      at <unknown source file>:<unknown line>
   5: <rtx::plugins::external_plugin::ExternalPlugin as rtx::plugins::Plugin>::install_version::h31dd4aaa1b03e23e
      at <unknown source file>:<unknown line>
   6: rtx::tool::Tool::install_version::h6eb7076c3fa1bad3
      at <unknown source file>:<unknown line>
   7: std::sys_common::backtrace::__rust_begin_short_backtrace::h4046d150ae04a3ec
      at <unknown source file>:<unknown line>
   8: core::ops::function::FnOnce::call_once{{vtable.shim}}::he80709fdf6914636
      at <unknown source file>:<unknown line>
   9: std::sys::unix::thread::Thread::new::thread_start::h06dea01d0985d944
      at <unknown source file>:<unknown line>
  10: __pthread_joiner_wake<unknown>
      at <unknown source file>:<unknown line>

Suggestion: Run with RTX_DEBUG=1 for more information.

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
[WARN] rtx::toolset: Tools not installed: erlang@latest!-1, erlang@latest!-2 (install with: rtx install)

rtx.toml:
[settings]
experimental = true

[tools]
erlang = ['latest', 'latest!-1', 'latest!-2']
elixir = 'latest'
nodejs = 'latest'
python = 'latest'

use sub-1:latest now

Perfect, that works, thanks! Curious about the new syntax, what does it mean and what was the reason for changing it? 🙂

https://github.com/jdxcode/rtx/discussions/340


Undefined is not an object RNFileSelector.Show

Hi,
I have installed the library using "npm install react-native-file-selector --save"
In android/app/build.gradle I have added the below lines
repositories {
maven {
url  "http://dl.bintray.com/lukaville/maven"
}
maven { url "https://maven.google.com" }
}
allprojects {
repositories {
mavenLocal()
jcenter()
maven { url "https://maven.google.com" }
}
}
I have imported import RNFileSelector from 'react-native-file-selector'; in js file
on click of button calling
RNFileSelector.Show(
{
title: 'Select File',
onDone: (path) => {
console.log('file selected: ' + path)
},
onCancel: () => {
console.log('cancelled')
}
}
);
I am getting "undefined is not an object RNFileSeector.Show"
Am I doing anything wrong?

Thanks @GunaSekhar1 for raising the issue.
Looks like the library is not linked properly. Can you please try below installation steps:

react-native link react-native-file-selector

Add below snippet in your app build.gradle file

repositories {
    maven {
        url  "http://dl.bintray.com/lukaville/maven"
    }
    maven { url "https://maven.google.com" }
    ...
}

allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven { url "https://maven.google.com" }
        ...
    }
}

Add below color attributes in your app res/color.xml. You can provide your own color codes

    <color name="colorPrimary">#3F51B5</color>
    <color name="colorPrimaryDark">#303F9F</color>
    <color name="colorAccent">#FF4081</color>

Thanks
</ Pranav >

i am getting the same in IOS and i have done all the linking options. help me.


Plugins own their settings. Rework PluginGroup trait.

Objective
Fixes #5884 #2879
Alternative to #2988 #5885 #2886
"Immutable" Plugin settings are currently represented as normal ECS resources, which are read as part of plugin init. This presents a number of problems:

If a user inserts the plugin settings resource after the plugin is initialized, it will be silently ignored (and use the defaults instead)
Users can modify the plugin settings resource after the plugin has been initialized. This creates a false sense of control over settings that can no longer be changed.

(1) and (2) are especially problematic and confusing for the WindowDescriptor resource, but this is a general problem.
Solution
Immutable Plugin settings now live on each Plugin struct (ex: WindowPlugin). PluginGroups have been reworked to support overriding plugin values. This also removes the need for the add_plugins_with api, as the add_plugins api can use the builder pattern directly. Settings that can be used at runtime continue to be represented as ECS resources.
Plugins are now configured like this:
app.add_plugin(AssetPlugin {
  watch_for_changes: true,
  ..default()
})

PluginGroups are now configured like this:
app.add_plugins(DefaultPlugins
  .set(AssetPlugin {
    watch_for_changes: true,
    ..default()
  })
)

This is an alternative to #2988, which is similar. But I personally prefer this solution for a couple of reasons:

#2988 doesn't solve (1) #2988 does solve (1) and will panic in that case. I was wrong!
This PR directly ties plugin settings to Plugin types in a 1:1 relationship, rather than a loose "setup resource" <-> plugin coupling (where the setup resource is consumed by the first plugin that uses it).
I'm not a huge fan of overloading the ECS resource concept and implementation for something that has very different use cases and constraints.

At first glance this makes a lot of sense to me. Does this mean that if a plugin author wants the users to be able access some of the immutable plugin settings as read only, it will need to insert them as separate resource? Probably not an issue, just curious.

At first glance this makes a lot of sense to me. Does this mean that if a plugin author wants the users to be able access some of the immutable plugin settings as read only, it will need to insert them as separate resource? Probably not an issue, just curious.

This is correct. In theory we could build a runtime interface into the App's Plugin structs themselves, but I think thats a conversation for another day. These types of settings are for "plugin constructor data" only. Anything that is needed at runtime should (probably) still be represented as a resource. The plugin settings disappearing is one of the reasons for this change in the first place, as these are values users shouldn't be relying on at runtime generally.

bors r+

bors r-

Cancelled because this needs a migration guide and changelog!

bors r+

bors r+

bors r+


Bulb stuck with intermediate firmware

I have a pair of generic wifi light bulbs that look just like this one. No identifying markings on the outside, but I did open one up and confirm it's using an Espressif board.
I put the bulb in flash mode and ran ./start_flash.sh. After a couple tries, I get a long set of dots after a Resending SmartConfig packets, then it just stops and I get the Device did not appear with the intermediate firmware message.
When I powercycle the bulb, no vtrust-recovery network is visible, however when I have the vtrust-flash network up the bulb flickers every ~10 seconds. Tailing smarthack-wifi.log shows those flickers are related to immediate connect/disconnect events from the bulb. This makes me believe that it's running the intermediate firmware. I am unable to curl <IP_ADDRESS> during this time, likely because the bulb doesn't stay connected for more than a fraction of a second.
Any ideas on how to keep the bulb connected to the wifi long enough to upload the new firmware?
pi@raspberrypi:~/tuya-convert $ ./start_flash.sh
tuya-convert v2.4.3
Checking for network interface wlan0... Found.
Checking UDP port 53... Available.
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking UDP port 6666... Available.
Checking UDP port 6667... Available.
Checking TCP port 1883... Available.
Checking TCP port 8886... Available.
sudo: ufw: command not found
======================================================
  Starting AP in a screen
  Starting web server in a screen
  Starting Mosquitto in a screen
  Starting PSK frontend in a screen
  Starting Tuya Discovery in a screen

======================================================

IMPORTANT
1. Connect any other device (a smartphone or something) to the WIFI vtrust-flash
   This step is IMPORTANT otherwise the smartconfig may not work!
2. Put your IoT device in autoconfig/smartconfig/pairing mode (LED will blink fast). This is usually done by pressing and holding the primary button of the device
   Make sure nothing else is plugged into your IoT device while attempting to flash.
3. Press ENTER to continue

======================================================
Starting smart config pairing procedure
Waiting for the device to install the intermediate firmware
Put device in EZ config mode (blinking fast)
Sending SSID                  vtrust-flash
Sending wifiPassword
Sending token                 00000000
Sending secret                0101
................
SmartConfig complete.
Resending SmartConfig Packets
.................
SmartConfig complete.
Resending SmartConfig Packets
.................
SmartConfig complete.
Resending SmartConfig Packets
........................................................................................
Device did not appear with the intermediate firmware
Check the *.log files in the scripts folder
Do you want to try flashing another device? [y/N]

======================================================
Cleaning up...
Closing AP
Exiting...

smarthack-psk.log
smarthack-udp.log
smarthack-web.log
smarthack-wifi.log
smarthack-mqtt.log

I have exactly the same problem

I am also having the same issue.
Weirdly, I flashed 6 bulbs that looked identical, and only the final one gave this error.

Same problem here, from the 4 plugs i bought the last one didn't work, the other 3 i flashed without issues like 3 months ago

Same here. Following!

same issue here.. any idea what happen?

I seem to have run into the same issue.  I'd happily flashed about 30 smartplugs (BN-LINK BNC-60/U133TJ) in a row, when it suddenly started failing with these symptoms.  I don't think it's just that some of these have a newer firmware version or something; I've got way too many plugs to have randomly flashed all the good ones first.  I think the problem started when I plugged in an Ethernet cable, but I don't know.
Reading the reports here, it's always the "last one" that's bad, which makes me think the host configuration is getting messed up somehow.


SplitBill date is incorrect when a date other than today is selected

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.39-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @tgolen
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1707500020195589
Action Performed:

Create a split bill
On the confirmation screen, set the date to a date in the future
After creating the bill, click on the preview to view the details

Expected Result:
The date should show as date that is not today
Actual Result:
The date shows today's date because it's showing the "created" date and not the date the user specified.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/06fe85ce-3a30-490d-a5a9-fd81e9c22296

View all open jobs on GitHub

Should we allow entries with future date?
If not we can disable selecting any future date on UI.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0121fccdaccc2abdc1

Proposal
Please re-state the problem that we are trying to solve in this issue.
The SplitBill date displays incorrectly when a date other than today is selected.
What is the root cause of that problem?
1 - While making an API call, the created field is not passed as a param. Consequently, the backend consistently returns today's date.
2 - The addition of the created parameter to SplitBillParams improves the optimistic transaction data. However, the SplitBill response still reflects today's date.
What changes do you think we should make in order to solve the problem?
To address this issue, two essential changes are required:
1 - Include the created parameter in SplitBillParams and other relevant split params types.
2 - Coordinate with the backend team to implement the necessary updates.
What alternative solutions did you explore? (Optional)

Noticed this issue while working on another PR. Interested in addressing it, despite the absence of the "Help Wanted" tag. However, I believe we still need an internal team member to check and implement the required backend adjustments.

Could I take this issue as C+ contributor because I have context and discuss here

Should we allow entries with future date?

I noticed this question and wanted to respond. This should be allowed, yes. Please use these constants for the date.

Assigned to you @DylanDylann to work on this.

Seems like the labels didn't apply correctly here. Thanks for noticing @brunovjk -- giving you a heads up if you want to make a proposal 😊

It seems like "created" is passed to the RequestMoney command with a value similar to "2024-02-17", but the same doesn't happen on SplitBill. I don't have my environment setup so just posting to anybody who's looking. Seems like you might have to make API changes aswell to implement the "created" parameter and do something with it on the server.

Very good, thank you @stephanieelliott, I already have a proposal. However, today I will re-investigate and re-make the proposal if necessary.

Proposal
Please re-state the problem that we are trying to solve in this issue.
SplitBill date displays incorrectly when a date other than today is selected.
What is the root cause of that problem?
Missing created parameters at SplitBillParams.
What changes do you think we should make in order to solve the problem?

Add created parameters at SplitBillParams.
Update IOURequestStepConfirmation to pass transaction.created to IOU.splitBill and IOU.splitBillAndOpenReport call.
Update splitBill, splitBillAndOpenReport and createSplitsAndOnyxData to receive and use created value to buildOptimisticTransaction.

[!NOTE]
Although the transaction created is correct with these changes, we also need to make changes to the BE so that it can use the created param passed, as we do in CompleteSplitBill, and returns the correct date.
POC: Create a splitBillAndOpenReport offline and than go online:

Proposed changes

https://github.com/Expensify/App/assets/95647348/24665cde-8444-479f-8421-0b85d6528a3e

Latest main

https://github.com/Expensify/App/assets/95647348/42186470-e7d6-489a-9537-a96cc31b0c8a

What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
SplitBill date displays incorrectly when a date other than today is selected.
What is the root cause of that problem?
Missing created parameters at SplitBillParams.
What changes do you think we should make in order to solve the problem?

Add created parameters at SplitBillParams.
Update IOURequestStepConfirmation to pass the created transaction value to IOU.splitBill and IOU.splitBillAndOpenReport call.
Update splitBill, splitBillAndOpenReport and createSplitsAndOnyxData to receive and use created value to buildOptimisticTransaction.

[!NOTE]
With these changes, transaction.created is correct, but we must also update BE to use the created parameter when we call SPLIT_BILL and SPLIT_BILL_AND_OPEN_REPORT, as we do in COMPLETE_SPLIT_BILL, which returns the correct date.
POC: Create a splitBillAndOpenReport offline and than go online:

Proposed changes

https://github.com/Expensify/App/assets/95647348/24665cde-8444-479f-8421-0b85d6528a3e

Latest main

https://github.com/Expensify/App/assets/95647348/42186470-e7d6-489a-9537-a96cc31b0c8a

What alternative solutions did you explore? (Optional)

@brunovjk Your proposal looks good to me
Note that: We need to update Split Bill APIs from BE side to fix this issue completely
🎀 👀 🎀 C+ reviewed

Thank you @DylanDylann  :D

Don't need to update StartSplitBill API

Exactly!
Thank you @DylanDylann for the review :D

Don't need to update StartSplitBill API

Exactly!
Thanks for the review @DylanDylann  :D

Hi @brunovjk, looks like the backend was just modified to support the created param for the commands SplitBill and SplitBillAndOpenReport a few days ago. Can you try your changes again and see if the backend returns the right date in the response now?

Ah shoot, actually this might be the same issue as https://github.com/Expensify/App/issues/34526, which just had this fix merged: https://github.com/Expensify/App/pull/35141. Right?

@francoisl Thanks for pointing out that. Let's close this one

Thank you for pointing out that. Can't reproduce anymore

I can't repro it anymore either -- gonna close this as resolved.


plop fails if prompt property is omitted in plopfile.js

Example: https://gist.github.com/despairblue/82a7bd6a16eccdbb7856493fb4d79c0a
Running node_modules/.bin/plop doesn't create a file or return an error code. When adding prompts everything works again.

Thanks, I'll look into adding some validation for the generator structure before executing it.

this issue will be taken care of in the next plop release when I integrate node-plop. node-plop addresses this issue in release v0.3.0. stay tuned...

this should be fixed now in v1.6.0


[UI] Rework Project Grid View /viewprojects

Use the attached layout for the project grid views

Use the color scheme from your Mock-ups for fonts etc...


add PHP 8.0 version

As PHP8 is now officially released and Silverstripe supports it, there should also be a docker container sporting PHP8.
I have tried to add it by interpreting the structure of this repo, but if I have missunderstood, just point me towards the right solution and I will update the PR!

Have pushed up a quick update now that the master branch has changed. Also repeated your string fix for the 8.0 float in Github tests for rest of the floats.

Looks like silverstripe/installer is still broken for PHP 8 due to PHPUnit dependencies.
Problem 1
    - sminnee/phpunit[5.7.28, ..., 5.7.x-dev] require phpunit/php-code-coverage ^4.0.4 -> satisfiable by phpunit/php-code-coverage[4.0.4, ..., 4.0.8].
    - phpunit/php-code-coverage[4.0.4, ..., 4.0.8] require php ^5.6 || ^7.0 -> your php version (8.0; overridden via config.platform, actual: 7.4.13) does not satisfy that requirement.
    - Root composer.json requires sminnee/phpunit ^5.7 -> satisfiable by sminnee/phpunit[5.7.28, 5.7.29, 5.7.x-dev].

The docker builds appear to work, however the tests are failing due the composer issues with 'beta' support of PHP 8.0.
You could use the Dockerfiles to build locally, otherwise will have to wait until issues are fixed.

Thanks for the input! I was trying to come back to this in the next few weeks, and I will have a look at the dependency-issues then.


Add option for processing Seurat objects

scIB provides a function for loading Seurat Rds objects. This should be implemented as potential first step of the pipeline, since a lot of users might prefer R for the data unification.

Done


Fix: scrollbars should no longer show when folder collapse

Fixes #139

😱

Should now be fixed @n1ru4l 😅


ci: add a missing permission required from v0.7

According to https://github.com/suzuki-shunsuke/tfaction/releases/tag/v0.7.0, actions: read is necessary to download the plan file.

Thank you for your contribution!
In the example, GitHub Token issued by GitHub App is used so you don't need to add the permission.
https://github.com/suzuki-shunsuke/tfaction-example/blob/8157d783365cff38dcbba74b8408fcaf5522cb9c/.github/workflows/apply.yaml#L44-L49
https://github.com/suzuki-shunsuke/tfaction-example/blob/8157d783365cff38dcbba74b8408fcaf5522cb9c/.github/workflows/apply.yaml#L76
But if users build workflows referring to the example but use GitHub Actions token, the apply workflow would fail and they would be confused.
So it may be safer to add the permission to the example.


conv1d_transpose not implemented

I would like to perform a conv1d_transpose, but I can’t see any implementation in tensorflow.
I guess that inserting zeros between each values and then applying a regular conv1d would do the job ?
(principle explained hereafter with conv2d_tranpose : https://github.com/tensorflow/tensorflow/issues/4306)
But I can't find a way to implement this kind of operation with tensorflow :
import numpy as np
arr = np.arange(1, 10)                 # array([1, 2, 3, 4, 5, 6, 7, 8, 9])
np.insert(arr, slice(1, None), 0)  # array([1, 0, 2, 0, 3, 0, 4, 0, 5, 0, 6, 0, 7, 0, 8, 0, 9])
Any ideas ?
Thank you

Likely we will not get to this feature request quickly. I'd suggest asking on stackoverflow if someone has an elegant way to implement this. Otherwise, we'd welcome a contribution from anybody who has time to implement this. To insert zeros you might try using
arr = np.arange(1, 10) # array([1, 2, 3, 4, 5, 6, 7, 8, 9])
foo = tf.zeros_like(arr)
stacked = tf.stack([arr, foo], axis=1)
zeros_inserted = tf.reshape(stacked, (stacked.get_shape().num_elements(), ))

@aselle I can work on this

conv1d internally invokes conv2d (here). Should conv1d_transpose, similarly, invoke conv2d_tranpose?

Hi,
I'm not very good a this, but I was wondering if you could use tf.expand_dims for a quick fix

Expanding dims for conv2d_transpose works fine for me.
One small gotcha is that your filter variables will need to be expanded on axis 0, not axis 1, since the conv2d uses the filter width, not filter height.  So:
new_x = tf.expand_dims(old_x, 1)
new_W = tf.expand_dims(old_W, 0)
deconv = tf.nn.conv2d_transpose(new_x, new_W, strides, output_shape)
deconv = tf.squeeze(deconv, axis=1)

Added a PR #13105 for conv1d_transpose.


Osmosis labs docs

@daniel-farina Merges your recent changes and my last PR

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Codecov Report

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

@@           Coverage Diff           @@
##             docs     #617   +/-   ##
=======================================
  Coverage        ?   20.17%
=======================================
  Files           ?      172
  Lines           ?    24122
  Branches        ?        0
=======================================
  Hits            ?     4867
  Misses          ?    18465
  Partials        ?      790

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 f2f0c78...5be1b17. Read the comment docs.


A generalized framework for accuracy benchmarks

This is kind of an unsatisfying PR, because

Stripe82Score.jl and validate_on_stripe82.jl can't be deleted yet, because the new versions aren't quite working the same yet, and we can't abandon the old files until the new implementation is satisfactory
The output of GalsimBenchmark.jl is a bit less useful than it was before (but that will change), and I had to comment out some test cases (temporarily), something I swore I wouldn't do anymore, and
We don't have support yet for synthetic imagery from the Celeste likelihood, one of the main goals.

But I wanted to get a PR out there because it's already been way too long and there are many lines of diff. And the new implementation is a lot more flexible than the old one, and hopefully cleaner.
The wiki page should give some context, but feel free to ask questions or request more context.
This implements most of #510.

LGTM. Nice to see it coming together. I appreciate the wiki documentation. Please go ahead and merge this PR whenever the Travis tests are passing.

For what it's worth, I think things are OK now but data.sdss3.org seems to be down so the travis tests can't run :-/. I'll at least do another run on my laptop...


Clean assembly files

Datasets initiated from assemblies must have a cleanup step. This could either be at registration or in the cds step (as it's done for reads). Cleanup should remove characters [^A-Za-z0-8_-] from the defline before the first space (replace them by _?).

Cleanup should also normalize line lengths (for indexing).


RPM installation fix

This was tested with an EIB image containing the fix and confirmed working so LGTM.

Fixes #565


New version: NIRX v0.1.5

Registering package: NIRX
Repository: https://github.com/rob-luke/NIRX.jl
Created by: @rob-luke
Version: v0.1.5
Commit: ec227e54e8d42ac160e00928a41283e6bb26aa47
Reviewed by: @rob-luke
Reference: https://github.com/rob-luke/NIRX.jl/commit/ec227e54e8d42ac160e00928a41283e6bb26aa47#commitcomment-38334284

Cancel auto-merge


Fix broken link

Hmm, that change didn't seem to fix it, according to the deployed preview. Here's where that link shows up:

Thanks @dkniffin - it should actually be <%= extend_url :params_overview %>.
Embarrassingly I have actually just accidentally just included a fix for this in PR #467 (which hopefully addresses your Nokogiri issue!) so I'll just close this for now and when that PR gets merged it will fix the link too :-)
Thanks for bringing it to my attention 👍


[CANNOLI-244] Update --terms and other options for Ensembl VEP

Fixes #244

Coverage remained the same at 0.0% when pulling cca71d838afaf82ea3a0cf3c85c1c01a71915719 on heuermh:issue-244 into 9f752ce7ac266fc5c6fdaead16f1df025cffffe2 on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/cannoli-prb/231/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/cannoli-prb/251/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/cannoli-prb/253/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/cannoli-prb/255/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/cannoli-prb/258/


Is it possible to have acknowledgements support for Adapter

Is it possible to have acknowledgements support for Adapter?
https://socket.io/docs/v4/emitting-events/#acknowledgements

Yes, It is needed


The README is unclear (and possibly the configuration is indirect)

Disclaimer: I am/was confused in so many ways, it was struggle to even write this issue down - I think I only started understanding how the autoscaler works when writing this but I'm still not really confident I do understand it now.
The documentation should explain why:

The parameter "coresPerReplica" is called so. If I want to decide how many replicas I want per core in the cluster, I want "replicasPerCore". Cores per replica seems like leaking implementation details.

"nodesPerReplica" is even more obscure - from my struggles I understand that we're trying to calculate the number of replicas from the number of cluster nodes - why isn't it "replicasPerNode"?

The presented formula:

replicas = max( ceil( cores * 1/coresPerReplica ) , ceil( nodes * 1/nodesPerReplica ) )

is beautifully exposing this issue. It could be rewritten to
replicas = max( ceil( cores * replicasPerCore ) , ceil( nodes * replicasPerNode ) )

For instance, given a cluster has 4 nodes and 13 cores.

A regular old example cluster would never have a number of cores indivisible by the number of nodes. Maybe except for MixedInstancesPolicy on AWS - but that's a very advanced topic. One may start thinking the README talking about used capacity.

The README should state if it's talking about used cores or total core capacity.

replicasPerCore and nodesPerReplica would result in fractional numbers in practice which are arguable more confusing...


Add support for Python 3

This uses the python package future to smooth over most of the
differences between the versions

Run stage 2 fixes with standard boilerplate

Get the test suite passing on Python 3

Cleanup code after futurize got at it:

Use set literals
Remove unnecessary list conversions
Convert old_div uses to floor division operator
Fix example.py
Mark the star imports noqa
Mark package as Python 3 compatible
Install the right version of protobuf in setup.py
Describe how tox is supposed to work
Commit tox configuration

Note to future readers: Most of the discussion happened on https://github.com/simon-weber/gmusicapi/pull/396

Great work!


Fix shader failure when using non-const initializer on a constant

Prevent using non-const (or uniform) expression in constant initializers:
uniform float scalar_uniform;

const float scalar = test; // INCORRECT

uniform float scalar_uniform;
const float scalar_constant = 1.0;

const vec3 v= vec3(0, 0, scalar_uniform); // INCORRECT
const vec3 v2= vec3(0, 0, scalar_constant); // CORRECT

That will also prevent using them in a local constants:
uniform float scalar_uniform;

void fragment() {
	const vec3 v= vec3(0, 0, scalar_uniform); // INCORRECT
}

That would lead to a compatibility breakage, because shaders like this seems working correctly (at least on Vulkan renderer) - but, for example, SHADERed accept it as error:

Fix https://github.com/godotengine/godot/issues/72466

Thanks!


Duplicate identifier 'FormData'.  TS2300

Environment
System:

OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Memory: 1.37 GB / 7.89 GB

Binaries:

Node: 10.14.1 - C:\Program Files\nodejs\node.EXE
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

npmPackages:

styled-components: 4.4.1 => 4.4.1

Reproduction
Steps to reproduce
Step 1 - Create component:
`import React from 'react';
import { Link } from 'react-router-dom';
import styled from 'styled-components';
const StyledLink = styled(Link)`
text-decoration: none;
&:focus, &:hover, &:visited, &:link, &:active {
    text-decoration: none;
}

`;
export default (props) => <StyledLink {...props} />;`
Step 2 - Use component:
<Tab component={StyledLink} to={'/'} label='Home' />
Expected Behavior
Open application in browser without errors
Actual Behavior
Error:
`TypeScript error in C:/Users/Игорь/Desktop/reactproject/GiverStamps/GiverStamps/ClientApp/node_modules/@types/react-native/globals.d.ts(40,15):
Duplicate identifier 'FormData'.  TS2300
38 | interface Blob {}
39 |

40 | declare class FormData {
|               ^
41 |     append(name: string, value: any): void;
42 | }
43 |`

Whatever that is has nothing to do with styled-components
On Wed, Oct 30, 2019 at 4:34 PM Igor Teterkin<EMAIL_ADDRESS>wrote:

Environment System:

OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Memory: 1.37 GB / 7.89 GB

Binaries:

Node: 10.14.1 - C:\Program Files\nodejs\node.EXE
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

npmPackages:

styled-components: 4.4.1 => 4.4.1

Reproduction Steps to reproduce
Step 1 - Create component:
`import React from 'react';
import { Link } from 'react-router-dom';
import styled from 'styled-components';
const StyledLink = styled(Link)`
text-decoration: none;
&:focus, &:hover, &:visited, &:link, &:active {
text-decoration: none;

}
`;
export default (props) => <StyledLink {...props} />;`
Step 2 - Use component:
<Tab component={StyledLink} to={'/'} label='Home' />
Expected Behavior
Open application in browser without errors
Actual Behavior
Error:
`TypeScript error in
C:/Users/Игорь/Desktop/reactproject/GiverStamps/GiverStamps/ClientApp/node_modules/@types/react-native/globals.d.ts(40,15):
Duplicate identifier 'FormData'. TS2300
38 | interface Blob {}
39 |
40 | declare class FormData {
| ^
41 | append(name: string, value: any): void;
42 | }
43 |`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/2842?email_source=notifications&email_token=AAELFVUATNH3ECZNH52IAXDQRHVWJA5CNFSM4JG77KY2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HVRXYLQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAELFVWSSIVZOTOMCJZHUA3QRHVWJANCNFSM4JG77KYQ
.

It is true it is not this project but it is this project's typescript definition @types/styled-components. The (at the time of writing 4.4.0) npm package dependencies have both react and react-native types and so overlap.
See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/34882
@Belka383 a workaround, for yarn,  https://github.com/DefinitelyTyped/DefinitelyTyped/issues/33311#issuecomment-494477593

Sure, but we also don't maintain the typings.


i18n: add color scheme option

I haven't really tested this because I don't know how to but the vconsole.conf file being generated is valid.

It sounds a bit strange to have color settings in i18n, but it makes sense to me to keep it close to the other options in there.

@vcunat Yes, I think so too.
Maybe someone else knows a better place.

Updates?

I'm sorry for the delays. There are really many issues and PRs coming daily.

This is the file generated for systemd-vconsole-setup.service so there must be something wrong. The problem is I don't know how to test this kind of changes.


BI-1365 - Scope ontology terms to be within a program when saved over BrAPI

Description
Story: BI-1365

Added program key to scope ontology terms

Dependencies
None
Testing

Create and update ontology terms. Verify that the observationVariableName, traitName, scaleName, and methodName values are scoped with the program key in the underlying brapi service and that these fields all appear normal without the program key in the BI interface.

Checklist:

[x] I have performed a self-review of my own code
[x] I have tested my code and ensured it meets the acceptance criteria of the story
[x] I have create/modified unit tests to cover this change
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to documentation
[ ] I have run TAF: <link to TAF run>

Test passed


Pr/31208

About the PR

Why / Balance

Technical details

Media

Requirements

[ ] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

Isn't this just the same as #31208 ?

Isn't this just the same as #31208 ? Edit: Ah, I see, also for sleeper agent. Write a proper PR description please.

 I thought I merged this into my own repository.
was testing git aliases


_changes handler dies on heartbeat message

The JSON parser bombs out when it receives a CouchDB heartbeat message, which is just a newline.  The error occurs on line 571, on calling JSON.parse.
                        var end;
                        if (~(end = chunk.indexOf('\n'))) {
                            buffer.push(chunk.substr(0, ++end));
                            buffer.length && response.emit('data', JSON.parse(buffer.join('')));
                            buffer = [chunk.substr(end)];
                        } else {
                            buffer.push(chunk);
                        }

At the time JSON.parse is called, buffer contains ['', '\n'] when a heartbeat message is received.  The join turns it into '\n' and JSON.parse throws SyntaxError: Unexpected end of input.
A possible fix would be:
                        var end;
                        if (~(end = chunk.indexOf('\n'))) {
                            buffer.push(chunk.substr(0, ++end));
                            var jsonstr = buffer.join('').trim();
                            jsonstr.length && response.emit('data', JSON.parse(jsonstr));
                            buffer = [chunk.substr(end)];
                        } else {
                            buffer.push(chunk);
                        }

This checks whether the string JSON.parse receives is empty instead of checking whether the buffer is empty (which will never be the case as far as I can tell).  When a heartbeat message occurs, buffer will contain ['', '\n'], which will be reduced to '' in jsonstr (because of the trim()), preventing JSON.parse from being called.
I didn't have any problem with version 0.5.6, the problem started with 0.5.7.  This is kind of odd, because looking through the code of 0.5.6, I can't really tell why it worked there.

This is fixed in<EMAIL_ADDRESS>and in the v0.6.x branch. We are now using the follow library to handle all of this.


Future Admin Generator: Don't generate toolbar in form, should be added in parent page component

And adjust demo Products Future.
This is a major braking change, but we never released a stable version containing the future generator.
Alternative
we could add a configuration if the toolbar should be generated. But I think we usually should not do that as we always want to use the SaveBoundary.
TODO (later):

[ ] add second form like in handmade (needs https://github.com/vivid-planet/comet/pull/1908)
[ ] add variants

we could add a configuration if the toolbar should be generated. But I think we usually should not do that as we always want to use the SaveBoundary.

@nsams couldn't the SaveBoundary just be part of the generated code?

@nsams couldn't the SaveBoundary just be part of the generated code?

no, because one SaveBoundary is responsible for (possibly) multiple forms. "Central Save Button"

@nsams please fix conflicts.


INT4 and other low-precision conversion support status

What is the current status of model conversion (PTQ specifically) with INT4 precision?
The question was raised before here https://github.com/tensorflow/tensorflow/issues/60125.
Also it looks like INT4 support is being added to various parts of tensorflow, as evidenced by https://github.com/tensorflow/tensorflow/pull/63870 and https://github.com/tensorflow/tensorflow/blob/6738c28cf4eed334d75d02b6e97fe16c34069ef1/tensorflow/compiler/mlir/quantization/tensorflow/quantization_options.proto#L76.
However at the moment there seems to be no way to quantize model to INT4 (specifically the weights):

the tflite converter MLIR based conversion (the "experimental" conversion) seems abandoned. It is not possible to specify the type of weights quantization
what seems to be a new API for quantization (is it the one from blog article https://blog.tensorflow.org/2023/05/google-io-2023-whats-new-in-tensorflow-and-keras.html ?) lives here https://github.com/tensorflow/tensorflow/tree/master/tensorflow/compiler/mlir/quantization/tensorflow (???). It is possible to use it with INT8, but not INT4 - but the resulting SavedModel cannot be converted to .tflite (SegFault).

Can anyone who actively works on this in TF team shine the light on what is the current direction and where one needs to dig to add INT4 PTQ quantization?

Hi @AIWintermuteAI,
Please share your .tflite file to reproduce the issue.
Thank You

Hi @abattery, can you please take a look or comment on this? Thanks.


[CodeCompletion] Don't suggest initializers on existential types

Existential types cannot be instantiated.
rdar://94369218

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@AnthonyLatsis

Do we still show inits for an existential metatype base? For example,

This change doesn't affects member completions like expr.<HERE> so it still show initializers on it.
As for meta(<HERE>, yeah maybe we should suggest initializers, could you file an issue?

@swift-ci Please smoke test


Fix  'Currencies must be identical' bug

This will fix InvalidArgumentException with message 'Currencies must be identical', because of  'USD  '  !== 'USD'

how did you produce the bug in the first place?

in db 'USD   '    (char is fixed length col type)
in code 'USD'
for ex.:
protected $currency = 'USD';
try to get balance got that error

php 7.2
lara 5.6
postgres


CodeSandbox not correctly running code

Using v7?
Yes
Describe the bug
Opening any example in CodeSandBox, get this error A cross-origin error was thrown. React doesn't have access to the actual error object in development. See https://fb.me/react-crossorigin-error for more information.
To Reproduce
Steps to reproduce the behavior:
Open any example in codeSandbox

This is a known issue and will be resolved with our next release. Stay tuned.

This should now be fixed. Thanks!


Implement run using the containerd snapshotter

When upstreaming this patch, we also need to include https://github.com/rumpl/moby/pull/43


Update documentation images

Fixes 1/3rd of PXBLUE-2656.

Changes proposed in this Pull Request:

Update documentation images so there is no reference to PX Blue

Screenshots:
Before

After

I know this is only 1/3 of the story, but just a little heads up that our pics are obsolete style-wise. So like in this drawer, our default style for menu item is regular font weight (body 1) for an unselected menu item, and the icon colors shall be black500 (I know our API allows something crazier). I think the default style for nav group title is overline and black500.

For an anatomy page, we may want to show the default behavior to not confuse people — your call.

@huayunh I'd prefer to keep this story to "remove px blue references". If we want to update the style stuff that should be revisited in another story. I personally think all of these examples should be properly built out in Figma so they can be easily modified and updated when we make style changes. Some of them are built with Figma components already, but some are just old screenshots that aren't easily reproducible. For this specific example, I just overlayed a header component over the old screenshot.

@huayunh I'll wait for a response or approval before merging this just in case you still want changes made.

if you do not plan to fix the styling part this round, then you would want to make another story for it (or does it already exist?)

if you do not plan to fix the styling part this round, then you would want to make another story for it (or does it already exist?)

Yeah @daileytj can you make a follow-up story and throw it into R23?

if you do not plan to fix the styling part this round, then you would want to make another story for it (or does it already exist?)

@daileytj can you make a follow-up story and throw it into R23?

You got it!


Update tokyonight config

the vim.g.tokyonight_style seems to be deprecated and does nothing
also added new style "moon"
from :help tokyonight.nvim-tokyo-night-usage:
    colorscheme tokyonight

    " There are also colorschemes for the different styles
    colorscheme tokyonight-night
    colorscheme tokyonight-storm
    colorscheme tokyonight-day
    colorscheme tokyonight-moon

we build documentation (and also the release notes) from the docs directory - you can simply add a line to the docs/release-notes/release-0.3.adoc file briefly descrobing the change

we build documentation (and also the release notes) from the docs directory - you can simply add a line to the docs/release-notes/release-0.3.adoc file briefly descrobing the change

ok, done

Thanks!


Add assert in pointwise.hpp for empty inputs

Ensure that we don't have empty inputs when computing shape for pointwise function

Add some tests in op_shape_tests.cpp as well for pointwise.

You can also modify fuse_pointwise with this change so that it doesn't attempt to create pointwise op with empty input args.

You can also modify fuse_pointwise with this change so that it doesn't attempt to create pointwise op with empty input args.

This is probably a good idea as well

Add some tests in op_shape_tests.cpp as well for pointwise.

Will do

This requires unit/verify tests.

related to #1587

Removed matcher related optimization for now. for convert(literal)

fuse_pointwise needs to be updated.

Done


[Request] Polorization Timer

How hard would it be to make a polorization timer? And maybe a windows notification showing when the timer is up?

@jsmb768ypl Nice feature request. What exactly was the timer: 4min right?

@exodus4d no 5 minutes


Support Sub-Referenced Assemblies in Blazor

Desired Goal
When calling ctors for objects in Blazor we should include all the assemblies that the user has loaded so that Types that require components from another Assembly can be created.

this is now done


Can't repeat deployment of private endpoint

Bicep version
Bicep CLI version 0.16.2 (de7fdd2b33)
Describe the bug
Deploying a storage account with private endpoints works the first time.  However, running the deployment again with identical parameters fails.  It attempts to redeploy the private endpoint, and fails with the error:
Cannot change the private link connection on private endpoint /subscriptions/<SUB_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.Network/privateEndpoints/<PEP_NAME>. Please ensure you are not updating the details of existing private link connection: '/subscriptions/<SUB_ID>/resourceGroups/<RG_NAME>/providers/Microsoft.Network/privateEndpoints/<PEP_NAME>/privateLinkServiceConnections/<PEP_SERVICE_CONNECTION>'. That is not allowed.

To Reproduce
This is my resource definition.  The bicep file is intended to be an all-in-one storage account deployment.
storageServices is an array of storage services to be enabled on the storage account., e.g. ['blob', 'dfs'].  The resource definition is intended to loop through this list and connect private endpoints for each enabled service.
// Private Endpoints
resource privateEndpoints 'Microsoft.Network/privateEndpoints@2022-09-01' = [for i in range(0, length(storageServices)): {
  name: '${basePepName}-${storageServices[i]}'
  location: location
  properties: {
    privateLinkServiceConnections: [
      {
        name: '${basePepName}-${storageServices[i]}'
        properties: {
          privateLinkServiceId: storageAccount.id
          groupIds: [
            storageServices[i]
          ]
        }
      }
    ]
    subnet: {
      id: snetId
    }
  }
}]

Additional context
On first run, this does exactly the right thing, so I'm wondering what's happening to make it try to modify the endpoint configuration rather than just see it exists and leave it as-is.
This is when running in the default incremental mode.

Perhaps it's related to the extra settings as below, it's been a while since I implemented this, so I would have to recheck the docs, however please test it yourself and let us know how you go.
          privateLinkServiceConnectionState: {
            status: 'Approved'
            description: 'Auto-Approved'
            actionsRequired: 'None'
          }

You were spot-on!  After adding this clause, the template deploys repeatedly in Incremental mode without error.
I shall raise a support ticket as requested by @alex-frankel just in case this might warrant a change in behaviour or an update in the docs.
Thanks again for your help!

linking to the older known issue on complete mode not working with privatelink/privateendpoint.

https://github.com/Azure/bicep/issues/6810


Belongs-To parent module scope is not consider in Submodule

Let's discuss based on yangster-test.yang (it could be found in io.typefox.yang/src/test/resources).
If we consider to create a submodule of the yangster-test.yang with the following content.
submodule yangster-test-sub {
    yang-version 1.1;
    belongs-to yangster-test {
        prefix ytest;
    }
    augment /ytest:c1 { }
}

When we are trying to load it first (purpose is to update this submodule and serialize it afterwards), we found the SchemaNodeIdentifier /ytest:c1 is not linked correctly. schema node c1 is still an eProxy.
So we tried to add yangster-test as an import module, like:
   belongs-to yangster-test { prefix ytest; }
   import yangster-test { prefix ytest; }

Then yang parser solve the link correctly.
But accutally, this is a weired behavior for yang lsp. As to a submodule, if belongs-to has already been defined, the submodule should have the parent module scope by default. Back to the example, the additional 'import' of yangster shouldn't be used in this example.
Same scope problem also happens when we are trying to serialize a new create submodule.
Serializer couldn't finish to serialize Augment because missing target node in the scope.
yangster-test-sub.yang.txt

Although I am still having serialization test issues, I have fixed the flawed belongs-to case. I have a question; let's assume we have the following two Yang models:
foo.yang:
module foo {
    yang-version 1.1;
    namespace "foo:bar";
    prefix x;

    typedef foo {
        type int32 {
            range "1..40 | 60..100";
        }
    }
    typedef foo2 {
        type foo {
            range "4..20";
        }
    }
    typedef foo3 {
        type foo2 {
            range "5..15";
        }
    }

    container c12 {
            container cool {}
    }
}

foosub2.yang:
submodule foosub2 {
    yang-version 1.1;
    belongs-to foo {
        prefix "fooprefix";
    }
    grouping mygrouping2 {
        container c12 {
        }
    }
    uses "fooprefix:mygrouping2" {
        augment "c12" {
            container augmented {}
        }
    }
}

Would you expect an error in the foosub2.yang file at foosub2.mygrouping2.c12 as it is already defined in foo.yang too. Thank you!

Hi Kittaakos,
It is a tricky case, really.
From my understanding (according to RFC7950), submodule has full view of parent module scope, due to belongs-to.
But parent module may not have any information about submodule, if there is no 'include' for a certain submodule in parent module.
So basically, in this particular case, I think, there should has a warning on foosub2.yang, because foosub2.yang defines an duplicate data definition node c12.
Why do I propose warning here? Because, in current case, foosub2.yang is not included into foo.yang yet.
The duplicate issue hasn't be involved into foo.yang. (Submodule couldn't be used without parent module).
But when foo.yang includes foosub2.yang, I think both foo.yang and foosub2.yang should report error.
This is my opnion.
Meanwhile, I compared with Pyang validation result. Pyang doesn't report any error for current case (I don't think this is correct). Of cause, Pyang does report error when 'include' is used in foo.yang. Because duplicate really happens in both foo.yang and foosub2.yang.
I'm also asking our Yang Expert to share their idea, I will follow up ASAP.

Hi Kittaakos,
After discussing with our Yang Expert, I think we could handle the case according the following rules.

For submodule (foosub2.yang), it shouldn't be an error, because submodule couldn't decide when it is used by parent module. Personally, I recommend to raise a warning in submodule, because it can detect this kind of duplicate as potential error.
For parent module (foo.yang), when include is not used, there shouldn't be an error. But when submodule is 'include' into parent module, this kind of duplicate must be raised as an error, (prefer to report in parent module, the same reason, parent module decide when to involve submodule).

Does this make sense?

Does this make sense?

Absolutely, thank you for the clarification, @huyuwen.
Please note, these additional constraints make the scoping (and the validation) a bit more tricky, in other words, it will take some time to have this additional feature on the master branch.


[AUDIT] Match DataSourceV2ScanExecBase changes to groupPartitions method

As part of https://github.com/apache/spark/commit/9e2aafb1373 Spark has made changes to the DataSourceV2ScanExecBase which should be matched.

I'm taking a crack at this one.

As discussed offline, this is redundant due to #10712. We can converge our efforts in #10944

Closing this. It's handled by #10944.


file for variables

such as scheme ('mda_streams')

I was just thinking you could code it as a package global

Still need a script/file for it, right?

Yeah, often in an AAA.R file

ok, so your disagreement with "file for variables" ...was...what?

none, apparently interpreted it poorly

plotttly

i believe this is called mda.streams:::pkg.env now - that's what holds scheme. we also have get_var_codes() and get_ts_variables() which report on available variables.


[codesign] bring up verify codesign test on release branches

bring up fixed verify codesign test on release branches on dashboard. This would help release engineer detect codesign problems in an earlier stage, and prevent the possibilities of merging in unsigned binaries.
context: Christopher and I invested a ton of hours on this and after eliminating a ton of possibilities, come up with https://flutter-review.googlesource.com/c/recipes/+/34180 (which is already merged) to fix https://github.com/flutter/flutter/issues/95297, tested with led.

I think this is right, @CaseyHillers this should work, right?

Yeah, this will override the top level enabled_branches.


Implement classes to compute checksums on behalf of the user.

We need classes that will compute MD5 and CRC32 checksums so the users do not have to find their own classes.  Both should be "easy" because we depend (indirectly) on openssl which provides abstractions to do this.

This was fixed in #1344.


Add typescript types for returned tokens

See https://github.com/edgedb/edgedb-js-lexer/pull/2/files#r484564585


getenv function prevents the hooks.json file from being parsed

Good Morning / Evening,
I'm having a strange issue where a sample code involving getting an environnement variable isn't working and throwing a YAML to JSON parsing error as you can see in the screenshot below.
Thank you very much for your assistance

It looks like you may be missing the -template command-line option, so webhook tries to read the config as JSON (which fails parsing due to the mismatched double-quotes) then as YAML (which it's clearly not) and finally yields an somewhat-unexpected YAML to JSON error.

Thank You so much , i spent quite the time re reading the documentation and i understood that i need the -template flag to parse and use the getenv function , thank you so much for the detailed explanation


Understand the decision logic to add a specific type import and update the method to know current set.

Currently when we add things via the component browser the import list gets duplicated (as a lot is exported in Standard.* anyway).
We want to understand how we determine whether or not to add to this list and improve logic.
from Standard.Base import all
from Standard.Base.Data.Boolean import Boolean
from Standard.Base.Data.Index_Sub_Range import Index_Sub_Range
from Standard.Base.Data.Ordering.Sort_Direction import Sort_Direction
import Standard.Base.Data.Text.Extensions
from Standard.Base.Data.Text.Text_Ordering import Text_Ordering
from Standard.Base.Errors.Problem_Behavior import Problem_Behavior
from Standard.Base.Network.HTTP.HTTP_Method import HTTP_Method
from Standard.Base.System.File.Existing_File_Behavior import Existing_File_Behavior
import Standard.Base.System.File.Write_Extensions
from Standard.Database.Data.Table import as Table
from Standard.Table import all
from Standard.Database import all
from Standard.Table.Data.Column import Column
from Standard.Table.Data.Column_Selector import Column_Selector
from Standard.Table.Data.Match_Columns import Match_Columns
from Standard.Table.Data.Table import Table
from Standard.Table.Data.Type.Value_Type import Value_Type
import Standard.Visualization

The Suggestion class has a reexport field that contains the shortest module (module with the shortest path) re-exporting this suggestion.
Initially, the suggestion is created with an empty reexport field. The field gets populated in the SuggestionsHandler https://github.com/enso-org/enso/blob/4ba8409defb01a698e606f4de0f9a76231b54419/engine/language-server/src/main/scala/org/enso/languageserver/search/SuggestionsHandler.scala#L487 when applying the database update and then sent to IDE as an update message.
After implementing the library suggestions cache, SuggestionsHandler no longer sets re-exports https://github.com/enso-org/enso/blob/4ba8409defb01a698e606f4de0f9a76231b54419/engine/language-server/src/main/scala/org/enso/languageserver/search/SuggestionsHandler.scala#L460-L471
The fix would be to set the suggestion reexport field when building the suggestions cache https://github.com/enso-org/enso/blob/4ba8409defb01a698e606f4de0f9a76231b54419/engine/runtime/src/main/scala/org/enso/compiler/SerializationManager.scala#L255-L257


Tensorflow Java API reliability/stability guaranties

Hello everyone
I want to use the TensorFlow Java API ( https://www.tensorflow.org/install/lang_java )
On the official page provided above it is stated that "Caution: The TensorFlow Java API is not covered by the TensorFlow API stability guarantees."
I have read the "TensorFlow API stability guarantees", googled little and still have the following questions:

If I will load the trained model with "TensorFlow Java API"  and it will not complain, can I be sure that the inferred output is correct, meaning that I would get the same output if I would load the model in python?
When the 2.3 release expected to happen so TensorFlow Java API will support tensorflow 2?

Thanks
Harut

@hbeybutyan
Apologies for the delay and I found similar issue #43335 where user has noticed slight difference in the result of model with TF version 1.15.2 in Python and libtensorflow-1.15.0.jar. but user tried Tensorflow version 1.x which is not actively supported.
TensorFlow Java has its own release cycle, independent from the TensorFlow runtime. Consequently, its version does not match the version of TensorFlow runtime it runs on. Consult the TensorFlow Java versioning table to list all versions available and their mapping with the TensorFlow runtime.
Could you please try TensorFlow/Java Version as per the versioning table and check your model is giving the same result with Tensorflow Java API and TF version in python ?
If issue still persists, in order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here and the dataset you are using ?
Thank you!

Hello @gaikwadrahul8
Thanks for your response.
Unfortunately I can not provide any details to you because I am not working on the project any more.
But I believe the question is clear by itself. Seems I just did not found the answer in documentation and wanted to make sure everything will work as expected.
I just requested a clarification on documentation.
Regards

Hi, @hbeybutyan
Thank you for the clarification and Apologies for the delayed response w.r.t your questions related with TensorFlow Java API is not covered by the TensorFlow API stability guarantees documentation so Could you please confirm if this issue is resolved for you ? Please feel free to close the issue if it is resolved ?
If you need any further assistance please let us know ?
Thank you!

Hello @gaikwadrahul8
Can you please try to answer the mentioned 2 questions?

If I will load the trained model with "TensorFlow Java API" and it will not complain, can I be sure that the inferred output is correct, meaning that I would get the same output if I would load the model in python?
When the 2.3 release expected to happen so TensorFlow Java API will support tensorflow 2?

Regards
Harut

Hi, @hbeybutyan
To be honest with you it's hard to say but some users experienced the difference in the output of TensorFlow Java API model and python model you can refer this one of our user comment, you can refer this version support table as per that table latest  TensorFlow Java Version(0.5.0-SNAPSHOT) supports TensorFlow Version :2.9.1 with Minimum Java Version :11
We recommend that you upgrade to the latest 2.x version and please let us know if the issue still persists in newer versions ?
Thank you!

Thanks @gaikwadrahul8


Setup actions like setup-python that depend on toolcache don't work

We've been experimenting with the runner controller and have run into problems trying to use setup actions to install tools not available on the default actions-runner image.  The README makes it sound like this is expected to work, but when we try to use actions/setup-python to install Python 3.8.6 we get errors like:
Run actions/setup-python@v2
Version 3.8 was not found in the local cache
Version 3.8 is available for downloading
Download from "https://github.com/actions/python-versions/releases/download/3.8.6-86952/python-3.8.6-linux-18.04-x64.tar.gz"
Extract downloaded archive
/bin/tar xz --warning=no-unknown-keyword -C /runner/_work/_temp/0f003edb-caff-4018-929e-3c2d946ee037 -f /runner/_work/_temp/0dd0919a-39a5-454f-be8b-fc95bb62f759
Execute installation script
Check if Python hostedtoolcache folder exist...
Creating Python hostedtoolcache folder...
Create Python 3.8.6 folder
Copy Python binaries to hostedtoolcache folder
Create additional symlinks (Required for the UsePythonVersion Azure Pipelines task and the setup-python GitHub Action)
Upgrading PIP...
##[error]./python: error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory
##[error]The process '/bin/bash' failed with exit code 127```

Experimenting with this, I have found that on the official Actions virtual environment images there are some environment variables and paths that are created to support the toolcache functionality in the setup actions.  It looks like the path `/opt/hostedtoolcache` is expected to exist with `777` permissions.

 If I manually run a bash prompt on the actions-runner image and create /opt/hostedtoolcache with 777 permissions, I'm then able to successfully run the setup.sh installation script as the `runner` user that is failing during setup-python.

It seems like this issue could be resolved by adding the folder creation and permissions to the actions-runner image, but I was curious if anyone else had run into this same issue and had a different fix before I filed a PR against the Dockerfile

Are you running GitHub Enterprise?

Yes

The version actions/setup-python@v2 that has been installed on your ghe is most likely an older version of whats currently on the main branch at https://github.com/actions/setup-python. My recommendation is to fork the repo to your ghe instance, check-out the action via actions/checkout@v2 and then invoke the main branch. Something like:
- name: Checkout YOUR_ORG/setup-python
      uses: actions/checkout@v2
      with:
        repository: YOUR_ORG/setup-python
        ref: main
        path: ./.github/actions/setup-python
        token: ${{ secrets.REPO_CHECKOUT_TOKEN }}

    - name: Setup python
      uses: ./.github/actions/setup-python
      with:
        python-version: '3.6.12'

Yep, I think you're right.  Our instance was 2 minor versions behind and the latest release included some fixes for GHES.  using actions-sync to pull the latest version to our instance solved the problem.
Thanks!


Move to PHP 7.2+, fix up all strict variable and parameter types

?
!

Type
improvement

BC Break
yes

Fixed issues
n/a

Summary
This PR sets the minimum requirement to PHP 7.2.
Introduce strictly typed parameters and return types.

@KristobalJunta I'd highly appreciate it if you could test this pretty big PR, to see if you run into any problems that could help put together a migration guide.
So if you have some time and a test environment for your bot, that would be awesome, thanks 😊

@noplanman sure!

@jacklul Would appreciate your feedback too, as time permits :pray:

@jacklul Would appreciate your feedback too, as time permits 🙏

I don't really have time to closely look into it other than to say that this is a good change and direction

@KristobalJunta Had a chance to try this yet? Any feedback?

@noplanman do we plan to release a major version?

@akalongman 1 step closer 😇

@noplanman I just took a quick view. Will test when I have free time. I think its important PR.
Whaqt do you think about PSR-12 coding standard?

Cool, thanks! Would be great to get this merged, as it's a big step forward.
I'm happy with PSR-12, but PSR-2 is great too. As long as everybody sticks to the same thing it works for me 😅
Wha do you ask?

@noplanman I want to send a PR with the reformatting of the codebase according to PSR-12. But first, let's make this PR merged. I'll review it in this week

@akalongman I thought it is already PSR-12 compliant 🤔
Anyways, I'll merge your latest PRs into this one, then you can take a look and do some testing.


Steady RF Carrier output?

Experiencing a steady RF Carrier, when pluged into USB?
Which functionality have LED 1..4?
Schematic?

Hi!
That's strange. Check my image:

Can you test this by connecting the device to an external battery? It is strange that Evil Crow RF generates that carrier.
About the leds... you can turn off/on them using these pins:

led_1 = io12
led_2 = io13
led_3 = io15

About the schematics, tell me your email and I will send you
Thanks!

Can you check this with this code?
#include <ELECHOUSE_CC1101_SRC_DRV.h>
#include <RCSwitch.h>
RCSwitch mySwitch = RCSwitch();
RCSwitch CC1101_1 = RCSwitch();
RCSwitch CC1101_2 = RCSwitch();
//CC1101 Pins
int sck = 18;
int miso = 19;
int mosi = 23;
int csn1 = 5;
int csn2 = 27;
int gdo0_1 = 2;
int gdo2_1 = 4;
int gdo0_2 = 25;
int gdo2_2 = 26;
void setup() {
Serial.begin(38400);
ELECHOUSE_cc1101.setSpiPin(sck, miso, mosi, csn1);
ELECHOUSE_cc1101.setMHZ(433.92);
ELECHOUSE_cc1101.Init();
CC1101_1.enableTransmit(gdo0_1);
ELECHOUSE_cc1101.SetTx();
CC1101_1.send(1648498, 24);
delay(3000);
CC1101_1.send(1648498, 24);
delay(3000);
ELECHOUSE_cc1101.SetRx();
}
void loop() {
}

Hi Joel,
thanks for that quick response. ;-)
I had overwritten the original flash-content and used your github-code, without modifications on the Elechouse-Lib.
I'll  check with your suggested testcode.
Thank you!
Juergen

Hi Joel,
thank you very much for your work & time.
My email-address:          @.*** @.***>
I would appreciate to get a schematic, to check the error. 😉
Might be,  that I haven’t  used the second Radio, by setting it to receive mode?
We‘ll try to use this device for our german Homeautomation-System FHEM (https://fhem.de/)  as RF-gateway-device.
thank you + regards,
Juergen
From: Joel Serna Moreno @.>
Sent: Thursday, May 6, 2021 12:19 AM
To: joelsernamoreno/EvilCrow-RF @.>
Cc: Jürgen @.>; Author @.>
Subject: Re: [joelsernamoreno/EvilCrow-RF] Steady RF Carrier output? (#3)
Can you check this with this code?
#include <ELECHOUSE_CC1101_SRC_DRV.h>
#include <RCSwitch.h>
RCSwitch mySwitch = RCSwitch();
RCSwitch CC1101_1 = RCSwitch();
RCSwitch CC1101_2 = RCSwitch();
//CC1101 Pins
int sck = 18;
int miso = 19;
int mosi = 23;
int csn1 = 5;
int csn2 = 27;
int gdo0_1 = 2;
int gdo2_1 = 4;
int gdo0_2 = 25;
int gdo2_2 = 26;
void setup() {
Serial.begin(38400);
ELECHOUSE_cc1101.setSpiPin(sck, miso, mosi, csn1);
ELECHOUSE_cc1101.setMHZ(433.92);
ELECHOUSE_cc1101.Init();
CC1101_1.enableTransmit(gdo0_1);
ELECHOUSE_cc1101.SetTx();
CC1101_1.send(1648498, 24);
delay(3000);
CC1101_1.send(1648498, 24);
delay(3000);
ELECHOUSE_cc1101.SetRx();
}
void loop() {
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/joelsernamoreno/EvilCrow-RF/issues/3#issuecomment-833086714 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2N6N6FLAEFRG2OFJYOIMTTMG75RANCNFSM44FX6AVA .  https://github.com/notifications/beacon/AA2N6NZXH3HVD7P3BMJA4KDTMG75RA5CNFSM44FX6AVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGGT6J6Q.gif

Hello!
This has nothing to do with setting up the second radio. You can use one radio or use both radios. For both radios to work correctly you need to use the libraries included in the libraries folder. These libraries have been modified to make the device work correctly.
Try the example I have sent you. Possibly the carrier you see is a problem of the basic firmware. I have talked to some colleagues who have Evil Crow RF and there is one friend who has this problem too.
If the example I sent you works and you don't get the carrier, I will tell you how to fix this in the basic firmware
I look forward to your reply :)
Thanks!

Other, but similar behavior: Carrier is there, but interrupted.

Can you try transmitting with the second module?

Yes. Receiving with original FW was not possible ... with obvious "powerful" traffic nearby ... (;-(

_ELECHOUSE_cc1101.setSpiPin(sck, miso, mosi, csn1);
ELECHOUSE_cc1101.setMHZ(433.92);
ELECHOUSE_cc1101.Init();
CC1101_1.enableTransmit(gdo0_1);
ELECHOUSE_cc1101.SetTx();
CC1101_1.send(1648498, 24);
delay(3000);
CC1101_1.send(1648498, 24);
delay(3000);
ELECHOUSE_cc1101.SetRx();
delay(3000);
ELECHOUSE_cc1101.setSpiPin(sck, miso, mosi, csn2);
ELECHOUSE_cc1101.setMHZ(433.92);
ELECHOUSE_cc1101.Init();
CC1101_2.enableTransmit(gdo0_2);
ELECHOUSE_cc1101.SetTx();
CC1101_2.send(1648498, 24);
delay(2000);
CC1101_2.send(1648498, 24);
delay(2000);
ELECHOUSE_cc1101.SetRx();_

Can't receive with the second module? For the second module to work you need to copy the libraries from the libraries folder (rcswitch and SmartRC) to your arduino libraries directory
About the schematics, check this: https://github.com/joelsernamoreno/EvilCrow-RF/tree/main/schematics
Can you try transmitting with the rfquack firmware and see if you get the carrier?

Thank you, i will check, but will take some time ...

Okay, let me know if you have any problems with RFQuack
It is strange that you see that carrier, this is why I would like you to try the RFQuack firmware. I want to know if this is a firmware problem or a hardware problem
If it is a hardware problem you will have to talk to the manufacturer to send you a new one. Right now they are out of stock, but hopefully they will have stock soon

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/sub-1-ghz-forum/872424/cc1101-how-to-send-unmodulated-carrier-using-cc1101
compiling .pio\build\rf\libbe6\SmartRC-CC1101-Driver-Lib\ELECHOUSE_CC1101_SRC_DRV.cpp.o
libraries\SmartRC-CC1101-Driver-Lib\ELECHOUSE_CC1101_SRC_DRV.cpp: In member function 'void ELECHOUSE_CC1101::setPA(int)':
libraries\SmartRC-CC1101-Driver-Lib\ELECHOUSE_CC1101_SRC_DRV.cpp:403:16: warning: 'a' may be used uninitialized in this function [-Wmaybe-uninitialized]
PA_TABLE[0] = a;
^

What do you want to tell me with this?

Anyway, can you tell me what SDR hardware you are using and what software? I will try to replicate your scenario
Example: hackrf with gqrx

SDRSharp community package (Win10): [(https://airspy.com/download/)]
and USB-DVBT-Stick.
May be the antennas position is to near to transceiver ?
2m away there are some carrier traces visible.

That should not affect
I have spoken to LSatan, it seems to be a library problem. This is the response from LSatan:
"yes i know the narrow carrier signal. we should set set setSidle after sending. or SetRx. that should fix the problem."
Try the rfquack firmware and tell me if the carrier is still there

Try the rfquack firmware and tell me if the carrier is still there.
I am searching all needed libs  ;-)
..\RFQuack\examples\RFQuack-esp32-CC1101-serial\src\main.cpp
..\RFQuack\src\radio

You can see the RFQuack section in my repository. In this section you have the steps to flash RFQuack in Evil Crow RF
https://github.com/joelsernamoreno/EvilCrow-RF/blob/main/README.md

Seems to work now:
ELECHOUSE_cc1101.setSpiPin(sck, miso, mosi, csn1);
ELECHOUSE_cc1101.setMHZ(433.92);
//*************************************
ELECHOUSE_cc1101.setPA(10);
//*************************************
ELECHOUSE_cc1101.Init();
CC1101_1.enableTransmit(gdo0_1);
ELECHOUSE_cc1101.SetTx();
CC1101_1.send(1648498, 24);
Serial.println("TX_1)");
delay(3000);
CC1101_1.send(1648498, 24);
Serial.println("TX_2)");
delay(3000);
CC1101_1.send(1648498, 24);
Serial.println("TX_3)");
delay(3000);
CC1101_1.send(1648498, 24);
Serial.println("TX_4)");
delay(3000);
ELECHOUSE_cc1101.SetRx();
delay(3000);
//---------------------------------------------------
... and set PKTLEN = 0xFF
//SpiWriteReg(CC1101_PKTLEN,   0x3D);
SpiWriteReg(CC1101_PKTLEN,   0xFF);

Well, I'll modify this in the repository library
The SmartRC library in my repository is version v2.3. I am using this version because I had to modify the library to make both CC1101 modules work at the same time. I have also made this modification in the latest version of SmartRC, but in the latest version the two radio modules do not work at the same time even though I modified the library.
When I have free time I will modify the spi register with your change. I think setPA(10) has nothing to do with that carrier. SetPA is for increasing the transmit power. Anyway, if you want to use the basic firmware from my repository you can add setPA in the code.
LSatan and I are trying to make the latest version of SmartRC compatible with Evil Crow RF, but we haven't managed to make both CC1101 modules work at the same time yet. If you want you can help on this
Let me know if I can close this issue. Thank you very much!

Thank you for your kind support!
RX is working, too     :-)
PartNum: 0
VERSION: 20
Module: 1
Frequency: 433.92
Bandwidth: 58.00
Received: 1648496 BIN:<PHONE_NUMBER>11101110000 / Codelen:24bitsProtocol: 5
Received: 1648496 BIN:<PHONE_NUMBER>11101110000 / Codelen:24bitsProtocol: 5
Received: 1648496 BIN:<PHONE_NUMBER>11101110000 / Codelen:24bitsProtocol: 5
Received: 1648498 BIN:<PHONE_NUMBER>11101110010 / Codelen:24bitsProtocol: 5

You can close this issue.

CC1101 modules work at the same time yet. If you want you can help on this
We have a 4 CC1101-module transceiver with Maplemini STM32F103 solution:
Take a look @:
[(https://github.com/Ralf9/SIGNALDuino/blob/dev-r412_cc1101/SIGNALDuino.ino) ]
for FHEM Homeautomation system.

Thanks!


NPE in MiniAccumuloClusterImplTest

The test passes but I saw this NullPointerException in the test output:

2022-01-26T07:42:15,439 [zookeeper.ClientCnxn] ERROR: Error while calling watcher
java.lang.NullPointerException: null
	at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:535) [zookeeper-3.5.9.jar:3.5.9]
	at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:510) [zookeeper-3.5.9.jar:3.5.9]

I have a fix incoming.


Provide an option for applyUnsafeFixes

Can you provide an option for biome check --apply-unsafe?

PR opened: #8


Begin migration to sphinx

Migrating https://sainsburywellcomecentre.github.io/software-skills/ to the NIU Sphinx theme to make it easier to work with in the future.

I've blindly copied some of the info from the old software skills site to this version based on the Sphinx theme. I'm not sure what the best way to structure it is. Ideally we would:

Have a single page for each course, that could be used to host materials etc
Keep previous versions of courses around
Allow people to discover new courses that may be run

On the previous site, each course was a page, and I copied and pasted to a new page when the course was re-ran. These pages were then organised under "Upcoming" and "Previous". I quite like this system, but the copying and pasting isn't great.
Anybody have any ideas how to structure this better? @niksirbi?

I think this has the basic structure sorted now (thanks @niksirbi, @lauraporta) and is ready to review. Additional content will be added as we have it.