text:
Treatment of results from separate check repo locations

Question
When running tests using the default repo and a user-defined repo that pipes out to generate a JSON file, the last repo's results will overwrite the previous repo checks' runs since they internally run as separate pester calls.
For example:
Invoke-DbcCheck -SqlInstance $Servers -Check $checks -PassThru -OutputFormat NUnitXml | Update-DbcPowerBiDataSource -Path $destPath -FileName $FileName

With checks in two repos will overwrite the packaged dbachecks file results with the user specified repo results file. Is this is the intended behavior? It could be coded around manually, but I'd most likely end up rolling my own DbdPowerBiDataSource to do it. My presumption was that this should be able to aggregate multiple repo check results into a single file.
My lazy workaround for now is keeping my custom tests in the checks folder of the module itself.
A quick solution might be to use an -Append parameter for the Update-Dbc function to allow for appending results. I'm happy to work on it

Hmm, I definitely have this working at a client with a custom check folder and am not seeing this behaviour.  First gut feeling late at night is the filename parameter.
Also, the PowerBi takes results from multiple files and combines them into one PowerBI Report.
What is the requirement for one XML file ?

Yeah, so with the filename specified it is overwriting that same file once it moves on to a second check folder.
I could run Invoke-DbcCheck one time for each of the test sets, each with a separate file name param, and load those into PowerBI, but that seems unnecessary when the majority of that can be done via one command like above.

OK I can reproduce

I think you are right, the best way is to add append to Update-DbcPowerBi command
`                if ($PSCmdlet.ShouldProcess($FilePath, 'Passing results')) {
if($Append){
$InputObject.TestResult | ConvertTo-Json -Depth 3 | Out-File -FilePath $FilePath -Append
Write-PSFMessage -Level Output -Message "Appended results to $FilePath"
}
else{
$InputObject.TestResult | ConvertTo-Json -Depth 3 | Out-File -FilePath $FilePath
Write-PSFMessage -Level Output -Message "Wrote results to $FilePath"
}
            }`

I am happy for you to add this John if you want to ??

Coded into next release

Thank you! Sorry I missed your reply from a few days back. 😨

authors: LowlyDBA SQLDBAWithABeard

repo: sqlcollaborative/dbachecks


text:
Import-DbaCsv add parameter for simple progress messages

Summary of new feature
It would be great to add a -SimpleProgress parameter that writes a message after each imported batch.  The visual progress bar looks great (and it can be turned off with the -NoProgress parameter), but if the import fails, there is no record of where the failure occurred.
Proposed technical details (if applicable)
There's an old script by @potatoqualitee that has the functionality I'm describing.
https://gallery.technet.microsoft.com/scriptcenter/Import-Large-CSVs-into-SQL-216223d9

Latest version of dbatools as of writing
1.0.59

This output should be available using the parameter -NotifyAfter. Check the docs here for reference: https://docs.dbatools.io/#Import-DbaCsv

source: gharchive/issue

repo: sqlcollaborative/dbatools

license: MIT

license_type: permissive

license_source: github-api


text:
Availability Group commands

While I'm out this weekend, can one/some perform some code reviews.
Still missing:

