Why is the n of hoist not a monad?

I mean, why
hoist :: Monad m => (forall a. m a -> n a) -> t m b -> t n b

instead of
hoist :: (Monad m, Monad n) => (forall a. m a -> n a) -> t m b -> t n b

?
I've stumbled upon that trying to implement MMonad in terms of this function.

Here's another one: the free package defines
hoistFT :: (Monad m, Monad n) => (forall a. m a -> n a) -> FT f m b -> FT f n b
hoistFT phi (FT m) = FT (\kp kf -> join . phi $ m (return . kp) (\xg -> return . kf (join . phi . xg)))

If there's a way to weaken that to Monad m, I haven't been able to find it. I suspect the "work from the inside out" approach may be defeated by this Yoneda-style type.

@treeowl: Yeah, for the efficient implementation you require the Monad n constraint.  In theory you can still do it inefficiently by converting to Control.Monad.Trans.Free.FreeT and then converting back
The problem is that adding the Monad n constraint breaks the Control.Monad.Trans.Compose module

I don't think you can convert back.
On May 21, 2017 10:36 PM, "Gabriel Gonzalez"<EMAIL_ADDRESS>wrote:

@treeowl https://github.com/treeowl: Yeah, for the efficient
implementation you require the Monad n constraint. In theory you can
still do it inefficiently by converting to Control.Monad.Trans.Free.FreeT
and then converting back
The problem is that adding the Monad n constraint breaks the
Control.Monad.Trans.Compose module
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Gabriel439/Haskell-MMorph-Library/issues/11#issuecomment-302985407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzi_TaXl1X99SN6VnAPQQD2LcmJEKVQks5r8PSVgaJpZM4BhqFj
.

You can, using Control.Monad.Trans.Free.Church.{toFT,fromT}, but I just realized it still doesn't work anyway because you still need the Monad n constraint for toFT

The problem is that adding the Monad n constraint breaks the Control.Monad.Trans.Compose module

While this isn't quite complete, one option is to use constraints:
instance (MFunctor f, MonadTrans f, Lifting Monad g, MonadTrans g) => MonadTrans (ComposeT f g)
  where
    lift :: forall m a. Monad m => m a -> ComposeT f g m a
    lift = ComposeT . hoist lift . lift   \\ (lifting :: Monad m :- Monad (g m))

This requires a Lifting instance for each inner transformer. While that's unfortunate, I'm not convinced that it's more unfortunate than failing to support FT from free. There is even some cause to hope that GHC may eventually be able to provide built-in support for Lifting thanks to recent research on implication constraints.

@treeowl: There's yet another issue, which is that adding a Monad n constraint will break the use case that fixing #29 was designed to solve (i.e. the case where n has kind k -> *).  Adding the Monad n constraint would force k to be *, defeating the purpose of making the class poly-kinded

I don't understand what this polykinded thing has to do with monad
morphisms. The rmap example seems a bit silly, since hoist is already
too restrictive to do everything rmap can.
On Thu, Aug 24, 2017 at 10:34 PM, Gabriel Gonzalez<EMAIL_ADDRESS>
wrote:

@treeowl https://github.com/treeowl: There's yet another issue, which
is that adding a Monad n constraint will break the use case that fixing
#29 https://github.com/Gabriel439/Haskell-MMorph-Library/issues/29 was
designed to solve (i.e. the case where n has kind k -> *). Adding the Monad
n constraint would force k to be *, defeating the purpose of making the
class poly-kinded
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Gabriel439/Haskell-MMorph-Library/issues/11#issuecomment-324808288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABzi_dN5kINPOb87S4jtMUvVMD5K1WYyks5sbjKbgaJpZM4BhqFj
.

Either way, adding the Monad n constraint would be yet another a breaking change due to previously enabling PolyKinds
I also would still like to keep the constraints on the use of hoist as small as possible

Actually, even without considering PolyKinds adding the Monad n constraint is still a breaking change to the API (since there may be some call sites in the wild where n is not a Monad)

I just stumbled over the mmorph example. Even if you implement, as suggested this function:
unviewT :: Monad n => ProgramViewT instr n a -> ProgramT instr n a
unviewT (Return a) = return a
unviewT (instruction :>>= continuation) = singleton instruction >>= continuation

...you still need the Monad n constraint on the target monad. I'd like to use mmorph and add an MFunctor instance, but unfortunately like this it won't work. Can we reopen and reconsider?

@turion: I believe you can implement MFunctor for ProgramT, like this:
instance MFunctor (ProgramT instr m) where
    hoist nat (Lift   m) = Lift (nat m)
    hoist nat (Bind m f) = Bind (hoist nat m) (\x -> hoist nat (f x))
    hoist _   (Instr  i) = Instr i

I have not type-checked that, though

You are right indeed! Thank you very much.

You're welcome! 🙂


Dynamically reload bot

Is there a built-in way to reload the bot (without having to kill the ruby process and start a new one)? I'd like to test my code, but I'm getting klined due to rapid reconnects. Not ideal.

My super hacky way to get around this is to use irssi as a proxy between my testing bot and the network.  I used this blog post to get the proxy running, and then pointed my bot to the proxy with the password attached.
http://chriscarey.com/wordpress/2009/07/18/irc-with-irssi-proxy-screen/

Heh, that's an original way of doing it. Now I almost feel bad for actually implementing reloadability for Cinch :)

Oh hey, I'm not complaining!   That's awesome!

Oh snap. Coming out soon, is it?

It'll likely take some more time, as the next release will be a new major version.

Cool. I can wait.
On Oct 27, 2011, at 17:07, Dominik<EMAIL_ADDRESS>wrote:

It'll likely take some more time, as the next release will be a new major version.
--
Reply to this email directly or view it on GitHub:
https://github.com/cinchrb/cinch/issues/15#issuecomment-2549426

@dominikh is your gist still applicable? There is a Fixme section I am hoping you can elaborate on how to solve.

The gist is still applicable and the latest version. The fixme refers to the fact that plugin options in Cinch are represented in a hash, mapping classes to options. Deleting the class and creating a completely new one would break that mapping (plugins would lose their configuration). The downsides (not removing methods, not being able to change the superclass) don't usually come up a lot in practice, in my experience.
Personally, I have long switched to a different model, where something like znc proxies the bot, allowing you to restart the bot without users noticing. It's a far simpler approach.


Bundle step keep failing to install fastlane

We are facing a problem with the new release of fastlane step 2.5.0
Our Bitrise Xcode is 10.2 which is using the bundler 1.17.3 and ruby 2.5.3.
After updating bitrise step we get an error that must user Bundler > 2.0 after updating the GemFile.lock to Bundle 2.0.2 we get another error
Install Fastlane with bundler $ bundle "_2.0.2_" "install" "--jobs" "20" "--retry" "5".

Hi @georgehadly-marleyspoon could you please include the related build URLs?

update to Bundle 2.0 issue -> https://app.bitrise.io/build/ef85ca6bcb840e8e#?tab=log
installing fastlane issue with bundler 2 -> https://app.bitrise.io/build/b735f6641ed6dda9#?tab=log

Thanks!
Just so you know the the issue on the 2.4.0 can be workaround by placing this script before the fastlane step:
#!/bin/bash
set -ex
gem install bundler --force

For the issue with the new version, could you contact us on our on-site chat and send us your Gemfile.lock and Gemfile from your repo? It could also help to run this script in the failing build: https://github.com/rbenv/rbenv-installer/blob/master/bin/rbenv-doctor

Hi @georgehadly-marleyspoon ,
There is a new version of fastlane-install available (2.5.1):
https://github.com/bitrise-steplib/steps-fastlane/releases/tag/2.5.1
Bundler is installed before executing bundle install, in case a Gemfile.lock is present. The specific version defined in the Gemfile.lock under BUNDLED WITH is installed and used to run the bundle install command.
The issues fixed include the error messages printed during build:  rbenv: bundle: command not found
and You must use Bundler 2 or greater with this lockfile.
The fix is also available in:
cocoapods-install  (https://github.com/bitrise-steplib/steps-cocoapods-install/releases/tag/1.8.0)
deploy-to-itunesconnect-deliver (https://github.com/bitrise-steplib/steps-deploy-to-itunesconnect-deliver/releases/tag/2.16.0)

Thanks for the update :)

FYI - this also solves issue "Could not find 'bundler' (1.17.3)"
in " ios auto provision" step

Hey @abdullah-s , thanks for the info and for sharing! 😉


build: Add plugin to check conventional commit message format

Changes description
Add commit checker plugin https://github.com/nicolasfara/conventional-commits
It is based on this https://www.conventionalcommits.org/en/v1.0.0/#summary
Examples of success commit
"feat(buttons): Add a new size for buttons"
"fix: Fix all ui tests"
Example of fail commit
"new: Add my new feature" ( not a conventionnal type )
"feat(button): Add a new size for buttons" (  button instead of buttons is not one of our modules)
": New feature" (no type)
Context
Keep a conventional & consistent format in our history.
Checklist

x ] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.

You can download the apk here :
sample-debug.apk :
https://app.bitrise.io/app/e9ae480151be4514/build/336387c5-46cf-479a-a998-2d401827e9f8/artifact/b15a419871130334/p/05584c5bbf982aea2544f255d02243ed

You can download the apk here :
sample-debug.apk :
https://app.bitrise.io/app/e9ae480151be4514/build/485e085c-9f87-4d37-8e7d-f16b02a1a94c/artifact/ef82b4dbd7a2b89a/p/b0c7f0a5582353798899716ef1b29f1d


File Location text runs over other text in settings title

See image. File Location path overwrite other text

Closing as this has been entirely redesigned


Feat/async rework

Codecov Report

Merging #122 (2cf9c64) into develop (a003fbd) will decrease coverage by 0.64%.
The diff coverage is 35.29%.

:exclamation: Current head 2cf9c64 differs from pull request most recent head 1c3730a. Consider uploading reports for the commit 1c3730a to get more accurate results

@@             Coverage Diff             @@
##           develop     #122      +/-   ##
===========================================
- Coverage    59.53%   58.89%   -0.65%
===========================================
  Files           33       30       -3
  Lines         1389     1299      -90
===========================================
- Hits           827      765      -62
+ Misses         562      534      -28

