LinuxFile reused scratch buffers ensuring size was usable.  But the …

…limit value cannot be modified so later usage failed as an intended overwrite
Modified both methods that return a buffer.   The methods ensured the an existing buffer was large enough for the new request and returned it. But its new usage may containa greater limit value.   I could not alter the limit value of an existing buffer, instead if an old buffer exists I remove it an allocate a new buffer.
This is an answer to a  post.  If you agree with this, can you spin a 2.5.1 snap shot so this user can progress.
I did not research how many attributes we needed to compare if we wanted to reuse an existing buffer
@eitch @FDelporte

Further if i look at the old code, then we reuse the buffer... Are we sure this is ok, to just always write a new buffer? Are we not using the buffers in multiple calls in some way?

My last sentence in the pr about further validation for reuse.  We could test if the limit is the same or now less and i think reuse is ok. I would need to decide if there are other attributes that require similar validation.       And your code suggestion. I must retest but i think this will not handle the new limit being greater.   Will be late my daytime before i can do this work

-Git repeated saying that the push failed for my local being behind.  Seems it did accomplish something each attempt until I figured out how to fix this without using some dangerous force.  That left these extra commits, sorry about that.


Supporting delete in db client

Todo:

explore exception error and possibly propagating that up instead of a boolean

Todo:

explore exception error and possibly propagating that up instead of a boolean

Are you going to be adding the TODO to this PR and then review, or is that a TODO for a later date? @ahmedhamodi

I was going to do the todo in this PR probably tomorrow (today since it's after midnight).

Note: leaving the cleaning of error message to your implementation/decision on Tornado side @jaydhulia @vivianliu0


Exporting problems (Resolved after some tinkering)

While tinkering with animations, I ran into a problem where I can't export, test the project in-game, or update the gist.
I have tried-

Exporting with a new (doesn't update) and old name (doesn't make a new .png)
Saving the project as a new one
Removing certain animations
Removing certain blocks/parts

Even with the latest version of the mod, the problem persists.
I'm unsure what exactly caused this problem, but I feel it might be a problem others might've encountered and it could be looked into.
Alright after converting the vanilla parts for the second time, that seemed to fix it

I would assume messing with the head after converting it for the first time might've cause the mod to think there wasn't a head there initially?


ICCV2023 full paper list

I am wondering where I can find the full paper list for ICCV 2023.

Hi @Mrkkew,
Main conference program


'onAnimationFinish' never called

I am trying to use this package but for some reason my animation does not play.
My scenario is:

show Full image.
once the user press the image - animation starts
on animation end:
required scenario - show EMPTY image, which is the last image of my frames sequence.
current scenario - animation continue

when loopAnimation is false -> the animation does not play after the user press.
when loopAnimation is true (as it is now) -> the animation starts after the user press but it never stops, onAnimationFinish is never called.
My code is:
import React, { PureComponent } from 'react';
import PropTypes from 'prop-types';
import {
    Text,
    View,
    StyleSheet,
} from 'react-native';
import AnimatedSprite from 'react-native-animated-sprite';
import cupSprite from './MySprite';

class MyCom extends PureComponent {
    static propTypes = {
        ...
    }

    constructor(props) {
        super(props);

        let animationType;
        if (props.isDisabled) {
            animationType = 'DISABLED';
        } else {
            animationType = props.isFull ? 'FULL' : 'EMPTY';
        }

        this.state = {
            animationType,
        };
    }

    onPress = () => {
        if (!this.props.isDisabled) {
            if (this.props.isFull) {
                this.setState({
                    animationType: 'ALL',
                });
            } else {
                this.setState({
                    animationType: 'FULL',
                });
             }
            this.props.handlePress(this.props.number);
        }
    }

    handleAnimationFinish = () => (
        this.setState({
            animationType: 'EMPTY',
        });
    )

    renderAnimatedImages = () => (
        <AnimatedSprite
            sprite={mySprite}
            animationFrameIndex={mySprite.animationIndex(this.state.animationType)}
            loopAnimation
            draggable={false}
            size={{
                width: mySprite.size.width,
                height: mySprite.size.height,
            }}
            coordinates={{
                top: 0,
                left: 30,
            }}
            onPress={this.onPress}
            onAnimationFinish={this.handleAnimationFinish}
        />
    )

    render() {
        const {
            number,
            containerWidth,
            isDisabled,
        } = this.props;

        const textColor = isDisabled
            ? { color: 'rgba(83, 86, 90, 0.3)' }
            : { color: '#00a9e0' };

        return (
            <View style={...}>
               <Text style={[...]}>
                   {number}
               </Text>
               <View style={...}>
                   {this.renderAnimatedImages()}
                </View>
            </View>
        );
    }
}

export default Cup;

mySprite is:
const mySprite = {
    name: 'spriteName',
    size: { width: 60, height: 65 },
    animationTypes: ['ALL', 'DISABLE', 'EMPTY', 'FULL'],
    frames: [
        imageDisable,
        image01, image02, image03, image04, image05, image06, image07, image08, image09,
        image10, image11, image12, image13, image14, image15, image16, image17, image18,
        image19, image20, image21, image22, image23, image24, image25, image26, image27,
        image28, image29,
    ],
    animationIndex: function getAnimationIndex(animationType) {
        switch (animationType) {
            case 'ALL':
                return [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,
                    18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29];
            case 'DISABLED':
                return [0];
            case 'EMPTY':
                return [29];
            case 'FULL':
            default:
                return [1];
        }
    },
};

export default mySprite;

Sorry for slowness, see responses.
1) when loopAnimation is false -> the animation does not play after the user press.

Does the onPress function get called? You have several conditions in the onPress function, does
this.setState({
                    animationType: 'ALL',
                });

get called and set?
2) when loopAnimation is true (as it is now) -> the animation starts after the user press but it never stops, onAnimationFinish is never called.

Yes, when loopAnimation is true it will never call onAnimationFinish as how currently implemented loop is infinite. This could be changed and a PR is always welcome. See AnimatedSprite.js for code to change.

@micahrye thank for your reply
regarding question 1:
the onPress is called.

When loopAnimation === true: tapping on it starts the animation but the animation does not stop when it reaches the last image in the sequence.
When loopAnimation === false: tapping on WON'T starts the animation. and the image never change because onAnimationFinish never called.

Another issue, on Android the animation flickers.
I tried to reduce the number from 29 to 16-17 but it did not help.
I also changed the fsp, tried 15 and 25 with no luck.
I have 3 copies for every image: imageA.jpg<EMAIL_ADDRESS>and<EMAIL_ADDRESS>when the sizes are 4-6KB each.


All renders are completely black since installing ffmpeg.

Hey, so I've installed this mod on Fabric 1.20.2, and I've rendered like 2 test .png's to test it out, and it worked great! But then I've noticed that this mod has an option to render animations too, so I wanted to test it out. I've installed ffmpeg, checked in cmd if it's installed correctly by typing 'ffmpeg version'. It is installed correctly, so I restarted my PC and went back to Minecraft. The animation part of the GUI is now available, but when I've tried to render animations with any kind of file extension, it always resulted in black renders only. There's no content at all, only a black screen when I want to play back the mp4/gif/etc. I assume I've installed both the mod and ffmpeg correctly since I could render those 2 test png's fine prior to downloading ffmpeg. I've set the proper environment variables for ffmpeg as well. So I'm not sure what's the issue here, unfortunately. Oh, and now I've just noticed that even the still images come out completely black too. Btw, I'm not getting any error messages while I'm in-game. Any help would be appreciated.
Renders:

Logs:
https://mclo.gs/N5czMnr

Nevermind, I've just read https://github.com/gliscowo/isometric-renders/issues/7, and disabling iris did fix it. lol


Set additional header with user guid

A short explanation of the proposed change:
Set user guid as additional header. This can be used for example in the nginx access logs.
There will be a related capi PR which ensures that the guid is not forwarded to the client/user

Links to any other associated PRs

https://github.com/cloudfoundry/capi-release/pull/191

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

Hi @johha ,
Thanks so much for the PR! One minor question, it seems like we've eased an assertion in moving from eq to an include in the  it 'forwards the response from the rate limiter' test. It feels like it would be beneficial to keep at least one equality test, to guard against any potential accidental header inclusions in the future. What would you think about either moving back to an eq and including the X-USER-GUID header in that test, or changing the it 'sets the X-USER-GUID header' assertion to say it 'adds the X-USER-GUID header' and moving to an eq in that case?
Thanks,
Sarah & @MarcPaquette

Hi @sweinstein22 @MarcPaquette
thanks for your suggestions. I adjusted the tests but now the CI jobs are failing. Locally all tests are green. Could you have a look?
Thanks,
Johannes

The failing tests are unrelated flakes, so I am going to merge this in.  Thanks for the PR!


Enable locations to be generated for the caller in libraries

If a library uses this fault package but the caller does not (yet) then the reported error line is within the library which is not so useful to the caller. It makes sense to me that libraries should report the location of the caller to make it easier for non fault code to get an accurate location.
I however think that In user code this should stay as the line where the wrap is generated to enable the user to identify the relevant return statement.
To handle these 2 situations I separated out location generation in my fork and ensure that only 1 location is created per fault.Wrap
I have some additional changes on my branch relating to nil handling that I can separate out if this issue is accepted but my nil handling suggestion not.

