Pass only interface name to syscall.util.if_nametoindex()

The syscall.util.if_nametoindex() only needs to be passed the name of the interface. The version of the function which accepts an open socket as second argument is internal to ljsyscall, and not even exported to client code.
Also, this moves the call to syscall.util.if_nametoindex() to the top of RawSocket:new() to simplify error handling: this way one less explicit call to syscall.close() is needed in case of errors.

Some background on how I got to write this patch: while adding support for running the lwAFTR using TAP interfaces (see Igalia/snabbswitch#236), one of my tests was to use a TAP interface for the B4 side and RawSocket for the Internet side, and it would crash with:
apps/tap/tap.lua:46: Failed read on aftr: Bad file descriptor
stack traceback:
        core/main.lua:122: in function <core/main.lua:120>
        [C]: in function 'error'
        apps/tap/tap.lua:46: in function 'method'
        core/app.lua:76: in function 'with_restart'
        core/app.lua:287: in function 'breathe'
        core/app.lua:241: in function 'main'
        program/lwaftr/run_nohw/run_nohw.lua:112: in function 'run'
        program/lwaftr/lwaftr.lua:17: in function 'run'
        core/main.lua:41: in function <core/main.lua:32>
        [C]: in function 'xpcall'
        core/main.lua:151: in main chunk
        [C]: at 0x004511b0
        [C]: in function 'pcall'
        core/startup.lua:1: in main chunk
        [C]: in function 'require'
        [string "require "core.startup""]:1: in main chunk

Using strace I found out that at the Tap application would be issuing a few hundreds of calls to read(), then close() would be called on the FD, and the next call to read() would cause the above error.
Then I added calls to print(debug.traceback()) inside syscall.close() to better understand from where the calls were coming. During the initialization, in RawSocket:new(), which ends up calling if_nametoindex(), file descriptor 5 gets closed, and then the same number gets assigned to the Tap socket FD, and then after a while a __gc metamethod kicks in and closes the same FD number 5 again, which causes the next read() to fail:
close(5)
stack traceback:
        syscall/syscalls.lua:80: in function 'close'
        syscall/linux/util.lua:50: in function 'if_nametoindex'
        apps/socket/raw.lua:20: in function 'new'
        core/app.lua:165: in function <core/app.lua:162>
        core/app.lua:201: in function 'apply_config_actions'
        core/app.lua:110: in function 'configure'
        program/lwaftr/run_nohw/run_nohw.lua:90: in function 'run'
        program/lwaftr/lwaftr.lua:17: in function 'run'
        core/main.lua:41: in function <core/main.lua:32>
        [C]: in function 'xpcall'
        core/main.lua:151: in main chunk
        [C]: at 0x004511b0
        [C]: in function 'pcall'
        core/startup.lua:1: in main chunk
        [C]: in function 'require'
        [string "require "core.startup""]:1: in main chunk
TAP socket FD: 5
...
close(5)
stack traceback:
        syscall/syscalls.lua:80: in function 'close'
        syscall/methods.lua:145: in function '__gc'
        apps/socket/raw.lua:43: in function 'can_receive'
        apps/socket/raw.lua:37: in function 'method'
        core/app.lua:76: in function 'with_restart'
        core/app.lua:287: in function 'breathe'
        core/app.lua:241: in function 'main'
        program/lwaftr/run_nohw/run_nohw.lua:112: in function 'run'
        program/lwaftr/lwaftr.lua:17: in function 'run'
        core/main.lua:41: in function <core/main.lua:32>
        [C]: in function 'xpcall'
        core/main.lua:151: in main chunk
        [C]: at 0x004511b0
        [C]: in function 'pcall'
        core/startup.lua:1: in main chunk
        [C]: in function 'require'
        [string "require "core.startup""]:1: in main chunk
apps/tap/tap.lua:47: Failed read on aftr: Bad file descriptor
...

That's what led me to look at syscall.util.if_nametoindex() to see how it works and understand why it would cause the file descriptor it used to be GCd later on. There's where I noticed that the function was incorrectly passed an additional argument, and decided to move the call to the beginning of RawSocket:new() to simplify error handling, in an attempt to avoid the file descriptor for the socket being GCd later on.
(Related to this, I have also posted a patch for ljsyscall to immediately close sockets on errors when calling the lower-level implementation of if_nametoindex(), see justincormack/ljsyscall#188.)

@aperezdc Do we need the https://github.com/justincormack/ljsyscall/pull/188 patch for this patch to work?

@eugeneia: This patch is enough by itself to fix the issue.
(The other patch for ljsyscall is not technically needed: it avoids having the file descriptor open waiting for the GC to collect it in case of an error, by explicitly closing it. I made the patch to ljsyscall as a small enhancement while investigating this issue.)

Okay, then I am merging this right away. Great detective work in this PR! I like when there are a lot of references to give context. :-)


[Release 1.13] Stop previous remote cluster when updating secret

fix https://github.com/istio/istio/issues/39389

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio_release-1.13
339d2946bfd0134416b884af35b97ae787291b4d
link
true
/test integ-pilot-multicluster_istio_release-1.13

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-multicluster_istio_release-1.13

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio_release-1.13
339d2946bfd0134416b884af35b97ae787291b4d
link
unknown
/test integ-security_istio_release-1.13

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security_istio_release-1.13


Allow remapping of can_fd topics via launch file

In PR #39, remapping can (but not can_fd) topics via launch file arguments was enabled. This PR also allows the remapping of can_fd topics via launch file arguments while keeping the current default values for both can and can_fd topics.

Not sure why the CI is not initiated.

https://github.com/autowarefoundation/ros2_socketcan/actions/runs/12166396297/job/33932587833?pr=52#step:4:52

Error: fatal: unable to access 'https://github.com/autowarefoundation/ros2_socketcan/': The requested URL returned error: 502

Right now github and its public runners are having some server issues. I will look into the failing CIs tomorrow.


Error: Building package liblzma:x64-windows-static with: BUILD_FAILED

HI, I am not able to build liblzma:x64-windows-static for x64-windows.
PS D:\vcpkg> ./vcpkg install liblzma:x64-windows-static
The following packages will be built and installed:
    liblzma[core]:x64-windows-static
Starting package 1/1: liblzma:x64-windows-static
Building package liblzma[core]:x64-windows-static...
-- Using cached D:/vcpkg/downloads/xz-mirror-xz-v5.2.4.tar.gz
-- Using source at D:/vcpkg/buildtrees/liblzma/src/v5.2.4-66bfe33102
-- Configuring x64-windows-static
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
    Command failed: ninja;-v
    Working Directory: D:/vcpkg/buildtrees/liblzma/x64-windows-static-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      D:\vcpkg\buildtrees\liblzma\config-x64-windows-static-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:273 (vcpkg_execute_required_process)
  ports/liblzma/portfile.cmake:15 (vcpkg_configure_cmake)
  scripts/ports.cmake:71 (include)

Error: Building package liblzma:x64-window
[config-x64-windows-static-out.log](https://github.com/Microsoft/vcpkg/files/3123579/config-x64-windows-static-out.log)
[CMakeError.log](https://github.com/Microsoft/vcpkg/files/3123584/CMakeError.log)
[CMakeOutput.log](https://github.com/Microsoft/vcpkg/files/3123585/CMakeOutput.log)

s-static failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: liblzma:x64-windows-static
  Vcpkg version: 2018.11.23-nohash

Additionally, attach any relevant sections from the log files above.
PS D:\vcpkg>

config-x64-windows-static-out.log
CMakeError.log
CMakeOutput.log

Remarque : I have the same error when installing Boost library  ./vcpkg install boost:x64-Windows-static

This issue is due to the fact that libxml2 cannot linke to the libxslt function:
libxml2.lib(xzlib.c.obj) : error LNK2019: unresolved external symbol lzma_code referenced in function xz_decomp
libxml2.lib(xzlib.c.obj) : error LNK2019: unresolved external symbol lzma_end referenced in function __libxml2_xzclose
libxml2.lib(xzlib.c.obj) : error LNK2019: unresolved external symbol lzma_properties_decode referenced in function is_format_lzma
libxml2.lib(xzlib.c.obj) : error LNK2019: unresolved external symbol lzma_auto_decoder referenced in function xz_head
F:\vcpkg\buildtrees\libxslt\x64-windows-static-rel\bin.msvc\libexslt.dll : fatal error LNK1120: 4 unresolved externals

@LeMoussel, thanks for posting this issue.
Related issue https://github.com/microsoft/vcpkg/issues/5299.
You can workaround this by installing windows sdk by VS, then the rc.exe path will set to
C:\Program Files (x86)\Windows Kits\10\bin\x64\rc.exe
C:\Program Files (x86)\Windows Kits\10\bin\x86\rc.exe
I tried it, it works.

Duplicated to issue https://github.com/microsoft/vcpkg/issues/5299, please reopen it if it still be an issue for you.

It's OK. I I applied the method described by @dankegel in issue #5299
Visual Studio 2015 Command Prompt variables set.
PS D:\vcpkg> ./vcpkg install liblzma:x64-windows-static
The following packages will be built and installed:
    liblzma[core]:x64-windows-static
Starting package 1/1: liblzma:x64-windows-static
Building package liblzma[core]:x64-windows-static...
-- Using cached D:/vcpkg/downloads/xz-mirror-xz-v5.2.4.tar.gz
-- Using source at D:/vcpkg/buildtrees/liblzma/src/v5.2.4-66bfe33102
-- Configuring x64-windows-static
-- Building x64-windows-static-dbg
-- Building x64-windows-static-rel
-- Applying patch D:/vcpkg/ports/liblzma/auto-define-lzma-api-static.patch
-- Performing post-build validation
-- Performing post-build validation done
Building package liblzma[core]:x64-windows-static... done
Installing package liblzma[core]:x64-windows-static...
Installing package liblzma[core]:x64-windows-static... done
Elapsed time for package liblzma:x64-windows-static: 23.91 s

Total elapsed time: 23.91 s

The package liblzma is compatible with built-in CMake targets:

    find_package(LibLZMA REQUIRED)
    target_include_directories(main PRIVATE ${LIBLZMA_INCLUDE_DIRS})
    target_link_libraries(main PRIVATE ${LIBLZMA_LIBRARIES})


Profile Tool: make order consistent between runs

a couple of the results between runs would vary on the order so add more sort columns.
Signed-off-by: Thomas Graves<EMAIL_ADDRESS>

build

build

build


Validate the widget from schema before creating it

Today if we pass a widget as a setter property, we have to blindly take it in as dynamic. When we actually build the widget (later in the build cycle), only then we would figure out if it is a valid widget or gibberish. The proposal here is to validate it at the setter so we can warn the user. We can check at least the following:

is it a valid widget (e.g. "Column" or "Grid" or. ...)
is it a custom widget that the user defined.

done, closing


See quote-posts on a post

Is your feature request related to a problem? Please describe.

I think there should be an easier way to access quote-posts on Bluesky.
Describe the solution you'd like

I would like to see a link to see quote-posts on posts. Maybe a button under the 3-dot menu?
Describe alternatives you've considered

Have a dedicated link on posts to see quote-posts
Have a way to search for quote-posts related to a specific account

Ta-dah https://bsky.app/profile/bsky.app/post/3l2s5ocuzyc24

ayy


When specifing a JavaParser's classpath from byte[][], usage of classes in the default package cannot be resolved

The setup
There are 3 classes in the default package:
public interface InterfaceA {
    void methodA();
}

public interface InterfaceB {
    void methodA();

    void methodB();
}

public class User implements InterfaceA, InterfaceB {
    @Override
    public void methodA() {}

    @Override
    public void methodB() {}
}

The JavaParser instance can be specified in two ways:
// Classpath from compiled class files, fails to acknowledge classes in the default package
public static JavaParser prepareBinaryCP(byte[][] classpath) {
    JavaParser parser = JavaParser.fromJavaVersion()
            .classpath(classpath)
            .build();
    return wrap(parser);
}

// Classpath from directories (in our case, a single path pointing to the default package containing our sources)
public static JavaParser prepareSourceDirCP(Collection<Path> classpath) {
    JavaParser parser = JavaParser.fromJavaVersion()
            .classpath(classpath)
            .build();
    return wrap(parser);
}

Using org.openrewrite:rewrite-java-17 attempting to resolve the J.Identifier type of the classes referened in implements InterfaceA, InterfaceB yields different results based on the type of classpath.
The parser created from prepareBinaryCP fails, and tells you the types are Unknown. The parser from prepareSourceDirCP succeeds and reports InterfaceA and InterfaceB respectively.
Attached you can find a gradle project with the full setup demonstrating this behavior.
demo_project.zip

That's quite unfortunate @Col-E ! Thanks for reporting it here. Appreciate the time you've taken to produce the demo project.zip.
It took me a while to bring that down to this reproducing test: https://github.com/openrewrite/rewrite/pull/3245
Some simplifications that I've applied are:

Not have a method methodA in both InterfaceA and InterfaceB.
Move InterfaceA to package example, and reference that from User.
Do not provide a compiled User class to .classpath(byte[][]).
Limit reproduction to a single unit test.

Would you agree that covers the same case as what you've reported here?

The test in #3245 serves the purpose of this bug report perfectly well.
I'd like to verify after this gets solved that this also does not affect resolving of fields and method declarations belonging to classes in the default package, but since the class itself couldn't be resolved there was no way to verify that in my demo.
Perhaps a follow-up test to ensure this works as intended is warranted?

I've gone ahead and merged the test as it is, such that you can explore from the main branch yourself if you want to, and start a subsequent pull request if that helps. Signing off since it's close to midnight here. I've got some travel ahead for the rest of the week. Will keep an eye on this one but not sure I'll be able to resolve this immediately.

Think I've pinned it down to https://github.com/openrewrite/rewrite/pull/3249 ; feel free to test locally with ./gradlew publishToMavenLocal as well, pending a merge.

You can try out this change through our snapshot versions. Hope that helps!

Thanks for the quick fix :+1:

You're welcome! Glad it was relatively easy to do. Curious about your use case for byte[][] though; are you able to give a bit of background to your use case there? Just so we can support it better going forward.

Thanks for sharing your use case! It's indeed a bit out of scope for what we'd thought to cover, but you're welcome to use our internals if that helps. Do note that we are working on an 8.0 release, which might break some of those internals. You might already want to switch to a local copy of https://github.com/openrewrite/rewrite/tree/large-repositories . And then I suppose we just have to hope your use of OpenRewrite for code de-obfuscation does not end up hurting us both. ;)


SIMD support

SIMD enabled by simd feature, make sure to compile using nightly (cargo +nightly) for a supported target (using RUSTFLAGS='-C target-cpu=native' or RUSTFLAGS='-C target_feature=+avx2' for example).
Checks at compile time if the target supports AVX512/AVX2/WASM SIMD and chooses x16/x8/x4 accordingly.
Keeps bigger in and out buffers in the SIMD implementation, so only useful  if atleast 48 * 16/8/4 byte input/outputs are absorbed/squeezed.
SIMD xoodoo permutation is fully generic over the amount of SIMD  lanes.
Xoofff implementations are not fully generic due to unrolling on a  generic constant not being possible using crunchy.
Operations converting bytes to N parallel state and vice versa are not optimized.  They might be faster using gather/scatter methods.

TODO:

[ ] document how to enable the feature.
[ ] doc test compilation currently fails.
[ ] test simd in CI.
[ ] test or not include the x16 code (support is low, I don't have it either)

Thanks, feedback is appreciated. Since WASM does not have runtime feature detection I decided to not use any of the #[target_feature(enable = "...")] stuff.

Totally makes sense. I'll need some time before I can review the PR. Though it's a relief to see that tests are passing.

Hi @leonbotros , I merged back latest from master into your PR branch and when I benchmark on my machine 12th Gen Intel(R) Core(TM) i7-1260P, running GNU/Linux kernel 6.5.0-13-generic, I see :arrow_down:

It's pretty good :100:
I'd like to merge this and publish on crates.io. Would you doing the remaining or you want me to take over for the rest of the part ?

Hi, I currently have no time to clean this up a bit so feel free ;)
On Sun, Nov 26, 2023, 06:16 Anjan Roy @.***> wrote:

Hi @leonbotros https://github.com/leonbotros , I merged back latest
from master into your PR branch and when I benchmark on my machine 12th
Gen Intel(R) Core(TM) i7-1260P, running GNU/Linux kernel
6.5.0-13-generic, I see ⬇
Screenshot.from.2023-11-26.09-11-40.png (view on web)
https://github.com/itzmeanjan/xoofff/assets/45074836/e4651462-47e6-4a84-95f8-2fdcc6d66f96
It's pretty good 💯
I'd like to merge this and publish on crates.io. Would you doing the
remaining or you want me to take over for the rest of the part ?
—
Reply to this email directly, view it on GitHub
https://github.com/itzmeanjan/xoofff/pull/5#issuecomment-1826562275, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANY4MOE3JESN7JMHXNJBY3YGLGETAVCNFSM6AAAAAAZYJZQOOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGU3DEMRXGU
.
You are receiving this because you were mentioned.Message ID:
@.***>


appengine-java-vm-runtime change debian

I tried to install nacl and use nacl to compile other libraries based on the this image, and I have a problem finding the C compiler, and also run into many problems for other libraries. When I changed to debian:testing as the base image, everything works. So I am wondering can I directly use debian:testing as the base image of appengine-java-vm-runtime (instead of google/debian), and then deploy a VM instance? I tried so but it seems I have not be able to successfully deploy it yet. It will be great to get more information from you, thanks!

yes, you can clone this repository and change the base image you need for the Dockerfile.
You then build your image, locally. You may push it to the Docker hub if you want.
Let's say you call your built image YunchaoGongSC/myimage
You can then use it as
FROM YunchaoGongSC/myimage
ADD . /app


Accept

Issue: R# throws a warning at me, saying that an exception is not documented. Although it's already documented in the corresponding interface.  This already should be enough - IMHO.
Although - if I use the <inheritdoc /> tag it definitely should not throw a warning around. Right?

Here my simplified code broken down to the important parts.
/// <inheritdoc />
[Serializable]
public sealed class CantMoveForwardException
{
    public CantMoveForwardException(){}
    public CantMoveForwardException(string message) : base(message){}
    public CantMoveForwardException(string message, Exception innerException) : base(message, innerException){}
}

public interface IMyService
{
    /// <summary> ... </summary>
    /// <exception cref="CantMoveForwardException"> ... </exception>
    void MoveForward();
}

public class MyService : IMyService
{
    /// <inheritdoc />
    public void MoveForward()
    {
        if (!CanMoveForward)
        {
            throw new CantMoveForwardException("Can not move forward.");
        }

        _beforeCurrent.Push(Current);
        Current = _afterCurrent.Pop();
    }
}

Pretty essential...

I agree, this is a pretty big gap 😞

Looks the same as #26, #32, and #65

I'll look at it as soon as possible

What do you expect, how should Exceptional behave?
Simple solution
Ignoring any methods using /// <inheritdoc />
More complex solution
Checking the parents documentation if the exception is already documented.

If not: highlight the expression and provide catch quickfix
If not: highlight the expression (and provide documentation quickfix (could be hard to be implement, because the parent type can be outside the project))

Checking the parents documentation if all documented exceptions are thrown.

If not: highlight the method

I think Exceptional should checking the parent's documentation.
If the parent type is outside the project, I wouldn't expect to be able to do a quickfix on the parent type.  However, it'd be nice to maintain the ability to quickfix the implementation's documentation.

A quickfix could be provided for the parent documentation (if it's a source file that is modifiable, as opposed to just in an external assembly that isn't built from the solution), as well as another quickfix that adds the documentation to this implementation, since you can provide more documentation tags after /// <inheritdoc /> which will add or override documentation.


feat(SchemaUtil): parse a partial definition

We've fixed that in 1.10 as a part of #2411 https://github.com/dcos/dcos-ui/pull/2411/commits/552770ab47e3f849e7e3cabc870682ab0314708f and agreed not to fix on master since the form will be gone in 1.11
But people still stumble upon this bug, so let's fix it just in case.
to test try editing spark-history catalog package. Without the fix it throws with the fix it opens the form that looks broken but that's because the package doesn't provide anything to config.

LGTM 💯 ✨


Add a facet with datetime pickers

Add a facet that can display bootstrap's date time pickers as terms.

PR https://github.com/MyPureCloud/ember-multi-faceted-search/pull/8


Allow applying styles on all children of neeto-editor-content

https://www.loom.com/share/0e2c783b3ee54c4fb915306ce9facb9d
@AbhayVAshokan _a
Please take a look into this.
Issue origination: https://github.com/bigbinary/neeto-engage-web/pull/280#issuecomment-1038735622
cc: @labeebklatif

as an alternative, we may take separate prop, may be something like contentClassName and apply this to every note if wanted.

I would suggest adding this.

but I think this is against the convention that we follow.

@labeebklatif Can you please elaborate more on this? Thanks.

@labeebklatif Can you please elaborate more on this? Thanks.
@yedhink  Correct me if I'm wrong but I think I have read somewhere in our guide/convention that we don't take each and every style inside a reusable component as props and instead we take a single className prop for the component container and use css for styling the elements further down the tree. But now, I couldn't find the reference for this.

let me know If I can go forward with adding the contentClassName prop.

@karthiknmenon You can make the final call on this.
I would stick on to my previous suggestion that is to add this prop, because we'd be fixing an actual issue and moreoever keeping things sane.
The component here is named EditorContent. Which means we are dealing with content right? If I apply className to it, then it gets only applied to container as mentioned by Labeeb. As an end user, who uses other neetoUI components, not sure this pattern aligns with the convention of using className prop to apply styles to the component. Example take the Button component from neetoUI and how it's using className.
Here the prop should have been named containerClassName over classNames and we should add another className called contentClassName.
PS: I still haven't understood why it's named plural classNames over singular className in this component.

PS: I still haven't understood why it's named plural classNames over singular className in this component.

This prop classNames must have been named so by mistake, or typo. will be changing that.

@labeebklatif @yedhink Please watch the following loom video for more details. Lmk your thoughts on this.

Will rename the prop classNames to className and this can be used to target elements down the tree. I think no other changes required.

I agree with this argument. Adding an editorContentClass prop for all the children may provide unintended behavior for the different types of nodes. Here is a reference from KB where we add individual styles to different nodes: _article.scss.

@labeebklatif _a Assigning this to you. Please make the necessary changes with prop renaming. Please document the changes as well.

Closed #166 via #192.


Count backcrits stat

Is it possible to determinate if a hit was a backhit? - probably not
But I think it's possible to detect backCrits:
all DD players wear  Forceful niveots,
so when a player with it backcrit - right after it he receives a refreshed 10 sec status effect buff of the forceful niveot, I believe for each backcrit,
so if you count those effect refreshes and mark previous hits as backcrits it would be possible to count them and display stats " percent of backcrits out of total crits" - a pretty important and informative DPS debugging stat,
information about other players and their buffs is also sent to each client as we can see those in party window so it can be counted for everyone in the party.
P.S. - submitted my idea at https://github.com/gothos-folly/TeraDamageMeter/issues/19 also

I'm not going to work on this unless there's a reliable method of determining whether or not a hit is made from the back.  As far as I'm aware, this data isn't present in any specific packet and would require some guess as to how it's calculated.  Feel free to reopen this issue if there's a solid, accurate way of determining this information.


Feature request: Give a title for a groove

If Banana Drum is used as a practice aid, then links to a complete groove/beat will be shared.
It would be useful if these could have a free text title field which the sharing URL also encapsulates, for example "London School: Break 1".
This would also help for printed output from the app

This is actually the next thing I intend to do! It was suggested to me by someone else as well. I think it's a great idea.

This is now released!


[AutoRelease] t2-servicefabricmanagedclusters-2024-12-03-87446(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5756
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=2422

issue link:https://github.com/Azure/sdk-release-request/issues/5756


Chore - Refine VectorAnswer for vairous vector_document types

Changes

updated lib/boxcars/boxcar/vector_answer.rb for recent refactoring for vector stores
updated specs for various vector store types

Why?

vector_answer also needs to be updated
provide more exampels in the spec and in notebook
resolves https://github.com/BoxcarsAI/boxcars/issues/84

Test

irb console result
specs are green

i will open this later when it is ready.


Significant slowdown downloading blobs since 6.2.0 release

We updated from 6.0.0 to 6.4.0 and found significant slowdown downloading blobs from our s3 blobstore (for example, one blob went from taking ~1 second to ~1 minute). We iterated through the cli versions and found that this issue appears to have started with the 6.2.0 release, and seems to happen consistently with that release and following releases.

This happens when we call bosh-cli -n create-release --force --final --tarball="./${RELEASE_NAME}.tgz"
You can see some more context around how we're calling it here: https://github.com/cloud-gov/cg-pipeline-tasks/blob/master/finalize-bosh-release.sh#L21
The output looks something like:
Blob download 'clamav/clamav-0.103.0.tar.gz' (13 MB) (id: ce95e602-72a4-4bad-468c-b201bbb5eac8 sha1: sha256:32a9745277bfdda80e77ac9ca2f5990897418e9416880f3c31553ca673e80546) started
Blob download 'clamav/clamav-0.103.0.tar.gz' (id: ce95e602-72a4-4bad-468c-b201bbb5eac8) finished
-- Started downloading 'clamav/10a4dbaee8d249a360357bbcf850c4191f00f651ce6a3beb881fbca96f1a56c2' (sha1=sha256:5efd38c87e51a51d6db19815a5e4a6bc6f111e6f34ca463e388e21c301ff7c9c)
-- Finished downloading 'clamav/10a4dbaee8d249a360357bbcf850c4191f00f651ce6a3beb881fbca96f1a56c2' (sha1=sha256:5efd38c87e51a51d6db19815a5e4a6bc6f111e6f34ca463e388e21c301ff7c9c)
Adding package 'clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e'...
Added package 'clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e'
-- Started downloading 'license/b905361e886a6c30116305b2bc1e5cfcedc103d44a95ff2a820d125ecc9757d8' (sha1=sha256:1dd6f4b256bd948203262749c373e91d9d7859bc11ee3092e3a3a4789e00d4d9)
-- Finished downloading 'license/b905361e886a6c30116305b2bc1e5cfcedc103d44a95ff2a820d125ecc9757d8' (sha1=sha256:1dd6f4b256bd948203262749c373e91d9d7859bc11ee3092e3a3a4789e00d4d9)

Added dev release 'clamav/25+dev.1'

Adding package 'clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e'...
-- Started uploading 'clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e' (sha1=sha256:98d7f8de33355530a840427ca0499b79e1cc82e35a80ef9acfee5d42c8c9de13)
2021/01/29 15:48:51 Successfully uploaded file to https://s3.us-gov-west-1.amazonaws.com/cloud-gov-release-blobstore/bf948d44-c870-4291-6373-d1de1adb2167
-- Finished uploading 'clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e' (sha1=sha256:98d7f8de33355530a840427ca0499b79e1cc82e35a80ef9acfee5d42c8c9de13)
Added package 'clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e'

Added final release 'clamav/26'

Name         clamav
Version      26
Commit Hash  7fa516d+
Archive      /tmp/build/99c0cfc8/release-git-repo/clamav.tgz

Job                                                                      Digest                                                                   Packages
clamav/10a4dbaee8d249a360357bbcf850c4191f00f651ce6a3beb881fbca96f1a56c2  sha256:5efd38c87e51a51d6db19815a5e4a6bc6f111e6f34ca463e388e21c301ff7c9c  clamav

1 jobs

Package                                                                  Digest                                                                   Dependencies
clamav/ed6019fcc603a20421754ce0837856ae37065757fc565f886f230bd5465f478e  sha256:98d7f8de33355530a840427ca0499b79e1cc82e35a80ef9acfee5d42c8c9de13  -

1 packages

Succeeded

we notice the slowdown in the length of time between -- Started downloading [...] and -- Finished downloading [...]
When on one of the problem versions, we see this slowdown consistently across all blobs in our releases

The Started downloading / Finished downloading is where the bosh cli is downloading packages created from previously built final releases. It does this if the current package it wants to build has the same "fingerprint" as a previously created package, so it reuses the previously built one rather than creating it again from scratch.
We tried to simulate this by doing a bosh create-release /path/to/release.yml and ensuring our ~/.bosh/cache does not contain any of the packages for that release. We saw it download all the packages needed from the release blobstore.
Doing this with 6.1 it took ~48 seconds. Doing it with a version >6.2 took ~52 seconds. So we're still not able to reproduce it.
Are you able to reproduce it both in CI and on your workstations?

Good call on testing locally - I tested this on my workstation (OS X) and couldn't repro. I then retested in our CI (linux) and it was reproducible:
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8# cp -pr release-git-repo release-git-repo-1
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8# cp -pr release-git-repo release-git-repo-2
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8# cd release-git-repo
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo# cd ../release-git-repo-1
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-1# rm -rf ~/.bosh/*
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-1# bosh-cli --version
version 6.1.1-a0c78bc2-2019-10-25T22:16:25Z

Succeeded
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-1# time bosh-cli -n create-release --force --final --tarball="./release.tgz"
Blob download 'jq/jq-1.5.gz' (1.4 MB) (id: 6c933704-2057-4fa6-938b-ae67d9d51e30 sha1: 2e281d558b5d2c4695f9a9de87dca70d3e7cdc16) started
Blob download 'jq/jq-1.5.gz' (id: 6c933704-2057-4fa6-938b-ae67d9d51e30) finished
Blob download 'nessus-manager/Nessus-8.8.0-ubuntu1110_amd64.deb' (82 MB) (id: 9ce808a8-c4b3-4c7d-432c-447d336eac47 sha1: sha256:9db5f923f835ed54babe356e11730bc9da755affae1b922a3fd9875b24467ade) started
Blob download 'nessus-manager/Nessus-8.8.0-ubuntu1110_amd64.deb' (id: 9ce808a8-c4b3-4c7d-432c-447d336eac47) finished
-- Started downloading 'nessus-manager/7658ffa77bf65e9c304de588063af1ddcf4994bffe9ee181caf53ebdfe40bb9d' (sha1=sha256:633f147df26bfde816ee5ead711c18b77bef5bda1cfeecb56aef412bee745329)
-- Started downloading 'jq-1.5/ed1ad3461377d92db53d7a9481b928ef019fcc314a0a5c4aea4de260a095216f' (sha1=sha256:6a69d838525643f7f6cb29302a72daae27b74dbdf76eb7c6f06a8c645fc7b7de)
-- Started downloading 'nessus-manager/d73de857700a5a9b845b21263c26ed8f209628a8a177a9dcde180b2fc44ac2bc' (sha1=sha256:21c9b203ec0c8d97ec0506800fb2c01ff593dfa777a5bc6fe7666577249f9099)
-- Finished downloading 'nessus-manager/d73de857700a5a9b845b21263c26ed8f209628a8a177a9dcde180b2fc44ac2bc' (sha1=sha256:21c9b203ec0c8d97ec0506800fb2c01ff593dfa777a5bc6fe7666577249f9099)
-- Finished downloading 'jq-1.5/ed1ad3461377d92db53d7a9481b928ef019fcc314a0a5c4aea4de260a095216f' (sha1=sha256:6a69d838525643f7f6cb29302a72daae27b74dbdf76eb7c6f06a8c645fc7b7de)
-- Finished downloading 'nessus-manager/7658ffa77bf65e9c304de588063af1ddcf4994bffe9ee181caf53ebdfe40bb9d' (sha1=sha256:633f147df26bfde816ee5ead711c18b77bef5bda1cfeecb56aef412bee745329)
-- Started downloading 'license/7ba24dda6fb53dcd88909c880c29c12ed4538ac24db4c2057374ca79c39f7187' (sha1=sha256:bb1d6007ae51a3f68fc9e08c6435723a31ace8b830301c08c6415bb88336de77)
-- Finished downloading 'license/7ba24dda6fb53dcd88909c880c29c12ed4538ac24db4c2057374ca79c39f7187' (sha1=sha256:bb1d6007ae51a3f68fc9e08c6435723a31ace8b830301c08c6415bb88336de77)

Added dev release 'nessus-manager/28+dev.2'

Added final release 'nessus-manager/29'

Name         nessus-manager
Version      29
Commit Hash  5d10f53+
Archive      /tmp/build/99c0cfc8/release-git-repo-1/release.tgz

Job                                                                              Digest                                                                   Packages
nessus-manager/d73de857700a5a9b845b21263c26ed8f209628a8a177a9dcde180b2fc44ac2bc  sha256:21c9b203ec0c8d97ec0506800fb2c01ff593dfa777a5bc6fe7666577249f9099  nessus-manager
                                                                                jq-1.5

1 jobs

Package                                                                          Digest                                                                   Dependencies
jq-1.5/ed1ad3461377d92db53d7a9481b928ef019fcc314a0a5c4aea4de260a095216f          sha256:6a69d838525643f7f6cb29302a72daae27b74dbdf76eb7c6f06a8c645fc7b7de  -
nessus-manager/7658ffa77bf65e9c304de588063af1ddcf4994bffe9ee181caf53ebdfe40bb9d  sha256:633f147df26bfde816ee5ead711c18b77bef5bda1cfeecb56aef412bee745329  -

2 packages

Succeeded

real	0m5.040s
user	0m3.982s
sys	0m1.076s
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-1# cd ../release-git-repo-2
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-2# rm -rf ~/.bosh/*
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-2# bosh-cli-6.2.0 --version
version 6.2.0-e5ce64ab-2020-01-16T19:22:05Z

Succeeded
root@6fdc47d3-3140-4b55-7b65-c10e4a90d97a:/tmp/build/99c0cfc8/release-git-repo-2# time bosh-cli-6.2.0 -n create-release --force --final --tarball="./release.tgz"
Blob download 'jq/jq-1.5.gz' (1.4 MB) (id: 6c933704-2057-4fa6-938b-ae67d9d51e30 sha1: 2e281d558b5d2c4695f9a9de87dca70d3e7cdc16) started
Blob download 'jq/jq-1.5.gz' (id: 6c933704-2057-4fa6-938b-ae67d9d51e30) finished
Blob download 'nessus-manager/Nessus-8.8.0-ubuntu1110_amd64.deb' (82 MB) (id: 9ce808a8-c4b3-4c7d-432c-447d336eac47 sha1: sha256:9db5f923f835ed54babe356e11730bc9da755affae1b922a3fd9875b24467ade) started
   Blob download 'nessus-manager/Nessus-8.8.0-ubuntu1110_amd64.deb' (id: 9ce808a8-c4b3-4c7d-432c-447d336eac47) finished
-- Started downloading 'nessus-manager/7658ffa77bf65e9c304de588063af1ddcf4994bffe9ee181caf53ebdfe40bb9d' (sha1=sha256:633f147df26bfde816ee5ead711c18b77bef5bda1cfeecb56aef412bee745329)
-- Started downloading 'jq-1.5/ed1ad3461377d92db53d7a9481b928ef019fcc314a0a5c4aea4de260a095216f' (sha1=sha256:6a69d838525643f7f6cb29302a72daae27b74dbdf76eb7c6f06a8c645fc7b7de)
-- Started downloading 'nessus-manager/d73de857700a5a9b845b21263c26ed8f209628a8a177a9dcde180b2fc44ac2bc' (sha1=sha256:21c9b203ec0c8d97ec0506800fb2c01ff593dfa777a5bc6fe7666577249f9099)
-- Finished downloading 'nessus-manager/d73de857700a5a9b845b21263c26ed8f209628a8a177a9dcde180b2fc44ac2bc' (sha1=sha256:21c9b203ec0c8d97ec0506800fb2c01ff593dfa777a5bc6fe7666577249f9099)
-- Finished downloading 'jq-1.5/ed1ad3461377d92db53d7a9481b928ef019fcc314a0a5c4aea4de260a095216f' (sha1=sha256:6a69d838525643f7f6cb29302a72daae27b74dbdf76eb7c6f06a8c645fc7b7de)
-- Finished downloading 'nessus-manager/7658ffa77bf65e9c304de588063af1ddcf4994bffe9ee181caf53ebdfe40bb9d' (sha1=sha256:633f147df26bfde816ee5ead711c18b77bef5bda1cfeecb56aef412bee745329)
-- Started downloading 'license/7ba24dda6fb53dcd88909c880c29c12ed4538ac24db4c2057374ca79c39f7187' (sha1=sha256:bb1d6007ae51a3f68fc9e08c6435723a31ace8b830301c08c6415bb88336de77)
-- Finished downloading 'license/7ba24dda6fb53dcd88909c880c29c12ed4538ac24db4c2057374ca79c39f7187' (sha1=sha256:bb1d6007ae51a3f68fc9e08c6435723a31ace8b830301c08c6415bb88336de77)

Added dev release 'nessus-manager/28+dev.2'

Added final release 'nessus-manager/29'

Name         nessus-manager
Version      29
Commit Hash  5d10f53+
Archive      /tmp/build/99c0cfc8/release-git-repo-2/release.tgz

Job                                                                              Digest                                                                   Packages
nessus-manager/d73de857700a5a9b845b21263c26ed8f209628a8a177a9dcde180b2fc44ac2bc  sha256:21c9b203ec0c8d97ec0506800fb2c01ff593dfa777a5bc6fe7666577249f9099  nessus-manager
                                                                                jq-1.5

1 jobs

Package                                                                          Digest                                                                   Dependencies
jq-1.5/ed1ad3461377d92db53d7a9481b928ef019fcc314a0a5c4aea4de260a095216f          sha256:6a69d838525643f7f6cb29302a72daae27b74dbdf76eb7c6f06a8c645fc7b7de  -
nessus-manager/7658ffa77bf65e9c304de588063af1ddcf4994bffe9ee181caf53ebdfe40bb9d  sha256:633f147df26bfde816ee5ead711c18b77bef5bda1cfeecb56aef412bee745329  -

2 packages

Succeeded

real	8m18.203s
user	0m3.979s
sys	0m1.124s

Just tried in a vanilla ubuntu docker container, thinking it might be a linux problem, but didn't see a major difference in times there either.
I would guess it's something weird either in your docker image that the job is running inside, or something to do with the concourse infrastructure itself. If you're able to pin point what it is that's different in your CI vs your workstation it might let us identify where the cli is tripping up for you.
The cli basically is just calling out to https://github.com/aws/aws-sdk-go to fetch the assets from s3, and we did bump the library between versions 2.1.0 and 2.2.0, although we didn't see anything in any of the aws-sdk-go release notes that made it seem like the newer version had any bugs or major changes in the s3 behavior.

Closing due to inactivity


Add PHP 8.4 to CI matrix

@dbu Could you please merge this, and then tag a new release?
I need https://github.com/php-http/guzzle7-adapter/commit/c6975e5dae550cedfb8a5c1b801f3b27aadca2a5 to be able to run this on PHP 8.4

PHP Deprecated:  Http\Adapter\Guzzle7\Promise::then(): Implicitly marking parameter $onFulfilled as nullable is deprecated, the explicit nullable type must be used instead in vendor/php-http/guzzle7-adapter/src/Promise.php on line 76

thanks!

https://github.com/php-http/guzzle7-adapter/releases/tag/1.1.0


Handled for Failed Scenarios and Scan Paused

CoreConstants.java:
Alignment Rectification of new code
String SUSPENDED_RUNNING_SCAN and String ERROR_RUNNING_SCAN constants definition should be in ASE section below
String ERROR_RUNNING_SCAN is defined in ScanConstants.java. Why do we need it here?
ASE_GET_FITEMS_STATISTICS to be renamed to ASE_GET_FOLDER_ITEMS_STATISTICS
messages.properties
messages.suspended.scan to be defined in ASE section below
ASEResultsProvider.java
Please rectify all the alignment issues. The diff should only show the code modified.
Need more clarity on Suspend message construction. Looks too crude now. Will take it offline.
Copyright changes in IResultsProvider.java

I have updated my code accordingly, also regarding ERROR_RUNNING_SCAN I am reusing this variable defined in ScanConstants.java ..
The message for Suspend status is constructed to signify that the Scan is paused in ASE and it is reset when that Scan is again resumed, ASE returns Suspended (By User) status message for paused scan ..


Childnodes not deleted from index if parent node is deleted

For example, if the "Authors" node contains some child "Author"-nodes and the "Authors" node is deleted, the "Author"-nodes remain in the index.

@mcl-sz I will have time post 15th of June, I will have a look than!

I've created a pr (https://github.com/bielu/bielu.examine.providers/pull/22) to delete childnodes from the indexes. Could you give it a try?

@mcl-sz I guess we can close this ticket now, if not ping me and will reopen it


Your request to provision "Microsoft 365 learning pathways"  template failed!

As instructed here is the correlation ID: 6c5e1315-4edf-4186-8329-d3d87ae5d0ce !
Hope there is an easy fix for this as we are very interested inn the product :)
Regards
Hans Petter

Hi, Thanks for your feedback. I'm closing this item because it is now outdated.


Fix fasta_paired hardcoding

TEST RUN: https://staging.idseq.net/samples/835
Initial file type gets set as like:

    initial_file_type_for_log = "fasta"
    if "fastq" in FILE_TYPE or "fq" in FILE_TYPE:
        initial_file_type_for_log = "fastq"
    if len(fastq_files) == 2:
        initial_file_type_for_log += "_paired"

^ going to change them all to either fasta or fasta_paired


Update github source links to latest blob

This PR updates each Github src link \blob.*#L\ to the latest respective commit SHA.

Changed any link that contains a line number that points to blob\master because it would be likely pointing to the wrong place on future updates to master (e.g. the fix on L938) addresses that).
I went ahead and updated each blob to the latest commit SHA just to help this repo stay up to date.

wow thank you!

@sw-yx No no, thank you, this repo is 🏅
I forgot to mention that the change on L1342 also changed the link from a single line to a range of lines to highlight all of the built-ins instead of just point to Exclude.

gotcha. appreciated! its a team effort hahah


Fix to just project the exact fields are declared on columns and extraFields

Tabular has an amazing feature that is take care of the publications to just publish the fields are defined in columns and extraFields.
But there was an issue when you have a document/object with sub-documents, because the code
fields[cleanFieldName(data)] = 1;
execute cleanFieldName function to set what fields should be projected. When you have subdocuments and per example you set a column data with parent.child, cleanFieldName will get just the parent, then if you have a big document, all that fields will be published. This can be a security issue too.
I changed that line to doesn't clean the the field name, than unnecessary fields will be published.
fields[data] = 1;
This simple change will save a lot of traffic but can have a little negative impact on systems that are using another subdocuments that are not explicit published. Anyway, I guess this is a important change.

Hey @ricaragao , sorry about taking so long to reply. I think this is a better way of doing it. I only have two concerns:

if someone is using this and inadvertently relying on getting more fields
if they have another publication active on the collection I think merge-box can't handle subfields. So if you ask for config.a here and in another ask for config.b it will overwrite it.

Maybe we can make it opt-out ? So a config option saying cleanFieldName which defaults to true and you can set it in the tabular to turn it off ?

Hey @ricaragao , sorry about taking so long to reply. I think this is a better way of doing it. I only have two concerns:

if someone is using this and inadvertently relying on getting more fields
if they have another publication active on the collection I think merge-box can't handle subfields. So if you ask for config.a here and in another ask for config.b it will overwrite it.

Maybe we can make it opt-out ? So a config option saying cleanFieldName which defaults to true and you can set it in the tabular to turn it off ?

Hi @lynchem , yes, can be a good idea use a opt-out. Do you think it can be on main configuration object?

Hi @lynchem , yes, can be a good idea use a opt-out. Do you think it can be on main configuration object?

Yup, sounds good 👍🏻


🐛 [Firebase_core] Release apk file is not working

I'm trying to publish an app on google play but my apk release file is not working. However the app works fine on debug mode. When I launch the app, there is just a white screen. I think this is an error from firebase_core when I'm calling "await Firebase.initializeApp();".
I get this issue in the logcat:
E/flutter: [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: MissingPluginException(No implementation found for method Firebase#initializeCore on channel plugins.flutter.io/firebase_core)
    #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:157)
    <asynchronous suspension>
    #1      MethodChannel.invokeListMethod (package:flutter/src/services/platform_channel.dart:345)
    <asynchronous suspension>
    #2      MethodChannelFirebase._initializeCore (package:firebase_core_platform_interface/src/method_channel/method_channel_firebase.dart:30)
    <asynchronous suspension>
    #3      MethodChannelFirebase.initializeApp (package:firebase_core_platform_interface/src/method_channel/method_channel_firebase.dart:75)
    <asynchronous suspension>
    #4      Firebase.initializeApp (package:firebase_core/src/firebase.dart:44)
    <asynchronous suspension>
    #5      main (package:stream_in/main.dart:9)
    <asynchronous suspension>

main.dart :
void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  runApp(MyApp());
}

class MyApp extends StatelessWidget {

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: "Stream'In",
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      debugShowCheckedModeBanner: false,
      home: HomeController(),
      routes: <String, WidgetBuilder>{
        "/home" : (BuildContext context) => HomeController(),
      },
    );
  }
}

class HomeController extends StatelessWidget {

  @override
  Widget build(BuildContext context) {
    return StreamBuilder(
        stream: FireServices().onAuthStateChanged,
        builder: (context, AsyncSnapshot<String> snapshot) {
          if(snapshot.connectionState == ConnectionState.active) {
            meUid = snapshot.data;
            final bool signedIn = snapshot.hasData;
            return signedIn ? MainController() : FirstView();
          }
          return Scaffold(backgroundColor: Color(0xFF00B97E),);
        }
    );
  }
}

Hi @killian74
Could you please provide your flutter doctor -v and flutter pub deps -- --style=compact?
Thank you


fix: In debug model, there is progress display.

Set progress mode in code, and fix: #1253 .

Thanks for your contribution! :tada: :+1:


identifying blank nodes without an rr:template or rml:reference

In Section 4.1 Identifying collections is stated:

If no rr:template or rml:reference is provided for generating blank node IDs (rr:BlankNode) or IRIs (rr:IRI), then each iteration generates a new blank node identifier for the collection or container.

I think there is a general issue that we need to decide on here which is: Do we allow the generation of blank nodes without an explicit expression (rr:template, rml:reference, or other)?
Generating a random blank node id has impact on how you can implement joins on those terms, because there is no way to make the id generation repeatable. The R2RML spec does not allow blank node generation without an rr:template or rr:column, I assume for this reason.
So if we would want to allow this we would either have to:

Force processors into a way of implementing joins.
Have processors issue warnings when such a mapping is encountered, but it cannot guarantee correct results.
?

let's discuss this on a call, it's a difficult one

During the meeting (28/09/2022), we have decided to allow the generation of BN without reference to the data.
Does this issue have any impact on collections/containers spec then? @chrdebru @frmichel
If yes, we will leave it open. If not, we can close or transfer it to the core spec

During the meeting (28/09/2022), we have decided to allow the generation of BN without reference to the data.

The way we've written the container/collections specification is in line with this assumption, that is, the generation of a new blank node (that therefore cannot be named anywhere else) when there is no rml:reference of rr:template.
I'm closing this issue.

I'll open it again and transferred to the core spec


Spinner on Receive Screen

Add Spinner on Receive screen upload clicking the button

Which spinner do you want to use?

I would like to use the one that matches the mobile design.

The ScaleLoader one from https://www.react-spinners.com/?
On Mon, Nov 18, 2019 at 2:18 PM Linda Yang<EMAIL_ADDRESS>wrote:

I would like to use the one that matches the mobile design.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/lindaayangg/Wave-Web/issues/19?email_source=notifications&email_token=AI2J2LSY3XSNPD5NGACTKDDQULS7BA5CNFSM4JOLDC4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEELS2JY#issuecomment-555167015,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI2J2LWAREG2HMD64OC5OXDQULS7BANCNFSM4JOLDC4A
.

Added ScaleLoader


feat(glue): Use table name as human-readable name for Glue ingestion

The FQN includes the catalog ID and database name. Add in the 'name' field that is just the table name, like the SQL-based sources, to make it more readable in the UI
Before:

After:

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@hsheth2 @jjoyce0510 thanks for looking at this! Seems like the tests passed but the Datahub Jars step failed to do with the TestSparkJobsLineage though, which I don't understand. Is this possibly some transient issue with that build step?

Hey @danielcmessias Glue tests are also failing due to current change - https://github.com/datahub-project/datahub/actions/runs/4060755489/jobs/6990676582 You'll need to update glue test golden files for adding the field name .

oof didn't scroll down, missed those checks. On it! 👍

Re-raising as #7213. Please don't merge master into branches, it makes it a nightmare dealing with rebasing! 😅

@danielcmessias ah my bad - sorry about that


Update HalideIR submodule to include TVM_STATIC_IR_FUNCTOR_REGISTER

Submitted PR to HalideIR repo to fix this compiler error.
https://github.com/dmlc/HalideIR/pull/20
Will update this PR after the above is merged

Also added 2 minor bugfixes that are needed upstream in NNVM


Create a way to have a page for a local question

There's interest in having a question page for a Portland question, so we need a way to have those that can be linked from the local elections page, but not get put in with the statewide questions on the homepage.

Potentially using collections.


Adding test id to cluster level eviction strategy tests

What this PR does / why we need it:
Adds tests IDs to cluster-wide eviction strategy tests
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/ok-to-test

/retest

/retest-required


How to remove Paket references from the project?

When somebody wants to remove Paket created references from the project naive approach is to delete paket.references file. It takers some time to realize that the only effect it has - Paket does not look at that project anymore, but does not remove existing references from it either. Approach which works is to have empty paket.references file - then references indeed get removed.
Ideally removal of the paket.references file should have the same effect, but it may be ineffective performance wise as it would require to look inside each and every project. If performance impact appear to be substantial, then the trick with empty paket.references file should be documented.

"he trick with empty paket.references file should be documented"
I'd love to see such a PR

I decied that we should cover this case and now paket removes all installed Paket entries from projectes which have no corresponding paket.references.

I'm glad you did! Trick with empty Paket.references really looked as a clumsy workaround. I would hate to have it documented as a proper way of removing references. Now it is much more natural.


low firm OTP doesn't tell to skip section 1 step 18 in part 5

Someone on reddit has tried the low firm OTP guide and didn't understand what to do in section 1 step 18 in part 5, so please add the fact you skip it to the guide.

New guide is up and all currently open issues are being closed. If you feel your issue still applies to the new guide, you can request for it to be re-opened by replying to it.


Fix committer nomination email address

Purpose / why
I recently tried nominating a committer using the process outlined here and noticed the email address that was mentioned was out of date.
De-CLAWing relates to: https://github.com/Islandora/documentation/issues/1082
What changes were made?
Updated to the new email address for the Islandora 8 committers list. While I was modifying the templates I also noticed that they referenced CLAW, so I did a bit of de-clawing as well.
Interested Parties
@dannylamb @Islandora/8-x-committers
Checklist

Pull-request reviewer should ensure the following

[ ] Does this PR link to related issues?
[ ] Does the proposed documentation align with the Islandora Documentation Style Guide?
[ ] Are the changes accurate, useful, free of typos, etc?

Person merging should ensure the following

[ ] Does mkdocs still build successfully? (This is indicated by TravisCI passing. To test locally, and see warnings, see How To Build Documentation.)
[ ] If pages are renamed or removed, have all internal links to those pages been fixed?
[ ] If pages are added, have they been linked to or placed in the menu?
[ ] Did the PR receive at least one approval from a committer, and all issues raised have been addressed?

ugh... travis looks stuck

oh this is :100: me messing around with the default branches and stuff.  let me see if there's something extra i need to do on the travis side of things.

:man_shrugging: maybe travis just needs a little time to catch up.  it thinks the default branch is still master, yet there's no way for me to configure that in travis itself or through the app settings in github.  ima merge this and we'll see on the next one.


Consider implementing UnwindSafe for lock-free atomic types

If std atomic types can do it, so can you.

Same reasoning applies to RefUnwindSafe too.

UnwindSafe and RefUnwindSafe are not available in core, and this crate is no_std.

Could it be provided behind an off-by-default (for backcompat) std feature?

Sure, a std optional feature would work.
I don't think implementations for UnwindSafe are needed, they should have been derived automatically since it is an auto trait.
Are you willing to create a PR?

Ah yes, you're right, UnwindSafe should be auto-implemented for the UnsafeCell<T> inside of Atomic<T>. It's RefUnwindSafe that was giving me trouble the other day.
Let me roll out a quick PR now that we agree on the design...

So, I'm almost there, but there is an unexpected wrinkle. Your SpinLock fallback does not implement poisoning, which means that implementing RefUnwindSafe for non-lock-free Atomic<T> is incorrect.
How do you want to resolve this? By implementing lock poisoning for the SpinLock, or by adding a blanket trait that discriminates whether types are lock-free and is used as a trait bound by the RefUnwindSafe implementation.

It's fine since code never unwinds while holding the spinlock.

Ah, yes, you're right. The current atomic-rs API does not expose any operation that could lead to a panic while the object is in an inconsistent state.


Escape Special Chars + clean-up abandonned review request.

Hope you'll like it ;)

:+1:

many thanks :)


Request to enable uv.lock to not include the index url

Hello team,
Many thanks for the awesome work you're doing, and the countless amounts of time you've saved everyone using uv (and ruff).
I've seen the recent blog post about 0.3.0 and the accompanying documentation update, and from playing a bit to test commands like uv lock and uv sync, I actually have a question about uv.lock.
I've described the setup I use in https://github.com/astral-sh/uv/issues/1710 (a proxy, and using invoke, etc.). That setup means that on different team member's machine's, each is likely to have a different INDEX_URL and even the CI/CD system we use would have a different one.
I've generated the uv.lock file using UV_INDEX_URL=... uv lock, and the main thing I noticed is that the index url is included in the lock file e.g.
[[package]]
name = "aws-embedded-metrics"
version = "3.2.0"
source = { registry = "http://<omitted>/pypi/simple" }
dependencies = [
    { name = "aiohttp" },
]
sdist = { url = "http://<omitted>/pypi/simple/aws-embedded-metrics/3.2.0/aws-embedded-metrics-3.2.0.tar.gz", hash = "sha256:f235f87ab25ff328f6f3afca1c6b3218e81eea6e96e6aee012d368bb813fae7b" }
wheels = [
    { url = "http://<omitted>/pypi/simple/aws-embedded-metrics/3.2.0/aws_embedded_metrics-3.2.0-py3-none-any.whl", hash = "sha256:887b76d24914efa5fc42a7b77983e77fc670633e6e1195aac7653c425fee7399" },
]

I have not tried using that file across our different machines yet, but I suspect it's going to cause problems so I wanted to confirm with you folks

What would happen if the index in the lock file is not available, and UV_INDEX_URL?
Is there a way to not include the full index url in the lock file?

I've tested it further and confirmed that uv sync would fail on the different machines given the UV_INDEX_URL= would be pointing to a different index url.
With that that, I think this is a request to enable not writing the index url into the lock files via uv lock, and to enable uv sync - and other commands to use the lock file that does not have index urls as part of the lockfile

I discovered uv recently and I'm pretty excited about it! So even if we're discussing issues, thanks! 🫶
Now, coming to the topic, I think this becomes important given the ability to setup index-url and extra-index-url as user-level configuration, and potentially as system-level configuration (#6742).
Right now if you have a user-level config pointing at a package repository that acts as proxy to PyPI (that might add private pacakges on top) you will record that url in any lock file you generate. So if you want to work on some public project where uv is used as pacakge manager, either

the project -that you might not control- specifically defines index-url and extra-index-url to point at PyPI
you disable the user-level config
or you will generate lock files that people outside of your org will not be able to use

Option 2 might not seem that bad, but then that defies the purpose of being able to define user-level or system-level configs. Plus, it might not be the ideal setup ideal to take advantage of uvx and uv tool using private packages that are only available in the private repository.

Just adding a couple more comments

I did see on some other issue/pr, a mention that thanks to including those full paths, uv wouldn't be doing any further resolutions, and it just goes ahead to install things - which would save some time which sounds great
In the case of the setup we're using, I noticed something which might be useful to call out

when the index, is public pypi index i.e. https://pypi.org/simple, the package artifacts have urls with a prefix looking like https://files.pythonhosted.org/packages/c1/08/1bb1f7392cd9c3a65c4571a7f7286056ec52b3cd3d432485ca2b9907e0f9/. For example, for aws-embedded-metrics, it's https://files.pythonhosted.org/packages/c1/08/1bb1f7392cd9c3a65c4571a7f7286056ec52b3cd3d432485ca2b9907e0f9/aws-embedded-metrics-3.2.0.tar.gz
in my case, this custom index, which uses a local proxy on dev/ci machines i.e. http://<omitted>/pypi/simple, the package srtifacts urls follow a more deterministic url pattern e.g. http://<omitted>/pypi/simple/<package name>/<package version>/. The same aws-embedded-metrics would be http://<omitted>/pypi/simple/aws-embedded-metrics/3.2.0/aws-embedded-metrics-3.2.0.tar.gz.

This determinism, can actually lead to a simpler handling of this, where I tested with

Generate the uv.lock with setting a UV_INDEX_URL to my custom index
Used it in other machines, by running another small script, prior to uv sync, that modifies uv.lock to replace the index in http://<omitted>/pypi/simple with the content of UV_INDEX_URL

All of this, makes me wonder if there's some solution to cases like mine, along the lines of

Executing commands like uv lock, to have a flag to indicate usage of placeholder index urls, where it would have a place holder for UV_INDEX_URL or the extra indices
Executing commands like uv sync can take a similar flag, where it'd use the values passed through UV_INDEX_URL to resolve the placeholder values in uv.lock

What follows is a +1 comment you should all ignore, but I'm writing it to include some keywords in this issue so other people who run into this can find it more easily than I just did (took me a while):

Having the same issue because I fetch all my PyPI packages through a local devpikeyword 1 installation, so all source.registry and sdist.url URLs in uv.lock say https://localhost:3141/...keyword 2 and, needless to say, this results in Connection refusedkeyword 3 errors when trying to install the package elsewhere (e.g. CI systems such as GitHub Actionskeyword 4 or GitLab CI/CDkeyword 5).

The more comments this gets, the more I think there needs to be an option for the lock file to not include any index information.
This way, all those use cases that use local proxies, different on developer machines from those in CI environments, and the likelihood that those different proxies having different conventions for their asset (wheel/sdist) URLs, that a general simple solution to exclude those index/asset URLs would be very useful and enable them to adopt uv.lock

We could really also use this to be able to have lock-files without disclosing internal urls.
If not in the sync file then an option to the export subcommand to export a new uv.lock but with this or other things omitted would also be a good alternative

@charliermarsh That may very well work for our requirements but it looks like the uv lockfile is richer (all the extras are declared). Otherwise it would just be a convenience to not have someone outside (that don't have access to internal dns-names) being able to use the lock-file without having to regenerate it from the requirements.txt (pardon me if I've missed a quicker way to handle that).
Basically my thought was that the hashes should be enough to guarantee that it's indeed the same packages that are being installed even if the urll has to be found again.
That said if it doesn't feel like the right way to do it and the recommended way is to manage that with requirements.txt exports we'll try that and raise a more specific issue or discussion if a showstopper or question regarding that comes up.
(feel free to edit/move/hide post if it derails original thread)

@charliermarsh
At the moment, I'm actually using uv pip compile pyproject.toml... and uv pip install -r ... to simulate having a lockfile.
The main thing I don't like about it, is keeping the lockfile up to date with pyproject.toml dependencies is all manual. I didn't want to always call uv pip compile, then follow immediately by uv pip install as that would (1) be slower (2) force updating resolved dependencies that are declared via version ranges.
So, I'd say that's not on par with the experience of something like package.json and package-lock.json for node, and I was hoping that uv.lock and the commands that maintain/use it are giving a better experience.
The other thing I like about uv.lock is uv.tool.dev-dependencies. Without that, I end up declaring those dependencies as optional dependencies which is really not right, but ended up doing it this way, so I can declare all my dependencies in pyproject.toml, and then generate the current requirements.txt "lockfile".
Omitting the URLs is one potential solution - me thinking out loud.
In the case of my proxy, given that the sdist/wheel URLs have a specific pattern with the index url being a prefix, I was able to run some code to manipulate the lock file before running uv sync --all-extras --frozen to install dependencies
@task
def update_lock_index_url(ctx):
    """
    Workaround for `uv lock` writing the index url to the lock file.
    Update `source` and `url` fields with values based on `UV_INDEX_URL` environment variable.
    """
    with open("uv.lock", "r+") as file:
        contents = file.read()
        pattern = r"http://<IP_ADDRESS>:\d+/[^/]+/[^/]+/[^/]+/pypi/simple"
        replacement = os.environ.get("UV_INDEX_URL", "NO_INDEX_OVERRIDE_SET")
        new_contents = re.sub(pattern, replacement, contents)
        file.seek(0)
        file.truncate()
        file.write(new_contents)

Downside for this, is that any dev on my team will end up having modifying uv.lock.
2 thoughts I had about this

uv having this concept of a hook - some python code to execute to modify file content - before installing dependencies
Ability to specify path to a lockfile, whereby I can run the hook myself, to generate a modified version of the lockfile, make sure it's in .gitignore, or in some tmp directory, and use uv sync while pointing to my modified version

I thought the simplest of all of the above would be this whole omission of URLs from the file tbh.
Moreover, generally when I think about what's uv story for supporting specifying index/extra index, and how that interacts with commands like uv sync, I think the strong assumption there is that the index URLs are not changing, which at least in my case is not true - whether across dev machines, or in the CI environment.

I'm not sure that a lockfile without URLs is a good idea. One of the goals of the lockfile is to be hermetic: you can install from just the lockfile without making any queries or relying on any external sources.
If you're going to omit source information like that, why not just export to requirements.txt?

As far as I can see, poetry records the file name and the hash, which should be enough to ensure that you are getting exactly the same files without relying on external sources.
On the other hand, by including the URLs you are coupling the lock file with the specific path of the package repository that you are using. And while this might remove the need of interacting with the package index, it also seems that adding a proxy package repository on the working environment should be transparent to the dependency specification of my project.

I consider it fairly critical that the lockfile includes the URLs directly and I suspect that the lockfile standard (should it be accepted) will do the same. We do have a plan to support these use-cases though. After #7481, we'll add something like:
[[tool.uv.index]]
name = "private"
url = "https://private.org/simple"
proxy = "http://<omitted>/pypi/simple"

So you can set the index URL (which will appear in the lockfile) and then the proxy separately. You'll also be able to set the proxy as an environment variable, like UV_PRIVATE_PROXY_URL or similar.

Hey @charliermarsh,
Just to make sure I understand this, and try to assess whether it'd work.

The url in our case is not needed, though I dunno whether the intention is for it to be a valid index, or any url so maybe you can clarify that.
I guess the url is what would be saved in index? and the proxy is kinda what replaces it when doing the actual resolving/downloads?
for the package urls e.g. sdist, and wheels, how would that work with the proxy? In my earlier messages, I did see https://pypi.org/simple has sdist and wheels that don't have the index as part of their urls e.g. https://files.pythonhosted.org/packages/c1/08/1bb1f7392cd9c3a65c4571a7f7286056ec52b3cd3d432485ca2b9907e0f9/aws-embedded-metrics-3.2.0.tar.gz but in my case, it does have the index in the url e.g. http://<omitted>/pypi/simple/aws-embedded-metrics/3.2.0/aws-embedded-metrics-3.2.0.tar.gz

Ideally it is a valid index and indicative of the actual locations of the files but that wouldn't be strictly required.
Correct.
Both the file URLs and the registry URLs would be "replaced" correctly as long as they're on the same domain. So this wouldn't work for PyPI but would work for your case.

Great... then I look forwards to that :)

I consider it fairly critical that the lockfile includes the URLs directly and I suspect that the lockfile standard (should it be accepted) will do the same.

Sorry! Actually, reading about the proposed standard I found this comment that properly describes what was my concern, and then the answer to it. The point that I was missing is in fact addressed in the PEP draft:

Installers MUST NOT assume the URL will always work, but installers MAY use the URL if it happens to work.

So yeah, I understood that URLs would be assumed to work, and that didn't seem a great idea. I see that's not the case, so nothing to object!
What got me confused is that apparently uv sync does assume the URLs to work unless you explicitly configure a value for either index-url or extra-index-url somewhere. I reported it in #8076 and #8074, hope it's useful. In any case, that's just about keeping improving uv and not a design disagreement.
Thanks for the answers!

I saw that the revamped index support got released in 0.4.23.
Is there any separate issues to track the proxy/env variables support, or is this issue itself that?

I think it’s ok to track it here.

May I ask what's the current status of the issue? What aspects remain unclear?
Currently I use a workaround (Run uv lock once with the alternative index URL and use the updated uv.lock file in the whole pipeline) to make CICD work with an alternative index. However, with this approach, you must be careful not to update any dependencies.

I don't know if anything is unclear, it's more that it hasn't been prioritized.


yamlfmt insert blank line between commented line

I have the following YAML:
---
Resources:
  ElasticBeanstalk:
    Type: AWS::CloudFormation::Stack
    Properties:
      #NotificationARNs:
      #  - String
      #Parameters:
      #  Key : Value
      #Tags:
      #  - Tag
      TemplateURL: https://examplebucket.s3.ap-southeast-1.amazonaws.com/example-file.json
      TimeoutInMinutes: 5

after formatting, each commented line will have a blank line inserted, becoming:
Resources:
  ElasticBeanstalk:
    Type: AWS::CloudFormation::Stack
    Properties:
      #NotificationARNs:

      #  - String

      #Parameters:

      #  Key : Value

      #Tags:

      #  - Tag
      TemplateURL: https://examplebucket.s3.ap-southeast-1.amazonaws.com/example-file.json
      TimeoutInMinutes: 5

I don't see any option to configure the formatter so that it does not include a blank line after each comment.
Thank you.

Hi @sharuzzaman,
Unfortunately at this time there aren't a ton of configuration options, so you wouldn't be able to configure a behaviour like this for the time being.
However, I'm unable to reproduce this behaviour locally at the moment. I tried copying the yaml from the first block into a file on its own and it did not insert the newlines as you've mentioned.
x.yaml:
---
Resources:
  ElasticBeanstalk:
    Type: AWS::CloudFormation::Stack
    Properties:
      #NotificationARNs:
      #  - String
      #Parameters:
      #  Key : Value
      #Tags:
      #  - Tag
      TemplateURL: https://examplebucket.s3.ap-southeast-1.amazonaws.com/example-file.json
      TimeoutInMinutes: 5

Piping it into stdin:
braydonk@bk:~/Git/yamlfmt$ cat x.yaml | yamlfmt -dry
dry run produced no output

There's a chance this is a platform issue. What operating system are you on?

This seems to be a Windows-specific issue. Gotta be some kind of CRLF problem if I had to guess. I'll keep looking into it.

This is tough. It's a combination of 2 bugs in yaml.v3, one is pretty simple and one is not.
yaml.Encoder always writes \n, I'll make a PR upstream that makes it configurable to write \r\n instead
When the parser scans a head comment ending in \r\n, if the next line is anything but another line break, it inserts an extra line. This is deep in the parser code, and won't be fast to solve...
The silver lining is that this is not a universal Windows issue, this is particularly with CRLF line endings. That is a possible workaround if you are flexible with line endings in your project. Regardless, I'll do what I can to get this solved.

Opened https://github.com/go-yaml/yaml/issues/891 and a PR for it https://github.com/go-yaml/yaml/pull/892

I managed to find the problem in the parser code too. Opened https://github.com/go-yaml/yaml/issues/893 and https://github.com/go-yaml/yaml/pull/894

I've opened a hotfix for the behaviour while waiting for the upstream stuff to get fixed, and that's what will go in v0.3.0 so that Windows users can be fixed sooner.

I would like to update that this issue is not happening again and the hotfix is working correctly. Thank you


on Warning about unclosed IF, give the script name

Reported by ansley b manke on 1 Jul 2016 23:21 UTC
As part of the the work for SET REDIRECT and VTREE, we implemented warnings when exiting a script and there is an unclosed IF block.
    *** NOTE: Unclosed IF statement ... assuming ENDIF

To make it easier to fix scripts, add the script file name to this NOTE.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2446

Modified by ansley.b.manke on 11 Jul 2016 17:26 UTC


regex enable UTF8 clan name

May i know how to disable only allows alphanumeric characters? Thanks.

If I remember correctly while testing, you should be able to by removing the & in "^[a-zA-Z0-9&]*$"


This is so complicated, No examples for doing a simple email on failures.

Why is the documentation so bad that it's impossible to ever find anything when it comes to application insights? Is there any example or documentation for simply setting up a simple email alert that can be received anytime a failure occurs in our applications.

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

ID: f826c77e-a9c8-5baa-af70-690e8383372b
Version Independent ID: df6cea2c-8b90-706a-2dfd-041026e7396d
Content: Action rules for Azure Monitor alerts
Content Source: articles/azure-monitor/platform/alerts-action-rules.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @anantr
Microsoft Alias: anantr

@jwisener :Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

Hi @jwisener, sorry for the unsatisfactory experience. we take these feedback very seriously and open to any suggestion on how your experience can be improved.
Regarding your question: Here's a sample ARM template you can review and customize for your scenario. This template creates a simple alert via an action group to send email notifications for any failed Autoscale records in the Azure Activity Log. Check here for a comprehensive list of community-authored templates.
I recommend posting your question directly on the MSDN ApplicationInsight forum where one of our subject matter experts provide specialized guidance.
We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Issue in R Interactive Sessions Caused by get_Rscript_filename() returning NA

get_Rscript_filename() function returns NA in interactive R sessions while debugging/developing, causing errors in the script. NA propagates to functions creating/naming .tsv files.

This should be done on branch from develop-refactor.

This has been merged into develop #147, so I'm closing this issue.


PathNameValue only lowercase

I think this should be:
PathNameValue: /[a-zA-Z0-9\-_\.\/]+/;
https://github.com/coreruleset/secrules_parsing/blob/070ea31be168c2875c6be4df329193f526110f45/src/secrules_parsing/model/secrules.tx#L193
isn't it?

isn't it?

perhaps yes.
Could you show the use-case example? I'd try to parse and fix if it necessary.

something like @beginsWith /Foo
Syntax invalid: Syntax error in line 18 col 35: Expected '"' at position xxx.conf:(18, 35) => 'ginsWith /*HRPortal/s'.

something like @beginsWith /Foo
Syntax invalid: Syntax error in line 18 col 35: Expected '"' at position xxx.conf:(18, 35) => 'ginsWith /*HRPortal/s'.

like /Foo or like /*HRPortal/s? :)
$ cat themiddle.conf
SecRule ARGS_NAMES "@beginsWith /*HRPortal/s" \
    "id:123,\
    phase:2,\
    pass,\
    log,\
    t:none"

diff --git a/src/secrules_parsing/model/secrules.tx b/src/secrules_parsing/model/secrules.tx
index dc78842..2c52a2f 100644
--- a/src/secrules_parsing/model/secrules.tx
+++ b/src/secrules_parsing/model/secrules.tx
@@ -190,7 +190,7 @@ StringWithSpaces: /[A-Za-z0-9\-\/\ \._]+/;
 PathOrMacro: PathNameValue | MacroVar;

 // Filesystem Paths (could be merged with URI, tought)
-PathNameValue: /[a-z0-9\-_\.\/]+/;
+PathNameValue: /[a-zA-Z0-9\-_\.\/]+/;

 // Macros, e.g: %{tx.critical_anomaly_score}
 Macro:  INT | OperationMacro | ExtendedMacro | MacroVar;

$ poetry run secrules-parser -c -f themiddle.conf -v
Processing file themiddle.conf:
Syntax invalid: Syntax error in line 1 col 34: Expected '"' at position /home/airween/src/secrules_parsing/themiddle.conf:(1, 34) => 'ginsWith /**HRPortal/'.

but
diff --git a/src/secrules_parsing/model/secrules.tx b/src/secrules_parsing/model/secrules.tx
index dc78842..e864883 100644
--- a/src/secrules_parsing/model/secrules.tx
+++ b/src/secrules_parsing/model/secrules.tx
@@ -190,7 +190,7 @@ StringWithSpaces: /[A-Za-z0-9\-\/\ \._]+/;
 PathOrMacro: PathNameValue | MacroVar;

 // Filesystem Paths (could be merged with URI, tought)
-PathNameValue: /[a-z0-9\-_\.\/]+/;
+PathNameValue: /[a-zA-Z0-9\-_\.\/\*]+/;

 // Macros, e.g: %{tx.critical_anomaly_score}
 Macro:  INT | OperationMacro | ExtendedMacro | MacroVar;

seems solves the problem:
$ poetry run secrules-parser -c -f themiddle.conf -v
Processing file themiddle.conf:
Syntax OK: themiddle.conf

If this is what you want, I can send a PR.
The question is here do we want to allow the * in PathNameValue?
Cc @fzipi, @theseion.


v3.0.1

This release includes:
Update the govuk_frontend_toolkit to 5.1.2. This updates show-hide-content.js to work with new .multiple-choice custom radio buttons and checkboxes, released in GOV.UK elements 3.0.0.
A fix for table cells, these are now 19px when using tabular-numbers.
What type of change is it?

Bug fix (non-breaking change which fixes an issue)

https://github.com/alphagov/govuk_elements/blob/master/VERSION.txt was missed.


tmpdir module should be required first when using Ruby 2.3.1

/usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/atomos-0.1.1/lib/atomos.rb:8:in `atomic_write': undefined method `tmpdir' for Dir:Class (NoMethodError)
	from /usr/local/var/rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/xcodeproj-1.5.5/lib/xcodeproj/project.rb:354:in `save'
	from ./node_modules/instabug-reactnative/link.rb:79:in `<main>'

Fixed according to similar steps: https://github.com/ydkn/capistrano-git-copy/issues/22

Thanks @EvianZhow for pointing this out. We'll be adding it to our docs :)


RSA Algorithm in Cryptography

🚀 Feature
RSA algorithm is a public key encryption technique that can be considered as the most secure way of encryption. It is an asymmetric cryptographic algorithm i.e it has two keys: public key and private key
Have you read the Contributing Guidelines on Pull Requests?
Yes

I would like to work on this in python

i would like to work on this in java


docs: how to integrate with Istio

Kong and Istio can play together. We have written blogs about these, but these should be included in documentation:
https://konghq.com/blog/kong-istio-setting-service-mesh-kubernetes-kiali-observability/
https://kubernetes.io/blog/2020/03/18/kong-ingress-controller-and-istio-service-mesh/

Let me know if there is anything blocking this on the Istio side

@hbagdi   Please 。Can both kong and kong ingress be combined with istio, what's the difference between them?

Request from #777:

Excuse me, I want to combine kong and istio. But don't know how to do it. There are some official tutorials but they are not very detailed. For example, how to replace the gateway of istio and combine it with virtualservice. The native istio virtualservice is bound by selecting the istio gateway. So can I bind to the kong ingress controller or other ways. I strongly suggest that the official can give a relatively complete case. This place is really confusing.

@mflendrich
We are planning to provide a complete how-to on running Kong with Istio soon, and the work is tracked in #703.
I have added your request to that issue. Let's continue our discussion there - closing this issue as a duplicate. Please describe in #703 what exactly you are trying to achieve with Kong, and we might be able to cover that in docs.
Excuse me, as you replied above. One more question, is it not technically compatible with istio? You need to wait for the kong version to be updated, or is it technically compatible but the documentation is not perfect

@hbagdi Regarding documentation. What is the version of the kong, kong-ingress-controller and istio that it should work with?
In https://kubernetes.io/blog/2020/03/18/kong-ingress-controller-and-istio-service-mesh/ there is such info
If you would like a deeper dive into Kong Ingress Controller 0.7, please check out the GitHub repository. but host_header for kong is avaialble from 0.9:
https://docs.konghq.com/kubernetes-ingress-controller/1.1.x/references/annotations/#konghqcomhost-header

@andrzej-jedrzejewski You don't need host-header annotation to work with Istio. Version compatibility is as is listed in the doc.


ADAD-1179: Add support for zone constraints

Cool.
1 error(s) occurred:

* maas_instance.savvy-einstein: 1 error(s) occurred:

* maas_instance.savvy-einstein: ServerError: 400 BAD REQUEST ({"zone": ["No such zone: 'default2'."]})

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.


Homebrew installation seems be be broken

It has been fixed. Thanks.

Can confirm.  I was able to get this to install this morning.


Web apps from WSL2 not accessible from other devices in same LAN

Windows Version
Microsoft Windows [Version 10.0.22631.4602]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu 24.04
Other Software
Windows 11 Education,
My .wslconfig:
[wsl2]
memory=8GB
networkingMode=mirrored
defaultVhdSize=256GB
autoProxy=true
dnsTunneling=true
firewall=true

[experimental]
autoMemoryReclaim=gradual
hostAddressLoopback=true

Repro Steps
Run following command from this issue in elevated prompt and then launch some web app (in my case simple Node.js server running on port 3005).

A safer alternative is to Only allow connection to wsl in a Trusted (Private) network:

New-NetFirewallHyperVRule `

-DisplayName 'Allow All Inbound Traffic to WSL in Private Network' `

-Name 'WSL Rule' `

-Profiles Private `

-Direction Inbound `

-Action Allow `

-VMCreatorId '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' `

-Enabled True

This would block connection to wsl in a public (or untrusted) network, which is good.
In case you want to delete the rule, run:

Remove-NetFirewallHyperVRule -Name 'WSL Rule'

Originally posted by @tusharsnx in #10769
Expected Behavior
Web app is accessible on other LAN devices at WSL2_IPv4:PORT
Actual Behavior
Web app is only accesible on host machine via localhost:PORT and WSL2_IPv4:PORT
Diagnostic Logs
WslLogs-2024-12-23_16-15-20.zip

It was working last couple of days and today suddenly stopped. No idea why


Feature request: include (optional?) thesaurus of names relating to the search

I think an (optional?) thesaurus of names relating to the search could be useful.
Is this something others are interested in?
e.g. npm-name -t breakdance could give:

freakout is avaliable
harlem-shake is avaliable

That's a fun idea. I like it.

Thank you @sindresorhus . I agree -- it is important to not break existing users' workflows!

@sindresorhus I have a PR here: https://github.com/sindresorhus/npm-name-cli/pull/23

If anyone wants to work on this, see the initial attempt and feedback in https://github.com/sindresorhus/npm-name-cli/pull/23.

If anyone wants to work on this, see the initial attempt and feedback in https://github.com/sindresorhus/npm-name-cli/pull/23.


[BUG]Wrong error code in Scroll Context limit error

When the max open scroll context is reached. We get Internal Server Error (500) error instead of Too Many Requests (429) error.
To Reproduce
Steps to reproduce the behaviour:

Set max_open_scroll_context to 0. (To easily reproduce the error)
curl --location --request PUT 'localhost:9200/_cluster/settings' \ --header 'Content-Type: application/json' \ --data-raw '{  "persistent":{      "search.max_open_scroll_context": 0  } }'
Create a scroll context in your test index.
curl --location --request POST 'localhost:9200/test/_search?scroll=1m' \ --header 'Content-Type: application/json' \ --data-raw '{  "query":{      "match_all":{}  } }'
Error with status code 500

We should get error with 429 code.

Thanks @shiv0408 we might need to throw OpenSearchRejectedExecutionException instead here
https://github.com/opensearch-project/OpenSearch/blob/7469bf6e2603dbdbb808b96f453b4349c5f1d87f/server/src/main/java/org/opensearch/search/SearchService.java#L658-L663

Resolved by #1054


[CARBONDATA-3426] Fix load performance by fixing task distribution issue

Problem: Load performance degrade due to task distribution issue.
Cause: Consider 3 node cluster (host name a,b,c with IP1, IP2, IP3 as ip address), to launch load task, host name is required from NewCarbonDataLoadRDD in getPreferredLocations(). But if the driver is 'a' (IP1),
Result is IP1, b,c instead of a,b,c. Hence task was not launching to one executor which is same ip as driver.
getLocalhostIPs is modified in current version recently and instead of IP it was returning hostname, hence local ip hostname was removed instead of IP address.
solution: Revert the change in getLocalhostIPs as it is not used in any other flow.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed? NA

[ ] Any backward compatibility impacted? NA

[ ] Document update required? NA

[ ] Testing done
yes, tested with 17 node spark clusters with huge data.
Load performance is same as previous version. [degrade was 30%]

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.  NA

@ravipesala , @kumarvishal09 : please check

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3500/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11771/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3705/

LGTM

LGTM

LGTM


Correctly describe the usage of the mangle option

I got the wording from upstream README. I assume we should do what they do?

:+1:   Same needs done for compress option.


Import 8e5e3a97de: Merge remote-tracking branch 'origin/master' (by Caitlyn)

This is an automated proposal to look at a commit made by Caitlyn and import it into Overte

Commit:
8e5e3a97de2bd1992a565af5b856a8da56c9bb23

Author:
Caitlyn

Date:
Thu, 12 Mar 2020 12:33

Merge remote-tracking branch 'origin/master'

Stats:

Filename
Stats
Lines
Added
Removed
Lines in blame

hifi_qt.py

6
2
4
⚠ 0

1 files
-
6
2
4
0

To work on this, please assign the issue to yourself, then look at the commit and decide whether this would be a good addition to Overte.

If the commit is useful, tag it with "Tivoli: Keep", and keep it open until it's merged.
If the commit is not useful, tag it with "Tivoli: Discard", and close it.
If the commit is not useful right now, but might be later, tag it with "Tivoli: Maybe later", and close it.
If it's hard to decide, tag it with "Tivoli: Discuss", and keep it open.

Useful commits should be submitted as a PR against Overte. Tag this issue in PR, so that it's automatically closed once the PR is merged.
You can cherry-pick this issue with this command:
git cherry-pick 8e5e3a97de2bd1992a565af5b856a8da56c9bb23

merge of hifi_qt changes


Custom RTCRtpTransceiver creating

This PR provides API for creating custom RTCRtpSender, RTCRtpReceiver and RTCRtpTransceiver and adding RTCRtpTransceiver to RTCPeerConnection.

Can you talk a bit about why this is necessary? The spec compliant API should be enough I think

In general, it provides more advanced ways for working with RTCRtpTransceivers. For example, in our project we need to pass the unique Interceptor for every RTCRtpSender.

@k0nserv it is ready for review

@k0nserv ping

For example, in our project we need to pass the unique Interceptor for every RTCRtpSender.

Out of interest why is this needed? This isn't something that Pion provides atm so I'm thinking maybe there's another solve for your use case

@logist322 Can you talk a bit more about why this requires opening up this API? You can still register custom interceptors via the interceptor registry


Add YARD docs

This pull request adds on a lot of new YARD documentation.

This pull request adds on a lot of new YARD documentation.

Due to the above, should PR title be:

Add YARD documentation #63

https://github.com/SonderMindOrg/sober_swag/blame/better-rdoc-documentation/README.md#L310
"Servant" link doesn't work.

@Riveascore to avoid this branch getting staler, I've decided to just slap the merge button — I think we should add further fixes to docs in much smaller, more easily-digestible PRs, so we can respond to feedback and such more effectively.

@AnthonySuper Sounds like the right call to me.


Updated installation instructions

Cleaned of the instructions
Added link to HACS website
Added link to the latest release (https://github.com/dvd-dev/hilo/releases/latest) Added step 2 of the installation process

Merci pour la contribution @maxyvon


some characters like < display incorrectly in asterisk links

See https://toadua.uakci.pl/##qDsXDRse8.

Fixed in 95f621b853d23d1a430522d9ac923060d6726e9c.


Show loading BPS instead of 0

when i first load the page it says that 0 BPs have joined the alliance

@xavier506 a solution to this loading time is to move the bps joined the alliance data to the backend and fetch it from there, what do you think of the approach?

I think it could be a good idea if it dosent require too much more work


Search PDF for phrases and terms simultaneously

https://mozilla.github.io/pdf.js/web/viewer.html
Configuration:

Web browser and its version: Chrome
Operating system and its version: Windows 10
PDF.js version: Current
Is an extension: No

Steps to reproduce the problem:
I am trying to search tracemonkey for "Dynamic languages", "Google Docs", and JavaScript at the same time. How would I construct my URL? This used to work in #5496. Could someone post an example? I tried everything- must not work. Thanks.
What is the expected behavior? Words should be highlighted
What went wrong? Words not highlighted
I contributed 100+ hours to the original PR.

Instead of honoring the double-quotes in the #search it just strips them out. By parsing the terms correctly in the match array (viewer.js) it works perfectly. I made it work correctly in my tests by adding one line of code.

calcFindWordMatch: function PDFFindController_calcFindWordMatch(
query, pageIndex, pageContent) {
var matchesWithLength = [];
// Divide the query into pieces and search for text on each piece.
var queryArray = query.match(/\S+/g);
var subquery, subqueryLen, matchIdx;
  for (var i = 0, len = queryArray.length; i < len; i++) {
    subquery = queryArray[i];
    subqueryLen = subquery.length;
    matchIdx = -subqueryLen;

    **//check for equal-sign delimited phrase (supported in #5496)
    //parsing dbl quote phrases will require an additional loop
    subquery = subquery.replace(/\=/ig, ' ');**

    while (true) {
      matchIdx = pageContent.indexOf(subquery, matchIdx + subqueryLen);
      if (matchIdx === -1) {
        break;

There is no intent to extend functionality of the #search= for compatibility with other readers. (However internal search engine PDFFindController API can be modified to to perform better search queries, but it shall not regress existing functionality)

You would certainly want to highlight a set of phrases just as you would want to highlight a set of terms. I believe that functionality is currently broken. Only one phrase at time can be highlighted. The fix is rather trivial.

@mainseq is the snippet above still working for you?  I need the exact same thing. it's probably not the best performancewise, but for the time being in a POC I'm doing, i'm just taking an array of terms and phrases and encodeURIComponent['Dynamic Languages', 'Google Docs', 'Javascript'].join(' ') and using that as the search.

but yeah I agree, having a way to have multiple terms/phrases would be awesome.

After reading posts going back a number of years, can you still not search for phrases and terms via the #search parameter?
Is there any fork or PR that has this working? As with you @mainseq - I need it for a resume display feature where users search for phrases and terms within a search string.

Actually, mainseq's fix above still works. Just add that line in as above into calcFindWordMatch in viewer.js and then you pass the search term in as normal, but join phrases together with equals, i.e. Dynamic=Languages Google=Docs Javascript
This is so trivial its shocking that its still not fixed.

We are trying to find the exact search in pdf.js however we are not able to locate the search because the pdf is loaded with double space in between two words.
Kindly help with the solution how can we ignore two spaces or can add the space in text while searching Exact word.

Not sure if that helps, but I struggled to figure out how to pass one complete phrase, not multiple phrases. So maybe I'm not the only one coming to this thread, searching for an answer.
pass 'search' parameter AND pass 'phrase' parameter set to 'true' like:
/web/viewer.html?file=/pdf/book.pdf#search=Staatsrat%20der%20VR&phrase=true
Without 'phrase' being set to 'true' there will only be results that match any of the word in the phrase.
It may take a while to display the result (depending on PDF size), but it will show the exact match for the phrase searched for.
The Option is not listed under Viewer options in wiki

I want this feature implemented so bad !!

@stevechilds https://github.com/mozilla/pdf.js/pull/11749 I thik it won't be accepted, though :(