Unexpected behaviour for non-strictly monotonic values in scipy.interpolate.interp1d

I am having an issue with some unexpected behaviour with the scipy.interpolate.interp1d method for the following kinds:

kind= ['nearest','linear', 'previous' and 'next'] (i.e. kinds not involving spline interpolation according to the doc)

When providing non-strictly monotonic x values, unexpected results are returned rather than the method failing:
Reproducing code example:
import numpy as np
from scipy.interpolate import interp1d

x = np.array([0, 1, 1])
y = np.array([0, 1, 0])

for kind in ['nearest', 'linear', 'previous', 'next']:
    f = interp1d(x,y,kind=kind)
    print("{k}: ".format(k=kind), f(x))

Output
nearest:  [0. 1. 1.]
linear:  [0. 1. 1.]
previous:  [0. 0. 0.]
next:  [0. 1. 1.]

Error message:
For kind='cubic' it fails in a similar matter as I would expect it to for the others:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-30-064ad468e798> in <module>
----> 1 f = interp1d(x,y,kind='cubic')
      2 f(x)

C:\anaconda\envs\atlite\lib\site-packages\scipy\interpolate\interpolate.py in __init__(***failed resolving arguments***)
    533
    534             self._spline = make_interp_spline(xx, yy, k=order,
--> 535                                               check_finite=False)
    536             if rewrite_nan:
    537                 self._call = self.__class__._call_nan_spline

C:\anaconda\envs\atlite\lib\site-packages\scipy\interpolate\_bsplines.py in make_interp_spline(x, y, k, t, bc_type, axis, check_finite)
    797
    798     if x.ndim != 1 or np.any(x[1:] <= x[:-1]):
--> 799         raise ValueError("Expect x to be a 1-D sorted array_like.")
    800     if k < 0:
    801         raise ValueError("Expect non-negative k.")

ValueError: Expect x to be a 1-D sorted array_like.

Scipy/Numpy/Python version information:
[1]: import sys, scipy, numpy; print(scipy.__version__, numpy.__version__, sys.version_info)
1.2.1 1.15.4 sys.version_info(major=3, minor=6, micro=6, releaselevel='final', serial=0)

We have the right checks, but there's a subtle error in them somewhere. If I change your example to x = np.array([0, 1, 2]) instead of x = np.array([0, 1., 1.]) then things work fine.

The thing is with x = np.array([0, 1, 2]) we are again back to using a (strictly) monotonic x with which I don't have any issues :) . It's just about this border case of a monotonic but not strictly monotonic x where there is no error for some of the possible kind parameters.

@euronion sorry I tried a bunch of things and my comment was incomplete. Also x = np.array([0, 2, 1]) gives consistent results, it's just [0, 1, 1] with two identical elements that does't. The sorting of indices looks right; there's something special for duplicate x-values here.

With duplicate x values, the procedure is not well-defined. In the OP, what would the rwsult be at x=1: zero or one? Erroring out could be a reasonable choice: this would produce an error when it did nit before, but what it does now is really an implemenration detail (likely, what np.searchsorted does)

With duplicate x values, the procedure is not well-defined

Hmm, I think x has a float dtype most of the time, so comparing for exact equality seems wrong. I'm fine with adding a test case and doing whatever argsort does now.

Other interpolation kinds do
 if x.ndim != 1 or np.any(x[1:] <= x[:-1]):
         raise ValueError("Expect x to be a 1-D sorted array_like.")

regardless of x.dtype. In floating point, sure, equality checks are dubious. I think we can just use the same check here and forget about this whole issue :-).

okay, fair enough - copying is easier than redesiging:)

That is just the check and error I would have loved to see. I also think that sufficient. :)

Fix in gh-9887.
The check had to be made a trifle trickier because assume_sorted=True apparently allows monotonically decreasing values.

Note that the result is correct under the assumption that you are trying to interpolate right-continuous functions. For example,
f = sp.interpolate.interp1d(np.array([0., 1., 1., 2.]), np.array([1., 2., 0., 1.]), kind='linear')
g = sp.interpolate.interp1d(np.array([0., 1., 1., 2.]), np.array([1., 2., 0., 1.]), kind='nearest')
x = plt.linspace(0, 2, 500)
plt.plot(x, f(x), label="f(x)")
plt.plot(x, g(x), label="g(x)")
plt.legend()

correctly gives

For the discontinuity you have lim_{x\to 1} f(x) = 2 and f(1) = 0, which is perfectly fine; see for example a right-continuous step function.

Actually, there is a subtle inconsistency:
f = sp.interpolate.interp1d(np.array([0., 1., 1., 2.]), np.array([1., 2., 0., 1.]), kind='linear')
g = sp.interpolate.interp1d(np.array([0, 1, 1, 2]), np.array([1., 2., 0., 1.]), kind='linear')
print(f"f(1) = {f(1)}, g(1) = {g(1)}")

prints
f(1) = 0.0, g(1) = 2.0

Hm, I didn't expect to wake so many sleeping dogs.
With the comments in https://github.com/scipy/scipy/pull/9887#issuecomment-468649810 , maybe an update to the doc might be more appropriate?

@euronion possibly yes, a doc update could be an alternative.
Touching interp1d is always fraught with backwards compat issues :-(.

With gh-9887 rejected, this turns into a request for improving the docs. Would you be intetested in sending a PR @euronion ?

OK, the conclusion seems to be that interp1d should keep doing whatever it was doing, even if it is not very consistent. I think we're open to accepting a pull request to clarify the documentation, otherwise there's not much to do here. Closing, thanks @euronion , all.


User/ryano/c li client functions2

for review, I still have merger to do

This change is

as to naming, I'd like to keep Fabric out of the name.   We should not be shipping our org chart, and from the the customer's perspective, DOS is the product.
This is not a super strong opinion, so let's discuss if someone has a strong opinion to put fabric into the name,

Two additional points about the name to counter your argument about org chart :-)

Fabric.Identity is the name of the service that this CLI works with.
The org name of Fabric is inherited from the fact that the name of the service layer in DOS is called Fabric.

@johnrulon - any strong opinions here?


Systems Tables, Views, Stored Procedures missing in user databases

SQL Operations Studio Version: 0.31.4 and latest dev build

Steps to Reproduce:

Connect to a SQL Server and expand Databases
Go to a user databases and expand Tables, Views or Stored Procedures

Expected:

I can see a System Tables / System Views / System Stored Procedures folder and expand it to see system objects
Actual:
I cannot see these folders at all

note, this does not apply for master and other DBs under System Databases
The problem here is it's helpful to understand what system procs are there and how to run them.

Changing this to a suggestion after syncing with Karl. It's currently by design but it's a change from SSMS.

Some context is that when we originally designed the Object Explorer node layout we decided to only show System Objects on System Databases in order to simply the default view when working with User Databases.  The logic was that most users doing non-administrative work in User Databases would prefer not to see these "implementation details."  Whereas DBA users would likely be working in master in any case.
In any case, this is a change from SSMS so it's reasonable to revisit if the change is really adding value or just making the SQL Ops harder to use for our SSMS users.

Please consider adding this as an optional preference in settings (and let it be disabled by default). I find this to be very useful in SSMS when searching stored procedure schema in our user databases. I can understand, though, not wanting to see it by default.

I'm going to close this issue as "closely related to" https://github.com/microsoft/azuredatastudio/issues/11511.  For 11511 the system tables are CDC and need to be in the user DB.  When fixing that we can consider if it makes sense to bring in all the system tables into user DBs.

We need to be able to see system tables.  This program is worthless because I cannot see all database objects.  Why would you hide them?  It makes no sense.

