Qubes Polybar (Dom0 Fedora-25) build  issue.

Build Process
Describe how you build polybar, list the exact commands you are using:
All above dependencies from here
https://github.com/polybar/polybar/wiki/Compiling#compiling
git clone --recursive https://github.com/polybar/polybar
tar cvf polybar.tar polybar/
qvm-run --pass-io untrusted 'cat /home/user/polybar.tar' > polybar.tar
tar xvf polybar.tar
cd polybar/
mkdir build
cd build
cmake ..
make -j$(nproc)
sudo make install

If you build polybar directly from this repository:

Output of git describe --tags:

git describe --tags
3.4.0-69-g8d07f2a

If you use some other way (like the AUR):
List exactly where you are building from and which version you are building.
Build Log
Post everything that is output to the terminal while building polybar below. This HAS to include the output of the cmake and make commands, if you used them.
[dom0 build]$ cmake ..
-- Trying to enable ccache
-- Couldn't locate ccache, disabling ccache...
-- The CXX compiler identification is GNU 6.4.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could not detect version with git, falling back to built-in version information.
-- No build type specified; using Release
-- Using supported compiler GNU-6.4.1
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Checking for module 'cairo-fc'
--   Found cairo-fc, version 1.14.8
-- Checking for module 'alsa'
--   Found alsa, version 1.1.1
-- Checking for module 'libcurl'
--   Found libcurl, version 7.51.0
-- Checking for module 'libmpdclient'
--   Found libmpdclient, version 2.9
-- Checking for module 'libnl-genl-3.0'
--   Found libnl-genl-3.0, version 3.2.29
-- Checking for module 'libpulse'
--   Found libpulse, version 10.0
-- Checking for module 'xcb-composite'
--   Found xcb-composite, version 1.12
-- Checking for module 'xcb-xkb'
--   Found xcb-xkb, version 1.12
-- Checking for module 'xcb-randr'
--   Found xcb-randr, version 1.12
-- Checking for module 'xcb-randr>=1.12'
--   Found xcb-randr, version 1.12
-- Checking for module 'xcb-xrm'
--   Found xcb-xrm, version 1.2
-- Checking for module 'xcb-cursor'
--   Found xcb-cursor, version 0.1.3
--  Build:
--    Version: 3.4.0
--    Type: Release
--    CXX: /usr/bin/c++  -Wall -Wextra -Wpedantic -O2 -DNDEBUG
--    LD: /usr/bin/ld
--  Install Paths:
--    PREFIX:  /usr/local
--    BINDIR:  /usr/local/bin
--    DATADIR: /usr/local/share
--    DOCDIR:  /usr/local/share/doc/polybar
--    MANDIR:  /usr/local/share/man
--  Targets:
-- [X]   polybar-msg
-- [ ]   testsuite
-- [X]   documentation
--  Module support:
-- [X]   alsa (1.1.1)
-- [X]   curl (7.51.0)
-- [X]   i3
-- [X]   mpd (2.9)
-- [X]   network (libnl) (3.2.29)
-- [X]   pulseaudio (10.0)
-- [X]   xkeyboard (1.12)
--  X extensions:
-- [X]   xcb-randr (1.12)
-- [X]   xcb-randr (monitor support) (1.12)
-- [X]   xcb-composite (1.12)
-- [X]   xcb-xkb (1.12)
-- [X]   xcb-xrm (1.2)
-- [X]   xcb-cursor (0.1.3)
--  Log options:
-- [X]   Trace logging
-- The C compiler identification is GNU 6.4.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Checking for module 'xcb-proto'
--   Found xcb-proto, version 1.12
-- Found PythonInterp: /usr/bin/python3.5 (found suitable version "3.5.4", minimum required is "3.5")
-- XCB[XCB]: Found component XCB
-- Found XCB_XCB: /usr/lib64/libxcb.so
-- XCB[ICCCM]: Found component ICCCM
-- Found XCB_ICCCM: /usr/lib64/libxcb-icccm.so
-- XCB[EWMH]: Found component EWMH
-- Found XCB_EWMH: /usr/lib64/libxcb-ewmh.so
-- XCB[UTIL]: Found component UTIL
-- Found XCB_UTIL: /usr/lib64/libxcb-util.so
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB_IMAGE: /usr/lib64/libxcb-image.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so
-- Searching for xcbgen with python
-- Found xcbgen in /usr/lib/python2.7/site-packages
-- XCB[RANDR]: Found component RANDR
-- Found XCB_RANDR: /usr/lib64/libxcb-randr.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so;/usr/lib64/libxcb-randr.so
-- XCB[COMPOSITE]: Found component COMPOSITE
-- Found XCB_COMPOSITE: /usr/lib64/libxcb-composite.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so;/usr/lib64/libxcb-randr.so;/usr/lib64/libxcb-composite.so
-- XCB[XKB]: Found component XKB
-- Found XCB_XKB: /usr/lib64/libxcb-xkb.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so;/usr/lib64/libxcb-randr.so;/usr/lib64/libxcb-composite.so;/usr/lib64/libxcb-xkb.so
-- xpp: including xcb proto composite.xml
-- xpp: including xcb proto randr.xml
-- xpp: including xcb proto xkb.xml
-- xpp: including xcb proto xproto.xml
-- Checking for module 'jsoncpp>=1.7.7'
--   Found jsoncpp, version 1.8.1
-- Font not found: fixed:pixelsize=10
-- Found font: unifont:fontformat=truetype
-- Found font: siji:pixelsize=10
-- Configuring done
-- Generating done
-- Build files have been written to: /home/0rb/polybar/build
[0rb@dom0 build]$ make
Scanning dependencies of target doc_man
[  1%] sphinx-build man: see doc/builder-man.log
[  1%] Built target doc_man
Scanning dependencies of target doc_html
[  2%] sphinx-build html: see doc/builder-html.log
WARNING: html_static_path entry '/home/0rb/polybar/doc/_static' does not exist
[  2%] Built target doc_html
Scanning dependencies of target doc
[  2%] Built target doc
[  3%] Generating ../../../lib/xpp/include/xpp/proto/x.hpp
Traceback (most recent call last):
  File "/home/0rb/polybar/lib/xpp/generators/cpp_client.py", line 3101, in <module>
    from xcbgen.state import Module
  File "/usr/lib/python2.7/site-packages/xcbgen/state.py", line 7, in <module>
    from xcbgen import matcher
  File "/usr/lib/python2.7/site-packages/xcbgen/matcher.py", line 12, in <module>
    from xcbgen.xtypes import *
  File "/usr/lib/python2.7/site-packages/xcbgen/xtypes.py", line 504
    print "Explicit start-align for %s: %s\n" % (self, self.required_start_align)
                                            ^
SyntaxError: invalid syntax
lib/xpp/CMakeFiles/xpp.dir/build.make:73: recipe for target '../lib/xpp/include/xpp/proto/x.hpp' failed
make[2]: *** [../lib/xpp/include/xpp/proto/x.hpp] Error 1
make[2]: *** Deleting file '../lib/xpp/include/xpp/proto/x.hpp'
CMakeFiles/Makefile2:506: recipe for target 'lib/xpp/CMakeFiles/xpp.dir/all' failed
make[1]: *** [lib/xpp/CMakeFiles/xpp.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

Environment:
Qubes OS R 4.0
Additional context
Trying with Clang, no success.

The xcb-proto package in your distro still uses python2. We no longer support python2 because support for python2 ended at the end of 2019.
Find a way to install an xcb-proto package that uses python3 and this should work. But I really suggest you update fedora because Fedora 25 is also no longer supported since the end of 2017.

Have a look here: https://github.com/QubesOS/qubes-issues/issues/5624
I already fixed those troubles when packaging them for R4.0. Indeed, with newer Qubes R4.1 based on Fedora 31 those packages would be already in Fedora repositories.


GAN training with Pytorch Lightning is broken.

I was trying to train a DCGAN on my dataset but it wouldn't work in any means until I detach the training logic from Lightning and run the code without it. It was not working when my training logic is in Lightning module. I checked the gan examples in the docs and also multiple optimizer things. After 2 days of headaches, source code inspections and putting numerous print statements in the lightning source code, I found the culprit.
GAN training with Pytorch Lightning is simply broken. The culprit is only calling optimizer.zero_grad() after optimizer.step() since it clears the gradients of Generator or Discriminator only. Before the other network's weights are updated for, say, Generator; "loss.backward()" is called and it updates gradients for all parameters, but when optimizer.zero_grad() is called after the parameters are updated, only Generator's gradients are cleaned. So when it comes the Discriminator loss.backward(), leftover gradients are accumulated for Discriminator parameters and it just messes up with everything. Any kind of GAN training is impossible with this settings. That's why you can not find any GAN implementations with Pytorch Lightning on the internet.
Possible solutions
-Putting a warning in the docs or on the console after detecting multiple optimizers are defined like "if you train GAN, don't forget to zero all gradients by overriding the optimizer_step method or just reset gradients in your training loop before returning loss dictionary". (would be weird, honestly)

calling zero_grad before calling backward in optimizer_closure (but it would mess with gradient accumulation, i suppose)

calling self.zero_grad() instead of optimizer.zero_grad() by default in the optimizer_step.

call zero_grad for all optimizers of the lightning module after gradient step by default so that the hook on_before_zero_grad is called whenever appropriate.

(By the way, on_before_zero_grad is not seem to be called anywhere right now. Maybe the issue can be fixed with a default behavior of that method, alternatively.)
I just sent a pull request which implements the last option and updates the docs.

sorry for the trouble! good catch though. Thanks for the PR, we’ll merge it once tests pass :)

Whoops, I just have failed to submit the PR. I think it is ready now. Appreciate your work very much. Thanks for the great library :)

hi, at work we train GANs successfully with lightning by calling zero_grad in the beginning of each optimizer_step. it may mean you have other issues with your code.
my teammate recommends that you just put no_grad around your discriminator forward, and your runtime would be faster.

Hi, I'm that teammate. Strictly speaking you shouldn't even need to zero gradients at the start of optimizer_step, or have to overload optimizer_step. Between with torch.no_grad(): and Tensor.detach(), you can prevent unwanted gradient accumulation.

