Keep getting an annoying warning message since version 1.0.1

Hi,
I'm keep getting an annoying warning message in the browser console after I upgrade to version 1.0.1 or 1.0.2, Every time I navigate to a different route...:
Warning: You cannot change ; it will be ignored
I've checked and made sure that routes prop nor the children prop of the Router has not been modified, (maybe react is doing some internal things)...
Does not happen in version 1.0.0 or lower, force me to keep react-router to be 1.0.0...
Is this a bug?
Thank you.

Can you copy/paste your code that renders the <Router/>

The warning was a previously missing one - something you are doing is changing the set of routes passed into your <Router>, and we currently don't support that. This is to let you know that you are doing something potentially dangerous and wrong.

I too just started getting this warning after upgrading to 1.0.2. It occurs immediately after webpack's hot loader reloads the modules after an update.
I don't see anything unusual about how my Router is defined:
export default class App extends Component {
	render () {
		return (
			<Router history={history}>
				<Route component={AppView} path="/">
					<IndexRoute component={Home} />
					<Route component={Home} path="/home" />
					<Route component={Changelog} path="/changelog" />
					<Route component={Loader} path="/:type/:component" />
					<Route component={FourOhFour} path="*" />
				</Route>
			</Router>
		);
	}
}

render(<App />, document.getElementById('App'));

Everything continues to work as normal, but the warning pops up after any module is hot reloaded.

Hot reloading routes doesn't work, I'm pretty sure, so that sounds like an appropriate error in context.

