Process.run(command, shell: true) inconsistent on Windows and POSIX

Process.run with shell: true behaves differently on Windows and POSIX platforms when the command executable does not exist:
Process.run("filedoesnotexist", shell: true)

On POSIX system it returns Process::Status with exit code 127 (which indicates failure).
On Windows it raises FileNotFoundError.

Other error conditions might show similar inconsistent behaviour.
IMO raising FileNotFoundError is a more reasonable choice. The user asks to run a command and when that command doesn't even exist, this should usually be considered an error and raise. However, this might need to be considered a breaking change.
Btw. in Ruby `filedoesnotexist` raises the exception Errno::ENOENT on both Linux and Windows.

Maybe not directly relevant, but there's also this related discussion about shell: true with args on Windows: #9030

FileNotFoundError will be incorrect on Unix-like systems, because the command can also be a built-in shell command.
crystal eval 'Process.run("set", shell: true)' will succeed for instance, but set is not a file.

I don't think that's exactly incorrect. Yes, a command could also be a shell built-in or alias. But when invoking that command fails with error 127 it means there is neither a built-in, alias nor file by that name. So file not found would be acceptable IMO.
It could also use a more specific error type, though.

Other possible valid one word "commands" I found:

variables: Process.run("$some_variable", shell: true)
one-liner with no spaces: Process.run("ls>/tmp/output", shell: true)

What's the significance of "one word commands? Does that have any special meaning?
It shouldn't matter what the command is (it can even be a complex shell expression). If a command is not found, the shell returns exit code 127. That implicitly means no file was found that would match the command name.
If there would be a more specific error type (such as CommandNotFound error), it should probably be a subtype of FileNotFound. I doubt that such specificity is necessary, though.

Another difference is that on POSIX the shell besides returning exit code 127 also prints a message to stderr (something like --: 1: filedoesnotexist: not found). On Windows there's no output. I suppose this could be acceptable as functional differences of the operating system / shell being used for executing the command. It might still be worth considering.

I mean, there isn't necessary a file involved in the process for shell expressions.
I wasn't sure if there was any parsing done, with spaces for instance, so in my examples I didn't include any - but that's not the case.

Well, yes when running a command that is actually a shell built-in, no file will be looked up and it doesn't matter if it exists or not. But when it's not a built-in, the shell looks up a file by the name of the command. A file is involved in that scenario. Or rather its absence. And that's a perfect fit for FileNotFound.

Faire enough. Another alternative is to still return a Process::Status with an #exit_reason getter, which will be FileNotFound (can be an enum member).
The advantage being not a breaking change.

I think I may have confused myself the behavior with shell: false.
It can be good to have the same behavior between the two.

I think I may have confused myself with the behavior of shell: false.
It can be good to have the same behavior between the two.

I think I may have confused myself with the behavior of shell: false.
It can be good to have in this case the same result between the two.

Another alternative is to still return a Process::Status with an #exit_reason getter, which will be FileNotFound

Yeah that would align with #12284
But I think communicating this as Process::Status is not a good model.
When the command to be executed is not found, the shell doesn't even attempt to run any process because there is nothing to run. So this should be expressed as an error state of Process.run, i.e. raise an exception. Process.run("commandnotexists", shell: true) returning a Process::Status with exit code 127 exposes an implementation detail on POSIX. shell: true is implemented via /bin/sh -c which communicates that the command was not found via exit code 127. The public API has nothing to do with /bin/sh, so this specific error communication should not leak outside of Process.run.

Due to the implementation of shell: true and the mechanics of spawning a process on POSIX systems, there is some inherently different behaviour. On Windows, Process.new(shell: true) directly spawns a process with the given command and raises if the command cannot be found. On POSIX, Process.new(shell: true) only spawns the shell (/bin/sh) which should usually succeed. The shell then executes the command and we can't know whether that was successful until the shell process exits, which requires to wait for it.
So a command not found error can be observed in different places: On windows it's directly raised in Process.new(shell: true). On POSIX, it's later in Process#wait. At that point the original command and whether it's run with a shell are unknown, because Process is a very thin wrapper and doesn't persist that information. That impacts the amount of information that can be available for an error message.
Process.new(shell: false) raises immediately on all platforms.
Process.run calls .new and #wait internally and can handle any kind of error.
But when using the Process.new API with shell: true, exceptions about the command not being found will be raised in different places.

There's an additional complication with mapping exit codes 127 and 126 to File::NotFoundError and File::AccessDeniedError on POSIX: Those exit codes don't necessarily need to come from the shell process telling that it couldn't run the command it received. It could also be passed through from the command that's run within the shell. Still telling that a command couldn't be run, but then it's inside the user-supplied command and not from the transparent wrapper around it.
For a completely transparent implementation of shell: true we would need to differentiate where the exit status originates. If it's from the shell, raise an exception. Otherwise it's just the exit status of the command that's being executed in the shell.

I find it odd that POSIX calls /bin/sh -c but Windows doesn't call %COMSPEC% /C. At least for the backtick (where #9030 does not apply because there are no extra arguments) it should be possible to use built-in shell commands:
`exit 123`   # raises on Windows
$?.exit_code # 123 on POSIX, unreachable on Windows

There's an additional complication with mapping exit codes 127 and 126 to File::NotFoundError and File::AccessDeniedError on POSIX: Those exit codes don't necessarily need to come from the shell process telling that it couldn't run the command it received. It could also be passed through from the command that's run within the shell.

That's not supposed to happen. 126 and 127 are reserved return codes under POSIX:

Exit Code
Meaning
Example
Comments

126
Command invoked cannot execute
/dev/null
Permission problem or command is not an executable

127
"command not found"
illegal_command
Possible problem with $PATH or a typo

Source: https://tldp.org/LDP/abs/html/exitcodes.html
(I'd like to link to the POSIX specification, but it's paywalled)

@SamantazFox Yes, the meaning of these exit codes is clearly define, that shouldn't be an issue. But the reference can be ambiguous.
On windows, there's a clear indicator whether the specified shell command could be executed or not. Process.run("foobar", shell: true) raises when it fails to execute foobar.
On POSIX, the exit code 126 or 127 can mean that foobar failed to execute. But it could also mean that foobar itself executed correctly, but it failed executing another command.
Compare the result of these very similar command invokations on Windows and POSIX:
# Windows
Process.run("cmd /c NUL", shell: true).exit_code # => 1
Process.run("NUL", shell: true).exit_code # File::NotFoundError

# POSIX
Process.run("bash -c /dev/null", shell: true).exit_code # => 126
Process.run("/dev/null", shell: true).exit_code # => 126

Ah, hmm, I see. I'd expect exit code 126/127 to raise on POSIX systems anyway.
I spent an hour yesterday trying to figure out why Process.run wasn't raising, where the documentation mentions it should.

Yes, the documentation is incorrect when using shell: true on a POSIX system.


Routing with conditional parameter

Hi @gi0baro . The following works fine (for docs)
@mymodule.route("/profile(/<int:user_id>)?")
def profile(user_id):
    if user_id:
        # get requested user
    else:
        # load current logged user profile

But if I want to use it in the home of the module, it fails:
@mymodule.route("/(<int:user_id>)?")
def index(user_id):
    if user_id:
        # get requested user
    else:
        # load current logged user profile

http://<IP_ADDRESS>:8000/mymodule/ or http://<IP_ADDRESS>:8000/mymodule/1
I get Resource not found
Jose

@mymodule.route("(/int:user_id)?")
def index(user_id):
if user_id:
# get requested user
else:
# load current logged user profile

Thanks @tweenietomatoes, but I still get Resource not found

@josejachuf this is probably a bug regarding conditional parameters and first component of the route url. I will need to inspect this. Will update you.

hi @gi0baro Is this bug resolved?

@gaytomycode this was reported before 2.0, it needs to be verified


Automated UI Tests for iOS

Addresses tasks & features detailed at issue #39

ios-ci is failing due to make ui-tests.  Investigating if there needs to be a simulator associated with the build machine on GitHub Actions.

The GitHub checks for this commit can be found at #47/checks.
While browsing the log, look for "Running iOS UI Tests" you can use this example output as a starting point.
A typical output from the test runner can be found at Test Suite iosapp UITests.xctest, line 1846

Test Suite iosapp UITests.xctest started iosapp_UITests
✓ test_iosappScheme (10.181 seconds)
✓ testDebugBoundaryTiles (23.704 seconds)
✓ testLaunchPerformance (22.810 seconds)
✓ testRecord (3.343 seconds)

and Test Suite bench UITests.xctest, line 1862

Test Suite bench UITests.xctest started
bench_UITests
✓ test_benchScheme (103.902 seconds)

This PR is ready to be reviewed and, if approved, then it can be merged.


Deprecate in favour of vates pulumi provider

Hi @aslak11,
we have added a repository in the vatesfr github organization and rebuilt the pulumi provider using the boilerplate repository.
Would you be interested in contributing to the vates/pulumi-xenorchestra repo?
Also, we would like to publish an up to date package on pypi.org, could you transfer ownership to vatesfr?

The project pulumi-xenorchestra has been deleted.


Back off deploy loop error

This PR creates a global map of loggers for each app that deploy loop uses to keep track of last time an error was logged.  Errors are considered the same if the error text matches exactly.  And only last error is remembered, so if error changes every time, every error will be logged.  The period of silence is doubled every time the error is logged until the max of 30 minutes is reached.


Request: change artifact name or re-increase version