Impacted Files
Coverage Δ

...nnect_for_snmp_poller/manager/mib_server_client.py
29.03% <20.00%> (+0.08%)
:arrow_up:

splunk_connect_for_snmp_poller/manager/tasks.py
38.66% <38.46%> (+1.68%)
:arrow_up:

..._connect_for_snmp_poller/manager/task_utilities.py
22.56% <45.45%> (+0.08%)
:arrow_up:

splunk_connect_for_snmp_poller/manager/poller.py
0.00% <0.00%> (ø)

..._for_snmp_poller/manager/realtime/interface_mib.py
98.03% <0.00%> (ø)

...for_snmp_poller/manager/realtime/real_time_data.py
88.46% <0.00%> (ø)

...mp_poller/manager/validator/inventory_validator.py
95.23% <0.00%> (ø)

...nect_for_snmp_poller/manager/data/event_builder.py

... and 4 more

Continue to review full report at Codecov.

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

:tada: This PR is included in version 1.5.0-develop.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Revert "[network] migrate to simple discovery"

Looks like validators are not connecting in cluster test (see #network), and since this is only networking PR that was merged while we had land-blocking cluster test disabled, this is top suspect
Still confirming if reverting this PR make things work again, but I think possibility is strong

oh gosh, we probably shouldn't have pushed the smoke test refactor PR in with land blocking off...

@bors-libra r+ p=1000
Confirmed that cluster test passes with this revert
I think my learning for future is that I will try to fix cluster test(even if it means blocking pipeline for short duration), otherwise it's just too dangerous. Good thing we did not have merge conflicts on revert (although, we are not merged yet :D )

:pushpin: Commit 401859e has been approved by andll

:hourglass: Testing commit 401859e24750339efd0654c6b9a7e6db2aab1239 with merge b04c7cd4d786861377cc34ae4e98413e6bc42732...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: andll
Pushing b04c7cd4d786861377cc34ae4e98413e6bc42732 to master...


Factor out loop label parsing

Currently we parse labels as lifetimes, then always need to do lt.map(|lt| lt.ident). Let's factor this into a separate label parser.

Fixed in 8b07f37e6b28d57c3688a16b61293936a573f9c5. @gregkatz this may be useful to you.

Definitely useful. Thanks, @dtolnay. I'm working on a PR for break, continue and return. Hoping to get that in tomorrow.


Docs: More details about az_log_set_classifications()

Closes #1227.
Closes #1192.
I don't think there is much more we can do for #1227.  We still can - maybe we can have a local copy of an array of some finite size, and copy elements there, but besides that I don't see much options. az_log_set_classifications() would need to return az_result in this case, if the limit is exceeded. Then, if you want more than the predefined limit, one of the options is to pass NULL to receive all classifications, and filter them out in log callback, which does receive classification in addition to message.
I had two solutions in mind:

Use mutex, and lock it when setting classifications, and while iterating over them. I do not think it is possible, given that az_log is used by IoT, and mutex is in PAL, and we don't want the dependency on PAL for the IoT scenarios.

If we know all the possible classifications, make some sort of a map of classification -> bool is_enabled, and use that internal copy; this would also have some perf benefits as side effect. But given that we now extracted IoT classifications from core into a file in the iot directory, I do not see a realistic good and simple way of doing this anymore.

I think I might give this whole idea another shot in the next sprint, I put more details in the PR description (local array copy of a finite size + returning az_result when limit is exceeded); so maybe after all we will be able to safely handle stack-allocated arrays.


Requesting angular cdn not working

Hi,
After typing Ctrl-alt-c, selecting Angular.js and typing 1.4.8, the following appears:

and when you press enter you see:

and this does not work

I guess the reason may be the changes of "filename" in angular.js, @thomasdavis what do you think?

I can't replicate this error and it seems to work well with 2.x.x

@MickelSierra85 do you still have this problem?


Add metadata to layers

This attaches Axon specific metadata to layers in the form of the op_name. This allows backends and compilers to match specifically on these patterns if they're available and provide optimized versions of layers rather than depending on the lower-level Nx implementation.

@seanmor5 it should be good now :)

FWIW, the failing tests should be fixed by using Nx.all_close or similar. :)


Add compaction.failed event

Actually, as it has now been decided (for a better browser support) to remove imports of native node modules, including node:events for EventEmitter.
An option could be to shim EventEmitter with a package or the browser's EventTarget, but nedb is not very event-oriented, it is not worth it.
Therefore, the compaction.done event will be replaced with an onCompaction: (err?: Error|null) => void callback, which can be used by users to shim a 'compaction.done' naively, which will provide an error if any is thrown during compaction.


Memory Leak in LibreOffice

I'm using unoserver/ unoconvert to convert bulk files to JPG format using Docker.
I have a large number of files that need processing so my server is always up and running, converting each file one by one sequentially. However, after 2-4 hours of work, the conversion processes start getting stuck, and then soon the whole docker container is down, and I have to manually restart it.
When checking the memory while it was stuck I found that the process soffice.bin holds 10GB of memory.
The unoserver starts automatically with the container starts, then I only call unoconvert command for each file.
I'm thinking that maybe LibreOffice is not releasing the files after loading and converting them.
I looked through the README again to see if there's a configuration I can set that will allow me to free up memory after each conversion, but I didn't find any.
Is there a way to implement that?
Thanks and regards.

LibreOffice should release the memory, if it doesn't that's a LibreOffice bug.
It seems to me this can be triggered by documents that fail to convert, sometimes. If you can find specific documents that trigger this you could probably file a LibreOffice bug report.


Question about correctness of Domain Accuracy

Hello everybody, we are currently examining different DA method and tried to reproduce the SDAT paper results on our system.
So far I have made two trainings with all the settings and arguments I could gather from the paper for DomainNET. The val_acc do look quite promising:
real->sketch:

sketch -> clipart

However, the Domain accuracy is somewhat confusing for us (not smoothed):
real->sketch:

sketch -> clipart:

We would have expected a graph similar to this one from the paper for the Domain Accuracy:

However, it seems this was done with the Homeoffice dataset and different settings. Question is now, can we assume that our results are correct?

Thanks for your question.
The Domain accuracy fluctuates as it's adversarial training (i.e. discriminator will try to increase the domain accuracy, whereas the feature extractor will decrease it).
In the DomainNet cases you have mentioned, you can observe the mean value of SDAT is similar to the plot provided by us. However, the fluctuations are function of dataset, hence can change with dataset and settings.
Hence, in my view the results produced by your experiments are correct in my opinion.
Thanks
Harsh


adds reduce_sum and tests

Summary
This adds a reduce_sum and reduce_sum_static function to stan math that chunks up a functions arguments and then applies the function with a sum reduction in parallel.
Tests
Tests exist for prim, rev, and mix and can be run by first setting STAN_THREADS in make/local to true and then calling
STAN_NUM_THREADS=4 ./runTests.py -j4 ./test/unit/math/ -f reduce_sum

Side Effects
None
Release notes
Adds a reduce_sum functor that performs a parallel map reduce over a function.
Checklist

[x] Math issue #1616

[x] Copyright holder: Sebastian Weber, Columbia University
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

@bbbales2 it looks like the static and regular tests only differ in calling reduce_sum_static and reduce_sum, is it okay to just combine the two? That would cut out like 800 lines of code.
Also do we want auto_partitioning to come in as a template parameter? It looks like it's set constant anyway and that will  let the compiler clean up the dead code of the if in operator()

@bbbales2 it looks like the static and regular tests only differ in calling reduce_sum_static and reduce_sum, is it okay to just combine the two?

I kept them in separate files so that it's easier for someone to find the tests (since we mostly do these things individually).
Sort of in the same spirit that there would have been a more compact way to write all the tests we have, but it's just easier to figure out exactly what blew up when they're broken apart.
Your call what you wanna do. I felt the same way as you, but just went with copy and paste for the reason above.

Also do we want auto_partitioning to come in as a template parameter?

There's gonna be no performance hit, and I think regular C++ is easier to read.

I changed copyright holder to Columbia Uni for Ben, but I'm not sure what the deal is with copyright on things Steve does.  Do you know, @SteveBronder?

I'm not sure but I'd bet it's either me or columbia so as long as columbia is up there it should be fine

Cool! Will review this soon. Do we have a proper issue for this already?

Will review this soon. Do we have a proper issue for this already?

Nah, you could make one and point it at the design doc I suppose.
Come up with any names other than reduce_sum_static or reduce_sum_deterministic?

Merging prim and mix's tests for static and normal together deleted like a 1000 lines of code. I think that's a reasonable tradeoff

That's a pretty wild error

g++ -std=c++1y -m64 -D_REENTRANT -Wall -Wno-unused-function -Wno-uninitialized -Wno-unused-but-set-variable -Wno-unused-variable -Wno-sign-compare -Wno-unused-local-typedefs      -I lib/tbb_2019_U8/include -O3  -I . -I lib/eigen_3.3.3 -I lib/boost_1.72.0 -I lib/sundials_5.1.0/include -I lib/gtest_1.8.1/include -I lib/gtest_1.8.1   -D_USE_MATH_DEFINES  -DBOOST_DISABLE_ASSERTS             -Wl,-L,"C:/Jenkins/workspace/Math_Pipeline_PR-1813/lib/tbb" -Wl,-rpath,"C:/Jenkins/workspace/Math_Pipeline_PR-1813/lib/tbb"  test/unit/math/mix/meta/scalar_type_test.o lib/gtest_1.8.1/src/gtest_main.cc lib/gtest_1.8.1/src/gtest-all.o lib/tbb/tbb.dll  -static-libgcc -static-libstdc++       -o test/unit/math/mix/meta/scalar_type_test.exe

test/unit/math/mix/functor/reduce_sum_test.cpp:481:1: internal compiler error: Segmentation fault
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See http://sourceforge.net/projects/mingw-w64 for instructions.

I'm gonna break the mix up into two functions to see if that helps

Oh yeah, that file is definitely too big for the Windows g++ 4.9.3. We had this issue in the flatten.
I have a windows machine next to me. Want me to split it so you dont stab in the dark?

I can probably get it, unless you think it's v confusing then I'd be happy for the assist! Is the issue just thatI'm running too much in each test or there are too many tests in each file?

