make error

Hi folks,
thank you so much for creating and maintaining this repository. I would like to build and use it. This is what I did so far.
mkdir build
cd build/
cmake ..
make

And this is the error I end up with.
~/GitHub/ttwatch/build$ make
[ 25%] Built target libttbin
[ 27%] Linking C executable ttbincnv
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `root_container__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:20: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `root_container__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:27: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `root_container__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:34: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `root_container__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:43: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `root_container__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:53: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `metadata__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:65: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `metadata__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:72: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `metadata__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:79: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `metadata__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:88: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `metadata__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:98: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `data_container__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:110: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `data_container__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:117: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `data_container__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:124: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `data_container__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:133: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `data_container__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:143: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `sub_data_container__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:155: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `sub_data_container__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:162: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `sub_data_container__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:169: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `sub_data_container__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:178: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `sub_data_container__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:188: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `device_info__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:200: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `device_info__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:207: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `device_info__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:214: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `device_info__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:223: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `device_info__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:233: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `software_version__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:245: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `software_version__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:252: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `software_version__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:259: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `software_version__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:268: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `software_version__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:278: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `unknown01__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:290: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `unknown01__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:297: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `unknown01__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:304: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `unknown01__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:313: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `unknown01__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:323: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `summary_record__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:335: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `summary_record__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:342: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `summary_record__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:349: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `summary_record__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:358: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `summary_record__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:368: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record2__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:380: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record2__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:387: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record2__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:394: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record2__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:403: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record2__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:413: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `tag_value_container__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:425: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `tag_value_container__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:432: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `tag_value_container__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:439: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `tag_value_container__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:448: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `tag_value_container__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:458: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `value_container__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:470: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `value_container__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:477: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `value_container__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:484: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `value_container__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:493: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `value_container__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:503: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record3__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:515: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record3__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:522: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record3__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:529: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record3__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:538: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record3__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:548: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record4__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:560: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record4__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:567: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record4__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:574: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record4__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:583: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `record4__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:593: undefined reference to `protobuf_c_message_free_unpacked'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `activity__get_packed_size':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:605: undefined reference to `protobuf_c_message_get_packed_size'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `activity__pack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:612: undefined reference to `protobuf_c_message_pack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `activity__pack_to_buffer':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:619: undefined reference to `protobuf_c_message_pack_to_buffer'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `activity__unpack':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:628: undefined reference to `protobuf_c_message_unpack'
/usr/bin/ld: libttbin.a(activity_tracking.pb-c.c.o): in function `activity__free_unpacked':
/home/user/GitHub/ttwatch/src/protobuf/activity_tracking.pb-c.c:638: undefined reference to `protobuf_c_message_free_unpacked'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/ttbincnv.dir/build.make:86: ttbincnv] Error 1
make[1]: *** [CMakeFiles/Makefile2:142: CMakeFiles/ttbincnv.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

I appreciate any hint that is pointing me in the right direction. I read the documentation and tried to install all dependencies on the following computer I am using.
~/GitHub/ttwatch/build$ uname -a
Linux tpx200 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64 GNU/Linux

Hopefully I am just blind and do not see the issue myself. Please unblind me. ;-)
Cheers!

Hi folks,
I still do not now why, however after I build and installed protobuf c compiler from this repository on my own, also ttwatch ran entirely through the make call.
I am only guessing, but it might be related to the installation directory of protobuf c compiler. I was playing around and ended up installing it to /usr/lib instead of /usr/local/lib.

Please unblind me. ;-)

Well, just give some time for answers. The README says:

Prebuilt packages should be available for most systems using the system's built in package manager (dpkg, yum, apt, rpm etc...). Make sure that the -dev version of the packages (eg. libssl-dev, libcurl-dev, libusb-1.0-0-dev) are installed so that the headers are available.

Since you seem to be using a variant of Debian, you would probably need to do:
apt-get install libprotobuf-dev

I am only guessing, but it might be related to the installation directory of protobuf c compiler. I was playing around and ended up installing it to /usr/lib instead of /usr/local/lib.

Sure. If you compile yourself, you don't want this to mix random versions of libraries with (Debian) distribution libraries. That's why you would install your custom protobuf to /usr/local. And then you would tell cmake that it needs to look there, in general, or at least for protobuf.
Now you installed to /usr/lib, and possibly replaced files of Debian package libprotobuf. So other programs from Debian which rely on the specific version provided by Debian may fail. In the best case with a big bang. In the worst case in very subtle ways.

For the record, "Prebuilt package" of protobuf gives the error above on Debian/Ubuntu systems, but it's ok on Fedora.


[NEW]: LastPass vaults starting to get cracked - crypto stolen

Date
2023-9-5
Description
MetaMask CEO and other researchers are finding that lots of stolen crypto going to same/linked address, common link between thefts is that the users were all LastPass users. This is the first real example I've seen of LastPass vaults cracked and used in the wild. Fitting that it's crypto
Links
https://krebsonsecurity.com/2023/09/experts-fear-crooks-are-cracking-keys-stolen-in-lastpass-breach/
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
No response
Personal link
No response

Thanks!


RUB-18 Fixes from standard gem

@rtdp Used standard ruby gem to generate these fixes. Please review.

@rtdp Should I merge this ?

@ashish91 yes, please get this merged first, so that you can revamp other PRs for this standard and then those merged too.

@ashish91 once conflicts are fixed, please merge this.


Automatically close Modaal when video stops playing

Hey, first off - thanks for a superb solution for modals.
I have a modaal that has a Vimeo (YouTube is also useful) video that autoplays when you open it. Though once it's stopped playing you have to manually close the modaal.
Is it possible to make it so the modaal closes automatically once the video ends? It would be a very useful feature if not! I appreciate any help.
Thanks in advance.

Hey @elliottmangham thanks for the kind words. Currently there is no support to detect video end, and allow for an event to fire, or other video events.
Our goal is to keep Modaal as lean as possible while ticking all the right boxes of accessibility, aesthetics and features other designers and developers might want. Extending the plugin to support video events would introduce other dependencies and weight that not all users may want, such as the need for the Vimeo Froogaloop library.
See this stack overflow thread, and this Vimeo developer page for information and examples on how you may be able to connect to your video to a 'finish' event. You could then, using that event, call the $('.modaal-selector').modaal('close'); method to trigger the modal close.
Youtube appears to be slightly more friendly however I don't believe it would be wise at this time to add these event checks for one supported video format and not the other in the plugin's current setup, without overcomplicating things.
We may look into this again sometime down the track if we ever extend the video functionality for more control.

@danhumaan thank you! And that's perfectly understandable, actually it's what I love about Modaal (how clean it is) so it makes sense. I'll have a look at the links you provided and see what I can do.


Operating system library: Copy file to an existing directory

Robot Framework version: 2.9.2
Python Interpreter: Jython 2.7.0 on java1.8.0_65
Operating System: Windows 8.1
I have been trying to copy a file to an existing folder using "OperatingSystem.Copy File" but encounter the following error:
 :  FAIL : OSError: [Errno 21] Is a directory:
The culprit is located in lines 806-807 of robotframework/src/robot/libraries/OperatingSystem.py.  The _atomic_copy function tries to remove the destination directory if it is already there.
In my case, I do not have the permission to remove the destination directory.  In addition to the permission, we cannot assume that we are always copying files to an empty directory.  Some files may have already be there and are needed.
I suggest that lines 806-807 should not remove the existing directory.

Those lines are there to remove possible destination file if it already exists. It seems you are trying to copy a file over an existing directory, not into an existing directory. The latter should definitely work.

Yes, you read my mind.  I was trying to copy a file to an existing directory.  From the documentation, I should be able to specify the destination by its directory:

If the destination is an existing directory, the source file is copied into it. A possible file with the same name as the source is overwritten.

With this line, the destination directory is removed prior copying the file over.  @pekkaklarck , would you consider the bug to be in the code or in the documentation?

Based on the code you are copying over an existing directory, not into it. I'm fairly certain the latter is tested pretty thoroughly. Bugs are always possible, though. To know for sure, we'd need an example we can run ourselves.

Thanks for getting back to me quickly.
It looks like the software that I've been testing is actively working on the same directory when the robot tests are running.  The error may be triggered by the fact that robot cannot carry out the copy file operation.  The following seems fine on both jybot and robot:
RobotFrameworkIssue2319.txt


Fix WebArchive links in Documents page

The Documents page currently has only dead links to WebArchive, making it impossible to access the Constitution, Meeting Minutes, etc which have been ported to the new website. These links should be fixed to allow navigation within https://ufvcsa.ca.
This is a subissue for #7.

The links directly on /docs.html are fixed, but it's worth noting that the meeting minutes page still contains old WebArchive links. Currently, I don't think this is an issue, but in the future it's probably going to be worth porting those over and reformatting the page so it contains them instead, for historical purposes.


Compilation fails for 6.3 kernel