Hi, teammates.
I was getting good results as I added a zero_grad before my training loop but the problem is, the training loop should not include these tricks for the generic training regimes like GAN in the first place. The mentality of Lightning is to just define a loss with respect to your models and leave that kind of boilerplate to the framework, that's why I thought it would be better to submit a PR instead of hacking my training loop or advising it in the docs as I mentioned in the PR message :)

can you guys post pseudocode for both versions to see what you mean more clearly?

def training_step(self, batch, batch_nb, optimizer_idx):
        self.zero_grad()
        x_data = batch
        batch_size = x_data.shape[0]
        z = torch.randn(batch_size, 100).cuda()
        x_gen = self.G(z)
        real_labels = torch.ones(batch_size).cuda()
        fake_labels = torch.zeros(batch_size).cuda()

        if optimizer_idx == 0:

            D_real = self.D(x_data)
            D_fake = self.D(x_gen)

            real_loss = self.loss(D_real, real_labels)
            fake_loss = self.loss(D_fake, fake_labels)
            d_loss = real_loss + fake_loss

            return {
                'loss': d_loss,
                'progress_bar': {'d_loss': d_loss}
                }

        if optimizer_idx == 1:

            D_fake = self.D(x_gen)
            g_loss = self.loss(D_fake, real_labels)

            return {
                'loss': g_loss,
                'progress_bar': {'g_loss': g_loss}
                }

this code works but it fails without self.zero_grad()

Yes, it would. Make the following changes to fix it:
D_fake = self.D(x_gen) -> D_fake = self.D(x_gen.detach())
D_fake = self.D(x_gen) -> with torch.no_grad(): D_fake = self.D(x_gen)

I've tried these and it works. I mean don't get me wrong, it's a really smart and elegant way to handle things, it even speeds up the code by ~10% but I think people shouldn't think about what gradients to prevent and what to let when training different models when it can be solved by a simple change at the high level that covers most of the cases. I really can't think of a case why one needs to hold any gradients after optimizer step. Also, your no_grad method would still be relevant after this PR.

Ok, sounds like we actually want to make sure users think about this when training GANs. But totally agree that it’s a bit annoying.
Let’s make these changes:

no change to the code
update docs to help users understand this.

If it turns out that other users run into this as well, we can make it the default.
thank you all for a great discussion!

Looking at the gan.py example - does line 121 there (https://fburl.com/p8jnvbpf) needs to be updated to include with 'torch.no_grad():' beforehand, as suggested by @dbarnhart?
It seems like currently the discriminator is accumulating gradients from both the generator and the discriminator phases of the training step.

Yes, it is currently incorrect but I think it won't be an issue after #603 is done.

I've attempted to include no_grad() at the generator step, but using no_grad() removes the gradients history entirely which in effect cuts the feedback from the discriminator when training the generator model.
The alternatives I came up with were either wrapping the discriminator call with "for param in self.discriminator.parameters(): param.requires_grad = False", or call discriminator.zero_grad() before returning the discriminator loss (faster):
I've submitted fix #666 in the meantime to fix the GAN example, as it seems people are blocked on training GANs with PTL due to the same issue (see #557).

I've attempted to include no_grad() at the generator step, but using no_grad() removes the gradients history entirely which in effect cuts the feedback from the discriminator when training the generator model.
The alternatives I came up with were either wrapping the discriminator call with "for param in self.discriminator.parameters(): param.requires_grad = False", or call discriminator.zero_grad() before returning the discriminator loss (faster):
I've submitted fix #666 in the meantime to fix the GAN example, as it seems people are blocked on training GANs with PTL due to the same issue (see #557).

Gradient resetting would prevent gradient accumulation option.

Hi, I am trying to train a GAN model using pytorch lightining and I found this example from this repo.
https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pl_examples/domain_templates/generative_adversarial_net.py
I have read above comment about having to add the line self.zero_grad() first. However, I can not find this line in the above example. Is that still necessary to add it ?
I found that in the above example, u guys have used detach() function in training the Discriminator.
https://github.com/PyTorchLightning/pytorch-lightning/blob/5c35db94fa338b8720175541a3b0dc872d963bdf/pl_examples/domain_templates/generative_adversarial_net.py#L152
Does it mean if I use detach() there then there is no need to add the line self.zero_grad() first ? Please clarify. Thanks

Yes, it would. Make the following changes to fix it:
Prevent gradients accumulating on the generator during the discriminator pass:
D_fake = self.D(x_gen) -> D_fake = self.D(x_gen.detach())
Prevent gradients accumulating on the discriminator during the generator pass:
D_fake = self.D(x_gen) ->
with torch.no_grad():
    D_fake = self.D(x_gen)

Hope that helps.

Hey, I had a question, shouldn't it technically work just as well (or perhaps a bit faster even), if the discriminator train step also involves a torch.no_grad() part instead of detaching the tensor, either way, the computations done in the generator are detached from the computation graph, but with no_grad, less memory will be used, right?

with torch.no_grad():
    D_fake = self.D(x_gen)

this should not work unless backward() is also called within with torch.no_grad():, right?

Here's a better example. We need to remove those and just point to bolts.
https://pytorch-lightning-bolts.readthedocs.io/en/latest/gans.html#basic-gan

Yes, with the PR merged things will work. I was only trying to discuss the workaround mentioned earlier :)


Support time zone information in the createDate attribute in the index

Add time zone information in the createDate when creating the index.  The time zone is derived from the offset between the createDate and gpsDateTime as recorded in the exif data, if gpsDateTime is available.  As a fall back, the local time zone is assumed.
Still consider:

[ ] get time zone and daylight saving time information from vendor specific exif data,
[ ] add a command line flag to set the default time zone, in place of the local time zone as fall back,
[ ] adapt tests and add specific tests for the new feature.

Close #7.

While working on this, it reveals a challenge: if we determine the time zone for each image individually, based on the exif metadata, it may happen that some images, e.g. index items, end up having a time zone set and some don't. But we need to compare the creates date between the items in the index and the datetime standard library does not support comparing naive and aware dates.
There are essentially two options to deal with this:

enforce a homogeneous index, having either all index items a naive create date or all of them an aware one.
enhance the internal comparing methods for the index items to allow aware and naive create dates to coexist in one index.

It is not clear, how the second option could be done. We will implement the first option. But this requires a larger change than anticipated: we need to manage attributes of the index. We need to store in the index, whether the create dates are meant to be aware or naive and we need to store a default time zone as fallback in the index.  And we need to store these attributes, e.g. we need to change the index file format.


[Azure Event Grid] API Review

New API Review meeting has been requested.
Service Name: Azure Event Grid
Review Created By: Javier Fernandez
Review Date: 3/28/2023 1:00 PM PT
PR:
Hero Scenarios Link: here
Core Concepts Doc Link: Not Provided
Description: Follow up review meeting to review the TypeSpec for the new APIs released in May.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Meeting updated by Javier Fernandez
Service Name: Azure Event Grid
Review Created By: Javier Fernandez
Review Date: 3/28/2023 1:00 PM PT
PR:
Hero Scenarios Link: here
Core Concepts Doc Link: Not Provided
Description: Follow up review meeting to review the TypeSpec for the new APIs released in May.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

This is a follow-up of https://github.com/Azure/azure-rest-api-specs/issues/21880

Meeting updated by Javier Fernandez
Service Name: Azure Event Grid
Review Created By: Javier Fernandez
Review Date: 3/28/2023 1:00 PM PT
PR: https://github.com/Azure/azure-rest-api-specs/pull/23204
Hero Scenarios Link: here
Core Concepts Doc Link: Not Provided
Description: Follow up review meeting to review the TypeSpec for the new APIs released in May.
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

API Stewardship Board Review: 28-Mar-23

Adding to notes:

Receive should always returns 200 (and not a mix of 200 and 201)


Allow libvirt to relay audit logs (SELinux)

What this PR does / why we need it:
The permission is originally dontaudit-ed (silently deny), and doesn't seem to cause any problem.
However, the blocked logs might be useful, and the denial triggers errors like:
Failed to send audit message virt=kvm vm=\"kubevirt-test-default_testvmi5w79tl6bg28svmx92fkp76r2bttsk96ls7dnrhmkkt6vrnd9\
Adding the permission will silence these errors by allowing libvirt/qemu to:
"Send user space audit messages to the kernel audit system."
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/lgtm

/approve
/hold
Unhold when you're ready

/hold cancel

/retest

/cherry-pick release-0.30

Great patch. We have from time to time issues with audit logs. See https://www.redhat.com/archives/libvirt-users/2019-October/msg00031.html. However I don't think this is directly related since that issue happens on clusters without selinux too.

/retest


Add LogentriesAppender.setUseExceptionFormatter and wire in

append(ILoggingEvent); add protected method getAsyncLogger to permit
meaningful override of append in subclasses

CI fails due to openjdk buffer overflow?


Exception in thread "main" liquibase.util.grammar.TokenMgrError: Lexical error at line 146302, column 163. Encountered: "\u00b0" (176), after : ""

Environment
Liquibase Version:  3.8.6
Description
As reported in CORE-3269 the ° sign inside sql liquibase formatted file throws the error liquibase.util.grammar.TokenMgrError
Steps To Reproduce
Create a changeset with an insert statement like
insert into table (column) values ('warm temp. 32°')
Actual Behavior
Error: TokenMgrError
Expected/Desired Behavior
No Errors.
┆Issue is synchronized with this Jira Bug by Unito

https://github.com/liquibase/liquibase/pull/1107

Why is this problem still open?


The link to the raw dataset is broken

Hi there,
The link to the raw dataset for mosei and mosi which I have highlighted below, seems to be broken.

The link leads to 404.

Thank you for pointing out this error! The correct link should be _https://github.com/matsuolab/CMU-MultimodalSDK_ . I will fix it in the README.

Thanks for the prompt reply! :)
But it is written in the README that the raw dataset is available, but when I go to the link that you have given, https://github.com/matsuolab/CMU-MultimodalSDK, in the FAG, it says that the raw data is not available.

is there anyway that I can get the raw data? By raw data I mean, the URL and the timestamp to the VIdeos or the downloaded videos.

Sorry for the confusion. They used to be available when we made MultiBench. It seems that there is an update on the CMU-MOSI/MOSEI datasets (by the authors of those datasets) about one year ago that removed access all the raw data (as shown in screenshot below). I will update the readme on MultiBench as well to reflect that. If you really need to access the raw videos instead of processed features, I would recommend directly contacting the authors of the datasets.