Too many tests in a file and its really hard to find (guess) where the actual limit is.
For that reason we have log_mix_part1_test and part2_test in https://github.com/stan-dev/math/tree/develop/test/unit/math/mix/fun

hmm, I think we can just cut the file in half and it's fine. lemme give it as shot

Ugh actually @rok-cesnovar would you be able to give me a hand with this?

Ah. I forgot: Do we have tests in place which check that we get 0 for the case of an empty vmapped argument? We need that for the double and var case.

Here is the benchmark example which just helped me to uncover that we do not turn up parallelisation with reduce_sum due to not picking up the right specialisation. I am not sure where or how to put it. Maybe the example-model repo (but it is really a fake example)?
I did cast things into "txt" ...
sample-oral_2cmt_sh.txt
oral_2cmt_stan.txt

@SteveBronder I had to split it in four files (lol). Rtools 4.0 cant come soon enough.

Can we maybe add a test which makes sure that we actually use multi-threading? Here is how I would suggest to do that:

use an example which uses log-gamma function calls
time execution clamped to just 1 thread
time execution with maximal concurrency of 4 cores
test if the execution time was at least twice as fast - to give this some extra grace time in case the machine is busy.

You can use a task_arena to control the number of threads like this:
tbb::task_arena single_thread(1);
tbb::task_arena multiple_threads(4);

single_thread.execute([&]() {
  // call task to time
});

multiple_threads.execute([&]() {
  // call task to time
});

the TBB probably has facilities to time stuff. If you could please add such a test, then do one commit where the reverse model overload will not be included so that the test will show failure, and then switch back to enabled parallelism, then we are good.
Does that sounds sensible?

Ah, and I forgot: The current version does run things in parallel again. The benchmark runs nice and fast with reduce_sum.

the TBB probably has facilities to time stuff

Mmm, a performance test probably goes with those downstream things that run at the end.
But we could add a couple asserts to the fully templated reduce_sum_impl that'll throw errors if it gets a set of arguments that are purely arithmetic or include vars (cuz these should go to the other specializations)

Maybe another way we could verify threading is happening is have a reducer function that writes thread ids to a global variable? Do you know how to get thread ids?

I think a timing test in the math lib test suite sounds dangerous. We can add it to the cmdstan performance tests suite (a model with data). We can also track regression/improvements over time.

I agree, a timing test is not ideal.
Using a global variable can work, yes. You can get the a thread id via: https://en.cppreference.com/w/cpp/thread/get_id
but what would be easier is to use this probably:
tbb::this_task_arena::current_thread_index()
this returns an integer in the range 0 - max_concurrency-1.
Thus you can create a reducer function object which has a static member for which you register in a vector of length max_concurrency if the respective index turns 1 which you do when the operator() of the functor is called. We should use the reduce_sum_static for that as you then know that you create a number of tasks.
Better?

I moved the generic version of reduce_sum to fwd so it won't get used if someone only has rev or prim included and those implementations aren't available.
I put #ifdefs around the threading tests so they turn off when this is built without threading.

I changed reduce_sum_static so that:

With threading, each partial sum in the reduce is of length less than or equal to the grainsize
Without threading, everything is computed in one partial sum.

Is this ready for review again? Tests seem to pass which is cool.

Yup, go for it. I added some #ifdefs to the test to handle the threading vs. non-threading stuff.

Ah.. and the release notes sections needs an update as we also add reduce_sum_static.

static_check is here: https://github.com/stan-dev/math/pull/1813/files#diff-361fc33970963952845de9f860dac64dR105

Moreover, could you please change that static_check_lpdf operator() so that it always just adds 1. Then you can test for the returned sum being equal to the number of splits which you expect. This can be done for 2-3 grainsizes. This test should be run for the prim and the rev code.

I don't think we need these extra checks. What we're checking right now makes sure that the work size is less than or equal to grainsize, which is what the tbb says it will do. I think any checks from then on would be tbb implementation dependent or whatever.

I dont want to revive the old Discourse topic so asking here.
What model and data would you suggest for a test model we can let users test and run? I want to try out a AMD threadripper on a remote machine I got access to. I can make a cmdstanr test script for a bit of PR :)

Here is a test model to test the scaling:
https://github.com/stan-dev/math/pull/1813#issuecomment-607847579
This is what was run and demonstrated in the discourse thread.
Generally I don't expect any user to test this... but for those power users who want to play, the above model is good as it calculates analytically, with a matrix exponential or ODE solver. That can be done with map_rect or reduce_sum.
Are u suggesting to include performance info in this PR? If so, then we should copy over results from discourse which are very comprehensive.

Are u suggesting to include performance info in this PR?

No no, just want to try it out on a beefier machine and make a script for any power user that wants to try this out. Kind of like a demo.
I think the speedups were checked deep enough by everyone so no need to add more.

I also have R scripts written which runs my example on the back of batchtools. This is an R package which can dispatch the work to a number of backends - including multi-core machines & clusters. Do you want to have a look at that? Only with these R scripts I was able to create comprehensive comparisons.

Well I added the std::forward calls but I think that was a mistake so I removed them again and then I thought I saw a way to add them again so I added them again.
std::forward acts like std::move for rvalues, so I think it's only safe to do one forward after you're done with the variable. In this case the forwards were used on the later functions: https://github.com/stan-dev/math/pull/1813/files#diff-8283b21f45f7557cada3e4da4bc636b6R232
So I just swapped those save_varis calls to be before the recursive_reducer constructor so the recursive_reducer constructor would get to use the forwarding.
But still is this really safe @SteveBronder ? Like, we pass things into the constructor of that recursive_reducer, but then if that object gets destructed then the memory attached to those variables (if they were rvalues going in) would get freed.
TBB makes copies of the first recursive reducer to get the other reducers, but I don't think we know that it won't deallocate that first recursive reducer before it calls operator() on another one?

TBB makes copies of the first recursive reducer to get the other reducers, but I don't think we know that it won't deallocate that first recursive reducer before it calls operator() on another one?

But we are constructing a recursive_reducer ourselves and give that to the TBB reduce. Thus, recursive_reducer which we feed with the forwarded stuff will always be in scope and will not be deallocated during the life-time of the use of this object.
It would be good if @SteveBronder can comment. I understood that forward just keeps rvalues and lvalues as to what they are; thus I would have expected that we can use forward twice on a given argument, since it just maintains the reference to the object in the form given to the function.

But we are constructing a recursive_reducer ourselves and give that to the TBB reduce. Thus, recursive_reducer which we feed with the forwarded stuff will always be in scope and will not be deallocated during the life-time of the use of this object.

@wds15 aaaah, good point

But still is this really safe @SteveBronder ? Like, we pass things into the constructor of that recursive_reducer, but then if that object gets destructed then the memory attached to those variables (if they were rvalues going in) would get freed.

Sebastian is right here, that first reducer is made and the data is stored then and deleted once it leaves scope. If we did something like return a promise from reduce_sum_impl::operator() then it would get weird but the same is true for any reference type we used.

But we are constructing a recursive_reducer ourselves and give that to the TBB reduce. Thus, recursive_reducer which we feed with the forwarded stuff will always be in scope and will not be deallocated during the life-time of the use of this object.

It would be good if @SteveBronder can comment. I understood that forward just keeps rvalues and lvalues as to what they are; thus I would have expected that we can use forward twice on a given argument, since it just maintains the reference to the object in the form given to the function.

Forward treats lvalues as not movable and rvalues as movable. That means for rvalues, if the object has a move constructor defined it will move ownership of the original object's memory and leave the initial object in a valid but unspecified state. That means you only want to forward once you don't need the original object anymore.

@SteveBronder Then we're good to go? The current version does a single forward per argument: https://github.com/stan-dev/math/pull/1813/files#diff-8283b21f45f7557cada3e4da4bc636b6R223

I'll give it all a review rn

I am running over night the big benchmark once more. If that turns out to look good, then I will approve and merge unless @SteveBronder (or someone else) finds a showstopper.

@wds15 sooner the better. We should all move on to trying to break @rok-cesnovar 's branch: https://github.com/stan-dev/stanc3/pull/451#issuecomment-610004920

All looks good just added a could little things https://github.com/stan-dev/math/pull/1813/commits/ad02fdf2ff2f9a6efba5867c055172ff1ba3d496
One thing, I added export STAN_NUM_THREADS=4 to the jenkinsfilef or linux (accidentally added it for windows but removed it.

Merge when the tests pass @wds15 wooooo

Grr... I had to find out that the benchmark crashed over night, as I had grainsize=0 which is now blocked (correctly) from the reduce_sum function. Rerunning it... ~5h from now it should be done...

Well... our cluster is apparently busy and I am not getting results as fast as I would like to. Below is a comparison of map_rect and reduce_sum. To me this looks all good. No need to wait any longer (seems like people want to submit large chunks of stuff before the holidays):

Approving...


Trio support

Hey, thanks for this awesome looking library. I'm investigate the feasibility of using it on one of my projects and I see that pyee supports asyncio and twisted for async capabilities. I am wondering if there is any motivation to also support the trio library:

https://trio.readthedocs.io/

I'm relying on the trio async streams implementation and I'd also like to be able to plug on this event emitter class onto my stream. What do you think?

I'm down to support the trio library. I thought trio's Futures were naively compatible with asyncio's - is that not the case?
If you want to sketch out what trio support would look like (aside from what exists now), I can help iterate on the ideas and give adding support for it a shot. Otherwise, if you want to take a crack at it and just PR what you want here you should be able to do something similar to the asyncio EE which subclasses the BaseEventEmitter and adds special handling around the result of a handler function.

I did some quick research, it looks like the necessary abstraction is called a nursery. Adding support for this looks relatively straightforward.

more research, unlikely to actually bang this out tonight but I can at least get my notes here
so the nursery is def the correct abstraction, though it should be noted that nurseries are async contextmanagers - so I could potentially make TrioEventEmitters also async contextmanagers. this would be loosely similar to how ExecutorEventEmitters optionally use sync contextmanagers. cool beans!
and here's how I can sense the event for the tests:

Between these, this sounds like a few hours of work. I can probably hack this up sometime over the weekend!

Thanks a lot! I'm trying to catch up on the discussion in the trio gitter and that was pretty helpful to understand why this is also perhaps not the correct approach to what I want to do. Since the asyncio streams people and trio streams people are collaborating closely, I am inclined to listen to their thoughts about structure ;) I am wondering perhaps now if I shouldn't just close this off and save you the work! Perhaps this is just a docs issue!?

it's true that an EventEmitter might not be the best solution to your problem, though I can't really tell you that either way. I would need a lot more information about your use case, and probably greater familiarity with trio, to tell you either way.
all that said, please keep this issue open. I actually thought trio's interop with asyncio was a lot tighter (meaning this exposed a use case I wasn't aware of) and I'm totally down to implement even if it's "non-idiomatic". like I said in the gitter, I don't really care about dogma and I don't have a horse in this race.