Environment:
6.3.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12) x86_64 GNU/Linux - Debian Trixie
xorg-server 2:21.1.7-1
Issue:
Apt install fails as follows:
sudo apt install evdi-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  evdi-dkms
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B/30.6 kB of archives.
After this operation, 172 kB of additional disk space will be used.
Selecting previously unselected package evdi-dkms.
(Reading database ... 258204 files and directories currently installed.)
Preparing to unpack .../evdi-dkms_1.12.0+dfsg-0.3_all.deb ...
Unpacking evdi-dkms (1.12.0+dfsg-0.3) ...
Setting up evdi-dkms (1.12.0+dfsg-0.3) ...
Loading new evdi-1.12.0+dfsg DKMS files...
Building for 6.3.0-1-amd64
Building initial module for 6.3.0-1-amd64
Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
Consult /var/lib/dkms/evdi/1.12.0+dfsg/build/make.log for more information.
dpkg: error processing package evdi-dkms (--configure):
 installed evdi-dkms package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 evdi-dkms

The make log is this:
make.log

This works with the latest master / 1.14.  I'll be NMU'ing the package over in Debian; @opirko-ui, should be fixed in trixie in a couple of days.

Alright, thanks @hlieberman :+1:

Tried it out today and works now. Thanks again.


--from does not accept pattern starting with #

$ repren --from '#include <a.h>' --to '#include <b.h>' .
error: found no parse patterns

Same with --literal:
$ repren --literal --from '#include <a.h>' --to '#include <b.h>' .
error: found no parse patterns

--
This is because it interprets the # as a comment character (in function parse_patterns()).
It would be nice if this comment logic did not apply when patterns are supplied directly via --from --to, and/or when --literal is given.

Yeah, agreed. Feel free to submit a PR (with a test showing it working).


Move default getClientIp to use proxy-addr, just like express does.

Includes #61 which bumps lodash version to fix security issues. Typos fixed in the readme.
Removes allowedHeaders in favour of proxy-addr (to streamline with Express behind proxies).
For more info and discussion check issue #62

@pdefreitas perhaps it would be good to republish as express-ipfilter2 ? since this is unmaintained?

@bam-interactive do you intend to maintain the package or could someone take ownership or at least be maintainer?

@casz I can republish this project as express-ipfilter2 tomorow. I don't think the current owner of the repo is active.

@pdefreitas could you try ask NPM transferring ownership first 😅

https://www.npmjs.com/policies/disputes

@casz thanks for sharing, I have contacted NPM.

I followed up with @pdefreitas but just so every knows, I left the company a while back so I haven't been able to administer this at all. I reached out to see if I can get the ownership transferred and will let you know what happens

thanks for the update @ryanbillingsley 🙌

@pdefreitas @casz as you may have noticed, the repo was transferred back to me. I will look at this PR as soon as I can this evening.
I mentioned it on #61, but I do want to get that version in before pushing a new major version out so I will try and get that taken care of if it isn't already by the time I can get to it.


07/29/2018 23:50 : Create Pull Request for branch master -> prTesting1_2018072923

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Check out this file and Create WSD_LeskUpgrade.py

This is upgradation of standard Lesk Algorithm For Word sense Disambiguation

I'm sorry @DASHANANT... in the case of established methods we are only taking bug fixes.

Okay , but is it working correctly?


Update CONTRIBUTING.rst

Description

Update the following:

[ ] branching structure
[ ] how to make releases
[ ] how towncrier works

closed via #418


[Do not merge] Conditional phrase triggering test

This is a PoC that checks if we are able to change nexmark args depending on branch we use in Jenkins.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


A button inside PopupPanel always gets stretched to fill the whole panel

Godot version: 3.1
OS/device including version: Xubuntu 18.10 x86_64
Issue description:
A button inside PopupPanel always gets stretched to fill the whole panel. PopupDialog works as expected.
Steps to reproduce:

Create a new project.
Add a PopupPanel node and a single Button node as its child.
Manually position and resize the button.
Call panel's .popup() in root node's _ready() function.
Play the project.

CC @groud

Still valid in 6a683f8

It seems like that's intended behavior, it fits in the children into the panel intentionally:
https://github.com/godotengine/godot/blob/8a21f7231f0851aec4c06abee28a549b1f8083fd/scene/gui/popup.cpp#L220-L244
(similar for 3.x)
So PopupPanel seems to work like PanelContainer, not like Panel. I guess that's not a bug, just a matter of documenting it properly.


Generate libdispatch.pc on non-apple platforms

libdispatch should install a pkg-config file as it is the defacto standard querying mechanism on Linux, and other platforms (excluding Apple).

I'm not sure how I feel about this. We should instead just provide a DispatchConfig.cmake instead I think.

I will look into that!

I'm not sure how I feel about this. We should instead just provide a DispatchConfig.cmake instead I think.

Do you mean a Configuration in cmake/config? Should I write a cmake function or just extract the existing generation of the pkg config file?

@compnerd

I'm not sure how I feel about this. We should instead just provide a DispatchConfig.cmake instead I think.

Do you mean a Configuration in cmake/config? Should I write a cmake function or just extract the existing generation of the pkg config file?

No, CMake has its own means of providing the configuration for the project.  Look at the CMake documentation related to FindPackage.


Fix footer responsive

Fixed footer responsiveness issue  for issue #570. Thanks in advance for the code review :)

Overall looks very good! As a general rule we're not using inline styling for each element.
We use styles.js or makeStyles function according to the style doc
https://github.com/civictechindex/CTI-website-frontend/blob/main/UI-THEME-STYLES.md

Thanks for the review, I resolved all the thing we mention above

There seems to be a unit test that failed.  I don't think it's related to any of your changes, so just try submitting the new changes (moving styling from elements to styles.js).


is it possible to show magnification in slider widget, how to do that

hello.
is it possible to show magnification in slider widget, how to do that if yes
like 20x when slide to level 5, 40x when slide to level 10, and show the 20x/40x when scroll the slider bar

Not directly, but it wouldn't be hard: for instance, you could use map.geoOn(geo.event.zoom, () => {<some code to update a DOM element with the scale>}).

thanks for the reply sir.
i can't figure out what DOM element i can update to achieve that after reading the sliderWidget
so i modified the geo.js, add a d3 text like this
m_level = svg.append('text')
  .text('20')
  .attr('x', m_xscale(0))
  .attr('y', m_yscale(0.5) - m_nubSize)
  .attr('width', m_width/2)
  .attr('height', m_nubSize)
  .attr('font-size', 12)
  .style('dominant-baseline', 'central')
  .style('text-anchor', 'middle');

then update the y and text
this._update = function (obj) {
  var map = m_this.layer().map(),
    zoomRange = map.zoomRange(),
    zoom = map.zoom(),
    zoomScale = d3.scale.linear();
  obj = obj || {};
  zoom = obj.value || zoom;
  zoomScale.domain([zoomRange.min, zoomRange.max]).range([1, 0]).clamp(true);
  m_nub.attr('y', m_yscale(zoomScale(zoom)) - m_nubSize / 2);
  m_level.attr('y', m_yscale(zoomScale(zoom)) - m_nubSize);
  m_level.text(((parseInt(zoom)+1)*5).toString());
};

now it looks like this

i got an magnification text which can change with the zoom event, but it can only locate upon the nub, as the text will be covered when i change the m_level x bigger than m_xscale(4)
i guess its a bad idea to modify the source code right, do you have any suggestions to do it in an elegant way


set the values of maturestop, maturestart to 0

In my modification, I didn't allow for mismatches. If the mature sequence is not found, I set the values of maturestop, maturestart and other related fields to 0 in the output. Additionally, some error trapping is implemented, and the code will output a warning.

I've decided not to go this route. Thank you for the modifications, but ultimately adding 0's as a non-value place holder is not appropriate for the analysis.


Deps not mentioned in docs

Hi
There are a couple of deps that the Limix master of today (13/08/2014) has that are not mentioned in the docs:

h5py
pandas

The deps are checked in setup.py but not mentioned anywhere else. H5PY is a dep for the limix_runner binary that is part of the Python bindings.

I'm closing it since it is already solved.


(1.0) Remove references to private images from project

#160
Removes private image references for 1.0 as well

Testing file changes were not found.
Paging @goodevilgenius to review the back-end work in this pull request!
Paging @Chekote to review the testing work in this pull request!
I couldn't recognize who these files were relevant to:
.circleci/config.yml
docker/docker-compose.yml

!reassign testing


Install Renovate to help manage npm dependencies

More info here:
https://renovatebot.com/docs/configure-renovate/
Being successfully used by the AMP folks and others.  It's also a replacement for GreenKeeper

I don't think we're planning to do this or similar any time soon.


Interval "expand" produces invalid intervals

