[CP] Modify DB and Add org support and user context support to devportal and backoffice

Purpose
This PR does the following.

This will modify db scripts and do the followings

Introduce new APK_USER table
Remove Subscriber and other unwanted tables
Modfy foreign keys and remove auto increment

Add user Registration to the DB from the token for devportal
Add organization and user retrieval from request context support in devportal

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Fixes

https://github.com/wso2/apk/issues/1062

Codecov Report
Patch coverage has no change and project coverage change: +21.28 :tada:

Comparison is base (417b800) 34.14% compared to head (d7819c3) 55.43%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1105       +/-   ##
===========================================
+ Coverage   34.14%   55.43%   +21.28%
===========================================
  Files         352       21      -331
  Lines       38954     1638    -37316
  Branches    12182     1016    -11166
===========================================
- Hits        13302      908    -12394
+ Misses      25412      730    -24682
+ Partials      240        0      -240

Flag
Coverage Δ

adapter
?

admin-domain-service
58.16% <ø> (ø)

backoffice-domain-service
51.03% <ø> (+0.24%)
:arrow_up:

devportal-domain-service
?

idp-domain-service
?

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 334 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Beautifier creates spaces after "?" when using optional chaining

Description
I have an optional chain when assigning values to a variable from fetched json data (see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining). Beautifying adds a space before and after the question mark.
Input Before Beautification
This is what the code looked like before:
const dogName = adventurer.dog?.name;
Expected Output
The beautified code should have looked like this:
const dogName = adventurer.dog?.name;

Actual Output
The beautified code actually looked like this:
const dogName = adventurer.dog?.name  ? .name
Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor

Same issue

This project doesn't seem to be well maintained any more. However, I found a way to manually fix this issue:
Internally js-beautify v1.8.1 (2018.8.28) is used, although v1.14.0 (2021.6.14) was already released (assuming your JavaScript formater setting is the default "JS Beautify")... so you could just manually update the formater package of atom-beautify.

Navigate to ~/.atom/packages/atom-beautify/node_modules/js-beautify.
(or wherever atom stores your installed packages)
Create a a new folder and move all old files and folders in there, in case you want to undo these steps.
Insert the files and folders of v1.14.0.
→ js-beautify_v1.14.zip

To fix this well, @Glavin001 whould need to update line 202 in package.json.


Process to feed in positive test results from PoC test

Rapid tests are now available in large quantities. A possibility should be created that allows test results of these tests to be quickly fed into the CWA. A special app for physicians could be created to quickly generate a QR code that allows one to generate a positive report.

@stefanlin this seems very similar to https://github.com/corona-warn-app/cwa-verification-portal/issues/101. Maybe you can check out the other issue and see whether it fits and if so close this one here and move the discussion over there 🙂.

Close this ticket to move discussion corona-warn-app/cwa-verification-portal#101


Support Redux

React + Redux would be pretty nice to have. We only need something like react-redux since I already gave the Redux library a try myself 😃  Take a look! The example project demonstrates how it is used. Redux middleware are supported as well and Thunk middleware is also included by default.

Sorry I've taken so long to reply - I had a very quick glance at this last week but haven't been able to look into it properly yet!

No problem! I look forward to hearing your thoughts on the Redux bindings and on how to approach the integration of the two libraries.

I've started looking through your example project code. I've not got to the point where I understand it all yet, partly because I need to go back and read up on Redux again!
I'm thinking that the best approach to relating your bindings with Bridge.React would be for the Redux bindings to be a separate NuGet package that has a dependency on Bridge.React - is that the sort of thing you had in mind?

Yes, indeed. Having Bridge.Redux seperate is the logical thing to do as it is an independent library of it's own and knows nothing about React. This is the part where the react-redux comes into play. It the library that lets React know how to talk to Redux by giving two things, first: the Provider component, this is a React component that wraps the main app. A connect decorator that tells some component of the app which part app state object it will handle.
Mechanically translating the Provider component looks not too difficult, maybe something like this:
ReactElement Provider(Store myStore, ReactElement mainApp)
{
    return Script.Write<ReactElement>("React.createElement(ReactRedux.Provider, { store: myStore }, mainApp)");
}

As for the connect decorator part, since it is a decorator, I don't know how that translates into ES5 syntax.
Could you please elaborate on what exactly you found confusing in my code? I might be able to help explain things

