Matrix report with additional column after the total (right side)

Hi,
We are using FastReport.Opensource.web for generating reports.
I have a report with the below columns. In the below columns the columns marked as "**" are row values which needs to be converted as column values (like a matrix report).
Opening/Transactions | Transaction no. | Currency | **Cash chips | **NNeg chips | **Non-RFID chips | [-] Denomination | Chip code | Total chips |   | Total Value | Date_time | Remarks
My problem is that I have more columns after the columns which are converted from row values. I don't know how to specify them in the matrix report. Please let me know how this can be achieved. Is matrix report is the right way to do this report?
Your help is greatly appreciated.

Hello,
Sorry but I don't understand what you want to do. Can you explain it with pictures, maybe?

Hi,
Thanks for contacting for more information.
The report should look like the below one. The currency (Red box) and the Chips (Purple box) are the one to come as a matrix report. My question was, If I am defining this as a Matrix report, how do I define the rest of the columns in the report?
<EMAIL_ADDRESS>Regards,
Valanarasu J.
From: ATZ-FR<EMAIL_ADDRESS>Sent: Tuesday, June 30, 2020 1:20 PM
To: FastReports/FastReport<EMAIL_ADDRESS>Cc: Innocent Maria Valanarasu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [FastReports/FastReport] Matrix report with additional column after the total (right side) (#194)
Hello,
Sorry but I don't understand what you want to do. Can you explain it with pictures, maybe?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/FastReports/FastReport/issues/194#issuecomment-651616321, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQDU22SCB3UCPSD7BOCYQVLRZGKLVANCNFSM4OLF7WAA.

It seems the picture in your message is lost. Try to repost or write to support at fast-report.com.

Hi,
I have attached the image here for your reference. If you still didn’t get the image please let me know.
Regards,
Valanarasu J, Technical Manager
valan<EMAIL_ADDRESS><EMAIL_ADDRESS>This e-mail message is a confidential communication and is intended only for the named recipient(s) above. It may contain information that is a XUVI trade secret, is proprietary or privileged. If you have received this message in error or are not the named or intended recipient(s), please immediately notify the sender and delete this e-mail message and any attachments from your workstation or network mail system.
From: ATZ-FR<EMAIL_ADDRESS>Sent: Thursday, July 2, 2020 7:25 PM
To: FastReports/FastReport<EMAIL_ADDRESS>Cc: Innocent Maria Valanarasu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [FastReports/FastReport] Matrix report with additional column after the total (right side) (#194)
It seems the picture in your message is lost. Try to repost or write to support at fast-report.com.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/FastReports/FastReport/issues/194#issuecomment-653020060, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQDU22VAQAOU7MYHJRERKPTRZSGTHANCNFSM4OLF7WAA.

Nope, just a string<EMAIL_ADDRESS>

Attached the file

Hi,
I’ve attached it as a PNG file now in github. It is appearing. Also I’ve attached here as the PNG again.
Valanarasu J, Technical Manager
valan<EMAIL_ADDRESS><EMAIL_ADDRESS>This e-mail message is a confidential communication and is intended only for the named recipient(s) above. It may contain information that is a XUVI trade secret, is proprietary or privileged. If you have received this message in error or are not the named or intended recipient(s), please immediately notify the sender and delete this e-mail message and any attachments from your workstation or network mail system.
From: ATZ-FR<EMAIL_ADDRESS>Sent: Thursday, July 2, 2020 8:51 PM
To: FastReports/FastReport<EMAIL_ADDRESS>Cc: Innocent Maria Valanarasu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [FastReports/FastReport] Matrix report with additional column after the total (right side) (#194)
Nope, just a string<EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/FastReports/FastReport/issues/194#issuecomment-653069936, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQDU22WMD3LEPWYY263V4C3RZSQUFANCNFSM4OLF7WAA.

I'm afraid it is not the kind of data required for matrix-type reports.
https://www.fast-report.com/public_download/html/UserManFrNET-en/matrixtheory.htm
You may try to use Table object and fill it dynamically.

Thank you very much for the support. I will try with table.
Regards,
Valanarasu J.
From: ATZ-FR<EMAIL_ADDRESS>Sent: Thursday, July 2, 2020 10:14 PM
To: FastReports/FastReport<EMAIL_ADDRESS>Cc: Innocent Maria Valanarasu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [FastReports/FastReport] Matrix report with additional column after the total (right side) (#194)
I'm afraid it is not the kind of data required for matrix-type reports.
https://www.fast-report.com/public_download/html/UserManFrNET-en/matrixtheory.htm
You may try to use Table object and fill it dynamically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/FastReports/FastReport/issues/194#issuecomment-653113670, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQDU22WXQD57XYMBJ5NPVNDRZS2NHANCNFSM4OLF7WAA.

Thank for the support.
Valanarasu J.
From: Aleksandr Fediashov<EMAIL_ADDRESS>Sent: Sunday, July 5, 2020 3:58 PM
To: FastReports/FastReport<EMAIL_ADDRESS>Cc: Innocent Maria Valanarasu<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [FastReports/FastReport] Matrix report with additional column after the total (right side) (#194)
Closed #194https://github.com/FastReports/FastReport/issues/194.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/FastReports/FastReport/issues/194#event-3513207732, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQDU22WSBZMD5DYGMFPUFRTR2BIUVANCNFSM4OLF7WAA.


Search Details Page / DOI Landing Page

Design and Implement

I've completed the initial implementation of the DOI landing pages. You can see those changes here
This code is pushed to doi-mockup branch
Some known differences from mockups, with room for discussion:

I kept some of the iconography that we had initially in our design
The pill appended to the title is "PDS4 Bundle/Collection" instead of just "Bundle/Collection" because it also needed to support PDS3
I left Observing System components on the sidebar, as we originally had it on our site (still labeled as Spacecraft/Mission/Instrument) since I believe that's a better place for it, but it was also just easier.
I only auto-collapsed those side boxes if there are more than three items
I did not auto-expand the details on the high width breakpoint mostly because I really just ran out of time to do anything fancy ensuring that the primary Browse button was always visible above the fold
The Citation Builder is just some arbitrary patterns that show how we could go about dynamically constructing citations for the user. I looked into adding some real examples, but quickly realized how complicated and varied (and undocumented) widely-used citation styles are

Some additional handy new features to be aware of on that deployment:

If you append &mockup=true to the URL, additional mockup data will be integrated into the dataset pages, to highlight the additional features
If you append &pdsOnly=true to the URL, then any additional metadata that we have supplemented as part of the Archive Loader at PSI will be left out of the pages (so you can see results purely from the PDS core registry).

Meta-note: I'm out next week so don't find anything too broken too soon

October Schedule Status ⏳:  On track

1

Here is some crit for what is here

Is this supposed to adhere to our dark theme that we defined?
I think removing 'relevant tags' is ok. They are removed when adjusted for mobile, so I think it ok to remove this all together
Regarding the right-hand container (other versions, PDS3 Versions, etc.), is this something we can potentially push back in to an accordion header, much like 'show more'? Why do we have this in its own container (what makes it so special?)
Also, no good reason to have each version to be contained in their own card. We can just contain them in to one accordion or module container as you see in the mockup I've attached
I am confused as to why we use 'bundle' and 'dataset' when concerning Bundles. Are they the same thing? Or are we nudging user to browse the collection with the button? I am not sure what the distinction is.
We don't have that sized button defined in the design system - it is a bit excessive
Here is a mockup of what it should look like in the theme

Is this supposed to adhere to our dark theme that we defined?

Per Mike, we will create new ticket to track converting to using dark theme.

I think removing 'relevant tags' is ok. They are removed when adjusted for mobile, so I think it ok to remove this all together

Will be removed.

Regarding the right-hand container (other versions, PDS3 Versions, etc.), is this something we can potentially push back in to an accordion header, much like 'show more'? Why do we have this in its own container (what makes it so special?) Also, no good reason to have each version to be contained in their own card. We can just contain them in to one accordion or module container as you see in the mockup I've attached

Mike will try out accordion as an alternative to see if it makes sense to use instead of cards.

I am confused as to why we use 'bundle' and 'dataset' when concerning Bundles. Are they the same thing? Or are we nudging user to browse the collection with the button? I am not sure what the distinction is.

Mike to try out some different layouts to make this distinction more clear.

We don't have that sized button defined in the design system - it is a bit excessive

Will look to figure out a better way to display this.

We have icons defined in the design system - I have swapped for our flat 'folder' icon.

Copy. Mike will look into this.

@edwardbarraza can you provide a link to the figma mockup you have above?

Here is the link for the DOI work in Figma
I can also link to the Design System that is still WIP, here

Closing out this Epic per comments above and sub-ticket completion. See https://sbnarchivedemo.psi.edu/?identifier=urn:nasa:pds:cassini_iss_saturn:data_raw&mockup=true


add submit applications api

What do you mean?

What do you mean?

https://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/ResourceManagerRest.html
POST http:///ws/v1/cluster/apps/new-application
why "Post" is not impl yet?


Question: Is there any way to reduce project size?

I implemented hxvlc in a project where I have to play just a single video and it works great, but, hxvlc adds +200MB to the entire project. Is there any way to reduce the size hxvlc takes up with all of its files?

By removing some of the plugins you can reduce the size but i don't recommend it as it can cause issues with libvlc.


[BLAS] New BLAS backend: SYCL-BLAS

Description

Add SYCL-BLAS as a backend for OneMKL.
SYCL-BLAS is a pure-SYCL, open-source, BLAS implementation.

Checklist
All Submissions

[ x ] Tests: Logs attached below

syclblas_ct.txt
syclblas_rt.txt
The failures for double-precision functions on an iGPU that does not support double precision. In these cases, the backend throws mkl::unsupported_device, which results in a test failure.
The tests were run with --gtest_filter=-ImatcopyBatchStrideTestSuite* because this test suite segfaults. This function is not implemented in SYCL-BLAS.

[ x ] Have you formatted the code using clang-format?

Thank you for the PR! Can you provide more details on the segfaults? There are several other routines that are not implemented in SYCL-BLAS but they do not segfault (omatcopy, omatadd).

@andrewtbarker

Thank you for the PR! Can you provide more details on the segfaults? There are several other routines that are not implemented in SYCL-BLAS but they do not segfault (omatcopy, omatadd).

The only segfaulting test is ImatcopyBatchStrideTestSuite, for complex single precision with row-major.  I'm compiling DPC++ with the 2022-06-10 nighty on Ubuntu. double free or corruption and then Aborted (core dumped) are encountered after the test catches the unimplemented exception, and after the test<elem_t> function has executed:
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) where
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff6bd2859 in __GI_abort () at abort.c:79
#2  0x00007ffff6c3d26e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff6d67298 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3  0x00007ffff6c452fc in malloc_printerr (str=str@entry=0x7ffff6d69690 "double free or corruption (!prev)") at malloc.c:5347
#4  0x00007ffff6c46fac in _int_free (av=0x7ffff6d9cb80 <main_arena>, p=0x13b2d70, have_lock=<optimised out>) at malloc.c:4317
#5  0x00000000009e5095 in (anonymous namespace)::ImatcopyBatchStrideTests_ComplexSinglePrecision_Test::TestBody() ()
#6  0x00007ffff776b518 in void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) ()
   from /home/hugh/dev/onemkl/build/lib/libgtest.so
#7  0x00007ffff774894f in testing::Test::Run() () from /home/hugh/dev/onemkl/build/lib/libgtest.so
#8  0x00007ffff774a04d in testing::TestInfo::Run() () from /home/hugh/dev/onemkl/build/lib/libgtest.so
#9  0x00007ffff774a800 in testing::TestSuite::Run() () from /home/hugh/dev/onemkl/build/lib/libgtest.so
#10 0x00007ffff77581f3 in testing::internal::UnitTestImpl::RunAllTests() () from /home/hugh/dev/onemkl/build/lib/libgtest.so
#11 0x00007ffff776c3f8 in bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) () from /home/hugh/dev/onemkl/build/lib/libgtest.so
#12 0x00007ffff7757df9 in testing::UnitTest::Run() () from /home/hugh/dev/onemkl/build/lib/libgtest.so
#13 0x0000000000ab4e16 in main ()

If I comment out the call to imatcopy_ref, there is no segfault, so I think imatcopy_ref is corrupting the heap. It isn't clear to me why this seems to occur for complex-single-precision row-major and not for real matrices.
If I was guessing as to the location of the bug, I'd look into
    lda = std::max(m, n);
    ldb = std::max(m, n);

which I don't understand at the moment - the imatcopy docs and imatcopy batched strided docs make this parameter look rather more complicated.

I'm still working my way through the code, so there could be more comments, but here are a few to start:
1. This could be a very nice addition to the project!

2. Does SYCL-BLAS not support USM memory at all? I am not sure of the long-term future of the buffer interfaces so this could be a concern.

3. I cannot reproduce the segfault for imatcopy batch stride.

4. I am seeing quite a few failures in my local testing (integrated Intel GPU). I have not investigated these closely, but I'm attaching the log just in case the list of failures means anything.

test.txt

Thank you!
SYCL-BLAS doesn't support USM memory at the moment, but it will support USM in the future. We will add support USM in the backend when SYCL-BLAS's implementation is ready.
Interesting. I don't think this is an issue introduced in this PR, but something to keep track of. If I can find time, I'll investigate more with other backends and create an issue for this.
Your failures are all of the functions that SYCL-BLAS implements. If you could provide more details on how you compiled this, and the drivers you're using, that would help us reproduce the issue.

Typical error message from my failures:
1: [ RUN      ] Nrm2TestSuite/Nrm2Tests.RealSinglePrecision/Column_Major_Intel_R__Iris_R__Pro_Graphics_580__0x193b_
1: Native API failed. Native API returns: -997 (Command failed to enqueue/execute) -997 (Command failed to enqueue/execute)
1: Enqueue process failed. -59 (CL_INVALID_OPERATION)
1: Enqueue process failed. -59 (CL_INVALID_OPERATION)
1: unknown file: Failure
1: C++ exception with description "Enqueue process failed. -59 (CL_INVALID_OPERATION)" thrown in the test body.
1: [  FAILED  ] Nrm2TestSuite/Nrm2Tests.RealSinglePrecision/Column_Major_Intel_R__Iris_R__Pro_Graphics_580__0x193b_, where GetParam() = (0x3162320, 1-byte object <00>) (222 ms)

This is quite possibly a bad configuration locally, I'm investigating more closely.

I have the tests passing on a different machine, so never mind the failures I saw. Overall I think this PR is looking good.

I have the tests passing on a different machine, so never mind the failures I saw. Overall I think this PR is looking good.

@andrewtbarker Do we have any plans in place for testing this backend in terms of machines, compilers as a part of CI? If not, I think, we should make that plan and validate the PR on all configurations (if we have not done it yet).

@mmeterel The PR in its current form is only supported with dpc++ compiler and Intel GPU. There is some discussion about the eventual scope for this, we'll see. I will try to document the scripts for the install and test process so we can automate it in the future.

Is this intended to skip all row_major tests?

Is this intended to skip all row_major tests?

Yes, SYCL-BLAS does not support row major operations currently. We are planning to support this in the future.

On nVidia hardware I'm seeing lots of errors of this form:
949: Note: Google Test filter = Nrm2TestSuite/Nrm2Tests.RealDoublePrecision/Column_Major_NVIDIA_TITAN_RTX
949: [==========] Running 1 test from 1 test suite.
949: [----------] Global test environment set-up.
949: [----------] 1 test from Nrm2TestSuite/Nrm2Tests
949: [ RUN      ] Nrm2TestSuite/Nrm2Tests.RealDoublePrecision/Column_Major_NVIDIA_TITAN_RTX
949: Native API failed. Native API returns: -42 (PI_ERROR_INVALID_BINARY) -42 (PI_ERROR_INVALID_BINARY)
949: Enqueue process failed. -59 (PI_ERROR_INVALID_OPERATION)
949: Enqueue process failed. -59 (PI_ERROR_INVALID_OPERATION)
949: unknown file: Failure
949: C++ exception with description "Enqueue process failed. -59 (PI_ERROR_INVALID_OPERATION)" thrown in the test body.
949: [  FAILED  ] Nrm2TestSuite/Nrm2Tests.RealDoublePrecision/Column_Major_NVIDIA_TITAN_RTX, where GetParam() = (0x1b6bf90, 1-byte object <00>) (77 ms)
949: [----------] 1 test from Nrm2TestSuite/Nrm2Tests (77 ms total)
949:
949: [----------] Global test environment tear-down
949: [==========] 1 test from 1 test suite ran. (77 ms total)
949: [  PASSED  ] 0 tests.
949: [  FAILED  ] 1 test, listed below:
949: [  FAILED  ] Nrm2TestSuite/Nrm2Tests.RealDoublePrecision/Column_Major_NVIDIA_TITAN_RTX, where GetParam() = (0x1b6bf90, 1-byte object <00>)
949:
949:  1 FAILED TEST

I'll dig in a little more and let you know what I find.

@andrewtbarker this looks like an error with the wrong target triple?
For reference I tested this on an RTX 2060 with the CMake command line cmake -Bbuild -GNinja -DENABLE_SYCLBLAS_BACKEND=ON -DREF_BLAS_ROOT=/path/to/lapack/install -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -DTARGET_DOMAINS=blas -DENABLE_MKLCPU_BACKEND=OFF -DENABLE_MKLGPU_BACKEND=OFF -DCMAKE_CXX_FLAGS="-fsycl -fsycl-targets=nvptx64-nvidia-cuda"  and a build of intel/llvm with CUDA support.

@Rbiessy that's exactly it, thanks. Do you think we can modify the way FindCompiler.cmake sets the -fsycl-targets argument so it's similar with SYCL-BLAS and the other backends (see here) ?

@andrewtbarker I am not keen on adding more CMake flags specific to SYCL-BLAS. One difference with the variables in FindCompiler.cmake is that we can enable multiple targets for SYCL-BLAS which is an important feature. I think it would be confusing for multiple targets. This requires more work to automate this on the CMake level so could be worth doing in a separate MR if we decide this is needed?

Would it be better if we add the -fsycl-targets configuration in backends/syclblas/CMakeLists.txt? Then we can do it based on the already existing ENABLE_SYCLBLAS_BACKEND_* cmake variables.
At the very least this needs to be documented much better. I did not know the explicit CMAKE_CXX_FLAGS would be needed until you told me today - how will users know how to configure this backend?

It's not possible to set -fsycl-targets in backends/syclblas/CMakeLists.txt. ENABLE_SYCLBLAS_BACKEND_* are internal variables, they will be overwritten if set on the command line (and are not visible when listing the available options).
We are documenting CMAKE_CXX_FLAGS in docs/building_the_project.rst. They are meant as advanced options for now but we could improve this later if needed.

I made a PR into this branch to show what I have in mind. It works fine on our nvidia GPU, have not tried it with AMD.
For documentation, do I understand the following correctly:

Intel GPU is supported without -fsycl-targets option;
nVidia and AMD GPU require an explicit -fsycl-targets option (this is my experience);
Enabling multiple GPU types will also require explicit -fsycl-targets;
SYCL-BLAS can only tune for a single GPU;
Tuning is strongly recommended in the SYCL-BLAS docs for performance.

If I'm right on these points (or even if I'm wrong), some of this needs to be clarified in building_the_project.rst.

I have updated the documentation according https://github.com/codeplaysoftware/oneMKL/pull/16 will be merged.
I am trying to keep it generic. For instance the default sycl-target is spir64 so that should run on a wide range of devices if they have the right drivers (including Nvidia or AMD).

This is much better, thank you. Sorry for the churn and confusion, I just want to make sure that if we claim to support multiple HW it's clear to users how to use them. I'm ready to approve this once the above PR (or something similar) is merged.

@mkrainiuk Can you or someone from engine team take a look at this when you get a chance?

Hi @andrewtbarker @mkrainiuk is there anything else that you would like us to add in this PR?

Hi @muhammad-tanvir-1211 , from my perspective this is ready to go but we need a second review to merge. Our team is right in the middle of a busy process right now, sorry for the delay.


Run oauth proxy tests on jenkins

https://github.com/department-of-veterans-affairs/vets-contrib/issues/3671
More tests to come, but for now we should at least make sure the existing oauth proxy tests get run on each commit.

Do we need to install packages before running tests?

We already install packages when we build the Dockerfile. Adding npm install to the Jenkinsfile would cause us to install them twice for each run.
However, we do need to cd /opt/app (the WORKDIR set in the dockerfile) to take advantage of those already installed packages, since Jenkins overrides the workdir setting at runtime.

Why not use npm run-script test?

No reason, other than I didn't notice that was defined. I'll switch!

Do we need to generate and gather test results in an xml file (like is done for the saml-proxy tests?)
I don't think so. We could do that, but it hides test failures behind a second click that I've seen lots of people miss in the past. I think just printing failures to the console is the best solution for the way we use Jenkins. If we were relying on Jenkins to calculate some kind of metrics based on the number of tests passed/failed, then I think it would be worth switching to an xml report.

what does Jenkins override the directory to? haven't run into that, would like to learn 😄

It got set to /home/jenkins/workspace/xy_kalilsn_run-oauth-proxy-tests on my last run. If you search for that string in the log you can see the full command. Let me know if you think there's a better way to do this! I'll go ahead and make sure we run the SAML and OAuth proxy tests the same way before merging this.

in the SAML proxy tests, what does withEnv(['CI=true']) do? couldn't find anything with a quick grep. if nothing, can it be removed here?

I think you're right that it doesn't do anything. I assumed the CI var meant something to jest but I can't find any evidence of that. Nice catch!


Seems like a bug in the open-source implementation of perturbtion prediction

Hi, thanks for your great work. When I tried to run the new perturbation prediction code, I found a bug:

Could you please help me address it? Thanks.

I've faced a similar error, and the solution is using the 0.0.1 version of cell-gears, I guess you may installed the 0.0.4 version?

@taffy-miao Hi, thanks for your feedback. But sorry I do not have plans to follow Taffy at Bilibili :).

I downgrade my gears to 0.0.1, but I still face this error. Is it possible to have a version with updated gears? Thanks.

Hi @HelloWorldLTY , after you reinstall gears 0.0.1, please also delete the downloaded data and let the package build it again. A similar discussion can be found at #36 as well. I've also added the dependency to the pyproject.toml and uploaded a new version. Hopefully, this will help avoid future confusion.

Thanks a lot for your explaniation!!!


CORE-1411 - MariaDB support

Added a MariaDBDatabase class extending MySQLDatabase class and updated tests

Merged into master rather than 3.3.x since the change is larger than I like to do in a point release. It will go out with 3.4.

Thanks. Any estimate as to when 3.4 will be released ?
I have another pending PR to include MariaDB support for a project using liquibase.


chore(package): update npm-pkgbuild to version 6.11.5

Coverage remained the same at 87.261% when pulling 93a56d37d53d2eda979153e2630687ba2c8a5148 on greenkeeper/npm-pkgbuild-6.11.5 into 3316c4b62fb986825e1ab06b5288fc401f8d90d1 on master.


[Request for External] codeunit 99000854 "Inventory Profile Offsetting" - multiple procedures

I'm implementing a new type of Reordering Policy and so need to amend the "Inventory Profile Offsetting" codeunit to handle this.  I would like the scope for the following procedures changed from local to global so that I can re-use the procedures.  I have tried replicating the needed procedures (not ideal) but still can't achieve what I need to do because I can't set/use some global variables like FutureSupplyWithinLeadtime, OverflowLevel, DampenerQty etc...
Please can you change the following procedures from local to global...
CreateDemand
InitSupply
CreateSupplyForward
CalcOrderQty
CalcReorderQty
CalcMaximumReorderQty
ScheduleForward
MaintainPlanningLine
SumUpProjectedSupply
DecreaseQty
CanDecreaseSupply
CheckNewOverflow

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11018.


Not working

Hi
I follow your guide but not helpful...
what i've done:

added id pass in both file
Turn On less secure apps in gmail
Installed pyinstaller
executed implant.py using pyinstaller
and last python gcat.py -list Nothing happen...

Same problem facing.


EO hamcrest release 0.4.0

PR-Codex overview
This PR updates the version of the org.eolang.hamcrest package and its dependencies and adds new test cases.
Detailed summary

Updated org.eolang.hamcrest package version from 0.3.2 to 0.4.0
Updated dependencies to version 0.4.0
Added new test cases for various matchers

The following files were skipped due to too many changes: objects/org/eolang/hamcrest/matchers/blank-string-matcher.eo, objects/org/eolang/hamcrest/matchers/contains-string-matcher.eo, objects/org/eolang/hamcrest/matchers/array-each-matcher.eo, objects/org/eolang/hamcrest/matchers/described-as-matcher.eo, tests/org/eolang/hamcrest/close-to-tests.eo, tests/org/eolang/hamcrest/failed-output/all-of-failed-output.eo, objects/org/eolang/hamcrest/assert-that.eo, objects/org/eolang/hamcrest/assert-twice-that.eo, objects/org/eolang/hamcrest/matchers/close-to-matcher.eo, tests/org/eolang/hamcrest/failed-output/close-to-failed-output.eo

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@yegor256 Please, have a look

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 14min)


Enabling higher DPI settings

Submitting scale parameter to get tiles with higher DPI settings
Removing scale overwrite

@nyurik I did. And the solution also depends on some abaculus changes.
I posted a screenshot in Phabricator. Let me know if you have any more doubts.


[Bug]: Command not visible

Contact Details
<EMAIL_ADDRESS>What happened?
On Fosscu getting started page. command Ctrl+k is not visible to users.

Note: I would like to work on this issue
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

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

@Ahtaxam the pull request of this issue have been already made

@Bharadwajshivam28 if pull request have been closed. then why changing are not visible ?

pr have been made but not merged .. maintainer will come on and merge it

https://github.com/FOSS-Community/Community-Hub/pull/10
have a look


Cloudwatch PutMetric

The PR includes PutMetric for Cloudwatch. Since a single PutMetric can include many individual metrics and dimensions, the approach is compositional and is expected to be used in a pipeline. This PR is primarily to find out if this (or another) approach is palatable and to solicit any comments on alternatives.
An example:
ExAws.Cloudwatch.start_metric_data("Support", "out", 50, "Count", source: "generator")
|> ExAws.Cloudwatch.add_metric_data("in", 47, "Count", source: "network")
|> ExAws.Cloudwatch.put_metric_data
|> ExAws.request

Hey! I really really like this overall approach.
As a first question, I'm a bit unclear about the difference between start_metric_data and add_metric_data, is that an AWS distinction or one that you have?

The start_metric_data establishes the namespace (support in this case) and allows for one metric at the same time, Add just takes more metric data, but can't alter the namespace. The start_ could take only the namespace and then Add just do the metrics, might be clearer. I'm glad it seems generally ok, the AWS api itself is such a mix I'm never quite sure if I have the model quite right.

Changed start_metric_data to only take one param (the namespace). Added doctest

@danj3 Great contribution! We also need this functionality. @benwilson512 what stops you from merging it?

Hey! I'd be happy to include these changes. As you may have seen via https://elixirforum.com/t/proposal-exaws-2-0/9269 the project is splitting up each service into its own package to improve the maintenance process.
Please re-open this PR on https://github.com/ex-aws/ex_aws_cloudwatch

Move to https://github.com/ex-aws/ex_aws_cloudwatch/pull/2


Release the GIL for geometry-creating operations

This addresses #155 , now only for the geometry-to-geometry operations (like envelope and convex_hull)
The same pattern could be repeated for all other geometry-creating operations.

Cool. I assume the python wrappers still need to be decorated with multithreading_enabled ?
Now, I am trying this out, and I don't see any speedup. I actually don't see usage of multiple threads on my laptop (I was testing with make_valid, both with dask as with stdlib threading). Which seems to point that there is still somewhere the GIL being reacquired in the loop, but don't directly see where that would be.
(but would need to do a more elaborate profile to be sure where it is spending time)

.. ahum, most stupid error ever ;) I forgot to restart my python kernel after building this branch
Now I see a good speedup. For make_valid (an expensive operation), I see around 3x speedup by running in parallel on my laptop
Also no noticeable slowdown in the single threaded setting compared to master.