define "test": expand {Interval[@2020-01-01, @2020-01-08]} per day
The above CQL calculates:
[Interval[2020-01-01, 2020-01-01), Interval[2020-01-02, 2020-01-02) [...]
Those intervals are invalid, both including and excluding a particular day. If the "expand" operator uses the "except" operator, this issue may be linked to issue #560

This same behavior is confirmed for integer intervals.
define "test": expand {Interval[4,6]} //results in Interval[4, 4), Interval[5, 5), Interval[6, 6)]

This is an engine issue, so I've reported it there


IAuthorizeResponseGenerator and IAuthorizeRequestValidator are internal

These two interfaces are internal which makes extensibility less flexible.
For example, if one needs to change/replace AuthorizeEndpoint, these two interface implementations cannot be reused.

IAuthorizeResponseGenerator is now public,
but AuthorizeResponse is not -> cannot build the solution with error
error CS0050: Inconsistent accessibility: return type 'Task' is less accessible than method 'IAuthorizeResponseGenerator.CreateResponseAsync(ValidatedAuthorizeRequest)'

fixed


[RFC] Automatic chunked messaging

How do you envision this feature/change to look/work like?
The new system would automatically split the message data into pieces that wouldn't reach the size limitation of the browser messaging API. Each piece would then be sent as an ArrayBuffer to the recipient (ArrayBuffers can only be sent as number[]) where it would be stored till it receives all chunks of the data. After that the recipient would reassemble it using the split data and extra information submitted with the chunk. After the reconstruction of the message, the chunks need to be deleted.
There would be 3 different types of chunks:
Init chunks
The first chunk to send, it tells the recipient to start collecting chunks for this chunkCollectionId.
interface InitChunk {
	// chunk type
	type: "init";
	// the index of the chunk (helps to reconstruct the data in order)
	// for init chunks this should always be 0
	index: number;
	// an unique ID for the chunks for this specific message
	// this helps to handle multiple messages at once and not
	// confuse the chunks with other messages' chunks
	chunkCollectionId: number;
	// the total amount of chunks that the original message
	// was split to
	totalChunks: number;
	// the length of the data split into chunks
	dataLength: number;
	// the data of the chunks (can be converted back to an ArrayBuffer)
	data: number[];
}

Data chunks
Data chunks are the simplest chunks sent right after the init chunk has been sent.
interface DataChunk {
	type: "data";
	index: number;
	chunkCollectionId: number;
	data: number[];
}

End chunks
The last chunk to send, it tells the recipient to end the collection of the chunks for this chunkCollectionId.
interface EndChunk {
	type: "end";
	// this should be totalChunks - 1
	index: number;
	chunkCollectionId: number;
	data: number[];
}

Chunked messaging flow process
Here is an sketch of how this would work between a content-script and a background service worker.

What is the purpose of this change/feature? Why?
In my testings, the maximum allowed size of messages is 67108862 bytes or ~67 Mbs. This means that if you're trying to send a larger message or bytes of a bigger file, you can't use the browser's messaging API.
The solution to this is chunked messaging, where developers don't need to worry about limits, because if they're handling larger data, the messaging library automatically splits their data into chunks, sends it to the message target and reassembles it on the other side. It would be also nice to allow developers to optionally customize max chunk sizes or otherwise use a fixed limit.
Personally, we deal with large data transmissions in the ArConnect extension, sometimes even gigabytes, so we need a permanent solution to send these datas.
Example implementations
A primitive and basic implementation of this can be found at the ArConnect crypto wallet repo:

Chunks handler
Data builder (from chunks)

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

Running into this problem now, another solution might be - although prob a different RFC - but using Transferables with postMessage like over here https://groups.google.com/a/chromium.org/g/chromium-extensions/c/UyNHEHQKlJA/m/it_eC58DAwAJ


[BUG] Hasura Data Provider - Allow remote schemas and possibility to change ID type

Describe the bug
When a remote schema is imported into Hasura, the grouping relationships are called as {table}_aggregated instead of {table}_aggregate. Right now the Hasura dataProvider always expects that the name of the aggregation table is suffixed with aggregated.

We can see this in https://github.com/refinedev/refine/blob/next/packages/hasura/src/dataProvider/index.ts#L215
Aggregate Problem
const hasuraFilters = generateFilters(filters);

            const operation = metaData?.operation ?? resource;

            const aggregateOperation = `${operation}_aggregate`;

            const hasuraSortingType = `[${operation}_order_by!]`;
            const hasuraFiltersType = `${operation}_bool_exp`;

The same goes for the Hasura id field, which is forced by the data provider to be a uuid and cannot be of the numeric or string type.
https://github.com/refinedev/refine/blob/next/packages/hasura/src/dataProvider/index.ts#L162
UUID Problem
        getOne: async ({ resource, id, metaData }) => {
            const operation = `${metaData?.operation ?? resource}_by_pk`;

            const { query, variables } = gql.query({
                operation,
                variables: {
                    id: { value: id, type: "uuid", required: true },
                    ...metaData?.variables,
                },
                fields: metaData?.fields,
            });

            const response = await client.request(query, variables);

            return {
                data: response[operation],
            };
        },

Is it possible to parameterize these cases in some way or give a solution to the problem?
Steps To Reproduce
For aggregated problem:

Go to Hasura and export a remote Schema
Try to get the list through Hasura Data Provider with useList hook.
Try to execute the next query generated by the dataProvider:

query: "query ($limit: Int, $offset: Int, $where: users_test_bool_exp) { users_test (limit: $limit, offset: $offset) { id, name, lastname, email, genre, role } users_test_aggregate (where: $where) { aggregate { count } } }"
variables: {limit: 20, offset: 0}
For uuid problem:
You could find this problem is your example case of Hasura DataProvider when you try to access to the detail of a post:

Install your hasura data provider sample: npm create refine-app@latest -- --example data-provider-hasura

access to: http://localhost:3000/posts

Access to the detail of a post:

See the network error
{"errors":[{"extensions":{"code":"validation-failed","path":"$.selectionSet.posts_by_pk.args.id"},"message":"variable 'id' is declared as 'uuid!', but used where 'Int!' is expected"}]}

Expected behavior
Give the possibility of defining these use cases for different data schemas by parameterization.
Screenshot
No response
Desktop

OS
Browser: Last Chrome
Data Provider: @pankod/refine-hasura

Mobile
No response
Additional Context
No response

Hey @diegoarda for the UUID problem, you can solve it temporarily.
import { useParams } from "@pankod/refine-react-router-v6";

....

const { id } = useParams();
const { queryResult } = useShow<IPost>({
  metaData: {
    fields: [
      "id",
      "title",
      {
        category: ["title"],
      },
      "content",
    ],
    // override variables
    variables: {
      id: { value: id, type: "Int", required: true },
    },
  },
});

However, as a definitive solution, dataProvider can only be added to client as well as idType.
Can you open a pr for solving these problems to support us? 🙏

I don't understand at all your answer. Do you see better that the option is added to Hasura's GraphQLClient? It's constructor could be new GraphQLClient(url, options, config) where config could be { idType: 'Int' }.
About remote schemas problem, could you fix it?
Thanks a lot!

Hey @diegoarda
I think the temporary solution is not for you. Let me explain my solution in more detail.
You can copy the data provider files to your project and make changes as follows. You can solve this quickly.
const dataProvider = (client: GraphQLClient, options?: { idType: string } }): Required<DataProvider> => {

https://github.com/refinedev/refine/blob/next/packages/hasura/src/dataProvider/index.ts#L154
If you want to contribute to the refine for this topic, you can create a PR 🙏

Hey @diegoarda
I think the temporary solution is not for you. Let me explain my solution in more detail.
You can copy the data provider files to your project and make changes as follows. You can solve this quickly.
const dataProvider = (client: GraphQLClient, options?: { idType: string } }): Required<DataProvider> => {

https://github.com/refinedev/refine/blob/next/packages/hasura/src/dataProvider/index.ts#L154
If you want to contribute to the refine for this topic, you can create a PR 🙏

i will try to create PR for this issue

Hey @zulianrizki, thanks! We are looking forward to it.


fix(api): Keep command keys stable across boots

Overview
Fixes RSS-215. See that ticket for details.
Test Plan
I've reproduced the original problem on an OT-3, and run this branch on an OT-3 and confirmed that it fixes it.
Changelog

Do not use Python's built-in hash() function to compute Protocol Engine command keys, because it changes across runs of the Python interpreter. Instead, compute the hash "manually" with hashlib.md5.
Add tests for this function. The tests can't cover this particular bug, unfortunately, but we should have them anyway.

Review requests
Risk assessment
Low.

Oh @SyntaxColoring if you want to test this exact behavior you could write a little script that calls this code and then run it with a python subprocess twice and check the outputs

Do we use hash() anywhere else?

It looks like we have a few places, but they look legitimate: using hash() to implement __hash__(self).

Oh @SyntaxColoring if you want to test this exact behavior you could write a little script that calls this code and then run it with a python subprocess twice and check the outputs

I was hoping this would work with a pair of concurrent.futures.ProcessPoolExecutors, but I think they share the same hash seed because they're forked from the same parent process.
It's probably possible to get test coverage with something like what you said, where we explicitly start a Python subprocess ourselves. From a call with @TamarZanzouri and @jbleon95, we don't think that's worth it at the moment, though.


window.onerror ReferenceError: "log" is not defined.

I am using bugsnag and it keeps on giving "log" is not defined near line 2272 i.e.
HandlebarsEnvironment.prototype = {
	constructor: HandlebarsEnvironment,

	logger: logger,
	log: log,

Not much to work on here. Can you create a reproducible case in jsfiddle?

Close as there's not enough details for anything actionable here. Glad to reopen if we get some more details that we can work with.


Too many setup.py's

We have too many setup.py's, in different modules, for deployment, for installing from source. All of them have a similar look with subtle differences.
Looks like something that demands refactoring.

Assign to @ultmaster for further design discussion first.


missing --version option

the CLI version of trafilatura does not have a --version option
This would be good to have for reporting issues

Thanks for pointing this out, it's now fixed.


Cannot push to Docker registry

I have a docker registry running on my server.
The apache is used as reverse proxy for ssl and authentication.
Everything worked well with the Registry Version 1.
Now i upgraded to Registry Version 2.
I can log in to the registry via docker login but cannot push any image.
Error message:
docker push registry-docker.synyx.coffee/nginx
The push refers to a repository [registry-docker.synyx.coffee/nginx] (len: 1)
ceab60537ad2: Buffering to Disk
dial tcp <IP_ADDRESS>:80: connection refused

I think the problem exists in my apache config. Using the registry directly works without problems.
This is my apache config:
<VirtualHost _default_:443>
        SSLEngine on
        SSLCertificateFile /etc/ssl/certs/certificate.crt
        SSLCertificateKeyFile /etc/ssl/certs/synyx.coffee.key

        ProxyRequests     off
        ProxyPreserveHost on
        ProxyPass         / http://${REGISTRY_PORT_5000_TCP_ADDR}:5000/
        ProxyPassReverse  / http://${REGISTRY_PORT_5000_TCP_ADDR}:5000/

        LogLevel info ssl:warn

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined
        RequestHeader set X-Forwarded-Protocol "https"
        Header always set Docker-Distribution-Api-Version "registry/2.0"

        <Location />
                AuthType Basic
                AuthName "Docker Repository"
                Order deny,allow
                AuthLDAPUrl ldap://ldap-r.localdomain/ou=People,dc=theia,dc=localdomain
                AuthBasicProvider ldap
                Require valid-user
       </Location>
</VirtualHost>

Does anyone know what would solve my problem?

There is a sample apache config [here].(https://github.com/docker/distribution/blob/master/docs/apache.md)
A quick glance suggests your ProxyPass and ProxyPassReverse are not mapping to the correct url in the v2 registry, all urls are prefixed under /v2/.
Additionally, your apache logs will be useful for debugging this.

Thanks for your help. Now it works. I adjusted the ProxyPass and ProxyPassReverse.
Following config works for me:
<VirtualHost _default_:443>
    SSLEngine on
    SSLCertificateFile /etc/ssl/certs/certificate.crt
    SSLCertificateKeyFile /etc/ssl/certs/synyx.coffee.key

    ProxyRequests     off
    ProxyPreserveHost on

    ProxyPass /error/ !

    ProxyPass        /v2 http://${REGISTRY_PORT_5000_TCP_ADDR}:5000/v2
    ProxyPassReverse /v2 http://${REGISTRY_PORT_5000_TCP_ADDR}:5000/v2

    LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
    Header always set "Docker-Distribution-Api-Version" "registry/2.0"
    Header onsuccess set "Docker-Distribution-Api-Version" "registry/2.0"
    RequestHeader set X-Forwarded-Proto "https"

    <Location /v2>
      AuthType Basic
      AuthName "Docker Repository"
      Order deny,allow
      AuthLDAPUrl ldap://ldap-r.localdomain/ou=People,dc=theia,dc=localdomain
      AuthBasicProvider ldap
      Require valid-user
    </Location>
</VirtualHost>


Option to configure project path

Firstly.. Gorgeous app, loved the onboarding and the sleek ui.. Nice work..I was wondering if you could add an option for configuring project path to save guppy projects at onboarding else use the default path. Also once the project is created you should specify the folder path. Alternatively you could also give a button saying. Open in VScode or some editor..
I had to run the dev server to know the folder path, but again i think this is a fantastic app.. Kudos.

Thank you for your interest in the project.
The features you asked for are already being discussed on https://github.com/joshwcomeau/guppy/issues/52 https://github.com/joshwcomeau/guppy/pull/46 and https://github.com/joshwcomeau/guppy/pull/70
I'm closing this issue on behalf of those. Please consider participating on those conversation if you have anything to add.
Again, thank you for your feedback.


docs: Consider Replacing python-dev with python3-dev in "Installing Superset from Scratch"

The installation guide in the "Installing Superset from Scratch" section currently uses python-dev in the command:
https://github.com/apache/superset/blob/3a7d76cece4408c8e80862ab9db3a38eaaafdc8c/docs/docs/installation/installing-superset-from-scratch.mdx#L21
This package is for Python 2 and not available in recent Ubuntu versions (e.g., 20.04, 22.04), where only python3-dev is supported.
I suggest updating the installation command in the documentation to use python3-dev.

Sorry, actually the command for ubuntu20.04 was clearly written here.
https://github.com/apache/superset/blob/3a7d76cece4408c8e80862ab9db3a38eaaafdc8c/docs/docs/installation/installing-superset-from-scratch.mdx#L27


Set domain to current machine when not explicit.

Background
This fix is in reference to #722 . When configuring the agent if you use .{user} it fails.
We want to support:
.\{user}
\{user}

Reproduction
vsts-agent_layout>config

Connect:

Enter server URL > http://ZZZZZZZZZZ:8080/tfs
Enter authentication type (press enter for Integrated) >
Connecting to server ...

Register Agent:

Enter agent pool (press enter for default) >
Enter agent name (press enter for ZZZZZZZZZZ) >
Scanning for tool capabilities.
Connecting to the server.
Successfully added the agent
Testing agent connection.
Enter work folder (press enter for _work) >
2017-08-24 13:23:26Z: Settings Saved.
Enter run agent as service? (Y/N) (press enter for N) > y
Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) > .\Administrator
Enter Password for the account ZZZZZZZZZZ\Administrator > **********
Cannot grant LogonAsService permission to the user ZZZZZZZZZZ\Administrator
Fix
When updating the login account for missing or . domain name, we need to update not only the logonAccount but also the domainName.
Fix Output
#1
Enter server URL > http://ZZZZZZZZZZ:8080/tfs
Enter authentication type (press enter for Integrated) >
Connecting to server ...

Register Agent:

Enter agent pool (press enter for default) >
Enter agent name (press enter for ZZZZZZZZZZ) >
Scanning for tool capabilities.
Connecting to the server.
Successfully added the agent
Testing agent connection.
Enter work folder (press enter for _work) >
2017-08-24 15:22:43Z: Settings Saved.
Enter run agent as service? (Y/N) (press enter for N) > y
Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) > .\Administrator
Enter Password for the account ZZZZZZZZZZ\Administrator > **********
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ successfully installed
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ successfully set recovery option
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ successfully configured
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ started successfully
#2
vsts-agent_layout>config

Connect:

Enter server URL > http://ZZZZZZZZZZ:8080/tfs
Enter authentication type (press enter for Integrated) >
Connecting to server ...

Register Agent:

Enter agent pool (press enter for default) >
Enter agent name (press enter for ZZZZZZZZZZ) >
Scanning for tool capabilities.
Connecting to the server.
Successfully added the agent
Testing agent connection.
Enter work folder (press enter for _work) >
2017-08-24 15:25:39Z: Settings Saved.
Enter run agent as service? (Y/N) (press enter for N) > y
Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) > \Administrator
Enter Password for the account ZZZZZZZZZZ\Administrator > **********
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ successfully installed
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ successfully set recovery option
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ successfully configured
Service vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ started successfully