Thanks for your reply and sorry for not getting back in time.
I don' think I'm doing anything special there. First I thought it was because it was because I was passing context down from parent, (I've move context from Router to Canvas for testing) but even I've remove context it still happening...  I'm also using webpack.
Here's my route setup:
function getRoutes(state) {
return (

);
}

Btw I'm not using hot reloading... I'm using react-transform.

@DrkCoater react-transform is a tool that is built on hot reloading (the module.hot API, specifically). It only supports the hot reloading of pure React components. react-router uses objects and functions that exist outside of React's component infrastructure, so react-transform can't manage their reloading. We are looking to add hot reload support into router in a future version, though.

thanks. I still don't quite understand what taion meant by "Hot reloading routes doesn't work,"... Is that mean Hot reloading not working so it's causing warning message appear? Trying to identify whether it's a configuration issue or coding issue now.

Hot reloading of routes doesn't yet work. We don't have any mechanism or API for replacing routes in place. So changing your route config will not be reloaded into your app during development until you refresh the full page.

Thanks @timdorr That's fine. We can do manually refresh. But it doesn't explains why the warning message keep showing up...
My router is located at:
https://github.com/DrkCoater/superspintt/blob/debugrouter/src/routes.js

I want to update my routing logic along with the state of my app (I'm using redux).  So say I have a list of todos in my store, and each todo has it's own page.  I want to do a check in the component prop of the /todo/:id route to see if my state contains that todo, and render an error page if it does not.  I have this working, but each time the state is updated, this warning shows up.
Is this something react-router is not intended to handle? If not, do you have any recommendations?

@taion so does this mean that if I change absolutely anything inside of a component that is being hot loaded that it will always "warn" me now due to it being inside of a route?

@jonstuebe That seems to be the behavior that I see too and it isn't very useful if I understand all of the points here.

The warning was a previously missing one - something you are doing is changing the set of routes passed into your , and we currently don't support that. This is to let you know that you are doing something potentially dangerous and wrong.

So according to @taion it sounds like the warning was only intended to show when the list of routes have changed and not necessarily the components to which those routes lead. If this is the case then perhaps a new issue needs to be opened to report that the warnings are showing when they are unintended. I think the fact that this issue used the word "annoying" that it may be safe to assume that original issue here was not complaining about a useful warning that would result from actually making a change directly to the routes.
This warning happens to be the last in a list of frequent warnings in an app I'm developing and it causes a bunch of noise so I'm eager to resolve what ever underlying issue is causing them.

Things will break whenever the set of routes breaks referential identity. Just don't hot reload your routes.js or whatever – it will do no good.

@taion how prevent routes.js from hot reloading? Is this possible with react-hot-loader?

@bmamouri
if (module.hot) {
  module.hot.decline("./routes.js");
}

I am having the same issue here, but with React-Intl v2.0.0-beta-2.
If I update the locale of the new <IntlProvider> provided by React-Intl which is wrapping the <Router>, the router thinks that I am trying to hot reload the Routes (or maybe React-Intl is effectively hot reloading the Routes, but I think it is only updating the context).
Here is my code:
const Root = React.createClass({
  PropTypes: {
    siteCurrentLocale: PropTypes.string.isRequired
  },

  render () {
    const intlData = {
      locale:   props.siteCurrentLocale,
      messages: i18n[props.siteCurrentLocale]
    }

    return (
      <IntlProvider key="intl" {...intlData}>
        <Router history={ history } >
          <Route path="/(:locale/)" component={ App } >
            <IndexRoute component={ NewsCardsContainer }/>
            <Route path="/(:locale/)articles" component={ NewsCardsContainer }/>
            <Route path="/(:locale/)article/:id" component={ IndividualNewsContainer }/>
          </Route>
        </Router>
      </IntlProvider>
    )
  }
})

@CedricLor: we worked around the same issue by defining the routes in a constant:
https://github.com/rackt/react-router/blob/latest/docs/guides/basics/RouteConfiguration.md#alternate-configuration
For example:
const routeConfig = [
  { path: '/:locale',
    component: App,
    indexRoute: { component: NewsCardsContainer },
    ...
  }
];

return (
  <IntlProvider key="intl" {...intlData}>
    <Router history={history} routes={routeConfig} />
  </IntlProvider>
)

Great idea. Thanks a lot.

I'm running into the same problem, please view my sample code below. I use onEnter to handle authentication so I can navigate to correct pages base on the authenticated flag:

_requireAnonymous(nextState, replaceState) {
  if (isAuthenticated) {
    replaceState({nextPathname: nextState.location.pathname}, '/dashboard')
  }
  return true
}

<Router history={history}>
  <Route path='/.' component={Loader}/>
  <Route component={Main}>
    <Route path='/' component={Container}>
      <IndexRoute component={Default} onEnter={::this._requireAnonymous}/>
      <Route path='login' component={Login} onEnter={::this._requireAnonymous}/>
      <Route path='register' component={Register} onEnter={::this._requireAnonymous}/>
      <Route path='dashboard' component={dashboard}/>
    </Route>
    <Route path='/logout' onEnter={this.props.logout} />
  </Route>
</Router>

This LoC has checked that the Router's children were changed, if I remove onEnter handler, the warning will disappear. Seems like I'm doing the authentication checker in a wrong way, do you have any suggestion for me?

@crashbell I've run into the same error but it seems the problem is if I have the component wrapped in a react-redux connect export default connect(state => state)(App) where App is defined as in you mentioned. In this case @noahmiller's solution worked though I had to define the routes config in the constructor if your using the class syntax.

thanks @SimeonC! It also works fine to me.

Strangely this was happening because I had a reducer called application declared in my Redux store.
I changed it from
export {default as application} from './ApplicationReducer';
to
export {default as app} from './ApplicationReducer';
and that fixed the issue for me with routes being re-rendered. Is application some sort of reserved name?

I'm having this issue in a react-redux scenario as well and I'm guessing that that is my problem although I'm not sure if I understand white how to follow @noahmiller's workaround example to move from Route components to a configuration. I don't want to screw something up in the process just to work around the warning.

Oh, just changing this below seemed to do the same trick for me.

const routes =
    <Route path="/" component={App}>
        <IndexRedirect to="default"/>
        <Route name="one" path="one" component={One}/>
        <Route name="two" path="two" component={Two}/>
        <Route name="three" path="three" component={Three}/>
        <Route path="*" component={NotFound} />
    </Route>;

    return (
      <Provider store={store}>

            <Router history={history}>
                {routes}
            </Router>
            {__DEV__ && <DevTools />}

      </Provider>
    );

Thanks @noahmiller!

Same issue but only when I call parent handling functions.
Example. My component holds data like the current logged user, current project, ...
getInitialState: function (){ return { project: {}, user: {} },
As well as handlers...so that my whole UI updates depending on the state...ex:
setProject: function(newProject){ this.setState({project:newProject}); }
<Router>
		<Route path="/" component={Layout} {...this.state} setProject={this.setProject}>
			<IndexRoute name="projects" component={Projects}></IndexRoute>
			<Route path="/product/:productId/:view" name="product" component={Product} />
			 <Route path="*" component={NotFound}/>
		</Route>
</Router>

As soon as I call the setProject in the my child component, I get the error...
If you go for defining your ROUTES as a constant, how do you pass states and handlers?
EX
const routesConfig =  (
	<Router history={browserHistory}>
		<Route path="/" component={Layout} {...this.state} setProduct={this._setProduct}>
			<IndexRoute name="products" component={Products}></IndexRoute>
			<Route path="/product/:productId/:view" name="product" component={Product} />
			<Route path="scrum" name="scrum" component={Scrum}></Route>

			<Route path="login" component={Login}></Route>
			<Route path="register" component={Register}></Route>
			<Route path="forgotten" component={Forgotten}></Route>

			 <Route path="*" component={NotFound}/>
		</Route>
	</Router>
);

this in the example above is not defined. Any ideas?

@rackt/redux Do you have any recommendations for what to do here? rackt-redux <Provider> makes the same check, with a caveat that it only warns once. Should we just do that here?

@desduvauchelle You should be connecting your components to the store set via <Provider>. You don't need to, nor should you, try to pass them as props via <Route>. The connect function provides you with a lot of rendering optimizations specific to Redux and pulling data from state.
@taion It appears to be because most people are defining and rendering their routes within a component. And, as is usually the case, they have react-transform set up, which is re-rendering their routes repeatedly, causing this error to trip. Routes should be defined outside of a component. I put them into a separate file, for example. This route config should not include the <Router>, as you will need to define that separately for client and server contexts. I have this, verbatim, in one of my apps working just fine:
ReactDOM.render(
  (
    <Provider store={store}>
      <Router history={browserHistory} children={routes(store)} />
    </Provider>
  ),
  document.getElementById('root')
);

Everything below that is my app code and gets hot reloaded by react-transform just fine.

Same situation like @globexdesigns. Have you solved this? For me, the error still there even I separate routes into a single file and module.hot.decline that file.

@mjackson and I were just talking about writing a custom renderer for route config, instead of simply stripping props. The idea was to allow route config to be composed the same way any components are composed, I wonder if it would also help us in this scenario ...

@ryanflorence It will work to the extent that it can resolve https://github.com/rackt/react-router/issues/2182, but I think those two are somewhat orthogonal. I do think having a separate transition manager makes this easier, though.

To hot-swap routes it seems like we'd need to diff them to know if we need to update anything in the transition manager. If we actually "render" routes (with a custom renderer), we might get the diffing for free.

We can always re-run the match if the routes change. I think the issue is actually the "leave" transition hooks.

I've the same Warning, might it be webpack-dev-server causing it for me?  In which case I can safely ignore?

FYI - Another workaround for this error message is to provide a unique key for Router so that it gets reconciled to a new instance. e.g.
let counter = 0;

class App extends React.Component {
    render() {
        return (
            <Router key={ counter } history={browserHistory}>
                <Route path="/" component={Main}>
                    <Route path="child" component={Child} />
                </Route>
            </Router>
        );
    }
}

ReactDOM.render(<App />, document.body.children[0]);

if (module.hot) {
    counter++;
    module.hot.accept();
}

For everyone still struggling with this message (unrelated to hot-reloading) - I found a solution that works pretty well without including any framework such as Redux or multiple event listenersinside each view component:
Don't pass any of your model to the routes. Trigger model updates in the component that you pass to your "/"-Route, i.e. your main view. Use React.cloneElement() to pass the model to all child route components.
Example:
routes.js
ReactDOM.render(
  <Router history={hashHistory}>
    <Route path="/" component={Main}>
      <IndexRoute component={Some} />
      <Route path="other" name="other" component={Other}>
      <Route path="route" name="view" component={Other}>
    </Route>
  </Router>,
app);

Main.js:
export default class Main extends React.Component {
  constructor(props) {
    super(props);
    this.state = { model: initialModel };
  }

  /*call this function from the outside, from event handlers, actions,
    electron main thread etc. Whatever way you want to set up your app. */
  updateModel(newModel) {
    this.setState({ model: newModel  });
  }

  renderChildren() {
    return React.Children.map(this.props.children, child =>
      React.cloneElement(child, this.state.model)
    );
  }

  render() {
    return (

        { this.renderChildren() }

    );
  }
}

Yes, the only reason you get this warning is because you re-render Router. You can either stop doing it and move setState (or connect in case of Redux) to the top level route handler.
Alternatively you can define your routes outside the root component’s render function:
var routes = <Route>...</Route>

class Root extends Component {
  render() {
    return <Router routes={routes} />
  }
}

Then even re-rendering that component won’t cause different routes to be passed.

@gaearon I am setting everything const, still I get error.
const routes = createRoutes(routeConf);
const history = syncHistoryWithStore(browserHistory, store);
const router = (<Router
  history={history}
  render={applyRouterMiddleware(useRelay)}
  environment={Relay.Store}
>
  {routes}
</Router>
);

ReactDOM.render(<AppContainer><Root store={store} router={router} /></AppContainer>, rootEl);

the error is at the first check on history
/* istanbul ignore next: sanity check */
  componentWillReceiveProps: function componentWillReceiveProps(nextProps) {
    process.env.NODE_ENV !== 'production' ? (0, _routerWarning2.default)(nextProps.history === this.props.history, 'You cannot change <Router history>; it will be ignored') : void 0;

    process.env.NODE_ENV !== 'production' ? (0, _routerWarning2.default)((nextProps.routes || nextProps.children) === (this.props.routes || this.props.children), 'You cannot change <Router routes>; it will be ignored') : void 0;
  },

nextProps.history === this.props.history

what can I do to avoid this?? thanks.

@gaearon after playing around, adding a specific handler like this seems solved the issue
  module.hot.accept(Root, () => {
    console.warn('hot! ./Root');
    ReactDOM.render(<AppContainer><Root store={store} router={router} /></AppContainer>, rootEl);
  });

thanks.

Remembering the original problem that state is being modified at the router level where the routes are dependent on state, here's another option:
<Router key={new Date()} ... >

Cleared up the errors on my end. FWIW this is what my index/main looks like:
const root = document.getElementById('root');

const renderApp = () => {
  const routes = require('./routes').default;

  render(
    <AppContainer>
      <Provider {...stores} children={routes} />
    </AppContainer>,
    root
  );
};

renderApp();

if (module.hot) {
  module.hot.accept('./routes', () => {
    unmountComponentAtNode(root);
    renderApp();
  });

For routes:
const routes = (
  <Router history={browserHistory}>
    <Route path="/" component={App}>
      <IndexRoute getComponent={(location, cb) => {
        require.ensure([], (require) => {
          cb(null, require('~/views/Home'));
        });
      }}
      />
      <Route path="/compose" getComponent={(location, cb) => {
        require.ensure([], (require) => {
          cb(null, require('~/views/Compose'));
        });
      }}
      etc…

I found a very simple solution:
<Router key={Math.random()} history={browserHistory} >...</Router>

does providing a key not cause you to lose state?
I have added they key to a project,  https://github.com/peter-mouland/react-lego#react-hot-loader-v3, and when hot-reloading is complete state is lost.  Without the key i do get the warning, but hot-reload completes keeping state intact

after hot reloading my states stayed the same

@frankwallis's Solution worked for me. Adding a unique key to the router.
let counter = 0
const App=(props)=>{
	counter++
		return (
  		<Router key={counter} history={browserHistory}>

great to hear, must be my app having state problems then 🤔

Here is my workaround, just adding one line:
import React from 'react';
import { Provider } from 'react-redux';
import { Router } from 'react-router';
import routeConfig from '../common/routeConfig';

export default class Root extends React.Component {
  render() {
    const { store, history } = this.props; // eslint-disable-line
    if (!this.routeConfig) this.routeConfig = routeConfig;

    return (
      <Provider store={store}>
        <Router history={history} routes={this.routeConfig} />
      </Provider>
    );
  }
}

I looked at the source code: https://github.com/ReactTraining/react-router/blob/6eeb7ad358f987520f5b519e48bdd31f725cbade/modules/Router.js , the warning is just logged when routes changes, so just always pass the first one to it.

@supnate Thanks for this workaround! It not only has better performance, but it actually works. Because the Math.random() workaround effectively invalidates the whole tree of components and hence prevents the state from being kept upon a hot reload.

@sterjakovigor  太棒了

My two cents. Based on @gaearon's comment, you will actually have to send an array of Routes to avoid JSX warning that you must have a root element.
const routes = [
  <Route path="/" component={Home} />,
  <Route path"/blog" component={Blog} />
]

class Root extends Component {
  render() {
    return <Router routes={routes} />
  }
}

I want to pass props to routes. I am doing it this way but getting error.
Failed prop type: Invalid prop routes supplied to Router in Router
Anyone knows what I am doing wrong
const routeConfig = (type) => {
  return (
  <Route>
  <Route path='/' component={Template}>
    <Route path='/pageform(/:id)' component={PageForm} />
  </Route>

  <Route path='/:pageSlug' component={Page} type=type/>
  </Route>
);
}
class App extends React.Component {
  render() {
    return (
      <MuiThemeProvider muiTheme={getMuiTheme()}>
        <Provider store={store}>
          <Router history={browserHistory} routes={routeConfig type='abc'} />
        </Provider>
      </MuiThemeProvider>
    );
  };
};

I think this will be much better for various environment:
import React from 'react';
import ReactDOM from 'react-dom';
import {AppContainer} from 'react-hot-loader';
import Router from './Router';

const render = (Component) => {
    ReactDOM.render(
        <AppContainer>
            <Component key={module.hot ? new Date() : undefined}/>
        </AppContainer>,
        document.getElementById('root')
    );
};

render(Router);

if(module.hot) {
    module.hot.accept('./Router', () => {
        render(Router);
    });
}

What about don't use redux, and be able to call setState of parent from child?

I getting error while using browserHistroy in react as
'react-router' does not contain an export named 'browserHistory'.
using react-router version of 4.1.1
could someone help me

I am getting this error while routing:
'react-router' does not contain an export named 'browserHistory'.
using react-router version 4.1.1
could someone help me to reslove it


verify_ssl deprecation warning

I saw this in the logs:

Aug 02 10:55:46 vfdaq python[32025]: /home/kitware/distiller/cli/watch/distiller/watch.py:173: DeprecationWarning: verify_ssl is deprecated, use ssl=False instead

closed since this is a duplication of #970


Fix reciprocity issue for from_edge

Fix for #20

@SarahAlidoost I with this PR all tests are passing but I having troubles with a real dataset (shared separately) and the following script:

edges <- sf::st_read("data/street_network_edges_Bucharest.gpkg", quiet = TRUE)
edges <- sf::st_geometry(edges)

angle_threshold <- 150.
from_edge <- c(1)

strokes_from_edge <- rcoins::stroke(edges, angle_threshold = angle_threshold, from_edge = from_edge)

plot(strokes_from_edge)

The output I get is the following one:

where we clearly have an angle that is <150 degrees. I am trying to understand why this is happening..

Hi @SarahAlidoost, I could finally spot the cause of the problem above, it was a bug unrelated to the implementation of  from_edge but related instead of the filtering of links when angle_threshold is set to a value > 0. This should fix the problem!


Increase coverage of BPF sockmap

Extend the syscall definition for BPF_MAP_UPDATE_ELEM to include socket fds, which should make some paths in the sockmap code easier to discover.
Also expand BPF_PROG_ATTACH to include a BPF map fd as the target, since this is used to associate BPF programs with a sockmap.

@pchaigno do you mind taking a look? You did most of the recent changes to bpf descriptions.

Ack. Please ping the PR when you update code.

I applied your fixes, and coverage for the sock map update part looks really nice. The sock map attach thing seems to not have enough information yet to make it efficient.
The problem is that attaching a program to a sockmap is fairly specific:

Create a program with type SK_SB and attach type SK_SKB_STREAM_PARSER
Call map update with prog and attach type SK_SKB_STREAM_PARSER

I think I'll need to investigate more how I can teach syzkaller about this. In the meantime this PR should already improve things a little bit I think.

I applied your fixes, and coverage for the sock map update part looks really nice. The sock map attach thing seems to not have enough information yet to make it efficient.
The problem is that attaching a program to a sockmap is fairly specific:

Create a program with type SK_SB and attach type SK_SKB_STREAM_PARSER
Call map update with prog and attach type SK_SKB_STREAM_PARSER

I think I'll need to investigate more how I can teach syzkaller about this. In the meantime this PR should already improve things a little bit I think.

Right, let's do smaller steps.
The change looks good to me. I will give @pchaigno some time to look at it, and otherwise merge tomorrow.
Re sockmap, I don't what's exactly the best way to improve it. We could introduce a bpf_prog subtype for SK_SB, and then have specialized attach on it only with SK_SKB_STREAM_PARSER and so on. But if we do much custom descriptions for each type, that maybe too much? It's a bit of an art and an exercise in doing trade-off...
But I assume you are running an instance with only bpf syscalls enabled, right? Sometimes it takes few days for the fuzzer to grope the right syscall sequences.

I am going to merge this since there seems to be an agreement this is a step forward. If there are any improvements, please send them as follow ups.
Regarding fine-tuning priorities, I think long term going forward it would be wrong to considerably over-complicate descriptions (introducing sub-unions, splitting structures) in the name of the fine-tuning. "This field is probably somewhat more important than that one" affects just everything. And if we go and rework all descriptions around this, this will massively complicate descriptions and make them more obscure.
Overall I am leaning towards more scalable solutions  and keeping as much readability as possible. Improving fuzzing logic to make better choices and/or using learned sequences in the corpus better looks like much better direction. This will benefit just everything and will also allows us to fine tune these heuristics later, rather then having hard-coded in every piece of descriptions.
One thing I see as more or less reasonable (if somebody would analyze existing descriptions and make a strong case) is addition of priority attribute for union options. I recently added call attributes and I think sooner or later we will end up with struct/union attributes anyway, e.g. for direction/alignment, etc. So I see we could have something along the lines of:
bpf_attach_targets [
	cgroup	fd_cgroup[opt]    (dir[in], prio[1])
	map	fd_bpf_map[opt]    (dir[out], prio[10])
]

At least this does not force us to split unions and encodes what we want to say very explicitly and precisely.

I've also posted this reply to the mailing list. If anybody wants to reply to this, please reply on the mailing list. That discussion much better belongs to the list, rather than this PR.


Add Semigroup and Monoid instances to Op

I suspect these may have been omitted to avoid any confusion with the Dual monoid, but that's just a guess - it's probably not quite a good enough reason not to have them.

Thanks! And uh, sorry about the delay, as usual.


Create thorvg loader and editor

I am thinking about a debugging software that could load file of formats supported by thorvg (mainly I mean tvg, svg and, if supported in future, json), display it and show list of elements. Allow hiding some elements, display paint’s composite as normal and highlight the element if hovered with mouse cursor.
I think about making it system and efl independent (browser app and wasm?).
Please write your comments

Sure, that's a good idea. Thorvg Viewer is the good place to support it, the thing is the manpower to do it. Probably, we can plan it for a next year goal?

https://github.com/Samsung/thorvg.viewer

https://github.com/Samsung/thorvg.viewer

Image file can not drag to viewer on google chrome. version is 95.0.4638.54

https://github.com/Samsung/thorvg.viewer

Image file can not drag to viewer on google chrome. version is 95.0.4638.54

I will test it with this particular chrome version on monday. Could you give me the below informations:
What operating system? Does it occur for a particular file or for all files you tested? Does this file load when you select it using "Add files" button?
Is there something printed in the developer console (Right click anywhere on the page -> Inspect -> Press "esc" -> click Console tab)?

https://github.com/Samsung/thorvg.viewer

Image file can not drag to viewer on google chrome. version is 95.0.4638.54

I will test it with this particular chrome version on monday. Could you give me the below informations: What operating system? Does it occur for a particular file or for all files you tested? Does this file load when you select it using "Add files" button? Is there something printed in the developer console (Right click anywhere on the page -> Inspect -> Press "esc" -> click Console tab)?

Win 10 21H1 Ver 19043.1348


Admin Dashboard - Implement "Delete Organization"

Steps
Creating the organization deleting option

[ ] Create GUI view with selection
[ ] Functionality - connect to the DB

Points: 1

Done


Change contribution PR target branch to main

Resolves #490

Docs Build status updates of commit 3d151ff:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

CONTRIBUTING.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[vite] Files shared between Remix and Express are loaded twice

Reproduction
https://stackblitz.com/edit/remix-run-remix-muutqq?file=server.js,app%2Froutes%2F_index.tsx
Check server.js and routes/_index.tsx (there are comments indicating where).
System Info
System:
    OS: macOS 13.5.2
    CPU: (8) arm64 Apple M1
    Memory: 109.50 MB / 8.00 GB
    Shell: 3.6.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 18.19.1 - ~/.local/share/mise/installs/node/18.19/bin/node
    npm: 10.2.4 - ~/.local/share/mise/installs/node/18.19/bin/npm
    pnpm: 8.7.5 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 123.0.6312.106
    Safari: 16.6

Used Package Manager
npm
Expected Behavior
In the StackBlitz, I'd expect that all imports of foo-service would resolve to the same memory reference.
Actual Behavior
When importing the same module in express code and in Remix code, the module gets loaded "twice" (once the actual module, and the other is its copy bundled in build/server/index.js)
I tried using ssr.external but that doesn't seem to work with relative files, only node_modules?
With the classic compiler, I was able to work by using the server option in remix.config.js, but I can't find a way to that with Vite (I'm not well versed with Vite's options though). If there's any workaround to this problem I'd appreciate. Otherwise, I won't be able to use the new Vite compiler at all in my projects

Interesting. Yeah, I thought that importing directly from app/services from my server file would work, but you're right. The generated build/server/index.js file contains a copy of the imported code.
Anyway, I played around with a bunch of Vite and esbuild flags, but never could get them to combine since they're not built together.
So I got the crazy idea of simply having Remix import my Express server file directly. My server file actually exports the express app (for use in my Vite plugin)
// app/entry.server.tsx
import app from "#server/index";  // import the created express app
export { app }

// rest of entry.server.tsx

Had Remix build the production file and sure enough, the generated file included both my Express code and the Remix stuff.
Ran NODE_ENV=production node ./build/server/remix.js
Voila!

Thanks @kiliman, that's actually not a bad idea
I was able to make it work by (ab)using entry.server.tsx:

create an express app in entry.server.tsx that has the Remix handler and other related express code

you can create the Remix request handler by importing virtual:remix/server-build directly

in my server.ts file I create another express app (this is the one that will actually handle requests)

call the ssrLoadModule() to access the build file
then you can access the "inner" express app with build.entry.module.app (app is how I exported the express app in entry.server.tsx)

It's cool that I get HMR in the server for my entire app (both express and Remix parts)!
You can see the resulting code here: https://stackblitz.com/edit/remix-run-remix-t9pwxg?file=server.js,app%2Fentry.server.tsx
I'm not sure there's anything in Remix side that could be done to make this better, at least make sure the build file won't change too much in the future (but if it does change, that would be easy to catch in dev because it will fail fast). Either way, I do think this is a reasonable workflow and should be supported by Remix somehow.
PS: One thing I noticed is that the server build file exports some of my components and hooks. I could not understand why that happens, but got worried I could get a name conflict with the app in entry.server.tsx


[#1] Handle mismatch between model.config.vocab_size and tokenizer.vocab_size

It's also possible to avoid the error described in the #1 by resizing the model's token embeddings, feel free to close this PR if that's the preferred solution.
model.resize_token_embeddings(tokenizer.vocab_size)

Thank you!


Fixes ENYO-2866 blur Spotlight from previous panel when transitioning off

Enyo-DCO-1.1-Signed-off-by: Ryan Duffy<EMAIL_ADDRESS>

Closing in favor of https://github.com/enyojs/moonstone/pull/2668.


softdeleteable + sluggable + entity copy = i want slug don't change in the cloned entity.

Hello. I have a (easy) use case:
First i edit a entity, in the background it clone it and then persist it (the cloned entity is then soft deleted). So if for the oldEntity i have 'xxx' slug then for the new a have now 'xxx-1'. My goal is to have 'xxx' slug for the new entity.
I tried to overide the SoftDeleteableListener to reset the slug on the oldEntity to leave the reference free for the new, but without success.
A idea ?

Please ask this to maintainers of the extensions. This bundle does not implement this logic.


Add version: Wondershare.Anireel version 1.2.1

- [X] Have you signed the Contributor License Agreement?

[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.0 schema?

Resolves #35018
Microsoft Reviewers: Open in CodeFlow

'  >:O

' >:O

Accidentally referenced wrong issue 🤕

I was referring to us creating the same PR's seconds apart 😁
And yeah noticed 😁


Deprecate?

Any thoughts on adding a deprecation message or generally a louder warning in the README?

A louder warning in the README sounds good to me. Perhaps just bump the current one to the top, and change the description to something like partitioned storage system based on blosc [UNMAINTAINED]?

Hello,
Forgot that awhile back, I made #60 .
It looks like this project is being deprecated. Too bad. I thought you were doing amazing work. (I'm not volunteering to take this over... I'm nowhere near competent for that.)
Can I ask if that's just because of a lack of interest or you are going to focus development on things like bcolz (or another project with overlap) instead? I'm trying to find the best on-disk data column-chunked compressed datastore for my purpose. They all have pluses and minuses.
Thanks for at least demo-ing this. I had fun toying with it.

It's still around.  I just don't personally intend to actively maintain it.  This isn't due to any particular flaw with the project, I just don't have enough time and there is no clear replacement who does have enough time.


len of typetracer array raises TypeError (cannot be interpreted as integer)

Version of Awkward Array
1.8.0rc4
Description and code to reproduce
This looks to be related to #1216 -- the typetracer length issue causing the repr to break is now raising if I try to compute the meta of an object that has had len map partitioned across it:
x = dak.from_json(...)
x.map_partitions(len)

will fail because map_partitions will try to call len(x.meta) to compute a new meta.
In [95]: x
Out[95]: dask.awkward<getitem, npartitions=2>

In [96]: x.meta
Out[96]: <Array-typetracer type='?? * var * int64'>

In [97]: x.compute()
Out[97]: <Array [[1, 2, 3], [1, 2], ..., [3, ..., 4], [1, 2, 3]] type='40 * var * int64'>

In [98]: len(x.meta)
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Input In [98], in <module>
----> 1 len(x.meta)

File ~/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/awkward/_v2/highlevel.py:537, in Array.__len__(self)
    527 def __len__(self):
    528     """
    529     The length of this Array, only counting the outermost structure.
    530
   (...)
    535     is `3`, not `5`.
    536     """
--> 537     return len(self._layout)

TypeError: 'UnknownLengthType' object cannot be interpreted as an integer

I traced the __len__(self) call for x.meta to be rely on the length attr of its layout (which is an awkward._v2._typetracer.UnknownLengthType):
In [111]: x.meta._layout.length
Out[111]: UnknownLength

What JSON data did x come from and what Awkward operations get applied to do the x.map_partitions(len)? I'm trying to reproduce this with Awkward-only, so that I can narrow down to find out what's putting an UnknownLength on the typetracer.

x is created by loading this line delimited JSON data twice.

I still don't know how to reproduce your issue, but I did find some cases that resulted in UnknownLength, just due to the fact that typetracer arrays were initialized with UnknownLength and that propagated up.
PR #1312 changed the policy to use length information wherever possible, though it will always be the case that some typetracers won't know their lengths. (E.g. nplike.arange(typetracer_has_no_data[-1]).) That exposed a lot of places where we were checking lengths—previously, typetracers skipped over the test because UnknownLength == integer is always False, but now those checks all need to be guarded by if nplike.known_shape (which is False for typetracers; they don't know their shape).
It might unblock you, but you need to be prepared for partitions that don't know their lengths.

It might unblock you, but you need to be prepared for partitions that don't know their lengths.

Oh yes absolutely! Sorry for creating a little confusion here (I now see my wording was pretty bad), I'm not looking to try to keep or know length information, but to have the typetracer usage give back something like UnknownScalar when len is called. Here's a better description I hope:
My reason for calling x.map_partitions(len) was experimenting with implementing dak.num(x, axis=0),
def num(array, axis=..., ...):
    # in the case where we don't know the divisions we will need to create a task graph
    if axis == 0 and not array.known_divisions:
        all_lens = array.map_partitions(len)
        return dak.sum(all_lens)
    # if we know the divisions this is trivial
    elif axis == 0
        # return a lazy scalar wrapping the value of  array.divisions[-1]

Writing this code led me to create this issue because array.map_partitions(f) is calling f(array.meta); here f is len which caused the TypeError. This was just some experimentation which led to something I thought may be a bug.
Even more details: I went down this route after running into another typetracer issue with ak.num (was planning on opening another issue for that so to not spin this one out of control!)

to have the typetracer usage give back something like UnknownScalar when len is called

Unfortunately, that's not going to work because Python has forbidden it:
>>> class Something:
...     def __len__(self):
...         return ak._v2._typetracer.UnknownLength
...
>>> len(Something())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'UnknownLengthType' object cannot be interpreted as an integer

and
>>> class Something:
...     def __len__(self):
...         return ak._v2._typetracer.UnknownScalar(int)
...
>>> len(Something())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'UnknownScalar' object cannot be interpreted as an integer

Actually, the typetracer does return UnknownLength when its len is called (if it is unknown, and now that will happen less often, but it still can happen), and that's why you get the TypeError.
Throughout the Awkward codebase, we've replaced len(something) with something.length, where length is a property that might return UnknownLength, as a way of avoiding this problem.

Unfortunately, that's not going to work because Python has forbidden it:

🤦 ah yes huge brain-lapse for me. Had I remembered this I never would have opened this issue


make storage-integration-test fails due to issues in CompareTrace() but error is forgotten

While writing the K/V/Badger storage backend, I enabled the storage-integration-test for that one also. That led me to silly errors, where byte-by-byte equal spans are not actually equal.
It does:
if !assert.EqualValues(t, expected, actual) {

Where expected & actual are of type *model.Trace. This leads to stretch/testify's doing a call to reflect.DeepEqual() and that fails. I copied over the code from reflect to check where this fails and what I get is:
	case reflect.Struct:
		for i, n := 0, v1.NumField(); i < n; i++ {
			if !deepValueEqual(v1.Field(i), v2.Field(i), visited, depth+1) {

This returns false, with the following output:
fmt.Printf("deepValueEqual v1.Field() != v2.Field() inside, %v != %v Struct\n", v1.Field(i), v2.Field(i))

Printing out deepValueEqual v1.Field() != v2.Field() inside, 0 != 0 Struct. For more reason, if we do:
fmt.Printf("first %v == second %v: %v\n", v1.Field(i), v2.Field(i), v1.Field(i) == v2.Field(i))

We get: first 0 == second 0: false. The reflect.DeepEqual unfortunately hits an unexported field at this point making things difficult, but it does:
	if v.kind() == Interface {
		if v.NumMethod() == 0 {
			return *(*interface{})(v.ptr)
		}

For both v1.Field(i) and v2.Field(i) and then compares the result. Thus, we end up with uint64(0) is not equal to uint64(0) and the Trace-comparison fails. This obviously works with the memory backend as it compares the same backing pointers, but these fail if we do json.Unmarshal / Marshal combination in between.
All I could say is that .. this type of assert is not going to work. Or can someone figure out the reason (I'm not this familiar with the golang runtime)? Doing fmt.Printf("Found mistake %v != %v\n", *expected, *actual) gives two byte-slices, but they are equal so I don't really see any mistake in the real code.
Why this hasn't been caught is simple also, the code in integration_test.go calls:
	if !assert.EqualValues(t, expected, actual) {
		for _, err := range pretty.Diff(expected, actual) {
			t.Log(err)
		}
		out, err := json.Marshal(actual)
		assert.NoError(t, err)
		t.Logf("Actual trace: %s", string(out))
	}

Thus is catches the assert-failure, but it does not actually pass that failure to the testing.T so the test is considered a success. Also, pretty.Diff should return the difference in the first parameter, I'm not sure why that is ignored and not logged.. not that testutils.NewLogger() does do any logging at all when using the make storage-integration-test thus all errors go unnoticed. Maybe this should have been another ticket.

Closed by #781


Missing documentation for Single Sign-On (SSO) credentials

Describe the issue
We are an AWS partner and require SSO to access AWS via Okta. I am writing a Rust application against AWS APIs, which needs to authenticate via SSO.
There is no documentation on how to use SSO with the Rust SDK.
Using the crate reference, I was able to hack something together that compiles, but panics at runtime.
The AWS CLI works fine with SSO, so I know the credentials work alright. I need to get the Rust SDK working though.
use aws_sdk_s3 as s3;

use s3::Client;

#[tokio::main]
async fn main() {
    let sso_region = aws_config::meta::region::RegionProviderChain::default_provider().or_else("us-east-1").region().await;
    let sso_creds = aws_config::sso::Builder::new();

    let prov_config = aws_config::
    let sso_prov = sso_creds
        .region(sso_region.unwrap())
        .role_name("AdministratorAccess")
        .start_url("https://zzzzzzzzzz.awsapps.com/start#")
        .account_id("zzzzzzzzz")
        .build();

    let target_region = aws_config::meta::region::RegionProviderChain::default_provider().or_else("us-west-2").region().await.unwrap();
    let config_aws = aws_config::ConfigLoader::default().credentials_provider(sso_prov).region(target_region).load().await;

    let s3_client = s3::Client::new(&config_aws);

    let bucket_list = s3_client.list_buckets().send().await;

    for bucket in bucket_list.unwrap().buckets.unwrap() {
        println!("{}", bucket.name.unwrap());
    }
}

The panic shows this error message, indicating that the Rust SDK is looking for a SSO cache file that doesn't even exist on the local filesystem:

ProviderError(ProviderError { source: IoError { err: Os { code: 2, kind: NotFound, message: "No such file or directory" }, path: "/Users/zzzzzzz/.aws/sso/cache/zzzzzzzzzz.json" } }), connection: Unknown } })', src/main.rs:23:31
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

How do I authenticate to AWS with SSO, using the Rust SDK?
Links
https://docs.aws.amazon.com/sdk-for-rust/latest/dg/credentials.html

Unfortunately, what you're trying to do isn't implemented in the current release (see https://github.com/awslabs/aws-sdk-rust/issues/703). I think it should land in a release fairly soon though, as it's just about ready to be merged (https://github.com/awslabs/smithy-rs/pull/2917).


pull request for e2e test at 11/09/2016 13:45:09

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

Details

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


Csse layout opt/td

Description

Changelog description

[x] Unlike previous PRs that changed one field at a time in Atomic<> schema (has a large footprint in QCEngine), this does the more extensive rearrangement of Opt<> and TD<> schemas all at once (albeit small footprint in QCEngine).
The changelog is overdetailed and unorganized at this point. A easier way (for some) to see the planned changes is in this  figure, where v1/v2 pairs of Atomic<>, Opt<>, TD<> schemas are shown with old/new fields aligned.

QCSchema_models_wide2_12Dec_cean.pdf
Status

[x] Code base linted
[x] Ready to go

Requesting review @davidbrownell, @krachwal, @rfievet, @ketanbj, @varun646, @jyoung3131


extend utils for rollback to explicit height

currently the rollback can be performed for a specific "snapshot-height" only using the tools.
in my project I have the test-scenario where I want to claim a set of names in before  and after each test a rollback to the snapshot after those names have been claimed is performed.
I need to perform an additional rollback after all tests have been executed to the height before those names have been claimed.
otherwise my test scenario isn't working anymore because the names have actually been claimed already.
of course I can now call the rollback endpoint of the devmode without using the devmode. and maybe it even makes sense to keep the names claimed and just do a short initial check before claiming the names, but in general it might be helpful to have the utils extended to allow an explicit rollback to a specific height even before the "snapshot" has been taken.
while writing this it makes more sense for me to keep the names and do simple check 😅

I think this issue has to be raised with the dev-mode plugin first, as it only exposes 2 functions for snapshots. 1. create snapshot at current height, 2. rollback to last created snapshot

I don't think this is correct. when looking at the functionality I don't see any real "snapshot" usage. what aeproject utils do now is remembering the block height to perform a rollback to.
the devmode plugin of the node allows to perform a rollback to a specific height OR a specific keyblock/microblock by providing its hash.

you are right, forgot about this as initially it was specified differently I think. Added a PR here: https://github.com/aeternity/aeproject/pull/477


Bug: Error listing tags for Config Rule in Secure-baselines

Expected Behavior
The Terraform: Scheduled Baseline workflow hasn't run completely successfully for about a week. In particular the secure-baselines jobs have not all been succeeding due to an error when trying to list tags for config rule sin a terraform plan.
Actual Behavior
Example of error:
Error: listing tags for Config Config Rule (arn:aws:config:eu-west-2:767123802783:config-rule/config-rule-mzxknb): operation error Config Service: ListTagsForResource, failed to get rate limit token, retry quota exceeded, 3 available, 5 requested
See Slack thread for more info.
Steps to Reproduce the Problem
No response
Version
No response
Modules
No response
Account
No response

See this TF AWS provider bug which seems to be related https://github.com/hashicorp/terraform-provider-aws/issues/34669

Also see this... https://github.com/hashicorp/terraform-provider-aws/issues/36024

I have raised https://github.com/ministryofjustice/modernisation-platform/pull/6494 to pin the TF provider to v5.38.0 as we didn't have this sort of failure occurring previously. This worked successfully under this run ... https://github.com/ministryofjustice/modernisation-platform/actions/runs/8341764086
See v5.38.0 in TF init....
https://github.com/ministryofjustice/modernisation-platform/actions/runs/8341764086/job/22828878548#step:6:144

I've run a job on main branch (so latest TF provider v5.41.0 e.g. https://github.com/ministryofjustice/modernisation-platform/actions/runs/8342287044/job/22830537939#step:6:145) and it's failed again
https://github.com/ministryofjustice/modernisation-platform/actions/runs/8342287044 96 out of 175 secure-baseline jobs failed.

PR #6494 has been merged to main which has pinned the provider for the secure-baseline code to v5.38.0
This has added some stability to the job; it runs through on a single attempt.
I'm considering whether or not that's enough for now, I think that something must have been introduced by the provider which has been acknowledged here https://github.com/hashicorp/terraform-provider-aws/issues/36024 and will hopefully be addressed in future.
I did try some of the suggested workarounds e.g. setting retry_mode to adaptive and also setting token_bucket_rate_limiter_capacity to a very large number but these suggestions didn't seem to help.

Agreed to keep this ticket open for now to test that this change has added stability and in case there is any progress on the underlying issue with the TF provider. I will take a look again next week.

Since the TF AWS Provider bug mentioned above has now been closed an integrated to v5.42.0 I am testing it out on a scheduled baseline run https://github.com/ministryofjustice/modernisation-platform/actions/runs/8419490112 on branch fix/remove-pinned-provider-in-secure-baselines

In this PR  I tried setting max_retries to 100 (the default is 25) which was being hit in the previous run.
It worked ... https://github.com/ministryofjustice/modernisation-platform/actions/runs/8422101284

https://github.com/ministryofjustice/modernisation-platform/pull/6598 is merged to main and ran successfully ...
https://github.com/ministryofjustice/modernisation-platform/actions/runs/8435420976
I think this should be enough to close the issue.


RNN with dropout / recurrent dropout and 1 timestep shows warning with CNTK

Hello,
I am creating the following network:
model = Sequential()
model.add(LSTM(512,return_sequences=True,recurrent_dropout=0.2,
              input_shape=(train_x_lstm.shape[1], train_x_lstm.shape[2])
         ))
model.add(Dropout(0.2))
model.add(LSTM(128))
model.add(Dense(len(selected_y_cols)))
model.add(Activation('sigmoid'))
model.compile(loss='binary_crossentropy', optimizer='rmsprop', metrics =["accuracy"])

history = model.fit(train_x_lstm,
                    train_y_lstm[selected_y_cols].values,
                    epochs=50,batch_size=64 ,
                    validation_data=(validate_x_lstm, validate_y_lstm[selected_y_cols].values),
                    verbose=1, shuffle=False)

When using CNTK as backend, I am getting error:
'RNN dropout is not supported with the CNTK backend when using dynamic RNNs (i.e. non-unrolled).  You can either set unroll=True, set dropout and recurrent_dropout to 0, 'or use a different backend.'
However, I cannot unroll, because train_x_lstm.shape[1] = 1

Precision, this is the error when attempting to unrolling:
ValueError: Cannot unroll a RNN if the time dimension is undefined or equal to 1.

Actually this is fixed in 2.1.3... I updated before posting but looks like I forgot to restart python session or some cleared some cache. Closing issue.


Previewer is not available after successful build of project on Linux

Bug
Hello I am trying to preview just a simple welcome to Avalonia project but it seems that preview button doesn't work.
To Reproduce
Steps to reproduce the behavior:

Build the project dotnet build
Go to MainWindow.axaml or App.axaml
Click on the Show Preview
Throws an error:  Previewer is not available. Build the project first.
Type dotnet run works fine.
Restart the VScode same issue
Re-open folder does't work

Expected behavior
Working Show Preview
Environment

OS: Linux (Ubuntu 22.04.1 LTS)
Avalonia-Version: [0.0.31]

@Apisteftos would you like to try a workaround? I had a similar issue in MacOS. you can edit directly the extension inside the .vscode folder
Previewer is not available

I updated the post at the end
Check it out!

Same here.

OS: Linux Ubuntu 24.04
Avalonia for VSCode version: 0.0.31

I have tried a workaround suggested by @tofferteves, and it doesn't work.
I have added a line, calling previewerAssetCommand, to out/commands/ShowPreviewToSideCommand.js:
    async execute(mainUri, allUris) {
        const activeFile = mainUri ?? vscode.window.activeTextEditor?.document.uri;
        await vscode.commands.executeCommand(Utilities_1.AppConstants.previewerAssetsCommand);   // <<-- test to force update the workspace

I had to add Utilities_1., because AppConstants was undefined.
After adding this line, on the first attempt, there was a rotating indicator on the status line of VSCode in the bottom.
However, no preview has appeared, and the Command palette now doesn't show Avalonia: Show preview


Failed to pull image public.ecr.aws/eks-distro/kubernetes/etcd:3.4.13-0 when installing with kubernetes-version v1.21.2-eks-1-21-3

Hi Fellows,
I ran into issue that failed to pull image public.ecr.aws/eks-distro/kubernetes/etcd:3.4.13-0 when kubeadm init with kubernetes-version v1.21.5-eks-1-21-9
Background
I'm trying to install the EKSD on bare metal based on the guide: https://distro.eks.amazonaws.com/users/install/kubeadm-onsite/
I installed with current latest version 1-21-9
https://distro.eks.amazonaws.com/releases/1-21/9/
What has failed
The installation is successful.
But it failed when coming to execute kubeadm init command:

kubeadm -v 7 init --image-repository public.ecr.aws/eks-distro/kubernetes  --kubernetes-version v1.21.5-eks-1-21-9

The command output is:

root@control-plane-1:~# kubeadm -v 7 init --image-repository public.ecr.aws/eks-distro/kubernetes  --kubernetes-version v1.21.5-eks-1-21-9
I0228 04:05:42.920153 1179099 initconfiguration.go:115] detected and using CRI socket: /var/run/dockershim.sock
I0228 04:05:42.920723 1179099 interface.go:431] Looking for default routes with IPv4 addresses
I0228 04:05:42.920747 1179099 interface.go:436] Default route transits interface "eno1np0"
I0228 04:05:42.920983 1179099 interface.go:208] Interface eno1np0 is up
I0228 04:05:42.921080 1179099 interface.go:256] Interface "eno1np0" has 2 addresses :[<IP_ADDRESS>/24 fe80::b226:28ff:fe4b:1880/64].
I0228 04:05:42.921131 1179099 interface.go:223] Checking addr  <IP_ADDRESS>/24.
I0228 04:05:42.921152 1179099 interface.go:230] IP found <IP_ADDRESS>
I0228 04:05:42.921174 1179099 interface.go:262] Found valid IPv4 address <IP_ADDRESS> for interface "eno1np0".
I0228 04:05:42.921194 1179099 interface.go:442] Found active IP <IP_ADDRESS>
[init] Using Kubernetes version: v1.21.5-eks-1-21-9
[preflight] Running pre-flight checks
I0228 04:05:42.981821 1179099 checks.go:582] validating Kubernetes and kubeadm version
I0228 04:05:42.981865 1179099 checks.go:167] validating if the firewall is enabled and active
I0228 04:05:42.990740 1179099 checks.go:202] validating availability of port 6443
I0228 04:05:42.991756 1179099 checks.go:202] validating availability of port 10259
I0228 04:05:42.991832 1179099 checks.go:202] validating availability of port 10257
I0228 04:05:42.991868 1179099 checks.go:287] validating the existence of file /etc/kubernetes/manifests/kube-apiserver.yaml
I0228 04:05:42.991889 1179099 checks.go:287] validating the existence of file /etc/kubernetes/manifests/kube-controller-manager.yaml
I0228 04:05:42.991903 1179099 checks.go:287] validating the existence of file /etc/kubernetes/manifests/kube-scheduler.yaml
I0228 04:05:42.991916 1179099 checks.go:287] validating the existence of file /etc/kubernetes/manifests/etcd.yaml
I0228 04:05:42.991939 1179099 checks.go:437] validating if the connectivity type is via proxy or direct
I0228 04:05:42.991982 1179099 checks.go:476] validating http connectivity to first IP address in the CIDR
I0228 04:05:42.992010 1179099 checks.go:476] validating http connectivity to first IP address in the CIDR
I0228 04:05:42.992022 1179099 checks.go:103] validating the container runtime
I0228 04:05:43.036464 1179099 checks.go:129] validating if the "docker" service is enabled and active
I0228 04:05:43.102682 1179099 checks.go:336] validating the contents of file /proc/sys/net/bridge/bridge-nf-call-iptables
I0228 04:05:43.102831 1179099 checks.go:336] validating the contents of file /proc/sys/net/ipv4/ip_forward
I0228 04:05:43.102887 1179099 checks.go:654] validating whether swap is enabled or not
I0228 04:05:43.102943 1179099 checks.go:377] validating the presence of executable conntrack
I0228 04:05:43.103000 1179099 checks.go:377] validating the presence of executable ip
I0228 04:05:43.103026 1179099 checks.go:377] validating the presence of executable iptables
I0228 04:05:43.103056 1179099 checks.go:377] validating the presence of executable mount
I0228 04:05:43.103068 1179099 checks.go:377] validating the presence of executable nsenter
I0228 04:05:43.103081 1179099 checks.go:377] validating the presence of executable ebtables
I0228 04:05:43.103100 1179099 checks.go:377] validating the presence of executable ethtool
I0228 04:05:43.103112 1179099 checks.go:377] validating the presence of executable socat
I0228 04:05:43.103124 1179099 checks.go:377] validating the presence of executable tc
I0228 04:05:43.103152 1179099 checks.go:377] validating the presence of executable touch
I0228 04:05:43.103167 1179099 checks.go:525] running all checks
I0228 04:05:43.163983 1179099 checks.go:408] checking whether the given node name is valid and reachable using net.LookupHost
I0228 04:05:43.164657 1179099 checks.go:623] validating kubelet version
I0228 04:05:43.226445 1179099 checks.go:129] validating if the "kubelet" service is enabled and active
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
I0228 04:05:43.235205 1179099 checks.go:202] validating availability of port 10250
I0228 04:05:43.235313 1179099 checks.go:202] validating availability of port 2379
I0228 04:05:43.235370 1179099 checks.go:202] validating availability of port 2380
I0228 04:05:43.235430 1179099 checks.go:250] validating the existence and emptiness of directory /var/lib/etcd
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
I0228 04:05:43.282451 1179099 checks.go:850] pulling public.ecr.aws/eks-distro/kubernetes/kube-apiserver:v1.21.5-eks-1-21-9
I0228 04:07:54.154419 1179099 checks.go:850] pulling public.ecr.aws/eks-distro/kubernetes/kube-controller-manager:v1.21.5-eks-1-21-9
I0228 04:10:29.871136 1179099 checks.go:850] pulling public.ecr.aws/eks-distro/kubernetes/kube-scheduler:v1.21.5-eks-1-21-9
I0228 04:11:51.677215 1179099 checks.go:844] image exists: public.ecr.aws/eks-distro/kubernetes/kube-proxy:v1.21.5-eks-1-21-9
I0228 04:11:51.712994 1179099 checks.go:844] image exists: public.ecr.aws/eks-distro/kubernetes/pause:3.4.1
I0228 04:11:51.752692 1179099 checks.go:850] pulling public.ecr.aws/eks-distro/kubernetes/etcd:3.4.13-0
I0228 04:12:19.701682 1179099 checks.go:850] pulling public.ecr.aws/eks-distro/kubernetes/coredns:v1.8.0
[preflight] Some fatal errors occurred:
[ERROR ImagePull]: failed to pull image public.ecr.aws/eks-distro/kubernetes/etcd:3.4.13-0: output: Error response from daemon: repository public.ecr.aws/eks-distro/kubernetes/etcd not found: name unknown: The repository with name 'kubernetes/etcd' does not exist in the registry with id 'eks-distro'
, error: exit status 1
[ERROR ImagePull]: failed to pull image public.ecr.aws/eks-distro/kubernetes/coredns:v1.8.0: output: Error response from daemon: repository public.ecr.aws/eks-distro/kubernetes/coredns not found: name unknown: The repository with name 'kubernetes/coredns' does not exist in the registry with id 'eks-distro'
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
error execution phase preflight
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:235
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdInit.func1
k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:152
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
_output/local/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
runtime/proc.go:225
runtime.goexit
runtime/asm_amd64.s:1371

