bazel build error for PolymerElements

I am trying to build tensorflow from source, and bazel is giving some unrelated error
eddie7@albus:~/lab/tensorflow$ git pull
Already up-to-date.
eddie7@albus:~/lab/tensorflow$ ~/lab/bazel/bazel-bin/src/bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
.......
ERROR: /home/eddie7/lab/tensorflow/tensorflow/tensorboard/bower/BUILD:3:1: no such package '@iron-validatable-behavior//': https://github.com/PolymerElements/iron-validatable-behavior.git: cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'.
ERROR: Loading failed; build aborted.
INFO: Elapsed time: 129.792s

FYI: I have also build bazel from source

@danmane: Do you know what might be going wrong?

I encountered the same issue after adding Android NDK to the WORKSPACE.
I also built bazel from the source.
It happened after syncing my tensorflow directory with Change 109591880 that apparently fixes loading dummy shared library issue #419 .

I have the same issue after adding Android NDK to the WORKSPACE.
It happened to me after syncing my tensorflow directory with cd53f3c3302c9312c1840389a9988a879b8b9dd5 change number 109591880 that apparently load pthread shared library after building it through the top level build flow. (related to issue #419)

@hamidb: that sounds like a red herring.
Can you try
bazel clean
followed by
bazel build -j 1 --spawn_strategy=standalone
(These are the instructions we've been suggested for those having trouble with bazel builds)...

@vrv
I tried to rebuild tensorflow after, executing your instruction, still no luck
eddie7@albus:~/lab/tensorflow$ ~/lab/bazel/bazel-bin/src/bazel build -j 1 --spawn_strategy=standalone
.......
INFO: Found 0 targets...
INFO: Elapsed time: 2.096s, Critical Path: 0.01s
eddie7@albus:~/lab/tensorflow$ ~/lab/bazel/bazel-bin/src/bazel clean
INFO: Starting clean (this may take a while). Consider using --expunge_async if the clean takes more than several minutes.
eddie7@albus:~/lab/tensorflow$ git pull
remote: Counting objects: 34, done.
remote: Total 34 (delta 28), reused 28 (delta 28), pack-reused 5
Unpacking objects: 100% (34/34), done.
From https://github.com/tensorflow/tensorflow
   f88fb6f..8242b4d  master     -> origin/master
 * [new tag]         0.6.0      -> 0.6.0
Updating f88fb6f..8242b4d
Fast-forward
 tensorflow/core/public/version.h                                | 2 +-
 tensorflow/models/image/imagenet/BUILD                          | 1 +
 tensorflow/python/BUILD                                         | 1 +
 tensorflow/python/kernel_tests/parsing_ops_test.py              | 4 ++--
 tensorflow/python/kernel_tests/sparse_serialization_ops_test.py | 2 +-
 tensorflow/python/ops/gradients.py                              | 2 +-
 tensorflow/python/ops/image_ops_test.py                         | 4 ++--
 tensorflow/tools/pip_package/setup.py                           | 2 +-
 8 files changed, 10 insertions(+), 8 deletions(-)
eddie7@albus:~/lab/tensorflow$ ./configure
Please specify the location of python. [Default is /usr/bin/python]:
Do you wish to build TensorFlow with GPU support? [y/N] n
No GPU support will be enabled for TensorFlow
Configuration finished
eddie7@albus:~/lab/tensorflow$ ~/lab/bazel/bazel-bin/src/bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
ERROR: /home/eddie7/lab/tensorflow/tensorflow/tensorboard/bower/BUILD:3:1: no such package '@mocha//': https://github.com/mochajs/mocha.git: cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'.
ERROR: Loading failed; build aborted.
INFO: Elapsed time: 129.614s

it seems issue with bazel rather than tensorflow, as far as I think.
I have never used bazel before too, so can't tell anything

Sorry, I meant:
$ ~/lab/bazel/bazel-bin/src/bazel build -j 1 --spawn_strategy=standalone -c opt //tensorflow/tools/pip_package:build_pip_package
That is indeed weird that it can't open the mocha.git file...

@vrv I have no problem with mocha.git. It was @jayendra13's error.
I was able to fix my issue. I was trying to build the android sample. I noticed that to be able to build the android sample, you need to first build other dependencies such as protobuf, etc.
I would ideally expect calling
bazel build //tensorflow/examples/android:tensorflow_demo
it should automatically build dependencies if already not built. Am I right?
So if you have a clean workspace, build bazel android_demo does not work.

Assigning to andrew to take a look.

I am unable to reproduce this issue using a fresh bazel install (from source) and clone of the TF repo. tensorflow/examples/android:tensorflow_demo still builds cleanly for me.
Note that unless you clone the TF repo with --recursive, you will not grab the protocol module into your local tree. Could this be related to your issue?

I had protobuf already cloned.
I will try to reproduce it again and provide more details.

@andrewharp
I can reproduce it when using bazel 0.1.1. It compiles with 0.1.2
Here are the steps to reproduce:
1- bazel clean --expunge
2- cd google/protpbuf/ & make clean
3- rm -rf ~/.cache/bazel/_bazel_user
4- compile bazel
5- ./configure tensorflow without gpu
6- bazel build --verbose_failures  //tensorflow/examples/android:tensorflow_demo
I get this:
ERROR: /home/hamid/.cache/bazel/_bazel_hamid/f7e3d3cb1f79b9a7f53120cc4d577bcd/external/default_android_tools/src/main/protobuf/BUILD:19:2: every rule of type gensrcjar implicitly depends upon the target '//third_party:protoc',  but this target could not be found. If this is an integration test, maybe you forgot to add a mock for your new tool?.
ERROR: Loading failed; build aborted.

It will be OK if I first compile protobuf and then build the demo. But it would be nicer for the demo build flow to automatically resolve it.

To confirm, you are unable to reproduce the issue when building with bazel 0.1.2?
I am unable to follow your reproduction steps for "cd google/protobuf & make clean":
~/tf_git/tensorflow$ cd google/protobuf/ & make clean
[1] 939
make: *** No rule to make target `clean'.  Stop.
Given that "//third_party:protoc" appears nowhere in the Tensorflow or google/protobuf repos, I'm guessing this sounds like a bad config is being pulled in from somewhere external, likely Bazel.
At its root, when you chase down what tensorflow/core:protos_cc actually is (this nessecitates following several layers of indirection between tensorflow/core/BUILD, tensorflow/tensorflow.bzl, tensorflow/core/platform/default/build_config/BUILD, and tensorflow/core/platform/default/build_config.bzl), you find it's a cc_proto_library from /google/protobuf/protobuf.bzl.
Are you able to build tensorflow/core:protos_cc independently?

@andrewharp
You don't need to make clean if you are using fresh protobuf repos. It will be automatically created. And yes. With 0.1.2 it compiles OK.
I will explore more since I still can reproduce it

@ahumesky Does this look like a Bazel issue that was fixed between 0.1.1 and 0.1.2?

My best guess is that this was fixed by https://github.com/bazelbuild/bazel/commit/c74ee3784d3fd3a722f92c39805e57b4353a4509
When you clean out everything some pregenerated binary must be getting lost. I would suggest using Bazel 0.1.2 or later if that solves your problem. There are no Java protocol buffers used by the demo, so  figuring out a way to somehow force the unecessary //third_party:protoc to exist for < 0.1.2 builds after cleaning would be something of a hack, especially since the root issue has already been fixed.

Yes. For me, it only happens when I use 0.1.1

@jayendra13 Are you still experiencing your original problem?

'//third_party:protoc' is referring to the protoc in bazel here:
https://github.com/bazelbuild/bazel/tree/master/third_party/protobuf
https://github.com/bazelbuild/bazel/blob/master/third_party/BUILD#L20
How were you doing this step: "4- compile bazel"? If you were doing just "compile.sh compile", then the embedded tools might not have been created
@lberki may know which commit may have fixed this issue, we've done a few different things in this area

@andrewharp , Yes I am still facing the problem, this time I also tried to install bazel from ready-made shell script instead of building it. It is still giving errors!!
eddie7@albus:~/lab/tensorflow$ bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
Extracting Bazel installation...
......
ERROR: /home/eddie7/lab/tensorflow/tensorflow/tensorboard/bower/BUILD:3:1: no such package '@paper-dropdown-menu//': https://github.com/PolymerElements/paper-dropdown-menu.git: cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'.
ERROR: Loading failed; build aborted.
INFO: Elapsed time: 130.648s.

@hamidb
I'm trying to make sure I completely understand this thread. If I understand correctly, you originally encountered this issue:
"cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'."
What was the solution for you, if you found one, and how was this connected to the protobuf issue you also related here?
@jayendra13
Which version of Bazel are you using?

@lberki, @davidzchen in case they've seen this before.
@jayendra13: try searching for "cannot open git-upload-pack"  on the web and see if you can find some resources to help.  At this point it is out of scope of the TensorFlow team.

@jayendra13 - Can you paste the output of running that bazel command with --verbose_failures? Are you getting any similar errors with other remote repositories? I am wondering whether this is related to bazelbuild/bazel#587.

cannot open git-upload-pack seems to happen when the host name in the remote= attribute of git_repository cannot be resolved. Try running git clone with the URI mentioned in the offending git_repository rule. My hunch is that it won't work, and then it's a network misconfiguration.
Bazel could be more explicit about it, though.

I'm getting this error while installing from source. Any help? I'm now behind any proxy system. I'm able to access the link on chrome.
anish@anish:~/Projects/tensorflow$ bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
ERROR: /home/anish/Projects/tensorflow/tensorflow/tensorboard/bower/BUILD:5:1: no such package '@paper_styles//': Error cloning repository: https://github.com/polymerelements/paper-styles.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-styles.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-styles.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-styles.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-styles.git: cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'.
ERROR: Loading failed; build aborted.
INFO: Elapsed time: 128.161s

After doing bazel clean and running build again.. I get different error:
anish@anish:~/Projects/tensorflow$ bazel build -c opt //tensorflow/tools/pip_package:build_pip_package
ERROR: /home/anish/Projects/tensorflow/tensorflow/tensorboard/bower/BUILD:5:1: no such package '@iron_checked_element_behavior//': Error cloning repository: https://github.com/polymerelements/iron-checked-element-behavior.git: cannot open git-upload-pack caused by https://github.com/polymerelements/iron-checked-element-behavior.git: cannot open git-upload-pack caused by https://github.com/polymerelements/iron-checked-element-behavior.git: cannot open git-upload-pack caused by https://github.com/polymerelements/iron-checked-element-behavior.git: cannot open git-upload-pack caused by https://github.com/polymerelements/iron-checked-element-behavior.git: cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'.
ERROR: Loading failed; build aborted.
INFO: Elapsed time: 129.496s

Please help.

Hi
I'm trying to build a docker image on DockerHub, and I get the same error. For the full log:
https://hub.docker.com/r/nitnelave/tensorflow/builds/bbhn9ycakwkbmzyqupkzjbh/
The dependencies are installed from https://hub.docker.com/r/nitnelave/tensorflow-dependencies/builds/bujqarnnsp7hmbetck5a6ug/ , so Bazel 0.2.1
It works on my machine, but only randomly on DockerHub (and then it times out, but that's another issue).
Sadly, I have no control on the DockerHub settings, so I have no more information than you.

+cc @kchodorow
@AnishShah IIRC the problem with using the git_* rules behind a proxy has been fixed in the most recent versions of Bazel. Which version are you using?
@nitnelave It seems that your build was able to successfully clone a bunch of the other repositories and this particular failure seems to be caused by spurious errors when cloning a repository. AFAIK, the git_repository rules currently do not support retrying failures.

@davidzchen It could be useful to have a retry, or to find what is causing the problem in the cloning process... I can't reproduce it on my machine, but it's annoying to have the build system fail every other build because of this.

@nitnelave Agreed, might be good to see if we jgit supports retries. Can you open a bug on bazelbuild/bazel for the Git retry issue?
@AnishShah If you are using an old version of Bazel, can you try using the latest version and see if that works for you?

same problem here. Using the newest tf and bazel. The error message is as following:
no such package '@paper_dialog//': Error cloning repository: https://github.com/polymerelements/paper-dialog.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-dialog.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-dialog.git: cannot open git-upload-pack and referenced by '//tensorflow/tensorboard/bower:bower'. ERROR: Loading failed; build aborted.

@lightingghost Can you paste the full output from running your bazel command with --verbose_failures?

@davidzchen Thanks for helping.
I am using bazel 0.2.2b at that time, when I changed to 0.2.2, it works fine.

@davidzchen: What's the status of this?

experiencing same issue with bazel 0.3.0:
ERROR: /home/ray/tensorflow/tensorflow/tensorboard/bower/BUILD:5:1: no such package '@paper_radio_group//': Error cloning repository: https://github.com/polymerelements/paper-radio-group.git: cannot open git-upload-pack caused by https://github.com/polymerelements/paper-radio-group.git: cannot open git-upload-pack caused by Connection reset and referenced by '//tensorflow/tensorboard/bower:bower'.
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted.
INFO: Elapsed time: 19.680s

@davidzchen Friendly ping, do you have any update on this?

Sorry for the wait. This fell off my radar, and I just returned from vacation.
bazelbuild/bazel#1408 is the tracking issue for Git rules written in Skylark. @nelhage has already committed an initial implementation of the Skylark Git rules. There is still some work to do before we can fully migrate over, but in the meantime, you can give them a try by load()ing @bazel_tools//tools/build_defs/repo:git_repositories.bzl. These rules should be drop-in replacements for the Java ones and use the Git binaries installed on your system rather than jgit.
Note that it seems the Git binaries also do not support retries. If you are still having the same issue with the Skylark Git rules, then we should look into making use of git-retry, which is included with Chromium's depot_tools and not the standard Git distribution.

Closing due to lack of recent activity. Please open a new issue referencing this one if it is still an issue. Thanks!


Distinguish G12 recovery suppliers

Trello: https://trello.com/c/KikQx3R2/593-as-a-g12-recovery-supplier-i-can-see-something-other-suppliers-cannot
We had an outage during G12 closing. Some suppliers will be involved in a recovery process to account for the outage causing them to fail to submit their services in time.
We have previously provided a list of the affected supplier IDs via the environment - see alphagov/digitalmarketplace-credentials#359 and alphagov/digitalmarketplace-aws#797. This PR allows suppliers who are part of the G12 recovery to create G12 draft services when G12 is not 'open'. Tests show that this is working correctly.
We don't expect real suppliers to use this API endpoint - we hope to have loaded all their drafts into the system already. However, we will need the ability to create draft services for testing with.
This also shows that we've wired everything up correctly.

Force pushed to fix flake 8 error. Will merge once Travis wakes up - or once we've switched to Github actions.


dbus not found

 jack-select
Traceback (most recent call last):
  File "/usr/local/bin/jack-select", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3088, in <module>
    @_call_aside
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3072, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 574, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 892, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 778, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'dbus-python' distribution was not found and is required by jack-select

I am under ubuntu 18.04, and python3-dbus is installed. When I run the python3 interpreter, and issue an " import dbus ", it is working as expected. I did a "sudo make install" install, which installed to /usr/local

Yes, unfortunately the dbus-python package, when installed via your Linux distribution's packages, does not register itself correctly as a setupotools compatible package. Thatswhy I patch the setup.py file to remove the explicit dbus-python dependency in my AUR package for jack-select.
The dbus-python package has been marked as outdated now, so I should probably switch to pydbus, but that will probably not happen for another few weeks.
I can only recommend to either edit the setup.py file yourself and remove the dbus-python dependency or install jack-select into a virtualenv. This will install all the dependencies (dbus-python, PyGObject and pyxdg) from PyPI instead of from your distribution packages and will install them into the virtualenv in a way that satisfies the setuptools dependency check. You'll need to have a compiler and the python development headers installed, though (install package build-essential and python3-dev), since some packages are not available as binary wheels on PyPI and need to be compiled on your system (e.g. pycairo).

ok. thanks
removing python-dbus package from install_requires, I get
update-desktop-database -q
gtk-update-icon-cache /usr/local/share/icons/hicolor
gtk-update-icon-cache: No theme index file.
Makefile:25: recipe for target 'install' failed
make: *** [install] Error 1

because of gtk-update-icon...
then when I run it:
jack-select

(jack-select:7231): Gtk-WARNING **: 22:06:37.806: Theme parsing error: gtk.css:3841:23: Junk at end of value for outline-offset
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in activate_name_owner
    return self.get_name_owner(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in get_name_owner
    's', (bus_name,), **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'de.chrisarndt.JackSelectService': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/jackselect/jackselect.py", line 363, in main
    client = get_dbus_client(bus)
  File "/usr/local/lib/python3.6/dist-packages/jackselect/jackselect.py", line 337, in get_dbus_client
    obj = bus.get_object(DBUS_NAME, DBUS_PATH)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name de.chrisarndt.JackSelectService was not provided by any .service files

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/jack-select", line 11, in <module>
    load_entry_point('jack-select==1.1.0', 'console_scripts', 'jack-select')()
  File "/usr/local/lib/python3.6/dist-packages/jackselect/jackselect.py", line 376, in main
    JackSelectApp(bus)
  File "/usr/local/lib/python3.6/dist-packages/jackselect/jackselect.py", line 176, in __init__
    self.load_presets()
  File "/usr/local/lib/python3.6/dist-packages/jackselect/jackselect.py", line 196, in load_presets
    ) = get_qjackctl_presets(qjackctl_conf)
  File "/usr/local/lib/python3.6/dist-packages/jackselect/qjackctlconf.py", line 49, in get_qjackctl_presets
    preset, setting = name.split('\\', 1)
ValueError: not enough values to unpack (expected 2, got 1)

It seems that your QjackCtl.conf file has a line in the [Settings] section, which does not conform to the expected format.
Did you create any presets with QjackCtl at all before starting jack-select? Can you post the contents of the [Settings] section of your QjackCtl.conf  file here? It should be in the ~/.config/rncbc.org/ directory.

[Settings]
Audio=0
Chan=0
Dither=0
Audio=0
Chan=0
Dither=0
Driver=alsa
Frames=2048
HWMeter=false
HWMon=false
IgnoreHW=false
InChannels=0
InDevice=
InLatency=0
MidiDriver=none
Monitor=false
NoMemLock=false
OutChannels=0
OutDevice=
OutLatency=0
Periods=3
PortMax=256
Priority=6
Realtime=true
SampleRate=44100
Server=/usr/bin/jackd
ServerName=
ServerSuffix=
Shorts=false
SoftMode=true
StartDelay=2
Timeout=500
UnlockMem=true
Verbose=false
Wait=21333
WordLength=16
I have some startup scripts defined, could that be the source of the error? qjackctl version is qjackctl_<IP_ADDRESS>git.06f15c-1_amd64 from rui's suse-openbuildserver repository

The problem was, that if you have only the default preset saved in QjackCtl, its configuration file, resp. the Settings section, has a slightly different format than when you have one or several custom presets, and jack-select didn't handle this correctly. This should be fixed in version 1.1.1, which I just released.
I also tweaked the Makefile to ignore the error when running gtk-update-icon-cache and added some hints to the readme on how to solve installation problems.

I opened #2 to track the task of replacing dbus-python. I'll close this issue, since the other issues you mentioned should be fixed. Feel free to re-open this issue if you still have problems regarding these issues with version 1.1.1. If you should encounter other problems, please open a new issue.

thanks a lot!
I always wanted to have means to visually see the status of JACK, and not having cadence or qjackctl running for that.
Very cool to have one now. The Presets integration tops it - Really handy if you have more the one device and you switch often
Schoene gruesse aus der Steiermark ;-)


Updated the project to Swift 3 beta 6

We needed to keep in sync with Swift 3 beta 6. There were some important changes in beta 6 that affect the project, including some limitations in how literal support is implemented. It pulls back some of that support, and changes with type inference make other parts a little trickier. Hopefully this pull request will meet all the needs of the project. Let us know if there's anything we can do to make the transition easier or help in any way. Thanks!

Thank you for sending this PR.
I know you send this first, but I kinda started merge from the top.
Anyway, we have landing swift3 support in master branch.
Feel free to give it a go.
🍻


AsyncSnapshot should have stackTrace

Use case
Dart's Streams are really powerful. One feature of them is that they can contain StackTraces.
By calling stream.onError((error, stackTrace) { … }) developers can retrieve StackTraces along with the errors.
AsyncSnapshots, which are Flutter's representation of the status of a Stream or a Future at a specific point in time, don't have the option to contain a StackTrace though.

StreamBuilder<T>(
  stream: someStream.onError((error, stackTrace) {
    throw ErrorAndStackTrace(error: error, stackTrace: stackTrace);
  }),
  builder: (context, snapshot) {
    if (snapshot.hasError) {
      final errorAndStackTrace = snapshot.error as ErrorAndStackTrace;
      final error = errorAndStackTrace.error;
      final stackTrace = errorAndStackTrace.stackTrace;
      …
    }
  },
);

Proposal
I think it would be really great if AsyncSnapshot could also contain a stackTrace field, which can optionally contain a StackTrace if (and only if) the error is non-null. Then, FutureBuilder and StreamBuilder could both populate the field whenever possible.

Hi @marcelgarus
I believe your proposal is legitimate,
but I'm not sure if it belongs to flutter or dart itself
in the doubt I'll keep the issue open for the time being
thank you for your contribution

Hmm. AsyncSnapshot is defined in the Flutter repo, so I'm pretty sure it's Flutter-specific.

Ohh man this really bothers me, it's like driving a car while looking through the back window. Just wanted to add the error message. This is what I get when an Exception in a Stream used by a Streambuilder throws:

So big upvote on this one!

This is such high benefit and so trivial to implement. I am thinking about contributing this feature, however, I have the feeling that code review will bite me because testing it is propably a pain (given that AsyncSnapshot is used so much).

The fact that nobody has even started a PR makes me want to do this now 🤔

tagging @TahaTesser for visibility
I agree with @creativecreatorormaybenot 's statement above

I am working on a PR for this 👍

My PR (#69507) has been merged into master 🎉
AsyncSnapshot has a stackTrace property now - so you can use snapshot.stackTrace if the snapshot has an error 😃


More usage examples for continuous motor control?

Hi, I was trying powered-up the other day and I noticed a pretty big delay when trying to control motors using a controller.
I assume this is because I keep sending StartPowerAsync and awaiting it, which seems to be expensive performance wise?
All of this happens inside of a while-loop, so the code is running as fast as it can, though waits for the Bluetooth commands to go through.
If StartPowerAsync isn't the way to control motor speed continuously, what is? I'd love some more examples on how this can be accomplished.
if (currentAccelerationValue != lastAccelerationValue)
{
    await aMotor.StartPowerAsync(currentAccelerationValue);
    lastAccelerationValue = currentAccelerationValue;
}

if (currentTurnValue != lastTurnValue)
{
    await bMotor.GotoPositionAsync((sbyte)(currentReading.LeftThumbstickX * 90), 100, 100, SpecialSpeed.Brake);
    lastTurnValue = currentTurnValue;
}

Yes, there is a Bluetooth Ping Pong. Problem with the protocol is that hubs have a buffer ... so if you send them commands too fast, they might drop them.
So let me see how I can help you. From your code snippet, I assume you have somewhere input for currentAccelerationValue and currentTurnValue which you synchronize into the motor using that loop.
Depending on your use case I would recommend on of the following:

directly dispatch from your UI or handler or whatever the command and await the feedback. Bluetooth should be much faster than your UI input.
considering that a loop with Bluetooth may take some ms .... maybe implement a threshold when you start sending commands to it
you do not need to await the response of the StartPowerAsync / GotoPositionAsync, you can just let them hang or you can resolve the tasks later. There is a risk that you having commands being dropped by the motor in this case. There is a risk that the dispatching of the commands to the bluetooth stack is out of order because you would also skip the await for the SendMessage and not only for the receiving.
if all of the above is not matching your use case, you can consider

directly using the ILegoWirelessProtocol as demonstrated in the README. The related motor messages you can see in the implementation of the motor.
I am also open for a pull request if you want to implement a "fast-mode" in the StartPowerAsync method.

The detailed feedback is much appreciated, thanks!
I'll give it a shot later and see if I can get it to work faster. It's good to know about the command drops and out-of-order delivery if you send too fast. Maybe a threshold will work just fine.

For whoever comes across this, I ended up solving it using a command pool. Basically, waiting for every command to complete is too slow, but sending them all at once overloads the device's buffer.
// initialization
    List<Task> commandPool = new List<Task>();
    const int maxCommands = 2;

// trying to send commands every tick
if (commandPool.Count < maxCommands) {
    commandPool.Add(aMotor.StartPowerAsync((sbyte) -currentAccelerationValue));
}

// remove completed commands every tick
commandPool.RemoveAll(t => t.IsCompleted);

Cool. If you have other questions, just create an issue


Problem installing slime on OS X 10.10

I get the following error when oh-my-emacs is setting up slime:
slime.texi:6: warning: unrecognized encoding name `UTF-8'.
slime.texi:6: Unknown command `codequoteundirected'.
slime.texi:7: Unknown command `codequotebacktick'.
makeinfo: Removing output file `/Users/esteban/.emacs.d/el-get/slime/doc/slime.info' due to errors; use --force to preserve.
make: *** [slime.info] Error 1
--force```

Ah, you're a lazy guy, ^_^
https://github.com/xiaohanyu/oh-my-emacs/issues/85
https://github.com/xiaohanyu/oh-my-emacs/issues/120
https://github.com/xiaohanyu/oh-my-emacs/commit/140825dc0d47c84a91cbba043e0a4fe7246f7d95

Thanks.  That fixed it.


[FLINK-15635][table] Now EnvironmentSettings accepts the user ClassLoader

This PR solves the issue of allowing the user to provide its own classloader for UDFs and at other places where it's more appropriate than the current Thread context classloader.
The PR also contains a couple of hotfixes (mergeable separately):

Deprecate CatalogFunction#isGeneric
Remove CodeGeneratorContext#apply which makes the code unnecessarily more complicated
Fix singleton config in EnvironmentSettings, which among various issues, it's also causing in this case to select the wrong user class loader

Thx!

If we don't choose to backport the functionality to 1.15, we need to backport the fix for EnviromentSettings with the static variables.

@slinkydeveloper Thanks for your contribution, can you help to rebase the master and push this pr merge to master, here some other work rely on you.

Working on rebasing and reshaping this PR

ping @slinkydeveloper

I don't think I'll be able to finish this PR, can someone take it over?

I'm working on it: https://github.com/matriv/flink/tree/FLINK-15635-new already.

ping @matriv Can you help to complete this work as soon as possible? FLIP-214 is blocked by this issue now, thanks.

ping @matriv Can you help to complete this work as soon as possible? FLIP-214 is blocked by this issue now, thanks.

Hi, @matriv , If you don't have time to complete this work, I will take over it, thanks.

Due to @matriv had not responsed for a long day, I will take over this ticket, thanks for all works.

Continue the review work in #19845


feat: on page load handler

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Checklist

[ ] This PR will resolve #___
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[x] I have added a convincing reason for adding this feature, if necessary
[x] It can be built on all targets and pass CI/CD.

Other information

I haven't added the change files yet and I need to test the Mac implementation, which I'm the most uncertain about, but thought I'd put this out there for early feedback.

I've added all three handlers and I believe addressed all concerns and comments.

I'm just going to remove the handler for navigation starting.

LGTM but I will keep the PR open a while for @wusyong and @lucasfernog to give their approvals too

LGTM but there's still a clippy error.

I would consider using a single event function with_on_page_load_handler with an enum payload PageLoadEvent { Started, Finished } instead of two separate functions.

@wusyong There is a clippy error, but I'm not sure how you all would like it resolved. The error is due to new lints applied to old code, not anything that I added. The issue is a structure that is a unit class for some environment and not for others so default is used to create it, but using default to build a unit struct is now a clippy violation. I think the most straight forward is to add a lint exclusion, but it's possible you want a different solution.
@lucasfernog I could make that change.


Add tests for ByteArrayExtensions

Fixed up some bugs found while testing.
Added UTF32 Big Endian
Closes #4

Arguable, but you have a point.
Will verify in the morning that ...GetBytes() returns the proper encoding markers also, to make sure it is testing a as close to real life situation as possible.
If so will gladly update the PR.
While I have your attention, any thoughts on how to identify a UTF16 file with zero in first two bytes after marking as opposed to thinking it is UTF32?

@Teodor92 fixed the issue with using the FS in the tests.

@M-Zuber, I can't think of a better approach than the additional check bytes.Length % 4 == 0 added to the check for UTF-32. UTF-32 encoding is 4 bytes fixed-width and UTF-16 is variable 2 or 4 bytes so the check won't catch all cases correct but the change of getting the correct encoding is higher.
PS I'm sorry for my late answer. I was very busy last week...

@vladislav-karamfilov thanks for the tip, added a check + test for a UTF16 buffer with leading zeros.
So this should be finished and ready to merge

It looks good to me. Just a few improvements in a comment and I can merge it. :-)

Comments updated. Thanks.


🏛Smart Maps Denkmal

Create a convenient list of Smart Maps XXX brands as discussed in #163. The list would like:
SMA: Smart Maps Assistant
SMB: Smart Maps Bazaar
SMC: Smart Maps Community (reserved)
SMD: Smart Maps Documentation
SME: undefined
SMF: undefined
...
The definition of undefined and reserved would follow the definitions in programming language specifications ;-)