It seems that you recently reduced the version number of the latest version of this library from 2.6.12 to 2.4.17.x. It's rather undesirable to have a version number decrease, because it now means that all your users will get notices for the foreseeable future saying that their version is out of date. I'm having to put a comment in our build-management system saying "2.4 is actually newer than 2.6 as of March 2017."
So I'm requesting that you either change the artifact name or that you increase the version number to restore its monotonicity: newer versions should have a higher version number. It's your project, but I'll lay out a few reasons why I think you and your users would benefit.
I'm guessing that this was done to align with Akka. If you really want to communicate the dependency on a particular version of Akka, I would suggest that a better approach is to have an artifact name like akka-persistence-jdbc-akka2.4. This "qualifier" approach is standard practice for things like JDBC drivers, Scala libraries, etc—and it's even codified into the Maven artifact standard.
Besides the fact that it leaves you with a version-number decrease, piggybacking on Akka's version numbers poses a couple of additional challenges.
The first is that it takes away your ability to use your own version number to communicate the scope of changes. It's dangerous for people to rely on this too much, but users do gain information from knowing whether they are upgrading from 2.6.12 to 2.6.13 or 3.0.0.
It also means that you're somewhat obliged to push a release of your software every time Akka does a point release, even though Akka maintains binary compatibility. It seems unlikely that there's any actual problem with using akka-persistence-jdbc <IP_ADDRESS> with akka-persistence 2.4.16, but it may create confusion if Akka 2.4.18 comes out and you're still on 2.4.17.x.
I think it's worth noting that two projects in this space recently moved away from coupled version numbers for exactly this reason. Just in the last month or so Postgres decoupled the version of their database from the version of their JDBC drivers, for basically these reasons. Also, Akka decided to stop synchronizing the version numbers of Akka HTTP and Akka Core just a few months ago since they're not actually built together. (Akka HTTP went from version 2.4.12 to 10.0.0.)
Thanks for at least reading this and considering the request.

Hi Sarah. Thank you for the information and your suggestion. It gives food for thought and needs to sink in. I will park the issue for now, but will take it into consideration.

Thanks @dnvriend. 😄

In the next release two versions will be released: 3.0.0 for akka 2.5, and 2.7.0 for akka 2.4

Yesterday the versions 3.0.0 for akka 2.5, and 2.7.0 for akka 2.4 have been released. Therefore this issue has been resolved


[CJR] LE bus de CJR aux couleurs de CJR !

Is there an existing issue for this?

[X] I have searched the existing issues

In which category does your improvement fall?
BUS - CJR
Explain the current situation that you do not think is right.
le bus carl junior est avec un skin de base on aimerai un bus custo CJR
How is the improvement you propose?
on propose de mettre le bus de CJR au couleurs de CJR

Accepted. We'll be taking a closer look very soon. <3

Thanks for the proposition, it has been intégrated


[FLINK-12407][python] Add all table operators align Java Table API.

What is the purpose of the change
This pull request add all methods of Table and TableEnvironment to Python Table API except user defined function related, external catalog related and connector descriptor related methods.
Brief change log

Improve the functionality of Table and TableEnvironment in flink-python.
Add QueryConfig and improve the functionality of TableConfig.
Add window api, contains GroupWindow and OverWindow.
Add tests for these apis.

Verifying this change
This change added tests and can be verified as follows:

Added integration tests: test_batch_table_api.py, test_batch_table_environment_api.py, test_stream_table_api.py and test_stream_table_environment_api.py.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs)

@dianfu @sunjincheng121 Thanks for your comments, great help to me! I have addressed your comments and fix them in the new commit.

Thanks for the update @WeiZhong94!
I have added the API align check test, So please rebase the code, an open the check.
Best,
Jincheng

@sunjincheng121 Thank you for reminding! I have rebased my code and enabled the completeness tests.

@WeiZhong94 Thanks a lot for the updated. LGTM. +1 to merge.

@sunjincheng121 Thanks for your review again! For the documents translating, I have only translated the documentation added in this PR. Regarding to other documents that not changed in this PR, what about translating them in a independent PR?

Thanks for your updated!
And It makes sense to me about the doc. @WeiZhong94
+1 to merged.
@flinkbot approve all


Debug Mode

Would mostly enable debug() module calls, possibly logging them to a downloadable file as well (maybe with auto pastebin upload?) so people can share their logs easily.

Obsolete as of 26c3afe.


Set up manual keys

Can we set up key manually on android screen? Example: I want to open top left corner of my screen. I will set "k" key in that location. Whenever I will press "k", it will touch on that part of android screen.

#712


How to install?

Hi! Sorry for the dumb question but I've been trying to install this and I'm not sure how.
I'm using Neovim, and I'm testing LunarVim right now.
Should I install this plugin? Like Plug "RRethy/nvim-treesitter-endwise" or similar?
I'm asking because I configured it as documented but seems that It's not working.

Yes, you'll need to install the plugin following whatever the installation process is for your specific plugin manager, as well as doing the required configuration steps in the README.

Cool, after that and restart nvim everything works perfectly! Thanks, great work!

Try def foo<Enter>, def end isn't really valid Ruby so end won't be added for dev<Enter>.
Also, <Enter> == <CR> in Vim lingo.

That did it.  Thank you!


Moving last files unrelated to parcel layer to modules

Is this branch in a state that I can play with? it turns out I need to get libfabric stuff running again and I'll need a place to begin work. I should try to keep up to date with parcelport related changes.

Is this branch in a state that I can play with? it turns out I need to get libfabric stuff running again and I'll need a place to begin work. I should try to keep up to date with parcelport related changes.

John, I think you can start with master. I have not touched the parcelport yet (I did move one file only on this branch), you should be fine.

@hkaiser this looks like it would be ready for merging modulo formatting.

@hkaiser this looks like it would be ready for merging modulo formatting.

This is on my todo list for a while now. Will fix.


[Backport 2.x] Fix PSA RSA PSS verify with ALT implementations

This is the 2.x backport of #4665 - almost trivial except for two differences:

mbedtls_rsa_set_padding() returns void in 2.x instead of int in 3.0
mbedtls_rsa_rsassa_pss_verify() still has the mode and RNG parameters in 2.x

I think the places in PSA that end up calling set_padding do it on an RSA context that's internal to PSA and not supposed to be accessed directly by the user, so I don't think it's worth mentioning them here.


Change Y&X lines and background grid color

Is it possible to change default blue color, to my custom? I searched in all opened & closed issues, and didn't find any solutions.

+1

+1


Add aserver record

🌐 Link

Link: aserver.vrtxx.uk
📋 Checklist

[x] I have starred the repository.
[x] I have read and accepted the Terms of Service.
[x]  There is reasonable content on my site.
[x] I have configured a custom domain for my site.

Please allow TutorialMan7727 to edit and take over if necessary

Welcome! Your site is live at aserver.rweb.site 🎉


how can i dump pre-computed HLL to origin value

i found the metric tagged by HyperUnique is display as pre-computed HLL (base64 encoded string).How can i deserialize the base64 string to origin value

Do you mean the original value from your input data? It's not preserved (HLL is lossy) so you can't decode that. But you can load it into a Druid HyperLogLogCollector object if you want to look at it -- check out HyperUniqueSerde for an example.


Compute trace and determinant

The computation of eigenvalues can be used for the determinant, or perhaps there is a more specific LAPACK function

The Faq mentions:

Are there routines in LAPACK to compute determinants?
No. There are no routines in LAPACK to compute determinants. This is discussed in the "Accuracy and Stability" chapter in the LAPACK Users' Guide.

In gonum this is done using the LU factorization of the matrix.
var lu LU
lu.Factorize(a)
lu.LogDet()
det, sign := lu.LogDet()
math.Exp(det) * sign

Yeah, I know it's not very stable. There is no LU factorization here yet, but the Schur form can be used for now (although it is more costly; the determinant will be unstable for large matrices anyway)

https://github.com/unicredit/neo/commit/742c60f852a4d3ebc531b7089fb4cb9d2068b916 introduced the two functions. det can be optimized, but as remarked it only makes sense for small matrices anyway, so it not much of an issue for now

I'm too new to nim and this to make a PR, but I cobbled together a cholesky decomp. I'm not sure if I used the T right since I think that has to be float64 with the dpotrf call..
anyway here it is:
proc cholesky*[T](a: Matrix[T]): Matrix[T] =
  var
    h = a.clone()
    n = a.ld.cint
    info: cint
    ulo: cstring
  ulo = "L"
  dpotrf(ulo, addr n, h.fp, addr n, addr info)
  if info > 0:
    raise newException(LinearAlgebraError, "ERROR finding the LU decomp")
  for i in 0 ..< n:
    for j in i + 1 ..< n:
      h[i, j] = 0.0
  return h

awesome work on this package!


Idea: Open random book

As per the title. A button on the home page that opens a random book for studying/reviewing.

In the interest of backlog/feature management, I'm going to decline this one ... but perhaps someone else will see it and jump in :-)  Sorry @jamesdeluk , cheers and thanks for your other notes.

Fair enough! For now, I've made a simple bookmarklet. It only works for the books currently visible, but it does the job. I guess a "proper" implementation would use the database to get the book IDs.
var bookTitles = document.getElementsByClassName('book-title');
var hrefs = [];
for (var i = 0; i < bookTitles.length; i++) {
  var href = bookTitles[i].getAttribute('href');
  hrefs.push(href);
}
var randomIndex = Math.floor(Math.random() * hrefs.length);
var randomHref = hrefs[randomIndex];
window.location.href = 'http://localhost:5000' + randomHref;

And minified and as a bookmarklet:
javascript:(function()%7Bvar%20e%3Ddocument.getElementsByClassName(%22book-title%22)%2Ct%3D%5B%5D%3Bfor(var%20n%3D0%3Bn%3Ce.length%3Bn%2B%2B)t.push(e%5Bn%5D.getAttribute(%22href%22))%3Bvar%20r%3DMath.floor(Math.random()*t.length)%2Co%3Dt%5Br%5D%3Bwindow.location.href%3D%22http%3A%2F%2Flocalhost%3A5001%22%2Bo%3B%7D)()%3B

Well that's pretty slick :-)  Try it out for a while and see how it works for you.
Sometime I find that I want an idea, and then after I use it for a bit, I stop using it, because it doesn't really add much to my fun quotient.  I should really add an API for questions like your book IDs, but haven't thought much about it beyond "I should really add an API."