Not shown by default.
https://learn.microsoft.com/en-us/answers/questions/1297325/azure-data-studio-not-showing-system-views
[https://learn.microsoft.com/en-us/media/open-graph-image.png]https://learn.microsoft.com/en-us/answers/questions/1297325/azure-data-studio-not-showing-system-views
Azure Data Studio not showing system views - Microsoft Q&Ahttps://learn.microsoft.com/en-us/answers/questions/1297325/azure-data-studio-not-showing-system-views
I have recently started using Azure Data Studio as well as SSMS. If I connect to a database in SSMS and go to the object explorer under views there is a system views folder that I can browse. If I connect to the same database in Azure Data Studio using…
learn.microsoft.com
Byron
Cell:<PHONE_NUMBER>
Skype:<PHONE_NUMBER>

From: Scott Greenfield @.>
Sent: Tuesday, March 26, 2024 10:10
To: microsoft/azuredatastudio @.>
Cc: Byron Smith @.>; Manual @.>
Subject: Re: [microsoft/azuredatastudio] Systems Tables, Views, Stored Procedures missing in user databases (#2106)
We need to be able to see system tables. This program is worthless because I cannot see all database objects. Why would you hide them? It makes no sense.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/azuredatastudio/issues/2106#issuecomment-2020696098, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA7D6OHYI7PRFHTVLC3Q7RTY2GFU3AVCNFSM4FNGXBTKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBSGA3DSNRQHE4A.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


yii2-pjax no longer wokrs?

where i use "composer update",composer told me ：
The "https://bower.herokuapp.com/packages/yii2-pjax" file could not be downloaded (HTTP/1.1 410 Gone)
https://bower.herokuapp.com/packages could not be fully loaded, package information was loaded from the local cache and may be out of date

yii2 version > 2.0.6

@SilverFire, @hiqsol ?

https://github.com/fxpio/composer-asset-plugin/issues/309

closing as it is not an issue to be fixed in Yii. Sent a pull request to the asset plugin: https://github.com/fxpio/composer-asset-plugin/pull/310

Could this be hotfixed with https://github.com/fxpio/composer-asset-plugin/blob/c375f86955e53270b84c0f4cae4f541010ae1e6f/Resources/doc/index.md#usage-with-private-bower-registry ?

if it would not work right now I'd consider that but as the URLs are redirecting it should be fine to update the asset plugin. We can not fix existing code anyway, this is for new setups, which could then directly get the latest verison of the plugin.

Oh well...

https://twitter.com/bower/status/921039231623024640
On next Wednesday we’ll disable old registry for a full day. Please upgrade Bower to not experience any disruption: npm install -g bower

we need some announcements about this and also update the application templates.

Fixed


Create responsive Version from videojs-ima

I have modified the script so that there is a query whether the script is used in a "responsive environment". For this I have created a sample. All other examples are unaffected by the change.

Closing for lack of activity - please feel free to re-open if you'd still like us to consider your pull request.


Container takes long time to stop

Compose down actually takes 10s when all other containers take at most 1s.
Compose:
 kratos_admin_ui:
    image: ghcr.io/dfoxg/kratos-admin-ui:v2.5.0
    ports:
      - '9095:8080'
    restart: unless-stopped
    environment:
      KRATOS_ADMIN_URL: http://kratos:4434
      KRATOS_PUBLIC_URL: http://kratos:4433

Hi @robertsLando,
thanks for opening that one!
But I cant reproduce this. Since the image is only based on the nginx-base-image, maybe you should create your issue there.


Feedback: Confusing & Not intuitive API

I've been trying to follow your documentation (1, 2). However, I can't really make heads or tails of how to actually parse a document and its sections.
I can see the detail and care that when into designing the API, but I do think a simpler abstraction needs to be introduce. For instance, I've struggled for days to try and parse out a filing's sections and grab its text. While, I have gotten output it hasn't been usable, and I'm certain that text got truncated (all user error).
A big issue is just what method to call when since this works off inheritance. You have to do type checks all over the place. I think creating a higher level API or refactor might be needed to reduce the steep learning curve here.
I was kind of hoping this could just parse the tags automatically for me and put them into types.

Hey @aaronclong, thanks for reaching out and trying out the package!

Could you link us to a document(s) you're trying to parse? And/or could you post some particular issues (screenshots/examples) that you're coming across?
As for this works off inheritance, could you provide a simple example of how the structure could be improved? I would love to hear your thoughts on it 🚀


NumLock throwing error

Creating a new issue - not sure if my comment the in the closed issue referenced below was seen.
          There seems to be a mismatch somewhere with NumLock - when I use Key.NumLock I get an error:

Error: [nut.js] - Error: Invalid key code specified.
    at Object.libnut. [as keyToggle] (/Users/ksmith/dev/nutjs-test/node_modules/@nut-tree/libnut-darwin/permissionCheck.js:68:96)

But if I use Key.NumberLock, I don't get an error...I'm not sure if it's actually working correctly or not, though...
This is on macOS 12.4
Originally posted by @smithkyle in https://github.com/nut-tree/libnut-core/issues/102#issuecomment-1595577281

Hi @smithkyle 👋
macOS does not have a dedicated NumLock key, thus it throws an error if you try to press it.
Key.NumberLock is not a valid key at all, so even though it does not trigger an error, it also has no effect.
Best regards
Simon

Closed by #166

Thanks for your contribution, @smithkyle 💯


bubble total supply fix

Taptools misrepresents the total supply of bubble as 100 trillion.
The real total supply is 100 million.
This is a static total supply fix; there have been no token burns, taptools just got the total supply wrong.

Taptools misrepresents the total supply of bubble as 100 trillion.
The real total supply is 100 million.

@similiken please run npm run format


[suggestion] Make the focus buffer bg different than the nonfocus on so to easy differentiate which one is the main buffer in multi buffer window

Looks like so far all buffers are using the same bg. I did a bit hack override to use a little darker bg and it turns out wonderful side effect is that the nonfocused ones are still in the lighter one but the focused is now using my override which is immediately helpful in identifying which one I am editing.

Initially I though this might be out of scope, but I see tokyonight has it.  I am more than happy to add it, unless you are keen to make a PR?

You are welcome to re-open.


world time implementation

Description
Implementation of world time for instance. Support sets the time explicitly, advances the time and adjusts the frequency that the server sends WorldTimeUpdateS2c packet to clients.

Playground:
use valence::client::despawn_disconnected_clients;
use valence::client::hand_swing::HandSwingEvent;
use valence::client::message::SendMessage;
use valence::inventory::HeldItem;
use valence::network::ConnectionMode;
use valence::prelude::*;
use valence::world_time::{ChangeTrackingTimeBroadcast, LinearTimeTicking, WorldTime};

#[allow(unused_imports)]
use crate::extras::*;

const SPAWN_Y: i32 = 64;

pub fn build_app(app: &mut App) {
    app.insert_resource(NetworkSettings {
        connection_mode: ConnectionMode::Offline,
        ..Default::default()
    })
    .add_plugins(DefaultPlugins)
    .add_startup_system(setup)
    .add_system(init_clients)
    .add_system(despawn_disconnected_clients)
    .add_system(handle_adjust_speed)
    .add_system(handle_display_time)
    .add_system(toggle_gamemode_on_sneak.in_schedule(EventLoopSchedule));
}

fn setup(
    mut commands: Commands,
    server: Res<Server>,
    biomes: Res<BiomeRegistry>,
    dimensions: Res<DimensionTypeRegistry>,
) {
    let mut instance = Instance::new(ident!("overworld"), &dimensions, &biomes, &server);

    for z in -5..5 {
        for x in -5..5 {
            instance.insert_chunk([x, z], Chunk::default());
        }
    }

    for z in -25..25 {
        for x in -25..25 {
            instance.set_block([x, SPAWN_Y, z], BlockState::GRASS_BLOCK);
        }
    }

    commands.spawn(instance).insert((
        WorldTime::default(),
        ChangeTrackingTimeBroadcast,
        LinearTimeTicking { speed: 1 },
    ));
}

fn init_clients(
    mut clients: Query<(&mut Client, &mut Location, &mut Position, &mut Inventory), Added<Client>>,
    instances: Query<Entity, With<Instance>>,
) {
    for (mut client, mut loc, mut pos, mut inv) in &mut clients {
        loc.0 = instances.single();
        pos.set([0.5, SPAWN_Y as f64 + 1.0, 0.5]);

        client.send_chat_message("Let's control time!");
        client.send_chat_message("- Left click the clock to make time run faster");
        client.send_chat_message("- Left click the trident to make time run slower");

        inv.set_slot(36, Some(ItemStack::new(ItemKind::Trident, 1, None)));
        inv.set_slot(37, Some(ItemStack::new(ItemKind::Clock, 1, None)));
    }
}

fn handle_adjust_speed(
    mut instances: Query<&mut LinearTimeTicking, With<Instance>>,
    clients: Query<(&Inventory, &HeldItem)>,
    mut events: EventReader<HandSwingEvent>,
) {
    for e in events.iter() {
        let Ok((inv, inv_state)) = clients.get(e.client) else {
            continue;
        };

        let mut ltt = instances.single_mut();

        let slot = inv_state.slot();
        let Some(is) = inv.slot(slot) else {
            continue;
        };

        match is.item {
            ItemKind::Clock => ltt.speed += 1,
            ItemKind::Trident => ltt.speed -= 1,
            _ => (),
        }
    }
}

fn handle_display_time(
    mut clients: Query<&mut Client>,
    instances: Query<(&WorldTime, &LinearTimeTicking), With<Instance>>,
) {
    for mut client in clients.iter_mut() {
        let (time, ltt) = instances.single();

        client.send_action_bar_message(format!(
            "Time: {} / {} per tick",
            time.time_of_day, ltt.speed
        ));
    }
}

// Add more systems here!

example: cargo run --package valence --example time_travel
tests: cargo test --package valence --lib -- tests::world_time
Related
part of #210

One problem I see here is that the LinearTimeTicking and LinearWorldAging components do not mix well with the ChangeTrackingTimeBroadcast component, since it constantly triggers change detection and spams the client with world time packets. This is problematic for WorldTimeBundle.

I might have to redesign the API a bit. I will create a Broadcaster kind of a mix of the 2 current broadcasters.
struct ScheduledBroadcaster {
    pub next_tick: i64;
    pub interval: u64;
}

And a prebuilt query to provide some API sugarily. I want to separate WorldTime and ScheduledBroadcaster because the user can choose the level of abstraction they want
struct TimeControllingQuery {
    pub time: &mut 'static WorldTime,
    pub schedule: &mut 'static ScheduledBroadcaster
}

impl TimeControllingQuery {
    pub set_time(&mut self, time: i64) { ... }
    pub set_time_defered(&mut self, time: i64) { ... }
}

to change the time we can do:
let mut query: TimeControllingQuery = ...;
// Update immediately
query.set_time(10);

// Scheduled
for i in 11..20 {
    query.set_time_defered(i);
}

What do you think about this API?


Create a terraform provider/scripts for litmus

Develop a terraform provider on top of helm provider to provision litmus with the following operations

Install chaoscenter on k8s
Install chaos agent via helm
Add chaoshub to ChaosCenter via API provider
Run chaos workflows via API provider

Along with the documentation of the provider/script

Hi, @Adarshkumar14 @rajdas98 @Jonsy13 I want to work on this issue in GSoC 2022. Also, wanted to know is there a document or proposal available on this issue that gives me more context.

How can I apply for this idea for GSOC? is there any communication channel with the mentors?

Hi @Mostafa-wael
You can join the open community here: https://join.slack.com/t/chaosnative/shared_invite/zt-tff9qr0z-cgahgNmux5rSDFl1yac90w
:)

Hi all. I am Excel, and I im interested in contributing to this project for GSoC '22. I have joined the community,  and have been looking into ChaosEngineering too. I am thinking of attending the event that was posted on the community to get up to speed with LitmusChaos and Chaos Engineering in general.
Is this alright?  And are there any prerequisites I need to complete to increase my chances,  or to write a good proposal?  Thank you!

Is there is a specific channel on slack for GSoC?

Hii I'm akshat jain and I'm interested in this project . I have intermediate knowledge of kubernetes and basic knowledge of terraform and golang . I never applied to gsoc previously but have some prior experience of open source .
I don't have any idea on how to write a proposal please can u help me out with that .
Is I'm late to apply ??

Closing this due to being descoped.


Add note to license upload for cli and cluster setups

Currently the docs do not state that the mattermost server needs a restart to reflect changes after uploading a license file.
Also added a note for cluster setups specifying that the license file needs to be uploaded to every note in the setup.

Thanks Amy, applied the changes. :)


fix: set interface to stricter typings

This is a small fix in the casparcg-typings.
I found out that we did have defined the enums for ITransition.easing, ITransition.direction & ITransition.type, but we didn't use them.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #147   +/-   ##
=======================================
  Coverage   76.70%   76.70%
=======================================
  Files          42       42
  Lines        4867     4867
  Branches     1098     1156   +58
=======================================
  Hits         3733     3733
  Misses       1090     1090
  Partials       44       44

Impacted Files
Coverage Δ

src/types/src/casparcg.ts
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


Update dyno and redis plans for prod

bors merge

bors merge

bors merge

bors merge

bors merge

bors merge


Body does not have an attribute is_hfss