Thanks for the prompt reply! :)


codecs.load_all_yaml(...) doesn't handle objects that are of kind *List

given a file like this defined by ServiceAccountList
apiVersion: v1
kind: ServiceAccountList
metadata: {}
items:
- apiVersion: v1
  kind: ServiceAccount
  metadata:
    name: test-sa
    namespace: kube-system

can't be handled by codecs.load_all_yaml(...)
I think i could patch something pretty simply to read through the items of the list and they'd be parsed just fine.  I'll likely raise a PR for this.

Change present in release v0.14.0. Thanks for your contribution!


NIFI-6868: Ensure that when a property value is obtained by calling P…

…rocessContext.getPropertyValue(...).evaluateAttributeExpressions(...).getValue() that we still retain the appropriate value even if the property references a sensitive parameter
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...

Thanks @rfellows . I pushed a new commit with additional unit tests and one other minor tweak.


Compile error

During pull of 3.31.0 latest from Git at 2022-10-07 7:55z

eresolve-report.txt

Tested once after -rc2 release, all OK.


Bug: Unfurled URLs for Frames are inconsistent

Describe the bug
Frame URL unfurling is inconsistent
Some users are seeing the full url within the message, others are seeing a shortened domain url outside of the frame
Slack thread: https://xmtp-labs.slack.com/archives/C07DX271K6V/p1728570845547599
Expected behavior
No response
Steps to reproduce the bug
No response

This has been fixed in 2.0.8


Unable to view any data

I'm unable to view any netflow information within Grafana. Checking the chi-netmeta-netmeta-0-0-0 logs, I can see the following error message appear which repeats itself. Not sure if this is a misconfiguration or a bug.
I'm using the latest version (master), default example config.
2023.05.01 14:06:18.830838 [ 252 ] {} <Debug> MemoryTracker: Peak memory usage: 64.25 MiB.
2023.05.01 14:06:18.832640 [ 252 ] {} <Error> void DB::StorageKafka::threadFunc(size_t): Poco::Exception. Code: 1000, e.code() = 0, Timeout, Stack trace (when copying this message, always include the lines below):

0. Poco::Net::SocketImpl::receiveBytes(void*, int, int) @ 0x17617c94 in /usr/bin/clickhouse
1. Poco::Net::HTTPSession::refill() @ 0x175fb99d in /usr/bin/clickhouse
2. Poco::Net::HTTPHeaderStreamBuf::readFromDevice(char*, long) @ 0x175f493d in /usr/bin/clickhouse
3. ? @ 0x175ea988 in /usr/bin/clickhouse
4. std::__1::basic_streambuf<char, std::__1::char_traits<char>>::uflow() @ 0x892e44a in /usr/bin/clickhouse
5. std::__1::basic_istream<char, std::__1::char_traits<char>>::get() @ 0x892fa59 in /usr/bin/clickhouse
6. Poco::Net::HTTPResponse::read(std::__1::basic_istream<char, std::__1::char_traits<char>>&) @ 0x175f9d4f in /usr/bin/clickhouse
7. Poco::Net::HTTPClientSession::receiveResponse(Poco::Net::HTTPResponse&) @ 0x175edf4d in /usr/bin/clickhouse
8. ? @ 0x10a03e22 in /usr/bin/clickhouse
9. ? @ 0x10a01bac in /usr/bin/clickhouse
10. ? @ 0x109ffea5 in /usr/bin/clickhouse
11. ? @ 0x109fcec2 in /usr/bin/clickhouse
12. ? @ 0x109fc2b8 in /usr/bin/clickhouse
13. ? @ 0x10a1ff0a in /usr/bin/clickhouse
14. DB::HTTPDictionarySource::loadAll() @ 0x10a1fac1 in /usr/bin/clickhouse
15. DB::IPAddressDictionary::loadData() @ 0x10a3ca4b in /usr/bin/clickhouse
16. DB::IPAddressDictionary::IPAddressDictionary(DB::StorageID const&, DB::DictionaryStructure const&, std::__1::shared_ptr<DB::IDictionarySource>, DB::ExternalLoadableLifetime, bool) @ 0x10a3c850 in /usr/bin/clickhouse
17. ? @ 0x10a624ad in /usr/bin/clickhouse
18. DB::DictionaryFactory::create(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, Poco::Util::AbstractConfiguration const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::shared_ptr<DB::Context const>, bool) const @ 0x123da10b in /usr/bin/clickhouse
19. DB::ExternalDictionariesLoader::create(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, Poco::Util::AbstractConfiguration const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const @ 0x12fac5db in /usr/bin/clickhouse
20. DB::ExternalLoader::LoadingDispatcher::doLoading(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, unsigned long, bool, unsigned long, bool, std::__1::shared_ptr<DB::ThreadGroupStatus>) @ 0x12fb92ad in /usr/bin/clickhouse
21. void std::__1::__function::__policy_invoker<void ()>::__call_impl<std::__1::__function::__default_alloc_func<ThreadFromGlobalPoolImpl<true>::ThreadFromGlobalPoolImpl<void (DB::ExternalLoader::LoadingDispatcher::*)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, unsigned long, bool, unsigned long, bool, std::__1::shared_ptr<DB::ThreadGroupStatus>), DB::ExternalLoader::LoadingDispatcher*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>&, unsigned long&, bool&, unsigned long&, bool, std::__1::shared_ptr<DB::ThreadGroupStatus>>(void (DB::ExternalLoader::LoadingDispatcher::*&&)(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, unsigned long, bool, unsigned long, bool, std::__1::shared_ptr<DB::ThreadGroupStatus>), DB::ExternalLoader::LoadingDispatcher*&&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>&, unsigned long&, bool&, unsigned long&, bool&&, std::__1::shared_ptr<DB::ThreadGroupStatus>&&)::'lambda'(), void ()>>(std::__1::__function::__policy_storage const*) @ 0x12fbf450 in /usr/bin/clickhouse
22. ThreadPoolImpl<std::__1::thread>::worker(std::__1::__list_iterator<std::__1::thread, void*>) @ 0xe196e6a in /usr/bin/clickhouse
23. ? @ 0xe19c521 in /usr/bin/clickhouse
24. ? @ 0x7f2af6121609 in ?
25. __clone @ 0x7f2af6046133 in ?
 (version <IP_ADDRESS> (official build))