I didn't find anything confusing in your code, per se, I'm just trying to get back up to speed with Redux (and how it varies from "classic" Flux) and what is required for the React Redux aspect of it.
The basics about stores, action and reducers are coming back to me from times that I've read about Redux in the past, having looked at your code. I'm just trying to work out how the Connector ties components back to the store, to allow state changes to be communicated. Like I said, I'm catching up on the Redux basics.. (starting with this article, which seems good: Writing a Basic App in Redux.. hopefully it all still applies since these technologies move so fast! One of the comments on the posts suggests otherwise..).
Ok. I've read that and now I've also read How to Build a Todo App Using React, Redux, and Immutable.js, which was written more recently (March 2016 rather than July 2015) and that seems to describe it differently!
The newer article still has a "Provider" at the top level, which is basically just a component that allows the top level / "container" component (the "TodoList") to be "store-aware", meaning that it has access to two functions "mapStateToProps" and "mapDispatchToProps". A "connect" method is used to make these available to the component but there doesn't seem to be any other concept of a "connector".
This seems like good news because the older article suggested that all components might have access to dispatch actions directly, via sharing references in React "context" (which is a bit voodoo magic and isn't supported by the Bridge React bindings).
So.. the Provider component barely even needs to be a class, I don't think. In fact, it doesn't even need to be a generic / re-usable component.. it could just be that you have an "TodoApp" top level component that has a props class that has properties that are the methods "mapStateToProps" and "mapDispatchToProps" and then the child components that it renders pass up actions that they want to dispatch.
Unless I'm missing the point, then, can React / Redux not be implemented as a pattern by using the Redux bindings that you've provided and the current React bindings here?
One other thought - that's barely related to this conversation - when you create actions for setting user name or user age, you use the same class "SimpleAction" but only use a subset of the properties for particular actions (eg. SetUserName doesn't need the Age property and SetUserAge doesn't need the Name property). Do you think that it would make more sense to have more specific action classes - a particular action class for setting user name (that only has the new name as a property) and a particular action class for setting user age (that has only has the new age as a property)? Instead of testing the ActionType enum, you could test the type of the class. Just a thought.. what you're doing currently looks like most of the examples "in the wild", but that's because they're for JavaScript which doesn't favour classes so much, whereas they would feel very natural (to me) to use in cases like this!

Oh, I meant to add one more thing - I got a bit confused when I first tried your sample because I tried to open the demo.html file in the "Bridge.Redux" project instead of the "Bridge.Redux.Examples" project!
When you add the Bridge NuGet package, it automatically creates the "Bridge" folder (with bridge.json, the "www" folder, etc..) but if you're creating a library project then you can add the "Bridge.Min" package instead and that will just add the Bridge translator and the runtime library dependencies but not the "Bridge" folder. Keeps your library project tidier! (If you need DOM references then also add the "Bridge.Html5" package).

Ok. I've read that and now I've also read How to Build a Todo App Using React, Redux, and Immutable.js, which was written more recently (March 2016 rather than July 2015) and that seems to describe it differently!

Thanks for pointing this out as this article was helpful in explaining things. Good thing is that the "connecter" was not a decorator or some other magic.

Unless I'm missing the point, then, can React / Redux not be implemented as a pattern by using the Redux bindings that you've provided and the current React bindings here?

Correct, I wrote a one-to-one translation of the todo app example made in the article but I came across React errors that I didn't understand :( then I realized that a solution was to just forget about how the bindings work and just use what React gave me with the existing Redux code. It eneded up working!!! the only caveat is that it re-renders everything after every store dispatch which could be problematic, performance-wise. This is how it looks like:
var appReducer = Reducers.ItemsReducer();
var initialState = new TodoItem[] { };
var store = Redux.CreateStore(appReducer, initialState);
Action render = () =>
{
    var todoList = Components.TodoList(new TodoListProps
    {
        Todos = store.GetState(),
        AddTodo = text => store.Dispatch(Actions.AddTodo(text)),
        ToggleTodo = id => store.Dispatch(Actions.ToggleTodo(id))
    });
    var appContainer = Document.GetElementById("app");
    React.Render(todoList, appContainer);
};
// Invoke render with every state change
store.Subscribe(render);
render();

One other thought - that's barely related to this conversation - when you create actions for setting user name or user age, you use the same class "SimpleAction" but only use a subset of the properties for particular actions (eg. SetUserName doesn't need the Age property and SetUserAge doesn't need the Name property). Do you think that it would make more sense to have more specific action classes - a particular action class for setting user name (that only has the new name as a property) and a particular action class for setting user age (that has only has the new age as a property)? Instead of testing the ActionType enum, you could test the type of the class. Just a thought.. what you're doing currently looks like most of the examples "in the wild", but that's because they're for JavaScript which doesn't favour classes so much, whereas they would feel very natural (to me) to use in cases like this!

I agree, I haven't decided yet what design is the final way to go. C# Polymorfism does sound a good candidate for reducer construction where the execution of different code blocks of the if-else clauses can deferred to different descendants according to their type. It would be idiomatic C# and surely look more clean. Still thinking about how to implement that.

When you add the Bridge NuGet package, it automatically creates the "Bridge" folder (with bridge.json, the "www" folder, etc..) but if you're creating a library project then you can add the "Bridge.Min" package instead and that will just add the Bridge translator and the runtime library dependencies but not the "Bridge" folder. Keeps your library project tidier! (If you need DOM references then also add the "Bridge.Html5" package).

Wow, thats awesome. I didn't know that. Thanks man!

First off, I think that we can improve your re-render every time mechanism. In your TodoList implementation, you currently use functions that return a ReactElement as your component renderers. This is fine for "stateless components" where everything that you need to render is in the props reference and where you don't need any of the React component life cycle methods. 99% of your components should render only according to props and not require life cycle metods, so this is generally a good thing.
However, sometimes you want a component that has state as well as props because state has some magical properties. The most important one is that every time that you call SetState from within a component that has state, it will trigger a re-render of the component without you having to explicitly call the "Render" method again.
So I would create a "container" class (some guidelines specify a difference between "container" components and "presentation" components - the container only deals with tying state together and doesn't render anything directly while presentation components only render things directly from props and pass action up) like this:
public class TodoListContainer : Component<TodoListContainer.Props, IEnumerable<TodoItem>>
{
	public TodoListContainer(Store<IEnumerable<TodoItem>> store)
	    : base(new Props { Store = store }) { }

	protected override void ComponentDidMount()
	{
		props.Store.Subscribe(() => SetState(props.Store.GetState()));
	}

	protected override IEnumerable<TodoItem> GetInitialState()
	{
		return props.Store.GetState();
	}

	public override ReactElement Render()
	{
		return new TodoList(new TodoListProps
		{
			Todos = state,
			AddTodo = text => props.Store.Dispatch(Actions.AddTodo(text)),
			ToggleTodo = id => props.Store.Dispatch(Actions.ToggleTodo(id))
		});
	}

	public class Props
	{
		public Store<IEnumerable<TodoItem>> Store;
	}
}

Then you could change you App.cs "Main" method to the following:
public static void Main()
{
	var appReducer = Reducers.ItemsReducer();
	var initialState = new TodoItem[] { };
	var store = Redux.CreateStore(appReducer, initialState);
	React.React.Render(
		new TodoListContainer(store),
		Document.GetElementById("app")
	);
}

This will still "fully re-render" every time that the state changes - however, it's only a React virtual DOM re-render, which is much cheaper than a real DOM re-render. So we probably don't have to worry about it; this is what React is designed to do.
However.. if you want to go a step further then you could help React out a bit. If you replace your static render methods with component class that are derived from PureComponent like this:
public class TodoList : PureComponent<TodoListProps>
{
	public TodoList(TodoListProps props) : base(props) { }

	public override ReactElement Render()
	{
		return DOM.Div(new Attributes { },
			DOM.Input(new InputAttributes
			{
				Type = Html5.InputType.Text,
				Placeholder = "Add todo",
				OnKeyDown = e =>
				{
					var textInput = e.CurrentTarget.Value;
					if (e.Which == 13 && textInput.Length > 0)
					{
						props.AddTodo(textInput);
						e.CurrentTarget.Value = "";
					}
				}
			}),
			DOM.UL(new Attributes { },
				props.Todos.Select(todo =>
				{
					var attrs = new LIAttributes
					{
						Key = todo.Id,
						OnClick = e => props.ToggleTodo(todo.Id)
					};
					return DOM.Li(attrs, new Todo(todo));
				})
			)
		);
	}
}

public class Todo : PureComponent<TodoItem>
{
	public Todo(TodoItem props) : base(props) { }

	public override ReactElement Render()
	{
		var attrs = new Attributes { Style = props.IsDone ? Styles.Done : Styles.NotDone };
		return DOM.Div(attrs, props.Text);
	}
}

.. then you get some under-the-hood optimisation magic applied. Any "PureComponent" will automatically get a "shouldComponentUpdate" implementation (it's not visible in the C# code but it's provided for React) that will return false if the new props reference has all of the same data as the current props reference. You can see this by adding the following line at the top of the "Todo" class' Render method:
Console.WriteLine("Todo[" + props.Id + "].Render");

Every time that a Todo item is render, it will write to the console. Note that as you add new items, you only get the Render method called for the new item and not for the existing items. If you want to see the difference then change "Todo" to be derived from StatelessComponent instead of PureComponent - now, every time that you add a new item every item in the list re-renders.
This works really well with simple properties like string, int and bool but it gets more complicated with collections or nested object graphs since the shouldComponentUpdate only does a "shallow comparison". If you really want to get the benefits of this then you want to move to using immutable data types. Conveniently, I have a Bridge library to help out with that :D See ProductiveRage.Immutable (also available on NuGet).
I don't know if you saw that I did a three part series about how I think that Bridge React apps should be written? Although it's three parts, each is quite long - but I think you might find it interesting, even if you end up using a slightly different Flux-like store for the code that you want to write. Part one is here: Writing React apps using Bridge.NET - The Dan Way (from first principles). It starts simple but moves on to talk about immutable data types for props, state and the store data and talks about Component vs StatelessComponent vs PureComponent. It also has a nice (imho!) demonstration of a way to describe dispatcher actions using specific classes and show a way  to match them cleanly (which relates to what I was talking about yesterday).

One more note: It's not compulsory to create classes that derive from StatelessComponent or PureComponent when you want to create presentation components - in your example code, you were using the "StaticFunctions" class to create stateless components from simple render methods. This is a valid approach (and there is a "PureComponent" function to do similar for pure components) but I think that it's easier to understand using a class-based approach initially - once you're happy with that, we can always come back to look at the StaticFunctions.PureComponent version.

Nice! Your container component worked perfectly as expected. However, at first glace, it seemed like a lot of code just to tie the react with redux part. Looking at the types and the how things are being transformed, I was able to abstract it a little. You only need these stuff:

A store of type Store<TAppState>
StateToPropsMapper Func<TAppState, TProps>
Renderer Func<TProps, ReactElement>

You can guess what will happen just by looking at the types!  To contruct the same TodoListContainer the code becomes the following, in our case TAppState = TProps = IEnumerable<TodoItem>
var todoListContainer = ReduxContainer.Create(new ContainerProps<IEnumerable<TodoItem>, IEnumerable<TodoItem>>
{
    Store = store,
    StateToPropsMapper = state => state,
    Renderer = props => Components.TodoList(new TodoListProps
    {
        Todos = props,
        AddTodo = text => store.Dispatch(Actions.AddTodo(text)),
        ToggleTodo = id => store.Dispatch(Actions.ToggleTodo(id))
    })
});

In my opinion the code looks cleaner and it is easier to read. What do you think?

public class Todo : PureComponent
{
public Todo(TodoItem props) : base(props) { }
public override ReactElement Render()
{
    var attrs = new Attributes { Style = props.IsDone ? Styles.Done : Styles.NotDone };
    return DOM.Div(attrs, props.Text);
}

}

These pure components look like pretty good fit for presentational components. I am still looking into your library on immutable data types and it works.

I don't know if you saw that I did a three part series about how I think that Bridge React apps should be written? Although it's three parts, each is quite long - but I think you might find it interesting, even if you end up using a slightly different Flux-like store for the code that you want to write. Part one is here: Writing React apps using Bridge.NET - The Dan Way (from first principles).

I actually I did come across your blog post a while ago. I was really impressed, I didn't think we were already able to do so much with C# on the browser. That said, I was also overwhelmed by the amount of information. for me it was  "meant for a different crowd", thats natural considering my 0 experience with React and with Bridge by that time. Now I am reading it again, and since that I have written some examples with both React and Bridge, it became more accessible and even more interesting.

One more note: It's not compulsory to create classes that derive from StatelessComponent or PureComponent when you want to create presentation components - in your example code, you were using the "StaticFunctions" class to create stateless components from simple render methods. This is a valid approach (and there is a "PureComponent" function to do similar for pure components) but I think that it's easier to understand using a class-based approach initially - once you're happy with that, we can always come back to look at the StaticFunctions.PureComponent version.

After writing so much code with F#, my brain shifted a little. So when writing in C# I still tend to do things in terms of functions. Its not a "Functional is better" mentality, its just what I got used to write.

I think your abstraction for the container component (aka "Provider"..?) makes a lot of sense!
If you prefer the functional approach for generating components (which is understandable anyhow but especially if you're coming in with F# experience), then it's a simple change for Pure or Stateless components - instead of a component class such as:
public class Todo : PureComponent<TodoItem>
{
	public Todo(TodoItem props) : base(props) { }

	public override ReactElement Render()
	{
		Console.WriteLine("Todo[" + props.Id + "].Render");
		var attrs = new Attributes { Style = props.IsDone ? Styles.Done : Styles.NotDone };
		return DOM.Div(attrs, props.Text);
	}
}

.. which is rendered by creating a new instance..
return DOM.Li(attrs, new Todo(todo));

.. you would create a static class with a Render function -
public static class Todo
{
	[Name("Todo")]
	public static ReactElement Render(TodoItem props)
	{
		Console.WriteLine("Todo[" + props.Id + "].Render");
		var attrs = new Attributes { Style = props.IsDone ? Styles.Done : Styles.NotDone };
		return DOM.Div(attrs, props.Text);
	}
}

.. and then render it using the "StaticFunctions.Pure" method -
return DOM.Li(attrs, StaticComponent.Pure(Todo.Render, todo))

Actually, you could render the content by just calling the method directly and using the returned ReactElement. The "StaticComponent.Pure" has two benefits, though. Firstly, it automatically injects the "shouldComponentUpdate" implementation that can save React some work if the old and new props are the same. Secondly, it uses the value in the [Name] attribute to assign a display name to the component - this will be displayed if you use the React dev tools (a browser extension).
There is a (small) performance gain to defining components using "StaticComponent.Pure" instead of deriving from PureComponent - probably not enough to make much difference in real use but still nice to know if you prefer the functional approach already.

Just in case you've not used the React dev tool extension and don't know what I mean, this is what they look like (note the component names and the props references - can be helpful from time to time in working out why something's not doing what you expect).

I have installed React dev tools, but I still didn't get the (display) names right with [Name] :( Stateless components rendered with StaticComponent.Stateless have StatelessComponentas the display name. The pure ones, rendered with StaticComponent.Purehave display name No display name. Maybe its just a firefox thing (where I have the dev tools installed, chrome wasn't able to install React tools).

Can you include the code from your static render functions and the code that passes them through either "Pure" or "Stateless" calls?
Why wouldn't chrome install the extension, did it give a particular error?

Ofcourse,
Renderer = props => StaticComponent.Stateless(Components.TodoList, new TodoListProps
{
    Todos = props,
    AddTodo = text => store.Dispatch(Actions.AddTodo(text)),
    ToggleTodo = id => store.Dispatch(Actions.ToggleTodo(id))
})

is translated to
setRenderer: function (props) {
                    return Bridge.React.StaticComponent.stateless(Object, Bridge.Redux.Examples.Components.TodoList, { todos: props, addTodo: function (text) {
                        store.dispatch(Bridge.Redux.Examples.Actions.addTodo(text));
                    }, toggleTodo: function (id) {
                        store.dispatch(Bridge.Redux.Examples.Actions.toggleTodo(id));
                    } });
                }

Using StaticComponent.Stateless above for TodoList, and StaticComponent.Pure for the following TodoItem
TodoItem: function (todo) {
    var attrs = { style: todo.isDone ? Bridge.Redux.Examples.Styles.done : Bridge.Redux.Examples.Styles.notDone };
    return React.DOM.div(attrs, todo.text);
},
TodoList: function (todoListProps) {
    return React.DOM.div({  }, React.DOM.input({ type: "text", placeholder: "Add todo", onKeyDown: function (e) {
        var textInput = e.currentTarget.value;
        if (e.which === 13 && textInput.length > 0) {
            todoListProps.addTodo(textInput);
            e.currentTarget.value = "";
        }
    } }), React.DOM.ul({  }, System.Linq.Enumerable.from(System.Linq.Enumerable.from(todoListProps.todos).select(function (todo) {
        var attrs = { key: todo.id, onClick: function (e) {
            todoListProps.toggleTodo(todo.id);
        } };

        return React.DOM.li(attrs, Bridge.React.StaticComponent.pure(Object, Bridge.Redux.Examples.Components.TodoItem, todo));
    })).toArray()));
}

The result:

Chrome didn't give any errors, its just that nothing happened when I tried to install the tools. (I thought there should have been some react icon on toolbar but there weren't any)  I haven't looked into it properly yet.

I think that I've had similar problems with Chrome - the new dev tools tab won't appear until you close it all down and start it again, sometimes.
It's weird that Firefox's tools behave differently - I've confirmed this on my computer; the names appear correctly in the React tools in Chrome but not in Firefox (see screenshot). I can't find any information about it through Google yet, though.

To get back to the original issue.. how do you feel about the Redux integration now? Are you happy to create a distinct NuGet package that adds the Redux bindings and helper classe (but that depends upon Bridge.React)? I don't know if you've created and published any NuGet packages in the past - if not, be assured that it's really easy! I can help out if you need any guidance. Are you happy for me to close this issue? (I'll raise a separate one about the Firefox Dev Tools).

I think the end-solution is very sound and I like it a lot! Nothing is really needed on the React part of this feature so I will write a seperate library for this one. Thanks a lot for your help, really really appreciate it!
Oh yes, I have made some basic Nuget packages a while ago, a couple bindings libraries for Bridge :D nothing fancy haha so this won't be a problem.
As for this issue, we can close it since it is no longer an issue ;)