This is weird, it is attempting pulling etcd:3.4.13-0 which doesn't match what is defined in the eks-d release manifest.
In the release maniest, version of etcd says: public.ecr.aws/eks-distro/etcd-io/etcd:v3.4.16-eks-1-21-9
Can someone help on this?
Additional info that might help
OS: ubuntu 20.04 LTS
docker version: 20.10.7 (installed by apt install docker.io)
kubeadm version is v1.21.5-eks-1-21
kubectl version is v1.21.5-eks-1-21
kubelet version is v1.21.5-eks-1-21

The kubeadm config file needs to have the etcd and coredns sections to override the tags otherwise kubeadm is going to use the default upstream tag which is why it's trying to download an image that doesn't exist in our repo.
Looking at that doc, it uses kubeadmin init with flags to override the kubernetes version and image repo. I'm not sure if there are flags for etcd and coredns. You may need to generate a kubeadm config instead and add the etcd/coredns parts then run init, passing the kubeadm config.
The kubeadm config for etcd/coredns will look something like this
https://github.com/aws/eks-anywhere/blob/d07c35902107f4d21c785ac7ee93439cfc8177d7/pkg/executables/testdata/kind_config.yaml#L5
As a side note, if you happen to be using vsphere/vcenter as your infrastructure provider you may want to check out eks anywhere instead of self managing with kubeadm.