Complete. https://unopengis.github.io/smart-maps-denkmal/


TypeError: Can only call Navigator.javaEnabled on instances of Navigator

This error happened with one of our clients:
Error message: Can only call Navigator.javaEnabled on instances of Navigator
https://github.com/snowplow/snowplow-javascript-tracker/blob/4e52a258dba248d824c360941caadd338f9e4490/src/js/lib/detectors.js#L224
{
 "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.78.2 (KHTML, like Gecko) Version/7.0.6 Safari/537.78.2",
  "userAgentInfo": {
    "browserName": "Safari",
    "browserVersion": "7.0.6",
    "engineName": "AppleWebKit",
    "engineVersion": "537.78.2",
    "isBot": false,
    "isMobile": false,
    "os": "Intel Mac OS X 10_9_4",
    "platform": "Macintosh"
  },

Thanks for reporting this @christoph-buente. Surprisingly, I can't find any Google results for "on instances of Navigator". It's strange that window.navigator wouldn't be an instance of Navigator...

It's happening in an old Safari 7, not sure if that is relevant. But i thought i give a notice, that those things are happening. Browser compliance is a minefield.


Testing with production bits

We're testing with dev builds which don't always catch issues like the one in #7443. We need to update our tests to support testing with production bits.

How we'd potentially want to do it: https://github.com/microsoft/azuredatastudio/blob/master/scripts/test-integration.bat#L15-L24

https://github.com/microsoft/azuredatastudio/pull/7507


Update rucocop

Updated rubocop
Adds bin/update_rubocop for easy updating
Adds cron GH action to run every Sunday and automatically create a PR

Tested locally, and looks good.

Actually, isn't working as well as I thought, the actual bundle update fails....

My fault. Think I was adding single comments by accident instead of one whole one, all good though 👍


Support for set_security_user ingest processor

I was going to use document-level security feature, but stuck with the fact that I cannot restrict users to access only their documents.
Such use case is described here: Pre-processing documents to add security details. And it turns out that set_security_user feature seems not implemented in OpenDistro:
PUT _ingest/pipeline/my-pipeline-id
description: set user
processors:
  - set_security_user:
      field: user
---
error:
  root_cause:
  - type: "parse_exception"
    reason: "No processor type exists with name [set_security_user]"
    header:
      processor_type: "set_security_user"
  type: "parse_exception"
  reason: "No processor type exists with name [set_security_user]"
  header:
    processor_type: "set_security_user"
status: 400

Would it possible to implement this processor? Is there any workaround?

Hi @dpotapov,
Yes, there is a way you can restrict user to just access their own documents using DLS (doc level security).
Consider employees index in which each document has a field called manager, which contains the username of the employee’s manager. Each logged in user should only have access to employees he/she manages. You can do it by defining DLS query as below:
employee:
  index_permissions:
    - index_patterns:
      - 'employees'
      allowed_actions:
        - ...
      dls: '{"term" : {"manager" : "${user.name}"}}'

Let me know if you have furthre questions!

DLS does not solves the problem when the user can overwrite data that belong to another user.


New UI Design Contribution

Make sure you have read our contributing guidelines before submitting this issue.
Name
Suxz
Figma Community URL
https://www.figma.com/community/file/1211276735395024758
Your Figma Profile
https://figma.com/@irhammshidiq

Thank you for your contribution, @xevorte! I will add the design to the collection.


Any way to catch uncaught exceptions?

In the browser, we have window.onerror, but that doesn't seem to work in Tabris.js apps. Is there an equivalent method for capturing uncaught exceptions in a Tabris app in order to setup exception notifications with a service like Rollbar/Airbrake/etc.
Couldn't find anything in the documentation about exception handling, so forgive me if I'm asking an already answered question.

I think a master try/catch would be the only way.

Yeah I'll give that a shot.
It's my understanding that window.onerror works in Cordova; any idea why it wouldn't work in Tabris built on top of Cordova?

Cordova leverages the device's WebView and since it's operating in a browser it has all the capabilities of a browser.  Tabris.js uses a JavaScript engine for all commands, so all the browser-specific elements have to be re-implemented.

What would it take to re-implement root-level uncaught exception handling using Tabris' JS engine? The master try/catch would work for simple programs but anything that goes async wouldn't be caught by that.

A request for the global error event handler has already been made here. https://github.com/eclipsesource/tabris-js/issues/1033. Unfortunately we haven't gotten around to it yet.

Right, so let's close it as a dup.

Sounds good thanks all. I'll track it on the other issue.


Set up security groups, subnets, etc. as part of CDK

Addressed in https://github.com/petergtz/g2s3/commit/5689db3d5bd6ced8caae9b2f65d36c78adf82d80


Generate SLSA Build L3 provenance

Hi 👋
I'm Ian, working on behalf of Google and the Open Source Security Foundation (OpenSSF) to help open source projects to improve their supply chain security.
After some analysis minimist showed up as one of the top transitive dependencies in the JavaScript/Node ecosystem.
I would like to offer help update minimist builds to generate a SLSA Build Level 3 Provenance. The Supply chain Levels for Software Artifacts, or SLSA (salsa) framework aims to improve security in the build process by defining increasing levels of build integrity.
Now that npm supports distributing package provenance via the official npm registry, I think this would be a good time introduce provenance generation to minimist.
Given minimist is such a highly used package, I suggest generating SLSA Build L3 provenance using the Node.js Builder reusable workflow for GitHub Actions. This would provide the highest level of integrity for the build while hopefully being a fairly simple publish workflow.
Would the minimist project be open to a PR introducing these changes?

Add a publish.yml to call the Node.js builder workflow and publish the resulting package when a new tag is created. This could alternatively be run manually via workflow_dispatch.
README: A brief description for end-user to know how to verify the package integrity using the generated provenance.
README: A SLSA Level 3 badge (optional)

Thanks Ian. I will pay attention, but the conversation for this project is likely to be driven by @ljharb who handles the releases.

Thanks! @ljharb is everywhere! Jordan and I have interacted elsewhere so perhaps we can work something out.

In general, I'm opposed to publishing from CI because it can only be done with either 1) a single factor, which is objectively way less secure than publishing locally with 2FA, or 2) a process that can sit and wait for the OTP code, or the web auth link to be visited, which for the former requires trusting a separate server (not github) and i haven't tried out the latter yet.
Additionally, npm's provenance feature guarantees only the publish location, and I haven't yet seen anyone demonstrate why that's valuable nor a single security incident that would have mitigated, so I'm hopeful there's evidence I'm unaware of :-)