.. ahum, most stupid error ever ;) I forgot to restart my python kernel after building this branch
Now I see a good speedup. For make_valid (an expensive operation), I see around 3x speedup by running in parallel on my laptop
Also no noticeable slowdown in the single threaded setting compared to master.

Good! Thanks for checking :) I'll proceed with the other geometry-returning functions. And indeed, I should add the decorators as well.

@jorisvandenbossche  I am running into issues with the set operations. If you do this two-step procedure (create GEOSGeometry without GIL, create PyObject with GIL), the reduce functions do not work, as they expect the full PyObject to be created in the ufunc loop.

I am running into issues with the set operations. If you do this two-step procedure (create GEOSGeometry without GIL, create PyObject with GIL), the reduce functions do not work, as they expect the full PyObject to be created in the ufunc loop.

Hmm. So you mean that they expect that at the end of each loop iteration, there is a PyObject that can then be used as starting point for the next iteration?
Basically, a reduce operation looks like (so where the result gets reused as input)
r = identity
for i in range(len(A)):
  r = func(r, A[i])
return r

and currently, we have the OUTPUT_Y inside the loop (which converts the GEOSGeometry pointer to a PyObject and assigns this to op1).
And I assume that numpy then sets the input pointers and strides in such a way that op1 gets used as input again? (just guessing here, to try to understand what is exactly going on).
So then I was wondering: can't we solve it with adding yet another loop? First a loop unpacking the input objects into an array pointers. Then the loop with the actual operation only dealing with GEOSGeometry pointers, and then afterwards the loop wrapping in python objects.
But I suppose this actually doesn't help at all since when doing a reduce, you don't have two input arrays that can be unwrapped (do you know what ip1 and ip2 point to when it is called from reduce ?)

