Fast text espanol

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f12e909). Click here to learn what that means.
The diff coverage is 66.66%.

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   96.77%
=========================================
  Files             ?        4
  Lines             ?       93
  Branches          ?        0
=========================================
  Hits              ?       90
  Misses            ?        3
  Partials          ?        0

Impacted Files
Coverage Δ

src/fasttext.jl
97.05% <ø> (ø)

src/Embeddings.jl
100% <100%> (ø)

src/glove.jl
92% <60%> (ø)

Continue to review full report at Codecov.

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


netty-4.0.27.Final  compile error for cannot import netty-tcnative lib

I download the netty-4.0.27.Final version by git, but after build project, the netty-handler project has compile error, like following:

is my local mavne repository setting problem or others problem??

What OS ?

windows7

@stoneCrystal 64bit or 32bit ?

import org.apache.tomcat.jni.Library;
import org.apache.tomcat.jni.Pool;
import org.apache.tomcat.jni.SSL;
import org.apache.tomcat.jni.SSLContext;

64

it seems like netty-tcnative  not import in project succesfully

@normanmaurer  how to fix is problem?

@stoneCrystal does mvn clean package works for you on the cmd line ?

@normanmaurer   mvn clean pakcage not work, following is the error message

I need the full output to see why it fails.

Closing as this need more info... Please ensure you have:
maven 3.1.1+
java 7+


Support quantum circuits on Device SV1 using boto3-1.27.0

Running the following PennyLane circuit,
import pennylane as qml

device = qml.device(
    "braket.aws.qubit",
    device_arn="arn:aws:braket:::device/quantum-simulator/amazon/sv1",
    wires=1,
)

@qml.qnode(device)
def circuit(x: float):
    qml.RX(x, wires=0)
    return qml.expval(qml.PauliX(0))
print(circuit(0.2))

works accordingly with boto3 v1.26 and throws a value-error with boto3-1.27.0.
Traceback including the error message:
  File "example.py", line 3, in <module>
    device = qml.device(
  File ".../python3.10/site-packages/pennylane/__init__.py", line 326, in device
    dev = plugin_device_class(*args, **options)
  File ".../python3.10/site-packages/braket/pennylane_plugin/braket_device.py", line 532, in __init__
    raise ValueError(f"Device {device.name} does not support quantum circuits")
ValueError: Device SV1 does not support quantum circuits

This may be an expected error message (due to some deprecation which I couldn't find any notes about) or an incompatibility issue with the plugin that requires a fix.
System information

Amazon Braket Python SDK v1.47.0
Amazon Braket Python Schemas v1.17.0
Amazon Braket Python Default Simulator version v1.16.0
Python v3.10

@maliasadi Thank you for reporting this. For now we ask that you pin your boto3 version similar to what has been done in https://github.com/aws/amazon-braket-sdk-python/pull/598/files. We are actively looking at a fix to allow newer versions of boto3 with the Amazon Braket Python SDK.


hierholzer algorithm not found

I am trying to implement the problem using python. When I try running the code, hierholzer is not found in network algorithms. Can you give me an solution ?

Oh! got it. Thanks. How can I get the results from gpx file ?

Thanks a lot. I am using this for my college project. Could you please say
how can I use this to obtain the results in the form of a gpx file?
Thanks in advance
On Sat, May 8, 2021 at 1:18 PM Matej Kerekrety @.***>
wrote:

I see, the issue is the Hierholzer algorithm isn't in networkx package,
but it is in matejker/network https://github.com/matejker/network, see
it in network/algorithms/eulerian.py#L33
https://github.com/matejker/network/blob/master/network/algorithms/eulerian.py#L33
.
The jupyter notebook is importing it from network.algorithms import
hierholzer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/matejker/everystreet/issues/9#issuecomment-835183715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7D77PZ34TNQF6DCTAXZRLTMTUGXANCNFSM44KWHEUQ
.


Meenu/Translation 379 meenu trustpiolet subtask

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

fixed in another branch


Unown the room when owner leaves room empty

When the owner leave the room and it becomes empty, lets unown it.
So that the next one join it can be the owner.
A not owned room is already assigned to users in:
https://github.com/yuumasato/have_you_heard_back/blob/8ecd8880d04e74474c0b936034e9c9328b9efb04/src/server/rooms.service.js#L148

This should fix the issue of unowned rooms reported in https://github.com/yuumasato/have_you_heard/pull/89


Add unitsConsumed field to RPC simulateTransaction response

Right now there is no unitsConsumed field in SimulateTransaction structure though API defines this field

thank you for bumping this one. solved in v1.28.0.


Ditch terminal size for libc

here be dragons, unsafe code is now in the codebase.
(and also merge conflicts)

nope im recreating the branch this branch is way too old


nuke: cleanup stale OpenStack resources

@zmc the general idea is to replace the scripts you currently have in your script directory.

@zmc repushed with the suggested changes :-)


Complaint progress bar on exercise dashboard always full

Describe the bug
On the general Assessment Dashboard the progress bar is shown correctly however if you enter the exercise specific dashboard it's always full.
To Reproduce
Prerequesites: Exercise with open complaints

Go to the Assessement dashboard
Check the complaint progress bar
Enter the exercise
See that the complaint progress bar is full

Expected behavior
The complaint progress bar matches the correct value
Screenshots
Shows the faulty bar at the top and the open complaints at the bottom

Shows the correct one on the dashboard overview

Environment

 - OS: Windows 10
 - Browser: Chrome v86.0.4240.111

Additional context
Make sure that the issue doesn't occure on the original assessment as well.

We noticed this for the EIST repeat GOE.

Probably a duplicate of #2124?

Indeed, my bad


fix(Search): Allow default action if there is no selected result

Currently, in the Search component, when there is no selected result, users cannot use the Enter key due to a misplaced call to "e.preventDefault()".
We should not stop the default action unless we actually do something.
This tiny PR will allow users to specify a custom onKeyPress action when there is no selected result.

Codecov Report

Merging #1742 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1742   +/-   ##
=======================================
  Coverage   99.75%   99.75%
=======================================
  Files         142      142
  Lines        2468     2468
=======================================
  Hits         2462     2462
  Misses          6        6

Impacted Files
Coverage Δ

src/modules/Search/Search.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Ah, nice catch.  Thanks much.

Released in<EMAIL_ADDRESS>


Trigger doesn't work when provided as a context in a Transition

Describe the bug
Using a trigger provided as a context and used in a child which is nested in a Transition does not work.
Leptos Dependencies
leptos = { version = "0.5.1", features = ["nightly"] }
leptos_meta = { version = "0.5.1", features = ["nightly"] }
leptos_router = { version = "0.5.1", features = ["nightly"] }
leptos_dom = { version = "0.5.1", features = ["nightly"] }

To Reproduce
#[component]
fn App() -> impl IntoView {
    let trigger = create_trigger();
    provide_context(trigger);

    create_effect(move |_| {
        set_interval(move || trigger.notify(), Duration::from_millis(500));
    });

    // If this line is placed above the create_trigger then the bug disappears.
    let stuff = create_resource(|| (), |_| async move { do_something().await });

    view! {
        <Transition>
            {move || {
                stuff
                    .get()
                    .map(move |_| {
                        view! {<CountDisplay/> }
                    })
            }}

        </Transition>
    }
}

#[component]
fn CountDisplay() -> impl IntoView {
    let (count, set_count) = create_signal(0);

    let trigger: Trigger = expect_context();
    // Increment the count when the trigger triggers
    let _ = watch(
        move || trigger.track(),
        move |_, _, _| {
            set_count.update(|count| *count += 1);
        },
        false,
    );

    view! { <span>{count}</span> }
}

async fn do_something() {
    // This timeout is needed, otherwise the bug disappears...
    // AND it needs to be more than the time set for the interval above (500ms)
    TimeoutFuture::new(600).await;
}

In this example, the count should increment every 500ms.
However, with this specific code it doesn't work. But if you change either:

Move the create_trigger below the create_resource
Set the TimeoutFuture to below the interval
Then the bug disappears and the code works correctly.

Expected behavior
The code should work no matter if the Trigger or Resource is created first.

This is kind of interesting. I wonder whether the example is both a little too complex for me to fully track what's going on, and to simple to reflect what's actually happening in an app.
The issue seems to be caused by <CounterUpdater/> running twice. Simply replacing
view! {
    <Transition>
        {move || {
            stuff
                .get()
                .map(move |_| {
                    view! {<CountDisplay/> }
                })
        }}
    </Transition>
}

with
view! {
    <Transition>
        <CountDisplay/>
    </Transition>
}

fixes the example. But I imagine such a simple fix is not available in the complete example.


Removes zfs from only the "new_kernel" installer variants

Fixes #58959.
This was tested using this patch to neuter the zfs kernel module.
nix-build nixos/release-combined.nix -A nixos.iso_minimal_new_kernel.x86_64-linux

and on aarch64
nix-build nixos/release-combined.nix -A nixos.iso_minimal_new_kernel.aarch64-linux

I wasn't able to think of an elegant way to reduce the duplication of the list of supported filesystems. Referencing to a configured value within the module system is an infinite recursion.  The only way I thought of is a bit ugly, is through having the list in a .nix file which would be imported (and filtered as needed). This would have made one bizarro file which would live within the other module files, but couldn't be added to imports.
Any inputs on ways to remove the mostly duplicated list?

If we remove zfs on these images we should either remove it from all install mediums or not at all since this is an invisible difference only waiting for users to trip on it and start getting confused.

I agree, this is a reason why this hasn't progressed further yet.

Another option would be to always use the latest Linux kernel compatible to zfs.

Sometimes they get EOL'd before the next is compatible. This means that we may have "new kernel" pointing to the LTS (e.g. 4.19 last not EOL'd version) sporadically.
This not something that is exactly under our control.
We really are between a rock and a hard place here, the kernel advancing, and zfs not being ready for stable yet for weeks at a time.

We may want to review the policy on including zfs on all installer media. We may want to make it only on the media we can support adding zfs to, meaning LTS.
While this may be confusing at first, we could be doing this by having those media:

installer_lts-kernel[_zfs]
installer_latest-kernel[_zfs]

Always specifying the kernel type in the media name, and always appending _zfs as a "feature" flag.
The only published variants would be:

installer_lts-kernel_zfs
installer_latest-kernel

This would at least reduce confusion about the features of the available media.
This example skipped over the _graphical feature flag that should also be considered the same.

installer_lts-kernel_zfs_graphical

How frequent is it actually that a kernel is EOL'd before ZFSonLinux adds support for it? And is it really completely unacceptable to use an EOL'd kernel?