2023.05.01 14:06:19.335310 [ 253 ] {} <Debug> StorageKafka (flows_queue): Started streaming to 1 attached views
2023.05.01 14:06:19.725129 [ 253 ] {} <Debug> StorageKafka (flows_queue): Pushing 0.00 rows to default.flows_queue (5a3e20e6-093a-4fd2-81bf-26c5d3504d6b) took 389 ms.
2023.05.01 14:06:19.726266 [ 253 ] {} <Debug> MemoryTracker: Peak memory usage: 151.34 KiB.
2023.05.01 14:06:20.148853 [ 229 ] {} <Debug> system.asynchronous_metric_log (308ada1b-9d7b-49e5-8cc4-6da5998709d3) (MergerMutator): Selected 2 parts from 202305_85519_86230_458 to 202305_86231_86231_0
2023.05.01 14:06:20.149090 [ 211 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86231_459} <Debug> MergeTask::PrepareStage: Merging 2 parts: from 202305_85519_86230_458 to 202305_86231_86231_0 into Wide with storage Full
2023.05.01 14:06:20.149243 [ 211 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86231_459} <Debug> MergeTask::PrepareStage: Selected MergeAlgorithm: Horizontal
2023.05.01 14:06:20.149293 [ 211 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86231_459} <Debug> MergeTreeSequentialSource: Reading 121 marks from part 202305_85519_86230_458, total 979216 rows starting from the beginning of the part
2023.05.01 14:06:20.149439 [ 211 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86231_459} <Debug> MergeTreeSequentialSource: Reading 2 marks from part 202305_86231_86231_0, total 1372 rows starting from the beginning of the part
2023.05.01 14:06:20.227309 [ 254 ] {} <Debug> StorageKafka (flows_queue): Started streaming to 1 attached views
2023.05.01 14:06:20.385757 [ 214 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86231_459} <Debug> MergeTask::MergeProjectionsStage: Merge sorted 980588 rows, containing 4 columns (4 merged, 0 gathered) in 0.236685286 sec., 4143003.6339479084 rows/sec., 61.94 MiB/sec.
2023.05.01 14:06:20.390787 [ 214 ] {} <Debug> MemoryTracker: Peak memory usage to apply mutate/merge in 308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86231_459: 12.57 MiB.
2023.05.01 14:06:20.442126 [ 86 ] {} <Debug> DNSResolver: Updating DNS cache
2023.05.01 14:06:20.445636 [ 86 ] {} <Debug> DNSResolver: Updated DNS cache
2023.05.01 14:06:24.026861 [ 179 ] {} <Debug> system.asynchronous_metric_log (308ada1b-9d7b-49e5-8cc4-6da5998709d3): Removing 2 parts from filesystem (serially): Parts: [202305_85519_86162_390, 202305_86163_86163_0]
2023.05.01 14:06:24.032182 [ 179 ] {} <Debug> system.asynchronous_metric_log (308ada1b-9d7b-49e5-8cc4-6da5998709d3): Removing 2 parts from memory: Parts: [202305_85519_86162_390, 202305_86163_86163_0]
2023.05.01 14:06:25.719886 [ 182 ] {} <Debug> system.trace_log (c315da78-9e32-47eb-8c56-3433eb25ec6d): Removing 6 parts from filesystem (serially): Parts: [202305_72505_72545_8, 202305_72546_72546_0, 202305_72547_72547_0, 202305_72548_72548_0, 202305_72549_72549_0, 202305_72550_72550_0]
2023.05.01 14:06:25.724943 [ 182 ] {} <Debug> system.trace_log (c315da78-9e32-47eb-8c56-3433eb25ec6d): Removing 6 parts from memory: Parts: [202305_72505_72545_8, 202305_72546_72546_0, 202305_72547_72547_0, 202305_72548_72548_0, 202305_72549_72549_0, 202305_72550_72550_0]
2023.05.01 14:06:26.470279 [ 147 ] {} <Debug> system.trace_log (c315da78-9e32-47eb-8c56-3433eb25ec6d) (MergerMutator): Selected 4 parts from 202305_72505_72609_25 to 202305_72612_72612_0
2023.05.01 14:06:26.471081 [ 210 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTask::PrepareStage: Merging 4 parts: from 202305_72505_72609_25 to 202305_72612_72612_0 into Compact with storage Full
2023.05.01 14:06:26.471572 [ 210 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTask::PrepareStage: Selected MergeAlgorithm: Horizontal
2023.05.01 14:06:26.478524 [ 210 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTreeSequentialSource: Reading 3 marks from part 202305_72505_72609_25, total 11626 rows starting from the beginning of the part
2023.05.01 14:06:26.478964 [ 210 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTreeSequentialSource: Reading 2 marks from part 202305_72610_72610_0, total 6 rows starting from the beginning of the part
2023.05.01 14:06:26.479103 [ 210 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTreeSequentialSource: Reading 2 marks from part 202305_72611_72611_0, total 6 rows starting from the beginning of the part
2023.05.01 14:06:26.479280 [ 210 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTreeSequentialSource: Reading 2 marks from part 202305_72612_72612_0, total 596 rows starting from the beginning of the part
2023.05.01 14:06:26.498841 [ 216 ] {c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26} <Debug> MergeTask::MergeProjectionsStage: Merge sorted 12234 rows, containing 12 columns (12 merged, 0 gathered) in 0.027717648 sec.,<PHONE_NUMBER>1886443 rows/sec., 153.13 MiB/sec.
2023.05.01 14:06:26.502784 [ 216 ] {} <Debug> MemoryTracker: Peak memory usage to apply mutate/merge in c315da78-9e32-47eb-8c56-3433eb25ec6d::202305_72505_72612_26: 13.64 MiB.
2023.05.01 14:06:27.155194 [ 118 ] {} <Debug> system.asynchronous_metric_log (308ada1b-9d7b-49e5-8cc4-6da5998709d3) (MergerMutator): Selected 2 parts from 202305_85519_86231_459 to 202305_86232_86232_0
2023.05.01 14:06:27.155957 [ 219 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86232_460} <Debug> MergeTask::PrepareStage: Merging 2 parts: from 202305_85519_86231_459 to 202305_86232_86232_0 into Wide with storage Full
2023.05.01 14:06:27.160920 [ 219 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86232_460} <Debug> MergeTask::PrepareStage: Selected MergeAlgorithm: Horizontal
2023.05.01 14:06:27.162256 [ 219 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86232_460} <Debug> MergeTreeSequentialSource: Reading 121 marks from part 202305_85519_86231_459, total 980588 rows starting from the beginning of the part
2023.05.01 14:06:27.163481 [ 219 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86232_460} <Debug> MergeTreeSequentialSource: Reading 2 marks from part 202305_86232_86232_0, total 1372 rows starting from the beginning of the part
2023.05.01 14:06:27.408433 [ 212 ] {308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86232_460} <Debug> MergeTask::MergeProjectionsStage: Merge sorted 981960 rows, containing 4 columns (4 merged, 0 gathered) in 0.252848184 sec., 3883595.224872171 rows/sec., 58.06 MiB/sec.
2023.05.01 14:06:27.414217 [ 212 ] {} <Debug> MemoryTracker: Peak memory usage to apply mutate/merge in 308ada1b-9d7b-49e5-8cc4-6da5998709d3::202305_85519_86232_460: 12.57 MiB.
2023.05.01 14:06:29.192782 [ 254 ] {} <Debug> MemoryTracker: Peak memory usage: 64.25 MiB.

It seems like it cant update the dictionary. Do you have any firewall for outgoing traffic?

We do have a firewall in place, but netmeta is running locally. Could that still cause any issues?

The VM where it is running has no firewall, all default/stock Ubuntu. We do have a hardware firewall but that is not blocking HTTP(s) traffic and I don't see anything being blocked.

Even tho everything should be run on Ubuntu nowadays there where some issues in the past. Can you check if all pods are running?

Did you got it to work? If not feel free to contact me directly :)

Closed because of inactivity


How to use bitmovin analytics in  bitmovin-player-react-native

Hi,
We wanted to use bitmovin analytics in bitmovin-player-react-native. How to use it ?
Do you have code snippets of this ?

Dear @vishnushelar ,
a React Native library for our Analytics product is in the works, coming early 2023.
Thanks

Okay
Thanks for the updates.


Clear up "Add to Existing" section

see screenshot first, comments below:

Imo its unclear what is actually getting "added to existing" projects. From what I can tell we are providing info for how to add the dao-utils package to an existing project, so maybe we could make that more explicit?

would be helpful to mention or at least hyperlink the dao-utils repo in that first sentence where it says "react componentry and hooks to interact"

@salieflewis can you confirm that we should actually be providing yarn/npm/pnpm examples as opposed to pnpm? Seems like we have moved on to pnpm being our main package manager so perhaps that could be the default example, and include a guide for installing pnpm if people havent used it before?

The "adding peer dependenices" part is confusing to me as related to point #1 -- because I dont think someone actually needs to do this if they are just trying to consume the dao-utils package in their own package. This specific example seems more like its trying to explain "how to manage the dao-utils monorepo and add peer dependencies to it" -- this is actually imnportant info to provide since it will help ppl make tweaks + push updates to dao-utils besides us, but there is no monorepo structure in the Flexible repo so its currently confusing as is

token explorer example is great !!

The deps was written before the package go completely abstracted of all peer deps


Patch DSL: support patching multiple modules with one statement

Should be able to write:
jvmDependencyConflicts {
    patch {
        module("org.openjfx:javafx-base", "org.openjfx:javafx-graphics") {
            addTargetPlatformVariant("", "none", "none")
            addTargetPlatformVariant("linux", OperatingSystemFamily.LINUX, MachineArchitecture.X86_64)
            addTargetPlatformVariant("mac", OperatingSystemFamily.MACOS, MachineArchitecture.X86_64)
            addTargetPlatformVariant("mac-aarch64", OperatingSystemFamily.MACOS, MachineArchitecture.ARM64)
            addTargetPlatformVariant("win", OperatingSystemFamily.WINDOWS, MachineArchitecture.X86_64)
        }
    }
}

If patching for OS specific artifacts is a common use case, maybe we can come up with an even more compat way of declaring just that in addition.

Just realized that this signature is (of course) not possible in Java:
public void module(String... modules, Action<PatchModule> action)

If you want to have varargs the only way I see to get this working would be a method chain like the following:
jvmDependencyConflicts {
  patch {
    modules("org.openjfx:javafx-base", "org.openjfx:javafx-graphics").each {
       ...
    }
  }
}

The modules method would have the following signature:
public EachModuleConfigurer modules(String... modules);

interface EachModuleConfigurer {
  public void each(Action<PatchModule> action)
}

But this would just wrap around a forEach call and would spare you from writing listOf. Not sure if this is really better. The problem with these kind of chaining APIs is always when you forget to make the terminal call nothing happens. And that is sometimes hard to find.

Lets not do this now. I would prefer not to overload the DSL unless there is a really clean DSL concept (and not a technical API).


Keep Pod's source code

Thanks for this awesome plugin!
I would like to

use binary pods in order to reduce my project's compile times and
keep the original pod sources and check them in git so that I always have the source code, even if I actually use the prebuilt frameworks in my build.

Is this possible? I tried using the keep_source_code_for_prebuilt_frameworks! flag but the source files are being deleted.

@kremizask  What's the purpose of 'always have the source code'?
if using 'keep_source_code_for_prebuilt_frameworks', you can find the source code in Pods/_prebuilt/. This feature is to speed up the prebuild install.  Maybe the name is a litter inaccurate.

@leavez I think I understand what @kremizask wants and I'm looking for the same thing. I would like to use the binaries to reduce compile time, but keep the source code organized as vanilla cocoapods organizes it so that Xcode recognizes the implementation files and I can see the implementation directly in xcode as I'm developing through a command click. Is this possible? Thanks!


Define option for automatic import for icons

Please check if there is a possibility via Figma API to import the icons from Schwarz Icon Library to our Onyx Library file with giving theme also a defined variable
If it works please check in copy of Onyx Libary file what happens with the icons page and icons that are used in components.

Works! Implement ticket: #2309


CORS error when routing from http to https in openshift

It seems like the routing in openshift loses the allow-access header while redirecting.
First attempt should be to fix the redirecting in openshift.
Otherwise http could be deactivated.

should no longer be an issue?


Push Send from Backed not working

Hallo to all,
I'm testing from Azure - portal  and it working.
But if i send from backend - not working.
Should i yet template register?
I use NotificationHubClient

I checked devices with GetRegistrationsByTagAsync and my device be present.
So i send notifications:
Hub.SendTemplateNotificationAsync(new Dictionary<string, string> { { "message", sendvalue.ToString(Newtonsoft.Json.Formatting.None) } }, users.First());

With SendFcmNativeNotificationAsync and SendAppleNativeNotificationAsync ist working :) Tnx

With SendFcmNativeNotificationAsync and SendAppleNativeNotificationAsync working

Hallo to all,
I'm testing from Azure - portal and it working.
But if i send from backend - not working.
Should i yet template register?
I use NotificationHubClient

I can give a good advice. Develop your own framework for push notification. I used the plugin which only worked for iOS but not 100%. It never worked for android. So I decided to create my own framework in order to have more control whenever ios or android is updated. I did that and it worked for me. Kudos to the people that developed this plugin but I rather implement mine


Issue 439 build with scala3

Draft PR to cross build for scala 3

Adapt the build for scala 3
Use type pattern : instead of extractor @
Update example dependencies

Caveats:

[ ] fetchJS tests do not compile for scala 3 as scalatest isn't published for scalaJS with scala 3 ( https://mvnrepository.com/artifact/org.scalatest/scalatest )
[ ] fetch-example http4s isn't published for scala 3 yet.
[ ] fetch-example monix isn't published for scala 3 yet.
[ ] sbt-mdoc-toc sbt plugin isn't published for scala 3 yet. I think sbt-mdoc-toc transitively depends on mdoc being  ready for scala3. According to this issue, it is currently published for scala3 but only to allow worksheet support
[ ] sbt-scoverage isn't published for scala 3 yet. (See this issue

I've updated the 2 scala versions. I've tried to find workarounds to get the build to pass, but haven't settled on anything satisfactory. It looks like at this stage we still have too many dependencies that aren't published for scala 3.

Hi @benderpremier , thanks for helping with the Scala 3 migration! Some comments:

I think scalatest is cross-compiled with [scala 3-RC1]

https://github.com/scalatest/scalatest/blob/d7b65ba585106ba655a856601d5e43cea965ab25/project/DottyBuild.scala
https://github.com/scalatest/scalatest/releases/tag/release-3.2.4

sbt-mdoc-toc: I don't think we are using this plugin?
Examples: as we are not publishing them in maven central, maybe we could avoid cross-compilation for example modules. Makes sense?
sbt-scoverage: this one might be tricky. Perhaps, we could disable code-coverage for now.

Again, thanks!

Thanks for the feedback @juanpedromoreno.

I think scalatest is cross-compiled with [scala 3-RC1]

It is cross compiled for scala 3 on the JVM, but not for scala 3 on scalaJS. For the moment I've disabled cross compilation on scalaJS with.
lazy val fetchJS = fetch.js
  .disablePlugins(ScoverageSbtPlugin)
  .settings(crossScalaVersions := scala2Versions)

sbt-mdoc-toc: I don't think we are using this plugin?

I think we do here (on line 9). It generates the table of content that we see in the readme.md at the root of the repo. However, I think we can scope the mdoc task to only run on 2.13

Examples: as we are not publishing them in maven central, maybe we could avoid cross-compilation for example modules. Makes sense?

Yes I think it makes sense. I'll only compile this project with 2.13.

sbt-scoverage: this one might be tricky. Perhaps, we could disable code-coverage for now.

If everyone is happy with that let's do it 💪.

I've removed the code coverage plugins and adapted the build. I think if we want to publish for 3.0.0-RC1 that could do the trick.

@benderpremier @franciscodr Some Scala3 porting projects will trigger some (significant) code-refactoring. It would be good to have this. Can we merge this and publish a new version (1.4.3)? Question: Am I right to assume that sbt-scoverage does not need to be updated, but that I need to set coverageScalacPluginVersion to 1.4.3 to make this work?

Thanks for all the reviews!!! (cc: @benderpremier @franciscodr)

@benderpremier I am interested to get this merged/published. Let me know, if/how I can help.

I am not sure how we want to move forward with this. I agree that having the a: FetchOne[Any, Any], isn't great. As Chris pointed out, looks like we were taking advantage of a limitation of the scala2 compiler. I guess our choice are:

merge with those Any which seems to be on par with what the library is doing now
fix this before publishing for scala3

@benderpremier I agree with @juanpedromoreno:  Would suggest to merge now and create a followup ticket to work on FetchOne. WDYT?

@juanpedromoreno I had to update to scala3 RC2. After merging master into this branch, scalatest got updated to 3.2.7 which is only published for RC2. Could you give it a ✅ ?


fix(package.json): update axios version

🆙

:tada: This PR is included in version 1.22.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


some update about RegioSQM

this request is the result by the occasional -- local -- use of RegioSQM, which may be described as

a conservative approach, to alter hopefully none of the functionality offered by your scripts when porting them to Python3
the addition of some functionality by a separate "moderator script" (i.e., batch_regiosqm.py) to keep your scripts basically conserved when seeking for an option to submit i) larger sets of input data in multiple smaller input files then either explicitly defined by their name, or submitted en bloc by the -a.  Or ii), to submit just a single structure as SMILES string without manual write of a dedicated input file.

From one of your other projects, calculate_rmsd.py, I know that you welcome suggestions if these already are documented, and may be tested automatically.  The present suggest however does not contain such tests.  Compared to your development of regiosqm as documented to the public, some of the work in my fork was not fruitful, or in retrospect, lengthy.  While the number of increments does not bother me, you may think that a condensation of these changes by a git rebase would be beneficial.
Over time, the documentation (including the reference folder with the "quick" data) more and more became a recapitulation for myself, all in one place; this contrasts with the shorter one by you equally pointing to your seminal publication.  I'm aware that in addition to the «old» regiosqm you equally wrote and published about regiosqm20.

While updating my fork, I didn't recall (anymore) that I once filed a PR here (some time ago).  Under the assumption your work focus' evolved to other topics, and because there is RegioML published shortly after the PR, which in days of machine learning is more attractive to maintain for you, I retract this PR.


AzureAppServiceSettings appsettings section, max length limited to 5000

Required Information
Question, Bug, or Feature?
Type: Feature
Enter Task Name: AzureAppServiceSettings
Environment
Not relevant
Issue Description
The AzureAppServiceSettings task allow only 5000 chars in the appsettings input field. We are hitting this limit, with no real way to extend it.
Suggestion
Either increase the limit of appsettings input and/or allow a reference an external file (preferably on a blob storage)

@bkvisiosign

I have the same problem, what's the alternative?


remove all jit trace related code and examples

This is just a proposal to see if we're happy to go this way, or if we prefer to fix this by duplicating what is done in torch.utils.tensorboard.
The update to the notebook is simply removing the part that was showing the jit trace printing.

thanks Alban!


[IOS] Crash - AVPlayerItem cannot service a seek

Configuration
package.json
    "react": "16.3.1",
    "react-native": "0.55.4",
    "react-native-track-player": "^1.1.3",
    "react-native-swift": "^1.2.2",

react-native info
Environment:
  OS: macOS High Sierra 10.13.6
  Node: 8.11.2
  Yarn: 1.9.4
  npm: 5.6.0
  Watchman: 4.9.0
  Xcode: Xcode 10.1 Build version 10B61
  Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: 0.55.4 => 0.55.4

Problem
I am receiving this error in Crachlytics (mostly happens on iOS 10.3.3 / 10.2.1 and less from what I can see) :
Fatal Exception: RCTFatalException: Exception 'AVPlayerItem cannot service a seek request with a completion handler until its status is AVPlayerItemStatusReadyToPlay.' was thrown while invoking seekTo on target TrackPlayerModule with params (
    "591.99016881",
    14402,
    14403
)
callstack: (
	0   CoreFoundation                      0x1cbcbb55 <redacted> + 152
	1   libobjc.A.dylib                     0x1be53067 objc_exception_throw + 38
	2   AVFoundation                        0x2347b2c3 <redacted> + 1114
	3   AVFoundation                        0x23467fef <redacted> + 132
	4   xxx                             0x0060b62b _ZN5folly6detail15str_to_integralIxEENS_8ExpectedIT_NS_14ConversionCodeEEEPNS_5RangeIPKcEE + 2858690
	5   xxx                             0x0060bbff _ZN5folly6detail15str_to_integralIxEENS_8ExpectedIT_NS_14ConversionCodeEEEPNS_5RangeIPKcEE + 2860182
	6   xxx                             0x005ef4b3 _ZN5folly6detail15str_to_integralIxEENS_8ExpectedIT_NS_14ConversionCodeEEEPNS_5RangeIPKcEE + 2743626
	7   xxx                             0x006037d1 _ZN5folly6detail15str_to_integralIxEENS_8ExpectedIT_NS_14ConversionCodeEEEPNS_5RangeIPKcEE + 2826344
	8   xxx                             0x005fb6ed _ZN5folly6detail15str_to_integralIxEENS_8ExpectedIT_NS_14ConversionCodeEEEPNS_5RangeIPKcEE + 2793348
	9   CoreFoundation                      0x1cbd0354 <redacted> + 68
	10  CoreFoundation                      0x1caf42b9 <redacted> + 300
	11  CoreFoundation                      0x1caf7e87 <redacted> + 48
	12  xxx                             0x002f549f xxx + 2180255
	13  xxx                             0x003328cd RCTFBQuickPerformanceLoggerConfigureHooks + 91982
	14  xxx                             0x0033254f RCTFBQuickPerformanceLoggerConfigureHooks + 91088
	15  libdispatch.dylib                   0x1c299797 <redacted> + 10
	16  libdispatch.dylib                   0x1c2a659d <redacted> + 854
	17  libdispatch.dylib                   0x1c29cb71 <redacted> + 886
	18  libdispatch.dylib                   0x1c2a6a1f <redacted> + 282
	19  libdispatch.dylib                   0x1c2a81b5 <redacted> + 326
	20  libdispatch.dylib                   0x1c2a800f <redacted> + 106
	21  libsystem_pthread.dylib             0x1c44e87d _pthread_wqthread + 1040
	22  libsystem_pthread.dylib             0x1c44e45c start_wqthread + 8
)
0  CoreFoundation                 0x1cbcbb3d __exceptionPreprocess
1  libobjc.A.dylib                0x1be53067 objc_exception_throw
2  xxx                        0x2e197f RCTFormatError (RCTAssert.m:150)
3  xxx                        0x332b09 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&) (RCTNativeModule.mm:111)
4  xxx                        0x33254f invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) (Optional.h:299)
5  libdispatch.dylib              0x1c299797 _dispatch_call_block_and_release
6  libdispatch.dylib              0x1c2a659d _dispatch_queue_serial_drain
7  libdispatch.dylib              0x1c29cb71 _dispatch_queue_invoke
8  libdispatch.dylib              0x1c2a6a1f _dispatch_queue_override_invoke
9  libdispatch.dylib              0x1c2a81b5 _dispatch_root_queue_drain
10 libdispatch.dylib              0x1c2a800f _dispatch_worker_thread3
11 libsystem_pthread.dylib        0x1c44e87d _pthread_wqthread
12 libsystem_pthread.dylib        0x1c44e45c start_wqthread