And I assume that numpy then sets the input pointers and strides in such a way that op1 gets used as input again? (just guessing here, to try to understand what is exactly going on).

That indeed seems to be the case:
https://github.com/numpy/numpy/blob/a5d021a1b6f439a19812926bc4d796ef5f346c44/numpy/core/src/umath/ufunc_object.c#L3500-L3508
            /* Turn the two items into three for the inner loop */
            dataptrs_copy[0] = dataptrs[0];
            dataptrs_copy[1] = dataptrs[1];
            dataptrs_copy[2] = dataptrs[0];
            strides_copy[0] = strides[0];
            strides_copy[1] = strides[1];
            strides_copy[2] = strides[0];
            innerloop(dataptrs_copy, &count,
                        strides_copy, innerloopdata);

And I assume that numpy then sets the input pointers and strides in such a way that op1 gets used as input again? (just guessing here, to try to understand what is exactly going on).

That indeed seems to be the case:

That is indeed the case. I added
printf("Args: %d, %d, %d Steps: %d, %d, %d\n", args[0], args[1], args[2], steps[0], steps[1], steps[2]);

into the ufunc and I got
>>> pygeos.lib.intersection.reduce(arr)
Args: 30428160, 26932968, 30428160 Steps: 0, 8, 0

I presume that the output array is filled with the first geometry in the array, else this would never work ;)

So then I was wondering: can't we solve it with adding yet another loop? First a loop unpacking the input objects into an array pointers. Then the loop with the actual operation only dealing with GEOSGeometry pointers, and then afterwards the loop wrapping in python objects.

I think this is our safest option. This might be tricky to get right though.

@jorisvandenbossche  I tried 2 approaches, one with the temporary array, and one with some custom logic inside the inner loop. The second one turned out to be much cleaner than the first.

Thanks for your review @brendan-ward , I gave especially the reduce function some additional attention.

I was initially going to say: we can also simply "punt" on having a no-gil reduce version if it turns out to be too difficult / complex.
But it seems you already found a relatively clean solution in the meantime! ;) Taking a look now