For context, I add one or two new books/articles every day, each only 100 words or so. Due to this, I will end up having a lot of books. For reviewing purposes, I'll be using my little random bookmarklet, as it will be easier (and more fun!) than clicking through each in order.

Hey that's fun.  Others might be interested in it, maybe post to the discord?  Cheers!

I don't really use Discord but feel free to post it on my behalf :)

Hey that's fun. Others might be interested in it, maybe post to the discord? Cheers!

I was thinking that Greasemonkey and userscripts could be useful for tweaking little things here and there. Might even help in testing some things. I'll keep a list of them - if more are created, we'll have a little collection.

Any semi-usable ones I'll share on Greasyfork, so they should show here: https://greasyfork.org/en/scripts?q=lute


Typing the date doesn't follow set format

If I have format set for example to "d.M.yyyy", like this:
<datepicker format="d.M.yyyy" :typeable="true">
And then I select 1st of June 2017, it shows up correctly as "1.6.2017", but then if I only change the year by manually typing "1.6.2018", it interprets the changed date as 6th of January 2018.

Same problem

Yes internally I parse the dates with Date.parse, so this will follow your locale I presume rather than the format you set in the datepicker.

I have the same problem. I want to write in pt-br format, but because my browser is defaul en, it does not let me use the correct format.

I have the same problem.
<datepicker :language="ptBR" format="dd/MM/yyyy" v-mask="'##/##/####'" :typeable="true" class="form-control" v-model="dt_ini" @keyup.enter="doFilter" ></datepicker>
If I type 15/06/2018 then press TAB, my input is cleaned.

Same here, so something like this is not possible as well (select month and year only with typeable) :
<datepicker v-model="product.release_date" format="MM/yyyy" :minimumView="'month'" :maximumView="'month'" :typeable="true"></datepicker>

I have the same problem. Would be grateful for a bug fix.

No bug, this is a new feature.
Happy to look at PRs as I don’t have time right now to develop this.

@charliekassel I wasn't talking about the problem from @julienmonty . I meant that I have the same problem as @peenorolampi .

This is down to javascript Date parse @RipkensLar interpreting in your locale and is directly related to us using the prop format to interpret the date.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse

I found a solution to the Date.parse problem. I don't know if it's the best approach, but it solved my problem, and I hope it can help someone else. I created a pullRequest #536. @charliekassel


Support png

Currently the tool assumes the name of the file is background.jpg. It should support png as well automatically.

The resolution order should be jpg, png, also names should be lowercase.

Hi @nbeloglazov do you still have the issue? Please let me know as I might help you get it done.  Best.


offered a fix for rechunking with zero-size-chunks

[x] Closes #5661
[x] Tests added / passed
[x] Passes pre-commit run --all-files

@TomAugspurger
I copied your tests (with a few modifications) which you recommended in #5661 to this PR.  These proved very useful in bringing about this fix.
@TAdeJong, may I invite you to test whether this PR fixes your problem with diagonal(A, k) or not.
To clarify: as you've mentioned already, diag(A, k) of #8689 does not depend on diagonal(A, k).  Nevertheless, since diagonal(A, k) depends on how dask handles zero-size-chunks, it would be prudent to check that diagonal(A, k) works under this PR.

The currently failing CI's seem to be unrelated to this PR.

I have also checked diagonal(A, k) myself and found it to be working under this PR. That is, the following code no longer breaks:
x = da.ones((8,8), chunks=(4,4))
dd = da.ones((8,8), chunks=(4,4))
d = da.diagonal(dd)
print(d.compute())  # works
print((d+d).compute())  # also works
A = (d + x)
A.compute() # no longer breaks.

and gives the right result, as far as I can see.

