Getting an error when giving bigrig a file

I'm having a go at creating a trace and sending it to bigrig for the first time, and I've run into a problem I don't understand.
What I did:

Installed bigrig globally @ 1.2.0
In Chrome 48.0.2564.97 (64-bit)
I opened the app I want to test (localhost)
I closed every other tab
I opened the dev tools, went to the timeline tab, hit cmd+r and waited for the timeline to be recorded
Right click Save Timeline Data, saved it to my desktop
Ran bigrig --file ~/Desktop/Timeline.json -s -pp

Here's the output:
Hannahs-MacBook-Air ~/Desktop $ bigrig --file ~/Desktop/Timeline4.json -s -pp

/usr/local/lib/node_modules/bigrig/lib/third_party/tracing/base/iteration_helpers.js:303
    for (var value of map.values())
                   ^^
Usage: bigrig <input> [<option>]

Options:
  --file, -f            The trace file to be parsed              [default: ""]
  --pretty-print, --pp  Pretty print the results              [default: false]
  --strict, -s          Throw if extensions are found         [default: false]

I also tried creating the trace in an incognito tab, but that resulted in a zero-byte trace file.
Any ideas what I'm doing wrong?

I wonder if there's been a trace file change recently. It's something of a cat-and-mouse game to keep the trace parser inline with the traces that Chrome generates. Is there any way you can post the file up so I can repro the issue at my end? I'll try taking tip-of-tree for the tracing parser and see if that fixes things.

Here ya go http://puu.sh/mNcOz.json

Ahhhhhhh wondering if it's something to do with node versions! for(var x of y) is ES2015 stuff, which is, like, Node 4+, isn't it? Dangit, that's my bad for failing to update the engines property in the package.json. In the short term I've updated the minimum version in package.json, but I'll grab a copy of 0.12 and see if the fixes would be straight forward.

Oh yeah, I'm totally set to 0.10.x by default :grin:


Fix2

Fixed the selection functionality with ctrl key

Replaced all 'document.getElementyById' with Angular methods

Fixed all JsPlumb repaint issues

Cleared all JsPlumb warnings

Refactoring

Other small Bug fixes

Added relationships types for unique colorization

Possible now to generate and drag new nodes from the palette with one click

Opening of the sidebar when clicking on a relationship with all its properties

Changed relationship names are stored into the store

Relationships can only now be deleted by deleting one of the nodes

Multiple different connections between 2 nodes are possible now

Start and end date:  2017-10-09 to 2017-10-20

Contributor: Thommy Zelenik, @zelenikty

Supervisor: Oliver Kopp, @koppor

Yannic said everything, other than that it looks good, going to merge.


Missing .NET Framework 4.8.1 source code

Refiling here, previous issue was closed.
Re: Developer Community item 10491767
Does the .NET team have any plans to provide an updated snapshot of .NET Framework source code? .NET Framework 4.8.1 (released in 2022) is missing. @rzikm indicated the reference source website is in maintenance mode but did not address the actual code request.
By continuing to release the .NET Framework source code, Microsoft is not only affirming its commitment to transparency, but also providing a valuable resource for developers to understand the changes between versions. Furthermore, it plays a crucial role in ensuring that third-party software remains compatible with the .NET Framework.

I'm also missing the source code for 4.8.1.
Even worse is that a project targeting 4.8 will automatically use 4.8.1 runtime if installed, otherwise 4.8(.0).
This makes it very hard to understand what's happening if there is some .net runtime problem.


Set maximal number of relations displayed in the tooltip

For each relationship type, a maximal number should be displayed in the tooltip.

@adammertel : do you mean individual relations of one type, or you mean the limit on branches of trees? Not sure here.

Probably both. The idea is to limit the size of the tooltip.

For the Superclass and SuperordinateLocation trees, which might have different branches (because two Superclasses are allowed), I would allow at least 4 lines of text (corresponding to 2 forks). This also applies to AEE's Superclass tree displayed under As (but not Cs, there I do not request the AEE's Superclass tree and recommend it is not there).
Synonyms, Antonyms etc. take less space, because only a list is given and not any tree. So there, the threshold can be like 5 items, perhaps? But the label length might be an issue here in some cases.

[ ] Tree structure two forks
[x] Clouds & multilple short label
[ ] Clouds & multiple relations max 5.

@davidzbiral what do specifically you mean by "two Superclasses are allowed"?

@adammertel : Sorry about imprecise words - I meant simply that Superclass and SuperordinateLocation allow multiple values. I.e. something you know very well, nothing new.


Migrate S3 CSV Input step from SVN to GIT

S3 CSV Input step resides in my local github repository https://github.com/dbahdano/pdi-s3-csv-input-step-plugin
Before merging this pull request, please create pentaho repository for plugin, merge my changes there, and run the build to publish artifact to ivy

merged in another pull request


Updated pipeline declaration to use with to solve gc issue

As I was working through the examples from the book I continued to receive issues about garbage collection and beam pipelines would not complete with the output files.  Usage of the with statement made sense over setting the results.
One alternative to fix this is also:
result = pipeline.run()
result.wait_until_finish()

I signed it!


Bug: https URL not working with opencv-python

Bug summary:
opencv-contrib-python python library's VideoCapture class  fails to parse https URL received from pafy/youtube-dl. But strangely this bug doesn't exist on same/different machine with OpenCV installed from scratch.
Affected users:
Users with OpenCV installed with opencv-contrib-python or opencv-python python library from PyPi
Non-Affected users:
Users with OpenCV installed from scratch/source-code and not from PyPi(Tested with OpenCV 4.1.0-dev & 3.4.5)
Steps to reproduce

operating system - Ubuntu 18.04.1 bionic

architecture x64

opencv-python            <IP_ADDRESS>

youtube-dl               2019.5.20

pafy                     0.5.4

python_version  3.6/2.7/3.5 tested

Test-Code: You can copy URL directly to cv2.VideoCapture class and this result in same Bug.

import cv2
import pafy

video = pafy.new("dQw4w9WgXcQ")
object = video.getbestvideo()
url = object.url
print(url) #means pafy and youtube-dl working correctly

stream = cv2.VideoCapture(url)

# infinite loop
while True:
	(grabbed, frame) = stream.read()
	# read frames

	# check if frame empty
	if not grabbed:
		print('opencv is buggy')
		break

	cv2.imshow("Output Frame", frame)
	# Show output window

	key = cv2.waitKey(1) & 0xFF
	# check for 'q' key-press
	if key == ord("q"):
		#if 'q' key-pressed break out
		break

cv2.destroyAllWindows()
# close output window

stream.release()
# safely close video stream.

This code exit instantly with no error on opencv-python <IP_ADDRESS> since no frame grabbed BUT instead this algorithm works when OpenCV installed from scratch and returns valid frames.

Update: This may be something to do with G-Streamer not supported on opencv-python.

@abhiTronix cv2 installed using pip install opencv-python fail to load any http videos but works when I installed it from scratch. The .getBuildInformation() printout of my working cv2 installation has no GStreamer.
Python 3.6.8 |Anaconda, Inc.| (default, Dec 30 2018, 01:22:34)
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cv2
>>> print(cv2.getBuildInformation())

General configuration for OpenCV 4.1.0 =====================================
  Version control:               unknown

  Extra modules:
    Location (extra):            /home/han/opencv_contrib-4.0.0/modules
    Version control (extra):     unknown

  Platform:
    Timestamp:                   2019-05-21T17:43:25Z
    Host:                        Linux 4.15.0-50-generic x86_64
    CMake:                       3.10.2
    CMake generator:             Unix Makefiles
    CMake build tool:            /usr/bin/make
    Configuration:               RELEASE

  CPU/HW features:
    Baseline:                    SSE SSE2 SSE3
      requested:                 SSE3
    Dispatched code generation:  SSE4_1 SSE4_2 FP16 AVX AVX2 AVX512_SKX
      requested:                 SSE4_1 SSE4_2 AVX FP16 AVX2 AVX512_SKX
      SSE4_1 (15 files):         + SSSE3 SSE4_1
      SSE4_2 (2 files):          + SSSE3 SSE4_1 POPCNT SSE4_2
      FP16 (1 files):            + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 AVX
      AVX (5 files):             + SSSE3 SSE4_1 POPCNT SSE4_2 AVX
      AVX2 (29 files):           + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 FMA3 AVX AVX2
      AVX512_SKX (2 files):      + SSSE3 SSE4_1 POPCNT SSE4_2 FP16 FMA3 AVX AVX2 AVX_512F AVX512_SKX

  C/C++:
    Built as dynamic libs?:      YES
    C++ Compiler:                /usr/bin/c++  (ver 7.4.0)
    C++ flags (Release):         -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -O3 -DNDEBUG  -DNDEBUG
    C++ flags (Debug):           -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wundef -Winit-self -Wpointer-arith -Wshadow -Wsign-promo -Wuninitialized -Winit-self -Wno-delete-non-virtual-dtor -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections  -msse -msse2 -msse3 -fvisibility=hidden -fvisibility-inlines-hidden -g  -O0 -DDEBUG -D_DEBUG
    C Compiler:                  /usr/bin/cc
    C flags (Release):           -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections  -msse -msse2 -msse3 -fvisibility=hidden -O3 -DNDEBUG  -DNDEBUG
    C flags (Debug):             -fsigned-char -W -Wall -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Wformat -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef -Winit-self -Wpointer-arith -Wshadow -Wuninitialized -Winit-self -Wno-comment -Wimplicit-fallthrough=3 -Wno-strict-overflow -fdiagnostics-show-option -Wno-long-long -pthread -fomit-frame-pointer -ffunction-sections -fdata-sections  -msse -msse2 -msse3 -fvisibility=hidden -g  -O0 -DDEBUG -D_DEBUG
    Linker flags (Release):      -Wl,--gc-sections
    Linker flags (Debug):        -Wl,--gc-sections
    ccache:                      NO
    Precompiled headers:         YES
    Extra dependencies:          dl m pthread rt
    3rdparty dependencies:

  OpenCV modules:
    To be built:                 aruco bgsegm bioinspired calib3d ccalib core datasets dnn dnn_objdetect dpm face features2d flann freetype fuzzy gapi hdf hfs highgui img_hash imgcodecs imgproc line_descriptor ml objdetect optflow phase_unwrapping photo plot python3 reg rgbd saliency shape stereo stitching structured_light superres surface_matching text tracking ts video videoio videostab xfeatures2d ximgproc xobjdetect xphoto
    Disabled:                    world
    Disabled by dependency:      -
    Unavailable:                 cnn_3dobj cudaarithm cudabgsegm cudacodec cudafeatures2d cudafilters cudaimgproc cudalegacy cudaobjdetect cudaoptflow cudastereo cudawarping cudev cvv java js matlab ovis python2 sfm viz
    Applications:                tests perf_tests apps
    Documentation:               NO
    Non-free algorithms:         YES

  GUI:
    GTK+:                        YES (ver 3.22.30)
      GThread :                  YES (ver 2.56.4)
      GtkGlExt:                  NO
    VTK support:                 NO

  Media I/O:
    ZLib:                        /home/han/miniconda3/lib/libz.so (ver 1.2.11)
    JPEG:                        /home/han/miniconda3/lib/libjpeg.so (ver 80)
    WEBP:                        build (ver encoder: 0x020e)
    PNG:                         /home/han/miniconda3/lib/libpng.so (ver 1.6.34)
    TIFF:                        /home/han/miniconda3/lib/libtiff.so (ver 42 / 4.0.9)
    JPEG 2000:                   build (ver 1.900.1)
    OpenEXR:                     /usr/lib/x86_64-linux-gnu/libImath.so /usr/lib/x86_64-linux-gnu/libIlmImf.so /usr/lib/x86_64-linux-gnu/libIex.so /usr/lib/x86_64-linux-gnu/libHalf.so /usr/lib/x86_64-linux-gnu/libIlmThread.so (ver 2.2.0)
    HDR:                         YES
    SUNRASTER:                   YES
    PXM:                         YES
    PFM:                         YES

  Video I/O:
    DC1394:                      YES (2.2.5)
    FFMPEG:                      YES
      avcodec:                   YES (57.107.100)
      avformat:                  YES (57.83.100)
      avutil:                    YES (55.78.100)
      swscale:                   YES (4.8.100)
      avresample:                YES (3.7.0)
    GStreamer:                   NO
    v4l/v4l2:                    YES (linux/videodev2.h)

  Parallel framework:            pthreads

  Trace:                         YES (with Intel ITT)

  Other third-party libraries:
    Intel IPP:                   2019.0.0 Gold [2019.0.0]
           at:                   /home/han/opencv-4.1.0/build/3rdparty/ippicv/ippicv_lnx/icv
    Intel IPP IW:                sources (2019.0.0)
              at:                /home/han/opencv-4.1.0/build/3rdparty/ippicv/ippicv_lnx/iw
    Lapack:                      NO
    Eigen:                       NO
    Custom HAL:                  NO
    Protobuf:                    build (3.5.1)

  OpenCL:                        YES (no extra features)
    Include path:                /home/han/opencv-4.1.0/3rdparty/include/opencl/1.2
    Link libraries:              Dynamic load

  Python 3:
    Interpreter:                 /home/han/.pyenv/shims/python3 (ver 3.6.8)
    Libraries:                   /home/han/miniconda3/lib/libpython3.6m.so (ver 3.6.8)
    numpy:                       /home/han/miniconda3/lib/python3.6/site-packages/numpy/core/include (ver 1.16.3)
    install path:                lib/python3.6/site-packages/cv2/python-3.6

  Python (for build):            /home/han/.pyenv/shims/python3

  Java:
    ant:                         NO
    JNI:                         NO
    Java wrappers:               NO
    Java tests:                  NO

  Install to:                    /usr/local