As this is open for 2 years, it seems like we won't make this perfect but it's better to have a live image with the latest kernel without ZFS support rather than none?

I guess we could really go with the plan I previously proposed:

https://github.com/NixOS/nixpkgs/pull/59863#issuecomment-536208982

And deprecate the "unqualified" iso names. We could go with that scheme without producing all variants. E.g. produce only "lts+zfs", but (try to) produce "latest+zfs", and produce "latest+none".

Do we know that zfs is broken at eval time?
I haven't checked, maybe we have a meta.broken set to the last known good major kernel version to build zfs.
Though there is a fundamental UX difference in always producing the unstable image without zfs, and when possible producing the one with zfs: consistency. If the "same" iso image is produced sometimes with, sometimes without, it will be harder for end-users to really know whether the current unstable iso has zfs support. If instead there is always the "unstable without zfs support" variant, and sometimes the additional "unstable with zfs" variant isn't built, the messaging stays more consistent.
So even if, at eval time, we can know zfs support is present or not, we shouldn't arbitrarily change the supported features of the published unstable iso.
Does that make sense?

Do we know that zfs is broken at eval time?
I haven't checked, maybe we have a meta.broken set to the last known good major kernel version to build zfs.

No way to ensure that, but ZHF does end up marking it as broken.

Though there is a fundamental UX difference in always producing the unstable image without zfs, and when possible producing the one with zfs: consistency. If the "same" iso image is produced sometimes with, sometimes without, it will be harder for end-users to really know whether the current unstable iso has zfs support. If instead there is always the "unstable without zfs support" variant, and sometimes the additional "unstable with zfs" variant isn't built, the messaging stays more consistent.
So even if, at eval time, we can know zfs support is present or not, we shouldn't arbitrarily change the supported features of the published unstable iso.
Does that make sense?

Makes sense, although the expectation that you need to use another image for zfs is an UX issue itself (and the fact that currently users are used to zfs being part of latest kernel) so there's no ideal solution.
Either way, whatever gets us this fixed sounds good to me.

We're losing users due to this bug: https://twitter.com/KirinDave/status/1439053837914968068

Can you point out to me what's the breakage in his case?  I see lots of green for new_kernel ISOs: https://hydra.nixos.org/job/nixos/trunk-combined/nixos.iso_minimal_new_kernel.x86_64-linux
but they also wrote

I'm not confident in setting up NixOS without a gui
which would mean graphical ISO (right?) but we don't even have those with new_kernel and they're channel-blocking 🤷🏽

Ah, perhaps you meant the fact that we don't have new_kernel ISOs on 21.05 anymore due to ZFS?  (combination mentioned in Graham's blog post)

The current code knows compatible version combinations and sets meta.broken based on that.  I believe that should work automatically on kernel updates, etc... so perhaps include it in default based on that?  (as suggested by SamuelDR)