Update versions/recipe logic.

Some improvements / modernizations for the package and dependencies. Depends on #108.

/merge


[Snyk] Upgrade @sentry/integrations from 7.54.0 to 7.109.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @sentry/integrations from 7.54.0 to 7.109.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 82 versions ahead of your current version.
The recommended version was released 22 days ago, on 2024-03-28.

Release notes

Package name: @sentry/integrations

7.109.0 - 2024-03-28This release deprecates some exports from the @ sentry/replay package. These exports have been moved to the browser SDK
(or related framework SDKs like @ sentry/react).

feat(feedback): Make "required" text for input elements configurable (#11287)
feat(node): Add scope to ANR events (#11267)
feat(replay): Bump rrweb to 2.12.0 (#11317)
fix(node): Local variables skipped after Promise (#11248)
fix(node): Skip capturing Hapi Boom error responses (#11324)
fix(web-vitals): Check for undefined navigation entry (#11312)
ref(replay): Deprecate @ sentry/replay exports (#11242)

Work in this release contributed by @ soerface. Thank you for your contribution!
Bundle size 📦

Path
Size

@ sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped)
80.48 KB

@ sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)
71.47 KB

@ sentry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped)
75.49 KB

@ sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped)
65.11 KB

@ sentry/browser (incl. Tracing) - Webpack (gzipped)
35.41 KB

@ sentry/browser (incl. browserTracingIntegration) - Webpack (gzipped)
35.29 KB

@ sentry/browser (incl. Feedback) - Webpack (gzipped)
31.52 KB

@ sentry/browser (incl. sendFeedback) - Webpack (gzipped)
31.53 KB

@ sentry/browser - Webpack (gzipped)
22.74 KB

@ sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped)
78.59 KB

@ sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)
69.97 KB

@ sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)
35.77 KB

@ sentry/browser - ES6 CDN Bundle (gzipped)
25.17 KB

@ sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)
220.31 KB

@ sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)
108.12 KB

@ sentry/browser - ES6 CDN Bundle (minified & uncompressed)
75.48 KB

@ sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)
39 KB

@ sentry/react (incl. Tracing, Replay) - Webpack (gzipped)
71.97 KB

@ sentry/react - Webpack (gzipped)
22.77 KB

@ sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)
89.81 KB

@ sentry/nextjs Client - Webpack (gzipped)
53.95 KB

@ sentry-internal/feedback - Webpack (gzipped)
17.3 KB

7.108.0 - 2024-03-22

7.107.0 - 2024-03-14

7.106.1 - 2024-03-11

7.106.0 - 2024-03-08

7.105.0 - 2024-03-04

7.104.0 - 2024-02-29

7.103.0 - 2024-02-27

7.102.1 - 2024-02-22

7.102.0 - 2024-02-20

7.101.1 - 2024-02-15

7.101.0 - 2024-02-13

7.100.1 - 2024-02-07

7.100.0 - 2024-02-06

7.99.0 - 2024-01-30

7.98.0 - 2024-01-25

7.97.0 - 2024-01-25

7.95.0 - 2024-01-23

7.94.1 - 2024-01-19

7.93.0 - 2024-01-10

7.92.0 - 2024-01-04

7.91.0 - 2023-12-22

7.90.0 - 2023-12-20

7.89.0 - 2023-12-19

7.88.0 - 2023-12-14

7.87.0 - 2023-12-13

7.86.0 - 2023-12-07

7.85.0 - 2023-12-04

7.84.0 - 2023-11-30

7.83.0 - 2023-11-28

7.82.0 - 2023-11-27

7.81.1 - 2023-11-21

7.81.0 - 2023-11-20

7.80.2-alpha.1 - 2023-11-15

7.80.2-alpha.0 - 2023-11-14

7.80.1 - 2023-11-14

7.80.0 - 2023-11-09

7.79.0 - 2023-11-08

7.78.0 - 2023-11-08

7.77.0 - 2023-10-31

7.76.0 - 2023-10-27

7.75.1 - 2023-10-25

7.75.0 - 2023-10-24

7.74.2-alpha.1 - 2023-10-23

7.74.2-alpha.0 - 2023-10-19

7.74.1 - 2023-10-17

7.74.0 - 2023-10-13

7.73.0 - 2023-10-02

7.72.0 - 2023-09-26

7.71.0 - 2023-09-25

7.70.0 - 2023-09-20

7.70.0-beta.1 - 2023-09-15

7.70.0-beta.0 - 2023-09-14

7.69.0 - 2023-09-13

7.68.0 - 2023-09-06

7.67.0 - 2023-09-05

7.67.0-beta.0 - 2023-08-31

7.66.0 - 2023-08-30

7.66.0-alpha.0 - 2023-08-29

7.65.0 - 2023-08-28

7.65.0-alpha.0 - 2023-08-16

7.64.0 - 2023-08-14

7.64.0-alpha.0 - 2023-08-11

7.63.0 - 2023-08-10

7.62.0 - 2023-08-09

7.61.1 - 2023-08-04

7.61.0 - 2023-07-31

7.60.1 - 2023-07-26

7.60.0 - 2023-07-21

7.59.3 - 2023-07-19

7.59.2 - 2023-07-18

7.59.1 - 2023-07-18

7.59.0-beta.1 - 2023-07-17

7.59.0-beta.0 - 2023-07-13

7.58.1 - 2023-07-13

7.58.0 - 2023-07-12

7.57.0 - 2023-06-28

7.57.0-beta.0 - 2023-06-21

7.56.0 - 2023-06-19

7.55.2 - 2023-06-14

7.55.1 - 2023-06-14

7.55.0 - 2023-06-13

7.54.0 - 2023-06-01

    from @sentry/integrations GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Build fails due to API change, we will need to manage this manually.


Use custom triplet for buildpack to disable debug+release builds

This should reduce the build time by 1/2, and reduce the size by more than that as the debug symbols are bulky.

This should help with #172