@stephenmichaelf,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@TingluoHuang
[2017-08-24 18:05:00Z INFO Terminal] WRITE: Enter User account to use for the service (press enter for NT AUTHORITY\NETWORK SERVICE) >
[2017-08-24 18:05:00Z INFO Terminal] READ LINE
[2017-08-24 18:05:04Z INFO Terminal] Read value: '.\Administrator'
[2017-08-24 18:05:04Z INFO WindowsServiceControlManager] LogonAccount after transforming: ZZZZZZZZZZ\Administrator, user: Administrator, domain: ZZZZZZZZZZ
[2017-08-24 18:05:04Z INFO CommandSettings] Arg 'windowslogonpassword': ''
[2017-08-24 18:05:04Z INFO CommandSettings] Flag 'unattended': 'False'
[2017-08-24 18:05:04Z INFO PromptManager] ReadValue
[2017-08-24 18:05:04Z INFO Terminal] WRITE: Enter Password for the account ZZZZZZZZZZ\Administrator >
[2017-08-24 18:05:04Z INFO Terminal] READ SECRET
[2017-08-24 18:05:09Z INFO Terminal] Read value: '********'
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering IsValidCredentialInternal
[2017-08-24 18:05:09Z INFO NativeWindowsServiceHelper] Verify credential for account Administrator.
[2017-08-24 18:05:09Z INFO NativeWindowsServiceHelper] Credential for account 'Administrator' is valid.
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Credential validation succeed
[2017-08-24 18:05:09Z VERB WindowsServiceControlManager] Entering CalculateServiceName
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Service name 'vstsagent.ZZZZZZZZZZ.ZZZZZZZZZZ' display name 'VSTS Agent (ZZZZZZZZZZ.ZZZZZZZZZZ)' will be used for service configuration.
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering IsServiceExists
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Verifying if the account has LogonAsService permission
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering IsUserHasLogonAsServicePrivilege
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Account Administrator has 'SeServiceLogonRight' right.
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Account: ZZZZZZZZZZ\Administrator already has Logon As Service Privilege.
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Create local group and grant folder permission to service logon account.
[2017-08-24 18:05:09Z VERB WindowsServiceControlManager] Entering GrantDirectoryPermissionForAccount
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Calculated unique group name VSTS_AgentService_Gd7387
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering LocalGroupExists
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Trying to create group VSTS_AgentService_Gd7387
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering CreateLocalGroup
[2017-08-24 18:05:09Z INFO NativeWindowsServiceHelper] Local Group 'VSTS_AgentService_Gd7387' created
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Trying to add userName ZZZZZZZZZZ\Administrator to the group VSTS_AgentService_Gd7387
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering AddMemberToLocalGroup
[2017-08-24 18:05:09Z INFO NativeWindowsServiceHelper] Account 'ZZZZZZZZZZ\Administrator' is added to local group 'VSTS_AgentService_Gd7387'.
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Set full access control to group for the folder E:\github\vsts-agent_layout
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering GrantFullControlToGroup
[2017-08-24 18:05:09Z INFO WindowsServiceControlManager] Set full access control to group for the folder E:\github\vsts-agent_layout_work
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering GrantFullControlToGroup
[2017-08-24 18:05:09Z INFO NativeWindowsServiceHelper] Local group 'VSTS_AgentService_Gd7387' already has full control to path 'E:\github\vsts-agent_layout_work'.
[2017-08-24 18:05:09Z VERB NativeWindowsServiceHelper] Entering InstallService