Yeah I think you're right here, I went back and forth quite a bit on stack trace implementation and eventually settled on something quite simple though it's unfortunately opinionated.
I did consider making stack traces a decorator instead of integrated into the actual Fault library itself. But I opted for integration because it's pretty much a feature you'd never want to turn off. (and if you do, Fault probably isn't the right choice anyway)
One solution was to store a full stack trace (a slice of frame pointers) within the error chain and then when flattening/extracting metadata, locate the useful frames. However, this solution ended up being a bit too over-engineered.
It's worth considering a better solution long-term though. Perhaps it's as simple as just capturing two layers above the caller instead of just one and presenting one based on some heuristic?

I had the same issue when I tried to create an internal error package in one project where I would create all my errors using fault. All my stacktraces were pointing to the same internal package which was useless.
Just brainstorming, but could we introduce the Option pattern to fault.New
func New(message string, opts ...Option) error {

and we could pass an option to calculate an alternative location, something like

Hi! Thanks for the library and research around the topic of errors. It's fairly common for a project to have own "errors" package, and I think it is the right thing to do in many cases for following reasons:

Tailoring API for specific project needs; some projects may benefit from customised error formatting etc...
Avoid 3rd party dependency for something as core as error handling (remember when github.com/pkg/errors was archived?)

For that reason I think it would be great to have ability to create "Fault" instance which mirrors API of current fault package, but also allows to customise things like callerSkip or error formatting.
Something like this:
package myerrors

import "github.com/Southclaws/fault"

var fault = fault.NewInstance().WithMsgFormatter(myErrMsgFmtFunc).WithCallerSkip(4)

func New(msg string) error {
   return fault.New(msg)
}

// And the rest of myerrors API

Currently, I just copied source code of fault into internal package in my project to be able to build our project-specific errors package on top of fault.

This makes sense, Fault is designed as an error library library - a toolkit for building our your error handling solution with your own wrappers to chain in .Wrap calls so I'd welcome any improvements to the design in that regard.
An instance with configuration seems like a logical balance between keeping the top level interface very simple and providing flexibility. Definitely one to tackle for v1 #40

@matdurand ,
That would be great. Are you already working on this? I created a wrapper so that my APIs are consistent for what I need.  The location is always in my wrapper, of course.
e.g.
func New(errMsg string) error {
return fault.New(errMsg)
}
func NewF(errMsg string, va ...any) error {
return fault.Newf(errMsg, va...)
}
func NewWithContext(errMsg string, ctx context.Context, kv ...string) error {
return fctx.Wrap(fault.New(errMsg), ctx, kv...)
}
func NewWithValues(errMsg string, kv ...string) error {
return fctx.Wrap(fault.New(errMsg), context.Background(), kv...)
}
func Wrap(err error, errMsg string) error {
return fault.Wrap(err, fmsg.With(errMsg))
}
...

Yeah this is being worked on, I'll get a PR open for feedback from users soon!
I also do a similar thing with sentinel errors so there's a lot of re-use I could probably cut back on.
var errNotFound = fault.Wrap(fault.New("not found"), fmsg.WithDesc("not found", "The specified resource was not found"), ftag.With(ftag.NotFound))

Adding location to sentinel errors at the point of definition is unnecessary. Would be nice to have something like func NewSentinel(msg string, opts ...func(error)error)error that does not add location info.

@mculleyhl no I'm not.


[FLINK-20442][python][legal] Updated flink-python NOTICE

What is the purpose of the change
This pull request fixes the license problem of flink-python module
Verifying this change
This change is a trivial rework without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

cc @rmetzger @zentol

There are a lot of .proto files in the jar. Are they needed? afaik they are used for generating protobuf files, which is probably not happening at the user's side, right?

The META-INF/licenses/ASM file is still around.

@rmetzger I pushed a new commit which removed the byte bundle(also META-INF/licenses/ASM) and the *.proto files from the fat jar.

PS: Byte buddy is used in Beam's Java SDK harness and isn't used by PyFlink and should be safe to remove.

I reported the CI failure here: https://issues.apache.org/jira/browse/FLINK-20420

@rmetzger @zentol Thanks a lot for your review. Merging..

Closed via 7818b7a8290c84b99e809773b8c91fb028670865


CategoryRelations reg_scatter error with separator='cids'

An error appears from line 435 generally as
AttributeError: 'FacetGrid' object has no attribute 'map_DataFrame

Believe the bug has been fixed. Check in Jupyter notebook.


Inform user they should fetch a specific source when trying to launch a build shell

See original issue on GitLab
In GitLab by [Gitlab user @bochecha] on Sep 2, 2018, 10:48
Summary
I'm trying to open a build shell on an element which was pulled from the artifacts cache, not built.
That fails because I don't have the tarball.
Steps to reproduce

(optional: this helps making this 100% reproducible from scratch) completely clean your Buildstream cache:
$ rm -rf ~/.cache/buildstream

let's do this with the freedesktop-sdk:
$ git clone https://gitlab.com/freedesktop-sdk/freedesktop-sdk.git
$ cd freedesktop-sdk
$ git checkout 18.08

pull the libdrm build artifacts:
$ bst build base/pkg-config.bst desktop/libdrm.bst

try opening a build shell:
$ bst shell --build desktop/libdrm.bst

What is the current bug behavior?
$ bst shell --build desktop/libdrm.bst
[… snip …]
[00:00:00][13b665a5][ main:desktop/libdrm.bst            ] FAILURE Staging sources

Error launching shell: tar source at desktop/libdrm.bst [line 26 column 4]: Error staging source: [Errno 2] No such file or directory: '/home/mathieu/.cache/buildstream/sources/tar/https___dri_freedesktop_org_libdrm_libdrm_2_4_92_tar_bz2/e9e48fdb4de139dc4d9880aa1473158a16ff6aff63d14341367bd30a51ff39fa'

What is the expected correct behavior?
A working build shell.
Possible fixes
I guess Buildstream could download the sources itself, since that's necessary to open a build shell?
However the Buildstream UX is usually to require the user to explicitly take actions. The problem is that in this specific case, nothing seems to tell Buildstream to download the sources…
Other relevant information
… for example, I tried the following:
$ bst fetch desktop/libdrm.bst

But that did nothing, because Buildstream found that desktop/libdrm.bst was already built and cached.

BuildStream version affected: 1.1.7

Update: What happened here is that BuildStream tried to stage sources which were not previously fetched when trying to open a build shell with bst shell --build, and gave a confusing error message.
[Gitlab user @bochecha] tried running bst fetch --deps all desktop/libdrm.bst, but bst fetch --deps none desktop/libdrm.bst should have been sufficient.
We have some precedent for suggesting exactly what command invocation should be issued in some cases, like when trying to build with unfetched junctions, we should issue such a message in this case.

In GitLab by [Gitlab user @tristanvb] on Sep 2, 2018, 10:52
Ouch.
So it's totally plausible to run the scheduler as a part of bst shell in the case that the code is not present.
Also, the purpose of bst fetch is to obtain sources for later possibly offline work, it definitely should not ignore elements that happen to have a cached build.

In GitLab by [Gitlab user @bochecha] on Sep 2, 2018, 12:48
So, a bst fetch --deps all desktop/libdrm.bst allowed me to get a shell. It fetched a lot more than just the libdrm tarball though. :sweat_smile:

In GitLab by [Gitlab user @tpollard] on Sep 19, 2018, 14:28
Shouldn't bst pull handle this?

In GitLab by [Gitlab user @bochecha] on Sep 19, 2018, 23:04

Shouldn't bst pull handle this?

bst pull just tells me there's nothing to do, because everything is already cached locally. (since bst build actually pulled)

In GitLab by [Gitlab user @valentindavid] on Sep 24, 2018, 09:25
bst pull should not download source. But for the user experience, we should of course provide a better error message and suggest to use bst fetch.

In GitLab by [Gitlab user @tlater] on Sep 25, 2018, 15:10
mentioned in merge request website!93

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 11:59
changed title from {-Can't open a build shell on an element which was pulled-} to {+Inform user they should fetch a specific source when trying to launch a build shell+}

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 11:59
changed the description


add command lesson type

this is going to be one of those "cover your eyes" type PRs...

I kept my eyes open


raise InvalidURL(f"URL can't contain control characters. {url!r} "

Even with the simple example I have this error  :
File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\http\client.py", line 1200, in _validate_path
raise InvalidURL(f"URL can't contain control characters. {url!r} "
raise InvalidURL(f"URL can't contain control characters. {url!r} "
I commented out these lines, but it didnt help
from pytube import YouTube
YouTube('https://www.youtube.com/watch?v=Ic_FnHBiOYo').streams.first().download()
print ("ok")

hi @rcsmit that error appears to be coming from python's HTTP client code, and not pytube. Can you give the full traceback output from running the program?

Traceback (most recent call last):   File "c:/Users/rcxsm/Documents/phyton_scripts/youtubedownloader.py", line 108, in <module>     main()   File "c:/Users/rcxsm/Documents/phyton_scripts/youtubedownloader.py", line 106, in main     download(url)   File "c:/Users/rcxsm/Documents/phyton_scripts/youtubedownloader.py", line 72, in download     YouTube(durl).streams.first().download(filename=_filename)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\site-packages\pytube\__main__.py", line 91, in __init__     self.prefetch()   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\site-packages\pytube\__main__.py", line 184, in prefetch     self.js = request.get(self.js_url)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\site-packages\pytube\request.py", line 36, in get     return _execute_request(url).read().decode("utf-8")   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\site-packages\pytube\request.py", line 24, in _execute_request     return urlopen(request)  # nosec   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\urllib\request.py", line 222, in urlopen     return opener.open(url, data, timeout)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\urllib\request.py", line 525, in open     response = self._open(req, data)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\urllib\request.py", line 542, in _open     result = self._call_chain(self.handle_open, protocol, protocol +   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\urllib\request.py", line 502, in _call_chain     result = func(*args)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\urllib\request.py", line 1393, in https_open     return self.do_open(http.client.HTTPSConnection, req,   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\urllib\request.py", line 1350, in do_open     h.request(req.get_method(), req.selector, req.data, headers,   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\http\client.py", line 1255, in request     self._send_request(method, url, body, headers, encode_chunked)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\http\client.py", line 1266, in _send_request     self.putrequest(method, url, **skips)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\http\client.py", line 1100, in putrequest     self._validate_path(url)   File "C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\http\client.py", line 1200, in _validate_path     raise InvalidURL(f"URL can't contain control characters. {url!r} "

@rcsmit this actually appears to be a problem with your python installation. I would recommend uninstalling and reinstalling python to see if that fixes the issue.
That traceback appears to point to a typo in the http.client code itself. Since it looks like you're using a windows machine, be sure to install python directly from python.org

Hello! Thank you for your help. I did, but it didn't resolve my problem. If I am the only one, it seems to be out of scope of pytube though. Thanks again.

Sorry that I can't help more, I just can't seem to reproduce this problem myself, even when I copy and paste your code sample, and that error output makes it look like its an issue with the C:\Users\rcxsm\AppData\Local\Programs\Python\Python38\lib\http\client.py file


Require connections to Vault instances on the same node or availability zone

Blocked by https://github.com/hashicorp/vault-helm/issues/424

Vault is gone! 🎉


Add details about updating item metadata in MSBuild

Should be merged only after the following PR from MSBuild makes it into Visual Studio: https://github.com/microsoft/msbuild/pull/4975

@cdmihai : Thanks for your contribution! The author(s) have been notified to review your proposed change. @kempb

@cdmihai : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@rainersigwald: Added documentation for updating metadata, including the new qualified metadata references.

@cdmihai : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@cdmihai : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ghogen, this is the new 16.6 feature that we talked about the other day, so we should probably retarget this to the internal 16.6 branch. It's tied to https://github.com/microsoft/msbuild/pull/4975.

@rainersigwald @cdmihai OK, let's close this here then and resubmit the changes internally. I created a release-16.6 branch just now for us to use.


Add function to improve nested dict config parsing

Hydra-core uses a nested dict config format to represent config. Such data structure is poorly parsed actually (see picture).

Do

This PR improves the parsing of nested dict structure (DictConfig) along with sequence structure. It results in more readable config logging (see picture below).
This PR also fixes the inconsistent doc-hint typing for init config parameter.
This PR introduces base cases tests for parse_config.
This PR introduces tests for newly introduce parsing.

Don't

I've tried adding hint typing to parse_config but mypy does not like the missing FLAGS type missing from Tensorflow.
If PR is accepted, will improve related doc to config logging.

@dmitryduev, do you have an ETA to the merge of my PR?

hey @davebulaval, many thanks for the excellent contribution and sorry about the slow response!
we have been thinking about how to best incorporate this as it is really nice to be able to natively support hydra/nested mappings in general. our main concern is with the way the (nested) config keys are flattened, which makes the transformation non-invertible.
we are currently hacking on a frontend component that will allow (interactively) displaying nested configs on the run info page. how does that sound to you?

@dmitryduev, I agree that flatten config is less readable in the GUI. I agree that hacking to show the config in a nested way is way more interesting. Keep me updated!

Our current thinking is that it'll look something like what we have in the run comparer; so we'd want to merge in most of what you have in this pr, except for the nested key flattening logic.
Thanks again, and I'll keep you posted!

@dmitryduev, it seems like it.

@davebulaval a quick update: we have the frontend PR in review now - I'll ping you once that is merged.

hey @davebulaval: our frontend can now display nested mappings:

Please give it a try!
Would you be willing to repurpose this PR into one that adds native support of Mapping objects like OmegaConf's dictionary (using e.g. omegaconf.OmegaConf.to_container), i.e. so that one could feed those directly into wandb.init(config=...)?

@dmitryduev, to be sure, you want to add a clear implementation in parse_config that will use OmegaConf.to_container(conf, resolve=True) to handle the conversion of OmegaConf into primitive dict?
Do I keep the other nested approach? Or we will only focus on OmegaConf-like nested dict?
I think that Hydra-core uses OmegaConf, but I haven't validated it.

@dmitryduev, to be sure, you want to add a clear implementation in parse_config that will use OmegaConf.to_container(conf, resolve=True) to handle the conversion of OmegaConf into primitive dict? Do I keep the other nested approach? Or we will only focus on OmegaConf-like nested dict? I think that Hydra-core uses OmegaConf, but I haven't validated it.

My bad. @dmitryduev I'm still waiting for responses to my previous questions.

Hey @davebulaval, apologies for the late reply.

add a clear implementation in parse_config that will use OmegaConf.to_container(conf, resolve=True) to handle the conversion of OmegaConf into primitive dict?
Yes, please!
Do I keep the other nested approach?
Basically, we only need to make sure that the config is a (true) nested dict, so I'd only focus on OmegaConf for now (with a test case that a hydra config gets processed properly).

Thanks once again for your contribution!

@dmitryduev sorry for the long delay, I've been busy. I've just pushed a fix with what you are asking.

I've just pushed a fix for the missing requirements omegaconf in the requirements. I don't know If there is another place that is indicated for the doc.
Also, flake and mypy is not passing due to import order and frankly, I don't know what to do with it. Flake comply about placing order and I'm not familiar with that. I personally prefer Black.


Added Romanian translation

Will be nice to have something like this: zero_results / one_results / few_results / other_results
Here is a reference for ranges:
https://www.unicode.org/cldr/charts/44/supplemental/language_plural_rules.html#ro

Someone to merge this PR?

Hey @mateesville93 , sorry for the delay! Merging now, and I'll ping you again when the next release lands.

Released in released in v1.1.0, thanks again!


'DOTweenEditorPreview' does not contain a definition for 'isPreviewing'

Hey @brunomikoski ,
Just trying out version 0.2.4 with DOTween 1.2.632 and getting this:
Assets\Animation-Sequencer\Scripts\Editor\Core\AnimationSequencerControllerCustomEditor.cs(113,38): error CS0117: 'DOTweenEditorPreview' does not contain a definition for 'isPreviewing'

Did you manually edit DOTween to expose this?
All the best.

I just tested both 0.24 of the sequencer and DOTween 1.2.632  and both are working here, are you sure you created the asmdef files from the DOTween Setup Panel?

Hey @brunomikoski ,
Yeah, I definitely did that as I was getting other errors prior to that.
Using Rider to peek into the DOTween code, only _isPrviewing exists and it is Private:

To repro:

Create new Unity 2019.4.29 3D Project
Import Animation Sequencer 0.2.4
Import the free DOTween from Asset Store - "DOTween (HOTween v2)" - https://assetstore.unity.com/packages/tools/animation/dotween-hotween-v2-27676
Setup DOTween with all tickboxes
Create the .asmdef files.

Repro Project: https://drive.google.com/file/d/1-M51qlSm1JNDETA4n138bXlZ16QyHtKG/view?usp=sharing
All the best.

Looks like DOTween version on Asset Store it outdated:

Install the version v1.2.632 from their website:
http://dotween.demigiant.com/download.php

That's really weird, it does list as the same version in the Asset Store:

I'll give the version you linked a shot.
Thanks!

The direct download from the DOTween site has resolved this, thank you.

Holy cow I'm so sorry, also for not seeing this sooner! I just checked and the Asset Store reports the right package uploaded so I don't understand what happened, but I'll re-upload a newer version within the week (which also has a few nicer additions) 👀

Maybe was some caching issue? But I noticed this a couple of times with this past release, that said one version on the asset store, but when you download it, was actually a older version

The weird thing is that DOTween itself was telling me I had the newest version in the Utility Panel but it was missing the IsPreviewing functionality.
I wonder if I somehow got a frankenbuild.and that is how I was missing the required functionality... .That said, I'm 99.9% sure I imported it fresh into a new project!


Hidden Test Cases for Lab 8 Level 6

Hello everyone is anyone else facing the same issues as me? I can't seem to pass these few test cases and I can't figure out what's wrong.... Does anyone have any advice or tips on what are the possible steps I can take to resolve this? Thanks!

for line 74 you should check your back method such that the same room(same reference) is returned if there is no previous room. also ensure that your add method doesnt change the current previous room

Hi. For your output line 38, I had the same issue as well. The problem probably lies with the fact that every time you enter a new room, and if you are holding the sword, you have to bring it to the new room first. You should only add this sword into the new room, and not all of the items into the new room.
I had a checker in level 4 where there is a boolean method that checks if user isholdingSword and if it is, I will store that sword via another method called insertSword that returns a sword. Hence, in my go() method, I would add this sword into the new room, and that solves my issue for Line 38. Hope this helps!

Hello! There are two main errors with the logic of the code.

The insertion order of the sword is wrong, you should change this in the back() method. Essentially, objects being brought into the previous room should appear last, after all the objects in the previous room.
If the player is carrying a sword and leaving room A to room B, then the sword should be removed from room A. If the person drops the sword in room B and then goes back to room A, the sword should not be present in the list of objects in A. The second error where the sword keeps appearing is due to the sword still appearing in the previous room. This is rectified in the go() method.

Hope this helps!


Destroy objects created in enable() when disable() is called

For example, settings: https://github.com/model-map/view-split-gnome-extension/blob/6ce331a282c3c692434bc082a48fdb6e98be1fbf/extension.js#L92
Here is some good reference documentation: https://gjs.guide/extensions/review-guidelines/review-guidelines.html#basics

Hi Cole!
New release declares the settings as a let variable that is assigned value in enable() and subsequently made null in disable().
Thank you for raising the issue!


removes unnecesary console log

This console log was forgotten there, and creates 30 lines of logs everytime someone access public timeline


Replace external usage of loader.fetch with use of new virtualNetwork.authedFetch

I think this is a good approach :+1:

I think the matrix test errors are real and related to session state leaking when logging out and logging back in as a different user


Authorized Distributors

Hello,
Is it possible to filter by Authorized Distributors?
Thanks 🙂

Hi @Ana-Oxit - thanks for your question
As you spotted this is supported already in our NEXAR_SUPPLY_DISTRIBUTOR_*...() functions.


[WIP] Increase test coverage

WHY
Current C0 test coverage is under 100%. To keep the quality of Terraforming, we have to keep test coverage 100%.

Changes Unknown when pulling f3d111b7967a42069744c79c6b0e68e5af6fca73 on increase-test-cov-160528 into ** on master**.

Changes Unknown when pulling 9b5ca249511c530e3d8b48fb874af455d78f7367 on increase-test-cov-160528 into ** on master**.


Support for minification

We need to write a grunt script to allow for minification of each individual file as well as a combined file.
Tests should run off the minified files to ensure that minification did not break anything.

Done with https://github.com/dequelabs/ngA11y/pull/7

ok, looks like its closed, took me a couple of versions to get the bower files to a minimum :-/


Specify NodeJs version in readme.

The Nullish Coalescing Operator is not supported in v12 for example (ES2020)
could be replaced following the syntax below:
return answer == null ? 42 : answer;
same than
return answer ?? 42;

Since this is a web application, the code is running in the browser’s JavaScript runtime. Node is not involved here. Therefore, you should check caniuse: https://caniuse.com/?search=nullish coalescing
Bullish coalescing works in all browsers, except IE, which is fine, as this was replaced by Edge.

Well. I am not expert. Just noticed moving from 12 to 20 did the trick because of the Nullish Coalescing Operator: https://share.eva.mpg.de/index.php/s/bdoi3wzHdb26o99

Ah okay, a node package (the toastify component) was using that syntax. Indeed this was an node issue. Anyway, Node 16 is pretty old and it is end-of-life. I never developed this experiment with such an old version. When people install node, they usually get the latest LTS version. Is your distro shipping with such a legacy version?

Yes it is. Not sure why though. But was fast to fix once known.
I would just suggest specifying min requirements to avoid other users to run in the same kind of error or modifying the syntax ;)


Render FlowComponents into layout

When i use
FlowLayout.render 'main_layout',
        content: 'settings'

and i have a component settings -> rendering only Blaze.Template and not starting component

I'm quite not sure what you are raising?
Could you work on a sample repo with isolated example.
So, we can fix it quickly.

https://github.com/gibson/flowtest

Just curious, have you tried:
{{> render component=content}}
instead of
{{> Template.dynamic template=content}}
Template.dynamic is Blaze's provision for dynamically selecting a template.  render is Component's provision for rendering a component.

I think @lassombra answer is correct.

I threw together a quick and dirty proof of this working: http://meteorpad.com/pad/33RKCXvTrqqWME2HH/Flow-Component-In-Layout
You'll see there the Template.dynamic replaced with render.


How does Kronos handle lack of connection / reachability changes?

Curious to know if there are mechanisms in place for reachability changes

AFAIK there isn't anything custom in kronos for this and it's up to you to call again if you need to refetch this info when these change

Thank you!


[AST] Preserve l-valueness of covariant result type after replacement

It's possible that covariant result type is wrapped in l-value.
Just like currently preserved optionality, transformation should
maintain l-valueness of a result type as well.
Resolves rdar://problem/71167129

@swift-ci please smoke test

@swift-ci please smoke test


bind ctrl + s to screenshot by default

added ctrl + s as a keybind for the screenshot plugin as requested by issue #2483

Instead of having everyone PR their favorite key for everything, I think we should allow people to set hotkeys for things.

The hot key combination should be customizable in my opinion.


Add config option to disable the concept of "pending tabs"

After updating to atom 1.6.0-beta0, I found that my usual habit of opening tabs through single clicking was disrupted by having the tabs replace each other instead of opening next to each other.
I had to dig in to the release notes to find the problem - I was automatically opted in to the feature of "pending tabs", with no way out.  I never want to see a tab in a "pending" state, ever.  There should be a way to turn this feature off, and return to the previous behavior, in which every tab is always "non-pending".  A checkbox in the settings should be sufficient for this.

/cc @kuychaco

Planning to add a config option and patch it into 1.6 beta. Stay tuned.

Thank you!

Excellent!  Thank you so much for fixing this.  If I'd realized it was that easy, I might have submitted a patch myself. :)

@bjmiller you're welcome. Thanks for your feedback! If you do decide to open a pull request in the future, we'd totally welcome it :)

I'm still unable to get the old behaviour in Atom 1.8.0.
By default, if I single click items in the tree view, panes replaces themselves. If I uncheck the new Allow Pending Pane Items in core settings, single clicking an item does nothing. What me and I guess @bjmiller want is that the single click always opens new non-pending pane.

@lorenzos You might be looking for https://atom.io/packages/single-click-open.

@50Wliu Exactly! Thank you.

We have it now! https://flight-manual.atom.io/using-atom/sections/pending-pane-items/#disabling-pending-pane-items


Fix panic while decoding large Miniscripts from Script

Use private module to guard all constructors.

The new lockfiles don't work with MSRV.

@apoelstra this is ready for review.

The new lockfile updates cc to 1.1.6  which still does not work  with MSRV.
Ok if I force-push to this PR to try to fix the lockfiles?

@apoelstra I just tested it again with 1.56.1 and it works.

Re "CI happy means we're good", see #719 -- we are actually testing only with Cargo-minimal.lock, not Cargo-recent.lock (which is broken).
Furthermore, this lockfile commit makes several unnecessary changes and because it's in a separate commit from the one that changes Cargo.toml, also means that I cannot locally test every  commit of this PR.

Tagged and published.


Feat: Adding animations on Careers Page

Describe the feature
Currenty the Careers page is decent but can add animations to make it better UI we can use GSAP or anime.js libraries for that
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@upsaurav12 Issue assigned to you


fixed bug in dist/sampler - rule=Gaussian quadrature

Fixed bug in sampler, rule=Gaussian quadrature where trans needed an additional keyword verboose.
File "/usr/local/lib/python2.7/dist-packages/chaospy/dist/sampler.py", line 118, in samplegen
X = trans(X, verbose=verbose)
TypeError: () got an unexpected keyword argument 'verbose'

Takker. :)

Bare hyggelig :)
2015-09-15 9:10 GMT+02:00 jonathf<EMAIL_ADDRESS>
Takker. :)
—
Reply to this email directly or view it on GitHub
https://github.com/hplgit/chaospy/pull/2#issuecomment-140300868.

--

Simen


🐛: Incorrect Mode Switch Button Label

:red_circle: Title : Incorrect Mode Switch Button Label
:red_circle: Bug : When the website is in dark mode, the mode-switch button incorrectly displays "dark" instead of "light." The button should indicate the mode to switch to, not the current mode.
:red_circle: Changes :   Replacing words
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Rupal Patel Yadav
What is your participant role? (GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@Avdhesh-Varshney kindly assign so i can resolve it asap


使用ScreenUtilInit运行报错：Ensure to initialize ScreenUtil before accessing it.

版本：4.0.4+1以及其他4.0.X其他版本
错误：======== Exception caught by widgets library =======================================================
The following assertion was thrown building LayoutBuilder:
Ensure to initialize ScreenUtil before accessing it.
Please execute the init method : ScreenUtil.init()
'package:flutter_screenutil/screen_util.dart':
Failed assertion: line 34 pos 7: '_instance != null'
The relevant error-causing widget was:
OrientationBuilder file:///D:/tool/flutter-env/flutter_1.22.6/.pub-cache/hosted/pub.flutter-io.cn/flutter_screenutil-4.0.4+1/lib/screenutil_init.dart:25:14
When the exception was thrown, this was the stack:
#2      new ScreenUtil (package:flutter_screenutil/screen_util.dart:34:7)
#3      Base.dp (package:qniqni/common/base.dart:14:36)
#4      _StartPageState.build. (package:qniqni/page/init/start.dart:81:26)
#5      ScreenUtilInit.build.. (package:flutter_screenutil/screenutil_init.dart:35:25)
#6      OrientationBuilder._buildWithConstraints (package:flutter/src/widgets/orientation_builder.dart:52:19)
代码：
@override
Widget build(BuildContext context) {
return ScreenUtilInit(
designSize: Base.size,
builder: () {
return Scaffold(
body: SizedBox(
width: MediaQuery.of(context).size.width, //获取屏幕宽度
child: Stack(
alignment: Alignment.center,
children: [
SizedBox(
width: dp(375),
child: Image.asset("assets/start.jpg"),
),
Positioned(
right: dp(40),
top: dp(40),
child: CountDown(),
),
],
),
),
);
},
);
}

需要 WidgetsApp, CupertinoApp, 或者 MaterialApp

也就是说在main.dart文件中MyApp类的build方法中使用ScreenUtilInit，该设置就会对全局作用，不需要再到其他页面使用ScreenUtilInit对吗？？？？

是的

也就是说在main.dart文件中MyApp类的build方法中使用ScreenUtilInit，该设置就会对MaterialApp声明的路由都起作用，不需要再到其他页面使用ScreenUtilInit对吗？？？？

谢谢解答


BAU Extract IOS patch inline style into class

inline styles do not play nicely with Content Security Policies, directly injecting an element with style forces upstream services to allow unsafe-inline for styles
move the style out into a "patch" class considering this should be supported going forward

Relates to https://github.com/alphagov/accessible-autocomplete/issues/398
Contributes to https://github.com/alphagov/accessible-autocomplete/issues/398

The status element also uses this inline technique, so I'm wondering if we would need to change that too?
https://github.com/alphagov/accessible-autocomplete/blob/dbbb07603c6561f76f03e94dfd7b208f680cbed8/src/status.js#L89-L99
It's worth noting that the reason these are inline are so if CSS fails to load these messages are not shown visible on the page, however we might want to compromise on this if there's no alternative.

As consumers with content security policies we've been able to work around this issue as described in reference pull requests/ issues.
If this is something there is interest in fixing in the future I'd be happy to help out, closing for now to reduce noise.


[pickers] Console warning when migrating from the lab

Duplicates

[x] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I have warnings (in console displayed as errors) after migrating DatePickers from lab to mui-x.
Warning is Warning: forwardRef render functions accept exactly two parameters: props and ref. Did you forget to use the ref parameter?.
I modified all files in the project. No exports from mui/lab.
Maybe it will be helpfully. I use LoadingButton components from @mui-lab.

Hello there! Same issue here :) But with 2 different mui components :

I have same issue when I use
import { LoadingButton } from '@mui/lab';

          <LoadingButton
            type="submit"
            fullWidth
            size="large"
            variant="contained"
            sx={{ mt: 3, mb: 2 }}
            disabled={loading}
            loading={loading}
          >
            Sign In
          </LoadingButton>

and solved as  kkaplita mentioned in https://github.com/mui/material-ui/issues/33080#issuecomment-1150818679
change this
import { LoadingButton } from '@mui/lab

to this
import LoadingButton from '@mui/lab/LoadingButton'


1234 remove admiral adxx

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide
[x] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[ ] Link the issue in the Development Section on the right hand side.
[ ] Address all merge conflicts and resolve appropriately
[ ] Pat yourself on the back for a job well done! Much love to your accomplishment!

Hello,
when I run the devtools::check(), I got one failure and one issue:
── Failure (test-user_helpers.R:2:3): all templates are listed ─────────────────
unclass(list_all_templates()) not identical to c("ADAE", "ADCM", "ADEG", "ADEX", "ADLB", "ADPP", "ADSL", "ADVS").
Lengths differ: 2 is not 8
── Error (test-user_helpers.R:11:3): package templates can be used ─────────────
Error: No template for 'ADVS' available.
ℹ Run list_all_templates() to get a list of all available ADaM templates.
Backtrace:
▆

└─admiral::use_ad_template("advs", save_path = file, open = FALSE) at test-user_helpers.R:11:2
└─rlang::abort(err_msg)

The failure is probably coming from use_ad_template.Rd, not sure about the error. Can you please advise on both? Thanks!

Thanks Tom! I thought I was in the right folder.
I have asked @JunseKim1159 to commit and push his code (without pulling from here) as he worked at the same issues, but then we decided to merge only my branch. It should work but we will let you know if further issues will come up. Thanks again

Deleting branch as @JunseKim1159 created a new one


[website] Site responsiveness and adaptability when zooming

Steps to reproduce
Link to live example:
https://github.com/mui/material-ui/assets/110468377/378a054d-8335-44f1-bc35-58a9bd7fcea6
Current behavior
the website isn't responsive to the zooming in feature, elements on the right get hidden when zooming in which hinders the user's ability to see and notice some elements on the right side if they enter the website with a normal 100% standard zoom
Expected behavior
the site's elements should be responsive to the zooming action
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: zoom

This has been already mentioned in #41913.

Thanks for the clarification, @danilo-leal . While I appreciate the design intentions, the current zoom functionality could affect accessibility for some users when they already enter the website having the standard 100% zoom or even greater, a section of those elements won't be seen. Could we look into temporary solutions to improve usability at various zoom levels until the planned redesign? This would greatly enhance the user experience for those relying on zoom or even for a normal user that has the default 100% zoom. Thank you!

a section of those elements won't be seen

I appreciate that! But as I mentioned, being unable to see part of the customized components in the hero section, be it because of zoom level or viewport size, is expected—they're illustrative. The interactivity on them is just a bonus, so the site feels less static. Let me know if you're experiencing these problems on other parts of the site!


Fix schedule path

When schedule run come command he not found where artisan locate.
To fix it we go to project path and then run schedule. And now it more agree with doc
https://laravel.com/docs/5.8/scheduling
* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1

1th commit with home not correct if we have many cron tasks at root user

Thanks for your fix.

Version 1.0.2 just published to supermarket.


Clarify accumulate: true example

The existing squareValues example is misleading in the sense that it makes a reader believe that values is (naturally) an array of passed values. However, values in the example is actually an array of arguments arrays:
function squareValues (values) {
  console.log(values) // [ [ 1 ], [ 2 ], [ 3 ], [ 4 ] ]
  return Promise.all(values.map(val => val * val))
}

Coincidentally, multiplying arrays [ 2 ] * [ 2 ] gives 4 in Javascript, which obscures the fact that values consists of arrays rather than values. But this conversion is not going to take place in most other circumstances. For instance, if you return val + val instead of val * val in your example, the debounced promise will resolve to 11 22 33 44 instead of 1 2 4 8.
The PR makes it more obvious to infer the actual API from the example:
function squareValues (argTuples) {
  return Promise.all(argTuples.map(args => args[0] * args[0]))
}

Another options would be to use arguments destructuring:
function squareValues (argTuples) {
  return Promise.all(argTuples.map(({0: value}) => value * value))
}

but I think it's even harder to comprehend.

Ah, good catch! Agreed about the first example being clearer. Thanks!


GBIF API/links need to be updated

GBIF changed their API on their end which leaves taxon_links and the map overlay and map overlay link broken. Referencing #420 incase we can hold off fixing these until this update

GBIF data on maps was addressed in https://github.com/inaturalist/inaturalist/pull/503, taxon link just isn't going to work until they implement some kind of name-based URL scheme, so I just deleted that taxon link.


Improve perf by not firing db query when review author and review opinion author is accessed

Currently, a query is fired for each row in the submissions list table when review author and review opinion author is accessed in the template. Uses Prefetch objects.
Also, are we using Opinion on the Review feature in the apply site? The code is present but not sure it is being used. If not we can update the modified code.

A significant performance improvement for the dashboard. A busy reviewers dashboard went from 134 queries to 71 and CPU time from 5,7s to 3s.

A reviewer can give opinion on another reviewers review (Agree/Disagree). This is not displayed on the dashboard but an opinion should count as "has been reviewed by".

Great


Update AutoRest C# version to 3.0.0-beta.20230719.3

Update AutoRest C# version to 3.0.0-beta.20230719.3

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Health.Insights.ClinicalMatching

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Health.Insights.ClinicalMatching Azure.Health.Insights.CancerProfiling Azure.Analytics.Purview.Sharing

Those are all beta versions. And we've got approval from service team in #37584


fix: update lock file

relates to #96

@dalmo3  @iambumblehead
please pull branch locally and let me know if it. works

Still no luck. Same error. Invalid hook call in Dropdown.tsx. Tried with npm 7 like you suggested and yarn v1.

hmm doesnt add up .. i used same env and worked.
Steps:
git checkout fix-lockfile
Tests 1:

deleted node_modules
yarn
yarn start

Tests 2:

deleted node_modules
npm i --legacy-peer-deps
npm start

Both worked

I just discovered this PR... I haven't tried running @dalmo3's sample app on the linux machine but I'll try it and see how it goes. There's a similar error that occurs when running storybook https://github.com/storybookjs/storybook/issues/10662#issuecomment-848399964 but the error only occurs on the mac machine --storybook runs fine on the linux machine

mac
linux

node v16.0.0
node v16.2.0

npm 7.10.0
npm 7.14.0

Error: Invalid hook call
??

still no issues for me

mac

node v16.2.0

npm 7.14.0

all fine

many other people are recently affected by the same sort of problems facebook/react#13991

yup but this issue is from 2018.
Im not certain if im reproducing the issue as you guys are doing it.
can you give detailed instructions and what you are using to test the issue

so i confirmed that our bundle had a react version inside and this removes it..however your setup with npm link still has issue so ill fix this up and we do a patch release to test correctly

i also confirmed the test app is working actually
instead of using npm link

i just installed v6.0.0
npm run build on this local branch
copied the dist folder into the node_module of the test app

k @iambumblehead .. you can do a patch release
Thanks

@lwhiteley your latest branch works here after removing react-dropdown-now's node modules directory
bumble@duck react-dropdown-now-app水$ cd node_modules/react-dropdown-now/
bumble@duck react-dropdown-now水$ mv node_modules node_modulesOLD

great! :)