Thanks @jorisvandenbossche, I tried to clarify the docstrings a bit.
Also, this PR is now tested for memory leaks using valgrind (see #159). It passes the tests.

@jorisvandenbossche and @brendan-ward , I think I addressed the issues. OK to merge?

Thanks a lot @caspervdw !

(BTW, I recently experimented with those multithreading capabilities again a bit in dask-geopandas -> https://github.com/jsignell/dask-geopandas/)

Thanks! @jorisvandenbossche maybe we should have a hangouts session sometime about this dask integration. I have this work project at github.com/nens/dask-geomodeling that also parallelizes geopandas.

@caspervdw for some reason I only notice your comment now, but: certainly interested in a hangout chat about dask integration!


Add scoped topics, suback response topic before publish

Distinguishes between scoped topics (operations other than enrollment) and non-scoped topics (enrollment response will contain the scope suffix for later operations)
Matches correlation id from the mqtt correlation-data to pair the subscripbe with its acknowledgement from the mqtt broker
various fixes and tweaks
deletion of some unused/redundant codec
made state store in-memory only to simplify (will add persistence back later)

For 'ainfo_resp' messages, if the Correlation Data matches the 'en,the client should parse the message and update the agentinfo state.

what is 'en?

Refers to: src/extensions/agent_modules/cloud_communication/eg_mqtt_broker_client/src/adu_agent_info_management.c:65 in 4720e51. [](commit_id = 4720e512a20cf4eb0d01d8f7f504bbe837449c27, deletion_comment = False)

@brief Implements the Device Update agent state store functionality.

I could use another pair of eyes on this

Refers to: src/extensions/agent_modules/shared/state_store/src/agent_state_store.c:3 in 4720e51. [](commit_id = 4720e512a20cf4eb0d01d8f7f504bbe837449c27, deletion_comment = False)

For 'ainfo_resp' messages, if the Correlation Data matches the 'en,the client should parse the message and update the agentinfo state.

what is 'en? Oh, enrollment.
Refers to: src/extensions/agent_modules/cloud_communication/eg_mqtt_broker_client/src/adu_agent_info_management.c:65 in 4720e51. [](commit_id = 4720e51, deletion_comment = False)

No actually it's a serious typo--I think I was trying to say matches, then the client but I was typing way to fast with probably some editor key-seq macros mixed in.

merged up to top pr stack that was merged to topic


Argspec

Add a macro for extracting arguments from an mruby interpreter …
mruby calls mrb_raise which unwinds via longjmp if the args passed to
a function do not match the spec passed to mrb_get_args instead of
validating the argspecs declared on function register before delegating
to our Rust implementation. See mruby/mruby#4688.
This is not ideal because unwinds via longjmp do not let Rust clean up
resources (like RefCell borrows). This causes bugs like GH-243.
This commit introduces a macro that extracts arguments from the
mrb_state for a predefined set of argspecs. This code uses the argc
returned from mrb_get_args to determine which MaybeUninits are
initialized.
This macro is intended to be called before unwrapping the interpreter
from the mrb_state. At this point all stack variables are Copy so
unwinding is safe.
Fixes GH-200.
Convert Kernel to use arg extraction macro
Partial fix for GH-243.

cc @kenaniah


feat: set window.name in excalidraw app & also support target for excalidraw libraries

set window.name in excalidraw app so library installation always opens on same tab & also support target for excalidraw libraries
upstream PR: https://github.com/excalidraw/excalidraw-libraries/pull/79

[x] update readme/changelog

:tada:


Store browser sessions in database

This changes the session store to use an Active Record one, allowing us to store more data in the session than the cookie store allows us to.
Although we're not seeing problems at the moment, I think it's worth doing now as we're starting to create draft vaccination records and consents in the session, there's a risk the cookie will get too big.

Somewhere, maybe the SLSP, we documented that we store data on the client browser in the cookie, and had to explain that it's encrypted, etc. Gotta love over-documentation.


fix: BrowserAuthError Interaction_in_progress error

According to MSAL doc, the app should wait for handleRedirectPromise to resolve before calling any interactive API:
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/errors.md#using-loginredirect-or-acquiretokenredirect

It's not necessary to make msalAuthProvider async, we could add the check in a optimized way in all the authProvider methods like we did for ra-keycloak (See https://github.com/marmelab/ra-keycloak/pull/9)

It's not necessary to make msalAuthProvider async, we could add the check in a optimized way in all the authProvider methods like we did for ra-keycloak (See marmelab/ra-keycloak#9)

Yes, that should be a better solution!
We just need to nvoke handleRedirectPromise when the application uses redirect flows. When using redirect flows, handleRedirectPromise should be run on every page load..
I'll update this PR with the proposed changes shortly.

It's not necessary to make msalAuthProvider async, we could add the check in a optimized way in all the authProvider methods like we did for ra-keycloak (See marmelab/ra-keycloak#9)

@slax57, @djhi
Please take a look at the changes now when you have a chance.


Scrollable area width not calculated correctly in _setViewportEntered()

In the non-Observer case, if a scrollableArea is provided, the _setViewportEntered() method in addon/mixins/in-viewport.js appears to calculate the width of that area incorrectly.
What's in the code:
    const height = scrollableArea ? scrollableArea.offsetHeight + scrollableArea.getBoundingClientRect().top : window.innerHeight;
    const width = scrollableArea ? scrollableArea.offsetWidth : window.innerWidth;

What I think it should be:
    const height = scrollableArea ? scrollableArea.offsetHeight + scrollableArea.getBoundingClientRect().top : window.innerHeight;
    const width = scrollableArea ? scrollableArea.offsetWidth + scrollableArea.getBoundingClientRect().left : window.innerWidth;

Was this done intentionally?  I can try to come up with a simple test case that demonstrates why/how it's a problem, but to me this just looks like an obvious oversight.
Version
3.0.3
Test Case
Will provide if others agree this is a bug
Steps to reproduce
Expected Behavior

Actual Behavior

@snewcomer It looks like this is came in when the height calculation was updated in this commit: https://github.com/DockYard/ember-in-viewport/commit/4a11b4e70dd388b444c1e8fe0d1a7e4860df6700#diff-2c2e18a7ca7e78c5dad2dd4b0e42d657

@pfgilbert 💯 I think what you found is a bug.  I have a bug w/ right-left scrolling and this may help so thank you!
Lmk if you have time to put up a PR.  Otherwise I can get to it sometime later this week.


[KBM] Remap to a specific char instead of key

Description of the new feature / enhancement
Now you can remap keys & shortcuts using following format in config:
{"originalKeys":"165;219","newRemapKeys":"192"}],"appSpecific":[]}

I would like to set instead the fixed char to be replaced, not dependent on any specific keyboard.
E.g.:
{"originalKeys":"165;219","newRemapChar":"00B4"}],"appSpecific":[]}