The kubeadm config file needs to have the etcd and coredns sections to override the tags otherwise kubeadm is going to use the default upstream tag which is why it's trying to download an image that doesn't exist in our repo.
Looking at that doc, it uses kubeadmin init with flags to override the kubernetes version and image repo. I'm not sure if there are flags for etcd and coredns. You may need to generate a kubeadm config instead and add the etcd/coredns parts then run init, passing the kubeadm config.
The kubeadm config for etcd/coredns will look something like this
https://github.com/aws/eks-anywhere/blob/d07c35902107f4d21c785ac7ee93439cfc8177d7/pkg/executables/testdata/kind_config.yaml#L5
As a side note, if you happen to be using vsphere/vcenter as your infrastructure provider you may want to check out eks anywhere instead of self managing with kubeadm.

Thank you so much Jackson!
I will try pass a config file with coredns and etcd image repo configured then.

The issue is resolved when passing a config file to specify image tag for etcd and coredns


Improvements to PcodeSyntaxTree.locRange

This PR has two changes:

A fix for VarnodeBank.locRange(AddressSpace) using AddressSpace.getAddress(0) rather than AddressSpace.getMinAddress() as a minimum address. This causes the function to not return varnodes with a negative offset, which is particularly relevant on the stack.

A helper function PcodeSyntaxTree.locRange that takes in a minimum and maximum Address. A variant that takes in min/max Varnodes, or one that takes AddressSpace + min/max offsets might be worth considering as well. I am operating under the assumption that the VarnodeBank is not intended to be accessible from PcodeSyntaxTree, or else a simple getter would work.

