treat k=0 modes carefully in window calculation

I was wondering why the unit window normalization did not agree better with the sum over cells normalization - it seemed like they should agree to pretty high precision for the Y5 mock test I was doing. This for the traditional calculation with only the same size box as the power calculation. So this led me to notice that, when I set up kedges to isolate it, the k=0 mode appears to be set to zero minus shot noise, even though for window it should not at all be zero (the mean field is not zero). I couldn't figure out where/why this actually happens, but when I figured out how to hack in a reasonable value in the window power output object before plugging it into "to_real", and commented out this line which ignores k=0 anyway:
https://github.com/cosmodesi/pypower/blob/a6d91712229b61b00710ec1a533f89ffbfa9a121/pypower/smooth_window.py#L382
it looks like this will fix the problem, i.e., the sum over cells normalization will agree with full window normalization to high precision.
So I think this should be fixed. The window is just wrong if k=0 is not treated properly, and this will propagate into a real error in fits. Here's where, Florian's trick of adding larger boxes can fix the problem (if done carefully - I will file another issue about that), by taking the k you use in the calculation closer to zero, but this may not be so necessary if the zero mode in the smaller boxes is actually used.

Good catch! This comes from MeshFFTPower zeroing k=0 modes for pk estimation, e.g. https://github.com/cosmodesi/pypower/blob/a6d91712229b61b00710ec1a533f89ffbfa9a121/pypower/fft_power.py#L1322. I think I'll just add the power back in CatalogSmoothWindow. Hope I find some time to do this soon.

Shouldn't this just not be here? I.e., if the mean of the field is zero, it will be zero anyway, and if it is not, it is wrong...

Current convention is, if field is non zero, the selection function is assumed uniform, equal to the mean field (e.g., case where we are computing the power spectrum of cubic mock, providing only "data_positions").

Ok, but that will produce 0 Fourier mode value for k=0 mode, so no problem not setting it to zero by hand. I.e., I can't imagine a scenario where you want to set it to zero by hand...
Ok, unless you don't actually subtract the mean before calculating the power in that case... but to me this is a special trick which, if you are going to use, you should be responsible for dealing with the (correctly non-zero) zero mode in the output... The current thing is a trap for general users...

Well, the general users expect that giving data positions only to CatalogFFTPower will compute Pk assuming uniform selection function, no?

I'd just say, it is not a generally correct thing to do, so one way or another I would not hard-code it in... (i.e., I'd put it in only at a level where the context is clear enough to justify). This is the kind of thing that gets us in trouble, with things that should work appearing not to work...

To put it another way: no one should ever want to actually use this 0 you are writing in for k=0, because it is trivial (e.g., for my power summary statistic I had set up kedges to avoid confusingly mixing this with other bins), so the only people for whom it should matter should want the non-trivial, non-zero, value... (e.g., for your uniform cube, people who would be mixing in this mode... just shouldn't do that (unless they have though it through carefully enough to have a good reason)... so it should be fine if you just report the non-zero value)

Well, the issue is that other modes may fall together with k=0 in the kbin [0, whatever k>0].
Ok, so what about separately keeping track of the k=0 value in the end result (PowerSpectrumMultipoles and PowerSpectrumWedges) - just as shotnoise, and dub that "power_zeromode_nonorm", and propose options:

to not remove k=0 power
to not remove shotnoise (unrelated, but might be the opportunity to propose that)
in e.g. https://github.com/cosmodesi/pypower/blob/a6d91712229b61b00710ec1a533f89ffbfa9a121/pypower/fft_power.py#L791 (same for PowerSpectrumWedges)

I'm not sure I understand what you're saying, although at this point I guess you understand the issue well enough to do something that works out ok in practice.
I guess I'd just re-iterate that, after digesting everything, I really think it should be fine to just delete those lines singling out k=0. Yes, sometimes people may set up kedges that mixes this with other modes, but those people probably don't want the 0 mixed in either, and should just fix this - it might be better for them if it was more obvious because a really crazy result came out. Now that we have run into the confusion, if you write this into the documentation (e.g., of kedges), problems should be mostly avoided.
Incidentally though, could k=0 not be excluded from a naive kmin=0 bin by defining all bins to include modes with k>kmin, k<=kmax... you must need to make a choice on this in any case, so a mode doesn't fall in 2 bins, right? I.e., no one setting a bin 0-x should assume the k=0 mode is in the bin - they should look it up/experiment (as I did), if they care - so if this kind of kedges does not report k=0 at all, most people will be happy, and people who want it, like for the window, can explicitly set a negative kmin to make sure to include it...
Bottom line: your goal of making almost everyone happy even if they haven't thought about any of this should be best achieved by excluding the k=0 mode from an input 0-x bin by definition, not by including it but setting it to zero...

Yes, currently we take left edges to be inclusive, right edges to be exclusive, but that can be reversed very easily. Even if P(k=0) = 0, changing the convention will change the value of the first bin (due to changing the number of modes), but maybe it is the actual best thing to do. I will think about it a bit more.

It seems clearly the best thing to do, since excluding k=0 is generally what people will want, with no argument for going the other way that I see. And delete this setting zero mode to zero so when one writes in negative kedges you pick up the correct thing. (anyone who writes in negative kedges and really wants k=0 set to zero... has clearly thought things through enough that they can figure out how to do it themselves)

I'll try to correct this tonight.

I ended up treating separately pk(k=0), as passing in negative edges would not be super-intuitive for an average user. At least with current implementation we have all information stored (while keeping backward-compatibility, hopefully). See 948546adc9fed1dc3ac510240c720657d7dcda0b. Not much time to test, though, so there may be some bugs left.

I was happy to see that you had commented out the part that zeroed the zero mode before, so I could just ignore whatever else you did and propagate things naturally... but then it seems like the zero mode is still zeroed...  Is this intentional? Where does it happen?
E.g., a very natural binning seems to be something like:
L=7000
N=256
dk=2*np.pi/L
print(dk,np.pi/(L/N))
kedges = np.arange(-dk/2, 0.4+dk,dk)
(i.e., following the 1D grid, although of course not unambiguously best in 3D)
If someone wants to use 0-x bins, I don't understand why you weren't happy with doing kmin<k<=kmax so it doesn't matter to them what you do with zero mode? (and then not zeroing it) Mixing in the zero mode seems like a trap for naive users whether you zero it or not...

Ok... I found "get_power"... It seems like the window version of "remove_zero" should default to False. Also, "remove" is ambiguous, i.e., it might (arguably should) mean just treat this mode as not existing, rather than setting it to zero (the "zero" only telling you that you mean k=0). (this solution seems like a bunch of unnecessary bookkeeping... but if you're the one doing it, I guess I can't complain)
As a general coding thing, it would be nice to have some way of indicating "you are not supposed to access this from outside" (like private in C++). If only by naming convention. Isn't there some convention like this with underscores?

I guess I spoke too soon. When I do
window1r=window1.to_real(sep=np.geomspace(1e-2, 1e4, 2**11))
now I just get a bunch of nans (was wondering if it was going to include zero mode).
With my simple "don't zero zero mode" hack, I was getting single-box window functions beautifully consistent with combined-box thing.

I just renamed remove_zero into null_zero_mode, setting to False by default for window function, and extrapolation values to zero (which would remove the "bunch of nan's" you are getting).

"I just renamed remove_zero into null_zero_mode, setting to False by default for window function, and extrapolation values to zero (which would remove the "bunch of nan's" you are getting)." (not sure why this comment doesn't show up here for me)
I'm still getting nans. E.g., for your window2 in window_examples notebook. (if you want to say I shouldn't feed it a power measurement that has nans in it, I wouldn't hate that, it's just that before you could...)

I deleted my message because it figured out that nans were not removed. Now this should be fine, see https://github.com/cosmodesi/pypower/blob/main/nb/window_examples.ipynb, cell 6. Does this match what you obtained? Below my original comment.
I have just (c6e2d91) renamed remove_zero into null_zero_mode, setting to False by default for window function, and extrapolation values to zero (which would remove the "bunch of nan's" you are getting). I was not totally happy with kmin<k<=kmax, as the user would have needed to input negative k-edges for PowerSpectrumSmoothWindow, which would not be very intuitive. (I could have manually added a negative bin internally, but that is not something the user would expect). Anyway, my current suggestion does not prevent us from switching to kmin < k <= kmax at a later stage, as we have all the information recorded.
Yes, in Python the convention is to start names of "private attributes" with an underscore. Where do you see an application of that? (I do not think we should tell the user not to access any of the current power spectrum / window function attributes?).

The example of needing private I was thinking of was that, because zero mode is zeroed in underlying power storage, if I'm using that directly I will get wrong answers - if you force the user to access it through get_power they will see these options and understand how to get what they want.
Anyway, to_real is working now.


Remove a workaround for a resolved runtime issue

As far as I can tell, dotnet/runtime#30295 has been fully resolved and backported to 3.0. We shouldn't need this workaround in YARP anymore.
We can delete this block of code:
https://github.com/microsoft/reverse-proxy/blob/5d2a76546620ab1d9b784d0f05242958cbc508c8/src/ReverseProxy/Forwarder/StreamCopyHttpContent.cs#L167-L182

Actually, we still want to flush here to force the headers to be sent, even if the HTTP/2 bug has been fixed.


Remove usage of git submodule for cardano-mainnet-mirror

Reported by @michalrus:
❯ git clone  --recurse-submodules=never https://github.com/IntersectMBO/cardano-ledger.git
Cloning into 'cardano-ledger'...
remote: Enumerating objects: 179162, done.
remote: Counting objects: 100% (1276/1276), done.
remote: Compressing objects: 100% (514/514), done.
remote: Total 179162 (delta 998), reused 854 (delta 676), pack-reused 177886 (from 1)
Receiving objects: 100% (179162/179162), 113.63 MiB | 2.24 MiB/s, done.
Resolving deltas: 100% (101207/101207), done.
error: object eb6fb9bef41871323404b2c19e23fb5550ef04c9: gitmodulesUrl: disallowed submodule url: https://github.com/:input-output-hk/cardano-mainnet-mirror.git
fatal: fsck error in pack objects
fatal: index-pack failed