I'm not into the dogma either but there is some stream gathering around this idea of structured concurrency now and I want to find the surest path for my work that won't have me re-writing all the things.
OK, let's keep this open :+1:

https://github.com/jfhbrook/pyee/pull/62


Sonos

I too have several Sonos speakers and would like to use them as my Alexa speaker. I would also like to be able to control the Sonos system from AlexaPi to request music, stations and books. Can you share your code you use to control your Sonos speaker system and/or include it in 1.1 or 2.0 as an option for those who have Sonos?

Yep the sonos output code should make it into a release soon, I just need to refactor the code into smaller more manageable files so it doesn't get too huge!
I'm not sure yet if it will be possible to send the music output to sonos or if that would need to be done via a skill.


gradient tests for inn.ROIPooling, nnf.ROIPooling; also comparison of their outputs

my crude implementation of the Jacobian check for nnf.ROIPooling and inn.ROIPooling.
I made the following not so comfortable choices but not sure if there were any better solutions.

nnf.ROIPooling.lua is copied from the object-detection.torch project/fast-rcnn branch for comparison.
In order to use nn.Jacobian for Gradient testing, I had to subclass both ROIPooling methods such that the subclassed forward()/backward() take single input tensor instead of {input,ROI}.

Some observations running test_jacobian.lua

SpatialSameResponseNormalization fails. (same failiure in master branch as well).

tingfan@UmboMars:~/dnn/imagine-nn/test$ th ./test_jacobian.lua
Running 3 tests
_*_  ==> Done Completed 10 asserts in 3 tests with 2 errors
--------------------------------------------------------------------------------
SpatialSameResponseNormalization
error on state
 LT(<) violation   val=nan, condition=0.001
	...tingfan/dnn/torch/install/share/lua/5.1/torch/Tester.lua:26: in function 'assertlt'
	./test_jacobian.lua:112: in function <./test_jacobian.lua:103>

The two ROIPooling methods give very close results (2-norm diff <1e-7).
The gradient tests pass most of time (diff<1e-3), but not always. Both methods fail at the same test case . Maybe you could help  point out some incorrect input?

tingfan@UmboMars:~/dnn/imagine-nn/test$ th ./test_jacobian.lua
Running 6 tests
___|__  ==> NnfROIPooling
Testing module nnf.ROIPooling
test no 1
err 4.6730041503906e-05
test no 2
err 4.6730041503906e-05
test no 3
err 0.025642871856689
___**|  ==> InnROIPooling
Testing module inn.ROIPooling
test no 1
err 4.6730041503906e-05
test no 2
err 4.6730041503906e-05
test no 3
err 0.025642871856689

Hi @0wu,
Thank you very much for those gradient checks. It's very cool :)
Also I liked your subclassing to use the standard jacobian tests. The only small problem is that we can't evaluate the error wrt the bboxes, but I think that's ok.
We are aware of the failing SpatialSameResponseNormalization problem https://github.com/szagoruyko/imagine-nn/issues/8 , it's due to some change in nn or torch from a couple of months ago (the tests were passing with an old version), but I hadn't had the time to explicitly check which commit is causing the problem.
It's great that both nnf and inn versions of ROIPooling are giving the same results :) I'm curious though that the gradient checks doesn't pass all the time, inn version is mainly an adaptation from original Fast-RCNN implementation to torch, the kernels are the same. I'll have a better look later on today.

@0wu I'm a bit in a hurry lately, I'll review it this weekend at most.

I figure out the failing gradient test above, it was because the the added "delta" for finite difference changed the maximum element in the maxpooling function. One quick fix is to generate test input carefully such that the elements in each pool are different enough that their order is preserved even with the added "delta".  do you want me re-submit a fixed pull-request for this ?

@0wu Sorry for the late reply, things were crazy here with CVPR deadline.
Indeed, there is a difference between nnf and inn implementations of ROIPooling when the pooling region is outside the image. I'll eventually fix it in nnf (but it will involve a memory copy in this case).
Regarding resubmitting the pull request with the fixes, I think you can add the new commits here, no need to create a new PR for that.
Thanks again !

v2 fixes the issue in the backprop, fixed by https://github.com/szagoruyko/imagine-nn/pull/17


unable to read downloaded sample png file

1f66fb9
Downloaded sample png file from github but could not read

What about this?


Fix console\Controller preg_split error

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Tests pass?
✔

Fixed issues

Test added

Test added

Thanks.

Thanks.


Backend: Assume Universal Vendor Ids

Closes https://github.com/ethyca/fidesplus/issues/1129
Description Of Changes
Update all-things TCF on the BE (namely, overlay generation and preferences saving) to account for new "universal vendor ID" scheme.
In other words, we assume that TCF vendor preferences are saved against universal vendor ids, and also that universal vendor ids are returned in the experience.
Therefore, the main thing that needs to change on the backend is the translation to and from the TC string itself.
Code Changes

Vendor ID -> GVL Universal Vendor ID: Save privacy preferences under universal vendor id when unpacking vendor preferences from a TC string by adding the gvl prefix
Universal Vendor ID -> Vendor ID: When building a TCModel from the TCF Experience (a prerequisite to building TC strings), convert universal vendor ids to vendor ids (integers)

Steps to Confirm