Looks good.


Write in input

IS there a way to write directly in the input as well, so I can type my own value and then keep changing it using the buttons ?

This is actually not closed.

Unfortunately, i haven't implemented such a feature, would you like to give me a PR on this?

Well, when I'll get some time I'll try to look into it, but do not expect too much tbh.


Google Play Installation

I assume that there are plans to be able to install this eventually through the Play store, right?
Seems like if you have to learn how to build and install this app on your phone manually that there's going to be pretty slow up-take on this.
Any ETA?

@mgifford  See https://github.com/CovidShield/mobile/issues/131#issuecomment-646380950


Refs #27090 -- Added real database sequence introspection

buildbot, test on oracle.

buildbot, test on oracle.

@claudep Sorry 😞. I assumed that "Squash and merge" would behave differently and keep you as an author.

@felixxm I'm granting you my pardon :-)


New version: LGUG2Z.komorebi version 0.1.28

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Here we go again 😅

2024-07-14 16:49:58.687 [FAIL] Installer failed security check. Url: https://github.com/LGUG2Z/komorebi/releases/download/v0.1.28/komorebi-0.1.28-x86_64.msi Result: 0x80004005
2024-07-14 16:49:58.687 [CLI ] Terminating context: 0x8a15002d at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\DownloadFlow.cpp:1e6

Typically these errors resolve themselves within 24-48 hours. We can try re-running the PR periodically


'has process part' in BFO 2020

'has process part' may be redundant in BFO 2020.  BFO 2020 includes 'has occurent part', which is not coextential with 'has process part', but covers most of the same cases.  'has occurrent part' is more general than 'has process part' in that it can have any occurrents as relata, not only processes.
The primary role that 'has process part' plays seems to be specifying the a process' process profiles.  'has occurrent part' is more general than 'has process part', and can have temporal regions or spatiotemporal regions as relata.   If 'has process part' were deprecated, we would need to make sure that only processes, not other occurrents, have process profiles as parts. We could do this pretty straightforwardly by making Process Profile SubclassOf 'occurent part of' some Process.
Another option is to model process profiles differently, without 'has process part'.  The BFO 2020 Reference Document (though not its releases) includes a 'process profile of' object property, which could be used to connect processes to their process profiles.

@ameliakahn @jonathanvajda What exactly is the issue being raised here?

Closing this issue.


FCA Giorgio: Alfa Romeo Stelvio / Giulia

Car
Support for Alfa Romeo Stelvio and Giulia.

[ ] commaai/opendbc#1251
[ ] commaai/panda#1980

Very few actual openpilot changes needed, mainly opening this as a CI runner during development.

We need this route uploaded to the CI bucket: 6a3e5d31bf499cfe/0000000b--a48d1b4e42


Fix default colors

Take the default colors from https://github.com/bheisler/criterion.rs/blob/master/src/plot/plotters_backend/summary.rs.
Fixes #46.

Should probably address #11 too.


error: could not compile bumpalo

I encountered the following error whilst trying to build automerge-c-v2 at commit 3c0c407192076cf97ab4e51f439dc00ead04ea6b on Ubuntu 21.04 e.g.
$ cd automerge-rs/automerge-c-v2
$ cargo build --release
  Downloaded once_cell v1.9.0
  Downloaded thread_local v1.1.4
  Downloaded os_str_bytes v6.0.0
  Downloaded arbitrary v1.0.3
  Downloaded smallvec v1.8.0
  Downloaded anyhow v1.0.53
  Downloaded indexmap v1.8.0
  Downloaded combine v4.6.3
  Downloaded clap v3.0.11
  Downloaded 9 crates (537.8 KB) in 1.07s
warning: output filename collision.
The lib target `automerge` in package `automerge-c-v2 v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c-v2)` has the same output filename as the lib target `automerge` in package `automerge-c v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c)`.
Colliding filename is: /home/jason/workspace/automerge-rs/target/release/deps/libautomerge.so
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The lib target `automerge` in package `automerge-c-v2 v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c-v2)` has the same output filename as the lib target `automerge` in package `automerge-c v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c)`.
Colliding filename is: /home/jason/workspace/automerge-rs/target/release/libautomerge.so
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The lib target `automerge` in package `automerge-c-v2 v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c-v2)` has the same output filename as the lib target `automerge` in package `automerge-c v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c)`.
Colliding filename is: /home/jason/workspace/automerge-rs/target/release/deps/libautomerge.a
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
warning: output filename collision.
The lib target `automerge` in package `automerge-c-v2 v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c-v2)` has the same output filename as the lib target `automerge` in package `automerge-c v0.1.0 (/home/jason/workspace/automerge-rs/automerge-c)`.
Colliding filename is: /home/jason/workspace/automerge-rs/target/release/libautomerge.a
The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
   Compiling log v0.4.14
   Compiling cfg-if v1.0.0
   Compiling serde_json v1.0.78
   Compiling ryu v1.0.9
   Compiling itoa v1.0.1
   Compiling bumpalo v3.9.1
   Compiling typenum v1.15.0
   Compiling lazy_static v1.4.0
   Compiling wasm-bindgen v0.2.79
   Compiling byteorder v1.4.3
   Compiling crc32fast v1.3.1
   Compiling tinyvec_macros v0.1.0
error[E0658]: arbitrary expressions in key-value attributes are unstable
 --> /home/jason/.cargo/registry/src/github.com-1ecc6299db9ec823/bumpalo-3.9.1/src/lib.rs:1:10
  |
1 | #![doc = include_str!("../README.md")]
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: see issue #78835 <https://github.com/rust-lang/rust/issues/78835> for more information

   Compiling hex v0.4.3
   Compiling ppv-lite86 v0.2.16
   Compiling pin-project-lite v0.2.8
error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `bumpalo`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

This problem is apparently a side-effect of Ubuntu 21.04's build of rustc-1.53.0.
The solution was to remove the "rustc" package and install the stable toolchain using the rustup command e.g.
$ sudo apt remove rustc
$ sudo rustup toolchain install stable

Probably we should specify an MSRV, although in this case that wouldn't have helped because the version of cargo that ships with Rust 1.53 doesn't understand the rust-version manifest entry anyway.


Feature Request: Module Schedules

Hi
Firstly thanks for the project.
I was wondering if it would be possible to a schedule to the module config sections.
What I mean is the following
From 05:00 - 10:00 I would like module X to run at position A
From 10:00 - 15:00 I would like module Y to run at position A
This would allow the screen to "dynamically" update with relevant info based on the time of day (could possibly go further and also do it by day)
I am thinking along the lines of between 01:00 - 05:00 I don't need to know the bus times (as they don't run) but I might want to know the temperature. Or in the morning I need to know about trains leaving from X station but in the afternoon I need to know about trains leaving from Y station.
I hope that makes sense ?
I am not a programmer so wouldn't know where to start with this. I could do a crude cron job that swaps out he config files but that feels "wrong"
Thoughts
Thanks

Aargh. just found this https://github.com/ianperrin/MMM-ModuleScheduler
Why couldn't I find it before !
Apologies for wasting your time

Please close the issue
cc @MichMich


Conditionally display template details link