Closed by f6dfa0964acb2ee3379a1c4f7f94a95ed7a9cba4


Export emacsPackages as emacs.pkgs

Describe the bug
The use of emacsPackages was deprecated in https://github.com/NixOS/nixpkgs/pull/107152:

The previous versioned names emacsPackages have been moved to
aliases.nix and are now considered deprecated in favour of emacs.pkgs.

Since https://github.com/NixOS/nixpkgs/pull/113713 emacs packages are again exported into packages.json but as emacsPackages.
Please find a solution so they are listed as emacs.pkgs to be consistend with documentation.
The file to change is https://github.com/nixos/nixpkgs/blob/master/pkgs/top-level/packages-config.nix.
cc @adisbladis

A big problem is that nix-env doesn't seem to want to recurse into the attrs of a drv which makes sense as there are a bunch of derivation-internal derivations inside which you wouldn't want to show up in the list.
I don't think I'm a fan of putting important things like large sets of derivations inside a derivation; it should be elemental (as nix-env assumes). Putting something inside a drv for convenient access is absolutely fine with me but I don't think it should be the canonical location for that thing.
Maybe we should rethink #107152 instead of finding a solution to this surprisingly hard problem.


update: avoid write below etc to trigger with falcoctl

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area rules

/area registry

/area build