@Guichaguri any wild guess on that problem ? a bad configuration of my part or a bug you know about ?

I have also started getting reports of this error in Bugsnag and Crashlytics.
In my app I seek in 3 ways.
Using jump forward/backward buttons.
Scrubbing a timeline.
And resuming playback at a certain point by play -> seek right away.
My hunch, just like @ishigamii, is that it has to do with the last one. Playing and then seeking immediately. (Even using await play())

@Guichaguri With some more datas it seems this is a 100% iOS 10 crash hope it helps to find it out

@ishigamii are you still getting this in more recent versions?
I am no longer seeing it in my logs. I think it may have been fixed in https://github.com/jorgenhenrichsen/SwiftAudio/pull/51.
Closing for now. Please let us know if it is still occurring for you.


Can’t use OR-condition on PR

Expected Behavior
here’s an (I hope, standalone) excerpt of our proposed config:
pull_request_rules:
  - actions:
      label:
        add:
          - merge delay passed
    name: Wait for 2 days before validating merge
    conditions:
      - updated-at<2 days ago
      - or
        - label=merge me
        - label=squash+merge me

I expect it to apply a label under the said condition.
Actual Behavior
Mergify complains:

Invalid condition 'or - label=merge me - label=squash+merge me'. Invalid attribute @ pull_request_rules → item 0 → conditions → item 1