-----------------------------------------------------------------

The issue is not GStreamer but FFmpeg. It's most likely compiled without https support or some other build flag is missing and therefore it cannot open Youtube video streams.
Your script works under Windows which confirms that this is related to FFmpeg build time configuration. To see the FFmpeg build flags check out the Dockerfiles: https://github.com/skvark/opencv-python/blob/master/docker/Dockerfile_x86_64

@skvark Thanks for this valuable info. Problem is indeed with FFmpeg, and I've discovered the solution:

It's most likely compiled without https support or some other build flag is missing and therefore it cannot open Youtube video streams.

Yes, FFmpeg is compiled with no support for openssl that enables support for https and other protocols in FFmpeg, missing in docker file you provided. It can solved with following steps:

Install libssl development files:  debian: sudo apt install libssl-dev, or on redhat: yum install -y openssl-devel

Add  --enable-openssl --enable-nonfree  --enable-protocol= file,ftp,http,https,httpproxy,hls,mmsh,mmst,pipe,rtmp,rtmps,rtmpt,rtmpts,rtp,sctp,srtp,tcp,udp flags to the FFmpeg configure.

Please take a look here:
https://askubuntu.com/questions/650577/how-to-compile-ffmpeg-with-https-support
https://stackoverflow.com/questions/43565190/couldnt-open-https-stream-protocol-not-found-ffmpeg-with-openssl

Thanks. Note that the flag --enable-nonfree cannot be added because the resulting build must licensed under LGPL (--enable-nonfree makes it GPL). I think OpenSSL has a permissive license, but it must be checked that GPL'ed components are not included.

Thanks @skvark for the update,
Please test if FFmpeg works with openSSL without --enable-nonfree flag. Maybe it does works.
Also when will be these changes will be integrated into opencv-python binaries, are you working on a new PR or You need my help in this?

If there are GPL'ed components I would have to re-license the whole package under GPL license and any package using opencv-python, respectively, would have to be licensed under GPL. This would also mean that this package or any package which uses opencv-python could not be used for commercial purposes / proprietary applications.
I have to re-buid the Docker images and check if this problem is present also on macOS. I cannot give any timetable when this will happen. Please note that this is not a bug. This is a feature request. If you wish to speed up the process, you can try to enable the SSL support in FFmpeg builds locally in the Docker images, build a opencv-python wheel and test if the solution works.

If there are GPL'ed components I would have to re-license the whole package under GPL license and any package using opencv-python, respectively, would have to be licensed under GPL. This would also mean that this package or any package which uses opencv-python could not be used for commercial purposes / proprietary applications.
I have to re-buid the Docker images and check if this problem is present also on macOS. I cannot give any timetable when this will happen. Please note that this is not a bug. This is a feature request. If you wish to speed up the process, you can try to enable the SSL support in FFmpeg builds locally in the Docker images, build a opencv-python wheel and test if the solution works.

Thank you for this valuable information. I don't want the feature right now, but my vidgear python library relies on opencv-python for its core functions and for features like Live YouTube streaming, Thereby I just need heads up from your end to plan next update for vidgear accordingly. So I'll wait for this change. Again thanks for letting me know.

@skvark Hey, Take a look at this issue: https://github.com/opencv/opencv/issues/14617, Is this related?

@abhiTronix , it is not related, that issue is caused by very long string incorrectly processed by built-in CAP_IMAGES backend.

Note that the flag --enable-nonfree cannot be added because the resulting build must licensed under LGPL (--enable-nonfree makes it GPL)

Actually, the complete opposite:
  --enable-nonfree         allow use of nonfree code, the resulting libs
                           and binaries will be unredistributable [no]

However, despite openssl marked nonfree in configure logic, https://github.com/FFmpeg/FFmpeg/blob/master/LICENSE.md#incompatible-libraries claims:

To the best of our knowledge, [Fraunhofer FDK AAC and OpenSSL] are compatible with the LGPL.

git blame'ing configure shows that openssl has been marked nonfree since its adoption and there are no explanation of the reason.
I believe this may have been done to discourage users from choosing these "problematic" libraries over freer alternatives -- in particular, to remove any technical roadblocks to using GPLed parts.
Whatever is the case, GNU TLS (LGPL) should work as an alternative.

@abhiTronix since you are the interested party, could you make a PR?

@abhiTronix since you are the interested party, could you make a PR?

Yeah sure, Please correct me if I'm wrong, I've to make changes to this line:
https://github.com/skvark/opencv-python/blob/da7d02271d2ffca8f293ed3f3032f30881319db8/docker/Dockerfile_x86_64#L53
Also, How do I test these changes, as I currently have access to a Ubuntu machine only? and What should I keep in my mind while making this PR?

The other Dockerfile, too.
You'll need to mimic the build logic as close as practical. IIRC running setup.py bdist_wheel in the resulting container and checking cv2.getBuildInformation() of the resulting wheel (and your use case, naturally) should be enough.
If you enable Travis CI for your fork, you can override the link to Docker image that's somewhere in the build scripts and run the official build logic with your image.

The other Dockerfile, too.
You'll need to mimic the build logic as close as practical. IIRC running setup.py bdist_wheel in the resulting container and checking cv2.getBuildInformation() of the resulting wheel (and your use case, naturally) should be enough to check the SSL support specifically.
If you enable Travis CI for your fork, you can override the link to Docker image that's somewhere in the build scripts and run the official build logic with your image.

Thanks, will do.
Also @native-api and @skvark , Why the turbo-jpeg libs are being built from scratch in the docker file here:
https://github.com/skvark/opencv-python/blob/da7d02271d2ffca8f293ed3f3032f30881319db8/docker/Dockerfile_x86_64#L63
When OpenCV itself provide optimized turbo-jpeg libs starting from this PR: https://github.com/opencv/opencv/pull/11497

The libjpeg-turbo can be removed from the Dockerfiles. It has been there since beginning and I haven't had the time remove it. FYI: I can't provide much support during next 5-7 days but I will try to answer if there's something urgent.

@skvark it seemed to add latency to the have CLI builds, that's a bit concerning. Anyways thanks for the clarification.
Also, I've pushed the PR #229 to fix this issue finally.

Successfully Fixed & Merged in #229


port vertical flip

cc @vfdev-5

They look like identical copies with only a few names / callable / matrices changes

They are. I didn't find a good pattern using base classes:
class Base:
    FOO = None

    @pytest.mark.parametrize("foo", FOO)
    def test_foo(self):
        ...

class Test(Base):
    FOO = ["foo", "bar", "baz"]

The snippet above does not work, since @pytest.mark.parametrize is evaluated at class creation and thus sees FOO=None.
Another approach would be to merge both classes into one TestHorizontalVerticalFlip and parametrize over the kernels, dispatchers, and transforms, e.g.
@pytest.mark.parametrize("kernel", [F.horizontal_flip_image_tensor, F.vertical_flip_image_tensor])
def test_image_kernel(kernel):
    check_kernel(kernel, ...)

If we want that, I'll implement it in a follow-up PR.


calc_Pstatic_TMATS.c problem

Because of the different mass flow in subsonic and supersonic with identical (Pt,Tt,far,Aexit) input, the guess values x1=0.2 & x2=0.5 just are suitable for subsonic flow to calculate Ps, which will cause error in supersonic flow. I think x1&x2 initial values should be distinguished.  Of course, the secant method also easily cause this problem when faced to mass flow curve like this.

What values are you having issues with? I'm not sure what you are referring to as x1 and x2.
This block is meant to back calculate the static conditions based on total conditions. You can assume either a MN or an Area (it says A throat, but is is more just an area. it is not trying to act like a nozzle). If you know the area it then uses the MN as an initial guess. Because there are two answers for each Pt (a subsonic and supersonic) if you guess below 1 you will get a subsonic answer and if you guess above 1 you get supersonic.  This is was it was meant to do anyhow.
If you have specific values that cause the block to crash feel free to post them and I can take a look.
Thanks,
-Jeff