Connection refused on mf4.xiph.org

vlad@vlad-Aspire-E5-572G ~/s/rav1e-0.3.3 [1]> ./build.sh
--2020-06-15 08:20:37--  https://mf4.xiph.org/~ltrudeau/videos/nyan.y4m
Resolving mf4.xiph.org (mf4.xiph.org)... <IP_ADDRESS>
Connecting to mf4.xiph.org (mf4.xiph.org)|<IP_ADDRESS>|:443... failed: Connection refused.
wget and curl not found or failed!

You can comment out the line trying to download that file if you just want to build the codec and run it on other content. I'm not sure if we have a mirror of nyan.y4m right now, I'll find a place to rehost it if not.

Building rav1e did fail for me because of the same reason. Commenting out the complete nyan if block helped building rav1e. But I got
Running `target/debug/rav1e  -o enc_file.ivf -s 3 -r rec_file.y4m`
!! Cannot open input file: No such file or directory (os error 2)
Error: Generic { msg: "Cannot open input file", e: "No such file or directory (os error 2)" }
rav1e failed to run

That's not a build error. The script tries to encode nyan.y4m as a test, and it's not there.

we should consider removing the script for the time being.
On Sun, Jun 21, 2020, 21:06 Raphaël Zumer<EMAIL_ADDRESS>wrote:

That's not a build error. The script tries to encode nyan.y4m as a test,
and it's not there.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/xiph/rav1e/issues/2393#issuecomment-647168062, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB2LJGBGDWMOQIF3XNTMZTRXZK2XANCNFSM4N52J3CQ
.


Wrapping Up - Meal Section Idea

Define

Overview
Meal Types

Got it clear today:
Rename to "meals and fit"
The tabs will be:

Overview:

Today Meals
Tomorrow Meals
Meals of the week
Create shopping list

Recipes or Meals
Ingredients
Menus(later)
Running Log (if I have time or can let it for later)

Behavior

users can have different menus


ROX-12342: Add support for creating resolver instance with context

Description
Adding gen'd code for wrapping graphql objects with a passed context to allow for cleaner handling of passing contexts on to sub resolvers.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
No testing required for these changes

/test all


Who's using Async-graphql in production?

If your company is using Async-graphql in production, please let me know who are you so I can mention you in the README.

I'll start: We're using async-graphql to power the API in Vector. We have two clients connecting to it:

top, our CLI tool for observing event activity across all components.
An upcoming UI dashboard, built in Typescript, React + Urql.

I wrote a blog post about it here, although there are some updates required to that post to pick up the latest schema changes.
Things that have been particularly awesome:

The code-first approach writing. In a previous project, we used a Go GraphQL library, which required writing everything in SDL and building resolvers around it. Being able to keep everything in Rust has been awesome.
Minimal boilerplate. Being able to drop in a few annotations around methods and parameters and get a fully working GraphQL API is perfect!
Relay connections. It was trivial to add pagination support to our queries, which has proven very useful when dealing with very large data sets. I love how this interface was designed - it was easy to come up with a cursor format that works well for our records, and the helpers async-graphql offers make it simple to roll out to everywhere we need pagination support.
Websockets + subscriptions. These are the backbone of exposing real-time metrics (and after https://github.com/timberio/vector/pull/6363, events). It's so nice being able to return an impl Stream<Item = T> and it just work.
Above all, the incredible support we've received from @sunli829 personally when we ran into issues, or had feature requests. I don't think we've ever seen an issue go more than a few hours without being resolved. A million thanks 👍

I'm very excited by this project and where it'll go next. Thanks for making our lives (and my life in particular) easier!

While not on production yet, here is a simplified version of a future production app slimmed down for a meetup.
The goal was to make a presentation for Rust Lang Los Angeles which uses SQLx, actix and async-graphql:
https://github.com/camsjams/rust-actix-graphql-sqlx-postgresql
This showcases

Federation with async-graphql,
Federation using Actix
Database usage via PostGreSQL and SQLx
Seamless UUID juggling between GraphQL and PostGreSQL

Thanks @sunli829 awesome library!

Not in production yet, but close. A very simple and small service talking to a redis cluster is in the works. A great library, thank you!

Still a work in progress, I'm working on a website to catalogue and describe scuba diving sites.
The stack is as follows:
Backend:

Actix Web
Tokio Postgres
Async-graphql

Frontend:

React
Apollo

We're using it at Kairos Sports tech, using it in combination with graphql mesh to move some parts of an existing ruby on rails grahpql API. Not in production yet but will be in the next few weeks

At AxieInfinity, we are using Async-graphql on production sites.
Our GraphQL back-end serves multiple query sources:

Axie Marketplace
Game servers
Community dev sites

The story of mine back into the middle of 2020, while we were migrating our GraphQL to Rust. There are only 2 options at the time, and I decided to move with async-graphql, that can work well with Search Engine async libs (Elasticsearch) and can integrate with Apollo Federation gateway.
Until now, we're still following Async-graphql development progress, and just update to the latest version recently.
Thank you for the your effort and time @sunli829 .

We use it at Nando's for our capacity management services, both client and cluster side, clients can request restaurant capacity times which is a GQL call.
In cluster, the capacity tracker listens to a confirmed orders subscription, does some validation, then calls the record order mutation in another service, which will then adjust the capacity accordingly :)

