Whenever gem doesn't run on production

I have whenever installed on my Rails 4.2.4 application and want to run this command:
rake punching_bag:combine[14,3,2] for punching_bag gem.
punching_bag gem is a hit tracker & this command combines all posts hits for better performance.
My schedule.rb looks like this:
every 1.day, :at => '3:30 am' do
  rake "punching_bag:combine[2,3,2]"
end

When I run crontab -e in my server Ubuntu 12, I can see the cron job:
30 3 * * * /bin/bash -l -c 'cd /home/productiondeploy/mydomain/releases/201611107983652 && RAILS_ENV=production bundle exec rake punching_bag:combine --silent'
But I can see that the command is not running and posts hits are Not combined. Is it something I do wrong here and how to fix it?
Thanks in advanced!

Do you use RVM or rbenv or similar?

This is what I use:
Rails: 4.2.4
Ruby: 2.3.1
RBENV
Ubuntu 12

Can you run the task from the command line?
cd /home/productiondeploy/mydomain/releases/201611107983652 && RAILS_ENV=production bundle exec rake punching_bag:combine --silent

Also, are you using the same user for deployments and to run the app?

I know it's a couple of months ago and this might be resolved but I see a lot of issues here that people's cronjobs are not running (#655, #665, #628). Mine were not running either. If you don't specify the error output the errors will be sent by mail to the user who created the cronjob. So on your server type mailx. Enter to read unread mail. Here you will probably find your problem.
In my case the error was
Your Ruby version is 1.9.3, but your Gemfile specified 2.3.3
and
Undefined local variable or method 'git_source' for Gemfile
I use Capistrano for deployment with a dedicated user deploy and rbenv for installing Ruby. When the cronjob is run all the environment variables necessary for rbenv are missing. bundle exec rake uses the system Bundler. To solve this I changed the whenever rake jobtype via
# top of schedule.rb
job_type :rake, "cd :path && :environment_variable=:environment bin/rake :task --silent :output"

This uses the rake binstub generated by Rails. Of course this works only for Rails projects. For non-rails projects you should use the absolute path to bundle/rake/rails.

I know it's a couple of months ago and this might be resolved but I see a lot of issues here that people's cronjobs are not running (#655, #665, #628). Mine were not running either. If you don't specify the error output the errors will be sent by mail to the user who created the cronjob. So on your server type mailx. Enter to read unread mail. Here you will probably find your problem.
In my case the error was
Your Ruby version is 1.9.3, but your Gemfile specified 2.3.3
and
Undefined local variable or method 'git_source' for Gemfile
I use Capistrano for deployment with a dedicated user deploy and rbenv for installing Ruby. When the cronjob is run all the environment variables necessary for rbenv are missing. bundle exec rake uses the system Bundler. To solve this I changed the whenever rake jobtype via
# top of schedule.rb
load_rbenv = 'export PATH="$HOME/.rbenv/bin:$PATH" ; eval "$(rbenv init -)";'
job_type :rake, "#{load_rbenv} cd :path && :environment_variable=:environment bundle exec rake :task --silent :output"

as seen here.

@haffla After chasing my own tail for half a day, I stumbled across your suggestion and it worked like a charm, thanks!
For future generations:
the output of
crontab -l

on the server should look something like this:
PATH=/var/www/your-app-here/shared/bundle/ruby/2.6.0/bin:/home/ubuntu/.rbenv/versions/2.6.6/bin:/home/ubuntu/.rbenv/libexec:/home/ubuntu/.rbenv/plugins/ruby-build/bin:/home/ubuntu/.rbenv/plugins/rbenv-vars/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

* * * * * /bin/bash -l -c 'export PATH="$HOME/.rbenv/bin:$PATH"; eval "$(rbenv init -)"; cd /var/www/your-app-here/releases/20210323224359 && RAILS_ENV=production bundle exec rake your_task:here --silent >> log/whenever.log 2>&1'

I couldn't for the life of me figure out why rbenv-vars weren't loading and explicitly adding the export path and rbenv init to the crontab worked!


Feat/193 masonry error

close #193

The cause of error

Raise error when Masonry has no child element.
I render masonry when there are no items
I changed masonry will not be rendered when items.length === 0


ERROR: ResolutionImpossible

pip install -r requirements.txt
Collecting tensorflow==1.15.4
Using cached tensorflow-1.15.4-cp37-cp37m-macosx_10_9_x86_64.whl (123.3 MB)
Collecting tensorflowjs==2.7.0
Using cached tensorflowjs-2.7.0-py3-none-any.whl (62 kB)
INFO: pip is looking at multiple versions of tensorflow to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install -r requirements.txt (line 2) and tensorflow==1.15.4 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested tensorflow==1.15.4
tensorflowjs 2.7.0 depends on tensorflow<3 and >=2.1.0
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies

What OS and pip/python version are you running? For me with Windows 10 and Python 3.7/pip 20.1.1 it shows an error but installs anyway (which is fine to ignore that error). A workaround could be installing first the tensorflowjs==2.7.0 requirement, then in a separate pip install tensorflow==1.15.4

MacOS Catalina, Python 3.7, pip-20.3.1
That workaround was successful 🎉
I feel like I may have done that the first time, but forgot about it 😂


[rc] Unpin aws-sdk-cpp

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Closing in preference of #245.


add signal/event systems

Short Description:
Implement signal system.

I'm concerned that a dispatcher + event system will be very incompatible with the longer term approach of using behavior trees.
It might be compatible, but I'm not sure how we intend to use this / what we intend to dispatch.
I'll talk to @namlehong offline about this and see if I can understand better.

From @namlehong:
For example, a sign_in_signal

people can add ton of receiver like
- check inventory
- do transfer old pokemons

then
pre_catch_pokemon:
- check pokeball

post_catch_pokemon:
- do transfer or not
- update pokeball count

One of the typical problems with hooks is that you end up having to have a bunch of logic to handle people who want to order hooks, or hooks that need to dispatch other things and thus call more hooks which call more hooks.

I'm worried that this event system will actually cause more problems than it solves.

It has been mentioned in slack that the intention for the event system is for things like the logger. Which would provide plugin level support for something like the lcd display and the web ui.
I think that is a reasonable decision, but it becomes very important that we do not trigger bot behavior with events. For example, we should not have events like in the above snippet where we send an event on pre_catch that checks the pokemon inventory and transfers old pokemon. This type of logic should be handled by the behavior tree.

this isn't completed but will be added in the future


Add get_clebsch_hf_factors_iso

Mix of all 3 polarisations. Should be same as get_decay_factors() but divided by three (check the sum is correct)

Fixed in #167.


STORM-2194: Report error and die, not report error or die

This appears to have just ported an existing bug from executor.clj -- this is what I believe the expected behaviour is/was.

-1.
InterruptedException we often use to indicate that the process is shutting down, and we want to not blow up when we see them.  Perhaps what we want to do is to better document it.

I've left some follow up comments in 1767.


[5.6] Allow eager-loading mixed relationships of polymorphic collection

I've had this macro kicking around for awhile since the framework doesn't offer a way to avoid N+1 queries from morphTo() nested relationships. This adds Illuminate\Database\Eloquent\Collection@loadMorph() to allow nested eager loading by naming the unique relationship(s) for each class name.
Issue reported:

https://github.com/laravel/framework/issues/15248

External Laravel community:

https://github.com/laracasts/Lets-Build-a-Forum-in-Laravel/issues/4

In response to https://laracasts.com/series/lets-build-a-forum-with-laravel/episodes/26

http://derekmd.com/2017/06/eager-loading-laravel-polymorphic-relations/

My long-winded write-up about what this is solving.

Example Use Case
class ActivityFeed
{
    public function parentable()
    {
        // e.g., hydrate a Collection of Event, Photo, or Post instances.
        return $this->morphTo();
    }
}

$activities = ActivityFeed::with('parentable')
    ->get()
    ->loadMorph('parentable', [ // could instead be named loadMixed()? loadMorphed()?
        Event::class => 'calendar',
        Photo::class => 'tags',
        Post::class => ['author', 'commentsCount'],
    ]);

In an ideal world...
...this would be supported:
ActivityFeed::with([
    'parentable' => [
        Event::class => 'calendar',
        Photo::class => 'tags',
        Post::class => ['author', 'commentsCount'],
    ],
    'user:id,name',
    'zonda' => function ($query) {
        $query->ofSomeScope();
    },
])->get();

I really wanted to work this into the existing eager-load infrastructure:

Illuminate\Database\Eloquent\Builder@with()
Illuminate\Database\Eloquent\Collection@load()
Illuminate\Database\Eloquent\Model@with (array object property)

However this is going to require a significant rewrite of the Eloquent internals that store an associative array of query constraint Closures.
Pagination
For better developer experience in controllers, an explicit AbstractPaginator@loadMorph() proxy is added to return the paginator. This allows it to be passed into the view or returned by an API response.
Then controllers don't have to awkwardly do:
$tags = Tag::with('taggable')->latest()->paginate();

$tags->getCollection()->loadMorph('taggable', [
    Post::class => 'category', 'comments',
    Video::class => 'likes',
]);

return view('tags.index')->with('tags', $tags);

but:
$tags = Tag::with('taggable')->latest()->paginate()->loadMorph('taggable', [
    Post::class => ['category', 'comments'],
    Video::class => 'likes',
]);

return view('tags.index')->with('tags', $tags);

We don't support eager loading morphTo relationships already?

This is allowing eager-loading from mixed classes that have relationships uncommon between each other. From the above example:
$activities = ActivityFeed::with([
    'parentable.calendar',      // Event@calendar() hasOne
    'parentable.tags',          // Photo@tags() hasMany, relation doesn't exist in Event class
    'parentable.author',        // Post@author() hasOne
    'parentable.commentsCount', // Post@commentsCount hasOne
])
->get();

Illuminate\Database\Eloquent\RelationNotFoundException: Call to undefined relationship [tags] on model [App\Models\Event].

I didn't see anything on https://laravel.com/docs/5.6/eloquent-relationships#eager-loading or in the source code that supports such eager loading?

Gotcha.

I'm fine if you want to add the paginator helper to this PR so I can review it all at once.

@derekmd is there any plan to work on your "ideal world" (which is amazing btw)?
This problem does not encourage developers to use polymorphic relation. :(
I have to process hundreds of polymorphic records and play with nested relations and the overload of queries is a nightmare.
Best


MSVC 2015 Selecting Incorrect erf & erfc Implementation?

cl version: 19.00.23506
stan version: 2.9.0
Compiling a model whose generated C++ includes use of stan::math::normal_cdf_log results in this compiler error:

Error	C2440	'=': cannot convert from 'stan::math::var' to 'T_partials_return'	\stan_math_2.9.0\stan\math\prim\scal\prob\normal_cdf_log.hpp	75

The problem section of code is:
const T_partials_return scaled_diff = (y_dbl - mu_dbl)
  / (sigma_dbl * SQRT_2);

T_partials_return one_p_erf;
if (scaled_diff < -37.5 * INV_SQRT_2)
  one_p_erf = 0.0;
else if (scaled_diff < -5.0 * INV_SQRT_2)
  one_p_erf =  erfc(-scaled_diff);
else if (scaled_diff > 8.25 * INV_SQRT_2)
  one_p_erf = 2.0;
else
  one_p_erf = 1.0 + erf(scaled_diff);

MSVC is finding stan::math::erfc and stan::math::erf.
Adding this:
#ifdef _MSC_VER
using boost::math::erfc;
using boost::math::erf;
#endif

above the definition of the normal_cdf_log class allows successful compilation. From running two tests, my model seems to be sampling correctly.
Is boost::math::* the correct API call here? std::erf and std::erfc seem to be in scope too.

Hi Alex,
Are you using CmdStan? Could you provide a simplified version of the Stan
program and how you compiled it? I'll try to reproduce once you send that
over.
Daniel
On Sat, Mar 5, 2016 at 11:57 AM, Alex<EMAIL_ADDRESS>wrote:

cl version: 19.00.23506 stan version: 2.9.0
Compiling a model whose generated C++ includes use of
stan::math::normal_cdf_log results in this compiler error:
Error C2440 '=': cannot convert from 'stan::math::var' to
'T_partials_return'
\stan_math_2.9.0\stan\math\prim\scal\prob\normal_cdf_log.hpp 75
The problem section of code is:
const T_partials_return scaled_diff = (y_dbl - mu_dbl)
/ (sigma_dbl * SQRT_2);
T_partials_return one_p_erf;
if (scaled_diff < -37.5 * INV_SQRT_2)
one_p_erf = 0.0;
else if (scaled_diff < -5.0 * INV_SQRT_2)
one_p_erf =  erfc(-scaled_diff);
else if (scaled_diff > 8.25 * INV_SQRT_2)
one_p_erf = 2.0;
else
one_p_erf = 1.0 + erf(scaled_diff);
MSVC is finding stan::math::erfc and stan::math::erf.
Adding this:
#ifdef _MSC_VER
using boost::math::erfc;
using boost::math::erf;
#endif
above the definition of the normal_cdf_log class allows successful
compilation. From running two tests, my model seems to be sampling
correctly.
Is boost::math::* the correct API call here? std::erf and std::erfc seem
to be in scope too.
—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/math/issues/252.

Hello Daniel,
Yes, I am compiling CmdStan from source. Find a copy of the VS2015 solution here:
http://hslmathsci.org/stan/cmdstan.zip
The model code is in \src. Before trying the build, you will need to edit the Stan.props file and change the paths to point at your local Stan source. I should forewarn you: you will find that the two C2440 error messages are buried in a deluge of warnings - mostly about possible loss of data from conversion of size_t to int, and about unreferenced locals.
Thanks for looking into this. Please let me know if there's anything else I can do to help.
Alex

@ashmsuhsl you're absolutely right. The error is due to there not being an erf and erfc in the cmath include. I'll create a pull request for this soon.

You're on---I assigned it to you.

I'll double-check. #134 fixed most of it.

This will be taken care of as part of #370


Update the status of registration

Hey, thanks for the great gem. It's not actually an issue, I am a noob in this area. I am trying to have a wicked form for registration My use case is like this.

Initially user have to register his account am using devise

A confirmation mail will be sent to the user's inbox.

after successful confirmation user will be redirected to the registration page-1 followed by page-2 and page-3.

page-1,page-2,page-3 are wicked steps
I need to track which page the user completed and if the user doesn't fill the form every time he logs in I have to redirect to the exact place where he left of.

I had a similar need for a project I was working as well. In my case, I needed 2 features:

Partial validations as the user goes through each step
Knowing which step the user is (your need)

To deal with the Feature 1, you can follow this excellent guide https://github.com/schneems/wicked/wiki/Building-Partial-Objects-Step-by-Step. At the end of the guide, your model will have an extra column status which will hold the information about the user's current step. Now, all you have to do is to redirect the user to the next step in the process in your controller.
For example, in your sessions controller,
#SessionsController
def create
  # Typical authentication logic
  if @user.status != 'completed'
    redirect_to user_build_path(@user) #redirect to the index action of your wicked controller
  else
   redirect_to default_path
end

#Users::BuildController (your wicked controller)
def index
  @user = User.find(user_params.id)
<EMAIL_ADDRESS>  render_wizard
end

This is not the only way to implement. The main thing is that you need to store information about the step the user is on. This does not have to be on the database - it can also be on the session store. But once you have that information, you can use a variety of wicked helpers to get your user to the right page.


389-ds-base: fix compilation

Things done

[X] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Multiple outputs in openldap made this package confused. Remove the explicit reference to the openldap library and let configure sort it out. Note, I did not confirm functionality merely that the package built OK and verified that it links to the expected openldap libraries using ldd.
CC maintainer: @wkennington

Yes, --with-foo=${foo} getting confused by multiple outputs isn't an uncommon thing.


 Some dependencies are only useful for the lib, some other dependencies are only useful for the bin.
I use this to distinguish where I want them:

[target.'cfg(target_arch = "wasm32")'.dependencies]
wasm-bindgen = "^0.2"

[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
structopt = "0.3"

When I do cargo run --bin <name_of_the_package> it builds and run successfully the CLI.
When I do cargo run it tries to build lib.rs which fails because the dependencies are not available.

$ cargo run
   Compiling basic v0.1.0 (/home/cecile/repos/wasm-run/examples/basic)
error[E0433]: failed to resolve: use of undeclared crate or module `wasm_bindgen`
 --> src/lib.rs:1:5
  |
1 | use wasm_bindgen::prelude::*;
  |     ^^^^^^^^^^^^ use of undeclared crate or module `wasm_bindgen`

What I expect: running cargo run --bin <name_of_the_package> does exactly the same than cargo run if there is only one bin in the package.
I wouldn't mind too much if it was just the dependencies but this is slowing down a lot the build process as it compiles the lib in WASM for no good reason.
Possible Solution(s)
...
Notes
cargo 1.50.0 (f04e7fab7 2021-02-04)

(I forgot to mention but I don't put any [lib] or [[bin]] in the Cargo.toml. This is why you need to use the package's name with --bin)

#8970 also got a similar issue. Maybe they share the same behavior from filter_default_targets`.

So I guess it would make sense to add somewhere:
enum DefaultFilterBehavior {
    All,
    Bin,
}

So when running run or install it can be set to DefaultFilterBehavior::Bin and when it is running build, test, ... it can be set to DefaultFilterBehavior::All.

Just trying to complete the "Possible solution(s)" section :grin:

It is normal that there is an implicit dependency from a binary to the library.  I'm unable to reproduce your example where cargo run --bin foo works successfully.
$ cargo new foo
     Created binary (application) `foo` package
$ cd foo
$ cat <<EOF >> Cargo.toml
[target.'cfg(target_arch = "wasm32")'.dependencies]
wasm-bindgen = "^0.2"

[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
structopt = "0.3"
EOF
$ echo "use wasm_bindgen::prelude::*;" >> src/lib.rs
$ cargo run --bin foo
    Updating crates.io index
   Compiling version_check v0.9.2
   Compiling proc-macro2 v1.0.24
   Compiling unicode-xid v0.2.1
   Compiling libc v0.2.88
   Compiling syn v1.0.61
   Compiling bitflags v1.2.1
   Compiling unicode-width v0.1.8
   Compiling unicode-segmentation v1.7.1
   Compiling ansi_term v0.11.0
   Compiling vec_map v0.8.2
   Compiling strsim v0.8.0
   Compiling lazy_static v1.4.0
   Compiling textwrap v0.11.0
   Compiling proc-macro-error-attr v1.0.4
   Compiling proc-macro-error v1.0.4
   Compiling heck v0.3.2
   Compiling quote v1.0.9
   Compiling atty v0.2.14
   Compiling clap v2.33.3
   Compiling structopt-derive v0.4.14
   Compiling structopt v0.3.21
   Compiling foo v0.1.0 (/Users/eric/Temp/foo)
error[E0433]: failed to resolve: use of undeclared crate or module `wasm_bindgen`
 --> src/lib.rs:1:5
  |
1 | use wasm_bindgen::prelude::*;
  |     ^^^^^^^^^^^^ use of undeclared crate or module `wasm_bindgen`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0433`.
error: could not compile `foo`

To learn more, run the command again with --verbose.

If you want the library to work with different targets, you'll need to use #[cfg] conditional compilation.  If you want to have a binary that is independent of the library, you'll need to use separate packages.

@ehuss I just checked and it seems you need to add this to your Cargo.toml to reproduce it:
[lib]
crate-type = ["cdylib"]

Ah, I see, yea the implicit dependency is only added if it is a linkable library.  I'm not sure if this can be changed, since there might be projects relying on this behavior.  But I can see how it can be a little unclear on how the implicit dependencies work, and there's no real control over them.

Yes :sweat: I'm not an expert so for me it just looked surprising at first. That is why I opened an issue for this.
Now I'm not sure. Is it a bug? Is it intended? Is there anything to do about it in cargo? Or should I just find another way to deal with it?
In my opinion it was surprising because I expect the main.rs or lib.rs to be an entry point. From there I expect to use mod to insert more modules. But ok I can accept that the lib.rs is always included.

I have an additional feedback on this.
On a completely unrelated project: I made a crate that is only a bin. Today I wanted to expose some of the functionalities of this crate so I wanted to use it as a lib (and keep the bin). But things don't make much sense:

I tried to build the documentation to see what is already public. But since everything is private I was expecting to see absolutely nothing. In fact, I saw all the modules and even the main function despite they are not prefixed by pub.
So I made a lib.rs and moved the mod ... from main.rs to lib.rs. Now the binary doesn't compile because it can't find the module. I'm confused because for one moment I thought the lib was always built even if I target the binary. So I guess it is built but it is not used by the bin?

But since everything is private I was expecting to see absolutely nothing.

Binary crate types default to show --document-private-items.  This could probably be added to the docs.

Now the binary doesn't compile because it can't find the module.

The paths to access items in a library from a binary should be name_of_crate::path::to::item.  If you want to create local aliases, you can write use name_of_crate::path::to::item;.  This is assuming you're not using cdylib.  See chapter 7 of the book for more information on the relation between packages, crates, and modules, and how paths work.


1.12. Store subscription information

We need to incorporate a routine where the subscription information is stored in the database. It should contain the following information

id (queue-name)
entities (routing-key)
last-refreshed-time

Subscriptions are stored in DB according to the schema defined: here


:sparkles: Certificate support for image registry

Updates the ClusterExtension API to support a certificate to retreive a bundle from an image registry.
Fixes #921

Description

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

See #960 for a different approach


Offload prep template creation/deletion from the webserver

Solved here: https://github.com/biocore/qiita/pull/1720

Not true, we still need to fix this one.

AFAIK, this has been solved. Please reopen if that's not the case.


Bump up cli version to trigger prod cli release

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

/unhold


Update dependencies

lnd dependencies should be updated after the following changes are merged:

[x] https://github.com/btcsuite/btcd/pull/1217
[x] https://github.com/lightninglabs/neutrino/pull/98
[x] https://github.com/lightninglabs/neutrino/pull/96
[x] https://github.com/lightninglabs/neutrino/pull/108
[x] https://github.com/btcsuite/btcwallet/pull/541

Unfamiliar with dependency management in GoLang but it looks like Renovate supports it via go.mod files. It automatically posts PRs with updates as they become available.

Renovate will search each repository for any go.mod files.
Existing dependencies will be extracted from require statements
Renovate will resolve the dependency's source repository and check for semver tags if found (GitHub-only currently)
If the source repository has either a "changelog" file or uses GitHub releases, then Release Notes for each version will be embedded in the generated PR.

https://renovatebot.com/docs/golang/

All deps updated!


[improve][ci] Upload native crash dump files hs_err_.log & core. in CI unit tests

Motivation

helps investigate issues when there's a JVM crash such as #19250

Modifications

upload native crash dump files hs_err_.log & core. in CI unit tests

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Codecov Report

Merging #19251 (9c09d6b) into master (334c3a5) will increase coverage by 0.32%.
The diff coverage is 8.28%.

@@             Coverage Diff              @@
##             master   #19251      +/-   ##
============================================
+ Coverage     47.04%   47.36%   +0.32%
- Complexity     9190    18904    +9714
============================================
  Files           607     1625    +1018
  Lines         57677   132275   +74598
  Branches       6007    14562    +8555
============================================
+ Hits          27132    62650   +35518
- Misses        27598    63312   +35714
- Partials       2947     6313    +3366

Flag
Coverage Δ

unittests
47.36% <8.28%> (+0.32%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.


Text only pages start, home page

This is work towards #480.
Throwing this up, not finished yet, but wanted to discuss.

This branch/PR is pretty stale and I think we're going a different direction for doing a text only / lite site. So, I'm closing out this PR. Thanks for the start on this project though!


Add "disabled" states frontend (removing functions depending on price plan)

Summary:
As a DAO user I would like to see which features are disabled when I downgrade my plan.
AC:

[ ] proposal card on proposal list
[ ] proposal profile (can still claim) but no new periods are red
[ ] circles (not live yet)
[ ] Badges
[ ] Personal profile
[ ] Cards on the member list
[ ] Treasury
[ ] Proposal Creation Wizard: Policy
[ ] Configuration Settings: Voting Mechanism
[ ] Configuration Settings: Disable full branding (only leave colours and logos)
[ ] Add tooltip "Upgrade your plan to activate"

Design:
See individual items on design system: https://xd.adobe.com/view/dff2df13-c8f4-480e-8a2e-2a74a54a6db5-8aa1/screen/065cb819-475c-479d-aab5-1773764ceaff/

@leonieherma1 Could you please share with me a description of what features are available for which plan?

@evgenibir https://hypha.earth/single-dao-pricing-models/


Added sleep moded, fixed bridge.py tests accordingly

Coverage decreased (-0.2%) to 90.931% when pulling b08b3d5f886094f78cc4e0c27e5244846bb726f5 on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+2.8%) to 93.905% when pulling 4bcc50f1039f61c35dccea34cc2267c0f692f764 on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+1.1%) to 92.24% when pulling 34f4009105e2be7a9926656fa3569e7dddefac45 on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+0.9%) to 92.035% when pulling 9d4a917e4516f28e146bb0f573c2294e27eda4ad on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+0.9%) to 91.99% when pulling 765c417e9175f53d3110c512402802ad7bf7c2b9 on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+0.9%) to 92.005% when pulling c21f4522ad8daa835d388c957f87e5af2305946a on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+0.4%) to 91.503% when pulling 93872e087a21b268b3fd0017aa009570d93f4a12 on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+0.4%) to 91.503% when pulling 942638c8af6f6ae0da27cd4b5e1d805d8c9d91a8 on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.

Coverage increased (+0.4%) to 91.503% when pulling 84c6d87fa83d278a800f93d112cd52a317ef4c4f on dev_sleep_mode into 9f7723c4ebbda16993e2755b3ecc553162de9573 on add_sleep_mode.


My transaction is stuck

My transaction is stuck and is unconfirmed

О
Отправлено с моего Galaxy A50 с помощью FastHub

Hello,
We will be deprecating "zencash-mobile" soon. It won't be updated.
Please use any other wallet from the list: https://www.horizen.io/wallets/


plan for 2021 census, and archive 2011 nepalmap

as i think about the next census, i think we can have the current version available on 2011.nepalmap.org, when we have data from 2021 census available. thoughts?

You're planning in advance! I can see the value in making the old data available so that it doesn't get lost, and that sounds like a good way to do it.

2011.nepalmap.org
2021.nepalmap.org -> redirected to nepalmap.org.
Sounds right!


[1.20.1] Crash when loading mod on a server.

Title ^
MC: 1.20.1
Forge: 47.1.3
ROA: 2.0.0
Logs: https://gist.githubusercontent.com/Gbergz/f6e29955dc7ad311c1dc7e6dddde9a59/raw/506045be41993992a2c3a078553e8bdd8b29c809/gistfile1.txt

Thanks for the report! Fixed on the latest version.
CurseForge -> https://legacy.curseforge.com/minecraft/mc-mods/rings-of-ascension/files/4767255
Modrinth -> https://modrinth.com/mod/rings-of-ascension/version/s9CnaavG


[csolution] [cbuild] directory tree gets difficult to use.

Add capability to define custom output directories.

Address https://github.com/Open-CMSIS-Pack/devtools/issues/221 schema part

I think it is not wise to include 'rtedir' here. From my perspective the content of today's 'RTE' directory is part of the project source (it always needs to be committed to revision control system).
The other directories specify (reproducible) build information, intermediate build output and build artifacts.
In the context of layer handling as well depending on whether we plan to support multiple cprojects per single directory, we may need further review of the RTE directory.

@jkrech not sure to understand your trouble here if RTE
Default can be:

output-dirs:
rtedir: ./RTE

Renaming RTE folder is part already of Allow the "RTE" folder name to be configurable. Such contribution was handling cprj only. Now we have yml so just promoting same here.

Maybe we can extend this https://github.com/Open-CMSIS-Pack/devtools/issues/314#issuecomment-1118243602

@brondani Thanks for such contribution !
I've got a try relying on some local build. Works as expected on my local example project. I've been got thru project manager and build manager workflow with some success.

I'm getting as expected new defaults in sync. #314
Only comment is cproject.yml output-dirs settings if some are not applied per my trials.

Only comment is cproject.yml output-dirs settings if some are not applied per my trials.

Thanks for the feedback @VGRSTM
As I commented here it is purposely implemented only at csolution level, so it is not handled yet in cproject.yml. Let's get it consolidated before extending it.


Make styling look more native (especially on Android)

Hello,
Thank you for the work you've put into this project it's amazing. As you may have noticed, the Ratchet/Android CSS doesn't look native on Android anymore, it still does on Froyo (Android 2.2) but who uses that anymore? Maybe go for a lighter, more flat design, something like :
http://ionicframework.com/docs/components/#striped-style-tabs
http://cdn.androidpolice.com/wp-content/uploads/2013/05/nexusae0_unnamed-105.png
http://img.phonandroid.com/2014/10/nexus-5-lollipop.jpg

+1


Retrieving the Trained Model

How can we get back our trained model once we train using the pipe object and Gpipe Scheduler as a normal nn.Module class?

Also interested in this. Did you ever figure it out?

Not as of now.

Sorry for replying late.
We have migrated the PiPPy library to torch.distributed.pipelining
Here is our new documentation: https://pytorch.org/docs/main/distributed.pipelining.html.
In section "Option 2", you can see:

The Pipe object provides a method for retrieving the “model partitions”:
stage_mod : nn.Module = pipe.get_stage_module(stage_idx)

The return object is a nn.Module, so you can save it as you would do with a regular module, such as:
torch.save(stage_mod, filepath)

or
torch.save(stage_mod.state_dict, filepath)

(Reference: https://pytorch.org/tutorials/beginner/saving_loading_models.html)

Sorry for replying late. We have migrated the PiPPy library to torch.distributed.pipelining Here is our new documentation: https://pytorch.org/docs/main/distributed.pipelining.html.
In section "Option 2", you can see:

The Pipe object provides a method for retrieving the “model partitions”:
stage_mod : nn.Module = pipe.get_stage_module(stage_idx)

The return object is a nn.Module, so you can save it as you would with a regular module, such as:
torch.save(stage_mod, filepath)

or
torch.save(stage_mod.state_dict, filepath)

(Reference: https://pytorch.org/tutorials/beginner/saving_loading_models.html)

I think the question (at least for me) was if we could turn the nn.Module back into the non-pipelined version for modification and saving?

Hmm, do you mean getting back the full model at the end of training, but before saving the final checkpoint?
It might be hard, I think, because each stage's updated weights are now on different ranks.
So unless we do an all-gather, the weight in the pipe object would only has part of it being up-to-date.
That said, imagine we would do a torch.load later, that would be a good time for gluing the model back together, because:
(i) we have the full, original model; and
(ii) PP does not change the FQN of the weights.
It is only a matter of loading from a single checkpoint file vs multiple checkpoint files.
As far as I know, HF already uses multiple checkpoint files for large models.

OK, so here is what I want to do, Obtain gradients of each layer from each rank of the stage from the pipe object, and send it to the CPUs. Get some modifications done on the gradients on the CPU, then bring it back to the subsequent ranks of the pipeline stage and update the model with modified gradients. Is this possible with Pippy?


Add an API for backup / store data in pure text

It's nice that you considered the backups which is one of the very important component for a service.
But I have to idea for you to improve the user experience for backups.

Add an API for backup. Then users could remotely do backups by calling this API.
Store the data in pure text. If all data store in pure text, then everything can be backuped by regularly commit and push through VCS.

Wonder if this can be integrated with ArchiveBox

Hi, that's really a good idea. I would like to give a try for ArchiveBox.
Should I close this issue? Or should we wait a bit to see further comments?

@junwei-wang

I added a REST API which can be used to retrieve / manage bookmarks. Does that fit your use-case?
Interesting idea to use VCS for bookmarks, but I would not consider adding this as a core feature. Regular file backup is common enough and also sufficient for most people. It should be possible to do something like this by writing a 3rd party script / app using the REST API mentioned above. It might also be possible write a simple script which makes a curl request against the /settings/export URL (with proper authentication) to download all bookmarks and then trigger a commit in the VCS.

Closing due to inactivity. Also there are now docs on how to create a SQL dump from the database that can be added to VCS.


CI: fix examples - MNIST

What does this PR do?
Resolves #6323
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Hello @Borda! Thanks for opening this PR.

In the file pl_examples/__init__.py:

Line 38:1: E402 module level import not at top of file

Do see the Hitchhiker's guide to code style


Does routellm support routing queries to different models in OpenAI assistant?

I can see that queries can be routed to different models of chat completion, but can routellm also route queries to different OpenAI assistants or use different llms for the same OpenAI assistant?

Hi there! At the moment, we only support the Chat Completions API.

Thanks for clarifying @iojw, is there any way i can contribute towards this idea ? is this integration in your roadmap ?


WIP Use java DatagramSocket directly

Attempts to address https://github.com/elastic/logstash/issues/9346 by just using the Java UDP API directly. The issue there is that JRuby's implementation uses too much memory, the underlying ruby strings returned from the UDP socket use up as much memory as the UDP buffer size, regardless of how big the actual packet is.
I would like to benchmark this and make one more pass before this is ready for review.

I haven’t tested or benchmarked this PR, but it might be worthwhile to use Netty instead of the Java socket API. Other plugins like logstash-input-tcp already do.
(Also, this would be so much simpler once the Logstash Java API is available!)

Netty would be worth exploring I agree, but I think it makes sense to solve
this memory issue in a minimal way for the time being.
I agree Netty makes more sense as a pure java plugin.
On Fri, Apr 20, 2018, 5:47 PM Mark Janssen<EMAIL_ADDRESS>wrote:

I haven’t tested or benchmarked this PR, but it might be worthwhile to use
Netty https://netty.io instead of the Java socket API. Other plugins
like logstash-input-tcp
https://github.com/logstash-plugins/logstash-input-tcp already do.
(Also, this would be so much simpler once the Logstash Java API is
available!)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-input-udp/pull/38#issuecomment-383241462,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIBY6dGMHvDtTM5PE_O64vet-Ick6PSks5tqmV3gaJpZM4TeKGz
.

You need to assign to rcvbuf

Also, it's not clear to me that for UDP Netty would be much faster than
blocking IO. At any rate, it's a question we should ask when we port to
Java.
On Fri, Apr 20, 2018, 6:30 PM Andrew Cholakian<EMAIL_ADDRESS>wrote:

Netty would be worth exploring I agree, but I think it makes sense to
solve this memory issue in a minimal way for the time being.
I agree Netty makes more sense as a pure java plugin.
On Fri, Apr 20, 2018, 5:47 PM Mark Janssen<EMAIL_ADDRESS>wrote:

I haven’t tested or benchmarked this PR, but it might be worthwhile to
use Netty https://netty.io instead of the Java socket API. Other
plugins like logstash-input-tcp
https://github.com/logstash-plugins/logstash-input-tcp already do.
(Also, this would be so much simpler once the Logstash Java API is
available!)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-input-udp/pull/38#issuecomment-383241462,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIBY6dGMHvDtTM5PE_O64vet-Ick6PSks5tqmV3gaJpZM4TeKGz
.

@IrlJidel good catch on rcvbuf, that should be fixed now. I think this needs another pass from me this week to double check java exception handling and also to add more tests. That error, for instance didn't fail the test suite.

Let me know when you think it's OK, so I can run perf tests using this patch and see the results before releasing it.

I'd like to attempt a fix of the issue with JRuby instead of going directly to a rewrite of the plugin. For reference, a workaround was proposed by @original-brownbear here.
That said I'm +1 on exploring a more native implementation, just not for the reason of fixing the memory usage issue.

jruby RubyString doesn't have a .b method

I agree that JRuby should be fixed.
Joao, why not do both? Using the java classes directly is going to be more
efficient. This refactor is relatively small. If you think it's not
worthwhile however I'm glad to abandon it.
On Mon, Apr 23, 2018, 6:07 AM João Duarte<EMAIL_ADDRESS>wrote:

I'd like to attempt a fix of the issue with JRuby instead of going
directly to a rewrite of the plugin. For reference, a workaround was
proposed by @original-brownbear https://github.com/original-brownbear
here
https://github.com/elastic/logstash/issues/9346#issuecomment-382996516.
That said I'm +1 on exploring a more native implementation, just not for
the reason of fixing the memory usage issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/logstash-plugins/logstash-input-udp/pull/38#issuecomment-383537992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIBY7ChTwPmrWzGCYi0cm7HR7UzXs0Tks5trbXOgaJpZM4TeKGz
.

I put the perf test results  in https://github.com/elastic/logstash/issues/9346#issuecomment-383546958 but might make more sense to have them here:
tested on LS 5.6.3.
Tests were run for 15minutes with 300 byte message.

buffer_size
Patch
3.3.2

1K
52k eps
51k eps

64K
51k  eps
40k eps *

3.3.2 with 64K buffer_size  udp->main cpu usage was 92%, for all other cases was 46%

Couldn't test using @original-brownbear suggestion to use .b as this method doesn't appear to be available in jruby

@jsvd those are all valid concerns. I have a lot of irons in the fire and likely won't be able to address things in that detail given time concerns.
I'm going to leave this PR open, but I won't do further work on it.

Just for reference, I tried running this on logstash 6.2.4 and got an exception when setting the host field in the event:
[2018-04-23T17:16:36,493][ERROR][logstash.inputs.udp      ] Exception in inputworker {"exception"=>org.logstash.MissingConverterException: Missing Converter handling for full class name=java.net.Inet4Address, simple name=Inet4Address, "backtrace"=>["org.logstash.Valuefier.fallbackConvert(Valuefier.java:97)", "org.logstash.Valuefier.convert(Valuefier.java:75)", "org.logstash.Valuefier.lambda$static$3(Valuefier.java:51)", "org.logstash.Valuefier.convert(Valuefier.java:73)", "org.logstash.ext.JrubyEventExtLibrary$RubyEvent.ruby_set_field(JrubyEventExtLibrary.java:95)", "org.logstash.ext.JrubyEventExtLibrary$RubyEvent$INVOKER$i$2$0$ruby_set_field.call(JrubyEventExtLibrary$RubyEvent$INVOKER$i$2$0$ruby_set_field.gen)", "org.jruby.internal.runtime.methods.JavaMethod$JavaMethodN.call(JavaMethod.java:741)", "org.jruby.ir.targets.InvokeSite.invoke(InvokeSite.java:145)", "Users.joaoduarte.projects.logstash_plugins.logstash_minus_input_minus_udp.lib.logstash.inputs.udp.RUBY$method$push_decoded_event$0(/Users/joaoduarte/projects/logstash_plugins/logstash-input-udp/lib/logstash/inputs/udp.rb:155)", "Users.joaoduarte.projects.logstash_plugins.logstash_minus_input_minus_udp.lib.logstash.inputs.udp.RUBY$method$push_decoded_event$0$__VARARGS__(/Users/joaoduarte/projects/logstash_plugins/logstash-input-udp/lib/logstash/inputs/udp.rb)", "org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77)", "org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:93)", "org.jruby.ir.targets.InvokeSite.invoke(InvokeSite.java:145)",

We should, by the way, aim for a minimal refactor, re-initializing the string somehow to free that memory.

Also, for reference, I created an issue in JRuby about this: https://github.com/jruby/jruby/issues/5148

I created a PR that works around the memory issue https://github.com/logstash-plugins/logstash-input-udp/pull/39


local variable 'score' referenced before assignment

Hello,I have the following problem when i  use it：
\openfe\openfe.py", line 662, in _calculate_and_evaluate_multiprocess
\openfe\openfe.py", line 595, in _evaluate return score
UnboundLocalError: local variable 'score' referenced before assignment
How can I solve it
thank you

Hello,I have the following problem when i use it： \openfe\openfe.py", line 662, in _calculate_and_evaluate_multiprocess \openfe\openfe.py", line 595, in _evaluate return score UnboundLocalError: local variable 'score' referenced before assignment How can I solve it thank you

Could you please provide the code and datasets so that I can reproduce this bug?


A pkg-config file would be useful for linux or macOS

As implemented for the old make-based build system in the now closed PR #2. A .pc pkg-config file would be useful for macOS and linux users. I'm trying to write some Swift bindings for example but the pkg-config utility can't find my installed leveldb library.
This was also suggested in #145 but that kind of died with the transition from the make-based build system to cmake.

The only thing we have to add is the following file: leveldb.pc
prefix=@prefix@  exec_prefix=${prefix}  libdir=${exec_prefix}/lib  includedir=${prefix}/include  Name: leveldb  Description: A fast key-value storage  Version: @version@  Libs: -L${libdir} -lleveldb  Cflags: -I${includedir}
where @version@ should be replaced by the version number of the built version of leveldb. And @prefix@ should be replaced by the folder it is installed in (often /usr/local)
This should be placed somewhere in the leveldb project and then a link to that file should be placed in the pkg-config files location (often /usr/local/lib/pkg-config)

The team considered adding pkg-config support, but decided to stick with the packaging support provided by CMake only for the time being.

Hi @cmumford - can you share the team's reasons? Would you accept a PR for this issue if I submitted one? Thanks -

@njwhite Thank you for volunteering to put together a PR! Unfortunately, we're not currently interested in reviewing pkg-config support.
The main factor here is maintenance cost. We don't use pkg-config, so we wouldn't be testing the support, which means it'd eventually break. We don't want to spend time dealing with this in the future.
A secondary factor is that pkg-config support would open up the flood gates to requests for other useful packaging systems, such as conan, hunter, and vspkg. We want to focus on developing leveldb.

I do hate necroposting, but I feel it is justified here.

The main factor here is maintenance cost. We don't use pkg-config, so we wouldn't be testing the support, which means it'd eventually break. We don't want to spend time dealing with this in the future.

If the pull requester included a test script (perhaps as simple as gcc $(pkg-config --cflags --libs leveldb) test.c -o test-pc && ./test-pc), would you change your mind? You'd get an immediate notification of any problems.

A secondary factor is that pkg-config support would open up the flood gates to requests for other useful packaging systems, such as conan, hunter, and vspkg. We want to focus on developing leveldb.

pkg-config is the lingua franca of the "finding a library" world on linux.
For example, conan supports it, and cmake supports it (and by extension, I assume hunter does too.) So does meson, waf, and autotools. I could go on. My point is that you shouldn't need to do any additional work to support more build systems, because pkg-config enables most of them.


amend: fixed

:tada: This PR is included in version 1.14.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


remove the default exposecontroller configmap as it will try to overr…

…ite an existing one created by gofabric8 deploy otherwise related to fabric8io/fabric8#6448

[merge]


Adding decimalSeparator field constraint

Relevant issue: https://github.com/dataprotocols/dataprotocols/issues/246

@rgrp @danfowler can we make progress here?

+1 @akariv.  To add to the discussion, I will point out that having format be a string or an object puts JSON Table Schema into greater alignment with W3C CSVW for the number format: http://w3c.github.io/csvw/syntax/#formats-for-numeric-types .

If the datatype base is a numeric type, the datatype format annotation indicates the expected format for that number. Its value MUST be either a single string or an object with one or more of the properties:

We can go further and rename decimalSeparator -> decimalChar and thousandsSeparator -> groupChar*
{
  "currency": true,
  "decimalChar": ".",
  "groupChar": ","
}

* http://stackoverflow.com/questions/15286545/why-is-the-thousands-separator-called-the-grouping-separator

@danfowler +1 - can we move this stuff to the issue which is #246 - i think we need consensus there before PR. This can be quite rapid i think.


Delete the span we log for the startup moment

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#726  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bidetofevil and the rest of your teammates on  Graphite


Windows build

@ngoldbaum if you can create a branch that setups up a build env on windows, I can work on getting the windows build working

I've gotten to the point of building csp itself on a windows box, but the build fails trying to find brotli:
CMake Error at cpp/cmake/modules/FindBrotli.cmake:92 (message):
--
Could not find the Brotli library.  Looked in in
C:/Users/goldbaum/csp/_skbuild/win-amd64-3.11/cmake-build/vcpkg_installed/x64-windows.
Call Stack (most recent call first):
vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
cpp/cmake/modules/FindDepsParquetAdapter.cmake:13 (find_package)
vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:304 (find_package)

-- Configuring incomplete, errors occurred!
Traceback (most recent call last):
File "C:\Users\goldbaum\mambaforge\envs\csp\Lib\site-packages\skbuild\setuptools_wrap.py", line 666, in setup
env = cmkr.configure(
^^^^^^^^^^^^^^^
File "C:\Users\goldbaum\mambaforge\envs\csp\Lib\site-packages\skbuild\cmaker.py", line 357, in configure
raise SKBuildError(msg)

An error occurred while configuring with CMake.

Looking at the contents of FindBrotli.cmake it seems to be specifically looking for unix static libraries with a .a suffix. I think we just need to add some more names that might appear on windows too. The version of this in apache parquet-cpp might work on windows too?

Do you have the steps you took to get to this point?

See #123

Sorry I'm still getting used to github.  How do I checkout your forked clone / branch, do I need a fresh git clone or can I do it in an existing area?

Do the instructions from the dev guide in #117 help?
https://github.com/Point72/csp/blob/7f24717460753a36f2bdb2b806d961c5f23f12e6/docs/DEVELOPER_GUIDE.md#how-to-check-out-a-pr-locally
Although I see now the second-to-last step has a typo, it should be git switch.
Those instructions are nice because you don’t need any info about forks to follow them, but if I’m working with someone a lot I’ll often add their fork as a remote for my clone and pull from the contributor’s fork directly without using the github-specific PR ref trick described there.
You can configure my fork of csp as a git remote on your clone and pull the PR branch from my fork:
$ git remote add ngoldbaum https://github.com/ngoldbaum/csp
$ git fetch ngoldbaum windows-dev-enc
$ git checkout windows-dev-env

(you can read my branch name in the header of the PR description)


add ignore property to includeAll XSD (DAT-14921)

Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
The ignore code has existed for a long time for includeAll, but it was not part of the XSD.

Things to be aware of

Things to worry about

Additional Context

Should we add an xml test for this or do you think it's appropriately covered already?

I can add a test, good idea.


Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'The service configuration is nil

-swift demo: when i touch upload or download button, there is a error:
at this line:
let s3 = AWSS3.defaultS3()

app due to uncaught exception 'NSInternalInconsistencyException', reason: 'The service configuration is nil. You need to configure Info.plist or set defaultServiceConfiguration before using this method.'

Which sample app are you trying to run? Looking at the S3TransferUtility example, there are instructions for updating the Info.plist. Did you do this?

I have the same issue when trying to run the S3TransferManagerSampleSwift on iOS10. Uploading works fine, but download immediately fails in listObjects() with the exception described above.
I believe I did the Info.plist setup correctly:

I am also facing the same issue. Any one can resolve that?

Add below code in didFinishLaunchingWithOptions
AWSCognitoCredentialsProvider *credentialsProvider = [[AWSCognitoCredentialsProvider alloc] initWithRegionType:AWSRegionUSEast1 identityPoolId:AWS_POOLKEY];
AWSServiceConfiguration *configuration = [[AWSServiceConfiguration alloc] initWithRegion:AWSRegionUSEast1 credentialsProvider:credentialsProvider];

AWSServiceManager.defaultServiceManager.defaultServiceConfiguration = configuration;

Add below code in AppDelegate.swift:
let credentialsProvider = AWSCognitoCredentialsProvider(regionType: "Your Region Type", identityPoolId: "Your Identity Pool ID")
let configuration = AWSServiceConfiguration(region: "Your Region Type", credentialsProvider: credentialsProvider)
AWSServiceManager.default().defaultServiceConfiguration = configuration

Closing issue as it appears to have been address by @raymondyyy and @TijenderSingh


Deal with CC0057 (unused args) and event handling methods

Discussion started on #916.
If we have this in UWP and XAML:
<Button Click="ButtonBase_OnClick" />

And in the code behind:
private void ButtonBase_OnClick(object sender, RoutedEventArgs e)
{
}

We cannot remove these two arguments, or the event handling will fail. We should not report CC0057 in this scenario.
The way to fix this is alter the analyzer, which already checks method and constructor declarations, to ignore them if a signature with two parameters is found, where the first is of type object, and the second is a class that inherits from EventArgs, and the return is void or Task (or a descendant of Task).

This happens in a lot of cases where a method signature has to match a delegate and contains parameters that are not used. I'm not sure if there is an easy way to detect this but if the method address is referenced it should probably be ignored.

@CZEMacLeod if it matches a delegate but is never assigned to it, we can't detect. This is a special case, the binding is happening in the background, and we can't find it.

It can  also happen for an interface implementation method, which doesn't use a provided parameter. There should be a way to switch that warning off.
And I am from VB world, if that matters :-)

@mc0re Do you have a sample code of this ?

Public Interface IDo
    Sub DoIt(value as Integer)
End Interface

Public Class Doer
    Implements IDo

    Public Sub DoIt(value as Integer) Implements IDo.DoIt
        Console.WriteLine("Do it")
    End Sub
End Class

The same can happen with an overiden method - it must accept the same amount of arguments as its ancestor, but it might not need them all.

@mc0re In the VB implementation we could consider ignoring this rule if we detect the "Implements x" or "Handles y" syntax on the declaration. However, VB no longer requires the parameters for event handlers, so recommending that they be removed is actually valid there.
I don't see an issue with keeping this as an info on interfaces as well as long as it can be suppressed at the individual method level in the case of interfaces where the implementation doesn't need the passed parameter.

Suppressing involves two pragmas around the code, which uglifies it. The CodeAnalyzer way with <Attributes> is somewhat better, but limited to at least method scope. And it's always cleaner without the suppressions :-)
The same issue with possibly unused parameters arises in Overrides and AddressOf scenarios, where the infrastructure requires them even if they are not used.


[3.0.0] Chrome Debugging does not work if you use Sync APIs / Invariant violation: Calling synchronous methods on native modules is not supported in Chrome

As per the title, I get this when debugging on an iOS simulator (yet to try android, but assume it would be the same).

Dang - and the reason we went away from constants is because app init was taking a long time (c.f. getUserAgent). This is a problem that needs thought.
I don't personally use a debugger (strange but true) thus had not noticed at all, and this doesn't affect me (your current maintainer) but I recognize it's important to many.
I'm open to any suggestions.

I will say that I'm happy to release a breaking 4.0 or whatever if a solution is proposed that is workable for the synchronous use case. Perhaps the compromise is that only certain items are exposed synchronously, are fetched as constants, and the rest is async only. Then we just categorize which APIs get the constants + sync API treatment with sensitivity to startup time and it's good enough?

In chatting with @Johan-dutoit it appears this only happens if you use the sync APIs - if your app is async-only APIs then chrome devtools should be fine?
I will add a mention of this to the docs, and that makes me think that the compromise strategy of loading a few things as constants underneath the sync APIs and having the rest (the not likely to be used at app startup items) be "dangerous" might be the best we can do to balance my desire to support sync use case at startup, and debugging, and fast init time.

Having the same issue. Don't really know how to help as I really don't know what's happening.

@MakhouT if you use the debugger, and you touch a xxxSync() method, the debugger will fail. If you want to use the debugger currently, you must not use any xxxSync() methods. That means you need to convert to a fully async style and if there are items you need at startup then before you create your App and display your root view, you need to fetch those items during bootstrap and the app creation / root view display needs to be in a .then() after you've got the items you need.
I recognize this is painful - being fully async on critical items during bootstrap - which is why Sync() APIs exist but they blow up the debugger, which is why I propose a pragmatic solution of making a few select items available via constants (which are synchronous) again but I haven't made that PR yet.
That's all the info I've got. Hope it helps.

FWIW this is my workaround in my app, basically following the above comments. In short, when my app's root component mounts, I throw up a loading screen while I populate my needed constants, then when that is finished I render the rest of my app.
First I create a deviceInfo.js:
// deviceInfo.js
import DeviceInfo from 'react-native-device-info'

var output = {}

exports.populateDeviceInfo = async () => {
  output.isEmulator = await DeviceInfo.isEmulator()
  output.version = await DeviceInfo.getVersion()
 // ... and whatever else you may need
}

export default output

Then in my AppContainer.js (my root component). I have some stuff relating to redux below but obv adjust it to whatever your app views should be.
// (import your components, etc)
import { populateDeviceInfo } from './deviceInfo'

export default class AppContainer extends Component {

  state = {
    deviceInfoLoaded: false
  }

  componentDidMount = async () => {
    await populateDeviceInfo()
    this.setState({ deviceInfoLoaded: true })
  }

  render() {
    return (
      <Provider store={store}>
        <PersistGate loading={<LoadingView />} persistor={persistor}>
          { this.state.deviceInfoLoaded ? <App /> : <LoadingView /> }
        </PersistGate>
      </Provider>
    )
  }
}

And then afterwards I can just import DeviceInfo from './deviceInfo' where I need it and use the populated constants. I didn't have that many constants to load, nor did they take a huge amount of time, so this worked for me.

That's fantastic, thanks especially for showing working code. That is about exactly what I'd expect to handle a fully async style for things you need before first render, and I'm guessing many (like myself) weren't sure how to handle it so cleanly.

@TimMun Actually there could be the cases when this approach won't work. For example when you use the lib within some code that is executed during the app startup. E. g. when you create a StyledComponent object and use isTablet() function inside. So this code won't wait until the populateDeviceInfo object is populated.

I personally had some code that was ill-advised but called DeviceInfo items in the constructor on objects that had a singleton pattern (exported result of MySingleton.getNewInstance() which calls the constructor, which calls DeviceInfo) so just import statements were triggering things. So I do sympathize with the desire for Sync() APIs and for making those work with the debugger.
But in general each example of how to handle things slightly better gets people to consume the API more async which I think is more javascript-idiomatic

@TimMun
I understand why the API has been rewritten to become async and reduce app boot time but to me it's just weird I need asynchronous calls for constants that are readily available on the device.
Imagine programming in javascript and writing this to fetch a constant:
const MY_CONSTANT_VARIABLE = 1

const fetchMyConstant  = Promise.new(() => {
 resolve(MY_CONSTANT_VARIABLE)
}, reject)

Writing promises like this for constants is just weird but that's what is essentially happening right now with the rewrite to asynchronous calls.
The sync calls are a great addition but you completely lose debugging functionality for your entire app which breaks every developer team that uses react-native-device-info.
My point is:
All if not most of react-native-device-info calls are short running processes that take milliseconds to complete and send data.
Picking async calls to boost app performance in my opinion isn't the best solution to this problem. I mainly think that sending all this data over the react native bridge is the bottleneck and switching to async calls just pushes the problem down the line while adding extra complexity.
I would rather have a few extra ms of boot time then having to deal with async calls for fetching constants.
If I can help in any way let me know.

All if not most of react-native-device-info calls - which ones? for which devices? My first cut was purist and intended to not arbitrarily decide. Just make them all async.
My experience integrating that was that it was irritating at bootstrap yes. So my second cut was to add a companion Sync API.
Only later I learned it blew up debugging. So here we are.
Pragmatically, https://github.com/react-native-community/react-native-device-info/pull/784 goes down the arbitrary "let's decide for some calls to not be async" route by restoring a few key things as constants.
For your example I'd say I can imagine writing code like that but why would I do that?
async myUsefulFunction() {
  try {
    const myConstant = await deviceInfoCall();

     // all that other stuff useful functions
     // seemingly always relying on async stuff anyway so...

  } catch (e) {
    console.log('that sucked');
  }
}

Not trying to debate really. I intend to get have chrome debugging support resolved. If you want to help, work on the draft of that PR - I haven't had time to work on it yet

My example was just to demonstrate react-native-device-info prior to writing most functions from constants to functions.
For example:
These are declared as constants on the module:
Prior to rewrite:
https://github.com/react-native-community/react-native-device-info/blob/master/ios/RNDeviceInfo/RNDeviceInfo.m#L130
Now:
https://github.com/react-native-community/react-native-device-info/blob/41ee8c78e561ff5d689a353095e25c6b7f821218/ios/RNDeviceInfo/RNDeviceInfo.m#L98
I just think stuff like this should be declared as a constant since it's instant and should be accessible as so. Not as a function that should be waited on.
If calling all these methods in succesion is raising boot time significantly maybe we could bundle all these calls and send all info over the bridge in 1 call.
Native:
// EXPORT AS CONSTANT
deviceInfo: {
  systemName: self.systemName,
  bundleId: self.bundleId,
}

Javascript:
const { systemName, bundleId } = DeviceInfo.getInfo()

// At this point you can cache all values in javascript that won't change like systemName, etc...

// Specific call for up to date battery level
const batteryLevel = await DeviceInfo.getBatteryLevel()

did you look at the linked PR?

Have this same problem

100% in agreement with @JensDebergh, very well presented.
https://github.com/react-native-community/react-native-device-info/issues/776#issuecomment-535053950
I come from mainly a native mobile background, and think that async calls for device constants is excessive. It leads to unnecessary complexity, which is something that I'm always against. But if it doesn't impact the user (a delay of a few ms at worst), and especially if there's no clear conclusion if any delay is primarily caused by the bridge or not, it seems wise to just opt for brevity on the API level and use constants instead.

This is all interesting, we are all in agreement in general, and it does nothing to move the issue forward 🤷♂

@mikehardy I'm able to work on the pull request this saturday but I'm only able to the iOS part. My java is terrible.

tag team activate: my ios is terrible but I'm really strong at java :-)

Here I came, just looking to get the updates for iPhone 11's, and walked into a hornet's nest! Programming, am i right?
This is pretty critical. Our app has core, core bootstrap code that has been running for years that would take an entire rewrite to get working with async operations. Using the sync alternatives works, but breaks the debugger, per this issue. I plan on sticking to v2.x of this package and manually working around it for iPhone 11 support. But this won't work forever.
...Here's another temporary solution: we can detect if the debugger is open.
const DEVICE_MODEL = global.__REMOTEDEV__ ? 'Debugger' : DeviceInfo.getModelSync();

I'm using react-native-debugger. YMMV.

I like the workaround - that is potentially useful for people thanks
I don't imagine this will stay unresolved more than another week - this module was already working fine with constants (implication: I/we have code I can refer to quickly to get some constants back without the async or debugger breaking)
Quick question for anyone following along - what is your minimal set of constants you need for bootstrap to work?
There will always be APIs in this module that are async because they are so slow (lookin' at you UserAgent...) so I want to find the middle path that includes the right things as constants but leaves the rest

Here are all the calls we use from this package. It's actually not as many as  I had thought.
DeviceInfo.getManufacturer(),
DeviceInfo.getModel(),
DeviceInfo.getSystemVersion(),
DeviceInfo.getBuildNumber(),
DeviceInfo.getUniqueID();
DeviceInfo.getVersion()
DeviceInfo.getBundleId();

those are all included in the ones I was thinking of making constants yes - curious for other responses so I can look at the union of set

@mikehardy Can you post the list you have for properties that are going to be available as constants?
If you the list of properties I can make the changes this saturday.

this is what I have in my app that I need at bootstrap
interface EssentialDeviceInfo {
  uniqueId: string;
  model: string;
  manufacturer: string;
  systemVersion: string;
  appVersion: string;
  buildNumber: string;
  phoneNumber: string;
  bundleId: string;
}

We were able to migrate relatively easily to async, though our app isn't too complex. The main ones that took some refactoring for us were:
DeviceInfo.getUniqueID()
DeviceInfo.isTablet()
DeviceInfo.hasNotch()

We used the notch and tablet information in some cases to determine how to mount a component at bootstrap, such as with react-navigation. Otherwise, it was a pretty smooth refactor.

Just a note to say hasNotch() isn't going anywhere right now, and I believe it could be a constant, but you might be interested in https://github.com/th3rdwave/react-native-safe-area-context - it's the real solution to all these viewable area encroachments and already works way better

I sugguest isTablet() also need to make as constants

Looked at my code and found out that i also use getBrand method alongside with the methods specified above during the app startup.

this is what I have in my app that I need at bootstrap
interface EssentialDeviceInfo {
  uniqueId: string;
  model: string;
  manufacturer: string;
  systemVersion: string;
  appVersion: string;
  buildNumber: string;
  phoneNumber: string;
  bundleId: string;
}

The list of properties we use in our app:
DeviceInfo.getDeviceName()
DeviceInfo.getDeviceLocale()
DeviceInfo.is24Hour() -> +3.1.4 extracted to different library
DeviceInfo.getDeviceCountry() -> +3.1.4 extracted to different library
DeviceInfo.getTimezone() -> +3.1.4 extracted to different library
DeviceInfo.isTablet()
DeviceInfo.getMaxMemory() as (number | undefined)
DeviceInfo.getTotalMemory()
DeviceInfo.getManufacturer(),
DeviceInfo.getModel(),
DeviceInfo.getBrand(),
DeviceInfo.isEmulator(),
DeviceInfo.getSystemName(),
DeviceInfo.getSystemVersion(),
DeviceInfo.getUserAgent(),
DeviceInfo.getDeviceId(),
DeviceInfo.getUniqueID(),
DeviceInfo.getBundleId(),
DeviceInfo.getBuildNumber(),
DeviceInfo.getVersion(),
DeviceInfo.getApplicationName(),

@JensDebergh some of those will never be constants again, e.g. UserAgent, probably the memory ones. Can you separate out the ones that are vital to your bootstrap?

My bad I just listed everything we do on boot but obviously not all of these are required.
Just as you said UserAgent and Memory can be skipped in our app aswell. We just check these to allow certain animations.
Maybe we should list the obvious performance bottleneckcalls and convert the rest to constants again?

It would be nice if isEmulator() could make the list.

I want to have the opposite stance - constants for what is needed, async (with a sync mirror as workaround for edge cases). I think the real bootstrap need is pretty low but the API surface area here is large and will grow
@ethanneff I'll see about isEmulator but I have a PR that makes that call pretty comprehensive - #721 - and I don't know how it could be fast, so likely not, at least in the first cut

@mikehardy never mind the need for isEmulator(). I used to use it to turn off useNativeDriver for animations, but this appears to no longer be broken with the latest React Native version.

inexorable forward progress :-) good stuff @ethanneff

@mikehardy Have a look at https://github.com/react-native-community/react-native-device-info/pull/817

Ah, so I really need the model to be available directly. (Using it to distinguish a certain style, which is created on import, so async won't work). For now I've downgraded to 2.x. Just chiming in to let you guys know I'd appreciate model being marked as an essential.

Thanks @JensDebergh I'm not sure if I will get to it today, but I will try, and it's definitely on the short list for review as I really want to get this knocked out and feel more solid about the v3+ experience
@jasperkuperus - model request is noted - and that's the same use case I have (device info used immediately via import chains) and I will say that if you restructure your code so that the AppContainer / Root View stuff happens as a then() in bootstrap, and you restructure your code so that the things you needed on import are instead done using info from a device info query etc, then it's possible. And I went down that path and then added the Sync parallel API so I get that this is unpalatable but just wanted to mention in case you were stuck on UIWebView references or something as an emergency.

To answer your question @mikehardy and to drop some more insights of how the package is being used I can tell you I am in need of the following constants:
DeviceInfo.getDeviceType();
DeviceInfo.getUniqueID();
DeviceInfo.getModel();
DeviceInfo.getVersion();

I am also using a package called applicationinsights-react-native, they also still have a dependency on the ones above.

@MakhouT thanks - those all seem sane for now. We have an iOS pull request already to make this change I'll see about an Android and Windows one shortly so we can get this sorted

just to confirm hasNotch could be available as a constant?

@rtman yeah it could be but you really want to move to something like this https://github.com/th3rdwave/react-native-safe-area-context

@mikehardy I had a look at react-native-safe-area-context and I'm interested in it, but to be honest there's a lack of information on that package, so I'm wary to change to it yet. There's hardly any description on what it does. I'd prefer to stick with hasNotch if possible.

Yeah - the package is new but the contributor there is a frequent react-native contributor / maintainer, and the library does what hasNotch() here wishes it did ;-) - this article shows how that package already correctly works with all the simulators and emulators, and even the web https://github.com/th3rdwave/react-native-safe-area-context#resources

hasNotch will eventually go away here and be handled by that package once the maintainer there and I finish making sure the use cases here are easily handled etc

@mikehardy ahh i see, ok well maybe I can get the maintainer to flesh out the readme a bit and that will satisfy my concerns.

@mikehardy I'm not seeing any indication that react-native-safe-area-context allows for code to run if there is no notch, it looks to only replace SafeAreaView. We use hasNotch to apply padding to the screen when there is no notch and remove padding when there is. (I asked this question in an issue on the package, but thought you might know since you are planning on migrating hasNotch to this)

@rtman We do similar things with hasNotch for more control. Although <SafeAreaView> is nice you lose control of the top and bottom of your screen.
Imagine using 2 different colors for your header & footer of a screen. You are unable to do this with this type of view. Whereas hasNotch gives you control to add paddings if you need it.

since i use custom header in my app, I need hasNotch to decide the height of the  custom header in iOS (in Android  I use StatusBar.currentHeight to set the height)

Some of this methods extremely need in Styles.
It is impossible to use them with Async style.

I kept looking for a solution that uses this library but avoids async and promises and couldn't find one so I've forked this project to make almost all of the constants exposed without callbacks. You can find the new project here. I've renamed some of the constants (e.g. appBuildNumber instead of the more ambiguous buildNumber) but it is basically the same otherwise.
If there's any interest in this, I'll create an npm module for it. Until then, you can link directly to the github project.

@plowman I mean cool, but, could have done a PR that implemented it for Android and in combo with iOS we're basically done here?

@mikehardy Sure, not opposed to trying to merge my changes into this project if that's something people are interested in.
Anyway, I figured changing this project would be a multi-week process in the best case (or you would reject my PR in the worst case), but I needed to hack together a fix sooner than that, so wanted to share for others who are in the same boat.

@plowman If it looks anything like the iOS version in PR right now - https://github.com/react-native-community/react-native-device-info/pull/817 - I will merge it as soon as I have time to review and the internet will grant you virtual fame ;-)

@plowman if you have time please look into making a pr for this.

Here's hoping this gets solved soon, I really need DeviceInfo.getUniqueID()

@mikehardy haha, well if internet points are involved... I might have time this week to put up a PR for Android. Can you confirm for me that the list of properties in #817 is comprehensive, i.e. does it list every property we want to expose as a constant? Or are there others?

If an android code change in harmony with the existing windows one and ios one appeared that would be insta-points and insta-merged yes :-). I believe that's all we want to expose now - however - just re-adding the constants infrastructure is the actual task. Easy to add to the list if needed to get the tension right

Current status is in #817 - last comments

Test it please https://github.com/react-native-community/react-native-device-info/releases/tag/v4.0.1-beta.5

4.0.1-rc.1 is out and the migration guide is up, unless bugs are found I will release it tomorrow
https://github.com/react-native-community/react-native-device-info/releases/tag/v4.0.1-rc.1
react-native-community/react-native-device-info/wiki/V3-to-V4-Migration-Guide
Please test it, and edits / improvements to the migration guide are always welcome.
Thanks!

I just noticed in the new release we are missing DeviceInfo.getDeviceType(); This is still a Promise currently.

I can see how that would be important for initial layout which is my loose criteria for constants, can you create a fresh issue for it for tracking? I can get it in a 4.0.2 for you as going from Promise to direct return is non-breaking for people I believe (where the other way is not)

@MakhouT you can try the @next tag to get 4.0.2-rc.1 with deviceType as a constant
https://github.com/react-native-community/react-native-device-info/releases/tag/v4.0.2-rc.1
I may need to release it as a breaking change v5 - I think removing the promise is breaking, but you can use it now at least

@MakhouT please report back on 4.0.2-rc.1

@mikehardy Thanks for the quick reaction! I haven't had time yesterday, I will try to test it this evening or tomorrow morning. I'll definitely get back to you!

@mikehardy Would it at all be possible to have getDeviceName exposed as a constant? (as in, anything impeding it from being a constant?). I'd imagine it should be pretty safe as (under normal circumstances) the device name shouldn't change between app launches?

getDeviceName is backed by bluetooth on android and can actually change any time, plus going in to that system has costs I'm unsure of but it isn't like a built-in system constant, I'm not sure on that one

Thanks for the explanation @mikehardy - that makes more sense as to why it is implemented that way.

@mikehardy Sorry that it took a bit longer than promised. I was able to test it and it works perfectly as expected! Thanks!
Any more chances we can take into V5?

Probably not, but I'm not afraid of major versions, I'm only afraid of accidentally breaking people in a non-major, so no need to wait much. I'll get this packed up and a v5 out probably by Monday

Perfect! Thanks!

@acro5piano submit a PR please, I can merge it in if it's got all the associated "stuff" (type files, README etc)

@mikehardy thank you for your work.
Just one question, a few folks mentioned it would be great if deviceName was available as a constant. Is there any specific reason not to have it?

good question - device name is not a constant in reality, it may change (e.g., rename your android in bluetooth), the API should reflect that - it is reality

good question - device name is not a constant in reality, it may change (e.g., rename your android in bluetooth), the API should reflect that - it is reality

Sorry @mikehardy , after re-reading above I noticed you had already replied to that question so I deleted my comment : )
I appreciate you getting back to me so quickly!
Anyway I understand the folks above difficulty as I'm facing it as well. The case is: Styling headers depending on device (making use of libraries like react-navigation). As you can't add the async wrappers or use state, you can't style the Header.
This is definitely not an easy one 😢

For those exact cases we have the Sync calls, but then you can't use the Chrome debugger. It's not an easy thing.
If it really is a fundamental need and you've got no valid workaround it is open source, patch-package makes carrying a local mod pretty easy and you can just add it to constants for your project, knowing that it may change in reality but you're willing to accept it in order for styling to somehow be based on a device name

Hey. I faced this issue today with the getFontScaleSync() method. Is it possible to detect if Chrome Debugging is running and either do this request or replace it with a self defined constant? That would help immensely.

No @AndrinGautschi - I really do not want to gum up the package with chrome debugger-not-chrome-deubugger code. We have sync methods, we have async methods, it's open source, use what you need to use for your use case, patch at will as needed please


Added new quickstart

Added new quick stats for Azure Cosmos DB: Build a MongoDB API console app with Golang and the Azure portal

@Durgaprasad-Budhwani,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@Durgaprasad-Budhwani, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@Durgaprasad-Budhwani : Thanks for your contribution to the Azure documentation! The author, @durgaprasad, has been notified to review your proposed change.

@mimig1
Hi Mimi This pull request includes new content for cosmos-db. Can your team work to move the content to the private repo and then close this pull request? Thanks.

@Durgaprasad-Budhwani Thank you for the new article, it's great. Give us a few days to review it, test it and pull it into our private repo for validation. We will be in touch.

Hi @mimig1 ,
Thanks for the update.
If you need working example, you can refer this link
Kindly let me know if you need any other information my side.
Regards,
Durgaprasad

@sivethe Please refer new pull request

@mimig1 - Can we get some update on this pull request?
Thanks in advance.

Hi @Durgaprasad-Budhwani - This is in my queue, I should get to it in the next few days.

I am pulling this into our private repo and will publish it from there, likely on Monday. When the file is merged in the private repo, this bug will get auto-closed.

Thank you @mimig1

Still in process in PR https://github.com/Microsoft/azure-docs-pr/pull/15133

@Durgaprasad-Budhwani I sent an email to your gmail acct with a copy for you to review.

@mimig1 Thanks for the email. It looks great.
Thanks for awesome work.


Feature request: hide "Choose media" button when field is declared readonly

Hi, I tried to use the Nova's MediaHubField as readonly() but it still show the button "Choose media". Was wondering if it's be possible to add this feature in a future release ?
Thanks!

Fixed with #44


chore: cleanup from splitting plugin-templates

What does this PR do?
Updates the repo to bring it up to standard with other salesforce CLI Plugins post-migration. Updates include:

Add gitconfig
Add bug/feature request/PR templates
Add "Run Current Test", fix "Run All Tests"
Fix debugging doc
Check that tests pass locally
Run basic test linked with sfdx plugins

What issues does this PR fix or reference?
@W-11309541@

Hey @randi274 👋  Could you do a search for salesforcedx and remove those references. One important one is the repository value in the package.json

You'll need to add all of the plugin's topics and subtopics in the package.json for the --help to work correctly. If you run bin/dev force --help the only (sub)topic that shows up is force:analytics. Here is an example of some nested topics.
FWIW, you don't need to worry about adding a longDescription, just description is fine.

Hey @iowillhoit 👋  Finally circling back to this one! Is there anything else you'd like me to add before merging this in?

Hey @randi274 👋 Could you please do a final round of QA on this? I will do the same and then I think we'll be good to merge!

Alright @iowillhoit things are looking groovy - did a follow-up sanity check and confirmed that we can:

Locally create apex and LWC using default templates
Link the plugin and create apex using custom templates

All good from my end!

Thanks Randi! Things are looking great on my end too. Approved and ready for merge.
QA Notes:
force:analytics:template:create
🟢 Able to create analytic templates (and set output dir)
🟢 JSON output matches
force:apex:create
🟢 Was able to create an Apex class with every available template (and set output dir)
🟢 JSON output matches
force:lightning
force:lightning:app:create
🟢 Able to create a lighting app
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
force:lightning:component:create
🟢 Able to create a lighting component
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
force:lightning:event:create
🟢 Able to create a lighting event
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
force:lightning:interface:create
🟢 Able to create a lighting interface
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
force:lightning:test:create
🟢 Able to create a lighting test
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
force:project:create
🟢 Able to create a project (with all templates)
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
🟢 force overwrites files changed
🟢 Allows setting namespace
🟢 Allows setting defaultPackageDir
🟢 Supports creating a manifest
force:staticresource:create
🟢 Able to create a project (with all templates)
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
🟢 Supports setting contentType
force:visualforce
force:visualforce:component
🟢 Able to create a visualforce component
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
🟢 Supports setting label
force visualforce page
🟢 Able to create a visualforce component
🟢 Able to set outputDir
🟢 JSON output matches
🟢 Detects identical files
🟢 Supports setting label


Title: COPYRIGHTS SECTION AT THE BOTTOM OF THE PAGE IS MISSING.

Initiative (Required)
GSSoC 2024 Extd 🚀
Is your feature request related to a problem? Please describe.
A COPYRIGHT SECTION IS NEEDED TO BE ADDED AT THE BOTTOM OF THE SCREEN FOR SECURITY REASONS.
PLEASE ASSIGN THIS ISSUE TO ME AND ALSO ADD THE LABELS OF hacktoberfest-accepted and gssoc-extd.
Describe the solution you'd like.
Adding the section would make the page more professional.
Add any other context or screenshots about the feature request here.
No response

I am the mentor of this project.
Hello @ABHISIKTAcommits
I appreciate your pull issue, can you give screenshots!!!

@SakiraAli1115 yes i'm sending the screenshot....

@Kushal997-das please assign the issue to me so that I can start working on the project asap...!!!

Hello @ABHISIKTAcommits ,
Since you’ve already opened issue #1449, please allow that to be completed and merged before opening any new issues. We will be closing this current issue for now.
Thank you for your understanding!


React.createElement: type should not be null, undefined, boolean, or number.

I'm trying to upgrade to v1.0.0 and I'm running into some really basic issues
    var MissingPage = React.createClass({
        render: function render() {
            return (

Missing Page!

Check your routing

            );
        }
    });

    var App = React.createClass({
        render: function render() {
            return (

                    {this.props.children}

            );
        }
    });

    var Index = React.createClass({
        render: function render() {
            return
Index

        }
    });

    let history = createBrowserHistory();
    var router = (<Router history={history}>
                    <Route path="/" component={App}>
                      <IndexRoute component={Index} />
                      <Route path="*" component={MissingPage}/>
                    </Route>
                  </Router>);

This generates React.createElement: type should not be null, undefined, boolean, or number. This is using react-router 1.0.0-rc3, react 0.14 and webpack. It appears Router is returning an Object instead of a Function?

You're importing something incorrectly, most likely Router. Most likely issue is that e.g. var Router = require('react-router'); won't work any more (though import Router from 'react-router' will).

I am having this same problem. This is my file:
/** @jsx React.DOM */
import React from 'react'
import ReactDOM from 'react-dom'
import Router from 'react-router'
import createBrowserHistory from 'history/lib/createBrowserHistory'
import routes from '../../lib/components/Routes.jsx'

let history = createBrowserHistory()

React.render(<Router history={history}>{routes}</Router>, document.getElementById('react-app'))

And I am getting these errors in browser.
Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components).Uncaught Error: Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

We're running an isomorphic app, and server side rendering has been upgraded to 1.0.0 and is working. This is the last bit and I can't figure out what's happening.

Does this mean we need to use an es6 compiler to use react router now?

No, you can use the standard require with CJS modules, along with React.createClass.

I would still need to use something like babel though...
Otherwise I get this error: Module build failed: Error: Parse Error: Line 4: Illegal import declaration

Use e.g. var Route = require('react-router').Route.

Ahhh, I see. Thanks.

Getting this same problem, but in the browser. Using:
var Router = ReactRouter
var Route = Router.Route

I'm running into this same error:
Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components).

My main code:
import React from 'react';
import ReactDOM from 'react-dom';
import {DefaultRoute, Route, Router} from 'react-router';
import createBrowserHistory from 'history/lib/createBrowserHistory';
import {About, LeaderboardPage, Profile, TopNav, Validate} from '../components';

var App = React.createClass({
  displayName: 'App',
  propTypes: {
    className: React.PropTypes.string,
    contentClassName: React.PropTypes.string,
    navClassName: React.PropTypes.string
  },
  getDefaultProps: function() {
    return {
      className: 'data-validation-tool',
      contentClassName: 'data-validation-tool-content',
      navClassName: 'data-validation-tool-navbar'
    };
  },
  render: function () {
    var props = this.props;

    return (

          <TopNav />

          {props.children}

    );
  }
});

let browserHistory = createBrowserHistory();
ReactDOM.render((
  <Router history={browserHistory}>
    <Route path="/" component={App}>
      <DefaultRoute component={About} />

      <Route path="about" component={About} />
      <Route path="leaderboards" component={LeaderboardPage} />
      <Route path="profile" component={Profile} />
      <Route path="validate/:projectId" component={Validate} />
    </Route>
  </Router>
), document.getElementById('app'));

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router.
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.

This solved my issue: https://github.com/rackt/react-router/issues/1799

have you export your component?

don't use React.createClass, please try "extends Component"

https://codereviewvideos.com/blog/warning-react-createelement/
Check this out.

For future googlers who come across this error, by upgrading from 0.24 -> 0.26 react-native
Check if:
"export default class"
is changed to:
"export class".
And a name has been defined in the class.
Also I refer to the release: https://github.com/facebook/react-native/releases

Hey guys, how are you?
So I've a problem with react-router. The version v3.0.0 not support Router.run ? I did upgrade react v13 to v15 and react-router v0.3.* to v3.0.0. There is a workaround to problem? below has code!
// write files
`const write = (pathname, applicationMarkup) =>
(filePath => {
fs.writeFileSync(filePath,
  formatHTML(
    rawHTML(pathname.substr(1).replace(/\//g, '_'))
      .replace('__APPLICATION__', applicationMarkup)
  )
);

})(path.resolve(${__dirname}/../dist${pathname}/index.html));`
// make files
const makeHTML = pathname =>   Router.run(     routes, pathname, Handler =>       write(pathname, useReactRenderToString           ? React.renderToString(<Handler />)           : React.renderToStaticMarkup(<Handler />)       )   );
// this is my array
['/s',   '/s/guest',   '/s/login',   '/m',   '/m/guest',   '/m/login', ].forEach(makeHTML);


ExcelPainter: format_name in paint_box for totalsum views incorrect...

... when there are more than one total sum views and they are grouped (possibly with dummy too).

Resolved by #418.


Prefetch client

A basic prefetch function in client.rs and one test.
Also updated the prefetching buffer to handle a return of "None" from the database. The buffer handles None by changing the key state to "Fetched" and leaving the buffer without a value for the key (i.e. matching the database).
Note that there is something funky with the prefetch_test in that it passes when run by itself but sometimes fails when run in conjunction with the other tests due to a "connection refused" issue. I suspect this is due to an address conflict issue with the other tests but will have to debug further.

@tamer-eldeeb I'm not sure how to not wrap the proto_client in a Mutex because technically it can be concurrently accessed by multiple threads. It also avoids a prefetch using the client before the connection is available.


Searching by ENS is giving a "Bad input" as response...

Dunno if going to be implemented later, just not working so reporting it.. :-)

Mainnet ENS names are not mirrored on Goerli testnet. If the ENS is not registered, it will error.


Flights CSV import fails if no distance stipulated

Import of Flights fails if no distance value is stipulated.
Given this is marked as a non required field, this seems like a bug
Valid Work around: enter a value of 0.
NOTE: Distance is not automatically calculated if value is 0.

Is the field in the CSV being omitted or just blank?

blank

Should be fixed in latest dev


Revert "Update KSCrash dependency"

Reverts ably/ably-cocoa#981
@QuintinWillison This broke the build:
❌  /Users/vagrant/git/Source/ARTSentry.m:19:9: 'KSCrashAblyFork/NSData+GZip.h' file not found
#import <KSCrashAblyFork/NSData+GZip.h>
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I'm reverting it pending a fix.

Bitrise: ✅

Superseded by #988.


please keep this version up with the core version

The core version is 3.32 now, but this is still 3.31

Current version is v3.32, maybe you can try brew upgrade v2ray-core to upgrade version.