[ ] Set tcf_enabled=true in fides.toml
[ ] nox -s dev -- shell
[ ] Create [GVL system locally, Instructions here] - this creates a system with vendor id "gvl.8"(https://ethyca.atlassian.net/wiki/spaces/EN/pages/2809724964/API+How-to+Create+GVL+System+Locally)
[ ] PATCH Privacy Preferences using the following accept-all TC string for the given system above:
PATCH http://localhost:8080/api/v1/privacy-preferences

{
  "browser_identity": {
    "fides_user_device_id": "932209c6-e765-472c-b614-68f9b95b3278"
  },
  "tc_string": "CPzevcAPzevcAGXABBENAUEAALAAAEOAAAAAAEAEACACAAAA.IAEAEAAA"
}

[ ] Verify vendor consent and legitimate preferences were saved against id "gvl.8" and tc_mobile_data > IABTCF_VendorConsents="00000001" and IABTCF_VendorLegitimateInterests="00000001":

  "vendor_consent_preferences": [
    {
      "purpose_consent": null,
      "purpose_legitimate_interests": null,
      "special_purpose": null,
      "vendor_consent": "gvl.8",
      "vendor_legitimate_interests": null,
      "feature": null,
      "special_feature": null,
      "system_consent": null,
      "system_legitimate_interests": null,
      "id": "cur_dc981346-1dcb-4c21-adf1-7f8e0a88746e",
      "preference": "opt_in",
      "privacy_notice_history": null,
      "privacy_preference_history_id": "pri_25d3af5e-520b-4ae1-8903-0f6c0e0888ae"
    }

[ ] Fetch the TCF Privacy Experience for EEA with include_meta=True and the same fides user device id from above (to retrieve currently saved preferences)

curl -X 'GET' \
  'http://localhost:8080/api/v1/privacy-experience?show_disabled=true&region=eea&fides_user_device_id=932209c6-e765-472c-b614-68f9b95b3278&systems_applicable=false&include_gvl=false&include_meta=true&page=1&size=50' \
  -H 'accept: application/json'

[ ] Assert vendor consents and vendor legitimate interests are what is expected ("00000001") in the tc mobile data section, that the vendor consents and legitimate interests have "gvl.8" in them, and the previously saved preferences of opt-in for all are surfaced.

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md
[ ] For API changes, the Postman collection has been updated

merged https://github.com/ethyca/fides/pull/4228 into integration branch, then merged integration branch here and adjusted tests accordingly in https://github.com/ethyca/fides/pull/4256/commits/1b2d3f8854fa5e371da35846767b35d43052a104
i'll let CI run - if it's green, i think we're good to go on this?


Opening a new work opens two new works (2 tabs) of the same type.

Please answer these questions before submitting your issue. Thanks!

What version of Workcraft are you using?
Workcraft master repo
What operating system are you using?
Occurs on Windows and macOS (have not tested Linux)
What did you do? If possible, provide a list of steps to reproduce
the error.
Run Workcraft, open a new work via CTRL+N (CMD+N for macOS) and select anything.
What did you expect to see?
Open only one new work.
What did you see instead?
Opened two new works.

Is it reproducable or happens only from time to time?

It happens every time for me.

If it helps, I have identified the code responsible.
org.workcraft.Framework, lines 572-574, this creates a new editor window.
org.workcraft.gui.MainWindow, lines 701-703, this also creates a new editor window, after having called the method in Framework.
I am not sure which is preferred, or which was original, but these both do the same thing, based on whether the user has chosen to open the work in the editor (visually).
I would search for other uses of both of these methods, to find out if one of these is preferred over the other, but gradle doesn't seem to want to work through eclipse at the moment, and I don't know why.

@jrbeaumont thanks for debugging. I know the reason, need to decide what to do about it...


Add Codakuma blog

Codakuma iOS blog

Thank you!

Thanks for merging, and sharing all these brilliant resources 😄


fix: updated styles on career site

Closes #159.

[ ] I have reviewed my code in "Files changed" tab.
[ ] I have re-read the issue and this PR fully resolves it.

New PR without a lot of conflicts https://github.com/freeats/freeats/pull/166


fix(core): do not update completed mutations

fixes https://github.com/TanStack/query/issues/6839
This PR fixes that updating options on a mutation will update the latest mutation in the cache, even though it is completed.

please fix formatting

please fix formatting

Sorry about that, should be fixed now


Detox tests fail on Github Actions CI Runners

What happened?
The tests are failing with the following error:
unable to get output buffers (err=-38) Encoder failed (err=-38)
Tha app is busy with the following tasks:
“LooperIdlingResource-846-mqt_native_modules”
“LooperIdlingResource-846-mqt_js”
What was the expected behaviour?
No response
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[ ] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version:
React Native version:
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version:
Device model:
Android version:
Test-runner (select one): jest / other
Detox logs
Detox logs
paste logs here!

Device logs
Device logs
paste your device.log here!

More data, please!
No response

https://github.com/wix/Detox/pull/4440 Probably a reproduction of the issue

@gosha212
What was the expected behaviour?

android tests should be running in github actions, currently its getting stuck without launching app and abiove mentioned is the error

so issue is it runs fine initially with setup steps, build is successful but when we try to run it it gets stuck without launching app and we get above mentioned errror in github actions log


Bump versions for release march 2024

You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/370/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/370/


⚠ Bofrost.lu has degraded performance

In f8542c9, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1833 ms

Resolved: Bofrost.lu performance has improved in 10e025b after 27 minutes.


Bookshelfs dont enhance the Enchanting Table

As title.
Put appropriate amount of bookshelves around the enchanting table, no level 30 enchant available.
Repeat process with vanilla bookshelf, level 30 enchant shown

Can you elaborate? I just tried in a test world, and everything seems to be working as expected. It's possible there is some mod compatibility issue I need to look at.

seems I was unknowingly playing a 1.18 version.
works fine on 1.19 apologies.

No worries. It's good to know that this is happening on 1.18, so I will reopen this. I still support 1.18 for bug fixes, so I want to be sure this gets addressed.
Thanks!


⚠ Spryr has degraded performance

In fa0f02c, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5857 ms

Resolved: Spryr performance has improved in 6864525 after 7 minutes.


Fix for partial tables.

Fixes #64

Not 100% sure this is a complete fix, but I like that it keeps using plain text markers in attribute positions. Will keep looking for test cases.

@graynorton @cdata the text position detection we talked about appears to be working. More adversarial test cases appreciated!

Text markers in attributes allow you to leave off the quotes:
html`<my-element foo=${foo}></my-element>`

PTAL

@cdata PTAL.
fyi, I found this bug while working on this: https://github.com/PolymerLabs/lit-html/issues/114 so I included a failing but skipped test in the PR.

Rebased on master


MINOR: after reading BYTES type it's possible to access data beyond its size

After reading data of type BYTES, COMPACT_BYTES, NULLABLE_BYTES or COMPACT_NULLABLE_BYTES returned ByteBuffer might have a capacity that is larger than its limit, thus these data types may access data that lies beyond its size by increasing limit of the returned ByteBuffer. I guess this is not very critical but I think it would be good to restrict increasing limit of the returned ByteBuffer by making its capacity strictly equal to its limit.  I think someone might unintentionally mishandle these data types and accidentally mess up data in the ByteBuffer from which they were read.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@showuon @C0urante could you please review this? Thanks.

Hi @bachmanity1! This is a bit outside my area of expertise and it's probably best for another committer to review.

@ijuma could you please review this? Thanks!

@cmccabe could you please review this? Thanks!

The CI test failures look unrelated to this PR

Failed tests are unrelated
    Build / JDK 11 and Scala 2.13 / org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.testReplicationIsCreatingTopicsUsingProvidedForwardingAdmin()
    Build / JDK 8 and Scala 2.12 / kafka.admin.ReassignPartitionsIntegrationTest.testReassignment(String).quorum=kraft
    Build / JDK 17 and Scala 2.13 / org.apache.kafka.connect.mirror.integration.DedicatedMirrorIntegrationTest.testMultiNodeCluster()
    Build / JDK 17 and Scala 2.13 / org.apache.kafka.connect.mirror.integration.MirrorConnectorsWithCustomForwardingAdminIntegrationTest.testCreatePartitionsUseProvidedForwardingAdmin()
    Build / JDK 17 and Scala 2.13 / kafka.server.KafkaServerKRaftRegistrationTest.[1] Type=ZK, Name=testRegisterZkBrokerInKraft, MetadataVersion=3.4-IV0, Security=PLAINTEXT


Upgrade embulk-util-config to 0.3.4, embulk-util-file to 0.1.5, and embulk-util-text to 0.1.3

It fails, but it should be okay when embulk-util-text:0.1.3 is ready.

Thanks!


Linear axis with step size not supports general tick options

Expected behavior
When I specify any LinearScaleOptions specific options on the ticks, I'd like to keep and also have the other Tick related options provided by CartesianTickOptions.
Eg.:
"ticks":{
"display": true,
"font": {
"size": 75
},
"stepSize": 1
}
This passed in as a tick option for a x axis scale options should allow me to have the given font size and also the step size set.
Current behavior
Currently if I specify anything for tick options that I have in the CartesianTickOptions, I loose the possibility to set any LinearScaleOptions specific things for the Ticks, like the stepSize.
Reproducible sample
https://www.chartjs.org/dist/master/chart.umd.js
Optional extra steps/info to reproduce
No response
Possible solution
No response
Context
No response
chart.js version
v4.4.0
Browser name and version
No response
Link to your project
No response

This is because of the autoSkip property, if you set that to false it works as you want:
https://jsfiddle.net/6qg75uwk/


Added my repo file

@shristirwt Is that your project ? i think it;s senior program manager's repository

Yes I asked him if I could submit the repo for hack web3conf and he permitted me to do so

Yes I asked him if I could submit the repo for hack web3conf and he permitted me to do so

He might have misunderstood it, but it is not permissible, you have to add your own project or any idea related to web3

Yes I asked him if I could submit the repo for hack web3conf and he permitted me to do so

He might have misunderstood it, but it is not permissible, you have to add your own project or any idea related to web3

Okay I will ask him again and let you know

Please submit a new project idea, this PR cannot be merged as it is someone else's project.


Add user doc on Admin services

Description
There should be a document explaining exposed admin services and related configurations.

Since we have exposed all the administrative services as a RESTful API, exposing the swagger through a swagger hosting site would be sufficient rather than duplicationg the api information into a different doc.

relates: #484


Vol 10 fixes

Vol 10 fixes

Minor correction on Chapter 3
Minor correction on Chapter 4

Hey, thanks for giving this a shot, you made it to the right place!
Your first suggestion looks fine, tool is an odd insult that is apparently common in Japanese, if I recall correctly, but fools is less clunky in most cases.
The second one I believe goes against the original meaning, unless you have a source to back this up, so I added a clarification to change it to something better. I believe the sentence there means that he had been using her "brand" essentially as a front for his own goals.

Hi.. missed ur text, but thanks for merging.
I didnt know there is slang for tools :) but yeah fools is more common.
For second one, I believe his strength is likely referring to Granbell's strength.


Change flickr/find-photoss to store urls under RemoteResource.url

fixes: #2837

This will break current samples. What @willhite did in for a previous example was generate both the old schema and the new one. Unsure whether it's worth trying to keep this stuff working for now.

LGTM


Force cancel all events on client (for discussion)

Once a test leaves a client running, all other tests will fail.  But leaving things running can impact other tests, so make another attempt to cleanup.

@swankjesse It's internal class, but you might not want to expose.


iOS WebView plugin render incorrect texture after leaving from app

Steps to Reproduce

Put WebView widget in body of Scaffold.
Navigate to other page (Scaffold)
Launch other app (ex. google map, safari)
Back to app.
Back to WebView page.

at 5. point, you will see incorrect texture which is old rendering result in 2. state.
I create a project for reproduce this problem.
https://github.com/niusounds/flutter_webview_bug
Logs
Any crash or exceptions are not logged.
Flutter doctor
[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.14.3 18D42, locale ja-JP)
    • Flutter version 1.2.1 at /Users/yuya.matsuo/flutter
    • Framework revision 8661d8aecd (6 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/yuya.matsuo/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.6.0

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.1.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] VS Code (version 1.32.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.24.0

[✓] Connected device (1 available)
    • niusounds iPhone • 45a5d2b16249285c1255238af9780508db95e17c • ios • iOS 11.3

• No issues found!

I noticed that 3. Launch other app (ex. google map, safari) is not exact. It happens just pressing home button (when app goes to background).

It seems that it was fixed at current stable version.


Initial commit, dir structure fix

File wasn't going in from Kerbal Stuff because of no GameData, despite ckan tag.

License was misspelled at KS, but there's also the directory structure issue.
Please accept this one - https://github.com/KSP-CKAN/NetKAN/pull/2387


Issue : Unable to set max_output_tokens for VertexAI models

System Info
I am using VertexAI model to parse data in a document. Since the documents are large, I am trying to increase the max_output_tokens parameter for "chat-bison-32k" model. I am not able to change this parameter and my output gets truncated after a certain token limit is reached. Is there a way to increase the output token limit?
The output also has a " ```JSON" tag at the beginning which is not desired @
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[x] My own modified scripts

Related Components

[x] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
model = ChatVertexAI(model_name=model_name,
max_output_tokens = 2400,
temperature=0.01)
example_gen_chain = LLMChain(llm=chat, prompt=prompt)
def generate_examples(generator, data):
return generator.apply_and_parse(data)
Loop through each text to parse it
for i, item in enumerate(texts, start=1):
text = item
new_example = generate_examples(
    example_gen_chain, [{"doc": text}]
)

Expected behavior
The output gets truncated when the token limit is reached.
{
 "sections": [
   {
     "SectionNumber": "1",
     "SectionName": "Product",
     "Body": "Body of the document.",
   },
   {
     "

Hey Dosu,
Thank you for the quick response. I am able to change the output length in OpenAI but not able to change the same in VertexAI. Can you let me know how we can change the output size for VertexAI. I am using this code, but it doesn't seen to overwrite the max_output_tokens parameter :
ChatVertexAI(model_name=model_name,
max_output_tokens = 2400,
temperature=0.01,
verbose=True,)

Great. That solved the issue. Thank you

Hi. I am able to change the max_output_tokens for text based models such as text-bison@001 and text-davinci. I am still facing the issue when working with the chat-bison-32k model. Can you let me know how the max_output_tokens can be changed for the chat-bison-32k model specifically.


ffqueue: persist ffqueue.cfg

Closes #XXXX

Relates to #XXXX

[ ] I have read the Contributing Guide.

Thanks!

why persist ffqueue in delete?
and how to use persist ffqueue new?

Because ffqueue.cfg has its unique header. If the header is not found in the file, then FFQueue will report error and crash. So we can only copy it before uninstalling to preserve the file.
We use New-Item in pre_install because ffqueue.cfg does not exist in the archive, so we need to create it first so that we can persist it.
New-Item creates an empty file. This would work fine for most apps, but not for FFQueue.
Another solution is to use Set-Content to set the initial content of the config file. This method can be useful for apps requires something like "a proper JSON" or "a proper INI", but I would not recommend it for the case of FFQueue, because the header may change in the future.


Postfix completions are not properly indented

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
The title says it all...
Environment
Zed: v0.96.0 (preview)
OS: macOS 13.2.1
Memory: 32 GiB
Architecture: x86_64
If applicable, add mockups / screenshots to help explain present your vision of the feature
VSCode:

(After I tested in VSCode, I notice that VSCode also indicates the subsequent cursor locations as one can see in the screenshot which make actions more predictable.)
Zed:

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

cc: @SomeoneToIgnore


1465 regional endpoint option

Checklist

If this is a non-trivial commit, did you open a ticket for discussion? yes
Did you put the URL for that ticket in a comment in the code? yes
If you made a new function, did you write a good docstring for it? yes
Did you avoid putting "_" in front of your new function for no reason? yes
Did you write a test for your new code? Adjusted existing tests, added coverage in cli testing. there was no existing coverage of zappa.create_domain_name / update_domain_name, did not add new tests
Did the Travis build pass? TBD - local nose passes on 3.7
Did you improve (or at least not significantly reduce)  the amount of code test coverage? yes
Did you make sure this code actually works on Lambda, as well as locally? Yes, converted REGIONAL to EDGE and back
Did you test this code with both Python 2.7 and Python 3.6? No, shouldn't be anything version dependent

Description
This turned out a little bigger than I liked for a couple reasons.
We wanted to use A - Alias records in Route53 for regional endpoints. I included that without changing the existing behavior in the default case, but probably it would be better to replace the CNAME with A - Alias.
Finding the update from EDGE to REGIONAL required changing a bit of the logic around if something is a create or update. Truthfully the old method of using Route53 existence to drive create or update was flawed. Now it will check with APIG to see if the domain_name entry exists and use that to drive create or update of the APIG domain_name. If Route53 is in use, it will always try to UPSERT the record, at worst this is a noop.
GitHub Issues
https://github.com/Miserlou/Zappa/issues/1465

Coverage decreased (-0.5%) to 73.871% when pulling ed3fb61501a0dd65e5390b52f2c9b7476960c286 on aarcro:1465_regional_endpoint_option into 7d38c157f575ab95c8dd25a9e42c9edaeb9c93a7 on Miserlou:master.


Cannot authenticate with email (upn)

I'm use UPN for authenticate on vpn gateway. But connection stucked with log record like this:
03:21:23 | Invalid characters in username<EMAIL_ADDRESS>Is it possible to allow connect with upn/email?

New release out now version 1.783 which should fix this


Update Inventory to use big.Int

Currently the inventory system works on int64 and doesn't recognize big.Int quantities which are necessary to process CryptoCurrency listings.

Fixed in https://github.com/OpenBazaar/openbazaar-go/pull/1775


Switched to using reflection to create the desired condition for testing an expected exception.

Switched to using reflection to create the desired condition for testing an expected exception.

:shipit:


15.09 branch wifi failure (regression)

Wifi module doesn't work when using the latest stable 15.04 ISO: https://nixos.org/releases/nixos/15.09/nixos-15.09.911.53286a8/nixos-graphical-15.09.911.53286a8-x86_64-linux.iso
However using the older 15.04 ISO: https://nixos.org/releases/nixos/15.09/nixos-15.09.706.45128de/nixos-graphical-15.09.706.45128de-x86_64-linux.iso the wifi works again. (Also wifi works on Ubuntu)
The problem is the iwlwifi kernel module cannot start.
On the journalctl, I get a message like: iwlwifi Failed to start init ucode -110. The radio is not blocked.
Wifi hardware is: Intel Corporation Wireless 7265 (rev 59)

Could someone find a time to bisect between the 2 commits 45128de (good) to 53286a8 (bad) which has 205 commits between the 2 states. I don't currently have the infrastructure to compile and test nixos builds.

I might not have time to look in depth at this, but I can confirm this behavior. It is not just the live CD, but the dist as a whole if that helps at all.

It has to do with the kernel. Upgrading to 4.1 made it work again. There was some kernel change in 15.09 that caused this problem.

Thank you, that kernel worked for me.

I've seen this problem as well, where running an upgrade for 15.09 breaks WiFi. Before the upgrade (when WiFi was working) I had
Linux version 3.18.24 (nixbld1@machine) (gcc version 4.9.3 (GCC) ) #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970

After upgrading (no WiFi) I had
Linux version 3.18.25 (nixbld@localhost) (gcc version 4.9.3 (GCC) ) #1-NixOS SMP Thu Jan 1 00:00:01 UTC 1970

journalctl for the failure shows
iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
...
iwlwifi 0000:02:00.0: Failed to start INIT ucode: -110
iwlwifi 0000:02:00.0: Failed to run INIT ucode: -110

The suggestion of using Linux 4.1 avoids the problem for me as well. Thanks @CMCDragonkai! To be precise, I added this to my /etc/nixos/configuration.nix:
boot.kernelPackages = pkgs.linuxPackages_4_1;

(triage) we have now 16.09, this issue is outdated


Binary Classification Evaluator

Linked issue(s):
Fixes KOL-2704
What change does this PR introduce and why?

Refactors multiclass classification evaluator
Modified the workflow schema

dogs-vs-cats binary classification (threshold=0.5)
dogs-vs-cats multiclass classification
Based on the # of prediction labels seeded as part of Inference determines which evaluator to run.  If only positive label's prediction is used, then it will be treated as a binary classification.  If both labels' predictions are added, then it will be 2 class multiclass evaluation.
How are multiclass and binary evaluator different?:

Per-class evaluation for multiclass (for both "dog" and "cat" class metrics are available) (e.g., TP for class "cat" is for correctly predicted "cat" class) — binary shows the same information but in different wordings (e.g., TP is for positive label which in this case is "dog" and TN is for negative label which in this case is "cat")
ROC curve on positive label only for binary vs on both labels for multiclass
Score distribution (for binary, only the positive prediction scores are used so it ranges from 0 to 1; whereas, for multiclass, maximum confidence score label is used so it will range from 0.5 - 1.
Classification label annotation: for binary, it will only show the prediction on the positive label and for multiclass, the label which has the "maximum" confidence score will be shown.

TestSampleMetrics: for binary, there are more fields like is_TP, is_FN and etc., whereas for multiclass, only is_correct and predicted label is shown.

For binary classification cases where performance on positive label can be clearly defined (e.g., "is_live" or "is_dog") then using binary classification evaluator is a better experience.  For cases where both label are equally important (e.g., "dog" vs "cat") where a positive label cannot be specified, using multiclass evaluator is preferred.
Proposal on UX improvement:
Once we make this into a pre-built, we should consider changing the color of TestSampleMetrics.classification label to be green (if is_correct=True) or red (otherwise).
Please check if the PR fulfills these requirements

[ ] Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
[ ] Relevant tests for the changes have been added
[ ] Relevant docs have been added / updated

will have a separate PR for seeding scripts and doc updates


Feature/update profile api calls

Description
As an Admin I'd like to be able to:

find a user a consult its profile
edit profiles
deactivate user accounts

This is the completion of a Trello card started by the previous team at Labs. The goal is to add requests to the form to complete the functionality of updating users as an admin, as well as address the slight UX changes suggested by Jason at the last stakeholder meeting.
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

Loom Video
Code
https://www.loom.com/share/c926837a9bc346af94fbd7348d008d56
App
https://www.loom.com/share/e4bfaa2b1dea437a803cf9d122ee3a06
Trello Card
https://trello.com/c/8SfgRWkz
Co-Contributors

Christopher Boyle

Nice I was wondering if we needed to use an API call to the backend. looks great. also looks like this has branch conflicts might want to check on that

Resolved it! Thanks for letting me know.


wis2box

Can WIS2Box run on Windows environment? For a small WIS node, they may just operate in Windows environment on a desktop.


ashm data frames have inconsistent chr prefixing

The data frames stored under GAMBLR.data::somatic_hypermutation_locations_GRCh37_v* have chr prefixing in the chromosome column, which creates a lot of extra work to handle in most instances. Also the column names could be streamlined substantially.

I kept the chr prefixing and column names in this package to reproduce what was in the original GAMBLR bundled data. I can easily strip the prefix and update the column names - but not sure how many issues it will cause for the existing codebase in the current functions that (probably?) expect this behavior. I think to address this issue we need first a reproducible set of tests that can indicate whether or not there are issues with existing functions, and this issue will be an excellent use case for the testing approach. I will work on bundling the data with GAMBLR so we can start the work of developing the test suite.


Rename modalities.yaml in schema

The file modalities.yaml describes the technologies supported in the specification (e.g., MRI, EEG). Given that "modality" has its own meaning, and will soon have a distinct definition in Common principles (see #592), the naming of the file in the schema is misleading. Some viable alternatives might be "technologies.yaml" or "instruments.yaml".

I'm leaning toward "instruments.yaml" after reading something @robertoostenveld wrote. Additionally, I like the idea of combining the EEG and iEEG data types (i.e., folders) under a shared instrument like "biopotential amplifiers" (again, per @robertoostenveld). What do folks think of this structure?
---
mri:
  name: Magnetic Resonance Imaging
  datatypes:
    - anat
    - dwi
    - fmap
    - func
bioamp:
  name: Biopotential Amplification
  datatypes:
    - eeg
    - ieeg
meg:
  name: Magnetoencephalography
  datatypes:
    - meg
beh:
  name: Behavioral experiments
  datatypes:
    - beh

While this doesn't affect the specification at all at the moment, I think it would eventually impact the organization of the text. Currently, we have an MRI page with subsections for the different data types derived from the same instrument, while EEG and iEEG have separate pages. Ultimately, iEEG and EEG would also fall under one page (or major section) named "Biopotential Amplification".

Although I like instruments, it sounds a bit "too specific".  More appropriate term might be "Measurement Technique" or may be "Measurement Method"  ( @satra ?) for which there is even an MMO ontology which lists MRI, EEG and may be more.
Filename then indeed might grow in length to measurement_methods.yaml or alike

@yarikoptic the thing I wrote that @tsalo refers to is this https://docs.google.com/document/d/1cY-iZL8rtgDJ1-YVs1f2h5ugOiuK144zu4ju9UXZEGY/edit#heading=h.r2qz45a4irn1. It is not yet ready for wide dissemination, as I would like to get some more feedback from specific people before opening it up for wider discussion. But then... it clarifies the organization and naming proposed here.

@robertoostenveld sorry, I knew it wasn't ready for dissemination, so I tried to hint around it, but the proposals there seemed to be directly relevant to this issue.

Reegarding Instrument versus Measurement Technique or Measurement Method: people working with sEEG will consider their "technique" or "method" to be totally different than ECoG (and rightfully so), but from a data perspective (i.e. someone who wants to (re)use data that already sits on disk) the two are more similar than different, with the most crucial difference being in the placement of the electrodes. Idem for OPM-based versus cryogenic MEG systems. Hence trying to make it specific about the instrument that converts the (complex) measurement to data on disk.

@robertoostenveld If I'm understanding correctly, you're saying that Instrument is a level that reflects the purpose of the data better than Measurement Technique or Measurement Method?
I should say that this can probably be changed later. Currently, modalities.yaml stands in direct contradiction to the definition of "modality" (esp. once #592 is merged), and the file isn't actually used for anything yet. So as long as the new name doesn't conflict with existing terms in the specification, it should be fine.
@yarikoptic @robertoostenveld What do you both think of the organization I proposed? Basically demoting EEG and iEEG from "instruments" or "measurement techniques" down to just "datatypes" (and of course suffixes) and nesting both under "Biopotential Amplification"? I would end up splitting up the entity tables to match the new convention.


Bug 2052996: object: do not check for upgrade on external mode

Description of your changes:
The object child controller should not compare versions if the object
store is external. The current version comparison is using the
cmdreporter to check the ceph version of the image in the CephCluster spec.
In external mode, this image is not set so the cmdreporter fails.
Also, this check is only valid for converged mode, so external mode
should be skipped.
Signed-off-by: Sébastien Han<EMAIL_ADDRESS>(cherry picked from commit 856b14e60a1a49f61f9f1bf0d63f4f70c13b326a)
(cherry picked from commit dfe060100590d32ab5dd347047a0b09ff7e68d0e)

Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
[ ] Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.
[ ] Pending release notes updated with breaking and/or notable changes, if necessary.
[ ] Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
[ ] Code generation (make codegen) has been run to update object specifications, if necessary.

/approve
/lgtm


Moving all FCL and BCL documentation into its own section and making it awesome

Currently the primer has a link to a document that isn't in the TOC tree describing briefly what the FCL is, giving a brief overview of the BCL and some examples of what the BCL and FCL contain.
There is also a section called "Base Class Library", which I think is a good candidate for renaming to "Framework Class Library" and modifying it to contain all things FCL, including a link to reference documentation.  This would include:

Overview of the FCL with a diagram showing its relationship with .NET Managed Langs

Section with BCL overview and example of its contents, with link to reference docs
Section with other FCL examples, with links to reference docs

Article about FCL libraries which are important for cloud devs

Snippet about each relevant library for cloud devs with sample code highlighting a common use case in C#, VB, and F#
Link to reference docs for each library
Links to sample applications or full code samples

Article about FCL libraries which are important for mobile devs

same as for the cloud devs article
Links to the UWP samples and other platform samples

I see value in making it clear to developers the relationship between the libraries and the languages and providing conceptual docs + code samples covering some common scenarios.  This is a large enough area that it also demands its own section.

Closing for now; we have more stuff to hash out before we can consider writing this documentation.


cellStyle and fill need more documentation

The fill prop on <Hexagon /> only supports strings, while cellStyle accepts JS in CSS.  This isn't clear, and should be documented.

This is now mostly explained in the docs.  However, Pattern still needs documentation.  #31


drivers: ethernet: fix rx used bit not set when high bps ethernet dat…

…a coming in and wrap dma buffer descriptor
recently, I am using zephyr with its Ethernet driver and running on ZynqMP RPU, however, when I doing throughput test I found when high data rate cause the rx dma buffer wrap arround, the rx isr pending handle will not clear the dma buffer.
This scenario can be fixed by flushing the the exist dma buffer packet and re-configure the dma rx buffer.

@decsny please take a look

@gitGideonhub please read
https://docs.zephyrproject.org/latest/contribute/guidelines.html#contribute-guidelines
https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html
you need to clean up your commits to meet these guidelines

Thanks! I will handle this in a few days!

@gitGideonhub please read https://docs.zephyrproject.org/latest/contribute/guidelines.html#contribute-guidelines https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html
you need to clean up your commits to meet these guidelines

Hello, Is there any method to modify commit message without re-open a PR.
Thanks.

Hello, Is there any method to modify commit message without re-open a PR.

Yes, search for instruction on how to do an interactive rebase in Git.


Update tutorial to include Environment.NewLine for newlines

Summary

Further implement {Environment.NewLine} into more tutorials.

Just noticed another tutorial program that could be switched from \n to {Environment.NewLine} to further build off of the work done in #23201

Thanks for the catch! Missed that one.
Updated!

Thanks @BenjaminMichaelis

@tdykstra is there a way to allow for the XREF: to Environment.newline to show "Environment.newline" for clarity on the https://docs.microsoft.com/en-us/dotnet/core/tutorials/with-visual-studio document as right now it says "NewLine is a platform-independent and language-independent way to represent a line break. Alternatives are \n in C# and vbCrLf in Visual Basic." and I think instead should show "Environment.NewLine is a platform-independent and language-independent way to represent a line break. Alternatives are \n in C# and vbCrLf in Visual Basic." As this directly matches the example and since this is a base level tutorial might make things just a bit more clear.

Yes there is a way to do that, I'll fix it.


Proposal for Sampling Database (back-end of Viz Tool(s))

Goal: Propose a solution to CRWA
Probable direction: Google Sheet
To Do: Write a proposal that summarize the situation, what we propose, why it's a good idea and what are the drawbacks, what are the questions that we need to answer, what are our proposed next steps?
Eventually build a prototype.
! QA/QC and formatting of data to send to EPA done in Access. Need to think if propose to have Google Sheet database "after" (on top of) Access DB (eventually in a first phase).
preliminary work: #84, #83, #93, #90.
need communication with #89 and #102

work on this is continued in issue #102


The pylint component seems to be a bit buggy

From<EMAIL_ADDRESS>on 2009-10-09T01:58:49Z
(Sorry if it's confusing, I'm quite tired right now...)
I downloaded the 1.0.0.rc2 and played around with it for 2 or 3 hours. One
thing I found is that there are several small bugs in the pylint component.
All of them are not really reproducible and happen at random.
Things I've seen:

Sometimes the line numbers are off. I analyze code using pylint, correct
a few things, run a new analyze, then click on an entry in the pylint list.
The reported line number of the error/warning sometimes differ from their
place in the code. This might be related to:

Sometimes pylint seems to refuse to run the analysis on corrected code.
That means: run pylint, correct something, save the file, run pylint again
and the corrected thing is shown as uncorrected again although it is
definitively fixed in the code and the file is saved.

If there is a syntax error in the code pylint refuses to run. I fix the
error, click analyze -> sometimes pylint still refuses to run. Sometimes
clicking the analyze button multiple times helps but sometimes I have to
load a new file into pylint, analzye it, and then switch back to the old file

As I said above: all of this happens at random and I'm not able to
reproduce it reliable.
(Ubuntu + Python 2.6)
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=68

From<EMAIL_ADDRESS>on 2009-10-10T19:36:44Z
I don't see this behavior anymore. One day there where errors all over the place and
on the next day it worked flawless, I'm not sure what happened there.

From pierre.raybaut on 2009-10-11T01:01:35Z
That's good because I couldn't reproduce any of these behaviors.
Please do not hesitate to open an Issue if you are able to reproduce this kind of bug.
Status: Invalid


TypeError: L.DistanceGrid is not a constructor

Getting this error at runtime. Any ideas?

Did you install leaflet? Can you share some code?

Yes Ive got leaflet working already. You can see my code and package.json
below:
import { useEffect, useState } from 'react';
import { MapContainer, Marker, Popup, TileLayer, useMap, useMapEvents } from
'react-leaflet';
import MarkerClusterGroup from 'react-leaflet-markercluster';
import 'leaflet/dist/leaflet.css';
import 'leaflet/dist/leaflet.js';
import
'leaflet-defaulticon-compatibility/dist/leaflet-defaulticon-compatibility.css'
;
import 'leaflet-defaulticon-compatibility';
import
@.***/react-leaflet-markercluster/dist/styles.min.css';
import * as L from 'leaflet';
const tileset = "https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png";
const attribution = '© OpenStreetMap
contributors';
export default function Mapper( {content, lat, long, zoom, itemWidth,
itemHeight } )
{
return (
<MapContainer center={lat, long]} zoom={zoom} scrollWheelZoom={true}
zoomSnap={0.1} style={{height: '100%', width: '100%'}}>

{
content && content.map((contentItem, index) => {
if (contentItem.lat == null)
return;
else
return <Marker key={index} position={[contentItem.lat, contentItem.long]}>

;
})
}

);
}
On Thu, Feb 9, 2023 at 11:13 AM sur.la.route @.***>
wrote:

Did you install leaflet? Can you share some code?
—
Reply to this email directly, view it on GitHub
https://github.com/christopherpickering/react-leaflet-markercluster/issues/16#issuecomment-1424448039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXMPTSPITMYBFHOGPSFDE3WWUJRNANCNFSM6AAAAAAUWV4UKM
.
You are receiving this because you authored the thread.Message ID:
<christopherpickering/react-leaflet-markercluster/issues/16/1424448039@
github.com>

Thanks, have you also installed the peer deps?
"leaflet": "^1.9.3",
"leaflet.markercluster": "^1.5.3",
"react-leaflet": "^4.0.0"

Try to debug by starting with one of the examples.


Issue/front end infra

Issue/front end infra (#5)
Summary

Front end infrastructure Terraform
Github actions for deploying front end application

Fixes # (#5)
Type of change
Please delete options that are not relevant.
- [ ] Bug fix (non-breaking change which fixes an issue)

[x] New feature (non-breaking change which adds functionality)
- [ ] This is a documentation update

How To Test
Checklist:

[x] My code follows the style guidelines of this project and has no linting errors
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation, including any applicable ADRs
[x] My changes generate no new warnings
[x] I have added tests that fail without these changes
- [ ] New and existing tests (unit, integration, accessibility) pass locally
- [ ] Documentation updated
- [ ] If there are security concerns they are addressed or ticketed after being discussed

I know this is a big too big. Let me know if this need to be split up into infra and pipeline changes


Fix the path encoding when character encoding is set on HttpServletRequest

This fixes #647. I've already signed the contributor's agreement. Thanks!

Merged via fc08b55eaca983d865281d85cb0bc73a75bd1710. @jebeaudet similar fix as #979, but I wanted to include your tests. Thanks again!


Upgrade to drone v0.5

The template is copy-pasted from:
https://scalacenter.github.io/platform-staging/ci-integration.html#creating-the-drone.yml-file
The CI now runs two parallel tasks: ci-fast and ci-slow. The fast task runs unit tests and doc generation. For most PRs, a green response from this task is enough to merge. The slow tests run large property tests on the parser/tokenizer as well as scripted sbt plugin tests.

CI passes, ship it! :shipit:


Fix DscResources foldername

DscResources foldername is cases sensitive on platforms that have case sensitive file systems

@TravisEz13 Maybe we should update the folder structure https://docs.microsoft.com/en-us/powershell/dsc/resources/authoringresourcemof#folder-structure-for-a-mof-resource with a note that is is case sensitive on on platforms that have case sensitive file system? What looks for DscResource and not DSCResource, maybe that can be added as well?

@johlju  I'm not sure a final decision has been made here.  Please work with the Nitin and @amitsara  and they agreed they would own everything beyond this change wrt to this case sensitivity.


[depdive] integrate rustsec reporting in dep metrics

Currently, we only offer it during updates.
We already have advisory module implemented. Should be fairly straightforward to incorporate into overall dep analysis just for the sake of completeness.

a functionality similar to cargo audit. Closing as redundant.


Admin Panel - Not responsive enough

Hi there,
I see the admin panel is not responsive enough, see my screenshot

Please fix in next version :) thanks

not related for Flextype Core


candlestick x timeseries

Hi, using
var fp = WpfPlot1.Plot.AddCandlesticks(ohlcs.ToArray());
fp.Sequential = true;

I get the the candlesticks  display looking thick enough, but the dates are wrong. Set to false the dates are correct but the candles are to thin. Is there any way to have correct dates with sequential.  I tried the example plot candlesticks, but I Couldn't get my data to work with it.

Hi @robcpettit

Is there any way to have correct dates with sequential

I do not think so. The Sequential flag is used to indicate your data is a sequence of integers (not dates). This is useful because most financial charts aren't actually plotted using horizontal dates otherwise there would be gaps for weekends.

See https://scottplot.net/cookbook/4.1/category/plottable-finance for examples of how to create candlestick charts


[feat] Allow experimental features in WebView

Describe the problem
I would like to enable experimental features on webkit or chromium. Is there a way to do such?
Describe the solution you'd like
Add documentation on how to enable experimental features if already possible. Otherwise expose a tauri config option to enable experimental browser features.
Alternatives considered
No response
Additional context
No response

If i remember everything correctly we have the following limitations:

macos: Doesn't support this at all
windows: Only supports chromium's command line flags. Which for now you have to set via the WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS environment flag. Keep in mind that many of these flags only work in non-stable browser versions (webview2 uses the stable channel)
Linux: Hmm, can't remember the situation, but i think it's similar to macos.

tldr: Really nothing we can do here, so i'm going to close this issue until someone can show that i got that stuff wrong.


Remove dependency on indexedDB

This allow duckdb-wasm-shell to work also on Firefox Incognito, fixing #1014

This is not the right solution, moving this to #1209


Unable to compile shadowJar and other issues

Not sure what change caused this breakage, but here it goes.
Command: ./gradlew build shadowJar proguard release
Fails with error:
> Configure project :
Building RELEASE (master): 2.10.0-xiaomi.eu

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':release'.
> Task with path 'proguard' not found in root project 'apktool-cli'.

When commenting out this line in brut.apktool\apktool-cli\build.gradle.kts:
tasks.getByPath(":release").dependsOn("proguard")

Then the JAR compiles fine, but when trying to use it, none of the XML files can be decompiled and ends with an error:
org.xmlpull.v1.XmlPullParserException: caused by: org.xmlpull.v1.XmlPullParserException: resource not found: /META-INF/services/org.xmlpull.v1.XmlPullParserFactory make sure that parser implementing XmlPull API is available
        at org.xmlpull.v1.XmlPullParserFactory.newInstance(SourceFile)
        ... 4 more

When manually adding META-INF/services/org.xmlpull.v1.XmlPullParserFactory extracted from a previous Apktool JAR to the build JAR, all works fine.
Also, when building without "release", the output is apktool-v2.9.2-48-6b986e9a-SNAPSHOT.jar, not 2.10.0.
Quite a whole lot of mess.

Yeah R8 is having some issues and stripping way more than it should - blocker for 2.10.x at the moment.

Broke here for context, but I'm not reverting to force myself to fix it before a release - https://github.com/iBotPeaches/Apktool/commit/e69ecb578da9100ccbd1704cd35baa7bd16ba4bb

Another thing I committed to Google's smali repo. Dudes used incompatible DEX version for Android 10...
https://github.com/google/smali/pull/55

I dug into this - it appears the old old xmlpull library is violating spec for loaders, so R8 is stripping it out.
Warning in /home/ibotpeaches/Desktop/Projects/Java/Apktool/brut.apktool/apktool-cli/build/libs/apktool-cli.jar:META-INF/services/org.xmlpull.v1.XmlPullParserFactory:
Unexpected reference to missing service implementation class in META-INF/services/org.xmlpull.v1.XmlPullParserFactory: org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer.

So two classes comma delimited, but spec says it must be newline delimited. I was hoping I could just upgrade this package, but its been dead for a decade.

A service provider identifies itself by placing a provider-configuration file in the resource directory META-INF/services. The file's name should consist of the fully-qualified name of the abstract service class. The file should contain a newline-separated list of unique concrete provider-class names. Space and tab characters, as well as blank lines, are ignored. The comment character is '#' (0x23); on each line all characters following the first comment character are ignored. The file must be encoded in UTF-8.

https://docs.oracle.com/javase/6/docs/technotes/guides/jar/jar.html#Service Provider


Unify navbar dropdown and sidebar category styling experience

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
The navbar dropdown arrow is not configurable and by default has a different style compared to the sidebar category arrow. We'd like to propose unifying this styling experience:

Remove the border-based styling from the navbar dropdown and replace it with styling similar to the background styling of the sidebar category.
Use a variable for the icon of the navbar dropdown and let it default to the same icon as the sidebar category.

Has this been requested on Canny?
No response
Motivation
It would allow for a consistent styling experience for similar components.
API design
Not much would change. The icons would be configurable by either changing the associated CSS variables or by overriding the respective :after pseudo element.
Have you tried building it?
We solve it now by using the following CSS snippet:
.dropdown > .navbar__link:after {
  background: var(--ifm-menu-link-sublist-icon) 50% / 2rem 2rem;
  border: none;
  filter: var(--ifm-menu-link-sublist-icon-filter);
  transform: rotate(180deg);
  height: 1.25rem;
  width: 1.25rem;
}

Self-service

[X] I'd be willing to contribute this feature to Docusaurus myself.

The navbar dropdown arrow is not configurable

True, the caret is added in :after and comes from Infima classes. In my opinion such elements should always be stylable in a more flexible way, at least with swizzle.

by default has a different style compared to the sidebar category arrow.

I think it doesn't always make sense to share the exact same icon in multiple places. But in this one I think it could make sense.
VitePress uses a similar icon for its dropdown and it doesn't look bad compared to ours so I'd be ok to make that switch

What we must be sure to keep is to give the ability for users to easily switch one icon on the navbar (ie possibly revert to previous style) without affecting the docs sidebar icon: there must be 2 distinct components available to swizzle.

Remove the border-based styling from the navbar dropdown and replace it with styling similar to the background styling of the sidebar category.

Honestly, I'm not a fan of all of these background icon styling using CSS variables. They come from Infima and this was not really designed React-first so the integration is a bit weird.

Use a variable for the icon of the navbar dropdown and let it default to the same icon as the sidebar category.

seems reasonable, but we must keep the navbar icon / doc category icon decoupled from each others

If we change this, we'd rather make real React components that we can swizzle:

IconArrow  (default)
NavbarDropdownIconArrowIcon (defaults to IconArrow)
SidebarCategoryArrowIcon for example (defaults to IconArrow + 90° rotation)

Does it make sense?

Note, we already have an IconArrow component to collapse the docs sidebar, but it created confusion in a past and we should find a better name like "IconDoubleArrow" or something 🤷♂


Change more uint256 into SHAMapHash

@mtrippled @miguelportilla

Current coverage is 49.38%

Merging #1414 into develop will not affect coverage as of 9218fd0

@@            develop   #1414   diff @@
=======================================
  Files           964     964
  Stmts         67065   67067     +2
  Branches          0       0
  Methods           0       0
=======================================
  Hit           33122   33122
  Partial           0       0
- Missed        33943   33945     +2

Review entire Coverage Diff as of 9218fd0

Powered by Codecov. Updated on successful CI builds.

I left a comment but not holding this back.
:+1:

Rebased to b9.

:+1:

Rebase to b10.