The only other way I can see (that haven't been mentioned) is to use kernel that's not latest upstream but a bit later which hopefully has such issues resolved (also nvidia is often reported).  But that seems too complicated to me; arguably I don't personally care for those cases prone to breaking.

I don't see why ZFS should get special treatment, if it doesn't work on the latest kernel it should just be disabled. There are other uses of an OS than using only ZFS and latest kernel is important for newer hardware - laptops.
We could have another image with zfs and latest compatible kernel, but that's really another issue beyond fixing new_kernel.

Well, I personally don't mind removing ZFS from new_kernel ISOs (unconditionally).  Using meta.broken just seemed like a cheap compromise.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/package-zfs-kernel-2-0-5-5-14-5-is-marked-as-broken-refusing-to-evaluate/15139/11

Another option not mentioned above would be to use zfs.latestCompatibleLinuxPackages (which exists already), i.e. for new_kernel images use possibly a slightly older kernel.
Yes, it would be a special treatment for ZFS.  I don't use ZFS myself, but I can understand it's hard to install with ZFS on newer HW without some image like this – such argument does not hold in other cases like nvidia drivers AFAIK.

I will leave my current thoughts about a solution:
Re-think image generation with "features"; we currently have two features:

new_kernel
zfs

We do not need to build all features combinations. Adding features should be done only when absolutely needed.
A generation needs the following two "feature sets" to pass to advance:

[ zfs ]
[ new_kernel ]

And these installer image feature sets will be tried to be built (exhaustively)

[ zfs ]
[ new_kernel ]
[ new_kernel zfs ]

The website can only directly link to the iso images with feature sets required for advancing. (But we don't necessarily need to link to the new kernel image directly.)
The website could link to a generated page (generated by the channels script, which already copies the iso) with a list all of the built images. Images not built could (should?) provide a short blurb explaining why they aren't built (do we have that info from the Hydra build attempt, or eval?). (This generated list of images could also include other more "exotic" images like aarch64 iso and sd cards in the future.)
As for naming, nixos-XX.YY-${concatStringsSep "-" features}.iso (and similar for SD card images).
Anything missing? Anything unclear?

I give up, no one else is getting sniped into fixing this. I took the time to fix this.

https://github.com/NixOS/nixpkgs/pull/207371


revert fix shellcheck error

 Here is an overview of what got changed by this pull request:

Coverage decreased per file
===========================
- application/consumer-rabbitmq-quarkus/src/main/java/webapp/tier/service/RabbitmqDeliverSubscriber.java  -31

See the complete overview on Codacy


AppCenter step doesn't work

I set all variables in this step but it doesn't work.

I recommend upgrading to v1.0.3
The script will always (AFAIK) output an error message prior to exiting, even for missing required variables.
Try setting the APPCENTER_API_TOKEN to TestApiToken and see if you get a success message.


jsx documentation + example

@paldepind / @mightyiam want to give me a review pass ?

kind ping @paldepind ^

I do not feel comfortable with having an built artifact checked in to version control. I don't like that. Could we avoid that, please? How about deploying to some service, instead? How about https://zeit.co/ ?

The rest of the examples had built files, so I followed convention.
I do like that examples are hosted by github as flat files and are in the repo. It’s close to rest of other documentation and we don’t have to depend on another third party.
I’ll make the other changes.
Re JSX example: I wanted to have something neat and fun with function components. Not too complex but enough to show how a great performant app could be built. I was going to go with something like TodoMVC but this seemed simpler and more fun to look at.
Happy to take proposals
Will open another PR to move jsx-globals.d.ts to repo root and keep this pure documentation.

But that being said I’m debating with myself whether JSX even makes sense. I feel @paldepind was right. We aren’t changing the h function (except handling null)
This feels like increasing surface area and could belong to another module, where the pace of improving it is much faster. I’m working with Typescript folks to land jsx fragment support and it feels supporting JSX could be an ongoing thing.
If you’re okay @mightyjam, I think we should revert the existing JSX PR and only leave the simple null handing change in there.
With the null change h function will still support jsx out of the box with children in array. So all is not lost.

:+1: to ignore compiled example files.

Pending #497 .

Re JSX example: I wanted to have something neat and fun with function components. Not too complex but enough to show how a great performant app could be built. I was going to go with something like TodoMVC but this seemed simpler and more fun to look at.

I think that is fine and in line with the existing examples. They aren't completely stripped down but actually, somewhat, pleasant and fun.
I think having the build files is fine given that the other examples currently also have build files. One could argue that having prebuilt files makes it easier for someone to take a quick look at the example. But, one could also argue that having build files in git is annoying. In any case, I think that should be discussed in a different PR/issue and this PR can follow the current convention until then.

@mightyiam ready for another pass. NOTE: it depends on merging #502 before though. When that lands I want to update TSX Clock example to use sel shorthand which makes things more readable.

@mightyiam another review pass here please.

kind ping @paldepind / @mightyiam ^

@paldepind would also love a pass from you on this PR.
Is there any chance you can guarantee us an SLA of minimum one review per week for PRs that need your approval to be merged and published.
What I assumed would take a week max has almost spanned for 3 months now.

This has been open for 6 months. I doubt @paldepind will ever come back to approve this. 6 months is ridiculous. Closing it.

@nojvek , I'm sorry about this situation very much.
I saw you extracted this functionality into https://github.com/nojvek/snabbdom-jsx-lite. That's very cool!
Let's add this information to ReadMe, @nojvek , @mightyiam ?

But now that I have permission to make decisions freely, we can merge in JSX properly.

Would love to merge in snabbdom. It’s mostly just one file.
It’s cool that @mightyiam has full permissions now. That’s cool.
I can open a PR to bring in the changes.

Please do, @nojvek. And feel free to contribute.

By 'contribute', I mean open pull requests. They will be reviewed.


As a build author, I would like to know where a given task is coming from

Expected Behavior
Given a task name, I would like to know which plugin or project or script the task creates it.
I am willing to query this myself through the CLI or Tooling API, or have this written in some other task's report.
Current Behavior
I do not have a "current" model way of determining provenance for a task. The best alternative I have is to guess by applying plugins and using the task report or a Tooling API query.
Context
I think we've known this to be a user need for some time, and tried to address this in different ways. I could not find an issue already for this, however.
I believe a significant percentage of users would benefit from this functionality, so even if we have a way to achieve incremental improvement, I imagine users would appreciate it.

This information is now in build scans


New branch2

Hi,
Your homework has been reviewed.
Great! Keep up the good work!
Best wishes from Automation Test Pro,
Khanh


💡[Feature]: Dementia disease prediction using Machine learning

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Dementia is a broad term for a range of conditions characterized by a decline in cognitive function severe enough to interfere with daily life. It encompasses symptoms such as impaired memory, reasoning, and communication skills, often accompanied by changes in mood and behavior. This project aims to predict the early dementia thereby user can get related remedial treatments at early stages.
I will do a complete data analysis ,EDA , data science steps , apply 4-5 ML models ,compare them and will build the web application for dementia detection using ML by using Streamlit library.
dataset link :
https://www.kaggle.com/datasets/timothyadeyemi/dementia-patient-health-dataset
Use Case
The machine learning model can analyze diverse health-related parameters and lifestyle factors to predict the onset of dementia, thus aiding in early diagnosis and intervention. It can also facilitate research by identifying potential correlations and patterns among various risk factors and dementia status, contributing to a better understanding of the disease.
Benefits
Early detection through this model allows for timely medical and lifestyle interventions, potentially slowing disease progression and improving patient outcomes. Additionally, the insights gained from the model can inform public health policies and preventative strategies, enhancing overall community health and resource allocation.
Add ScreenShots
none
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Avdhesh-Varshney @TAHIR0110 please assign this issue to me along with gssoc'2024 level and label .


ICE works on 1 account but not the other.

[09/17/17 21:05:16] 'NoneType' object has no attribute 'exe'
Traceback (most recent call last):
File "", line 45, in
File "", line 31, in main
File "c:\Users\Scott.Scott-PC\Development\Projects\Ice\build\ice\out00-PYZ.pyz\ice.rom_manager", line 40, in init
File "c:\Users\Scott.Scott-PC\Development\Projects\Ice\build\ice\out00-PYZ.pyz\ice.rom_manager", line 52, in is_managed_by_ice
AttributeError: 'NoneType' object has no attribute 'exe'
[09/17/17 21:05:16] ####################################
Latest issue.  Now its not due to the shortcut bug because I already deleted those both from my A and C steam files and inside of both accounts.  Currently my games transfer fine to 1 steam account but choose not to go to the other.
My config files and all are running correctly since they're just calling files, they're working and have nothing to do with the steam accounts directly.
Not sure what's wrong.

SRM works with all user accounts by default. #473


Update footer to have relevant content

User Story
As a user I can see the correct app description from the footer so I don't have to figure out what the app is about.
Discussion
Currently, the footer on the app has this appearance:

This is left over from the template repo used to create the app.   Instead it should say something like:

This app is a class project of CMPSC 156 at UCSB.  Check out the source code on GitHub!

Note that the links in the replacement text go to the correct places.
Acceptance Criteria

[ ] Footer should have a more accurate description about the app
[ ] Footer should link to the correct GitHub repo ( https://github.com/ucsb-cs156-w21/proj-ucsb-courses-search)
[ ] CMPSC 156 should link to https://ucsb-cs156.github.io
[ ] UCSB should link to https://ucsb.edu

Implementation Todos
Front end:

[ ] Change text and links in footer (in javascript/src/main/components/Footer/AppFooter.js)

Testing:
See testing hints below

[ ]  A new test is added to cover the UI change
[ ]  All previous tests still pass

Testing Hints
In file: javascript/src/test/components/Footer/AppFooter.test.js
This test will make sure that the indicated words appear and that they link to the correct places
 test("Links are correct", async () => {
    const { getByText } = render(<AppFooter />);
    expect(getByText('CMPSC 156').closest('a')).toHaveAttribute('href', 'https://ucsb-cs156.github.io')
    expect(getByText('UCSB').closest('a')).toHaveAttribute('href', 'https://ucsb.edu')
    expect(getByText('GitHub').closest('a')).toHaveAttribute('href', 'https://github.com/ucsb-cs156-w21/proj-ucsb-courses-search')
  });

branch name is set as 5pm-1-fixFooter.


Performance tests between original and fork

In my own testing, I found that my version of the tool actually got ~33% more frames than the original (120 FPS vs 180 FPS) which I call black magic. However, to prevent bias, I'd like some independent tests from people.
If you can, please try and run both the latest versions of the original Roblox FPS Unlocker and my version with the same settings (FPS cap set to none) and post your screenshots here. Use SHIFT+F4 to get your FPS. Note that you cannot run both at the same time as I and axstin prevent it, and even if I didn't they would conflict.
Thank you in advance. ❤

original tool the fps is between 120 and 140 at best

cpu usage from 0.00% to 0.08% the memory usage is 2.4 mb without the console the console adds 6.4 to 6.3 mb

size of the executable file

your tool the fps is between 120 and 140 at best

cpu usage from 0.00% to 0.05% the memory usage is 2.4 mb without the console the console adds 6.4 to 6.3 mb

size of the executable file

my own tool the fps is between 120 and 140 at best

cpu usage from 0.00% to 0.02% the memory usage is 0.5 mb without the console the console adds 6.4 to 6.3 mb

size of the executable file

note that my own tool doesn't use AOB scans its simply uses a pointer also it doesn't have any other features for example support for Roblox studio and the windows 10 version of Roblox from the Microsoft store

it shouldn't really have a difference between the fps in each of the tools its simply changing a value in memory
the only difference is in cpu/memory usage and executable size
for optimization u can try closing opened handel's

also lets be hones no one is going to use our tools anyway xD

Shrug, I mainly did this fork to help me learn C++ more and it has helped me learn a lot. I wonder why the original gave me less FPS -- maybe the CPU usage from it gave Roblox a slight performance hit and since my version has a lesser average CPU, whilst minimal, it might have affected my testing in that regard.

I wonder why the original gave me less FPS -- maybe the CPU usage from it gave Roblox a slight performance hit and since my version has a lesser average CPU, whilst minimal, it might have affected my testing in that regard.

Tbh i have no idea but if i have to guess maybe there was something running in the background that was using 3D hardware acceleration , maybe like discord or youtube idk .

I tried multiple times and got consistent results, maybe it's just a bug with the original on my machine or something? ¯\_(ツ)_/¯

yeh probably i dont get the Roblox devs tho like this should be a in game feature if u ask me bcs those tools are just changing a value in memory im sure that thing can be easily added in the game but still

Closing, guess it was just placebo.


Create Scene class and action models

First part of the new Theater API. This implements the student-facing Scene class which essentially just creates action objects for each operation.  This also allows us to do some small optimizations, such as converting file names to Image objects/sound sample arrays before storing the action data.
This also includes a small change to add a FILE_NOT_FOUND exception key for TheaterRuntimeException so we can throw custom runtime exceptions for FileNotFoundExceptions, because a requirement of the new Theater API is to not have students explicitly catch FileNotFoundExceptions.
JIRA: https://codedotorg.atlassian.net/browse/JAVA-487

I know a lot of this is boilerplate from the API spec, but is there any way to break this PR up?


gcc: tighten platform flags special-case for aarch64-darwin

The 4aa95e33121c316c5b34031bb08106d2dc113e38 commit added support for
aarch64-darwin but also ignored platform flags if the build platform
is aarch64-darwin. This leads to confusing errors such as
pkgsCross.raspberryPi packages compiled with soft-float even though
the platform supports hard-float (and is built as such on other
platforms).
The correct way to ignore platform flags is to check targetPlatform,
not the build platform. This change fixes that.
While we're here, tigthen the special-case to cover only the problematic
flags: -with-cpu and -with-arch.
Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Gentle ping.

@trofi may I ask for a review? I know this is darwin, but you've had good insights into gcc guts on my other PRs.
FWIW, this PR is the only missing piece for getting rid of darwin-builder in my project.

Conflicting files pkgs/development/compilers/gcc/common/platform-flags.nix

If you can resolve the conflict we can push it to master very quickly.

Done, thank you.

Done. This time I tested with
$ nix build .#gcc

not
$ nix run .#hello

🤦

Pulled as is. Thank you!


Send Test Requests over Socket and effects improvements.

Hi,
this is the actual improvement that i wanted to propose, and previous updates were only a prepartion steps. I would like to be able as GM, send requests for Tests to players. This way, a GM instead of saying 'Roll Perception' could easily open a test for given player and ask him to roll. Of course, its a minor improvment, however, for active effects it could open many new possibilities. There are many rules in the book saying "do this and that when test fails" and one example could be Cool Test on Blackpowder Weapon shoot:
if (args.test.weapon?.id == this.item.id) {
    if (args.test.data.context.targets && args.test.data.context.targets.length > 0) {
        let targets = args.test.data.context.targets;
        for(let i = 0; i < targets.length; i++) {
            let tokenId = targets[i];
            let token = game.canvas.tokens.get(tokenId.token);
            if (token) {
                let test = await token.actor.setupSkill("Opanowanie", { title: "Test Opanowania - Wystrzał z broni palnej",  absolute : {difficulty : "average"}});
                if (!test.result.outcome) {
                    await test.roll();
                }
                if(test.result.outcome == "failure") {
                    const html = `<div>${token.actor.name} Recieve @Condition[Broken] because of gunshoot.</div><div class="apply-conditions"><a class="chat-button apply-condition" data-cond="broken">Dodaj Stan Panika</a></div>`
ChatMessage.create({ content: html });
                }
            }
        }
    }
}

With this option enabled, this effect running on RollWeaponTest would open a modal dialog for character's owner and on fail - show message on chat to apply Broken, or even - automatically apply Broken.
There is also another change in philosophy here - the effect is always run in context of GM instead of a user. It has one disadvantage in context of few existing effects - whenever an effect shows a notification - it will be presented to GM instead of user.

Closing this due to the effect refactor, let's discuss reimplementing it with the new system.


Builds are broken on master

Recent PRs haven't had passing builds when they were merged, and now builds are broken on master: https://travis-ci.org/uber-common/node-kafka-rest-client/builds.

It is broken due to formatio cannot be found.
Local npm and tests are all fine.

@akshayjshah do you have any suggestion on how to fix/debug such server side package installation errors? It was broken for a while

I haven't looked at the failure in detail; this is (presumably) your team's project, so you own the CI and build process. If you're not sure what to do, please escalate within the streaming team or the larger data engineering org.

Fixed finally.


Update zio-config, zio-config-magnolia, ... to 3.0.1

Updates

dev.zio:zio-config
dev.zio:zio-config-magnolia
dev.zio:zio-config-typesafe

from 1.0.10 to 3.0.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #214.


[FLINK-14572][test] Print the root cause if job fails in BlobsCleanupITCase

What is the purpose of the change
Prints the root cause of the unexpected job failure for tests in BlobsCleanupITCase to help locate the unstable test failure.
Brief change log

d95e12bdcb570c4cbe5a37a9670d7427e8c461a1 prints the cause when job execution result is detected to be not successful.

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Thanks for opening this PR @gaoyunhaii. It would be helpful to identify the failure cause once BlobsCleanupITCase happens again.
The change looks good to me. Will merge it once travis gives green.

Merging.

Very thanks @tillrohrmann and @zhuzhurk for the review! :)


Dynamically decide upstream host in network filters

In my setup I have two network filters in my filter chain:

Custom network filter that in onNewConnection() has some logic to resolve a variable, say "dst"
TcpProxy filter

I have an upstream that exposes many endpoints, for each option of the variable "dst". For example:

x1.host.com
x2.host.com

Is there currently an option in Envoy to dynamically select between x1/x2 based on the resolution of "dst"? Meaning that if "dst" is resolved to "x1" then the tcp proxy will be routed to x1.host.com, similarly if "dst" is resolved to "x2" then the routing will be to x2.host.com
Thanks for helping!

cc: @KBaichoo

I think you can do dynamic cluster selection with tcp proxy: see https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/tcp_proxy_filter#dynamic-cluster-selection

@KBaichoo I didn't understand from the docs and the implementation what would be the value of the "cluster" field in the tcp proxy filter. Can you help with that?

@ohadvano
The key is defined here: https://github.com/envoyproxy/envoy/blob/ac91620f25b28fe83d9883757eb801171027fd19/source/common/tcp_proxy/tcp_proxy.cc#L41
And it is accessed here: https://github.com/envoyproxy/envoy/blob/ac91620f25b28fe83d9883757eb801171027fd19/source/common/tcp_proxy/tcp_proxy.cc#L156
I think you filter needs to setData() on the streamInfo on the Network connection using the given key with your filter to select the upstream: https://github.com/envoyproxy/envoy/blob/ac91620f25b28fe83d9883757eb801171027fd19/envoy/stream_info/filter_state.h#L130

I see, thanks. What if the clusters are unknown in advance and I would like to make use of the dynamic forward proxy cluster, could it work with that setup?

@ohadvano There are two mechanisms for unknown upstreams. DFP, like you said, which uses DNS to resolve a hostname. ORIGINAL_DST cluster which uses a known destination IP. For your use case, we use ORIGINAL_DST that programs it to use a header from :authority in HTTP CONNECT downstream, for example, in Istio.

Thanks @kyessenov, it seems like for using ORIGINAL_DST with override destination, I can either use http headers override or filter state override, but it seems like both can only be an IP address, can you confirm that?


You have requested a non-existent service

Hi,
After following the install instruction, I'm getting the following error when I try to display the admin :
You have requested a non-existent service "wandi.easy_admin_plus.acl.security.admin_authorization_checker".
Thanks in advance for your help,
Julien

Just realized it requires SF4 while I'm on SF3, so I think that might be it.. Sorry !

No problem


Fix operator precedence

All the binary operators are left-associative but there is no precedence between them. So the following function wont type well.
fn foo(x: Int, y: Int, z: Int) do
     x + y > y - z
end

Because it is parsed as ((x + y) > y) - z instead of (x + y) > (y - z). I don't have an strong opinion about having precedence between arithmetic operations. But I think that at least the precedence should be
(+, -, *, /, %) < (<=, >=, <, >, ==, !=) < (&&, ||)

So x + y > 0 && z > x + y should be parsed as ((x + y) > 0) && (z > (x + y))

Having equal precedence for + and * will be confusing. If you don't want * to bind tighter than +, then you should probably disallow mixing them without grouping parentheses.

Having equal precedence for + and * will be confusing. If you don't want * to bind tighter than +, then you should probably disallow mixing them without grouping parentheses.

Well at this point I suppose is better to do the whole thing if precedence is going to be introduced.

I believe this should be a valid testcase:
def loop() do
    if false do
        true
    else
        loop()
    end
end
true || loop()

should return true without diverging.


no data loaded

Warning: noob error probable!
My problem is that no data is loaded.
I built the dump using pouchdb-dump-cli. You can see a replicated copy of it here: http://<IP_ADDRESS>:5984/artendb/ae_objekte/ae_objekte.txt
It is a 340 MB file.
(the app is a CouchApp - so in order to serve the dump I attached it to a document - could there be something wrong with that?)
in app.js I set up the db like this:
app.extend({
  init () {
    this.localDb = new PouchDB('ae', function (error) {
      if (error) return console.log('error initializing local pouch ae:', error)
    })
  }
})
app.init()

In actions.js I'm setting up like this:
import PouchDB from 'pouchdb'
import pouchdbLoad from 'pouchdb-load'
PouchDB.plugin(pouchdbLoad)

I then do:
const url = 'http://localhost:5984/artendb/ae_objekte/ae_objekte.txt'
app.localDb.load(url)

or:
function filterFunction (doc) {
  if (doc.Typ && doc.Typ === 'Objekt') return true
  return false
}

const url = 'http://localhost:5984/artendb/ae_objekte/ae_objekte.txt'
const couchUrl = 'http://localhost:5984/artendb'
app.localDb.load(url, {
      proxy: couchUrl,
      filter: filterFunction
    })

No error occurs. But localDb remains empty.
I have also tried requesting the dump first using superagent (https://github.com/visionmedia/superagent):
request
  .get('http://localhost:5984/artendb/ae_objekte/ae_objekte.txt')
  .end(function (error, res) {
    // res.body is null!
  })

So no data arrived in the body?? This smells like some very nooby mistake to me.
I have added normal replication to take over after the load finished. This works - but ALL docs are replicated. I first thought it was because I had made a mistake with the proxy or the filter but it seems like it is because loading didn't work.

Did you try putting a .then() and a .catch() on your promise? If you just call db.load() it returns a promise, and any errors will be swallowed. I wrote more about promises here if that helps.
Did you check the network tab in the Chrome Dev Tools? Maybe CORS is not enabled on your server.
You can also try fetching your file through normal AJAX and then you can load() the string directly.

yes, I did put .then and catch. Here is more of the code:
Actions.loadPouchFromRemote.listen(function () {
  console.log('Actions.loadPouchFromRemote active')
  // get all items
  const couchUrl = getCouchUrl()
  const url = couchUrl + '/ae_objekte/ae_objekte.txt'
  app.localDb.load(url, {
    proxy: couchUrl,
    filter: objectFilterFunction
  })
  .then(function () {
    // let regular replication catch up if objects have changed since dump was created
    return app.localDb.replicate.from(app.remoteDb)
  })
  .then(function () {
    Actions.loadPouchFromRemote.completed()
  })
  .catch(function (error) {
    console.log('Actions.loadPouchFromRemote, replication error:', error)
  })
})

CORS is enabled.
I tried fetching the file through AJAX (using superagent) but got no data:
request
  .get('http://localhost:5984/artendb/ae_objekte/ae_objekte.txt')
  .end(function (error, res) {
    // res.body is null!
  })

I feel like this is the smelly fact.

meanwhile I found out this does work with files up to 340 MB but it still does not work with the original file which is not 340 but rather about 700 MB big (that is the only difference to the other files, as they are extracts of the big one). I guess I will have to split it up into smaller files.
Closing the issue as it does work with smaller files and I guess it is not a good idea to load 700 MB in one chunk into the browser

I use the --split option from pouchdb-dump-cli now to produce files of approximately 5 MB size. This now works very nice
Thanks for great tools!

Great, happy to hear it! :)


PouchDb support for Arcs Storage

Introduces pouchdb-adapter-memory at v7.0.0
Add a new manual test as pouch-db-tests.js
exports Model from CrdtCollectionModel, adds more detail on error messages
PouchDbStorage manages mapping from PouchDbKeys to actual database instances and replication.
PouchDbStorageProvider mimics the inmemory and firebase version of the same class.
PouchDbCollection supports reference mode and maintains a CrdtCollectionModel in Pouch.
PouchDbVariable introduces and maintains a new VariableStorage interface based on the _stored variable.
PouchDbBigCollection is unimplemented.
Adds some docs to StorageProviderBase
Adds PouchDbStorage support to StorageProviderFactory
Document shell query parameters to some extent.
Adds a build:typedoc target to help visualize datastructures

There are still ~29 TODOs in the code, and more to do.  You can test this manually
by adding a storage and torageKeyBase query param. Here's an example of using indexeddb:
http://localhost:8080/shell/apps/web/index.html?storage=1&storageKeyBase=pouchdb://local/mydb
And here's an example of using a remote server (which you can setup by following the instructions in server/README.md)
http://localhost:8080/shell/apps/web/index.html?storage=1&storageKeyBase=pouchdb://local/mydb

Sorry for the Big PR.  I'm still adding tests and more docs for README.md.

Thanks everyone!  addressed most comments and will sync and submit shortly.


proton transport part of simulation

@ziaber  Does it still work after your changes ?

Yes, if you are asking about BeamOpticsParams.cc change in geometry data directory, it seems that these methods were not used at all.


todo: add landing page

decided that the landing page should be part of my main website, which i will make some other time.


Include the Ubuntu suite of tools that support CNCF ecosystem technologies

Over the last few years, we have extended support of each of the following open source projects to support Cloud Native ecosystem at several different levels.  We are delighted to share and extend this vibrant ecosystem.
Please add the following logos to the ecosystem map sections:
INFRASTRUCTURE

MAAS: Metal as a Service.  MAAS is an open source project (AGPL) implemented in Python that automates bare metal provisioning of any Linux OS and WIndows, through a command line interface, a web interface, and an REST API.  Complex workloads like Kubernetes are easily deployed to bare metal machines with MAAS.
See: http://maas.io/
Logo: https://insights.ubuntu.com/wp-content/uploads/950d/maas-logo-text.png

PROVISIONING --> Infrastructure Automation

Juju: Service modeling.  Juju is an open source project (AGPL) implemented in Golang that provides a graphical and command line interface for modeling complex software deployments.  Charms of Kubernetes are part of the upstream Kubernetes source tree that enables deploying (day 1) and operating (day 2 - infinity) Kubernetes in a high availability configuration across any public cloud, private cloud, and bare metal.
  The infrastructure behind Snaps is open source (GPLv3) code implemented in Golang.  As of Kubernetes 1.6, all parts of the Kubernetes infrastructure are available as highly portable Snap Packages.
See: https://snapcraft.io/
Logo: http://people.canonical.com/~kirkland/snap.png

RUNTIME --> Container Runtime

LXD: LXD is a container runtime that runs general purpose operating system, able to boot dozens of Linux OSes, and provides an extremely efficient replacement for virtual machines for Linux-on-Linux systems.  LXD includes open source (GPLv2) code entirely upstream in the Linux kernel, as well as an open source (Apache) userspace daemon implemented in Golang.  High Availability Kubernetes deployed on Ubuntu uses LXD for clustering, efficiency, and snapshot/rollback upgrades.
See: http://linuxcontainers.org/
Logo: http://people.canonical.com/~kirkland/lxd.png

PLATFORMS

Ubuntu: Ubuntu is one of the world's most widely deployed operating systems, freely available, and widely used as the basis OS for cloud and container workloads, from Kubernetes to Cloud Foundry to OpenStack.
See: http://www.ubuntu.com/
Logo: http://people.canonical.com/~kirkland/ubuntu.png

OBSERVABILITY AND ANALYSIS --> Monitoring

Landscape: The Landscape client/agent is an open source (GPLv3) tool implemented in Python that provides deep OS and application monitoring and systems management at tremendous scale.  Landscape is intimately aware of containers and cloud native infrastructure and manages the security updates and compliance.
See: http://landscape.canonical.com/
Logo: http://people.canonical.com/~kirkland/landscape.png

If you need any of these logos rotated or in a different orientation (e.g. linear versus stacked), just ask.
Thanks,
Dustin

Bump?

Hi @dustinkirkland , we'll be including below in the upcoming release. Thanks.
MAAS: Bare Metal (new branch of Infrastructure)
Juju : PROVISIONING --> Infrastructure Automation
Snap - agreed to not include
LXD : RUNTIME --> Container Runtime : updating existing LXD logo
Ubuntu : PLATFORMS
Landscape - agreed to not include

Thanks @dustinkirkland, closing as these updates were included in the most recent version https://github.com/cncf/landscape#current-version


More data returned in the buffer than what the components indicate

Describe the Bug
Hi,
I am using a linear hyperspectral camera SpecimFX17.
When the binning is low (1 or 2), no issue is present. Although, when I try to set the binnings both for x and y to 8, Harvesters returns the following error
Traceback (most recent call last):
  File "/home/bota/Desktop/apic-bench/bota/specim_capture.py", line 236, in scan
    _1d = component.data.reshape(wavelength, x)
ValueError: cannot reshape array of size 2560 into shape (28,80)

And when I print the component height and width it says 28 and 80 respectively. Although, 28x80 is equal to 2240, not 2560.
When I set a lower binning (e.g. 4 for x and 4 for y) I get the same issue but with different values
Traceback (most recent call last):
  File "/home/bota/Desktop/apic-bench/bota/specim_capture.py", line 236, in scan
    _1d = component.data.reshape(wavelength, x)
ValueError: cannot reshape array of size 9216 into shape (56,160)

But when I set only one of the binnings high (e.g. x = 1 and y = 8 or x = 8 and y = 1) everything works perfectly.

OS: Linux Ubuntu 20.04.4
Python:  3.8.10
Harvester: 1.3.4
GenTL Producer: MvImpact 2.45.0
Camera: Specim FX17

@TouchTheFishy Hi, thank you for the report. Could you show me the output from the following code? It would be great if you could try to run the code with some binning settings:
ia.start()
with ia.fetch() as buffer:
   component = buffer.payload.components[0]
    attributes = ["width", "height", "x_offset", "x_padding", "y_offset", "y_padding"]
    for attribute in attributes:
        print("{}: {}".format(attribute, getattr(component, attribute, None)))
ia.stop()

Regards, Kazunari.

Hi Kazuna
Here's what I got:
BinningVertical = 8 , BinningHorizontal = 8:
width: 80
height: 28
x_offset: 0
x_padding: 0
y_offset: 132
y_padding: 640

BinningVertical = 4 , BinningHorizontal = 4:
width: 160
height: 56
x_offset: 0
x_padding: 0
y_offset: 132
y_padding: 512

BinningVertical = 2 , BinningHorizontal = 2: (This one works)
width: 320
height: 112
x_offset: 0
x_padding: 0
y_offset: 132
y_padding: 0

BinningVertical = 1 , BinningHorizontal = 8: (This one works as well)
width: 640
height: 28
x_offset: 0
x_padding: 0
y_offset: 132
y_padding: 0

BinningVertical = 8 , BinningHorizontal = 1: (This one works too)
width: 80
height: 224
x_offset: 0
x_padding: 0
y_offset: 132
y_padding: 0

Thanks for your help,
Paolo

Hi Kazunari (Sorry for misspelling your name in the last comment),
Your change seems to have done the trick
Thanks for the help!
Fishy

@TouchTheFishy Hi, thank you for the reply. You're welcome, I'm glad it worked for you (and I hope it does not break anything for the others, either). Regards, Kazunari.

Sorry to reply to a closed issue, but would you be able to share some more information about your environment and code @TouchTheFishy ? I am working with an FX10 and I can't get to the point of receiving any data from the camera. My code hangs when I try to call h.create() . I suspect it might be because I'm not sending the correct information about binning etc. ahead of time..


add name column to instruments-select and widget header

Fixes #456
Description
add name column to instruments-select
add name to widget header
Testing
add select-instrument widget
look at table columns
add orderbook
look at the header
Risk
No major changes
Do you agree with those?

[] I agree to follow the Contributing guidelines
[] I agree to follow the terms of the Code of Conduct

Добавленное поле не обновляется:
XT4mYnaEFa.mp4

fixed


[WIP] Pytorch v1.2

Main issue is uint8 / bool.
unit tests are passing, except checkpointer test: had to modify since the expected behavior of nn.DataParallel has changed.
Feel free to add any modifications

I was wondering if it would make more sense to dynamically check pytorch version, and choose torch.bool or torch.uint8, so that the code remains backward compatible, and fewer nasty surprises when updating codebase/pytorch? Could be done with a simple helper function mask_dtype():
import torch
from maskrcnn_benchmark.somewhere import get_version

def mask_dtype():
    major, minor = get_version(torch)[:2]
    if major >= 1 and minor >= 2:
        return torch.bool
    else:
        return torch.uint8

and put this helper function in somewhere:
def get_version(module):
    version = getattr(module, '__version__').split('.')
    parsed_version = []
    for v in version:
        try:
            v = int(v)
            parsed_version.append(v)
        except ValueError:
            parsed_version.append(-1)
    return parsed_version

This can also be used to dynamically control the place we call scheduler.step(), whose behaviour changed in pytorch 1.1.

I like the idea, but I think the same amount of effort would be more useful in adding a few convenience features in detectron2.
There are a lot of stuff still here waiting for cleanup, also detectron2


Run unit tests for master_v8.1 with the Intel -ftrapuv option.

Development for #1139 revealed a sporadic runtime abort when writing NetCDF output files.  The most recent example was with gen_vx_mask (see below) but when rerun, it completes without error.
This task is to compile the master_v8.1 branch with Intel using the -ftrapuv option and then run the full set of unit tests.  The hope is that this problem will become repeatable and easier to dubug, assuming it has to do with an uninitialized variable somewhere.
/d2/projects/MET/MET_development/MET/met/share/met/../../bin/gen_vx_mask
/d2/projects/MET/MET_development/MET/test_output/gen_vx_mask/DATA_APCP_24_mask.nc
/d2/projects/MET/MET_development/MET/met/share/met/poly/LMV.poly
/d2/projects/MET/MET_development/MET/test_output/gen_vx_mask/POLY_PASS_THRU_APCP_24_LMV_mask.nc
-type poly -value 10 -v 2
DEBUG 1: Input File: /d2/projects/MET/MET_development/MET/test_output/gen_vx_mask/DATA_APCP_24_mask.nc
DEBUG 1: Mask File: /d2/projects/MET/MET_development/MET/met/share/met/poly/LMV.poly
terminate called after throwing an instance of 'netCDF::exceptions::NcEdge'
what(): NetCDF: Start+count exceeds dimension bound
file: ncVar.cpp line:1614
Aborted

The master_v8.1 was compiled with Intel using the -ftrapuv option.  Unit tests were run, excluding the tests for mode graphics and python embedding.  The tests ran successfully until running "regrid_data_plane_GOES_16_AOD_TO_G212", when a segmentation fault was produced.  The log file can be found at dakota:/d2/jpresto/MET/MET_test_output/unit_test.log
/d3/projects/MET/MET_intel_testing/MET-master_v8.1/met/share/met/../../bin/regrid_data_plane
/d3/projects/MET/MET_test_data/unit_test/model_data/goes_16/OR_ABI-L2-AODC-M3_G16_s20181341702215_e20181341704588_c20181341711418.nc
G212
/d2/jpresto/MET/MET_test_output/regrid/regrid_data_plane_GOES_16_AOD_TO_G212_compute.nc
-field 'name="AOD";  level="(,)";'
-qc 1,2,3 -method MAX
-v 1
DEBUG 1: Reading data file: /d3/projects/MET/MET_test_data/unit_test/model_data/goes_16/OR_ABI-L2-AODC-M3_G16_s20181341702215_e20181341704588_c20181341711418.nc
Segmentation fault
ERROR: /d3/projects/MET/MET_intel_testing/MET-master_v8.1/test/perl/unit.pl unit_regrid.xml failed.

John ran this case through the debugger.  And was able to replicate the error Julie got.
However, Howard is right.  This error is due to an uninitialized boolean on line 671 of regrid_data_plane:
bool has_coord_input;
And that line has already been corrected by another branch of master_v8.1:
bool has_coord_input = false;
John will pull the tip of the master_v8.1 branch, recompile with Intel, and rerun the unit tests.

All of the unit tests ran without problem using the tip of the master_v8.1 branch with Intel 15.0.2 20150121 and the -ftrapuv option.  Closing this issue.


Fix broken PeerForwardingProcessingDecoratorTest by casting object

Description
One of our tests is broken.
Sample failure:
https://github.com/opensearch-project/data-prepper/actions/runs/3069628849/jobs/4958500535
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

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

Codecov Report

Merging #1777 (e68d77c) into main (e94d91a) will decrease coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #1777      +/-   ##
============================================
- Coverage     94.11%   94.05%   -0.07%
- Complexity     1423     1424       +1
============================================
  Files           187      187
  Lines          4180     4188       +8
  Branches        336      336
============================================
+ Hits           3934     3939       +5
- Misses          167      170       +3
  Partials         79       79

Impacted Files
Coverage Δ

.../dataprepper/peerforwarder/LocalPeerForwarder.java
100.00% <100.00%> (ø)

...taprepper/peerforwarder/PeerForwarderProvider.java
96.55% <100.00%> (ø)

...eerforwarder/PeerForwardingProcessorDecorator.java
100.00% <100.00%> (ø)

...dataprepper/peerforwarder/RemotePeerForwarder.java
86.00% <100.00%> (+2.27%)
:arrow_up:

...peerforwarder/server/PeerForwarderHttpService.java
97.77% <100.00%> (ø)

.../org/opensearch/dataprepper/pipeline/Pipeline.java
88.40% <0.00%> (-4.35%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


operator-sdk generate openapi omits field that contains numbers

What did you do?
Execute the command operator-sdk generate openapi using operator-sdk master branch.
The CRD Go specification contains the following struct:
type SystemFileStorageSpec struct {
	// Union type. Only one of the fields can be set.
	PVC *SystemPVCSpec `json:"persistentVolumeClaim,omitempty"`
	S3  *SystemS3Spec  `json:"s3,omitempty"`
}

This struct is not the Spec of the CRD itself nor its own CRD (it is not registered in the schema) but a field in the CRD spec.
What did you expect to see?
The YAML file of the CRD should contain s3 as one of the validation fields. Instead it does not appear.
I've observed that if I change the json field name from   json:"s3,omitempty" to   json:"sthree,omitempty" it is included in the .yaml validation section.
operator-sdk version: master branch

@miguelsorianod if this is indeed a bug it is in upstream kube-openapi, as we directly call that binary in generate openapi.

Check out this issue for more info: https://github.com/kubernetes-sigs/controller-tools/issues/139


Issues in RKE CIS 1.4 and 1.5 hardening guide

In this cluster.yml file: https://rancher.com/docs/rancher/v2.x/en/security/hardening-2.3.5/#reference-hardened-rke-cluster-yml-configuration
Actual:

# If you intend to deploy Kubernetes in an air-gapped environment,
# please consult the documentation on how to configure custom RKE images.
kubernetes_version: "v1.15.9-rancher1-1"
enable_network_policy: true
default_pod_security_policy_template_id: "restricted"

Expected:
# If you intend to deploy Kubernetes in an air-gapped environment,
# please consult the documentation on how to configure custom RKE images.
default_pod_security_policy_template_id: "restricted"
enable_network_policy: true
rancher_kubernetes_engine_config:
  kubernetes_version: "v1.15.9-rancher1-1"

In this rke template: https://rancher.com/docs/rancher/v2.x/en/security/hardening-2.3/#appendix-c-complete-rke-template-example

Actual:
#
# Cluster Config
#
docker_root_dir: /var/lib/docker
enable_cluster_alerting: false
enable_cluster_monitoring: false
enable_network_policy: false
#
# Rancher Config
#
rancher_kubernetes_engine_config:
  addon_job_timeout: 30
  ignore_docker_version: true

Expected:
#
# Cluster Config
#
docker_root_dir: /var/lib/docker
enable_cluster_alerting: false
enable_cluster_monitoring: false
enable_network_policy: false
default_pod_security_policy_template_id: "restricted"
#
# Rancher Config
#
rancher_kubernetes_engine_config:
  addon_job_timeout: 30
  ignore_docker_version: true

Also the following if present in the yaml file in kube-apiserver params, cluster fails to come up

extra_binds:

"/var/log/kube-audit:/var/log/kube-audit"

audit-policy-file: /opt/kubernetes/audit.yaml
admission-control-config-file: /opt/kubernetes/admission.yaml

kube-api - parameters should not include the following also as the cluster fails to come up

encryption-provider-config: /opt/kubernetes/encryption.yaml

The following has to be added
event_rate_limit:
        enabled: true

After discussion with @paraglade this 1. in this issue -- https://github.com/rancher/docs/issues/2368#issue-585363749 is NOT an issue. it is as expected.


main sf logo in the top, remove the space and make clickable to go back to main page?

read title

Yeah should be good, will add soon.

Alr, gonna go to my house and create a pull req that makes the issue.

thanks @efenow!


Update product details page to display video when available

Utilize the new video and preview thumbnail image URLs from the AppData definition update to display a playable video on the product details screen when one is provided in the data

Done in 4.1.0


Annoying Broken Character

Hi,
I am getting this character '☰' to not render properly for some reason, when running MacVim (in GUI mode). It renders as '[?]' Is there a way to fix that? It is not like that in iTerm2 or Alacritty (non-gui mode). Here are some more images:
Working nicely:

Broken :(

Font is the same in both cases:
DroidSansMonoForPowerline:h11
OSX, ElCapitan, MacVim binary release (151)
Thanks.

I use a different font, Fira Code Light:h12. I've tried Fura Code, but they broke many important things for me.

Hi @eirnym, thanks for your interest in this topic. I am not sure if this is a font issue. I tried different fonts etc, it might be some cache somewhere, cause the problem does not go away with new MacVim snapshots etc. I mean, this might be related to the OS, some MacVim font or glyph cache somewhere on the OS. Any ideas?

I have following image on my macOS Sierra (10.12). I use the same font for both terminal and GUI MacVim
In GUI:

In terminal:

:( I really do not want to upgrade to Sierra, might break a lot of stuff for me. But, eventually will happen.

Have you tried this font?

Hi, sorry for the delay. I have tried your font also tried flushing the font caches etc. Nothing has worked. Tomorrow, I might have to install macOS Mojave, I hope that fixed it.
Unless there is some kind of a MacVim specific font cache somewhere.

Good luck with Mojave (looking for Mojave-related issues in MacVim)

@cryptoeraser Updates on this? Did you update? I couldn't repro on Mojave as well, but if this is still an issue for you I could find a way to repro.


[Bug] NX command with Maven not executing for some reason, gradle seems to be working

Plugin Name
@nxrocks/nx-spring-boot
Nx Report
Node   : 20.12.2
OS     : linux-x64
pnpm   : 9.0.6
nx             : 19.4.2
@nx/js         : 19.4.2
@nx/workspace  : 19.4.2
@nx/devkit     : 19.4.2
@nrwl/tao      : 19.4.2
typescript     : 5.5.3
Registered Plugins:
@nxrocks/nx-spring-boot
Community plugins:
@nxrocks/nx-spring-boot : 10.2.1
Expected Behaviour
Execute any command, server, build, format etc to run as expected or as normal
Actual Behaviour

The command just hangs, nothing is executed.
Steps to reproduce the behaviour

Create maven project
Add any spring boot dependancies/none
Run desired nx command

Hi @Divaaaaaan
Thanks for using the plugin.
Can you elaborate about the issue you are having? provide the error stacktrace  and the exact reproduction steps;
So far, I was NOT abble to reproduce the errror when creating a spring boot app with the latest v10.2.1...

Never mind,  I misread your original post. Indeed I can see/reproduce the issue now.
Will try to provide a fix.
Stay tuned!

Hi @tinesoft
Awesome thanks, I did try checking the package itself but was unable to find anything so I just ended up using the standard mvn commands for now.

No worries, I have identified the issue :-)
The fix is in progress. It should be released very shortly


Major framerate drop when controlling a vehicle

On one of the maps I'm working on, controlling vehicles by selecting the engine causes major framerate drop. I'm not sure why this is, but it could be something to do with the fact that the wheels seem to have multiple sets of tracks attached to them? This only happens outside of the map editor, as the extra set of tracks and fps drop are both nonexistent there.
Also, it looks like you can't see the framerate going down in the video, but the portions where the video goes fast or stops completely are when it happens.
https://github.com/InfernoSuperNova/forts-wheels-mod/assets/134165959/0812e355-0dc9-43a3-ae0a-b4681d5ffe33

Can you please ensure you are on the latest version?

How do I guarantee that the mod is updated?


Dockerization

Advantages:

Tests
Easier "installation" for developers (and we could just say "See Dockerfile")
Tracks prerequisites

Disadvantages:

Slow as the hell

It looks like travis compatiblity done


Failing to parse binary

Conform is failing to parse my config file with this error:
Expected value of type `:binary`, got "$date $time [$metadata] [$level] [$message]\n"
That looks like a legit :binary to me.
Looking at the code it seems it's always expecting things to be wrapped in a list:
https://github.com/bitwalker/conform/blob/master/lib/conform/translate.ex#L321-L326
Applying the following patch fixes the issue locally:
index 84fe4c7..94dd83b 100644
--- a/lib/conform/translate.ex
+++ b/lib/conform/translate.ex
@@ -140,7 +140,7 @@ defmodule Conform.Translate do
         for {conf_key, value} <- results, not datatype in [:complex, [list: :complex]] do
           parsed = case value do
             nil -> default
-            _   -> parse_datatype(datatype, value, mapping)
+            _   -> parse_datatype(datatype, List.wrap(value), mapping)
           end
           :ets.insert(table, {conf_key, parsed})
         end

Damn, can't believe that was missed. Nice catch! I can make the patch myself, but if you'd like the credit, open up a PR with your patch and I'll merge it right away. Thanks!

Glad I could help, thanks for the amazing tooling work you've been doing!
https://github.com/bitwalker/conform/pull/137

I'll publish a new release this afternoon with your fix, thanks again!


Fixes tools/run_local_tests.sh by updating path for SIMPLE_KBS_DIR

Fixes tools/run_local_tests.sh by updating path for SIMPLE_KBS_DIR from $(dirname $0)/.. to $(dirname $0)../db.  This ensures that run_local_tests.sh will run after moving database sql definitions to db directory in repository.
Signed-off-by: Derren Dunn<EMAIL_ADDRESS>

This PR has no changes in it. Did Dov's PR make the same updates?

This PR has no changes in it. Did Dov's PR make the same updates?

Yes, indeed, #52 included this change (I had to have a working script to test sqlite).
We can either:

close this PR
use the chance and rename the SIMPLE_KBS_DIR variable (according the comment above).

I am ok with closing this PR since #52 already included it.

Ok. Sorry I didn't notice that when we were merging #52.


[WIP] Add Box widget schema for redwood layout

LGTM so far

Current dependencies on/for this PR:

trunk

PR #1521   👈

PR #1523

PR #1543

This comment was auto-generated by Graphite.


Doesn't working with electron forge (DLL initialization routine failed)

I'm trying to build an application with voice commands in electron, so i've made a test with picovoice packages for nodejs and it works well on default nodejs environment, but when i tried to use it with electron it gives me this error.
Error: A dynamic link library (DLL) initialization routine failed.
<EMAIL_ADDRESS>    at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:1822)
    at Module._extensions..node (node:internal/modules/cjs/loader:1354:18)
    at Object.func [as .node] (node:electron/js2c/asar_bundle:2:1822)
    at Module.load (node:internal/modules/cjs/loader:1124:32)
    at Module._load (node:internal/modules/cjs/loader:965:12)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
    at Module.require (node:internal/modules/cjs/loader:1148:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at <static_initializer> (D:\Projetos\elect-forge-test\node_modules\@picovoice\pvrecorder-node\dist\pv_recorder.js:23:26)
    at Object.<anonymous> (D:\Projetos\elect-forge-test\node_modules\@picovoice\pvrecorder-node\dist\pv_recorder.js:17:18)

Already tried to use eletron rebuild and electron forge to build the packages with DLLs, but still no progress.
So, it's possible to use it with electron? How do i achieve that?
package.json
{
  "name": "elect-forge-test",
  "productName": "elect-forge-test",
  "version": "1.0.0",
  "description": "My Electron application description",
  "main": "src/index.js",
  "scripts": {
    "start": "electron-forge start",
    "package": "electron-forge package",
    "make": "electron-forge make",
    "publish": "electron-forge publish",
    "lint": "echo \"No linting configured\""
  },
  "keywords": [],
  "author": {
    "name": "João Marcos Rocha Souza",
    "email"<EMAIL_ADDRESS>  },
  "license": "MIT",
  "dependencies": {
    "@picovoice/picovoice-node": "^2.2.1",
    "@picovoice/pvrecorder-node": "^1.2.0",
    "electron-squirrel-startup": "^1.0.0",
    "node-powershell": "^5.0.1",
    "node-speech": "^1.0.5",
    "speaker": "^0.5.4",
    "wav": "^1.0.2"
  },
  "devDependencies": {
    "@electron-forge/cli": "^6.3.0",
    "@electron-forge/maker-deb": "^6.3.0",
    "@electron-forge/maker-rpm": "^6.3.0",
    "@electron-forge/maker-squirrel": "^6.3.0",
    "@electron-forge/maker-zip": "^6.3.0",
    "@electron-forge/plugin-auto-unpack-natives": "^6.3.0",
    "electron": "25.4.0"
  }
}

It's expected as the Node.js SDK is explicitly built to function within the Node environment. For Electron or any browser-based environment, you might be able to use our web-voice-processor

@mrrostam I don't believe this issue should've been closed (although it's a bit too late now)

It's expected as the Node.js SDK is explicitly built to function within the Node environment. For Electron or any browser-based environment, you might be able to use our web-voice-processor

Electron has 2 processes: main and renderer. The renderer process is indeed a web environment, but the main process IS a Node environment so the above explanation is unfortunately incorrect. As a Node library, I fully expect pvrecorder to run in Electron's main process, just like all other Node libraries do.
I'm also trying to use this library inside of Electron and ended up on this issue before opening my own (my issue is a different one).
Note: It's likely not worth reopening this issue after a whole year but just thought I'd leave this comment here for reference.


Editing pages causes hookaborted error

The edit caused by the $abbrv command causes the bot to die, with the error "hookaborted". Figure out what this actually means, then figure out how to fix it.

This is caused by the Translate extension, and happens on all marked pages. I may need to use the other MediaWiki module for this, or just the api method directly.

I tried MediaWiki::Bot, and it was not erroring (when I told it to not error if the code is undefined). it then said it was a success, but never actually edited the page.

As of @792beb9 it no longer crashes. Now it just doesn't edit the page. I may need to use some other language for this particular command. Maybe I should generate a JSON file with the abbreviation and name, then use another language to perform the edit (JavaScript maybe?). Or maybe I could just use the web API to edit via WWW::Mechanize.

 Using Ruby for wiki stuff from now on. Will write some Ruby scripts for the existing MediaWiki commands.

Mostly fixed with new Ruby code.


on the board s32k118evb,    nuttx can not start up when power off and restart

I get one issue on the board S32K118EVB,    follow this steps :

use  ./tools/configure.sh -l s32k118evb:nsh  to build,   then get nuttx.bin
firmware has been burned to board S32K118EVB  (echo "loadfbin nuttx/nuttx.bin 0" |JLinkExe -if SWD -device S32K118 -speed 25000 -NoGui 1  )
some message will show up on the console LPUART0,  and it works well.
disconnect jtag  and power off the board
restart ,  then LPUART will get nothing

but firmware (example project) whilch build from IDE S32 Design for ARM follow steps 2,3,4, 5 can work properly .
:(  .     Hope to get some help.

Problem has been solved .   missing  ECC RAM Init at startup code .   refer to  https://github.com/apache/nuttx/blob/2f9c082f8f26a1abcc5484085f329040c7224fda/arch/arm/src/s32k3xx/startup.S#L39C1-L39C1


How to add a URI fragment with a hash mark # to routeLink?

I want to make use of type-safe routes using routeLink and I want the resulting route to look something like this:
https://www.palantype.com/patternoverview#patSimpleMulti
... making use of the # to scroll to an anchor within the document upon load.
How to do that (or something similar) in obelisk?

Something like this would be nice:
routeLink  (FrontendRoute_Foo :/ SubRoute_Bar :# "my-fragment") $ text "Click me!"

The tricky thing about the fragment is that it is generally not delivered to the backend as part of the HTTP request, and so if we added them to an application's abstract notion of the route, the backend could end up prerendering things in a way which was incongruent with the frontend's notion of what the route was meant to be.
On the other hand... maybe one/we could make something like routeLink but which just tacked on an arbitrary fragment without making it part of the formal route.


Implement Slug Cfgu Type

Suggestion
Add a Slug type to the Cfgu type system of Configu.
Using type: Slug in a ConfigSchema should enforce a valid Slug as a config value at upsert or eval.
{
  ...
  "CONFIG_KEY": {
    "type": "Slug"
  }
  ...
}

Motivation
Extending Configu's type system capabilities.
Context

https://github.com/validatorjs/validator.js
https://configu.com/docs/cfgu/
https://github.com/configu/configu/blob/main/types/Cfgu.ts
https://www.npmjs.com/package/slugify

I would like to be assigned to this issue

@michaldziuba03 go for it! 🥇


Please, update?

Lua could benefit from a up-to-date mongodb driver greatly.

Hi, I'm sorry to say we don't have any staff allocated to this project at MongoDB. Are you interested in contributing?

Actually, I am. Lua community has seem some growth with web development tools and a strong database library would do wonders to the ecosystem. How can I help?

Great, let me know what features you're missing and offer some pull requests for them.

This would probably be a good start: https://github.com/mongodb/specifications/blob/master/source/crud/crud.rst

Sounds good. I don't know Lua, which is why I'm not maintaining this now that the author has moved to a different company. But I'm happy to review your pull requests to the best of my ability and to merge them.


Add OpenMP reference card

What does this PR do?
Add resource(s)
For resources
Description
Add OpenMP cheat sheet.
Why is this valuable (or not)?
This cheat sheet is very helpful for developers working with OpenMP frameworks.
How do we know it's really free?
It's freely accessible to everyone.
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

It's usually not helpful to add a category for a single resource. Try to find another category, or see if there are other books in our lists that would fit into your category.
Put it with C/C++

Will do after this https://github.com/EbookFoundation/free-programming-books/pull/7729 merged.

Updated.

please resolve conflicts.

Resolved conflict.


grafana: 5.1.3 -> 5.1.4

Motivation for this change
Important security fix
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Cherry-picked to 18.03.


Bootstrap 5 theme incoming any time soon?

Hi there, i am rewriting the an old web app. I want it to be the latest at everyting, today i changed bootstrap 4 to bootstrap 5 and using select, some theme is messy.
Can we expect bootstrap 5 theme any time soon ?

Hi,
You can find a Bootstrap 5 compatible theme here: https://github.com/tagliala/select2-bootstrap4-theme/tree/feature/bootstrap-5
It is based on my work done on #67, so it requires Select2 4.1
(and don't upgrade jQuery to 3.6.0, as per select2/select2#5993)

Even tho it is compatible with BS5, it does not supports bootstrap's form-control-sm classes, which means we can't use *-sm classes with selects ( small selectboxes ). More here.

it does not support bootstrap's form-control-sm classes ( small selectboxes ).

Yes, this theme does not support small controls neither in BS4. Ref: #40

@martinbarilik just saw this in the Select2 repo: https://github.com/apalfrey/select2-bootstrap-5-theme
Demo doesn't work, but it looks like a complete theme with support for small and large classes

Holy moly, it's recent. Thanks, last i checked it wasn't any ( 2 weeks ago ).

@tagliala - Were you able to make that BS5 theme work for the small dropdown size?

@MarcPinnell please take a look at https://apalfrey.github.io/select2-bootstrap-5-theme/

I was never able to get that working. I did find a BS4 theme that I managed to get working yesterday. Not ideal, but it works.


Feature tags

Hello,
As already talked with 'guiton' on IRC channel, I implemented myself the TAG feature using the (still not used) tables:

TAG
TAG_FILE

The full requirement description is below.
Requirement

Add a TAG FEATURE in order to tag all the files in IRMA

A new scanned file should have no tags registered

When consulting a scanned file, user should be able to:

see the tags related to the file
add (+ remove) new tags to the file

When adding tag(s) to a file:

user must select the tag in a suggestion list
suggestion list is mapped on a table (IRMA TAG table)
user cannot register a tag which is not in the suggestion list in order to avoid tagging error (+ misspelling)
the tag list must be filtered with the user input dynamically

When searching in database, user should be able to:

search using new field: TAG
see the tag(s) in the datatable containing all the search results

Clean code, tests, so far so good. Could you just redo your PR but on testing branch this time.

Did a new PR to testing branch.
I close this PR.


Issue with bitwise & coming from floating point range numerical stability fixes

MWE:
using Enzyme
function f(y::Array{Float64}, x::Float64)
    ts = Array(0.0:x:3.0)
    y .= ts
    return nothing
end;
y  = zeros(13)
dy = zeros(13)
Enzyme.autodiff(Reverse, f,  Duplicated(y, dy), Active(0.25));

enzyme_error.txt

Dup of https://github.com/EnzymeAD/Enzyme.jl/issues/274


chore: Dependabot Merge

Instructions

PR target branch should be against development
PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/stable/.github/workflows/pr-title-check.yml
PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/stable/.github/workflows/pr-branch-check-name.yml

Summary

Dependabot merges

Testing Plan

{explain how this has been tested, and what additional testing should be done}

Master Issue

Closes https://go.mparticle.com/work/SQDSDKS-5198

Closing https://github.com/mParticle/mparticle-web-sample-apps/pull/495 due to merge/conflicts

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


[Feature] Dict specs in vmas

I had this feature in my fork for a long time and di not realize it was not in main.
This allows dictionaries as observations in VMAS

let's activate the vmas tests for this


Update the overall elements for the Cupcake website

chsanche created the following on Sep 10:
User story:

As a Digital Design System adopter

I need to see the correct website title, footer, and navigation on the Cupcake website

so that I know I am on the right website.
Additional information

Overall elements are such as the site title, footer, navigation, etc.
The current Gatsby theme for the Cupcake website can be viewed here

Deliverables

The overall elements for the Cupcake website are updated with code.

Acceptance criteria

[ ] The overall element updates are live and reviewed and approved by Jenny and Wonil.

Original issue: https://github.ibm.com/webstandards/digital-design/issues/1675

On Sep 30, chsanche commented:
@Wonil-Suh1 We need to talk to @Jeff-Chew on this issue and see if Sprint 19 is the proper sprint for the work to be started and set story point to this task issue.

On Oct 10, Jeff-Chew commented:
@Wonil-Suh1 @chsanche what updates are we adding here? We're not using the current header/footer from gatsby theme?


Update README.md

Thank you @mmeganos for the fix to our documentation
Welcome to the Rubix community


What is meant by conversion?

Hello,
I have been reading through the source code, and I can't seem to make sense of what conversion means. Does it simply refer to a celcius to fahrenheit conversion, or something else?

At the heart of the DS18B20 is an ADC - AnalogDigitalConversion - which measures the temperature as a voltage or current (analog) . This analog value is converted to a digital value (bits) and the more accurate bits you want the more time it takes. Roughly the time doubles for every additional bit (in its working range). This is also known as the conversion time.

Thanks!


MountWizzard 2 issue with Platesolving

Hi Michel
Switching from 10micron forum to here for issue posting.
Thank you very much for the time spent on my issue with mw2 and tsk. I know that mw2 is not the latest version and that you have more than enough to do with mw4 and probably other things . So if it is not easy to solve my issue with plate solving then we leave it, esp.if you dont have a w10 environment to test. I like your app because it has this imaging window that helps with the polar alignment.
So we leave it as is, i will check the usage of model creator 2 wo PA assistance. Thanks again for your time.
Marc

Issue solved, the plate solving issue was pure handling, version 2.6.1 includes a bug fix for the image windows, thanks a lot Michel!


Server issue

Can you guide me for running the server on local machine

Hi @yashsalvi , what is problem at your side?
You can find info here https://github.com/pararell/eshop_mean/blob/master/README.md
and here http://miroslavsmrtic.sk/blog/build_eshop_template_with_mean_stack_and_typescript___dev_and_prod_build
http://miroslavsmrtic.sk/blog/build_eshop_template_with_mean_stack_and_typescript___set_environment_variables_and_build_it
For the server you need mongoDB, that setting depends on your operating system. Or you can use https://account.mongodb.com/ and create free sandbox DB for dev purpose

I will try to use the sandboxDB right now.
I'm not getting how to use the local mongoDB setup which has a URI in .env file
I'm not able to get that URI.

It depends on the operating system, it is probably easier setup in Ubuntu that in Windows. Anyway, try mongodb.com sandbox DB and you will get link from there and that you can use in .env
MONGO_URI="mongodb+srv://username:password@yourclusterurl.mongodb.net/yourDBname?retryWrites=true&w=majority"


command not working

command not working / result on ubuntu 20.04

@medyes27 The extension requires fd as per the README. You can install fd (installed as fdfind in Ubuntu) with sudo apt install fd-find.

thanks. I have running well file search..


Can't update existing resource

  kubernetes:networking.istio.io/v1alpha3:VirtualService (kit):
    error: 1 error occurred:
        * the body of the request was in an unknown format - accepted media types include: application/json-patch+json, application/merge-patch+json, application/apply-patch+yaml

temporary deleteBeforeReplace: true helps to resolve the issue.

This doesn't appear to be a crd2pulumi issue based on what you've provided above? Do you mind providing more details on what's going on and how you expect things to work?

I've generated istio CRDs using crd2pulumi, if I change anything in the resource, getting such error:
  `${config.appName}-gw`,
  {
    metadata: {
      namespace: namespace.metadata.name,
      labels: deployment.spec.template.metadata.labels
    },
    spec: {
      servers: [
        {
          hosts: ['*'],
          port: {
            name: 'http',
            number: 80,
            protocol: 'HTTP'
          }
        }
      ]
    }
  }
);``

@leezen looks like the issue was not providing a custom provider for k8s. Closing.
P.S. Would be great to getter a better error description, missing provider inside args, confuses a lot!


Caleblatonia spotlight upload

Description
DESCRIBE YOUR PULL REQUEST'S CHANGES.  We made the spotlight upload page with all of the input fields and buttons.
Screen shots or GIFs of UI changes

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Part of a feature.
[ ] Refactor (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Testing-

Checklist

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ x] My changes generate no new warnings
[ ] added new dependencies
[ ] added tests
[ ] updated documentation
[x ] Looks good on large screens
[ ] Looks good on mobile

Organization

[ ] Have you linked this pull request to a project ticket?

Review

[ ] Is this a work in progress?
[ x] Is this ready to be reviewed?
[x ] Have you added two reviewers to this pull request?

 build spotlight upload form

Please address failing tests before I review

closing to pull agains dev


Read Recipe first then Replace string "${ }"

Read the recipe first then loop through yaml file and replace all of the strings containing "${ }"
Function that will need update: _load_recipe in recipe.py

@ChrisWRWX
Let me know if this is what you had in mind.
Code is working, it iterates over all values in recipe object and replaces all instances of ${ } with the corresponding value.
The code needs to be condensed as it repeats the same logic more than once.
See Replace-String-${} branch


calling this code multiple time on one device

Hello!
How this code supposed to generate unique id if you're using system boot time ? i suppose that every time when this code called on particular device, then different output is returned, right ?

System boot time will not be changed unless system reboot.

system reboot is not such a rare thing nowadays.. thanks for the buggy iOS and iPhone hardware. so, it seems like the output of this class is still not very reliable. But, we can at least save in keychains and use it on permanent basis..

If you want to track a device for a long time, we suggest you save idfv in keychains.  This code provide the same deviceID shared by different  APP at specific times.

that exactly my thoughts


TypeError: Cannot read properties of undefined (reading 'id')

TypeError: Cannot read properties of undefined (reading 'id')
    at Request._callback (C:\Users\User\Documents\Websites\MemberManager\API\node_modules\passport-patreon\lib\passport-patreon\oauth2.js:33:25)
    at Request.self.callback (C:\Users\User\Documents\Websites\MemberManager\API\node_modules\request\request.js:185:22)
    at Request.emit (node:events:513:28)
    at Request.emit (node:domain:489:12)
    at Request.<anonymous> (C:\Users\User\Documents\Websites\MemberManager\API\node_modules\request\request.js:1154:10)
    at Request.emit (node:events:513:28)
    at Request.emit (node:domain:489:12)
    at IncomingMessage.<anonymous> (C:\Users\User\Documents\Websites\MemberManager\API\node_modules\request\request.js:1076:12)
    at Object.onceWrapper (node:events:627:28)
    at IncomingMessage.emit (node:events:525:35)

{
  errors: [
    {
      code: null,
      code_name: 'OAuthClientViewForbidden',
      detail: 'You do not have permission to view OAuth Client with id REDACTED.',
      id: 'bcf806cb-01e1-580b-b3f8-ca9e72a74d61',
      status: '403',
      title: 'You do not have permission to view this OAuth Client.'
    }
  ]
}```

I have the same issue now when I use this library with my new testing Patreon account.
It worked fine with my "creator" account.
Any idea how to fix this? Maybe I'm just using a wrong scope?


OpenXR to support VR Compositor Layers extensions

In order to support VR Compositor Layers the following extensions need to be supported in OpenXR SDK:

https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#XR_KHR_android_surface_swapchain
https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#XR_KHR_composition_layer_cube
https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#XR_KHR_composition_layer_equirect2
https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#XR_KHR_composition_layer_cylinder

@Lixming @dingsing2021  please provide a feedback on this request ☝. Thanks.


Ensure that pdb is generated in release mode for win debugging

I have read and agree to the terms under CLA.md
Noticed that when kuzu_shared.dll is built in debug mode then somehow client app crashes at randomly at time during new or delete. It is not clear what is going wrong there. This change will at least generate PDB (debugging symbols) for release mode, while keeping the release mode DLL same as before. This will allow better debugging on windows.

https://www.atmosera.com/blog/correctly-creating-native-c-release-build-pdbs/
https://discourse.cmake.org/t/use-cmake-to-generate-pdb/2583
https://stackoverflow.com/questions/28178978/how-to-generate-pdb-files-for-release-build-with-cmake-flags

Noticed that when kuzu_shared.dll is built in debug mode then somehow client app crashes at randomly at time during new or delete. It is not clear what is going wrong there.

Are you also building the client app in debug mode? MSVC enables standard library data structure debugging for debug builds which adds extra fields to some classes such as std::string (see #2521), which means you can't safely pass some data in either direction without using the same debug definitions (and this actually includes the Database and QueryResult classes since they each contain a std::string).
Is the idea that you would like us to distribute debug symbols with the release builds, or is this for personal debugging use in release mode?
If it's the former, It would be useful to know how the size compares to the current release binaries.
If it's the latter, how does this compare to building using using the RelWithDebInfo configuration? I'm not sure if the data structure debug definitions are used in that mode, but that seems like it would be the best way of handling an optional release build with debug symbols (and if you want we could add an easier way of running such builds to the Makefile, but I think just using cmake -B <builddir> -DCMAKE_BUILD_TYPE=RelWithDebInfo && cmake --build <builddir> --config RelWithDebInfo works).
From what I understand from the docs, -Zi would require us to distribute the PDB files with the release dll:

If you create a library from objects that were compiled using /Zi, the associated PDB file must be available when the library is linked to a program. That means, if you distribute the library, you must also distribute the PDB file.

One of my dependencies is built with /MTd for Debug and /MT for Release configuration. I have to include them as shared libraries and not building from source.
When I forced /MTd to all my code and Kuzu, then I noticed the following warning when configuring kuzu (at configure stage and not at build).
Run Build Command(s): C:/PROGRA~1/Meson/ninja.EXE -v cmTC_544df
[1/2] C:\PROGRA~1\MICROS~3\2022\ENTERP~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\cl.exe  /nologo /TP   /Zi  /MTd -MDd /showIncludes /FoCMakeFiles\cmTC_544d
f.dir\CMakeCXXCompilerABI.cpp.obj /FdCMakeFiles\cmTC_544df.dir\ /FS -c G:\tools\cmake-3.29.0-windows-x86_64\share\cmake-3.29\Modules\CMakeCXXCompilerABI.cpp
^M
cl : Command line warning D9025 : overriding '/MTd' with '/MDd

I also inspected build/compile_commands.json for kuzu and noticed that -MDd is automatically injected although I dont remember setting it. Is there a cmake configuration in kuzu which depends on /MDd for Debug and /MD for Release?

Conclusion 1:
I found out that MSVC compiler automatically defaults to /MD or /MDd, so I do get warnigs about overriding /MDd with /MTd if I set CMAKE_CXX_FLAGS to /MTd explicitly. For MSVC it is better to set CMAKE_MSVC_RUNTIME_LIBRARY directly to "MultiThreaded$<$CONFIG:Debug:Debug>". This will alow correct usage of /MT or /MTd.
Conclusion 2:
I tested with /MTd build of kuzu_shared.dll and still memory deallocation in my application when allocation was done in kuzu_shared.dll fails in debug mode. This is despite /MTd used at both places. In the mean time I have switched to using C-API of kuzu and explicitly using the *_destroy functions provided by Kuzu C-API to free allocated memory. This is a bit cumbersome and has potential issues of missing this call, but for now relying on careful code review and creating a wrapper works. I will revisiting the memory allocation / free issue even with aligned C-Runtime on windows bit a little later.


Wrong camera position in the Ground Clamping example.

Open the Ground Clamping Sandcastle example. Switch to 2D or Columbus view and select either the point or billboard from the drop down. The camera reference frame is wrong.

Related #5042

Actually, this is definitely a the same problem as #5042
Closing as a duplicate