If the policy framework can not create the policy template (because the
CRD does not exist, or if the template is invalid), then the link that
was previously added would go to a page with a not found error. This
change detects most situations where that would occur, and skips adding
the link.
Refs:

https://github.com/stolostron/backlog/issues/24746

Signed-off-by: Justin Kulikauskas<EMAIL_ADDRESS>

/retest-required
🤔
[ci:*frontend] npm ERR! cb() never called!
[ci:*frontend]
[ci:*frontend] npm ERR! This is an error with npm itself. Please report this error at:
[ci:*frontend] npm ERR!     <https://npm.community>
[ci:*frontend]
[ci:*frontend] npm ERR!  Exit status 1
[ci:*frontend] npm ERR!
[ci:*frontend] npm ERR! Failed at the<EMAIL_ADDRESS>ci:frontend script.
[ci:*frontend] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[ci:*frontend]
[ci:*frontend] npm ERR!


make it possible to use react component or string

There is PropTypes warning in a case when I use react class instead of string, although it works fine with function.

Added in v1.4.0


Debugger for C# doesn't work; Hangs in infinite loop

Copied from the original report:
The debugging doesn't work at all. When running 'dotnet run' from an external terminal, the app runs with no problems(builds and runs properly). But when going to the "Run" tab in the "Activity Bar" and launching the ".NET Core Launch (console)" option, nothing happens. It doesn't run the program at all. It is like it hangs in a infinite loop. No breakpoints hit, not even the Main method is executed(tested with my application and with a "Hello World" example). I tried changing the "console" in launch.json to "integratedTerminal", "externalTerminal" and "internalConsole". None work. "ExternalTerminal" goes further then the others, but still nothing show. No print statements show, no cursor movement, no action. Just hangs and nothing. With this option, when i stop the debugger from the vscode itself, it does print "Click any key to continue...". In the end i tried with the ".NET Core Attach", but no success there too. I need to debug my application, because it's essential for my work. Please, I can use some assistance. Haven't had this problem before.
Note: I haven't tested with other languages
Note: Creating a new project and debugging it doesn't fix the issue. It still persists with default debug settings and default launch.json file.
Note: When using "console": "externalTerminal" in launch.json, the settings option "Terminal › External: Linux Exec" is set to "konsole". Tried with "gnome-terminal", but no success.
Environment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version:   3.1.106
Commit:    0f94483edc
Runtime Environment:
OS Name:     arch
OS Version:
OS Platform: Linux
RID:         arch-x64
Base Path:   /usr/share/dotnet/sdk/3.1.106/
Host (useful for support):
Version: 3.1.6
Commit:  47a41ad866
.NET Core SDKs installed:
3.1.106 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
VS Code version: 1.47.3
C# Extension version: V.1.22.1
OmniSharp log
Nothing changes when debugger starts.
Log(Linux username replaced with $USER!):
Starting OmniSharp server at 8/12/2020, 10:30:15 PM
Target: /home/$USER/Documents/Programming/Projects/C#/Binary Search
OmniSharp server started.
Path: /home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/run
PID: 18932
    Starting OmniSharp on arch 0.0 (x64)

    DotNetPath set to dotnet

    Located 1 MSBuild instance(s)
        1: StandAlone 16.4 - "/home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin"

    MSBUILD_EXE_PATH environment variable set to '/home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin/MSBuild.dll'

    Registered MSBuild instance: StandAlone 16.4 - "/home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin"
        CscToolExe = csc.exe
        MSBuildToolsPath = /home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin
        CscToolPath = /home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin/Roslyn
        BypassFrameworkInstallChecks = true
        MSBuildExtensionsPath = /home/$USER/.vscode-oss/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild

    Detecting Cake files in '/home/$USER/Documents/Programming/Projects/C#/Binary Search'.

    Could not find any Cake files

    No solution files found in '/home/$USER/Documents/Programming/Projects/C#/Binary Search'

    Queue project update for '/home/$USER/Documents/Programming/Projects/C#/Binary Search/Binary Search.csproj'

    Detecting CSX files in '/home/$USER/Documents/Programming/Projects/C#/Binary Search'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Loading project: /home/$USER/Documents/Programming/Projects/C#/Binary Search/Binary Search.csproj

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140

    Configuration finished.

    Omnisharp server running using Stdio at location '/home/$USER/Documents/Programming/Projects/C#/Binary Search' on host 18409.

    Successfully loaded project file '/home/$USER/Documents/Programming/Projects/C#/Binary Search/Binary Search.csproj'.

    Adding project '/home/$USER/Documents/Programming/Projects/C#/Binary Search/Binary Search.csproj'

    Update project: Binary Search

    Solution initialized -> queue all documents for code analysis. Initial document count: 4.

Steps to reproduce
I. Open VSCode and a '"Hello world" C# example
II. Place breakpoint in the Main method
III. Start debugger
Expected  behavior
Hitting the breakpoint
Actual behavior
Nothing. No print statements and console hangs in non-existant in the code infinite loop

Can you add a debugger log? Here are instructions: https://github.com/OmniSharp/omnisharp-vscode/wiki/Enabling-C%23-debugger-logging