BaseHtml setActivePlaceholder inconsistent with activeLabel

The setActivePlaceholder method introduced with 2.0.14 is inconsistent with the activeLabel method with regards to attribute names.
What steps will reproduce the problem?
<?= Html::activeTextInput($model, '[0]attribute', ['placeholder' => true]) ?>
What is the expected result?
The placeholder should be the same as the label.
What do you get instead?
Placeholder is the attribute name, [0]attribute
Additional info
activeLabel uses the static method getAttributeName as the input to getAttributeLabel
setActivePlaceholder just passes the attribute name unfiltered.

Q
A

Yii version
2.0.14

PHP version
7.1

Operating system
Linux

Thank you. Would you like to create a PR to fix this issue?


Permissions

Hi. I'm using the default GITHUB_TOKEN permissions set and am not seeing the simplecov report from the GH Actions bot. Could you confirm the permissions necessary for the coverage to be properly shown on a PR? Thank you!

Can you provide a mini repo ?

Here's the actual one, it's fairly open: https://github.com/joshuamcginnis/postalpast

I think it's because github.context.issue.number doesn't exist.
https://github.com/aki77/simplecov-report-action/blob/aa7e761094e4ae7487959988f26657b1ce3b61e5/src/report.ts#L12
https://github.com/joshuamcginnis/postalpast/actions/runs/3019473897

Hm. The PR has a referenced issue but the coverage bot still isn't reporting on the PR.


not in filter

I think there might be an issue for this already, but we have in for filtering based on arrays, it would be nice to have not in as well.

not is grouping operator and I believe that this is already possible:
not: { in: [] }
However, I have no way to test it at the moment and do not see unit tests for this use case.

not is grouping operator and I believe that this is already possible:
not: { in: ['whatever'] }
However, I have no way to test it at the moment and do not see unit tests for this use case.

Yes, the suggestion should work. I've added a few tests in https://github.com/aerogear/graphback/pull/1733


Release securityinsights microsoft.security insights 2022 11 01

All PRs to this branch have been reviewed and approved.

/azp run


IOR Feature, for TLS Termination configuration.

When using Istio gateway generated Openshift routes. We need the ability to configure the type of TLS termination created. Currently, this Defaults to passthrough termination here: https://github.com/maistra/istio/blob/maistra-2.0/pilot/pkg/config/kube/ior/route.go#L183 .
My hope is that we can discuss how this is configured and move to a solution. One option is to look for an annotation on the Istio Gateway configuration and depending on its value set the TLS termination type. There may be another way, let's discuss
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@dgn @jwendell Just a heads up. I just realized, the new annotation propagation on routes for ACME won't be able to be used until we can configure the route to be Edge terminated.

How about this, We create annotations on the Istio gateway with the spec below.
ior.pilot.maistra.io/TLSTerminationType = {VAL}
  Allowed Values: {TLSTerminationEdge, TLSTerminationPassthrough, TLSTerminationReencrypt}

ior.pilot.maistra.io/InsecureEdgeTerminationPolicyType = {VAL}
  Allowed Values: {InsecureEdgeTerminationPolicyNone, InsecureEdgeTerminationPolicyAllow, InsecureEdgeTerminationPolicyRedirect}

ior.pilot.maistra.io/TLSCertificateSecret = {VAL}
  Allowed Values: {ANY} Will correspond to a Secret in the secrets API Controller
  Expected Secret Properties: {Certificate, Key, CACertificate, DestinationCACertificate}. Should match the definition of v1.TLSConfig properties.

Closing this as we don't use GitHub issues. If you encounter a bug, please file an issue on our Red Hat JIRA

Closing this as we don't use GitHub issues. If you encounter a bug, please file an issue on our Red Hat JIRA


Remove Prometheus dependency from the Swarm chart

https://hivemq.kanbanize.com/ctrl_board/22/cards/22656/details/

We probably also have to remove the charts.lock file or?
For some reason, it didn't go to the commit I pushed. Thanks for noticing. Will address that.

Also can we add a hivemq-swarm folder in the examples folder and add the example grafana dashboard and an example servicemonitor.yaml?
Good one, will do.

@mhofsche it should be now ready for review again. It can also be reviewed along with the doc PR: https://github.com/hivemq/hivemq4-documentation/pull/1716


Terminal: Letter clipping

Notice the git words in the following screenshot:

Does not reproduce in ca8a8376b46b63db7379cbcc827c75d92bf25e14, from 3 days ago.

I'm on Windows, using CaskaydiaCove Nerd Font as my font, default size, no zoom.

Caused by https://github.com/microsoft/vscode/pull/152347

https://github.com/xtermjs/xterm.js/pull/3866


Custom logger not used in OTLPTraceExporter

What happened?
Steps to Reproduce
Hello,
Here are the main steps to reproduce the issue:

Start an opentelemetry stack
Define a 1ms traces exporter timeout with env var OTEL_EXPORTER_OTLP_TRACES_TIMEOUT=1
Define log level to error with env var OTEL_LOG_LEVEL=error
Define a custom logger with diag.setLogger
Try to send traces
You should see an error DEADLINE_EXCEEDED