Sweet, I love my chicken with a side of GraphQL 😄 Love these kind of infrastructure insights -- thanks for sharing!

(P.S @nandos -- If there's a GraphQL mutation for requestBlackCard, I'll happily test that for you 😉 )

(P.S @nandos -- If there's a GraphQL mutation for requestBlackCard, I'll happily test that for you 😉 )

🤫

Haha, that's great @nandos... now if you could just fwd over the endpoint URL and create an Okta login profile for me, I think our work here is done 😄

We are using it at Prima.it and we have a couple of microservices actually running in production

We use it in production at Voxjar to power api.voxjar.com.

We're using async-graphql and async-graphgate in production at Zenly.
It's powering a simple view of all the available data across the services, we are using it in production for months 🙂
No issue so far, +200k/s with a p999 under 50 ms, thank you @sunli829 😉

It's not a company, but wanted to highlight that I use it in two projects that are getting started.

entity-rs via entity-async-graphql integration
vimwiki-rs via vimwiki-server, a binary that serves vimwiki document elements over graphql (graphql query/mutation objects and graphql data structures)

I just released version 0.1.0 of the vimwiki crates and entity crates are slowly improving, including providing generated filters to use when querying data like this:

#[gql_ent]
pub struct Paragraph {
    /// The segment of the document this paragraph covers
    #[ent(field(graphql(filter_untyped)))]
    region: Region,