The submodule URL has a colon where it should have a slash: https://github.com/:… instead of https://github.com/….

We do not use cardano-mainnet-mirror aside from some byron era tests. We retrieve that repo differently on CI, so we do not need it as a git submodule. It should be removed.

@neilmayhew found the real reason.  The setting in ~/.gitconfig is:
[transfer]
        fsckObjects = true

A one-time workaround:
❯ git --config-env transfer.fsckObjects=false clone https://github.com/IntersectMBO/cardano-ledger.git

The stronger check in git fsck was added in January 2024. It was introduced in this patch thread in the git mailing list. One review response said this:

By making it an fsck check, though, any mistakes that are embedded in history (even if they are now corrected) will make it a pain to use the repository with sites that enable transfer.fsckObjects.
My gut feeling is that this is probably OK in practice. If it does cause pain, we might consider loosening the fsck.gitmodulesUrl severity (under the notion from above that it is no longer a critical security check). But if it doesn't cause real-world pain, being pickier is probably better (it may save us from a vulnerability down the road).

I've written a response asking if loosening could now be considered, since a significant real-world example of pain has been identified.

Rewriting history is obviously not an option. Therefore it looks like we can close this issue as won't fix, since there isn't really anything that we can do in order to avoid this problem.
If I am wrong and someone has a cute idea about how to deal with this, please reopen the issue with such suggestion.

The git maintainers are open to downgrading the fsck message to a warning instead of an error. This is an easy fix and I'm in the process of submitting a patch for it.
The maintainers did make me aware of a way to handle this in our own repo, however. There's a repo config option to specify a "skiplist" file containing a list of objects that shouldn't have semantic checks applied to them. In our case, this is just one object (the blob of the .gitattributes file that existed briefly). This option works well, and enables fsck in our repo to complete successfully without errors or warnings.
I propose we create a hidden file called .git-fsck-skiplist, similar to the .git-blame-ignore-revs we have already, containing the offending blob hash. We then add a small note at the end of the README mentioning this problem that's embedded in the repo history, and telling them to run git config fsck.skipList .git-fsck-skiplist if they plan on using git fsck. Unfortunately, I don't know of a way to set this automatically, other than putting it in a shellHook that gets run by nix develop whenever it starts.
This won't help someone who has transfer.fsckObjects enabled and wants to clone, but we can mention in the note the command-line config option they can use to set the skiplist or downgrade the error to a warning.
It's annoying to have to clutter up our README with this info, but I think we have an obligation to at least mention it, and if we put it at the end of the README perhaps it won't be too annoying. What do you think?

I made a PR for it since I had all the information to hand, and even if we don't merge it the information is now recorded somewhere.


add --stdin-from-command flag to backup command

What does this PR change? What problem does it solve?
This pull request is a continuation of #4254.
This fixes #4251 by providing the requested --stdin-from-command flag to the restic backup command. It skips snapshot creation in case the given commands fails as determined by exec.Cmd.Wait() and returns the stderr of the given command as an error message back to the user.
I have not written any tests, nor documentation because I wanted to get some feedback about the path taken here wrt. upstream inclusion first. I am seeing various test failures in existing tests but these seem to be unrelated and might just occur because I'm building/testing the project within a container. Using these changes locally does look promising though:
$ ./restic backup --stdin-from-command --repo ./backup -- pg_dump -h foobar
enter password for repository:
repository 55e7d5a0 opened (version 2, compression level auto)
using parent snapshot cc6e1dec
error: read /stdin: no data read
Fatal: unable to save snapshot: pg_dump: error: connection to database "root" failed: could not translate host name "foobar" to address: No address associated with hostname

Was the change previously discussed in an issue or on the forum?
Closes #4251
Checklist

[x]  I have read the contribution guidelines.
[x]  I have enabled maintainer edits.
[ ]  I have added tests for all code changes.
[ ]  I have added documentation for relevant changes (in the manual).
[ ]  There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x]  I have run gofmt on the code in all commits.
[x]  All commit messages are formatted in the same style as the other commits in the repo.

I have rebased the code to the latest master, and in few days I will proceed to fix it based on changes requested in the old PR :+1:

Is there other software that has this option name (--stdin-from-command)? It's quite long, feels like --stdin-command is more concise without losing any semantics.

Is there other software that has this option name (--stdin-from-command)? It's quite long, feels like --stdin-command is more concise without losing any semantics.

Actually, content-from-command may be better, that is also the name it has in Borg backup. See https://github.com/restic/restic/pull/4254#discussion_r1160749426

Nah, there's already two --stdin-* options, no point in deviating from that prefix.

@MichaelEischer I've implemented your suggestions from the old pull request. I implemented a new io.ReadCloser instead of a new fs.FS, calling cmd.Wait() on io.ReadCloser.Close(). The archiver is back to the original code.
I'm testing the code now :-)

Thank you for continuing with this feature. I tested your branch and it still creates snapshots when subcommand exists with non zero:
$ restic-stdin-command/restic backup --stdin-from-command -- pg_dump -h foobar
repository 12ba8696 opened (version 2, compression level auto)
using parent snapshot 75e9f4c7
subprocess pg_dump: pg_dump: error: could not translate host name "foobar" to address: Name or service not known
error: read /stdin: no data read

Files:           0 new,     0 changed,     0 unmodified
Dirs:            0 new,     0 changed,     0 unmodified
Added to the repository: 0 B   (0 B   stored)

processed 0 files, 0 B in 0:00
snapshot d044b2eb saved
Warning: at least one source file could not be read

$ echo $?
3

$ pg_dump -h foobar; echo $?
pg_dump: error: could not translate host name "foobar" to address: Name or service not known
1

Thank you for continuing with this feature. I tested your branch and it still creates snapshots when subcommand exists with non zero:
$ restic-stdin-command/restic backup --stdin-from-command -- pg_dump -h foobar
repository 12ba8696 opened (version 2, compression level auto)
using parent snapshot 75e9f4c7
subprocess pg_dump: pg_dump: error: could not translate host name "foobar" to address: Name or service not known
error: read /stdin: no data read

Files:           0 new,     0 changed,     0 unmodified
Dirs:            0 new,     0 changed,     0 unmodified
Added to the repository: 0 B   (0 B   stored)

processed 0 files, 0 B in 0:00
snapshot d044b2eb saved
Warning: at least one source file could not be read

$ echo $?
3

$ pg_dump -h foobar; echo $?
pg_dump: error: could not translate host name "foobar" to address: Name or service not known
1

Uh, I was about to do the same test :-D
Thanks for your report, I'll investigate and fix :+1:

The problem was that the error returned in file reading or closing was logged, but the snapshot itself was continuing unaffected (because the logic assumed that an error while reading one file should not abort the snapshot).
The ReadCloserCommand now returns a "fatal" error, and the error is checked in the cmd_backup.go file: if it is "fatal", the snapshot is aborted. Otherwise, the behavior is the same as before: log the error, and exit with code 3 after completing the snapshot.
What do you think?

What do you think?

I'm not sure about the command terminated with no output fatal error. The current behaviour in stdin mode is to log no data read and exit with status code 3 when reading no data.
I like your current implementation more, because having a snapshot with no data makes no sense for me. But it might be behaving differently than we have in existing implementations.

What do you think?

I'm not sure about the command terminated with no output fatal error. The current behaviour in stdin mode is to log no data read and exit with status code 3 when reading no data.
I like your current implementation more, because having a snapshot with no data makes no sense for me. But it might be behaving differently than we have in existing implementations.

You are right, it is a different behavior. I assumed that this is expected, given that we are explicitly asking for monitoring the command.
On second thought, the best way is to check the command exit code also in ReadCloserCommand.Read(), and return a fatal error only when there is an EOF and the exit code is non-zero. By doing so, if the command exits with 0 and there is no output, the snapshot is created with a warning (which is the current behavior for files and stdin), while the snapshot is not created if the exit code is non-zero (which is expected).
I'll modify the code asap :-)

Ok, now the code should stop the snapshot creation by looking only at the exit code. If there is no output, the snapshot is still created with a warning (and exit code 3), which is the same behavior that other snapshot options have (--stdin, but also normal file backup). Let me know if there is something we can improve :-)

Works for me. Very good!
I think there should now be some feedback on the code itself.

I rebased the branch to the latest master :-)

@Enrico204 Thanks for finishing the PR, and sorry for the late feedback. I've somehow missed that the review comments have been addressed in the meantime.
I've reworked the code a bit: the command startup is now handled by fs.CommandReader (that's the new name for the helper in fs). Instead of using canceling the backup indirectly using a context, arch.Error now just returns an error if it is Fatal. This also allows for a nicer error message.

No problem at all :-)
I will compile this branch and I will test it as soon as possible!

I am testing the code since a few weeks: so far, no issues :-)


Update git commit workflow