A lot of methods in drawpylib require the Body from drawpy to have an attribute is_hfss. However, Modeler is not initialized with is_hfss. A lot of scripts I tried do:
pm = Modeler('hfss')
pm.is_hfss = True
chip = Body(pm, 'chip')
In this case chip doesn't inherit is_hfss which causes problems later. I can workaround by defining is_hfss for each Body but it doesn't seem like that was the goal.
Should we just initialize the Modeler with this attribute ?

This is correct. This property is a reminiscent feature from the past version of the code. We need to modify HFSSdrawpy so that :

either the body inherits the modeler property "is_hfss"
or replace each time we are testing for the chip.is_hfss property by testing on modeler.is_hfss property.
I think the first one will be more transparent.


Update file timestamps to reflect real systemtime

What does this PR do?
This commit retains the use of a stateless tick in the model but
allows for the filesystem to report times in systemtime. This
resolves a problem where all times were previously reported by the
filesystem as being UNIX_EPOCH even though the model kept track of
time.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1042
#1041  👈
#1034
#1037
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @blt and the rest of your teammates on  Graphite

Merge activity

Oct 28, 12:25 PM EDT: A user merged this pull request with Graphite.


Enhancement: Update localheinz/composer-normalize

This PR

[x] updates localheinz/composer-normalize

💁♂ For reference, see https://github.com/localheinz/composer-normalize/compare/0.8.0...0.9.0.

Thank you, @chartjes!


WEB UI working without design.

I've builded an rpm and installed cmak, but when i'm browsing it i see plain text without design, i don't have internet access on this server.

i figured out the problem


Replace getQueue() with defaultQueue in Web GPU article

In an effort to support multi-queue with WebGPU, the shape of the API has changed in the spec side. This PR replaces getQueue() with defaultQueue in the Web GPU article so that web developers can continue to experiment with GPU Compute in Chrome Canary.
FYI @kangz

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L72 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L224 - Common typo found: 'implicity' Should it be 'implicitly'?
src/content/en/updates/2019/08/get-started-with-gpu-compute-on-the-web.md#L231 - Line must be at most 100 characters

There's no "implicity" but "simplicity" in the article, therefore I think we're good.

:tada: This has been pushed live to https://developers.google.com/web/


Coverlet collectors integration does not work on full framework projects

In practice, it seems like coverlet is only compatible with analysing .net core projects? Could someone please confirm the current compatibility of Coverlet with respect to this bug https://github.com/microsoft/vstest/issues/2278
And update the project start page to reflect this would be great. I am trying to implement this on a .net full project, by calling vstest.console.exe directly with

$vstestconsolepath = "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions\TestPlatform\vstest.console.exe"

$vsTestArguments = @(
$testDlls #.net 4.6.2
"/logger:trx"
"/InIsolation"
"/collect:"XPlat Code Coverage""
"/TestCaseFilter:" + $testCaseFilters
"/testadapterpath:" + (get-location).Path + "\packages\coverlet.collector.1.2.0\build\netstandard1.0"
)

Microsoft (R) Test Execution Command Line Tool Version 16.4.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 2 test files matched the specified pattern.
Data collection : Data collector 'XPlat Code Coverage' threw an exception during type loading, construction, or initialization: System.FormatException: Input string was not in a correct format.
   at System.Text.StringBuilder.FormatError()
   at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)
   at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
   at System.String.Format(IFormatProvider provider, String format, Object[] args)
   at Microsoft.VisualStudio.TestPlatform.Common.DataCollector.DataCollectionManager.LoadAndInitialize(DataCollectorSettings dataCollectorSettings, String settingsXml).
Data collection : Data collector 'XPlat Code Coverage' threw an exception during type loading, construction, or initialization: System.FormatException: Input string was not in a correct format.

I have the same issue on TeamCity.

Yes the collectors version of coverlet at the moment is supported only for .NET Core app and not for .NET Framework, I'm waiting some answer from vstest team to understand if move to netstandard is ok or no(I think it's possible but I need confirmation), because collector was written by vstest team not by us.

dup of https://github.com/tonerdo/coverlet/issues/705
I'll update documentation asap.

@NPadrutt @captainjono for now the unique way to use coverlet for .NET Framework is https://github.com/tonerdo/coverlet#msbuild-integration-suffers-of-possible-known-issue and https://github.com/tonerdo/coverlet#net-global-tool-guide-suffers-of-possible-known-issue that suffer some known issue, but not all users hit the problem.

@MarcoRossignoli  Thank you! I found a blog post where he integrated it into teamcity via msbuild, so exactly what I was looking for and that worked.
https://medium.com/@justingoldberg_2282/setting-up-code-coverage-with-net-xunit-and-teamcity-for-a-solution-with-multiple-test-projects-5d0986db788b

Glad to hear...and sorry, I think we will support .NET Framework...but I cannot update code without green light from vstest team so I'm blocked for now on it.

TL;DR;
The issue is that we cannot load netcoreapp dll into .net framwork process because resolution fails, so the solution should be compile to netstandard so .net framework host(test host in this case) will load coverlet with no problem.

thanks @MarcoRossignoli. Your effort is greatly appreciated! :)


Replace macros with associated type, add more descriptive names

I have replaced the uses of the TYPENAMES and DIMS macros with an associated type Quantity::Self, as well as gave some of the internal components more descriptive names. This should hopefully be a step towards making the errors generated by this library a bit more comprehensible. In a future PR I will work on adding static_asserts as well.
I also fixed some minor bugs in the units versions of the <math> functions.

I did now, the compiled code is identical.


Setup release process

We should set up a release process, similar to the oasis-core and oasis-core-ledger repositories.

Preliminary automation/release process in #44, but it needs some improvements and tooling.

npm version minor --sign-git-tag seems to get us most of what we wanted in terms of tooling. it commits the change and creates a signed tag. but would we prefer to sign the merge commit when we merge into master?


Could not parse expression with acorn: Unexpected content after expression

What's happening?
This error pops up when I try to generate data from an mdx file in my Next.js project. I am also using Windows 10.
File updated: my-third-post.mdx
X [ERROR] [plugin @mdx-js/esbuild] Could not parse expression with acorn: Unexpected content after expression

    _mdx_bundler_entry_point-27a13489-87ec-46ba-8796-96ce5630b3bf.mdx:53:47:
      53 │         repositoryCrossCaptcha(development_url);
         ╵                                                ^

Error: Found 1 problems in 1 documents.

 └── Encountered unexpected errors while processing of 1 documents. This is possibly a bug in Contentlayer. Please open an issue.

     • "my-third-post.mdx": UnexpectedMDXError: Error: Build failed with 1 error:
     _mdx_bundler_entry_point-27a13489-87ec-46ba-8796-96ce5630b3bf.mdx:53:47: ERROR: [plugin: @mdx-js/esbuild] Could not parse expression with acorn: Unexpected content after expression

SourceFetchDataError: {
  "_tag": "HandledFetchDataError"
}

Reproduction
This error pops up ONLY when the following (fake) code is not escaped with ``` in my mdx file.
pum += binary_passive_input - zif + wheel_flash * ocrCursor;
flashEccDv(point_upload_up);
if (-2 - pum_zero_systray + key < pasteFramework(market_domain_system, core)
        + maximize_script_dpi) {
    repositoryCrossCaptcha(development_url);
    computingAdf.pointIcs = 4;
    interface(3, raid_font + rteNewlineSpreadsheet);
}
if (bareDdr) {
    bandwidth_dpi.imap += icq(25731, driverPpi, bezel) * -4 +
            scarewareRwExport;
    node += 56;
}

I've also attached the .mdx file that throws this error. Uploaded it as an .md file because GitHub isn't supporting uploading .mdx
my-third-post.mdx.md

I am an idiot..


swaggerValidator not setting failedValidation property

Jeremy,
Using swagger 2.0, I ran into an issue when the swagger validator validators.validateContentType throws an error, the framework fails to set the ```failedValidation`` property.
Inside function swaggerValidator in the catch section (line 356).
  return function swaggerValidator (req, res, next) {

  ............
  ............

      // Validate the request
      try {
        // Validate the content type
        validators.validateContentType(req.swagger.swaggerVersion === '1.2' ?
                                         req.swagger.api.consumes :
                                         req.swagger.swaggerObject.consumes,
                                       operation.consumes, req);

       ................
       ................

      } catch (err) {
        if (err.failedValidation === true) {
          if (!err.path) {
            err.path = paramPath;
          }

          err.paramName = paramName;
        }

        debug('    Validation: failed');

        mHelpers.debugError(err, debug);

        return send400(req, res, next, err);
      }
    } else {
      return next();
    }
  };

Since swagger-tools is in our middleware along with other components, we depend on the failedValidation property to determine the source of the error.
Can you please help?
Thanks

I see what you mean.  I should wrap the call like I do here: https://github.com/apigee-127/swagger-tools/blob/master/middleware/swagger-validator.js#L227  In all honesty, it should be a helper that just does the right thing.  I'll get it sorted.

Thanks Jeremy!


Distinguish between raw and actual parameters

Currently, we define the raw parameters and the parameterized parameters  with the same name. For example, for the QuadExp kernel, we use kernel.alpha returns the raw parameters, whereas alpha, _ = kernel.prms returns the parameterised (positive alpha). This is rather confusing and makes the code much harder to read. We should change this by adding the prefix "raw_" in front of all the raw parameters. In other words, the can access the raw parameters alpha with kernel.raw_alpha.

what about @property decorators? I.e. define setters and getters with the suitable softplus transformation whenever you access the non private variable alpha versus alpha = softplus(_alpha). I got this from GPyTorch and Pyro if I remember correctly

what about @Property decorators? I.e. define setters and getters with the suitable softplus transformation whenever you access the non private variable alpha versus alpha = softplus(_alpha). I got this from GPyTorch and Pyro if I remember correctly

That's a good idea. That's how I'm defining the prms property of these objects. I think we should do both, consistently use the raw_ prefix for raw parameters and define the actual parameters as properties.
To be clear, I'm thinking along the lines of:

class Foo(Module):
   def __init__(self, alpha):
        self.raw_alpha = Parameter(inv_transform(alpha), requires_grad=True)
   @property
   def alpha(self):
        return transform(self.raw_alpha)
   @property
   def prms(self):
        return [self.alpha]

Is that what you mean as well @davindicode ?

Yes exactly, so from the outside it just looks like alpha is automatically constrained. prms probably doesn't need the decorator though, what was the reason to add it there? So the getter/setter system is pretty much the same I think, the setter may not be necessary if init is the only place for setting as you wrote above.
    @property
    def variance(self):
        return self.f(self._variance)

    @variance.setter
    def variance(self):
        self._variance.data = self.f_inv(variance)