    /// The content within the paragraph as individual elements
    #[ent(edge(policy = "deep", wrap, graphql(filter_untyped)))]
    contents: Vec<InlineElement>,

    /// The content within the paragraph as it would be read by humans
    /// without frills
    #[ent(field(computed = "self.to_string()"))]
    text: String,

    /// The page containing this paragraph
    #[ent(edge)]
    page: Page,

    /// The parent element containing this paragraph
    #[ent(edge(policy = "shallow", wrap, graphql(filter_untyped)))]
    parent: Option<Element>,
}

I'm using async-graphql for my side project (will be come production soon).
Switch from Flask/Python. So far so good.

Not a company, but I made an open-source wrapper around async-graphql called Diana (no relation to the Julia one!) that connects a serverless queries/mutations system with a serverful subscriptions system. Couldn't have done it without this, it's a fantastic project you've got here!

I use it at Brevz! it's an incredible project!

We use it at Nando's for our capacity management services, both client and cluster side, clients can request restaurant capacity times which is a GQL call.
In cluster, the capacity tracker listens to a confirmed orders subscription, does some validation, then calls the record order mutation in another service, which will then adjust the capacity accordingly :)

oh nice my fav chicken restaurant uses rust. Now I have even more respect for you guys.

We're now running async-graphql in production @ thorndyke hosted off an AWS Lambda function. A ground up rewrite from a previous TypeScript implementation with significantly better performance and developer experience.

Although not running a company, I have been using async-graphql on my hobby website (Github), a forum on lateral thinking puzzles. The website has been running stably without any crash since a year ago when I migrated the backend to rust. Subscription is really a thing to me and your project is the first to get it implemented in rust. Thank you for your work!

We're using async-graphql at Grafbase (https://grafbase.com). Grafbase is a data platform for developers that enables you to deploy globally fast apps in seconds.

At futuREproof, we use async-graphql to extend Hasura's graphql-engine with custom functionality. This is in production and works great!
In addition, we use async-graphql extensively to mock other graphQL api's in the tests of the above graphQL extensions (but the test code itself is obviously not 'in production').

Most of the back-end services in our company Biznet Gio Nusantara uses Async-GraphQL.

Not a company, nor in production, probably not even a good use of this library, but this is a Rust full-stack study which involves async-graphql: https://github.com/rongcuid/gqlforum-rs
I won't say this is the best way to use the library, as I was exploring in the process.

Disable stale bot here.

Disable stale bot here.

This robot is not smart enough.😂

https://www.plan3.aero Has a large (around 80k lines with everything included like tests and more) GraphQL API that started as a Juniper project but was fully migrated to async-graphql around a year ago

https://github.com/contentstech-com is using async-graphql in production


ap-5120: Rake task to generate new users script

What
Link to story
This pr (for discussion) creates a rake task to generate the new apply users.
To run you would:-

Shell onto the production pod
Run rake portal:new_users['pipe|separated|list|of|names']
Exit the pod
Run kubectl cp -n laa-apply-for-legalaid-production {pod name}:/usr/src/app/tmp/output.ldif . to copy the generated file to your current directory

I am not sure whether or not this would overall be an improvement over the current process but it would:

Mean the standalone user script was tracked in our codebase (and linted etc.)
Mean we can use the PDA url and auth_key directly from the rails configuration rather than having to pass them into the script.
(potentially)We could extend the script to check the apply database to see if they already exist before adding them to the output ldif file.

Do people have any thoughts?
Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
The standards in the Git Workflow document on Confluence should be followed
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

@jsugarman I have added some tests as requested would you please be able to re-review? Thanks! 🙁

looking good. double-approved


Typo in README.md

In the current README under Weather String Placeholders - Current Weather Placeholders, it seems like date1 and date2 are flipped: date1 may display single digit day while date2 zero-prepends single digit days. The observed behavior is consistent with the naming of year1, year2 and month1, month2, so I think it might have been a typo.
Obsidian: v1.6.5
Plugin: v1.8.0

Sorry for not getting back to you sooner. I was busy completing 2 new VSCode extensions but I am free to work on this one again. I'm sure you are correct and that is just a typo. I will correct that as soon as I fix a minor bug that another user found. Should be updated soon.
Thanks for bringing this to my attention, William.

I just want to inform everyone that this plugin in being discontinued. Open Weather has discontinued the API 2.5 on which this plugin is based. I have however created a new plugin using the Visual Crossing Weather API and it follows the same basic approach to representing the weather as this plugin did so it should be relatively easy to move over to the new plugin. While it is still in development it is almost 100% functional. The documentation however is almost non existent but the list of available macros is complete and is in a nicely formatted table for better viewing. I hope to have it published soon as it is very close to being completed. If you want to try it before it is released you can find it on Github here.
Thank you, William McKeever


Example fails to build

This seems like a super cool project, unfortunately, the example in the repo fails to build on my machine, with a missing cpp file:
    Updating crates.io index
   Compiling unicode-xid v0.1.0
   Compiling memchr v2.5.0
   Compiling regex-syntax v0.6.26
   Compiling cc v1.0.73
   Compiling fnv v1.0.7
   Compiling proc-macro2 v0.3.8
   Compiling quote v0.5.2
   Compiling syn v0.13.11
   Compiling aho-corasick v0.7.18
   Compiling regex v1.5.6
   Compiling verilator v0.1.6 (/tmp/verilated-rs/verilator)
   Compiling verilated v0.1.2 (/tmp/verilated-rs/verilated)
   Compiling example v0.0.0 (/tmp/verilated-rs/example)
   Compiling verilated-module v0.1.1 (/tmp/verilated-rs/verilated-module)