/area documentation

What this PR does / why we need it:
While testing the Falco systemd unit for the incoming release, I've noticed this rule kept triggering with false positives due to falcoctl installing rules in /etc/falco. Let's just allow that, cause it's normal behavior.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign jasondellaluce for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[Feature-8386][Server] Custom timezone - Add timezone into user info

Purpose of the pull request
Custom timezone - Add timezone into user info

Brief change log

Add column time_zone varchar(32) default null in table t_ds_user
Add system default timezone like GMT+08:00 when create user
Add timeZone property when update user info

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #8457 (e241faf) into dev (234f399) will decrease coverage by 0.00%.
The diff coverage is 56.25%.

@@             Coverage Diff              @@
##                dev    #8457      +/-   ##
============================================
- Coverage     45.35%   45.35%   -0.01%
- Complexity     4028     4029       +1
============================================
  Files           686      686
  Lines         26702    26717      +15
  Branches       2867     2869       +2
============================================
+ Hits          12112    12117       +5
- Misses        13448    13454       +6
- Partials       1142     1146       +4

Impacted Files
Coverage Δ

...lphinscheduler/api/controller/UsersController.java
61.53% <0.00%> (ø)

...inscheduler/api/service/impl/UsersServiceImpl.java
74.79% <42.85%> (-0.47%)
:arrow_down:

.../apache/dolphinscheduler/api/utils/CheckUtils.java
65.85% <50.00%> (-1.72%)
:arrow_down:

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <100.00%> (ø)

...a/org/apache/dolphinscheduler/dao/entity/User.java
74.13% <100.00%> (+1.41%)
:arrow_up:

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-2.82%)
:arrow_down:

Continue to review full report at Codecov.

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

@caishunfeng plz review，thx~

@caishunfeng i‘ve updated the code, thx for your advice, plz take a review

@caishunfeng i‘ve updated the code, thx for your advice, plz take a review

Look good to me, I had merged the pr, thanks for your contribution.

this pr close #8386


Add a changelog in both packages to satisfy the pub.dev analyzer

the pub.dev analysis score removes 5 points when there is no changelog file in a package.
cf. #96

We could use a symlink (if pub publish supports that). And have a shared CHANGELOG.
Otherwise we'll need to maintain two changelogs, I'm afraid.

Once the Flutter package will use the native plugins, will the 2 packages be impact by the same changes ?

we already have symlinks, if pub publish doesn't support it, we'll reopen it


unable to downlaod from vporn

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.04.25. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.04.25

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: [u'--external-downloader', u'aria2c', u'--external-downloader-args', u'-c -x 16 -s 16 --min-split-size=1M']
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'https://www.vporn.com/big-boobs/priya-rai-wod/1144284/']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.04.25
[debug] Python version 2.7.14 (CPython) - Darwin-17.5.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 4.0, ffprobe 4.0, phantomjs 2.1.1
[debug] Proxy map: {}
[Vporn] priya-rai-wod: Downloading webpage
WARNING: unable to extract description; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract uploader; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract duration; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract view count; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 789, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 440, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/vporn.py", line 108, in _real_extract
    self._sort_formats(formats)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1083, in _sort_formats
    raise ExtractorError('No video formats found')
ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description of your issue, suggested solution and other information
unable to download from vporn

using the generic extractor via --force-generic-extractor does work


Styled-components