I never understood how PyTorch distributions constrain their parameters but I think this is also done in some way, though never understood the PyTorch distribution constraints mechanism (if you do would be great to hear).

Currently, I'm using prms to return the parameterised version of all the parameters, not the raw ones.  This is quite useful when some of the parameters use the same intermediate variables in their parameterisation, but perhaps we can give it a better name.
An yes, I haven't really defined the setters as I'm assuming that the only place that we initialize these variables are in __init__.
I'm not entirely sure how pytorch distribution constraints are used internally within the distributions package. As far as I understand, we can use it to parameterise alpha to be greater than or equal to zero as follows:
import torch.distributions as dists
class Foo(Module):
   def __init__(self, alpha):
       self.alpha_transform = dists.transform(dists.constraints.greater_than_equal(0))
        self.raw_alpha = Parameter(self.alpha_transform.inv(alpha), requires_grad=True)
   @property
   def alpha(self):
        return self.alpha_transform(self.raw_alpha)
   @property
   def prms(self):
        return [self.alpha]

There are also lots of other constraints that are quite useful e.g., constraints.lower_cholesky.

Ah ok that makes sense, yeah in the PyTorch distributions they just label some of the parameters with a constraint and somehow internally this transformation is applied. Looks pretty clean in code but no idea how they implemented that still, even after looking at the constraints code for a bit

I think the magic basically happens here:
https://github.com/pytorch/pytorch/blob/master/torch/distributions/constraint_registry.py
dists.transform_to is a register which you can register a constraint and the corresponding transform. The transforms are mostly defined here:
https://github.com/pytorch/pytorch/blob/master/torch/distributions/transforms.py
For exmaple, constraints.positive is registered with ExpTransform  here
https://github.com/pytorch/pytorch/blob/d3023d86ba6eebbcfeafc1633d1a8f8249d12e6d/torch/distributions/constraint_registry.py#L178
When you call transform_to on a registered constraint (positive), you get back the corresponding transform (Exp). At least, that's how I think it works...


Change Batch Ingest to put in content via Bendo

Don gave the worked involved for this, off the cuff, as 20 days. My experience thus far is that his estimates, when applied to me, are low.

dup of #46


Group Commands in commandset extension

From @dhanabalramesh on August 3, 2018 12:20
Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Scenario:

We have created 3 List view command sets "Mark as complete", "Create reminder" and "Update as Pending" based on a client requirement and we managed to make it work in a single package. Challenge came when customer asked to group the commands under single main menu called "Record Operations"

Client expectation:

Question:
Is it possible to group those command sets under single menu item say "Record Operations". Same behavior as "New", "Upload", "Flow" etc.. which has sub menu items (Files, Folders) inside main menu item (Upload). I'm not able to find any help from web site so far. Examples or keyword to search on how approach this functionality will be highly helpful.
Thanks in advance experts!
Sharing is caring.
Copied from original issue: SharePoint/sp-dev-fx-extensions#149

Are there any new information available? This is a real blocker in creating List View Command Sets. Even the workaround in using a Drop-Down-Control is not the way to go. This really should be native.


TypeError and request error in latest version

Since this past update, I have been seeing several error like:
0|mm       | Whoops! There was an uncaught exception...
0|mm       | TypeError: Cannot read property 'substring' of null
0|mm       |     at Request._callback (/home/pi/MagicMirror/modules/MMM-Todoist/fetcher.js:69:35)
0|mm       |     at Request.self.callback (/home/pi/MagicMirror/modules/MMM-Todoist/node_modules/request/request.js:187:22)
0|mm       |     at emitTwo (events.js:106:13)
0|mm       |     at Request.emit (events.js:191:7)
0|mm       |     at Request.<anonymous> (/home/pi/MagicMirror/modules/MMM-Todoist/node_modules/request/request.js:1126:10)
0|mm       |     at emitOne (events.js:96:13)
0|mm       |     at Request.emit (events.js:188:7)
0|mm       |     at IncomingMessage.<anonymous> (/home/pi/MagicMirror/modules/MMM-Todoist/node_modules/request/request.js:1046:12)
0|mm       |     at IncomingMessage.g (events.js:286:16)
0|mm       |     at emitNone (events.js:91:20)
0|mm       | MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm       | If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