The following warnings were emitted during compilation:

warning: cc1plus: fatal error: /tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Slow.cpp: No such file or directory
warning: compilation terminated.

error: failed to run custom build command for `example v0.0.0 (/tmp/verilated-rs/example)`

Caused by:
  process didn't exit successfully: `/tmp/verilated-rs/target/debug/build/example-47864a376f1eeb3a/build-script-build` (exit status: 1)
  --- stdout
  6 items
  cargo:rerun-if-changed=src/main.rs
  running: "/usr/bin/verilator_bin" "--getenv" "VERILATOR_ROOT"
  verilator root: "/usr/share/verilator"
  running: "/usr/bin/verilator_bin" "--cc" "-Mdir" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out" "--top-module" "top" "--coverage" "--trace" "+1364-2001ext+v" "rtl/counter.v" "+1364-2001ext+v" "rtl/top.v" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/top.cpp"
  OPT_LEVEL = Some("0")
  CXX_x86_64-unknown-linux-gnu = None
  CXX_x86_64_unknown_linux_gnu = None
  HOST_CXX = None
  CXX = None
  CXXFLAGS_x86_64-unknown-linux-gnu = None
  CXXFLAGS_x86_64_unknown_linux_gnu = None
  HOST_CXXFLAGS = None
  CXXFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("true")
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
  running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/usr/share/verilator/include" "-I" "/usr/share/verilator/include/vltstd" "-I" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out" "-Wall" "-Wextra" "-std=gnu++17" "-faligned-new" "-Wno-bool-operation" "-Wno-sign-compare" "-Wno-uninitialized" "-Wno-unused-but-set-variable" "-Wno-unused-parameter" "-Wno-unused-variable" "-Wno-shadow" "-DVL_PRINTF=printf" "-DVM_COVERAGE=1" "-DVM_TRACE=1" "-o" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop.o" "-c" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop.cpp"
  exit status: 0
  running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/usr/share/verilator/include" "-I" "/usr/share/verilator/include/vltstd" "-I" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out" "-Wall" "-Wextra" "-std=gnu++17" "-faligned-new" "-Wno-bool-operation" "-Wno-sign-compare" "-Wno-uninitialized" "-Wno-unused-but-set-variable" "-Wno-unused-parameter" "-Wno-unused-variable" "-Wno-shadow" "-DVL_PRINTF=printf" "-DVM_COVERAGE=1" "-DVM_TRACE=1" "-o" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Syms.o" "-c" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Syms.cpp"
  exit status: 0
  running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/usr/share/verilator/include" "-I" "/usr/share/verilator/include/vltstd" "-I" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out" "-Wall" "-Wextra" "-std=gnu++17" "-faligned-new" "-Wno-bool-operation" "-Wno-sign-compare" "-Wno-uninitialized" "-Wno-unused-but-set-variable" "-Wno-unused-parameter" "-Wno-unused-variable" "-Wno-shadow" "-DVL_PRINTF=printf" "-DVM_COVERAGE=1" "-DVM_TRACE=1" "-o" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Slow.o" "-c" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Slow.cpp"
  cargo:warning=cc1plus: fatal error: /tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Slow.cpp: No such file or directory
  cargo:warning=compilation terminated.
  exit status: 1

  --- stderr

  error occurred: Command "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-m64" "-I" "/usr/share/verilator/include" "-I" "/usr/share/verilator/include/vltstd" "-I" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out" "-Wall" "-Wextra" "-std=gnu++17" "-faligned-new" "-Wno-bool-operation" "-Wno-sign-compare" "-Wno-uninitialized" "-Wno-unused-but-set-variable" "-Wno-unused-parameter" "-Wno-unused-variable" "-Wno-shadow" "-DVL_PRINTF=printf" "-DVM_COVERAGE=1" "-DVM_TRACE=1" "-o" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Slow.o" "-c" "/tmp/verilated-rs/target/debug/build/example-04a0d54f79755afe/out/Vtop__Slow.cpp" with args "c++" did not execute successfully (status code exit status: 1).

warning: build failed, waiting for other jobs to finish...
error: build failed

Trying to build with rust 1.59 and verilator version 4.222

Thanks for the report.

It looks like verilator changed the default naming scheme for the generated C++ source somewhere between 4.108 and 4.222.

I just repulled again (and switched to main).  At efab3b3275bc49e2204053192a4306463da25dec cargo build fails with
  running: "c++" "-O0" "-ffunction-sections" "-fdata-sections" "-fPIC" "-g" "-fno-omit-frame-pointer" "-I" "/usr/share/verilator/include" "-I" "/usr/share/verilator/include/vltstd" "-Wall" "-Wextra" "-std=gnu++17" "-faligned-new" "-Wno-bool-operation" "-Wno-sign-compare" "-Wno-uninitialized" "-Wno-unused-but-set-variable" "-Wno-unused-parameter" "-Wno-unused-variable" "-Wno-shadow" "-DVERILATOR_VERSION_MAJOR=4" "-DVERILATOR_VERSION_MINOR=226" "-o" "/home/tommy/projects/verilated-rs/target/debug/build/verilated-2b7a9d3a2d6377b6/out/src/verilatedvcdc_shim.o" "-c" "src/verilatedvcdc_shim.cpp"
  cargo:warning=src/verilatedvcdc_shim.cpp: In function ‘void verilatedvcdc_rollover_mb(VerilatedVcdC*, size_t)’:
  cargo:warning=src/verilatedvcdc_shim.cpp:47:10: error: ‘class VerilatedVcdC’ has no member named ‘rolloverMB’; did you mean ‘rolloverSize’?
  cargo:warning=   47 |     vcd->rolloverMB(rolloverMB);
  cargo:warning=      |          ^~~~~~~~~~
  cargo:warning=      |          rolloverSize

on Asahi Linux (fully up-to-date).
On up-to-date Ubuntu/RISC-V it fails with
...
   Compiling memchr v2.5.0
/home/tommy/.rustup.riscv64-linux/toolchains/stable-riscv64gc-unknown-linux-gnu/bin/../lib/librustc_driver-ac972a4e10c98556.so(+0xc3d810)[0x3f93eb4810]
linux-vdso.so.1(__vdso_rt_sigreturn+0x0)[0x3f9a94a800]
...
/home/tommy/.rustup.riscv64-linux/toolchains/stable-riscv64gc-unknown-linux-gnu/bin/../lib/libstd-f41102d4d21d2c30.so(rust_metadata_std_ac92b06979af539e+0xa0542)[0x3f7e30c542]
/lib/riscv64-linux-gnu/libc.so.6(+0x6a450)[0x3f7e197450]
error: could not compile `unicode-xid`

Caused by:
  process didn't exit successfully: `rustc --crate-name unicode_xid /home/tommy/.cargo.riscv64-linux/registry/src/github.com-1ecc6299db9ec823/unicode-xid-0.1.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -idory ea,link -C embed-bitcode=no -C debuginfo=2 --cfg 'feature="default"' -C metadata=86b26df15dd8bbd4 -C extra-filename=-86b26df15dd8bbd4 --out-dir /home/tommy/projects/verilated-rs/target/debug/deps -L dependency=/home/tommy/projects/verilated-rs/target/debug/deps --cap-lints allow` (signal: 1 IEG:iv11, SIGSEGV: invalid memory reference)
warning: build failed, waiting for other jobs to finish...
error: could not compile `memchr`

In all cases Rust is fully updated to version 1.64
Maybe it would make sense to include verilator as a submodule so we are building a known-good version?

FWIW, current version (version 0.1.6) builds and runs perfectly for me with
Rust 1.64 on
Ubuntu 22.10/{Arm64,AMD64,RISC-V}
(However clippy has something to say).
Also FWIW, it still fails to build on Asahi-Linux/M1, but I'm not sure that's the fault of verilated-rs.
I think we can close?

Executing verilator with --lib-create and using make -f V{top_name}.mk to build instead of call cc manually may be the better solution.
And verilator renamed rolloverMB to rolloverSize (verilator/verilator#3570).

Has this crate been abandoned?  There are four pull requests with not even a comment

@tommythorn Has this crate been abandoned? There are four pull requests with not even a comment

Perhaps, I'm looking into maybe writing a more general set of bindings, potentially also handling cxxrtl. I did similar work for Calyx (think LLVM for hardware) by writing bindings to Calyx's hand rolled simulator.


Update makefiles to fix TARGET support for crosscompiling

Have you tested this to cross compile?  And if so, do you have instructions on how to setup the cross compiling? And which architectures have you cross-compiled (Windows? Arm?)

Yes, I have an additional change that I still need to cleanup which allowed me to build the server side for the raspberry pi 2+ (armhf). We used to also support building for mipsel a long time ago. I'll add instructions once I send that for review, the main idea is to pass TARGET=arm-linux-gnueabihf and have a properly setup cross compiler with at least zlib and freetype.

That is very cool.  I have a pi3 and I was doing some cross compiling (for another unrelated project) this past week and it got me thinking about sagetv and compiling for pi, so great timing :)  If we can get this working on a PI, then I can likely update the Travis scripts to create/deploy ARM builds as well that people can test out.

This is really interesting. I too have a few RPi's that could be put to use.

I have several Pis as well so I would be happy to test things out.  I have everything from Pi3s to Pi Zero Ws to the older original Pi and Pi2.  There is also the Rock64 which is very similar to the Pi3 but a bit faster at 1.4GHz vs 1.2 GHz and supports 4K@60fps, has USB 3.0 ports, IR and a Gb ethernet port.  http://www.dailytech.com/Comparison+Rock64+vs+Raspberry+Pi+3/article42443.htm

Building for embedded/slim hardware would really be great if/when sage gets modularized a bit more, so not only can it be built, but maybe slimmed down as necessary to perform specific tasks suited to the limited hardware.