Hi @jcrist
Yes, in the diagonal PR #8689, I indeed completely avoided zero-size-chunks, but only for those routines: diag() and diagonal().  Elsewhere in dask, of course, is a different story.  But I'm hoping that this PR will at least help ease the handling of zero-size-chunks everywhere else in dask that they may appear.   For example, they appear quite naturally during the dask array-indexing routines and disappear again.
I'm not sure if we'll always be able to avoid zero-size-chunks throughout dask though, as doing so often seems to involve some clever chunk re-indexing schemes that are not always easy to come by.
My feeling (though don't quote me on this) is that there might exist a simple mathematical theory that clarifies and guides the the treatment of zero-size-chunks.  But I'm yet to explore this.

Hi @jcrist
Please examine the new diffs to see if the comments I've added are helpful or not. :smile:


Script could use checking for throttle_thermal_policy too

On my system (ASUS TUF A16 FA617NS-N3003 laptop, Linux 6.9.3, Arch Linux), the file /sys/devices/platform/asus-nb-wmi/fan_boost_mode does not exist. Instead, there is /sys/devices/platform/asus-nb-wmi/throttle_thermal_policy in the same directory, which otherwise is identical and performs the same function. Editing the script for myself to point it at that instead works, but this is probably better to be checked here too.
If the former file is not found, it may make sense to check for the latter?

The same on my Asus TUF F15 throttle_thermal_policy is used instead fan_boost_mode.


ES7 support in v3.13.x

Describe the bug
is that anyway to make ES7 support in v3.13.x ? i cant find the es7 folder in this version.

You need to import it from the community package - IMO ES7 should be the default now but for some reason Conductor is sticking to ES6. There are some docs kicking around on how to do this I think, but it's definitely not as easy as it should be!

ES7 source code https://github.com/Netflix/conductor-community/tree/main/index
ES7 artifact in central maven repo https://central.sonatype.com/artifact/com.netflix.conductor/conductor-es7-persistence/3.13.5

I'm 2nd to @bjpirt , +1 to get ES7 as default, as ES6 has been out of date for a long while


migrate to nodejs's native iterator API when napi-rs is ready

We rely heavily on napi-rs to implement our functions.
The following APIs are still in some sort of simulation and will be migrated to the native implementation when napi-rs is ready.

[ ] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/iterator
[ ] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/asyncIterator

Also see https://github.com/datafuselabs/opendal/issues/1525#issuecomment-1461494776
napi-rs side

napi-rs/napi-rs/issues/1493

Is there an issue at napi-rs side?

Updated.

list should return Vec<Entry> now. @suyanhanx, would you like to change the API of opendal-nodejs?

list should return Vec<Entry> now. @suyanhanx, would you like to change the API of opendal-nodejs?

I'll handle this.

Plan to implement the System.iterator on the js side. Close this issue now.


[Fix] Wrapper: Improve scroll smoothly

Overview
I have seen the position: fixed in .wrapper and it makes the content can't scroll smoothly.
So, I remove the fixed position by padding-top for header.
Scope of work
Remove position fixed and implement padding-top
If you have any feedbacks or suggestions, please do not hesitate to reply on this PR. 😎

@googlebot I signed it

@googlebot I signed it


Add SyntacticHeap Roots

Add concept of root for a SyntacticHeap which can be updated in place.  This is the root of all valid references within a SyntacticHeap.  It will require changing the binary format, presumably.

Done, easy.


Request ContentType

May I ask to consider use of ContentType?
The keyword "if"
import value from "module" if { type: "json" };

implies that request would be issued with ContentType:*/* and response would be discarded based on ContentType. Which is wasteful, we already know what we accept.
Mechanism already defined in HTML <script language=vbscript type=text/vbscript>. Unfortunately used by type="module" but
<script src="foo.css" type="text/css"></script>
<script src="foo.json" type="application/json"></script>
<script src="foo.wasm" type="application/wasm"></script>

makes no requests. So it can be defined as "import WASM module".
It covers the need for Content Negotiation:
<script src="foo" type="application/json,application/wasm;q=0.9">

may be not pretty, but functional, tested in transition to PNG.
Currently there is a need to define "new types", searching for "type that is not MIME type" may be hard. While we are half there with image/*, audio/*, video/*.
Please reconsider use of alias (iftype) as core dependency. It may be built on top:
import value from "module" with { typeAlias: "json" };
contentTypeAlias.define("javascript", "application/javascript,application/javascript-binast")
contentTypeAlias.define("json|wasm", "application/json,application/wasm;q=0.9")

Thank you.

It's currently unclear to us if we should communicate the expected type to the server, see https://github.com/whatwg/html/issues/5640.
My understanding is that content negotation is not what we want for the web anymore, it's documented here https://wiki.whatwg.org/wiki/Why_not_conneg.

The proposal has been updated to allow import assertions/attributes to affect the module loading process, so that HTML could send headers such as Accept: to the server.


CI failure in thunder/tests/test_grad.py::test_vjp_correctness_sort_torch_cpu_thunder.dtypes.float64

🐛 Bug
Encountered a CI failure in #710. Here is the link to the CI run that failed: https://github.com/Lightning-AI/lightning-thunder/actions/runs/9853856513/job/27205396177?pr=710
Below is the error message:
FAILED thunder/tests/test_grad.py::test_vjp_correctness_sort_torch_cpu_thunder.dtypes.float64 - AssertionError: Scalars are not close!

Expected 5.901072911436645 but got 5.884414821545493.
Absolute difference: 0.016658089891152805 (up to 1e-06 allowed)
Relative difference: 0.002822891725141778 (up to 1e-06 allowed)
= 1 failed, 2682 passed, 522 skipped, 61 xfailed, 95 xpassed, 64905 warnings in 635.13s (0:10:35) =
C:\hostedtoolcache\windows\Python\3.10.11\x64\lib\site-packages\coverage\control.py:888: CoverageWarning: No data was collected. (no-data-collected)
  self._warn("No data was collected.", slug="no-data-collected")

@nikitaved
cc @borda

Hmm, interesting. Well, the samples for sort that we are producing do not guarantee to be always differentiable. I expected to hit this issues later rather than earlier :) Let me fix that

Thank you @nikitaved !


Consider making it possible to evaluate strings like tagged template literals

As a web developer, a common issue I run into is wanting to format localized strings. For example, an email app might have text like this:

You have 5 messages in Travel

where the folder name is displayed in bold.
Right now, you need to encode HTML or other formatting into the string, which opens up issues with input sanitization.
You have {count} messages in ${folder}

It's also difficult to work with a framework like React, where you ideally want to build a JSX array like this.
['You have ', 5, ' messages in ', Travel]

Since MessageFormat already knows where the variables locations are, it would be great if it could be used to get an array of strings where variables could be interested later by developers.
This would be very similar to tagged template literals. As an alternative to returning a plain string, template literals can be combined with a tag function.
That tag function receives an array with the string parts, along with each variable as a function argument. It can then be used to return a new string, manipulate arguments, or return something else like an array.
As an alternative, it might be better for there to be some way to treat any string like a template literal.

This sort of use case is definitely within the intended use of the proposal. In particular, it's why the resolveMessage() method provides for an array of parts, rather than just a string. This makes it possible for the  wrapping of a part of the result to be defined in three different ways, each of which has its uses:

The value passed in as $folder could already be wrapped, so it's not a string but a JSX element.
The message itself could include markup from which the element is generated. The syntax we're settling on this would be something like {+strong}{$folder}{-strong}.
The relevant part could be identified from the output, and wrapped then.

Playing around with the polyfill, here's a possible solution following the third approach:
import { MessageFormat } from 'messageformat';

// Ignoring the singular case for simplicity
const mf = new MessageFormat('{You have {$count} messages in {$folder}}', 'en');
const res = mf.resolveMessage({ count: 5, folder: 'Travel' });
const parts = res.value.map(el =>
  el.source === '$folder' ? {String(el)} : String(el)
);

[
  'You have ',
  '5',
  ' messages in ',
  Travel
]

For complex use cases like DOM or React localization, we're not aiming to necessarily provide a direct solution, but the building blocks that allow for its construction.

Really great to hear! I focused on the motivation and use cases in the proposal and didn't realize ResolvedMessages include the lookup values. Hope to see this keep advancing :)


Very interesting library. but...

Very interesting library. What I fear the most is making compatible versions of RxUI and DynamicData, libraries that I use INTENSIVELY.
Without them working, I'm out of luck.
My suggestion is that you could talk with major library owners to make compatible versions so end devs like me could use R3 instead.
Anyways, heep up the good work!
I wish you luck.

GPT
AsSystemObservable and ToObservable support conversion to and from standard Rx, so it's not completely unusable.
However, it's undoubtedly difficult to use.
In R3, we have ReactiveProperty for UI support and ObservableCollections for collections,
but these are entirely different from ReactiveUI or DynamicData, so they cannot serve as a migration guide.
If R3 becomes widely used, there's a great chance it will be supported!
So, please start using R3 and help spread the word!


Intermittent test failures

This test fails from time to time, not clear why: https://github.com/java-operator-sdk/java-operator-sdk/runs/2131801927?check_suite_focus=true

Next time this happens could you take a screenshot or copy the info? These logs expire after a while, it would be nice to see them here.

Closing for now, if new tests fail, please open a new issue with the logs and error message.


chore: update usage docs for react-query example

Hello!
I saw this PR got merged: https://github.com/mrousavy/react-native-mmkv/pull/642
After some post-merge discussions in that PR, we came to the conclusion that it might be good to revert the instructions to how they were before, to be more in-line with usage within React.

Makes sense! Thanks


Social media cards for new posts aren't visible during the build

I just published https://til.simonwillison.net/til/til/cloudrun_using-gcloud-run-services-list.md and then noticed that the card image looks like this: https://til.simonwillison.net/-/media/screenshot/cloudrun_using-gcloud-run-services-list.md

That's because the script that fetches the previews ran during the build - so the page hadn't been deployed yet!

I need to be able to render the image before it's been deployed to the site. That's tricky. I may have to move my screenshot rendering into the GitHub Action itself.

Maybe use this: https://github.com/JarvusInnovations/puppeteer-cli

This worked:
npm install -g puppeteer-cli
puppeteer screenshot https://til.simonwillison.net/til/til/cloudrun_using-gcloud-run-services-list.md --viewport 800x400 --full-page=false > img.png

It works from disk too - so I can use datasette --get in combination of it to generate a screenshot:
datasette . --get /til/til/pytest_subprocess-server.md > page.html
puppeteer screenshot page.html --viewport 800x400 --full-page=false > img.png

I'll need to do this as a separate script from the original build_database.py.

This works now (I had to solve #25 on the way): https://twitter.com/simonw/status/1301029646033534977


No examples on v5.2.0

No examples on v5.2.0

What examples do you mean?
Here are the examples:
https://github.com/kxxt/aspeak#examples

I mean rust code examples

What examples do you mean?
Here are the examples: https://github.com/kxxt/aspeak#examples

I mean rust code examples on v5.2.0, please write some examples.
Thanks.

Two examples are added in v6.0.0-beta.1: https://github.com/kxxt/aspeak/tree/v6.0.0-beta.1/examples


bladebit_cuda *** Panic!!! *** Fatal Error:

From time to time, bladebit_cuda crashes. I guess it is nVidia driver/OS combo. Also most likely overheating issues. We have heat waves in Europe.  Reboot "cures" this issue...plotter runs many hours without issue. It may also be related to lack on space in destination drive, and plotter simply crashes instead of waiting for free space.
Once, plotting crashes...it will crash again until one reboots the rig.
SuperMicro X9DR7-TF+
2 x Xeon 2697v2
512GB DDR-1867MHz
ASUS RTX 3060Ti 8GB
Clear Linux OS (build 39830)
kernel 6.1.46-1306.ltscurrent
nvidia Driver Version: 535.98
CUDA Version: 12.2
./bladebit_cuda(_Z9PanicExitv+0xf)[0x560390015e9f]
./bladebit_cuda(_ZN10PlotWriter9WriteDataEPKhm+0x13e)[0x56038fffd05e]
./bladebit_cuda(_ZN10PlotWriter16WriterThreadMainEv+0x270)[0x56038fffda10]
./bladebit_cuda(_ZN6Thread17ThreadStarterUnixEPS_+0x80)[0x56038fe89ed0]
/usr/lib64/libc.so.6(+0x94f4a)[0x56038f694f4a]
/usr/lib64/libc.so.6(+0x122b08)[0x56038f722b08]
CUDA error: 4 (0x4 ) cudaErrorCudartUnloading : driver shutting down

*** Panic!!! *** Fatal Error:
CUDA error cudaErrorCudartUnloading : driver shutting down.
./bladebit_cuda(_ZN7SysHost14DumpStackTraceEv+0x5b)[0x56038fe8914b]
./bladebit_cuda(_Z9PanicExitv+0xf)[0x560390015e9f]
./bladebit_cuda(_ZN15GpuUploadBuffer11UploadArrayEPKvjjjjPKjP11CUstream_st+0x16a)[0x56038fe6d3da]
./bladebit_cuda(_ZN15GpuUploadBuffer11UploadArrayEPKvjjjjPKj+0x13)[0x56038fe6d6a3]
./bladebit_cuda(_Z10WritePark7R18CudaK32PlotContext+0x22c)[0x56038fe4fc4c]
./bladebit_cuda(_Z17CudaK32PlotPhase3R18CudaK32PlotContext+0x11e9)[0x56038fe46889]
./bladebit_cuda(_ZN14CudaK32Plotter3RunERK11PlotRequest+0x95b)[0x56038fe348bb]

second run...plotting crashes within a few hours again...only reboot helps.
*** Panic!!! *** Fatal Error:
Failed to write to plot with error 28:
./bladebit_cuda(_ZN7SysHost14DumpStackTraceEv+0x5b)[0x55c14940214b]
./bladebit_cuda(_Z9PanicExitv+0xf)[0x55c14958ee9f]
./bladebit_cuda(_ZN10PlotWriter9WriteDataEPKhm+0x13e)[0x55c14957605e]
./bladebit_cuda(_ZN10PlotWriter16WriterThreadMainEv+0x270)[0x55c149576a10]
./bladebit_cuda(_ZN6Thread17ThreadStarterUnixEPS_+0x80)[0x55c149402ed0]
/usr/lib64/libc.so.6(+0x94f4a)[0x55c148c94f4a]
/usr/lib64/libc.so.6(+0x122b08)[0x55c148d22b08]

Failed to write to plot with error 28: is running out of space on destination drive. We have this fixed in bladebit 3.1 beta1. should be ready for 256GB mode in 3.1 beta2.
for the first error, I have seen that, something about the crash that crashes the nvidia driver. Reboot will reload the driver or you can manually reload the nvidia kernel modules as a workaround. Haven't been able to reproduce that one though

Yes, it is definitely out of space + driver crash. Otherwise, it runs without issues.


Notifications not arriving

Hi there, I subscribed to receive Notifications about my Vercel builds, however, they're not arriving. I checked on Vercel and everything looks fine with the integration, notifications are enabled in the app.
What could cause this?
Thanks!
Nils

It started working now, but kinda annyoning there's no answer on this after 4 days. Afterall, it's a paid service.


Variable length fields

As far as I can tell, the behavioral model seems to miss support for variable length fields. From a quick look at the source code it looks like adding this would mean moving some stuff around. Is anyone working on adding this, or is this a lower priority thing?
In general it would be useful to outline what's missing somewhere, e.g. in the README.
Thanks

You are right, there is no current support for variable length headers in the behavioral model and I don't have time to add support in the near future. Of course anyone is welcome to contribute a patch, but I think supporting this feature would require some big changes.
Will try to update the README with current limitations of the model soon.


case insensitive headers

Hi, Just noticed this.
Headers are supposed to be case insensitive.
Wouldn't  it lead to confusion?

I just noticed that. My bad


[PL-48351] Add doc to install the Azure CLI

PL-48351 Add doc to install the Azure CLI
For reviewers, a preview is available:
--preview building--
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screenshot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66073448b87aa360004345ea--harness-developer.netlify.app


Polish Levels

Remove moving block from Level 1
Level 2 is too finnicky. Possible solution: move two narrowing blocks further from lens. Remove single moving block.
Some level 3 walls are unaligned.
Level 4 left route needs tweaking. Maybe remove one of the three moving blocks and move florida man?

Polished levels 2-4, using the suggestions above. Level 4 Florida Man has been moved up and right a little.


Should be able to write test result and output to file as artifact

Also able to generate graph image


services/horizon: Reap history object tables when ingestion is idle

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
This commit adds code responsible for clearing orphaned rows in lookup historical tables. Orphaned rows can appear when old data is removed by reaper. The new code is separate from the existing reaper code (see "Alternative solutions" below) and activates after each ledger if there are no more ledgers to ingest in the backend. This has two advantages: it does not slow down catchup and it works only when ingestion is idle which shouldn't affect ingestion at all. To ensure performance is not affected, the ReapLookupTables method is called with 5 seconds context timeout which means that if it does not finish the work in specified time it will simply be cancelled.
The solution here requires new indexes added in c2d52f0 (without it finding the rows to delete is slow). For each lookup table, we check the number of occurences of a given lookup ID in all the tables in which lookup table is used. If no occurences are found, the row is removed from lookup table.
Rows are removed in batches of 10000 rows (can be modified in the future). The cursor is updated when tables is processed so after next ledger ingesion the next chunk of rows is checked. When cursor reaches the end of table it is reset back to 0. This ensures that all the orphaned rows are removed eventually (some rows can be skipped because new rows are added to lookup tables by ingestion and some are removed by reaper so offset does not always skip to the place is should to cover entire table).
Close [partially] #4396.
Alternative solutions
While working on this I tried to implement @fons'es idea from #4396 which was removing rows before clearing historical data which are not present in other ranges. There is a general problem with this solution. The lookup tables are actively used by ingestion which means that if rows are deleted while ingestion reads a given row it can create inconsistent data. We could modify reaper to aquire ingestion lock but if there are many ledgers to remove it can affect ingestion.
We could also write a query that finds and removes all the orphaned rows but it's too slow to be executed between ingestion of two consecutive ledgers.
Why
While Horizon removes history data when --history-retention-count flag is set it doesn't clear lookup historical tables. Lookup tables are [id, key name] pairs that allow setting pointers to keys in historical tables, thus saving disk space. This data can occupy a vast space on disk and is never used when old historical data is deleted.
Known limitations
[TODO or N/A]

I'm going to merge this without 👍 to start testing a new release. Please add comments and I'll open another PR with review fixes/requests.


Don't show loading component until pastDelay === true

Awesome library, I'm really glad I found it! Really makes lazy-loading a breeze! 🌬🍃 One thing I noticed is the delay prop does not currently work. This PR adds an extra check for this.state.pastDelay before showing the loading component.

Should check it in the loading component

@blling thanks, I guess I kinda skimmed over the README. Passing a prop to the loading component makes sense for the error state, but I'm not sure why the responsibility for delay is passed off to the user. In case someone wants to have two different loading states?


Consider Fat LTO instead of Thin LTO for the project

Problem
It's not a problem - it's an improvement idea for the project.
Feature
I decided to experiment with more optimized LTO versions for the project and switched from Thin LTO to Fat LTO plus experimented with codegen-units = 1 option. I have made quick tests (Fedora 41, Rust 1.82, the latest version of the project) - here are the results for the tv binary:

Release + codegen-units = 1: 11 Mib
Release + Thin LTO (current default): 14 Mib
Release + Fat LTO: 11 Mib
Release + codegen-units = 1 + Fat LTO: 9.7 Mib
Release + codegen-units = 1 + Thin LTO: 11 Mib

I think it could be worth to switch to Fat LTO and/or enable codegen-units = 1.
Examples
N/A
Additional context
N/A

Thanks for the feedback, opened a PR 🙏🏻


[1.19.2] Crash when chopping a tree

crash-2024-12-22_18.45.29-server.txt

crash does not occur on version 0.18.6

Thanks for reporting. It's a conflict with terraformers. Open config/treechop-common.toml and set terraformers = false in the Compatibility section


production.ERROR: No application encryption key has been specified.

Hello!
I get this error

production.ERROR: No application encryption key has been specified.

when I frequently (more than 3 times/second) send requests to the server using AJAX (axios exactly).
I wonder why it is production.ERROR, because in my .env it is APP_ENV=local. Obviously, my APP_KEY is present.
Full trace:
[2018-10-06 11:09:05] production.ERROR: No application encryption key has been specified. {"exception":"[object] (RuntimeException(code: 0): No application encryption key has been specified. at <>\\vendor\\laravel\\framework\\src\\Illuminate\\Encryption\\EncryptionServiceProvider.php:42)
[stacktrace]
#0 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Support\\helpers.php(1038): Illuminate\\Encryption\\EncryptionServiceProvider->Illuminate\\Encryption\\{closure}(NULL)
#1 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Encryption\\EncryptionServiceProvider.php(46): tap(NULL, Object(Closure))
#2 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Encryption\\EncryptionServiceProvider.php(24): Illuminate\\Encryption\\EncryptionServiceProvider->key(Array)
#3 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(749): Illuminate\\Encryption\\EncryptionServiceProvider->Illuminate\\Encryption\\{closure}(Object(Illuminate\\Foundation\\Application), Array)
#4 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(631): Illuminate\\Container\\Container->build(Object(Closure))
#5 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(586): Illuminate\\Container\\Container->resolve('encrypter', Array)
#6 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Foundation\\Application.php(732): Illuminate\\Container\\Container->make('encrypter', Array)
#7 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(885): Illuminate\\Foundation\\Application->make('encrypter')
#8 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(813): Illuminate\\Container\\Container->resolveClass(Object(ReflectionParameter))
#9 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(780): Illuminate\\Container\\Container->resolveDependencies(Array)
#10 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(631): Illuminate\\Container\\Container->build('App\\\\Http\\\\Middle...')
#11 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Container\\Container.php(586): Illuminate\\Container\\Container->resolve('App\\\\Http\\\\Middle...', Array)
#12 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Foundation\\Application.php(732): Illuminate\\Container\\Container->make('App\\\\Http\\\\Middle...', Array)
#13 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Foundation\\Http\\Kernel.php(215): Illuminate\\Foundation\\Application->make('App\\\\Http\\\\Middle...')
#14 <>\\vendor\\laravel\\framework\\src\\Illuminate\\Foundation\\Http\\Kernel.php(189): Illuminate\\Foundation\\Http\\Kernel->terminateMiddleware(Object(Illuminate\\Http\\Request), Object(Illuminate\\Http\\JsonResponse))
#15 <>\\public\\index.php(60): Illuminate\\Foundation\\Http\\Kernel->terminate(Object(Illuminate\\Http\\Request), Object(Illuminate\\Http\\JsonResponse))
#16 {main}
"}

Route, connected to the issue has GET method and auth middleware.
Responsible route's method resturns collection:
    $users = User::select(...)->get();
    return response($users);

This issue happens time-to-time, but I'm worried about getting it on product staging.

You should cache your config with php artisan config:cache so that this issue doesn't happen. As to why it does happen without config cache - it's a long story :)

I have some lines of code that reads from the .env file using the function env(). For instance,
'client_secret' => env('PASSWORD_CLIENT_SECRET'),
If I cache the .env file then, the function env() returns null. I would like to understand why I have to cache the .env file to avoid the error "No application encryption key has been specified", why the error ocurrs when the file is not cached and finally, why the env() function doesn't work when the .env file is cached.
Of course, I have setted up my APP_KEY in my .env file.

i think the overall issue here is that reading the .env file has problems when you have too many requests
caching the config is a solution to this
the problem with env helper returning null is because you are using it outside the config files, which the docs have a warning against fir this reason

pudiste solucionarlo, tengo el mismo problema! en local funciona pero no cuando deployo en versel

You should cache your config with php artisan config:cache so that this issue doesn't happen. As to why it does happen without config cache - it's a long story :)

It works when cached, otherwise issues. Can someone explain why it happens anyway?


test_long_timeline_create_cancelled_by_tenant_delete is flaky

Example: https://neon-github-public-dev.s3.amazonaws.com/reports/pr-7154/8322014390/index.html#suites/3556ed71f2d69272a7014df6dcb02317/aaf0b71ba586a08f

I've managed to reproduce this failure locally with 16 test instances running simultaneously. It looks like the issue was fixed with https://github.com/neondatabase/neon/pull/8082. On 15728be0~1, this test fails for me on iterations 1, 2, 2, but on 15728be0 10 iterations passed (twice).


CIFUZZ-528: add action to list findings as github checks

Did you configure any project to use this GitHub Action, so that I can look at what the results look like?

Hi Adrian, here you can see the triggered action:
https://github.com/CC-CIFUZZ-TEST/lighttpd/pull/15


[sqlserver dialect] Duplicate key row error is skipped

GORM Playground Link

https://github.com/go-gorm/playground/pull/180
Description
When using sqlserver dialect Create method silently fails on duplicate insert - no error returned. Expected result would be for Create method to return relevant error.
In the same time Create method works correctly for postgres dialect in the same situation.

If I traced it correctly, there is a rows.Err() check is missing for this call https://github.com/go-gorm/sqlserver/blob/master/create.go#L118 after rows.Next() sections.

https://github.com/go-gorm/sqlserver/blob/86e3f937aa20e6d4b7b37569a0e8f9c1bdc79e3b/create.go#L163
Added here. I have checked, the driver doesn't returns any errors in this case, so we can't fixed that ;(
Maybe should open an issue on the sqlserver driver side
Thank you for your report

@jinzhu I debugged driver a bit, it does return an error the problem is it will return error via rows.Err() after rows.Next() is called at least once. I agree, conventionally it should be returned by QueryContext itself.
This can be easily fixed of in Create method if we will check rows.Err() value after calling rows.Next(), it is also recommended in the database/sql.Rows docs example.

@jinzhu could you please reopen this issue? This bug is definitely in gorm sqlserver driver.

Fixed, thank you for your report.


Example of GenerateJson : 'verify-email' field missing in description but present in outputClaim (json string)

[Description missing for "verify-email" field]

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

ID: bc19c543-3efb-08a2-55a0-fd8b9b35db7e
Version Independent ID: 4704812b-44bb-831a-04a3-8c5a2ae5cf8b
Content: JSON claims transformation examples for custom policies - Azure AD B2C
Content Source: articles/active-directory-b2c/json-transformations.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@raju-thorat
Thanks for your feedback! We will investigate and update as appropriate.

@raju-thorat
Thanks for your pointing this out! I've assigned this issue to the author who will investigate and update as appropriate.

@raju-thorat
We've updated the document in another PR, and the changes are live. #please-close


Segmentation violation error in concurrency test after recall test with IVF_PQ

I ran a recall benchmark test using a 49K vector dataset (hdf5 file for data and recall config file attached) with IVF_PQ index. It ran fine and a valid output was created (also attached). This was the command line for the recall test:
python3 main.py recall --host localhost --engine milvus --dataset-name yoochoose-item
Then I run a concurrency test on the same Milvus collection (concurrency config file attached), and Milvus server generated a "segmentation violation" error and crashed. The command line was:
python3 main.py concurrency --host localhost --engine milvus
Attached is the output from Milvus server screen and the main.py output screen that show 100% failure on all concurrency requests.
No problems with recall using HNSW index followed by concurrency test.
Code is based on: https://github.com/zilliztech/vectordb-benchmark.git
yoochoose-item.hdf5.zip
config_yaml.zip
recall_output.txt
concurrency_error_server.txt
concurrency_output.txt

/close


Errors inside kubeconfig sa setup are ignored

https://github.com/interTwin-eu/interLink/blob/f53c66e730f0c70d21edcc8aa4f7d690b69a8185/pkg/common/func.go#L148C5-L148C5
@Surax98 high prio

I'm not getting what you mean. Errors are detected and returned from the function. In the VK package the error is then checked:
https://github.com/interTwin-eu/interLink/blob/f53c66e730f0c70d21edcc8aa4f7d690b69a8185/pkg/virtualkubelet/virtualkubelet.go#L157

to be closed @dciangot


Determine country from SIM

It would be nice if countrypicker could determine the country by the SIM card
Similarly to how it's done with mukeshsolanki/country-picker-android:
val countryPicker = CountryPicker.Builder().with(this).build()
val country = countryPicker.countryFromSIM

Implementation: https://github.com/mukeshsolanki/country-picker-android/blob/master/countrypicker/src/main/java/com/mukesh/countrypicker/CountryPicker.java#L545

I thought about this, but don't know where should default country picking works UI-wise. When I have free time I will display this default option as ListView header.


Recovery services backup october release

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

    "description": "Validate operation for specified backed up item in the form of an asynchronous operation. Returns tracking headers which can be tracked using GetValidateOperationResult API.",

do you mean: backupValidateOperationResults ?

Refers to: specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2021-10-01/bms.json:2595 in 8aa4223. [](commit_id = 8aa4223dfdb2fe533a5298c8ed6047f2aba234d8, deletion_comment = False)

    "description": "Validate operation for specified backed up item in the form of an asynchronous operation. Returns tracking headers which can be tracked using GetValidateOperationResult API.",

do you mean: backupValidateOperationResults ?
Refers to: specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2021-10-01/bms.json:2595 in 8aa4223. [](commit_id = 8aa4223, deletion_comment = False)

These changes were done as part of this PR https://github.com/Azure/azure-rest-api-specs/pull/16402
I had pulled in these changes in my current PR since it was causing a merge conflict.

        "$ref": "./examples/AzureIaasVm/ValidateOperationStatus.json"

For some reason I am not seeing this file in your PR.
Refers to: specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2021-10-01/bms.json:2744 in 8aa4223. [](commit_id = 8aa4223, deletion_comment = False)

Same.  https://github.com/Azure/azure-rest-api-specs/pull/16402

        "$ref": "./examples/AzureIaasVm/ValidateOperationResults.json"

For some reason I am not seeing this file in your PR.
Refers to: specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2021-10-01/bms.json:2692 in 8aa4223. [](commit_id = 8aa4223, deletion_comment = False)

Same.  https://github.com/Azure/azure-rest-api-specs/pull/16402


TypeError: place is not a function

Hello,
I'm using react-codemirror and I've installed code mirror with npm i -S codemirror
TypeError: place is not a function
	  if (place) {
	    if (place.appendChild) { place.appendChild(d.wrapper) }
	    else { place(d.wrapper) }
	  }

else { place(d.wrapper) } is throwing the error.  Is this a react-codemirror bug or a codemirror bug?
The header for that section of code has // CodeMirror, copyright (c) by Marijn Haverbeke and others  am I missing a library?
├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>

You're passing a value of the wrong type to the CodeMirror constructor. This is not a CodeMirror bug -- it might be a react-codemirror bug or a problem in the way you're using the library


historyextra.com is broken by any AdGuard extension

Original issue: https://github.com/AdguardTeam/AdguardFilters/issues/141249#issuecomment-1410572263
Steps to reproduce

Disable Base filter or the rule in Base filter @@||historyextra.com^$extension
Enable any AdGuard extension
Go to https://www.historyextra.com/period/modern/britain-strikes-history-industrial-action/

Actual behavior
When enabled any AdGuard extension, the site is broken (loads for a second and content is suddenly deleted).
The site is not broken, when extensions module is enabled, but all extensions are disabled.
Browser: Chrome 109
AdGuard for Windows 7.12 and AdGuard for Mac <IP_ADDRESS>4

If I'm not wrong, it looks like that it's related to - https://github.com/AdguardTeam/CoreLibs/issues/1701 and https://github.com/AdguardTeam/CoreLibs/issues/1571
This rule:
historyextra.com#%#(function(){window.DD_LOGS={onReady(){},logger:{log(){}}}})();

seems to works fine in this case too.

Ok, added your rule.


Leon A - Crash After Leaving Cable Car After Birkin Attack

Version: BioRand 2.1.7
Seed: R520-FX0A-ZTBE9MQLL16Q
Can't tell if it was the room or the enemy that caused the crash. Screen went black once I opened the door.
Thank you so much for making this
randomizer!

log_pl0.txt

This room tended to crash when you the partner and random enemies spawn. This should be fixed in the dev. builds.

Sounds good. Were you keeping issues open until they are fixed in the next release? Or did you want me to close this one?

Duplicate of #193

Sounds good. Were you keeping issues open until they are fixed in the next release? Or did you want me to close this one?

I think it is the same as #193, so I have closed it as duplicate.


Reorganize repo and test shuffles

:tada: This PR is included in version 1.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


adjust font size to make Navbar responsive

Fixes Issue #583

Changes proposed
What were you told to do ?
need some spacing for the navbar in mobile view

What did you do ?
Added Font Size to make responsive

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

Screenshots

Before

After

Hello @rohit-rambade Thankyou for making the PR but unfortunatey you never commented on the issue and got it assigned. Someone else was talking in the issue's comment and i think they should work for it.
Closing the PR, keep looking for more issues/ Create your own


[v1.27] Work around upgrade bug from versions that don't support TPROXY.

Description
Set the TPROXYMode to nil instead of "Disabled" to avoid confusing older felix versions that don't understand the new config field.

For PR author

[x] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

Are you planning on adding this to the master branch and release-1.28 also? From the discussions it sounded like it should go in those also.

Yes, I think the current version is reasonable to ship across the board.  I'll pick it over.

Thanks Shaun.
As to tmjd's question, thanks for bringing that up. We are looking to bring this to v3.15.1 as well which is scheduled within the next month give or take.


GEODE-567: Wait for async datastore creation to reach appropriate point

This test appears like it was trying to test what happens if a put
happens when data store creation is at a particular point.
Unfortunately, it failed to do so correctly because it just spun off the
data store creation in separate threads and then did the put. The wait
criterion used was also completely wrong, so the test would always wait
for 1 minute.
Finally, there were some race conditions caused by passing the same
array list to multiple async task.
Changed the code to wait until the data stores are at the given point in
region creation and then do the put.
Thank you for submitting a contribution to Apache Geode.
@balesh2 @mhansonp

Looks like the build is failing due to Spotless violations?


WIP: Restarting pods

What this PR does / why we need it: This PR allows cert-manager to restart pods that mount a secret with a refreshed certificate.
The use case for this is when a certificate expires and cert-manager refreshes the certificate, the service running inside the pod may not be able to pick up the certificate. Having the pod be restarted when a certificate is refreshed allows the service running within the pod to pick up the new certificate.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1440
Special notes for your reviewer:
This adds an additional command line flag --enable-pod-restart to allow this feature to be turned on. This feature is turned off by default.
Release note:

When a certificate is refreshed, it allows cert-manager to refresh pods that mount that certificate.

Hey, thanks for the PR!
I don't think we want to explore this as an option right now in cert-manager, as it's outside of our scope.
cert-manager itself currently deals specifically with delivering the TLS secrets, not getting involved with the complexities of how those certificates are then used.
It may be something we explore in future, but if we do it'll likely be a separate controller/project altogether.
There's currently some discussion in #1168 about documenting a 'best practice' for how to achieve this, and one commenter linked to https://github.com/pusher/wave which appears to do what you want:

Wave watches Deployments within a Kubernetes cluster and ensures that each Deployment's Pods always have up to date configuration.
By monitoring ConfigMaps and Secrets mounted by a Deployment, Wave can trigger a Rolling Update of the Deployment when the mounted configuration is changed.

It'd be awesome if you could give the pusher solution a try, and maybe write a tutorial that explains how to use these two together 😄

Thanks @munnerz! I'll look into the solution you linked and I understand. Should I close this PR?

Yep, but thanks again for putting it together 😄
If you've got any other ideas for extensions you'd like to see, it can help to ping the #cert-manager-dev channel on Kubernetes Slack, or otherwise open an issue against the repo so we can discuss a way forward without taking up so much of your time in future!
/close

It's needed. ЭТО НУЖНО


added barcode visualization

function plot_barcode() added

I don't know why The Travis CI build failed.

It looks like Travis is failing because you are using python 2.7 syntax for print. Try wrapping the string in paren like ‘print(contents)’

Codecov Report

Merging #15 into master will decrease coverage by 6.11%.
The diff coverage is 6.89%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   78.84%   72.72%   -6.12%
==========================================
  Files           9        9
  Lines         312      341      +29
  Branches       72       78       +6
==========================================
+ Hits          246      248       +2
- Misses         53       80      +27
  Partials       13       13

Impacted Files
Coverage Δ

persim/visuals.py
61.62% <6.89%> (-27.85%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f234f54...b830d1a. Read the comment docs.

Codecov Report

Merging #15 into master will decrease coverage by 6.11%.
The diff coverage is 6.89%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   78.84%   72.72%   -6.12%
==========================================
  Files           9        9
  Lines         312      341      +29
  Branches       72       78       +6
==========================================
+ Hits          246      248       +2
- Misses         53       80      +27
  Partials       13       13

Impacted Files
Coverage Δ

persim/visuals.py
61.62% <6.89%> (-27.85%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f234f54...b830d1a. Read the comment docs.

Good, I fixed it now and the test passed successfully.

Any news in this direction, to have the function merged in the official code?

Hey sorry for the delay. I haven’t had the opportunity to give it a good review. Could you include a few examples of the output so I can see how it looks? It might be faster for me to nitpick the design that way.

Thanks.
I don't know how to add only the images on git so I am sending it here.
Can you confirm that you got them?
Regards.
Thiago
Em qua, 19 de jun de 2019 às 22:51, Nathaniel Saul<EMAIL_ADDRESS>escreveu:

Hey sorry for the delay. I haven’t had the opportunity to give it a good
review. Could you include a few examples of the output so I can see how it
looks? It might be faster for me to nitpick the design that way.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scikit-tda/persim/pull/15?email_source=notifications&email_token=ADT2OBKQKN4S4RBSEK5XPCTP3LPBBA5CNFSM4HGZMHGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYDYGQQ#issuecomment-503808834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADT2OBNVGPGBF4L5DZIQOBTP3LPBBANCNFSM4HGZMHGA
.

--
Thiago de Melo

Hey sorry for the delay. I haven’t had the opportunity to give it a good review. Could you include a few examples of the output so I can see how it looks? It might be faster for me to nitpick the design that way.

Awesome, some suggested edits:

don't show the numbers on the y-axis.
can you plot 0d and 1d on the same plot?
what does the red dotted line represent?

* don't show the numbers on the y-axis.
* can you plot 0d and 1d on the same plot?

Good idea!

* what does the red dotted line represent?

It represents the maximal epsilon used. I'll work on your suggestions.


Not finding any PortMappers

Hello. I was trying to use this library to setup some port forwarding, but I found out that that PortMapperFactory.discover is not returning any PortMappers. I dont know if that is just something about the network I am on, or a problem with the library, but I wanted to ask just in case.
Here is the log https://gist.github.com/minecreatr/def8b7c6362a4d12740521805acc2371 .
My code is the same as your example, as I just wanted to check if it was working first.
Thank you`

I'm at work but I can take a look when I get home in a few hours. Can you
set logging level to debug and post the full logs? It'll show network
traffic.
That error is superfluous. It's just the library trying to run some Linux
commands. Since you're not running Linux, you're seeing errors for those
Linux commands. The equivalent Windows commands are being run as well and
succeeding, so you aren't seeing errors for those.
On May 31, 2017 1:35 PM, "Minecreatr"<EMAIL_ADDRESS>wrote:
Hello. I was trying to use this library to setup some port forwarding, but
I found out that that PortMapperFactory.discover is not returning any
PortMappers. I dont know if that is just something about the network I am
on, or a problem with the library, but I wanted to ask just in case.
Here is the log https://gist.github.com/minecreatr/def8b7c6362a4d12740521805
acc2371 .
My code is the same as your example, as I just wanted to check if it was
working first.
Thank you`
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/offbynull/portmapper/issues/35, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGD4In8lyhUn7uh7m2CKtDBMssc0MTjTks5r_c8PgaJpZM4NsKHG
.

Hi again,
I understand that you closed my previous ticket, and I'm sorry for being late on this. Since this issue is the same as mine, I'll post my logs here: https://gist.github.com/adam-law/f219ddecf7ca9ffc749463a219d98fb9
I had time to trace through the source, and as far as I can tell, while the correct service descriptor for the router was collected, the accompanying identified services was empty. While running through its processes, PortMapper was able to open a (random?) port on the router, though no mapper was added to the identification list.
As for your question about the jar dropin, I got it through maven, & I believe all the dependencies exist within our project already.
Thanks :)

What's the name of the network interface the Netgear router is attached to. What's the IP of that network interface?

Just the default. From ipconfig: Ethernet Ethernet Adapter <IP_ADDRESS>

@offbynull I am experiencing this same issue. UPnP is definitely available (I tested with weupnp), so it find at least one mapper

Hey, I don't have the capacity to keep up with this project anymore. There
are too many routers out there / too many configurations to keep up with.
Your best bet is to migrate to miniupnpc. It's a native library but you can
make Java bindings to it (if some don't exist already).
On Wed, 17 Nov 2021 at 05:54, Inze Bielderman @.***>
wrote:

@offbynull https://github.com/offbynull I am experiencing this same
issue. UPnP is definitely available (I tested with weupnp), so it find at
least one mapper
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/offbynull/portmapper/issues/35#issuecomment-971460755,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQPQIXTSG4LFG643LH4I7DUMOCVHANCNFSM4DNQUHDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Pasting duplicated a string.

You fixed the issue where pasting in the filter field duplicated the string, now pasting in a field to edit data still duplicated.

Thanks feedback, I will fix it in the next version.


Monorepo - Cross reference to other package not resolved

Search terms
Cross reference other package not resolved
Expected Behavior
When I have a monorepo with multpple packages, and I create typedoc via "packages", I expect that types defined in one package but used in another package are properly linked from the other package to the one package.
Actual Behavior
These types do not become links, but they are plain text.
Steps to reproduce the bug
See https://github.com/TypeStrong/typedoc-repros/pull/32
The readme contains repro steps + some additional observations.
Environment

Typedoc version: 25
TypeScript version: 4.9.5
Node.js version: 18.13.0
OS: Windows

The code for inherited links predates all of the work for packages mode, and it looks like I missed it when implementing that feature... I'm not seeing an immediately obvious reason why I can't switch it to use symbol references now and just see it work.
Method parameters, property types, etc. should all just work.

Thank you for your reply. I do not quite understand your wording. Do you mean you will investigate and try to switch to symboil references for my use cases? Or can/should I do that locally?
For method parameters, that also does not work. I have updated the example. So it appears that (at least for me) they do not 'just work'.
By the way -- compliments for the many improvements of TypeDoc over the last year or so. It is really looking much better, and monorepo also works very nice. It's just these little things I observe now :D

Duplicate of / closely related to new issue https://github.com/TypeStrong/typedoc/issues/2420

For me, cross-project links work if packages have "types" point to a .ts file and not to a .d.ts file. See sample project.

I'm currently working around this with a custom unknownSymbolResolver. It's very fragile, but it mostly works.

Short story: You can get the behavior you want by turning on the declarationMap compiler option, and recompiling. In 0.25.3, you shouldn't need this compiler option anymore.
Looking at all three of #2428, #2420, #2416 when not on antihistamine makes me really concerned with anything I did last week... TypeDoc already correctly creates inheritance links with cross-references as it should, so my previous statement was just flat wrong.
To determine how to link files between packages, TypeDoc needs to be able to determine what file they'll be defined in. In 0.25.2, this is completely reliant on the existence of declaration maps, which seems to only be documented in a passing mention in the beta release issue for v0.24... However, when running in packages mode, there's really no reason that TypeDoc shouldn't be able to tell where files come from for the converted packages, since we have the compiler options and the file names which will be compiled.
I'm making an update to TypeDoc which will use this to derive source file names. I was hopeful that doing this would remove the requirement to build all the packages before running TypeDoc on them, but unfortunately this isn't quite enough since TypeScript (at least with a references based monorepo) requires that sub-projects be built. If emit is set to both when converting earlier projects, and projects are passed to TypeDoc in the order that they need to be built, TypeDoc's emit can be used rather than a pre-build, but it's easier to tell people to just build with tsc first, particularly since TypeDoc doesn't do any project dependency tracking.

I'm currently working around this with a custom unknownSymbolResolver. It's very fragile, but it mostly works.

I am surprised that works at all, TypeDoc was supposed to handle escaping, but it looks like I mistakenly assumed that \\" wouldn't close an attribute... I'm going to fix that now...

I suspect the declarationMap issue not working is because I forgot to test on Windows, and paths are annoying...
The inheritance hierarchy is interesting, the way that's built today has always felt fragile to me... I'm going to look at improving it in a way which should also solve the cross-package inheritance issue.

I've decided to pull smarter hierarchy detection out into #2467 to avoid having to read through this issue every month or so when I forget what the actual remaining work for it is. I believe this is the only open problem still.

I've decided to pull smarter hierarchy detection out into #2467 to avoid having to read through this issue every month or so when I forget what the actual remaining work for it is. I believe this is the only open problem still.


use self hosted runner

The CI cluster config file also needs to commit to the git repo. @yourmoonlight


xml file stays opened after reading

After opening a xml file with XML::Document.file I can't delete the opened file until ruby exits. A function for closing the file after the read process would solve the problem.

This no longer seems to be the case (the file is closed).  Note this functionality is handled by libxml2, not the ruby bindings.


refactor: update sql schema autogen tool

Description
Replacement of dbviz, schema generation tool with SchemaSpy. Removal of old references to dbviz in the postgres earthly target and Catalyst-CI Postgres Example
Output Link For Docs:
https://input-output-hk.github.io/catalyst-ci/branch/chore_update_sql_schema_autogen_tool/appendix/examples/
Related Issue(s)
https://github.com/input-output-hk/catalyst-ci/issues/315
Description of Changes

Modified the SQL schema autogen tool to removing existing dbviz tool and replacing with SchemaSpy for automated schema generation.
Improved documentation around tooling,removing references no longer relevant to SchemaSpy autogen tool.
Added markdown template and custom script to ensure the auto-generated SchemaSpy UI displays correctly and fills the screen removing double scroll bars in the view.
Added Java Eartly stage to use as a base from which to copy necessary files during document build stage and improve caching.
Refactored how Java dependencies are downloaded and cached. Added a base image openjdk:21-jdk-slim to avoid network calls like apt-get running on every build. This caches the Java installation and other dependencies to avoid unnecessary network calls during a build.

Please confirm the following checks

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream module

Also, because its no longer used, we can totally remove the dbviz tooling from this repo.  Add that to this PR.


MajorVersion and MinorVersion is coming from external input and it ma…

…ybe greater than ten.
fix: #699
Signed-off-by: Zhao, Zhiqiang<EMAIL_ADDRESS>

Would you please clarify the call stack for this error?
How the version is propagated from external to this libspdm_create_signing_context()?
I think checking version should be the first step for every command/response...

The call stack for this error is as following:
    #4 0x56384c in libspdm_debug_assert /home/test/libspdm/os_stub/debuglib/debuglib.c:43:9
    #5 0x58fdad in libspdm_create_signing_context /home/test/libspdm/library/spdm_crypt_lib/libspdm_crypt_crypt.c:1620:5
    #6 0x592f8a in libspdm_req_asym_sign /home/test/libspdm/library/spdm_crypt_lib/libspdm_crypt_crypt.c:3048:9
    #7 0x59eaa0 in libspdm_requester_data_sign /home/test/libspdm/os_stub/spdm_device_secret_lib_sample/lib.c:739:18
    #8 0x561b74 in libspdm_test_responder_finish_case8 /home/test/libspdm/unit_test/fuzzing/test_responder/test_spdm_responder_finish_rsp/finish_rsp.c:387:5
    #9 0x56233c in libspdm_run_test_harness /home/test/libspdm/unit_test/fuzzing/test_responder/test_spdm_responder_finish_rsp/finish_rsp.c:433:5

OK. The issue is at
#8 0x561b74 in libspdm_test_responder_finish_case8 /home/test/libspdm/unit_test/fuzzing/test_responder/test_spdm_responder_finish_rsp/finish_rsp.c:387:5
        m_spdm_finish_request.header.spdm_version << SPDM_VERSION_NUMBER_SHIFT_BIT, SPDM_FINISH,

You cannot input fuzzed version. It is illegal configuration.

Merge, since it is test code only.


Unsupervised graph sage demo

This is a demo of learning unsupervised GraphSAGE based embeddings of the CORA network. This notebook is a simple step by step demonstration of how Unsupervised GraphSAGE is implemented.

A few comments:

As I mentioned, I think the demo notebook might be better placed under the embeddings directory – but this can be done later when you reorganize the demos directory.
Related to @youph 's comment about link prediction you use the terms 'true links' and 'false links' as well as positive and negative links. I don't think we should use the terms true and false.

For example, instead of saying:

by feeding it a training sample of true and false links from the underlying graph that are extracted without any true class label information.

I think we should say: "by feeding it a training sample of node pairs from random walks on the underlying graph and negative node pairs from a global node distribution"

I think we should note that this method is a reimplementation of the algorithm in the GraphSAGE paper adding a citation (in the top section).

Under "Unsupervised GraphSAGE with on demand sampling" I don't think we need to specify the parameters of the class – this is given in the API documentation.

Currently we don't specify a walker object so references to this in the text should be removed.

6 . I don't think we need to get to this level of detail – most users won't care:

regardless of whether the negative sample is the target itself or one of the contexts.

This is no longer needed:

2. The random walker used in sampling.

Use standard Python code style (https://www.python.org/dev/peps/pep-0008/). For example, this:

unsupervisedSamples = UnsupervisedSampler(G, nodes = G.nodes(),length = length, number_of_walks = number_of_walks )

is better written:
unsupervised_samples = UnsupervisedSampler(G, nodes=G.nodes(), length=length, number_of_walks=number_of_walks )

Note the spaces, the use of underscores not camelCase.

Under "Create a link mapper" can we simplify this explanation and use the term "node pairs" instead of "links".

Under "Data Splitting", this looks like debugging code:

print("Array shapes:\n X_train = {}\n y_train = {}\n X_test = {}\n y_test = {}".format(X_train.shape, y_train.shape, X_test.shape, y_test.shape))

"### Thoughts about why we should care?" might be better phrased as "Uses for unsupervised embeddings"?

@adocherty and @youph,
i have updated the unsupervised graphsage notebook.
Following are the list of changes. I tried to keep the numbering consistent with @adocherty recommendations for changes.

The notebook is now under the embedding folder. The name of the notebook has been updated to better reflect its purpose. The readme in the embedding folder has been updated with the relevant details.
True and false in connection to positive and negative links has been changed. Now, it should be consistently true and false.
About the text in the introduction, I gave it another shot to get rid of the ambiguities regarding links and pair terminology. I will have another go on it with a fresher mind. @youph I will check the language in the blog you sent me the link of and see if I can refine the text.
Added reference to the original paper.
Removed the list of parameters under Unsupervised GraphSAGE with on demand sampling. Described what goes into the class as free text.
Removed reference to walker object.
Removed "regardless of whether the negative sample is the target itself or one of the contexts."
Removed the walker object creation part.
Fixed the python coding style and naming of the variable.
Under "Create a link mapper"  changed links to pairs.
Removed the train test data sizes.
Changed the heading of the conclusion.

Also, updated the readme in the demo folder. Added unsupervised graphsage reference under embeddings.
Also, added a couple of words in the readme in the main stellargraph directory, mentioning unsupervised graphsage in the graphsage reference.

@habiba-h I made further clarifications of the workflow, please have a look.

@youph I looked over the notebook and all looks good. So will merge it now.


Added an optional performCustomAnimations method in CKClusterManagerD…

This is an option for users of the library to implement animations in a custom way. Giving out the [CKClusterAnimation] array gives the possibility to implement the animations in any desirable way. I added another method in the delegate instead of changing the current one for the existing users of the library not to have to change much code.

Nice work here @aramsargsyan and sorry for the late reply.
Instead of adding the type as a CKClusterAnimation property, the enum value could be pass as an argument of the MKMap method performAnimations:completion:. Then the additional delegate method signature would look like:
- (void)clusterManager:(CKClusterManager *)clusterManager performAnimations:(void (^)(void))animations type:(CKClusterAnimationType)type completion:(void (^ __nullable)(BOOL finished))completion;

In order to be merged, you will also need to update MapKit, GoogleMaps and YandexMapKit extensions.


Add visual clue that Plugins menu is scrollable

(Ignition Citadel 3.3.0) It looks like the Plugins menu is missing the Transform Control plugin, but what is actually happening is the vertical size of the Plugins menu is limited and the plugin menu is scrollable.
It would be helpful if there was a visual cue that the menu was scrollable. Maybe an always shown scrollbar, or a gradient at the bottom if there are more choices?

Here's what each might look like:

Yeah I've seen people caught by this before, thinking some plugin wasn't available when all they needed to do was scroll.
I think we can just make the scroll bar always visible. The fix would go on ign-gui, I think all that's needed is policy: ScrollBar.AlwaysOn here.

Done on https://github.com/ignitionrobotics/ign-gui/pull/134


[10.x] Ability to add custom filename for inline embed email

Hi team,
This PR adds the $name param for the email inline embedding. This shouldn't introduce any breaking changes.

Would really helpful to add inline file with the desired filename instead of random when using string path.
Alternatively solution
We can use the Attachment::fromPath('foo')->as('bar.jpg'), however it'd get long and kinda ugly in the blade template 🤔
Cheers!

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

thanks @taylorotwell , was thinking this one could be a good improvement for inline embedding with a desired filename


Add prometheus-cpp (and civetweb)

Thanks for the PR!
Just as a notification, here're our build results:
Processing arm-uwp
    civetweb                                                    Fail vs
    prometheus-cpp                                              Skip vs
Processing arm64-windows
    civetweb                                                    Fail vs
    prometheus-cpp                                              Skip vs
Processing x64-linux
    civetweb                                                    Pass vs
    prometheus-cpp                                              Pass vs
Processing x64-osx
    civetweb                                                    Fail vs
    prometheus-cpp                                              Skip vs
Processing x64-uwp
    civetweb                                                    Fail vs
    prometheus-cpp                                              Skip vs
Processing x64-windows
    civetweb                                                    Pass vs
    prometheus-cpp                                              Pass vs
Processing x64-windows-static
    civetweb                                                    Pass vs
    prometheus-cpp                                              Pass vs
Processing x86-windows
    civetweb                                                    Pass vs
    prometheus-cpp                                              Pass vs

Hey guys,
Looks like the FindCivetWeb.cmake is not copied to the proper location, once I try to link with pull it fails to find the CivetWeb. First when I use find_package for prometheus-cpp it fails with

CMake Error at /home/user/Development/vcpkg/scripts/buildsystems/vcpkg.cmake:159 (_add_library):
Target "kuddel" links to target "CivetWeb::CivetWeb" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
lib/server/CMakeLists.txt:232 (ADD_LIBRARY)

Looks like it does not invoke the FindCivetWeb.cmake stuff, then I add the find_package for CivetWeb and then it fails to find the FindCivetWeb.cmake. When the import of the FindCivetWeb.cmake is forced everything works as expected. Looks like it should reside in shared folder or something.

This is what I did. As a workaround it works fine