Hi everyone !
Did anyone successfully make it work with Styled-components using server-side rendering ? (e.g: https://www.styled-components.com/docs/advanced#server-side-rendering).

I've managed to do it in a hacky way, if someone is interested, just comment here :)

Me interested... @loiclouvet could you share your solution?

@georgii-ivanov Sorry, was on holidays.
I don't own the source anymore :(, maybe @LoicGoyet can help you...
As far as I remember, It was only about configuration !

@georgii-ivanov Hello, sorry for the late late answer :(
On the first hand what we did is a HOC like this :
const ServerRendering = Component => {
  const ServerRenderingComponent = props => {
    const styleTags = () => {
      const sheet = new ServerStyleSheet();
      renderToString(sheet.collectStyles(<WrappedComponent {...this.props} />));
      return sheet.getStyleTags();
    }

    return (
      <React.Fragment>
        <style>{styleTags()}</style>
        <Component {...props} />
      </React.Fragment>
    );
  }

  ServerRenderingComponent.displayName = `ServerRenderingComponent(${Component.displayName || Component.name})`;

  return ServerRenderingComponent;
};

// Then export the component you want to render in SSR like this
export default ServerRendering(MyComponent)

Today we got a more custom way to handle it, really specific to our technical stack (which is weird). HOC should still work, but a more elegant way with react hooks.


Update toolchain auto provisioning related content in manual

Fixes #23178

@bot-gradle test and merge

I've triggered a build for you.


Make expiry key symbolized

I'm currently getting a null expiry header,
https://github.com/lynndylanhurley/devise_token_auth/blob/master/app/models/devise_token_auth/concerns/user.rb#L163
Changing it to a symbol fixed it, so i assumed that the same issue would occur for all places where we used self.tokens[client_id]['<key>'].
Edit: Changing it everywhere broke the suite, so i changed it to just the expiry header.

Thanks @jartek - I'll review this ASAP!

@jartek - I'm not sure why, but sometimes the tokens hash uses string keys, and other times it uses symbol keys.
I think I've fixed most of the issues in version 0.1.31.beta8. Please pull it down and let me know if you run into any trouble.


chore(V2): Remove deprecated constructs from main branch

Issue #, if available:
Closes #798
Description of changes:
Removes code for constructs deprecated in V2. The code will always be available in the frozen V1 branch.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 9ed09c3ab55dbec285fc272eaf8b8c5c961ee32b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Any way to run SQL queries using SDK?

Hello, is there a way to run sql queries using sdk or in pocketbase in general ?
I am trying to avoid manually creating database schema by dashboard using clicks etc

Executing raw SQL statements with the JS SDK is not supported.
If you want to manage your schema programmatically, you can check https://pocketbase.io/docs/migrations/.


Any chance of making a GIMP plugin?

for Affinity Photo as well

https://github.com/thndrbrrr/gimp-stable-boy


[Sprint3#92]API Auth Logout and Refreshing JWT Token

Adding API Auth in Recruiter signup, Password Hashing in Recruiter Signup/Login. API Auth in Candidate Signup/Login.
Correcting Rec Login API calls from the Front end. Util Methods for JWT Auth, JWT Refresh Token Utils, JWT Refresh check from cookies.

OK!


Add note to timeout error log

Sometimes a FlowInterruptedException occurs that isn't from timeout
Usually from the failure of a downstream job
This PR adds notes to the error message in these unique cases
That the user should check the downstream job results
And not assume a timeout was reached

Signed-off-by: Morgan Davies<EMAIL_ADDRESS>

See https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-hotspot/809/console as an example of this happening

@M-Davies i've noticed in recent weeks this happening a lot:
[Checks API] No suitable checks publisher found.
java.io.IOException: Tried to load head FlowNodes for execution Owner[build-scripts/jobs/jdk11u/jdk11u-windows-x64-hotspot/809:build-scripts/jobs/jdk11u/jdk11u-windows-x64-hotspot #809] but FlowNode was not found in storage for head id:FlowNodeId 1:201
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:689)
	at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:726)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:691)

has something changed to produce these FlowNode errors?

@andrew-m-leonard There was some similar discussion on slack about something similar to this (this thread in particular) that never came to a conclusion. Nothing has changed that could cause this that I know of 😕 . Maybe raise an issue and I'll have a poke around when I get a chance?

Thanks @aahlenst 👍


OME-TIFF samples page restructing

Following the last comment in https://github.com/openmicroscopy/ome-documentation/pull/1459#issuecomment-217627466, this PR adds more samples links in the OME-TIFF file structure discussion page.
Additionally, it reviews the content of the OME-TIFF samples page as follows:

moves the OME-TIFF/OME-XML compression discussion to a separate page
groups/unifies the description of all OME-TIFF samples under ome-tiff/data
adds missing description for the binary only fileset
add references that can be linked to from other places in the documentation

To review this PR, check https://www.openmicroscopy.org/site/support/ome-model-staging/ and especially https://www.openmicroscopy.org/site/support/ome-model-staging/ome-tiff/data.html. The goal is to increase the clarity/lisibility/maintenance of the samples section while allowing to link from it from other places.

Overall looks fine.  I think the compression section could use a little rework.

Pushed a few extra changes for the data samples page. As suggested by @rleigh-dundee, the compression page might need more attention including both regeneration of the up-to-date metrics and rewriting. I propose to get this effort recorded somewhere for future improvements and have the documentation re-published prior to the Users Meeting with the last set of improvements to the OME-TIFF section (file structure, specification, samples).

All looks fine to me, I second the proposal to ticket work on the compression page and merge this. @sbesson did you want to add your new diagrams to the docs prior to POTN or shall i just merge and release the updated docs today?

Agreed on the proposal. For the diagrams, I would be inclined to get feedback at the Users Meeting first and open a PR afterwards including them.

👍 I'll merge and update the live docs, then stick a card somewhere.


Landing page v2

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡

Add online demo for the public app shown in the video.
Link docs from landing page (later to be moved to MUI -> Docs)
Link GitHub issues from docs
Showcase features

Stretch:

Update video (record with new UI)

Examples 🌈
No response
Motivation 🔦
No response

Update video with dark theme
Add live demo to use cases
Bring up self-host
Improve features


Fix Droppable class not extensible.

This fixes a fatal error occurring for me with Ember 2.3.0:
Uncaught TypeError: Cannot define property:_currentDrag, object is not extensible.

If you think we need to initialize this property to null, then we could instead use:
Droppable.reopenClass({ _currentDrag: null });

Thanks for the PR, I'll pull it in soon.

A few lines below there is also breaking for the same reasons:
    Droppable._currentDrag = event.target;

@jgelens Good catch. Just force-pushed a fix for that too using reopenClass.

Had to modify the code a bit, but looks like all the tests are passing now.  Sorry about the delay on this, had a busy couple of weeks. Loot for a release with this fix later tonight.

@dgavey Thanks!


Nodejs version of SampleAADv1Bot

I am looking for node.js version of SampleAADv1Bot. Is it available ?

Hi @rjgmail88
AuthBot is a deprecated library.  Please refer to BotAuth: https://github.com/MicrosoftDX/botauth/tree/master/Node where you will find an aadv1 example for node: https://github.com/MicrosoftDX/botauth/tree/master/Node/examples/aadv1

Thanks Eric. But I only see following 2 files in aadv1 link you mentioned.
README.md
package.json

Oh, wow ... My apologies.  It is apparently

(coming soon)


Add Travis

This should trigger a build.

Nice, in this case failed travis build is progress!

and that's how it's done

actually shucks, I just noticed that the PSI test prematurely exits with 0 and phantomas didn't run during the passing build. No problem with the Travis code, just poor async handling on my part.


Implementation on velodyne lidar

I am using Velodyne (VLP-32C) Lidar. Could you please let me know, if this Lidar gives range data (as 32 rows and many columns, used in your method) or I need to create this kind of format using the point cloud. Creating a cylindrical projection from a point cloud increases the run time to great extent..

If you have your own driver for a lidar, you can definitely implement it in a way where it gives you the image (or rather multiple small "scan" images). If you don't own a driver, it depends on what it provides you. Projecting the data takes really not that long even if you only have a point cloud. Definitely enough for prototyping, and if you actually want to use this in production, you should probably have your own driver.

We have Velodyne LiDAR sensor but can you please clarify, what exactly you mean by "driver"?

The driver is the software that interprets the data coming directly from the sensor and creates a useful representation that is used further down the line, i.e., to point clouds.

Thanks for ur reply. I am getting a run time of approx. 0.02 second for each frame on 32GB RAM system. Is this run time justified or could there be a problem in implementation , in ur opinion?

The amount of RAM is relatively irrelevant here. The crucial factor is what is your processor. Otherwise, you are getting around 50fps, which seems rather slow. What are you measuring?
I will close this issue, but feel free to continue the discussion here.


Weaker performance on Android than the editor

Description
I tested it on a Samsung A33 phone and the performance was not satisfactory, but it was excellent on the editor, what is the difference?

I guess the device, OS, CPU, and even the architecture are different as well.

I'm having the same issue, for example in the unity editor the app shows continuously the keypoints, however, on the cell phone they appear and disappear even when the person remains still, I thought it was something in the phone so I tried it on the following devices:
MotorolaG200
Redmi 11
Redmi Note 13
Samsung A34
Redmi Note 11
Samsung Note 10
Redmi 12
Xiaomi mi Lite 11
Oppo A 38
In none of the previous devices the problem was solved.

@MARLOPD If necessary, create a new issue and write down what is your problem and how to reproduce it.
@ghasedak3411

the performance was not satisfactory

If you need help, please write objective issues rather than expressing personal feelings about performance.

I have the same issues in all of the android devices. The mediapipe character flickers in the holistic scene when running on the device. This doesn't happen in the player or the IOS!!


Integration Testing: Assert things on events investigation

Epic: #4735
Given that we need structured events for open tracing anyway, we want to reuse that infrastructure for making our assertions in the integration tests.
The plan here is to attempt to use StackDriver as we already have it set up to ingest logs pending the results of the following investigations:

Throughput

Can we stream in stack driver logs with minimal filtering and process them fast enough to keep up with realtime with 200 nodes reporting?

Latency

How long does it take between a log line emitting in a node to it appearing in the stream on a different node?
Assuming (1) and (2) are confirmed -- this is our mechanism for implementing assertions in tests.

Latency of logs is acceptable, and throughput has been deemed as not significant in the short term. At this point, sounds like we may end up using the automated validation service for consuming structured events as statistics from the network. If we do that, then throughput is not significant issue since we can scale the automated validation service rather easily.


draft: Testing CI

DO NOT MERGE - testing CI

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

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 90.272%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
1429

Relevant Lines:
1583

💛  - Coveralls

Closing - this PR helped diagnose the issue with remote fork PRs