I had to do a few steps manually and haven't had time to finish cleaning up the build scripts to work with cross compiling.
If you want to try the one I had built it's at https://mu3d.com/sagetv/sagetv-server_rpi2.tar.gz, it's been running fine since the weekend.
The main setup steps are installing the lite version of the latest raspbian, tweaking the usb power settings (using a good PS), adding a usb hard drive and tuner, installing java then extracting the tar.gz to /opt/sagetv/server and running startsage.


Does opencvsharp4 VideoCapture class can read a rtsp stream on a centos 7 system?

Summary of your issue
I am using opencvsharp4\<IP_ADDRESS>90326 and opencvsharp4.runtime.centos7-x64\<IP_ADDRESS>90129 in my a .netcore(Microsoft.NETCore.App2.1) console application.when I deploy the project to Centos 7,the app is run ,but the  VideoCapture can not Open a rtsp stream.But there is no exception throw by the code.
Environment
Centos 7 X64
What did you do when you faced the problem?
Example code:
 var capture = new VideoCapture(this.ImageSource);
            int sleepTime = (int)Math.Round(1000 / capture.Fps);
            // Frame image buffer
            using (Mat image = new Mat())
            {
                capture.Open(this.ImageSource);
                Console.WriteLine("capture.Mode is "+capture.Mode + ", DateTime.Now is " + DateTime.Now);
                Console.WriteLine("capture.CaptureType is " + capture.CaptureType + ", DateTime.Now is " + DateTime.Now);
                Console.WriteLine("capture.Fps is " + capture.Fps + ", DateTime.Now is " + DateTime.Now);
                Console.WriteLine("capture.GStreamerQueueLength is " + capture.GStreamerQueueLength + ", DateTime.Now is " + DateTime.Now);
                while (true)
                {
                    if (! capture.IsOpened())
                        {
                        Console.WriteLine(this.ImageSource + " read image not opened , DateTime.Now is " + DateTime.Now);
                        break;
                    }
                    Console.WriteLine(this.ImageSource + " read image , DateTime.Now is " + DateTime.Now);
                    capture.Read(image); // same as cvQueryFrame
                    if (image.Empty())
                    {
                        Console.WriteLine(this.Id + " read image is Empty , DateTime.Now is " + DateTime.Now);
                        break;
                    }

                    this.OrginalImage = image;
                    var v = this.CurrentValue;
                    Console.WriteLine(this.Id + " value is " + v + " DateTime.Now is " + DateTime.Now);
                }
                Console.WriteLine(this.ImageSource + " read image break , DateTime.Now is " + DateTime.Now);

            }

Output:
capture.Mode is 0, DateTime.Now is 19-4-9 下午5:51:05
capture.CaptureType is File, DateTime.Now is 19-4-9 下午5:51:05
capture.Fps is 0, DateTime.Now is 19-4-9 下午5:51:05
capture.GStreamerQueueLength is 0, DateTime.Now is 19-4-9 下午5:51:05
rtsp://admin:123456@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1 read image not opened , DateTime.Now is 19-4-9 下午5:51:05
rtsp://admin:123456@<IP_ADDRESS>:554/cam/realmonitor?channel=1&subtype=1 read image break , DateTime.Now is 19-4-9 下午5:51:05
What did you intend to be?
Why I can't get the image by "capture.Read(image); "?the image object is Empty.

You need to invoke capture.Grab(); first before reading an image.


Improve readme formatting (markdown)

Move README file to markdown format

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


Container for bedtools and samtools ("bed_samtools") is missing

There is a conda environment that contains bedtools and samtools, which is used by the filter_true_dcs_alignments process. No matching container exists though, causing a crash when the -profile singularity --strict_dcs options are used together.

Ah good find.
Here you go:
nanozoo/bed_samtools:2.30.0--cc7d1b9
I used the same versions for samtools and bedtools as in https://github.com/hoelzer/clean/blob/master/envs/bed_samtools.yaml
And I did not build it in the rki-mf1 account bc all the other images we are using in CLEAN are also from the nanozoo organisation. To keep that consistant.


Document the roll and give credit back to the dice roll lib and the cinch bot in the readme

Documented and gave credit to cinch with https://github.com/bbourqu/cinch-yadr/pull/3

https://github.com/bbourqu/cinch-yadr/commit/9f18a35656ab0f60913b2186723e01e7bd37cb7b added all the rest


Initial Implementation for the new WASM based instruction set

Thanks a lot for working on this!
From a methodological point of view (and to ease the work of the reviewer) it would be great if you could focus on a single test file, have it validate, then we can merge the PR and move on to more test. Do you think it's a viable approach?

Yes, the initial idea was to first have all the basic arithmetic operations only (more or less everything tested in https://github.com/xtensor-stack/xsimd/blob/master/test/test_batch.cpp), and then find a way to reuse the already existing tests in WASM.

Thanks a lot for working on this!

Thanks for having a look. Yeah this pr branches out from #943 and I think so Thorsten is trying to port the test files and run them all considering wasm. I guess once that is done we could merge that PR and rebase this one top of that.

@anutosh491 can you rebase on latest master branch? Wasm support for CI has been merged in.

Sure I'll do it !

@serge-sans-paille Ahh I think I made a bad commit somewhere and also the commit history looks very messy here. I've pushed my changes on top of current master on a seperate branch (#952). Should make reviewing and merging more easier.


Add the following to the "Other multimodal data formats" section

OJP: An EU standard that exchanges information about transport services and provide information for longer journeys (https://www.transmodel-cen.eu/ojp-standard/)
RDEX+: A standard that facilitates data exchange between different carpooling agencies (https://rdex.fabmob.io/)
CDS-M: Established agreement on the use of different standards/specifications (https://cds-m.com/)
CDS: Helps cities express curb regulations and policies (https://github.com/openmobilityfoundation/curb-data-specification)
OCPI: Helps with connections between eMobility Service Providers and Charge Point Operators (https://evroaming.org/ocpi-background/)
Open Trip Model: Helps exchange real-time logistic trip data. Helpful for shipping and carrying (https://www.opentripmodel.org/page/about)
TransXChange: A UK Department of Transportation standard that improves the exchange of bus schedules and related data (https://www.gov.uk/government/collections/transxchange)
Travel Model Two: Expansion of the work done of Travel Model One. Expanded to use more California state data rather than Bay-Area specific data. Uses a model to project weekday travel to improve planning (http://bayareametro.github.io/travel-model-two/transit-ccr/)
Transitous: Focuses on public transit user experience. (https://public-transport.github.io/transitous/)
GTFS-Diff: A standard for measuring differences between GTFS files (https://github.com/MobilityData/gtfs_diff)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 16 committers have signed the CLA.:white_check_mark: isabelle-dr:white_check_mark: emmambd:white_check_mark: dancesWithCycles:white_check_mark: 1Maxnet1:white_check_mark: mil:white_check_mark: tbuckl:white_check_mark: carlfredl:x: mesozoic-drones:x: gabrielvazdemelo:x: Joaobazzo:x: mem48:x: said026:x: rafapereirabr:x: Simha-Kalimipalli:x: fbarbe00:x: AdrianaCericYou have signed the CLA already but the status is still pending? Let us recheck it.


[TW#17195] AWS IoT MQTT continuously disconnects

I have my own application, which keeps on disconnecting.  (It used to operate much longer without disconnection before -- not aware since which update)
So, I tested with the AWS IoT subscribe_publish example from the esp-idf git repo.  And it still behaves similarly.
But when it disconnects, there is no way of knowing what caused it.  Could it be the WiFi / Router problem? Or is it the firmware?
And also, at launch, it the handshake failes once or twice before successfully connecting.  (Does not take too long to establish connection though).
Please help!  Or, if anyone is experiencing a similar problem, please comment.

@seopyoon
pl check https://github.com/espressif/esp-idf/issues/1695
this suggestion form negativekelvin had worked for me.

Closing due to lack of update. Hopefully the linked issue solved the problem.


Feature Request: Implement the option to expire inactive sessions and to revoke a session on password changes

Currently, there is no way to

expire inactive sessions
revoke a session on password changes

As per the documentation at: https://github.com/ParsePlatform/parse-server/wiki/Compatibility-with-Hosted-Parse#session-features both of these features are available in parse.com.
Is the parse team planning to push these changes into parse server? It will be greatly appreciated if the parse team can open source this functionality as it is tried and tested.
@gfosco, @flovilmart, @drew-gross - thoughts?
Can this issue be tagged with a discussion label by the people who have write access to this repo?

Not sure we'd wanna to that for security reasons (the ability to hijack any user account that is not validated after a delay). But that's my opinion.

@flovilmart
I can take a shot at updating the documentation...
As the documentation that needs to be updated is in the project WiKi and I can't submit a pull request on the wiki...any idea, how I can update it?

uhh right...
can you fork the wiki?

As per https://help.github.com/articles/about-github-wikis/
By default, only collaborators on your repository can make changes to wikis, but you can configure this to be enabled for all users on public repositories.

I'll check what I can do to open it or update the docs then.

Docs are updated


When disable a mat-button, the button is hided and not disabled.

Bug:
When disabling a button, the button is hide and not just disabled.
What is the expected behavior?
When disabling a button, the button is disabled and not hided
What is the current behavior?
When disabling a button, the button is hide and not just disabled.
What are the steps to reproduce?
<button mat-button  [disabled]="true">

What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/core": "^5.0.3"
"@angular/material": "5.0.0-rc.2"
"typescript": "~2.4.2"
Is there anything else we should know?

Is working with "@angular/core": "^5.1.0"

We haven't been able to reproduce this issue. Feel free to open a new issue if you are able to provide a reproduction via Plunker.

I've just experienced this issue.


Refactor PostgreSQLScalarFunctionsIT when test-db-builder Table#truncate() is implemented

When https://github.com/exasol/test-db-builder-java/issues/67 is done we can remove truncateTable(String) from PostgreSQLScalarFunctionsIT

outdated