Debug Console:
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Code - OSS","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
-> (C) {"command":"launch","arguments":{"name":".NET Core Launch (console)","type":"coreclr","request":"launch","preLaunchTask":"build","program":"/home/$USER/Documents/Programming/Projects/C#/Binary Search/bin/Debug/netcoreapp3.1/Binary Search.dll","args":[],"cwd":"/home/$USER/Documents/Programming/Projects/C#/Binary Search","console":"internalConsole","stopAtEntry":false,"logging":{"engineLogging":false},"internalConsoleOptions":"openOnSessionStart","__sessionId":"4a51e22f-07a1-499e-855c-db9ec875c0ce"},"type":"request","seq":2}
<- (E) {"seq":3,"type":"event","event":"output","body":{"category":"console","output":"-------------------------------------------------------------------\nYou may only use the Microsoft .NET Core Debugger (vsdbg) with\nVisual Studio Code, Visual Studio or Visual Studio for Mac software\nto help you develop and test your applications.\n-------------------------------------------------------------------\n"}}
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
<- (R) {"seq":4,"type":"response","request_seq":2,"success":true,"command":"launch"}
<- (E) {"seq":5,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":-1989017584,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"arch","VS.Diagnostics.Debugger.vsdbg.Command":"handshake","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.6.20415.1 commit:0184bb70e1ed40656c0dfa53125805036207007b"}}}
<- (R) {"seq":6,"type":"response","request_seq":1,"success":false,"command":"handshake","message":"Error processing 'handshake' request. Unknown Error: 0x89720010"}

I am not sure why you aren't seeing a better error message (I will take a look), but the problem you are running into is because you are using the OSS version of Visual Studio code. If you want C# debugging, you need to install the official version of VS Code from Microsoft.


Fix python ivf-pq for int8/uint8 dtypes

The ivf-pq python bindings weren't working appropriately for int8/uint8 dtypes. Fix.

/merge


Multi select not working with js array

When using a js array of options multiple select does not work correctly. It works fine when I don't include the multiple attribute.
Here is how I set it up:
var categories = [];

_.each(form.offlineData.categories, function(categoryData, categoryID) {

    var children = [];

    // We need the parent to be selectable, can't select opgroups
    children.push({
        id: categoryID,
        text: categoryData.text
    });

    _.each(categoryData.children, function(childData, childID) {

        children.push({
            id: childID,
            text: childData.text
        });
    });

    categories.push({
        id: categoryID,
        text: categoryData.text,
        children: children
    });
});

$('.category-input').select2({
    data: categories,
    width: '100%'
});

<select name="submission-category" class="category-input text-input--full-width" multiple></select>

This is it working without the multiple tag

Here it is with the multiple tag, as you can see when I choose multiple options it only ever fills the select2-selection__rendered div with the last chosen selection. However as you can see from the gif you get a quick flash of it working as intended (mutliple green tags appearing) before it quickly reverts back to this.

Have you tried using the multiple tag as stated in the documentation? By which I mean.
<select name="submission-category" class="category-input text-input--full-width" multiple="multiple"></select>

Gut instinct makes me think jQuery isn't catching the tag properly.

Yer I've tried multiple="multiple". Also tried "multiple: true" in the js init options

If you check the second gif you can also see it's applying the class select2-selection--multiple correctly too

Humm I wonder if it's not being applied as the array could be causing a race condition? Have you tried delaying select2 being applied until the array has completed?

Worth trying, I've added a 5 second timeout before initialising select2 in the example above, but still no joy :(

It works in isolation so I'll have to assume it's something else in my app
https://jsfiddle.net/omzbrq6d/


Padcirc exe as part of build.sh process

Getting padcirc compiled as a part of build.sh on
Why the padcirc is not getting generated on Hera?
@pvelissariou1  @zacharyburnettNOAA
Note from Takis:
work/makefile go to the line all: (line 500). over there you can define what to build. Currently it compiles/builds metis adcprep adcpost adcirc padcirc and libadc.a

Update:
We need to modify the padcirc line like below:
make NETCDF=enable NETCDF4=enable libadc.a
make NETCDF=enable NETCDF4=enable adcprep
make NETCDF=enable NETCDF4=enable padcirc


Example for object does not work

Actual behavior (the bug)
static class Barbie {

    private String name;
    private String link;

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public String getLink() {
        return link;
    }

    public void setLink(String link) {
        this.link = link;
    }
}

// should contain object example
@OpenApiExample(objects = {
    @OpenApiExampleProperty(name = "name", value = "Margot Robbie"),
    @OpenApiExampleProperty(name = "link", value = "https://www.youtube.com/watch?v=dQw4w9WgXcQ")
})
public @NotNull Barbie getExampleObjects() {
    return new Barbie();
}

With such configuration, at the end I do not see my examples in the OpenAPI specification
"exampleObjects": {
    "name": "string",
    "link": "string"
}

Specification which is generated is
"exampleObjects": {
    $ref": "#/components/schemas/Barbie",
    "example": {
        "name": "Margot Robbie",
        "link": "https://www.youtube.com/watch?v\u003ddQw4w9WgXcQ"
    }
}

....

"Barbie": {
    "type": "object",
    "additionalProperties": false,
    "properties": {
        "name": {
            "type": "string"
        },
        "link": {
            "type": "string"
        }
    }
}

Expected behavior
I would expect, that example should be injected to the openapi description like
"exampleObjects": {
    "name": "Margot Robbie",
    "link": "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
}

So specification code generated should be more like
"exampleObjects": {
    "$ref": "#/components/schemas/Barbie",
},

....

"Barbie": {
    "type": "object",
    "additionalProperties": false,
    "properties": {
        "name": {
            "type": "string",
            "example": "Margot Robbie"
        },
        "link": {
            "type": "string",
            "link": "https://www.youtube.com/watch?v\u003ddQw4w9WgXcQ"
        }
    }
}

Additional context
Currently, when I change type to Barbie[] (the same as we have in existing example Object[]), then it is properly injected example, but it requires to change specification, what it not acceptable.

The intention behind @OpenApiExample(object = {}) is to attach an example in-place, for e.g. unknown types or this particular use-case, so it's not leaked to referenced types. Thanks to that, we can provide such formats for e.g. Object type:
// should contain inline object example
@OpenApiExample(objects = {
    @OpenApiExampleProperty(name = "name", value = "Margot Robbie"),
    @OpenApiExampleProperty(name = "link", value = "https://www.youtube.com/watch?v=dQw4w9WgXcQ")
})
public @NotNull Object getInlinedExampleObject() {
    return new String[] { timestamp };
}

results in:
"inlinedExampleObject" : {
  "type" : "object",
  "example" : {
    "name" : "Margot Robbie",
    "link" : "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
  }
}

And this:
// should contain object example
@OpenApiExample(objects = {
        @OpenApiExampleProperty(name = "Barbie", objects = {
                @OpenApiExampleProperty(name = "name", value = "Margot Robbie"),
                @OpenApiExampleProperty(name = "link", value = "https://www.youtube.com/watch?v=dQw4w9WgXcQ")
        }),
})
public @NotNull Object[] getExampleObjects() {
    return new String[] { timestamp };
}

results in:
"exampleObjects" : {
  "type" : "array",
  "items" : {
    "type" : "object"
  },
  "example" : {
    "Barbie" : {
      "name" : "Margot Robbie",
      "link" : "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
    }
  }
},

If we know the type tho, such as your Barbie type, and we want to define global example for specific fields, it should be specified directly on properties within this type, like here:
https://github.com/javalin/javalin-openapi/blob/0d81c03ba1bc745140317cac01e2a6063b44d7fd/examples/javalin-gradle-kotlin/src/main/java/io/javalin/openapi/plugin/test/JavalinTest.java#L383-L397
So in the referenced object:
"foos" : {
  "type" : "array",
  "items" : {
    "$ref" : "#/components/schemas/Foo"
  }
},

we can see these dedicated examples:
"Foo" : {
  "type" : "object",
  "additionalProperties" : false,
  "properties" : {
    "property" : {
      "type" : "string"
    },
    "link" : {
      "type" : "string",
      "example" : "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
    }
  }
},

As far as I understand, you'd like to achieve a similar result by enforcing @OpenApiExample to override examples in referenced entities. If that's correct, then I see 3 issues:

Descriptions defined on a reference side, not in the entity definition, can overlap - e.g. the same entity can be used in 2 or more places. Each of them can define a custom description, so we're ending up with an entity definition that has multiple examples.
It might be a bit unclear that there are 2 approaches to do the same thing
It might be a little bit painful to implement 😅

I've updated the example to cover this with cases we were talking about:
https://github.com/javalin/javalin-openapi/blob/c86e9dcddc6421558c28619ac279da9326dfab57/examples/javalin-gradle-kotlin/src/main/java/io/javalin/openapi/plugin/test/JavalinTest.java#L343-L370
That returns:
 "exampleFoo" : {
  "$ref" : "#/components/schemas/Foo",
  "example" : {
    "name" : "Margot Robbie",
    "link" : "Dedicated link"
  }
},
"exampleObject" : {
  "type" : "object",
  "example" : {
    "name" : "Margot Robbie",
    "link" : "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
  }
},
"exampleObjects" : {
  "type" : "array",
  "items" : {
    "type" : "object"
  },
  "example" : {
    "Barbie" : {
      "name" : "Margot Robbie",
      "link" : "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
    }
  }
},

and unaffected example (as expected) in the Foo scheme:
"Foo" : {
  "type" : "object",
  "additionalProperties" : false,
  "properties" : {
    "link" : {
      "type" : "string",
      "example" : "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
    }
  }
},


Make default alias more human identifiable

I have lots of peers that have their alias left as the default and it is hard to recongize as a human which are which without basically writing them down.
It would be nice if something more human identifiable was added on so I could recongize them after coming back after a day.
I think a cool idea would be to add emojis based on the node's pubkey

I like this idea.  Similar to https://samouraiwallet.com/paynym | https://paynym.is/ - it would be helpful to have such a thing for LN NodeIDs.

@benthecarman @GlenCooper
Hi there,
I actually did exactly that for Zap Android. I called the project Avathor. It is a specification for avatars based on node public keys.
I made this wallet agnostic and free available so others can implement it as well.
Here is a link to the project.
https://github.com/michaelWuensch/avathor-rfc#avathor


Ad not showing in iOS

Hi,
I have followed all the steps and set up everything but no matter what ad is not showing on the physical iOS device. I wasn't getting the ad in the simulator too, but for the past few days, I'm seeing ads in the simulator. everything is working fine on the android side. I'm calling a function to show an ad and the code for it is as follows.
  componentDidMount() {
    AdMobRewarded.setAdUnitID(this.rewardID);
    AdMobInterstitial.setTestDevices([AdMobInterstitial.simulatorId]);

    AdMobRewarded.addEventListener('rewarded', (reward) => {

    /*this function will reward the user for seeing ads*/

      this.addTickets('ads');

    });
    AdMobRewarded.addEventListener('adLoaded', () =>
      console.log('AdMobRewarded => adLoaded'),
    );
    AdMobRewarded.addEventListener('adFailedToLoad', (error) =>
      console.warn(error),
    );
    AdMobRewarded.addEventListener('adOpened', () =>
      console.log('AdMobRewarded => adOpened'),
    );
    AdMobRewarded.addEventListener('videoStarted', () =>
      console.log('AdMobRewarded => videoStarted'),
    );
    AdMobRewarded.addEventListener('adClosed', () => {
      console.log('AdMobRewarded => adClosed');
      AdMobRewarded.requestAd().catch((error) => {});
    });
    AdMobRewarded.addEventListener('adLeftApplication', () =>
      console.log('AdMobRewarded => adLeftApplication'),
    );
    AdMobRewarded.requestAd().catch((error) => {});
}

    AdMobRewarded.showAd().catch((error) => {
      Toast.show('Ad is not ready, Please try after sometime.');
    });

Package versions
    "react": "16.9.0",
    "react-native": "0.61.5",
    "react-native-admob": "^2.0.0-beta.6",

do I need to start a campaign in Google Ad-Mob for ads to show on the iOS device?
it would be very grateful if someone helps me with this

Facing same issue. any solution on this

Make sure your device is setup as a test device on your Admob profile (app > settings > test devices). The IDFA you need for this you can get using a 3rd party application (e.g. "My Device Id").

Make sure your device is setup as a test device on your Admob profile (app > settings > test devices). The IDFA you need for this you can get using a 3rd party application (e.g. "My Device Id").

Thanks for this, I have one more doubt. So how will this work with the apps listed on the appstore? My app is already there in the appstore.

@MutableLoss Thank you. will try to register real device as test device in Admob. But I am facing the issue in emulator! Which is default test device. Also, the banner and native ads works perfectly fine as testmode in emulator. Only the Interstitial ads has the issue.

@zubinraja try this after setting ad unit id
AdMobInterstitial.setTestDevices([AdMobInterstitial.simulatorId]);
for me, all the issues were in the simulators and iOS devices. is your app in the play store?

Thanks @rahulje9
here is my code
AdMobInterstitial.setAdUnitID('xxxxxxxx');
AdMobInterstitial.setTestDevices([AdMobInterstitial.simulatorId]);
AdMobInterstitial.requestAd().then(() =>{
AdMobInterstitial.showAd();
})

@zubinraja I'm having a similar setup but using AdMobRewarded as I need that one. I have added the code in componentDidMount.
Did you add the necessary codes in the android manifest file?

@rahulje9 Weill in android everything is working cool. in ios facing issue with only interstitial. rest like banner, reward, native ads working cool

@zubinraja Okay, even ads were not showing in the simulator for a really long time, and then it started showing, and then stopped then again started getting ads, no Idea why it is like that. while looking in every forum I was seeing similar issues.

What I mentioned was specific to ads not showing on an iOS device in testing (replying to the OP). This was a common issue for me when testing on a device, as google determines the ID of each device via the the IDFA before showing an ad.
For what it's worth, I also had issues with ads in the iOS simulator early on, but the cause was specific to the validity of my new Admob account. When I got everything sorted on my account, I never had another issue in the simulator. 👍

Tried reward video ads, with the same logs you have kept. And getting below result. All events happens without actual ad is displayed!
[Wed Dec 16 2020 02:09:57.242]  LOG    AdMobRewarded => adLoaded
[Wed Dec 16 2020 02:10:01.904]  LOG      AdMobRewarded => adOpened
[Wed Dec 16 2020 02:10:01.904]  LOG      AdMobRewarded => adClosed
[Wed Dec 16 2020 02:10:03.442]  LOG      AdMobRewarded => adLoaded

New finding to the original issue. observe the code
componentDidMount() {      AdMobRewarded.setAdUnitID('<unitid>');      AdMobRewarded.setTestDevices([AdMobRewarded.simulatorId]);      AdMobRewarded.requestAd(); }
`showVideoAd(){
//setTimeout(() => {
AdMobRewarded.showAd();
  AdMobRewarded.addEventListener('adLoaded', () =>
      {console.log('AdMobRewarded => adLoaded')
      if(this.state.displayVideoAd === true)
          return;
        console.log("show ad");
        AdMobRewarded.showAd();
      }
    );
    AdMobRewarded.addEventListener('adFailedToLoad', (error) =>
      console.warn(error),
    );
    AdMobRewarded.addEventListener('adOpened', () =>
      console.log('AdMobRewarded => adOpened'),
    );
    AdMobRewarded.addEventListener('videoStarted', () =>
      console.log('AdMobRewarded => videoStarted'),
    );
    AdMobRewarded.addEventListener('adClosed', () => {
      console.log('AdMobRewarded => adClosed');
      AdMobRewarded.requestAd().catch((error) => {});
    });
    AdMobRewarded.addEventListener('adLeftApplication', () =>
      console.log('AdMobRewarded => adLeftApplication'),
    );

          // AdMobRewarded.requestAd().then(() =>{
          //   console.log("ad available");
          // }).catch((error) => {});

AdMobRewarded.addEventListener("rewarded",() =>{
  //this.setState({displayVideoAd: true});

});

AdMobRewarded.addEventListener("videoStarted",() =>{
    this.setState({displayVideoAd: true});
    AdMobRewarded.removeAllListeners();
  });

  AdMobRewarded.addEventListener("adFailedToLoad",() =>{
    //this.setState({showNewPNR:true})
  });

//}, 500);
}`
called showVideoAd function on submit click, but it didn't showed the ad. after few seconds, when I closed the modal screen the ad appeared and worked well.

some solution?

I have to be honest, once I got it to show interstitial/reward ads reliably, it was still an uphill battle to consistently show ads afterwards; there are just too many ways to cause ad load crashes. Since this shouldn't be an issue, and it hasn't be addressed by the maintainer, makes me think the module has since been abandoned.

some solution?

I ended up switching to react-native-firebase/admob . Not only did I stop having ad load issues (easy transition btw), but I also gained access to other options this module doesn't offer (content ratings, consents, personalized ads, etc).


Default value of placeholder. command line

Which version and edition of Flyway are you using?
4.2.2
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Not issues
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command line
Which database are you using (type & version)?
Mysql ad postgres
Which operating system are you using?
Linux
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
-placeholders.KYC_VALIDATION=${KYC_VALIDATION}:false
What did you expect to see?
I would expect it will have defalut value for placeholder when KYC_VALIDATION not exist I expect it will get false
What did you see instead?
I would expect it have default value.

We don't think this is the right thing for Flyway.


Chart Line should allow configuring stroke-width

Feature request type
Enhance component
Component name
MudChart
Is your feature request related to a problem?
The stroke-width should be configurable for line charts, so I can use 1 instead of the default value 3. Using 3, the line is bold and the chart is not as readable as I would like.
Describe the solution you'd like
Add a new option in ChartSeries or ChartOptions: public double StrokeWitdth { get; set; }
Then, you can use this option in https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor/Components/Chart/Charts/Line.razor#L38
Have you seen this feature anywhere else?
KendoUI provides stroke configuration https://docs.telerik.com/kendo-ui/api/javascript/dataviz/diagram/line/configuration/stroke
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I've made the requested changes and done a pull request #3645

I've made the requested changes and done a pull request #3645

@Garderoben this one is also resolved

@Garderoben this one is also resolved

pro tip, if you write in the PR next time: fixes #1337   then this issues auto closes :) but thanks!


feat(NOTIFY-1140): add batch PUT endpoint for account syncing

Explanation
This PR replaces the singular PUTs by batch PUTs for account syncing.
References
NOTIFY-1140
Changelog
@metamask/profile-sync-controller

CHANGED: use batch endpoint instead of singular requests to update user storage for account syncing

Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate
[x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

@metamaskbot publish-preview

@metamaskbot publish-preview


New wine 9.0 supports PCSC and Smart card support

More of a comment than an issue. I'll be testing your package to see if this integrates properly.
https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0

Sounds good! Please update the issue with the resume of your test.

@dPing did you ever complete your test under wine 9.0?

I hadn't tried yet and hadn't thought of a good use case but thought it was interesting.
Since MS store apps don't work in wine this chops it down to maybe RDP with mstsc but I believe that uses the less secure flavor of rdp


tvOS compatibility

tvOS compatibility must be added to SRG Analytics.
TagCommander SDKs are not available for tvOS at the moment. An issue has been opened.

The project is being updated for tvOS.
Until TagCommander binaries are available for tvOS, and to make the least possible changes, I manually removed the TCCore and TCSDK binary dependency from all framework targets, and disabled the associated code using preprocessor platform checks.
To avoid altering the build phases to omit copying those frameworks in the tvOS demo, we should copy the iOS frameworks manually into the tvOS Carthage build folder so that the copy phase does not fail. The incorrect framework will be copied in the tvOS bundle but not used, so there will be no error at runtime.
Once the binaries are available (hopefully they will):

[ ] Click on TCCore.framework and TCSDK.framework in the project tree, and use the inspector panel to enable them for all framework targets which have to link against them.*

Here is what still needs to be done:

[ ] Add tvOS TagCommander binaries.
[ ] Click on TCCore.framework and TCSDK.framework in the project tree, and use the inspector panel to enable them for all framework targets which have to link against them.
[ ] Update NetMetrix code for tvOS, or drop it entirely (question asked to @ckuert).

The NetMetrix guidelines for tvOS (here and here) have been applied.
This should be now correct, though I asked @ckuert whether we still need to keep page tracking or not.

UIAutomation purpose is to test UI items. In our case, we need to check that notifications are received, but since the tested app runs in a different process from the test code which controls it, notifications will never be received.
As discussed on Stack Overflow, achieving what we want would require some inter-process notification mechanism, for which Realm blog provides an interesting discussion.
For the moment, though, and since we have very few UI tests, I recommend we drop this test target. I have preserved my investigation code (which shows how a regular unit test target can be transformed into a UI one).

UIAutomation purpose is to test UI items (tap on items, check that displayed items are expected). In our case, we need to check that notifications are received, but since the tested app runs in a different process from the test code which controls it, notifications will never be received.
As discussed on Stack Overflow, achieving what we want would require some inter-process notification mechanism, for which Realm blog provides an interesting discussion.
For the moment, though, and since we have very few UI tests, I recommend we drop this test target. I have preserved my investigation code (which shows how a regular unit test target can be transformed into a UI one).

UIAutomation purpose is to test UI items (tap on items, check that displayed items are expected). In our case, we need to check that notifications are received, but since the tested app runs in a different process from the test code which controls it, notifications will never be received.
As discussed on Stack Overflow, achieving what we want would require some inter-process notification mechanism, for which Realm blog provides an interesting discussion.
For the moment, though, and since we have very few UI tests, I recommend we drop this test target. I have preserved my investigation code (which shows how a regular unit test target can be transformed into a UI one).

UI tests with KIF removed.


Update keybase to 1.0.21-20170413194119,9dea6e1

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

@vitorgalvao thanks for merging.

@debo Thank you for the submission. Have a nice weekend.