I'm going to close this for now; I continue to have not been shown a single concrete incident that publish provenance would have prevented, and since we don't have a build process at all, the git repo always precisely matches the published package, so there's no better form of verification achievable.
I will always be happy to reopen this if I'm shown persuasive evidence :-)


Spelling error with discriminator for oneOf nodes

Discriminator references for oneOf have a spelling error. If I put a discriminator in my schema, it gets referenced by node.deciminator instead of node.descriminator (the 'r' is missing in the word).
node.discriminator gives this error in ruby:
*** NoMethodError Exception: undefined method 'discriminator' for <Openapi3Parser::Node::Schema:0x00007f9872942480>
But node.disciminator  gives Openapi3Parser::Node::Discriminator(#/components/schemas/xx/yy/zz/discriminator)
Workaround is to use node['descriminator']

Thank you @kerrgibson - I've fixed this in 0aaf26e5 and have released 0.8.1 with a fix for this issue.

Thanks. I like this product.

On May 11, 2020, at 7:39 PM, Kevin Dew<EMAIL_ADDRESS>wrote:
Thank you @kerrgibson https://url.emailprotection.link/?buEq4eyNl9NRYRhKUfm4VcB3vTj4i-rK8VCwtr1KPZXd2Ge2z3vBuilOCovLd0ur67G-zSMuy-GPyem_4_x3gepB6ci4XnRAKVZg21ioRMOVCzygrCMtKcxUmO-JK3UH5 - I've fixed this in 0aaf26e https://url.emailprotection.link/?b0x4ul4zOhcIJvZRNeS24AlAEJ55S6QZ8BXaZw2To-NAZiixrI5R1tMuSSGKAHe0ZQpPqWM4hRXfnzB5ecigzPi5XnWJIZrMox70Wys5Evpcf8xvuHrn_NqH061acF0ME8_UXf5f1tNj3QwV5-GfXH0a1P2GDV2O1jS6ij3PlnvQ~ and have released 0.8.1 with a fix for this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://url.emailprotection.link/?boJyVaA8SwqP41YoEK_LlpCA5bDo3lAQBU7Cj6b02DmT7iagfMD8X6gmh-s3q9kPKOg11eN5oNKxSeeGoqgx44Sp6sEAjENXnhH2nEqPTiN81wTaJ3qv13D2HPHLt_txViNMrna0--q_TIY8ezfUGsHUdejvUE_y6bVgIcsvKTZs~, or unsubscribe https://url.emailprotection.link/?byODWZ7yxtiC034i8xyTcEMEFi0Mc5APQZqpek_qGU9uVTFc2DdwZJmNvdjf6LgR0d3Teg_FJZP_105EQzerDAzEH8YUgBhzsw4p65FBuA2DZ8wMmyTH19p_fqxUTxILKCnokQ8esiXfwBYGx808gl2DQUJ08nXneGDGi6dTtsZDb0eocj36SKH4MfZCJYxYOJ6Y_Qu29BPA_zv7MW2xT3w~~.

William “Kerr” Gibson, CTO
America's Floor Source http://americasfloorsource.com/
3442 Millennium Ct., Columbus, Ohio 43219
Telephone:<PHONE_NUMBER> | Fax:<PHONE_NUMBER> | Mobile:<PHONE_NUMBER>


Change color of the notification number

Hey,
I was wondering if there is a way to change the color of the notification number. In my app the notification number is almost unreadable due to its color, as you can see on the attached image.

Well, actually I'm working to add the Dark Theme to the Drawer, because If you see your drawer use the Light theme, but you are using MaterialNavigationDrawer theme, that should be dark.
See the main issue #76

Ohhh I see, thank you very much!

How do you manage to draw lines on top and bottom of "konversation" ?


The ability to make a room private

Only people with a link or at least the ability to turn the privacy on and off so people can join

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Thanks for feedback, this is already on the list - see #16


[Bug] DBT unit tests don't work properly when source table name matches another source or model

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
One of my models had the same name as the source Snowflake table. They live in different schemas. dbt run works fine and generates all the data as expected. However, DBT unit tests fail because unit tests can not differentiate mocked source tables from these tables. Here is an example:
unit_tests:
  - name: test_model_1
    description:
    model: MODEL_1
    overrides:
      macros:
        is_incremental: true

    given:
      - input: this
        rows:
          - { column_1: "1", column_2: "2" }

      - input: source('src', 'MODEL_1')
        rows:
          - { column_1: "1", column_2: "3" }

    expect:
      rows:
        - { column_1: "1", column_2: "3" }

When I checked the generated SQL query, I saw that it adds __dbt__cte__ prefixes to the CTE names and replaced raws for source('src', 'MODEL_1') with values from this.
Expected Behavior
Fix unit tests to support identical model and source table names in different schemas.
Steps To Reproduce

Create a model that relies on a table with the table's exact name
Create an incremental unit test and add data both for the source table and this (the model itself)
Run the unit test and see its outcome

Relevant log output
No response
Environment
- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?
snowflake
Additional Context
No response

Thanks for reporting this @yengibar-manasyan-sp !
Root cause
It appears that the root cause is that during unit testing, sources aren't guaranteed to have a CTE that is unique from refs or other sources.
Example
See below for a reproducible example ("reprex") of the issue you reported when a model and a source have the same name (case_1). It also includes a separate issue when two sources have the same name (case_2).

Reprex

dbt_project.yml
name: "my_project"
version: "1.0.0"
config-version: 2

models/model_a.sql
select -1 as id

models/model_b.sql
select -2 as id

models/case_0.sql
select * from {{ ref("model_a") }}

union all

select * from {{ ref("model_b") }}

models/case_1.sql
select * from {{ ref("model_a") }}

union all

select * from {{ source("src_2", "model_a") }}

models/case_2.sql
select * from {{ source("src_1", "model_a") }}

union all

select * from {{ source("src_2", "model_a") }}

Create some sources that just point to the database objects created by a couple of our models 😂
models/_sources.yml
sources:

  - name: src_1
    schema: "{{ target.schema }}"
    tables:
      - name: model_a

  - name: src_2
    schema: "{{ target.schema }}"
    tables:
      - name: model_a

models/_unit_tests.yml

unit_tests:

  - name: test_case_0
    description: "Unit test SQL: target/run/my_project/models/_unit_tests.yml/models/test_case_0.sql"
    model: case_0
    given:
      - input: ref("model_a")
        rows:
          - { id: 1 }
      - input: ref("model_b")
        rows:
          - { id: 2 }
    expect:
      rows:
          - { id: 1 }
          - { id: 2 }

  - name: test_case_1
    description: "Unit test SQL: target/run/my_project/models/_unit_tests.yml/models/test_case_1.sql"
    model: case_1
    given:
      - input: ref("model_a")
        rows:
          - { id: 1 }
      - input: source("src_2", "model_a")
        rows:
          - { id: 2 }
    expect:
      rows:
          - { id: 1 }
          - { id: 2 }

  - name: test_case_2
    description: "Unit test SQL: target/run/my_project/models/_unit_tests.yml/models/test_case_2.sql"
    model: case_2
    given:
      - input: source("src_1", "model_a")
        rows:
          - { id: 1 }
      - input: source("src_2", "model_a")
        rows:
          - { id: 2 }
    expect:
      rows:
          - { id: 1 }
          - { id: 2 }

Commands:
dbt run -s model_a model_b
dbt build -s case_0
dbt build -s case_1
dbt build -s case_2

I get the following output:
$ dbt build -s case_0

20:42:08  1 of 2 START unit_test case_0::test_case_0 ..................................... [RUN]
20:42:08  1 of 2 PASS case_0::test_case_0 ................................................ [PASS in 0.21s]
20:42:08  2 of 2 START sql view model feature_456.case_0 ................................. [RUN]
20:42:08  2 of 2 OK created sql view model feature_456.case_0 ............................ [OK in 0.12s]
20:42:08
20:42:08  Finished running 1 unit test, 1 view model in 0 hours 0 minutes and 0.54 seconds (0.54s).
20:42:08
20:42:08  Completed successfully

$ dbt build -s case_1

20:41:15  Failure in unit_test test_case_1 (models/_unit_tests.yml)
20:41:15

actual differs from expected:

@@ ,id
---,1
   ,2
+++,2

$ dbt build -s case_2

20:42:57  1 of 2 START unit_test case_2::test_case_2 ..................................... [RUN]
20:42:57  1 of 2 ERROR case_2::test_case_2 ............................................... [ERROR in 0.03s]
20:42:57  2 of 2 SKIP relation feature_456.case_2 ........................................ [SKIP]
20:42:57
20:42:57  Finished running 1 unit test, 1 view model in 0 hours 0 minutes and 0.23 seconds (0.23s).
20:42:57
20:42:57  Completed with 1 error and 0 warnings:
20:42:57
20:42:57    Compilation Error in unit_test test_case_2 (models/_unit_tests.yml)
  Unit_Test 'unit_test.my_project.case_2.test_case_2' (models/_unit_tests.yml) depends on a source named 'src_1.model_a' which was not found

Looking at the output files like the following helps highlight what is going wrong:

target/run/my_project/models/_unit_tests.yml/models/test_case_0.sql
target/run/my_project/models/_unit_tests.yml/models/test_case_1.sql

Acceptance criteria
The key outcome we'd need is:

each node in the DAG to have a corresponding CTE name that is guaranteed to be unique from that of every other node in the DAG (regardless of node type like source, model, seed, snapshot, etc.).

A possible building block
One thing that is already to be unique across the DAG is unique_id, so possibly that could be transformed into a suitable CTE name.
Relevant code
Some of the relevant code is described in https://github.com/dbt-labs/dbt-core/issues/5273#issuecomment-1131543844.
https://github.com/dbt-labs/dbt-adapters/pull/236 and https://github.com/dbt-labs/dbt-core/pull/10290 have proposed updates to the code that generates the CTE name, but I don't think either would fix this particular issue with unit tests.

Relevant code
https://github.com/dbt-labs/dbt-core/blob/c668846404c78ea7317dc0523b49703c61c9885f/core/dbt/context/providers.py#L1595-L1600
Specifically, we could generate some kind of globally_unique_identifier and then use it like this:
            return self.adapter.Relation.add_ephemeral_prefix(globally_unique_identifier)

Implementation ideas
Here are a couple ideas of how to create the CTE in unit tests so that they are unique:

Use a quoted version of unique_id + quoted identifiers
Use a hexadecimal formatted hash of the unique_id + quoted identifiers

1. Use a quoted version of unique_id + quoted identifiers
Example:
with "__dbt__cte__source.my_project.src_1.model_a" as (
...
),
"__dbt__cte__model.my_project.model_a" as (

Pros:

Retains and utilizes uniqueness of the unique_id
Doesn't transform the unique_id at all -- just quotes it
Preserves readability of the CTE name
Would also solve the problem described in dbt-core #5273

Cons:

Not sure if data warehouses commonly allow CTE names to have quoted identifiers or not 🤷

2. Use a hexadecimal formatted hash of the unique_id + quoted identifiers
Examples:
with __dbt__cte__e83c5163316f89bfbde7d9ab23ca2e25604af290 as (

or
with __dbt__cte__dim_customers_e83c5163316f as (

Pros:

Utilizes uniqueness of the unique_id
Doesn't rely upon quoted identifiers

Cons:

CTE name is either less readable or not readable at all
Not 100% guaranteed to be unique after hashing

Details
We could hash the unique_id similar to _create_sha1_hash:
https://github.com/dbt-labs/dbt-core/blob/c668846404c78ea7317dc0523b49703c61c9885f/core/dbt/task/deps.py#L56
If we don't care about readability of the CTE name, then we could just use the hexdigest as-is which for SHA1 would be a 40-character value like this:
e83c5163316f89bfbde7d9ab23ca2e25604af290

If there are readability concerns, then we could combine an abbreviated version of the hash along with the node name (or identifier), which might look like this:
dim_customers_e83c5163316f

We've just come across this issue ourselves. Are you planning contributing to this in the nearest future, @dbeatty10 ?

Did anyone find a workaround?

There’s no workaround, @jhoffland. However, if you’re using dbt-core, you could modify the code to use the full path (source name + model) or hash like previous suggested


Modern Buffer Overflows

Adds a post outlining the reasons buffer overflows exist, and examining exactly how they work. This is the first of a series of posts on the subject

On the by and large, I found this article, as a whole, impressive and informative. I look forward to future entries.

fixup! added which standardizes  on 32-bit and 64-bit. Corrects capitalization of Linux and adds a reference to https://en.wikibooks.org/wiki/X86_Assembly/X86_Architecture for more information on x86 registers

Go ahead and squash it.

squashed!

:shipit:


fix: resolving duplicate outbound address names for acl rules

Description
This is to fix the issue seen as duplicate names for acl rule. Refer issue-4501
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[x] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content

Resolved duplicate ACL rule name seen for outbound rules.

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

:tada: This PR is included in version 6.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Pin RPC raise master's cpu usage in high level

Alluxio Version:
2.3.1
Describe the bug

There is about 35TB data pined in Alluxio in disk.
Each block of the data has  3 replicas.
File size of the data is around 50MB.
Master's CPU usage is over 80%.
Users want to pin over 150TB data (not include replicas) in Alluxio, because the speed of data transformation between remote UFS and Alluxio is too slow, and the use cases have specific deadline.

Urgency
Normal

@JySongWithZhangCe Thanks for reporting, will take a look.


js9_start: command not found

After having executed source ~/.jsenv.sh in a new terminal session, js9_start is not found...
What can be cause of this? What to check?

@yveskerwyn You need to reinstall.
Please follow the documentation and close when verified


Uncaught TypeError: Cannot read property 'emit' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.9
System: Mac OS X 10.10.5
Thrown From: gulp-watcher package, v0.1.2
Stack Trace
Uncaught TypeError: Cannot read property 'emit' of undefined
At /Users/samstr/.atom/packages/gulp-watcher/lib/watcher.coffee:47

TypeError: Cannot read property 'emit' of undefined
  at /Users/samstr/.atom/packages/gulp-watcher/lib/watcher.coffee:47:29
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at BufferedProcess.module.exports.BufferedProcess.handleError (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:251:20)
  at ChildProcess.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/buffered-process.js:240:24)
  at emitOne (events.js:77:13)
  at ChildProcess.emit (events.js:166:7)
  at Process.ChildProcess._handle.onexit (child_process.js:1055:12)
  at child_process.js:1127:20
  at process._tickCallback (node.js:357:13)

Commands
     -5:18.9.0 command-palette:toggle (atom-pane.pane.active)
 11x -5:17.3.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -5:16.5.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -5:16.5.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -5:12.3.0 settings-view:open (atom-pane.pane.active)
     -5:00.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
 22x -4:48.9.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -4:33.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  3x -3:35.5.0 gulp-helper:toggle (div.settings-view.pane-item)
     -0:52.8.0 core:cancel (div.pane-item.native-key-bindings.about)
     -0:49 settings-view:open (div.pane-item.native-key-bindings.about)
     -0:00.6.0 gulp-watcher:toggle (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "term"
    ],
    "themes": [
      "atom-dark-ui",
      "monokai"
    ]
  }
}

Installed Packages
# User
angularjs, v0.3.0
gulp-watcher, v0.1.2
monokai, v0.15.0

# Dev
No dev packages

I've got some questions.

Is gulp the correct command on the OS X?
If not, what is it?


can i add some function CONFORMING TO FIPS186-4 Section B.3.3 Generation of Random Primes that are Probably Prime for fip test?

I want to gen RSA KEY CONFORMING TO FIPS186-4 Section B.3.3 and test it ,how can i do?

No description provided.

You cant. We implement B.3.6 instead.
The standards do not require you to implement all approved implementations.

Question was answered so closing.


condor_ce_trace: use python bindings for condor_ping (SOFTWARE-3030)

https://jira.opensciencegrid.org/browse/SOFTWARE-3030

Re-submitting from different branch


Trtl maintenance mode sc-2047

This PR introduces a maintenance mode for trtl that is similar to the maintenance mode we have for GDS; it allows the underlying trtl database to be accessible outside the context of normal operations (e.g. migrations, repairs, etc).
One observation is that we may want to create another story for introducing a Status endpoint for trtl, since that is not currently defined in the protos; this is probably related to the work we'll do in sc-952.

Codecov Report

Merging #258 (0ffad48) into main (671713e) will increase coverage by 0.23%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main     #258      +/-   ##
==========================================
+ Coverage   43.78%   44.02%   +0.23%
==========================================
  Files          53       53
  Lines        6052     6074      +22
==========================================
+ Hits         2650     2674      +24
+ Misses       2926     2923       -3
- Partials      476      477       +1

Impacted Files
Coverage Δ

pkg/trtl/interceptor.go
52.94% <0.00%> (-3.31%)
:arrow_down:

pkg/trtl/trtl.go
34.48% <50.00%> (+1.14%)
:arrow_up:

pkg/gds/gds.go
62.50% <0.00%> (+0.76%)
:arrow_up:

pkg/gds/admin.go
56.05% <0.00%> (+1.06%)
:arrow_up:

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 671713e...0ffad48. Read the comment docs.


Add link to fpdf2 + .id on headings in maintainer-guidelines.md

I used a small JS <script> that I have been using for a while in order to create "linkable" headings on this page,
in order for the table of content to work: https://py-pdf.github.io/pages/maintainer-guidelines.html

@MartinThoma: I disabled the Require signed commits setting on this repository in order to merge this PR.
This issue that I have is that:

I use an anonymized git user.email for my commit (which is required by the repo / org), provided by GitHub<EMAIL_ADDRESS>my GPG key does not include this anonymized GitHub email address, only my own my personal address. This leads to my commits being signed, but GitHub considering them to be "Unverified" as the signature does not match commit author email address

The only "clean" solution would be for me to re-generate a new GPG signing key that includes my Gitlab & GitHub anonymized email address, but I won't undertake this task now.
Is this OK with you or do you really wish for all commits to be signed on this repository?

By the way, how is the website published? https://py-pdf.github.io/
This does not seem automated through GitHub Actions when new commits land on the main branch:
https://github.com/py-pdf/py-pdf.github.io/actions


Error: Exceeded maximum number of revisions

Hello All
I am on CouchDB 3.3.1.
I am invoking a purge request to remove 50,000 documents, where my CouchDB contains about 150,000 documents.
I have updated local.ini with following
[purge] max_document_id_number = 100000
as well as changed the _purged_infos_limit for that couch database to 100,000 (upped from 1000 default)
In either of the cases, I am getting back error informing me
"{"error":"bad_request","reason":"Exceeded maximum number of revisions."}"
Please could you indicate what is wrong with my configuration.
Thanks.

@manurajsingh did the above suggestion help?

That helped thank you.