Worth noting: it worked when the condition had no ORs (instead of the OR it just had “label=merge me”). It’s just we want the OR.
Specifications

Mergify Config URL: https://github.com/haskell/cabal/blob/7d06617e891d283f233dbddaeb7c3f06483d340c/.github/mergify.yml

Hi!
I think the or condition is missing a : character. Otherwise, it might be wrongly interpreted.
Can you test something like this?
pull_request_rules:
  - actions:
      label:
        add:
          - merge delay passed
    name: Wait for 2 days before validating merge
    conditions:
      - updated-at<2 days ago
      - or
        - label=merge me
        - label=squash+merge me


Possibility to support LLama-3?

Thanks for sharing fantastic jobs, the VILA shows strong few-shot in context learning ability than original llava-1.5, will you plan to support LLama-3? The advantage of in context learning for vision could be expected.

yeah, the VILA1.5 we released today supports llama-3


Support platform generator type templates to infrastructure as code

Why do we need this improvement?
The idea here that we can extend the existing 'asyncapi generate' command to generate platform commands to create/configure the topics.
How will this change help?
This enables the user to leverage the asyncapi file as a form of infrastructure as code.
Screenshots
No response
How could it be implemented/designed?
On the assumption that kafka is the most popular event broker this enhancement would take the list of topic names from the ayncapi yml file, and output a set of 'kafka' style command to config the needed topics.
kafka-topics.sh --create --topic 'topic-name-per-async-api-yml'

The existing cli supports these two options currently
asyncapi generate fromTemplate ASYNCAPI TEMPLATE
asyncapi generate models LANGUAGE FILE

and i'd foresee a 3rd flavour called 'platform'
asyncapi generate platform ASYNCAPI

which based on the broker type in yml file we'd call the relevant platform-template module.
🚧 Breaking changes
No
👀 Have you checked for similar open issues?

[X] I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to work on this issue?
Yes I am willing to submit a PR!

As discussed on the slack channel - i opened the proposal issue here. Thanks for the suggestion. @derberg

makes sense to me :v:
Can easily be extended for multiple protocols 🤙 Remember to add this to the CLI not the generator though 🙂 https://github.com/asyncapi/cli

Let me move the issue to the cli repo and an attempt to start a coded proposal.


Selecting a non "_dir" vpk should be able to find the associated _dir vpk, instead of throwing an error

Describe Your Suggestion
VRF is able to do this, it makes opening vpks a tiny bit faster.

Was there a PR associated with this?

I just pushed directly to main, it was like 3 lines

I made a pr for the other one because I needed to test it on my Linux laptop


Need discussion of diagram for order schema

One order consists of a number of main menus, and one main menu consists of a number of option menus.

The main menu contains mandatory options and additional options. Each option value is an id in the option table.
The coupon is created separately from the menu, and depending on the attribute of the coupon, there is menu and dependancy. And the coupon is used to calculate the total amount.

The structure used in the order system is briefly described as a class diagram as follows. The total amount of an order is calculated by the ICaculator interface and can be implemented according to the situation of the merchant.

And we need to provide an admin web page where we can add menu and coupon freely and easily.
****** The above is a draft version for your understanding, not an actual implementation design. ******

@coconutperm, I'm closing this issue.


python36Packages.jsbeautifier is failing on master and 19.03

Issue description
python36Packages.jsbeautifier build is failing, the same error occurs on master and 19.03. Updating the package 1.8.9 -> 1.9.1 does not solve the problem.
Steps to reproduce
$ nix-shell -p nur.repos.kalbasit.nix-verify --run 'nix-verify -I nixpkgs=`pwd` -A python36Packages.jsbeautifier'
$ exec env -i NIXPKGS_ALLOW_UNFREE=1 nix-build -I nixpkgs=/yl/code/opensource/stories/nixpkgs_fix-js-beautifier/src/github.com/NixOS/nixpkgs -A python36Packages.jsbeautifier
these derivations will be built:
  /nix/store/967sjl11npm9gnbcsd46i7drpbiy5r4d-jsbeautifier-1.8.9.drv
building '/nix/store/967sjl11npm9gnbcsd46i7drpbiy5r4d-jsbeautifier-1.8.9.drv' on<EMAIL_ADDRESS>unpacking sources
unpacking source archive /nix/store/sra58bakragbm410y5hgrhm9bim3irf1-jsbeautifier-1.8.9.tar.gz
source root is jsbeautifier-1.8.9
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file jsbeautifier-1.8.9/setup.cfg
patching sources
configuring
building
running bdist_wheel

[... SNIP ..]

running test
running egg_info
writing jsbeautifier.egg-info/PKG-INFO
writing dependency_links to jsbeautifier.egg-info/dependency_links.txt
writing entry points to jsbeautifier.egg-info/entry_points.txt
writing requirements to jsbeautifier.egg-info/requires.txt
writing top-level names to jsbeautifier.egg-info/top_level.txt
reading manifest file 'jsbeautifier.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'js-beautify'
writing manifest file 'jsbeautifier.egg-info/SOURCES.txt'
running build_ext
============================= test session starts ==============================
platform linux -- Python 3.6.8, pytest-4.2.1, py-1.7.0, pluggy-0.8.1
rootdir: /build/jsbeautifier-1.8.9, inifile:
collected 3 items

jsbeautifier/tests/test-packer.py E                                      [ 33%]
jsbeautifier/tests/testindentation.py ..                                 [100%]

==================================== ERRORS ====================================
__________________________ ERROR at setup of test_str __________________________
file /build/jsbeautifier-1.8.9/jsbeautifier/tests/test-packer.py, line 11
  def test_str(str, expected):
E       fixture 'str' not found
>       available fixtures: cache, capfd, capfdbinary, caplog, capsys, capsysbinary, doctest_namespace, monkeypatch, pytestconfig, record_property, record_xml_attribute, recwarn, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory
>       use 'pytest --fixtures [testpath]' for help on them.

/build/jsbeautifier-1.8.9/jsbeautifier/tests/test-packer.py:11
====================== 2 passed, 1 error in 0.06 seconds =======================
builder for '/nix/store/967sjl11npm9gnbcsd46i7drpbiy5r4d-jsbeautifier-1.8.9.drv' failed with exit code 1
e

Technical details

