Parsing TFRecords bug in TensorFlow v1.2

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS High Sierra 10.13
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): ('v1.2.0-rc2-21-g12f033d', '1.2.0')
Python version: 2.7.10
Bazel version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce: See below

Describe the problem
I believe there's a bug in TensorFlow v1.2. The code below runs fine in v1.4, while erroring out in v1.2. Here's the code:
filenames = ["gs://bucket/file.tfrecords"]
dataset = tf.contrib.data.TFRecordDataset(filenames)
parse_fn = lambda r: tf.parse_single_example(r, {"f1": tf.VarLenFeature(tf.int64)})
dataset.map(parse_fn)

Here's the stacktrace that I get:
TypeError                                 Traceback (most recent call last)
<ipython-input-42-0473d32d7931> in <module>()
----> 1 dataset.map(parser)

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/contrib/data/python/ops/dataset_ops.pyc in map(self, map_func, num_threads, output_buffer_size)
    811       A `Dataset`.
    812     """
--> 813     return MapDataset(self, map_func, num_threads, output_buffer_size)
    814
    815   def flat_map(self, map_func):

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/contrib/data/python/ops/dataset_ops.pyc in __init__(self, input_dataset, map_func, num_threads, output_buffer_size)
   1434
   1435     self._map_func = tf_map_func
-> 1436     self._map_func.add_to_graph(ops.get_default_graph())
   1437     if num_threads is not None:
   1438       self._num_threads = ops.convert_to_tensor(

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/python/framework/function.pyc in add_to_graph(self, g)
    617   def add_to_graph(self, g):
    618     """Adds this function into the graph g."""
--> 619     self._create_definition_if_needed()
    620
    621     # pylint: disable=protected-access

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/contrib/data/python/framework/function.pyc in _create_definition_if_needed(self)
    165       # Call func and gather the output tensors.
    166       with vs.variable_scope("", custom_getter=temp_graph.getvar):
--> 167         outputs = self._func(*inputs)
    168       # If func only returned one value, make it a tuple.
    169       if not isinstance(outputs, (list, tuple)):

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/contrib/data/python/ops/dataset_ops.pyc in tf_map_func(*args)
   1425
   1426       # Extract shape information from the returned values.
-> 1427       flattened_ret = [ops.convert_to_tensor(t) for t in nest.flatten(ret)]
   1428       self._output_shapes = nest.pack_sequence_as(
   1429           ret, [t.get_shape() for t in flattened_ret])

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/python/framework/ops.pyc in convert_to_tensor(value, dtype, name, preferred_dtype)
    674       name=name,
    675       preferred_dtype=preferred_dtype,
--> 676       as_ref=False)
    677
    678

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/python/framework/ops.pyc in internal_convert_to_tensor(value, dtype, name, as_ref, preferred_dtype)
    739
    740         if ret is None:
--> 741           ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
    742
    743         if ret is NotImplemented:

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/python/framework/constant_op.pyc in _constant_tensor_conversion_function(v, dtype, name, as_ref)
    111                                          as_ref=False):
    112   _ = as_ref
--> 113   return constant(v, dtype=dtype, name=name)
    114
    115

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/python/framework/constant_op.pyc in constant(value, dtype, shape, name, verify_shape)
    100   tensor_value = attr_value_pb2.AttrValue()
    101   tensor_value.tensor.CopyFrom(
--> 102       tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
    103   dtype_value = attr_value_pb2.AttrValue(type=tensor_value.tensor.dtype)
    104   const_tensor = g.create_op(

/Users/stypka/env/tf-1.2/lib/python2.7/site-packages/tensorflow/python/framework/tensor_util.pyc in make_tensor_proto(values, dtype, shape, verify_shape)
    460       raise TypeError("Failed to convert object of type %s to Tensor. "
    461                       "Contents: %s. Consider casting elements to a "
--> 462                       "supported type." % (type(values), values))
    463     tensor_proto.string_val.extend(str_values)
    464     return tensor_proto

TypeError: Failed to convert object of type <type 'dict'> to Tensor. Contents: {'f1': <tensorflow.python.framework.sparse_tensor.SparseTensor object at 0x117918410>}. Consider casting elements to a supported type.

And again, this works fine in TensorFlow v1.4.0rc0 that I tested.
Let me know if I should provide any more info!

The tf.contrib.data API in TF 1.2 doesn't support dictionaries as Dataset nested structures. This feature was added in TF 1.3. To work around it, you will need to convert the dictionary to a tuple or namedtuple.

thanks @mrry! Are you referring to #10151 with your answer? It seems to me as it's not about what the parsing function returns but rather what we pack into tf.parse_single_example().

Is that not-working in 1.2 or 1.4?

Fails in v1.2, works in v1.4 @mrry

Perhaps it's the list return value that's the problem. (I fixed an issue related to that in d001b58de9d0d99ef34637b9a9bed5763875f655, which is only in the TF 1.4 release.) Can you try changing parse_fn to the following?
parse_fn = lambda r: tuple([tf.parse_single_example(r, {"f1": tf.VarLenFeature(tf.int64)})])

also breaks @mrry, the same error. It seems to not matter whether I return a list, tuple or a dict. Can you reproduce it?
I can also try in TF v1.3 if that would be helpful

The code doesn't work in tf-nightly for me. What code did you run that works in TF 1.4?
FWIW, the failure in tf-nightly is due to the current lack of tf.SparseTensor support. See this Stack Overflow answer for some workarounds:
https://stackoverflow.com/a/46732695/3574081

@mrry

Can you point me to some guide how to load TFRecords in TF1.2? I imagine it's quite a standard procedure and I don't want to do anything fancy. The ml-engine clusters run only v1.2, so I need to work with this version.

The 1.4 code is different: it uses a tf.FixedLenFeature named "mau_d180", whereas the code you're trying in 1.2 uses a tf.VarLenFeature named "f1".
The FixedLenFeature code should work in 1.2 if you convert the return type to a tuple. The VarLenFeature code won't work in either version until we add tf.SparseTensor support.
For common cases, the tf.contrib.data.read_batch_features() function (available in TF 1.2 and 1.4) should work, even with tf.SparseTensor-valued features.

It doesn't seem to work in v1.2. You're right that the code is slightly different - I simplified it for the sake of the example (named the variable f1 and used tf.VarLenFeature), but this shouldn't change the behaviour.
@mrry - I can check TF v1.3 tomorrow morning, I'm in the European timezone.

Can you share the whole 1.2 traceback?
I think you'll need to rewrite parser() as follows to work on TF 1.2:
def parser(record):
  return tf.parse_single_example(record, {"f1": tf.FixedLenFeature([], tf.int64)})["f1"]

If you have more than one feature, you'll need to extract the values from the dictionary in some consistent order, and create a tuple by hand.
While switching between tf.FixedLenFeature and tf.VarLenFeature might not seem like a significant difference, it changes the return type from something that Dataset currently supports (tf.Tensor) to something that it currently doesn't (tf.SparseTensor). It'd be great to separate these two issues!

Make sense! The code that you gave works - I will probably have tens of features, so it might get quite awkward to build all of that by hand.
Final question - what's the recommended and suggested way moving forward? Should I not use TFRecords and maybe move to CSV? Or should I use the read_batch_features() function that you suggested? My usecase is not special in any way and I also control the serialisation code.
Thanks for the help annyway @mrry! I'll get you a beer if you're around Stockholm at any point

I'd suggest trying read_batch_features()... it'll work in the older version of TF, and make it easier to deal with multiple (potentially sparse) features. It's also got a pretty simple implementation on top of standard Dataset transformations, so it's pretty hackable if you end up needing something different (just copy the code to your own project and customize it as necessary).

Seems to work well, the read_batch_features() is what I was looking for. It's nowhere in the docs, if you didn't tell me, I wouldn't find it. Maybe it would not be a bad idea to include it somewhere in the docs/tutorials, so that other people don't go my path.
Cheers!


add AppID field to ListCheckRunsOptions

Both https://docs.github.com/en/rest/reference/checks#list-check-runs-for-a-git-reference and  https://docs.github.com/en/rest/reference/checks#list-check-suites-for-a-git-reference endpoints document the following query parameter:

Name
Type
In
Description

app_id
integer
query
Filters check suites by GitHub App id.

(Though the former is missing a description; perhaps it was added at a different time.)
The ListCheckSuiteOptions struct already has this field:
https://github.com/google/go-github/blob/fef3638524ab6c27e005edbe752c35b37f85894d/github/checks.go#L298
I wanted to report that there's an opportunity to add it to the ListCheckRunsOptions struct for listing check runs, because it's not there yet:
https://github.com/google/go-github/blob/fef3638524ab6c27e005edbe752c35b37f85894d/github/checks.go#L232-L239

Hi I can help out.

Hi I can help out.

Great, thank you, @rojanDinc !  It's yours.


Broken??

The AUR package fails to build.
rm: cannot remove
'/home/parzival/.cache/paru/clone/wifi4wofi/pkg/wifi4wofi/usr/bin/wifi4wofi':
Permission denied

==> ERROR: An unknown error has occurred. Exiting...
error: failed to build 'wifi4wofi-0.5.1-1':

It's been removed from the AUR.


⚠ Samsung has degraded performance

In d24d80b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2451 ms

Resolved: Samsung performance has improved in 02ac00c.


MMR is showed incorrectly

http://steamcommunity.com/id/phoenixdd28/
https://www.opendota.com/players/64126565
Gained +25 aren't added to solo mmr counter. Nevertheless, match can be seen through my opendota profile and mmr is displayed in dota 2 profile. Is it possible to fix?
P.S. the same problem with party mmr stuff. I have lost game but party mmr counter on the opendota says that i didn't.
MMR changes for last games aren't represented.

Valve sometimes doesn't update the MMR value for a while after the match is played.  It should update eventually after you finish another game.


Update FlowSensor.cpp

Hi Hafidhh
I have tested your library on an Arduino Leonardo Board, more exactly and Arduino Things Uno Board based on Arduino Leonardo architecture, and interrupt has not been working.
Researching for possible causes, i found that Interrupt Pin versus Interrupt Number, is not fixed on all boards, and arduino recommend to use the translation funcion   attachInterrupt(digitalPinToInterrupt(this->_pin) as mentionated here https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/
I tested now and is working!
I hope this can help other users.
Best Regards
@hugojorgemuller

Thanks for fixing the error.
I haven't tried on Arduino Leonardo yet.

Hi Hafidhh
Thanks by the merge!.
I´m working with the library and a ThingsUno Board (simil UNO but Leonardo Core) and making suggestions to improve.
Regards
Hugo


Strong mode top level inference regression

The test code below passes the dart analyzer in strong mode with no errors in version 1.23.0-dev.0.0 .  In version 1.23.0-dev.1.0, the field m fails to be inferred as MyList<int>, and a downcast composite is reported on the assignment in main.
class MyList<T> {
  final List<T> _list;
  MyList(List<T> list) : _list = list;
}

class Test {
  final m = new MyList([0]);
}

void main() {
  Test test;
  MyList<int> list = test.m;
}

cc @scheglov @stereotype441
I see some commits in the range between those two tags related to turning off the task model which make me wonder if we switched over to a different implementation of top level inference?

Yes, analyzer_cli was switched to using the new analysis driver, which uses summary based type inference.

I see this in Intellij pointed at bleeding edge as well, so presumably also there?

Yes, Analysis Server was switched to using the new analysis driver since the very beginning of 1.23.

@scheglov Is this a result of replacing the task model? If so, do you know what step(s) are missing in the new code?

Inference for instantiation was not implemented in linker.
I'm working on this now.

Fix for processing invokeConstructor.
https://codereview.chromium.org/2711733003

Fix for constructors with field formal parameters.
https://codereview.chromium.org/2710943007

I think this is fixed now.
https://github.com/dart-lang/sdk/commit/02da0fb1dda0a04f78e211c77c96ee1581c6a907

Great, thanks!


Disabling the receive buffer warning?

I'm using quic-go in a command line app that makes a few network requests - nothing performance sensitive. As expected, the receive buffer warning is printed and interferes with the output the user is expecting:
2022/03/02 16:24:42 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.

Would you be open to accepting a PR from me that exposes a bool to disable the warning? Users of quic-go could call:
quic.DisableReceiveBufferWarning = true

And then quic-go would check that bool in the function passed to the sync.Once that prints the warning.

Not opposed to this, but I think I'd prefer this to be an environment variable. Would that work for you?

An environment variable would also work. What about QUIC_DISABLE_RECEIVE_BUFFER_WARNING? I'm not attached to it. Just a suggestion.

No objections to that.


Remove incomplete banner

deleted isIncomplete, but what do i need to do to delete this banner too?

cc @antooni

@lucadonnoh I think this is the copy that we have on every bridge page, please contact @luke7211 whether we want to remove it or make it conditional on some pages

i quickly skimmed through the code and it looked conditional, could you please check that this is not the case?

i quickly skimmed through the code and it looked conditional, could you please check that this is not the case?

This is coming from here: https://github.com/l2beat/l2beat/blob/f7692f6a271c095f4d4c950e072ce0e335be33e2/packages/frontend/src/pages/bridges-projects/props/getTechnologyOverview.ts#L39.
There's a bug (fixed by https://github.com/l2beat/l2beat/pull/1644). After merging this PR, it should work as expected.


Default of maxPollingInterval

Default maxPollingInterval is 1 minute while in the documentation about it is 1 second.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5063120f-d48e-6a76-8e6d-208ead92d187
Version Independent ID: 72bb8ecc-6dec-079a-a9d4-52205466a8c6
Content: Azure Queue storage bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-storage-queue.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hi @himalpatel81 Thank you for your feedback! We will review and update as appropriate.

What time?

On 30 tháng 5 năm 2019 at 1:05 SA,    wrote:
Hi  @himalpatel81  Thank you for your feedback! We will review and update as appropriate.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,   view it on GitHub, or   mute the thread.

@himalpatel81 Polling interval increments up to 1min, as explained here, so existing documentation stating the starting time as 100ms seems valid.

@himalpatel81 Thank you for pointing this out and helping us drive improvements towards MS Docs! We have updated the specific section to clarify better that the polling interval starts from 100ms and increments up to 1min. We will now proceed to close this thread for now. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Hi Mike,
PropertyDefaultDescription
maxPollingInterval 00:00:01
As per this, it says that the default max polling interval is 1 second.
which is not true. Default is 1 minute.
On Tue, Jun 4, 2019 at 6:03 AM Mike Urnun<EMAIL_ADDRESS>wrote:

Closed #32311 https://github.com/MicrosoftDocs/azure-docs/issues/32311.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/32311?email_source=notifications&email_token=ADRA3RK3KVTUR7KDBZLUGDDPYV2IVA5CNFSM4HQJARW2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORY4FD4Y#event-2386055667,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADRA3RPD2XTZZXFIC4KUSIDPYV2IVANCNFSM4HQJARWQ
.

And what is the behavior of the auto increment if someone change that value?
I mean what if I change the default value to 1 minute, is it going to increment up to 2 minutes, 10 minutes or does not increment at all?
Is it possible to disable this auto increment if we want a predictable behavior, like if I mean to keep the polling as low as possible for maximum system responsiveness?

Based on the documentation maxPollingInterval default value is 1 second.
which means maximum it will wait between polling is 1 second. however that
is not true. It is 1 minute. so the value default value in the
documentation should be "00:01:00".
The functionality of maxPollingInterval is working as expected in all the
case.
On Tue, Jun 4, 2019 at 11:11 PM Guillaume Girard<EMAIL_ADDRESS>wrote:

And what is the behavior of the auto increment if someone change that
value?
I mean what if I change the default value to 1 minute, is it going to
increment up to 2 minutes, 10 minutes or does not increment at all?
Is it possible to disable this auto increment if we want a predictable
behavior, like if I mean to keep the polling as low as possible for maximum
system responsiveness?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/32311?email_source=notifications&email_token=ADRA3RPC4YFAXQR5KHTFNS3PYZSYZA5CNFSM4HQJARW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW4QNGY#issuecomment-498665115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADRA3RNPSPEJU7FBD7IJKW3PYZSYZANCNFSM4HQJARWQ
.


separate layer hash fetches and layer block data fetches

Motivation
Closes #2523
Changes
separate layer hash fetches and block data fetches. this will allow us to resolve hash difference with peers before actually fetching block data.
Test Plan
unit tests
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

bors try

bors merge

bors merge


Steam-run: many symbol lookup error, undefined symbol

Describe the bug
Since yesterday, steam-run is giving me strange errors. For example, when I start steam-run I get an error:
$ steam-run bash
/nix/store/mbrhnpc8a5kh5pyp92hnfbnlyywp5qdx-gnupg-2.2.23/bin/gpg-connect-agent: symbol lookup error: /lib64/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
bash-4.4$

Also, I cannot run Natron anymore while before it was working fine:
$ QT_X11_NO_MITSHM=1 steam-run ./Natron
/home/leo/Documents/Logiciels/Multimedia/Natron/bin/Natron: symbol lookup error: /lib64/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var

and I also experienced strange issues with appimage-run, so not sure if it's related https://github.com/NixOS/nixpkgs/issues/104614.
To Reproduce
Steps to reproduce the behavior:

On NixOs 20.09, install steam-run and type:

$ steam-run bash

or download Natron's portable on this page, extract, and run:
QT_X11_NO_MITSHM=1 steam-run ./Natron

I'm not sure if it's relevant, but I've emacs installed from unstable, most of my system installed from 20.09, commit 58f9c4c7d3a, and a few packages are installed from 20.03 commit f05c380a51da (kmymoney, kdenlive, and sageWithDoc).
Expected behavior
I don't expect to see errors about undefined symbols.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
warning: unknown setting 'extra-sandbox-paths'
warning: unknown setting 'extra-sandbox-paths'

system: "x86_64-linux"
host os: Linux 5.4.77, NixOS, 21.03pre-git (Okapi)
multi-user?: yes
sandbox: yes
warning: unknown setting 'extra-sandbox-paths'
version: nix-env (Nix) 2.4pre20201102_550e11f
warning: unknown setting 'extra-sandbox-paths'
channels(root): "nixos-20.09.1984.9da0758c1cd, nixos-unstable-21.03pre253060.a322b32e9d7"
warning: unknown setting 'extra-sandbox-paths'
channels(me): "home-manager, nixos-unstable-21.03pre250162.34ad166a830"
warning: unknown setting 'extra-sandbox-paths'
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

-- EDIT --
I just tried to install instead an older steam-run, coming from 20.03, and it work (well, better). I just have an issue after Natron starts, since it gives errors about missing drivers, but I'm thinking that it may be related to this since the driver's version is different from the version required by steam-run. Anyway, this means that the issue with symbols is only in recent version of steam-run.
$ LIBGL_DEBUG=verbose QT_X11_NO_MITSHM=1 steam-run ./Natron
Fontconfig warning: "/etc/fonts/2.11/fonts.conf", line 5: unknown element "description"
Fontconfig error: "/etc/fonts/2.11/fonts.conf", line 5: invalid attribute 'domain'
Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/40-nonlatin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/45-generic.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/49-sansserif.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/51-local.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/60-generic.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/60-latin.conf", line 4: unknown element "description"
Fontconfig warning: "/etc/fonts/conf.d/65-nonlatin.conf", line 4: unknown element "description"
Fontconfig error: Cannot load config file from /etc/fonts/2.11/fonts.conf
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: using driver i915 for 7
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: using driver i915 for 7
libGL: pci id for fd 7: 8086:3ea0, driver iris
libGL: MESA-LOADER: failed to open /run/opengl-driver/lib/dri/iris_dri.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /run/opengl-driver/lib/dri/iris_dri.so)
libGL error: MESA-LOADER: failed to open iris (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: iris
libGL: using driver i915 for 7
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: using driver i915 for 7
libGL: pci id for fd 7: 8086:3ea0, driver iris
libGL: MESA-LOADER: failed to open /run/opengl-driver/lib/dri/iris_dri.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /run/opengl-driver/lib/dri/iris_dri.so)
libGL error: MESA-LOADER: failed to open iris (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: iris
libGL: MESA-LOADER: failed to open /run/opengl-driver/lib/dri/swrast_dri.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /run/opengl-driver/lib/dri/swrast_dri.so)
libGL error: MESA-LOADER: failed to open swrast (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: swrast
X Error: GLXBadContext 158
  Extension:    152 (Uknown extension)
  Minor opcode: 6 (Unknown request)
  Resource id:  0x6200044
X Error: BadValue (integer parameter out of range for operation) 2
  Extension:    152 (Uknown extension)
  Minor opcode: 3 (Unknown request)
  Resource id:  0x0
X Error: GLXBadContext 158
  Extension:    152 (Uknown extension)
  Minor opcode: 6 (Unknown request)
  Resource id:  0x620008e
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
Natron: xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
/home/me/Natron : ligne 31 :  4860 Aborted                 (core dumped)$DIR/bin/Natron -style fusion $*

So in latest unstable, I don't have any symbol lookup error... But Natron now segfault (except that it ) while it works fine with 20.03.
LIBGL_DEBUG=verbose QT_X11_NO_MITSHM=1 steam-run ./Natron
Natron Version 2.3.15
Copyright (C) 2013-2018 INRIA and Alexandre Gauthier-Foichat
>>>Use the --help or -h option to print usage.<<<
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: using driver i915 for 4
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: using driver i915 for 4
libGL: pci id for fd 4: 8086:3ea0, driver iris
libGL: MESA-LOADER: failed to open /run/opengl-driver/lib/dri/iris_dri.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /run/opengl-driver/lib/dri/iris_dri.so)
libGL error: MESA-LOADER: failed to open iris (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: iris
libGL: using driver i915 for 4
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: using driver i915 for 4
libGL: pci id for fd 4: 8086:3ea0, driver iris
libGL: MESA-LOADER: failed to open /run/opengl-driver/lib/dri/iris_dri.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /run/opengl-driver/lib/dri/iris_dri.so)
libGL error: MESA-LOADER: failed to open iris (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: iris
libGL: MESA-LOADER: failed to open /run/opengl-driver/lib/dri/swrast_dri.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /run/opengl-driver/lib/dri/swrast_dri.so)
libGL error: MESA-LOADER: failed to open swrast (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: swrast
Error while loading OpenGL: GLX: Failed to create context
OpenGL rendering is disabled.
GLX: Failed to create context
GLX: Failed to create context
Caught segmentation fault (SIGSEGV) from thread Main(0x343fa10), faulty address is 0x7fc539fa598d from 0x3f8
Segmentation fault (core dumped)

However, even glxinfo fails:
$ nix run nixpkgs.glxinfo -c glxinfo
name of display: :0
libGL error: MESA-LOADER: failed to open iris (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open iris (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: iris
libGL error: MESA-LOADER: failed to open swrast (search paths /run/opengl-driver/lib/dri)
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  60
  Current serial number in output stream:  59

So I guess it's not linked with the original issue at all, so I'll close it.


How to use TF.data.Dataset for relational database like nuScenes

System information

TensorFlow version (you are using): tensorflow==2.5.0 (pip installed, Ubuntu 20.04, CUDA 11.)

Describe the feature and the current behavior/state.
tf.data.Dataset is excellent while implementing the data-pipeline, with map, shuffle, batch and prefetch (inducing AUTOTUNE features) . But currently the relational database like nuScenes (https://www.nuscenes.org/nuscenes#data-format). has difficulty to implement with multiple sensor data like camera images and pointCloud's. Please guide or inform the steps to be taken, with examples.
Will this change the current api? How?
Who will benefit with this feature?
All relational database like nuScenes can use the tf.data.Dataset and also perform better while using the distributed training.

@RRK13,
Have you got the chance to have a look at this tf.data.experimental.SqlDataset API which allows you to read data from a relational database using a SQL query. It is currently only supported for SQLite databases.
https://www.tensorflow.org/api_docs/python/tf/data/experimental/SqlDataset
dataset = tf.data.experimental.SqlDataset(
    driver_name="sqlite",
    data_source_name="/path/database.sqlite3",
    query="SELECT name, age FROM people",
    output_type=(tf.string, tf.int32),
)

Thank you!


[CMake] fatal error: 'nsync_time_init.h' file not found on mac

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Darwin T-X.local 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar  3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
TensorFlow installed from (source or binary):
Source.
TensorFlow version (use command below):
Not applicable. Happens during build.
Python version:
Not applicable. Happens during build.
Bazel version (if compiling from source):
Not applicable. Compiling directory tensorflow/contrib/cmake using CMake 3.7.2 and clang Apple LLVM version 8.1.0 (clang-802.0.42).
CUDA/cuDNN version:
Not applicable.
GPU model and memory:
Not applicable.
Exact command to reproduce:
cmake --build /Users/kasper/Development/tensorflow_pr/tensorflow/contrib/cmake --target all -- -j 8

Describe the problem
This is a bug related to the CMake build of TensorFlow which fails on my system due to an error with the nsync build. The nsync build seems to not include some headers (see below). I have tested with TensorFlow v1.0.0, v1.1.0, v1.2.0 and the current master branch. I have not been able to investigate the nsync error because a standalone nsync build (i.e. clone->cmake->make) fails at an earlier step (/Users/kasper/Development/nsync/platform/macos/platform.h:35:13: error: typedef redefinition with different types ('int' vs 'enum clockid_t') typedef int clockid_t;). Unfortunately, I have not been able to submit an issue to https://github.com/google/nsync and resolve this problem because issues are disabled for this repository.
Source code / logs
[ 46%] Building CXX object CMakeFiles/nsync.dir/platform/c++11/src/time_rep_timespec.cc.o
no
/Users/kasper/Development/TensorFlowImageFilter/SuperBuild/cmake-build-debug/TensorFlow-build/nsync/src/nsync/platform/c++11/src/time_rep_timespec.cc:19:10: fatal error: 'nsync_time_init.h' file not found
#include "nsync_time_init.h"

Manually copying nsync_time_init.h from nsync/platform/posix to nsync/platform/macos fixes the issue. Closing since this is not a TensorFlow issue. Pinging @m3bm3b.

@m3bm3b The issue is still present in TensorFlow 1.4. Are you interested in a PR?

Beware that the cmake build is not fully supported
and not routinely tested on MacOS.
The cmake build is there mostly for Windows.
However, at least for that particular error
'nsync_time_init.h' file not found
the current master branch of TensorFlow should
get past that point in the build.
The key difference from 1.4 that should fix the issue is in the file
tensorflow/contrib/cmake/patches/nsync/CMakeLists.txt
and especially (new) line 64 of that file.

Okay, many thanks for the update! Appreciated.


[BEAM-13498] [BEAM-13573] exclude new tests on Flink

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Flink ValidatesRunner

Run Flink ValidatesRunner

R: @y1chi


SuperpermsListener causing onPlayerLogin lag

Hey,
I've come across an issue where the SuperpermsListner causes lagspikes/delays when a player logins. The joining player either suffers from a long login time or eventually gets a timeout.
I've included the timings report as well.

Seeing this
http://timings.aikar.co/?url=12792792
On 1.23.3

Same as rlf.
http://timings.aikar.co/?url=13209806


Data Race in CI

Please answer these questions before submitting your issue. Thanks!

What did you do?
If possible, provide a recipe for reproducing the error.

What did you expect to see?

pass test

What did you see instead?

https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/pd_test/detail/pd_test/2556/pipeline
https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/pd_test/detail/pd_test/2552/pipeline/
https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/pd_test/detail/pd_test/2533/pipeline/
[2019-11-05T05:53:38.717Z] WARNING: DATA RACE

[2019-11-05T05:53:38.717Z] Write at 0x00c008d0e100 by goroutine 519:

[2019-11-05T05:53:38.717Z]   github.com/pingcap/pd/server.(*Server).startEtcd()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/src/github.com/pingcap/pd/server/server.go:203 +0x12d5

[2019-11-05T05:53:38.717Z]   github.com/pingcap/pd/server.(*Server).Run()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/src/github.com/pingcap/pd/server/server.go:298 +0x94

[2019-11-05T05:53:38.717Z]   github.com/pingcap/pd/server/api.(*testVersionSuite).TestGetVersion.func2()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/src/github.com/pingcap/pd/server/api/version_test.go:61 +0x1db

[2019-11-05T05:53:38.717Z]   github.com/pingcap/failpoint.parseTerm()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/failpoint@v0.0.0-20190512135322-30cc7431d99c/terms.go:154 +0x24d

[2019-11-05T05:53:38.717Z]   github.com/pingcap/failpoint.parse()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/failpoint@v0.0.0-20190512135322-30cc7431d99c/terms.go:129 +0xa9

[2019-11-05T05:53:38.717Z]   github.com/pingcap/failpoint.newTerms()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/failpoint@v0.0.0-20190512135322-30cc7431d99c/terms.go:101 +0x6a

[2019-11-05T05:53:38.717Z]   github.com/pingcap/failpoint.enableAndLock()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/failpoint@v0.0.0-20190512135322-30cc7431d99c/runtime.go:95 +0x11b

[2019-11-05T05:53:38.717Z]   github.com/pingcap/failpoint.Enable()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/failpoint@v0.0.0-20190512135322-30cc7431d99c/runtime.go:77 +0x5a

[2019-11-05T05:53:38.717Z]   github.com/pingcap/pd/server/api.(*testVersionSuite).TestGetVersion.func2()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/src/github.com/pingcap/pd/server/api/version_test.go:59 +0x11d

[2019-11-05T05:53:38.717Z]

[2019-11-05T05:53:38.717Z] Previous read at 0x00c008d0e100 by goroutine 298:

[2019-11-05T05:53:38.717Z]   github.com/pingcap/pd/server/api.(*redirector).ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/src/github.com/pingcap/pd/server/server.go:474 +0x700

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.middleware.ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:38 +0x116

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.(*Negroni).ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:96 +0x17b

[2019-11-05T05:53:38.717Z]   github.com/gorilla/mux.(*Router).ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/gorilla/mux@v1.6.1/mux.go:159 +0x17f

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.Wrap.func1()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:46 +0x68

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.HandlerFunc.ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:29 +0x5b

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.middleware.ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:38 +0x116

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.middleware.ServeHTTP-fm()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:37 +0x71

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.(*Recovery).ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/recovery.go:193 +0x99

[2019-11-05T05:53:38.717Z]   github.com/urfave/negroni.middleware.ServeHTTP()

[2019-11-05T05:53:38.717Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:38 +0x116

[2019-11-05T05:53:38.718Z]   github.com/urfave/negroni.(*Negroni).ServeHTTP()

[2019-11-05T05:53:38.718Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/urfave/negroni@v0.3.0/negroni.go:96 +0x17b

[2019-11-05T05:53:38.718Z]   net/http.(*ServeMux).ServeHTTP()

[2019-11-05T05:53:38.718Z]       /usr/local/go/src/net/http/server.go:2375 +0x28a

[2019-11-05T05:53:38.718Z]   go.etcd.io/etcd/embed.(*accessController).ServeHTTP()

[2019-11-05T05:53:38.718Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/go.etcd.io/etcd@v0.0.0-20190320044326-77d4b742cdbf/embed/serve.go:359 +0x3f3

[2019-11-05T05:53:38.718Z]   net/http.serverHandler.ServeHTTP()

[2019-11-05T05:53:38.718Z]       /usr/local/go/src/net/http/server.go:2774 +0xc4

[2019-11-05T05:53:38.718Z]   net/http.(*conn).serve()

[2019-11-05T05:53:38.718Z]       /usr/local/go/src/net/http/server.go:1878 +0x807

[2019-11-05T05:53:38.718Z]

[2019-11-05T05:53:38.718Z] Goroutine 519 (running) created at:

[2019-11-05T05:53:38.718Z]   github.com/pingcap/pd/server/api.(*testVersionSuite).TestGetVersion()

[2019-11-05T05:53:38.718Z]       /home/jenkins/agent/workspace/pd_test/go/src/github.com/pingcap/pd/server/api/version_test.go:56 +0x2c4

[2019-11-05T05:53:38.718Z]   runtime.call32()

[2019-11-05T05:53:38.718Z]       /usr/local/go/src/runtime/asm_amd64.s:519 +0x3a

[2019-11-05T05:53:38.718Z]   reflect.Value.Call()

[2019-11-05T05:53:38.718Z]       /usr/local/go/src/reflect/value.go:308 +0xc0

[2019-11-05T05:53:38.718Z]   github.com/pingcap/check.(*suiteRunner).forkTest.func1()

[2019-11-05T05:53:38.718Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/check@v0.0.0-20190102082844-67f458068fc8/check.go:836 +0x9fc

[2019-11-05T05:53:38.718Z]   github.com/pingcap/check.(*suiteRunner).forkCall.func1()

[2019-11-05T05:53:38.718Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/github.com/pingcap/check@v0.0.0-20190102082844-67f458068fc8/check.go:730 +0xb7

[2019-11-05T05:53:38.718Z]

[2019-11-05T05:53:38.718Z] Goroutine 298 (finished) created at:

[2019-11-05T05:53:38.718Z]   net/http.(*Server).Serve()

[2019-11-05T05:53:38.718Z]       /usr/local/go/src/net/http/server.go:2884 +0x4c4

[2019-11-05T05:53:38.718Z]   go.etcd.io/etcd/embed.(*serveCtx).serve.func3()

[2019-11-05T05:53:38.718Z]       /home/jenkins/agent/workspace/pd_test/go/pkg/mod/go.etcd.io/etcd@v0.0.0-20190320044326-77d4b742cdbf/embed/serve.go:135 +0x4c

Can we skip this test temporally? Seems it fails a lot :(


WSPR not decoding in WSJT-X

I'm trying to test the new WSPR function on 2m and have only had one transmission successfully demodulated by WSJT-X. I'm receiving the signal using a SDR in my garage, which is a proven setup for other experiments.
There appears to be some frequency drift - I wonder if this is causing issues with demodulation. I have tried various gain and volume settings with no improvement. Are others experiencing similar issues?

First of all, congratulations on your one-time decoding.
1.WSPR at 2M requires both transmission and reception to be stable.
Frequencies are multiplied, so higher frequencies produce drift.
For reference, my old device IC-706 cannot receive 2M WSPR. However,
FT-817, FT-857, etc. can be received.
2.If you are too close, the signal may be too loud. When testing at close
range, try using the minimum output. If you have a dummy load, try
connecting the dummy load.
Ian KD8CEC
On Thu, Mar 28, 2024 at 11:37 PM tristanmoney @.***>
wrote:

I'm trying to test the new WSPR function on 2m and have only had one
transmission successfully demodulated by WSJT-X. I'm receiving the signal
using a SDR in my garage, which is a proven setup for other experiments.
There appears to be some frequency drift - I wonder if this is causing
issues with demodulation. I have tried various gain and volume settings
with no improvement. Are others experiencing similar issues?
image.png (view on web)
https://github.com/phdlee/uvk5cec/assets/54490270/ba02eedb-9b9e-4ab5-86b2-fa75703c160e
—
Reply to this email directly, view it on GitHub
https://github.com/phdlee/uvk5cec/issues/45, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4DZPC7WZWSYKHOZAFIVV3Y2QTMBAVCNFSM6AAAAABFM5DEG6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIYTGNBQGY3DOMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I tried a dummy load and also receiving using another UV-K5(8) and an AIOC for audio interface instead of the SDR. Unfortunately still no transmissions showing up in WSJT-X. Also tried a different UV-K5(8) for transmit but no change.
I will continue testing when I have more time.

It works reliably now - I guess the tone needs to be between 1400 and 1600 Hz to be decoded. I was trying 700, 400, and 1000 Hz but those won't work! I will try it out at a distance with an antenna tomorrow.


Fixing another deserialization backwards compatability problem

Continuation of https://github.com/keras-team/keras/pull/8762.
I made a dumb mistake in my previous fix to this: I put a try/except around the acsii encoding/base64 decoding... unfortunately some strings encoded in the old format pass this without raising an except but then cannot be unpacked by marshall (marshall.load raises a ValueError).  One simple example of this is lambda x:x -- I added this case to the unit test.  Note that this is actually not a contrived example, we had some older models with Lambda layers where output_shape=lambda x:x and they were not deserialize-able with 2.1.3 due to this issue.

Hi @bbabenko , I can see the fix you have done on deseralization but I am facing the same issue. Here are the error logs.
I am trying to load these weights but getting error. I think these below weights trained in Keras 1.x.x and I am using Keras 2.1.6 - https://s3.amazonaws.com/stratospark/food-101/model4b.10-0.68.hdf5
LOGS
loaded_model = load_model('model/model4b.10-0.68.hdf5')
File "/usr/local/lib/python2.7/site-packages/keras/models.py", line 270, in load_model
model = model_from_config(model_config, custom_objects=custom_objects)
File "/usr/local/lib/python2.7/site-packages/keras/models.py", line 347, in model_from_config
return layer_module.deserialize(config, custom_objects=custom_objects)
File "/usr/local/lib/python2.7/site-packages/keras/layers/init.py", line 55, in deserialize
printable_module_name='layer')
File "/usr/local/lib/python2.7/site-packages/keras/utils/generic_utils.py", line 144, in deserialize_keras_object
list(custom_objects.items())))
File "/usr/local/lib/python2.7/site-packages/keras/engine/topology.py", line 2525, in from_config
process_layer(layer_data)
File "/usr/local/lib/python2.7/site-packages/keras/engine/topology.py", line 2511, in process_layer
custom_objects=custom_objects)
File "/usr/local/lib/python2.7/site-packages/keras/layers/init.py", line 55, in deserialize
printable_module_name='layer')
File "/usr/local/lib/python2.7/site-packages/keras/utils/generic_utils.py", line 146, in deserialize_keras_object
return cls.from_config(config['config'])
File "/usr/local/lib/python2.7/site-packages/keras/engine/topology.py", line 1271, in from_config
return cls(**config)
File "/usr/local/lib/python2.7/site-packages/keras/legacy/interfaces.py", line 91, in wrapper
return func(*args, **kwargs)
File "/usr/local/lib/python2.7/site-packages/keras/layers/core.py", line 848, in init
self.kernel_regularizer = regularizers.get(kernel_regularizer)
File "/usr/local/lib/python2.7/site-packages/keras/regularizers.py", line 80, in get
return deserialize(identifier)
File "/usr/local/lib/python2.7/site-packages/keras/regularizers.py", line 73, in deserialize
printable_module_name='regularizer')
File "/usr/local/lib/python2.7/site-packages/keras/utils/generic_utils.py", line 127, in deserialize_keras_object
raise ValueError('Improper config format: ' + str(config))
ValueError: Improper config format: {u'l2': 0.0005000000237487257, u'name': u'WeightRegularizer', u'l1': 0.0}

@dilipajm that does look like another backwards compatibility issue, but I don't think it's related to the bug I was fixing in my PRs... I was fixing something that had to do with user defined functions, whereas the above trace looks like it has to do with the config format for regularizers.

@bbabenko, thanks for the reply. Should i create a new issue related to this?

@dilipajm that, and/or glance through the release notes and see if something has been intentionally changed about the regularizer serialization format.


Ensure that args are saved inside of the throttled helper

May resolve #10935

It will not solve the issue:
https://github.com/chartjs/Chart.js/issues/10935#issuecomment-1338989248

Not sure; if the function errors out it wouldn't be callable again because ticking would still be true


General App Updates

These were not completed as part of v1.0.0 of the app but are items that may be completed in the future:

Consider modification to tab 1 figure 1 to potentially add a toggle for turning on/off points and have all selections shows a mean line (potentially with quantiles shaded) - on the fly mean lines/quantiles in Altair would either need to be preprocessed or use the experimental Altair transformer (originally noted in Issues #34).
Adding a year range filter to all graphs in app.
Adding a user rating count filter to the 3D graph.
Improve some of the app layouts to scale better on different browsers.
Alphabetize lists
Provide option to filter categories instead of multiple select on 3D explorer.

year range slider for density plot current stops at 2016
logic for all selected on density plot could likely be revised


Enterprise Master Patient Index

EMPI has a few components that we need to make sure we cover in the materials.

Scoring frameworks and candidate match, do not match lists (data model)
Integrations
Merge process - automatic and human in the loop
Auditability
Reporting and metrics

Target review in the August 31 Miletons.

Related issues:
https://github.com/medplum/medplum/pull/2674
https://github.com/medplum/medplum/issues/2678

Related issues https://github.com/medplum/medplum/issues/2694

Related issue: https://github.com/medplum/medplum/pull/2695

Related issue: https://github.com/medplum/medplum/issues/2710

Related issues all merged - closing this one out.


Any recommendation on which date picker component to use?

Just wondering if there is any recommendation on which date picker component I can use that integrates with the react forms library?

Funny u mention this .. i used react date pickee with react form and it worked great.

hmm alright, I will have a look at react date picker then :dancing_men:

I created custom input for this using FormField

Can I ask which date picker you are using? Is it this one?
http://react-day-picker.js.org/examples/

https://hacker0x01.github.io/react-datepicker/

I'm actually experiencing one tiny, rather annoying than blocking issue with this. I make sure to handle dates with moment all across my app - I try not to allow any string dates. And react-datepicker is perfect for that since the value it returns from the field is a moment object.
But react-form does one little thing on submit that translates it into a string date:
let values = JSON.parse(JSON.stringify(this.props.formState.values))
I can use preSubmit to transform it back into a moment, which is what I have to do, but it would be awesome, if I didn't have to do it...
And unfortunately, that line is posted runs no matter what, it's not a part of a condition.


03_fs_readsync needs buffer length modification to run correctly.

I'm not sure if it's supposed to be left as an exercise to the user, but I had to make a small off-topic modification to the buffer allocation to make this work.  The reason was that the buffer doesn't have a null terminator as created, and it needs one for the log_report() and log_info() calls.
I fixed it by adding this, but the null terminator could be added in other ways, I suppose:
  char buf[BUF_SIZE + 1];
  memset(buf, 0, sizeof(buf));

Fixed e931a79001fa4c5544e981d3450dad42e6b03899


When will kubernetes 1.25 be officially supported?

This repository now has the new GitHub Discussions enabled:
https://github.com/prometheus-operator/kube-prometheus/discussions
Please create a new discussion to ask for any kind of support, which is not a Bug or Feature Request.
Thank you for being part of this community!

We are still happy to chat with you in the #prometheus-operator channel on Kubernetes Slack!

Though 1.25 isn't listed as officially supported, kube-prometheus should be already working.

Though 1.25 isn't listed as officially supported, kube-prometheus should be already working.

@simonpasquier The helm chart contains PodSecurityPolicy objects which are deprecated and in my 1.26 cluster, its actively preventing the helm chart from upgrading.

this would be a question for https://github.com/prometheus-community/helm-charts then


Proposal: add meta data to delay effects for testing

With the invent of effectsMiddlewares it would be useful to be able to mock delay effects so that they can be asserted against and so that they don't actually cause a delay.
Problem: the delay effect returns a promise without any property to indicate that it is a delay which makes it impossible to distinguish from a promise returned by any other effect (AFAIK)
Proposal: add metadata to the promise returned by the delay effect to indicate that it is a delay and the length of the delay.
Example Useage: Mocking delays
  const delayMock = () => {
    const middleware = next => effect => {
      if (effect.type === 'delay') {
        for (resolveFn in middleware.waiting) {
          resolveFn({ next, effect })
        }
        middleware.waiting = []
      } else {
        return next(effect)
      }
    }
    middleware.waiting = []
    middleware.waitForDelay = () => new Promise((resolve, reject) => {
      middleware.waiting.push(resolve)
    })
    return middleware
  }

  test('it does something after 200ms', () => {
    const delays = delayMock()
    const sagaTester = new SagaTester({
      initialState,
      options: {
        effectMiddlewares: [delays],
      },
    })

    const delay = await delays.waitForDelay()
    expect(delay.effect.length).toBe(200)
    delay.next()

Edit: fixed the example

On the master (not yet released to npm) delay is now an effect, check the implementation. I believe it should ease distinguishing it from other effects. If not please comment back.

@Andarist yeah that's exactly what I was looking for! Thanks!
I rolled this example up into a little library that works with the latest code on redux-saga#master if anyone else wants to test their delays this way: https://github.com/D1plo1d/redux-saga-delay-mock


[BUG] Not compatable with Papper , Spigot 1.19.3

⚠ EDIT THIS TEMPLATE AND REMOVE THIS MESSAGE WHEN YOU'RE DONE ⚠
About
Changes to File structure and directories in 1.19.3 . plugin can not load on 1.19.3 and new pack directory structure and format 12

Minecraft version: 1.19.3
Server software: Paper
Plugin version: Branch Master

When and why?
Does not load
Documentation
Does not load

No one ever said that it's compatible with 1.19.3 yet.

It hasn't been updated yet.

MTVehicles_Pack_v0.2.1_1.19.3.zip
Here is the updated 1.19.3 Resource-pack


issues with graphite trigger

Report
Hi i have started using keda with graphite server to scale up our cicd system. i see that the values we get from graphite are not correct.
i get the following values via graphite:
[
{
"target": "starting builds",
"tags": {
"name": "sumSeries(stats.gauges.zuul.executor.*.starting_builds)",
"aggregatedBy": "sum"
},
"datapoints": [
[14,<PHONE_NUMBER>],
[11,<PHONE_NUMBER>],
[18,<PHONE_NUMBER>],
[39,<PHONE_NUMBER>],
[9,<PHONE_NUMBER>]
]
}
]
and In K8s HPA i get the following result:
Metrics:                                 ( current / target )
"s3-graphite" (target average value):  1389m / 2
1389 actually means 0.1389.
I don't see such value any where in the graph as well.
I am using the same query in keda that i used to curl the datapoints above.
Expected Behavior
Metrics:                                 ( current / target )
"s3-graphite" (target average value):  1389m / 2
I expected the above 1389m value to be 13890m or maybe some value near the above data points
Actual Behavior
Actual Behavior:
Metrics:                                 ( current / target )
"s3-graphite" (target average value):  1389m / 2
Steps to Reproduce the Problem
1.Its basically the same for any graphite usecase. The value is wrong
2.
3.
Logs from KEDA operator
example

KEDA Version
2.13.1
Kubernetes Version
1.29
Platform
None
Scaler Details
Graphite
Anything else?
I am using keda chart version 2.13.2 which was not specified in the above list

Hello
1389m means 1.389. This can be totally normal as the default metric type is average so the value that you see in the HPA is the result of calculating the average.
In this case, 1389m could be shown because you have 25 in your graphite scaler and there are 18 instances (25/18=1389m).

I understand . I have verified that this is indeed the case.


UI Pointer ignores Order by Layer

Environment

Source of VRTK: Github
Version of VRTK: d88c9eafc31975bb9566e5747c12e48e5f75fa3d
Version of Unity3D: 2018.1.4f1
Hardware used: HTC Vive Pro
SDK used: SteamVR v1.2.3 (Unity Assets Store)

Steps to reproduce

Copy the contents of scene Example 007 and place it in a new scene and save it.
Duplicate the gameobject Canvas at least two times in UnityUITestStation/UICanvas.
Starting from the canvas highest in the hierarchy, set the Order in Layer value of the canvas component of the original and duplicate canvas objects to respectively 100, 50 and 10.
Select the canvas objects with Order in Layer value 50 and 10 and move them along their local Z axis so they'll appear behind the original canvas with layer 100. Keep a distance of about half a unit between them.
Make sure that Graphic raycaster on canvas is set to Blocking Objects: All and Blocking Mask: Everything.
Play the scene and aim the UI Pointer towards the Scrolly buttons on the canvas with order in layer 100. Make sure that the scrollviews align.

Expected behavior
The UI Pointer would hit the front most canvas, allowing clicks on the buttons. The pointer renderer hits the same canvas. Placing the canvas with 100 behind the others would still force the UI Pointer to pick that one over the others according to the solution specified in #982 and #1609.
Current behavior
The UI Pointer hits the elements of the last canvas instead of the canvas closest to the controller.
The pointer renderer hits the front most canvas. The canvas with layer 100 always renders on top, even when put behind the other canvas but is not hit by the UI Pointer.

Yeah! Totally vote for this

Bug still exist, child reorder or reorder in general does not fix it.
The behaviour should be the same as the VRTK_UICanvas component is not applied. So like Unity is handling the order.
To Reproduce:
Open [007 - Interactions] InteractionHelpers and duplicate UICanvas set the Z-Position of UICanvas (1) to 0.235
Try to interact in Play Mode with UICanvas (wich is in front). you can only interact with the UI behind it.
I would suggest it is a order problem what is determined the "nearest".
This is also the case if more than 2 duplicates are made and are set behind in row.
I also wrote @bddckr in the slack channel an he only pointed me at #982 and his solution at the end which is not working. And is claiming that it works for others just fine.

Issue still remains

The canvas is in front of the other (not just drawn in front), Blocking Mask is in set to everything, Blocking Objects is set to all, it has a fitting box collider, the sorting layers are the same and sorting order is too. Changing the sorting order also does not fix anything.
It clearly is a Unity issue as it appears without VRTK, but this makes it totally useless to have multiple canvases in world space if they cannot be used as intended.

@finartist's fix worked for me, without doing the custom sort.

Closing this as it's related to an older version of VRTK (v3.3) the master branch is now on VRTK v4. Feel free to request to reopen if the issue is still present.


Add eqnrc and troffrc to Roff filenames list

This PR registers three more filenames as Roff source:

[eqnrc]: 384 results / 349 repos / 173 users
[troffrc]: 386 results / 355 results / 320 users
[troffrc-end]: 355 results / 325 repos / 293 users

Not much else to say. Pretty straightforward pull-request.
Checklist:

[x] I am associating a language with a new file extension.

[x] The new extension is used in hundreds of repositories on GitHub.com
[ ] I have included a real-world usage sample for all extensions added in this PR:
Every result I found was GPL-licensed.

Every result I found was GPL-licensed.

I thought we established with the legal team that GPL samples were fine even if not ideal?

Tests passed, so I figured the extra bytes in samples.json weren't necessary.


Add example for AAD Service Principal connection

Fixes #23.
@shueybubbles opened after addressing comments for #25.

Codecov Report

Merging #27 (79532e0) into main (f21bac1) will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
- Coverage   71.28%   71.17%   -0.12%
==========================================
  Files          24       24
  Lines        5418     5418
==========================================
- Hits         3862     3856       -6
- Misses       1311     1315       +4
- Partials      245      247       +2

Impacted Files
Coverage Δ

tds.go
65.13% <0.00%> (-0.73%)
:arrow_down:

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 f21bac1...79532e0. Read the comment docs.


Up to date documentation for Solid?

Hey 👋
I'm following through on your solid guide, specifically this page though it seems outdated.
There's no action property available on the Form and onSubmit() now seems to be required? I had assumed I somehow have to call my server function loggingInAction i.e const [loggingIn, loggingInAction] = createServerAction$(...) from the onSubmit now but I can't seem to see how?
Thanks in advance

Hey, actions are not yet implemented for SolidJS, as mentioned on the page. You can read more about it here: https://github.com/fabian-hiller/modular-forms/issues/3#issuecomment-1512877615


SheCode Africa Summit

Checkout the event details here
Link to register is here
Ensure you follow the exact date format that we're talking about in this issue 👉🏽 #47
For context, this https://github.com/kaf-lamed-beyt/ng-tech-events/issues/47#issuecomment-1630738288 explains why you should adhere to the aforementioned date format.

I'm picking this up


feat(lang): add 'zh_Hant' locale

Summary

Change: Added Traditional Chinese(繁體中文) locale
Motivation: I want my editor colleagues to have a enjoyable edit workflow under their native language

Test plan

Here's a partial review under this locale.
A picture of a cute animal (not mandatory but encouraged)

My lovely kitties :)

Thanks @cyihsu. Not sure why the build got stuck - rebased an re-opened here https://github.com/netlify/netlify-cms/pull/3068.
FYI, it is recommended to create a feature branch on your fork and open a pull request from there instead of directly from master (in case maintainers would like to add commits to your PR).


Excessing object wrapping.

I'm noticing with webpack v3 there's a lot of this kind of generated code:
Object(__WEBPACK_IMPORTED_MODULE_3__module_resolve_filename_js__["a" /* default */])(foo)

What's the reason for wrapping all references with Object() and can this be disabled or optimized away to a single wrap?

The reason is to call the function with the correct this context:
import x from "module";

x(foo); // <- called without this (undefined/root)

var __WEBPACK_IMPORTED_MODULE_1__module__ = __webpack_require__(1);

__WEBPACK_IMPORTED_MODULE_1__module__.default(foo);
// ^ called with this = __WEBPACK_IMPORTED_MODULE_1__module__

Object(__WEBPACK_IMPORTED_MODULE_1__module__.default)(foo);
// ^ called without this (undefined/root)

The Object() is generated when calling a imported symbol directly. I omitted this in an older version, assuming nobody care about this in an exported function, but this breaks when exporting native functions like setTimeout with expected no this.
Most of these are optimized away with the ModuleConcatenationPlugin.

A bit of history of this: (This started 1.5 years ago)

I started to use (0, a.b)() for this, but this broken because of ASI when the previous line has no semicolon...
I tried a.b.bind(undefined)() and also a.b.bind()() but bind is pretty slow.
I switched to a.b.call(undefined) as it's a bit faster.
I switched to __webpack_require__.i(a.b)() with a identity function
I switched to Object(a.b)() because Object behaves like identity for functions and doesn't require a custom function in the runtime.
I did some performance measurements:

Here are up-to-date results:
// chrome  60.0.3112.113
call x 1000000: 9ms
call with Object x 1000000: 24ms
call with comma operator x 1000000: 10ms
call with identity function x 1000000: 9ms
call with valueOf x 1000000: 15ms
call with .bind x 1000000: 45ms
call with own getter x 1000000: 12ms
call with .call x 1000000: 10ms
call cached version x 1000000: 8ms

// firefox 55.0.3 (32-Bit)
call x 1000000: 4.65ms
call with Object x 1000000: 33.15ms
call with comma operator x 1000000: 4.26ms
call with identity function x 1000000: 5.67ms
call with valueOf x 1000000: 5.26ms
call with .bind x 1000000: 183.52ms
call with own getter x 1000000: 5.49ms
call with .call x 1000000: 5.62ms
call cached version x 1000000: 4.57ms

// node 8.4.0
call x 1000000: 10.145ms
call with Object x 1000000: 22.028ms
call with comma operator x 1000000: 9.233ms
call with identity function x 1000000: 10.348ms
call with valueOf x 1000000: 16.490ms
call with .bind x 1000000: 43.926ms
call with own getter x 1000000: 10.633ms
call with .call x 1000000: 10.075ms
call cached version x 1000000: 8.391ms

// node 6.11.2
call x 1000000: 17.505ms
call with Object x 1000000: 23.144ms
call with comma operator x 1000000: 9.383ms
call with identity function x 1000000: 9.346ms
call with valueOf x 1000000: 18.307ms
call with .bind x 1000000: 823.117ms
call with own getter x 1000000: 9.449ms
call with .call x 1000000: 17.538ms
call cached version x 1000000: 7.075ms

Note: bind got faster in node 8, bind is slow in firefox, most calls are faster in FF than in Chrome, Object() is also a bit slow.

I noticed that Object() is slower than a identity function, but 30ms for 1 million calls... who cares?
I maybe switch back to an identity function
I could optimize cases where this is not used, or an arrow function is used.

@sokra very interesting! Thanks for the explanation.

Maybe I'm missing something, but why not just
const foo = o.foo;
foo();

instead of
Object(o.foo)();

Maybe it's a stupid question, but I'll ask anyway primarily out of curiosity: why not use (0, a.b)() with a semicolon beforehand?

Our Parser is not so clever to track what's before the identifier.
@bmeurer Caching the export is not always correct as these are live bindings which can change anytime.

Related:

If comma version is one of the fastest and is not bloating the generated code so much, why wasnt just ;(0, a.b)(); chosen? Code will get formatted later by the minifirier anyway. Im assuming no other troubles than ASI with comma version

@sokra I see, thanks for the clarification. Will land the Object call inlining today, so Chrome M63 and some future version of Node should have Object(o.f)() as fast as const f = o.f; f().

Great to see. If you want to you could improve the error messages for this cases a bit:
> var o = {}
undefined
> o.f()
TypeError: o.f is not a function 👍
> Object(o.f)()
TypeError: Object(...) is not a function 👎
> o.f.call()
TypeError: Cannot read property 'call' of undefined 👎
> (0,o.f)()
TypeError: (0 , o.f) is not a function 👍

This would help people debugging undefined/null functions.

i. e.
TypeError: Object(o.f) is not a function
TypeError: Cannot read property 'call' of undefined o.f

cc @hashseed @schuay @gsathya

Any support in turning this off. This does not allow to import function. Cause it break it to Object

I personally don't care so much about performance. But..it it's a pretty rough hit on readability. I would totally trade clarity for correctness during all development. Would you be able to provide a flag to turn it off?

If anyone's wondering, you can disable this in webpack 4 with the config:
{
	optimization: {
		concatenateModules: true
	}
}

Side note: concatenateModules is already enabled in production mode.

I noticed that with a mode of "production" that if the NODE_ENV was not "production" that the Object(...) wrapping is still applied. In my case NODE_ENV was "production-test".

Narrowed it down that when NODE_ENV had -test in it I was adding more config.entry builds which for some reason is enabling Object(...) wrapping:
config.entry.compiler = "./src/compiler.js"
config.entry.entry = "./src/entry.js"
config.entry.runtime = "./src/runtime.js"


Update Exec standard output to be compatible with configuration cache

Expected Behavior
Exec.getStandardOutput() is compatible with configuration cache
Current Behavior
Exec.getStandardOutput() is not compatible with configuration cache
> Task :getVersionInfo FAILED
bc00f347a22805f720fd975304b31335bd5fb665

2 problems were found storing the configuration cache.
- Task `:gitVersion` of type `org.gradle.api.tasks.Exec`: cannot deserialize object of type 'java.io.OutputStream' as these are not supported with the configuration cache.
  See https://docs.gradle.org/8.2/userguide/configuration_cache.html#config_cache:requirements:disallowed_types
- Task `:gitVersion` of type `org.gradle.api.tasks.Exec`: cannot serialize object of type 'java.io.ByteArrayOutputStream', a subtype of 'java.io.OutputStream', as these are not supported with the configuration cache.
  See https://docs.gradle.org/8.2/userguide/configuration_cache.html#config_cache:requirements:disallowed_types

Context (optional)
I want to use Exec.standardOutput in a project that has Configuration Cache enabled.
Steps to Reproduce
// build.gradle.kts
import java.io.ByteArrayOutputStream

val gitVersion by tasks.registering(Exec::class) {
  executable("git")
  args("rev-parse", "HEAD")

  val gitVersionFile = layout.projectDirectory.file("gitVersion.txt")
  outputs.file(gitVersionFile)

  standardOutput = ByteArrayOutputStream()

  doLast {
    val capturedOutput = standardOutput.toString()
    gitVersionFile.asFile.apply {
      parentFile.mkdirs()
      createNewFile()
      writeText(capturedOutput)
    }
  }
}

This code is based on the Javadoc example
https://github.com/gradle/gradle/blob/c9224537a77e25ff289ee072b078e9a2543c53cd/subprojects/core/src/main/java/org/gradle/api/tasks/Exec.java#L20-L41
Gradle version
8.2
Build scan URL (optional)
No response
Your Environment (optional)
No response

Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team and is prioritized by them.


katib-ui-rock is based on wrong Dockerfile

It turns out we have ROCKed the wrong dockerfile for katib-ui-rock.
The katib-ui component we 've charmed is the until recently (release 0.15) called new-ui component in the upstream. We can see this in the way they produced images. Looking at the0.15 release branch, this is the dockerfile we rocked while the image we use in our charm comes from this one. With release 0.16, they removed the old ui and thus renamed previous new-ui component to ui.
Summarizing, we need to update the ROCK to be based on this dockerfile (ui from release 0.16-rc.1).

This will be closed by https://github.com/canonical/katib-rocks/issues/32


Broken go cloud function builds

Hello, this commit  to opencensus-go seems to have broken go Google Cloud Function deploys for me. I understand that this is is probably not the correct place to report this but it was the best place I could find.
I started getting this error today when Im trying to deploy go cloud functions. Ive tried multiple regions and projects, always with the same error.
ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Build failed: # github.com/cloudevents/sdk-go/v2/extensions
src/github.com/cloudevents/sdk-go/v2/extensions/distributed_tracing_extension.go:161:3: cannot use span (type trace.Span) as type *trace.Span in return argument:
	*trace.Span is pointer to interface, not interface; Error ID: 1093f764

From the stack driver logs:
Step #4 - "builder": go version go1.13.12 linux/amd64
Step #4 - "builder": Done "go version" (4.124119ms)
Step #4 - "builder": Running "go get github.com/GoogleCloudPlatform/functions-framework-go/funcframework (GOPATH=/workspace GOCACHE=/tmp/serverless_function_app170363466)"
Step #4 - "builder": # github.com/cloudevents/sdk-go/v2/extensions
Step #4 - "builder": src/github.com/cloudevents/sdk-go/v2/extensions/distributed_tracing_extension.go:161:3: cannot use span (type trace.Span) as type *trace.Span in return argument:

Shouldn't the build pack used pinned versions of these dependencies instead of using master version?

Im building using a vendor folder since I have private dependencies. I have deployed the same code previously without any issues.

Related: https://status.cloud.google.com/incident/cloud-functions/20006

And: https://github.com/GoogleCloudPlatform/functions-framework-go/issues/56


Fix shellcheck brew style errors

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This is blocking CI.

Review period skipped due to critical label.

Thanks @Bo98.


Video WebRTC

sipsocery support video WebRTC

Video/Audio channels have not yet been implemented into the plugin, but should be an easy addition.
Should happen after #13.

great issue 13 closed : https://github.com/SakulFlee/Godot-WebRTC-Match-Maker/issues/13


Debug support

Solves #114
WIP Debug support. Currently only supports Stable version of Roslyn, the Nightly should be a no brainer, but I wanted to discuss this more in detail before implementing.
Done:

Added support for --debug (short -d) argument
Added Debug command + all that jazz
Added DebugScriptHost, which waits for a debugger to be attached
Added RoslynDebugSession, which compiles the cake-script and emits the dll + pdb to a memorystream which is loaded and executed.

I'm not sure about the Roslyn Session and SessionFactory implementations. Refactored out the common bits, but still feels kind of wierd? Any suggestions on this before proceeding with the Nightly version of Roslyn.
ALSO Still lacks Unit Tests, some bits should be refactored to allow testing, e.g. DebugScriptHost..
HOWTO:

launch cake.exe with -debug flag. cake.exe cakefile.cake -debug
Process will stop in prior to executing script and report Attach debugger to process XYZ to continue
Open Visual Studio, open the cake file, add a breakpoint.
Open Debug > Attach to Process... and attach to process with PID reported in step 2.
Enjoy debugging...
Sometimes VS will fail and report "Source not found", if this is the case, close the open cake-file and then from the call stack window right click on the first row and select "Go to source". This should open the source file and everything is fine :) Don't know why VS behaves like this, breakpoint hits, but it can't open source when it's already open.
Another nice way is to add System.Diagnostics.Debugger.Break(); to the line where you would like the debugger to break. In this case you can completely skip opening the file in VS, the debugging session will open it automatically once breakpoint is hit.

@mholo65
Great job! :+1:
Would it be possible to Rename the RoslynSessionFactory to DefaultRoslynSessionFactory and RoslynSession to DefaultRoslynSession, and after that rename AbstractRoslynSessionFactory to just RoslynSessionFactory and AbstractRoslynSession to RoslynSession.
public sealed class DefaultRoslynSessionFactory : RoslynSessionFactory { }
public sealed class DebugRoslynSessionFactory : RoslynSessionFactory { }

public sealed class DefaultRoslynSession : RoslynSession { }
public sealed class DebugRoslynSession : RoslynSession { }

Not sure that Default is a better prefix, but I'm really not a fan of the Abstract prefix.
@gep13 @devlead: Any input on naming?

Thanx! Default/Debug sounds better than current naming. Will wait and see what the others have to say about naming.
Another thing that cane to mind. What about adding #break pre-processor directive that would inject System.Diagnostics.Debugger.Break();? That could be a separate PR though.

@mholo65 +1 on naming :+1: Any thoughts @gep13?
New preprocessors should as you suggest be part of separate PR, so we keep this one as focused as possible.

Would you also like to have debug support for experimental (nightly) version of Roslyn as separate PR? It is not yet implemented in this PR.

@mholo65 I think debug support for experimental Roslyn could be a part of this PR.

I agree with @patriksvensson, would be great with support for experimental in this pr too.

@patriksvensson @devlead Thanks. I'll fix the naming, add experimental roslyn support and add some unit tests. I'll probably have it by the end of this week.

Sorry for not replying sooner, had a couple things on...
Yes, I agree with the suggested naming.  I really like the idea of the #debug pre processor as well, I think that will help during debugging sessions, but I agree that this should be a separate PR.
This really is great work @mholo65! This is going to make a lot of people very happy! :+1:

@mholo65 quick random question... will the debugger within say VSCode also be able to attach to this, in the same way as you can with Visual Studio?

@gep13 haven't tried that. But I could investigate.

@patriksvensson I think I'm confident enough to remove the [WIP] tag now :smile:
//cc @devlead @gep13

Damn! Really looking forward to taking a look at this, and having a play!
@mholo65 on a side note, did you take a look at using VSCode as the debugger?  Is that going to work, or is additional work required? Cheers!

@gep13 I checked up on VSCode debugging and unfortunately it won't work until Cake is ported to .NET Core as the Omnisharp VSCode Debugger uses CLRDBG which is designed for .NET Core.
However, the .NET Framework Command-Line Debugger, MDbg works like a charm. But this debugger is unfortunately not available as an extension for VSCode.
A third alternative is the Mono debugger, which may work. I'm currently not in a position to test that as I'm lacking an environment atm. (read not supported on Windows)

@gep13 and forget the third alternative as we don't do the Roslyn dance on Linux/Mac and this PR doesn't implement debugging support for Mono...

@mholo65 Awesome work! Really impressed. Will take a closer look at it tonight when I'm off work.
@gep13 Have you seen the Mono debug adapter? https://github.com/Microsoft/vscode-mono-debug

ping @devlead @patriksvensson @gep13 fixed, rebased and squashed!

@mholo65 Looks good to me! :smile:
@devlead Will you take lead on this?

@patriksvensson agree :+1: Just waiting for CI to complete.

@devlead seems like Travis osx build is stalled.. :(

@mholo65 I've restarted the Travis build.

@mholo65 This is now merged :+1:  Big thanks for your contribution!
@cake-build/team FYI 1/2 travis builds didn't complete(the Mac build - restarted 4 times), all other CI success and tested locally, so took decision to merge anyway.

@devlead Thank You! It was a pleasure doing this PR :smile:

Is there any plans on producing a write-up on using this feature. At this point debug support and intellisense are the only things blocking me from adopting cake as my go to build tool.

@DamianReeves yes, there's an issue here https://github.com/cake-build/website/issues/83 to track this.

@mholo65 @DamianReeves there will likely be an intro blog post too shortly.

@DamianReeves A blog post have been posted about this: http://cakebuild.net/blog/2016/05/debug-cake-file

@DamianReeves said...
At this point debug support and intellisense are the only things blocking me from adopting cake as my go to build tool.

As a point of curiosity, what are you currently using as your build tool?

@gep13  I go back and forth between psake and FAKE


Interpret dwc species profile extension

extract more taxon properties through the species profile extension:

lifezones (boolean flags)
extinct
temporalRange (aka livingPeriod)

Each taxon in theory can have multiple profile records which is bad practice.
Flag this and avoid setting a property which already exists

done a while ago


:bomb: dummy PR to check phantom_js work. It should be rejected.

It had random errors in 11.0 version and I've fixed in https://github.com/it-projects-llc/misc-addons/pull/640
(for 10.0 version, you can  replace menu Website to menu Settings)


New build of terminal services Windows 8.1  6.3.9600.18692 which is not supported

Good day!
There is a new version of terminal services in Windows 8.1 Pro that is not supported - 6.3.9600.18692

Here is the termsrv.dll 6.3.9600.18692
termsrv.zip


Add space to URI error

The URI gem recently updated its error messages to include a space where there previously was not one: ruby/uri@9f2c7ed5f2e2c4060c05e3db8fa1dc73dd24ba0f
This commit updates our test to reflect that change.

This does not need to be backported to 7.x.

Actually, I should include all of the test fixes in one PR. Closing this one out.


FastNoiseLite JavaScript Port

JavaScript port of FastNoiseLite
I did my best to debug this but with over 3k lines it is possible I missed something so be on the lookout :)

Looking at the diff between this port and C# is not easy, too many formatting changes. I'd want this to be closer to C# for future maintenance.
Have you done any testing on this code with a visual output?

No problem.
I was referencing the java port.  Unfortunately method overloading does not exist for JavaScript so it would difficult to have very similar formatting to the C# or Java version. JavaScript in general is a quirky language e.g.) enums are not natively supported. However, I tried to be as consistent as possible.
I have not done any testing w/ a visual output just comparing the results btwn this and the other versions to make sure outputs are consistent.

It's not the language changes I care about, I realise those are required, it's formatting changes I would like to avoid.
I'm not going to pull this in if it has had no testing, doesn't need to be anything fancy just some way to get a visual output of the noise produced.
Thanks.

I will conduct some more tests and create a visual output.
By formatting do you mean the documentation formatting?

Out of those tested (visual output)
Options that work:
FastNoise.NoseType.OpenSimplex2
FastNoise.NoseType.OpenSimplex2S
FastNoise.NoseType.Cellular
FastNoise.NoseType.Perlin

FastNoise.FractalType.None
FastNoise.FractalType.FBm
FastNoise.FractalType.Ridged
FastNoise.FractalType.PingPong

FastNoise.CellularDistanceFunction.Euclidean
FastNoise.CellularDistanceFunction.EuclideanSq
FastNoise.CellularDistanceFunction.Manhattan
FastNoise.CellularDistanceFunction.Hybrid

FastNoise.CellularReturnType.CellValue
FastNoise.CellularReturnType.Distance
FastNoise.CellularReturnType.Distance2
FastNoise.CellularReturnType.Distance2Add
FastNoise.CellularReturnType.Distance2Sub
FastNoise.CellularReturnType.Distance2Mul
FastNoise.CellularReturnType.Distance2Div

Options that dont work yet:
FastNoise.NoseType.Value
FastNoise.NoseType.ValueCubic

I will work to fix the bugs through the week
Tested with:
https://editor.p5js.org/stormy482/sketches/jq6JYVflh

Thanks, I think I see why the diff is so off, you are handling function overloading using if (arguments.length === x) Could you avoid trying to support overloads and instead prefix the function ie: Func2D, Func3D

Yeah that would be possible but would take a lot of refactoring. I would want to fix as many of the bugs w/ the current version as possible before making a change. For now can I just leave a comment explaining the method overloading?

This weekend I should have the time to fix the value noise and cubic value noise

Okay ALL noise functions work now including 3D. All tested w/ a visual output. Turns out the bug w/ the value noise and value cubic noise not working was just me forgetting to add the args lol.

I also think that the domain warp is good to go too! I tested all the types in 2d and 3d. I think that it might be time to pull...  🎉
Tonight I will write an explanation of the method overloading... To make it easier to preform future maintenance.

@Auburn Can we pull now?

@KdotJPG is having a look over the code for me, since he had some past JavaScript experience

Sounds Good!

Okay i will create a version w/o the method overloading solution and compare the performance.

In some functions I am seeing a 25% increase in speed

Did some optimizations in gen too

@Auburn Are we ready to merge?

@stormy482 Oop - sorry it took so long for me to get back to this! Great work, I think this will be much faster. Did you speed test the different ways of overloading the public methods that do need it? My suggestion was to do following. I think it will be a little faster and have a slightly lower footprint, at the same time.
	GetNoise(x, y, z) {
		switch (arguments.length) {
			case 2:
				x *= this.#Frequency;
				y *= this.#Frequency;

				switch (this.#NoiseType) {
					case FastNoise.NoiseType.OpenSimplex2:
					case FastNoise.NoiseType.OpenSimplex2S:
						const SQRT3 = 1.7320508075688772935274463415059;
						const F2 = 0.5 * (SQRT3 - 1);
						let t = (x + y) * F2;
						x += t;
						y += t;
						break;
					default:
						break;
				}

				switch (this.#FractalType) {
					default:
						return this.#GenNoiseSingleR2(this.#Seed, x, y);
					case FastNoise.FractalType.FBm:
						return this.#GenFractalFBmR2(x, y);
					case FastNoise.FractalType.Ridged:
						return this.#GenFractalRidgedR2(x, y);
					case FastNoise.FractalType.PingPong:
						return this.#GenFractalPingPongR2(x, y);
				}
				break;

			case 3:
				x *= this.#Frequency;
				y *= this.#Frequency;
				z *= this.#Frequency;

				switch (this.#TransformType3D) {
					case FastNoise.TransformType3D.ImproveXYPlanes: {
						let xy = x + y;
						let s2 = xy * -0.211324865405187;
						z *= 0.577350269189626;
						x += s2 - z;
						y += s2 - z;
						z += xy * 0.577350269189626;
						break;
					}
					case FastNoise.TransformType3D.ImproveXZPlanes: {
						let xz = x + z;
						let s2 = xz * -0.211324865405187;
						y *= 0.577350269189626;
						x += s2 - y;
						z += s2 - y;
						y += xz * 0.577350269189626;
						break;
					}
					case FastNoise.TransformType3D.DefaultOpenSimplex2:
						const R3 = 2.0 / 3.0;
						let r = (x + y + z) * R3;
						x = r - x;
						y = r - y;
						z = r - z;
						break;
					default:
						break;
				}

				switch (this.#FractalType) {
					default:
						return this.#GenNoiseSingleR3(this.#Seed, x, y, z);
					case FastNoise.FractalType.FBm:
						return this.#GenFractalFBmR3(x, y, z);
					case FastNoise.FractalType.Ridged:
						return this.#GenFractalRidgedR3(x, y, z);
					case FastNoise.FractalType.PingPong:
						return this.#GenFractalPingPongR3(x, y, z);
				}
				break;

			default:
				break;
		}
	}

Other than that small speed concern, great work!

That looks great!

I think that the performance was similar with the lamda functions compared to the switch functions but I might be remembering wrong. I will test it when I have a chance :)

There is no difference in preference between using a switch and not using a switch
Switch statement: RED
Arrow Function: GREEN

I have a graph image but I can't upload it now as on a flight

@KdotJPG @Auburn I just tested with and without simulated method overloading and found no difference in performance between the trials. Does anyone have anymore ideas to optimize?

I think it's best to leave the arrow function method overloading as I'm my opinion it's more readable and easier to maintain but it is your decision.

I left some comments around the code. I also just wanted to say nice work and thanks for getting it this far!

There should probably be a build step at least because of the private method declarations which are still technically experimental (though, stage 3). Source: https://github.com/tc39/proposal-private-methods

There should probably be a build step at least because of the private method declarations which are still technically experimental (though, stage 3). Source: https://github.com/tc39/proposal-private-methods

I can just write after the license to switch to non private methods just control + f and replace # with _

That is possible, though releasing code with notes like "you can ctrl-f" instead of providing a real build process is kind of jank. :p
Nowadays it's standard to include transpiled code as well as ESM, the latter of which additions like private class properties would fit well.
I do think, regardless of all this, that exposing some of the APIs makes sense anyway. I'm not a big fan of the monolithic approach where you configure everything and have all different noise types in the same class. Now, I don't necessarily take issue with providing a higher-level API to accomplish that. I just think that shouldn't be the only API, much less enforced rigidly with variable provenance restrictions.

ight

okay, sorry i was gone for so long, dealing with some health things. I updated the private(#) methods to use (_) because it was causing too much stress lol. Also, I am going to publish to npm for convenience and whatnot. gonna push soon.

Yeah, should be almost good to go. However, before pulling if any final suggestions would be great. In the future I might use babel to make an ES5 Version, or at the very least allow for use of the node package syntax eg. const noise = require("fastnoise-lite"); and I might move the class methods that are currently "private" to functions but that is for a future date. It is important to note that npm is not especially flexible with patching because you must publish a new version every time you want to make an update to the package so once we go to 1.0.3 there is no turning back lol. Anyway, yeah... Almost good to go!

Looks great! Thanks for doing the speed tests, really helps confirm it's not an issue.
The keywords section might not need the repeated words, and "3D/2D" might not make sense as a combined keyword. If you want, you can use this set. I included a lot of relevant terms, and tweaked the order of the noise names. Not sure if there's a max number.
  "keywords": [
    "noise",
    "fastnoise",
    "procedural",
    "simplex",
    "opensimplex",
    "cellular",
    "voronoi",
    "perlin",
    "value",
    "cubic",
    "fractal",
    "domain-warping",
    "2D",
    "3D",
    "heightmap",
    "terrain",
    "texture",
    "random",
    "generative",
  ],

If you wanted to compress all the commits into one -- not saying you need to, but if you wanted to and aren't yet familiar with rebasing, I use these steps in CMD line:

make sure your master branch local copy is up to date
make a backup of your current branch
If you have any updated changes, git stash
git rebase -i master
Assuming you have the default commandline-based text editor, press a so you can modify in the inline text
replace all instances of the word pick with fixup (and press :wq to save and quit if you use the commandline-based text editor)
Note that renaming the commits in the text doesn't actually rename them.

There's also a slight typo on line 70 in the readme if you want to fix it.
Looks great though!

Sounds good! Will do

(Rebased and resubmitted via https://github.com/Auburn/FastNoiseLite/pull/70 and merged)

(resubmitted by PR #70)


suggestion: remove lightningKillsDropsFix rule

the main mod (Carpet) already has this functionality

https://github.com/gnembon/fabric-carpet/wiki/Current-Available-Settings#lightningkillsdropsfix

https://github.com/fxmorin/carpet-fixes/wiki/Available-Settings#lightningkillsdropsfix
so they overlap
[13:24:30] [main/WARN]: Method overwrite conflict for method_5800 in carpet-fixes.mixins.json:itemFixes.ItemEntity_lightningKillsDropsMixin from mod carpet-fixes, previously written by carpet.mixins.ItemEntityMixin. Skipping method.

I wrote the original rule and asked gnembon to remove it, and he never did


Particle effect in Logo is messed up

The particle effect that renders the galactic cloud in the logo animation is messed up. It looks like it is going in the wrong direction and rotates weirdly as you move/roll your head.

No longer relevant with latest version of Galaxy Explorer


add collection - btc-mfers

we're the 10k collection which is listed on ME under the name "Bitcoin mfers", name/slug was taken on here ¯\_(ツ)_/¯

no offense, but are you mfers sleepin?


suggestion

when I finish the video page in my APP,I found the other pages can also rotate ,I think you should remove the orientation listener when the conponent unmount in the video page so that it will not influence on the other pages

Thanks for the suggestion @weizhiyang,
Have you tried adding lockPortraitOnFsExit, does that stop your app pages from rotating?


[SPARK-19333][SPARKR] Add Apache License headers to R files

What changes were proposed in this pull request?
add header
How was this patch tested?
Manual run to check vignettes html is created properly

Test build #72015 has started for PR 16709 at commit 63a0356.

Test build #72015 has finished for PR 16709 at commit 63a0356.

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/72015/
Test PASSed.

merged to master, branch-2.1, branch-2.0


Add test for missing inventory in version

https://ocfl.io/draft/spec/#W010 - should be a test case in fixtures too

See https://github.com/OCFL/fixtures/pull/35

Test is working fine against develop branch of the fixtures based on https://github.com/zimeon/ocfl-py/commit/15aba1f293f85b97b2a5daa8db28be55e2e339a7 , just waiting for OCFL/fixtures#35 to be merged

Done and tested against canonical fixture


Actuals use case

Adding education example on Accruals (AA, OA)
Adding MC N step
Change aggregation behavior
resolves #128

I would add a simple Test notebook in each directory that perform some numerical checks and evaluate them in the Test>Tests NB


Execution failed for task ':react-native-version-number:verifyReleaseResources'. > com.android.ide.common.process.ProcessException: Failed to execute aapt

While trying to create apk file for anroid, its throwing following error.

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':react-native-version-number:verifyReleaseResources'.

com.android.ide.common.process.ProcessException: Failed to execute aapt

How to fix this?

same issue here

I uninstalled library from this project due to this issue since I did not found any solution for this.

is there any update on this issue?

Same issue here!

I found a solution fortunately.
According to Afresh_Kedou, it was not originally a problem with the rn version. The reason is that the version of the Android SDK has been updated to 27 by 0.57.1, which is incompatible with most third-party plugins that use native code. Because the third-party updates are not timely, the SDK is still old. version.
Solution:

First find the build.gradle in the error package in node_modules, for example, this is \node_modules\react-native-version-number\android\build.gradle;

Modify this build.gradle to match the SDK version in android/build.gradle (and possibly android/app/build.gradle);

Change compile in build.gradle to implementation because compile is obsolete.

android {
    compileSdkVersion 27 // 23 -> 27
    buildToolsVersion "27.0.3" // 23.0.1 -> 27.0.3

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 26 // 22 -> 26
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    lintOptions {
       warning 'InvalidPackage'
    }
}

dependencies {
    implementation 'com.facebook.react:react-native:+' // compile -> implementation
}

Then re-release it.
credit - Afresh_Kedou (https://www.twblogs.net/a/5bd390a22b717778ac206d34)

below is what you need for react-native 0.59.5:
apply plugin: 'com.android.library'

android {
    compileSdkVersion 28
    buildToolsVersion "28.0.3"

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 28
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
    lintOptions {
       warning 'InvalidPackage'
    }
}

dependencies {
    compile 'com.facebook.react:react-native:+'
}

https://github.com/APSL/react-native-version-number/releases/tag/v0.3.6