text:
mapStateToProps should not be called with functional component rendering a connected class component

What version of React, ReactDOM/React Native, Redux, and React Redux are you using?

React: 18.2.0
ReactDOM: 18.2.0
Redux: 4.2.1
React Redux: 8.0.5

What is the current behavior?
Description:

Depending on a parent component being a functionnal or class component, children connected component do not see their mapStateToProps function called in the same way

Reproduction:

https://codesandbox.io/s/beautiful-gianmarco-wo67u0
Click on toggle and check the console logging
we can see a call to mapStateToProps in the class component child, when the parent component is a functional component ([APP1]) but not when the parent is a class component ([APP2])

Here is the logging, by app, when toggling off connected children (conditional rendering):
With a functional component as parent:
[APP1] CLASS CHILD MAP STATE TO PROPS
[APP1] NORMAL CHILD SELECTOR
x2 [APP1] NORMAL PARENT SELECTOR
[APP1] RENDER PARENT {showChild: false}
[APP1] NORMAL PARENT SELECTOR
[APP1] RENDER PARENT {showChild: false}

With a class component as parent:
[APP2] CLASS PARENT MAP STATE TO PROPS
x2 [APP2] RENDER PARENT {showChild: false}
[APP2] NORMAL CHILD SELECTOR

Note:

FYI this led to an issue in our code when refactoring a component, with uncaught error in the mapStateToProps function of a child of that component, because suddenly it was being called with unexpected state and trying to get state on undefined keys.

Maybe all of this is a normal consequence of the inherent difference in React rendering functional or class component, but I still wanted to document this in an issue for the record, and see if you have any comment.
Thanks!
What is the expected behavior?

mapStateToProps should be called consistently (or should it not?)

Which browser and OS are affected by this issue?
Chrome OSX
Did this work in previous versions of React Redux?

[ ] Yes

I'm not sure what you're trying to describe here, tbh.
At my first guess (just reading the description), I assume that the difference in rendering is not a bug, but simply a question of which components are re-rendering and which are not, per https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-mostly-complete-guide-to-react-rendering-behavior/#standard-render-behavior .

I have tried to explain as accurately as possible and provided a codesandbox, but if it is unclear or need more details, I'll be happy to provide them.
What I'm pointing is that the two examples in that demo are rendering exactly the same thing (supposedly) but mapState is called on one side and not on the other, which was unexpected and led to a bug, so I'm reporting on that.

@pandaiolo yeah, afraid I don't have time to look at this right now (busy with day job stuff).
But, my immediate guess is that:

When the parent is a class component, it avoids re-rendering the child, and the child's mapState is thus not called
When the parent is a function component, it does re-render the child, and thus the child's mapState is called

which sounds like a combination of how React itself works in general for rendering rather than a particular bug in React-Redux.
I'll try to look into this at some point, but not sure when.

Sure, thank you!

authors: markerikson pandaiolo

repo: reduxjs/react-redux


text:
Update ThreePrinciples.md

in the state explanation read-only is totally missed, need focused few words on it.

Strongly applies when programmer codes, suppose to write getter methods not setters, in simple words for beginners.

Hi.  Appreciate the PR, but I don't see a need to change the wording at this time.  Thanks anyway!

source: gharchive/pull-request

repo: reduxjs/redux

license: MIT

license_type: permissive

license_source: github-api


text:
Move the examples to a separate repo

I'd like to move the examples out of the repo. They add a lot of time to the build process and generally don't change significantly. They also don't require the source copy of Redux, so it's not like they are a canary for changes we make on master.
Moving them to their own home means it's more reasonable to accept new additions, which is something we've been hesitant to do for a long while (years!).
I've set them up in a new repo: reduxjs/examples
Is this a terrible idea? Anything we should do besides updating the docs and creating a new README in the examples path (which is temporarily gone at the moment).

Also of note:

Typical build time today: 3:30-4:10
This PR build time: 1:10

That's a 3-3.5x faster build time.

Thoughts and concerns:

The approach shown here and in the other repo appears to blow away all the accumulated Git history.  Could we at least do some git filter-branch work to extract the examples folder history as the starting point of the new repo, so that we can maintain that history?
We have a bunch of links in the docs, and there's probably also external links:

Yeah, we'd need to do a bunch of fixing up for our docs.
External links would result in a 404.  Can we at least leave placeholder README files that point to the new location?

What additional examples would you want to have in the future repo?

Out of curiosity, what about the examples is slowing down the build process?

There are so many of them and they all require separate npm ci commands.

But why are we even building / testing them at all as part of the main lib?  Where are they getting kicked off?

https://github.com/reduxjs/redux/blob/master/.travis.yml#L5-L6

Oh.  Well, at a minimum, we should remove those lines from Travis.  No reason to be checking those on every commit.

Redid the examples repo with history intact: https://github.com/reduxjs/examples

I'm still really not seeing a point to this.  If we're concerned about Travis build times for some reason, let's just configure Travis to not worry about the examples on every build or something.

I tried to figure out how to conditionally build certain examples based on the changed files using Travis' environment variables, but unfortunately it seems difficult to do this consistently. For example TRAVIS_COMMIT_HASH doesn't only show the commits from the PR which would cause false positives where examples are build when they shouldn't be, and if multiple commits are pushed outside of a pull request TRAVIS_COMMIT would only show the latest commit which could cause examples to break without being rerun in CI.
I think the safest way to make our builds faster is to remove the examples (like with this pull quest, but possibly replacing the existing files with links to the new repository) and move the example scripts to the other repository. Alternatively, we might be able to speed up our multiple package installations using monorepos with yarn workspaces or lerna, but I don't have experience with them.

We never did move these out, and tbh I'd like to keep them in here. Closing.

authors: markerikson nickmccurdy timdorr


text:
Improve the example in GettingStarted.

name: "New/Updated Documentation Content"
about: Adding a new docs page, or updating content in an existing docs page
Hello,
Thanks so much for this great project. I've just started leaning redux, and found a little bit of difficulty in the GettingStarted example.
I hope you will like it and please let me know if there are rooms for improvement in my PR.
PR Type
update an existing page.
Checklist

[ ] Is there an existing issue for this PR?

link issue here

[x] Have the files been linted and formatted?

What docs page is being added or updated?

Section:Introduction
Page:Getting Started with Redux

For Updating Existing Content
What updates should be made to the page?
The import part is a bit difficult for newbies to setup correctly.
Actually I failed to make this example work.
$ node example.js
(node:20108) ExperimentalWarning: The ESM module loader is experimental.
file:///private/tmp/my-redux/example.js:1
import { createStore } from 'redux'
         ^^^^^^^^^^^
SyntaxError: The requested module 'redux' does not provide an export named 'createStore'
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:92:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:107:20)
    at async Loader.import (internal/modules/esm/loader.js:164:24)

I know it's not a problem in Redux, but ideally example code should work without effort.
Do these updates change any of the assumptions or target audience? If so, how do they change?
Target audience:
a newbie to overall ecosystem of JavaScript (JS/npm/Redux)
Assumptions:
They can create an html and a js file by hand, and open the html by their browser.
Expected Results:
They'll feel more confident that they can move forward by the first success of the working example code.

Thanks, but we're not looking to create a working example here per se, just some example code of how a Redux store might be written.  If you click over to the Examples page in the next section, we do have a working example of this exact code.

authors: DQNEO timdorr


text:
ReactJS - setState causes viewer to re-render every time

When using Resium with ReactJS and adding an ImageLayer, it is causing the viewer to refresh every time any setState is called. How can I use setState to update certain parts of the page without re-rendering the map?
Example below and screenshot of the issue
`
class LiveMap extends React.PureComponent {
viewerRef = React.createRef();
state = {
name: "test"
};
handleSelectedEntityChanged = (event) => {
    console.log("selected: " + event);
    this.setState({
        ...this.state,
        name: this.state.name === "test" ? "testt" : "test"
    });
};

render() {
    const defaultImageryProvider = new UrlTemplateImageryProvider({
        url : "https://cartodb-basemaps-{s}.global.ssl.fastly.net/dark_all/{z}/{x}/{y}.png"
    });
  return (
    <Viewer
      full
      ref={this.viewerRef}
      onSelectedEntityChange={this.handleSelectedEntityChanged}>

    <ImageryLayer imageryProvider={defaultImageryProvider} />

    <Entity
        name={this.state.name}
        position={Cartesian3.fromDegrees(61, 130, 100)}
        point={{ pixelSize: 10 }} />
    </Viewer>
  );
}

};
`

You are constructing a new imagryProvider on every render. It looks like it does not depend on any props or state though, so you should be able to just build it once inside the constructor.

I am getting similar functionality with useEffect. I have an API call in my useEffect function which gets called every 5 seconds. With the data from the API I can set some state variables using "setMyVar()". This then updates the state variables and redraws a point in the Viewer. The weird thing is, this updates resets the clock.
I think this is because useEffect re-renders the view with every call. I am not sure if this is how this should work or if I am using state incorrectly with Resium.