[ ] Set commands
[ ] Sync command
[ ] Test commands
[ ] Tests (sql2017 instance will work well)
[ ] Proper examples for New-DbaAvailabilityGroup
[ ] Autoseeding examples (and maybe support? Didn't try it but assume it works)
[ ] The permission stuff Shawn mentioned as listed in the description of New-DbaAvailabilityGroup

I don't use AGs so I'm guessing for some things. Please confirm:

[ ] The ConfirmImpact for each command is appropriate

New-DbaAvailabilityGroup can make a super simple AG or it can make a group complete with replicas, Ips and databases. It should auto seed.
If anyone can figure out why the DbCert commands are failing in scenario 1, that would be appreciated. Feel free to commit to the AG branch.

will reopen later, but i'm up for code reviews at any time. i just dont like the PR pile up

source: gharchive/pull-request


text:
Export-DbaInstance - Append doesn't do what it appears

Type of Change

[X] Bug fix (non-breaking change, fixes #6918  )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
This is probably going to be a temporary measure until #5380 is completed but my hope is that we'll help people get what they're expecting in the meantime. Addresses #6918
In #5380 a -Append switch was proposed and I think the intention there was to have a single file exported which contains all scripts for the instance. But this being defaulted to $false (well, $null) prevents the complete scripts from being produced in the current implementation where we have one script per "group" and there are multiple object types per "group" (such as Agent and DBMail).
If I'm exporting AgentServer, I would expect everything for AgentServer to be exported. For DBMail, if we don't export everything, DBMail isn't fully configured by the script that's produced - configuration, accounts, profiles & server settings aren't there.
Approach
Default -Append to $true. I'm defaulting to this because it is what people expect from the function -
Commands to test
Export-DbaInstance -sqlinstance MYINSTANCE
With -Append set to $true (which will now be the default), Agent Operators, Schedules, Proxies, etc. should be included in the X-sqlagent.sql script.
With -Append set to $false, Agent Operators, Schedules, Proxies, etc. will be included in the X-sqlagent.sql script.

mmm, im not so sure about this one but need some time to articulate why 😅  ill bbiab

okay, so the reason is because it's semantically incorrect. We'd have to change the name of the variable like "NoAppend". A switch that defaults to true would require a :$false to work.
Is the issue just with Agent? If so, I'd have no problem throwing all of that into one file.

Thank you @alevyinroc - going to resolve any outstanding issues in https://github.com/sqlcollaborative/dbatools/pull/6957

authors: alevyinroc potatoqualitee


text:
javax.net.ssl.SSLHandshakeException: Handshake failed (Retrofit 2.1.0)

What kind of issue is this?

[x] Question. This issue tracker is not the place for questions. If you want to ask how to do
something, or to understand why something isn't working the way you expect it to, use Stack
Overflow. https://stackoverflow.com/questions/tagged/okhttp

[x] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
get fixed. Here’s an example: https://gist.github.com/swankjesse/981fcae102f513eb13ed

[ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

Throwing the below error in onFailure() call back method
javax.net.ssl.SSLHandshakeException: Handshake failed
i'm using below libraries
compile 'com.squareup.retrofit2:retrofit:2.1.0'
compile 'com.squareup.retrofit2:converter-gson:2.1.0'
compile 'com.google.code.gson:gson:2.6.2'

Thanks for your question. This issue tracker is only for bug reports with test cases and feature requests. Please ask usage questions on Stack Overflow.
https://stackoverflow.com/questions/tagged/okhttp

authors: swankjesse tulasi-ram

repo: square/okhttp


text:
Handling comma in cookie values

Hello,
I'm developing a mobile application using React Native which is using OkHttp as HTTP client in the Android version. My issue is how OkHttp handles commas in cookie values. When the client receives "set-cookie" header which contains a comma in the cookie value, OkHttp parses the value until the comma and ignores the rest of the value. I know that RFC6265 doesn't allow comma, but it seems to be widely supported in browsers such as Google Chrome and Safari.
I have located this line in the cookie parser in JavaNetCookieJar.java:
pairEnd = delimiterOffset(header, pos, limit, ";,");
This code seems to expect that cookie name-value pairs can be separated by either a semicolon or comma, but I'm not certain whether a comma is valid cookie separator (I have only seen semicolons used).
Hence my suggestion/question: Can we remove comma as cookie separator in the line above or is there any potential issue that I might have missed?
cc @swankjesse

We’re trying to satisfy a different discouraged case where the server folds multiple set-cookie headers into a single line, like this:
Set-Cookie: c1=first, c2=second

This is discouraged per the spec:

Origin servers SHOULD NOT fold multiple Set-Cookie header fields into a single header field.  The usual mechanism for folding HTTP headers fields (i.e., as defined in [RFC2616]) might change the semantics of the Set-Cookie header field because the %x2C (",") character is used by Set-Cookie in a way that conflicts with such folding.

My preference is to retain our current behavior, only because changing it risks breaking existing users.

Studying our code some more, you won’t get this behavior if you don’t use JavaNetCookieJar. The regular CookieJar has more modern behavior.

No action to take on this.

authors: jaruyot swankjesse


text:
How To fully simulate Chrome's TLS fingerprint？ How to break through ja3 or tls fingerprint

How to break through ja3 or tls fingerprint，
ja3指纹或tls指纹，怎么模拟和破解？

Better question for Stackoverflow - we can't provide this sort of 1:1 support.


text:
Install dependencies to a project-local repo

This allows integration tests to resolve the dependency like a real project would.

Great. Fails on CI and passes locally. And you can't debug Travis workers.

repo: square/sqldelight

license_source: bigquery


text:
[BUG] Keyboard input takes effect despite window minimized/inactive

Describe the bug
I've noticed sometimes when WaveTracker is running but inactive, some keyboard shortcuts will still control it even if its not active. For example pressing Ctrl+S in word processor may also open WT's save dialog, Pressing Enter while typing may start a song, pressing Space will enable Edit mode and typing letters will begin entering notes.
It seems to happen semi-randomly, and stops happening if you minimize or otherwise try to make it stop happening.
To Reproduce
Unfortunately I haven't identified the condition (apologies), but it's happened 3 times now.
Expected behavior
Under no circumstance should background input (besides MIDI devices, possibly) affect the program.
Desktop (please complete the following information):

OS: Win10

Okay, I found a way to reproduce this bug:

Open WaveTracker with a song.
Minimize by pressing the actual minimize button.
Switch to some other program. Press Enter. Nothing should happen.
Click WaveTracker once on the Taskbar, it should bring it up.
Without moving the mouse, click WaveTracker on the taskbar again. It should minimize it.
Switch to some other program. Press Enter. The song will play.

So somehow the app must think it's still active, despite having been minimized through the taskbar.

This appears to be an issue with XNA's "Game.IsActive" property not updating correctly.
This also means the bug is present when starting the application, where focusing a different window just before WaveTracker starts will yield the same input issue.
Additionally, I experimented with subscribing to the "Game.Activated" and "Game.Deactivated" events to update a custom bool, but ultimately these event's are used under the hood for the "Game.IsActive" property and therefore had the same issue.
I will look into some other win32 or Form alternatives for checking window state but I'm worried these might affect cross-platform-ness down the road

repo: squiggythings/WaveTracker


text:
[Feature Request] Vector fonts / Alternate UI

Is your feature request related to a problem? Please describe.
The UI is neigh impossible to use on high DPI displays without substantial scaling
Describe the solution you'd like
Alternate, high resolution, scalable fonts would resolve part of the problem. Alternatively, a standard Win32 UI could scale to any size and keep all elements, buttons, toggles, lists readable and acceasible, style be damned (a rework of the custom UI would always lead to conflict with the low resolution appearance, more clashing than high res fonts over low res fields)
Describe alternatives you've considered
Not applicable to a visual problem
Additional context
Using the program as-is is quite difficult due to how hard to see the elements are. Same with reading the text.

Is the 500% scale setting (Edit -> Preferences) not enough? Would 600-800% help you see it better? Or are you just saying you don't like pixel fonts/retro-inspired UIs? 🤔 Creating a whole new vector UI is a massive ask. Not to mention potential cross-platform considerations.
I personally am perfectly fine with the design, it's valid and follows the footsteps of popular trackers like Klystrack, Lovely Composer, MilkyTracker, all which have scale options so that the text gets larger on 4K displays etc.

It technically works, but the font itself is so low resolution that the only device where i can comfortably read it is on my 34 inch monitor at 200/300% scale. Trying to comfortably use the UI on something like my Framework 13 (13.5 inches, 2256x1504) is kind of painful and takes away real state. The problem itself is the "resolution" of the font, it being 5x5, and non-monospaced makes it incredibly hard to read (i have a fairly severe visual impairment).
Do not take me wrong, i love me some pixel art, and one of my hobbies is fontmaking, a search for my name on Pouet or dA should show you all the stuff i've worked on for 8 and 16 bit machines, including monospaced 3x5 and 4x5 bitmap fonts. However i'd never dare using them on an UI knowing i can't blow their size to 5mm vertical or equivalent.
However, needing to stop and trying to decipher the glyphs slowly to scan the UI is a terrible idea altoghether.
I am surprised you say using a vector UI would be problematic to cross compatibility, when Dear IMGUI (the same thing Furnace uses), or QT or GTK forms for the application (if not Win32 for Wine) could get the job done. It would kill the vibe for sure, but that's an option.
Aseprite, a project whose aesthetics have clearly influenced WaveTracker (and unfortunately, a project i can't use as-is because of the god-awful low resolution fonts and ui elements) at least offers a theme definition file where one could mangle up a color scheme and has the font definition as part of an XML file, so while making the UI actually usable takes a significant amount of effort, someone with the know how of how to get the default theme definitions and modify the XML properties for said theme (something that should NEVER be expected of end-users to do) can change the font to something different, vector based, even. They have the worst possible way to go around it, but it's at least an option.
While the project is early it would be a good idea to tackle the UX accesibility problems, before things have been fully cemented.
However, your last comment seems to point that this is program first and foremost, accessibility be damned. So, take my feedback as you will.

Accessibility issues are something I want to take pretty seriously and I try to do what I reasonably can to accommodate. A full remake of the entire interface to support vector fonts would for sure be an enormous undertaking. However, right now, I may be able to provide an option that switches all text to a higher resolution, sans serif font that will be more legible at larger scales than the default stylized one.

authors: ZanaGB bryc squiggythings


text:
NewCommitPreorderIter Fails with object not found When iterating over incomplete history.

In remote.go in getHaves, getHavesRef fails with object not found error when
iterating over incomplete history.
This causes Fetch to fail under certain circumstances, such as (at least) when fetching remotes with unrelated histories.
This likely happens because commits are processed in Preorder and once it reaches the last commit fetched with a given Depth, it fails for find its parent.
Suggestion Short Term
Ignore object not found error during a fetch operation
Suggestion Long Term
Add a terminal empty commit after fetch with a certain depth, to signify that no further commits can be reached. This will guarantee that object not found error if it happens, happens because of corrupt data as opposed to truncated history.

Seems like there is a related Issue #1143

repo: src-d/go-git


text:
I would like to request git-verify-commit support please

great library btw! 😁

Or at the very least the ability to extract the signature, sign from a commit?

Is this done now? @darkowlzz If so many much thanks! 👍

Is this actually done?  It seems like support for signatures to be included in commits has been added, but not the ability to verify them?

True, is not implemented, thanks!

authors: blacktop mcuadros


text:
Get the first commit ever

Hi,
What is the best way (performance like) to get first commit ?
I tried to find a "commit slice" (not iter) but didn't find anything.
Thanks

@Mirio First you need to think about what is the first commit. There might be more than one "first commit" in a repository, since you can merge two initially different repositories into a single one. For example, the official git repositories has seven "first_commits".
Now, assuming that you just want to get all of them, you just have to iterate over all commits and get those that have no parents. You can do this by getting the Commit you want to start walking (for example, the one being pointed by HEAD) and then use object.NewCommitPreorderIter or one of the other commit iteration functions to get a CommitIter.
You'll have to walk them all, and whenever you see a commit with 0 parents, that's the first one, which might be not unique.

authors: Mirio smola


text:
runtime error: slice bounds out of range (nextPackData)

runtime error: slice bounds out of range
goroutine 557650 [running]:
runtime/debug.Stack(0xc42000e018, 0xc433d4efa8, 0x1)
 /usr/local/go/src/runtime/debug/stack.go:24 +0x79
runtime/debug.PrintStack()
 /usr/local/go/src/runtime/debug/stack.go:16 +0x22
github.com/goodrain/rainbond/builder/exector.(*exectorManager).buildFromSourceCode.func1.1(0xc435d82160)
 /go/src/github.com/goodrain/rainbond/builder/exector/exector.go:193 +0x83
panic(0xec1bc0, 0x1793550)
 /usr/local/go/src/runtime/panic.go:489 +0x2cf
bytes.(*Buffer).Write(0xc432aeaf50, 0xc433416b41, 0x29, 0x80, 0x29, 0x0, 0x0)
 /usr/local/go/src/bytes/buffer.go:138 +0xc9
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/protocol/packp/sideband.(*Demuxer).nextPackData(0xc4208766e0, 0x0, 0x0, 0x0, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/protocol/packp/sideband/demux.go:127 +0x10f
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/protocol/packp/sideband.(*Demuxer).doRead(0xc4208766e0, 0xc430ede000, 0x8000, 0x8000, 0x0, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/protocol/packp/sideband/demux.go:83 +0x2f
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/protocol/packp/sideband.(*Demuxer).Read(0xc4208766e0, 0xc430ede000, 0x8000, 0x8000, 0x8000, 0x8000, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/protocol/packp/sideband/demux.go:71 +0x77
io.copyBuffer(0x7f8249624ab8, 0xc4202efdc0, 0x17a8980, 0xc4208766e0, 0xc430ede000, 0x8000, 0x8000, 0xf592a0, 0xc433d4f300, 0x7f8249624ab8)
 /usr/local/go/src/io/io.go:390 +0x100
io.Copy(0x7f8249624ab8, 0xc4202efdc0, 0x17a8980, 0xc4208766e0, 0xc4202efdc0, 0xc433d4f370, 0x40f4fd)
 /usr/local/go/src/io/io.go:360 +0x68
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/format/packfile.writePackfileToObjectStorage(0x7f8249624a10, 0xc42f24f7a0, 0x17a8980, 0xc4208766e0, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/format/packfile/common.go:51 +0x13b
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/format/packfile.UpdateObjectStorage(0x7f8249913478, 0xc42f24f7a0, 0x17a8980, 0xc4208766e0, 0xc42f24f7a0, 0x1)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/plumbing/format/packfile/common.go:30 +0x344
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git%2ev4.(*Remote).fetchPack(0xc433613620, 0x17b6480, 0xc42f24ed20, 0xc433d4f6e0, 0x17b52c0, 0xc4205d8050, 0xc42c891140, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/remote.go:366 +0x2f9
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git%2ev4.(*Remote).fetch(0xc433613620, 0x17b6480, 0xc42f24ed20, 0xc433d4f6e0, 0x0, 0x0, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/remote.go:301 +0x70e
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git%2ev4.(*Repository).fetchAndUpdateReferences(0xc4344ba660, 0x17b6480, 0xc42f24ed20, 0xc433d4f6e0, 0xc42f0695b0, 0xf, 0xc4336123c0, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/repository.go:548 +0xbf
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git%2ev4.(*Repository).clone(0xc4344ba660, 0x17b6480, 0xc42f24ed20, 0xc432aeafc0, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/repository.go:447 +0x25b
github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git%2ev4.PlainCloneContext(0x17b6480, 0xc42f24ed20, 0xc42cced200, 0x5d, 0x0, 0xc432aeafc0, 0xc4344ba390, 0x0, 0x0)
 /go/src/github.com/goodrain/rainbond/vendor/gopkg.in/src-d/go-git.v4/repository.go:322 +0xa5
github.com/goodrain/rainbond/builder/sources.GitClone(0xc433d64608, 0x0, 0xc43388e3f1, 0x2d, 0xc433d6460b, 0x4, 0x0, 0x0, 0x0, 0x0, ...)
 /go/src/github.com/goodrain/rainbond/builder/sources/git.go:154 +0x1c9d
github.com/goodrain/rainbond/builder/sources.GitCloneOrPull(0xc433d64608, 0x0, 0xc43388e3f1, 0x2d, 0xc433d6460b, 0x4, 0x0, 0x0, 0x0, 0x0, ...)
 /go/src/github.com/goodrain/rainbond/builder/sources/git.go:377 +0x3c7
github.com/goodrain/rainbond/builder/exector.(*SourceCodeBuildItem).Run(0xc435d82160, 0x1a3185c5000, 0xc435d82160, 0x17b9f00)
 /go/src/github.com/goodrain/rainbond/builder/exector/build_from_sourcecode_run.go:134 +0x1bd
github.com/goodrain/rainbond/builder/exector.(*exectorManager).buildFromSourceCode.func1(0xc435d82160, 0xc433d64a20)
 /go/src/github.com/goodrain/rainbond/builder/exector/exector.go:198 +0x110
created by github.com/goodrain/rainbond/builder/exector.(*exectorManager).buildFromSourceCode
 /go/src/github.com/goodrain/rainbond/builder/exector/exector.go:217 +0x1b9

@barnettZQG Any further information? Could you share an URL to a failing repository? What is the protocol being used for that URL?

@barnettZQG Which protocol? https://? git://? ssh://? Do you have any example URL?

authors: barnettZQG smola


text:
plumbing: fix signature with > before < parsing

This is a fix for issue: https://github.com/src-d/go-git/issues/202
Since the fullname is free text, given a foo> the result was a panic, now this is handled properly returning  foo> as the fullname. Another extra security guards was added to protect the function against malformed signatures.

If the email address is crap, this crap will be extended to the committer name:
`Foo Bar <foo>@bar.com>`: {
	Name:  "Foo Bar",
	Email: "foo>@bar.com",
	When:  time.Time{},
},
// ... obtained string = "Foo Bar <foo"
// ... expected string = "Foo Bar"
`Foo Bar <foo<@bar.com>`: {
	Name:  "Foo Bar",
	Email: "foo<@bar.com",
	When:  time.Time{},
},
// ... obtained string = "Foo Bar <foo"
// ... expected string = "Foo Bar"

We've checked the behavior of git and it's as follows:

When generating commits, < and > symbols are removed (no matter their position). Both for name and email.
When reading, different operations have slightly different behaviours For example, git log prints almost the original output (no normalization), but git log --pretty='%an|%ae', which actually fully parses the signature has the following behaviour:

foo <my<@email.com> is parsed as name foo and email my<@email.com.
foo <my>@email.com> is parsed as name foo and email my.

Here's the original source in git: https://github.com/git/git/blob/3ef7618e616e023cf04180e30d77c9fa5310f964/ident.c#L250
we might want to replicate the same or similar logic for name splitting.

authors: ajnavarro mcuadros smola


text:
add methods to enable debug of SQL statements

Closes #141

added Debug and DebugWith to Store
added Debug and DebugWith to typed stores as well

Done @dpordomingo

repo: src-d/go-kallax

license: mit


text:
Add max_delay option

Hi,
Thanks for making this crate. I really like it! I saw in the older version you had a max delay option for the strategies, but on master that has been removed during the tokio changes.
I tried adding that back in today. I'm not sure if this is the approach you had in mind, or even wanted this sort of behavior... Anyhow, here's what I came up with. I thought it would be more straight-forward, but the functions Duration provides are not exactly the best for this use case: e.g. checked_mul on a Duration, only takes a u32, not u64,  you can't multiply a Duration by another Duration, etc. I was hoping I could have stored base/curr as a Duration in the iterator, but that just didn't work out.
I also added a ExponentialBackoff::from_secs function (since the from_millis one didn't give me the right behavior I wanted (too fast or too slow). Also added some Debug impls.
Happy to address any comments.
Thanks!

Hi, and thanks for contributing!
A maximum delay I think is super useful, and we should add it back in, so I'm going to leave a few comments specifically about these changes.
As for the problem that is the current backoff implementation not giving you the desired behaviour, I had a chance to compare what this crate is doing to how others are handling backoff strategies, and would like to propose an alternative to introducing units.
Taking for example the exponential backoff, this crate calculates the duration as base ^ number of attempts, where base is configurable. Other popular modules in other languages to something subtly different, namely factor * 2 ^ number of attempts, where factor is configurable. Implementing this formular for both exponential and fibonacci backoff should allow you to tune the backoff to the speed that is right for your use-case.

Thanks for the great (and quick!) comments. I really like the idea of a factor! Simplifies the code a lot.
Thinking about this some more, I decided to remove the MaxDelay struct entirely and did the checks inline in the next function; they are pretty short now. I think I made them more complicated than needed before because I was caught up in the units conversion stuff.
Let me know how this looks.

Forgot to leave a comment, I've rebased this now. Should be good now.

Just published version 0.1.0 including your changes. Thanks again for your PR!

Awesome, thanks a lot!

authors: compressed srijs

repo: srijs/rust-tokio-retry


text:
Replace hyperlinks with "link#" to be able to print out that link in the output

context: Bunny Rabbit link2 is here
dictionary
link2 --> "rabbit.com"
predicted answer - Bunny Rabbit link2 is here
if "link" in answer:
hyperlink = dict['link2']
new_answer = Bunny Rabbit rabbit.com

Done. @sriyavasudevan please check a few examples to see if it's done the way it's supposed to

@MattSpeciale737 sorry, have you pushed the changes?

Function added in the following commit caf53433c555c33fbcebab36e7ed0a24b22f768f. Needs further testing on actual answers.

@sriyavasudevan  follow up with @matthewspeciale


text:
Why are the estimated series different from the input series?

Finally able to compile it on my mac. I can now do reprex::reprex(), which is a nice way to ensure an example is reproducible.
Question is probably a bit a dummy question.
library(BDFM)
library(tsbox)

fdeaths0 <- fdeaths
fdeaths0[length(fdeaths0)] <- NA
dta <- cbind(fdeaths0, mdeaths)

m <- dfm(dta, forecast = 2)
ts_plot(dta, predict(m))

Created on 2018-11-10 by the reprex package (v0.2.1)

When I estimate two factors, I get fdeaths as well:

library(BDFM)
library(tsbox)

fdeaths0 <- fdeaths
fdeaths0[length(fdeaths0)] <- NA
dta <- cbind(fdeaths0, mdeaths)

m <- dfm(dta, factors = 2, forecast = 2)
ts_plot(dta, predict(m))

But why do I get mdeaths exact and fdeaths not?

When you estimate the model with one factor (the first example) the model selects a series that contains the most information. Though estimation is Bayesian it's easiest to think about in maximum likelihood terms --- the factor will be that which maximizes the likelihood of the observations, i.e. has the most predictive power. In this example the factor fits mdeaths much more closely than fdeaths.  The easiest way to see this is by looking at the estimated errors in the observation equation:
library(BDFM)
library(tsbox)

fdeaths0 <- fdeaths
fdeaths0[length(fdeaths0)] <- NA
dta <- cbind(fdeaths0, mdeaths)

m <- dfm(dta, forecast = 0)
ts_plot(dta, predict(m))
diag(m$R)

which give the output  1012.4917  172.0752. The variance of shocks to observations of the first series is estimated to be 1012.4917, the variance of shocks to observations of the second is estimated to be 172.0752... obviously much less. You can see that predictions are not exactly the observed series for both series:
predicted <- predict(m)
difference <- dta-predicted
ts_plot(difference)

It's just that difference between predictions and observations are much smaller for mdeaths.
In the second example, with two factors and two observations the model can fit observations much more closely, as with principal components. If you were to do this using principal components, you would get exactly the observed series. This example is almost the same... the only (very small) differences between predictions and observations is due to inter-temporal smoothing.
Just for fun, if you wanted to force the predicted values to be smoother you could specify that using the prior "degrees of freedom" nu_q in the transition equation:
m <- dfm(dta, factors = 1, forecast = 0, nu_q = 15)
ts_plot(dta, predict(m))

However, using strong priors like this doesn't always work out if it makes the transition equation non-stationary, so be careful!

Ok. There is no reason to expect predict to be identical than the original series. Use adjusted() if you want to have the original values if available.

authors: christophsax srlanalytics

repo: srlanalytics/bdfm


text:
🛑 Plex is down

In 988d763, Plex (https://plex.srueg.ch/identity) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Plex is back up in 6ec234e after 1 day, 8 hours, 19 minutes.

repo: srueg/upptime


text:
Modernize test tools and apply prettier

This PR is in preparation for improving the tests in BIPF and ensuring that we have 100% code coverage. I don't intend to touch the implementation other than code style and things like that.
This one does two things:

Modernizes test tools

Updates tape
Adds tap-spec
Adds nyc for code coverage

Applies prettier for automatic code style

Same style as used in JITDB, ssb-db2 and other recent modules
Nothing else significant was done to the JS files

Just found that minor thing, that would be nice to leave as is. Otherwise looks ready to merge. I checked the coverage and it looks good. There is 2 methods not tested, we should maybe check if they are used anywhere and if not remove them. I wonder what seekkey2 is, maybe some attempt at something?

Alright, updated the 0xE thing.

I checked the coverage and it looks good. There is 2 methods not tested, we should maybe check if they are used anywhere and if not remove them. I wonder what seekkey2 is, maybe some attempt at something?

That'll be the theme of some future PR I'll send.

repo: ssbc/bipf


text:
Triggering redundant finetuning does not reset "In Progress" Display

We have a short cut to skip finetuning if nothing changed, but the progress update happens outside.

Done.

repo: ssciwr/similarity-webservice


text:
[마이페이지] 펫시터로 등록된 회원은 펫시터 프로필을 등록할 수 있습니다.

🐶 Success criteria

프로필 등록 및 수정을 할 수 있습니다

🐾 To-do

[ ] 1. 사진을 등록합니다
[ ] 2. 주소 및 자기 소개를 등록합니다
[ ] 3. 가능한 서비스를 선택합니다
[ ] 4. 가능한 반려 동물의 사이즈를 선택합니다

🎸 기타

[ ] 할일 1
[ ] 할일 2


text:
Rules not visible in TIC TOC TOE

Description
Rules given are not visible , the current color is black which is making it invisible , i want to fix that , please assign me this under gssoc'23
Screenshots

Additional information
No response

Hi @krutikajichkar , i have assigned this issue to you. Kindly complete within a week. Good luck!

repo: ssitvit/Games-and-Go


text:
スコア

初期値
===================================================
負荷試験が完了しました！！！
あなたのスコア: 1180
コミットID: e1d9598dfc5a451a5d6d08b9a785011f8d62d345
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240726_133420.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240726_133420.json
===================================================

縮小処理を修正
Commit: f99e94d758d817af6610e4d6f5110a059d5aa00c
===================================================
負荷試験が完了しました！！！
あなたのスコア: 3526
コミットID: f99e94d758d817af6610e4d6f5110a059d5aa00c
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_014555.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_014555.json
===================================================

backendのworkerを増やす 1 -> 4
Commit: b26aca711cccc8ed939f0a2fce1b10f5c1a39fff
===================================================
負荷試験が完了しました！！！
あなたのスコア: 5174
コミットID: b26aca711cccc8ed939f0a2fce1b10f5c1a39fff
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_020130.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_020130.json
===================================================

nginxで画像をキャッシュ
Commit: b540bcdc89b710bda263c6d91e0d75b855d9db56
===================================================
負荷試験が完了しました！！！
あなたのスコア: 9316
コミットID: e278cecb8128c413c02a707c339b544f109ab545
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_025845.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_025845.json
===================================================

画像を500x500に縮小
===================================================
負荷試験が完了しました！！！
あなたのスコア: 9423
コミットID: 834b6b65d83f9a4efe81295fbbd91442f176860d
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_043029.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_043029.json
===================================================

セッショントークン生成の効率化
===================================================
負荷試験が完了しました！！！
あなたのスコア: 8730
コミットID: 834b6b65d83f9a4efe81295fbbd91442f176860d
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_050050.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_050050.json
===================================================

index修正
===================================================
負荷試験が完了しました！！！
あなたのスコア: 9100
コミットID: c37ae28e4513456f0bda31be12db3b125eebc401
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_070556.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_070556.json
===================================================

ダイクストラ
===================================================

負荷試験が完了しました！！！
あなたのスコア: 42250
コミットID: c4d8bf0325f3b9092dc4375ea0f0dad44d1d0bd6
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_125939.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_125939.json

===================================================

index追加 locations(tow_truck_id), tow_trucks(driver_id)
===================================================
負荷試験が完了しました！！！
あなたのスコア: 42200
コミットID: 4e48d7d293d6daf69eeb6421b787f279db4e096e
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_140108.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_140108.json
===================================================

静的ファイルをキャッシュ
===================================================
負荷試験が完了しました！！！
あなたのスコア: 41020
コミットID: 61875874e2f328d4ba3782ded9f87ad5d48327d6
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240727_141015.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240727_141015.json
===================================================

edgesテーブルを非正規化しarea_idを追加
===================================================
負荷試験が完了しました！！！
あなたのスコア: 41750
コミットID: 6b0d9d8512417fc9e5d063525889628e879ed9c7
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240728_024112.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240728_024112.json
===================================================

===================================================
負荷試験が完了しました！！！
あなたのスコア: 40820
コミットID: 831e2d8a5ba9600b19dec31ac2fdd2ea8e823267
より詳細な情報は下記ファイルをご覧ください
ログファイル: ./benchmarker/logs/app-dolphin_20240728_043212.json
負荷試験詳細ファイル: ./benchmarker/scores/raw-data-app-dolphin_20240728_043212.json
===================================================

authors: snakeauk ssmyg


text:
How can I link a resource so that my authorizer function can access it?

How can I link a resource so that my authorizer function can access it?
The resource (DynamoDB table) is accessible in the api.hello function but not in the authorizer function. I am getting the error Error: "AllowedDomains" is not linked in your sst.config.ts.
export const apiGateway = new sst.aws.ApiGatewayV2('ApiGateway', {
  transform: {
    route: {
      handler: {
        link: [
          allowededDomainsTable,
        ],
      },
    },
  },
});

const myAuthorizer = apiGateway.addAuthorizer({
  name: 'myAuthorizer',
  lambda: {
    function: 'packages/functions/src/authorizer.handler',
    response: 'simple',
    payload: '2.0',
    identitySources: [],
  },
});

const defaultRouteOptions = {
  auth: {
    lambda: myAuthorizer.id,
  },
};

apiGateway.route(
  "GET /hello",
  "packages/functions/src/api.hello",
  defaultRouteOptions
);

@paolostyle Thank you very much, it works! You're totally right, linking only the resources that are actually needed per endpoint is much better. Thanks again!
Do you have any recommandations on a good Youtube walkthrough video on SST that would cover most of this stuff ?

Maybe not exactly what you are looking for but there's the terminal video: https://www.youtube.com/watch?v=POlZS8PcyZw

Maybe not exactly what you are looking for but there's the terminal video: https://www.youtube.com/watch?v=POlZS8PcyZw

Just finished watching it and this is amazing stuff! Thanks mate!

Maybe not exactly what you are looking for but there's the terminal video: https://www.youtube.com/watch?v=POlZS8PcyZw

@jayair Just finished watching it and this is amazing stuff! Thanks mate!

authors: gablabelle jayair

repo: sst/ion


text:
OpenNext Ignores force-cache Option on fetch Requests (Data Cache Behavior Differs from Vercel)

I recently migrated my project to OpenNext, deploying it with sst@v3. It's a news website built using a custom CMS developed with Next.js. Previously, when hosted on Vercel, nearly all fetch requests to the configuration endpoint were served from cache (with a 99.99% cache hit rate, according to Vercel and our server logs).
However, after the migration, the server is being hit hundreds of times per hour, suggesting that the cache is being bypassed—likely whenever new pages are rendered. This behavior differs significantly from our previous experience on Vercel, where caching worked as expected.
Problem

Expected Behavior: Fetch requests should be cached, with minimal server hits (as seen on Vercel).
Current Behavior: The server is hit far more frequently, implying the cache is not functioning as intended.

Questions

What could be causing this cache issue after migrating to OpenNext?
How can I debug or resolve this problem?

I'd greatly appreciate any help, insights, or advice on this issue.
Thank you in advance!
Useful Links

Next.js Fetch API Documentation
Next.js Fetch Options (cache)

What version of Next and OpenNext are you using ?
If you're on OpenNext 3.0.8, could you test with 3.0.7. I have a feeling that there might be a bug here because of the tag cache and the way it is done in OpenNext.

Right, I'm using 3.0.8. I'll try to downgrade. Thank you very much for the reply.

@mlukasik-dev You don't have a tag associated with this fetch call right ?
If that's the case the better fix is to just add a tag, this should fix the issue without having to downgrade

@mlukasik-dev You don't have a tag associated with this fetch call right ? If that's the case the better fix is to just add a tag, this should fix the issue without having to downgrade

@conico974,  I actually have one or two tags on each fetch. I've checked the DynamoDB and they are written correctly.

I see, in this case i think downgrading will do nothing for your issue.
The problem is coming from here https://github.com/sst/open-next/blob/c91c83b5c84c1ea582c03eb23250239954343b64/packages/open-next/src/adapters/cache.ts#L165-L170 We should also add revalidatedAt to 1 otherwise every new page make the fetch data cache stale.
I'll make a PR later today for this

@conico974, Thanks for finding a solution so quickly. I didn't even manage to test a downgrade :)
Unbelievable!
Btw, while browsing the DynamoDB table, I found another bug with cache tags that makes listing paths by tags unstable and unpredictable.
I'll create another issue and link it here.

#495

@conico974, unfortunately the update didn't fix the problem.
In SST I have set openNextVersion to 3.1.1, new DDB lines do have revalidatedAt set to 1.
But the problem persists. I am getting hundreds of requests to the same configuration endpoint from my website.

@mlukasik-dev You'll need to provide a reproduction then

If you want to debug in your app you should deploy like that OPEN_NEXT_DEBUG=true sst deploy.
This will provide a ton of log and might help identify what's wrong

@conico974, I've tried to create a very simple Reproduction Example.
However, everything works as expected so far.
So I thought: maybe the problem is with the previous cache inside DynamoDB? Shouldn't they be removed or something?

@mlukasik-dev Here everything is SSG, are you using ISR in your app ?

@conico974, then I'm not sure I understand what an ISR means...
I thought it was the SSG with pages generated at run time instead of build time (basically my example).

For my example run time generation is the case because I don't provide SUPPORTED_LANGS array to generateStaticParams in app/[lang]/layout.tsx.
https://github.com/mlukasik-dev/open-next-data-cache/blob/7d51f247f74509ecf3a2a3fd4f81d63118fddcd4/apps/web/src/app/[lang]/layout.tsx#L24-L26

ISR is when you use revalidate either in fetch or with export const revalidate

I do use revalidate in one place, but not for the problematic (/config) endpoint.

Not on this specific fetch, but does the revalidate happens inside a page where this config fetch is done ?

Yes, that page has another fetch with options.revalidate set to 86400.

I have updated Reproduction Example so it has a fetch with revalidate now:
https://github.com/mlukasik-dev/open-next-data-cache/commit/dffa951039cd2d7e4b42e31ff9d23faba1fa3e98

I checked the ConfigLambda function logs and confirm the bug is in the example.

I deployed it too. Only got 2 entries in the ConfigLambda log after navigating around to all pages.

authors: conico974 mlukasik-dev sommeeeer

repo: sst/open-next


text:
modified render options to add cookies

cookies that were set with the  Astro.cookie.set() method were not passed on to the CloudflareResult. and some cookies were also duplicated before they were converted into specific AWS Responses

@bayssmekanique does this make sense to you? Or is this more for Frank to look at?

@lvindotexe, could you provide some context to the original issue this PR addresses. I see the code and I think it's harmless enough, but I'm not sure I understand the original issue. Is it possible to get a reproduction step or example of some sort?

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble

authors: bayssmekanique jayair lvindotexe thdxr

repo: sst/sst


text:
[Feature] Layout Component

Box
Container
Grid
Stack
Hidden

각 페이지에서 제작해서 사용하는 것으로 결정

repo: ssu-commerce/frontend


text:
[FEAT] Locate flashcards in notes when click opening files

When I review the flashcards, I can click on "Open file" button to access the notes where the flashcards are located. When I review the flashcards, I can click on "Open file" to access the notes where the flashcards are located. However, it would be nice if I clicked on "Open file" to go directly to the specific passage in the note where the flashcards are located. This helps to refine the description of the card and makes memorization more efficient.

There's two of these #212, & neither has any elaboration.

There's two of these #212, & neither has any elaboration.

Sorry, I failed to submit the description due to the network problems. I have add the feature description.

Neat, I'll look into this.

Turned out to be a quick fix, should be available in the next release.

Stephen Mwangi @.***>于2021年8月1日 周日21:06写道：

Turned out to be a quick fix, should be available in the next release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/st3v3nmw/obsidian-spaced-repetition/issues/213#issuecomment-890517370,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOZJGR7QGVO2JGGVJRTS66TT2VBGHANCNFSM5BLBRW4A
.

Great! Thank you very much!


text:
[Feat] Multi-line reversed cards

i.e.
Multi-line
question
(or answer when reversed)
??
Multi-line
answer
(or question when reversed)

Configurable...

+1 for this feature

+1

Fix should be available in the next release once I'm done with testing.

authors: roamhacker st3v3nmw thakichowdhury


text:
Ticket-rule: add "see $url" tip

Implements #80
This PR also changes how e2e tests assert expected errors, because the raw format did not include the tip.

thank you

authors: EmilMassey staabm

repo: staabm/phpstan-todo-by


text:
fix: Validate processing fields everywhere

To reproduce the original issue:

Change the value of .providers[0]['processing:software']['IPF-S2L1C'] to something not a string, such as 2.6.
Run npm test.

The test passes even though the value should be considered invalid. I believe the reason for this is that anyOf requires that one of the sub-schemas are valid, not that one of the sub-schema structures are present. So even if some processing property values are invalid, as long as there is at least one valid value the JSON passes validation.
Caveat: Some unit tests would be in order to make sure the schema does the right thing in many more cases. If you're interested I can add some of those as well.

Hmm, interesting. Thanks for catching this. I'll investigate...

Ping?

Broken because of https://github.com/stac-extensions/processing/pull/14.

Indeed, the anyOf is a problem. It's an issue in all extensions basically. If one of them is fullfilled, the others don't need to be fulfilled. You can fix this to some degree by making pure field validation with no field requirements in allOf and then add the requirements in anyOf. An example how I believe it can be solved: https://github.com/stac-extensions/processing/commit/8045be9a6885e8a0fadd2bca8827e07b6a703c72
Nevertheless, this still does not solve the issue for the other potential occurances and only for provider.
PS: I'm basically the only one who's doing all the JSON Schema maintenance for the whole STAC spec + extension, which I have like 1-2 hours per month allocated for. Fixing this here and throughout the STAC ecosystem will need a funding effort so that someone can work on this for some time... @cholmes

I've changed these to Jest.

I have updated the JSON Schema to properly validate fields and requirements in #18 so this might be obsolete

The "should fail validation without any summaries processing: properties" test fails with the schema in the main branch. Also, this adds tests which are easier to read and understand in isolation than the schema itself, making sure that future changes don't break anything.

The "should fail validation without any summaries processing: properties" test fails with the schema in the main branch.

Yes, but that is intended (if I understand the tests correctly) as there are still processing properties in providers. For Collections, it checks whether any place contains processing properties, so if any of summaries, assets, item_assets or providers have processing properties, the requirement for specifying at least one processing property is fulfilled.

It also fails "should fail validation with invalid providers processing:software value".

The "should fail validation without any summaries processing: properties" test fails with the schema in the main branch.

Yes, but that is intended (if I understand the tests correctly) as there are still processing properties in providers.

I'll make sure it tests that.

It also fails "should fail validation with invalid providers processing:software value".

Haven't run your tests as I'm on my non-dev machine right now, but if I validate invalid stuff processing:software in providers in some online json schema validator it correctly throws an exception. So I guess something with your tests is wrong.

Looks like you fixed the original issue, thank you! The tests should still be relevant.

Anything missing to get this merged?

I don't work with STAC anymore, so I've unsubscribed from this. Please @ me if you would like some further feedback.

repo: stac-extensions/processing


text:
install error

@jcarpent Hi, sorry to distrub you.
I have followed the linux installation procedure step by step to install Pinocchio
but when I got to step 4 and input:
sudo apt update
the terminal feedback the error:
The repository 'http://robotpkg.openrobots.org/packages/debian/pub xenial Release' does not have a Release file. Updating from such a repository can't be done securely, and is therefore disabled by default.
How can I address this issue?

As we mentioned in other issues to you, we have dropped the support of xenial as it has reached its EOL.

Thanks for your reply.
Can you tell me which issue your mentioned can I refer to？
I‘m very hurry to install Pinocchio，but the official installation guidance don’t works.

repo: stack-of-tasks/pinocchio


text:
Spark: Add the HBase connector to the image

Add the Apache HBase™ Spark Connector to the image, so that Spark applications can access HBase.
The connector must be compiled for a specific HBase version. It must be tested, if choosing the current LTS version (2.4.18) also works with the other supported versions, i.e. 2.6.0.

[x] #878
[x] #882
[x] stackabletech/spark-k8s-operator#471

Do we have docs for this? If so, could you link to them? And could you include a snippet that we can use in the release notes?

Do we have docs for this?

No, we don't. I am not sure if it makes sense to document how to use HBase within a Spark application. This is not SDP specific. However, it could be useful to list the capabilities of our product images in the documentation, but I am not aware that we did this already.

And could you include a snippet that we can use in the release notes?

Release Notes
Other product features

Apache Spark: Apache HBase Spark Connector added

authors: lfrancke siegfriedweber

repo: stackabletech/docker-images


text:
Constant fix for the same error

Describe the bug
It tried to fix the same issue three time essentialy doing the same thing and failing chewing through all the available tokens.
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-jbxivb
Steps to reproduce
click the fix error button when it appears
Expected behavior
it should report that it cannot fix the error or that it is trying to fix the same error.  If it fails to fix the error it should refund the tokens it has used.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = 130.0.0.0
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 69580519,
  "usedJSHeapSize": 50096735,
  "jsHeapSizeLimit": 4294705152
}
Username = KWirePain
Chat ID = 1e95dd1c8437

Additional context
No response

#678 has a collection of best practices to avoid this


text:
I upgraded to the higher version, came back, and all (chat) memory was lost

Describe the bug
I've build the framework for an amazing app with your tool, just within 2 days.
Now I need to heavily restore it from a backup I made some hours ago, since bolt.new cant remember or restore checkpoints from 2 minutes (!!) ago, just because I upgraded the plan. Now fixing manually since 2 hours...
I also tried to import my backup project from git, but thats not possible (bolt.new not available for my git project!?) - just wanted to give you that feedaback because I strongly believe your product rocks!!
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-7v7d6s
Steps to reproduce
create a project, web app for 2 days, try to implement all supabase functionalities, leave the chat and come back -> tell bolt.new to recreate the last version -> no checkpoint memory for version before leaving the chat. also asking to restore the currently deployed version not possible
Expected behavior
give me the full functional version before the crash 2 minutes ago (checkpoint feature, but working after leaving and coming back to chat)
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = 130.0.0.0
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 67679763,
  "usedJSHeapSize": 63799743,
  "jsHeapSizeLimit": 4294705152
}
Username = gitlevo
Chat ID = 7399081abc2f

Additional context
No response

@gitlevo check #39 for the current workaround and for updates on the complete solution, coming soon. TLDR: your work is not lost, just not showing properly in the UI. Appreciate your patience during this beta!


text:
feat: add rule to enforce comment style

Added a lint rule to verify the line comments do not start with a capital letter or end with a dot and have to start with a capital and end with a dot.
I had to make some assumptions on the structure of the comment (based on how prettier formats them) cause I didn't want to use a regex to extract the first arg. That could make the rule much slower I think. Feel free to propose a better way to extract the args.

Updated it so that it checks

line comment should start with a space
line comment should start without a capital letter UNLESS the entire first word is capitalised and the first char is indeed a letter
block comment should start with /\*\*\n * (so slash star star newline space star
block comment has to start with a capital unless it's not a letter.

I think this should match all cases you mentioned and the ones I've found in the webcontainer repo.

That sounds great. Thanks for adding this rule 👍

Maybe we can use a more general commit message as well, e.g. feat: add rule to enforce comment style. WDYT?

I'll update the message when squashing

repo: stackblitz/eslint-plugin


text:
TOR patch

Description
This pr adds tor to the dev environment , generates an onion address #1493 and fixes some issues that could cause tor
to not work as expected in production.
LND and gRPC-js ✓
To connect to an onion address using grpc-js in ln-service, the only available solution appears to be setting the environment variable GRPC_PROXY or HTTPS_PROXY. However, this forces all gRPC traffic through Tor, which is not ideal.
To address this, I set up Privoxy in front of Tor and configured it to route only .onion traffic through the network. This HTTP (gRPC) only proxy runs alongside the Tor HTTP proxy on port 7051. this is now handled by a patched authenticatedLndGrpc that set  grpc.enable_http_proxy
CLN ✓✓
cln worked out of the box once the hidden service was connected.
LNBITS (?)
lnbits did not work out of the box. I had to replace the use of fetch with cross-fetch to make it functional, as the native fetch lacks support for agents. With this change, the connection works, but I'm still unable to connect successfully since the lnbits instance is set up to use VoidWallet, which is unrelated to this PR.
New commands
I've added some new commands to sndev

sndev stacker_lnd get_onion : returns the onion host:port for the stacker_lnd instance
sndev stacker_lnd get_cert : returns the tls cert for stacker_lnd (it now needs to include the onion address so it cannot be static)
sndev tor get_onion: returns the onion address (same as sndev stacker_lnd get_onion but without the lnd port)
sndev stacker_cln get_onion: returns the onion address (host:port)
sndev lnbits get_onion: returns the onion address (host:port)

Checklist
Are your changes backwards compatible? Please answer below:
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
all the wallets connect and the testInvoice succeed (except lnbits, see LNBITS )
Did you introduce any new environment variables? If so, call them out explicitly here:
GRPC_PROXY

This looks solid! I'll pull down tomorrow to QA and we'll get it merged.

When I attempt to use attach lnd with onion I get:

failed to create test invoice: No connection established. Last error: undefined

Did you see that in your testing? Do you know what might be causing that?

When I attempt to use attach lnd with onion I get:

failed to create test invoice: No connection established. Last error: undefined

Did you see that in your testing? Do you know what might be causing that?

I've seen this happening if you try to connect it too soon and the hidden service is not ready yet.
But can you please double check the address with sndev stacker_lnd get_onion  ?
And if you have tor browser or brave, you could also try to connect to the service and see if resolves.

sndev stacker_lnd get_onion works and the container has been up for awhile.

I'll try deleting the containers and starting again. I might not have started the env from scratch.

I've just tested it again, i can't reproduce, this is the commands i am using, just so that we are on the same page
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev stop
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev delete
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev start
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev login rblb
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev stacker_lnd get_onion
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev stacker_lndcli -n regtest bakemacaroon invoices:write
riccardo@riccardo-ws:/PROJ/DEV/stacker.news$ bash sndev stacker_lnd get_cert

After deleting my containers attaching lnd works.

Oh, I didn't realize the configuration was held together by the files under ./docker/lnd, thanks for finding it out. I've fixed it by making the docker compose to load the lnd files directly from the stacker_lnd volume

[x] fix nwc_send
[x] document what's required to connect to lnbits now in wallets/lnbits/ATTACH.md
fixed, it just works now
[x] fix sndev stacker_cln get_onion - it does not work currently
was a typo in the doc, the command is actually sndev stacker_clncli get_onion
[ ] document, if not fix, that cln's cert does not work with the onion
where does it fail? it attaches correctly for me

should be fixed by the last commit

That looked tricky, nice work!

I ended up having to revert this. See #1547

authors: huumn riccardobl


text:
Rebuild heat images with yaql 3.0.0 for 2023.1

To patch vulnerability https://wiki.openstack.org/wiki/OSSN/OSSN-0093 from yaql, bumped yaql requirements to 3.0.0 (See https://github.com/stackhpc/requirements/pull/15)
Then rebuilt heat images as they use yaql.

Actually could you provide a release note with a security section?

Yet again, I forgot about release note. I'll add it to all 3 of them

repo: stackhpc/stackhpc-kayobe-config


text:
Add SMART Monitoring with dash and alerts

Added smartmon script as is from the prometheus-community github and then removed NVME support from this script in favour of using the nvme-cli script, which has also been added in. This is because the nvme-cli script provides better metrics than the smartmon script does. The script also adds the serial number of the disk as a label to all SMART metrics.
Added a Kayobe custom playbook to easily deploy the script and associated cron job. This playbook installs smartmontool and nvmecli then copies these over to the hosts and sets up a cronjob which runs the scripts and stores the metrics in the docker volume for node exporter. The playbook changes the way the metrics are saved to a file by making use of the mv command as it is atomic. This was needed as at times prometheus would read a partially completed file.
Added a prometheus alert to alert when a drive is reported as not healthy for more than 10 minutes.
Added a Grafana dashboard to display the number of healthy and unhealthy drives reported in prometheus.

Ah ok. I guess that answers my question to Mark about including the changes in this PR or not. :) Thank you!

@dougszumski @markgoddard Added in the changes to globals.yml

docs now in stackhpc/yoga

authors: markgoddard technowhizz


text:
Update module github.com/stackitcloud/stackit-sdk-go to v0.5.0

This PR contains the following updates:

Package
Update
Change

github.com/stackitcloud/stackit-sdk-go
minor
v0.4.0 -> v0.5.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Updating to v0.6.0 directly in #43

authors: joaopalet stackit-pipeline

repo: stackitcloud/stackit-sdk-generator


text:
Re-enable NATS test with higher timeout

Summary
Re-enable tests for the NATS messaging channel; running this with go test -count 200 ./internal/events/nats produced 5 failures with the previous 5s timeout.  Increasing the timeout to 15s avoided all timeouts.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
go test -count 200 ./internal/events/nats
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[x] Included tests that validate the fix or feature.
[x] Checked that related changes are merged.

coverage: 53.132% (+0.5%) from 52.658%
when pulling eff53feae6091ea42f10fdefcbc40ece23e16277 on evankanderson:fix-nats-tests
into 87aae863100147925af55bdda575fb5bc2031c62 on stacklok:main.

authors: coveralls evankanderson

repo: stacklok/minder


text:
Reduce race condition likelihood, remove redundant diff download

This PR introduces a few changes to the sanity-vuln-check-updates job

Will reduce (not eliminate) the likelihood of a race condition that occurs when the definitions.stackrox.io GCS bucket is updated after the sanity-check-vuln-updates job has started (which has been observed).  It does this by using the age of the GCS diff.zip as close to the 1hr age check as possible (instead of the age determined when the job started)
The CloudFlare age header is now also logged for future troubleshooting / logic as necessary, it shows the actual cache age (for the particular CloudFlare node)
Each diff was being downloaded multiple times (back to back), once for extracting a manifest.json, and the other for extracting the cache-control headers.  This PR removes the redundant download (wget) which should reduce bandwidth and potentially speed up the job (further reducing race condition likelihood)
The temporary diff.zip downloads have been moved into the job's $WORKING_DIR so that cleanup can perform as expected

Smoke tested locally:
$ ./sanity-check-vuln-updates.sh
-----------------------------------------------------------------------
diff_id                  : 0133c2cf-8abe-4d79-9250-9b64b5b3e43e
gsutil_last_update       : Mon, 06 Feb 2023 21:58:07 GMT
gcs_object_age_seconds   : 8283
gcs_object_age_secs_now  : 8283

url_gsutil               : gs://definitions.stackrox.io/0133c2cf-8abe-4d79-9250-9b64b5b3e43e/diff.zip
url_cloudflare           : https://definitions.stackrox.io/0133c2cf-8abe-4d79-9250-9b64b5b3e43e/diff.zip
url_gcs_https            : https://storage.googleapis.com/definitions.stackrox.io/0133c2cf-8abe-4d79-9250-9b64b5b3e43e/diff.zip

metadata_cloudflare      : {"since":"2020-09-08T17:02:45.481154658Z","until":"2023-02-06T21:07:39.922044426Z"}
metadata_gcs_https       : {"since":"2020-09-08T17:02:45.481154658Z","until":"2023-02-06T21:07:39.922044426Z"}

cache_age_cloudflare     : 0
cache_control_cloudflare : cache-control: public, max-age=3600
cache_control_gcs_https  : cache-control: public, max-age=3600

md5sum_cloudflare        : 7c730179c770172308499094982549db
md5sum_gcs_https         : 7c730179c770172308499094982549db

...

/retest

repo: stackrox/scanner


text:
ROX-11697: Add OSG GCP e2e tests

Description
Per title.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
CI is sufficient

/test

/test eks-qa-e2e-tests
/test openshift-4-qa-e2e-tests
/test osd-gcp-qa-e2e-tests

/test eks-qa-e2e-tests
/test openshift-4-qa-e2e-tests
/test osd-gcp-qa-e2e-tests

/test eks-qa-e2e-tests
/test openshift-4-qa-e2e-tests
/test osd-gcp-qa-e2e-tests

/retest-required

repo: stackrox/stackrox


text:
add better description to readme

This one needed an update compared to the others, and it gives a visitor an idea of where to go for more information (issues tab).

@whoabuddy looks good to me. Do you think we should add something welcoming contributions? E.g., "Please feel free to comment on any of the existing proposals, or to make a new proposal by opening a new issue."
The more I think about it, the more I think it would be good to have a single governance "landing page" that we can direct people to - I think this could be very helpful especially for newcomers who don't necessarily have the lay of the land yet. The closest thing we have to that is https://github.com/stacksgov/resources (and maybe, at some point, stacks.org). Do you think we should link that here?

We can follow up on the "landing page" thing in https://github.com/stacksgov/pm/issues/45

authors: lrettig whoabuddy

repo: stacksgov/proposals


text:
Better program rule?

Does this looks like a slightly better implementation of the program rule? It follows the module rule.
Program can also support internal procedures like modules for example which are now supported.
and I have a question, why do we need prec.right in the original implementation of the program_block?
-    program_block: $ => seq(
-      prec.right(seq(
-        caseInsensitive('program'),
-        $.identifier
-      )),
-      optional($.comment),
-      $._end_of_statement,
+    program: $ => seq(
+      $.program_statement,
       repeat($._specification_part),
       repeat($._statement),
+      optional($.internal_procedures),
       $.end_program_statement
     ),

+    program_statement: $ => seq(caseInsensitive('program'), $._name),
     end_program_statement: $ => blockStructureEnding($, 'program'),

@oponkork I'm not sure why prec.right was needed before. I assume that sometimes the program name identifier was stolen sometimes or there used to be a conflict in a previous version of the grammar. If all the tests pass without the prec.right I'm fine with dropping it.
As for adding support for internal procedures to the program block if the language supports it please do, just add a test case to Program section of the test/corpus/constructs.txt file.

authors: oponkork stadelmanma

repo: stadelmanma/tree-sitter-fortran


text:
How does this interact with Error causes?

Considering that error causes are now part of the JS standard, using that instead would be beneficial, no?
This is the approach eg I took with https://github.com/voxpelli/pony-cause

Thanks! And what about the case console.log(new ErrorWithCause(......))?

@staltz ErrorWithCause is meant to be a drop in replacement for the standardised new Error('foo', { cause: err }), to be used in contexts where the built in one isn't supported (older browsers and Node 14 and older I believe).
The standard proposal doesn't specify anything around how console.log() should handle it: https://github.com/tc39/proposal-error-cause
Though Firefox prints it like this:

And Node.js 16.14.0 and 17.3.0 shipped https://github.com/nodejs/node/pull/41002, making it also printing the causes

Here's a screenshot of how Node 16.14.0 console.log handles it:

Eg. pino has got support merged as well: https://github.com/pinojs/pino-std-serializers/pull/78

Good to know! Note to self, here's how Node.js 16.14.0 renders "string errors" and stackless errors:
> console.log(new Error('bar', {cause: 'foo'}))
Error: bar
    at REPL10:1:13
    at Script.runInThisContext (node:vm:129:12)
    at REPLServer.defaultEval (node:repl:564:29)
    at bound (node:domain:421:15)
    at REPLServer.runBound [as eval] (node:domain:432:12)
    at REPLServer.onLine (node:repl:891:10)
    at REPLServer.emit (node:events:532:35)
    at REPLServer.emit (node:domain:475:12)
    at REPLServer.Interface._onLine (node:readline:487:10)
    at REPLServer.Interface._line (node:readline:864:8) {
  [cause]: 'foo'
}

> console.log(new Error('bar', {cause: {name:'TypeError',message:'foo'}}))
Error: bar
    at REPL11:1:13
    at Script.runInThisContext (node:vm:129:12)
    at REPLServer.defaultEval (node:repl:564:29)
    at bound (node:domain:421:15)
    at REPLServer.runBound [as eval] (node:domain:432:12)
    at REPLServer.onLine (node:repl:891:10)
    at REPLServer.emit (node:events:532:35)
    at REPLServer.emit (node:domain:475:12)
    at REPLServer.Interface._onLine (node:readline:487:10)
    at REPLServer.Interface._line (node:readline:864:8) {
  [cause]: { name: 'TypeError', message: 'foo' }
}

My use case is most important in Node.js, so would it be okay to ask that pony-cause follow the Node.js style of rendering in the cases of string errors and stackless errors?

@staltz That sounds like a good approach to it, I’ll try to make it happen soon 👍

@staltz What's your thoughts on this solution? https://github.com/voxpelli/pony-cause/pull/23

authors: staltz voxpelli

repo: staltz/clarify-error


text:
🛑 Recatt Server is down

In 6b48273, Recatt Server (https://recatt.its-telekom.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Recatt Server is back up in b915025.

repo: stamateas/upptime


text:
Adding doc for many functions in prim/scal/prob

Submisison Checklist

[ ] Run unit tests: ./runTests.py test/unit
[ ] Run cpplint: make cpplint
[ ] Declare copyright holder and open-source license: see below

Summary:
This doesn't finish adding doxygen doc to the distributions in prim/scal/prob but tips the balance in our favor and seems like a small enough stack to review. Begins to address issues in https://github.com/stan-dev/math/issues/475
Intended Effect:
No effect on code except for one function that was re-organized
How to Verify:
Check for errors in doc, allow CI to run tests. I'll check too.
Side Effects:
Should be none.
Documentation:
Reviewer Suggestions:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Going to make a superficial change (reverse the order of param and tparam in doxygen), don't merge this for a second.

Yes, definitely just doc now and change behaviors later.
I don't know what you mean by skipping invalid parameters, but our probability functions should throw if they get illegal arguments.  So please open another issue if that's what's going on.

Sounds good.  We don't want to just keep adding wrappers when we don't need them---better to fix the underlying issues with beta_rng.  But not in this pull request.

Agreed---we don't want to start duplicating this all over the place because it'll be too hard to maintain the doc.

Please let me know when it's ready to review again.  Thanks.

should be ready to go now

Looks great.  Thanks.

@thelseraphim  I merged and then it says "Closed with unmerged commits".  I don't know what that means.  I didn't quite understand this:
http://stackoverflow.com/questions/30132833/need-help-understanding-a-merge-and-closed-with-unmerged-commits-message
Any idea what's going on?

I think you hit close without hitting merge. I don't see it on develop.

@thelseraphim  Thanks for the heads up. That explains the odd message.

authors: bob-carpenter thelseraphim

repo: stan-dev/math