Fix unknown types

Add documentation

The errors I'm seeing are
/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:108: ERROR - could not determine the type of this expression
  return goog.global['navigator'] || null;
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:211: ERROR - could not determine the type of this expression
  return navigator && navigator.platform || '';
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:211: ERROR - could not determine the type of this expression
  return navigator && navigator.platform || '';
                      ^^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:339: ERROR - could not determine the type of this expression
      goog.string.contains(navigator['appVersion'] || '', 'X11');
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:410: ERROR - could not determine the type of this expression
    version = arr ? arr[1] : '';
    ^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:410: ERROR - could not determine the type of this expression
    version = arr ? arr[1] : '';
              ^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:420: ERROR - could not determine the type of this expression
    if (docMode != null && docMode > parseFloat(version)) {
                                                ^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:425: ERROR - could not determine the type of this expression
  return version;
         ^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:467: ERROR - could not determine the type of this expression
  return doc ? doc['documentMode'] : undefined;
         ^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:467: ERROR - could not determine the type of this expression
  return doc ? doc['documentMode'] : undefined;
               ^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:520: ERROR - could not determine the type of this expression
  return goog.userAgent.ASSUME_ANY_VERSION ||
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:521: ERROR - could not determine the type of this expression
      goog.reflect.cache(
      ^^^^^^^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:571: ERROR - could not determine the type of this expression
goog.userAgent.DOCUMENT_MODE = (function() {
                               ^^^^^^^^^^^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:574: ERROR - could not determine the type of this expression
  if (!doc || !goog.userAgent.IE) {
       ^^^

/Users/yannic/Developer/YB-App/build/closure-library/closure/goog/useragent/useragent.js:577: ERROR - could not determine the type of this expression
  return mode || (doc['compatMode'] == 'CSS1Compat' ?
                  ^^^
``

@Yannic can you provide information on how to reproduce these errors?

I enabled 'reportUnknownTypes' to see if there are unknown types in my code and got about 200 errors in closure-library.

@concavelenz Do we want to try to fix these?  Seems like a bit of a lost cause to me...

Pada tanggal 11 Mar 2017 02.39, "Yannic Bonenberger" <
<EMAIL_ADDRESS>menulis:
Add documentation
You can view, comment on, or merge this pull request online at:
https://github.com/google/closure-library/pull/805
Commit Summary

goog.userAgent

File Changes

M closure/goog/useragent/useragent.js
https://github.com/google/closure-library/pull/805/files#diff-0 (72)

Patch Links:

https://github.com/google/closure-library/pull/805.patch
https://github.com/google/closure-library/pull/805.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805, or mute the thread
https://github.com/notifications/unsubscribe-auth/AY-ovfRhnOXT3rrVanhtHWdljMDGn5yYks5rkZjrgaJpZM4MZuO2
.

Pada tanggal 17 Mar 2017 11.13, "JARWATI"<EMAIL_ADDRESS>menulis:
Pada tanggal 11 Mar 2017 02.39, "Yannic Bonenberger" <
<EMAIL_ADDRESS>menulis:
Add documentation
You can view, comment on, or merge this pull request online at:
https://github.com/google/closure-library/pull/805
Commit Summary

goog.userAgent

File Changes

M closure/goog/useragent/useragent.js
https://github.com/google/closure-library/pull/805/files#diff-0 (72)

Patch Links:

https://github.com/google/closure-library/pull/805.patch
https://github.com/google/closure-library/pull/805.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY-
ovfRhnOXT3rrVanhtHWdljMDGn5yYks5rkZjrgaJpZM4MZuO2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805#issuecomment-287255589,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY-ovbmejF7KEMwIGiPC6yxiJom3ztInks5rmfpJgaJpZM4MZuO2
.

Pada tanggal 17 Mar 2017 11.14, "JARWATI"<EMAIL_ADDRESS>menulis:
Pada tanggal 17 Mar 2017 11.13, "JARWATI"<EMAIL_ADDRESS>menulis:
Pada tanggal 11 Mar 2017 02.39, "Yannic Bonenberger" <
<EMAIL_ADDRESS>menulis:
Add documentation
You can view, comment on, or merge this pull request online at:
https://github.com/google/closure-library/pull/805
Commit Summary

goog.userAgent

File Changes

M closure/goog/useragent/useragent.js
https://github.com/google/closure-library/pull/805/files#diff-0 (72)

Patch Links:

https://github.com/google/closure-library/pull/805.patch
https://github.com/google/closure-library/pull/805.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY-
ovfRhnOXT3rrVanhtHWdljMDGn5yYks5rkZjrgaJpZM4MZuO2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805#issuecomment-287255589,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY-
ovbmejF7KEMwIGiPC6yxiJom3ztInks5rmfpJgaJpZM4MZuO2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805#issuecomment-287255673,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY-ovTKNan_P1QYSBLVfD_p79jvYxSGoks5rmfp2gaJpZM4MZuO2
.

Pada tanggal 17 Mar 2017 11.16, "JARWATI"<EMAIL_ADDRESS>menulis:
Pada tanggal 17 Mar 2017 11.14, "JARWATI"<EMAIL_ADDRESS>menulis:
Pada tanggal 17 Mar 2017 11.13, "JARWATI"<EMAIL_ADDRESS>menulis:
Pada tanggal 11 Mar 2017 02.39, "Yannic Bonenberger" <
<EMAIL_ADDRESS>menulis:
Add documentation
You can view, comment on, or merge this pull request online at:
https://github.com/google/closure-library/pull/805
Commit Summary

goog.userAgent

File Changes

M closure/goog/useragent/useragent.js
https://github.com/google/closure-library/pull/805/files#diff-0 (72)

Patch Links:

https://github.com/google/closure-library/pull/805.patch
https://github.com/google/closure-library/pull/805.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY-
ovfRhnOXT3rrVanhtHWdljMDGn5yYks5rkZjrgaJpZM4MZuO2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805#issuecomment-287255589,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY-
ovbmejF7KEMwIGiPC6yxiJom3ztInks5rmfpJgaJpZM4MZuO2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805#issuecomment-287255673,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY-ovTKNan_P1QYSBLVfD_
p79jvYxSGoks5rmfp2gaJpZM4MZuO2>
.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/closure-library/pull/805#issuecomment-287255931,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY-ovWlo6Qwv9NYM2aqsf8lrkItwqxuQks5rmfr3gaJpZM4MZuO2
.

We can't land this internally, and it's only a problem using non-recommended options, so I'm going to close this PR.  Please reopen if you want to continue the discussion.


Adding EFO in bulk to curation app

I have added the required EFO and the respective link in the spreadsheet
https://docs.google.com/spreadsheets/d/1drot5vkiXYYfT_uk48Aec6WMB5YVqeGTVitEoMY05-8/edit#gid=0

@Santhi1901 what's the deadline for this please?

atleast 2 days before next data release

@ljwh2 it is still not added in the curation app

EFO release is now out including fix for the duplicate URIs so you should be able to add these now @ala-ebi @Santhi1901
Note EFO have some problems with the update to the OLS website (working on a fix) but should be available in the API


Fix destruction of subclasses of Object

free() and queue_free() were failing to call the destructor of the actual object type.
UPDATE: Causing issues in 3.0 while 2.1 seems to be fine with it. I'll research and report.
UPDATE: Now implemented more cleanly and with no issues so far.

Wait, this does not make any sense, if destructors are virtual, they should always be called.
What is the specific problem going on?

As you see, Object has a virtual destructor:
virtual ~Object();
so all the destructors above should be called.

If you look at the current implementation of memdelete(), it's calling the
destructor of the template argument, that is, T::~T().
Since the delete queue holds pointers to Object, when it is flushed,
memdelete() will call ~Object() for these, which won't call the destructors
of the rest of the hierarchy, despite them being virtual.
Now, since all the codebase assumes no RTTI available and C++ hasn't (yet)
a "placement destructor" (unusable anyway even when compilers finally get
it as we are stuck in C++03), the only way I found was adding a
pseudodestructor member function.
And now I think about it, it should call the base class' destructor as well
for a complete cleanup.
El 11 jun. 2017 11:56 p. m., "Juan Linietsky"<EMAIL_ADDRESS>escribió:

As you see, Object has a virtual destructor:
virtual ~Object();
so all the destructors above should be called.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/9095#issuecomment-307659569,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQCtjhM7CE1Pbbz5cCC-maQalUHQlbnks5sDGKrgaJpZM4Nz9hC
.

`
Current implementation is:
template
void memdelete(T *p_class) {
if (!predelete_handler(p_class))
	return; // doesn't want to be deleted
p_class->~T();
Memory::free_static(p_class, false);

}
`
As you see there is a call to predelete_handler(), this function is implemented for Object type in object.h , and it looks like this:
`
bool predelete_handler(Object *p_object) {
return p_object->_predelete();

}
`
This makes sure that the whole hierarchy is freed

Then derived classes should have a trivial destructor and perform all their
cleanup in their _predelete(), shouldn't they?
If that's the "contract", CollisionObject is not meeting it and probably
others neither. In fact, I found this while debugging certain issues with
physics.
And, in any case, I don't think human-writable code in _predelete() can do
everything a compiler-generated destructor will, namely calling every
member's destructors, so in the end members of no basic type won't be
destructed.
El 12 jun. 2017 2:42 p. m., "Juan Linietsky"<EMAIL_ADDRESS>escribió:

`
Current implementation is:
template
void memdelete(T *p_class) {
if (!predelete_handler(p_class))
return; // doesn't want to be deleted
p_class->~T();
Memory::free_static(p_class, false);
}
`
As you see there is a call to predelete_handler(), this function is
implemented for Object type in object.h , and it looks like this:
`
bool predelete_handler(Object *p_object) {
return p_object->_predelete();
}
`
This makes sure that the whole hierarchy is freed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/9095#issuecomment-307777860,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQCtm2DvhjPnZlVH7E_KxwOTS_OeEigks5sDTJBgaJpZM4Nz9hC
.

No, It's not a contract, It's just a workaronud for a C++ limitation and
used in very specific cases.
The problem here is that Node needs to remove itself from the scene tree
cleanly before being deleted, because if it gets removed at the destructor
of ~Node, then classes that derive from it have no way to know the node
exited the scene.
On Mon, Jun 12, 2017 at 10:03 AM, Pedro J. Estébanez <
<EMAIL_ADDRESS>wrote:

Then derived classes should have a trivial destructor and perform all their
cleanup in their _predelete(), shouldn't they?
If that's the "contract", CollisionObject is not meeting it and probably
others neither. In fact, I found this while debugging certain issues with
physics.
And, in any case, I don't think human-writable code in _predelete() can do
everything a compiler-generated destructor will, namely calling every
member's destructors, so in the end members of no basic type won't be
destructed.
El 12 jun. 2017 2:42 p. m., "Juan Linietsky"<EMAIL_ADDRESS>escribió:

`
Current implementation is:
template
void memdelete(T *p_class) {
if (!predelete_handler(p_class))
return; // doesn't want to be deleted
p_class->~T();
Memory::free_static(p_class, false);
}
`
As you see there is a call to predelete_handler(), this function is
implemented for Object type in object.h , and it looks like this:
`
bool predelete_handler(Object *p_object) {
return p_object->_predelete();
}
`
This makes sure that the whole hierarchy is freed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/9095#issuecomment-307777860,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALQCtm2DvhjPnZlVH7E_
KxwOTS_OeEigks5sDTJBgaJpZM4Nz9hC>

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/9095#issuecomment-307782647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z22UdUnLiLkQnso_UOouD5qH4Kyxlks5sDTcYgaJpZM4Nz9hC
.

OMG! You won't believe how silly I feel now!
I've done some tests with MSVC and GCC and both call the virtual destructors fine despite manually specifying the name of the destructor of the top of the hierarchy. Now it all makes sense.
What has been confusing me is that while I was trying to debug physics issues, with Visual Studio, I set a breakpoint at ~CollisionObject2D() and stepped through the call to ~T() inside a memdelete() for a RigidBody2D. Guess what? The debugger didn't hit the breakpoint although the destructor was being called, so I thought I had found the cause (or one of them) and started to misdeadly look at object destruction under a wrong assumption.


add argocd custom healthcheck lua script for ack resource

Add an example on how to enable custom health checks for ACK resources in ArgoCD.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Manually merging to keep the original commit
/hold

thanks for the review, please let me know anything I can improve.
BTW, I have to deploy it for testing.  it can take some time.

Thank you folks! @Julian-Chu take your time for testing it, we can merge as soon as you can validate it.

we have tested it for more then 3 weeks,  didn't find any issue in the healthcheck logic.
I have just updated the indentation in new commit.


Slow Git Pre-Receive Hook Performance

I am having a performance related issue with using Git hooks.  If I run the server with no hook, all is good.  If I run the hook locally and run against the file system for the push, the hook runs successfully and completes very quickly.  If I run on Bonobo, the CopyTo on line 97 of GitServiceExecutor.cs takes an exceptionally long time to complete on a call to git.exe with arguments "receive-pack --stateless-rpc "C:\GitRepoServer\Bonobo.Git.Server\App_Data\Repositories\HookTest".  After about 30 seconds or so, the command finishes and it continues normally.   For this test case, the hook is simply calling an executable that writes 10 lines to stdout and 10 lines to stderr and returning -1;  Presumably something isn't closing right, but I can't tell what.

Does it make a difference if you don't write to stderr?

It does not seem to from previous hooks that were doing more, but I'll verify tomorrow.On Jun 6, 2018 5:19 PM, Will Dean<EMAIL_ADDRESS>wrote:Does it make a difference if you don't write to stderr?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

Ok, actually, I just realized that the success/failure issue may be unrelated.  Looks like the file system push is now succeeding and not getting any log messages, so something odd is going on there that I need to troubleshoot.  Not sure what's going on with the Bonobo version going so slow though.

If you saw the previous message in e-mail, it was a dumb error on my part.  I hadn't renamed the file away from being a txt file after renaming it to post here.  So file system version is working again correctly, showing the return and responding quickly.  Bonobo does not respond quickly and allows it to succeed even though it should be failing.

Solved the failure to fail issue.  Apparently the old version of bash used in Bonobo requires the return be exactly 1 to be detected as a non-zero return.  Odd, but workable.  Still getting slow performance though.  This also seems to be an odd edge case as it also revealed a problem in TortoiseGit where the output ends up blank for each line of output even though it works in command line git.  (A blank line shows up for each line of output, but nothing is displayed in TortiseGit.)

Adding some more detail.  It appears that the git process itself is taking a long time to end.  I swapped the order of the copy and the WaitForExit and it takes a long time for WaitForExit to occur.  Perhaps it's something with the particular version of git being used that causes the hook to be called much more slowly or something that prevents it from detecting the exit from the hook.  Any thoughts?

I think Bonobo does use a very old version of Git (can't remember off-hand what it is) - I suspect it would be relatively straightforward to upgrade that as an experiment.

It's running 1.9.5 which is the newest version before the 2 cut over which involved a completely different environment type on Windows unfortunately, which is probably why it hasn't been updated yet.  It seems like it would take a pretty substantial amount of work to update it from what I can see.  Trying to swap up the environment was one of the first things I tried, but unfortunately it failed pretty hard (though I didn't yet have quite as good of an understanding of the underlying flow of Bonobo as I've been getting while working through this implementation.)  I know I ran in to issues with newline handling and the way that return codes are handled due to the older bash environments that are used.

Ok, well this is really odd.  Used Procexp to see the process tree and discovered something very unexpected... the issue is not that bash remains open after the process finishes, but rather that bash just sits there without starting execution for the entirety of the delay and then runs the hooks and finishes very quickly.  I'd been focused on the stdout stream, but it looks like it might be something about the stdin stream that is being problematic or else it's some severe issue with the version of bash itself.

Ok, think I have it now... it appears to be an underlying mintty bash shell issue, my best guess is that it is related to the ATI graphics driver issue mentioned here https://stackoverflow.com/questions/42888024/git-bash-mintty-is-extremely-slow-on-windows-10-os.  I was able to replace the bash.exe used by the server and the performance immediately improved (although it resulted in some other oddities now that the newline stuff changed around again).  Our main git server might not have an ATI graphics card though, so I might not actually have to worry about this one.  Will report back when I see if a non-ATI graphics card fixes the issue...

Awesome.  The ability of Unix-ported stuff to find weird corner-case behaviour in Windows never fails to impress!

Yeah, confirming that it works fine on the actual server we are using to run Bonobo (a VM with no ATI driver)... go bizarre corner cases!!!


[feature request] Better format for large transactions

Thank you for this package, I can't believe I was doing this stuff by hand for almost a year when this was available.
Now, I live in Chile and here the transactions can easily run into the millions. Usually I use a comma to separate millions from thousands, for instance:
2021-01-13	SOME TRANSACTION
	Expenses:SomeAccount    CLP 1,234,567.00
	Assets:Bank

With reckon I get:
2021-01-13	SOME TRANSACTION
	Expenses:SomeAccount    CLP 1234567.00
	Assets:Bank

Which is a little hard to read.
Do you think you could add support for placing comma separators in large transactions?

Hi @matiya, thanks for using Reckon, I'm glad you like it.  Yeah, I think adding thousands separators makes sense, I've got a branch that I'm working on for this.  I'll let you know when I have something for you to test.

@matiya I pushed reckon 0.7.2 that should add commas on output by default.  Let me know how it works.
Thanks

It works!
I ran the same command in version 0.7.1 and 0.7.2 and I get the following diff:
> 2021-04-17
83c99
<       Pasivos:Cuenta                 CLP 1014294.00
---
>       Pasivos:Cuenta                 -CLP 1,014,294.00

Thank you! This is a big improvement for my use case

Great!  Glad it's working and thanks for helping make reckon better.


Add files via upload

Please read and mark the following check list before creating a pull request (check one with "x"):

[ ] I read and followed the CONTRIBUTING.md guide.
[ ] I read and followed the New Feature Checklist guide.

Short description of what this resolves:

done

clear


Adjust MOTD notification placement

bottom left to top right, beside new contract button

Updated in 15/AUGUST update.


Default sort using sortDirection isn't working

Taking the column-sort example from the repo as an example.  Adding sortDirection: 'asc' does not sort the table as expected.  It does nothing.
const columns = [
      {
        name: "Name",
        options: {
          sort: true,
          sortDirection: 'desc',
        }
      },
      {
        name: "Title",
        options: {
          sort: false,
        }
      },
...

That's deprecated, that particular example probably needs to be updated. See the sortOrder option.

Please, @patorjk where I can find information about sortOrder option?
Thank you in advance.

Please, @patorjk where I can find information about sortOrder option?
Thank you in advance.

Hi, @nickraphael
Did you succeed to sort?

Hi, @nickraphael
Did you succeed to sort?

@mromauricio It's documented in the main documentation. You can also see an example here:
https://github.com/gregnb/mui-datatables/blob/master/examples/customize-columns/index.js

@mromauricio It's documented in the main documentation. You can also see an example here:
https://github.com/gregnb/mui-datatables/blob/master/examples/customize-columns/index.js

Hi, @nickraphael
Did you succeed to sort?

I sure did!  Just tested it.  Thanks!

Hi, @nickraphael
Did you succeed to sort?

I sure did!  Just tested it.  Thanks!


Why I get an assertion error in this example

I have a signal r which was evaluated(sampled) at time t and the sampling frequency is not constant. The data are:
r = np.array([119.78410766,<PHONE_NUMBER>2,<PHONE_NUMBER>8,<PHONE_NUMBER>4,
<PHONE_NUMBER>6,<PHONE_NUMBER>4,<PHONE_NUMBER> ,<PHONE_NUMBER> ,
<PHONE_NUMBER>6,<PHONE_NUMBER> ,<PHONE_NUMBER>6,<PHONE_NUMBER>5,
       115.673267  ,<PHONE_NUMBER>7,<PHONE_NUMBER>6,<PHONE_NUMBER>5,
<PHONE_NUMBER>2,<PHONE_NUMBER>6,<PHONE_NUMBER>8,<PHONE_NUMBER>5,
<PHONE_NUMBER>9])

t = np.array([-408.60214685, -367.98645179, -326.11763398, -283.30427476,
       -240.51508415, -198.71111261, -158.2850487 , -118.96667683,
        -79.99044514,  -40.53604325,    0.        ,   41.86292241,
         84.76209664,<PHONE_NUMBER>5,<PHONE_NUMBER> ,<PHONE_NUMBER>6,
<PHONE_NUMBER>8,<PHONE_NUMBER>4,<PHONE_NUMBER>6,<PHONE_NUMBER>9,
<PHONE_NUMBER>1])

plt.plot(t, r, label='data')
plt.legend()

In the t variable the distance between each sampling instance is between 39 to 42 and not constant and this made the fft inaccurate for me.
When I use nfft however, I get the following assertion error but I am not sure what my mistake is in using the nfft package.
from nfft import nfft
f = nfft(z, r)

AssertionError  Traceback (most recent call last)
 in
1 from nfft import nfft
----> 2 f = nfft(z, r)
~/.local/share/virtualenvs/tf-tRAPLeXL/lib/python3.6/site-packages/nfft/core.py in nfft(x, f_hat, sigma, tol, m, kernel, use_fft, truncated)
123
124     N = len(f_hat)
--> 125     assert N % 2 == 0
126
127     sigma = int(sigma)
AssertionError:

So I noticed the problem was that the number of samples was not a power of 2.


Geometry optimization using CCSD(T)/meta-GGA

Hi,
The documentation mentioned that we can optimize geometry using CCSD(T), but I don't know how to do that. Could you add an example for that?
And there is a NotImplementedError: meta-GGA when optimizing using meta-GGA. Does that mean we cannot calculate gradient using meta-GGA methods?

I didn't implement the geometry optimization interface for CCSD(T) method. CCSD(T) geometry optimization requires a few coding.  Here is the example.
https://github.com/sunqm/pyscf/blob/master/examples/geomopt/13-ccsd_t.py
Please note the CCSD(T) nuclear gradients code was not optimized. It will not be able to handle large systems.
meta-GGA gradients were not available in the current version.

Thank you. I saw that the gradient for CCSD(T) was labeled "slow", so yes, I will expect that it is not optimized.
When will you expect that these meta-GGA gradients be implemented?

MGGA gradients will not be in the next release (v1.6, by Oct 2018). Version 1.7 (alpha release in Mar 2019) may include it.

Hi,
I found numpy.einsum() is used in ccsd_t_rdm_slow.py. When I replaced all the corresponding lines by lib.einsum(), I observed the gradient calculation is accelerated by around 60%.
Is there any reason why lib.einsum() is not used by default?


Download QR Code.

https://github.com/rosskhanas/react-qr-code/issues/187

Hi @rosskhanas, I would like to add a download feature to this repository. Should I proceed with that?

@prafuldivani it is already possible, please check the demo: https://rosskhanas.github.io/react-qr-code/ :)


Faster conflict cache

Builds on #14915
The current code loops over all package versions we have had past problems with to see which ones are currently active. This branch checks which version of the package is active to see if we have a conflict for it. If resolution is dominated by a package with many versions, then this find operation should go from O(n) to O(1).

After fixing the bug, the performance numbers seem worse than master.  The added layer of indirection may be too expensive. One more thing to try before I close.

No it is not faster. Sorry.


Feature Request: Register the app to open GPM links

OS: Windows 10
Wondows 10 has an ability to open certain links directly in apps. It would be nice to use this feature to open GPM links (//play.google.com/music/*) inside the app. When someone shares a song to me and sends me a link, it opens in browser, whereas I would prefer it to open inside the app.

This can't be done because it requires you to validate the domain with Windows.  We can't prove we own the GPM domain so it won't open links in our app.  This is for safety reasons on windows

Oh, that's sad. Thanks for quick feedback.


I have "NetworkError"

I would like to report a bug. When I turn on my pc, a window show this message and its not count the pomodoro or the combos in habits habitica:
NetworkError: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://habitica.com/api/v3/user/'.
Can you help me?

@iseocruz Hi, please try to disable an re-enable the extension.

Right click on the extension icon and choose "manage extensions"

-Disable and enable the extension

let me know if it solves the issue!


Bundle for 0.3.3

Hi,
Are you planning to append bundled (compiled) version of application to the v0.3.3 release ? Manually building is not very convenient for some of my environments.
Thanks in advance!

Hey, thanks for reaching out.
We've altered our release workflow that's why it's missing for 0.3.3. Future releases will have the jar file attached.
I've attached 0.3.3 here.

Many thanks!


Yes, your several codes comes many problems ...

es5 please....

This module mainly targets Node.js, not the browser. It's up to you to transpile it with Babel if you want to use it in the browser. You can find a more detailed explanation here: https://github.com/sindresorhus/ama/issues/446
If you use Webpack, check out babel-engine-plugin, which transpiles only the dependencies that needs to be transpiled.
If you use Create React App, upgrade to Create React App v2. It supports automatic transpilation of dependencies, which will make this package just work.


Cover all commands with tests

Currently, only one command is covered with a simple test but the envoriment is ready to cover the other ones.

All initial token and system commands are covered.


Order batch

Adds order_batch to the blotter and factors out ordering helper methods, so one can generate the orders and give them to order_batch.

Coverage decreased (-0.03%) to 86.952% when pulling 446fe72504f56ab2948e92137d97e92b1f02564a on order_batch into 515db18793422d280d2dce8bb6512583bee06cbc on master.

@richafrank finished this round.  No major issues.  Had a couple questions about naming/docs for order_batch and a style note for some of the test refactoring.

Coverage decreased (-0.03%) to 87.07% when pulling e512ef8c3af447637343318707272e0613502a0d on order_batch into 4174a090d04920c0d90530ea455377093dd58d88 on master.

Coverage increased (+0.08%) to 87.183% when pulling a0955cf21422734815916b8c53389e8c8e641432 on order_batch into 4174a090d04920c0d90530ea455377093dd58d88 on master.

Coverage increased (+0.02%) to 87.145% when pulling 87d30056207dedefc8962d91a853ca7a355d4a8a on order_batch into 0e3b290cc15b308d6307c2d07901981f69df45dc on master.

Coverage decreased (-0.04%) to 87.09% when pulling a59b6787ada59bd961eecc3638a3c850237b479c on order_batch into 9ac957f8a13d7fef2c6910dcf5db10aef6a93160 on master.

Coverage decreased (-0.03%) to 87.097% when pulling 2878bb726d8f59fd7ce45366706644de7c1ade7a on order_batch into 9ac957f8a13d7fef2c6910dcf5db10aef6a93160 on master.

Coverage decreased (-0.04%) to 87.097% when pulling d50eee7ea354a0b6034edb5e41a7d4cb74ee0f26 on order_batch into 47651363c0ecb05cd01b0bd0020e2162dc7d77a3 on master.

Coverage increased (+0.08%) to 87.217% when pulling 7d963402e8422b9e0be177bae93924197e856c5a on order_batch into 47651363c0ecb05cd01b0bd0020e2162dc7d77a3 on master.

Coverage decreased (-0.04%) to 87.103% when pulling 381029ac1a77e09a48f4548ccd5bc1f17387bd12 on order_batch into 0848a8a4862fd8bbe7ba64654e6bc731b4b622b7 on master.

Coverage decreased (-0.03%) to 87.11% when pulling e674e4e26a56282bb1efca266ad97dd781234841 on order_batch into 0848a8a4862fd8bbe7ba64654e6bc731b4b622b7 on master.

Coverage increased (+0.02%) to 87.165% when pulling e674e4e26a56282bb1efca266ad97dd781234841 on order_batch into 0848a8a4862fd8bbe7ba64654e6bc731b4b622b7 on master.


⚠ ClamAV has degraded performance

In 243e402, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 74 ms

Resolved: ClamAV performance has improved in a659883.


Showing non-existant updates

Using 17.72 with WebMin 1.780 on Internet Explorer 11.
I updated 8 packages on Unbuntu, which were shown on the dashboard. When I reopen WebMin later the dashboard will initially show that no updates are required then, a few seconds later, show that 8 package updates are required. Going to the updates page shows no actual updates available.

Same would happen in the default theme. It's not theme issue. It's reported.
https://github.com/webmin/webmin/issues/282#issuecomment-188618520


Which file should I modify to add additional button to image viewer page?

I need to add an additional button to image viewer page which opens a radiology report editor in our app, but I am unable to locate the file to modify for doing that.

In latest master version you can make use of customizationService


Confirmation URL in Email Template not giving back link with subdirectory

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
My app sits in a subdirectory of the homepage e.g.  https://my-page.com/app. Therefore I obviously need the {{ .ConfirmationURL }} in the email template of my "confirm signup" settings to put the access token at the end of /app and not the base URL.
My email configuration looks to be correct (see first screenshot) but the link I get back when I sign up with a new user points to the base URL and puts the access-token there (see second screenshot). It seems to ignore the /app in the site URL. So I guess there's a bug in the creation of the .ConfirmationURL?
Expected behavior
To generate the .ConfirmationURL with the correct Site URL even with subdirectory apps.
Screenshots

Is this occurring on a live project? If not, what version of GoTrue are you using?

yes, in a live project thats deployed

hi @derseitenschneider, are you using a custom domain here?

hi @derseitenschneider, can you please provide a snippet of the code you're using for the signup? are you using the supabase-js library?

@derseitenschneider I think it's best if you could reach out to Supabase support as this appears to be an issue with your project and not with this open-source codebase. If we identify a bug, then we can create a fix immediately or open an issue here for tracking.


CSRF protect_from_forgery with: :null_session is skipped

Version: 1.2.0
Environmental Info:

Gems: devise (4.8.0), rails (<IP_ADDRESS>)
enable_standard_devise_support = true
protect_from_forgery with: :null_session

We have controller that is already using rails session for the authentication. We want to add token auth in addition. They will run in parallel to allow transition.
Adding include DeviseTokenAuth::Concerns::SetUserByToken to the controller works well, but CSRF is broken.
After debugging it, this is why it happens:

Request gets to the controller and we execute before actions
We set user locale. This will get current_user, but since it's a first time we get user, we authenticate.

When set_user_by_token is called, it sets @resource instance variable.

CSRF before action is executed

protect_from_forgery with: :null_session
When CSRF is invalid, handle_unverified_request is called

https://github.com/heartcombo/devise/blob/8593801130f2df94a50863b5db535c272b00efe1/lib/devise/controllers/helpers.rb#L254-L258

The session is reset and all good.

Controller action is executed

Controller requests current_user, which is nil because it was cleared in the previous step
set_user_by_token is called again to get user
Because we enable_standard_devise_support = true we check devise. https://github.com/lynndylanhurley/devise_token_auth/blob/6d7780ee0b9750687e7e2871b9a1c6368f2085a9/app/controllers/devise_token_auth/concerns/set_user_by_token.rb#L58
Devise auth is nil (correct and expected)
Then we get to this line https://github.com/lynndylanhurley/devise_token_auth/blob/6d7780ee0b9750687e7e2871b9a1c6368f2085a9/app/controllers/devise_token_auth/concerns/set_user_by_token.rb#L69
Because @resource was previously set and wasn't cleared by invalid CSRF, we authenticate user and ignore invalid CSRF token

Expected: Authentication should fail after session was reset
Actual: User is authenticated with invalid CSRF token.

A temporary patch
# config/initializers/devise_token_auth.rb

# https://github.com/lynndylanhurley/devise_token_auth/issues/1514
module DeviseTokenAuthCSRFPatch
  def handle_unverified_request(*)
    super.tap do
      @resource = nil
    end
  end
end

DeviseTokenAuth::Concerns::SetUserByToken.include DeviseTokenAuthCSRFPatch


Add TailwindCSS support to PHP+HTML files

Check for existing issues

[X] Completed

Describe the feature
Now Tailwind autocompletion works only in pure HTML files but not inside HTML code in PHP files.
If applicable, add mockups / screenshots to help present your vision of the feature
No response

This is available in today's preview release - v0.110.0.


Contributing back?

Hi, are you planning to contribute your changes back or ...?

Yes, but not in the near future as I don't have much spare time


Upgrade test-suite to support v2.0.0

For testing the AdministratorAdministration application which is updating to version 2.0.0, the following tasks and their subtasks needs to be completed.
All the tasks needs to be implemented in test-suite collection in postman, reviewed and sample run against server or mock server and push into develop branch.
Improvements to existing testcases

[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/96
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/97
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/98
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/99
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/100
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/101

Common changes to existing services to support v2.0.0

[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/102
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/103
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/104
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/105
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/106
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/107
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/108
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/109
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/110
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/111
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/112
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/114
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/130

Service Specific Updates for Existing services to support v2.0.0

[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/115
[ ] https://github.com/openBackhaul/AdministratorAdministration/issues/116

New services added

Lets close the issue after testing under jenkins pipeline


Install via NuGet workflow has issues

Microsoft.Services.Store.Engagement
I've added the NuGet version to my UWP app. The issue happens when you create the store package and try to install the app using the powershell script inside the appxbundle you get this error.
Deployment of package Microsoft.Services.Store.Engagement_10.0.18101.0_x64__8wekyb3d8bbwe was
blocked because the provided package has the same identity as an already-installed
package but the contents are different. Increment the version number of the package to be
installed, or remove the old package for every user on the system before installing this package.

I ran a Get-AppPackage Microsoft.Services.Store.Engagement powershell command and found that windows already has installed the engagement package at the windows level
Name              : Microsoft.Services.Store.Engagement
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 10.0.18101.0
PackageFullName   : Microsoft.Services.Store.Engagement_10.0.18101.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.Services.Store.Engagement_10.0.18101.0_x64__8wekyb3d8bbwe
IsFramework       : True
PackageFamilyName : Microsoft.Services.Store.Engagement_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok
Need a fix ASAP this is critical to our QA/QC process which is broken by adding the store engagement nuget. We build the app bundle on jenkins and the QA/QC install the app using the powershell script. After adding the store engagement nuget no one is able to successfully install the app using the powershell script without hitting this error.

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

ID: 23ac044a-c64e-126c-5381-55fdd8856549
Version Independent ID: df6632af-07d6-fcf9-9c47-ecd9a49c4a6f
Content: Engage customers with the Microsoft Store Services SDK - UWP app developer
Content Source: windows-apps-src/monetize/microsoft-store-services-sdk.md
Product: uwp
GitHub Login: @mhopkins
Microsoft Alias: mhopkins

Thanks for reaching out to the Microsoft developer documentation team. Unfortunately, we don’t have the resources to offer individual technical advice to the broad array of customers who use the documentation.
You may have success posting your question in the Windows developer forums or reaching out to Windows developer support.
Again, thanks for reaching out. Best of luck with this issue.

@Xansky Thanks i'll log my but over there.


Feature Request: Detect that secret decryption depends on decrypted secret

While trying out sops-nix I configured:
{
  sops = {
    age.sshKeyPaths = [ config.sops.secrets."ssh/key".path ];
    secrets."ssh/key" = { sopsFile = ./sops/ssh.yaml; };
  };
}

That is, I tried to make the SSH host key both a secret, and the key to decrypt secrets. This even worked with nixos-rebuild switch since I did this step by step and first added secrets."ssh/key". However, I noticed my mistake, and if I understood nix-sops correctly, this configuration will not boot.
nix-sops could be more helpful here, and check that the options referring to keys for secret decryption (age.keyFile, age.sshKeyPaths, gnupg.home, gnupg.sshKeyPaths) are actually not secrets. For example, if any of those paths start with /run/secrets, something is wrong, and probably worth at least a warning, maybe even failure.

Only problem is that just now we populate age.sshKeyPaths by default from sops and it might trigger false positives for folks that want to manage ssh host keys with sops-nix, but use than other sops decryption methods i.e. aws-kms/gpg/normal age keys.


ARTEMIS-853 Support for exclusive consumers

Alternative QueueImpl - Seperated logic without counters

@clebertsuconic as per your comment to look at an alternative QueueImpl with it having separate flow without counters for exclusive.
IMO i don't think this is a better approach, but i want to offer it to you.
There is an amount of logic that is almost similar but not re-usable or abstract-able (ive done what i could).
This is why i followed the same logic that MessageGroups does when a group already is assigned,
which is to override the consumer and then don't update the pos, as it made for a lot smaller change, less intrusive change following a pattern already done with msg groups.
Anyhow if you prefer this then im not dead opposed to this approach just don't think its better, but i offer it for your review.

I’m closing this as no further comments.


GEODE-8530: Fix for coredump during tx commit

Client is fixed in a way that ignores all regions enlisted within
transaction that client doesn't have configured. This behavior is
aligned with the java client, since same thing is done there.

Thanks for the review!


Expired forecasts causing problems?

Noticed that many regions are showing no data after 6 PM PST, possibly because of a lag between the latest NWAC forecast being published and the NAC receiving it?
Missing data:

Also realizing that we should probably be able to display that a forecast is expired and that's expected, like in the Olympics:

I don't think this is necessarily expired forecasts - it seems like the data is there. But I wonder if our date filtering in useAvalancheForecastFragment is using dates generated in the local timezone when it should be using UTC!

This does seem to be it. 6 PM PST is ~2 AM UTC so we were in different days 😬

date-fns should have an easy fix for the timezone issue, would be good to add documentation to the hooks that makes it clear they expect UTC.
re: expired - yes! I don't know if the design has anything for that yet, I think I left a comment on Figma about that as well.


Cryptic error messages when pybids parsing fails

The error is often something like:
AttributeError in line 13 of /usr/local/lib/python3.8/site-packages/funcmasker_flex/workflow/Snakefile:
'NoneType' object has no attribute 'get'

Would be good to catch these and try to provide a more specific error message about what happened.

The bids-inputs branch checks if bids_layout is None. Perhaps you could take a look and see if the current error msg covers your use-case?

Re-opening this as I came across the issue again specifically when the dataset_description.json is missing or invalid.  Turns out this is an issue with pybids: https://github.com/bids-standard/pybids/issues/788
One workaround is to use scope='all' instead of scope='raw', though not ideal..

A quick 'fix' would be to put pybids parsing inside a try/except, and carry forward any exceptions with a new exception saying that pybids encountered a problem. That at least puts the ball in pybid's court so that people know where to look for issues


Screenmanager.children - list not populating?!

Versions

Python: 3.4
OS: Win10
Kivy: 1.9.1

Description
No matter how many Screens added to Screenmanager - children list still only enlists the first screen!
Code and Logs
Console >>> [<Screen name='1'>]  1
but should be: [<Screen name='1'>, <Screen name='2'>]   2
from kivy.app import App
from kivy.lang import Builder
from kivy.uix.screenmanager import ScreenManager, Screen

sm = ScreenManager()
sm.add_widget(Screen(name='1'))
sm.add_widget(Screen(name='2'))

class TestApp(App):

    def build(self):
        print(sm.children, len(sm.children))
        return sm

if __name__ == '__main__':
    TestApp().run()

I'm not sure if this is by design, but it does show the real amount of children + instances after the App is run(e.g. Clock + print). Anyway, it appears in master too.

This is a performance optimization, the children list is meant for active widgets.

Yes, this is by design. add_widget and remove_widget are overridden by ScreenManager, and children mostly holds the current screen only, or two screens during transitions. The property you're looking for may be screens.

OK, makes sense now. Thank you all!


Make it possible to sort repositories

We would like to be able to sort repositories, probably by:

Stars
Number of issues
???

Working on this.


Long implementation comments (//) gets appended to the previous line

When preferSingleLine: true is set, long implementation comments are reformated as trailing comment to the previous line of code, even though they're not related with it.
(I'm aware I could use a multi-line comment (/* ... */) but we usually reserve those for doc comments).
Input Code
if (
    cond1
    // first line of a long comment related to cond2
    // second line of a long comment related to cond2
    || cond2
) {

Expected Output
if (
    cond1
    // first line of a long comment related to cond2
    // second line of a long comment related to cond2
    || cond2
) {

Actual Output
if (
    cond1 // first line of a long comment related to cond2
    // second line of a long comment related to cond2
    || cond2
) {

dprint-plugin-typescript version: 0.61.0

A similar situation:
Input Code
let result =
  // comment for the first part of the expression
  first
  // explanation for the second part
  + second;

Expected Output
let result =
  // comment for the first part of the expression
  first
  // explanation for the second part
  + second;

Actual Output
let result = // comment for the first part of the expression
  first // explanation for the second part
  + second;


Revert "Candyland Background + additional framework"

Reverts erasels/SpireMapOverhaul#214
Alright, something went very wrong with that update from main

Alright, I'm messing up even more 😆


RSS/Atom Feed

A feed would let people read your articles from the comfort of their cosy feed reader. Also would let them know when there a new one.

@pointlessone Its a good idea, but do many people use feed readers anymore? Most of them are either dead or subscription-based apps. its probably not worth the time.

I can't tell how many people use feed readers. I do. And I'm sure as heck missing your content because I'm not going to manually visit your blog. Not your in particular, just any blog. I just don't have that kind of time and memory. If there's no feed then I'm just not getting the updates.

I can't tell how many people use feed readers. I do. And I'm sure as heck missing your content because I'm not going to manually visit your blog. Not your in particular, just any blog. I just don't have that kind of time and memory. If there's no feed then I'm just not getting the updates.

@pointlessone i agree. I'll keep this ticket open and see what it takes to add the feed 👍

+1 for RSS feed

@pointlessone @ipfans i've opened https://github.com/0xadada/0xadada.pub/pull/30 please review

@pointlessone @ipfans the RSS feed is now at https://0xadada.pub/rss.xml
thanks for the suggestion 👍


Updating "Automatic" log message

ECOPROJECT-1862

Considering a use case where the finalizer is placed by the agent and than we loose connectivity after reboot, missing this log message.
Also fixing a flaky UT in config

Idea: we could put the runtime strategy into an annotation, so it's visible on the CR, and we don't need to spam the logs with it in each reconcile?

Maybe, TBH I am not even so sure that we should even print this log to begin with. I think it comes down to how visible we want to be with the inner working of "Automatic".
I'm not sure what's the proper balance from a user perspective between: Automatic: I choose that because I trust you to do it best without involving me in the details to Automatic: here is how it works we selected X because Y

Maybe it's fair to discuss how much info to reveal to the user. But we also need it ourself for debugging, not?

I'm also a bit worried from followup bugs (when we chance the Automatic selection/ or when run on different ocp version) such as the runtime annotation used to be X and now it's Y

Actually I see this as an pro argument for the annotation. In case SNR or the cluster updates during remediation, it would be bad to switch from one strategy to another one, not? The cleanup would not match anymore. With the annotation we can ensure that we use the same strategy for the whole remediation process.

/test 4.14-openshift-e2e

Maybe it's fair to discuss how much info to reveal to the user. But we also need it ourself for debugging, not?

Sure SGTM.
In any case I consider logs as something less visible than annotations/events and targeted for more technical users.

it would be bad to switch from one strategy to another one, not?

I'm not sure.
In case the remediation still exist in this use case there is a very good chance that we weren't able to fix it for awhile, might not be such a bad idea to try with a different strategy - it might even be the purpose of a change in the Automatic strategy.

/test 4.13-test

/unhold


Could I translate this document into Chinese and share with more Chinese developers?

We have an organization of translation technology articles, and We have translated a lot of documents like jwasham/coding-interview-university. Could we translate this document into Chinese and share with more Chinese developers? We will open a PR once it's done.  ❤
About our organization: xitu/gold-miner

give you a star

Absolutely, the more people this can help, the better! Please open a PR when it's finished.


Remove some unneeded mem::forget() calls and Option wrappers

See individual commits.
@GuillaumeGomez @EPashkin

@sdroege Thanks, 👍


Excel preview: Only up to column Z?

In VS Code, the preview of Excel files is only up to column Z even though there are data beyond column Z. Is this an intentional limit (such as to save memory)?

Do you mean this extension? Excel Viewer

Do you mean this extension? Excel Viewer

I was referring to Office Theme. It was only when I realized that the preview was up to column Z did I disable yours and tried the Excel Viewer. The funny thing is after I installed Excel Viewer, yours failed to work even though I disabled Excel Viewer and re-enabled yours.

When I install Excel Viewer, my extension still works well. It's just a theme

Oops, sorry. Got confused between the two.

It's OK. Closed. (Probably this Extension's bug


Add comment feature copied from augeasproviders_shellvar

first attempt at copying in the comment feature from shellvar.
this was a basic copy and paste

Coverage decreased (-10.9%) to 86.364% when pulling 40e27dd93df2ef3b1f378d1519f2c73cd4e51a86 on jgrammen-agilitypr:feature/add-comment into e4eee3726d0472cba1d2d66a2d09031f1d100914 on hercules-team:master.

Superceded by #61


The API "authorisePayment" responses me 400

@org.junit.Test     public void authroizePayment() {         List<String> paymentIdList = new ArrayList<>();         paymentIdList.add("fec2f9c4-7f92-4d11-ac96-39e441aafbc9");         PaymentAuthorisations paymentAuthorisations = currencyCloud.authorisePayment(paymentIdList);         for (PaymentAuthorisation paymentAuthorisation : paymentAuthorisations.getPaymentAuthorisations()) {             System.err.println(paymentAuthorisation.toString());         }     }
response
`BadRequestException
platform: "Java 1.8.0_202 (Oracle Corporation)"
request:
parameters:
paymentIds[]: "fec2f9c4-7f92-4d11-ac96-39e441aafbc9"
verb: "post"
url: "https://devapi.currencycloud.com/v2/payments/authorise?paymentIds[]=fec2f9c4-7f92-4d11-ac96-39e441aafbc9"
response:
status_code: 400
date: "Tue, 16 Jul 2019 06:51:10 GMT"
request_id: "c03afe4d-7884-4cfc-9b3c-1e6aa51cb665"
error_code: "invalid_extra_parameters"
errors:

field: "base"
code: "invalid_extra_parameters"
message: "Invalid extra parameters:'{:paymentIds=>["fec2f9c4-7f92-4d11-ac96-39e441aafbc9"
]}'"
params:
parameters:
paymentIds:
- "fec2f9c4-7f92-4d11-ac96-39e441aafbc9"`

How can I deal with this? Is there the server or SDK error?  I use sdk 3.2.2

Hi @conkeyn, to enable payments (or conversions) authorizations the main account and its associated sub-accounts first need to be configured. This is achieved via the Currencycloud Direct web interface.
Instructions on how to do this are available in Multi-Level Authorization but if you run into any issues you are welcome to contact our Technical Support team who will be glad to help

No activity for over 30 days. Please open a new issue if problem persists


[SPARK-22684][SQL] datetime functions should not generate useless mutable states

What changes were proposed in this pull request?
Some datetime functions are defining mutable states which are not needed at all. This is bad for the well known issues related to constant pool limits.
How was this patch tested?
added UTs

Test build #84444 has started for PR 19883 at commit 78850c6.

Test build #84444 has finished for PR 19883 at commit 78850c6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/84444/
Test PASSed.

@cloud-fan @kiszk @viirya may you please review this? Thanks


Refactor src/stan/gm/command.hpp: debugging is difficult as is.

Issues like #379 are masked by the structure of src/stan/gm/command.hpp. Here are some things that should be done:

[ ] consistent use of return codes. Use the values in src/stan/gm/error_codes.hpp
[ ] remove switch in command()

use of sampler_select is opaque. Too hard to see which sampler is actually being called.

[ ] double check all exit codes

currently, there are no tests for how this exits

We should shift focus of this code and favor clarity and maintainability. This code should be Stan's interface to be utilized by CmdStan, RStan, and PyStan. (CmdStan and RStan currently does this. I'm not sure about PyStan.)

Switch removed in https://github.com/stan-dev/stan/tree/feature/issue-1361-writer_callback.

We'll fix this with #1361.

I'm closing this issue. It's being addressed in other issues and the file has moved to CmdStan.


Allow multiple providers by CLI

Allow configuring webhook even if github app is configured
need to pass --github-webhook to configure webhook if app is already
need to pass --force-configure to override existing gh app
Changes

Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

SGTM
feel free to merge


Persist CSR PrivateKey across Host-Agent restarts

The private key generated for the create CSR workflow should be persisted in case of the host-agent restarts before we could create the newer kubeconfig.

Done as part of #541


feat(mempool): add l2_gas_price support in BlockHeader

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#652  👈
#644
#643
#641
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @TzahiTaub and the rest of your teammates on  Graphite


Fix issue 202

imgui.ini should not be pushed to the repository.
List of related issues/PRs this will solve:

Impact
Issue/PR

Issues this solves
Closes #202

Other PRs this solves
None or #number(s)

Proposed fix (Make sure you've read on how to contribute to Hazel)
Added "imgui.ini" to".gitignore"

oops .. i forgot to do a new fork for the new issue fix ... closing this PR and opening it again :(


💅 Vue genetic type not detected in generic components

Environment information
CLI:
  Version:                      1.8.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm"
  JS_RUNTIME_VERSION:           "v20.14.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "npm/10.8.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 false

Linter:
  JavaScript enabled:           true
  JSON enabled:                 true
  CSS enabled:                  false
  Recommended:                  false
  All:                          false
  Enabled rules:
  complexity/noBannedTypes
  suspicious/noCatchAssign
  suspicious/noPrototypeBuiltins
  suspicious/noUnsafeNegation
  style/useAsConstAssertion
  suspicious/noDebugger
  complexity/noMultipleSpacesInRegularExpressionLiterals
  suspicious/noMisleadingInstantiator
  suspicious/noGlobalAssign
  suspicious/useValidTypeof
  suspicious/noAssignInExpressions
  correctness/noConstantCondition
  suspicious/noDuplicateParameters
  suspicious/useGetterReturn
  correctness/noEmptyPattern
  suspicious/noExtraNonNullAssertion
  correctness/noUnusedLabels
  correctness/noUnreachableSuper
  suspicious/noExplicitAny
  suspicious/noCompareNegZero
  correctness/noSwitchDeclarations
  correctness/useIsNan
  correctness/noUnsafeOptionalChaining
  correctness/noConstAssign
  suspicious/noAsyncPromiseExecutor
  suspicious/noControlCharactersInRegex
  complexity/noUselessTypeConstraint
  complexity/noWith
  suspicious/noDuplicateClassMembers
  complexity/noExtraBooleanCast
  suspicious/noMisleadingCharacterClass
  correctness/noPrecisionLoss
  suspicious/noRedeclare
  correctness/noSetterReturn
  correctness/noInvalidConstructorSuper
  suspicious/noFallthroughSwitchClause
  suspicious/noDuplicateObjectKeys
  suspicious/noUnsafeDeclarationMerging
  complexity/noUselessThisAlias
  correctness/noUnreachable
  correctness/noInnerDeclarations
  suspicious/noDuplicateCase
  correctness/noSelfAssign
  suspicious/noEmptyBlockStatements
  suspicious/noShadowRestrictedNames
  correctness/useValidForDirection
  complexity/noUselessCatch
  correctness/noUnsafeFinally
  correctness/noNonoctalDecimalEscape
  correctness/noUndeclaredVariables
  suspicious/noImportAssign
  correctness/useYield
  style/noNamespace
  correctness/noGlobalObjectCalls
  correctness/noNewSymbol
  correctness/noEmptyCharacterClassInRegex
  suspicious/noClassAssign
  suspicious/noFunctionAssign

Workspace:
  Open Documents:               0

Rule name
lint/correctness/noUndeclaredVariables
Playground link
https://codesandbox.io/p/sandbox/nostalgic-shape-qytz8v
Expected result
No error on line 7 of example.vue
Code of Conduct

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

This is related to #2456 but that was only to not throw an error on generic components rather than parsing the value inside the generic attribute.
<script setup lang="ts" generic="T = string">
import { ref } from "vue";

const example = ref<T | null>(null);

Currently, this gives a The T variable is undeclared. error

At the moment we can only detect and parse the JavaScript code inside these <script> tags, the lint rule doesn't understand the generic attribute. I'm afraid to say this is expected and I see this as an enhancement/feature request because our Vue support at the moment is partial and very ad-hoc.
We're still dicussing how we'll support HTML-ish languags fully. We welcome you to add your inputs in #1726, so we can settle on an infrastructure that can take most of the usecases into account.
In the meantime, I think you can try disabling the rule or using this option (tbh I'm not sure whether it will work) https://biomejs.dev/reference/configuration/#javascriptglobals as a workaround.


consumeBackgroundQueue not working (iOS 10.2)

I'm using this package along side wix/react-native-navigation, and I have my notification handlers set up in the root App class's constructor as follows:
// notice that this is just a simple class, it's not a React component
export default class App {
  constructor() {
    NotificationsIOS.addEventListener('remoteNotificationsRegistered', this.onPushRegistered.bind(this));
    NotificationsIOS.addEventListener('remoteNotificationsRegistrationFailed', this.onPushRegistrationFailed.bind(this));
    NotificationsIOS.addEventListener('notificationReceivedForeground', this.onNotificationReceivedForeground.bind(this));
    NotificationsIOS.addEventListener('notificationReceivedBackground', this.onNotificationReceivedBackground.bind(this));
    NotificationsIOS.addEventListener('notificationOpened', this.onNotificationOpened.bind(this));
    NotificationsIOS.requestPermissions();
    NotificationsIOS.consumeBackgroundQueue();

// ...rest of the code

However, when the app launches from a cold state after pressing a notification, there is never anything sent to the notification handlers. Any insight onto why this isn't working? Is it something to do with react-native-navigation?

Same problem here!

+1

not working in IOS 10.3.1, any news?

@enahum which version of RNN are you using?

@d4vidi im on RNN 1.1.72

Same here :)

It seems to fire the correct event and correctly enters the code on the native side but the premise always resolves with null on getInitialNotification.

I really don't know anything about Objective-C but I'm wondering if this has anything to do with it https://github.com/wix/react-native-navigation/blob/master/ios/RCCManager.m#L41

@bruchim Could you possibly help these guys out? They're using <2 navigation version.

I'm having the same problem and am also using react-native-navigation < v2.  Scratching my head here trying to figure out why these handlers don't seem to be called.

Ok guys I solved it... I think the react-native-navigation docs could definitely be updated for iOS to include this tidbit.
"launchOptions" is not passed to the bridge if you use the default AppDelegate example from the react-native-navigation docs.
You need to use this to start the app (passing launchOptions) so that the push notification that was pressed is available to the bridge.
[[RCCManager sharedInstance] initBridgeWithBundleURL:jsCodeLocation launchOptions:launchOptions];
Once the launchOptions are passed to the bridge you should see the notificationOpened handler is firing as expected.

I can confirm that the solution form @jbolter works as a charm. Thanks my friend


Pretty printer - remove sequential blank lines

Removes any blank lines above the limit specified in abaplint.json.

also include lines containing only whitespace (for sequential_blanks as well)
moved pretty printing operations to separate classes

I would like to keep the pretty printer under /abap/, but I guess it can be moved sometime in the future.
thinking of having multiple pretty printers, one for ABAP + CDS + XSLT + more, but it might also be okay to put it all under pretty_printer 🤷♂

thanks 👍


ImportError: cannot import name 'sql' from partially initialized module 'databricks'

Got this error ImportError: cannot import name 'sql' from partially initialized module 'databricks' (most likely due to a circular import)
Python 3.11.9

PS C:\Projects\Python\Databricks> pip install databricks-sql-connector
Collecting databricks-sql-connector
  Using cached databricks_sql_connector-3.1.2-py3-none-any.whl.metadata (4.4 kB)
Collecting lz4<5.0.0,>=4.0.2 (from databricks-sql-connector)
  Using cached lz4-4.3.3-cp311-cp311-win_amd64.whl.metadata (3.8 kB)
Collecting numpy>=1.23.4 (from databricks-sql-connector)
  Using cached numpy-1.26.4-cp311-cp311-win_amd64.whl.metadata (61 kB)
Collecting oauthlib<4.0.0,>=3.1.0 (from databricks-sql-connector)
  Using cached oauthlib-3.2.2-py3-none-any.whl.metadata (7.5 kB)
Collecting openpyxl<4.0.0,>=3.0.10 (from databricks-sql-connector)
  Using cached openpyxl-3.1.2-py2.py3-none-any.whl.metadata (2.5 kB)
Collecting pandas<2.2.0,>=1.2.5 (from databricks-sql-connector)
  Using cached pandas-2.1.4-cp311-cp311-win_amd64.whl.metadata (18 kB)
Collecting pyarrow<15.0.0,>=14.0.1 (from databricks-sql-connector)
  Using cached pyarrow-14.0.2-cp311-cp311-win_amd64.whl.metadata (3.1 kB)
Collecting requests<3.0.0,>=2.18.1 (from databricks-sql-connector)
  Using cached requests-2.31.0-py3-none-any.whl.metadata (4.6 kB)
Collecting thrift<0.17.0,>=0.16.0 (from databricks-sql-connector)
  Using cached thrift-0.16.0-cp311-cp311-win_amd64.whl
Collecting urllib3>=1.26 (from databricks-sql-connector)
  Using cached urllib3-2.2.1-py3-none-any.whl.metadata (6.4 kB)
Collecting et-xmlfile (from openpyxl<4.0.0,>=3.0.10->databricks-sql-connector)
  Using cached et_xmlfile-1.1.0-py3-none-any.whl.metadata (1.8 kB)
Collecting python-dateutil>=2.8.2 (from pandas<2.2.0,>=1.2.5->databricks-sql-connector)
  Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl.metadata (8.4 kB)
Collecting pytz>=2020.1 (from pandas<2.2.0,>=1.2.5->databricks-sql-connector)
  Using cached pytz-2024.1-py2.py3-none-any.whl.metadata (22 kB)
Collecting tzdata>=2022.1 (from pandas<2.2.0,>=1.2.5->databricks-sql-connector)
  Using cached tzdata-2024.1-py2.py3-none-any.whl.metadata (1.4 kB)
Collecting charset-normalizer<4,>=2 (from requests<3.0.0,>=2.18.1->databricks-sql-connector)
  Using cached charset_normalizer-3.3.2-cp311-cp311-win_amd64.whl.metadata (34 kB)
Collecting idna<4,>=2.5 (from requests<3.0.0,>=2.18.1->databricks-sql-connector)
  Using cached idna-3.7-py3-none-any.whl.metadata (9.9 kB)
Collecting certifi>=2017.4.17 (from requests<3.0.0,>=2.18.1->databricks-sql-connector)
  Using cached certifi-2024.2.2-py3-none-any.whl.metadata (2.2 kB)
Collecting six>=1.7.2 (from thrift<0.17.0,>=0.16.0->databricks-sql-connector)
  Using cached six-1.16.0-py2.py3-none-any.whl.metadata (1.8 kB)
Using cached databricks_sql_connector-3.1.2-py3-none-any.whl (427 kB)
Using cached lz4-4.3.3-cp311-cp311-win_amd64.whl (99 kB)
Using cached numpy-1.26.4-cp311-cp311-win_amd64.whl (15.8 MB)
Using cached oauthlib-3.2.2-py3-none-any.whl (151 kB)
Using cached openpyxl-3.1.2-py2.py3-none-any.whl (249 kB)
Using cached pandas-2.1.4-cp311-cp311-win_amd64.whl (10.6 MB)
Using cached pyarrow-14.0.2-cp311-cp311-win_amd64.whl (24.6 MB)
Using cached requests-2.31.0-py3-none-any.whl (62 kB)
Using cached urllib3-2.2.1-py3-none-any.whl (121 kB)
Using cached certifi-2024.2.2-py3-none-any.whl (163 kB)
Using cached charset_normalizer-3.3.2-cp311-cp311-win_amd64.whl (99 kB)
Using cached idna-3.7-py3-none-any.whl (66 kB)
Using cached python_dateutil-2.9.0.post0-py2.py3-none-any.whl (229 kB)
Using cached pytz-2024.1-py2.py3-none-any.whl (505 kB)
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Using cached tzdata-2024.1-py2.py3-none-any.whl (345 kB)
Using cached et_xmlfile-1.1.0-py3-none-any.whl (4.7 kB)
Installing collected packages: pytz, urllib3, tzdata, six, oauthlib, numpy, lz4, idna, et-xmlfile, charset-normalizer, certifi, thrift, requests, python-dateutil, pyarrow, openpyxl, pandas, databricks-sql-connector
Successfully installed certifi-2024.2.2 charset-normalizer-3.3.2 databricks-sql-connector-3.1.2 et-xmlfile-1.1.0 idna-3.7 lz4-4.3.3 numpy-1.26.4 oauthlib-3.2.2 openpyxl-3.1.2 pandas-2.1.4 pyarrow-14.0.2 python-dateutil-2.9.0.post0 pytz-2024.1 requests-2.31.0 six-1.16.0 thrift-0.16.0 tzdata-2024.1 urllib3-2.2.1

Hi @jimczhang. Try to give your file (databricks.py) a different name. When you do from databricks import sql it tries to import from itself


feature update : timesheet implementation

adding create,read and delete for timesheet implementation

conflicts were minor
-angular version and index.html swap attribute


feat: add experimental feature flag for dashboards-assistant plugin

Description
Describe what this change achieves.
Issues Resolved
#4361
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Adding @peterzhuamazon, @gaiksaya and @prudhvigodithi for the comments, thanks !!

LGTM, are we still using this opensearch_dashboards-default.x.yml @peterzhuamazon ?
Thanks

LGTM, are we still using this opensearch_dashboards-default.x.yml @peterzhuamazon ? Thanks

We are for 3.x right no.

@peterzhuamazon Thanks and done.


Fix angular UI

I've mentioned inability to set the date in admin UI. Need to fix this and check for any other inconsistencies.

@webknjaz: please provide the corresponding url and screenshots. If there is any error log, please attach it to the issue as well.

@anxolerd If you open event and modify date, you'll mention validation errors in console.

TypeError: s.test is not a function
    at http://localhost:8080/js/angular-strap.min.js:8:4847
    at https://ajax.googleapis.com/ajax/libs/angularjs/1.1.5/angular.min.js:151:379
    at Array.forEach (native)
    at n (https://ajax.googleapis.com/ajax/libs/angularjs/1.1.5/angular.min.js:6:470)
    at $setViewValue (https://ajax.googleapis.com/ajax/libs/angularjs/1.1.5/angular.min.js:151:349)
    at http://localhost:8080/js/angular-strap.min.js:8:5142
    at Object.e.$eval (https://ajax.googleapis.com/ajax/libs/angularjs/1.1.5/angular.min.js:92:272)
    at Object.e.$apply (https://ajax.googleapis.com/ajax/libs/angularjs/1.1.5/angular.min.js:92:379)
    at HTMLInputElement.<anonymous> (http://localhost:8080/js/angular-strap.min.js:8:5122)
    at HTMLInputElement.b.event.dispatch (http://ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js:3:28337)

Fixed by fd6a50b25a5c397affa3a7cb0f6ae5047c0e6995


Danger Swift will need to handle a danger.github which is null

The DSL is going to  be extended with an upcoming release today. Is there a way that Danger Swift can not break if an attribute is added to the JSON? I'm pretty sure every time a new attribute was added this needed to change.

@orta pretty sure you just need to add CodingKeys enum to specify which properties you want. Which would be adding here:
private enum CodingKeys: String, CodingKey {
    case git
    case github
}

I'm more interested in forward compatibility, when bitbucket_server appears in the JSON (which is will now) would that break the JSON parser?

It will only break the existing parser if you’re changed the order of the git and github nodes as well. If bitbucket is under the root node, this shouldn’t change anything.
Sent with GitHawk

The JSON decoder ignores any keys that are not properties of the object it is decoding.

Ah that's great.
Separately, yes, danger.github is now optional. In Danger JS' types, I declare both danger.github and danger.bitbucket_server as non-optional, but I don't think you can get away with that in Swift, which will require an update to all Dangerfiles :(

Yeah updating all Dangerfiles can be tricky especially if users aren't using an IDE for compile time warnings.
I wonder if we can make danger.github and danger.bitbucket_server implicitly unwrapped optionals. I'm pretty sure you can put nil in an IUO so decoding should work? The API is definitely less safe but if you're accessing BitBucket information and your repo is hosted on GitHub then this is a programmer error 🤔

That could probably work, yeah 👍

Fixed


Delete command should remove created id in config files

Following a discussion with @lalepee, the delete command should not use any id present in configuration file by default and id should be type explicitely


Fix for issue #256

Resolves #256. These changes will display # of snapshots of a selected year in bubble canledar view. This piece of information will be provided beside the total number of snapshots.

Not sure about localization of the added text.

I agree to add 'times in' in WaybackUI.properties instead of hard-coding it in BubbleCalendar.jsp.
BTW, how about renaming it to be OpenWaybackUI.properties?

I agree to add 'times in' in WaybackUI.properties instead of hard-coding it in BubbleCalendar.jsp.
BTW, how about renaming it to OpenWaybackUI.properties?

Renaming the file may break existing WAR overlays.


Spam in console

[15:17:48] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:17:49] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:17:51] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:17:53] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:17:55] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:17:57] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:17:59] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:01] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:03] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:05] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:07] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:09] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:11] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:13] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:15] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:17] [Server thread/INFO] [EasyScoreboards]: Building scoreboard
[15:18:19] [Server thread/INFO] [EasyScoreboards]: Building scoreboard

forge-1.12.2-<IP_ADDRESS>11-universal.jar
spongeforge-1.12.2-2611-7.1.0-BETA-2931.jar
EasyScoreboards.jar 2.3 latest

I'm sorry about that, just released a new version to fix it.


CROSS_APP_NAV_TO_EXT issue

Hi @oblomov-dev
Happy new year!
I install the latest tag 1.113.0 of ABAP2UI5 and the latest FLP integration approach.
Unfortunately, the cross application navigation "CROSS_APP_NAV_TO_EXT" in "EXT"  mode doesn't work anymore for my app.
I just see that the frontend event get's triggered and the parameters are passed, but nothing happened.
I don't see an error in the console.
Update:
I found an exception while requesting the uShell service:
oCrossAppNavigator = sap.ushell.Container.getService("CrossApplicationNavigation");

Could you please try to reproduce the error. Do you have the same behavior?
Thanks,
Axel

i close this one, just open in a new issue if you have further problems.


Get human-readable media options

I am currently trying to obtain a list of all supported media options for a printer in a human-readable format such as "A4", "letter 8.5x11", etc. Currently, I am using ippAttributeString() to obtain the media options, but they are returned in a format that is not easily readable, such as "om_a-4-borderless_210x297mm".
I was wondering if there is a correct method to obtain a human-readable form for media options. If not, can it be assumed that the results obtained from ippAttributeString() will always strictly follow the format "prefix_medianame-[borderless]_size", and can thus be parsed safely following this structure?
I also had a look at how media options are returned in lpoptions, where they are simply displayed as "A4", "A5", "A6", etc. However, I noticed that this uses PPD files, but the PPD API has been deprecated so this may not be a suitable solution.
Any help or guidance on this issue would be highly appreciated. Thank you!

See the cupsLocalizeDestMedia API for getting localized media names.


[Q] How to properly save and load fp8 NumPy arrays?

I would like to save and load an f8m5e2 array. I initially tried using the standard numpy.save() and numpy.load() functions, but loading fails.
.local/lib/python3.10/site-packages/numpy/lib/format.py", line 325, in descr_to_dtype
    return numpy.dtype(descr)
TypeError: data type '<f1' not understood

.local/lib/python3.10/site-packages/numpy/lib/format.py", line 683, in _read_array_header
    raise ValueError(msg.format(d['descr'])) from e
ValueError: descr is not a valid dtype descriptor: '<f1'

I found that I can save and load float8 arrays using a lower-level API (np.tobytes / np.frombuffer), as shown below:
import ml_dtypes
import numpy as np
import json

# Create the array
x = np.array([.2, .4, .6], dtype=ml_dtypes.float8_e5m2)

# Save the array
with open("a.npy", "wb") as f:
    f.write(x.tobytes())

# Save the array's shape and dtype separately
meta = {"shape": x.shape, "dtype": str(x.dtype)}
with open("a_meta.json", "w") as f:
    json.dump(meta, f)

# Load the array
with open("a.npy", "rb") as f:
    data = f.read()

# Load the metadata
with open("a_meta.json", "r") as f:
    meta = json.load(f)

# Reconstruct the array
x2 = np.frombuffer(data, dtype=getattr(ml_dtypes, meta["dtype"])).reshape(meta["shape"])

print(x2)

Is the solution above (np.tobytes / np.frombuffer) considered best practice for this case?
@jakevdp Jake, can you comment on it?
Related Issues

https://github.com/jax-ml/ml_dtypes/issues/148

Unfortunately NumPy's array serialization only works with NumPy's built-in dtypes. Probably the easiest way to serialize arrays with custom dtypes is to view them as unsigned int:
import ml_dtypes
import numpy as np
import json

# Create the array
x = np.array([.2, .4, .6], dtype=ml_dtypes.float8_e5m2)

np.save('x.npy', x.view('uint8'))
x2 = np.load('x.npy').view(ml_dtypes.float8_e5m2)

print(np.all(x == x2))
# True

Hi Jake, Thank you for your reply!
I have one additional question
I tired to use pickle.
It works. File size is almost the same as default np.save approach
import ml_dtypes
import numpy as np
import pickle

# Create the array
a = np.array([.2, .4, .6], dtype=ml_dtypes.float8_e5m2)
b = np.array([.2, .4, .6], dtype=ml_dtypes.float8_e4m3)

# Save
with open('a.npy.pkl', "wb") as f:
  pickle.dump(a, f)

with open('b.npy.pkl', "wb") as f:
  pickle.dump(b, f)

# Load back
a2 = np.load('a.npy.pkl', allow_pickle=True)
b2 = np.load('b.npy.pkl', allow_pickle=True)

print(np.all(a == a2))
print(np.all(b == b2))

Seems that it works out of the box and saves ml_dtypes dtype info into the the file.
What are the disadvantages of using pickle?
Cons which I found:

Pickle is not "secure".
It is sensitive to numpy version. env with older numpy might not be able to open files saved on envs with newer numpy version. e.g.

>>> b2 = np.load('b.npy.pkl', allow_pickle=True)
Traceback (most recent call last):
  File "/home/user/.local/lib/python3.9/site-packages/numpy/lib/npyio.py", line 441, in load
    return pickle.load(fid, **pickle_kwargs)
ModuleNotFoundError: No module named 'numpy._core'

Yes, pickle works, but has downsides. The two you mention are the main issues.


SCC Sensitivity labels

SCC sensitivity labels
Description
Resource for the following Get-Label, New-Label, Set-Label and Remove-Label
Proposed properties
Special considerations or limitations

@NikCharlebois Please assign to @desmay

Closing since the resource has been created


Update /waitlist/ to include supported diseases / interest checkboxes

Related Issue or Background Info

resolves https://github.com/CDCgov/prime-simplereport/issues/7320

Changes Proposed

Add a bullet point list of supported diseases
Add a checkbox for which diseases the submitter is interested in
Add a text field for any diseases not currently supported

Additional Information

deployed on dev3
Screenshots / Demos
https://github.com/CDCgov/prime-simplereport-site/assets/7085658/b7b33464-3c40-4a87-91a8-554cdd502a78
Checklist for Author and Reviewer
Design

[ ] Any UI/UX changes have a designer as a reviewer, and changes have been approved
[ ] Any large-scale changes have been deployed to test, dev, or pentest and smoke-tested by both the engineering and design teams

Content

[ ] Any content changes (including new error messages) have been approved by content team

Support

[ ] Any changes that might generate new support requests have been flagged to the support team

Testing

[ ] Includes a summary of what a code reviewer should verify

corresponding backend issue has been opened here: https://github.com/CDCgov/prime-simplereport/issues/7465


test/markdown: flaky test

Have run into this flaky test few times:
19.12s$ make test/markdown
./hack/ci/marker --root=doc
HTTP failure           (pool.sks-keyservers.net -> http://pool.sks-keyservers.net/) at doc/dev/release.md:80 : failed to lookup address information: Name or service not known
HTTP failure           (SKS PGP Public Key Server -> http://pool.sks-keyservers.net/) at doc/dev/release.md:90 : failed to lookup address information: Name or service not known
make: *** [test/markdown] Error 1
The command "make test/markdown" exited with 2.

and
21.62s$ make test/markdown
./hack/ci/marker --root=doc
Found broken url       (pool.sks-keyservers.net -> http://pool.sks-keyservers.net/) at doc/dev/release.md:80 : 502 Bad Gateway
Found broken url       (SKS PGP Public Key Server -> http://pool.sks-keyservers.net/) at doc/dev/release.md:90 : 502 Bad Gateway
make: *** [test/markdown] Error 1
The command "make test/markdown" exited with 2.

Triedhttp://pool.sks-keyservers.net and it resolves for me.
cc @AlexNPavel

Yeah, I'm not sure why it is doing this. It seems like some keyservers have been having weird 502 issues. This started happening after we changed the URL from pgp.mit.edu to the sks pool, since the mit server is unreliable and wasn't working when we were trying to add Ish's public key to the pool. I think we should wait maybe about 1 week, and if it continues just remove the hyperlink.

I think we should wait maybe about 1 week, and if it continues just remove the hyperlink.

That sounds good 👍

Should be fixed via #1108


[Enhancement] dump fragment instance id when be crash in DataStreamRecvr

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：
it's helpful to found the issue
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

run starrocks_admit_test

run starrocks_admit_test

https://github.com/Mergifyio backport branch-2.3


error TS18003: No inputs were found in config file 'tsconfig.json'. Specified 'include' paths were '["src/**/*"]' and 'exclude' paths were '["node_modules"]'.

can't parsing tsconfig.json
error TS18003: No inputs were found in config file 'tsconfig.json'. Specified 'include' paths were '["src/**/*"]' and 'exclude' paths were '["node_modules"]'.
tsconfig.json:

{
"compileOnSave": true,
"compilerOptions": {
"experimentalDecorators": true,
"sourceMap": true,
"strict": true,
"module": "es2015",
"moduleResolution": "node",
"target": "es5"
},
"include": [
"src/**/*"
],
"exclude": [
"node_modules"
]
}

webpack config:

{
test: /.tsx?$/,
loader: 'ts-loader',
include: [resolve('src')],
options: {
appendTsSuffixTo: [/.vue$/],
}
},

use:
vue2, webpack2, typescript2.4.1

Are you using tsc to compile your project?
Is there a src directory next to your tsconfig.json that contains .ts files?

this ok now, thank. .ts files write wrong.

I am getting the same error I also have .ts files in src folder. My package.json is like this

{
  "compilerOptions": {
    "rootDir": ".",
    "experimentalDecorators": true,
    "module": "es2015",
    "moduleResolution": "node",
    "noUnusedParameters": true,
    "strictNullChecks": true,
    "skipLibCheck": true,
    "outDir": "./dist/packages/all",
    "target": "es2015",
    "lib": ["es5", "es2015", "dom"],
    "types": ["jasmine"],
    "baseUrl": ".",
    "paths": {
      "@angular/material": ["./src/lib/public_api.ts"],
      "@angular/cdk/*": ["./src/cdk/*"],
      "@angular/material-examples": ["./src/material-examples"],
      "material2-build-tools": ["./tools/package-tools"]
    }
  },
  "include": [
 "/"
  ],
  "exclude": [
    "/"
  ]
}

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

@saishbhende24 Maybe remove the "exclude"?

I to have the same issue, the error was not there before, suddenly it appeared and not able to find root cause


Nuxt apollo subscription 400 (Bad Request)

I am trying to create a nuxt app using apollo with a graphql subscription, but every time I try to fetch data from the graphql server I get:
Failed to load resource: the server responded with a status of 400 (Bad Request)
I have the same setup in a regular vue app which works perfectly. Both are using vuex for local storage while querying graphql for data.
My store:
const createStore = () => {
  return new Vuex.Store({
    state: {
      projects: [],
      projectObservable: null,
      projectObserver: null
    },
    actions: {
      FETCH_PROJECTS ({ commit }) {
        if (!this.projectObservable) {
          this.projectObservable = this.app.apolloProvider.defaultClient.subscribe({
            query: PROJECT_SUBSCRIPTION
          })
        }
      },
      // You call this action to start the sunscription
      SUBSCRIBE_TO_PROJECTS ({ commit }) {
        console.log(this.projectObservable)
        this.projectObserver = this.projectObservable.subscribe({
          next (data) {
            let project = data.data.Project
            // then call your store mutation as usual
            switch (project.mutation) {
              case 'CREATED':
                commit('ADD_PROJECT', project.node)
                break
              case 'UPDATED':
                commit('UPDATE_PROJECT', project.node)
                break
              case 'DELETED':
                commit('DELETE_PROJECT', project.previousValues)
                break
            }
          },
          error (error) {
            console.log(error)
          }
        })
      },
      // You call this action to stop the subscription
      UNSUBSCRIBE_FROM_PROJECTS (context) {
        if (this.projectObserver) {
          this.projectObserver.unsubscribe()
          this.projectObserver = null
        }
      }
    },
    mutations: {
      SET_PROJECTS (state, projects) {
        state.projects = projects || null
      },
    }
  })
}
export default createStore

The project subscription:
export const PROJECT_SUBSCRIPTION = gql`
  subscription newProjects {
    Project (
      filter: {
        mutation_in: [CREATED]
      }
    ) {
      mutation
      node {
        id
        name
      }
    }
  }

My component
import createProject from '~/components/createProject'
import { mapGetters } from 'vuex'

export default {
  name: 'projects',
  data () {
    return {
      allProjects: [],
    }
  },
  components: {
    createProject
  },
  computed: {
    ...mapGetters([
      'projects'
    ]),
    projectSubscription () {
      return this.$store.state.projectSubscription
    },
    subscriptionButtonText () {
      return this.subscribed ? 'Unsubscribe' : 'Subscribe'
    }
  },
  created () {
    this.$store.dispatch('FETCH_PROJECTS')
    this.$store.dispatch('SUBSCRIBE_TO_PROJECTS')
  },
  destroyed () {
    this.$store.dispatch('UNSUBSCRIBE_FROM_PROJECTS')
  }
}

Can anyone help and tell me what I am going wrong because I would really like to use nuxt for this project.

@jespermb I don't know but this will never work I think:
            query: PROJECT_SUBSCRIPTION
          })```
I don't think that you can write like this into the this scope of a store (this is my guess). Why are you not using the subscriptions on the component level as the vue-apollo project is suggesting https://github.com/Akryum/vue-apollo#subscribe

The reason I am trying to do it this was is that i want to centralize my integrations with graphql and I have other external services which I need to store data from while users are logged in so it would be great to be able to use the store.
I have it working like this on another vue project but I would really love to get the benefits of nuxt.

I have isolated the issue to be my setup of the apollo client:
import { HttpLink } from 'apollo-link-http'
import { WebSocketLink } from 'apollo-link-ws'
import { ApolloLink, concat, split } from 'apollo-link'
import { InMemoryCache } from 'apollo-cache-inmemory'
import { getMainDefinition } from 'apollo-utilities'
import { SubscriptionClient } from 'subscriptions-transport-ws'
import WebSocket from 'ws'

export default (ctx) => {
  const httpUri = 'https://api.graph.cool/simple/v1/xxxx'
  const wsUri = 'wss://subscriptions.graph.cool/v1/xxxx'

  const client = new SubscriptionClient(wsUri, {
    reconnect: true
  }, WebSocket)

  const httpLink = new HttpLink({ uri: httpUri })
  const wsLink = new WebSocketLink(client)

  const link = split(
    ({query}) => {
      const {kind, operation} = getMainDefinition(query)
      return kind === 'OperationDefinition' && operation === 'subscription'
    },
    wsLink,
    httpLink
  )

  const authMiddleware = new ApolloLink((operation, forward) => {
    // const token = this.$store.getters.getAccessToken
    // if (token) {
    //   // add the authorization to the headers
    //   operation.setContext({
    //     headers: {
    //       authorization: `Bearer ${token}`
    //     }
    //   })
    // }

    return forward(operation)
  })

  return {
    link: concat(authMiddleware, link),
    cache: new InMemoryCache()
  }
}
```
I also tried the official recommended setup but got this error:

Unable to find native implementation, or alternative implementation for WebSocket!

You need to add a Node implementation for WebSocket if you want to have subscriptions server side. Please check the apollo project itself how to add it or simply wrap your code to add subscriptions only on client.

Thanks,
I am not sure I have the experience to understand how I would do that? :)

@jespermb check out this comments: https://github.com/apollographql/subscriptions-transport-ws/issues/321
You basically need to add 'ws' on server side or you wrap your subscription code depending to run only on client
if(ctx.isClient){
  //=> here you place your subscription code
}


Ball on fixed ground starts bouncing

Hi, I encountered strange situation.
A ball on the fixed ground starts bouncing.
Moreover, energy is not conserved. (It becomes larger and larger.)
import matplotlib.pyplot as plt
import numpy as np
import jax

try:
  import brax
except ImportError:
  from IPython.display import clear_output
  !pip install git+https://github.com/google/brax.git@main
  clear_output()
  import brax

RADIUS = 0.1
SIM_STEPS = 300

bouncy_ball = brax.Config(dt=0.01, substeps=4)

# ground is a frozen (immovable) infinite plane
ground = bouncy_ball.bodies.add(name='ground')
ground.frozen.all = True
plane = ground.colliders.add().plane
plane.SetInParent()

ball = bouncy_ball.bodies.add(name='ball', mass=1.0)
cap = ball.colliders.add().capsule
cap.radius, cap.length = RADIUS, 2*RADIUS

bouncy_ball.gravity.z = -9.8
bouncy_ball.elasticity = 1.0

sys = brax.System(bouncy_ball)
step_compiled = jax.jit(sys.step)

def reset_qp():
  return brax.QP(
    pos = np.array([[0., 0., 0.],    # ground
                    [0., 0., RADIUS]]), # ball is on ground
    vel = np.array([[0., 0., 0.],       # ground
                    [0., 0., 0.]]),     # ball
    rot = np.array([[1., 0., 0., 0.],   # ground
                    [1., 0., 0., 0.]]), # ball
    ang = np.array([[0., 0., 0.],       # ground
                    [0., 0., 0.]])      # ball
)

qp = reset_qp()
qps = [qp]
for _ in range(SIM_STEPS):
    qp, _ = step_compiled(qp, [])
    qps.append(qp)

qz = [_qp.pos[1, 2] for _qp in qps]
vz = [_qp.vel[1, 2] for _qp in qps]

plt.figure(figsize=(5,5))
ax = plt.gca()
ax.plot(qz, marker=".", linestyle=":", label="Z (left)")

ax2 = ax.twinx()
ax2.plot(vz, marker=".", linestyle=":", label="Vz (right)", color="tab:orange")

ax.legend(*[a+b for a,b in zip(ax.get_legend_handles_labels(), ax2.get_legend_handles_labels())])
plt.show()

Yep, this is a conspiracy of a few different approximations biting the simulator simultaneously.
tldr: You can avoid this by using elasticity slightly less than 1, and by cranking up the number of substeps.  At elasticity exactly 1.0, the error accumulated by the ball slightly penetrating the ground after every substep allows it to smuggle energy out of the simulator.  When elasticity is less than 1, it can still smuggle a little energy, but it's at least bounded.  Here's a version with elasticity .99 and substeps = 16:

This is a known issue with discrete physics simulation.  Fancier simulators implement "sleeping" methods, where objects that are at rest are simply not simulated to avoid the accumulation of this type of error.
Thankfully, this sort of thing should disappear completely in a new version of Brax that's in the works right now :)

@cdfreeman-google
Thank you for your reply.
I understand the situation and try to use smaller elasticity.

Thankfully, this sort of thing should disappear completely in a new version of Brax that's in the works right now :)

Great!
I hope it will come soon.


[mysql] incorrect handling of stored procedure and function with the same name

Operating system (distribution) and version: Debian 10
DBeaver version: 21.0.2
Database name and version: mysql 8.0.23
Driver name: MySQL

If there are one stored procedure and one function with the same name, you could loose function while editing the procedure.

create "test" PROCEDURE

DELIMITER $$
$$
CREATE PROCEDURE testdb.test()
BEGIN
END$$
DELIMITER ;

create "test" FUNCTION

DELIMITER $$
$$
CREATE FUNCTION testdb.test()
RETURNS INT
DETERMINISTIC
BEGIN
	RETURN 0;
END$$
DELIMITER ;

open the procedure, edit and save. CTRL+S generates the correct code:

DROP PROCEDURE IF EXISTS testdb.test;

DELIMITER $$
$$
CREATE DEFINER=`root`@`localhost` PROCEDURE `testdb`.`test`()
BEGIN
	# test
END$$
DELIMITER ;

edit the procedure again and press CTRL+S.... boom:

DROP FUNCTION IF EXISTS testdb.test;
DELIMITER $$
$$
CREATE DEFINER=root@localhost PROCEDURE testdb.test()
BEGIN
# test 1
END$$
DELIMITER ;
As you can see the second time you save, there is a DROP FUNCTION and CREATE PROCEDURE, so "test" function is deleted.

thanks for the report

Verified