system: "x86_64-linux"
host os: Linux 4.19.25, NixOS, 18.09pre-git (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.3
channels(root): ""
channels(kalbasit): "home-manager-18.09, nixpkgs-18.09.932.09195057114"
channels(yl): ""
nixpkgs: /run/current-system/nixpkgs

/cc @apeyroux maintainer of this package.

This was not happening back in dea01b84a5e4fa7711346a7d1dac747ccf92350d. I believe this started happening with version 1.8.0rc2 when test-packer was introduced upstream. https://github.com/beautify-web/js-beautify/commit/63013ff707277ec25de39b4bcbd294b91dbf3bc5

fixed via https://github.com/NixOS/nixpkgs/pull/58632.


Light and Dark Theme

I want to make a button which will trigger a(example - theme) function whose work will be to toggle between light and dark theme.
const theme = () => {
    // code
}

Submit this issue(or Pull request) in light-and-dark-theme-branch
NOTE: It should not reset the theme after changing the page nor after refreshing the page!

can i started your project has an assignee?

@Sengpai Yes, Thank you for helping.

Can you assign me to work this issue?

@NhutTuanB2112021 Yes, Thank you for helping.

hey although i solved this issue but i committed without tag of issue so which did not close, i will write some comment lines in code and please merge it, this is a part of document for me at school.

@Sengpai @NhutTuanB2112021 This issue is completed... So, no need to work on this issue. And sorry @NhutTuanB2112021 for not assigning you to this issue.

@Ankurcr7 i need you merge my last commit to this issue closed, so i can take a screen shoot for my Presentation material.

@Sengpai I merged it. I hope it will help you with your document at school.

Now I am closing this issue. Thank you for your contribution.


gr.svg - flag lines are wrong

The blue area under the white cross should be without the white lines.
See https://en.wikipedia.org/wiki/Greece.
https://github.com/lipis/flag-icon-css/blob/master/flags/4x3/gr.svg

Can you expand on what exactly is the difference? I don't really see much when comparing the 4x3/gr.svg with the svg from wikipedia (converted to PNG below)
from this repo

from wikipedia

The only potential issue I see is a very thin blue line at the bottom end of the white cross.

It only seems to be on GitHub when rendering. If you downloaded the svg, it looks good. Issue will be closed for this reason. Sorry.

There might be some rounding issues that cause the thin lines depending on the SVG renderer and resolution.


Vscode Sets breakpoint in both sessions in multicore debugging with single Debug Configuration

In multicore debugging with a single debug configuration when we try setting breakpoints in either of the sessions it sets breakpoints for both of the debug sessions. For Example, Consider the Following case:
When we set a breakpoint in one Session which turns out to be an outbound breakpoint, then it tries to resolve the breakpoint to a random location in the other Debug Session, which results in an exception.  So if we can stop setting breakpoint in both sessions and instead set them only in the user-requested session, we can overcome this problem.

What language? Adding a breakpoint always sets it in all debug sessions, but if it's not a valid location for some debug session that should be ignored.

If we set breakpoint always in all debug sessions, It might create an issue in case of Disassemly Debugging. The location of the breakpoints is the Instructions Addresses in disassembly Debugging. The Instruction addresses of one Session might resolve with the Instruction address of another Session. Hence, it might hit the breakpoint in an unexpected location.
To resolve such conflicts, we can set them only in the user-requested session.

I think you're right and that could possibly be an issue, just looking at DAP, but we don't have a way to avoid this right now

We would have to introduce the notion of session or config-specific breakpoints, which is a good idea but a bigger change


Update dependencies.

Closing in favor of #505, sorry didn't see it sooner.

No need to insta-close, we could use the rest of the upgrades but they need some more thought. Whenever upgrading libraries I always do a quick check in the changelog to see if there's anything useful, new features, or worrying shortcomings that I should keep in mind (which my only show at runtime).


Markdown formatter for _schedule_table.Rmd

https://github.com/jhudsl/intro_to_R_class/issues/75

Can styler package do this? I just want the table to be easy to look at...

I cant find an easy way to style rmd but luckily Quarto does this 🤩!!


Synthesis failed for nodejs-phishing-protection

Hello! Autosynth couldn't regenerate nodejs-phishing-protection. :broken_heart:
Here's the output from running synth.py:
b'gleapis.\n2020-06-05 04:35:51,494 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis\nDEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis\n2020-06-05 04:35:51,498 synthtool [DEBUG] > Pulling Docker image: gapic-generator-typescript:latest\nDEBUG:synthtool:Pulling Docker image: gapic-generator-typescript:latest\nlatest: Pulling from gapic-images/gapic-generator-typescript\nDigest: sha256:c9bc12024eddcfb94501627ff5b3ea302370995e9a2c9cde6b3317375d7e7b66\nStatus: Image is up to date for gcr.io/gapic-images/gapic-generator-typescript:latest\n2020-06-05 04:35:52,406 synthtool [DEBUG] > Generating code for: google/cloud/phishingprotection/v1beta1.\nDEBUG:synthtool:Generating code for: google/cloud/phishingprotection/v1beta1.\n2020-06-05 04:35:53,323 synthtool [DEBUG] > Wrote metadata to synth.metadata.\nDEBUG:synthtool:Wrote metadata to synth.metadata.\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main\n    spec.loader.exec_module(synth_module)  # type: ignore\n  File "<frozen importlib._bootstrap_external>", line 678, in exec_module\n  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed\n  File "/home/kbuilder/.cache/synthtool/nodejs-phishing-protection/synth.py", line 36, in <module>\n    extra_proto_files=[\'google/cloud/common_resources.proto\'],\n  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 66, in typescript_library\n    return self._generate_code(service, version, "typescript", **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 195, in _generate_code\n    f"Code generation seemed to succeed, but {output_dir} is empty."\nRuntimeError: Code generation seemed to succeed, but /tmpfs/tmp/tmpuivmo3ty is empty.\n2020-06-05 04:35:53,367 autosynth [ERROR] > Synthesis failed\n2020-06-05 04:35:53,367 autosynth [DEBUG] > Running: git reset --hard HEAD\nHEAD is now at 2a56034 chore: release 2.0.1 (#145)\n2020-06-05 04:35:53,373 autosynth [DEBUG] > Running: git checkout autosynth-self\nSwitched to branch \'autosynth-self\'\n2020-06-05 04:35:53,378 autosynth [ERROR] > Command \'[\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\' returned non-zero exit status 1.\n2020-06-05 04:35:53,508 autosynth [DEBUG] > Running: git checkout 2a56034f5b60fcfae84afbb484a26bcc79ab9224\nNote: checking out \'2a56034f5b60fcfae84afbb484a26bcc79ab9224\'.\n\nYou are in \'detached HEAD\' state. You can look around, make experimental\nchanges and commit them, and you can discard any commits you make in this\nstate without impacting any branches by performing another checkout.\n\nIf you want to create a new branch to retain commits you create, you may\ndo so (now or later) by using -b with the checkout command again. Example:\n\n  git checkout -b <new-branch-name>\n\nHEAD is now at 2a56034 chore: release 2.0.1 (#145)\n2020-06-05 04:35:53,513 autosynth [DEBUG] > Running: git checkout cd804bab06e46dd1a4f16c32155fd3cddb931b52\nPrevious HEAD position was 6dfd72d0 Add bazel build file for BigQuery Connection API v1.\nHEAD is now at cd804bab docs: cleaned docs for the Agents service and resource.\n2020-06-05 04:35:53,584 autosynth [DEBUG] > Running: git checkout d53a5b45c46920932dbe7d0a95e10d8b58933dae\nPrevious HEAD position was be74d3e build: do not fail builds on codecov errors (#528)\nHEAD is now at d53a5b4 docs: improve README (#600)\n2020-06-05 04:35:53,601 autosynth [DEBUG] > Running: git branch -f autosynth-127\n2020-06-05 04:35:53,605 autosynth [DEBUG] > Running: git checkout autosynth-127\nSwitched to branch \'autosynth-127\'\n2020-06-05 04:35:53,610 autosynth [INFO] > Running synthtool\n2020-06-05 04:35:53,610 autosynth [INFO] > [\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\n2020-06-05 04:35:53,612 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --\n2020-06-05 04:35:53,819 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/nodejs-phishing-protection/synth.py.\nOn branch autosynth-127\nnothing to commit, working tree clean\n2020-06-05 04:35:53,954 synthtool [DEBUG] > Ensuring dependencies.\nDEBUG:synthtool:Ensuring dependencies.\n2020-06-05 04:35:53,960 synthtool [DEBUG] > Cloning googleapis.\nDEBUG:synthtool:Cloning googleapis.\n2020-06-05 04:35:53,961 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis\nDEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis\n2020-06-05 04:35:53,965 synthtool [DEBUG] > Pulling Docker image: gapic-generator-typescript:latest\nDEBUG:synthtool:Pulling Docker image: gapic-generator-typescript:latest\nlatest: Pulling from gapic-images/gapic-generator-typescript\nDigest: sha256:c9bc12024eddcfb94501627ff5b3ea302370995e9a2c9cde6b3317375d7e7b66\nStatus: Image is up to date for gcr.io/gapic-images/gapic-generator-typescript:latest\n2020-06-05 04:35:54,863 synthtool [DEBUG] > Generating code for: google/cloud/phishingprotection/v1beta1.\nDEBUG:synthtool:Generating code for: google/cloud/phishingprotection/v1beta1.\n2020-06-05 04:35:55,760 synthtool [DEBUG] > Wrote metadata to synth.metadata.\nDEBUG:synthtool:Wrote metadata to synth.metadata.\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main\n    spec.loader.exec_module(synth_module)  # type: ignore\n  File "<frozen importlib._bootstrap_external>", line 678, in exec_module\n  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed\n  File "/home/kbuilder/.cache/synthtool/nodejs-phishing-protection/synth.py", line 36, in <module>\n    extra_proto_files=[\'google/cloud/common_resources.proto\'],\n  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 66, in typescript_library\n    return self._generate_code(service, version, "typescript", **kwargs)\n  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 195, in _generate_code\n    f"Code generation seemed to succeed, but {output_dir} is empty."\nRuntimeError: Code generation seemed to succeed, but /tmpfs/tmp/tmp02zq1is9 is empty.\n2020-06-05 04:35:55,803 autosynth [ERROR] > Synthesis failed\n2020-06-05 04:35:55,803 autosynth [DEBUG] > Running: git reset --hard HEAD\nHEAD is now at 2a56034 chore: release 2.0.1 (#145)\n2020-06-05 04:35:55,808 autosynth [DEBUG] > Running: git checkout autosynth\nSwitched to branch \'autosynth\'\n2020-06-05 04:35:55,813 autosynth [DEBUG] > Running: git clean -fdx\nRemoving __pycache__/\nTraceback (most recent call last):\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main\n    "__main__", mod_spec)\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code\n    exec(code, run_globals)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>\n    main()\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main\n    return _inner_main(temp_dir)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 595, in _inner_main\n    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 371, in synthesize_loop\n    synthesize_inner_loop(toolbox, synthesizer)\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 381, in synthesize_inner_loop\n    synthesizer, len(toolbox.versions) - 1\n  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch\n    synthesizer.synthesize(synth_log_path, self.environ)\n  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 119, in synthesize\n    synth_proc.check_returncode()  # Raise an exception.\n  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode\n    self.stderr)\nsubprocess.CalledProcessError: Command \'[\'/tmpfs/src/github/synthtool/env/bin/python3\', \'-m\', \'synthtool\', \'--metadata\', \'synth.metadata\', \'synth.py\', \'--\']\' returned non-zero exit status 1.\n'

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-phishing-protection. :sob:
Here's the output from running synth.py:
/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/nodejs-phishing-protection/synth.py", line 36, in <module>
    extra_proto_files=['google/cloud/common_resources.proto'],
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 66, in typescript_library
    return self._generate_code(service, version, "typescript", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 195, in _generate_code
    f"Code generation seemed to succeed, but {output_dir} is empty."
RuntimeError: Code generation seemed to succeed, but /tmpfs/tmp/tmp5uhrynfi is empty.
2020-06-05 15:53:21,200 autosynth [ERROR] > Synthesis failed
2020-06-05 15:53:21,200 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 2a56034 chore: release 2.0.1 (#145)
2020-06-05 15:53:21,205 autosynth [DEBUG] > Running: git checkout autosynth-self
Switched to branch 'autosynth-self'
2020-06-05 15:53:21,209 autosynth [ERROR] > Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.
2020-06-05 15:53:21,356 autosynth [DEBUG] > Running: git checkout 2a56034f5b60fcfae84afbb484a26bcc79ab9224
Note: checking out '2a56034f5b60fcfae84afbb484a26bcc79ab9224'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 2a56034 chore: release 2.0.1 (#145)
2020-06-05 15:53:21,361 autosynth [DEBUG] > Running: git checkout 40a354b0f47454be4986f9db504cca4d4371c8c3
Previous HEAD position was 6dfd72d0 Add bazel build file for BigQuery Connection API v1.
HEAD is now at 40a354b0 chore: add protoc proto3_optional flag in bazelrc
2020-06-05 15:53:21,433 autosynth [DEBUG] > Running: git checkout 9c2913e1831eb00fa01317f3fea4ce25d3f657eb
Previous HEAD position was be74d3e build: do not fail builds on codecov errors (#528)
HEAD is now at 9c2913e feat: show output from microgenerator runs (#575)
2020-06-05 15:53:21,449 autosynth [DEBUG] > Running: git branch -f autosynth-134
2020-06-05 15:53:21,452 autosynth [DEBUG] > Running: git checkout autosynth-134
Switched to branch 'autosynth-134'
2020-06-05 15:53:21,457 autosynth [INFO] > Running synthtool
2020-06-05 15:53:21,457 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-06-05 15:53:21,459 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2020-06-05 15:53:21,681 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/nodejs-phishing-protection/synth.py.
On branch autosynth-134
nothing to commit, working tree clean
2020-06-05 15:53:21,823 synthtool [DEBUG] > Ensuring dependencies.
DEBUG:synthtool:Ensuring dependencies.
2020-06-05 15:53:21,828 synthtool [DEBUG] > Cloning googleapis.
DEBUG:synthtool:Cloning googleapis.
2020-06-05 15:53:21,829 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2020-06-05 15:53:21,832 synthtool [DEBUG] > Pulling Docker image: gapic-generator-typescript:latest
DEBUG:synthtool:Pulling Docker image: gapic-generator-typescript:latest
latest: Pulling from gapic-images/gapic-generator-typescript
Digest: sha256:c9bc12024eddcfb94501627ff5b3ea302370995e9a2c9cde6b3317375d7e7b66
Status: Image is up to date for gcr.io/gapic-images/gapic-generator-typescript:latest
2020-06-05 15:53:22,710 synthtool [DEBUG] > Generating code for: google/cloud/phishingprotection/v1beta1.
DEBUG:synthtool:Generating code for: google/cloud/phishingprotection/v1beta1.
gapic-generator-typescript: https://github.com/googleapis/gapic-generator-typescript
Latest commit:
commit a858a371e225254fca1c32d8d6b142b42cb711ad
Author: release-please[bot]<EMAIL_ADDRESS>Date:   Thu Jun 4 16:54:54 2020 -0700

child_process.js:642
    throw err;
    ^

Error: spawnSync protoc EACCES
    at Object.spawnSync (internal/child_process.js:1041:20)
    at spawnSync (child_process.js:607:24)
    at Object.execFileSync (child_process.js:634:15)
    at Object.<anonymous> (/usr/local/lib/node_modules/@google-cloud/gapic-generator/build/src/gapic-generator-typescript.js:117:17)
    at Module._compile (internal/modules/cjs/loader.js:955:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
    at Module.load (internal/modules/cjs/loader.js:811:32)
    at Function.Module._load (internal/modules/cjs/loader.js:723:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
    at internal/main/run_main_module.js:17:11 {
  errno: 'EACCES',
  code: 'EACCES',
  syscall: 'spawnSync protoc',
  path: 'protoc',
  spawnargs: [
<EMAIL_ADDRESS>    '--typescript_gapic_out=/out',
    '--gapic-validator_out=.',
    '--typescript_gapic_opt="grpc-service-config=google/cloud/phishingprotection/v1beta1/phishingprotection_grpc_service_config.json"',
    '--typescript_gapic_opt="package-name=@google-cloud/phishing-protection"',
    '--experimental_allow_proto3_optional',
    '-I/in',
    '/in/google/cloud/phishingprotection/v1beta1/phishingprotection.proto',
    '/in/google/cloud/common_resources.proto',
    '-I/protos/api-common-protos-master'
  ],
  error: [Circular],
  status: null,
  signal: null,
  output: null,
  pid: 18,
  stdout: null,
  stderr: null
}
2020-06-05 15:53:23,530 synthtool [DEBUG] > Wrote metadata to synth.metadata.
DEBUG:synthtool:Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/nodejs-phishing-protection/synth.py", line 36, in <module>
    extra_proto_files=['google/cloud/common_resources.proto'],
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 66, in typescript_library
    return self._generate_code(service, version, "typescript", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_microgenerator.py", line 195, in _generate_code
    f"Code generation seemed to succeed, but {output_dir} is empty."
RuntimeError: Code generation seemed to succeed, but /tmpfs/tmp/tmpfa48pmpk is empty.
2020-06-05 15:53:23,564 autosynth [ERROR] > Synthesis failed
2020-06-05 15:53:23,565 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 2a56034 chore: release 2.0.1 (#145)
2020-06-05 15:53:23,570 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2020-06-05 15:53:23,574 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 595, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 371, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 381, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 266, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 119, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Relapse: Double Trigger when using Hue Wall Switch

Issue
With the latest version of HuePlugin v0.14.6 the double trigger when using Wall Switch came back.
Latest GitHub Ticket for that issue was: https://github.com/ebaauw/homebridge-hue/issues/1148
I did a fallback to the version v0.14.3 and all is stable again.
Log Messages
[20/11/2024, 17:28:50] [Hue-Bridge] SWI - Deckenleuchte Rocker 1: homekit button single press
[20/11/2024, 17:28:51] [Hue-Bridge] Deckenlampe: homekit on changed from false to true
[20/11/2024, 17:28:51] [Hue-Bridge] Deckenlampe: homekit brightness changed from 100% to 100%
[20/11/2024, 17:28:51] [Hue-Bridge] SWI - Deckenleuchte Rocker 1: homekit button single press
[20/11/2024, 17:28:51] [Hue-Bridge] Deckenlampe: homekit on changed from true to false
Debug Files
Not done yet. Let me know if needed.

Damn, check whether event stream was active happened too early (before the event stream was opened).  Fixed in v0.14.7.

Regression test done. No issues anymore with version v0.14.7. Issue can be closed. Many Thanks. 👍


Make schemas quack like procs/lambdas

At the moment you use schemas like:
    ClientRequest = Dry::Schema.Params do
      required(:request_id) { filled? > str? }
      required(:client_logid).filled(:string)
      required(:name).filled(:string)
      required(:currency).filled(:string)
    end

  ClientRequest.call(client_logid: 'foo', name: 'Foo', currency: 'EUR')

if you were to mix in something like this into Dry::Schema.Params:
module Functional
  def method_call
    method(:call)
  end

  delegate :>>, :<<, to: :method_call

  alias_method :as_proc, :method_call

  def [] *args, &block
    call(*args, &block)
  end
end

you would get full inter-operability with the "ruby lambda ecosystem", ie:

use the same short syntax for calling schemas like you do with lambdas ClientRequest[client_logid: 'foo', name: 'Foo', currency: 'EUR']
you would get compatibility with rxruby and similar functional libraries
you would be able to use Ruby 2.6 function composition ie: (UserValidator >> ApiValidator >> SomeProcOrMethodDoingValidating)[request]
...

I have been using "functional" mixins with "single public method classes" in my code for years now, I have only good things to say about it and the flexibility it allows you to play with and mix components :+1:

Ah I totally forgot to bring back this functionality. It'll be added for sure!

I added #to_proc and #[], this should be enough. For #>> and #<< I think dry-validation will be a better place.


remove service manager, which is obsolete

Hello @jazzdan,
Please review the following commits I made in branch nicks/ch55/service:
aaa4848a9d89eed437c1d209ea5d551f85731bda (2018-09-13 15:31:03 -0400)
remove service manager, which is obsolete

:tropical_fish: :tropical_fish: :tropical_fish:


Migrate MPI CI

Move back github hosted runners for the time being.
Note that workflow is being kept in the current format since we should be moving this back to our own cluster in the new year.

Thanks, merging

Thanks, merging


Define process for transfering files, recommend tools.

this looks promissing https://rclone.org/

agreed. WRT downloads, at least provide direct links for wget/curl

Andrey suggested this tool: https://github.com/odeke-em/drive#drive

There is also: https://rclone.org/
I haven't used it.
I am a bit worried that this quantity of data is beyond what google drive
is design for.

I agree with Mark

using synapse


User is unable to access collection edit form

Hi Amy, I followed your steps; logged in, and see the 'Logout'
link in the top window frame on the right. So the login seems
successful. I find my collection (Collated election voter turnout 2008 to 2018)
and see the "Terms of Use and..." section. I currently have no license
set (this is public data). When I click the pen icon, I get the popup error
window below.
Just FYI; not urgent on my end, as long as people can download the
collection and use it.
best,
Andreas

He was clicking on the item pencil instead of the collection pencil and was running into this error because the license wasn't properly set.


[Recovery] CBI Rear Bumper

Product Link
Cost: 1,980.00

C4 fab might be a better route since CBI is very expensive and C4 provides raw metal which means i could give it any color i want.

If using CBI buy from revere they allow for lighting configurations https://revereoverland.com/products/2022-toyota-tundra-rear-bumper?variant=44277881372949


Added support of nested translation directories

Accordingly feature request rmariuzzo/Laravel-JS-Localization/issues/43
Implements support of nested translation directories. trans('forum/thread.allThreads') will work the same way as native Laravel trans function then.

Travis config was updated, because of npm errors were thrown.


Missing dependency on Docile

It seems that IterativeSolvers depends on Docile but does not declare it (at least Pkg.clone("...iterativeSolvers.jl.git") does not install it) and later loading it gives following error in julia v0.3.5.
ERROR: Docile not found
 in require at loading.jl:47
 in include at ./boot.jl:245
 in include_from_node1 at ./loading.jl:128
 in reload_path at loading.jl:152
 in _require at loading.jl:67
 in require at loading.jl:54
 in include at ./boot.jl:245
 in include_from_node1 at ./loading.jl:128
 in include at ./boot.jl:245
 in include_from_node1 at ./loading.jl:128
 in include at ./boot.jl:245
 in include_from_node1 at ./loading.jl:128
 in reload_path at loading.jl:152
 in _require at loading.jl:67
 in require at loading.jl:51
while loading /home/jaak/.julia/v0.3/IterativeSolvers/src/IterativeSolvers.jl, in expression starting on line 6

Docile is only required for julia 0.3.x (it is integrated into 0.4-dev), and unfortunately there is currently no way to specify this dependency conditionally in Julia's package manager.
Ref: JuliaLang/julia#6195 MichaelHatherly/Docile.jl#64


Am i allowed to change the name and skin of the bot in your map, and if so, how do i do it?

You have to change the command blocks in the actual map, look for a command that is like player TheobaldTheBot spawn, and just change every theobaldthebot to your wanted skin/name. This is a fork of carpet mod, which doesn't affect the actual player which spawns, the player is defined in the world. This mod just changes the way the fake players from the original carpet mod work.


Creating GA4 Funnel Exploration reports in GA4

As a team
we need to monitor website conversions
so that we can identify and fix bugs or identify use cases for new features.
Reporting requirements:

user journey from catalogue search to works page view to item page view
user journey from image search to image modal view to image item page view

Draft GA4 Funnel Exploration report