Scenario when this would be used?
Some characters are not available at all in Windows (e.g. ` or ~ in Italian keyboard), so would be very useful to replicate same Linux behaviour.
See: https://github.com/ilpianista/itlinux-win-keyboard
More in general, setting a "fixed" char to be used it's definitely useful.
Supporting information
No response

i'd mark this as /dup #5668 as this would enable this concept.


Unable to view files

Brackets was working well for about a month.
Suddenly, it will not display file contents.  It just shows "Code the Web" screen.
It will open a project and show file explorer tree.  The menus will expand, but the menu items are unresponsive.  Close button is unresponsive.
No extensions are installed.
I reinstalled brackets and it worked for a couple days, but problem reappeared.
No approach to opening a file will get the contents, from the menu, from the tree or from the context menu in windows.

@MTyson Could you share snapshots or gifs of the issue, so that we can have a look at the issue.

As you told menus are not working. But by any chance can we get logs (bye pressing F12/Deubg > Show Developer Tools)? Apart from this can you try deleting AppData (For windows:- "%appdata%/Brackets")?


Arduino simualtor pages - 😀 - from Wokwi Arduino simulator

Hi There
Good day
Thank you for the wonderful library. I was quite excited to see it work on the first go.
Here is the link: https://wokwi.com/arduino/projects/309541392694116928

I would love to hear your feedback. We would be glad if we can also have a link in the ReadMe file for the readers of the ArduinoShiftIn library.
Wokwi Arduino simulator is free for all. Kindly feel free to share your feedback - https://wokwi.com
Thank you!

Thanks! Sure thing, I added a link to your awesome simulator!

Thank you. that's awesome. I will share the link for the other projects shortly. Will be glad to hear feedback on the simulator.


[Localization] Inconsistent localization handling for Node.js SDK Prompts.choice()

From documentation:

Internally, the SDK will call session.preferredLocale() to get the users preferred locale and will then use that in a call to session.localizer.gettext() to map the message ID to its localized text string. There are times where you may need to manually call the localizer. For instance, the enum values passed to Prompts.choice() are never automatically localized so you may need to manually retrieve a localized list prior to calling the prompt:

However, from prompts.ts if ListStyle is of type list, it uses args.localizationNamespace to localize choice options. Why is ListStyle.list's localization handling different from other list styles? Should "enum values passed to Prompts.choice() are never automatically localized" sentence in documentation be updated? Thanks.

That's a good point. I'll investigate to understand why we do it differently in that case. Probably has to do with yes/no prompts.

@Stevenic any updates on Prompts.choice() localization handling?

depreciated


How Should the Schemas Work

I'm submitting a...

[ ] Bug report
[ ] Feature request
[x] Question

Please how should one deal with the schemas?
Current behavior

Currently I define schema similar to how it is described in docs
Both migration table and  migration content are created in the public schema.
Behavior is the same regardless of the defined schema existence.
Expected behavior

Defined schema is created if one doesn't exist.
Migration table and content affect defined schema

Minimal reproduction of the problem with instructions
{
    "defaultEnv": "def",
    "def": {
      "driver": "pg",
      "host": {"ENV": "PGHOST"},
      "port": {"ENV": "PGPORT"},
      "database": {"ENV": "PGDATABASE"},
      "schema": {"ENV": "PGSCHEMA"},
      "user": {"ENV": "PGUSER"},
      "table": {"ENV": "PG_MIGRATION_TABLE"},
      "password": {"ENV": "PGPASSWORD"}
    }
}

I've tried both ENV link and exact value
What is the motivation / use case for changing the behavior?
Using data separation on schemas level
Environment

db-migrate version: 1.0.0-beta.15, 0.11.12
plugins with versions: not sure I have one
db-migrate driver with versions: pg 1.2.2

Additional information:
- Node version: 14.17.0
- Platform:  Mac

Others:

I'm also wondering how one configures what schema the migration tables are stored under. (I've got an automatic API generator and I'd like to keep the migrations tables out of where it's looking.)

It looks like this issue was reported back in 2017 (#459).

Same issue for me. Will this ever be tackled?


Created globals class to reference error messages

This PR has languished, @aawadall. Although I appreciate your desire to improve the code for this utility, it is seldom used. I'll close your PR.


[i2c] Reject Start/Stop if SCL changes too soon

Because the spec's data hold time is nominally 0, there are situations where an SDA change may arrive before an SCL change after CDC. This can give the appearance that a controller has sent a Start or Stop symbol, when the next bit was intended to be data, leading to unintended outcomes.
However, Start and Stop symbols have a significant required hold time, a period after the SDA transition when SCL is not allowed to change. Use some of this period to disambiguate data vs. control symbols. Require SCL to be held stable for at least thd_dat for a control symbol to complete decoding.
Note that thd_sta and t_buf must be longer than thd_dat, and thd_dat must be at least 1 cycle. Adjust the randomization of timing parameters in DV so this constraint is properly observed.
This is a cherry pick from the integrated_dev branch (PR https://github.com/lowRISC/opentitan/pull/21993), and it resolves https://github.com/lowRISC/opentitan/issues/22027.

Results from a reduced regression run (-i all -rx .1) suggest that this shouldn't fundamentally break I2C, as results are comparable to current nightly regression results:
|  Stage  |                   Name                    | Tests                                 |  Max Job Runtime  |  Simulated Time  |  Passing  |  Total  |  Pass Rate  |
|:-------:|:-----------------------------------------:|:--------------------------------------|:-----------------:|:----------------:|:---------:|:-------:|:-----------:|
|   V1    |                host_smoke                 | i2c_host_smoke                        |      22.820s      |     1.539ms      |     5     |    5    |  100.00 %   |
|   V1    |               target_smoke                | `                      |      2.134m       |    100.000ms     |     0     |    5    |   0.00 %    |
|   V1    |               csr_hw_reset                | i2c_csr_hw_reset                      |      0.680s       |    232.161us     |     1     |    1    |  100.00 %   |
|   V1    |                  csr_rw                   | i2c_csr_rw                            |      0.690s       |     17.578us     |     2     |    2    |  100.00 %   |
|   V1    |               csr_bit_bash                | i2c_csr_bit_bash                      |      3.110s       |    478.904us     |     1     |    1    |  100.00 %   |
|   V1    |               csr_aliasing                | i2c_csr_aliasing                      |      0.930s       |    316.068us     |     1     |    1    |  100.00 %   |
|   V1    |        csr_mem_rw_with_rand_reset         | i2c_csr_mem_rw_with_rand_reset        |      0.890s       |    112.455us     |     2     |    2    |  100.00 %   |
|   V1    | regwen_csr_and_corresponding_lockable_csr | i2c_csr_rw                            |      0.690s       |     17.578us     |     2     |    2    |  100.00 %   |
|         |                                           | i2c_csr_aliasing                      |      0.930s       |    316.068us     |     1     |    1    |  100.00 %   |
|   V1    |                                           | **TOTAL**                             |                   |                  |    12     |   17    |   70.59 %   |
|   V2    |              host_error_intr              | i2c_host_error_intr                   |      1.440s       |    207.951us     |     5     |    5    |  100.00 %   |
|   V2    |              host_stress_all              | i2c_host_stress_all                   |      8.777m       |     19.968ms     |     5     |    5    |  100.00 %   |
|   V2    |                 host_perf                 | i2c_host_perf                         |      8.808m       |     73.791ms     |     5     |    5    |  100.00 %   |
|   V2    |               host_override               | i2c_host_override                     |      0.620s       |     30.359us     |     5     |    5    |  100.00 %   |
|   V2    |            host_fifo_watermark            | i2c_host_fifo_watermark               |      1.690m       |     17.741ms     |     3     |    5    |   60.00 %   |
|   V2    |            host_fifo_overflow             | i2c_host_fifo_overflow                |      1.328m       |     2.678ms      |     5     |    5    |  100.00 %   |
|   V2    |              host_fifo_reset              | i2c_host_fifo_reset_fmt               |      1.130s       |    465.467us     |     5     |    5    |  100.00 %   |
|         |                                           | i2c_host_fifo_fmt_empty               |      14.970s      |    915.266us     |     5     |    5    |  100.00 %   |
|         |                                           | i2c_host_fifo_reset_rx                |      4.730s       |    145.919us     |     5     |    5    |  100.00 %   |
|   V2    |              host_fifo_full               | i2c_host_fifo_full                    |      1.409m       |     2.327ms      |     5     |    5    |  100.00 %   |
|   V2    |               host_timeout                | i2c_host_stretch_timeout              |      19.220s      |     4.309ms      |     5     |    5    |  100.00 %   |
|   V2    |           i2c_host_mode_toggle            | i2c_host_mode_toggle                  |      1.064m       |     31.661ms     |     5     |    5    |  100.00 %   |
|   V2    |             target_error_intr             | i2c_target_unexp_stop                 |      5.620s       |     1.426ms      |     5     |    5    |  100.00 %   |
|   V2    |               target_glitch               | i2c_target_glitch                     |      9.190s       |     8.720ms      |     1     |    1    |  100.00 %   |
|   V2    |             target_stress_all             | i2c_target_stress_all                 |      13.620s      |     16.242ms     |     0     |    5    |   0.00 %    |
|   V2    |                target_perf                | i2c_target_perf                       |      0.820s       |    618.288us     |     0     |    5    |   0.00 %    |
|   V2    |             target_fifo_empty             | i2c_target_stress_rd                  |      9.711m       |    100.000ms     |     2     |    5    |   40.00 %   |
|         |                                           | i2c_target_intr_smoke                 |      2.490s       |     1.817ms      |     3     |    5    |   60.00 %   |
|   V2    |             target_fifo_reset             | i2c_target_fifo_reset_acq             |      27.880s      |     10.034ms     |     4     |    5    |   80.00 %   |
|         |                                           | i2c_target_fifo_reset_tx              |      19.150s      |     10.115ms     |     5     |    5    |  100.00 %   |
|   V2    |             target_fifo_full              | i2c_target_stress_wr                  |      49.390s      |     35.896ms     |     5     |    5    |  100.00 %   |
|         |                                           | i2c_target_stress_rd                  |      9.711m       |    100.000ms     |     2     |    5    |   40.00 %   |
|         |                                           | i2c_target_intr_stress_wr             |      38.030s      |     23.345ms     |     4     |    5    |   80.00 %   |
|   V2    |              target_timeout               | i2c_target_timeout                    |      6.420s       |     8.435ms      |     5     |    5    |  100.00 %   |
|   V2    |           target_clock_stretch            | i2c_target_stretch                    |      2.821m       |     38.074ms     |     3     |    5    |   60.00 %   |
|   V2    |                bad_address                | i2c_target_bad_addr                   |      4.520s       |     3.020ms      |     2     |    5    |   40.00 %   |
|   V2    |            target_mode_glitch             | i2c_target_hrst                       |      2.530s       |     1.941ms      |     5     |    5    |  100.00 %   |
|   V2    |                alert_test                 | i2c_alert_test                        |      0.600s       |     15.809us     |     5     |    5    |  100.00 %   |
|   V2    |                 intr_test                 | i2c_intr_test                         |      0.640s       |     17.960us     |     5     |    5    |  100.00 %   |
|   V2    |           tl_d_oob_addr_access            | i2c_tl_errors                         |      2.780s       |    322.422us     |     2     |    2    |  100.00 %   |
|   V2    |            tl_d_illegal_access            | i2c_tl_errors                         |      2.780s       |    322.422us     |     2     |    2    |  100.00 %   |
|   V2    |          tl_d_outstanding_access          | i2c_csr_hw_reset                      |      0.680s       |    232.161us     |     1     |    1    |  100.00 %   |
|         |                                           | i2c_csr_rw                            |      0.690s       |     17.578us     |     2     |    2    |  100.00 %   |
|         |                                           | i2c_csr_aliasing                      |      0.930s       |    316.068us     |     1     |    1    |  100.00 %   |
|         |                                           | i2c_same_csr_outstanding              |      0.760s       |     38.601us     |     2     |    2    |  100.00 %   |
|   V2    |            tl_d_partial_access            | i2c_csr_hw_reset                      |      0.680s       |    232.161us     |     1     |    1    |  100.00 %   |
|         |                                           | i2c_csr_rw                            |      0.690s       |     17.578us     |     2     |    2    |  100.00 %   |
|         |                                           | i2c_csr_aliasing                      |      0.930s       |    316.068us     |     1     |    1    |  100.00 %   |
|         |                                           | i2c_same_csr_outstanding              |      0.760s       |     38.601us     |     2     |    2    |  100.00 %   |
|   V2    |                                           | **TOTAL**                             |                   |                  |    116    |   140   |   82.86 %   |
|   V2S   |                tl_intg_err                | i2c_tl_intg_err                       |      1.150s       |    419.290us     |     2     |    2    |  100.00 %   |
|         |                                           | i2c_sec_cm                            |      0.680s       |     41.173us     |     1     |    1    |  100.00 %   |
|   V2S   |           sec_cm_bus_integrity            | i2c_tl_intg_err                       |      1.150s       |    419.290us     |     2     |    2    |  100.00 %   |
|   V2S   |                                           | **TOTAL**                             |                   |                  |     3     |    3    |  100.00 %   |
|   V3    |      host_stress_all_with_rand_reset      | i2c_host_stress_all_with_rand_reset   |      4.464m       |     18.129ms     |     0     |    5    |   0.00 %    |
|   V3    |     target_stress_all_with_rand_reset     | i2c_target_stress_all_with_rand_reset |      1.055m       |     36.882ms     |     0     |    5    |   0.00 %    |
|   V3    |                                           | **TOTAL**                             |                   |                  |     0     |   10    |   0.00 %    |
|         |                                           | **TOTAL**                             |                   |                  |    131    |   170   |   77.06 %   |

I was somewhat unlucky with i2c_target_smoke, so I ran 50 seeds of that test again, and 6 of them passed. Not good at all, but not too low for V1.

Rebased on master, which should fix most CI failures unrelated to this PR


"Stelnica" is listed in the drop-down menu

Description:
When user writes "Stelnica" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Stelnica"
Expected results
The location appears in the drop-down menu as "Comuna Stelnica, ** IALOMIȚA**"


Multiplayer fix and update to Minecraft/Fabric

Made mod work in multiplayer
Updated to latest versions of Minecraft and Fabric

Gosh, I knew there was something sketchy about that toggle code. Thanks a lot!

Gosh, I knew there was something sketchy about that toggle code. Thanks a lot!


Registration

@JuliaRegistrator register

Registration pull request updated: JuliaRegistries/General/68747
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 2ece50676ee51e08775aa27e50b009a5dcc70677
git push origin v0.1.0


[WIP] F@H generator script

create a script to automate the project pipeline for folding at home

core.xml is not yet written

From CLI, arguments ideally will be:

RUN index to set up
YAML file for everything else

YAML file would ideally contain:

Project numbers for complex and solvent legs (e.g. 13400, 13401)
PDB, SDF for reference
SMILES list for targets

Directory structure must be (e.g. for ligand index):

complex: 13400/RUN{index}/{system,state,integrator,core}.xml
solvent: 13401/RUN{index}/{system,state,integrator,core}.xml

@hannahbrucemacdonald : These System objects are also still missing a MonteCarloBarostat!

@hannahbrucemacdonald : These System objects are also still missing a MonteCarloBarostat!

system generator is created here: https://github.com/choderalab/perses/blob/53bf910b65c17a21fc941850888c81f9f9928b36/perses/app/relative_setup.py#L285
pressure is defaulted as not None, and nonbonded method is defaulted as PME:https://github.com/choderalab/perses/blob/53bf910b65c17a21fc941850888c81f9f9928b36/perses/app/relative_setup.py#L246
pressure and barostat is only deleted from the system generator here (if vacuum phase, but only after complex/solvent are made): https://github.com/choderalab/perses/blob/53bf910b65c17a21fc941850888c81f9f9928b36/perses/app/relative_setup.py#L390
pressure and nonbonded method is set here (outside the class ): https://github.com/choderalab/perses/blob/53bf910b65c17a21fc941850888c81f9f9928b36/perses/app/setup_relative_calculation.py#L385
system for the HTF is pulled here: https://github.com/choderalab/perses/blob/53bf910b65c17a21fc941850888c81f9f9928b36/perses/app/setup_relative_calculation.py#L495
and the HTF copies the old system's barostat here: https://github.com/choderalab/perses/blob/53bf910b65c17a21fc941850888c81f9f9928b36/perses/annihilation/relative.py#L243
there might be a non-default set somewhere in the setup yaml, but i don't know where that is...perhaps it would be best if a default yaml could be put in app

@dominicrufa

Could we clean up the failures too?
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/runner/work/perses/perses/perses/tests/test_coordinate_numba.py", line 15, in <module>
    from perses.tests.test_geometry_engine import _get_internal_from_omm
  File "/home/runner/work/perses/perses/perses/tests/test_geometry_engine.py", line 46, in <module>
    small_molecule_forcefield = small_molecule_forcefield)
  File "/usr/share/miniconda/envs/test/lib/python3.7/site-packages/openmmforcefields/generators/system_generators.py", line 183, in __init__
    or nonperiodic_forcefield_kwargs (if it should be applied to non-periodic systems)""")
ValueError: nonbondedMethod cannot be specified in forcefield_kwargs;
                 must be specified in either periodic_forcefield_kwargs (if it should be applied to periodic systems)
                 or nonperiodic_forcefield_kwargs (if it should be applied to non-periodic systems)

Let me know if you want me to take a stab at these!


Fixed examples' accelerometer usage

The examples were using GetAngle instead of using GetAccel

#14 issue

#14 issue

@ProtoByter
Looks like a good catch!

@ProtoByter
Looks like a good catch!

Thanks

Thanks

np :)

np :)


Question: How to add DefaultStatTags to not standard Envoy metrics.

Hello! I've been trying to get more metrics from Envoy using IstioOperator configuration because the Standard Istio Metrics are not enough for our use cases. For instance, it would be pretty good having the number of active connections in all our istio-proxy containers. Following the documentation in here I added the following lines to the IstioOperator configuration:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  meshConfig:
    accessLogFile: /dev/stdout
    defaultConfig:
      proxyStatsMatcher:
        inclusionSuffixes:
          - "upstream_cx_active"

This produces the following output in the localhost:15000/stats/prometheus endpoint (many more similar lines appear with different cluster_name values):
# TYPE envoy_cluster_upstream_cx_active gauge
envoy_cluster_upstream_cx_active{cluster_name="BlackHoleCluster"} 0
envoy_cluster_upstream_cx_active{cluster_name="agent"} 16
envoy_cluster_upstream_cx_active{cluster_name="outbound|15010||istiod.istio-system.svc.cluster.local"} 0
envoy_cluster_upstream_cx_active{cluster_name="outbound|15012||istiod.istio-system.svc.cluster.local"} 0
envoy_cluster_upstream_cx_active{cluster_name="outbound|15014||istiod.istio-system.svc.cluster.local"} 0
...

This is ok, but I would be interested on adding some other tags to this metric, such as destination_service_name. I thought this would be automatically done by Istio. Since I saw that this wasn't happening automatically, I tried to add the tags by myself and added the following configuration to the IstioOperator following the documentation, but I did get the same result.
  values:
    telemetry:
      v2:
        prometheus:
          configOverride:
            gateway:
              metrics:
                - name: upstream_cx_active
                  dimensions:
                    destination_service_name: destination.service.name

Am I missing anything?

https://github.com/zirain/playground/blob/master/istio/iop/custom-metric.yaml

Sorry for the delay. I tested that as well and it didn't work; it's not exactly the same use case. In my case, I'm not creating a custom metric and then assigning some new dimensions to it, I'm just making an envoy metric visible. In that case, the new dimension is not added.


feat: implement metamask starknet snap

Description:
the PR is to add metamask starknet snap as a wallet options on the get-starknet UI and return a compilable wallet object to  get-starknet as well as the other wallets
the concept is same with the other PR: #195
Concept:
Due to MetaMask limitation, the SNAP itself can not directly inject a object into window instance, and snap itself is communicated via JSONRPC, SNAP can only return JSON-serializable response
https://docs.metamask.io/snaps/reference/rpc-api/
Hence we create a wallet object in get-starknet codebase, the object itself will setup as a bridge to communicate with SNAP via JSONRPC
We then runtime inject this object into get-starknet

Detail implementation

create a class object named MetaMaskSnap to communicate with the snap via the window ethereum provider
create a class object named MetaMaskAccount to extend the Account class from starknet package, and overriding execute, signMessage, declare with MetaMaskSnap
create a class object named MetaMaskSigner to implement the SignerInterface interface from starknet package, and implement all member methods with MetaMaskSnap
create a class object named MetaMaskSnapWallet to implement the same API as IStarknetWindowObject

when enable method trigger, it will request user to install starknet snap into metamask if not installed

inject MetaMaskSnapWallet when getAvailableWallets, getPreAuthorizedWallets, getDiscoveryWallets, getLastConnectedWallet method are consuming
enhance example page to demo the integration

@stanleyyconsensys
It seems that you add the snap implementation into get-starknet code.
starknet_metamask should be injected from the snap itself.

hould be injected from the snap itself.

hi @naorye2 thanks for the review
there is no way to injected from the snap like other wallet
such as
return a account object or injected the account object into window object
as snap is a JS script that run on metamask, it act like a serverless API, hence, the script itself cant inject anything
Plus
snap can be only communicate via rpc, means the snap will be able to return any non hashable response (such as account object)

@stanleyyconsensys got it. I suggest the following:

Your wallet implementation must be hosted on your behalf so you eventually will provide a url for a script.
get-starknet will hold a reference to that script (under discovery.js).
get-starket will check whether metamask loaded with snaps support (the code that you added under MetaMaskSnap.GetProvider) and if it is, it will load the script of yours.
From that point, starknet_metamask will be injected by your script.

WDYT?

account object or injected the

@naorye2
thank you for the advice
it is a good idea
but may i ask how about get-starknet adding a npm package from us, in that way, user does not required to load our jS via internet on the fly, instead, it compile together with get-starknet
the major different is, when we using async load script, there may be some issue from user ENV, may blocking the access of the script
with npm package, get-starknet would just need to maintain the version of our package, but it may also create a dependency on us
how does it sound like to you?

@stanleyyconsensys
This is sounds like a better solution :)
However, this package will be bundled along the build process into a separate file that will be imported dynamically according to metamask existence and snap support.

@stanleyyconsensys
I am working on a PR for metamask starknet brisge as we spoke.
Currently I am using the logic you wrote but than I realized that this logic is missing async loading of metamask (in case metamask loads minute after get-starkent, we will miss it).
I saw that approach: https://github.com/MetaMask/detect-provider
Is it good enough for metamask detection (than we will use provider && hasSnapSupport(provider))?

@stanleyyconsensys
https://github.com/starknet-io/get-starknet/pull/208

@naorye2 , the detectEthereumProvider can be useful if the client browser only install metamask,
but in some edge case, if the user has installed some wallets which overrided the Ethereum object, it will lead to using the wrong provider
i would suggest you can combine both way to inject the provider, may i ask where will you inject the bootstrapMetamaskBridge?

@stanleyyconsensys
According to @metamask/detect-provider, it verifies whether it is metamask.

Can you review my implementation?
bootstrapMetamaskBridge is called in packages/core/src/main.ts in getStarknet() function.

i think you can try that way first, and i will test it by enabling Phantom and coinbase wallet later

@naorye2 here is the consensys package for supporting get-starknet,
https://www.npmjs.com/package/@consensys/get-starknet
it is a dev version
we will release a stable version once the test is success

@stanleyyconsensys
I integrated your package (dev version for the meanwhile).
Can you expose MetaMaskProvider?
Please review my PR https://github.com/starknet-io/get-starknet/pull/208.

Sure, let me export all the type and component for you

Handled here https://github.com/starknet-io/get-starknet/pull/208


Negative index in jax.numpy.take

import numpy as onp
import jax.numpy as jnp

print(onp.take(onp.arange(10), -2))
print(jnp.take(jnp.arange(10), -2))
print(jnp.arange(10)[-2])

prints

8
0
8

I don't know if that's related to #278. It appears that the index gets clamped to [0, size-1], when using take, but not with regular indexing.

Thanks for the report! I'm going to mark as a bug; JAX should support negative indices in the default mode.

As discussed in #278 it is hard to replicate the numpy behavior. But it would be possible to at least make sure that the result in the 3rd example above is also 0.

#278 explains why giving an error would be hard. But it doesn't seem to explain why clipping the index is easier than wrapping?

Clipping the index is what is implemented by the XLA compiler, which JAX uses.

Hello! Is this issue being worked on? I would love to contribute. This is my first issue on this project.

Hello! Is this issue being worked on or not? I would like to contribute to this issue

I just tried the snippet in the first comment with jax 44b1791b7aed840073 on a laptop (no GPU/TPU backend), and I get a consistent behavior:
$ cat test.py
import numpy as onp
import jax.numpy as jnp

print(onp.take(onp.arange(10), -2))
print(jnp.take(jnp.arange(10), -2))
print(jnp.arange(10)[-2])

$ python test.py
8
WARNING:absl:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
8
8

Does this issue requires a GPU backend to manifest? Or maybe it is fixed already?


Version

Hi, Can you please specify the versions of Python, Tensorflow and Keras compatible with this API?

Thanks for raising this. Yes, that would be helpful. I've added a note to the README and the documentation just now as part of https://github.com/faustomorales/keras-ocr/commit/6a1590f92867d45467ecfcf134f19b4cc50c3192. But, just to close the loop, this package supports Python >= 3.6 and TensorFlow >= 2.0.0. It uses tf.keras so a separate Keras installation is not necessary.


exclude_ordefault_methods (for CA1826) is not documented

https://github.com/dotnet/roslyn-analyzers/pull/5877#discussion_r805657034
It would be good to review all user options and make sure everything is documented.

This was fixed by https://github.com/dotnet/docs/pull/32945.


Clarification needed on index creation

Thanks for the Code lab.
In step 5  "Sort and filter data" user learns to create an index in the Firestore. The index talked about is price and numRating. However there is no explanation why in the demo app user can  filer on food and  city without creating this Firestore index?
Further explanation:
If I search for city Miami I get two hits. This does not require a Firestore index right.
There are two Miami one with coffee and one with pizza.
If I search for city Miami and food pizza I get one result.  This should require a Firestore index or??

@erikswed the behavior you're seeing likely has to do with our offline behavior.  When reading data, we can return some documents from the offline cache even without the proper indexes.  So since you created all the restaurants on this same device, you get seemingly impossible results when querying.
If use another device or just uninstall and reinstall the app, you'll see that those queries fail due to lack of index as expected.

Thanks yea that makes sense . I see now the setPersistenceEnabled is enabled by default in Firestore I was thinking it was not

@erikswed yes we enable persistence by default on Android and iOS, but not on Web.
Thanks for doing the codelab!  I am going to close this issue since it's working fine and I purposely didn't mention this in the text, but let me know if you think additional clarification is needed.


feat(module:input): provide nzFocus event

PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Feature
[x] Documentation content changes

What is the current behavior?

https://github.com/NG-ZORRO/ng-zorro-antd/issues/73
What is the new behavior?
provide focus event
Does this PR introduce a breaking change?

[x] YES
[ ] No

Other information

Coverage remained the same at 52.163% when pulling a620251ec5b4b01fd107f4e48ea44093a4151a1d on giscafer:master into 530ae979e3ac55cb482b28a7078887c41ce99d76 on NG-ZORRO:master.

Coverage remained the same at 52.163% when pulling c304c33ef54609be7bcf22f371e70a6e6fb6f04d on giscafer:master into 530ae979e3ac55cb482b28a7078887c41ce99d76 on NG-ZORRO:master.

Would it better to merge into one commit? It would be cleaner in log and easier to revert.
And please follow this commit format, thanks
https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit

@vthinkxie ok, i  submitted separately


feat(evm): support multiple languages for deriveKey cheatcode

Motivation

Resolves #4560.
Solution

Add support for other languages' wordlist in https://github.com/summa-tx/bitcoins-rs/pull/119/.

<EMAIL_ADDRESS>contains non-english wordlists. Thanks @0xYYY!

pending another fix https://github.com/summa-tx/coins/pull/120

hey @0xYYY — do you plan on getting back to this soon?

hey @0xYYY — do you plan on getting back to this soon?

yeah, plan to finish this around next week

added a standalone derive_key_with_wordlist  function, bumped ethers version, rebased on master, all tests have passed, ready for review
cc @Evalir @mattsse

hmm seems we have some tests failing?

yeah, but weirdly can't see any details about why the tests failed

hmm seems we have some tests failing?

seems like the failing tests have ben re-ran and all tests have passed now

yup guessed they were just outage/unrelated failures, nice! will wait for matt to merge—nice work :)

hey @0xYYY — do you think we could rebase this? sorry for the extra work, but we recently refactored the abigen part of cheatcodes so will need to redo that bit

hey @0xYYY — do you think we could rebase this? sorry for the extra work, but we recently refactored the abigen part of cheatcodes so will need to redo that bit

no prob, on it

will wait for matt to review/merge—nice work :)

hi @mattsse, pls let me know if there are any changes that i can make to push forward this pr, thx

thanks @Evalir for pushing this over the line


Pass arguments when invoking eb:config a second time in deploy task

This fixes the issue I described in issue #12.

@jabr is this working for you?  I haven't gotten back to revisit and deploy to the new container yet, happy to merge on your approval.

Hi @rosskevin, this works for me.  Without @jabr changes, the show_config and deploy tasks do not use the provided environment and version.  Can we get an official release soon?
Thanks for an awesome gem.

@onomated v1.1.3 pushed

Sorry for the delayed response, but yes, I've been using this branch without issue for a while now.

Thanks @rosskevin!


Does it support IPv6 ?

Thanks for wanting to report an issue you've found in redis-py. Please delete this text and fill in the template below.
It is of course not always possible to reduce your code to a small test case, but it's highly appreciated to have as much data as possible. Thank you!
Version: What redis-py and what redis version is the issue happening on?
Platform: What platform / version? (For example Python 3.5.1 on Windows 7 / Ubuntu 15.10 / Azure)
Description: Description of your issue, stack traces from errors and code that reproduces the issue

@andymccurdy This issue makes no sense. Please close as irrelevant and invalid.


LMDB should resize map based on how full it is

Calculate how full an LMDB map is as a percentage and trigger resizing once it exceeds a certain level, ex. 80%.

The existing logic resizes the map only whenever the next write operation will exceed the size of the map. This seems to work ok on Linux, but not on MacOS. On MacOS the LMDB Store will randomly throw a "MDB_BAD_TXN: Transaction must abort, has a child, or is invalid" error when under a high concurrent write load.

If using this logic is then requiredSize needed at all?

Only if requiredSize is considerably bigger. Maybe a massive literal?


Can't install the mod

I can't install the mod from the zen mods page. When I press the install button, it dims out, but nothing much happens after that. The button stays dimmed out, doesn't say uninstall theme like other mods. When I refresh the page, I get a 'install theme' button again. Tried restarting without add-ons, adding a new profile, reinstalling without installing current version.

facing the same issue

same here.

Same here (linux).

Same issue.  The button seems to be completely disabled, and the preview image on the page is now broken.
This was working the other day when I installed Zen on another machine. Tried installing it last night and it didn't work anymore. Same thing this morning on a different machine/OS.

The page is removed now. Don't know what is the issue and why it is not being fixed?

Temporary Fix:

Download the theme's CSS file from the repository.
Open Zen browser's default profile folder:

Type about:profiles in the URL bar.
Click the Open Folder button.

Create a new folder inside chrome/zen-themes and paste the CSS file there.
Add the following line to the zen-themes.css file inside the chrome folder to import the theme:@import url("file:///{path_to_the_css_file}");

Replace {path_to_the_css_file} with the actual path to the CSS file, ensuring to include file:/// before the path.
Save the changes and restart the browser.

I switched to Super URL Bar instead. It has similar features. That may be why the Zen team is neglecting this one.


prefer-template

Current dependencies on/for this PR:

main

PR #147   👈

This comment was auto-generated by Graphite.


Uncaught TypeError: Invalid Point: ((28, 0), 0)

[Enter steps to reproduce below:]

Have some custom rules in my .nav-marker-rules:

#marker-rule: /(loaderdata)/i||%1||Markers||ext=hjson
...

Trying to use the plugin with an HJSON file. The file looks basically like this:

{
  //Introduction
  propA: "value",
  propB: [
    "value1",
  ],
  ObjectA: {
    loaderData:
      '''
      '''
    ,
    }
}

Restart ATOM
See Nav pane. If I click on the "loaderData" item, it gives me that pointer error. If I click on the small dot beside it, it does highlight the correct line number.

 Can I kindly request to have this checked out? Simply put, clicking on the bookmarks saved (by alt-clicking on a line) and generated using the .nav-marker-rules gives me the pointer error and thus preventing it to work and unfortunately, rendering the plugin useless :(. It seems to work with JS files.

The solution in the other thread works at least for now.

This  problem
temporarily solved by removing 270 line in
atom-nav-panel/lib/nav-view.coffee


fix: typo in HMR event

Please run yarn build locally and fix these errors:

Please run yarn build locally and fix these errors:


Short description of repo and tags need an update

The short description of the repo should be corrected. Instead of

A complete implementation of the SZZ algorithm as described by Zeller et al's.

I suggest

An implementation of the SZZ algorithm, i.e., an approach to identify bug-introducing commits.

The reference to the work by the SZZ authors is anyway first in the README.md... on top of that "Zeller et al." is wrong, since it's actually "Śliwerski et al."
Also, I suggest adding a few more tags to support findability of this repo from the software engineering research community. I suggest adding: "defect-prediction", "mining-software-repositories", and "software-engineering-research".

I agree. This change improves the description clarity. Furthermore, I think the description can also be a little bit misleading, since the SZZ version implemented should be the one based on the improvement done by Williams and Spacco and not the original version by Śliwerski et al.
Adding some more tags is a good idea as well. Making the project easier to find is definetely a good idea IMHO.

Absolutely. Do we have more tags than defect-prediction, mining-software-repositories and software-engineering-research?

I think we can start with these. I suggest implementing these minor changes asap.

I've made some updates regarding this. Please confirm if this is what you excpected @mrksbrg.

Thank you. One last thing:

The short description of the repo should be corrected. Instead of

A complete implementation of the SZZ algorithm as described by Zeller et al's.

This still needs to be changed. If you prefer not to change it to:

An implementation of the SZZ algorithm, i.e., an approach to identify bug-introducing commits.

I would suggest to just change Zeller et al. to Śliwerski et al. since otherwise the reference is wrong.

No, I think the:
An implementation of the SZZ algorithm, i.e., an approach to identify bug-introducing commits.
is better.


Problem with some of the folder names in Rainbow-Code/p5.js/ The repository becomes undeletable on windows!

as title says...some folders in that path ends with a space, and windows is unable to delete them. The only way to delete them was to manually do a painstaking process in cmd.
PLEASE SOMEONE FIX THIS ASAP

I'm trying to fix it, i can't clone repo to windows, because whitespace at the and

I can take a look at this now. . one moment. . .

I tried to rename folders and push to my repo, but whitespace %20 is still there. Maybe we must delete folders and create new ones with same files

Did I get them all or are there still some? It's hard to see which ones have spaces so feel free to add a list to this thread.

2.3_0_p5.js_JavaScript_without_objects
2.3_1_p5.js_JavaScript_with_objects
3.1_p5.js_Introduction_to_Conditional_Statements
3.2_p5.js_The_Bouncing_Ball
3.3_p5.js_Else_and_ElseIf_and_and_or
3.4_1_p5.js_Boolean_variables
3.4_p5.js_Boolean_variables
4.2a_Nested_loops
4.2b_Nested_loops
5.2_p5.js_Function_parameters_and_arguments
5.3_p5.js_Functions_and_return
7.2_p5.js_Creating_HTML_elements_with_JavaScript
7.4_p5.js_Handling_DOM_events_with_callbacks
7.5_p5.js_Other_events_and_inputs
7.8_p5.js_CSS_Selectors
7.9_p5.js_select_selectAll_with_CSS_selectors

Ok, should be good now! Let me know and I'll close.

It's OK now, thank you :)


ci: Add macos runner

Add a CI runner for macOS. On macos, we need to run rustc separately for each target in the Cargo.toml. The reason is that we currently pass extra linker arguments to rustc. This is not possible if multiple targets need to be build.

Compilation on macOS currently fails for the tests, as we pass extra arguments:
error: extra arguments to `rustc` can only be passed to one target, consider filtering
the package by passing, e.g., `--lib` or `--bin NAME` to specify a single target

== Compilation error in file lib/rustler_test.ex ==
** (RuntimeError) Rust NIF compile error (rustc exit code 101)
    (rustler 0.22.2) lib/rustler/compiler.ex:36: Rustler.Compiler.compile_crate/2
    lib/rustler_test.ex:6: (module)
    (stdlib 3.16.1) erl_eval.erl:685: :erl_eval.do_apply/6

For this to work, we need to call cargo build/cargo rustc separately for each target.

Compilation on macOS currently fails for the tests, as we pass extra arguments:

I work around that with 65d4171. For macOS, each target (bin or lib) is compiled separately. This feels kind-of hacky.

Maybe someone from @rusterlium/core can give some early feedback here.

I rebased on #439 to check if the runner works on that branch.

As this no longer requires changes to Rustler.Compiler and simply adds a runner, I will merge this.


[WIP]: NLU shouldn't be stochastic

For now the seed mechanism in the NLU is broken in many ways:

seed should not be in the config it rather should be in the shared_resources (or at least somewhere in the __init__ of the ProcessingUnits)
right now because of a the following scikit-learn bug, the intent classification can't be deterministic: https://github.com/scikit-learn/scikit-learn/pull/13422)

Roadmap

wait for the 0.21 release of scikit-learn which will include the SGDClassifier fix
change the current NLU api so that the random seed is not in the configuration anymore

This is work in progress I have a branch with almost every ready ;)

Exact duplicate of #779


Some ways to store fired query/result

So that we may analyze users' input

hey, what's in mind here, like a browser storage for users to use it somehow or storing everyone's requests in a central DB after making users accept an agreement, mongo etc.?

Yes. Tested with gsheets but it is too difficult to auth (need oauth)
I will now use Firebase. (the code will only enable in searchgpt-demo repository which is private.)

Thanks a lot for the response, sounds like a good plan and the outputs are really showing potential it seems from what you wrote  :)

Thank you @eren23
And the issue is done.


Rework collection to Registries

I need to unify how everything is being collected/loaded/registered. I have several implementations for doing the same thing, which is really confusing.

Fixed in #55


Add transaction (a list of deltas) as a primitive for applying sets o…

…f changes
This will also line up with removing "AddQuadSet" and help with some more intricate types of updates. It's not full-query-capability yet, but we'll need the primitive to do that anyway.

LGTM

LGTM


Add QuickSwap KIRO-MATIC and LMT-ETH

Removed the LMT-ETH farm.
Moved KIRO-MATIC to the dual farm section and added the rewardB property.
Ready for review


[BUG] Incomplete dependency chart installation after upgrading 1.0.3 to 1.1.0 and master-head.

Describe the bug

After upgrading Harvester from v1.0.3 to v1.1.0 or master-head, whereabouts CRD wasn't installed correctly.
Storage-network will not work properly without whereabouts CRD.
If user configure storage-network, Longhorn will not able to start instance-manager according incorrect whereabouts' crd.
To Reproduce
Steps to reproduce the behavior:

Install harvester v1.0.3 and upgrade to v1.1.0 or above.
Check Whereabouts IPPools is missing
kubectl get crd | grep ippools (we should see ippools.whereabouts.cni.cncf.io but we cannot)

Expected behavior

We have ipools.whereabouts.cni.cncf.io CRD
Support bundle

Environment

Harvester ISO version: v1.0.3 and upgrade to v1.1.0 or above
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.
But we can see daemonset is installed correctly.
$ kubectl get daemonset -A | grep whereabouts
kube-system                harvester-whereabouts                         4         4         4       4            4           beta.kubernetes.io/arch=amd64                     4h53m

Workaround
Before configuring storage-network, please apply these two CRDs
If you already configured storage-network, please disable storage-network and apply these two CRDs.
And re-configrue storage-network again and check if the Longhorn instance managers are ready without errors.

https://github.com/harvester/harvester/pull/3181 is a workaround. I create a following-up issue to find the root cause.

Verified fixed on master-7c1f4a24-head (11/22). Close this issue.
Result
After successfully upgrade 3 nodes Harvester from v1.0.3 to latest master (11/22)

Execute  kubectl get crd ippools.whereabouts.cni.cncf.io without errors.

harvester-node-0:~ # kubectl get crd ippools.whereabouts.cni.cncf.io
NAME                              CREATED AT
ippools.whereabouts.cni.cncf.io   2022-11-22T04:23:10Z

The Harvester Storage Network setting's status is True and the type is configured.

harvester-node-0:~ # kubectl get settings.harvesterhci.io storage-network -o yaml
apiVersion: harvesterhci.io/v1beta1
kind: Setting
metadata:
  annotations:
    storage-network.settings.harvesterhci.io/hash: 56248882bd3ee9a76ecee5fd7253fddd42d16a55
    storage-network.settings.harvesterhci.io/net-attach-def: harvester-system/storagenetwork-pngqf
    storage-network.settings.harvesterhci.io/old-net-attach-def: ""
  creationTimestamp: "2022-11-22T04:16:48Z"
  generation: 11
  name: storage-network
  resourceVersion: "201273"
  uid: 7869639a-904e-4f48-a53b-d6636d3a037b
status:
  conditions:
  - lastUpdateTime: "2022-11-22T06:26:21Z"
    reason: Completed
    status: "True"
    type: configured
value: '{"vlan":1,"clusterNetwork":"mgmt","range":"<IP_ADDRESS>/24"}'

Longhorn instance-managers are working.

harvester-node-0:~ # kubectl get pods -n longhorn-system -l longhorn.io/component=instance-manager -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: Pod
  metadata:
    annotations:
      cni.projectcalico.org/containerID: 3a7f390982daf111eec3f6ffed3977b785362f19a3467f5461dc243744531190
      cni.projectcalico.org/podIP: <IP_ADDRESS>/32
      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32
      k8s.v1.cni.cncf.io/network-status: |-
        [{
            "name": "k8s-pod-network",
            "ips": [
                "<IP_ADDRESS>"
            ],
            "default": true,
            "dns": {}
        },{
            "name": "harvester-system/storagenetwork-pngqf",
            "interface": "lhnet1",
            "ips": [
                "<IP_ADDRESS>"
            ],
            "mac": "22:0f:21:19:92:a8",
            "dns": {}
        }]
      k8s.v1.cni.cncf.io/networks: '[{"namespace": "harvester-system", "name": "storagenetwork-pngqf",
        "interface": "lhnet1"}]'
      k8s.v1.cni.cncf.io/networks-status: |-
        [{
            "name": "k8s-pod-network",
            "ips": [
                "<IP_ADDRESS>"
            ],
            "default": true,
            "dns": {}
        },{
            "name": "harvester-system/storagenetwork-pngqf",
            "interface": "lhnet1",
            "ips": [
                "<IP_ADDRESS>"
            ],
            "mac": "22:0f:21:19:92:a8",
            "dns": {}
        }]
      kubernetes.io/psp: global-unrestricted-psp
      longhorn.io/last-applied-tolerations: '[{"key":"kubevirt.io/drain","operator":"Exists","effect":"NoSchedule"}]'
    creationTimestamp: "2022-11-22T06:26:24Z"

Create and start a VM without errors.

Test Information

Test Environment: 3 nodes Harvester remote kvm machines
Harvester version: master-7c1f4a24-head

Verify Steps

Install harvester v1.0.3 with 3 nodes.
Upgrade to master-head with this PR.
Execute kubectl get crd ippools.whereabouts.cni.cncf.io without errors. (We need to have this CRD)
Create and setup storage-network in the harvester without errors.
Check Longhorn instance-managers are working.
Create and start a VM without errors.


Export all the properties we need from resin-vars so there's no need for other places to parse the config file

A pushed some changes which are only about cosmetic git log:

removed some conflict entries
add SOB
minor tweaks

@agherzan was this meant to be merged via versionbot in order to have the changelog entry added?

No @Page- . For now versionist is ran manually when we want to release.


PSRDADA header changes

I'm testing TransientSearch + ringbuffer now on ARTS0. Turns out that sampling_time is not set: TransientSearch itself doesn't set it and neither does readPSRDADAHeader in AstroData. Could you add it to the header keys to be read? Preferred name for the key is TSAMP, as we use that already.
I also request changing NCHANNELS to NCHAN, as the latter is required when using e.g. dada_dbdisk for writing raw data to disk - that way we don't have to put the same parameter twice in the header.

Just changed CHANNELS to NCHANS and added TSAMP to the header reader. The code is not here but in AstroData, so you need to pull and compile that one to test the changes.
Also this is just the reader, so someone needs to update the writer too.
Let me know.

Could you make it NCHAN (i.e without the S). Rest seems ok, thanks,

Done.

Thanks!


Consider converting md-input to an attribute directive

Proposal:
Since md-input is enhancing an input element I think it's more appropriate to convert it to an attribute directive. My concern about using a component is that the actual input element is boxed in and hard to access if you need to add additional attributes to it - for whatever reason.
My biggest concern is integrating it with the new Forms API. Unless the md-input component takes a direct dependency on the Angular Forms module (REACTIVE_FORM_DIRECTIVES etc), I don't see how to easily add the necessary form attributes. This dependency seems undesirable - especially for non forms applications.
With the current design, how are you planning to support the following internally in md-input?
example:
<input [formControlName]="fistName" />

If md-input was an attribute directive it wouldn't have to know anything about Forms. However, with the current component design it seems like you will have to build an API around it to "ferry in" forms attributes.
Thoughts?
What is the use-case or motivation for changing an existing behavior?
More flexibility. Forms is probably just one example.

We would love to do this, but it is currently not possible; Angular does not offer a way to wrap a host element in additional DOM. We've been exploring solutions to this with the core team (see https://github.com/angular/angular/issues/7297), but so far we haven't come up with a solid approach.
We may end up refactoring input to do this and handle all of the "wrapping" with direct DOM APIs, but this is something we'd like to avoid if possible.

Wouldnt this problem also be solved by using <md-input-container> approach that was used in material 1?

Yes, that would solve the problem too.


Add indeterminate checkbox styles

Added styles for indeterminate checkbox state (matches _checked styles)

@coopbri
Thanks for your time creating this PR and resoving this issue. You rock!

Hey no problem, sorry I didn't extend the work (documenting indeterminate state etc.). Happy to keep that in mind for any future PRs. Cheers @cschroeter!


Duplicate classes for PR_P0DTC4

You seem to have duplicate classes for envelope small membrane protein:
http://purl.obolibrary.org/obo/PR_P0DTC4
http://purl.obolibrary.org/obo/vo/ontorat/PR_P0DTC4
thanks

It appears that this issue has been resolved. So I am going to close this.
Thanks.

Still in Version: 1.0.337


[dvsim] Introduce {self_dir} as variable

Introduce a new variable {self_dir} which contains the absolute path to
the Hjson file using this variable. This variable can be used in Hjson
files to produce a path to a file relative to the Hjson file the variable
is used in, making Hjson files relocateable.

LGTM, thanks!


[infra-web] Salt change for writing Safari plist configurations

As a workaround for enabling Safari Driver, we would like to copy a plist to ~/Library/WebDriver directory in LUCI Mac bots.
More details on the content of the list is here: https://github.com/web-platform-tests/wpt/pull/19846/files

/cc @nturgut Please assign priority.

I'm closing this issue since @digiter tested it on a bot and it didn't work as an alternative to enabling the safari driver.