Expected Result
I would expect the error logs to be displayed using my custom logger.
Actual Result
The error logs are displayed using a default logger instead of my custom logger:
Service request {
  resourceSpans: [ { resource: [Object], scopeSpans: [Array], schemaUrl: undefined } ]
}
{"stack":"Error: 4 DEADLINE_EXCEEDED: ...

Additional Details
There are 2 logs displayed when a DEADLINE_EXCEEDED occurs.
The first one (Service request...) does not really look like an error in itself which seems a bit weird and it's a plain text error.
The second one ({"stack":"Error: 4 DEADLINE_EXCEEDED: ...) shows the real error and is formatted like a JSON error.
I find only the 2nd log as being relevant for the error happening and ideally I would love to:

Have both log being displayed using my custom logger
OPTIONAL - not see the first log error (Service request...) or have it being displayed as something else than an "error" (a "debug" maybe?)

I used https://github.com/vercel/opentelemetry-collector-dev-setup as a collector backend for these tests.
Thanks !
OpenTelemetry Setup Code
const dotenv = require("dotenv")
const { OTLPTraceExporter } = require("@opentelemetry/exporter-trace-otlp-grpc")
const { HttpInstrumentation } = require("@opentelemetry/instrumentation-http")
const { NodeSDK } = require("@opentelemetry/sdk-node")
const { BatchSpanProcessor } = require("@opentelemetry/sdk-trace-node")
const { diag, DiagLogLevel } = require("@opentelemetry/api")
const process = require("process")

dotenv.config({ path: ".env.local" })
dotenv.config({ path: ".env" })

// Assume here that the following env vars have been set:
// OTEL_LOG_LEVEL=error
// OTEL_EXPORTER_OTLP_TRACES_TIMEOUT=1

const logFn = (...args) => {
  console.log("CUSTOM_LOGGER", ...args)
}
const customLogger = {
  error: logFn, warn: logFn, info: logFn, debug: logFn, verbose: logFn,
}

diag.setLogger(customLogger, DiagLogLevel[process.env.OTEL_LOG_LEVEL.toUpperCase()])

const sdk = new NodeSDK({
  instrumentations: [new HttpInstrumentation()],
  spanProcessors: [new BatchSpanProcessor(new OTLPTraceExporter())],
})
sdk.start()

process.on("SIGTERM", () => {
  sdk
    .shutdown()
    .then(
      () => console.log("[OTEL] SDK shut down successfully"),
      err => console.log("[OTEL] Error shutting down SDK", err)
    )
    .finally(() => process.exit(0))
})

package.json
{
  "name": "opentelemetry-playground",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node -r './instrumentation.js' index.js",
    "start:watch": "node --watch -r './instrumentation.js' index.js"
  },
  "dependencies": {
    "@opentelemetry/exporter-trace-otlp-grpc": "^0.49.1",
    "@opentelemetry/instrumentation-http": "^0.49.1",
    "@opentelemetry/sdk-node": "^0.49.1",
    "@opentelemetry/sdk-trace-node": "^1.22.0",
    "dotenv": "^16.4.5"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

Relevant log output
Listen on http://localhost:3333

Request {
  url: '/',
  headers: { host: 'localhost:3333', 'user-agent': 'curl/8.1.2', accept: '*/*' }
}
Service request {
  resourceSpans: [ { resource: [Object], scopeSpans: [Array], schemaUrl: undefined } ]
}
{"stack":"Error: 4 DEADLINE_EXCEEDED: Deadline exceeded\n    at callErrorFromStatus (/Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/call.js:31:19)\n    at Object.onReceiveStatus (/Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/client.js:192:76)\n    at Object.onReceiveStatus (/Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)\n    at Object.onReceiveStatus (/Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)\n    at /Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/resolving-call.js:99:78\n    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)\nfor call at\n    at ServiceClientImpl.makeUnaryRequest (/Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/client.js:160:32)\n    at ServiceClientImpl.export (/Users/.../projects/opentelemetry-playground/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)\n    at OTLPTraceExporter.send [as _send] (/Users/.../projects/opentelemetry-playground/node_modules/@opentelemetry/otlp-grpc-exporter-base/build/src/util.js:75:39)\n    at /Users/.../projects/opentelemetry-playground/node_modules/@opentelemetry/otlp-grpc-exporter-base/build/src/OTLPGRPCExporterNodeBase.js:44:18\n    at new Promise (<anonymous>)\n    at OTLPTraceExporter._sendPromise (/Users/.../projects/opentelemetry-playground/node_modules/@opentelemetry/otlp-grpc-exporter-base/build/src/OTLPGRPCExporterNodeBase.js:43:25)\n    at Immediate.<anonymous> (/Users/.../projects/opentelemetry-playground/node_modules/@opentelemetry/otlp-grpc-exporter-base/build/src/OTLPGRPCExporterNodeBase.js:74:22)\n    at process.processImmediate (node:internal/timers:476:21)\n    at process.callbackTrampoline (node:internal/async_hooks:130:17)","message":"4 DEADLINE_EXCEEDED: Deadline exceeded","code":"4","details":"Deadline exceeded","metadata":"[object Object]","name":"Error"}

I think actually what is happening is that the SDK is overriding your custom logger. Can you try setting up the logger after the SDK start function call? We may be able to improve this by making sure the SDK doesn't override pre-registered loggers in the future.

I think actually what is happening is that the SDK is overriding your custom logger.

I concur.  If you set OTEL_LOG_LEVEL to a level lower than error, e.g. to debug or warn, then you should see the warn-level log output showing that the initial diag Logger is being overwritten. E.g. for me:
% cat app.js
setInterval(() => {
    console.log('hi from app, still here')
}, 3000)

% OTEL_LOG_LEVEL=info node -r ./instrumentation.js app.js
CUSTOM_LOGGER Current logger will be overwritten from Error
    at DiagAPI.setLogger (/Users/trentm/tmp/asdf.20240403T091816/node_modules/@opentelemetry/api/build/src/api/diag.js:65:37)
    at new NodeSDK (/Users/trentm/tmp/asdf.20240403T091816/node_modules/@opentelemetry/sdk-node/build/src/sdk.js:47:24)
    at Object.<anonymous> (/Users/trentm/tmp/asdf.20240403T091816/instrumentation.js:26:13)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at internalRequire (node:internal/modules/cjs/loader:174:19)
    at Module._preloadModules (node:internal/modules/cjs/loader:1433:5)
    at loadPreloadModules (node:internal/process/pre_execution:611:5)
Current logger will overwrite one already registered from Error
    at DiagAPI.setLogger (/Users/trentm/tmp/asdf.20240403T091816/node_modules/@opentelemetry/api/build/src/api/diag.js:65:37)
    at new NodeSDK (/Users/trentm/tmp/asdf.20240403T091816/node_modules/@opentelemetry/sdk-node/build/src/sdk.js:47:24)
    at Object.<anonymous> (/Users/trentm/tmp/asdf.20240403T091816/instrumentation.js:26:13)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at internalRequire (node:internal/modules/cjs/loader:174:19)
    at Module._preloadModules (node:internal/modules/cjs/loader:1433:5)
    at loadPreloadModules (node:internal/process/pre_execution:611:5)
hi from app, still here
^C

Can you try setting up the logger after the SDK start function call?

Another potential hack is to explicitly unset OTEL_LOG_LEVEL when constructing the NodeSDK. Currently the NodeSDK will not call diag.setLogger if OTEL_LOG_LEVEL is unset. Something like:
...
diag.setLogger(customLogger, DiagLogLevel[process.env.OTEL_LOG_LEVEL.toUpperCase()])
delete process.env.OTEL_LOG_LEVEL // make sure NodeSDK doesn't override my diag logger

Thanks a lot for your quick responses.
Both of your proposals work well 👍 .
I think I'll use the first workaround for now since if I understand correctly will allow me to keep having logs from other otel components.
Would you prefer me to keep the present issue open waiting for you to "improve this by making sure the SDK doesn't override pre-registered loggers in the future" or should I close it ?
Thanks.

I think I'll use the first workaround for now since if I understand correctly, it will allow me to keep having logs from other otel components.

FWIW, Both workarounds should result in getting all diag.info(), diag.warn(), etc. calls sent to your registered DiagLogger.

Would you prefer me to keep the present issue open waiting for you to "improve this by making sure the SDK doesn't override pre-registered loggers in the future" or should I close it ?

I think we can close this issue.  @dyladan can shout if he'd prefer to keep it open.


Add view history and use mutex to protect shared data

Please have a look.

It looks better now, thanks !


BOT can't see offer in incoming offers

Hello,
Sometimes I have a problem with sending the offer from BOT to BOT 2.
How does this look:
BOT 1 sent offer to BOT 2 and BOT 2 can't see this offer in incoming offers.
This problem occurs in 5% of all offers. How can I fix this? Whether it is the fault of steam?
Regards,
safe

If the offer is sent without any errors then this issue is not related to node-steam-tradeoffers library.


return T_x instead of T_core in heat balance

I think I found a bug in heat_balance. It should return T_core, but it is not defined anywhere in the function. In the "struct version" it was producing an error, but not in the "manual" one. Maybe it was picking T_core up from the global environment?
I think the same was happening with T_lung. I've uncommented those lines in heat_balance

It is a potential footgun in julia that global variables can be used in the function scope.


Property definition that impacts generated AssemblyInfo doesn't support CData

From @NTaylorMullen on November 1, 2016 18:30
Adding a <Description> to my csproj that looks like:
<Description><![CDATA[Line 1
Line 2
Line 3]]></Description>

Results in the following error when trying to build:
MSBUILD : error MSB4025: The project file could not be loaded. Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 7, position 44.

Copied from original issue: dotnet/sdk#347

This works in MSBuild 14, but fails in MSBuild 15.

@NTaylorMullen I tried both .netcore and full framework msbuild and they both seem to work. Can you please paste in a full repro project that fails for you, as well as the output from msbuild /version and whether it's the .net core or the full version?
Here's the project that I tested on:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="14.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <PropertyGroup>
        <Description><![CDATA[
    <Target Name="Build">
        <ItemGroup>
           <foo Remove=""/>
        </ItemGroup>
        <Message Text="-@(foo)-"/>
    </Target>]]></Description>

<![CDATA[Line 1
Line 2
Line 3]]>

    </PropertyGroup>

    <ItemGroup>

          <m><![CDATA[Line 1
Line 2
Line 3]]></m>

    </ItemGroup>

    <Target Name="Build">
        <Message Text="$(Description)" Importance="High"/>
        <Message Text="$(p)" Importance="High"/>

        <Message Text="@(i->'%(m)')" Importance="High"/>
    </Target>
</Project>

Project File (from dotnet new, and then dded the description):
<Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" />

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp1.0</TargetFramework>
    <Description><![CDATA[Line 1
Line 2
Line 3]]></Description>
  </PropertyGroup>

  <ItemGroup>
    <Compile Include="**\*.cs" />
    <EmbeddedResource Include="**\*.resx" />
  </ItemGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NETCore.App">
      <Version>1.0.1</Version>
    </PackageReference>
    <PackageReference Include="Microsoft.NET.Sdk">
      <Version>1.0.0-alpha-20161104-2</Version>
      <PrivateAssets>All</PrivateAssets>
    </PackageReference>
  </ItemGroup>

  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
</Project>

Then trying to run results in this:
C:\Users\nimullen\Documents\temp\msbuild> dotnet restore
  Restoring packages for C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj...
  Writing lock file to disk. Path: C:\Users\nimullen\Documents\temp\msbuild\obj\project.assets.json
  Generating MSBuild file C:\Users\nimullen\Documents\temp\msbuild\obj\msbuild.csproj.nuget.g.targets.
  Generating MSBuild file C:\Users\nimullen\Documents\temp\msbuild\obj\msbuild.csproj.nuget.g.props.
  Restore completed in 2436.5539ms for C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj.

  NuGet Config files used:
      C:\Users\nimullen\AppData\Roaming\NuGet\NuGet.Config

  Feeds used:
      https://www.nuget.org/api/v2/
C:\Users\nimullen\Documents\temp\msbuild> dotnet run
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(8,59): error CS1010: Newline in constant [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(8,66): error CS1003: Syntax error, ',' expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(9,6): error CS1003: Syntax error, ',' expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(9,7): error CS1003: Syntax error, ',' expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(10,6): error CS1003: Syntax error, ',' expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(10,7): error CS1003: Syntax error, ',' expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(10,7): error CS1010: Newline in constant [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(16,69): error CS1026: ) expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]
obj\Debug\netcoreapp1.0\msbuild.AssemblyInfo.cs(16,69): error CS1003: Syntax error, ']' expected [C:\Users\nimullen\Documents\temp\msbuild\msbuild.csproj]

The build failed. Please fix the build errors and run again.

On closer inspection it looks like the system is generating the msbuild assembly info file incorrectly. It looks like:
// Generated by the MSBuild WriteCodeFragment class.

using System;
using System.Reflection;

[assembly: System.Reflection.AssemblyCompanyAttribute("msbuild")]
[assembly: System.Reflection.AssemblyConfigurationAttribute("Debug")]
[assembly: System.Reflection.AssemblyDescriptionAttribute("Line 1
Line 2
Line 3")]
[assembly: System.Reflection.AssemblyFileVersionAttribute("<IP_ADDRESS>")]
[assembly: System.Reflection.AssemblyInformationalVersionAttribute("1.0.0")]
[assembly: System.Reflection.AssemblyProductAttribute("msbuild")]
[assembly: System.Reflection.AssemblyTitleAttribute("msbuild")]
[assembly: System.Reflection.AssemblyVersionAttribute("<IP_ADDRESS>")]
[assembly: System.Resources.NeutralResourcesLanguageAttribute("en")]

Lastly msbuild version is <IP_ADDRESS> and dotnet --info:
.NET Command Line Tools (1.0.0-preview4-004079)

Product Information:
 Version:            1.0.0-preview4-004079
 Commit SHA-1 hash:  43dfa6b8ba

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64

@rainersigwald must have also tested a property that impacts the assembly info. I've updated the title.

OK, I can also replicate the bad syntax in the generated AssemblyInfo.
What about the parsing CDATA error inside the actual msbuild file? Is that still an issue for you? If yes, can you please post the project file?


ML 1.13 : Confidence Interval (V) #2209

Description 📜
A video explaining Confidence Interval.
Fixes #2209

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Machine Learning

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.

[x] I have performed a self-review of my own code or work.

[x] My changes generates no new warnings.

[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Name: Deepthi M
Batch: 02
Serial Number: 198

Go to go. Nice one! @deepthi1107


Library Updates

This commit updates our libraries like this:
$ bundle update
$ yarn upgrade --latest

It was automatically run with this script:
$ ./bin/update

Looks like ddtrace is all fixed up with https://github.com/DataDog/dd-trace-rb/pull/1023 so I'm upgrading and going to deploy.
See also: https://github.com/DataDog/dd-trace-rb/issues/1021#issuecomment-624310107


Don't mutate "value"

Some operations, like array.sort do mutate original value.
I know, that you are aware of it, but why do you returning muted value, not mutated copy of the value?
Current approach probably could poison render, as long it may change value during the render.

Hey @theKashey thanks for opening this too.
I wasn't really sure what the best thing to do here was. I think I avoided it because I wasn't sure if copying the values would end up with performance issues, but honestly that seems now like not the right decision. Whenever I used to use this.setState for things like arrays I'd always manually .slice() them myself, so that does seem like it would be the desired behavior!

Released in 0.2.0!


Documentation Wrong for Instant Scroll Demo

🐛 Current behavior
https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/infinite-scroll/react/
hits is deprecated. The code flat out doesn't work if you copy it into a project. When was this last tested???
🔍 Steps to reproduce
Go to https://codesandbox.io/p/devbox/muddy-brook-nbdfm?file=%2Findex.html and try to build it. Doesn't work.
Live reproduction
https://codesandbox.io/p/devbox/muddy-brook-nbdfm?file=%2Findex.html
💭 Expected behavior
The demo above, linked from the page, won't even build. Again, when was the last time this was tested???
Package version
Irrelevant - Online Documentation is wrong.
Operating system
OSX Sequoia
Browser
Edge Latest
Code of Conduct

[X] I agree to follow this project's Code of Conduct

What do you mean it doesn't build? the example works for me perfectly fine. hits indeed should be changed to items, but for now both keys still work.
Build also seems to work:

I've made a pull request in the documentation to fix the hits that was still documented to use items like in the rest of the document


Can NumbaMinpack be used with Cuda?

Hi @Nicholaswogan.
Thanks for the great tools! I was looking at this stack overflow discussion where you posted an example of using NumbaMinpack for curve fitting.
I was wondering if NumbaMinpack (and this general approach you showed in that thread -- and copied below) can be made to work with Numba's cuda functionality. Do you know if that's possible/straightforward?
from NumbaQuadpack import quadpack_sig, dqags
from NumbaMinpack import minpack_sig, lmdif
import numpy as np
import numba as nb
import timeit
np.random.seed(0)

x = np.linspace(0,2*np.pi,100)
y = np.sin(x)+ np.random.rand(100)

@nb.jit
def fitfunction(x, A, B):
    return A*np.sin(B*x)

@nb.cfunc(minpack_sig)
def fitfunction_optimize(u_, fvec, args_):
    u = nb.carray(u_,(2,))
    args = nb.carray(args_,(200,))
    A, B = u
    x = args[:100]
    y = args[100:]
    for i in range(100):
        fvec[i] = fitfunction(x[i], A, B) - y[i]
optimize_ptr = fitfunction_optimize.address

@nb.cfunc(quadpack_sig)
def fitfunction_integrate(x, data):
    A = data[0]
    B = data[1]
    return fitfunction(x, A, B)
integrate_ptr = fitfunction_integrate.address

@nb.njit
def fast_function():
    try:
        neqs = 100
        u_init = np.array([2.0,.8],np.float64)
        args = np.append(x,y)
        fitparam, fvec, success, info = lmdif(optimize_ptr , u_init, neqs, args)
        if not success:
            raise Exception

        lower = 0.0
        uppers = np.linspace(np.pi,np.pi*2.0,200)
        solutions = np.empty(len(uppers))
        for i in range(len(uppers)):
            solutions[i], abserr, success = dqags(integrate_ptr, lower, uppers[i], data = fitparam)
            if not success:
                raise Exception
    except:
        print('doing something else')

fast_function()
iters = 1000
t_nb = timeit.Timer(fast_function).timeit(number=iters)/iters
print(t_nb)

Thanks.

Thanks! Unfortunately, I do not think you can’t use numba minpack with cuda. These extensions are compiled for the CPU, so I don’t think there is any way it can run on the GPU. There would need to be a cuda GPU implementation of minpack, which I do not think exists.


Extract distribution

Separate the actual distribution from the layer.

[x] Move distro parts to new project — https://github.com/jhnc-oss/protos/pull/1
[x] Remove distro parts from this repo — #80
[x] Update description (Readme, projects, topics)
[x] Update Manifest — https://github.com/jhnc-oss/yocto-manifests/pull/25

Distro is now at https://github.com/jhnc-oss/protos


Evolution visualization: Node not expected to exist in the object manager does exist.

The assertion in Assets/SEE/Game/Evolution/EvolutionRendererAddNodes.cs fails when the evolution of SEE's clones is visualized.
How to reproduce:

Choose and apply the configuration file Data\GXL\animation-clones-SEE\clones.cfg for the EvolutionCity.
Enable the EvolutionCity.
Run the game and start the automated visualization of the evolution. Occasionally, the assertion is failing.

The addition of a node appears to be called premature. The caller is unknown and the circumstances unclear because of the callback mechanism by DoTween used. More investigation is needed.


Add m2m fields from InventoryItem/VirtualMachine to SoftwareImageFile

Closes #5280
What's Changed

Add m2m from InventoryItem to SoftwareImageFile

Update SoftwareImageFileQuerySet.get_for_object to use this field

Add m2m from VirtualMachine to SoftwareImageFile

Update SoftwareImageFileQuerySet.get_for_object to use this field

Add default_image field to SoftwareImageFile (from DLM)

Remove is_default from DeviceTypeToSoftwareImageFile m2m through table model
Update SoftwareImageFileQuerySet.get_for_object to use the default_image field

Consolidate migration files

Screenshots

💥 InventoryItem edit/detail view looks like VirtualMachine
TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

I noticed we still had templates pointing to the deprecated generic/object_edit.html so I did a quick find/replace to change those to generic/object_create.html


Need to use createVolume instead of create

Need to use createVolume instead of create for disk creation here: https://github.com/ppc64le-cloud/powervs-csi-driver/blob/main/pkg/cloud/powervs.go#L248
Create method is deprecated and will be removed soon: https://github.com/IBM-Cloud/power-go-client/issues/91#issuecomment-990022383

/assign


Update concept-authentication-methods.md

Added Microsoft Authenticator (Passwordless) and changed the default one to Microsoft Authenticator (Push)

@Justinha
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Error whili wrapping MozJpegSharp

Hi, thanks for this great project! I am trying to implement MozJpegSharp image compression based on the HelloWorld example from the ReadMe you provided, and I'm getting an error. Here are the relevant files:
using System;
using DotNetJS;
using Microsoft.JSInterop;
using MozJpegSharp;

namespace ImageCompression;

public partial class Program
{
    // Entry point is invoked by the JavaScript runtime on boot.
    public static void Main()
    {
        var hostName = GetHostName();
        Console.WriteLine($"Hello {hostName}, DotNet here!");
    }

    [JSInvokable]
    public static string CompressBase64(string base64, int quality)
    {
        var bytes = Helpers.Base64ToByteArray(base64);
        var result = MozJpeg.Recompress(bytes.AsSpan(), quality, TJSubsamplingOption.Chrominance420, TJFlags.None);
        return Helpers.ByteArrayToBase64(result);
    }
}

ImageCommpression.csproj

<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">

    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <EmitSourceMap>true</EmitSourceMap>
        <EmitTypes>true</EmitTypes>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="DotNetJS" Version="0.3.12" />
        <PackageReference Include="MozJpegSharp" Version="2.1.12" />
        <PackageReference Include="MozJpegSharp.GdiPlus" Version="2.1.12" />
    </ItemGroup>

</Project>

JS function
<script src="bin/dotnet.js"></script>

<script>
	dotnet.ImageCompression.GetHostName = () => "Browser";

	window.onload = async function () {

		await dotnet.boot();
                var data = "<SOME BASE64 IMAGE>";
                const compressed = dotnet.ImageCompression.CompressBase64(data, 85);
		console.log(`Image: , ${compressed}!`);
	};
</script>

I ran dotnet publish to create the dotnet.js file and I am able to import the module, but I receive an error in console:

Uncaught (in promise) Error: System.DllNotFoundException: turbojpeg

When I run same program as a console application everything is working fine.
Do you have any ideas what might be a problem?

Make sure you're explicitly using something from that DLL, otherwise it'll be trimmed. https://devblogs.microsoft.com/dotnet/app-trimming-in-net-5

I am calling the method MozJpeg.Recompress(inBytes.AsSpan(), quality, subsampling, flags) from MozJpegSharp, which is referenced as NuGet package in my project.
I have tried to add assembly-trimming, like:
<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">
    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <EmitSourceMap>true</EmitSourceMap>
        <EmitTypes>true</EmitTypes>
		<PublishTrimmed>true</PublishTrimmed>
		<TrimMode>CopyUsed</TrimMode>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="DotNetJS" Version="0.3.12" />
        <PackageReference Include="MozJpegSharp.Core" Version="2.1.12" />
    </ItemGroup>
</Project>

but then I get the following error:

Uncaught (in promise) Error: System.TypeLoadException: Could not resolve type with token 0100001e from typeref (expected class 'System.Runtime.Serialization.ISerializable' in assembly 'System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e')

Any ideas what might be a problem and how to resolve it?

Something in that third party lib is probably trying to access System.Runtime.Serialization.ISerializable via reflection, while trimmer can't track that kind of dependencies. Try preserving the type via linker: https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/configure-linker


gmt: 6.1.1 -> 6.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/GenericMappingTools/gmt/releases.
meta.description for gmt is: "Tools for manipulating geographic and cartesian data sets"
meta.homepage for gmt is: "https://www.generic-mapping-tools.org"
meta.changelog for gmt is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0/bin/gmt passed the binary check.

/nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0/bin/isogmt passed the binary check.

/nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0/bin/gmt-config passed the binary check.

/nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0/bin/gmtswitch passed the binary check.

/nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0/bin/gmt_shell_functions.sh passed the binary check.

4 of 5 passed binary check by having a zero exit code.

4 of 5 passed binary check by having the new version present in output.

found 6.2.0 with grep in /nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0

found 6.2.0 in filename of file in /nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0

directory tree listing: https://gist.github.com/b0980ec754ba6ceef7dfecf27bf0b926

du listing: https://gist.github.com/16a1cd3f7876cdf3b7fa371725a767f1

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gmt
python38Packages.pygmt
python39Packages.pygmt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gmt https://github.com/r-ryantm/nixpkgs/archive/91a67c5c1a414d1e7c7eac6dd50d70e203713be7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0
ls -la /nix/store/10h5ik8qsp9ji08v0p79bvi1scxylnqa-gmt-6.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

gmt
python38Packages.pygmt
python39Packages.pygmt

Maintainer pings
cc @tviti for testing.

Result of nixpkgs-review pr 126037 at 91a67c5c run on x86_64-linux 1

3 packages built successfully:

gmt
python38Packages.pygmt
python39Packages.pygmt

1 suggestion:

error: no-flags-spaces
cmakeFlags cannot contain spaces, please use cmakeFlagsArray in Bash.
Near pkgs/applications/gis/gmt/default.nix:34:3:
   |
34 |   cmakeFlags = [
   |   ^

Result of nixpkgs-review pr 126037 run on x86_64-linux 1

3 packages built:

gmt
python38Packages.pygmt
python39Packages.pygmt


Fix broken link in README.md

PR Summary
Fix #12886
PR Context
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@PoshChan Please rebuild static

@iSazonov, successfully started rebuild of PowerShell-CI-static-analysis

@xtqqczze It seems another link died. Could you please look?

Issue opened: https://github.com/ironmansoftware/universal-dashboard/issues/1652

@PoshChan Please rebuild static

@iSazonov, successfully started rebuild of PowerShell-CI-static-analysis

@xtqqczze Thank you for your contribution!


[#17] fix sites that require headers and auth

Issue
Fixes #17
Details
Allow core web vitals to work on websites that require auth and headers.
CY.vitals will work with params passed
cy.vitals({
      url: 'https://www.someQaEnvironment.com/',
      headers: {
        "Accept-Encoding": "gzip, deflate"
      },
      auth: {
        username: 'qa',
        password: 'examplepass',
      }
 }); ✅

Note: CY.visit will still not work:
cy.visit({
      url: 'https://www.someQaEnvironment.com/',
      headers: {
        "Accept-Encoding": "gzip, deflate"
      },
      auth: {
        username: 'qa',
        password: 'examplepass',
      }
 }); 🚫

TODO:

update tests
update docs to introduce new options on cy.vitals({})

CheckList

[x] PR starts with [#ISSUE_ID].
[ ] Has been tested (where required).

@MichaelDimmitt is this ready for review? Clearing notifications and noticed this is still in draft?

It works as is and feel free to give feedback
I will try to finish it today so that tests are passing.
And will double check to see if there are any breaking changes for people doing custom things.

fix tests
update docs
make sure I broke no custom people.

const visitWithWebVitalsSnippet = (url, auth = undefined, headers = undefined) => {
  cy.intercept({ method: "GET", url, times: 1 }, (req) => {
    req.continue((res) => {
      const body = res.body.replace(
        /<head(>|.*?[^?]>)/,
        `<head$1${WEB_VITALS_SNIPPET}`
      );
      res.send(body);
    });
  });
  if(auth && headers) {
    return cy.visit(url, { auth, headers, log: false });
  }
  else {
    return cy.visit(url, { log: false });
  }
};

debating between these two options:
const visitWithWebVitalsSnippet = (url, auth = null, headers = {}) => {
  cy.intercept({ method: "GET", url, times: 1 }, (req) => {
    req.continue((res) => {
      const body = res.body.replace(
        /<head(>|.*?[^?]>)/,
        `<head$1${WEB_VITALS_SNIPPET}`
      );
      res.send(body);
    });
  });

  return cy.visit(url, { auth, headers, log: false });
};

@cmorten , can you trigger a test re-run

🚀


Chain/SyncMgr : Review use of node height

Currently the chain provides a method for the current height of the blockchain, we could also have this in syncmanager. Opening this to track discussion of this

hm. And what was the initial idea about moving it to syncmanager?

Closing as obsolete, see #283, #307.


ScribblejrExt crashes when drawing text with a color code

It sounds like this should work:
ScribblejrAddColor("c_red", #cc0000);
-----
var str = "The quick [c_red]brown fox[/c] jumped over the lazy dog";
var jr = ScribblejrExt(str, fa_left, fa_middle, undefined, 1);
jr.Draw(200, 250);

but instead it crashes with Variable __ScribblejrClassExt._forceNative(101352, -2147483648) not set before reading it
It looks like there's either an incomplete or removed feature here, since everywhere else the variable is called _forceNative_UNUSED. Removing the check for the variable works fine.

Whoops, silly typo my end.

a8e9e25


XSpec Users Meetup at XML Prague 2018

I submitted a proposal for an XSpec Users Meetup at XML Prague and it has been accepted. The first XSpec Users Meetup will take place on 8th February 2018 between 5.30 and 7pm at the University of Prague in the frame of XML Prague 2018.
I would like to use this issue to organise the preparatory work for our first XSpec Users Meetup. Together with other XSpec contributors who I know will attend XML Prague I sketched the following programme for the event:

Overview of XSpec (5 minutes - @cirulls)
XSpec 101 (10 minutes - @cirulls)
oXygen plugins (10 minutes - @AlexJitianu)
New features (e.g. Schematron support) (10 minutes - @cirulls)
Maven plugin (10 minutes - @cmarchand)
Use case of integration test with Maven and XSpec  (10 minutes - @mricaud)
How to contribute to XSpec (5 minutes - @cirulls)
Q & A

For all the XSpec users who will attend XML Prague 2018: please do join us! We may be able to slot in another 5-10 minute presentation, would you like to propose a topic?
For all those who can't attend XML Prague: we will post updates and materials in this issue to keep you posted, feel free to contribute with ideas and suggestions even if you can't attend in person.

Here are my slides for the XSpec Users Meetup. I will also present Schematron support in XSpec during the Schematron Users Meetup (here are the slides) to spread the word about this new feature within the Schematron community.

Here is my repo for "Use case of integration test with Maven and XSpec":
https://github.com/mricaud/xml-prague-2018-xspec-integration-testing
You'll find a working example and a few slides.

My slides of Using Maven to unit test with XSpec :
unit-tests-with-maven.pdf

Closing this issue as the presentations have been uploaded and linked here.


HSEARCH-383 Hibernate Search does not respect the @AccessType annotation in respect to @Id fields.

https://hibernate.atlassian.net//browse/HSEARCH-383
I doubt the problem was still relevant even in Search 5, but the test makes sense, so let's just add it.

Pull Request Test Coverage Report for Build 1

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.697%

Totals

Change from base Build 9:
0.0%

Covered Lines:
10128

Relevant Lines:
11682

💛  - Coveralls

Merged, thanks


Split treemaps?

As described in “Ordered and Unordered Treemap Algorithms and Their Applications on Handheld Devices” by Engdahl.

inspired by @thomasp85 ggforce implementation and the original paper, I have assembled an ugly mix of code from these two sources and other d3 treemap code.  Before I submit pull with proper tests, I wanted to first make sure that this (with much revision of course) would be welcome.
@mbostock I forked your d3 source treemap (thanks so much for this!) and applied the new split algorithm http://bl.ocks.org/timelyportfolio/e480359ea953d96a38a4466187d3d62b.

In just a little bit, I will also apply the d3v4 treemap with tile input to more closely inspect differences.

Fantastic! Implementation looks relatively straightforward which is always nice! Thank you for doing this and I look forward to the PR.

Just converted this to add treemapSplit http://bl.ocks.org/timelyportfolio/2bbd4cedf597eae6a5e90412d9df1c1f.  (Had no idea d3.hierarchy had changed so much since this early iteration).  I absolutely love all the convenience functions added in d3.hierarchy.

started and it seems to work correctly on smaller test networks and the d3 source example with much better speed, but now on my test on a larger network I get
Uncaught RangeError: Maximum call stack size exceeded(…)

I'll research and debug.

Certainly no rush whatsoever, but is this something you would like me to continue to push forward?  Thanks for everything, and please, please, please let me know if ever in any strange little way whatsoever I can help you in any way.

Turns out—with a bug fix and a small improvement—these are the same thing as binary treemaps which were implemented in<EMAIL_ADDRESS>(d3@4.0)!

👍 good learning experience.  Thanks!


Feature idea: HTTP response code selection for page response options

https://feedback.omg.lol/16605122973163


Add migrating documentation

I saw that a few people find that configuring rules is not straight forward. We should probably include documentation and maybe even a script that converts Settings.StyleCop files into rule sets.
See
http://stackoverflow.com/questions/31313249/stylecop-integration-with-visual-studio-2015-rc/31741929#31741929
and
https://twitter.com/pedrolamas/status/627593865323761664

I made small F# script (probably not very generic one, but works for me). Maybe someone will find it useful
http://fssnip.net/ss


Facing Issue Getting error

System.Net.WebException: 'The remote server returned an error: (400) Bad Request. - {"error":"invalid_request","error_description":"AADSTS90002: Tenant 'http://waii.sharepoint.com' not found. This may happen if there are no active subscriptions for the tenant. Check to make sure you have the correct tenant ID. Check with your subscription administrator.\r\nTrace ID: b44cfe10-e7d2-4144-ac06-c7e2d27a5e00\r\nCorrelation ID: dd6de0dd-b259-4618-a6ee-a291066914dc\r\nTimestamp: 2021-05-20 12:56:37Z","error_codes":[90002],"timestamp":"2021-05-20 12:56:37Z","trace_id":"b44cfe10-e7d2-4144-ac06-c7e2d27a5e00","correlation_id":"dd6de0dd-b259-4618-a6ee-a291066914dc","error_uri":"https://accounts.accesscontrol.windows.net/error?code=90002"}'

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

ID: 35a3017a-6d6c-237f-fc57-94247a8f7bf6
Version Independent ID: 93413445-18fa-9245-ea64-1c1d789dce1e
Content: Granting access using SharePoint App-Only
Content Source: docs/solution-guidance/security-apponly-azureacs.md
Product: sharepoint
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Your URL is invalid. You forgot the 's' for 'https://waii.sharepoint.com'


[No browser padding] - Padding is not applied to the right sidebar

When the sidebar is on the left, the padding on the right is removed (see image below).

But when the sidebar is on the left, the padding appears on the left, so the theme is not correctly applied for all configurations.
The corner of the sidebar is not correctly applied either

This will be fixed for next Zen release 👍🏽


Data not properly loaded in the ngx-datatable  when loaded in modal

Hi Team,
I facing issue when load the ngx-datatable in modal. can you help me to resolve this.
<modal [show-modal]="isPreviewSummaryPopup" class="print-summary-popup-container">

Preview Summary

<button class="pull-right back-to-page-button" (click)="closePreviewSummaryPopup()">

<ngx-datatable class="material" [rows]="previewSummaryDataList" [columnMode]="'flex'" [columns]="previewSummaryGridColumns" [headerHeight]="50" [scrollbarV]="true">

@Hemavaan can you make a plunker demo?


fetchgit fails behind proxy

Describe the bug
In my work environment, internet connectivity is through proxy. Trying to build ghcjs-base fails due to git fetch error.
$ nix-shell -p haskellPackages.ghcjs-base
...
exporting git://github.com/ghcjs/ghcjs-base (rev 01014ade3f8f5ae677df192d7c2a208bd795b96c) into /nix/store/rw6wianl67igvdka1jrddbsrq3q2kri8-ghcjs-base-01014ad
Initialized empty Git repository in /nix/store/rw6wianl67igvdka1jrddbsrq3q2kri8-ghcjs-base-01014ad/.git/
fatal: unable to look up github.com (port 9418) (Name or service not known)
fatal: unable to look up github.com (port 9418) (Name or service not known)
Unable to checkout 01014ade3f8f5ae677df192d7c2a208bd795b96c from git://github.com/ghcjs/ghcjs-base.
...

To Reproduce
Run below command behind a proxy.
$ nix-shell -p haskellPackages.ghcjs-base

Expected behavior
fetchGit operation must succeed.
Additional context
I ran into this when trying to build https://github.com/dmjio/miso
Metadata
[1 copied, 0.0 MiB DL]
 - system: `"x86_64-linux"`
 - host os: `Linux 4.15.0-55-generic, Ubuntu, 16.04.6 LTS (Xenial Xerus)`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - channels(a0393778): `"nixpkgs-19.03.173266.bd1358fed9d, nixos-16.09-16.09.1763.51d4de9"`
 - nixpkgs: `/home/a0393778/.nix-defexpr/channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

I fixed it by going to /nix/store and search for ghcjs-base ....drv
Then I changed
git://github.com/ghcjs/ghcjs-base
to
https://github.com/ghcjs/ghcjs-base


Steerd presto operator 0.1.0

Signed-off-by: gurushantj<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?

[ ] Is your submission signed?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[ ] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@gurushantj there is no such category "Distributed SQL". List of categories are listed at https://github.com/operator-framework/community-operators/blob/master/categories.json . Please choose one of them. Thanks

@gurushantj there is no such category "Distributed SQL". List of categories are listed at https://github.com/operator-framework/community-operators/blob/master/categories.json . Please choose one of them. Thanks

@gurushantj there is no such category "Distributed SQL". List of categories are listed at https://github.com/operator-framework/community-operators/blob/master/categories.json . Please choose one of them. Thanks

@mvalarh Thanks for guiding me , fixed the same.

@gurushantj there is no such category "Distributed SQL". List of categories are listed at https://github.com/operator-framework/community-operators/blob/master/categories.json . Please choose one of them. Thanks

@mvalarh Thanks for guiding me , fixed the same.

@gurushantj there is no such category "Distributed SQL". List of categories are listed at https://github.com/operator-framework/community-operators/blob/master/categories.json . Please choose one of them. Thanks

@mvalarh Thanks for guiding me , fixed the same.

@mvalarh : Could you please guide me, what shall I do next in order to get review this PR?

@gurushantj there is no such category "Distributed SQL". List of categories are listed at https://github.com/operator-framework/community-operators/blob/master/categories.json . Please choose one of them. Thanks

@mvalarh Thanks for guiding me , fixed the same.

@mvalarh : Could you please guide me, what shall I do next in order to get review this PR?

@gurushantj, please check Error: Value json: line 0: invalid character ''\\\\'' looking for beginning of object key string: error decoding example CustomResource
https://github.com/operator-framework/community-operators/pull/2973/checks?check_run_id=1705586037#step:3:548

@gurushantj, please check Error: Value json: line 0: invalid character ''\\\\'' looking for beginning of object key string: error decoding example CustomResource
https://github.com/operator-framework/community-operators/pull/2973/checks?check_run_id=1705586037#step:3:548

@gurushantj, please check Error: Value json: line 0: invalid character ''\\\\'' looking for beginning of object key string: error decoding example CustomResource
https://github.com/operator-framework/community-operators/pull/2973/checks?check_run_id=1705586037#step:3:548

Thanks @J0zi for pointing, Fixed and pushed.

@gurushantj, please check Error: Value json: line 0: invalid character ''\\\\'' looking for beginning of object key string: error decoding example CustomResource
https://github.com/operator-framework/community-operators/pull/2973/checks?check_run_id=1705586037#step:3:548

Thanks @J0zi for pointing, Fixed and pushed.

@gurushantj It look great, good job:)

@gurushantj It look great, good job:)


[SPARK-22049][DOCS] Confusing behavior of from_utc_timestamp and to_utc_timestamp

What changes were proposed in this pull request?
Clarify behavior of to_utc_timestamp/from_utc_timestamp with an example
How was this patch tested?
Doc only change / existing tests

CC @HyukjinKwon as I think we talked about this a long time ago

Test build #81918 has started for PR 19276 at commit 3ff334a.

Test build #81918 has finished for PR 19276 at commit 3ff334a.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81918/
Test FAILed.

Test build #81919 has started for PR 19276 at commit fc10be8.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81919/
Test FAILed.

Test build #81920 has started for PR 19276 at commit 87874b6.

LGTM

Test build #81920 has finished for PR 19276 at commit 87874b6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/81920/
Test PASSed.

Test build #81983 has started for PR 19276 at commit d81acdc.

Test build #81983 has finished for PR 19276 at commit d81acdc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/81983/
Test PASSed.

Merged to master.


Add saved entities

Hello. This is an amazing and very helpful tutorial. I have a question. I do save every change fo an image entity in my local database so that i can recreate the entity's matrix. What i want is to add that entity again in the MotionView ad the same scale position and rotation as it was. I am passing the saved Matrix but the bitmap seems to be with the original bitmaps size with no scaling and no rotation.

How do you save the entities? i have problem to serialize the ImageEntity

I actually have another object and just get the matrix of the MotionEntity split its values and save theme in my local database. And when i query them, i recreate the matrix based on these values


[BIOMAGE-1390] Remove validation for feature files

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-1390
Link to staging deployment URL
Links to any Pull Requests related to this
Anything else the reviewers should know about the changes here
We are removing validation for feature files since gene IDs can be in so many formats.
We are also adding more logic to the pipeline to replace all characters in feature names known to cause issues with R/Seurat.
Changes
Code changes
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Testing

[ ] Unit tests written
[ ] Tested locally with Inframock (with latest production data downloaded with biomage experiment pull)
[ ] Deployed to staging

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[ ] Relevant Github READMEs updated
[ ] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[ ] Photo of a cute animal attached to this PR

We are also adding more logic to the pipeline to replace all characters in feature names known to cause issues with R/Seurat.

Is this being done in a different ticket?

We are also adding more logic to the pipeline to replace all characters in feature names known to cause issues with R/Seurat.

Is this being done in a different ticket?

Same ticket but a different PR in pipeline that @ogibson-biomage was planning to do


WxyChat

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: http418:x: http600http418 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.