I don't know much about node but it appears it's not happy with request. All of my other plugins work so I don't think it's related to he latest MM update but I'm feeling around in the dark here.
My configs look like:
{
    module: 'MMM-Todoist',
    position: 'bottom_left',
    header: 'Personal Goals',
    config: {
        accessToken: 'removed-but-verified',
        maximumEntries: 10,
        interval: 60,
        lists: [ removed-but-verified ],
        fade: false
    }

I'm happy to help troubleshoot.

Hi Jeff...
Based on the stack error  message:  TypeError: Cannot read property 'substring' of null
at Request._callback (/home/pi/MagicMirror/modules/MMM-Todoist/fetcher.js:69:35)... it might be something with one of your Todoist entries.  I've just started using Todoist a few months back and added the code to MMM-Todoist to sort by due date.  Is it possible that one of your Todoist entries may be corrupted or not have a due date?
Tom

Thank you for the tips. I'll double check from my office tomorrow. I actually don't have due dates on anything and have used this for a few months. So maybe that's it. I'll try a little harder to debug and confirm. I did check for any blank entries in todoist, but I'm not seeing anything.

I've got exactly the same problem. It worked fine for month and now i got this issue.
If anybody has an idea please help. I reinstalled the module but the issue occurs again.
best,
jules

Hi all,
i found out that the error only occurs if you have a task without a due date.
Now my problem is that i build tasks with alexa, alexa puts no due date on the tasks. ist there away to automaticly attach a due date to all tasks?
best,
Jules

Hi Jules...
Thanks for helping to determine the problem.  I know the Android Todoist app defaults to today for due date but I don't think that is what you would want.  I found out the web-based Todoist  does allow for no due date... so I'm going to look at my code and see if I can put an exception code for the sorting when there is no due date.  I'm also going to check to make sure setting a time on the due date gets sorted properly.
Regards,
Tom

OK... I did a quick test and workaround for a null or empty due date.  My workaround is to internally set a null due date to Friday, 31 Dec 2100 at 23:59:59.  This does not modify someone's actual Todoist's list ... it is just for sorting purposes.  I also tested the sequencing based on time and it works.  Can anyone else think of any other due date tests that I can try before I ask Chris Brooker to review and implement the fix?

Hi @tkotz8105 ,
many thanks for your fast response. That sounds great. I don't have an idea for other test. I think u set an exception that when due date is null 31 Dec 2100 is set right? That should solve the problem for AVS and all other services that don't set a due date.
many thanks, best,
jules

Thanks for the updates! I appreciate you taking steps to find a fix. I use both the Todoist app for Mac and iOS which has no default date. I think having a really high date is a fine fix though. I would expect to see tasks with assigned dates with tasks without after.
In case someone else has this problem, I rolled back to the commit before the date sorting change via git checkout 155ffe4d49bd8af59ab8bb0736c3ad756c0515d6 as a workaround.


Refactor Patient notes to use React Query

🚀 Feature Proposal
Refactor Patient notes to use React Query instead of redux.
There should be three new hooks added:

usePatientNotes
usePatientNote
useAddPatientNote

The code for adding and viewing notes should be updated to use the new hooks.
Motivation
Remove redux
Technical Notes

See patient allergies for inspiration
delete redux code that will become unused

May I take this?

@michaelkramer You got it!


Presentation: Fix PresentationRpcImpl.getPagedContentSet request returning success response on error

Fixes https://github.com/iTwin/itwinjs-core/issues/6602

@mergifyio backport release/4.5.x

@mergifyio backport release/4.5.x

/azp run ITwin.js


Add support for test plans

Context 🕵♀

Xcode 11 added test plans, which neither XcodeProj nor XcodeGen support yet.

What 🌱

Support for test plans has been mentioned in #442, but there doesn't seem to be any other development.

Proposal 🎉

With this issue I'd like to start a discussion about what is still missing (if anything) in order to integrate test plans?

Thanks for reporting it @smeshko. I'm closing the issue though because there's already an issue created that includes this.

Reopening as #442 is closed, so this can be tracked. This issue can track the addition of initialising, reading and writing the test plan files themselves


Multi delivery services with same domain name and different path prefixes

For the issue #TC-55.

Hey @jifyang, the PR has conflicts, can you please rebase?

Done. Thanks!

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/35/

Unfortunately I am going to close this PR.  It is really old and most of the files that are changed in this PR have been re-written in go. If you feel that this functionality is still desired please port it to go and submit a new PR.


Regenerate Node packages

I can't build parsoid service on master now (contextify fails to build), and there is a new '0.4.0' version in the wild so regeneration might fix things. Unfortunately, I've stumbled into errors one after another while trying to regenerate by myself.
cc @offlinehacker (last person who regenerated packages)

I've pushed https://github.com/NixOS/nixpkgs/commit/763ad3372a9719f1187d800edbbb21a82180b143 as a workaround for now.

I have some patches in the works for npm2nix. Should be able to regenerate soon.

(triage) might be already fixed. Also, npm2nix will change in the near future.

Let's close, I've managed to rebuild it.


Next Patch Update

scenarios (remove s in the list)
introspect

update in this commit (21d9aa00b0f7d510855ba79829f29e6619208e18)


Should Psake have a more pluggable logging mechanism?

At present psake outputs it messages using Write-Output which makes them visible in the console as well as redirectable to a file (or any form of other STDOUT redirection).
This means that within your build process if you want to output a message that is visible alongside the psake output you need to use Write-Output too.  However, this pollutes the pipeline, which effectively prevents you from doing any logging from within a function that needs to return a value (unless you want play around with extracting the returned value from amongst any log messages).
To avoid polluting the pipeline you can use Write-Host to display a message and whilst this is visible in the console, it won't appear alongside the psake output in any STDOUT redirection.
Equally, any custom logging framework you may be using inside of your powershell (e.g. log to a file, database etc.) will not 'see' any of the psake output, including any unhandled exceptions.
Am I missing something, or do others think there is case for extending psake to support a more pluggable logging mechanism?

I've done a quick prototype of this; just need to tidy it up, add some tests, update documentation, etc.
The way I've implemented this, there would be a new public function named something like "OutputHandler" (happy for other name suggestions). You would call that function with a single scriptblock parameter which itself takes a single parameter (the output). The function would add the provided scriptblock to the psake context. From that point onwards instead of calling Write-Output, psake would run & $currentContext.peek().OutputHandler "Some output".
Does that sound like the right solution?

Slight change of approach. The scriptblock will be set via psake-config.ps1; this means that it will be accessible earlier in the execution of psake.

I've got the changes in a branch now. I'm just having some issues with what I think is a pre-existing bug which is preventing me from getting the tests working. Basically, the psake-config I use for my tests is leaking into the configuration of all the other tests and causing them to fail.
I'm not sure how long it will take me to resolve the bug; I've already spent a few hours and not been able to identify why it's happening. In the mean time, if anyone is interested to see the changes, they're here : https://github.com/UberDoodles/psake/tree/pluggable-logging.

Fixed it now.  In CreateConfigurationForNewContext I copied the outputHandlers hashtable to the new config by reference instead of by value, so when the nested psake build loaded the config file, it didn't just change the outputHandlers of the current context, but also of the existing contexts, and every context which was later created.


updated readme.md

Description

updated the networking details in the readme
Motivation and Context

How Has This Been Tested?

[ ] I have tested and validated these changes using one or more of the provided examples/* projects
[ ] I have executed pre-commit run -a on my pull request

merged in other branch


Add a {{ with page }} in templating

Idea
on path/to/page.md
@def myvar = "hello"

on some HTML:
{{with path/to/page}}
  {{fill myvar}}
{{end}}

so basically create an environment where, inside the env, the functions have access (only) to the page variables as defined on path/to/page. This would address part of #391
Reqs
One requirement would be to add a get_vars(path) which would only look for @def ... lines and ignore everything else.

closed in favour of  #420


Run Travis / Appveyor on latest Node LTS / stable

This PR updates Travis and Appveyor to always run on the latest versions of both LTS and stable. Since Travis uses nvm (also see https://docs.travis-ci.com/user/languages/javascript-with-nodejs#Choosing-Node-versions-to-test-against), we can just use 4 to load the latest LTS version (which will be the 4.x series until the next LTS is released) and 5 to run the latest stable version (which is currently 5.x). See also https://raw.githubusercontent.com/nodejs/LTS/master/schedule.png. I believe Appveyor follows the same semantics (https://www.appveyor.com/docs/lang/nodejs-iojs#selecting-node-js-or-io-js-version).

Looks great! Thanks for this.


Use ssh.putMulti instead of ssh.put

ssh.put requests a different sftp for each file, whereas putMulti reuses the same for all the files

It was there:
https://github.com/AutoCloud/ember-cli-deploy-simply-ssh/blob/262c324200fde72f63cfafcfd1724efddadac5ef/lib/ssh.js#L46-L54
But I didn't seem to reuse the same sftp-session, so I tried to reimplement that and eventually found that setting for sshd. Will look closer, anyways.

Isn't this effectively the same? https://github.com/steelbrain/node-ssh/blob/master/Source/SSH.js#L153-L155

The current implementation is only passing two args to ssh.put so to fill the third one, it requests a SFTP object each time. You can requestSFTP and then pass it as a third arg and it'll use that

Oh, I haven't read sources when making this plugin, so I got an impression that as long as it's called from node_ssh instance, then connection is established and is going to be used implicitly. But if we use single connection instance, is there some run-loop that makes files delivered sequentially? Cause I can swear I had the same issue with MaxSessions while using putMulti.

If you want to write files sequentially, here's how can you do that
files.reduce(function(promise, file) {
  return promise.then(function(){
    return ssh.put(file, remotePath(file))
  })
}, Promise.resolve()

Oh, looks neat, I'll try that, thank you :)


prod build error for msal-angular in custom library

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Framework

[x] Angular
[ ] React
[ ] Other

Description
I have integrated the msal angular solution into a library of a NX workspace. It is working just fine, when I use my library (that kind of wraps the msal lib) within an application.
But when I try to make a production build of this library, the build fails.
Error Message

Building Angular Package

------------------------------------------------------------------------------
Building entry point 'my-shared-auth-lib'
------------------------------------------------------------------------------
× Compiling TypeScript sources through NGC
ERROR: Cannot determine the module for class MsalRedirectComponent in<EMAIL_ADDRESS>Add MsalRedirectComponent to the NgModule to fix it.

Cannot determine the module for class MsalRedirectComponent in<EMAIL_ADDRESS>Add MsalRedirectComponent to the NgModule to fix it.

MSAL Configuration
@NgModule({
  imports: [MsalModule, StoreModule],
  providers: [AzureAuthService, MsalService, MsalGuard, MsalBroadcastService]
})
export class SharedAzureAuthModule {
  static forRoot(
    azureConfig: AzureConfig
  ): ModuleWithProviders<SharedAzureAuthModule> {
    return {
      ngModule: SharedAzureAuthModule,
      providers: [
        {
          provide: HTTP_INTERCEPTORS,
          useClass: MsalInterceptor,
          multi: true,
        },
        {
          provide: MSAL_INSTANCE,
          useValue: getMsalInstanceConfig(azureConfig.msalInstance), // basically same setup as in the sample app but parametrized
        },
        {
          provide: MSAL_INTERCEPTOR_CONFIG,
          useValue: getMsalInterceptorConfig(azureConfig.msalInterceptor), // basically same setup as in the sample app but parametrized
        },
        {
          provide: MSAL_GUARD_CONFIG,
          useValue: getMsalGuardConfig(azureConfig.msalGuard), // basically same setup as in the sample app but parametrized
        },
      ],
    };
  }

  constructor(@Optional() @SkipSelf() parentModule: SharedAzureAuthModule) {
    if (parentModule) {
      throw new Error(
        'SharedAzureAuthModule is already loaded. Import it in the AppModule only'
      );
    }
  }
}

Reproduction steps
Create a library, that wraps msal angular and handles communication with it through a NGRX store - meaning it provides actions for the consumer apps and auth information within its internal store that can be accessed via selectors.
Try to run a production build of the lib.
Expected behavior
It should build as expected, especially because the affected MsalRedirectComponent is nowhere used within the library itself.
Only the consuming apps bootstrap it. So I do not really get why this error occurs at all.
Identity Provider

[x] Azure AD
[ ] Azure B2C Basic Policy
[ ] Azure B2C Custom Policy
[ ] ADFS
[ ] Other

Browsers/Environment

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari
[ ] IE
[ ] Other (Please add browser name here)

Regression

[ ] Did this behavior work before?
Version:

Security

[ ] Is this issue security related?

Source

[ ] Internal (Microsoft)
[x] Customer request

@sidyes There may be an issue with the node modules. Can you npm uninstall and reinstall @azure/msal-angular again?

@jo-arroyo I see that the component is not added to the declarations array!
If we add this MsalRedirect Component to the msal.module.ts file declarations array, then it may solves this issue!

Same problem here. I'm trying to use it in a app-shell lib and get the same error. In Ivy, you cannot import a component from a library and declare it in one of your own NgModules. Instead, you should import the module from within the library which declared that component.

Thank you for all the contributions! The PR addressing this issue has been merged and will be part of the next MSAL Angular release. Please open a new issue if you are still encountering this problem.


Proxy Error after large request

I've encountered a Problem where a request to render my EBNF code led to a Proxy Error on multiple devices for a longer period of time.
I simply asked the server to render a very large EBNF. The request was processed and the result was the as before stated error.
The code i used was something like this:
EBNF Nightmare.txt
Of course, this is just example code. But the server should probably return an error when too large data is sent instead of crashing.

This just hits the memory limit of my small Tomcat server, and I won't increase that. If you insist on processing this, please run RR locally. Just tried that on my equally small laptop, and it indeed brought up the diagram, after quite some time, though. Below is a snippet from the top left corner.


Improve API keys input experience.

We need to strip whitespaces when user enters API keys.
See #29 and some of our customer support tickets.
Optionally, we could try to make a dummy request to API with given keys to detect errors/typos ASAP.

Close https://github.com/uploadcare/uploadcare-wordpress/issues/29 when it's done.


CurlTransport: curl_error not being checked every time

I noticed here below, that curl_error is only checked if content was returned, and only if configured as well.
https://github.com/ventoviro/windwalker-http/blob/07eeaebcec7acbb58f6ccc0d1ec51e869a232de2/Transport/CurlTransport.php#L39-L42
However, there are many errors that can occur, even though content has been returned. One example is: 18 - transfer closed with outstanding read data remaining.
As far as I can tell, there is no way to configure your lib, such that it can catch errors like this "curl 18", and throw them as runtime exceptions?

Yes, it seems should check error after every request, please wait for next release.

Move to main repository


Unexpected behaviour with shelf create permissions

With the custom permissions indicated in the attached image set on a shelf, I expected the behaviour to be:
Users can View + Users can Create new books + Users cannot update the shelf details + Users cannot delete the shelf
Instead, the Create permission does not appear to have any affect unless Update is also ticked. This in turn means I cannot let people contribute books to my shelf, without also allowing them to edit my Shelf details.

BookStack v21.04

Thanks for raising @maggie0002.
Yeah, The create permissions are currently redundant, likely originally copied from the permission options of books.

This in turn means I cannot let people contribute books to my shelf, without also allowing them to edit my Shelf details.

Is this just an example of a flow that may be broken from the current permission behaviour? Or is this an ability that you actually desire for your usage? If you desired this permission to allow the adding/removing of books I think we'd want to rename "Create" to "Curate" or "Manage Assigned Content". That would also need some more complex changes in functionality since the behaviour is not set-up for separate editing and curation.

Thanks for raising @maggie0002.
Yeah, The create permissions are currently redundant, likely originally copied from the permission options of books.

This in turn means I cannot let people contribute books to my shelf, without also allowing them to edit my Shelf details.

Is this just an example of a flow that may be broken from the current permission behaviour? Or is this an ability that you actually desire for your usage? If you desired this permission to allow the adding/removing of books I think we'd want to rename "Create" to "Curate" or "Manage Assigned Content". That would also need some more complex changes in functionality since the behaviour is not set-up for separate editing and curation.

It is something I desired for my usage. Although it's not time sensitive. Perhaps best to flag this one for thought as part of the broader permissions review you note is scheduled in the readme?

A note that  #3073 and #4326 have had different expectations to this, in expecting to be able to create new books within this shelf (Which would raise other concerns due shelf->book relationship).
I think for now it'd be better to be pragmatic and go ahead to remove this option from view (and delete existing entries) so that it's not causing confusion. User abilities/actions that may have been desired from this can then be raised independently of this specific check-box/implementation.

Create permission now removed from view as per above, within 847a57a49aef525d2f7f429a30e58a34cf69d43f. Will be part of the next feature release.


Parsing pages, but should be paragraphs

The code intends to be parsing paragraphs from a page, but was instead parsing pages from a document.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

fix type


[Bugfix] Fix Back Button

Checklist

[x] I tested all changes and all related features with different users (student, tutor, editor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Client: I followed the coding and design guidelines.
[x] Client: I added multiple integration tests (Jest) related to the features (with a high test coverage)
[x] Client: I documented the TypeScript code using JSDoc style.

Motivation and Context
Resolves part of https://github.com/ls1intum/Orion/issues/50
Description
The back-button just used location.back, which doesn't work if there is no previous page e.g. because Orion directly loads the correct link without entering the overview.
Artemis does have a helper to solve this issue, however the helper is not working correctly because it uses history.length to check if the page is the first page which does not work reliably since Firefox counts from 1, while Chrome counts from 2 (Chrome also counts the empty page). As discussed in great length here, there is no reliable solution. Thefore I added a new service that tracks the internal navigation, being independent from javascript primitives.
Steps for Testing

Log in to Artemis
Create/Locate an exercise as student
Click on the back button

You should end up on the previous page
Navigate to the exercise from a different source, e.g. by clicking on the diagram points on the statistics page

The back button should correctly lead you back to the different previous page
Copy and paste the url of the programming exercise into a new window/tab
The back button should now lead to the exercise overview
Also check the other buttons by copy/pasting the url and making sure it is still returned correctly. See changes for details.

Save/Cancel after creating/editing a system notification
Save/Cancel after creating/editing a user
Save/Cancel after creating/editing a course
Save/Cancel after creating/editing an exam
Save/Cancel after creating/editing an exercise hint
Save/Cancel after creating/editing a lecture

Optional: Try out different browsers

Test Coverage
navigation.utils.ts 73.8% -> 82.1%

I tested on TS1 and used Firefox (85.0). Nice changes, code looks good!!
Some thoughts...
1. when selecting a lecture, there is no "back arrow", which is not consistent with the exercise use case. We could add the arrow and use the functionality implemented by use here as well.

2. when editing an exercise we should not end up in the page visited before, but we rather see the details page. But for changes in a course/lecture/exam we will be redirected to the previous page after saving the changes... should this be made consistent?

While I agree that the navigation is not consistent there I think this is out of scope for this PR
I now also adapted the behavior for exercises although I am surprised you observed buggy behavior, previously the exercises were using the method with window.history.length which should work in Firefox (although not in Chrome)


Check keys length before using enacl

Pivotal story
Guard the enacl nif from keys with unexpected sizes.
Added some tests.

The main point was not crashing when verifying incoming keys (because it could be an attack vector)
What relates to a node signing with a broken key - this probably is a symptom for a bug so modified the silent producing of broken signed transactions into a loud bang.

I see comment clarified. Removing WIP label.

Addressed comments:

coinbases transactions in tests are spend transactions so one less dependency in removing the coinbase

error emitted by aetx_sign:sign2 does contain the invalid key(s)

aetx_sign:verify_one_pubkey/4 head that was processing 2 errors, now is split into two distinct heads for better visibility


RFP - iisnode

Source: https://github.com/Azure/iisnode
The upstream https://github.com/tjanczuk/iisnode seems no longer maintained.
This project is known to fail on latest platform: Azure/iisnode#46.

This appears to have been picked up outside of the RFP process and is available here: https://community.chocolatey.org/packages/iisnode


Update the script start command in checking ENV in CDK Getting Started

Changed the script call method from sh to ./ for

Fixes problems - who has basic SHELL - bash
example:

xxx@node:~/kurtosis-cdk$ sh scripts/tool_check.sh
Checking that you have the necessary tools to deploy the Kurtosis CDK package...
❌ kurtosis is not installed. Please install kurtosis to proceed: https://docs.kurtosis.com/install/
/usr/bin/kurtosis

xxx@node:~/kurtosis-cdk$ ./scripts/tool_check.sh
Checking that you have the necessary tools to deploy the Kurtosis CDK package...
✅ kurtosis 1.0.0 is installed, meets the requirement (=1.0).
✅ docker 27.1.1 is installed, meets the requirement (>=24.7).
...
🎉 You are ready to go!

To unify the approach of running scripts
example of the approach used in the Readme - https://github.com/0xPolygon/polygon-docs/blob/main/README.md

Thanks for your input @VorobevSA. It just so happens I'm reviewing this doc today so will definitely include your change. Thanks again :)

@kmurphypolygon Thank you!
I've also noticed that the default repository now uses -  erigon  -> https://github.com/0xPolygon/kurtosis-cdk/blob/8dba7da37e729178f134bd182ead2d0048e9ab25/params.yml#L44 but in the documentation - ETH_RPC_URL is used - zkevm
An experienced user will not be embarrassed by this, but the fact that you will encounter an error when performing actions according to the documentation is not pleasant).
xxx@node:~$ export ETH_RPC_URL="$(kurtosis port print cdk-v1 cdk-erigon-node-001 http-rpc)"
xxx@node:~$ export ETH_RPC_URL="$(kurtosis port print cdk-v1 zkevm-node-rpc-001 http-rpc)"
Error:  An error occurred running command 'print'
  Caused by: An error occurred calling the run function for command 'print'
  Caused by: An error occurred while getting service context for service with identifier 'zkevm-node-rpc-001'
  Caused by: An error occurred when trying to get info for service 'zkevm-node-rpc-001'
  Caused by: rpc error: code = Unknown desc = Failed to get service info for service 'zkevm-node-rpc-001'
  Caused by: An error occurred getting info for service 'zkevm-node-rpc-001'
  Caused by: An error occurred while fetching registration for service identifier 'zkevm-node-rpc-001'
  Caused by: An error occurred while fetching name for service identifier 'zkevm-node-rpc-001'
  Caused by: Couldn't find a matching service name for identifier 'zkevm-node-rpc-001'

Probably should be updated in the documentation?

çekme_isteği_hedefi

Agreed, thanks for raising, I'll reopen this.

Hi @VorobevSA please track PR #643 where I have added your suggestions. Thanks so much for the help and assistance :)


Read backup credentials from any namespace

In my org the developers create their own cnpg Clusters in their own namespace. Right now for every cluster created we need to also create a Secret containing the s3 credentials for backups.
Proposal
Read backup credentials from a different namespace than the one where the Cluster resource is created.
We (the admins) create a single Secret in a namespace not accessible by the developers, and they can just reference the secret from that namespace without having access to it.
Example:
  backup:
    barmanObjectStore:
      s3Credentials:
        namespace: admin-only    # set the isolated namespace here
        accessKeyId:
          name: do-s3-creds
          key: ACCESS_KEY
        secretAccessKey:
          name: do-s3-creds
          key: SECRET_KEY

Hi, that's not so common to have secrets/configmaps referenced across namespaces in kubernetes. I'd suggest you to have a look at the tools mentioned here.


Create SECURITY.md policy + post security audit

Fluentd should create a SECURITY.md file which is the standard way for GitHub now to deal with security disclosures. You should also post a link to the 2019 audit: https://cure53.de/pentest-report_fluent.pdf
Once you do, I recommend updating your README like this:
https://github.com/envoyproxy/envoy#security

@caniszczyk is this ok ?
https://github.com/fluent/fluentd#security


Use github actions to build the libraries.

The local compilation is a repetitive and boring thing. These should be handed over to CI. When we create a release tag, we compile it into a binary package available for all platforms, which can avoid the security risks caused by uploading binary files locally.
But this task is not simple. If you have any experience in compiling webrtc source code with GitHub actions, please help me

I don't have weBRTC experience
I don't know the webrTC source code either.
But I have a experience with libgit2,
github action file is: https://github.com/huang12zheng/libgit2/blob/main/.github/workflows/release.yml

I'll also take a look at WebRTC, but there might be a lot of blocking

question
I find that there is existing a action in github
https://github.com/shiguredo-webrtc-build/webrtc-build/blob/master/.github/workflows/build.yml
so, why we need to rework?

@huang12zheng Yes, Shiguredo’s compilation script is a good example, but this repo has added a lot of custom patches. Unlike Shiguredo, we need to compile the dynamic link library to ensure that the minimum binary size native SDK is provided to flutter-webrtc.

Hey @huang12zheng, If you are interested in this, I will be very happy to accept PR to resolve this issue.
Currently, we need to compile libwebrtc.aar for Android:
Include
armeabi-v7a arm64-v8a x86_64 x86
Darwin platform include
iOS armv7
iOS arm64
iOS x64 simulator
iOS arm64 simulator
macOS x64
macOS arm64
Combine all the above platforms into WebRTC.xframework and compress them into WebRTC.xcframework.zip
Windows/Linux/ARM Linux:
You need to clone https://github.com/webrtc-sdk/libwebrtc to the source directory during compilation and generate it. The dynamic link library of libwebrtc.{so,dll}.

Thank you for your reply. I am trying
@cloudwebrtc

I am indeed very sorry that I I give up going on. I feel awful about it and want show something.

In ci-demo I want to build without using run.py.

Build image for something about linux

However, it too big for image, which can’t pull again(would get 503 error). So, I can't reuse it. I must just build and run rightnow. it is the same with Shiguredo. That's reason one.

Build script ,which follow by this issue.

It can’t work simple. Action would run build in place if I had downloaded from source, but script need  some debug. It might just need to modify these scripts. But I am sorry for that I don't have the time or the ability to do that.

I also do patch for Shiguredo’s example.
Patch’s info is as follow:

Use min patch and add libwebrtc.
faster_clone than Shiguredo’s
container_preparations_advance, This is just a shift
fix_window_scriptinvocationpath_error, just due to my workspace is different with Shiguredo’s
But when I compile libwebrtc, it get some error

Finally, I apologize for some reason above. I don't want to do it for a while.


Using interface version

Hello
I compiled the library to use the interface version and I succeeded to compile a parallel application using the mpif90 available in the wi4mpi path but the mpirun seems no to be implemented:
$ cat ~/software/wi4mpi-interface/bin/mpirun
echo "Needed to pass some configure"
Is this normal ? what is the procedure to run the application?
Thank you in advance

Hello Cristian,
the script ~/software/wi4mpi-interface/bin/mpirun is present to prevent some issues with installer like cmake.
Some installers test the avalability of kind of script.
To lunch your application , you must use the launcher of the targeted mpi librarie.


Could you please provide an example of using multi-modal data like images, gene and language?

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

same ,also can you tell me how to download the model weight

@XGGNet and @chengyu89527 Yes I am making an example for this now.

Thanks just curious that will you project generate the text medical cases

same

bumping this. Same.

Hi, do you have any updates on how to play with the model? especially I would like to know some more details on how to tokenize the text promp input and how to convert the output tensor into human readable sentences? Thank you!


Remove version: WilbertBerendsen.Frescobaldi version 3.1.3

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: Duplicate;


Build error related to BRAINSDemonWarpTemplates_Vdouble

BRAINSTools version: https://github.com/BRAINSia/BRAINSTools/commit/eab1460fefc2406b8aa6cc0e6d6fdbbb93e5e41a
ITK v4.10.0rc2:  https://github.com/InsightSoftwareConsortium/ITK/commit/417d6a36d01aa3b835855349cc481a9b3dca8506  (including few Slicer specified changes)
 89%] Building CXX object Modules/Remote/BRAINSTools/BRAINSDemonWarp/CMakeFiles/BRAINSDemonWarpTemplatesLIB.dir/BRAINSDemonWarpTemplates_Vdouble.cxx.o
In file included from /home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates_Vdouble.cxx:19:0:
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h: In function ‘void ThirionFunction(const BRAINSDemonWarpAppParameters&)’:
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:312:55: error: ‘SpatialObjectType’ does not name a type
         actualfilter->SetFixedImageMask( dynamic_cast<SpatialObjectType *>( fixedMask.GetPointer() ) );
                                                       ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:312:73: error: expected ‘>’ before ‘*’ token
         actualfilter->SetFixedImageMask( dynamic_cast<SpatialObjectType *>( fixedMask.GetPointer() ) );
                                                                         ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:312:73: error: expected ‘(’ before ‘*’ token
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:312:74: error: expected primary-expression before ‘>’ token
         actualfilter->SetFixedImageMask( dynamic_cast<SpatialObjectType *>( fixedMask.GetPointer() ) );
                                                                          ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:313:56: error: ‘SpatialObjectType’ does not name a type
         actualfilter->SetMovingImageMask( dynamic_cast<SpatialObjectType *>( movingMask.GetPointer() ) );
                                                        ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:313:74: error: expected ‘>’ before ‘*’ token
         actualfilter->SetMovingImageMask( dynamic_cast<SpatialObjectType *>( movingMask.GetPointer() ) );
                                                                          ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:313:74: error: expected ‘(’ before ‘*’ token
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:313:75: error: expected primary-expression before ‘>’ token
         actualfilter->SetMovingImageMask( dynamic_cast<SpatialObjectType *>( movingMask.GetPointer() ) );
                                                                           ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:329:9: error: ‘SpatialObjectType’ has not been declared
         SpatialObjectType::Pointer fixedMask = ReadImageMask<SpatialObjectType, dims>(
         ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:332:9: error: ‘SpatialObjectType’ has not been declared
         SpatialObjectType::Pointer movingMask = ReadImageMask<SpatialObjectType, dims>(
         ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:335:41: error: ‘fixedMask’ was not declared in this scope
         actualfilter->SetFixedImageMask(fixedMask);
                                         ^
/home/jcfr/Projects/Slicer-Release/BRAINSTools/BRAINSDemonWarp/BRAINSDemonWarpTemplates.h:336:42: error: ‘movingMask’ was not declared in this scope
         actualfilter->SetMovingImageMask(movingMask);
                                          ^
Modules/Remote/BRAINSTools/BRAINSDemonWarp/CMakeFiles/BRAINSDemonWarpTemplatesLIB.dir/build.make:62: recipe for target 'Modules/Remote/BRAINSTools/BRAINSDemonWarp/CMakeFiles/BRAINSDemonWarpTemplatesLIB.dir/BRAINSDemonWarpTemplates_Vdouble.cxx.o' failed
make[2]: *** [Modules/Remote/BRAINSTools/BRAINSDemonWarp/CMakeFiles/BRAINSDemonWarpTemplatesLIB.dir/BRAINSDemonWarpTemplates_Vdouble.cxx.o] Error 1
CMakeFiles/Makefile2:27694: recipe for target 'Modules/Remote/BRAINSTools/BRAINSDemonWarp/CMakeFiles/BRAINSDemonWarpTemplatesLIB.dir/all' failed
make[1]: *** [Modules/Remote/BRAINSTools/BRAINSDemonWarp/CMakeFiles/BRAINSDemonWarpTemplatesLIB.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2

Currently investigating.

Thanks for merging :+1:


Feature request: API with swagger-style interface

Perhaps there are some not-too-complicated API calls that could be added as a way to learn/pilot adding API methods to the app?
We can brainstorm in the dynamic web team meeting, but perhaps something like an authenticated GET request for a list of groups a person is in? or a list of people in a group?

possible use case idea: for dynamic reporting, maybe have an API call to get number of AnVIL users in various groups? (AnVIL users by RC?)


Add ON_UPDATE support in migrations

Piggybacking off of https://github.com/elixir-lang/ecto/pull/705
Ecto currently supports adding ON DELETE column constraints in migrations.
Analogous to ON DELETE there is also ON UPDATE which is invoked when a referenced column is changed (updated). The possible actions are the same as ON DELETE.
This PR supports ON UPDATE on column definitions.
Would love Ecto to support this!
:heart: :purple_heart: :blue_heart: :green_heart:
Thoughts?

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


fix: Spark HBase connector on aarch64

Description
Fix the build of the Spark HBase connector on aarch64.
For aarch64, the protoc artifact from com.github.os72 is used. The same was already done for Hive (https://github.com/stackabletech/docker-images/blob/24.7.0/hive/stackable/patches/3.1.3/002-HIVE-21939-3.1.3.patch).
The "Apache Hadoop YARN Application Catalog Webapp" required an update of the node version to 14.17.0.
The Hadoop version was changed from 3.3.4 to 3.3.6 because this version is used for the HBase image. This reduces the build time and the required disk space.
part of #870
Definition of Done Checklist

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
Please make sure all these things are done and tick the boxes

- [x] Changes are OpenShift compatible
- [x] All added packages (via microdnf or otherwise) have a comment on why they are added
- [x] Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
- [x] All packages should have (if available) signatures/hashes verified
- [x] Add an entry to the CHANGELOG.md file
- [ ] Integration tests ran successfully

TIP: Running integration tests with a new product image
The image can be built and uploaded to the kind cluster with the following commands:
bake --product <product> --image-version <stackable-image-version>
kind load docker-image <image-tagged-with-the-major-version> --name=<name-of-your-test-cluster>

See the output of bake to retrieve the image tag for <image-tagged-with-the-major-version>.

:hourglass_flowing_sand: https://testing.stackable.tech/view/02 Operator Tests (custom)/job/spark-k8s-operator-it-custom/8/


Wrong keyboard path, keyboard not found

Hi! I really enjoy this project, thank you!
When I tried to use it the first time, I had a problem: the mouse was working, but the keyboard wasn't (keyboard not found). Then I found the problem: the keyboard path (in kb_client.py, line 57). The original was:
/dev/input/event0

I tried with
/dev/input/by-path/platform-...-event-kbd

and it worked. I use a Raspberry Pi 4 with the last version of Raspberry OS.

hi gabricgallo, Thank you for your feedback.  I had done the auto-detect feature for the mouse client only. I'm going to add the auto-detect feature for the keyboard also.

This is the first time I try Github and this is my first project. You made my life easier (I use an Ipad for school so using mouse and keyboard is very useful). I'll continue to let you know about everything that could help you with this project. 😁


Export figures/plots in SVG

atm only png is supported. SVG is not possible with the current setup.


Support writing LanceDataset directly

Currently, the pyo3 code for writing a dataset requires a block_on call using tokio runtime. If the input dataset is also a LanceDataset, then the reading also requires a block_on call. This causes tokio to not be happy.
Instead the solution should be that the pyo3 interface should be converted to async and the blocking happens in python to convert to Table or write a dataset

ok it's happening in lance.write_data. thought it was read side

duplicate of #736


packaging import fix

When trying to run a git push on any of our pipenv-cookiecutter repositories, both of the pipenv-setup pre-push hooks fail with the following error:
Traceback (most recent call last):
  File "/Users/stefmd/.cache/pre-commit/repoa7rtv7ax/py_env-python3.12/bin/pipenv-setup", line 5, in <module>
    from pipenv_setup.main import cmd
  File "/Users/stefmd/.cache/pre-commit/repoa7rtv7ax/py_env-python3.12/lib/python3.12/site-packages/pipenv_setup/main.py", line 25, in <module>
    from pipenv_setup import (
  File "/Users/stefmd/.cache/pre-commit/repoa7rtv7ax/py_env-python3.12/lib/python3.12/site-packages/pipenv_setup/lockfile_parser.py", line 3, in <module>
    from requirementslib import Lockfile, Requirement
  File "/Users/stefmd/.cache/pre-commit/repoa7rtv7ax/py_env-python3.12/lib/python3.12/site-packages/requirementslib/__init__.py", line 4, in <module>
    from .models.lockfile import Lockfile
  File "/Users/stefmd/.cache/pre-commit/repoa7rtv7ax/py_env-python3.12/lib/python3.12/site-packages/requirementslib/models/lockfile.py", line 13, in <module>
    from .requirements import Requirement
  File "/Users/stefmd/.cache/pre-commit/repoa7rtv7ax/py_env-python3.12/lib/python3.12/site-packages/requirementslib/models/requirements.py", line 26, in <module>
    from pip._vendor.packaging.specifiers import (
ImportError: cannot import name 'LegacySpecifier' from 'pip._vendor.packaging.specifiers'

After some research, I discovered that this issue was due, at its very heart, to the fact that the packaging lib deprecated its LegacyVersion and LegacySpecifier functionality (read about that here) from version 22.0 onwards.
How this relates to this particular problem is twofold:

packaging is used within the repo here, but THIS IS NOT THE PROBLEM since we pin its version in the pipfile to one that is compatible with version 21.0 which still contains the now deprecated functionality.
packaging also just so happens to be sub-sub-dependency of pipenv-setup via the requirementslib package which depends on pip which then itself depends on packaging. THIS IS THE ROOT CAUSE OF THE PROBLEM.

Taking a dive down into this particular rabbit-hole, raises yet another twofold problem:

even the latest versions of requirementslib still depends on the LegacySpecifier functionality from packaging via pip, as can be seen in the GitHub source code here and the raised issue here.
and crucially, requirementslib will install ANY version of pip greater than or equal to 22.2 which basically renders the package useless given it will by default install the latest version which has been updated to cater for the update in packaging and therefore give the error above.

In other words, requirementslib need to sort their sh*t out.
So in order to fix:

I had to manually install pip and pin the version within the Pipfile to an older compatible version (v24.0) which still depends on the older version of packaging containing the LegacySpecifier functionality (v21.3), as recommended here, as this will force requirementslib to use that version of pip which isn't problematic.

Problem solved. For now.

I'm not a fan of adding pip to the Pipfile because of other compatibility issues it might raise down the line

That's a very good point James. Luckily we have all dependencies locked down to a certain version in the Pipfile so, as long as it works now (which it does), I'm pretty sure it will continue to work. Until the day we decide to start updating things, but we'll cross that bridge when we get to it.
And yep, also good point on raising an issue to address this in the future. I've created one as suggested (link).
Thanks for the review.

The changes themselves look fine to me, although I'm cautiously apprehensive about pinning pip as this could cause us compatibility issues later (in other projects where pipenv-setup is installed as a hook or dependency, for example).
If I'm understanding correctly, the reason pip needs to be pinned is because the latest version of pip expects a fully updated version of packaging, which we can't use as requirementslib hasn't been updated to not use the now-deprecated LegacyVersion and LegacySpecifier functionality, right?
I echo James' sentiment that we should keep an eye on requirementslib and unpin pip if and when the issue is fixed.

Yes pretty much @csut-anmut.
But for the avoidance of any doubt, I'll try to explain it again:
The reason we need to pin pip is because requirementslib still uses old/deprecated packaging functionality via it's pip dependency (as can be seen from this import line in requirementslib here) BUT also specifies to import any version of pip >= 23.1 (as can be seen here).
This is problematic because any version of pip > 24.0 will have removed this old/deprecated functionality by upgrading its own dependency on packaging.
So to fix, we have to force requirementslib to use a version of pip that still works (ie. 24.0), instead of the latest which it installs by default, by installing it and pinning its version in our Pipfile.
Hope that makes sense.


[ALLUXIO-3299] worker should only be exposed in master after register (#7780)

https://alluxio.atlassian.net/browse/ALLUXIO-3299
Cherry-pick from branch-1.8

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/311/
Test PASSed.


Order allows sql injection

You can pass arbitrary SQL strings to Order, for example to drop a database.
This should be fixed asap.

You beat me to it @RichardKnop!

I would also check Limit as that seems like a candidate for sql injection too.

https://github.com/jinzhu/gorm/issues/152


Map: fix closure serialization bug

Add failing test
Map: fix hashing arrays with non-serializable components

qa_req 0
CC @sctice

Hmm, that test passed locally (after the fix), but it's not passing in CI...

Hmm, that test passed locally (after the fix), but it's not passing in CI...

My first guess is different configs that result in an error being triggered instead of an exception, resulting in the catch not being activated, but it sure looks like it's failing due to an uncaught exception. Maybe it's being converted to an exception later by PHPUnit? Or something else?
You could try a version that always hashes the array values to see whether that doesn't work as expected.
Separately, we might want to test an array in an array. I expect that to work, but it's easy to make mistakes here.

dev_block :hand: still only working locally, not in GH actions :shrug:

still only working locally, not in GH actions 🤷

Hm. Looking at the implementation on GH, I'd expect using a closure as part of the key to fail when using the native extension. I wonder whether the action is running using the native extension? I don't see anything in the workflow that would disable it. That seems a little silly, but it would explain the behavior we're seeing.

Now that it's passing would you prefer if I reverted fc9a22a @sctice-ifixit?

Ugh, I don't know. I think the case where we need to recursively hash is rare, so it seems dumb to me to do it proactively, but maybe setting up the exception handler is worse than
recursively hashing :shrug: Or maybe recursively hashing is fast enough that it truly doesn't matter.
I guess recursively hashing is the correct and simple thing to do, so we should do that until there's a demonstrated issue.


Adding support for dispatching execution in container through flow parameter

Introducing new flow parameter called dispatch.execution.to.container. If it's value is set to true then execution will be dispatched to CONTAINERIZED method.

Pull Request Test Coverage Report for Build 6054

6 of 9 (66.67%)  changed or added relevant lines in 2 files are covered.
17 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.009%) to 43.547%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-common/src/main/java/azkaban/executor/container/KubernetesContainerizedImpl.java
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

azkaban-common/src/main/java/azkaban/executor/container/KubernetesContainerizedImpl.java
17
64.44%

Totals

Change from base Build 6053:
0.009%

Covered Lines:
16393

Relevant Lines:
37644

💛  - Coveralls


ImportError: libodbc.so.2: cannot open shared object file: No such file or directory

Pyodbc successfully installs in my Kubernetes container through a requirments.txt file. But I receive errors when importing pyodbc in my python script.
Downgrading to the previous version fixed this issue.

What errors, specifically?

"ImportError: libodbc.so.2: cannot open shared object file: No such file or directory"
I did confirm that pyodbc did exists. Downgrading to 4.0.34 resolved this issue.

Install unixODBC.
4.0.34 came with unixODBC but it is a very old and buggy version which has caused other issues here.

https://github.com/mkleehammer/pyodbc/wiki/Install#installing-on-linux

For me, the solution to solve this problem was:
sudo apt remove libodbc2
sudo apt install libodbc2

I am using a distro based on Ubuntu 22.04 LTS (Jammy)

this made the trick !
sudo apt-get install unixodbc-dev

this made the trick ! sudo apt-get install unixodbc-dev

It's works for python:3.9-bullseye well ! THX

PyODBC ImportError: libodbc.so.2: cannot open shared object file: No such file or directory
If you encounter the ImportError: libodbc.so.2: cannot open shared object file: No such file or directory error when trying to import pyodbc after installing it via pip, follow these steps:
Install unixODBC: Run the following command to install unixODBC, which is required for pyodbc to work properly.
$ sudo apt install unixodbc
This should resolve the shared object file error and allow you to use pyodbc without any issues.

Do you really need to repeat what was said multiple times in previous comments already?

The way it worked for me (on Ubuntu 22.04)
i was trying to connect to SQL Server database from a django application, but I was facing this error, so the way I solved it was
1. Install unixodbc
First, ensure you have unixodbc installed. You can install it using the following command:
sudo apt install unixodbc

2. Install Microsoft ODBC 17 Driver
Run the following bash script to install the Microsoft ODBC 17 Driver:
if ! [[ "16.04 18.04 20.04 22.04" == *"$(lsb_release -rs)"* ]];
then
    echo "Ubuntu $(lsb_release -rs) is not currently supported.";
    exit;
fi

curl https://packages.microsoft.com/keys/microsoft.asc | sudo tee /etc/apt/trusted.gpg.d/microsoft.asc

curl https://packages.microsoft.com/config/ubuntu/$(lsb_release -rs)/prod.list | sudo tee /etc/apt/sources.list.d/mssql-release.list

sudo apt-get update
sudo ACCEPT_EULA=Y apt-get install -y msodbcsql17
# optional: for bcp and sqlcmd
sudo ACCEPT_EULA=Y apt-get install -y mssql-tools
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc
source ~/.bashrc
# optional: for unixODBC development headers
sudo apt-get install -y unixodbc-dev

Do you really need to repeat what was said multiple times in previous comments already?

It's a gpt bot.


partners[openai]: Add name field to tool message to match OpenAI spec

Discovered alongside @t968914

Description:
According to OpenAI docs, tool messages (response from calling tools) must have a 'name' field.
https://cookbook.openai.com/examples/how_to_call_functions_with_chat_models

Issue: N/A (as of right now)

Dependencies: N/A

Twitter handle: N/A

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, ccurme, vbarda, hwchase17.

Hello, thanks for this.
I do see in the cookbook you linked that the completions endpoint accepts a tool message with a "name" field.
I have a slight hesitation because in OpenAI's API reference, this parameter is not documented (and not required), and OpenAI in the past has removed support for undocumented parameters (which is why we include those checks).

So there is arguably some risk to this, depending on how much weight you give to the documentation in the cookbooks vs. the API reference.
I'm interested in hearing what is the benefit? Is there a scenario or code snippet you could provide to help illustrate what we gain?

We ran into this issue while using google gemini's OpenAI API spec endpoint with the ChatOpenAI wrapper. https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/call-gemini-using-openai-library
This API endpoint expects a name field on tool messages, and will error out (HTTP 400) if the key does not exist. Thus, you can't use it as the base api url with the ChatOpenAI wrapper.
I found the example in the cookbook that mentioned it as well, and so I believe this is in fact a part of the spec.  Additionally, LiteLLM (an OpenAI API spec proxy to other providers) expects this name field when translating from OpenAI to other specs. So it seems that this field has been largely accepted down stream by a lot of the community.
You are right though, this is not clearly documented by OpenAI. However, this key missing breaks many integrations with other services providing the OpenAI API spec

Sounds good @andrewmjc. Out of curiosity, have you considered using the langchain-google-vertexai or langchain-google-genai packages?

I am mainly working with OpenAI API proxies for governance, so I haven't really looked at the other wrappers! Might be worth considering in the future though!


[Script Lab] Tweak

Docs Build status updates of commit 57dfdf6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/explore-with-script-lab.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


issue 493

Avg response time
coverage on master

Rationale for changes
see #493 for the description
integration of mwe in the issue into the testsuite ?
Additional info and certifications
This pull request (PR) is a:

[x] Bug fix
[ ] Feature addition
[ ] Other, Please describe:

I certify that

[x] I reviewed and followed the contributing guidelines, including
- Increasing test coverage for all feature-addition PRs
- Increasing test coverage for all bug-fix PRs for which there
does not already exist a related test that failed before the PR
- At least maintaining test coverage for all other PRs
- Ensuring that all tests pass when run locally
- Naming PR  to indicate work in progress (WIP) and to attach the PR
to the appropriate bug report or feature request issue
- White space (no trailing white space or white space errors may
be introduced)
- Commenting code where it is non-obvious and non-trivial
- Logically atomic, self consistent and coherent commits
- Commit message content
- Waiting 24 hours before self-approving the PR to give another
OpenCoarrays developer a chance to review my proposed code

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@neok-m4700 You rock! I do certainly want to include the MWE in the test suite, I'll do that now quickly.
I vote we
:ship: it!

Still
looks good to me!


MM-12960: Only back to previous channel if is not archived

Summary
Only back to previous channels if the channel itself is not archived. If
it is archived, back to the Town Square.
Ticket Link
MM-12960
Device Information
This PR was tested on: [One Plus 5, Android 8.1]

@jespino build failed