Try to move new UrlTemplateImageryProvider(...) outside the render function.
Before:
  render() {
    const defaultImageryProvider = new UrlTemplateImageryProvider({
        url : "https://cartodb-basemaps-{s}.global.ssl.fastly.net/dark_all/{z}/{x}/{y}.png"
    });

After:
  defaultImageryProvider = new UrlTemplateImageryProvider({
    url : "https://cartodb-basemaps-{s}.global.ssl.fastly.net/dark_all/{z}/{x}/{y}.png"
  });

  render() {
    // ...
    <ImageryLayer imageryProvider={this.defaultImageryProvider} />

I think I have the same issue. When I update variable in parent that holds Entities as children, they all get redrawn

Same as you guys, when state of my component with Viewer is changed (with useState() or useEffect() hooks) - ImageLayer is reloaded. Is there some way how to fix this?

imageProvider prop of ImageryLayer component is read-only and is not changeable because ImageProvider of ImageryLayer of Cesium API is also read-only.
If the imageProvider is static, you can use outside const variable or useMemo hook as described in this page.
If you want to change the imageProvider dynamically, you cannot avoid regenerating the ImageryLayer. If you want to completely suppress warnings, key props can be used:
const imageProvider = useMemo(() => new UrlTemplateImageryProvider({ url }), [url]);

return <ImageryLayer key={url} imageryProvider={imageProvider} />;

We are also considering suppressing the warnings. Either way, please understand that the imageProvider is read-only.

source: gharchive/issue

repo: reearth/resium


text:
Suppressed the result of expressions at the end of test blocks

Fix #34, #47
Converted the optional expr at the end of test blocks to a statement so that test blocks can end with an unsuppressed expression (including loop statements).
A bit of a mess (lots of cloning) because of ownership issues. Suggestions are welcome.

@reem Thoughts?

Hey there, I volunteered to help out @reem with this crate. The code is probably not the prettiest ever as you said but it would be great to have this fixed so I'd be willing to merge this.

Could you also rebase this on the latest master so that we are completely sure that it doesn't break any of the existing tests?

Thanks for the changes. 👍

authors: cramertj ujh

repo: reem/stainless

license: mit

license_source: bigquery


text:
Fix for rustc 1.14.0-nightly (f09420685 2016-10-20).

Fixes #71.
See https://github.com/rust-lang/rust/commit/029dceedb9719ae5dbdbf2c033c920017e3d786e.

👍 Thank you.

authors: ujh utkarshkukreti


text:
Rails5

adds rails5 compatibility via upstream merge of collectiveideas master.

lgtm ??

authors: meesterdude nhance

repo: reenhanced/audited


text:
remote forms doesn't work after upload:complete event

When you try to submit a form with remote: true jquery-ujs checks if it's had any non blank file inputs https://github.com/rails/jquery-ujs/blob/master/src/rails.js#L422, so the remote option is ignore and the form is submitted with a normal POST.
My solution was to modify the if in this line https://github.com/elabs/refile/blob/master/app/assets/javascripts/refile.js#L37 to:
if((xhr.status >= 200 && xhr.status < 300) || xhr.status === 304) {
  var id = input.getAttribute("data-id") || JSON.parse(xhr.responseText).id;
  input.previousSibling.value = id;
  input.removeAttribute("name");
  input.value = ''; // <-- included this
  dispatchEvent("upload:success", xhr.responseText);
}

This make the input file empty, so for jquery-ujs all the file fields are blank and the form is submitted remotely.
I will be happy to make a pull request if this approach is considered correctly.

I'm the same problem =\

This gem https://github.com/JangoSteve/remotipart resolved the problem with upload file with remote: true

Is there any way to get this to work properly? I tried @cerdiogenes code and it didn't work.

@danieldocki I looked at the remotipart gem. I wouldn't use it. It is looking very long in the tooth and somewhat neglected. I'm paranoid about adding too much magic, especially when it involves adding new middleware to my stack. Seems like overkill anyway to work around this issue as it triggers submitting forms through a hidden iframe, which is not longer needed thanks to refile! Keep it simple.
We just need some way to tell Rails UJS to not count refile handled file inputs when determining whether to abort the AJAX form submission.
I poked around through the remotipart gem to see how it works. I found it relies on handling the ajax:aborted:file event fired by Rails UJS when it aborts due to non-empty file inputs.
I was able to come up with the event handler below which tells Rails UJS to proceed with submitting the form via Ajax if all the non-empty file inputs are associated with refile.
I used the data-reference attribute to detect the presence of refile handling. @jnicklas:  is that a safe bet?
$(document).on('ajax:aborted:file', 'form', function(){
  var form = $(this);
  // if all non-blank file inputs are handled by refile,
  // then resume
  var nonBlankFileInputs = $.rails.nonBlankInputs(form, $.rails.fileInputSelector);
  if (nonBlankFileInputs.filter(':not([data-reference])').length === 0) {
    $.rails.handleRemote(form);
    return false;
  } else {
    return true;
  }
});

@masonhale I think that's a fine workaround. Someone (not me ;)) should really patch rails_ujs to do the right thing though.

@jnicklas I was thinking about how to patch rails_ujs, and it occurs to me that it needs some way to know which file input fields should be excluded from its check of non-blank file inputs. I would propose that it looks for some specific attribute on the input as a flag to indicate it should be ignored. Something like data-rails-ajax-ignored=true. This way an application author could manually add the attribute to exclude it from the file input check (and potentially the separate required field input check), and rails-friendly file upload libraries like refile could potentially add the ignore attribute automatically to help make things work automatically. Any thoughts?

No, the reason for exclusion should be that the field is disabled. Disabled fields aren't submitted by browsers, rails_ujs shouldn't care that there's a disabled field with a file attached in the form.

@jnicklas thanks for the clarification. I didn't realize Refile disabled fields and that would be a good method to filter file input fields. Question: when does this disabling happen? Is it possible the rails_ujs script could fire before Refile sets the field to disabled?
@jnicklas Looking more closely at how the refile.js operates, I notice it removes the name of the input field after the file is processed here. I don't see where it sets the input file to disabled. Am I missing something? It makes me wonder if ignoring file inputs with no name attribute would work as well or better than ignoring disabled fields? (To be clear, I'm asking for clarification because I intend to submit a PR to fix rails_ujs. Thanks for the help).
PS: Thanks also for all the work you've put into Refile. I think it is really great work and I am very thankful you've put in the effort and hard-won experience to make it. Thank you!

@masonhale uuhh I was remembering it wrong. We do indeed remove the name to not submit the field. Browsers don't submit it, so rails_ujs should not accout for it, but it does.

Ok, based on what I've learned by working on a Rails UJS patch, I've come up with a better/simpler monkey-patch to get Refile and Rails UJS working together. This avoids having to catch the aborted file event. Much cleaner. It simply tweaks the fileInputSelect UJS uses to make sure the input has a name. (Interestingly, Rails UJS already has a similar check in place for required fields).
// run this anytime after rails / jquery-ujs is loaded
$.rails.fileInputSelector = 'input[name][type=file]';

@jnicklas actually does Rails UJS not include disabled inputs since v. 1.1.0 (https://github.com/rails/jquery-ujs/pull/430). Could we patch refile to disable the input instead of just removing the name attribute?

@jokklan no this does not work. Disabling the input not only has a visual effect we do not want, but it also prevents the user from selecting another file for upload.

It's really a simple fix in Rails UJS, which they should make anyway, someone should really submit a patch. It's not going to be me though, since I don't actually ever use rails_ujs ;)

I just submitted a pull request to jquery-ujs for this issue: https://github.com/rails/jquery-ujs/pull/464
I meant to do it before the holidays, but got busy/distracted and didn't get back to it.

You're a hero @masonhale! :smile:

@masonhale :metal:

@danieldocki @jnicklas Can you do a favor and comment on the jquery-ujs pull request I opened to draw more attention to it? https://github.com/rails/jquery-ujs/pull/464

@masonhale I added a comment. It's not been that long though, OSS moves slowly ;) They'll get to it eventually.

authors: JoshuaNovak919 cerdiogenes danieldocki jnicklas jokklan masonhale

repo: refile/refile


text:
Add collapse-duplicated-reviews feature

Fixes #5394
Test URLs
https://github.com/refined-github/sandbox/pull/10#pullrequestreview-958560681
Screenshot
https://user-images.githubusercontent.com/46634000/169702068-8bfe4f63-09b6-45c1-b2a1-0dee4d717f86.mp4

I'd rather collapse the whole thread into the title (so it's visible) and link the title to the real comment.
With the current PR, reacting to a comment means uncollapsing it and then clicking the permalink. Let's skip one step.

I'd rather collapse the whole thread into the title

By "title", do you mean the text next to the "review event"? But what happens if the review is made up of two duplicated comments, each responding to a different review thread?

By "title", do you mean the text next to the "review event"?

I mean this:

instead of this:

The latter is not actionable and it's out of context. That comment should not appear there, but the review should still keep the link to the real review comment, as shown in the first screenshot.

By title I mean filename

This is already what happens, see video above. We could avoid showing the "Show"/"Hide" text & icon, but since we hide something GitHub shows by default we should probably make it obvious it can be expanded.
Unless you want to drop the review thread completely?

and link the title to the real comment

+1

@fregante wdyt about this:

Instead of using the file name we make it clear this is a link to another comment (plus it's one less select because we don't need to grab the <summary>).

Closing until you have time to pick it up. This feature is just:
observe('collapsedReview', review => {
	if (isDuplicate(review)) {
	    const link = select('a', review)
	    details.replaceWith(link)
	    link.classList.add(...details.classList, ...otherClasses)
	}
})

authors: cheap-glitch fregante

repo: refined-github/refined-github


text:
🛑 SmartProtection is down

In 1be32fd, SmartProtection (https://smartprotection.com) was down:

HTTP code: 404
Response time: 297 ms

Resolved: SmartProtection is back up in 7003f29 after 10 minutes.

repo: reinaldoleon/monitoring


text:
ppo save expert demo

hi, how am i supposed to save expert demo in ppo main?

PPO is a method of reinforcement learning. However app, maxent and gail are all inverse reinforcement learning method. Due to the emergence of policy-based inverse reinforcement learning algorithms, you can use PPO with any inverse reinforcement learning algorithm to complete the training.
References:

Ng A Y, Russell S J. Algorithms for inverse reinforcement learning[C]//Icml. 2000, 1: 2.
Ho J, Gupta J, Ermon S. Model-free imitation learning with policy optimization[C]//International Conference on Machine Learning. PMLR, 2016: 2760-2769.

authors: francisduan gitouni

repo: reinforcement-learning-kr/lets-do-irl


text:
🛑 BINUSMAYA Praktikum (SLC Bluejack) is down

In 49bbdda, BINUSMAYA Praktikum (SLC Bluejack) (https://bluejack.binus.ac.id/binusmayalab/) was down:

HTTP code: 502
Response time: 1224 ms

Resolved: BINUSMAYA Praktikum (SLC Bluejack) is back up in 1070ff7.


text:
🛑 GreatNusa.com is down

In 12ab2d7, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 120 ms

Resolved: GreatNusa.com is back up in 76719e8.


text:
🛑 GreatNusa.com is down

In 3f36256, GreatNusa.com (https://greatnusa.com) was down:

HTTP code: 403
Response time: 118 ms

Resolved: GreatNusa.com is back up in 114ac4a.


text:
Client: Data export not respecting archived parameter

It seems the client.export_study_data endpoint does not adequately respect the archived parameter, returning archived reports when it is set to False. For now this means we can't filter on archived at the API, leading to a problem when exporting study data.
Currently we extract all data and then filter it ourselves.
Call has been opened.
    # DATA ANALYSIS
    def export_to_dataframe(self, archived=False) -> dict:
        """Exports all data from a study into a dict of dataframes for statistical analysis."""
        # TODO: change this to the correct archived,
        #  fails now because the parameter does not seem to be handled correctly server side
        self.map_data(archived=True)
        dataframes = {
            "Study": self.__export_study_data(archived),
            "Surveys": self.__export_survey_data(archived),
            "Reports": self.__export_report_data(archived),
        }
        return dataframes

This issue will be fixed with the next CDMS maintenance release (2023.2.2.0), which is planned for end of June.

authors: reiniervlinschoten slknijnenburg


text:
Decide what to do about auto-updates

See: https://github.com/actions/runner/issues/1396#issuecomment-983783264 also related to #16

This was transitively addressed via latest "version" and this PR: #39. Closing.

repo: related-sciences/gce-github-runner


text:
Update serializers to include new Locality data

After adding new models (Locality, LocalityStack and BibItemLocality) (see https://github.com/relaton/relaton-py/issues/18) to accommodate more DOI data, we want to include them when serialising a BibliographiItem.

@stefanomunarini, so doi2ietf (doilit) used to serialize this into <seriesInfo>—but it suddenly turned out to be wrong (violates XML specification). I stated the task as “reimplement the same handling as in doi2ietf/doilit”, so you have done what was requested—the mistake was at planning stage.
Apparently, we are supposed to use <refcontent>, based on:

Jean’s comment https://github.com/ietf-ribose/bibxml-service/issues/228#issuecomment-1177699864
The spec on <refcontent>

(cc @ronaldtse)

Note that <refcontent> data model is apparently plain text, so in the serializer we might need to format the entire locality hierarchy as one human-readable string.
It’s up to you how to attack this, but some considerations:

It’s probably worth encapsulating it in a separate, testable function that takes locality info and outputs a string (of course, if warranted, the logic can also be split further into smaller functions).
This function doesn’t have to cover all possible locality data from the start. We can increase coverage as we go, using existing samples as minimum baseline.
If we can write this nicely without extra requirements, that’d be ideal.

However, if this is a problem (f-strings don’t have conditionals, after all…), to prevent this logic from becoming a mess it may be worth adding a lightweight templating library to package requirements. I don’t really know a good one (Jinja2 seems overkill?), so let me know if you want to do this.

authors: stefanomunarini strogonoff

repo: relaton/relaton-py


text:
two big bugs! no support for "break" and inline loop

Describe the bug*
I am confront with two bugs,  key word "break" in "for loop" and inline loop are not supported in hot reload run. It output the error info: "Process finished with exit code -1073741819 (0xC0000005)".
here is the test code:
site=[0,2,2,2]
site=[ii for ii in site if ii!=0]
print('test')
for ii in site:
if ii==2:
break
print('finished')
when in debug mode, this code can run well in the first time, when something changed, such as print('somethin others'), it will quit directly when hot reload is triggered, and output the upper error code.
Desktop or remote (please complete the following information):**

OS: [Windows10, debian9]
Reloadium package version: [1.2]
Editor: [PyCharm]
Python Version: [3.9 and 3.10]
Python Architecture: [ 64bit]
Run mode: [Debug]

Additional context
Add any other context about the problem here.

Hi @jialay
Good catch! Thanks for opening this issue.
I've managed to fix the break issue but cannot reproduce the "inline loop" problem.
Do you mean the line comprehension in the second line?
Also could you provide the full version of your python interpreter (eg 3.9.8 )?

Hi, dkrystki, thank you for the great tool reloadium!
yes, the inline loop is just show as the second line. I tried it with python 3.9.12( debian 9, remote debug mode), and 3.10.0(windows 10, local mode), both of the them can't support hot reload。
such as the following code:
site=[0,2,2,2]
site=[ii for ii in site if ii!=0]
print('test')
print('finished')
debug with a breakpoint at line "print('finished')", any change of the code will interrupte the debug.

authors: dkrystki jialay

repo: reloadware/reloadium


text:
[BUG] ScrollView组件里slot无效

bug 描述
ScrollView组件slot无效
期望结果
如下截图所示
复现代码
可复现问题的代码仓库
关键代码
<View className="placeholder">placeholder</View>
<ScrollView scrollY refresherEnabled refresherDefaultStyle="none">
    <View className="refresher" slot="refresher">
        refresher
    </View>
    <View className="body">body</View>
</ScrollView>

版本信息:

remax 版本: 2.9.1
开发环境 win10，微信开发者工具

其他信息
微信原生可以

remax不可以

这个有进展吗，遇到同样的问题

这个有进展吗，遇到同样的问题

没有，当时我是打算搞个下拉刷新的loading。最后放弃了，直接用小程序原生的整页下拉刷新了。

bug 描述 ScrollView组件slot无效
期望结果 如下截图所示
复现代码 可复现问题的代码仓库 关键代码
<View className="placeholder">placeholder</View>
<ScrollView scrollY refresherEnabled refresherDefaultStyle="none">
    <View className="refresher" slot="refresher">
        refresher
    </View>
    <View className="body">body</View>
</ScrollView>

版本信息:

remax 版本: 2.9.1
开发环境 win10，微信开发者工具

其他信息
微信原生可以

remax不可以

目前不支持 slot 属性

authors: fhyoga ramen-curator watsonhaw5566

repo: remaxjs/remax


text:
Fix/missing macros

fix https://github.com/remaxjs/remax/issues/382#issuecomment-558000230

修复 babel-plugin-macros 找不到的错误

要改一下，要从开发者的角度去写

修复 babel-plugin-macros 找不到的错误

要改一下，要从开发者的角度去写

康康

authors: Darmody yesmeck


text:
Create an example of an app with nested routes

I'm trying to organize my routes using route folders, but I can't seem to get it to work. I came to the examples repo to find a good example, but none of the examples show how to use route folders. Could someone who knows how Remix route folders works create an example? Thanks so much.

Hi @elliotaplant,
This is a topic extensively covered by the documentation: https://remix.run/docs/en/main/file-conventions/routes#nested-routes
I suggest opening a Q&A conversation in the remix repository if you need guidance, showing us how you setup things and what's not working for you? I'd be happy to help you!

authors: elliotaplant machour

repo: remix-run/examples


text:
chore: fix ESLint errors & warnings

Fixes #625
Fixes #805

Thanks!

authors: MichaelDeBoey kentcdodds

repo: remix-run/remix


text:
Remove id attribute from RouteChangeAnnouncement component

https://github.com/remix-run/remix/discussions/763
tldr; the id attribute is not referenced anywhere, it seems it has no purpose.

we no longer have that in the template, but thank you!

authors: matmilbury ryanflorence


text:
Fix error when using modify() with pick, on a schema that doesn't define allOf

What this PR does
Fix an error that occurs if you pick fields using modify() on a schema that doesn't define allOf.
Why it happened / how it's fixed
Unguarded access to allOf.forEach(...) on the modified schema, which we now check.
How to reproduce and test
The following example no longer errors on this branch. The added test case demonstrates this.
const schema = {
 // This schema does not use `allOf`
  properties: {
    age: {
      title: 'Age',
      type: 'integer',
    },
    quantity: {
      title: 'Quantity',
      type: 'integer',
    },
  },
  'x-jsf-order': ['age', 'quantity'],
};

// TypeError reading properties of allOf
modify(schema, {
  pick: 'age'
})

Thanks @tcrammond this looks good, do you have a corresponding Dragon MR?

Thanks @tcrammond this looks good, do you have a corresponding Dragon MR?

Hi @ollyd, internal ticket here.

authors: ollyd tcrammond

repo: remoteoss/json-schema-form


text:
Process 'command '/Users/giuliopettenuzzo/Library/Android/sdk/ndk-bundle/ndk-build'' finished with non-zero exit value 2

I have been in this issue for one week. I'm not able to sort out, please help me!
I follow all the steps in the guide like 10 times and I still have the same error.
In the web I found a lot of people had this problem and I try all their solution but still don't work.
I have a MacBook Pro
Information:Gradle tasks [:app:generateDevelopDebugSources, :app:generateDevelopDebugAndroidTestSources, :app:prepareDevelopDebugUnitTestDependencies, :app:mockableAndroidJar, :app:compileDevelopDebugSources, :app:compileDevelopDebugAndroidTestSources, :app:compileDevelopDebugUnitTestSources, :tess-two:tess-two:generateDebugSources, :tess-two:tess-two:mockableAndroidJar, :tess-two:tess-two:prepareDebugUnitTestDependencies, :tess-two:tess-two:generateDebugAndroidTestSources, :tess-two:tess-two:compileDebugSources, :tess-two:tess-two:compileDebugUnitTestSources, :tess-two:tess-two:compileDebugAndroidTestSources]
Error:Execution failed for task ':tess-two:tess-two:ndkBuild'.
Process 'command '/Users/giuliopettenuzzo/Library/Android/sdk/ndk-bundle/ndk-build'' finished with non-zero exit value 2

in my case the path of ndk-build is like this:
ndkDir=/Users/giuliopettenuzzo/Library/Android/sdk/ndk-bundle

running the ndk-build in the tess-two jni directory I have the following error:
Android NDK: android-8 is unsupported. Using minimum supported version android-14.
Android NDK: WARNING: APP_PLATFORM android-14 is higher than android:minSdkVersion 8 in /Users/giuliopettenuzzo/AndroidStudioProjects/textfairy/tess-two/tess-two/AndroidManifest.xml. NDK binaries will not be comptible with devices older than android-14. See https://android.googlesource.com/platform/ndk/+/master/docs/user/common_problems.md for more information.
[armeabi-v7a] Compile        : lept <= adaptmap.c
make: /Users/giuliopettenuzzo/Library/Android/sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.8/prebuilt/darwin-x86_64/bin/arm-linux-androideabi-gcc: Command not found
make: *** [/Users/giuliop

See https://github.com/renard314/textfairy/issues/138#issuecomment-287583567. Same fix should work for you too.

should be fixed now

authors: GiulioPettenuzzo alexcohn renard314


text:
[BUG] Find daily notes & find week notes both show all the notes

Please confirm

[X] I am running the latest version of this plugin

Describe the bug
Both finding daily and weekly notes show all the notes that I have in my notes folder.
To Reproduce
Steps to reproduce the behavior:

Start nvim
:Telekasten find_daily_notes  (or :Telekasten find_weekly_notes)
Telescope window shows all the notes

Expected behavior
I'd like to only see daily/weekly notes
Screenshots
If applicable, add screenshots to help explain your problem.
Operating system (please complete the following information):

OS: Ubuntu 22-04

Additional context
Add any other context about the problem here.

Do you have the daily/weekly folders set to a different directory than the home directory? As far as I can tell, the pickers launched by find_daily_notes/find_weekly_notes uses the configured folder as the cwd for telescope.

@Tonitum No, I have everything laying flat within the ~/notes' folder. Should daily/weekly notes be in some specific place? When I create a daily note it also creates it within the '~/notes folder.

Then it is normal.
Basically find_daily/weekly opens a picker in the configured dailies and weeklies directory. If you have not specified anything special, it will always return everything in your home.

Not sure if there is a fix for that to be honest.
If it is possible, we could ask ripgrep to only search in files with the appropriate filename convention rather than using the default find_command. But I am not sure if it is possible.

Yeah, I can take a crack at this!

Think this is resolved, PR is here: https://github.com/renerocksai/telekasten.nvim/pull/328

authors: Tonitum lambtho12 marad


text:
Adds packageNameQuery to limit results on long feeds

This change is

<3


text:
Added support for Kubernetes 1.24.0

The code requires kubernetes.io/master label on two places

nodeSelectors
Tolerations

Add the master label right after kubeadm is inited and before installing the kurl addons. And this logic is added only if the current kubernetes version is >= 1.24.0
Tested for ekc-operator
$ kubectl get nodes --show-labels=true
NAME                                           STATUS   ROLES                  AGE   VERSION   LABELS
jalaja-k8s-v1-24-with-control-plane-labels-1   Ready    control-plane,master   26h   v1.24.0   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=jalaja-k8s-v1-24-with-control-plane-labels-1,kubernetes.io/os=linux,kurl.sh/cluster=true,node-role.kubernetes.io/control-plane=,node-role.kubernetes.io/master=,node.kubernetes.io/exclude-from-external-load-balancers=

What type of PR is this?
type::feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
SC-48706
Does this PR introduce a user-facing change?
No

Added support for Kubernetes 1.24.0

Does this PR require documentation?
Yes
TODO

@emosbaugh added logic for joining masters.

this looks better. can you please test on k8s 1.19,1.23 and 1.24

yeah, will let you know after testing on 1.19 and 1.23 and 1.24

Kurl:   Tested on 1.19 (only with master label and 1.24. Going to test 1.23 on staging.
Kots:  Built ttl image and manually edited the Deployment. And then ClusterNode, click Add Node to trigger the code path.
Ekco: Built ttl.sh image, manually edited the Deployment and added code to make sure it executes the new code.

$ kubectl get nodes --show-labels=true -A
NAME                        STATUS   ROLES    AGE   VERSION    LABELS
jalaja-kurl-1-19            Ready    master   58m   v1.19.16   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=jalaja-kurl-1-19,kubernetes.io/os=linux,kurl.sh/cluster=true,node-role.kubernetes.io/master=
jalaja-kurl-1-19-master-3   Ready    master   9m    v1.19.16   beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=jalaja-kurl-1-19-master-3,kubernetes.io/os=linux,kurl.sh/cluster=true,node-role.kubernetes.io/master=

$ kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.16", GitCommit:"e37e4ab4cc8dcda84f1344dda47a97bb1927d074", GitTreeState:"clean", BuildDate:"2021-10-27T16:24:44Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}

kubectl get nodes -A
NAME                        STATUS   ROLES    AGE   VERSION
jalaja-kurl-1-19            Ready    master   49m   v1.19.16
jalaja-kurl-1-19-master-3   Ready    master   23s   v1.19.16

Instance: 35.193.60.111

repo: replicatedhq/kURL


text:
[protocolv2] Fix passing input as first message being backwards incompatible

Why
In v1.1 sometimes the first message is not init, but instead it's the input. Let's handle that.
What changed
If we get an init that's not matching what we expect, we'll check if the client is on v1.1 and then we'll pass the first message as input and treat init as an empty object (which is what the first pass of requiring init for stream and upload be).
Versioning

[ ] Breaking protocol change
[ ] Breaking ts/js API change

Will link river-babel test PR shortly

test here https://github.com/replit/river-babel/pull/38/commits/814fe3be94f9d57850821a9d870315dbe8e00099

repo: replit/river


text:
Update set method not working as expected in Kotlin

From the docs
int rows = data.update(Person.class)
    .set(Person.ABOUT, "student")
    .where(Person.AGE.lt(21)).get().value();

I would expect the Kotlin equivalent to work similarly
val rows = data.update(Person::class)
    .set(Page::about, "student")
    .where(Page::age lt 21).get().value()

But I get Type mismatch: inferred type is KMutableProperty1<Person, String> but Expression<String> was expected. I realize that it must be an Expression, but I'm unsure of the proper way of converting the property to an Expression.
This is with a KotlinReactiveEntityStore<Persistable> data store

Thanks for reporting there was a bug in the set extension method it didn't have the right return type

Thanks for the quick fix!
On Mon, Jun 19, 2017 at 11:26 PM, Nikhil Purushe notifications@github.com
wrote:

Thanks for reporting there was a bug in the set extension method it didn't
have the right return type
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/requery/requery/issues/592#issuecomment-309656970,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLNR7F35Lj_7kZpU0UZTd9cPG_8UHtSks5sF2YCgaJpZM4N9DUB
.

Actually a question for you. I pulled the latest fixes and was still experiencing the problem. Looking at the test suite I saw that the Person class is a data class, but I'm using an interface. I figured out that I could get it to work if I just used the generated PersonEntity rather than the Person interface.
data.update(PersonEntity::class).set(PersonEntity.ABOUT, "student")

Is that intentional or should you be able to use the interface in the same fashion? It through me off because I'm using the interface in every other query.

data.update(PersonEntity::class).set(findAttribute(Person::about), "student")
Is this what you're looking for?

@consp1racy That's helpful, thank you!  I'm just curious if the API is working as intended. If I should expect the update function to behave the same when used with either an interface or data class, or if the workaround you've described is the intended way.

With the change you should be able to do:
data.update(Person::class).set(Person::about, "student")

I think the issue may be with my datastore which is a KotlinReactiveEntityStore<Persistable>(KotlinEntityDataStore(source.configuration)). Given the following model definition:
@Entity
data class Person constructor (
  @get:Key
  var id: Int,
  var name: String,
  var email: String,
  var birthday: Date,
  var age: Int,

  var about: String,

  @get:Column(unique = true)
  val uuid: UUID,
  val homepage: URL,
  val picture: String
) : io.requery.Persistable

I get the following errors:
    val rowCount = data.update(Person::class)
      .set(Person::about, "nothing") // Type mismatch: inferred type is KMutableProperty1<Person, String> but Expression<String> was expected
      .set(Person::age, 50) // Type mismatch: inferred type is KMutableProperty1<Person, String> but Expression<String> was expected
      .where(Person::age.eq(100)).get().value()

If I don't make Person persistable, the compiler obviously complains, but the errors on those lines go away.

I am having the same issue using KotlinReactiveEntityStore

Cannot choose among the following candidates without completing type inference:
public open fun <E : Any> update(entity: KClass<TreeInfoEntity>): KClass<TreeInfoEntity> defined in io.requery.sql.KotlinEntityDataStore
public open fun <E : Any> update(type: KClass<TreeInfoEntity>): Update<Scalar<Int>> defined in io.requery.sql.KotlinEntityDataStore

when I use update class. I'm using KotlinEntityDataStore

I am having the same issue.

authors: consp1racy exitface jeffzoch ninjudd npurushe xxxifan

repo: requery/requery


text:
Warning Please fix

warning
"request-promise-native > request-promise-core@1.1.3" has unmet peer dependency "request@^2.34".
warning
" > request-promise-native@1.0.8" has unmet peer dependency "request@^2.34".

Have you tried adding request dependency to your project?
Please read: https://nodejs.org/ru/blog/npm/peer-dependencies/

authors: ArtashMardoyan debugmaster

repo: request/request-promise-native

license: isc


text:
Using the response param from one endpoint in Request of another

Hello,
I want to pass the response received from one API as a request parameter in another API using Request-Promise NodeJs module. Can someone pls help me in this? I am giving a brief of the sample code below:
var Sequence = {
    test1: function (param) {
        return request({
            "method": "POST",
             "uri": baseURL+"/v1/" + userID + "/test/info/",
            "json": true,
            "headers": {
                "Accept": "application/json",
            },
        }).then(function (result) {
            return result.pairingInfo // I want to use this pairinfInfo param in another request
        })

test2 : function (param) {
       return request({
            "method": "POST",
            "uri": baseURL+"/v1/passenger/" + userID + "/test/test/",
            "json": true,
            "headers": {
                "Accept": "application/json",
            },
            "qs": {
                "pairingInfo": pairingInfo,//This pairingInfo would come from the returned result.pairingInfo of test 1 API call
            }
        })
    }
    },

function main(param) {
return sequence.test1(param).then(sequence.test2(param))
}

function main(param) {
    return sequence.test1(param)
        .then(function (pairingInfo) {
            return sequence.test2(pairingInfo)
        })
}

...should do the trick. Btw, if you want to understand why then read about the .then(...) function for promises in general.

repo: request/request-promise


text:
End to End TLS + SNI with proxy

Summary.
We are running TLS+SNI with fabio https://github.com/fabiolb/fabio and backed by a nodejs running an HTTPS server with self signed certs. We have the application working with curl. We can't get this working with requests. I tried the toolbelt as well as may other adapters I found on the internet. Fundamentally what we need to have happen is the client will connect to the proxy on the given physical IP and PORT. Then pass the logical host through so that the proxy can route the logical server name to the correct backend. Plz halp.
Expected Result
curl -v -X PUT --resolve "logical.server:10000:$IP" \
        "https://logical.server:10000/some/uri" -d '{"value": "hello"}' \
         -H "X-hmac: $(_hmac)" \
         -H "Content-Type: application/json" \
         -H "X-nonce: $(_nonce)"

Actual Result
With PyOpenSSL: (Caused by SSLError(SSLError("bad handshake: SysCallError(-1, 'Unexpected EOF')",),))
Without PyOpenSSL: (Caused by SSLError(SSLEOFError(8, u'EOF occurred in violation of protocol (_ssl.c:661)'),))

Reproduction Steps
However I can't find a reasonable solution in requests to mimic this curl behavior.
My first go was just following the toolbelt SNI example:
s = requests.Session()
s.mount("https://",  HostHeaderSSLAdapter())
nonce = _nonce()
data="foo"
r = s.put("https://$IP:10000/some/uri", json={"value": "hello"}, headers={
                                          "Host": "logical.server",
                                          "X-hmac": _hmac(data, SECRET),
                                          "Content-Type": "application/json",
                                          "X-nonce": nonce}, verify=False)

I tried other strategies around forcing TLS and spoofing with transparent proxies: https://github.com/jakubroztocil/httpie/issues/422#issuecomment-236398663. None changed the behavior.
System Information
$ python --version
Python 2.7.13
$ openssl version
OpenSSL 1.0.2l  25 May 2017
$ OSX (also tried on linux 14.04)
10.12.6

Without pyOpenSSL
$ pip freeze
asn1crypto==0.22.0
certifi==2017.7.27.1
cffi==1.10.0
chardet==3.0.4
cryptography==2.0.3
enum34==1.1.6
idna==2.6
ipaddress==1.0.18
pycparser==2.18
requests==2.18.4
requests-toolbelt==0.8.0
six==1.10.0
urllib3==1.22

With pyOpenSSL
$ pip freeze
asn1crypto==0.22.0
certifi==2017.7.27.1
cffi==1.10.0
chardet==3.0.4
cryptography==2.0.3
enum34==1.1.6
idna==2.6
ipaddress==1.0.18
pycparser==2.18
pyOpenSSL==17.3.0
requests==2.18.4
requests-toolbelt==0.8.0
six==1.10.0
urllib3==1.22

Openssl connecting to Fabio
$ openssl s_client -connect $IP:$PORT -servername logical.server
CONNECTED(00000003)
depth=0 /C=US/ST=CA/L=San Francisco/O=PubNub/OU=Dev/CN=logical.server
verify error:num=18:self signed certificate
verify return:1
depth=0 /C=US/ST=CA/L=San Francisco/O=PubNub/OU=Dev/CN=logical.server
verify return:1
---
Certificate chain
 0 s:/C=US/ST=CA/L=San Francisco/O=PubNub/OU=Dev/CN=logical.server.name
   i:/C=US/ST=CA/L=San Francisco/O=PubNub/OU=Dev/CN=logical.server.name
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIDozCCAougAwIBAgIJAM3s1shczk7eMA0GCSqGSIb3DQEBCwUAMGgxCzAJBgNV
BAYTAlVTMQswCQYDVQQIDAJDQTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzEPMA0G
A1UECgwGUHViTnViMQwwCgYDVQQLDANEZXYxFTATBgNVBAMMDHZhdWx0ci5sb2Nh
bDAeFw0xNzA5MTQyMjMzMzJaFw00NTAxMzAyMjMzMzJaMGgxCzAJBgNVBAYTAlVT
MQswCQYDVQQIDAJDQTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzEPMA0GA1UECgwG
UHViTnViMQwwCgYDVQQLDANEZXYxFTATBgNVBAMMDHZhdWx0ci5sb2NhbDCCASIw
DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKPtkscVVph69UEOYneVm9zh3Ru7
DPXihS4+P6U2hHANTpX/FOxQIP+FC5ELG+xDG2caCXbb7oER9MFm+TkytzQqW4ur
lbngnOl5t3QPHfsMB645SCYKmjREOMSwgIx4zi2brBf5GKAu5hOpP84FPSYd06a5
LzIJBEybiFJVKH/j2Ig5ekgvw6F6pjDMIb035G1WMHl341rOyusfAAEiJeTW0c6b
6MF4GJL8WS8tpwUVAGnFvcub6O/uxoniiW6vn53Xs04+zFgecYtklcqFZeUHKLxe
EPFbTXTi0yWUcC4UC/E9iFGVgVzBZxWQf1Bj/R3o1b+irZiYSGnNeX5IQSsCAwEA
AaNQME4wHQYDVR0OBBYEFFL6Npq18TvCkwc8tazezOERo5M9MB8GA1UdIwQYMBaA
FFL6Npq18TvCkwc8tazezOERo5M9MAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEL
BQADggEBAHtzLceffM1AWh/XXqidtb3fkLovpk9XAADoPetb2ARJBYG/BUJwmmiA
zEQ8IVxS5N3t+sdEC5RBKfqW05DDnW/0OY3eIHLUYqoyyvt6/WzJo08J6kKNLgIm
ukmOfNfs7i2R0YRbfsmq8Mze9Lk3G23Q44wOzx89vGX2mCYkeUznR9m28e+23wLX
aBYUix9XpWrj13R6pc1ljS2O9SqTWjsmi6zr/HhbdGd3QyVK+Q8g4DpJ2tWPzZR4
q7VsxEzJubKXGQb6d20k5DT4ehjQBAbxT4BSrqhyBABox4M/R2sQ4iDColXemXEI
YZl8zbJwpPZxV9mvstWY+NQDxCPe9yM=
-----END CERTIFICATE-----
subject=/C=US/ST=CA/L=San Francisco/O=PubNub/OU=Dev/CN=logical.server
issuer=/C=US/ST=CA/L=San Francisco/O=PubNub/OU=Dev/CN=logical.server
---
No client certificate CA names sent
---
SSL handshake has read 1299 bytes and written 447 bytes
---
New, TLSv1/SSLv3, Cipher is AES256-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1
    Cipher    : AES256-SHA
    Session-ID: DB0923D38B54871EE944C9A206A51B3C7C54BD5723EBB1DBF30D421AB742AD88
    Session-ID-ctx:
    Master-Key: D32CC66A48B71E577024A0947AC292CC32F374978F0156104D958A9AE24E9AA71B67AFCFD3D26F778139576E2CDF40EA
    Key-Arg   : None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - c3 64 25 44 9c 28 85 bc-a3 80 1c 79 96 e3 aa 45   .d%D.(.....y...E
    0010 - 2d dd 07 6d 8e 39 43 95-4c 36 dc 58 d6 ea 9e 2e   -..m.9C.L6.X....
    0020 - 60 10 f4 ba 83 84 e9 6a-29 25 d6 1e 5e 93 e7 15   `......j)%..^...
    0030 - 95 74 03 e5 d1 37 99 8f-c6 2b 15 ab bc ee 99 e4   .t...7...+......
    0040 - fd 89 a4 b4 57 d4 0a 0e-1e a6 86 22 ef 46 07 6a   ....W......".F.j
    0050 - 80 31 97 a7 6b 31 1f 45-f2 4e f7 63 65 e8 a0 d8   .1..k1.E.N.ce...
    0060 - 26 3e 5d d6 fa 97 87 3d-f2 dd 25 82 ff f7 d0 95   &>]....=..%.....
    0070 - d0 c9 f1 30 00 ba 71 e4-b4 1d 14 27 e9 ce 83 76   ...0..q....'...v
    0080 - c2 1e 25 84 1c ad 5c 0d-9f 03 ac a4 6b b8 4b 84   ..%...\.....k.K.
    0090 - 1d 38 f8 47 a4 01 c8 a9-79 55 1e 52 e2 0d 1d 42   .8.G....yU.R...B
    00a0 - ce 19 e2 ed d3 98 05 87-ba 6a de 45 e3 c7 01 c4   .........j.E....
    00b0 - 54 58 98 b0 40 c3 57 d2-96 08 30 41 ca b6 82 94   TX..@.W...0A....
    00c0 - 00 3e 1e 36 da 7f f3 44-7d f7 24 08 36 52 eb 69   .>.6...D}.$.6R.i

    Start Time: 1505515260
    Timeout   : 300 (sec)
    Verify return code: 18 (self signed certificate)

The problem here is the IP address. When you set that IP address Requests is unable to correctly set the SNI header, which may well be confusing your server.
Unfortunately at this time Requests does not support anything like curl's --resolve. You'd need to edit the hosts file on your machine to get this to work the way you want.

@lukasa is it understood the changes necessary to get this to work or is it unknown and require discovery?

The changes to the hosts file, or to Requests/urllib3?

The changes to requests or urllib to support resolve-like functionality

There is a semi-abandoned PR: shadow/urllib3#1209. That needs to be pursued.

Ok thanks! Will follow up if we have time.

repo: requests/requests


text:
Update README.md with "multimodal data" messaging

What
Update intro text, code snippet, and screenshot

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested demo.rerun.io (if applicable)

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Rendered

What about "About"? :zany_face:

authors: emilk nikolausWest teh-cmc

repo: rerun-io/rerun


text:
Allow SpaceViews to customize the behavior for how default visualizers are chosen

What

Builds on top of: https://github.com/rerun-io/rerun/pull/5047

We don't want to use Scalar as the indicator for LineSeries or PointSeries or else we would get both any time a user logs a Scalar. Instead we now delegate this choice to the space-view.
Additionally, entities are now always included in the query-results if they are visualizable, even if they aren't indicated. Without this there is no way to access the query-result in order to override its visualizers if necessary.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

nice. if we'd now enable visualizer overrides we could solve

#5010

authors: Wumpf jleibs


text:
Hover different on ocaml files.

The hover command gives identical results for hover on doc comments in .res and .ml files.
Hovever vscode shows markdown only for those from .res files.

Actually I was testing it wrong -- with the last published extension.
On master it works as expected.

repo: rescript-lang/rescript-vscode


text:
Long Sort and Copy

Thanks for the sort added in https://github.com/research-ag/vector/pull/15 !
I have started using vectors for buffer in a number of places even when I don't anticipate it getting too large.  Maybe this is a mistake as I saw that the performance for small collections is a bit better....but where the might get big I'm trying to use vector.
@timohanke mentioned a long-running sort which is really interesting to me and one particular use case that I have. This may be a different object all together, or maybe there is a 'mode' to add to this.
Thought one:  How hard would it be to add a "sort as you go" mode to vecotr so that it is a SortedVector? Is this just a function of sorting after each addition(It seems there might be some overhead to that).  Perhaps this is just StableHeapBTree and I should just stick with that, but I'd be interested in your thoughts.
Thought two:  Long running sort....If I do need to sort a huge vector for some reason at semi-regular intervals it would be great to be able to do that. Use case:  Once a month I want to sort all accounts by their balance and award them something(tokens, VP, give top 10% special rights).
Thought three:  Any thoughts on strategies to easily/quickly make copies of large vectors?  This seems like it could be a long process as well, but I'm not sure in motoko if there might be some way to efficiently make a 'quick copy' of a vector(or maybe some other object). I'm guessing that if the vector were static you might beable to use pointers to the original vector and then manipulate from there?  I'm thinking of things like snapshots for voting for tokens where there may be millions of accounts.
Perhaps this isn't the right place for this issue and I'd be happy to move it to the forum, but it seems that you all have likely done the most work around these things and it seemed like the right place to put it for now.

Thanks for the sort added in https://github.com/research-ag/vector/pull/15 !

Now published as vector 0.4.0 on mops.
Long running sort means that execution terminates, other messages can reach the canister, and then at some point sorting continues in another execution. There are two ways depending on your needs. The first is that we block (via lock) the use of the vector until sorting is completed. That means new messages can reach the canister but the lock does not allow them to alter the vector. In this case we can choose from a wider selection of sorting algorithms. Some algorithms might still be excluded, for example recursion will not work across executions, but many others are allowed.
The second way is an algorithm that sorts the vector in multiple steps, a little bit at a time, and does not lock the vector between executions. If you sort by balances for example then it could happen that a balance that has been "sorted" in the first step gets changed in between steps and then the second step has to "sort" it again. This way likely requires an algorithm that performs better than average on pre-sorted arrays. Otherwise it may never terminate. If the algorithm performs better on pre-sorted arrays the the hope is that with each step the remaining work will be reduced, even if the vector gets altered between steps.
Don't know if locking is acceptable for your application.

Re. copy. There already is a clone() function and it is as efficient as possible.

Re long sort. The benchmarks that you can see here show 7-9 billion instructions for sorting 1 million elements. So in 20B instructions, which I believe is the DTS limit, you can sort roughly around 2 million elements. That is true even for Array.sort. This means that long sort isn't anything that is Vector specific. It is needed for Array as well and should be implemented for Array first in my opinion.

authors: skilesare timohanke

repo: research-ag/vector


text:
Preview server does not support aliases

Describe the Bug
I use aliases with my TypeScript configuration in order to have simpler paths (@components/Test.tsx as an example), with the way the dev server currently works, I can't configure the tsconfig.json of the dev server, so it does not use proper aliases and do not found my components.
error - ../src/emails/TestEmail.tsx:19:0
Module not found: Can't resolve '@components/Test'

If I update the tsconfig.json used by the dev server, it works. In export mode, no problem.
Current workaround is to not use paths option, or to edit tsconfig.json inside .react-email folder, but it is auto-generated.
I am available to help with this fix if necessary and if you wish.
Which package is affected (leave empty if unsure)
react-email
Link to the code that reproduces this issue
None
To Reproduce
Add paths option in compilerOptions in tsconfig.json :
"paths": {
  "@components/*": ["components/*"],
  "@utils/*": ["utils/*"]
}

Expected Behavior
Dev server should work with aliases, like export mode.
What's your node version? (if relevant)
v20.5.1

I've implemented a workaround to temporarily address this issue by updating paths in React Email TypeScript configuration file (.react-email/tsconfig.json) and have also added a script entry for automating this process. Here's the code:
// src/utils/updateTsConfigDevServer.mjs
import * as fs from 'fs';

const devServerTsConfig = JSON.parse(fs.readFileSync('.react-email/tsconfig.json').toString());
const currentTsConfig = JSON.parse(fs.readFileSync('tsconfig.json').toString());

const normalizedPaths = Object.entries(currentTsConfig.compilerOptions.paths).reduce((prev, [key, paths]) => {
    return {...prev, [key]: paths.map(path => `../src/${path}`)}
}, {})

devServerTsConfig.compilerOptions.paths = normalizedPaths;

fs.writeFileSync('.react-email/tsconfig.json', JSON.stringify(devServerTsConfig, null, 2));

In addition, I've included a script in the package.json file to automate the workaround:
"scripts": {
    "dev": "node src/utils/updateTsConfigDevServer.mjs && email dev --dir src/emails"
}

Please note that this code may need modifications to suit another project folder structure.
I'm available and willing to assist with resolving this issue further. I've noticed that React Email seem to be using a similar approach to my workaround, such as merging the package.json for the dev server, could this be applied to tsconfig.json?. Please feel free to reach out if I can contribute to resolving the issue.

Any updates on this? It's a real hassle to have to update all path aliases to relative imports in order to preview and test emails. This also includes path aliases inside nested imports. The issue is happening on both the email dev command, as well as the VSCode extension. Any workarounds or suggestions would be greatly appreciated.

I'd love to see a screenshot of how you're organizing the filesystem with aliases for email templates. Given the simplistic and encapsulated nature of email templates, it's unusual that a complex file tree would be needed.

I'd love to see a screenshot of how you're organizing the filesystem with aliases for email templates. Given the simplistic and encapsulated nature of email templates, it's unusual that a complex file tree would be needed.

Hi @shellscape,
Personally, I don't have a particularly complex structure for my emails. However, I'm in a monorepo and each workspace uses more or less the same rules, including aliasing.
If I didn't have to use aliases, it wouldn't be very complicated without them either, but I wouldn't expect a dev server to change this behavior (and therefore my configurations), at least without it being documented.
Here's an example of the structure I use for my emails:
.
└── @acme/email/
    ├── atoms/
    │   └── Link.tsx
    ├── molecules/
    │   └── Article.tsx
    └── organisms/
        └── ArticlesGrid.tsx

We've just upgraded React Email and aliases no longer work in export mode, just like the dev server. This seems to have been introduced by this PR https://github.com/resend/react-email/pull/1027 which forces the use of a tsconfig.
I'm still of the opinion that React Email should be more flexible on the tools used for build and development and give this responsibility to the user but could facilitate integration with existing stacks. Or at least make this part configurable?
For the moment, I've simply removed the aliases from my project and I'm no longer using my previous workaround, which no longer works.

@Gregory-Gerard

I'm still of the opinion that React Email should be more flexible on the tools used for build and development and give this responsibility to the user but could facilitate integration with existing stacks. Or at least make this part configurable?

That is our intention with the project, what other pain points do you find make us hard to use on some stacks?

We've just upgraded React Email and aliases no longer work in export mode, just like the dev server. This seems to have been introduced by this PR https://github.com/resend/react-email/pull/1027 which forces the use of a tsconfig.

Sorry to hear that, I'll try getting a fix on this for you soon. For context, we had to use a specific tsconfig due to the esbuild JSX option getting overridden by tsconfig's which caused errors with users that had "jsx": "preserve". Just bumping esbuild should fix this for you. If you want I can get you a quick patch for now since I'm not sure I'll be able to get this fixed and released very soon.

@gabrielmfern
Thanks for your reply.
Mainly the pain points are with build / dev opinionated tools, which is great for getting started quickly but obviously less flexible. Maybe we could set up something to be able to configure at least the config files (tsconfig and so on) used by export and build?
There's no real critical issue, I just removed the aliases from my project for now, but thanks for offering me a quick patch.
I just saw that @bukinoshita closed this issue, may I open another issue about export mode?

@Gregory-Gerard Yeah, please do that, after today I think I'll tackle that, if you want I can also get you a quick patch you can use for now.

@Gregory-Gerard Hey, I forgot that I had implemented this, but I think the 2.0.0 also includes a fix for this. Can you check it out?

@gabrielmfern
Hey, thanks for your patience and assistance. The preview server seems to work perfectly with aliases and launches with serious performance improvements. Congrats!
Unfortunately, it seems that export is broken for now. I keep getting this error:
~/projects/stackblitz-starters-bziz8k 3s
❯ email export
✔ Preparing files...

✖ Failed when rendering Test.js
TypeError: component.default is not a function
    at eval (file:///home/projects/stackblitz-starters-bziz8k/node_modules/react-email/cli/index.js:777:75)
    at step (file:///home/projects/stackblitz-starters-bziz8k/node_modules/react-email/cli/index.js:185:23)
    at Object.eval [as next] (file:///home/projects/stackblitz-starters-bziz8k/node_modules/react-email/cli/index.js:126:20)
    at asyncGeneratorStep (file:///home/projects/stackblitz-starters-bziz8k/node_modules/react-email/cli/index.js:11:28)
    at _next (file:///home/projects/stackblitz-starters-bziz8k/node_modules/react-email/cli/index.js:29:17)

It does not seem to be my configuration because here is a minimal repro with just React Email installed: Minimal Repro
It appears to be related to this line: export.ts#65
By replacing component.default({}) with component.default.default({}), it works without any issues as before. I don't believe the problem is specifically with this line, but rather with the build method that may have changed.

Interesting, I think this might be an ESM issue since we build with CJS format. Maybe using require might fix this, will open a PR for it.

Hi. I can see it's been just 4 days. However, any progress on this?
I just initiated a new project inside turborepo using this guide and also took inspiration from this example and I am running into the TypeError: component.default is not a function issue as well.
The output is a bunch of javascript. I also found this already closed issue which basically has the same result.
We do have various different tsconfigs in our monorepo but don't use aliases within the packages folder that this project resides in.
Our base tsconfig is this:
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "display": "Default",
  "compilerOptions": {
    "plugins": [
      { "name": "next" }
    ],
    "target": "es2017",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "checkJs": true,
    "skipLibCheck": true,
    "strict": true,
    "strictNullChecks": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "noUncheckedIndexedAccess": true
  },
  "exclude": ["node_modules"]
}

However, I have doubts about this having an influence. I don't extend this base.
So far, I've tried this, but to no avail:
{
  "$schema": "https://json.schemastore.org/tsconfig",
  "compilerOptions": {
    "jsx": "react",
    "baseUrl": "."
  },
  "exclude": ["node_modules", "out"]
}

@tim3w4rp PR is open for this #1214

Hope, it would be resolved sooner.
Temporarily, i've just added my components or the whole my "src" folder as a dependency in package.json using local paths
{
  "dependencies": {
    "src": "file:./src"
  }
}

so, i able to import my file with absolute path like importing a package/library in node_modules,
import { MyComponentLego } from 'src/components'
import { SomeHelper } from 'src/helpers'

authors: Gregory-Gerard RakaDoank gabrielmfern shellscape taylor-lindores-reeves tim3w4rp

repo: resendlabs/react-email


text:
All examples core dump when running

This is built on a Ubuntu 18.04 docker following all of the directions for adding requirements.  Each example dies when trying to parse and build from its urdf file.  I've tried using DART master as well, which doesn't help.  Any ideas on what I could have missed that's causing this issue?
Compiled:
g++ -g -I/usr/include/eigen3 -o /tmp/hex src/examples/hexapod.cpp -l RobotDARTSimu -ldart

Run (gdb /tmp/hex):
Program received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x3a1) at malloc.c:3103
3103	malloc.c: No such file or directory.
(gdb) bt
#0  __GI___libc_free (mem=0x3a1) at malloc.c:3103
#1  0x00007fa6fc740f5b in dart::common::EmbeddedStateAndPropertiesAspect<dart::dynamics::GenericJoint<dart::math::SE3Space>, dart::dynamics::detail::GenericJointState<dart::math::SE3Space>, dart::dynamics::detail::GenericJointUniqueProperties<dart::math::SE3Space> >* dart::common::SpecializedForAspect<dart::common::EmbeddedStateAndPropertiesAspect<dart::dynamics::GenericJoint<dart::math::SE3Space>, dart::dynamics::detail::GenericJointState<dart::math::SE3Space>, dart::dynamics::detail::GenericJointUniqueProperties<dart::math::SE3Space> > >::_createAspect<dart::dynamics::FreeJoint::Properties const&>(dart::common::SpecializedForAspect<dart::common::EmbeddedStateAndPropertiesAspect<dart::dynamics::GenericJoint<dart::math::SE3Space>, dart::dynamics::detail::GenericJointState<dart::math::SE3Space>, dart::dynamics::detail::GenericJointUniqueProperties<dart::math::SE3Space> > >::type<dart::common::EmbeddedStateAndPropertiesAspect<dart::dynamics::GenericJoint<dart::math::SE3Space>, dart::dynamics::detail::GenericJointState<dart::math::SE3Space>, dart::dynamics::detail::GenericJointUniqueProperties<dart::math::SE3Space> > >, dart::dynamics::FreeJoint::Properties const&) [clone .isra.593] () from /usr/local/lib/libdart.so.6.9
#2  0x00007fa6fc741f27 in dart::dynamics::FreeJoint::FreeJoint(dart::dynamics::FreeJoint::Properties const&) () from /usr/local/lib/libdart.so.6.9
#3  0x00007fa6fcc70ef5 in dart::dynamics::Skeleton::createJointAndBodyNodePair<dart::dynamics::FreeJoint, dart::dynamics::BodyNode> (this=0x55ca0103a9c0,
    _parent=0x0, _jointProperties=..., _bodyProperties=...)
    at /usr/local/include/dart/dynamics/detail/Skeleton.hpp:82
---Type <return> to continue, or q <return> to quit---
#4  0x00007fa6fb596b0b in dart::utils::DartLoader::modelInterfaceToSkeleton(urdf::ModelInterface const*, dart::common::Uri const&, std::shared_ptr<dart::common::ResourceRetriever> const&) () from /usr/local/lib/libdart-utils-urdf.so.6.9
#5  0x00007fa6fb5974ad in dart::utils::DartLoader::parseSkeleton(dart::common::Uri const&, std::shared_ptr<dart::common::ResourceRetriever> const&) ()
   from /usr/local/lib/libdart-utils-urdf.so.6.9
#6  0x00007fa6fcc66e38 in robot_dart::Robot::_load_model (
    this=this@entry=0x55ca0102cfe0, filename="res/models/pexod.urdf",
    packages=std::vector of length 0, capacity 0,
    is_urdf_string=is_urdf_string@entry=false)
    at ../src/robot_dart/robot.cpp:1013
#7  0x00007fa6fcc6990b in robot_dart::Robot::Robot (this=0x55ca0102cfe0,
    model_file="res/models/pexod.urdf",
    packages=std::vector of length 0, capacity 0, robot_name=...,
    is_urdf_string=<optimized out>, cast_shadows=<optimized out>,
    damages=std::vector of length 0, capacity 0)
    at ../src/robot_dart/robot.cpp:151
#8  0x00007fa6fcc69c95 in robot_dart::Robot::Robot (this=0x55ca0102cfe0,
    model_file="res/models/pexod.urdf", robot_name="robot",
    is_urdf_string=<optimized out>, cast_shadows=<optimized out>, damages=...)
    at ../src/robot_dart/robot.cpp:157
#9  0x000055c9ff1d96c0 in __gnu_cxx::new_allocator<robot_dart::Robot>::construct<robot_dart::Robot, char const (&) [22]> (this=0x7ffeb510ad67,
---Type <return> to continue, or q <return> to quit---
    __p=0x55ca0102cfe0) at /usr/include/c++/7/ext/new_allocator.h:136
#10 0x000055c9ff1d90d6 in std::allocator_traits<std::allocator<robot_dart::Robot> >::construct<robot_dart::Robot, char const (&) [22]> (__a=...,
    __p=0x55ca0102cfe0) at /usr/include/c++/7/bits/alloc_traits.h:475
#11 0x000055c9ff1d8b5c in std::_Sp_counted_ptr_inplace<robot_dart::Robot, std::allocator<robot_dart::Robot>, (__gnu_cxx::_Lock_policy)2>::_Sp_counted_ptr_inplace<char const (&) [22]> (this=0x55ca0102cfd0, __a=...)
    at /usr/include/c++/7/bits/shared_ptr_base.h:526
#12 0x000055c9ff1d84a5 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::__shared_count<robot_dart::Robot, std::allocator<robot_dart::Robot>, char const (&) [22]> (this=0x7ffeb510af28, __a=...)
    at /usr/include/c++/7/bits/shared_ptr_base.h:637
#13 0x000055c9ff1d8014 in std::__shared_ptr<robot_dart::Robot, (__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<robot_dart::Robot>, char const (&) [22]> (this=0x7ffeb510af20, __tag=..., __a=...)
    at /usr/include/c++/7/bits/shared_ptr_base.h:1295
#14 0x000055c9ff1d78d3 in std::shared_ptr<robot_dart::Robot>::shared_ptr<std::allocator<robot_dart::Robot>, char const (&) [22]> (this=0x7ffeb510af20,
    __tag=..., __a=...) at /usr/include/c++/7/bits/shared_ptr.h:344
#15 0x000055c9ff1d6d48 in std::allocate_shared<robot_dart::Robot, std::allocator<robot_dart::Robot>, char const (&) [22]> (__a=...)
    at /usr/include/c++/7/bits/shared_ptr.h:691
#16 0x000055c9ff1d60cc in std::make_shared<robot_dart::Robot, char const (&) [2---Type <return> to continue, or q <return> to quit---
2]> () at /usr/include/c++/7/bits/shared_ptr.h:707
#17 0x000055c9ff1d515d in main () at src/examples/hexapod.cpp:11
(gdb)

Additional info (linking)
 ldd /tmp/hex
	linux-vdso.so.1 (0x00007fffa57eb000)
	libRobotDARTSimu.so => /usr/local/lib/libRobotDARTSimu.so (0x00007f56b6152000)
	libdart.so.6.9 => /usr/local/lib/libdart.so.6.9 (0x00007f56b5902000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f56b5579000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f56b5361000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f56b4f70000)
	libdart-utils.so.6.9 => /usr/local/lib/libdart-utils.so.6.9 (0x00007f56b4cba000)
	libdart-utils-urdf.so.6.9 => /usr/local/lib/libdart-utils-urdf.so.6.9 (0x00007f56b4a89000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f56b486a000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f56b44cc000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f56b42c8000)
	libdart-external-odelcpsolver.so.6.9 => /usr/local/lib/libdart-external-odelcpsolver.so.6.9 (0x00007f56b40ba000)
	libboost_system.so.1.65.1 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.65.1 (0x00007f56b3eb5000)
	libboost_filesystem.so.1.65.1 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.65.1 (0x00007f56b3c9b000)
	libboost_regex.so.1.65.1 => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.65.1 (0x00007f56b3993000)
	libfcl.so.0.5 => /usr/lib/x86_64-linux-gnu/libfcl.so.0.5 (0x00007f56b2eab000)
	libassimp.so.4 => /usr/lib/x86_64-linux-gnu/libassimp.so.4 (0x00007f56b24e0000)
	liboctomap.so.1.8 => /usr/lib/liboctomap.so.1.8 (0x00007f56b229c000)
	liboctomath.so.1.8 => /usr/lib/liboctomath.so.1.8 (0x00007f56b2096000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f56b65b8000)
	libtinyxml2.so.6 => /usr/lib/x86_64-linux-gnu/libtinyxml2.so.6 (0x00007f56b1e82000)
	liburdfdom_model.so.1.0 => /usr/lib/x86_64-linux-gnu/liburdfdom_model.so.1.0 (0x00007f56b1c60000)
	libicui18n.so.60 => /usr/lib/x86_64-linux-gnu/libicui18n.so.60 (0x00007f56b17bf000)
	libicuuc.so.60 => /usr/lib/x86_64-linux-gnu/libicuuc.so.60 (0x00007f56b1407000)
	libccd.so.2 => /usr/lib/x86_64-linux-gnu/libccd.so.2 (0x00007f56b11fc000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f56b0fdf000)
	libminizip.so.1 => /usr/lib/x86_64-linux-gnu/libminizip.so.1 (0x00007f56b0dd4000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f56b0bcc000)
	libtinyxml.so.2.6.2 => /usr/lib/x86_64-linux-gnu/libtinyxml.so.2.6.2 (0x00007f56b09b7000)
	libconsole_bridge.so.0.4 => /usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.4 (0x00007f56b07b2000)
	libicudata.so.60 => /usr/lib/x86_64-linux-gnu/libicudata.so.60 (0x00007f56aec09000)

Ok, there's probably something missing somehow in a straight build.  But after crawling around, I found the files in cmake/example and those worked.  So I created a equivalent cmakefile for the src/examples and so far all is well.
Closing this.

@danachee thank you for using our library. First of all, as we say in the README, the library is currently under heavy restructuring and many things (including the documentation/installation instructions) might not be up to date.
We will soon make a big v1.0 release with hopefully a proper documentation and surely many new features.

Compiled:
g++ -g -I/usr/include/eigen3 -o /tmp/hex src/examples/hexapod.cpp -l RobotDARTSimu -ldart

If you want to compile it by hand, you would need to add many more flags and link to more libraries. We strongly suggest to use waf (our current favorite build system -- for an example usage for finding robot_dart can be found here and here). If you prefer CMake, we recently provided support for this, so when you do [sudo] ./waf install a CMake config file will be installed, so that one can use CMake to find RobotDART along with its dependencies.
I guess you already discovered this, but just in case..

I realize its in flux, and I might just need to wait, but it seems the python side is "missing"??  I set it up to build the bindings, and it did install the object:

install /usr/local/lib/python3/dist-packages/RobotDART.cpython-38-x86_64-linux-gnu.so (from build/RobotDART.cpython-38-x86_64-linux-gnu.so)

But it didn't install anything else, and I can't find any python modules.  Are they missing, or do I need a different branch?
Thanks,

But it didn't install anything else, and I can't find any python modules

You do not need anything else. Most probably you have to change your PYTHONPATH (I guess by default it is not looking to /usr/local/): export PYTHONPATH=$PYTHONPATH:/usr/local/lib/python3/dist-packages/. Alternatively, you can do ./waf configure --prefix=/usr --python and then sudo ./waf install, this will install everything in /usr which should be okay for the PYTHONPATH. I prefer the first way (install in /usr/local and alter the PYTHONPATH as this keeps the system cleaner; you can also put the export in your bashrc/zshrc file so that you have it in every terminal by default).

You are correct!  Thanks again! (it was a typeo in my PYTHONPATH set that was the issue)
About waf.  Is it something that would be used on a "outside" set of code (not stored in the robot_dart repo)?
So if one were to create their own simulation, do they need to copy the waf and waf_tools into their directory?  And if so, what would they need to tell it?  Feel free to tell me this will all be in the user guide for the new version and to be patient :-).

You are correct! Thanks again! (it was a typeo in my PYTHONPATH set that was the issue)

Good!

About waf. Is it something that would be used on a "outside" set of code (not stored in the robot_dart repo)?

You do not need to use waf. We have provide the installation of CMake config for this reason: for people to use robot_dart within their CMake projects easily. So if you are familiar with CMake and using it, feel free to use the library in that way.

So if one were to create their own simulation, do they need to copy the waf and waf_tools into their directory? And if so, what would they need to tell it?

If you want to use waf for building your projects, there are many ways of doing this. I would suggest you to read the waf book where there is an extensive documentation of how to use waf in general.

Feel free to tell me this will all be in the user guide for the new version and to be patient :-).

We will make a small standalone example of how to use waf similar to our use-cases to find robot_dart and compile your projects, so you can be a bit patient until the documentation is finished. If you want to have a look now on possible use-cases, have a look at the whc library that depends on robot_dart and uses waf to get an idea.

authors: costashatz danachee


text:
webmanifest broken?

I tried to re-install Tileboard as an app after the recent restructure. But Firefox does not offer me install anymore. Only a regular add to home screen. I guess something broke with the webmanifest since I created it...

Hmm... The add to home screen does what I expect. It's working on the iPad. Maybe the icons/menus have just changed in Firefox...

Works for me too on Chrome.

authors: akloeckner rchl

repo: resoai/TileBoard


text:
Vertical Slider Tile

Add Vertical Slider tile.
Tile doesn't require any input from user, width and height will be calculated automatically based on Tile size.
Best to use with tile height > 1.
Also, some other options are available for user: sliderHeight and sliderWidth. If they are defined inside slider - they will be used in first place and take precedence via automated calculation.
Also, Tile supports icon. If icon doesn't defined it will be taken to consideration in case of automatic calculation.
Example:
{
    position: [0, 0],
    height: 3,
    id: 'light.entity',
    type: TYPES.SLIDER_VERTICAL,
    unit: '%',
    title: 'Slider',
    icon: 'mdi-lightbulb',
    state: false,
    filter: function (value) {
       var num = parseFloat(value) / 2.55 ;
       return num && !isNaN(num) ? num.toFixed() : 0;
    },
    value: '@attributes.brightness',
    slider: {
       max: 255,
       min: 0,
       step: 5,
       field: 'brightness',
       // sliderWidth: '60',
       // sliderHeight: '270',
       request: {
          type: "call_service",
          domain: "light",
          service: "turn_on",
          field: "brightness"
       },
    },
}

@rchl Can you please take a look on PR
Thanks in advance.

merged: https://github.com/resoai/TileBoard/pull/672
Thanks


text:
Reverb is always mono on any browser

HEllo!
Reverb is mono, even with the audio demos that are provided in the SDK like room models.
IT's mono on Electron, Safari, Firefox, everywhere.
Any chance to get this fixed?

I’ll look into this. We might be able to implement a stereo version of
reverb but that would only work if you dont want ambisonic output.
On Tue, Dec 25, 2018 at 2:28 AM ogomez92 notifications@github.com wrote:

HEllo!
Reverb is mono, even with the audio demos that are provided in the SDK
like room models.
IT's mono on Electron, Safari, Firefox, everywhere.
Any chance to get this fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/resonance-audio/resonance-audio-web-sdk/issues/23,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGDsNpH3u8tm2q7gBnOaXfNJIMyEg9HSks5u8dOWgaJpZM4Zg4vU
.

Reverb on mono sounds really wrong, that’s what I mean. I don’t think mono reverb is a good idea in any case.

On 6 Feb 2019, at 13:15, Drew Allen notifications@github.com wrote:
I’ll look into this. We might be able to implement a stereo version of
reverb but that would only work if you dont want ambisonic output.
On Tue, Dec 25, 2018 at 2:28 AM ogomez92 notifications@github.com wrote:

HEllo!
Reverb is mono, even with the audio demos that are provided in the SDK
like room models.
IT's mono on Electron, Safari, Firefox, everywhere.
Any chance to get this fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/resonance-audio/resonance-audio-web-sdk/issues/23,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGDsNpH3u8tm2q7gBnOaXfNJIMyEg9HSks5u8dOWgaJpZM4Zg4vU
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/resonance-audio/resonance-audio-web-sdk/issues/23#issuecomment-461002825, or mute the thread https://github.com/notifications/unsubscribe-auth/ADj_9fCBm5Z3gz7x__ewsOLeMZ_BQ4Ogks5vKsdegaJpZM4Zg4vU.

I agree. We just don’t want to implement something that will 4x as
expensive as current, and we’ll need to implement decorrelation filters,
I’ll need to see how cheap we can make them in WebAudio.
On Wed, Feb 6, 2019 at 11:14 AM ogomez92 notifications@github.com wrote:

Reverb on mono sounds really wrong, that’s what I mean. I don’t think mono
reverb is a good idea in any case.

On 6 Feb 2019, at 13:15, Drew Allen notifications@github.com wrote:
I’ll look into this. We might be able to implement a stereo version of
reverb but that would only work if you dont want ambisonic output.
On Tue, Dec 25, 2018 at 2:28 AM ogomez92 notifications@github.com
wrote:

HEllo!
Reverb is mono, even with the audio demos that are provided in the SDK
like room models.
IT's mono on Electron, Safari, Firefox, everywhere.
Any chance to get this fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/resonance-audio/resonance-audio-web-sdk/issues/23
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AGDsNpH3u8tm2q7gBnOaXfNJIMyEg9HSks5u8dOWgaJpZM4Zg4vU

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <
https://github.com/resonance-audio/resonance-audio-web-sdk/issues/23#issuecomment-461002825>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/ADj_9fCBm5Z3gz7x__ewsOLeMZ_BQ4Ogks5vKsdegaJpZM4Zg4vU
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/resonance-audio/resonance-audio-web-sdk/issues/23#issuecomment-461082838,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGDsNob8DriUSp2qMVNtAdxVx46GWnJrks5vKv9PgaJpZM4Zg4vU
.

This is a very uneducated guess, but wouldn't it be enough to simply create stereo noise for the reverb tail white noise in the convolver to at least give the impression? It might not be very accurate but already sound twice as real, if not more, until a better solution can be found that computes fast enough? Maybe it could be ported from the Resonance C library and compiled to WebAssembly. Right now I always set my room materials to transparent because the reverb actually makes it more confusing to tell where something comes from, because it's limited to a mono center channel and that throws off the perception. Adding a custom convolver with a real room impulse does, sadly, sound better at this point.

authors: Ghorthalon drewbitllama ogomez92

repo: resonance-audio/resonance-audio-web-sdk


text:
allowing before_execution_proc to be in the instance.

The ideia is to allowing Resource to have it's own before_execution_proc in addition to the one that's provided by the class. Let me know what you think.
thank you.

Could it be merged? looking for such functionality

@ab any chance to merge this? (open > 1yr), and we really want this functionality.

@ab any update on the status of this issue? do you need help to get it fixed?

Thanks! I ended up taking a slightly different approach here. You can set a :before_execution_proc as an option to any Request or Resource object.

authors: ab brbrr fribeiro oschreib simon3z

repo: rest-client/rest-client


text:
"self-update --output" fails to create a new file on Windows

Output of restic version
restic 0.9.6 compiled with go1.13.4 on windows/amd64
How did you run restic exactly? (/Actual behavior/Steps to reproduce the behavior)
Got the following error when running restic self-update:
$ restic self-update --output restic-new.exe
CreateFile restic-new.exe: The system cannot find the file specified.

If I create an empty file named restic-new.exe on the current directory, the command runs successfully:
$ touch restic-new.exe

$ restic self-update --output restic-new.exe
writing restic to restic-new.exe
find latest release of restic at GitHub
restic is up to date

I was able to update from 0.9.4 by creating such empty file.

Expected behavior
Restic should check for new version even when the output file doesn't exist.

Related Issues
On #2248 (self-update doesn't work on Windows), the suggested workaround is to use "--output".
Did restic help you today? Did it make you happy in any way?
It's the best backup solution I could find!

@guyshapiro Thanks for the report! Can you please update (edit) the initial post in this issue such that both examples (when it doesn't work and when it does work) contains the entire command and all the output from restic?

[I updated the report according to @rawtaz request.]

This doesn't appear to be specific to Windows, but also something I'm seeing on my Linux systems, that restic self-update --output requests the specified path to be an existing file.
$ mktemp --directory
/tmp/tmp.N7OIm2e9MO
$ /opt/restic/0.9.6/restic self-update --output /tmp/tmp.N7OIm2e9MO/restic
lstat /tmp/tmp.N7OIm2e9MO/restic: no such file or directory
$ touch /tmp/tmp.N7OIm2e9MO/restic
$ /opt/restic/0.9.6/restic self-update --output /tmp/tmp.N7OIm2e9MO/restic
writing restic to /tmp/tmp.N7OIm2e9MO/restic
find latest release of restic at GitHub
latest version is 0.10.0
download SHA256SUMS
download SHA256SUMS.asc
GPG signature verification succeeded
download restic_0.10.0_linux_amd64.bz2
downloaded restic_0.10.0_linux_amd64.bz2
saved 18378752 bytes in /tmp/tmp.N7OIm2e9MO/restic
successfully updated restic to version 0.10.0
$

The newly released restic 0.10.0 shows a corresponding behavior.
$ mktemp --directory
/tmp/tmp.ABJ89sJRmw
$ /opt/restic/0.10.0/restic self-update --output /tmp/tmp.ABJ89sJRmw/restic
lstat /tmp/tmp.ABJ89sJRmw/restic: no such file or directory
$ touch /tmp/tmp.ABJ89sJRmw/restic
$ /opt/restic/0.10.0/restic self-update --output /tmp/tmp.ABJ89sJRmw/restic
writing restic to /tmp/tmp.ABJ89sJRmw/restic
find latest release of restic at GitHub
restic is up to date
$

Unless I'm missing something this definitely feels like a bug, just the right size for me to take a stab at.

just the right size for me to take a stab at

Go pher it ;-)

Ok, here we go! https://github.com/restic/restic/pull/2937

authors: andreaso guyshapiro rawtaz

repo: restic/restic


text:
fix toJSON behavior

Fix long standing bug with double JSON stringifed errors.
When serializing to JSON, we now call toString() and VError should return the full context of the error message back. That's used as the 'message' when we have nested causes.

Blocker for restify/node-restify#1084

Coverage increased (+0.05%) to 98.02% when pulling 4f9137f4250130280d3316c7949f2f03e4c2ce48 on fix-toJSON into 03804812958d260c1c945498350b2f3980f236d1 on master.

@yunong @micahr incorrect usage of JSON.stringify (including tests) causing some integration issues with restify 5.x. This fixes that along with the tests.

authors: DonutEspresso coveralls

repo: restify/errors


text:
Fix #170 - set a 'dirty' flag in response to reconciliation

Issue: If a component calls setState, the UI does not get refreshed in response. This is very problematic for a UI, since the interesting interactivity will occur duet o state transitions.
Defect: Our setShouldRenderCallback should be smarter - as pointed out in #170 by @OhadRau , there are additional cases we need to handle here.
Fix: The reason-reactify reconciler was intended to help with this. It exposes both a onBeginReconcile and onEndReconcile events that are dispatched whenever a sub-tree is updated. For example, if you call setState(...) from some component, that event will be dispatched with the target node as the first argument. For now, we set a dirty flag to true, and clear that dirty flag on render.
There's a test case in reason-reactify that show how this functionality is intended to work:
https://github.com/revery-ui/reason-reactify/blob/cc0dbb453068f3693fc7fb692626c7d2f4ececcb/test/ContainerTest.re#L58
This PR addresses the particular case of updating the UI in response to nodes changing (which handles the style changing case, parent changing, an event happening, etc - as they all go through the reconciler).
Future work:

As called out in #170 - there may be other cases where we need to leverage such a flag, like when a window loses focus.
Incremental rendering - today, we always render the full screen. However, especially with something like #54 , we may be able to do much better in terms of just rendering a subtree.
I suspect there are still reconciler (reason-reactify) bugs we will run into - but that is good, it's expected we'll shake out the bugs in that space as we build out more real-world scenarios.

Fixes #170 , but we may want to track some of the corollary work called out (ie, re-rendering on window losing focus) in a separate issue.

Thanks for the review @OhadRau !

repo: revery-ui/revery


text:
Update requirements.md

Fixed typo mistake

Thank you for your first contribution @jignesh-baldha !

authors: janosmiko jignesh-baldha

repo: rewardenv/reward


text:
Update s3, sdk-core, sqs to 2.17.255

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

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

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

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

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

Superseded by #536.

repo: rewards-network/pure-aws


text:
Errors not propogated to the user

  function connect() {
    if (request) {
      return
    }

    readyState = CONNECTING
    controller = new AbortController()
    request = fetch(url, getRequestOptions())
      .then(onFetchResponse)
      .catch((err: Error & {type: string}) => {
        request = null

        // We expect abort errors when the user manually calls `close()` - ignore those
        if (err.name === 'AbortError' || err.type === 'aborted') {
          return
        }

        scheduleReconnect()
      })
  }

https://github.com/rexxars/eventsource-client/blob/d8244e895b0c47bcb15fc4f8dd1f098ed42daa57/src/client.ts#L80C2-L99C4
My understanding based on the code is when there is an error connecting there is no way to know. For my use case I'd like to display something to the user / have some logic to deal with errors like this.
I am planning on using this library - do you want a PR to add an onConnectionError or some other event?
Additionally, I'd like to update the reconnect logic to support some sort of back off strategy, do you want that in the library also?

@lukebelbina Did you figure this out?

@lukebelbina Did you figure this out?

I ended up pulling it down locally and making a couple changes, mainly
function connect() {
    if (request) {
      return;
    }

    readyState = CONNECTING;
    controller = new AbortController();
    request = fetch(url, getRequestOptions())
      .then(onFetchResponse)
      .catch((err: Error & { type: string }) => {
        request = null;

        // We expect abort errors when the user manually calls `close()` - ignore those
        if (err.name === 'AbortError' || err.type === 'aborted') {
          return;
        }

        onConnectionError(err);

        scheduleReconnect();
      });
  }

And throwing on non 200 status in onFetchResponse
async function onFetchResponse(response: FetchLikeResponse) {
    onConnect();
    parser.reset();

    const { body, redirected, status } = response;

    // HTTP 204 means "close the connection, no more data will be sent"
    if (status === 204) {
      onDisconnect();
      close();
      return;
    }

    if (status >= 400) {
      // todo better and more informative errors for the user
      // todo parse error body for more info
      throw new Error(`Unable to connect with HTTP status ${status}`);
    }

I was waiting to hear back from the maintainer if it was worth doing a PR. I'll give it until after the holidays and if I don't hear anything back I'll fork / submit a PR.

Thank you

authors: lukebelbina punkpeye

repo: rexxars/eventsource-client


text:
Pass node properties to renderer

This allow us to have an abstract representation of custom nodes and passing props to the render function such as:
{
  'type': 'linkbar',
  'description': 'some text',
  'image': 'image.jpg',
}

and render them as:
renderLinbar = ({description, image}) =>
  <Linkbar description={description} image={image} />

closing for now. Something is broken.

I'm going to need a test for this one

Closing this as #170 solved this with tests.

authors: juangl rexxars

repo: rexxars/react-markdown


text:
accept a path or bytes for Single and Parallel

let _ = Single::from_bytes(); // accepts a vector (or array) of bytes
let _ = Single::from_path(); // accepts a path leading to a .jpg image

let _ = Parallel::from_dir(); // accepts a directory containing .jpg images
let _ = Parallel::from_vec(); // accepts a vector of `Vec<u8>`'s or `&[u8]`'s

This allows for broader use of the crate.

it is decided this crate will not interact with filesystem at all, it will only deal with image bytes.

closed in #23

repo: rfdzan/jippigy


text:
Missing Copyright Info

Hi team,
I couldn’t identify the copyright information. I am not sure if the copyright info is accurate in the License file. If it is not, do you mind to provide the copyright information, maybe in the copyright notice file?

License was added on 45fbb83.
Thanks,

authors: morningwinter rfmoz

repo: rfmoz/grafana-dashboards


text:
[noco] Support for playlist

[x] I've verified and I assure that I'm running youtube-dl 2016.10.02
[x] README/FAQ/search
[x] Feature request (request for a new functionality)

Main extractor contributor: @dstftw

I'd like to suggest adding support for Noco's playlists, to allow download for a full series.
Example, with the "latest episodes" page:
http://noco.tv/emissions/64-4-148/olydri-studio/noob/derniers-episodes
{homepage} /emissions/ {playlist id} / {editor studio} / {series title slug} / {optional sorting filter; default: newest first}
Each episode is inside a <div class="item">, from which the fist link goes like:
http://noco.tv/emission/17205/olydri-studio/noob/s06e03-accomplissement
and is already supported by the Noco extractor URL matching. However, only the 30 newest episodes are listed in the HTML code of the page, older episodes get loaded by "infinite scroll".
Sidenote: Noco also uses this URL format:
http://noco.tv/famille/148/olydri-studio/noob
{homepage} / famille / {series id} / {editor studio} / {series title slug}
Which is an information page sorting by seasons, related contents, most viewed episode,  suggestions... From the actual series, the 15 most recent episodes can be seen in the slide menu, older ones get loaded by "infinite slide".
Pinpointing all episodes from a specific series may be quite challenging :(

+1 for this

authors: Alwaysin mitsukarenai

license: Unlicense