Update the git commit workflow to change the image tag (see PR https://github.com/vfarcic/argo-combined-app/pull/6) and commit to the app staging (and production) branches.
Also added a check not to trigger the build workflow if the push event is not from master branch.

Thanks a ton


[stable/opa] Parameterize deployment strategy

What this PR does / why we need it:
Template deployment strategy.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

This looks good.  Except it has the same version as the other 2 PRs.

I figured I'd rebase and bump as the others get merged. This way they're independent.

rebased

/approve

/lgtm


preHandler for auth

I can't seem to get 1.0.0-rc10 to work with @fastify/auth. I have the following code:
  fastify.addHook('preHandler', fastify.auth([fastify.verifyClientAuth]))

  fastify.zod.post( ... )

I ended up patching the lib in lieu of a solution.

Hello,
I'm sorry, as mentioned in #15 for some reason GitHub notifications got lost in my mailbox.
Can you please elaborate? I would very gladly welcome a patch that improves support for other plugins.

It does not seem to work for me either. Would love to know what solution you ended up with.


feat: more island injection strategies

Is your feature request related to a problem? Please describe.
Now island component can only hang on window object globally and it is difficult if we want to lazyload it.
In Astro, you can lazyload the island component by multi directives:
<ShowHideButton client:idle />
<HeavyImageCarousel client:visible />
<SidebarToggle client:media="(max-width: 50em)" />

So the key is that island component can be loaded dynamically.Then we can use requestIdleCallback, IntersectionObserver API or some custom logic to decide to load the component in proper time.
Describe the solution you'd like
In Island.js, we can implement above feature in these parts:

Expose more island config to user, such as __island="visible" | "idle" | "media".
Islands bundle build phase, we should hang the load function instead of component itself so that the component to can be loaded dynamically.
In client runtime, we should optimize the hydrate script.Base on the  island config by user, we choose to load the island component and hydrate it in the proper time.

Describe alternatives you've considered
No response
Additional context
No response
Validations

[X] Read the docs.
[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.

I will work on it for a long way.


Make value attribute and resetting the radio group public

Is your feature request related to a problem? Please describe.
When thinking about form validation, users need the ability to query and set the value attribute programmatically. They also need the ability to reset the radio group at a moment's notice.
Describe the solution you'd like
Make the currently existing value attribute and resetRadio function public in order to give the users this functionality.
Describe alternatives you've considered
Leaving as is
Additional context
In the grand scheme of things, we want the users to be able to query the value and reset the state of any of our form elements. So, this implementation should be present in all form elements and that work should be considered/investigated when this ticket is picked up.

This work will be handled in this ticket in auro-formkit:

https://github.com/AlaskaAirlines/auro-formkit/issues/135


bug fix #26

Added condition to verify custom element already exist or not. #26

Thanks for this PR.  I removed some dependencies and this is no longer needed with latest version. 😄


[Unifi] Add support for UnifiOS 3.2+

Description

Add support for UnifiOS 3.2+.
The Current version throw an unknown error without the update.

No feature changes
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer @mil3na Is this a general native warning? Or does that mean I can not use it because Raycast don't support native js code?

Hi @tonka3000 👋
I have to check this, I'll get back to this PR 🙂


accessing custom plugin settings

In ruby framework, I can create custom settings like,
{
  "my_custom_plugin": {
    "foo": true,
    "bar": false
  }
}

and access them in plugin,
def foo_enabled?
  settings['my_custom_plugin']['foo']
end

how can it be done in python framework?

Found it in the code.
for anyone interested,
import utils from sensu_plugin package,
from sensu_plugin import utils
and access settings using get_settings(),
utils.get_settings()['my_custom_plugin']['foo']

I'm going to reopen this with the intention of replicating the way this works in Ruby and making the settings available in the plugin base class.


Annotation "nginx.ingress.kubernetes.io/force-ssl-redirect" leads to an "ingress.yaml" template error

I assume there is an error in the ingress.ymal template. If we add the following annotation to the terraform  code:
nginx.ingress.kubernetes.io/force-ssl-redirect: 'true'
we get the template error "executing "kuberpult/templates/ingress.ymal" at <.Values.ingress.annotations>: range can't iterate over "nginx.ingress.kubernetes.io/force-ssl-redirect": true
--- ingress.yaml snipset ...
kind: Ingress
metadata:
annotations:
cert-manager.io/acme-challenge-type: dns01
cert-manager.io/cluster-issuer: letsencrypt
{{- range $key, $value := .Values.ingress.annotations }}
{{ $key }}: {{ $value }}
{{- end }}
name: kuberpult
spec:
{{}}

Hi @geeko4711 thanks for creating this issue, ingress.annotations should be an object in your terraform code, if you set it using ```
set {
name = "ingress.annotations"
value = "nginx.ingress.kubernetes.io/force-ssl-redirect: 'true'"
}
It will be treated as a string and the template will not compile correctly. You need to provide it as an object, I'm already trying to figure this out, I'll add a new comment once I manage to solve it

@mouhsen-ibrahim any update here?

@geeko4711
I think the easier and simpler solution is not to go through the woes of helm value parsing but pass the values directly in a values.yaml
values [ <<-EOT
  ingress:
    annotations:
      "nginx.ingress.kubernetes.io/force-ssl-redirect": "true"
  EOT
]


✨ feat(shortcodes): add 'aside' shortcode for side notes

Summary
Adds aside shortcode for supplementary content.
Users can set the margin on which to show the note. The content can be provided as a text parameter or using body within the shortcode tags (see docs).
Related issue
Resolves #444
Changes

Adds shortcode
Updates CSS
Adds documentation

Accessibility
Uses semantic HTML (<aside>) and has good contrast for the mobile look.
Screenshots
Wide screen:

Mobile (or narrow screen):

Type of change

[ ] Bug fix (fixes an issue without altering functionality)
[X] New feature (adds non-breaking functionality)
[ ] Breaking change (alters existing functionality)
[ ] UI/UX improvement (enhances user interface without altering functionality)
[ ] Refactor (improves code quality without altering functionality)
[ ] Documentation update
[ ] Other (please describe below)

Checklist

[X] I have verified the accessibility of my changes
[X] I have tested all possible scenarios for this change
[ ] I have updated theme.toml with a sane default for the feature
[ ] I have updated config.toml in tabi-start
[X] I have made corresponding changes to the documentation:

[ ] Updated config.toml comments
[ ] Updated theme.toml comments
[ ] Updated "Mastering tabi" post in English
[ ] (Optional) Updated "Mastering tabi" post in Spanish
[ ] (Optional) Updated "Mastering tabi" post in Catalan

Hello. I tried to use new aside feature - works good with default setting (text moved to left) but I can't move it to right. Documentation says:

The shortcode accepts two parameters:
position: Set to “right” to place in right margin (defaults to left)

So I tried this:
{{ aside(text="Sidenote text", position = right) }} [1]
and this:
{{ aside(text="Sidenote text", data-position = right) }} [2]
but none of them works.
[1] from documentation: https://welpo.github.io/tabi/blog/shortcodes/#aside-side-margin-note
[2] from sass/parts/_aside.scss file

Try
{{ aside(text="Sidenote text", position="right") }}

Just updated the docs (https://github.com/welpo/tabi/commit/da1b6bb0cc7719f3de23a6855d80dc0262d5c025) to make it clearer!
Thanks~

{{ aside(text="Sidenote text", position = right) }}

It works, thanks!

I've noticed another things. Take a look into attached screenshot.

If I use {{ aside(text="Sidenote text", position="right") }}, it renders as part 1 on the screenshot. Looks good.
If I put aside shortcode in one line with paragraph, it renders as part 2 on the screenshot. Sidenote text has the same baseline as main text -it is good and expected. But main text is shown in sans-serif font - it is unexpected and unwanted.
f I put aside shortcode as separate line in index.md, then blank line and the paragraph itself, it renders as part 3 on the screenshot. Sidenote text hasn't the same baseline as main text, they are offset - it is unwanted. But main text is shown in serif font - it is expected and wanted.
What should I check?

This is all in one page/article?
Can you give me the html/markdown so I can test the exact same setup on my end?

This is all in one page/article?

Yes, one page.

Can you give me the page content (markdown with shortcode calls) so I can test the exact same setup on my end?

Of course. Please check your e-mail box.

Got it!
Make sure you call the shortcode on its own line, not inside a paragraph. That should fix it!
I've added a warning to the docs (https://github.com/welpo/tabi/commit/1dcd615615b492dffc00c34bd7e1bbc680cf95fd)

Thank you for checking this.

Thank you for helping improve tabi!


[TUBEMQ-300] Update LICENSE [addendum]

Codecov Report

Merging #231 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #231      +/-   ##
===========================================
- Coverage      7.89%   7.88%   -0.02%
+ Complexity      458     456       -2
===========================================
  Files           242     242
  Lines         26862   26862
  Branches       4461    4461
===========================================
- Hits           2122    2119       -3
- Misses        24277   24279       +2
- Partials        463     464       +1

Impacted Files
Coverage Δ
Complexity Δ

.../apache/tubemq/corebase/policies/FlowCtrlItem.java
38.88% <0.00%> (-1.12%)
8.00% <0.00%> (-1.00%)

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
43.98% <0.00%> (-0.59%)
34.00% <0.00%> (-1.00%)

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 6a5ca49...1e69966. Read the comment docs.

Why not apache license?
MIT license?

The TubeMQ LICENSE is not changed, still Apache V2. This is the description of the external code LICENSE referenced by the project, include:

the reference's source code,
come from where,
what is the category and content of the LICENSE

So, @netroby, you see the MIT's statement

@justinmclean can you take a look? We are preparing to release the next version. Thanks

Preparing to release the next version, Merge firstly.


refactor(artifacts): consistently order ResponsePrepare fields

Fixes
Fixes WB-NNNN
Fixes #NNNN
Description
What does the PR do?
Testing
How was this PR tested?
Checklist

[ ] Include reference to internal ticket "Fixes WB-NNNN" and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Ensure PR title compliance with the conventional commits standards

copilot:poem

Current dependencies on/for this PR:

main

PR #5528

PR #5529   👈

PR #5530

This comment was auto-generated by Graphite.


chore: Address Node SDK vulnerabilities

PR summary
Dependency vulnerability updates
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[X] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.22.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ValidationError-ify ShaderModule

Changelog:
### Additions
- `ShaderModule` is now constructed with a `new` method, which takes a `ShaderModuleCreateInfo` struct. The old constructors `from_words` and `from_bytes` are deprecated.

Because having two different versions of ShaderModuleCreateInfo, one with bytes and one with words, would be difficult, I deprecated the old constructors. I also fixed an oversight in the runtime shader example: SPIR-V in byte form is always little-endian, so when reading the file you have to convert it.

What error format do you mean?


Additon of a FireEye Agent check similar to these

[Enter feedback here]
Hello Colleagues,
We have a challenge similar to what is solved on this page but it is in relation to the FireEye Agent.
Has anyone suggested until now the fireeye agent integration?
Michael

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

ID: b9d13d5f-fb6e-2757-2e97-ea13a5732086
Version Independent ID: 0fa41c6e-f5f1-3fb1-6eff-458977a71159
Content: Endpoint protection recommendations in Azure Security Centers
Content Source: articles/security-center/security-center-endpoint-protection.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

@BASFmthibodeaux We are checking this and will get back to you.

Hi @BASFmthibodeaux, thanks for the feedback. I've spoken with the relevant product team and, as far as I'm aware, there are no plans for including checks for the FireEye Agent.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close

Hi @BASFmthibodeaux, thanks for the feedback. I've spoken with the relevant product team and, as far as I'm aware, there are no plans for including checks for the FireEye Agent.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close


Remove OPENSSL_NO_STDIO guards around certain SSL cert/key functions

These functions are:
SSL_use_certificate_file
SSL_use_RSAPrivateKey_file
SSL_use_PrivateKey_file
SSL_CTX_use_certificate_file
SSL_CTX_use_RSAPrivateKey_file
SSL_CTX_use_PrivateKey_file
SSL_use_certificate_chain_file

Internally, they use BIO_s_file(), which is defined and implemented at
all times, even when OpenSSL is configured no-stdio.

This was found thanks to #1399

It's defined but it doesn't do anything real with no-stdio.
i think this is a waste of time right now.

I wholeheartedly disagree.
What happens is that with no-stdio, these guarded functions are not implemented, but they are called by code in ssl/ssl_conf.c without any restriction, and may thereby cause linking issues.
So I dunno about you, but I'd say that preventing a linking issue might be worth the time.

Assimilated into #1403.  Closing.


Apply to regular bank tabs?

In all seriousness, there are some conveniences here like maintaining a nice layout in regular tabs without costing absurd amounts of bank space.
Although if I did this, wouldn't this be functionally identical to adding a second tag tabs bar that replaces the existing bank tabs bar? Maybe I just want more bank tag tabs visible 😄 .

If this hypothetical feature is implemented, if you had a layout placeholder for an item in a tab, and add that item to the bank, but in a different tab, it would not show up in the tab but the layout placeholder would. I don't know if I could address this situation easily. Maybe


Fix use of ST_MSGN as sequence method

When we upgraded from version 2.7.2 to 4.1.0 of this library we noticed bugs and sneaky behaviours using the sequence method ST_MSGN.
We think that these two issues suffered the same behaviours that we noticed:

#341
https://github.com/Webklex/laravel-imap/issues/454

We checked the differences among old version and new version. We found that the main issue regards the use of the $uid variable in the "fetch" method of the ImapProtocol class. The old version used that variable as a boolean while the new code treats it sometimes as bool and sometimes as int|string.
This pull request restored the old behaviour and with these changes we can see our code started work again.
Can you please check it and understand if you want to merged it in the master branch?

+1
Did not run into the bug, but saw it in code when looking for how to ensure that UIDs are used. Fortunately for me, they are default in this library in a lot of places and PHP seems to treat the newly introduced constant IMAP::ST_UID as true in many places. However, the current code for sure will not work properly with the message numbers constant.
@gioid seems to have found all occurences of the problem and fixed the comparisons. I approve and would merge his changes. However, I have no write access. Just my two cents as info for @Webklex. :)

Hi @gioid ,
many thanks for your pull request as well as time and effort to look for all occurrences.
Best regards,


POC -Pentaho

Started working on it. Trying to compare multiple files, tried compare file, merge rows, switch/case, sort rows. Need to try more things.

ETL Flow.pdf
Please refer this ETL flow.

completed


Moustache templates are in foops!, but they are referenced here

I think this should be centralized a bit better. We can discuss this

Template have been included


How to choose distribution key if VARCHAR type in the only right candidate?

[Enter feedback here]
Tips in the document described "Don't distribute on varchar format".
So How can I choose a distribution key if VARCHAR type in the only right candidate(e.g. store_id, product_id etc.)?

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

ID: 61988aaf-ef0d-999f-536b-47af6b6b1258
Version Independent ID: bf939211-a490-f304-16cf-db870d3fae54
Content: Cheat sheet for dedicated SQL pool (formerly SQL DW) - Azure Synapse Analytics
Content Source: articles/synapse-analytics/sql-data-warehouse/cheat-sheet.md
Service: synapse-analytics
Sub-service: sql-dw
GitHub Login: @mlee3gsd
Microsoft Alias: martinle

@neednlab  Thanks for the question! We are investigating and will update you shortly.

@neednlab I will go ahead with closing this issue. The @notification mechanism continues to work even after an item is closed, in case further communication is needed. We hope to hear from you again.

#please-close


Add user metadata

🔗 Related PRs:

substra-tests (coming soon)
substra-chaincode (coming soon)
substra-backend (coming soon)
substra-frontend (coming soon)

The goal of these PRs is to add a metadata field in every asset in order to be able to store information related to this asset. It could be, for instance, a creation_ts, an epoch, a project_name, ...

@maeldebon could you edit the "coming soon" out of the link to the backend PR (and the same think in the backend PR as well)?

After looking at the substra-tests PR I realize you forgot to add metadata to compute plans.

I'm writing down here what's been decided: compute plan metadata and metadata in printers will be done in separate PRs.

@maeldebon you need to re-generate the references.

@maeldebon flake8 is failing :(


I cant pay in chrome

I want to use the pro version, but I cant. And chrome pay didn't work.
How can I get the pro version? Please tell me the method.

Upper picture said "You cant use the chrome pay now. You didn't complete payment. Please try it later."
T_T ....

You can do payment through PayPal and get subscribed manually.
Below are subscription charges:

01 month : 01$ + 0.052$ (conversion Fee  : 01 * 0.052) + 0.35$ ( PayPal Fee ) = 1.402$
03 month : 03$ + 0.156$ (conversion Fee  : 03 * 0.052) + 0.35$ ( PayPal Fee ) = 5.506$
06 month : 06$ + 0.312$ (conversion Fee  : 06 * 0.052) + 0.35$ ( PayPal Fee ) = 6.662$
12 month : 12$ + 0.624$ (conversion Fee  : 12 * 0.052) + 0.35$ ( PayPal Fee ) = 12.974$

PayPal Subscription

Please share the transaction id once payment is done.
Also share your email id which you want to register for full version.

Thanks,
<EMAIL_ADDRESS>


Add log-level control for dcos-launch

suppresses select libraries to prevent obfuscation
adds truncated options for existing long-name options
moves CLI code to its own module

@orsenthil @amitaekbote PTAL

@lingmann This PR is mostly limited to moving code to smaller files and allowing better debugging visibility when using dcos-launch PTAL


Non-JSON example files

We have some example SDP files for BCP-006-01 as well as JSON. I could include these in three-backtick code blocks in a markdown file, but I thought having them as separate files like the JSON examples would make sense. However I now realise the scripts don't currently publish the SDP files at all...

Possible changes required:

Render SDP (or all non-JSON) examples somehow: https://github.com/AMWA-TV/nmos-doc-build-scripts/blob/main/extract-docs.sh#L220-L224
Lint SDP examples somehow: https://github.com/AMWA-TV/nmos-doc-build-scripts/blob/main/lint.sh#L40-L47

@peterbrightwell, we need to get @AMWA-TV/nmos-architecture-review up to speed with the scripts so we're not the blockers for this!


Improve CycleOrmBootloader bindings

Made the EntityManagerInterface a singleton, so that the persist and run operations could be called independently of each other and the operations on the entity were performed. Also, instead of clearing the heap with ORMInterface, did it using the EntityManagerInterface::clean method.
But I find it a bit strange that the EntityManager has an argument $cleanHeap in the clean method that is not in the EntityManagerInterface. IMHO, it should not be in EntityManager at all, so both heap and entity manager should be called in the finalizer as follows:
$finalizer->addFinalizer(
    static function () use ($container): void {
       if ($container->hasInstance(EntityManagerInterface::class)) {
           $container->get(EntityManagerInterface::class)->clean();
       }

       if ($container->hasInstance(ORMInterface::class)) {
           $container->get(ORMInterface::class)->getHeap()->clean();
       }
});

And EntityManager should only create a new UnitOfWork instance:
public function clean(): static
{
      $this->unitOfWork = new UnitOfWork($this->orm);

      return $this;
}

@butschster, Hi. I fixed it.

@butschster, Hi. I fixed it.

Thank you! You are the best!

Can you add the second test please with EM mock?

bindSingleton(EntityManagerInterface::class => mock(EntityManagerInterface::class))
run $this->getContainer()->get(FinalizerInterface::class)->finalize();
check the method clean has been called


New version: AmN.yasb version 1.2.4

Pull request has been created with WinGet Releaser :rocket:
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


nothing is selected?

Hey! Any idea why nothing is selected as the "Page"? Should node:page work?

Yes, it's because you don't have an intermediary node called page.
Instead of node:page, try setting it to node:QQ-DATE

It works!
Why can't I set only "QQ-DATE" ?

That was the only one you defined. node:PARENT would return you the block represented by PARENT


Forget user feature missing

According to the official MaierLite Api documentation, they provide an endpoint to remove the subscriber from your account and all information will be completly deleted after 30 days too. However this package doesn't implement this call.
Please implement this feature.
https://developers.mailerlite.com/docs/subscribers.html#forget-a-subscriber

Forget the user endpoint released in v.1.1.0


Screen_view event sent in via POST doesn't appear to have the correct data structure

I can see a screen_view event sent in on the 18th structured as follows:
{
    "schema": "iglu:com.snowplowanalytics.snowplow/payload_data/jsonschema/1-0-0",
    "data": [
        {
            "schema": "iglu:com.snowplowanalytics.snowplow/unstruct_event/jsonschema/1-0-0",
            "tz": "Etc/UTC-2:00",
            "e": "ue",
            "tna": "AF003",
            "co": "{\"schema\":\"iglu:com.snowplowanalytics.snowplow/contexts/jsonschema/1-0-0\",\"data\":[{\"schema\":\"iglu:com.snowplowanalytics.snowplow/link_click/jsonschema/1-0-1\",\"data\":{\"targetUrl\":\"http://www.google.com\"}},{\"schema\":\"iglu:com.snowplowanalytics.snowplow/flash_context/jsonschema/1-0-0\",\"data\":{\"hasLocalStorage\":true,\"stageSize\":{\"height\":893,\"width\":1131},\"version\":\"WIN 11,1,102,63\",\"isDebugger\":true,\"playerType\":\"ActiveX\",\"hasScriptAccess\":true}}]}",
            "dtm": "1421582630549",
            "tv": "as3-0.1.0",
            "data": {
                "schema": "iglu:com.snowplowanalytics.snowplow/screen_view/jsonschema/1-0-0",
                "data": {
                    "id": "screen_1"
                }
            },
            "vp": "320x480",
            "aid": "cloudfront",
            "p": "pc",
            "eid": "91330203-7ef9-02ad-715d-66239902f5b9"
        }
    ]
}

There are several problems with this:

The screen view event is sent in on the wrong parameter - it is sent in on data instead of ue_px or ue_pr (depending on whether it is URI or base64 encoded respectively)
The unstruct_event schema (iglu:com.snowplowanalytics.snowplow/unstruct_event/jsonschema/1-0-0) should be sent in as the first field in the ue_px or ue_pr object referenced above
The entire block inside ue_px or ue_pr is not a JSON - it's a stringified JSON with either base64 or uri encoding
Note that the screen_view schema must live inside the unstruct_event, as illustrated below

[payload data
  [ue_pr|x
    [unstruct_event
      [screen_view

Hope that makes sense - please can you ping @alexanderdean if any of the above is unclear?
Thanks!

fixed in commit 2a97729d6f76d8f761ba8a18c40f5ec7d42eaa14


Try to fix docs build error

Blindly from https://github.com/executablebooks/jupyter-book/issues/1964

Codecov Report

Merging #135 (97cc460) into main (1d6414a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #135   +/-   ##
=======================================
  Coverage   81.69%   81.69%
=======================================
  Files          31       31
  Lines        1677     1677
=======================================
  Hits         1370     1370
  Misses        307      307


RuntimeErrors: No executable batch size found, reached zero. & CUDA out of memory

I’ve gotten this error — RuntimeError: No executable batch size found, reached zero. — running on both an AWS EC2 g5.2xlarge instance with CUDA 11.8, and a HuggingFace Nvidia A10G - small space with CUDA 11.3. I’ve tried bitsandbytes versions 0.37.2, 0.38.1, and 0.39.0. This happens with the 8-bit versions of the AdamW and Lion (v >= 0.38.0) optimizers. The trainer tries to auto-find the batch size, but it keeps cutting the batch size in half until it falls below one. Thanks for any help you can provide!
Below is the traceback and bug report for a run on a HuggingFace space.
Traceback (most recent call last):
File "/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 565, in _run_script
exec(code, module.dict)
File "/home/user/app/app.py", line 61, in
main()
File "/home/user/app/app.py", line 56, in main
app(session_state)
File "/home/user/app/src/application/app_fine_tune_flan_t5.py", line 107, in app
trainer.train()
File "/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/transformers/trainer.py", line 1664, in train
return inner_training_loop(
File "/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/accelerate/utils/memory.py", line 122, in decorator
raise RuntimeError("No executable batch size found, reached zero.")
RuntimeError: No executable batch size found, reached zero.
===================================BUG REPORT===================================
Welcome to bitsandbytes. For bug reports, please run
python -m bitsandbytes
and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
bin /home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/libbitsandbytes_cuda113.so
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/usr/local/nvidia/lib'), PosixPath('/usr/local/nvidia/lib64')}
warn(msg)
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: /usr/local/nvidia/lib:/usr/local/nvidia/lib64 did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] as expected! Searching further paths...
warn(msg)
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('chriswmurphy/llm-lion-finetuning')}
warn(msg)
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('Europe/Paris')}
warn(msg)
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('https'), PosixPath('//chriswmurphy-llm-lion-finetuning.hf.space')}
warn(msg)
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/usr/lib/pyenv/hooks'), PosixPath('/etc/pyenv.d'), PosixPath('/usr/local/etc/pyenv.d')}
warn(msg)
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//<IP_ADDRESS>'), PosixPath('tcp'), PosixPath('443')}
warn(msg)
CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths...
CUDA SETUP: CUDA runtime path found: /usr/local/cuda/lib64/libcudart.so
CUDA SETUP: Highest compute capability among GPUs detected: 8.6
CUDA SETUP: Detected CUDA version 113
CUDA SETUP: Loading binary /home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/libbitsandbytes_cuda113.so...
/home/user/.pyenv/versions/3.9.16/lib/python3.9/site-packages/bitsandbytes/cuda_setup/main.py:149: UserWarning: Found duplicate ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] files: {PosixPath('/usr/local/cuda/lib64/libcudart.so'), PosixPath('/usr/local/cuda/lib64/libcudart.so.11.0')}.. We'll flip a coin and try one of these, in order to fail forward.
Either way, this might cause trouble in the future:
If you get CUDA error: invalid device function errors, the above might be the cause and the solution is to make sure only one ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] in the paths that we search based on your env.
warn(msg)

Update: If I explictly set the batch size, instead of using auto_find_batch_size, it works as expected. As a practical matter, this resolves my issue. On the other hand, if someone needs to auto-find the batch size, they would still face this issue.

The above update was for AdamW8bit optimizer from bitsandbytes==0.37.1.
When I instead use the Lion8bit optimizer from bitsandbytes==0.38.1 I get the dreaded RuntimeError: CUDA out of memory exception. The strange thing is training successfully runs to completion. The runtime error is thrown when I tried to push the model to Huggingface hub.
I then tried setting os.environ["PYTORCH_CUDA_ALLOC_CONF"] = "max_split_size_mb:256, garbage_collection_threshold:0.95" and I ran torch.cuda.empty_cache() after training but before pushing to the hub only to receive the same error (with slightly different numeric values).
app({"optim_name": args.optim_name, "model_size": args.model_size, "n_epochs": args.n_epochs, "limit_samples": args.limit_samples})
File "/home/ec2-user/llm-lion-finetuning/src/application/app_fine_tune_flan_t5.py", line 119, in app
trainer.model.push_to_hub(output_dir)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/transformers/utils/hub.py", line 781, in push_to_hub
self.save_pretrained(work_dir, max_shard_size=max_shard_size)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/peft/peft_model.py", line 102, in save_pretrained
output_state_dict = get_peft_model_state_dict(self, kwargs.get("state_dict", None))
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/peft/utils/save_and_load.py", line 31, in get_peft_model_state_dict
state_dict = model.state_dict()
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1818, in state_dict
module.state_dict(destination=destination, prefix=prefix + name + '.', keep_vars=keep_vars)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1818, in state_dict
module.state_dict(destination=destination, prefix=prefix + name + '.', keep_vars=keep_vars)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1818, in state_dict
module.state_dict(destination=destination, prefix=prefix + name + '.', keep_vars=keep_vars)
[Previous line repeated 6 more times]
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1815, in state_dict
self._save_to_state_dict(destination, prefix, keep_vars)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bitsandbytes/nn/modules.py", line 268, in _save_to_state_dict
self.weight.data = undo_layout(self.state.CxB, self.state.tile_indices)
File "/opt/conda/envs/pytorch/lib/python3.10/site-packages/bitsandbytes/autograd/_functions.py", line 96, in undo_layout
outputs = torch.empty_like(tensor)  # note: not using .index_copy because it was slower on cuda
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 40.00 MiB (GPU 0; 22.19 GiB total capacity; 20.60 GiB already allocated; 14.50 MiB free; 21.11 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

I believe this issue was ultimately the same as #324, which I just saw was fixed, so I'm closing this issue.


update everything to get it to run almost everything.

Mostly appending to @EverybodyKurts great update
update everything to get it to run almost everything.
things known not to be working:

generator has an issue parsing some element, print a warning and return some default value for now instead of failing the build
broken API due to plotly updates:
** marker.size is broken (need to see what is going on with the code gen and learn about plotly source API)
** line.dash has changed
** yaxis.automargin has changed
** aaxis.showticklabels has changed

Hey @smoothdeveloper, thanks for this update and my apologies for not getting back to you sooner. I've merged in the pull request, but I removed the FSharpLint package and changed the dotnet version in global.json to version 8. I did this because FSharpLint doesn't support net8.0 and the fake runner only supports 6.0 for some reason.


Fix -h and --help for the ps program

There was an issue with the call to dogetopt where the help
option expected an argument, of course, this isn't the case.

test failure seems unrelated, merging anyway so we can release


Proposed task in worst_case.py

Task Description
This task evaluates a set of metrics, mostly related to worst-class performance, as described in
(J. Bitterwolf et al., "Classifiers Should Do Well Even on Their Worst Classes", https://openreview.net/forum?id=QxIXCVYJ2WP).
It is motivated by
(R. Balestriero et al., "The Effects of Regularization and Data Augmentation are Class Dependent", https://arxiv.org/abs/2204.03632)
where the authors note that using only accuracy as a metric is not enough to evaluate
the performance of the classifier, as it must not be the same on all classes/groups.
How to start
run
python examples/worst_case.py --imagenet_val_folder '/scratch/datasets/imagenet/val' --verbose --labels_type 'val'

for evaluating with original labels, and
python examples/worst_case.py --imagenet_val_folder '/scratch/datasets/imagenet/val' --verbose --labels_type 'val_clean'

for evaluating with cleaned ones from (C. Northcutt et al., "Pervasive Label Errors in Test Sets Destabilize Machine Learning Benchmarks", https://arxiv.org/abs/2103.14749, https://github.com/cleanlab/label-errors)
Dataset Creation
No dataset has been created.
Evaluation Metrics
The evaluation metrics are "A", "WCA", "WCP", "WSupCA", "WSupCR",  "W10CR", "W100CR", "W2CA", "WCAat5", "W10CRat5", "W100CRat5", and their relevance is described in (J. Bitterwolf et al., "Classifiers Should Do Well Even on Their Worst Classes", https://openreview.net/forum?id=QxIXCVYJ2WP).
Expected Insights/Relevance
To see the, how the model performs on its worst classes. The application examples are given in (J. Bitterwolf et al., "Classifiers Should Do Well Even on Their Worst Classes", https://openreview.net/forum?id=QxIXCVYJ2WP).
Access
Data
No dataset has been added.
License
No dataset has beed created.

Hi!
This is an automated report for the documentation coverage of your PR. To provide good user experience for the benchmark, we aim to cover most functions with doc strings, using the Google docstring format.
We would greatly appreciate your help in assuring that docstring coverage is sufficiently high for your contribution.
The current coverage is:

Name
Total
Miss
Cover
Cover%

examples/worst_case.py
23
22
1
4%

shifthappens/models/torchvision.py
4
0
4
100%

--------------------------------------
---------
--------
---------
----------

TOTAL
27
22
5
18.5%

RESULT: FAILED (minimum: 80.0%, actual: 18.5%)

You can reproduce this result by running
interrogate -v --ignore-nested-functions --ignore-private --ignore-semiprivate --ignore-init-method

on the files you added to your PR.


Add border for teams field in GUI

Codecov Report

Merging #74 (ab5d739) into master (e0163d8) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #74      +/-   ##
============================================
- Coverage     72.52%   72.47%   -0.05%
  Complexity      505      505
============================================
  Files            83       83
  Lines          1565     1566       +1
  Branches        169      169
============================================
  Hits           1135     1135
- Misses          375      376       +1
  Partials         55       55

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)

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 e0163d8...ab5d739. Read the comment docs.


Server crash after extensive logging on and off

Had a trolling user that kept logging on and off with different IP's and me trying to ban every IP he used.
The server started behaving strangely after a while.
Usernames kept changing sporadically or disappeared all together, leaving only the icons in the userlist.
When this happend, the following lines appeared in the log file, shortly before I got disconnected and I couldn't make a new connection without restarting Mobius:

2023-03-15T12:31:02.082+0100    error   error sending transaction       {"err": "write tcp my.internal.ip:5500-><IP_ADDRESS>:65082: use of closed network connection"}
2023-03-15T12:31:02.082+0100    error   PANIC   {"err": "runtime error: invalid memory address or nil pointer dereference", "trace": "goroutine 88535 [running]:\nruntime/debug.Stack()\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x65\ngithub.com/jhalter/mobius/hotline.dontPanic(0xc0000be2a0?)\n\t/home/circleci/project/hotline/panic.go:13 +0xb2\npanic({0x7bfb00, 0xb0f9d0})\n\t/usr/local/go/src/runtime/panic.go:890 +0x262\ngithub.com/jhalter/mobius/hotline.(*ClientConn).String(0xc00011c0e0)\n\t/home/circleci/project/hotline/client_conn.go:247 +0x495\ngithub.com/jhalter/mobius/hotline.HandleGetClientInfoText(0xc0000be2a0, 0xc0003300c0)\n\t/home/circleci/project/hotline/transaction_handlers.go:923 +0x456\ngithub.com/jhalter/mobius/hotline.(*ClientConn).handleTransaction(0xc0000be2a0, {0x0, 0x0, 0x0, {0xc0002fa322, 0x2, 0x1a}, {0xc0002fa324, 0x4, 0x18}, ...})\n\t/home/circleci/project/hotline/client_conn.go:82 +0xae3\ngithub.com/jhalter/mobius/hotline.(*Server).handleNewConnection(0xc000388ff0, {0x2?, 0x2?}, {0x7f3ebc7717d8, 0xc000090000}, {0xc00001c078, 0x15})\n\t/home/circleci/project/hotline/server.go:708 +0x2ae5\ngithub.com/jhalter/mobius/hotline.(*Server).Serve.func1()\n\t/home/circleci/project/hotline/server.go:197 +0x1ba\ncreated by github.com/jhalter/mobius/hotline.(*Server).Serve\n\t/home/circleci/project/hotline/server.go:193 +0x98\n"}

The issue seem to happen when you try to interact with a user that logged on without a nickname (just an icon in the userlist, no nickname specified). Try to get the users info or try to write a chat to the user.

This was someone who was banned on our Discord server and noticed he could "get through" to Discord using Hotline. When I shut down the Discord integration temporarily he started abusing the Hotline server instead. Some people are just... people.
Well, he or she triggered the bug in Mobius (or whatever it is), so I guess theres some kind of silver lining at least ;)

I've made a change in v0.10.18 to disconnect banned users earlier in the connection flow.  I think this should fix this issue.

Thanks for the quick fix, Jeff! :-)


Implement Texera User Avatars Featuer

This PR creates an Angular component to show the avatar of a Texera user.
The library/component ngx-avatar does not support retrieving Google users' avatars by Google ID (https://github.com/HaithemMosbahi/ngx-avatar/issues/51), so I implemented the logic to retrieve Google users' avatars myself in the component.
In order to send requests to Google People API, a public key is needed to provide.
Creating a Google API Public Key is easy, please follow this instruction.
https://developers.google.com/maps/documentation/maps-static/get-api-key
Then fill the public key in the environment.default.ts
google: {     clientID: "",     publicKey: "",   },
Demo:
If the user is a normal Texera user, the avatar will be the default avatar with a random background color.

If the user is a Google user, the avatar will be its Google profile picture.

Group discussion 1/11: @Yicong-Huang will merge this PR soon


How to handle interruptions (e.g. phone calls)?

Jukebox is a nice player, but when a phone call comes in, the player stops playing (as it should), but when the call ends, the player does not regain audio control...

Thanks for pointing this thing out! Will investigate and then come back to you.

Is there is any update for this issue.
Thanks for the demo.

I fixed that in my fork and created a pull request

@buddax2 The pull request you submitted has still a problem. For example a song is paused now, and an interruption occurs, after the interruption is ended, paused song starts playing!!
I can suggest 2 solutions:

Keep a previous player state: paused, palying and when interuption ends, restore player to same state
when pausing or stopping the song, remove observers and when playing, add them again.

@RajChanchal can you elaborate more on those 2 solutions ? I have the same problem: when a song is paused and an interruption occurs, the song plays again. I didn't understand what should I do. Thanks in advance

@SergeHaddad , I have used the second solution of mine. You can use my code: https://github.com/RajChanchal/Jukebox


Alpine Linux on Scaleway ARM64 VPS (ARMv8 SSD Cloud Servers)

Hello,
Does someone can tell me why Scaleway do not provide Alpine Linux on their ARMv8 SSD Cloud Servers ?
Is it because it does not work ?
Can i install it by himself ?
I would really like to use Alpine Linux on Scaleway ARMv8 servers because i use it on C1 and all X86 variants.
Bests regards, Olivier.

ARMv8 has architecture named "aarch64"


Using PixelFed reports 500 server error

Just passing along. Holler if I can help debug. Thanks!
Ray
GET https://granary.io/pixelfed/267478200693690368/@all/@app/?format=atom&access_token=...&user_id=267478200693690368&instance=https://pixelfed.social/
500 Internal Server Error
The server has either erred or is incapable of performing the requested operation.

Ugh, thanks for filing! Fixed.


Add GetProjectLanguages to get languages from a project

Implements the languages project API https://docs.gitlab.com/ce/api/projects.html#languages
Small detail:

Defines ProjectLanguages as map of string interfaces because the response is not structured and will have a list of languages with percentage.

Includes an example

I made the changes that you suggested, thanks for the input, is much better now

LGTM! Thanks @topochan!


[QA] Deleting unnecessary box

Is there any way to delete my unused boxes from the host?

No. Usually, it isn’t necessary. If you’re no long interested in a newsletter, as a courtesy you may unsubscribe from it with the usual means (probably clicking on a link in one of the newsletter entries). Or you may just unsubscribe from the Atom feed on your feed reader.


Created Rudimentary EXE Compiler

Happy Hacktoberfest!

Happy Hcktoberfest! Thank you for you contribution and sorry for missing your previous comment on #33   :s I'll test this PR in the following couple days (as soon as I spin up a windows vm :p )

Yeah, and as far as I can see, it's really hard to compile a windows application from a linux platform (which I feel your pain, but I have a dual boot system).  Maybe there is a way around this, though.  What if we were to compile a single executable as a release, and then integrate the addition of something like serialized plugins to customize the payload?  That way you wouldn't have to recompile every time. P.s. great project, good code, look forward to many contributions

Hmmm that sounds like a very good idea :) Command addition through plug-ins is already implemented on v0.4.0_rc so once that is merged into master it should be more or less straight forward.
Even if this doesn't work out well though it's not such a blow to require the user to compile on Windows, I just noted it to excuse the fact that it'll be a couple days before I can test and merge :p
Nevertheless I'll have to make my self a windows env to test RSPET on (and to build the release executables) and I've been putting it off for a while so ... it's time to do it.
Looking forward to future contributions :)


Allow manifest.json to be generated without fingerprint

if added to exclude list

See #38 for discussion.

Could you please add a test for this?

I tried adding a test but ran into difficulties because the manifest includes mtime for fingerprinted assets. Consequently the content and fingerprinted filename are different each test run.
If you have a suggestion as to how I can work around this please let me know.

Hmm, maybe you can just check the filepath and not assert that its contents are the same?

Added a test that only asserts the correct paths exist.
While all tests pass on my machine, the Travis build is failing. Not sure if it's legit (failing with Could not find .travis.yml, using standard configuration.).

Apologies about the delay. Could you rebase and then I will merge?

No worries. Rebased.

Thanks!


docs: Note that ATLAS PUB Note on simplified likelihoods is public

* Update README to include public link to Implementation of simplified likelihoods in HistFactory for searches for supersymmetry (ATL-PHYS-PUB-2021-038)
   - c.f. https://cds.cern.ch/record/2782654
* Change `sh` syntax highlighting to `console` to get better command line agreement
* Fix typos

Codecov Report

Merging #18 (44d772e) into master (a534210) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #18   +/-   ##
=======================================
  Coverage   94.60%   94.60%
=======================================
  Files           7        7
  Lines         482      482
  Branches       82       82
=======================================
  Hits          456      456
  Misses         23       23
  Partials        3        3

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 a534210...44d772e. Read the comment docs.


Component for  top-navbar

This will contain the logo component and the navbar buttons component

ESTIMATED 8 hours
REALIZED  12 hours


merge package template from Kronos-Tools/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

Coverage remained the same at 78.571% when pulling a6602b5cec76b948a27720ac3da562a7b409105f on template-sync-1 into bcf3d349b982a36e614076718bfbf182cd9f5e0b on master.

Codecov Report

Merging #113 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #113   +/-   ##
=======================================
  Coverage   83.33%   83.33%
=======================================
  Files           1        1
  Lines          12       12
=======================================
  Hits           10       10
  Misses          2        2

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 bcf3d34...a6602b5. Read the comment docs.


fix: oca branding fixes

Summary of Changes
This PR:
Commit 1- Add the shadow and the black text color inside the default icon:
Before:

Now:

Commit 2- Add the translation of the issuerName in the credentialDetails screen.
Commit 3- Put the default logo in the same order as the credentialCard11 (Name and after issuerName), so that the same letter is displayed.
Before ( with the same credential as the previous pictures, but in the credentialDetails screen):

Related Issues
N/A
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

Good changes, once it's up to date with the base branch I will approve 👍

@jcdrouin21 Able to resolve conflicts so we can merge this?


Rename "Nipst" as "NIPoST" throughout the codebase and docs

Overview / Motivation
As discussed and agreed with Tal Moran from here on "Nipst" will be forever changed to "NIPoST".
The Task
Rename "Nipst" as "NIPoST" throughout the codebase and docs.

Closed by https://github.com/spacemeshos/go-spacemesh/pull/2149.


Auto withdrawal to lightning address is failing

Description
My SN wallet is above the limit I have set. Went to the attach wallet config page for it and I see many log messages like this.
13m	[lnAddr]	error	creating invoice for SN: autowithdrawal failed: Error: invoice has incorrect amount
My wallet is a lightning address type of wallet. This seems to have started about 19 hours ago.
Steps to Reproduce
Set up an Alby wallet with lightning address and set your wallet limit. Now receive sats above the limit.
Expected behavior

I changed that code as part of the release. Thanks for making an issue!

Looks like even though the spec requires specifying amounts in msats, most implementations want the amount round to the nearest sat.

Ah! That error makes sense then. Maybe this should be reported to Alby

Looks like a lot of lightning providers don't like msats though. Natalia reported hers as:
creating invoice for SN: autowithdrawal failed: Error: Millisatoshi amount is not supported, please send a value in full sats.
Ahrg, without this changing, it means for p2p zaps the receiver can't receive all the millisats they're owed.

p2p zaps lightning address receivers can't receive all the millisats they're owed.

We so early  ™

I reached out to Alby

Looks like a lot of lightning address providers don't like msats though

@bumi from Alby also mentioned this. Looks like we also have to round our number or risk invoices over LNURL failing. Or we could catch this error, round down and retry so this only affects users with such LNURL providers. Ideally, we would let the user know that their LNURL provider does not support msats so they might receive receive a little less than possible of each zap.

The problem is that for p2p we assume the invoice hasn’t been rounded to compute what the zapper will pay, eg ‘inv.msats * 10 / 9’. I was going to try to get fancy with math but it’s probably better to just be explicit about forward amounts and what the zapper will pay when doing p2p.
Also its weird to hear “the spec is what we implemented not what it says” over and over.
At the very least, providers should not be rounding what’s requested. It’s like someone orders an apple and you give the customer an orange painted red.


this is window instead of Lightning.Component

I've implemented a kind of logic of repetitive update in a particular state of a component:
$enter() {
	this.interval = setInterval(this.sync, 1000);
}

This is the handler:
async sync() {
    const players = new Players(); // TODO ragionare
    await players.get(); // this update players from REST API
    // here (this == window) somethimes.
    this.players = players;
}

The problem is that this setter now not working. It works if I call from for example _init but not from the callback of setInterval because this in this case is window instead of the component itself.
set players(players = new Array()) {
    this.tag('Game').players = players;
    this.tag('ScoreBoard').players = players;
}

I've to bind the callback?
There are other patterns?
Best regards
Mattia

This is not really a Lightning related question or issue, but you forgot to bind the scope, so this in your sync method wil point to window
this.interval = setInterval(this.sync.bind(this), 1000);
Will fix your issue

@erikhaandrikman this indeed fixes my issue.
Anyway, after some work, I'm focused on prevent to define methods that are not to be exposed to parent so the scopes in the official methods are working good.
Thanks for the support.
Mattia


Replace rusoto with aws-sdk-rust

We should replace the unmaintained rusoto crates with the official and actively maintained aws-sdk-rust.
References:

#2190
RUSTSEC-2022-0071

cc @prestwich @gakonst

agree. this will technically be a break change due to the ability to pass in a client

i looked at this, and i am on the fence. the aws sdk is still in preview, and is not recommended for prod. Absent a stable thing to update to, I'm not sure we should move off the thing that is currently working

@prestwich rusoto is abandonware and has been so for more than a year. We do in fact need to switch.

running into this quite consistently with the aws kms signer https://github.com/rusoto/rusoto/issues/1686


Balance druid

Profile gets stuck at pooling for Starsurge, won't cast anything while waiting.
@Zurc in the discord channel.

Will look into it.
Pooling = Waiting for resources, because there's nothing else to do atm (according to the CR)
So if you have any idea what it should rather be doing at that moment, post it here, so i can try tweaking the CR.

Still an issue?

Sorry for the late reply. The update you released straight after fixed the problem.


need to do checks for count matrix

@TomVuod please insert a check to make sure that count matrix is in dgCMatrix

The issue has been addressed by commit eca043c. Assay matrices are now coerced to sparseMatrix.


Joystick

the link of the joysticks in README.md is corrupt. Where can i found the joyticks you used ?

Thanks fixed. Seller probably removed the item, changed to search result instead.


glib: Remove #[doc(hidden)] from once_cell and bitflags re-export

The blogpost1 mentions that these are re-exported, so to avoid causing confusion, make it so these appear in documentation.

Alternatives:

do nothing
remove the note about the two crates being re-exported from the blogpost

Even if I am looking forward to Lazy being in the std so we can fully drop the once_cell usage.

Yeah that's something I'm looking forward for my personal projects as well


Add support for Swift Package Manager in Xcode 11

Could you please add support for SPM in Xcode 11? Currently Xcode gives the error 'has no Package.swift manifest for version 1.4.2' when adding the package to the Xcode project.

Hasn't been fixed.


Support KRM input

Kubeconform could be used as a validator plugin in Kustomize (it's built into kubectl since v1.14)
All needed is just support KRM as input to Kubeconform.
I will create a PR for you if the feature is accepted.

Can you describe the implementation you have in mind? It would need a new flag to specify that the stdin input is in a different format, and a new output format to output the resource again? I m not against it in principle but i feel this might be non trivial to implement? Could you describe how this could work? Thanks! ❤

Hi Yann :wave:
I'm thinking in a simpler impelmentation where Kubeconform will detect the type of STDIN, and if it's ResourceList, it will process the values of the items key as files.
I already did something similar for SopsSecretGenerator
apiVersion: config.kubernetes.io/v1
kind: ResourceList
metadata:
  name: krm-function-input
items:
- apiVersion: goabout.com/v1beta1
  kind: SopsSecretGenerator
  metadata:
    annotations:
      config.kubernetes.io/function: |
        exec:
          path: SopsSecretGenerator
      config.kubernetes.io/local-config: 'true'
      config.k8s.io/id: '1'
    name: secret-from-file
  disableNameSuffixHash: true
  files:
    - testdata/file.txt
- apiVersion: goabout.com/v1beta1
  kind: SopsSecretGenerator
  metadata:
    annotations:
      config.kubernetes.io/function: |
        exec:
          path: SopsSecretGenerator
      config.kubernetes.io/local-config: 'true'
      config.k8s.io/id: '2'
    name: secret-from-env
  disableNameSuffixHash: true
  envs:
    - testdata/vars.env

If you think you can do this with reasonable effort maybe give it a shot... maybe push early, before writing tests, so I can review the implementation?

@yannh here is the PoC #170
Just 1 method that parses the Stdin content.


More things that can be removed now that jsdom supports them

From https://github.com/facebook/jest/blob/master/src/JSDomEnvironment.js;

The array buffer / typed array copies
The window.Image shim
Maybe the comment-out of window.close

Thanks for the list @domenic. On it.

fingers crossed for the segfault issue.

Seems like Buffer itself isn't part of jsdom. Would you be ok with me sending a PR to jsdom to add it? What about DataView (although I'm not sure any tests at FB depend on this). process should probably not be part of JSDomEnvironment – I'm planning to add other environments for this use case.

Buffer is not part of the web; like process, it's a Node-only thing. So nah, not going in jsdom.
DataView should be in jsdom already. I guess I have to expand my mental phrasebook from "array buffer / typed arrays" to "array buffer / DataView / typed arrays", haha.

yep, makes sense. Thought we had a buffer implementation on the web for some reason ;)

Done in e5484b0eaea9310c9c46859d368953026c791401 and bd1f22b7996725764fd41204f6c92be12f5f3987


Unlimited bandwith

Switch to Cloudflare Pages they have unlimited bandwith for free

Hi @catdroutcode , thanks a lot for the suggestion. I'll take a look at that! At the moment I'm on Netlify as hosting solution and I don't have an high bandwidth usage.
Usually the issue is with Cloudinary, since sometimes happen that websites with high bandwidth usage are pointing to images hosted by my Cloudinary account.

You could code a cloudflare workers to handle images with Workers KV

👍


Setup arca environment for hog scenarios in prow

Trying to fix issues in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/41204/rehearse-41204-periodic-ci-redhat-chaos-krkn-hub-main-krkn-hub-tests/1680747205616472064.


How can I archive ALL files from within cwd?

Hello,
First, thanks for writing this action.
I tried running it with the following settings:
- name: Compress build to TAR archive
  uses<EMAIL_ADDRESS>  with:
    command: c
    cwd: ./site
    files: "**/*.*"
    outPath: site.tar.gz

Unfortunately, glob patterns don't seem to be supported.
I have also tried not providing the files argument, hoping maybe it would just assume it must archive everything, but as stated in documentation, it is a required argument and therefore it doesn't work.
Is there an easy way to tell the action to archive all files and directories within the current working directory? At this point the only other way I can think of is running a find . -type f command prior to the action and set the result into an array variable. I'm not sure how to do that with GitHub Actions - or if it can be done at all.
Any insight would help a lot.

Any answer on this?


No match found.

the code that reproduces this issue or a replay of the bug
No match found. Progress images have been disabled. Don't worry, the results will still be sent when it completes.
error log，why？Normal prompt
Describe the bug

error log
Doubt is a matter of regularity


[Feature Request] Provide "Stop" button in run overview in Azure Portal

Is your feature request related to a problem? Please describe.
Make it simpler to stop a test run
Describe the solution you'd like
I'd love to have a "Stop" button here in the portal:

Describe alternatives you've considered
N/A
Additional context
You can go to the test run details and stop it there, but doing bulk stops makes this approach a bit of a pain.
AB#1664068

@tomkerkhove Thank you for the suggestion. We will explore on ways to improve this experience.


[Dev] Database improvements

Assigning various objects and string values a numeric ID would allow shrinking a lot of code, as well as create relations between data more easily, with little overhead in the code.

Players [UUID as ID]
Dimensions [Int, autoincrement]
Blocks [Int/Long, autoincement]

Additionally, we should look into creating (de)serializers for common data like Vec2/Vec3 classes. If this is not possible through Exposed, a compact way to serialize these should be considered.
Finally, we should look at what SQL solutions to support. Currently we support:

SQLite
PostgreSQL
MySQL

As of 6b246d4 database transactions are now handled on their own thread, returning CompletableFutures instead.


Issue/3192 pydantic anyurl doc rendering

Description
Fixing formating of AnyUrl types in the documentation (openapi and swagger).
closes #3192 and inmanta/inmanta-lsm#451
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

@edvgui I removed myself as reviewer because I really do not know the code. Can you explain why you changed the elif to if? This is equivalent but it seems unnecessary to make this change. Unless I am missing something.

@edvgui I removed myself as reviewer because I really do not know the code. Can you explain why you changed the elif to if? This is equivalent but it seems unnecessary to make this change. Unless I am missing something.

I think it looks better/cleaner/lighter, but this is definitely not worth fighting over.  I changed it back.

Processing this pull request

Failed to merge changes into iso4 due to merge conflict.Please open a pull request for these branches separately.

Merged into branches master in 3bd93bc25fdd017b6e63da43534a244d4b14babc

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches. You can safely close this pull request and delete the source branch.


Fixing table namespacing

Coverage increased (+1.6%) to 96.751% when pulling 765f83e0dfa1fc0349a90627da06365f4f7d5804 on alexperto:table-namespace-issue into 11927dace4f7ec9081360d85e5944279221d8b25 on Dynamoid:master.

Coverage increased (+1.8%) to 96.911% when pulling 063b9cb1a255e39559c0182ab8b9d3a125aa6642 on alexperto:table-namespace-issue into 11927dace4f7ec9081360d85e5944279221d8b25 on Dynamoid:master.


Add Flask instance folder

Contains private configuration. Equivalent to Django's local_settings.py.

Relevant docs: http://flask.pocoo.org/docs/0.10/config/#instance-folders

The instance folder is designed to not be under version control and be deployment specific. It’s the perfect place to drop things that either change at runtime or configuration files.

Thanks @Harrison-G!


Update get_started.md

This updates the get_started section to include a small blurb about newer version of npm that use --location=global as opposed to install -g

+1 I don't see other projects updating their instructions yet.
(I hope NPM simply messed up. Removing --global would be a highly disruptive change with no obvious benefit.)

Going to close this PR for now, we can reopen if there's new developments.


Auto Generate Document translator SDK

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.Translator.Document

/azp run

/azp run net - translation - ci


SEPATAROR in graph_chunk_entity_relation.graphml

Hi All,
In the graph_chunk_entity_relation.graphml file, where there are multiple keywords or chunks, those entries are separated by  delimiter. See example below.

<node id="COOLEY">
  <data key="d0">ORGANIZATION</data>
  <data key="d1">Law firm involved in the proceedings**<SEP>**Law firm representing Elizabeth Holmes</data>
  <data key="d2">chunk-a10761b4cfd1d1f69165324d9485721f**<SEP>**chunk-5404226401db79d2bc47e1798821aa07</data>
</node>

When I inserted the graph database into Neo4J using the script "graph_visual_with_neo4j.py", those entries are not separated as expected, so I end up with something similar to screenshot blow in Neo4J database.

Is that expected? Should I just fix it in the graph_visual_with_neo4j.py? I wonder if that will impact the Querying portion of LightRag in general.

This issue will indeed affect the visualization process, as the entries are not being separated as expected. However, it should not impact the querying process, since the data is originally stored in the XML file and the content separated by  will be correctly read during queries.


Add very basic payment module

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

What is the new behavior?

Other information

Well done!
However, there are some things related to Git and Github that are missing here.
Github

Before creating a pull request please create an issue first. Thanks to than we can easily track the whole lifecycle of the task (issue -> pull request -> merged -> issue moved to done)
Please add labels, assigned person, and linked issue (for that just type in the description of the PR Closes #number)
Resolve conflicts for this branch. Both for graphql and package.json (do yarn before pushing).

Git

This is a big change so having this all in just one commit is not the best idea. It would be very difficult to scan this feature in the future. Please divide this change into separate commits (in this case I would create at least 20 commits for such a big change)
Because we are using Git submodules in otasoft-core for each change we do in microservices/frontend/api/etc we also need to push that change to otasoft-core repository (we can achieve that by just copy+paste'ing commit from service to core i.e.
git commit -m "feat-#12: add payment controller" // in payment microservice
git commit -m "payment: add payment controller" // in otasoft-core
I will talk about it more during our workshop.

Well done!
However, there are some things related to Git and Github that are missing here.
Github

Before creating a pull request please create an issue first. Thanks to than we can easily track the whole lifecycle of the task (issue -> pull request -> merged -> issue moved to done)
Please add labels, assigned person, and linked issue (for that just type in the description of the PR Closes #number)
Resolve conflicts for this branch. Both for graphql and package.json (do yarn before pushing).

Git

This is a big change so having this all in just one commit is not the best idea. It would be very difficult to scan this feature in the future. Please divide this change into separate commits (in this case I would create at least 20 commits for such a big change)
Because we are using Git submodules in otasoft-core for each change we do in microservices/frontend/api/etc we also need to push that change to otasoft-core repository (we can achieve that by just copy+paste'ing commit from service to core i.e.
git commit -m "feat-#12: add payment controller" // in payment microservice
git commit -m "payment: add payment controller" // in otasoft-core
I will talk about it more during our workshop.


Project Restructure - The Seperation

The Project is Seperated into 3 Projects and has 1 Common Directory

Hurl.BrowserSelector
Hurl.Settings
Hurl.SharedLibraries

Extra

InnoSetup - now adds shortcuts in the Start Menu
Update README

Just testing hacktoberfest-accepted label....😂


Mandatory onMouseMove function?

Seems like the function onMouseMove is mandatory because when I don't supply it I get the following error: TypeError: _this4.props.onMouseMove is undefined.
Could be a bug in the implementation or an intended thing. If it is intended, please add this information to the documentation. Also, in this case, I don't think it should be mandatory. I ended up putting () -> undefined at its place.
Version: 0.0.11

This should not be mandatory. I'll have to patch it, but have no time currently. Any PR would be welcome for that.

I've published a new version (v0.0.14) where they should not be mandatory anymore.


Fix e2e test TestPullRequestRemoteAnnotations

We were exit 1 and since now we detect failures of pipelinerun then we
would get screwed :facepalm:
Signed-off-by: Chmouel Boudjnah<EMAIL_ADDRESS>

Codecov Report

Merging #244 (295d575) into main (5f70f86) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #244      +/-   ##
==========================================
+ Coverage   69.04%   69.07%   +0.03%
==========================================
  Files          27       27
  Lines        1615     1630      +15
==========================================
+ Hits         1115     1126      +11
- Misses        399      401       +2
- Partials      101      103       +2

Impacted Files
Coverage Δ

pkg/git/git.go
80.64% <0.00%> (-6.86%)
: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 5f70f86...295d575. Read the comment docs.


add Unique validator

This PR adds Unique validator to validate a fields uniqueness without enforcing a unique constraint at the database level. Consider precedence in Rails validates_uniqueness_of

Thanks for the PR, but this doesn't belong in WTForms, which is database agnostic. This is already present in WTForms-Alchemy. https://wtforms-alchemy.readthedocs.io/en/latest/validators.html#unique-validator

Ah, that makes sense. I didn't know about that package, thanks!