When PtIn & TtIn are defined, the same Area in subsonic or supersonic can get the same Wout, but  corresponding to different Ps. The calc_Pstatic_TMATS() function calculate Ps based on MN iteration. If the initial values is (x1=0.2,x2=0.5), the MN iteration will stop and get Ps at subsonic MN, but the fact is that the Wout&Area may be refered to the Ps at supersonic MN,  so the Ps answer is not correct.
the code as followed,
/----- use these 2 points to start the solution ----/
/*   where x ==> MN, y ==> W, and z ==> Ps */
x1 = 0.2;
x2 = 0.5;
as well as the x1&x2 is not input value in this function.
Thanks.

That’s true, so it is up to the user to know if they are dealing with subsonic or supersonic and fill out the initial MN accordingly.
-Jeff
-----Original Message-----
From: Jackeygou2015<EMAIL_ADDRESS>Sent: Wednesday, December 30, 2015 5:25 PM
To: nasa/T-MATS
Subject: Re: [T-MATS] calc_Pstatic_TMATS.c problem (#58)
When PtIn & TtIn are defined, the same Area in subsonic or supersonic can get the same Wout, but corresponding to different Ps. The calc_Pstatic_TMATS() function calculate Ps based on MN iteration. If the initial values is (x1=0.2,x2=0.5), the MN iteration will stop and get Ps at subsonic MN, but the fact is that the Wout&Area may be refered to the Ps at supersonic MN, so the Ps answer is not correct.
the code as followed,
/----- use these 2 points to start the solution ----/
/* where x ==> MN, y ==> W, and z ==> Ps */
x1 = 0.2;
x2 = 0.5;
as well as the x1&x2 is not input value in this function.
Thanks.
—
Reply to this email directly or view it on GitHub https://github.com/nasa/T-MATS/issues/58#issuecomment-168084686 . https://github.com/notifications/beacon/ACtx8lnNplhLWG_-tdSSnifL5KCkfjgkks5pVFFIgaJpZM4G8fyw.gif

Closing because the question was answered. If there is still concern please post again.


webhook server: "cache contained , which is not an Object" when handling workflow_job event

Checks

[X] I've already read https://github.com/actions-runner-controller/actions-runner-controller/blob/master/TROUBLESHOOTING.md and I'm sure my issue is not covered in the troubleshooting guide.
[X] I'm not using a custom entrypoint in my runner image

Controller Version
0.21.1?
Helm Chart Version
0.21.1
CertManager Version
No response
Deployment Method
Other
cert-manager installation
cert-manager is perfectly working.
Checks

[X] This isn't a question or user support case (For Q&A and community support, go to Discussions. It might also be a good idea to contract with any of contributors and maintainers if your business is so critical and therefore you need priority support
[X] I've read releasenotes before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes
[X] My actions-runner-controller version (v0.x.y) does support the feature
[X] I've already upgraded ARC (including the CRDs, see charts/actions-runner-controller/docs/UPGRADING.md for details) to the latest and it didn't fix the issue
[X] I've migrated to the workflow job webhook event (if you using webhook driven scaling)

Resource Definitions
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: samipsolutions-runners-arm64
  namespace: ci
spec:
  template:
    metadata:
      annotations:
        cluster-autoscaler.kubernetes.io/safe-to-evict: "true"
    spec:
      env:
        - name: DISABLE_RUNNER_UPDATE
          value: "true"
      image: summerwind/actions-runner-dind
      organization: samipsolutions
      affinity:
        nodeAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 1
              preference:
                matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - arm64
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  name: samipsolutions-runners-arm64
  namespace: ci
spec:
  minReplicas: 1
  maxReplicas: 10
  scaleTargetRef:
    kind: RunnerDeployment
    name: samipsolutions-runners-arm64
  scaleUpTriggers:
    - githubEvent:
        workflowJob: {}
      duration: "15m"
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: samipsolutions-runners-amd64
  namespace: ci
spec:
  template:
    metadata:
      annotations:
        cluster-autoscaler.kubernetes.io/safe-to-evict: "true"
    spec:
      env:
        - name: DISABLE_RUNNER_UPDATE
          value: "true"
      image: summerwind/actions-runner-dind
      organization: samipsolutions
      affinity:
        nodeAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 1
              preference:
                matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64
---
apiVersion: actions.summerwind.dev/v1alpha1
kind: HorizontalRunnerAutoscaler
metadata:
  name: samipsolutions-runners-amd64
  namespace: ci
spec:
  minReplicas: 1
  maxReplicas: 10
  scaleTargetRef:
    kind: RunnerDeployment
    name: samipsolutions-runners-amd64
  scaleUpTriggers:
    - githubEvent:
        workflowJob: {}
      duration: "15m"

To Reproduce
1. Create the resources
2. Setup webhook
3. Try to use an action with self-hosted label.

Describe the bug
I tried to setup runners for arm64 and x64 for org-wide, and the runners appear in Github, due to self-registration but doesn't seem to be picking up jobs.
Describe the expected behavior
I would have expected it to start working on my actions, but it doesn't seem to pick it up.
Whole Controller Logs
https://gist.githubusercontent.com/samip5/c6583ba8a6e5ccc3eadd4a487487eaa3/raw/a7d52157409d019902f117431fad7ffe830aaa3c/controller-logs.txt

Whole Runner Pod Logs
https://gist.githubusercontent.com/samip5/c6583ba8a6e5ccc3eadd4a487487eaa3/raw/a7d52157409d019902f117431fad7ffe830aaa3c/runner-logs.txt

Additional Context
My current GitOps can be seen here: https://github.com/samip5/k8s-cluster/tree/838dd6b08fb15c5410abef2756cb158c47478c77/cluster/apps/ci
Seems somewhat related to an old issue (#776).

Oh this seems to happen when your Default runner group in the org doesn't have public repos enabled, and as such no runner will see the jobs on public repos. I'm closing this myself as result.


Status change records

Is your feature request related to a problem? Please describe.
As a Program Admin, I want to have a record of when an applicant's status changed to be able to monitor and report out on how long it took for a resident to get a communication.
Describe the solution you'd like
A tabular view at the top of an application, when viewed in the web browser, of the application status, time and date it was changed, and the Program Admin who made the change.
Done when
Program Admins have a clear record of the timeline when an applicant's status changed.

record of status changes.pdf

Important for analytics / API export too!


"Protocol error communicating with device" while trying to read

Hi,
I was trying to simple try some another devices according to bug #24, and while using LightBlue Explorer on my iPhone to create Virtual Periperals I got this as a value (sic!) on .read() some of the characteristics
Protocol error communicating with device
Seemed pretty strange for me so I tried same code on macOS & noble and got proper value.
Best, JH

I don't know what might have caused the protocol error. As for why you got the error message back instead of the value... Currently whenever noble-uwp encounters an error, it returns the Error object as the result. So, you could check if the results is an instanceof Error to detect that.
That's probably not the way it should work, though I'm not sure what it should do instead. From what I can see, noble bindings for other platforms don't have consistent error-handling though. Some report errors via console.error(), and some just don't catch exceptions (so they would propagate up the stack and kill the process.


Compose

Do you guys not read your own examples? It is not clear what the compose input should be. You're saying use an array with integers but then somehow somewhere we have an array of emails? Can you provide clear examples of the inputs allowed and how they are referenced later?

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

ID: 79bddf7e-aad7-5b99-0b73-a893d25615f5
Version Independent ID: f2f0c4d6-b613-d269-4756-bcd7548f76ec
Content: Understand data operations (contains video) - Power Automate
Content Source: articles/data-operations.md
Service: power-automate
Sub-service: cloud-flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@rogerprz Thank you for your feedback. The different sections of this document use different examples to show how to use different data operations. In the compose action section (https://docs.microsoft.com/en-us/power-automate/data-operations#use-the-compose-action), it shows you how to use an array of integers. On the other hand, in the join action section (https://docs.microsoft.com/en-us/power-automate/data-operations#use-the-join-action) it shows you how to use an array of emails. I've updated the document to clarify this these sections are separate and not intended to be a full single example. Thanks for your feedback and have a great day.


Harvester refuses to die when harvesting and receiving lethal damage

Given a harvester that is in HarvestingState , when it takes damage so that it dies, it will remain in the HarvestingState before actually dying. What happens is that it will continue harvesting until the cell is harvester and then it will die.

Assign to @arjenvanderende because he likes fixing bugs! ;-)


Update to go modules

This tool is installable via brew. In order to maintain it easier when go 1.17 rolls around could the maintainers please add go modules support.
https://github.com/Homebrew/homebrew-core/issues/47627

@roopakv look at this - https://github.com/sosedoff/pgweb/pull/508

That looks promising! Thank you for making the PR :)

#509

@lelvisl awesome! please make a new release with the go modules stuff so that we can update the brew side of the world


Generate P2 update sites for core and plugins

Use https://github.com/reficio/p2-maven-plugin as a guide and generate p2 update sites for core and plugins.

Folder in repository should be called update-site

Deployment of p2 update sites will come at a later date


Missing Dockerfile in context directory for maven parent

parent:
pom.xml
    child1:
        Dockerfile
       pom.xml
        <src>
    child2:
        Dockerfile
        pom.xml
        <src>

When running mvn dockerfile:build dockerfile:push from each child, everything works as expected, but when running the same command from the parent, the fallowing error appears Failed to execute goal com.spotify:dockerfile-maven-plugin:1.3.6:build (default-cli) on project ...: Missing Dockerfile in context directory: parent
Is there a way to tell the plugin to skip maven parents as they should not be packaged in a docker container?

there are a few different approaches mentioned in #87 that might help. If you are configuring the plugin globally in the parent pom.xml then you might want to add configuration to have it skipped in the parent (i.e. not in the <pluginManagement> section)


make /seedcracker undetectable for servers

now, if you just write /seedcracker it sends to server, in my opinion it shouldn't

may be make that /seedcracker will just open gui

could be changed that anything starting with /seedcracker isnt sent to the server


PowerBI sample

Hi @arturl, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Thanks for the feedback, I addressed all comments except I2C initialization suggestion -- I'll use the old API for now, just like other samples do.

Thanks!
Artur
From: Brian Fjeldstad<EMAIL_ADDRESS>Sent: Friday, January 22, 2016 12:19
To: ms-iot/samples<EMAIL_ADDRESS>Cc: Artur Laksberg<EMAIL_ADDRESS>Subject: Re: [samples] PowerBI sample (#203)
Merged #203https://github.com/ms-iot/samples/pull/203.
—
Reply to this email directly or view it on GitHubhttps://github.com/ms-iot/samples/pull/203#event-523380675.


OSX has a limit of 256 open files

This has caused crashing issues for Mac users

Is this a problem with siad or just the UI?

It has implications for our API design. If the design encourages opening many calls open concurrently (e.g. when downloading many files), then it's a failing of our API design, not of the UI.

Ok. I will probably not leave this issue open for very long, because there's no action item associated with it. However we should definitely support non-blocking download calls in the api.

Agreed. That feature should dovetail nicely with our merged upload/download loop.

Same issue in Linux, siad rises more than 1024 file handlers

@daniel-lucio how long were you running Sia? Did you perform a specific action to hit 1024?
Trying to figure out the best way to keep this from happening in the future.
@lukechampine would the gateway have one open per peer?

Yes, I believe the current file handler sources are:

1 for the API listener
1 for each peer connection
1 for each database
1 for each host/renter connection
1 for each file being uploaded/downloaded (renter side)
1 (?) for each file being uploaded/downloaded (host side)

However, we don't need to worry about the limit when it comes to peer connections or host operations. In the rare case that you want a huge number of peers, you can manually raise the limit. And for hosts, it's expected that they will be more advanced users, so it's sufficient to document that hosting a large amount of data may require raising the limit. (Of course, minimizing the number of open file handles is still a good idea!)

I'm struggling to see how that would add up to 1024, though I could see it getting pretty close to 256 if you have the max number of peers. Perhaps we should drop the default maximum to 40.

@DavidVorick you need to know your SO. In Linux, I use the ulimit command to raise this limit. I ignore if OSX has that as well.

I could see it adding up to 1024 if you include all the other file descriptors in use on the system, not just Sia.

I had the impression that it was 256 files per process, not per machine?

Same problem on Fedora 24 with a soft limit of 1024 and hard limit of 4096 open files.
siad continues to work though.

Just investigated this a little closer, and it seems like siad is opening a ton of new sockets.
Reproduce

Start unlocking of wallet
find process id of siad (ps aux | grep siad or otherwise)
run ls -l /proc/<siad id>/fd | grep socket | wc -l

The count is about 150 to start with and then increases steadily by about 100 every few minutes. At block height 40k there are about 600 open sockets.

That is very interesting. I don't think the wallet itself is opening sockets, but once the wallet is unlocked, the renter can start trying to form/renew contracts, and each of those attempts requires a socket. Perhaps we are leaking those somehow.

Seems more likely to me that bolt is not cleaning up the file handles very well, I'm guessing it opens a separate socket for each call to db.Read and then eventually cleans them all up.

AFAIK bolt doesn't use sockets, just mmap. We could (sort of) confirm this by examining socket use after deleting something like hostdb.json and restarting.
@RNabel, any chance you can use a tool like ss to find out more about the socket connections? Ideally we'd be able to capture some of the data sent. That would tell us what code is responsible for opening the sockets.

@lukechampine Sure thing. I'll play around with this over the weekend and report back.

Alright, I ran through the above steps again (this time with said v1.1.2) and could not replicate this behavior anymore - could it be fixed by the latest update?

Were you using v1.1.0 before? It's possible that most of those sockets were created by the HostDB, which got a pretty big upgrade in v1.1.1.
I'm going to leave this open because I'm not convinced that the problem has been resolved, but if nobody can replicate it as of the most recent master branch, I guess we did something to fix it accidentally.
We have been in general working on improving our resource management.

I'm pretty sure that I was using v1.1.1. In any case, tried again and can't reproduce the error.

Closing for now, feel free to reopen if this issue presents itself again.


New circular primitives: Arc2d, CircularSector, CircularSegment

Objective
There are no 2d primitives available for the common shapes of an arc or a circular sector (pie slice).
Solution
This PR introduces three new types to the existing math primitives:

Arc2d: a portion of a (hollow) circle
CircularSector: the area between an arc and the centre of the circle
CircularSegment: the convex hull of an arc

Run cargo run --example 2d_shapes to see examples of the CircularSector and CircularSegment type.
Design decisions

What should the arc type be named?
Answer: Arc2d, because Arc is already taken by the standard library.

What should the origin point of these shapes be?

The origin point is the point around which the shape rotates, among other things.
For an arc and a circular sector, it's intuitive I think that the origin be the center of the corresponding circle.
But for a circular segment, I think the origin being the center of the chord is more intuitive, because it is easier to reason about rotation math that way.
On the other hand, consistency between the three shapes has value.

Answer: This PR puts the origin of all three shapes in the center, prioritizing consistency,

What should the UV-mapping of CircularSector and CircularSegment look like? There are two reasonable options:

Treat the shapes as masks of the corresponding circle. Good for animating the texture, or cutting a single circular texture into pieces e.g. pizza slices.
Map the shape's bounding box onto the texture. Good when the slice size is fixed and not going to change, to be maximally efficient with the texture space.

Answer: This PR chooses option 1 as the default, but puts UV-mapping configuration in a CircularMeshUvMode enum, as futureproofing for later adding option 2.

How should the angle of these shapes be expressed?

Follow mathematical conventions of starting from the right and going counterclockwise.
Start from the top and extend by half the angle on either side.

Answer: This PR chooses option 2, because it leads to better defaults and better ergonomics when reasoning about how to rotate the shape.

TODO

[x] Add convenience methods on CircularSector and CircularSegment that avoid needing to explicitly access the arc field.
[x] Add examples that make use of textures, to verify that the UV mappings are correct.
[x] Add testing, particularly of the shape math. (I've already caught at least one bug and there are probably more.)

Future Work
For after this PR is merged:

Add support for these shapes to Gizmos as in #11072.
Add support for the alternative UV mode discussed above, as a configurable option on the MeshBuilder types.
Integrate these shapes into the new math/primitives example.

Changelog

Added Arc2d, CircularSector, and CircularSegment primitives to [bevy::math::primitives].

Thanks for the review! I've made the changes plus a few more things. I'll update the first comment to reflect the current state of things.

I've now updated the PR and got it as close to working as I can, but #12729 is preventing all tests from passing and I can't figure out a fix locally.

There also seems to be a failing wasm build that isn't related to my PR.

That has been fixed #12730

@spectria-limina I'm happy to merge this as is: let me know if you're able to resolve merge conflicts?


Revert 1 marleyjustin08 patch 1

Why:

What's being changed:

Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

This PR appears blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!


Flattened documents will not print using Adobe products

Issue: A flattened PDF using the form.flatten() method will not print using Adobe Acrobat Reader or Adobe Pro. (Both macOS and Windows 10)
No Page Selected error
PDF Expert, Preview and other readers are unaffected.
Fix: remove flatten method.
Note: Setting the fields as read only works fine and the document will print.
fields.forEach(f => f.enableReadOnly())

The issue has been fixed, it's just it has not been released yet.
cc @Hopding

The issue has been fixed, it's just it has not been released yet.
cc @Hopding

Thanks for the update!  Will keep an eye out.

Thanks for the update!  Will keep an eye out.

Found this thread while researching a similar issue - upgrading from 1.14.x to 1.16 resolved for me!

See: https://github.com/Hopding/pdf-lib/issues/800#issuecomment-981404466


COWArrayOpts: make the optimization work again for two-dimensional arrays.

With removing of pinning and with addressors, the pattern matching did not work anymore.
The good thing is that the SIL is now much simpler and we can handle the 2D case without pattern matching at all.
This removes a lot of code from COWArrayOpts.
rdar://problem/43863081

Build failed
Swift Test Linux Platform
Git Sha -<PHONE_NUMBER>b2e70db01190dbd4d0b799d73a324c

Build comment file:
Performance: -O

TEST
OLD
NEW
DELTA
RATIO

Regression

IterateData
1615
1778
+10.1%
0.91x (?)

Improvement

Array2D
12296
6907
-43.8%
1.78x

Walsh
398
352
-11.6%
1.13x

Code size: -O

TEST
OLD
NEW
DELTA
RATIO

Improvement

RandomShuffle.o
3856
3521
-8.7%
1.10x

Array2D.o
4320
4000
-7.4%
1.08x

RC4.o
5231
5023
-4.0%
1.04x

Walsh.o
9544
9336
-2.2%
1.02x

Performance: -Osize

TEST
OLD
NEW
DELTA
RATIO

Regression

IterateData
1589
1798
+13.2%
0.88x (?)

Improvement

Array2D
11998
6909
-42.4%
1.74x

Walsh
967
884
-8.6%
1.09x

Code size: -Osize

TEST
OLD
NEW
DELTA
RATIO

Improvement

RandomShuffle.o
3815
3735
-2.1%
1.02x

Array2D.o
4243
4163
-1.9%
1.02x

Performance: -Onone

TEST
OLD
NEW
DELTA
RATIO

Regression

ObjectiveCBridgeStubDateMutation
743
800
+7.7%
0.93x

Code size: Swift libraries

TEST
OLD
NEW
DELTA
RATIO

Improvement

libswiftSwiftOnoneSupport.dylib
221184
217088
-1.9%
1.02x

How to read the data
The tables contain differences in performance which are larger than 8% and differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false alarms. Unexpected regressions which are marked with '(?)' are probably noise. If you see regressions which you cannot explain you can try to run the benchmarks again. If regressions still show up, please consult with the performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test

LGTM. I agree with Arnold that's it's nice to have SIL tests whenever there's a fair amount of extra complexity in the pass to handle that SIL.

The 2d tests start at 'sil @hoist_array2d'

They should (more or less) test all the extra logic which I added (which was not much)

@swift-ci smoke test OS X platform

@swift-ci smoke test OS X platform


broken entity code generated using with mysql datatype 'set'

@Column("set",{
    nullable:false,
    name:"flag"
    })
flag:;   //illegal syntax here in this line will cause tsc stop

fa_category.ts(54,10): error TS1110: Type expected

Could you provide DDL statements to reproduce the issue?

create table fruit(names set('apple','bananna','grape'));

https://github.com/Kononnable/typeorm-model-generator/issues/91

Duplicate of #91, lets keep this in one issue.


Term merge: [regulation of nucleosome density (GO:0060303)]

Term to be merged: Provide GO ID and term label
regulation of nucleosome density (GO:0060303)
Which term do you propose this term merge into? Provide GO ID and term label
nucleosome organization,
although some  annotation might be better as "nucleosome positioning" or nucleosome assembly/disassembly so perhaps obsoletion is better?
Reason for merge
but regulation of  nucleosome density is more of an observation (change in nucleosome positions) than a process
Any other information
I requested this term, back in the day, it seems very phenotype-y (these are 'affecting nucleosome density')
https://github.com/geneontology/go-ontology/issues/5189
but no longer use it for the publication it was requested for
https://www.pombase.org/reference/PMID:17446861
Most of the  EXP annotations are PomBase 20/30
others
SGD 8
FlyBAse 1
Agbase 1
@colinlog  does this sound OK to you?

Dear Val, Pascale and the other readers,
From a process-centric view, there is the nucleosome level and the polynucleosome array level (the 'real' stuff eukaryotic nuclear chromatin is made of). Both are part of the process chromatin organization. These processes are driven by activities that are often enzymes (ATPases, histone modifiers) but can be 'binders/readers' of the (poly-)nucleosome.

Nucleosome level:

Post- or co-replication nucleosome (dis)assembly (product is histone octamer with 147 bp of DNA)
Post or co-transcriptional (dis)assembly, which is itself part of transcription initiation, promoter escape or transcription elongation
Mono-nucleosome remodelling which is itself to be subdivided into

moving the nucleosome along the DNA (ATP-dependent activity). At gene enhancers, silencers and promoters but also inside transcribed regions to modulate splicing or transcription termination and probably also for DNA replication, repair and recombination as well as (sister-)chromatid cohesion, extrusion.
changing the nucleosome by replacing a canonical H2A, H2B or H3 histone (there no H4 variants known??) with a variant isoform (H2A.Z and other H2A variants, H3.3, CENP-A). Here there isalso a distinction between single histone insertion (SWR1 ATPase) or H2A-H2B dimer exchange.
post-translational modification of histones, sometime in the nucleosome, sometimes when the histone is in the cytoplasm or nucleosoplasm. There are more than 250 of these histone modifications. This may also include histone tail clipping.

Polynucleosome level:

Chromatin folding processes (eg H416ac is known to strongly modulate chromatin compaction at the 'inter-nucleosoma' contact level)

polynucleosome 30 nm fibre topology modulation one-start and two-start fibres (two-start is apparently the most common !!! and affected by many chromatin-binding proteins)
Nucleosome spacing (the activities are known and are ISWI or CHD ATPase enzyme activities) that makes nucleosomal arrays with rather precise linker lengths between adjacent nucleosomes that then have specific folding options.

polynucleosome binding via protein and/or(methylated) DNA binding leading to specific polynucleosome topologies that are stabilized into euchromatin or heterochromatin conformations.

Despite the appearances, the above may not be comprehensive. Rather, it is a minimum. My thoughts are that we should refactor this part of the ontology holistically and straight away organise the BPs hierarchically, with MFs that underlie them. The logic being that MFs are protein activity-centric while the processes should be process product-centered.
All this to say that it may be most effective to consider the whole matter of chromatin organization of rather than tinkering/obsoleting with individual terms and merging them with an upper term, which would overly simplify the GO and render future annotation options ambiguous.

I removed the PomBase annotations to prevent propagation. These were just a phenotype, and they all had more informative annotations. Introducing a "regulation of quality" term (i.e. density), doesn't seem to be helpful.
So I'll add 'transcription' and 'low priority' labels

Dear all,
The proposal has been made to obsolete GO:0060303 regulation of nucleosome density. The reason for obsoletion is that this represents a readout and in some cases a phenotype, and the term can be misconstrued for chromatin compaction.
There are 11 EXP annotations: https://docs.google.com/spreadsheets/d/1HV2nb-8U7b8b9b85pmcCF9m3Uw3z1zMPSTOknPwVLc4/edit#gid=0
1 FlyBase
9 SGD
Suggestions for reannotations have been made, including to a new term 'GO:0140750 nucleosome array spacer activity'.
There are no mappings; this term is not present in any subsets.
You can comment on the ticket: https://github.com/geneontology/go-ontology/issues/21503
Thanks, Pascale


semantically named derived colors, theme ultimate timeline

This adds basic theming for the Ultimate Timeline userscript.
It also creates some semantically named derived colors for you to use at the top. This should make things more readable/understandable throughout.
Lastly, note that the Ultimate timeline also creates some custom props for colors. This makes things really easy to tinker with consistently.

Here's an example of what the timeline looks like themed.

Looks like we have been chipping on the same thing. I just pushed out styling for the ultimate timeline

But I will definetly check out your solution as it seems more compact as well as take a look at the updated color solution

No worries! Use whatever makes the most sense to you.
Please do take a look at how I redefined the custom-props in my version. I think you'll quickly grok why props based on props make things easier to maintain (while remaining consistent). That pattern is showing up everywhere these days.


Integrate default config into demo pak

This will help us distribute the default configs with our binaries, so we don't have to do an extra step of copying configs to ~/.tyrquake/id1/

unpak the files in id1/
modify the default.cfg
repak if necessary

The python tool UnPak seems to omit some files.  Will try [PakExplorer](http://www.quaketerminus.com/tools/pakexplr.zip on windows.

Mac/Linux will read from game/id1/config.cfg if there is no ~/.tyrquake/id1/config.cfg.  So creating the former will work for first time installs, assuming they don't have tyrquake.  Should probably change the .tyrquake name to .blinky

changed .tyrquake to .blinky


RDO of transform size for intra block

Enabled for speed <= 2, i.e. when fi.config.speed_settings.rdo_tx_decision == true
&& INTRA frame only.
TODO: Currently, only works partition depth == 1, plan to fix for max depth 2 in a separate patch.

Coverage increased (+0.2%) to 82.357% when pulling 1114e54b812e17372eafede4df20e5581094c10a on ycho:rdo_intra_tx_size into 904cfa2d19d08cdf0073ebb1a7a58068e5db6617 on xiph:master.

AWCY result for speed 2

PSNR
PSNR Cb
PSNR Cr
PSNR HVS
SSIM
MS SSIM
CIEDE 2000

-1.3858
-1.1944
-0.8549
-0.9902
-1.3141
-0.9488
-1.1913

For speed levels (3~10) that does not use tx partition, encode tx_mode_select = false in frame header. Because if tx_mode_select is true in frame header then each block signals 'no partition' which causes loss in coding efficiency.


Import from CSV not getting all rows

Description
Similar to #14227 I have a CSV with 30354 entries. When uploading it to my Postgres database using DBeaver only 15781 entries are uploaded. And it is always the same amount for every run I try.
DBeaver Version
Community Edition 24.1.0
Operating System
macOS Ventura 13.6.1
Database and driver
PostgreSQL 12.5
PostgreSQL JDBC Driver
Steps to reproduce
No response
Additional context
No response

Similar discussion https://github.com/orgs/dbeaver/discussions/35154

Strangely, a second CSV with more entries (40942) is uploaded correctly. So whether it has to do with the CSV itself or there is a specific range of rows that causes this issue. The process planer also just considers the 15781 rows and stop there (even though I set the batch limit to 50000).

Hi, if possible,  could you provide a similar example of row 15782 data.

Please send us log files. You can collect them to archive automatically with Help->Collect Diagnostic Info

Seems this issue is stale. Let me know if the problem is still actual for you and provide requested log files. You can find instructions here https://dbeaver.com/docs/wiki/Log-files/.


🐞 WithMounted{File,Directory,Cache,Secret,Temp} don't allow setting arbitrary uid/gid

What is the issue?
WithMounted{File,Directory,Cache,Secret,Temp} operations are currently assigning root:root permissions inside the containers which makes any pipeline that doesn't use a root user fail.
Log output
#3 test
#3 0.147 uid=1000(foo) gid=1000(foo)
#3 DONE 0.3s

#3 test
0
#3 0.147 -rw-rw-r--    1 root     root            12 Mar  9 14:25 message.txt

As you can see from the repro steps, message.txt gets mounted as root even though current user is foo
Steps to reproduce
func main() {
	ctx := context.Background()
	client, err := dagger.Connect(ctx, dagger.WithLogOutput(os.Stderr))
	if err != nil {
		panic(err)
	}
	defer client.Close()

	msgFile := client.Host().Workdir().File("message.txt")
	output, err := client.Pipeline("test").
		Container().
		From("alpine").
		WithExec([]string{"adduser", "-D", "foo"}).
		WithUser("foo").
		WithMountedFile("message.txt", msgFile).
		WithExec([]string{"id"}).
		WithExec([]string{"ls", "-la", "message.txt"}).
		ExitCode(ctx)
	if err != nil {
		panic(err)
	}
	fmt.Println(output)
}

SDK version
Go v0.5.0
OS version
Linux xps 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

related issue regarding secrets: https://github.com/dagger/dagger/issues/3323

talked with @vito, and he will take a look at this one.

We were speaking with @grouville on Friday that this should also take into consideration withFile, withDirectory, withNewFile, etc

Proposal: for File and Directory we can add withOwners(uid: Int, gid: Int) which seems to fit naturally alongside with withTimestamps(timestamp: Int).
extend type Directory {
  withOwners(uid: Int, gid: Int): Directory!
}

extend type File {
  withOwners(uid: Int, gid: Int): File!
}

For caches + secrets + sockets we can add mount options:
type Container {
  withMountedCache(..., uid: Int, gid: Int): Container!
  withMountedSecret(..., uid: Int, gid: Int): Container!
  withUnixSocket(..., uid: Int, gid: Int): Container!
}

Not sure about withMountedTemp yet.

Proposal: for File and Directory we can add withOwners(uid: Int, gid: Int) which seems to fit naturally alongside with withTimestamps(timestamp: Int) (chown vs chtimes).

+1. One thing that brings my attention is that {Container, Directory}.WithNewFile and Directory.WithNewDirectory API's have the permissions (chmod) option as a field argument. Would it be possible to consolidate?

For caches + secrets + sockets we can add mount options:

SGTM here!

For caches + secrets + sockets we can add mount options:

I just realized we could technically make the same API change for these, it just feels a little odd for some reason:
extend type CacheVolume {
  withOwners(uid: Int, gid: Int): CacheVolume!
}

extend type Secret {
  withOwners(uid: Int, gid: Int): Secret!
}

extend type Socket {
  withOwners(uid: Int, gid: Int): Socket!
}

I think this feels weird because these three aren't so strictly tied to the idea of filesystems/permissions/etc. compared to files and directories. For example, Secret { withOwners } is pointless if the secret is only ever passed as an env var instead.
Right now I'm leaning towards sticking to mount options instead, just farming for dissent.
Arguably even File/Directory should be mount-time because the value is influenced by the running context (valid UID in container), as opposed to withTimestamps which applies to the object itself. In fact, there might be a way to support usernames instead of user IDS which seems like a major DX win.
Hmm...

Right now I'm leaning towards sticking to mount options instead, just farming for dissent.

yep, sharing the same feeling about this.

Arguably even File/Directory should be mount-time because the value is influenced by the running context (valid UID in container), as opposed to withTimestamps which applies to the object itself.

True. Another reason to add these as query arguments I guess?

In fact, there might be a way to support user_names_ instead of user IDS which seems like a major DX win.

yep, that'd be great. IIRC Dockerfiles have the same DX as well for --chown. I don't think it works for mounts though

True. Another reason to add these as query arguments I guess?

:+1:

yep, that'd be great. IIRC Dockerfiles have the same DX as well for --chown. I don't think it works for mounts though

It looks like this is easy (ish) for mounting files/directories. You can just use llb.WithUser("foo:foo") as long as the base of the llb.Copy operation stems from the filesystem. It'll resolve those names to IDs by looking at /etc/passwd on its own.
It seems a lot harder for secrets/sockets/caches. We'll have to manually load up /etc/passwd and /etc/group and resolve names to UIDs in that case. I'll try to implement it anyway, it's definitely a lot nicer to be able to use names everywhere rather than guess or print the ID beforehand.

Do we want container mounts to inherit the container's configured user by default? That seems to be the crux of the original report, but the title mentions explicitly configuring it.
I started implementing it, but it adds a bit of overhead (a copy + chmod for every mount), and I wonder if it's too surprising. For example maybe you want to keep ownership as-is when passing data from one container to another. I'm not sure when you would want to do that, and users in one container might not be present with the same ID in another, but sometimes it matters.

If we pass withMountedFile with foo:foo, what would be the expected behavior?
Do we check in the host /etc/passwd to transform this foo:foo into the host uid:gid? Or do we check in the /etc/passwd  in the container this file is mounted into?
What if we don't find it (in any of both cases), do we fall down to the default user (on host, that would be the user running the pipeline, on the container, it would be image's default)? Or do we fail with an error telling the mapping could not be found?

Do we check in the host /etc/passwd to transform this foo:foo into the host uid:gid? Or do we check in the /etc/passwd in the container this file is mounted into?

The latter

What if we don't find it (in any of both cases), do we fall down to the default user (on host, that would be the user running the pipeline, on the container, it would be image's default)? Or do we fail with an error telling the mapping could not be found?

The latter again, but now that you mention it, I'll add an explicit test :+1:

There's a sneaky interaction here with WithTimestamps, and file timestamps in general: chown is technically a write, so it bumps the timestamps, causing this test to fail:
func TestFileWithTimestamps(t *testing.T) {
	c, ctx := connect(t)
	defer c.Close()

	reallyImportantTime := time.Date(1985, 10, 26, 8, 15, 0, 0, time.UTC)

	file := c.Directory().
		WithNewFile("sub-dir/sub-file", "sub-content").
		File("sub-dir/sub-file").
		WithTimestamps(int(reallyImportantTime.Unix()))

	ls, err := c.Container().
		From("alpine:3.16.2").
		WithMountedFile("/file", file).
		WithEnvVariable("RANDOM", identity.NewID()).
		WithExec([]string{"stat", "/file"}).
		Stdout(ctx)
	require.NoError(t, err)
	require.Contains(t, ls, "Access: 1985-10-26 08:15:00.000000000 +0000")
	require.Contains(t, ls, "Modify: 1985-10-26 08:15:00.000000000 +0000")
}

Seems like more evidence that we shouldn't automatically chown things. If it's opt-in, you can at least mount + chown and then fetch that directory back out and apply WithTimestamps to it.

Somehow the above test is passing in CI. :thinking:
The only reason I can think of is that the file is already chowned to 0:0 and somehow Buildkit does a no-op, but I don't know why that wouldn't apply to my local machine:
❯ gotestsum ./core/integration/ -skip RemoteCache
[core/integration]······························································································································✖···············································································································································································································································
=== Failed
=== FAIL: core/integration TestFileWithTimestamps (2.95s)
#1 resolve image config for docker.io/library/alpine:3.16.2
#1 DONE 0.2s

#2 importing cache manifest from dagger:10686922502337221602
#2 DONE 0.0s

#3
#3 CACHED

#4 chown /file to 0:0
#4 CACHED

#5 from alpine:3.16.2
#5 resolve docker.io/library/alpine:3.16.2 0.1s done
#5 CACHED

#6
#6 0.124   File: /file
#6 0.124   Size: 11        	Blocks: 8          IO Block: 4096   regular file
#6 0.124 Device: 8ah/138d	Inode: 55974303    Links: 1
#6 0.124 Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
#6 0.124 Access: 2023-04-12 21:24:19.616862545 +0000
#6 0.124 Modify: 2023-04-12 21:24:19.616862545 +0000
#6 0.124 Change: 2023-04-13 19:51:53.191900704 +0000
#6 DONE 0.2s
    file_test.go:192:
        	Error Trace:	/home/vito/src/dagger/core/integration/file_test.go:192
        	Error:      	"  File: /file\n  Size: 11        \tBlocks: 8          IO Block: 4096   regular file\nDevice: 8ah/138d\tInode: 55974303    Links: 1\nAccess: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)\nAccess: 2023-04-12 21:24:19.616862545 +0000\nModify: 2023-04-12 21:24:19.616862545 +0000\nChange: 2023-04-13 19:51:53.191900704 +0000\n" does not contain "Access: 1985-10-26 08:15:00.000000000 +0000"
        	Test:       	TestFileWithTimestamps

DONE 366 tests, 1 failure in 276.621s

I noticed the dates above looked a little funny, so I pruned the Buildkit cache and re-ran and sure enough, it passes:
=== RUN   TestFileWithTimestamps
#1 resolve image config for docker.io/library/alpine:3.16.2
#1 DONE 0.2s

#2 importing cache manifest from dagger:10686922502337221602
#2 DONE 0.0s

#3
#3 CACHED

#4
#4 DONE 0.0s

#5 from alpine:3.16.2
#5 resolve docker.io/library/alpine:3.16.2 0.1s done
#5 DONE 0.1s

#6 chown /file to 0:0
#6 ...

#5 from alpine:3.16.2
#5 CACHED

#4
#4 0.125   File: /file
#4 0.125   Size: 11        	Blocks: 8          IO Block: 4096   regular file
#4 0.125 Device: 8ah/138d	Inode: 59113495    Links: 1
#4 0.125 Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
#4 0.125 Access: 1985-10-26 08:15:00.000000000 +0000
#4 0.125 Modify: 1985-10-26 08:15:00.000000000 +0000
#4 0.125 Change: 2023-04-14 20:52:16.330798492 +0000
#4 DONE 0.2s

#6 chown /file to 0:0
--- PASS: TestFileWithTimestamps (2.61s)

No idea why this would happen.

Do we want container mounts to inherit the container's configured user by default? That seems to be the crux of the original report, but the title mentions explicitly configuring it.

I would personally find it pretty surprising. Even though it adds some verbosity to the pipeline, having a magical inheritance of the uid/gid might become confusing. WDYT @helderco ?


chore: release 1.2.327

:robot: I have created a release *beep* *boop*
1.2.327 (2024-08-13)
Bug Fixes

build, buildah, stapel: prevent sensitive data exposure by not printing user commands (69d26bb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.327 :sunflower:


PropertySortOrder: Allow JSON file to be used for sort order

I'm using PropertySortOrder linter to validate property ordering for my existing scss. Since I don't want to re-order all the properties by hand, I'm using csscomb.js to do it for me automatically.
I'm using one of the csscomb preset files, but my problem is that scss_lint and csscomb use totally different formats to specify property ordering.
My feature request is to add a new option to PropertySortOrder where I can have sort order in a JSON file and have css_lint read it. That way importing sort order rules from csscomb will be really easy (more or less copy/paste).
Of course in the best case for me, I could pass my .csscomb.json file to PropertySortOrder and it would read the ordering from there.
Using JSON would also enable scss_lints ordering files to be compatible / easily converted to use with csscomb.

I don't think it makes sense for scss-lint to support an arbitrary format used by a third-party tool. That introduces an unnecessary coupling (any changes to that format will break scss-lint lint).
You can easily convert csscomb's preset format to an scss-lint-compatible one with the following short script:
require 'json'
require 'yaml'

json = JSON.parse(File.read('zen.json'))

puts({
  'linters' => {
    'PropertySortOrder' => {
      'order' => json['sort-order'].flatten,
    }
  }
}.to_yaml)

You can modify this to insert nil between the groups if you would like that.
Converting from an scss-lint preset order to JSON:
require 'json'

order = []
current = []

File.foreach('concentric.txt')
    .reject { |line| line.start_with?('#') }
    .each do |line|
  if line.strip.empty?
    if current.any?
      order << current
      current = []
    end
  else
    current << line.strip
  end
end

if current.any?
  order << current
end

puts JSON.pretty_generate(
  'sort-order' => order
)

If csscomb supported a JSON format that didn't have any keys (i.e. was just the array of arrays format under the sort-order key) I would be more open to considering this. Happy to hear your thoughts.

Thanks for the scripts! This is exactly one part of the problem I have. Since scss-lint is Ruby based, I'm not able to easily write scripts like you just did. Could you consider to include those scripts to the repo, readme, wiki, etc. so that those are available to someone else that has the same problem?
Also, csscomb is not just any tool because it can quite powerful when used together with scss-lint (first apply linting, then comb the code using shared settings). It is too bad that open source library authors often overlook the benefits that their tool can bring when used together with another library. For example, would be nice to see these two projects sharing their property order configurations (the order, not the format).

I don't think it makes sense for scss-lint to support an arbitrary format used by a third-party tool. That introduces an unnecessary coupling (any changes to that format will break scss-lint).

Yes absolutely not, my request was mainly for supporting JSON in general, but having something that would support csscomb out of the box would have been a plus.
Supporting a third party format does not mean that you have to create coupling. IMO the correct way of implementing something like that would be a plugin system that would enable any format to be supported. Look at PostCSS for example, with its plugin based architecture it can support almost any kind of tool/format. But anyway, these were just my 2 cents on how to support something without creating coupling.

Thanks for your thoughts, @kristerkari.
I'm happy to say that scss-lint supports plugins as of #440, so it sounds like the feature you are looking for is supportable if someone is willing to take on the responsibility of maintaining the plugin.
@brigade can't take on the task of maintaining all of these different integrations (we aren't experts with every toolset—no one is). Hopefully someone from the community will step up and and make those plugins a reality if the need for them is real.

Thanks! Sounds awesome.

@brigade can't take on the task of maintaining all of these different integrations (we aren't experts with every toolset—no one is). Hopefully someone from the community will step up and and make those plugins a reality if the need for them is real.

If you again look at PostCSS as an example, you can see that it is successful because of good documentation, guidelines, api docs, faq and community. Also the guy behind PostCSS goes around and gives conference talks about PostCSS. It is not easy, but it is doable.


Why is python3-babel in AppStream

Hello, could you please help me understand why is this package in AppStream?
https://tiny.distro.builders/view-rpm--view-eln--python3-babel.html
It is runtime-required by 3 packages - 2 are in buildroot and one is in CRB.
We maintain this package as a CRB-only dependency of Sphinx (also CRB-only). We do not wish to maintain it in AppStream, but we do not know who should own it there. Based on the visible data, this should also be in CRB-only.
Thanks.

Not answering, just providing context: Content Resolver doesn't compute the repos, it just shows where the pacakges are right now. And that's set in a Pungi config (likely the prepopulate.json) somewhere. (So whoever set it will need to answer your question, but it's not computed in CR.)

On c9s, python3-babel is pulled into AppStream by python3-jinja2. However, that runtime dependency no longer exists in the current ELN version of python3-jinja2.
Should I open a PR that changes prepopulate.json?

Yes, please submit an MR to fix prepopulate.json. We're trying to find a less unwieldy way to manage the repo split, but this is the best we have at the moment.

https://pagure.io/pungi-fedora/pull-request/1211


Can't import demo page preset with PostgreSQL 16

Link to reproduction
No response
Describe the Bug
When trying to create a fresh installation of the payload app with the demo page preset it can't import/seed the postgresql database.
To Reproduce

pnpx create-payload-app@latest .
Select the  payload-demo project template
Select  PostgreSQL (beta) database
Input a valid PostgreSQL connection string
Since I used pnpm as a package manager I replaced all occurrences of yarn to pnpm in my package.json
Execute pnpm run build

This will lead to the following output/error:
~/payload» pnpm run build                                                                                [16:46:47]

><EMAIL_ADDRESS>build /my/absolute/path/payload
> cross-env NODE_ENV=production pnpm build:payload && pnpm build:server && pnpm copyfiles && pnpm build:next

><EMAIL_ADDRESS>build:payload /my/absolute/path/payload
> cross-env PAYLOAD_CONFIG_PATH=src/payload/payload.config.ts payload build

><EMAIL_ADDRESS>build:server /my/absolute/path/payload
> tsc --project tsconfig.server.json

><EMAIL_ADDRESS>copyfiles /my/absolute/path/payload
> copyfiles -u 1 "src/**/*.{html,css,scss,ttf,woff,woff2,eot,svg,jpg,png}" dist/

><EMAIL_ADDRESS>build:next /my/absolute/path/payload
> cross-env PAYLOAD_CONFIG_PATH=dist/payload/payload.config.js NEXT_BUILD=true node dist/server.js

[16:47:08] INFO (payload): Starting Payload...
[16:47:08] INFO (payload): Payload Admin URL: http://localhost:3000/admin
[16:47:08] INFO (payload): Seeding database...
[16:47:08] INFO (payload): — Clearing media...
[16:47:08] INFO (payload): — Clearing collections and globals...
[16:47:09] INFO (payload): — Seeding demo author and user...
error: invalid input syntax for type timestamp with time zone: ""
    at /my/absolute/path/payload/node_modules/.pnpm/pg@8.11.3/node_modules/pg/lib/client.js:526:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /my/absolute/path/payload/node_modules/.pnpm/drizzle-orm@0.29.3_@libsql+client@0.3.6_@types+react@18.3.3_pg@8.11.3_react@18.3.1/node_modules/drizzle-orm/node-postgres/session.cjs:81:22
    at async upsertRow (/my/absolute/path/payload/node_modules/.pnpm/@payloadcms+db-postgres@0.8.5_@types+react@18.3.3_payload@2.23.1_@swc+helpers@0.5.5_@types+re_7ynksvd3t6jkdwjm2ejrkjmp2i/node_modules/@payloadcms/db-postgres/dist/upsertRow/index.js:49:29)
    at async Object.create (/my/absolute/path/payload/node_modules/.pnpm/@payloadcms+db-postgres@0.8.5_@types+react@18.3.3_payload@2.23.1_@swc+helpers@0.5.5_@types+re_7ynksvd3t6jkdwjm2ejrkjmp2i/node_modules/@payloadcms/db-postgres/dist/create.js:22:20)
    at async create (/my/absolute/path/payload/node_modules/.pnpm/payload@2.23.1_@swc+helpers@0.5.5_@types+react@18.3.3_esbuild@0.19.12_typescript@5.2.2_webpac_4ctwszy5cpauz6kb5e4zmf335y/node_modules/payload/dist/collections/operations/create.js:169:19) {
  length: 158,
  severity: 'ERROR',
  code: '22007',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: "unnamed portal parameter $4 = ''",
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'datetime.c',
  line: '4015',
  routine: 'DateTimeParseError'
}
  ▲ Next.js 14.2.4
  - Environments: .env

[16:47:10] INFO (payload): — Seeding media...
[16:47:10] ERROR (payload): Error seeding database.

I am on PostgreSQL 16.3 and NodeJS 20.15.0
Payload Version
2.23.1
Adapters and Plugins
db-postgres

Are there any workarounds?

Payload should handle converting dates for you. There may have been a regression in the recent db work made to get ready to release sqlite.
A workaround is to send any dates as string by calling .toISOString().

Try to update node and npm to latest version

So I retried everything again with Node 20.18.0 / NPM 10.8.2  and PostgreSQL 17 and still get the same error on npm run build
I created a fresh payload demo app with npx create-payload-app@latest and gave it a valid PostgreSQL connection string
I am on payload 2.30.3
payload➜~/httpdocs/payload-test» npm run build                                                                                [22:27:14]

><EMAIL_ADDRESS>build
> cross-env NODE_ENV=production yarn build:payload && yarn build:server && yarn copyfiles && yarn build:next

yarn run v1.22.22
$ cross-env PAYLOAD_CONFIG_PATH=src/payload/payload.config.ts payload build
Done in 27.91s.
yarn run v1.22.22
$ tsc --project tsconfig.server.json
Done in 6.64s.
yarn run v1.22.22
$ copyfiles -u 1 "src/**/*.{html,css,scss,ttf,woff,woff2,eot,svg,jpg,png}" dist/
Done in 0.38s.
yarn run v1.22.22
$ cross-env PAYLOAD_CONFIG_PATH=dist/payload/payload.config.js NEXT_BUILD=true node dist/server.js
[✓] Pulling schema from database...
[22:27:55] INFO (payload): Starting Payload...
[22:27:56] INFO (payload): Payload Admin URL: http://localhost:3010/admin
[22:27:56] INFO (payload): Seeding database...
[22:27:56] INFO (payload): — Clearing media...
[22:27:56] INFO (payload): — Clearing collections and globals...
[22:27:56] INFO (payload): — Seeding demo author and user...
[22:27:58] INFO (payload): — Seeding media...
error: invalid input syntax for type timestamp with time zone: ""
    at /var/www/pfiff.me/payload/httpdocs/payload-test/node_modules/pg/lib/client.js:526:17
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /var/www/pfiff.me/payload/httpdocs/payload-test/node_modules/drizzle-orm/node-postgres/session.cjs:82:22
    at async upsertRow (/var/www/pfiff.me/payload/httpdocs/payload-test/node_modules/@payloadcms/db-postgres/dist/upsertRow/index.js:49:29)
    at async Object.create (/var/www/pfiff.me/payload/httpdocs/payload-test/node_modules/@payloadcms/db-postgres/dist/create.js:22:20)
    at async create (/var/www/pfiff.me/payload/httpdocs/payload-test/node_modules/payload/dist/collections/operations/create.js:177:23) {
  length: 158,
  severity: 'ERROR',
  code: '22007',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: "unnamed portal parameter $4 = ''",
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'datetime.c',
  line: '4140',
  routine: 'DateTimeParseError'
}
[22:27:58] ERROR (payload): Error seeding database.
[22:27:58] INFO (payload): Next.js is now building...
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry

  ▲ Next.js 14.2.16
  - Environments: .env

   Creating an optimized production build ...
webpack built 3fce5c6b17554a951d1a in 28166ms
ERROR in ./dist/payload/cron/reset.js 159:27-40
Module not found: Error: Can't resolve 'fs' in '/var/www/pfiff.me/payload/httpdocs/payload-test/dist/payload/cron'

webpack compiled with 1 error
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: No serializer registered for RawSource
 ✓ Compiled successfully
   Skipping linting
 ✓ Checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (19/19)
 ✓ Collecting build traces
 ✓ Finalizing page optimization

Route (app)                              Size     First Load JS
┌ ƒ /                                    1.13 kB         132 kB
├ ƒ /_not-found                          873 B          88.1 kB
├ ● /[slug]                              1.13 kB         132 kB
├ ƒ /account                             3.35 kB         105 kB
├ ƒ /api/exit-preview                    0 B                0 B
├ ƒ /api/preview                         0 B                0 B
├ ƒ /api/revalidate                      0 B                0 B
├ ƒ /login                               3.11 kB         105 kB
├ ƒ /logout                              1.42 kB        95.5 kB
├ ● /posts/[slug]                        3.17 kB         134 kB
├ ● /projects/[slug]                     1.45 kB         132 kB
├ ƒ /recover-password                    2.16 kB         104 kB
├ ƒ /reset-password                      2.71 kB         105 kB
├ ƒ /styleguide                          310 B          94.4 kB
├ ƒ /styleguide/buttons                  863 B          94.9 kB
├ ƒ /styleguide/call-to-action           1.09 kB        95.2 kB
├ ƒ /styleguide/content-block            1.12 kB        95.2 kB
├ ƒ /styleguide/media-block              1.84 kB         101 kB
├ ƒ /styleguide/message                  411 B          94.5 kB
└ ƒ /styleguide/typography               310 B          94.4 kB
+ First Load JS shared by all            87.3 kB
  ├ chunks/117-c494b1b50affae7c.js       31.6 kB
  ├ chunks/fd9d1056-827ced90119f7f6c.js  53.6 kB
  └ other shared chunks (total)          2.04 kB

●  (SSG)      prerendered as static HTML (uses getStaticProps)
ƒ  (Dynamic)  server-rendered on demand

Done in 62.30s.

I'm just gonna try Payload 3.0 now 😁


WIP Dev/148564 verify status codes for created endpoints

Hi,
This PR contains code changes, unit test cases in WIP.
Please review the same
Thanks

WhenInvalidSinceDateTimeInRequest_ThenGetSinceDateTimeReturnsInternalServerError()

Hi Richard,
Thanks for your review, these unit test are for internal server error when we received any scs response other than 200 So, to avoid confusion we have renamed the unit test's names and for invalid request we have handled other unit tests.


Acute characters in CFBundleIdentifier causes upload to fail

Expected behavior
Upload data
Observed behavior
error:  cannot create /var/folders/wh/w71drswxxxxxsb1jdd7v9v540000gp/T/bugsnag-dsym-upload.XXX.bIUl4wOG/A7660156-XXXX-3F45-A0AD-4F663D8585EE.dSYM/Contents/Resources/DWARF/+?ntima M+?vil
Steps to reproduce
Use a product name that uses acute characters
Version
1.3.2

Thank you for the report, @argentounce. Looking into it.

👋 . we've just released https://github.com/bugsnag/bugsnag-dsym-upload/releases/tag/v2.1.0 of the bugsnag-dsym-upload tool which which will now allow you to upload dSYMs with special characters in the pathname. I believe this should fix the issue that you were observing in this issue, but do let us know if you spot any problems.


rkt: use new discovery.Endpoint struct from appc/spec.

This patch, should be merged together with the appc/spec part (appc/spec#132). Tests will fail due to this requirement.

@vcaputo thanks, sorry for missing that one

@jonboulle no problemo!


CRDT - support JSON type

DESCRIPTION:
Since JustinDB is datatype-agnostic database (it doesn't care what type our data is - it just stores clean bytes) we want to opaque them with technique called CRDT which should allow us to merge divergent replicas seamlessly.

GOAL: Add support to CRDT JSON.
library -> https://github.com/fthomas/crjdt
Still WIP.

Current coverage is 67.25% (diff: 100%)

Merging #25 into master will not change coverage

@@             master        #25   diff @@
==========================================
  Files            34         34
  Lines           284        284
  Methods         279        279
  Messages          0          0
  Branches          5          5
==========================================
  Hits            191        191
  Misses           93         93
  Partials          0          0

Powered by Codecov. Last update 194e693...91a648f


firebase() doesn't return app instance

    "@nativescript/firebase-core": "^2.2.9",
When i try to initialize firebase app, firebase() call doesn't return app instance
@NgModule({
  bootstrap: [AppComponent],
  imports: [],
  declarations: [AppComponent],
  providers: [
    ...APP_INTERCEPTORS,
  ],
  schemas: [NO_ERRORS_SCHEMA]
})
export class AppModule {
  constructor(private _router: Router, private appService: AppService) {
    console.log('firebase -->?', firebase()); //  <<--  here {}
    firebase().initializeApp().then(_ => console.log('Firebase app initialized'));
  }
}

Can anyone explain what's wrong with that?
Thanks
  "dependencies": {
    "@angular/animations": "~13.2.0",
    "@angular/common": "~13.2.0",
    "@angular/compiler": "~13.2.0",
    "@angular/core": "~13.2.0",
    "@angular/forms": "~13.2.0",
    "@angular/platform-browser": "~13.2.0",
    "@angular/platform-browser-dynamic": "~13.2.0",
    "@angular/router": "~13.2.0",
    "@kefah/nativescript-google-maps": "^1.0.7",
    "@nativescript-community/ui-material-bottomnavigationbar": "^7.0.25",
    "@nativescript-community/ui-material-bottomsheet": "^7.0.25",
    "@nativescript/angular": "^13.0.0",
    "@nativescript/appversion": "^2.0.0",
    "@nativescript/core": "~8.3.4",
    "@nativescript/firebase-core": "^2.2.9",
    "@nativescript/geolocation": "^8.0.2",
    "@nativescript/localize": "^5.0.4",
    "@nativescript/secure-storage": "^3.0.0",
    "@nativescript/theme": "~3.0.2",
    "@sergeymell/nativescript-svg": "^1.1.2",
    "rxjs": "~7.5.0",
    "zone.js": "~0.11.5"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~13.2.0",
    "@angular/compiler-cli": "~13.2.0",
    "@nativescript/android": "8.3.1",
    "@nativescript/types": "~8.3.1",
    "@nativescript/webpack": "~5.0.6",
    "@ngtools/webpack": "~13.2.0",
    "copy-webpack-plugin": "^11.0.0",
    "typescript": "~4.5.5"
  }

after watching problem deeper i got an exception after firebase().initializeApp() call
JS: ERROR Error: Uncaught (in promise): Error: Cannot read property 'initializeApp' of undefined
JS: Error: Cannot read property 'initializeApp' of undefined
JS:     at file: src\webpack:\szybkigroszyk\node_modules\@nativescript\firebase-core\index.android.js:283:0

Cleaning the project should fix you up ns clean

I have the same issue. ns clean didn't help. I try to init firebase in the app component with this.
import { firebase } from '@nativescript/firebase-core';
...
ngOnInit() {
firebase().initializeApp().then(
() => {
console.log("firebase.init done!");
},
error => {
console.log(firebase.init error: ${error});
}
);
}
anyone had the same issue and solved it?

You should call init outside of your app module

same issue here. Anyone find the fix ? share please.
`async function initifireBase() {
try {
const defaultApp = await firebase().initializeApp();

} catch (err) {
console.log(err);
}
}`
Console logs
Successfully synced application org.nsf.mobileaudit on device RZ8N20KGVZE.   JS: Angular is running in development mode. Call enableProdMode() to enable production mode.   JS: ERROR Error: Uncaught (in promise): Error: Cannot read property 'initializeApp' of undefined   JS: Error: Cannot read property 'initializeApp' of undefined   JS:     at file: src/webpack:/NSFAudit/node_modules/@nativescript/firebase-core/index.android.js:328:0   JS:     at new ZoneAwarePromise (file: src/webpack:/NSFAudit/node_modules/zone.js/fesm2015/zone.js:1429:0)   JS:     at Firebase.initializeApp (file: src/webpack:/NSFAudit/node_modules/@nativescript/firebase-core/index.android.js:267:0)   JS:     at AppComponent.initifireBase (file: src/webpack:/NSFAudit/src/app/app.component.ts:85:0)   JS:     at AppComponent.ngOnInit (file: src/webpack:/NSFAudit/src/app/app.component.ts:73:0)   JS:     at callHook (file: src/webpack:/NSFAudit/node_modules/@angular/core/fesm2015/core.mjs:2491:0)   JS:     at callHooks (file: src/webpack:/NSFAudit/node_modules/@angular/core/fesm2015/core.mjs:2460:0)   JS:     at executeInitAndCheckHooks (file: src/webpack:/NSFAudit/node_modules/@angular/core/fesm2015/core.mjs:2411:0)   JS:     at refreshView (file: src/webpack:/NSFAudit/node_modules/@angular/core/fesm2015/core.mjs:11979:0)   JS:     at renderComponentOrTemplate

Error is here
Looks like `FirebaseApp` is not a property of `com.google.firebase`

any update on this please ?

Can you try adding one of the optional modules e.g database or storage ?

Hi,
Same error here ; project cleaned, some other optional modules installed...
No error on logcat (android), but same object FirebaseApp empty on firebase-core node_modules
@gyan-nsf @R-chie Have you found a solution since?
Thanks !

Hello,
I have the same issu firebase().initializeApp() is an Empty function, here is my package.json"dependencies": {     "@angular/animations": "^12.2.5",     "@angular/common": "^12.2.5",     "@angular/compiler": "^12.2.5",     "@angular/core": "^12.2.5",     "@angular/forms": "^12.2.5",     "@angular/platform-browser": "^12.2.5",     "@angular/platform-browser-dynamic": "^12.2.5",     "@angular/router": "^12.2.5",     "@danvick/ngx-translate-nativescript-loader": "3.0.1",     "@nativescript/angular": "^12.2.0",     "@nativescript/core": "8.3.5",     "@nativescript/email": "^2.0.5",     "@nativescript/firebase": "^11.1.3",     "@nativescript/secure-storage": "^3.0.0",     "@nativescript/social-share": "^2.0.4",     "@nativescript/theme": "~3.0.0",     "@ngx-translate/core": "^13.0.0",     "copyfiles": "^2.4.1",     "nativescript-dna-deviceinfo": "^3.7.1",     "nativescript-email": "^1.6.0",     "nativescript-gtm": "^1.0.0",     "nativescript-openurl": "^1.0.2",     "nativescript-phone": "^3.0.1",     "nativescript-social-share": "^1.6.0",     "reflect-metadata": "~0.1.12",     "rimraf": "^3.0.2",     "rxjs": "~7.3.0",     "zone.js": "~0.11.4"   }

Anyone with only firebase-core installed will need to install one of the other firebase modules .eg storage.

Experiencing the same issue. firebase() returns an empty object instead of firebase.
I have the following modules installed for firebase:
"@nativescript/firebase-core": "^2.3.4",
"@nativescript/firebase-crashlytics": "^2.3.4",

A couple things to try

Those getting the following error JS: ERROR Error: Uncaught (in promise): Error: Cannot read property 'initializeApp' of undefined you need to install one of the other firebase packages

Those using any non vanilla flavor try calling the initializeApp in the app.(ts|js)/ main.ts early as possible

Hello @brysem , you will need to install "@nativescript/firebase-installations": "2.3.4", this will fix your issue

Thank you @aymenelhajayed.
For anyone else running into the problem setting up crashlytics. I will leave the following below.
After installing the following three dependencies I have crashlytics working.
"@nativescript/firebase-core": "^2.3.4",
"@nativescript/firebase-crashlytics": "^2.3.4",
"@nativescript/firebase-installations": "^2.3.4",

I mounted firebase in main.ts with the following code.
import { firebase } from '@nativescript/firebase-core';
import '@nativescript/firebase-crashlytics';

const firebaseApp = await firebase().initializeApp();

I can now use the log feature of crashlytics on the different pages in my app.
Example:
import { firebase } from '@nativescript/firebase-core';

firebase().crashlytics().log('Login@mounted');

resolved


Custom CSS

Hey,
I hate the way helvetica neue looks on messenger and I'd love to have some kind of custom CSS injection capabilities (or just a preference somewhere to change it to San Francisco). I know this is kind of a weird feature to have, so I'm willing to implement it myself, if anyone can point me where I should start, because I have no idea where should I hook in to do that.

You'll want to look at webView:didClearWindowObject:forFrame: which is called when the view's JS context has been setup (but most likely before the HTML DOM exists.) Execute some JS to add your CSS.
I just tried this and it works pretty well:
[webView.mainFrame.windowObject evaluateWebScript:
 @"document.addEventListener('DOMContentLoaded', function() { var s = document.createElement('style'); s.innerText = '* { font-family:\"marker felt\"; }'; document.head.appendChild(s); console.log('done'); });"];

I don't think we should add this to the main release, but making your own build is pretty easy :)


Beta decay not testing

Need to just test it...

Finish code to write out CSV file of results instead of graph.


Automated testing skeleton

I think it would be neat if we could get a few tests as part of our automated checks. I made some minor fixes to the simulator to get it to compile, and added a basic test for the CAN driver as a proof of concept. I'm interested to see what y'all think about this.
Please let me know any questions, comments, suggestions, etc.
A few things I would like feedback on are:

Do you think we can get meaningful test coverage out of this without a ton of extra work? I will try to make a test for one of voltage/temperature/amperes later to try this
Does it look like the process for adding tests is straightforward? Can we reasonably expect all of our members to understand how this works?
I did not put a whole lot of thought into directory/file structure or naming, so any feedback would be appreciated
Anything else you want to comment on

I also removed the timer from the BPS simulator because it uses a ton of CPU and is not a good simulation anyway. I am not sure if these changes break the interactive simulator's CAN implementation, but I don't think the interactive simulator is very useful anyway.


The issue_updates feature should be separated from opasDataLoader

Unless we want to combine these output files to generate the notice to send out, the issue_updates code should be moved to it's own file run after all the loaders terminate.  It should be able to use the tracker database to pull together the list of updated issues.

I don't think this is necessary anymore.


Allow key rotations without destroying SAMLv2 IDP resources

Resolves #268

ForceNew was intentionally added to this field in https://github.com/FusionAuth/terraform-provider-fusionauth/commit/37d66a75a85279366e5fa3e54c069fca0dd58127. @robotdan Do you have any context on why that was done?

#135 references this as well

This obvious bug is one of the things that are currently blocking us from using continuing the use the Terraform provider. Can we somehow poke a maintainer to merge this in? I've tried through our enterprise support, but with little success.

@edmeister looks like this will be in the next release per #275


/nl -- Add player final step lacks a prompt.

Menu simply closes and displays no prompt, but does await user input.
To reproduce: access a group via /nl and choose "Invite new member". Pick any level. An empty string is written to chat but no prompt.

Fixed by https://github.com/Civcraft/NameLayer/commit/9be6c6e4fb85f450582d6bf733249bf3eeee36bd


fail to make

The link in the Makefile directly under the repository is a dead link
https://github.com/pola-rs/polars-book/blob/master/Makefile
DATA_SRC=https://github.com/ritchie46/static/releases/download/0.0.1
DATA_SRC_STATIC=https://raw.githubusercontent.com/pola-rs/polars-static/master/data

Hi @pea-sys - do you mean https://raw.githubusercontent.com/pola-rs/polars-static/master/data? That link isn't supposed to work until the file paths are added further down. Or have I misunderstood?

@braaannigan
Sorry.
I am wrong.
You are right.
I happened to be accessing the URL at a time when the network was off.