rayon crashes

https://github.com/xiph/rav1e
All of them are like
---- api::test::output_frameno_incremental_reorder_scene_change_at_3 stdout ----
---- api::test::output_frameno_incremental_reorder_scene_change_at_3 stderr ----
thread '<unnamed>' panicked at 'index out of bounds: the len is<PHONE_NUMBER>31184 but the index is 128', /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:541:24
stack backtrace:
   0: rust_begin_unwind
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/core/src/panicking.rs:67:14
   2: core::panicking::panic_bounds_check
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/core/src/panic.rs:61:9
   3: rayon_core::registry::Registry::in_worker_cold::{{closure}}::{{closure}}
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:541:24
   4: rayon_core::job::JobResult<T>::call::{{closure}}
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/job.rs:218:41
   5: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/core/src/panic/unwind_safe.rs:265:9
   6: std::panicking::try::do_call
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panicking.rs:500:40
   7: std::panicking::try
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panicking.rs:464:19
   8: std::panic::catch_unwind
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panic.rs:142:14
   9: rayon_core::unwind::halt_unwinding
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/unwind.rs:17:5
  10: rayon_core::job::JobResult<T>::call
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/job.rs:217:5
  11: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/job.rs:120:32
  12: rayon_core::job::JobRef::execute
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/job.rs:64:9
  13: rayon_core::registry::WorkerThread::execute
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:874:9
  14: rayon_core::registry::WorkerThread::wait_until_cold
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:820:17
  15: rayon_core::registry::WorkerThread::wait_until
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:803:13
  16: rayon_core::registry::main_loop
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:948:5
  17: rayon_core::registry::ThreadBuilder::run
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:54:18
  18: <rayon_core::registry::DefaultSpawn as rayon_core::registry::ThreadSpawn>::spawn::{{closure}}
             at /home/gh-bjorn3/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/registry.rs:99:20
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

The same crash happens with wasmtime. Running rayons test suite also results in this error.

Looks like cg_clif accidentally used PanicBoundsCheck for AssertKind::MisalignedPointerDereference causing a wrong panic message. The correct panic message is:
thread '<unnamed>' panicked at 'misaligned pointer dereference: address must be a multiple of 0x80 but is 0x7f29244ed1c0', /home/gh-bjorn3/cg_clif/rayon/rayon-core/src/registry.rs:523:24
stack backtrace:
   0: rust_begin_unwind
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_nounwind_fmt
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/core/src/panicking.rs:96:14
   2: core::panicking::panic_misaligned_pointer_dereference
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/core/src/panicking.rs:175:5
   3: rayon_core::registry::Registry::in_worker_cold::{{closure}}::{{closure}}
             at ./rayon-core/src/registry.rs:523:24
   4: rayon_core::job::JobResult<T>::call::{{closure}}
             at ./rayon-core/src/job.rs:218:41
   5: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/core/src/panic/unwind_safe.rs:265:9
   6: std::panicking::try::do_call
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panicking.rs:500:40
   7: std::panicking::try
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panicking.rs:464:19
   8: std::panic::catch_unwind
             at /home/gh-bjorn3/cg_clif/build/stdlib/library/std/src/panic.rs:142:14
   9: rayon_core::unwind::halt_unwinding
             at ./rayon-core/src/unwind.rs:17:5
  10: rayon_core::job::JobResult<T>::call
             at ./rayon-core/src/job.rs:218:15
  11: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute
             at ./rayon-core/src/job.rs:120:32
  12: rayon_core::job::JobRef::execute
             at ./rayon-core/src/job.rs:64:9
  13: rayon_core::registry::WorkerThread::execute
             at ./rayon-core/src/registry.rs:855:9
  14: rayon_core::registry::WorkerThread::wait_until_cold
             at ./rayon-core/src/registry.rs:802:21
  15: rayon_core::registry::WorkerThread::wait_until
             at ./rayon-core/src/registry.rs:777:13
  16: rayon_core::registry::main_loop
             at ./rayon-core/src/registry.rs:926:5
  17: rayon_core::registry::ThreadBuilder::run
             at ./rayon-core/src/registry.rs:54:18
  18: <rayon_core::registry::DefaultSpawn as rayon_core::registry::ThreadSpawn>::spawn::{{closure}}
             at ./rayon-core/src/registry.rs:99:20

Looks like WorkerThread is stack allocated and aligned to the cacheline size. Cranelift doesn't support aligning stack values to more than 16 bytes yet. If I heap allocate WorkerThread all tests pass except for a single test which requires panic=unwind.

Fixed in 55380a5f. The entire rayon test suite now passes with the exception of a single test which tests the behavior of rayon when user code panics as cg_clif doesn't yet support unwinding on panics. In addition the entire test suite of rav1e passes on aarch64, but on x86_64 it requires _mm_avg_epu16.


chore: bump to Vue 3.0.0-beta.15

@pikax If you don't mind, I'd like your opinion on the failing dts test:
// no data provided
expectError(
  mount(AppWithDefine, {
    data() {
      return {
        myVal: 1
      }
    }
  })
)

is not throwing error with beta.15 whereas it was when you introduced it. Is there something we need to change in our mount signatures or is it normal that this does not fail anymore with mixins and entends?

This is just a types error that is breaking things yeah? What changed in Vue core 🤔

@lmiller1990 Nothing major, but it looks like we lost a bit of inference. Not a big deal, I just want to make sure we're not mising something ;)

@pikax Thanks for your help!
@lmiller1990 If that's OK with you, we can merge and I'll take care of removing the TODO when https://github.com/vuejs/vue-next/pull/1361 is merged and released (I hope it will make it in beta.16). Or we can wait for beta.16, as you wish

Seems like it's fine to wait - this PR isn't blocking anything.
Thanks for this!

Looks like we are good to merge yeah @cexbrayat ?

👍 I'll remove the TODO when beta.16 will be out


feat: upgrade capacitor v5 to v6

Migrate to capacitor v6

Hey sorry to bother but can we get a merge and release for this?
@epicshaggy @lcsoka @mlynch @rdlabo

I created a new PR (#111) as this PR did not meet all requirements. Nevertheless, thanks for the contribution!


⚠ Bofrost.de has degraded performance

In 5334144, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 817 ms

Resolved: Bofrost.de performance has improved in 4fd8245.


THRIFT-2721: reduce complexity of generated erlang code and add tests

This would need to be rebased and corrected, pass CI builds and code review.

@jfarrell please close this PR per my comments in Jira.  Thanks.

@jfarrell this can be closed; the Jira ticket is resolved.


a hacky unscoped option for csjs `require("csjs/unscoped")

I added a simple, minimally invasive bypass option to the scopify module.
Then I added a meta-function to the main csjs module, that builds the returned csjs method with either scoped class names or non-scoped class names.
This should probably be re-designed in the end, but it should work for now, with minimal changes to csjs.
now you can require("csjs/unscoped")

Coverage decreased (-1.4%) to 98.649% when pulling 74fa00f82434feeb8a0039d8b9a4a3c0b4835853 on SilentCicero:master into 695d7820f61e7c6bae6b264f8bde3b8e444289dc on rtsao:master.

This has since been implemented 😄


XGBoost - Use DaskDeviceQuantileDMatrix with GPU Training

Fixes #525
Goals :soccer:

Use more efficient datatype for training with GPU + XGBoost by default.
The DeviceQuantileDMatrix is recommended when using GPU to reduce memory usage and improve speed of training.
Implementation Details :construction:

When tree_method="gpu_hist" is used. Automatically switch the datatype used for training from DaskDMatrix to DaskDeviceQuantileDMatrix.
Testing Details :mag:

Test added for the default behaviour with gpu_hist - that the data used for training is of type DaskDeviceQuantileDMatrix. And checking that the optional argument added to the fit method use_quantile=False can be used to disable this.

Looks great! 🙌 🙂 Having this functionality will be very useful for running on GPU/large amounts of data!
One parameter that is very helpful when instantiating a DaskDeviceQuantileDMatrix is max_bin. It is the knob that allows you to turn down the precision of the calculation in order to limit your memory footprint (or conversely, to dial it up which can be quite useful in case of skewed data).
Your implementation is very elegant and I don't want to mess it up in any way. But I am wondering -- would there be a way to expose the max_bin parameter to the user?

@oliverholworthy I tried max_bin out and the default value of 256 seems to offer good performance and what is probably even more important, changing this value doesn't impact memory footprint to the extent I anticipated, there is an effect but smaller than I have imagined.
I am thinking that probably working towards exposing the max_bin parameter would be getting too much into the weeds and is likely not worth it at this point in time, given the other higher-level but generally much more useful functionality that we could have.


test: change zerodev e2e tests to use .env wallet

Requirements

change zerodev e2e tests to use .env wallet
use waitForUserOperationTxn and update test timeouts to 50 seconds for tests to account for "replacement underpriced" errors from not waiting enough time for prev. tests' sendUserOperations.

Tests:

PR-Codex overview
Detailed summary

Added API_KEY and OWNER_MNEMONIC constants to constants.ts in packages/accounts/src/kernel-zerodev/e2e-tests
Modified AccountSigner class in packages/ethers/src/account-signer.ts to include waitForUserOperationTransaction property
Modified simple-account.test.ts in packages/ethers/e2e-tests, packages/core/e2e-tests, packages/alchemy/e2e-tests, and packages/accounts/src/kernel-zerodev/e2e-tests to use await with sendUserOperation and waitForUserOperationTransaction methods

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Current dependencies on/for this PR:

main

PR #54

PR #60   👈

PR #55

PR #56

PR #57

This comment was auto-generated by Graphite.

Graphite rebased this pull request as part of a merge.

Graphite couldn't merge this PR because it was not satisfying all requirements.

@moldy530 started a stack merge that includes this pull request via Graphite.

@moldy530 merged this pull request with Graphite.


[WelcomeUX] Don't open Untitled file when Welcome page is opened

Having both seems like too much. Instead we could add a New File action to the Start section. /cc @rebornix

@bpasero What do you think? (No untitled file if Welcome opens and New File in Welcome's Start section, screenshot below.)

Fine by me.


299 remove default prop values

Sets the default props to empty strings for the following components

Modal
TimePickerSelect
TextArea
DatePickerInput
Checkbox
ToolbarSearch
RadioButton
Search
FormGroup
ProgressIndicator

Closes carbon-design-system/carbon-components-react#299

Thanks so much @alisonjoseph for taking the time to contribute this! It's incredibly helpful 😄
For certain props that are required for a11y, we'd probably just want to make them required instead of defaulting to an empty string. How do you feel about that?

Yes, that makes more sense, I was a little unsure when removing the defaults for some of these.
I'm not entirely sure how to set them as required though 😄

I think simplest thing is just updating the propTypes definitions to be something like:
Foo.propTypes = {
  // ...other props
  labelText: PropTypes.string.isRequired,
};

Would that work? And then just remove the field from defaultProps, if it exists.

I updated these to be required where it made sense, but did you mean remove them entirely? Or just keep the empty string in the defaultProps?

@alisonjoseph right, remove them completely. If we leave the empty string on the default props, then the isRequired check will always pass. It was my assumption that we want to make people pass in the label text as a non-null, non-empty string for a11y purposes. Let me know if that's not the case!

@joshblack that makes sense, however when I removed those then all the tests are failing for those components.
Warning: Failed prop type: The prop `labelText` is marked as required in `TextInput`, but its value is `undefined`.
          in TextInput

Just means we have to update the components calling it so that it doesn't use the default prop value (which was a generic message anyway).


Bug Fix: Embedded images must be restricted to mxc: URIs

#1921

Images with non expected URL appear like this:


Using React as a global variable, how to disable "react-in-jsx-scope"?

Hi guys,
On this project I have React as a global. I am getting this error:

What is the syntax for disabling this rule, 'react-in-jsx-scope' in JSON format?
Thanks,

Setting the react/react-in-jsx-scope rule to off in your .eslintrc should be enough to disable it:
{
  "rules": {
    "react/react-in-jsx-scope": "off"
  }
}

ESLint documentation


<EMAIL_ADDRESS>won't accept my follow request nor will it follow me back.

I read that the bot does not accept follow requests from accounts younger than 2 weeks old, however, I made my instance and my account on 2024.09.13, so it has now been almost 3. I thought maybe it might've been a problem with the bot not knowing when my account was made, as from my instance it says that the bot's account was made on the 16th, as seen below:

So I waited for it to be 2 weeks from the 16th under this impression. However, it is now 2 days after that, and it is still not accepting my follow request, so I am unsure what is happening. I am attempting to follow from user<EMAIL_ADDRESS>and my instance is a private IPV4 GoToSocial 0.16.0+git-f1cbf6f instance.

Hey, sorry for the trouble! Have you looked at https://fed.brid.gy/docs#troubleshooting ?

Also we've had at least some reports of interop trouble w/GoToSocial before, #1033. They've hopefully fixed them, but I haven't tracked that in detail, or whether those bug fixes are all released or in which version.

Have indeed, and unless I'm missing something everything here should be fine. My instance isn't blocking the bot's instance, and I am able to discover the bot and see its profile, as well as send a follow request, but then nothing happens. I'm not sure if #1033 is similar to my issue as they seemed to not be able to discover the bot at all.

Thanks for the info. Looking at our logs, when we fetched https://goto.tomato.pink/users/kelsey with Accept: application/activity+json, application/ld+json; profile="https://www.w3.org/ns/activitystreams", text/html; charset=utf-8; q=0.5 and an HTTP signature with keyId=https://fed.brid.gy/fed.brid.gy#key, we got an HTTP 500 back with a text/html body.

Oct 02 18:53:05 Marinette gotosocial[892]: timestamp="02/10/2024 18:53:05.983" func=server.init.func1.Logger.14.1 level=ERROR latency="562.026329ms" userAgent="Bridgy Fed (https://fed.brid.gy/)" method=GET statusCode=500 path=/users/kelsey clientIP=<IP_ADDRESS> pubKeyID=https://fed.brid.gy/fed.brid.gy#key errors="Error #01: AuthenticateFederatedRequest: error dereferencing account https://fed.brid.gy/fed.brid.gy: enrichAccountSafely: error getting account https://fed.brid.gy/fed.brid.gy from database after race: sql: no rows in result set\n" requestID=1mm98kmj04001hp5trs0 msg="Internal Server Error: wrote 910B"
This is what I'm seeing in the database.

Thanks. Sounds like you may need to ask the GoToSocial people.

Merging into #1033 to track our overall interop w/GoToSocial.


[Bug] Qbittorrent not saving the download path

Describe the bug
The download folder remains in appdata/qbittorent/config
To Reproduce
1-Download qbittorrent on Store
2-Download a torrent
Expected behavior
Downloads should be on DATA folder
Screenshots

tested without CASAOS, same problem.
Opened issue in hotio/qbittorrent repository:
https://github.com/hotio/qbittorrent/issues/36


What is {{#alacarte}} ?

Please join our chat at https://chat.vuetifyjs.com if you have any questions. Our issue boards are strictly for bug reports and feature requests.


Different Indicator position on IOS / Android devices

Hello,
We are using the plugin to show images f the same size / dimensions on a Content Page. The Indicators should be at the bottom of the image or alternatively under the image. (Bottom of the image is implemented).
We see on our devices that on IOS the Indicators are under the image and on Android devices it is inside the image. Is it a bug or a wrong implementation? Thanks.
IOS View:

The following XAML is used:
<cards:CarouselView ItemsSource="{Binding FirmImages}"                                     SelectedIndex="{Binding image_name}"                                     BackgroundColor="White">             <cards:CarouselView.ItemTemplate>                         <DataTemplate>                             <ContentView>                                 <Frame VerticalOptions="Start"                                        HorizontalOptions="FillAndExpand"                                        Padding="0"                                        HasShadow="false"                                        IsClippedToBounds="true"                                        CornerRadius="0"                                        Margin="0,0,0,5">                                     <Image Source="{Binding url}" />                                 </Frame>                             </ContentView>                         </DataTemplate>                     </cards:CarouselView.ItemTemplate>                     <controls:IndicatorsControl AbsoluteLayout.LayoutBounds="0.5,0.87,-1,-1"                                                 SelectedIndicatorStyle="{StaticResource ActiveIndicator}"                                                 UnselectedIndicatorStyle="{StaticResource InactiveIndicator}" />                 </cards:CarouselView>

Hello, I don't think it's a bug
Probably images on android and iOS take different space sizes.

Hello, I don't think it's a bug
Probably images on android and iOS take different space sizes.

Indicators are exactly at that place where you put them)
It seems that Image doesn't expand to take all available card's space

Indicators are exactly at that place where you put them)
It seems that Image doesn't expand to take all available card's space

Replace images with colored BoxViews and check if positions are different indeed.

Replace images with colored BoxViews and check if positions are different indeed.


Agreement categories table

DOD:
Categories table in hasura.

[ ] Validate with Tzur that we're dealing with one to many relations
[ ] Each category should contain a group (one to many), required
[ ] Each agreement should contain a category (one to many), optional

Q:
Each category should contain a group (one to many), required = if the connection is a category has at least 1 group, how to model it? If I understand correctly, I would think to have a categories table with name and ID, and in the GROUPS table to have a category column. not the other way around.


s/vector/riot/

Replace references to Vector with Riot (when appropriate).

ok to test

Thank you!


test: skip flaky tests :sadpanda:

Current dependencies on/for this PR:

main

PR #177   👈

PR #175

PR #176

This comment was auto-generated by Graphite.


Function Not Showing After Python Deploy To Lambda

Every other step worked fine while building this and I even moved ahead to create the Skills early and get the SKILL_APPID because it seems to ask for it in the env file. However, now I am not seeing any functions after using running the python commands in Terminal (Ubuntu 16.04).
At first I was seeing this error:
File "/usr/local/lib/python2.7/dist-packages/botocore/regions.py", line 135, in _endpoint_for_partition
    raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.

I made sure to change the region back to "us-east-1" as I had it as "us-west-1" and it seemed to move further through the process but now I get this alert:
:/kodi-alexa-master$ python deploy-to-lambda.py

Traceback (most recent call last):
  File "deploy-to-lambda.py", line 19, in <module>
    os.mkdir(app_name)
OSError: [Errno 17] File exists: 'kodi-alexa'

Checking the Lambda Management Console shows no Functions listed and I am not able to move forward.

Delete the folder kodi-alexa and try running the command again.

Thank you. Back to this error now
Starting new HTTP connection (1): <IP_ADDRESS> Traceback (most recent call last):   File "/usr/local/bin/lambda-deploy", line 11, in <module>     sys.exit(main())   File "/usr/local/lib/python2.7/dist-packages/lambda_deploy/lambda_deploy.py", line 360, in main     name=options.name   File "/usr/local/lib/python2.7/dist-packages/lambda_deploy/lambda_deploy.py", line 75, in __init__     self.client = boto3.client('lambda')   File "/usr/local/lib/python2.7/dist-packages/boto3/__init__.py", line 83, in client     return _get_default_session().client(*args, **kwargs)   File "/usr/local/lib/python2.7/dist-packages/boto3/session.py", line 263, in client     aws_session_token=aws_session_token, config=config)   File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 828, in create_client     client_config=config, api_version=api_version)   File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 69, in create_client     verify, credentials, scoped_config, client_config, endpoint_bridge)   File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 222, in _get_client_args     verify, credentials, scoped_config, client_config, endpoint_bridge)   File "/usr/local/lib/python2.7/dist-packages/botocore/args.py", line 44, in get_client_args     endpoint_url, is_secure, scoped_config)   File "/usr/local/lib/python2.7/dist-packages/botocore/args.py", line 101, in compute_client_args     service_name, region_name, endpoint_url, is_secure)   File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 295, in resolve     service_name, region_name)   File "/usr/local/lib/python2.7/dist-packages/botocore/regions.py", line 122, in construct_endpoint     partition, service_name, region_name)   File "/usr/local/lib/python2.7/dist-packages/botocore/regions.py", line 135, in _endpoint_for_partition     raise NoRegionError() botocore.exceptions.NoRegionError: You must specify a region.
I have the region in the LAMBDA file so not sure why it is asking for the region:
AWS_DEFAULT_REGION = us-east-1 LAMBDA_TIMEOUT = 60 LAMBDA_MEMORY_SIZE = 128 LAMBDA_HANDLER = wsgi.lambda_handler

What do you mean when you say "I have the region in the LAMBDA file"?
Are you using the .env file?

My guess is he/she didn't copy .env.lambda to .env before editing.  It seems Windows users frequently have trouble doing this, due to Windows wanting to 'correct' the filename.

Sorry, my fault for working off a guide instead of using the README file.
I never copied the files. I saved ".env.lamba" to ".env" and ran again and it seemed to work.
However I did get this error in the middle. Is this something to worry about:
WARNING:lambda_deploy: Skipping inclusion of of .env file - use LAMBDA_ENV_VARS instead (see documentation for more information)

You can safely ignore that.  It's simply telling you that it's not going to upload the .env because that would be a security risk.


update ring_vmfile.c : add listdir function

listdir function only gets exist folders and files in the path which passed as a parameter
without gets sub folders content

Thanks for the pull request
Just a little update
Before using RING_API_ERROR
Free the allocated string (str)
Because the Ring Code may call your function inside (Try/Catch/Done)
And avoid the runtime error
This will lead to a memory leak because of (str) is not deleted
Keep up the GREAT WORK


Colors will not work on my newly registered system.

Basically as said above, I deleted and re-imported my system so I could have the new ID's, and now pluralchum colors will not work at all with my system, but used to perfectly. It still works with other systems in servers I am in, but not ones with the new ID's.

Nevermind it was my privacy settings I am n

wait nevermind it broke again.

Two things you can try:
Clearing your cache (click the "Clear Cache" button in settings)
Check your contrast settings


Deprecate schema name field in table config

Apparently, it's more error-pruning and causing more confusion.
Plan is to always align table name with schema name.
Migration plan:
Controller can scan all tables with customized schema name and copy schema to table name, then update table config. In case the schema name is already occupied. We need to copy schema name to <table_name>_tmp, all table configs. Iterate all tables, then copy schemas from <table_name>_tmp to <table_name>, and update schema name again.
For any new table creation, if there is a reference schema, alway copy the schema then create table without schema name field.
Cc: @Jackie-Jiang

I'd suggest enforcing it instead of trying to handle the bad config by copying and renaming underlying. If we do this transparently, it can actually cause confusion because user might find their uploaded schema disappear, or the modification not reflected. Also, it is adding management overhead.
We can do an one time effort to move the existing schema, but for new tables, we simply disallow using different schema name. This way we can ensure a clean connection between table and schema

Sounds good to me. Schema is also a deprecated field in table configuration, I think it's ok to enforce schema.

@xiangfu0 @Jackie-Jiang

Can we keep a new REST API open for this action ? - Given a table name which allows a new schema with same name as table to be created from the existing schema  if the table name and existing schema are different.
As the table name and schema are going to be the same , in the long run can we start deprecating the API's for schema specific actions & extending the scope of table config API to edit the schema as well?

@eaugene The current plan is to do a one time modification to all the existing tables without manually trigger the API for each individual table, one implementation example is #11574. Do you have concern on this approach?

@xiangfu0 @Jackie-Jiang

Can we keep a new REST API open for this action ? - Given a table name which allows a new schema with same name as table to be created from the existing schema  if the table name and existing schema are different.
As the table name and schema are going to be the same , in the long run can we start deprecating the API's for schema specific actions & extending the scope of table config API to edit the schema as well?

One thing I can think of is to have an option to copy schema from referred schema name to table name.
The behavior of multiple tables referring to the same schema should be deprecated.

@eaugene The current plan is to do a one time modification to all the existing tables without manually trigger the API for each individual table, one implementation example is #11574. Do you have concern on this approach?

Thanks @Jackie-Jiang  for sharing the PR  . My only concern being having it as a periodic job is makes the action hidden from the table owners sight . Should we have it more transparent ?


SideNav: component overflow is not scrolling within the bounds of the component

When there is overflow, the entire page becomes scrollable.
Scrolling should be limited to the bounds of the component

Vertical scrolling set to auto in anchored forms.


Crawling through Google Analytics Script

Hi,
Firstly, thanks for the neat tool.
I use Google Analytics on my website, and whenever I run the following command:
$ sitemap-generator --path=public/code/ code.snipcademy.com
I get around 70 errors that are similar to below:
Not found: http://code.snipcademy.com/tutorials/data-structures/graphs/g;m.parentNode.insertBefore%28a,m%29
Not found: http://code.snipcademy.com/tutorials/algorithms/g;m.parentNode.insertBefore%28a,m%29
Not found: http://code.snipcademy.com/tutorials/algorithms/sorting/g;m.parentNode.insertBefore%28a,m%29

The 'g;m.parentNode.insertBefore%28a,m%29 portion is for sure coming from the Google Analytics javascript. If you could fix this, that'd be great - thanks!

This has been a bug in the underlying node-simplecrawler package. I updated the dependencies and explicitly excluded URLs from scripts, as those don't have to be in a sitemap.
I created a new Version (v3.2.0) which should fix your issue. If not please reply here again.
Have a nice day.


type in one of the headings

[Enter feedback here]
Hi a typo in one of the titles
Identity high memory-consuming statements
Should be "Identify" I believe, like all the others. thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9d159ae2-da25-63a1-2f90-124c158ffd7e
Version Independent ID: 6226c3b2-0a5b-c762-540b-f1c9eaea1b41
Content: Monitor performance using DMVs - Azure SQL Database & SQL Managed Instance
Content Source: articles/azure-sql/database/monitoring-with-dmvs.md
Service: sql-database
Sub-service: performance
GitHub Login: @julieMSFT
Microsoft Alias: jrasnick

@Miteshc1 We are checking this and will get back to you.

@Miteshc1 Thanks for the feedback and your help to make the documentation better. We have raised the request https://github.com/MicrosoftDocs/azure-docs-pr/pull/119392 to correct this.
Once approved you will see the changes in a day.


Feature Request: Add function to preprocess amount

My project uses a lot of dollar amounts but they are all stored on the server as "in cents." ie. $10.00 would be stored as 1000.
Currently, I have to pass these amounts through two filters, one to convert the amount from "in cents" to "in dollars" before passing it into the currency filter. It would be nice to be able to provide the currency filter config a function to do this.
Example:
Vue.use(VueCurrencyFilter, {
  symbol: "$",
  thousandsSeparator: ",",
  fractionCount: 2,
  fractionSeparator: ".",
  symbolSpacing: false,
  convert: function (amount) { return amount / 100 }
})

If you feel this is within the scope of the vue-currency-filter, and I would understand if you don't feel it is, I would be happy to give this shot and send you a pull request.

Can you help to check the code? Maybe you can build it for your needs.
I think it's good addition.

@mazipan Is this feature still open for a PR?

The project has great utility for some use cases but we need to work on the code quality as well to maintain a good developer experience for all potential contributors.
Should I make a PR with a linting set up first?
There are lint errors in almost all modules.

Yes sure

Any news on this one ? 🤗


Is it possible to draw a hole in polygon?

 For example, when user hold option key and draw new polygon inside existing polygon, it becomes a hole.
something like this http://jsfiddle.net/erictheise/VaGy5/

yes I'm going to support holes in all shapes in some way or another. It'll take a little time though

Hello,
I downloaded package. So many files. I want to look for only js and css
file. How can i easily test it?
Thanks.
Regards,
Kosa
On Tue, Aug 29, 2017 at 10:00 PM, Sumit Kumar<EMAIL_ADDRESS>wrote:

@leekosal https://github.com/leekosal can you try this branch #198
https://github.com/codeofsumit/leaflet.pm/pull/198 and see if it is
working for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/codeofsumit/leaflet.pm/issues/150#issuecomment-325692123,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXo2GPKrDDrADh6dULteW2wU7y_8aQcfks5sdCeIgaJpZM4M0YE0
.

Open terminal, go to project folder. Type
npm install && npm run build
Then there will be a dist folder with CSS and JS files in it. Thanks for trying!

Here are two tests that I've posted on twitter yesterday:

merged it now. Please test it if you can just to make sure. Will be in the next release 👍


[1.20.1]Compatibility with Every Compat(wood types goes wrong)

The wood(cypress and muddy_oak)noteblock does not sound to Bass like all woods should have. And could not be recognize by every compat.
https://github.com/MehVahdJukaar/WoodGood/issues/388#issuecomment-1883539490

Fixed in version 1.0.1
Download link: https://www.curseforge.com/minecraft/mc-mods/good-ending/files


Some transformations on @(ReferencePath) result in mangled references

Some builds fail with an error like
(CoreCompile target) ->
  CSC : error CS0006: Metadata file '%(FullPath)' could not be found

when building using VS 15.3 preview 2 builds (which are not yet public).
This ItemReferenceGroup sets a default value for the ReferenceAssembly metadata of ReferencePath items to %(FullPath). The engine evaluates that as a literal string, but it can be successfully read through by item transformations like FindReferenceAssembliesForReferences's @(ReferencePath->'%(ReferenceAssembly)'), because the evaluator recurses--it sees that literal, interprets it as a metadata reference, and reads the FullPath metadata.
However, not all transformations perform that recursion. An ITask implementation that uses return new TaskItem(oldItem), for example, evidently escapes the metadatum string, and when it is expanded it turns into a literal %(FullPath) instead of the value of the FullPath metadatum.
FindReferenceAssembliesForReferences then populates ReferencePathWithRefAssemblies with a list of items whose identity is %(FullPath), which isn't valid and confuses the compiler, producing the error above.
This is a regression introduced by e3a3d69 when implementing #1986.

You can work around the bug by setting the property
<CompileUsingReferenceAssemblies>false</CompileUsingReferenceAssemblies>

which avoids transforming @(ReferencePath) using the recursive metadata expansion.

Thanks for reporting this @KirillOsenkov and @ToddGrun.
FYI @dsplaisted--the task that hit this for them was StrongNamer. Filed https://github.com/dsplaisted/strongnamer/issues/14 in the hopes that anyone who sees it will find it there.

fyi @jcouv -- I'll also want to fix this in 15.3 p3.


ReplayKit broadcast extension : Getting Undefined symbols for architecture x86_64:   "_ExampleCoreAudioDeviceGetCurrentQueue", referenced from:       ScreenShare.ReplayKitVideoSource.processFrame(sampleBuffer: __C.CMSampleBufferRef) -> () in ReplayKitVideoSource.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

Before filing an issue please check that the issue is not already addressed by the following:

Video Guides
Changelog.

If this is an issue with the QuickStart itself, file it here. If this is an issue with the SDK or how to do something with the SDK please use twilio-video-ios instead.
Please ensure that you are not sharing any
Personally Identifiable Information(PII)
or sensitive account information (API keys, credentials, etc.) when reporting an issue.

Description
[Description of the issue]
Steps to Reproduce

[Step one]
[Step two]
[Insert as many steps as needed]

Code
// Code that helps reproduce the issue

Expected Behavior
[What you expect to happen]
Actual Behavior
[What actually happens]
Reproduces How Often
[What percentage of the time does it reproduce?]
Logs
// Log output when the issue occurs

Versions
All relevant version information for the issue.
Video iOS SDK
[e.g. 1.3.12 via CocoaPods]
Xcode
[e.g. 9.2]
iOS Version
[e.g. 11.2.6]
iOS Device
[e.g. iPhone 8 Plus]

It would be helpful to see your project configuration. Do you have ExampleReplayKitAudioCapturer.m included in the project and set to build for your target? The linker error makes me believe that while you have the header file, the linker cannot find the built objects at link time.

Hello
Thank you for your reply, I have added that file but it did not work, what
works is I deleted the entire extension thing and then create it again. And
it working fine now. Do not know how but right now working.
Thank you for you reply again..
On Wed, 5 Feb 2020 at 7:49 PM, Ryan C. Payne<EMAIL_ADDRESS>wrote:

It would be helpful to see your project configuration. Do you have
ExampleReplayKitAudioCapturer.m included in the project and set to build
for your target? The linker error makes me believe that while you have the
header file, the linker cannot find the built objects at link time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twilio/video-quickstart-ios/issues/451?email_source=notifications&email_token=AGMX6NFKCF6NIE77MI24W6TRBLDFNA5CNFSM4KMRIKOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK3SSZA#issuecomment-582429028,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMX6NGPWI5F3DDYK6SUQHLRBLDFNANCNFSM4KMRIKOA
.

@Zindal,
I’m glad to hear you got it resolved. Let me know if you have any further questions.
Ryan

@paynerc
I am facing this issue.
Undefined symbols for architecture arm64:   "_ExampleCoreAudioDeviceGetCurrentQueue", referenced from:       KeepFluent.ReplayKitVideoSource.processFrame(sampleBuffer: __C.CMSampleBufferRef) -> () in ReplayKitVideoSource.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

Hello,
I am facing the below error while integrating the TwilioReplyKit Extension:
ReplayKit broadcast extension : Getting Undefined symbols for architecture x86_64: "_ExampleCoreAudioDeviceGetCurrentQueue", referenced from: ScreenShare.ReplayKitVideoSource.processFrame(sampleBuffer: __C.CMSampleBufferRef) -> () in ReplayKitVideoSource.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
As per the above solution, I have tried with removing the broadcast extension and recreate it. But not successed.
To further update, below is the steps I followed:

Added "ReplayKitVideoSource.swift" file into my main project.
Created Broadcast Extension and added Twilio Pod. (Extension name is "BroadcastExtension"
I have added POD as below:

target '' do
Comment the next line if you don't want to use dynamic frameworks
use_frameworks!
Pods for
pod 'TwilioVideo', '~> 3.6'
end
target 'BroadcastExtension' do
use_frameworks!
pod 'TwilioVideo', '~> 3.6'
end
But after adding the pods, it is giving error for the file "ReplayKitVideoSource.swift". If I remove this file, the project successfully compiled. But when I am adding this file, facing the above issue.
Please let me know for that.

@Nishant9SPL,
ReplayKitVideoSource.swift currently has a dependency on the ExampleReplayKitAudioCapturer Objective-C files that are in the BroadcastExtension folder of the ReplayKit example. This is referenced here.
If you are integrating the example code into your application, you would also need to be sure to add the files in the BroadcastExtension folder as mentioned above.
Ryan

@paynerc
Yes, I have already added "ExampleReplayKitAudioCapturer.h" and "ExampleReplayKitAudioCapturer.m".
Also,  added Bridging Header file into extension as well.
Then also it is giving the same error.
-- Nishant


Installation

How do I install this?

Like any other fisher plugin. See https://www.jhipster.tech/fisher/ for details or do you have a specific problem/error?


Update requirements of manifest.json

Since HASS core 2024.4.0 the module "apscheduler" can not be loaded and it throws an error message. Adding "apscheduler" to the requirements solves the issue.

Hi, I confirm the issue and the fix. Thank you.

Thanks a lot @gerherha !


Verbose should contain Retry task instead of oposite

@rultor release, tag=0.11.3

@rultor release, tag=0.11.3

@dgroup OK, I will release it now. Please check the progress here

@rultor release, tag=0.11.3

@dgroup Done! FYI, the full log is here (took me 4min)


BUG image counter broken.

Image counter does not count all images sent in.

Please put in a fix. Possible before deploying on sunday @mattwr18 ?

This is a duplicate issue. I can link to it later, but I think we should close this in favor of the older issue.

Here is the original issue https://github.com/tactilenews/100eyes/issues/813. The fix is related to another issue https://github.com/tactilenews/100eyes/issues/1387 and is not something that can be quickly done.

related to #996 996 und #813 @mattwr18

Closed via https://github.com/tactilenews/100eyes/pull/1538


Lazy extensions

Opening this to discuss the developments in the lazyextensions branch.
It adds:

a Strict type class, that circumvents implicit divergences like Lazy, without the overhead of an anonymous function when instantiated (hence an extra class),
the possibility to extend Lazy with extensions, able to change the current derivation and its state, and keep their own state along with it,
a Priority type class and a Lazy extension, to be used wrapped in an implicit Strict or Lazy, like

implicit def mkTC[T]
 (implicit
   priority: Strict[Priority[TC[T], Other[T]]]
 ): TC[T] = priority.value.fold(identity)(_.mkTC)

which looks up for a TC[T], else for a Other[T], taking into account that a TC[T] is also provided through itself (and ignoring it in the first TC[T] lookup - thus looking for orphan TC[T] only),

various inlining of implicits in the Strict and Lazy output, for less overhead (see https://github.com/milessabin/shapeless/commit/1add5ffd55a7b04aef23022a9bd5089ed694436d).

Also things that proved not to be useful, that I'd like to remove carefully, like

some changes in Generic,
using the state monad to manage the derivation state,
keep track of implicit lookup that failed, not to look them once more,
a lazy extension called Scoped, that keeps the implicit dict from a lookup to the next (-> more caching).

I'm somehow benchmarking this versus the macro-based derivation of upickle, with a modified version of it. The better I get is a bit less than a 3 times longer compile time for its tests :-( (from initially... much more than that).

I'd like to remove what turned out unnecessary above, then this would be fine for a merge for me.

Almost done or ready for review. What's missing:

scaladoc
merge some commits with previous ones
scala 2.10 port (just a matter of merging lazy.scala in the scala-2.10.x branch)
tests of the cached versions of Lazy/Strict (maybe with a stateful implicit macro, counting the number of times it gets called?)

Awesome!
You've been hinting at compile time speedups ... do you have any benchmarks of that?

Yes, with the tests of https://github.com/alexarchambault/upickle-pprint. I'm trying to disentangle the effects of the various changes I made (both here and there).

Quick update: while assessing the effects of each change differently than my initial attempts, I found that one of them (inlining) sometimes slows things. I may remove it, I'm investigating further...
Also, the biggest speed ups seem to come from some "best practices" on the deriving library side, more than from changes here. I'll come up with clear benchmarks soon.

Would you say this is ready for review now?

@milessabin Not yet, I'm just ensuring that all its changes are really necessary, with various benchmarks (that I'll put online right after). It's almost done, but for inlining in Lazy results. I hope to have them, and clean the PR, later today.

I'd say its ready for review now :-)
Some benchmarks about the various additions of this PR are available here.
Only thing that does not speed up things is Implicit (https://github.com/milessabin/shapeless/commit/b9d46fcd1e6108c351ef9552e79031fe65d6c29d). I still find it nicer (and with a broader scope) than the current Values though, so I left it here for now.
Some minor points that I would like to change (but which don't prevent reviewing):

remove unnecessary 0 suffixes in some variable / method argument names,
simplify some unnecessarily complex variable / method argument names (e.g. instTpe -> tpe).

The last commit would have to be stripped before a merge (and either update the MIMA config, or bump version to 2.3.0-SNAPSHOT and temporarily disable MIMA).

This is looking pretty awesome :-)

@milessabin I'd recomment inspecting at the changes of this PR through https://github.com/milessabin/shapeless/tree/topic/lazyextensions, looking at the commits one-by-one (and the individual commit messages provide some explanations too).

By the way, I ported that to 2.10 too (https://github.com/milessabin/shapeless/tree/topic/lazyextensions-2.10.x). The port is not up to date anymore because of various rebase / changes, but I'll update it once the developments here are fine.

At this point I think I have only two concerns, one minor, the other hopefully minor.
I think that the introduction of Strict as a name here to contrast with Lazy is revealing that neither name is particularly good. What both of these are doing is allowing implicit resolution to continue to a fixed point. Laziness at the value level is necessary somewhere along the line, but the key thing is the type level fixed point.
I think I'd now also prefer to point people at Cats's Later if they want something with the value level properties that shapeless's Lazy currently has.
So I'd be inclined to come up with a new pair of names, alias Lazy to the appropriate one of them and deprecate Lazy.
That's the minor issue: it's "just" about names and deprecation ;-)
The hopefully minor issue is the changes in the serialization tests. If there's a change in behaviour here then we need to deal with it. If there isn't then I think we have a pretty bad bug in shapeless as it stands which needs to be fixed independently of this PR.

Just pushed new changes, adding extra tests (https://github.com/milessabin/shapeless/commit/d34fc337932fbfd31d4ac86e4ab926eed957589d, https://github.com/milessabin/shapeless/commit/a609a7e25ea561f494f76ecbd54e7c73a9b2f746), some scaladoc (https://github.com/milessabin/shapeless/commit/fd45288f468cf99fa25316bc583afd8c2780cded) in particular.
Only remaining problems (correct me if I'm wrong):

outer reference capturing in SerializationTests.testShow (failing tests commented out for now) in 2.12,
renaming?

About the outer reference capturing, the inlining in the generated trees seems to be the problem. If one comments out .optimize in this line, the tests pass. I don't really know why the transformation that inlining would make the result capture an outer reference (and only so in 2.12), but I haven't looked closely at the trees generated in the failing tests yet.

WRT Global ... how confident are you that the lifecycle of those caches is well behaved. Previously the lifetime of a cached was bounded by the nesting of implicit resolutions through a Lazy type constructor: there would always have been a well defined entry point with an empty cache and a well-defined exit point where the cache could be discarded. Presumably that's no longer the case?
So I guess that the potential trouble spots would be with incremental compilation and the presentation compiler. Do you have a feel for how this behaves with SBT ~testQuick and ENSIME? /cc @fommil

if you want a good testbed, try updating the sexp.scala example and open it up in ENSIME. Or migrate spray-json-shapeless to use Strict instead of Lazy and see how the tests behave.

I already tested that a bit with the comprehensive test suite of upickle, with an ad-hoc port of it to shapeless with the changes of this PR. See this project for an analysis of it (with comparison to upickle original macros - at then end, the shapeless version still makes the tests take 2.5x longer to compile).
I also ported argonaut-shapeless and scalacheck-shapeless to it, without facing any particular issue, but their test suites are not as comprehensive than the ones of upickle.
I tended to avoid incremental compilation with the test suite of upickle, to compare the compile times to previous versions in particular. I don't really know if it could be risky here.
I would expect libraries using it to have two versions of their API, one with Cached implicits, and the other without, so that users could use the latter first, and switch to the former if compile time is an issue. That would lower the risk of irky things to happen.

@fommil  I'll write something about the kind of changes I made to lower compile times (benchmarking with https://github.com/alexarchambault/upickle-pprint). I can send you an update of spray-json-shapeless if ever it takes too long.

:smile: yeah looks like Lazy => Strict and I'll play with Strict.Cached. I'll wait for this to be merged... I assume this will result in a big version bump in Shapeless?

Probably.

I'll be testing via snapshots way ahead of that, hopefully. Just let me know when a snapshot is available please.

OK, I think I'd like to get this merged so that we can start getting people playing with snapshots.
We can defer naming and the remaining test issues until later.
We should bumped the version to 2.3.0-SNAPSHOT.
We should reinstate the MiMa checks ... with previousArtifact set to 2.3.0 this will be a NOP.
If you'd like to squash any of the commits, please do :-)

Ah, yes, rebase against master too ...

Do you have a feel for how much of an effect does the inlining has?

Playing around with the inlining a little ... I've been able to get the tests to pass by commenting out the .orElse(inline) here which seems a bit less drastic than your suggestion of removing the whole optimize step.
Can you say a little more about what prioritySubstitute and inline are doing? I'm guessing that the former has important semantics, whereas the latter is (supposed to be) semantics neutral?

+1 for a RC process for this (and recommend people to give snapshots a try).
I bumped version to 2.3.0-SNAPSHOT, updated the mima previous artifact, and temporary disabled the mima check (all at once in https://github.com/milessabin/shapeless/commit/5529ba41ffce817632651f4231dffb1090108742).
I squashed some commits, but not all. Is it fine for you? I think it would be way harder to make sense of these changes if they were all squashed together.
It's rebased against the last master.
About inlining, in quick benchmarks that I just ran (based on https://github.com/alexarchambault/upickle-pprint), there's a slight gain (~10% speed up) if one removes it (all other things being equal). It mainly makes the output code simpler / more compact, which speeds up what's happening after implicit searches. The other optimization (simplifying trees with Priority.High) doesn't seem to bring much, I guess it could even be removed.
Inlining takes dict entries used only once (referred to by only one other entry), and substitutes their body in the latter (it replaces the Ident(some name) by the tree it is referring to). This makes the macro output simpler code.
The other optim detects implicits involving Priority.High. These are typically like mkTC(Lazy(Priority.High(value))), and mkTC just unpack the value wrapped in Priority.High then Lazy here. So the macro does that directly (replacing the previous expression by just value). But it doesn't bring that high gains appearently, maybe I should just remove it.

Fantastic! Thanks :-)
I've been thinking about the tree-rewriting part of this PR a bit more ...
On the inlining, I think that if the gain is only of the order of 10% at compile time then I'd prefer not to merge it, given that it's precisely that code which is causing trouble on 2.12.x. If the other transformation isn't making a significant contribution, then I'd prefer not to merge it either.
The reason I'm saying this is that these sorts of tree transformations, where we construct new trees from existing, already typechecked trees, are prone to very subtle bugs because of deficiencies in the the macro runtime. The thing that concerns me most is that even if we have a full set of passing tests, real code in the wild will use trees of different shapes and these will cause things to blow up in ways which are hard to predict, and hard for us to control given that the issues are in scalac. I've been playing whack-a-mole with prefix bugs for a while now, as you know, and I don't relish the prospect of a whole new class of hard to understand errors.
If the gains were more significant then it'd be a different story.
If you're willing to take those out I'll merge the rest of the PR immediately :-)

I removed inlining the PR. I think it can still be done through the newly added LazyExtensions, thanks to the (safe?) changes of https://github.com/milessabin/shapeless/commit/b2fc860f3b4cd50c24b3a337456e45fb80bf7646.
I'd like to add more tests of the global variants of Lazy and Strict, and possibly others I don't remember now, but these can be added later (and don't prevent merging).

Merged! Awesome job ... thank you :-)

Do you have bandwidth for the backport to 2.10.x?

I should in a few hours.
There's a not up-to-date one here: https://github.com/milessabin/shapeless/tree/topic/lazyextensions-2.10.x.
It should be too hard to port if you feel like trying. Else I'll do it later today, I remember the tricky points.

I'll leave it to you ... there's no huge rush :-)

yeah, I'm happy knowing that it'll come one day. I suppose I should go try this out with spray-json-shapeless and ensime then :smile:

@fommil yes, please do :-)

I get a stack overflow :cry: It also takes a lot longer to compile that before, taking about 70s for the tests.
I've pushed my changes to https://github.com/fommil/spray-json-shapeless if you could please have a look.

I didn't look at your code yet, but you know you must not only Stricts,
right? There still has to be some Lazys to break possible cycles.
Le lundi 17 août 2015, Sam Halliday<EMAIL_ADDRESS>a écrit :

I get a stack overflow [image: :cry:] It also takes a lot longer to
compile that before, taking about 70s for the tests.
I've pushed my changes to https://github.com/fommil/spray-json-shapeless
if you could please have a look.
—
Reply to this email directly or view it on GitHub
https://github.com/milessabin/shapeless/pull/435#issuecomment-131888406.

Nope didn't know that. Where are the docs of what to use when?

There are some scaladocs, but I have to write something about the big picture. It should be loosely based on https://github.com/alexarchambault/auto-type-class-benchmark (that needs to be updated, and is only for the braves in its current state :-)

if you could please have a look at sexp.scala in the shapeless examples and advise where you believe a Strict would hely, that would be good.

I updated a bit spray-json-shapeless, in this branch (not starting from the last commit from master, but from the previous one).
Beware if looking at the times here, to:

checkout the last shapeless,
change its version to a non snapshot one (like 2.3.0-87697b0) in version.sbt,
publish it locally,
and use this version from spray-json-shapeless during the test.

This way, SBT won't lose time checking for new versions each time it is run (as it does for snapshots). Comparisons will be more reliable.
I get bigger speed ups (like 50% in the most extreme cases) in my benchmark (link not up-to-date, better results since), but there are some differences with it (it is using Priority in particular).
To speed up compilation a bit more, you could try:

not using LabelledGeneric (just Generic), relying on an ad-hoc type class, materialized by a macro, to supply the labels in a List[String] (and trusting it that this list has the right length),
using ad-hoc type classes when deriving instances for HLists or coproducts (like WrappedRootJsonHListFormat[Wrapped, L <: HList] and WrappedRootJsonCoproductFormat[Wrapped, C <: Coproduct], and having two cases instead of familyFormat, one for HLists, the other for coproducts).

These brought nice improvements to me in the benchmark above (like 10% each).

I'm looking at this today, thanks

@alexarchambault fantastic! Thank you. I have some questions:

you removed some Lazys, is there an easy explanation why it was not needed here?
after moving to Strict you kept two Lazys around, is there an easy explanation for that?

btw, it's hard to say for definite, but it looks like ENSIME jerk/test (which is mostly compilation) has gone from 75 seconds to 60 seconds. Which is nice.
Did you say you'd expect a further performance enhancement by splitting familyFormat into two? I tried that and it didn't seem to make a difference.


feature: provide text box for device path entry in provider config

Not the prettiest thing out there, but it'll do until we find the time to figure out a nicer looking one.


Parse and write preamble layer data

Builds on #221 diff
The high level ideas here:

have a separate configuration namespace for preamble layers
process preamble layers when running layers (by making the CFR title/part optional)
look for those layers when writing (write_to). Preamble layers are written with the id "preamble:doc_num"

The individual changesets here are probably too confusing to review -- I went back and forth a few times. It may be easiest just to review the final diff.
Resolves eregs/notice-and-comment#18

Coverage decreased (-0.09%) to 91.118% when pulling 13c67747bd882966572b8b231e124e4adc6b0496 on cmc333333:18-preamble-layers into b5d5df04447b5105a1dd74a474b8d977ba259af4 on 18F:master.

Coverage decreased (-0.07%) to 91.131% when pulling ce87c245ad50b0b76019f4cc1e69720da733e962 on cmc333333:18-preamble-layers into b5d5df04447b5105a1dd74a474b8d977ba259af4 on 18F:master.

Coverage increased (+0.05%) to 91.143% when pulling 9b0e8a1777ef65581cd2f77e9b7420618c1b9c31 on cmc333333:18-preamble-layers into d6113a495e08cfa0d3f3e955b3d1c052ca43b048 on 18F:master.


Issue Relations Read Error for Copied Issues (Relation Type : copied_to)

Dears,
When reading the issue using .NET API 4.2.3; on ReadJson method in Redmine.Net.Api.Types.IssueRelation,
If the Related Issue is created using Copy feature, then Relation Type is coming as "copied_to".
But there is no copied_to type in IssueRelationType Enum then SDK throws an error.
When I added Copied_To enum type in IssueRelationType object, then the problem is solved.
Redmine Server Version : Unknown (Sorry, Remote Redmine we are using)
Redmine.Net.Api Version : 4.2.3
SerializationType : JSON

Create an Issue A
Create an Issue B using Copy To operation
Issue B will be listed under Relations of Issue A
Try to GetIssue for Issue A using includes:relations
Throws an error "copied_to was not found."

Solution

Add Copied_To in IssueRelationType Enum Class

"relations": [
{
"id": 2722,
"issue_id": 16767,
"issue_to_id": 17576,
"relation_type": "relates",
"delay": null
},
{
"id": 2921,
"issue_id": 16767,
"issue_to_id": 17571,
"relation_type": "relates",
"delay": null
},
{
"id": 2215,
"issue_id": 15557,
"issue_to_id": 16767,
"relation_type": "copied_to",
"delay": null
}
],
Bold item can not be deserialized from JSON because of undefined relation type.
Best regards

Thank you for pointing this out.


Support for mouseDown, mouseMove, and mouseUp

While click and rightClick works for most cases, we also need to be able to perform additional mouse functions to simulate drag and drop.

Thanks for the idea. I think the overall implementation is pretty simple and you can get done it yourself and send a PR. We use WebdriverIO as backend, and they have all those methods implemented in nice manner. I think they have even drag-and-drop thing. And you can submit pull request with adding those methods to CodeceptJS. All you need to write them in analogy with rightClick or doubleClick (i.e. to allow usage of strict locators and wrapping promises).
I will be glad to merge it

Seems simple enough.  I noticed that the docs mention being able to extend WebDriverIO via custom helpers.  So, I was heading down that path.  But, this functionality seems generic enough to create a PR so others can benefit.

Yes, sure, generic solved issues are welcome. That's the mission of CodeceptJS - to solve common issues in nice way )

I think this is still relevant.


Sketch Analytics System

base: https://info.uniswap.org/#/
what should it contain:

list of all swappable tokens
price of each token in fiat (determined through exchange rate to ae)
trading volume of each token

In order to avoid building a full ui we could also think about using grafana or something similar.

Additional data requested:

number of token holders
optional field for a description (from the backend) (Out of scope for the MVP)

moved to the wiki


Plutus transaction error when unlocking a script utxo

I have no problem creating the script address and locking the tokens, but am unable to close or buy the tokens. This is the error message I receive:
Command failed: transaction build  Error: The following scripts have execution failures:

the script for transaction input 1 (in the order of the TxIds) failed with:

The Plutus script evaluation failed: An error has occurred:  User error:

The provided Plutus code called 'error'.

Script debugging logs: PT5

As you can see, there is no specific error log, which makes this difficult for me to debug.
I'm certain all the information provided is correct, except for the close.json file. I'm not sure if I'm supposed to leave the "fields":[] section blank, but when I try filling it with the NFTSale information, it doesn't work.
I am also using the martify contracts release v1.0.0, with the correct plutus-starter commit for plutus-apps. On this note, does the cardano-cli version matter?
If anyone has any ideas of what's going on, I would love some help.

The information I provided was not correct - the datum-json command should be passed a text token-name, and not a hex token-name like with cardano-cli.


Bitfinex Error With JSON

 Error with JSON: {"message": "Could not find a key matching the given X-BFX-APIKEY."}. Retrying...

Receive this error when trying to connect to bitfinex. Problem Appears to be a malformed http request.

Here are other examples of people getting the same error:
https://bitcointalk.org/index.php?topic=528431.new

Uncommented this    // curl_easy_setopt(params.curl, CURLOPT_VERBOSE, 1L);
Saw this in the output.
X-BFX-APIKEY:"xxx"
X-BFX-PAYLOAD:xxx
X-BFX-SIGNATURE:xxx
Corrected this to be this:
X-BFX-APIKEY:xxx
X-BFX-PAYLOAD:xxx
X-BFX-SIGNATURE:xxx
But now I get the following error:
Error with JSON: {"message": "Invalid X-BFX-SIGNATURE."}. Retrying...

Hi @jspenc72,
Thanks for the feedback. When you put your credentials into the config file, make sure you don't include any quotes. It should be similar to this:
# Bitfinex
BitfinexApiKey=abcdef123456
BitfinexSecretKey=abcdef123456
BitfinexFees=0.0020

Can you please recreate an API key on Bitfinex and try again? Thanks.

What about the email addresses? Should they be in quotes?

On Feb 7, 2016, at 10:47 AM, Julien Hamilton<EMAIL_ADDRESS>wrote:
Hi @jspenc72,
Thanks for the feedback. When you put your credentials into the config file, make sure you don't include any quotes. It should be similar to this:
Bitfinex
BitfinexApiKey=abcdef123456
BitfinexSecretKey=abcdef123456
BitfinexFees=0.0020
Can you please recreate an API key on Bitfinex and try again? Thanks.
—
Reply to this email directly or view it on GitHub.

Still having the issue, blackbird.conf does not contain quotes. Set this Curl to verbose and got this
< HTTP/1.1 401 Unauthorized

Server nginx is not blacklisted
< Server: nginx
< Date: Sun, 07 Feb 2016 23:27:52 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 38
< Connection: keep-alive
< Vary: Accept-Encoding
< X-UA-Compatible: IE=Edge,chrome=1
< Cache-Control: no-cache

Still getting this:
 Error with JSON: {"message": "Invalid X-BFX-SIGNATURE."}. Retrying...

Testing with an api key and secret that have full permissions.

Sorry, i had a rogue' in my .conf. Removed and now Blackbird appears to be authenticating correctly but I get this:
Blackbird Bitcoin Arbitrage
DISCLAIMER: USE THE SOFTWARE AT YOUR OWN RISK
Log file generated: blackbird_log_20160207_183426.log
Blackbird is running... (pid 10607)

Hostname was NOT found in DNS cache
Trying <IP_ADDRESS>...
Connected to api.bitfinex.com (<IP_ADDRESS>) port 443 (#0)
successfully set certificate verify locations:
CAfile: none
CApath: /etc/ssl/certs
SSL connection using ECDHE-RSA-AES256-GCM-SHA384
Server certificate:
subject: OU=GT54605854; OU=See www.rapidssl.com/resources/cps (c)14; OU=Domain Control Validated - RapidSSL(R); CN=*.bitfinex.com
start date: 2014-10-16 17:43:37 GMT
expire date: 2016-10-15 19:38:19 GMT
subjectAltName: api.bitfinex.com matched
issuer: C=US; O=GeoTrust Inc.; CN=RapidSSL SHA256 CA - G3
SSL certificate verify ok.

POST /v1/balances HTTP/1.1
Host: api.bitfinex.com
Accept: /
X-BFX-APIKEY:111xxx
X-BFX-PAYLOAD:111xxx
X-BFX-SIGNATURE:111xxx
Content-Length: 0
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 200 OK

Server nginx is not blacklisted
< Server: nginx
< Date: Sun, 07 Feb 2016 23:34:26 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 2
< Connection: keep-alive
< Vary: Accept-Encoding
< X-UA-Compatible: IE=Edge,chrome=1
< Cache-Control: no-cache
< X-Runtime: 0.031755
< X-Rack-Cache: invalidate, pass
< Expires: Sun, 07 Feb 2016 23:34:25 GMT
< X-Frame-Options: SAMEORIGIN
< X-Iinfo: 0-10625592-10625593 NNNN CT(15 16 0) RT(1454888065555 49) q(0 0 0 0) r(0 0) U6
< X-CDN: Incapsula
<
Connection #0 to host api.bitfinex.com left intact
Found bundle for host api.bitfinex.com: 0xc985d0
Re-using existing connection! (#0) with host api.bitfinex.com
Connected to api.bitfinex.com (<IP_ADDRESS>) port 443 (#0)

POST /v1/balances HTTP/1.1
Host: api.bitfinex.com
Accept: /
X-BFX-APIKEY:111xxx
X-BFX-PAYLOAD:111xxx
X-BFX-SIGNATURE:111xxx
Content-Length: 0
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 200 OK

Server nginx is not blacklisted
< Server: nginx
< Date: Sun, 07 Feb 2016 23:34:26 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 2
< Connection: keep-alive
< Vary: Accept-Encoding
< X-UA-Compatible: IE=Edge,chrome=1
< Cache-Control: no-cache
< X-Runtime: 0.040354
< X-Rack-Cache: invalidate, pass
< Expires: Sun, 07 Feb 2016 23:34:25 GMT
< X-Frame-Options: SAMEORIGIN
< X-Iinfo: 0-10625592-10625593 SNNN RT(1454888065555 151) q(0 0 0 0) r(0 0) U6
< X-CDN: Incapsula
<
Connection #0 to host api.bitfinex.com left intact
Segmentation fault (core dumped)

This is my log file

Blackbird Bitcoin Arbitrage Log File

Blackbird started on 02/07/2016 18:34:26
[ Targets ]
Spread Entry:  0.80%
Spread Target: 0.30%
[ Current balances ]
~
~
~
~
~

This is my result file.
TRADE_ID,EXCHANGE_LONG,EXHANGE_SHORT,ENTRY_TIME,EXIT_TIME,DURATION,TOTAL_EXPOSURE,BALANCE_BEFORE,BALANCE_AFTER,RETURN

I am trying to use bitfinex and sevennintysix
The sevennintysix doesn't appear to be authenticating.
When the main.cpp gets to the loop that calls getAvail() on each exchange then it crashes on the second loop.

My blackbird.conf file lists them in this order.
Bitfinex
BitfinexApiKey=
BitfinexSecretKey=
BitfinexFees=0.0020
OkCoin
OkCoinApiKey=
OkCoinSecretKey=
OkCoinFees=0.0020
Bitstamp
BitstampClientId=
BitstampApiKey=
BitstampSecretKey=
BitstampFees=0.0025
Gemini
GeminiApiKey=
GeminiSecretKey=
GeminiFees=0.0025
Kraken
KrakenApiKey=
KrakenSecretKey=
KrakenFees=0.0025
ItBit
ItBitApiKey=
ItBitSecretKey=
ItBitFees=0.0020
BTCe
BTCeApiKey=
BTCeSecretKey=
BTCeFees=0.0020
796.com
SevenNintySixApiKey=
SevenNintySixSecretKey=
SevenNintySixFees=0.0025

I know you commented that 796 hasn't been tested but if you can provide any assistance I would greatly appreciate it.

Thanks in advance for your response  @butor

Hi @jspenc72,
Can you show us the output of the following command:
curl -v https://api.bitfinex.com/v1/ticker/btcusd

Also, can you comment again the line curl_easy_setopt(params.curl, CURLOPT_VERBOSE, 1L) then try to run Blackbird without 796 and show us the output?
I think the Segmentation fault (core dumped) you got is probably due to a bug in our 796 implementation (as you said it has never been tested).
Thanks

Here is the output
bash```
root@tribeca:~# curl -v https://api.bitfinex.com/v1/ticker/btcusd

Hostname was NOT found in DNS cache
Trying <IP_ADDRESS>...
Connected to api.bitfinex.com (<IP_ADDRESS>) port 443 (#0)
successfully set certificate verify locations:
CAfile: none
CApath: /etc/ssl/certs
SSLv3, TLS handshake, Client hello (1):
SSLv3, TLS handshake, Server hello (2):
SSLv3, TLS handshake, CERT (11):
SSLv3, TLS handshake, Server key exchange (12):
SSLv3, TLS handshake, Server finished (14):
SSLv3, TLS handshake, Client key exchange (16):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSLv3, TLS change cipher, Client hello (1):
SSLv3, TLS handshake, Finished (20):
SSL connection using ECDHE-RSA-AES256-GCM-SHA384
Server certificate:
subject: OU=GT54605854; OU=See www.rapidssl.com/resources/cps (c)14; OU=Domain Control Validated - RapidSSL(R); CN=*.bitfinex.com
start date: 2014-10-16 17:43:37 GMT
expire date: 2016-10-15 19:38:19 GMT
subjectAltName: api.bitfinex.com matched
issuer: C=US; O=GeoTrust Inc.; CN=RapidSSL SHA256 CA - G3
SSL certificate verify ok.

GET /v1/ticker/btcusd HTTP/1.1
User-Agent: curl/7.35.0
Host: api.bitfinex.com
Accept: /

< HTTP/1.1 200 OK

Server nginx is not blacklisted
< Server: nginx
< Date: Mon, 08 Feb 2016 15:53:16 GMT
< Content-Type: application/json; charset=utf-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Vary: Accept-Encoding
< Vary: Accept-Encoding
< X-UA-Compatible: IE=Edge,chrome=1
< ETag: "77d83bf71a9051244488c48beb888c4a"
< Cache-Control: no-cache
< X-Request-Id: 9b2885a564d6e1b61623f457a8744884
< X-Runtime: 0.008749
< X-Rack-Cache: miss
< Expires: Mon, 08 Feb 2016 15:53:15 GMT
< X-Frame-Options: SAMEORIGIN
< Set-Cookie: visid_incap_116519=U5O/u/XOSyKOz2FWSTYbHey5uFYAAAAAQUIPAAAAAABKHOAaOCjeTq3HjtAZzW2l; expires=Wed, 07 Feb 2018 14:42:57 GMT; path=/; Domain=.bitfinex.com
< Set-Cookie: nlbi_116519=1rnKMKvSgy/P7A3XGLrcwAAAAAAGpL0fmHBCl7T8Mo+9p0xx; path=/; Domain=.bitfinex.com
< Set-Cookie: incap_ses_128_116519=/1EaUTUrrCFATUJRH8DGAey5uFYAAAAAd+aIn213SyR2HNtVlaoDSQ==; path=/; Domain=.bitfinex.com
< X-Iinfo: 10-101585433-101520497 PNNN RT(1454946796211 49) q(0 0 0 1) r(0 0) U5
< X-CDN: Incapsula
<
Connection #0 to host api.bitfinex.com left intact
{"mid":"374.36","bid":"374.31","ask":"374.41","last_price":"374.41","timestamp":"1454946788.551013788"}

Blackbird runs fine without 796, or kraken

the output is the same as the readme.

--------------------------------------------
|   Blackbird Bitcoin Arbitrage Log File   |
--------------------------------------------

Blackbird started on 02/08/2016 11:02:39

[ Targets ]
   Spread Entry:  0.80%
   Spread Target: 0.30%

[ Current balances ]
0
1
After Balances
   Bitfinex:    0.00 USD        0.000000 BTC
   OKCoin:      0.00 USD        0.000000 BTC

[ Cash exposure ]
   TEST cash used
   Value: $25.00

[ 02/08/2016 11:02:42 ]
   Bitfinex:    374.59 / 374.64
   OKCoin:      375.68 / 375.69
   ----------------------------
   OKCoin/Bitfinex:     -0.29% [target  0.80%, min -0.29%, max -0.29%]

--------------------------------------------
|   Blackbird Bitcoin Arbitrage Log File   |
--------------------------------------------

Blackbird started on 02/08/2016 11:04:28

[ Targets ]
   Spread Entry:  0.80%
   Spread Target: 0.30%

[ Current balances ]
0
1
After Balances
   Bitfinex:    0.00 USD        0.000000 BTC
   OKCoin:      0.00 USD        0.000000 BTC

[ Cash exposure ]
   TEST cash used
   Value: $25.00

[ 02/08/2016 11:04:30 ]
   Bitfinex:    374.50 / 374.58
   OKCoin:      375.70 / 375.71
   ----------------------------
   OKCoin/Bitfinex:     -0.32% [target  0.80%, min -0.32%, max -0.32%]

[ 02/08/2016 11:04:33 ]
   Bitfinex:    374.50 / 374.58
   OKCoin:      375.70 / 375.71
   ----------------------------
   OKCoin/Bitfinex:     -0.32% [target  0.80%, min -0.32%, max -0.32%]

Thanks @jspenc72. The Kraken and 796.com implementations need to be fixed. Both have issues. I'll put a warning in the README file.

I think I have a solution, would you have a few minutes to skype?

Hi @jspenc72,
Can you propose your solution here so it will be shared by others, or if you prefer shoot me a private email at<EMAIL_ADDRESS>Thanks


ASU-515 Add application and applicant models

This PR removes obsolete application related code and replaces them with new ones.

The first commit removes the old code from application_form and contains migrations for removing them.
The second commit adds new application-related models (Application) and (Applicant) based on the new data model. It also contains the migrations for adding them.

Apartments and possible other related models will be added in separate PRs.
The REST API for creating new applications will also be added in a separate PR.

Codecov Report

Merging #51 (ab9a2a9) into develop (46208fd) will decrease coverage by 1.19%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #51      +/-   ##
===========================================
- Coverage    88.56%   87.36%   -1.20%
===========================================
  Files           34       30       -4
  Lines         1067      855     -212
  Branches       100       84      -16
===========================================
- Hits           945      747     -198
+ Misses          99       90       -9
+ Partials        23       18       -5

Impacted Files
Coverage Δ

apartment_application_service/urls.py
100.00% <ø> (ø)

application_form/enums.py
100.00% <100.00%> (ø)

application_form/models.py
100.00% <100.00%> (+10.10%)
:arrow_up:

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 46208fd...ab9a2a9. Read the comment docs.


libfabric: 1.15.1 -> 1.17.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ofiwg/libfabric/releases.
meta.description for libfabric is: "Open Fabric Interfaces"
meta.homepage for libfabric is: "https://ofiwg.github.io/libfabric/"
meta.changelog for libfabric is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.2 with grep in /nix/store/zzdql7cp7xy02jmvabsmglv0m508736p-libfabric-1.15.2
found 1.15.2 in filename of file in /nix/store/zzdql7cp7xy02jmvabsmglv0m508736p-libfabric-1.15.2

Rebuild report (if merged into master) (click to expand)

229 total rebuild path(s)

229 package rebuild(s)

First fifty rebuilds by attrpath
EBTKS
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
bicgl
bicpl
cdo
cloudcompare
cntk
conglomerate
cp2k
dl-poly-classic-mpi
eccodes
elmerfem
elpa
ezminc
febio
freecad
gdal
gdal_2
getdp
globalarrays
gmt
gnudatalanguage
gplates
gpt2tc
grass
gromacsCudaMpi
gromacsDoubleMpi
gromacsMpi
haskellPackages.haskell-mpi
haskellPackages.mpi-hs
haskellPackages.mpi-hs-binary
haskellPackages.mpi-hs-cereal
haskellPackages.mpi-hs-store
hdf5-mpi
highfive-mpi
hp2p
hpcg
hpl
inormalize
ior
lammps-mpi
libLAS
libfabric
libminc
librsb
libtensorflow
mapcache
mapnik
mapproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zzdql7cp7xy02jmvabsmglv0m508736p-libfabric-1.15.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libfabric https://github.com/r-ryantm/nixpkgs/archive/df0474dee5cc530dd538c0c559b591897c1d0b92.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zzdql7cp7xy02jmvabsmglv0m508736p-libfabric-1.15.2
ls -la /nix/store/zzdql7cp7xy02jmvabsmglv0m508736p-libfabric-1.15.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @bzizou for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ofiwg/libfabric/releases.
meta.description for libfabric is: "Open Fabric Interfaces"
meta.homepage for libfabric is: "https://ofiwg.github.io/libfabric/"
meta.changelog for libfabric is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.0 with grep in /nix/store/lqgmh9nrv76ri48vl1h8rwf9142braii-libfabric-1.16.0
found 1.16.0 in filename of file in /nix/store/lqgmh9nrv76ri48vl1h8rwf9142braii-libfabric-1.16.0

Rebuild report (if merged into master) (click to expand)

233 total rebuild path(s)

233 package rebuild(s)

First fifty rebuilds by attrpath
EBTKS
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
bicgl
bicpl
cdo
cloudcompare
cntk
conglomerate
cp2k
dl-poly-classic-mpi
eccodes
elmerfem
elpa
entwine
ezminc
febio
fftwMpi
freecad
gdal
gdal_2
getdp
globalarrays
gmt
gnudatalanguage
gplates
gpt2tc
grass
gromacsCudaMpi
gromacsDoubleMpi
gromacsMpi
haskellPackages.haskell-mpi
haskellPackages.mpi-hs
haskellPackages.mpi-hs-binary
haskellPackages.mpi-hs-cereal
haskellPackages.mpi-hs-store
hdf5-mpi
highfive-mpi
hp2p
hpcg
hpl
inormalize
ior
lammps-mpi
libLAS
libfabric
libminc
librsb
libtensorflow
libvdwxc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lqgmh9nrv76ri48vl1h8rwf9142braii-libfabric-1.16.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libfabric https://github.com/r-ryantm/nixpkgs/archive/087200e40b37bea8b155290c60518494f9d23f91.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lqgmh9nrv76ri48vl1h8rwf9142braii-libfabric-1.16.0
ls -la /nix/store/lqgmh9nrv76ri48vl1h8rwf9142braii-libfabric-1.16.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @bzizou for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ofiwg/libfabric/releases.
meta.description for libfabric is: "Open Fabric Interfaces"
meta.homepage for libfabric is: "https://ofiwg.github.io/libfabric/"
meta.changelog for libfabric is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.16.1 with grep in /nix/store/rix7p514k39pmb768g8bcl63zrqyr7fb-libfabric-1.16.1
found 1.16.1 in filename of file in /nix/store/rix7p514k39pmb768g8bcl63zrqyr7fb-libfabric-1.16.1

Rebuild report (if merged into master) (click to expand)

233 total rebuild path(s)

233 package rebuild(s)

First fifty rebuilds by attrpath
EBTKS
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
bicgl
bicpl
cdo
cloudcompare
cntk
conglomerate
cp2k
dl-poly-classic-mpi
eccodes
elmerfem
elpa
entwine
ezminc
febio
fftwMpi
freecad
gdal
gdal_2
getdp
globalarrays
gmt
gnudatalanguage
gplates
gpt2tc
grass
gromacsCudaMpi
gromacsDoubleMpi
gromacsMpi
haskellPackages.haskell-mpi
haskellPackages.mpi-hs
haskellPackages.mpi-hs-binary
haskellPackages.mpi-hs-cereal
haskellPackages.mpi-hs-store
hdf5-mpi
highfive-mpi
hp2p
hpcg
hpl
inormalize
ior
lammps-mpi
libLAS
libfabric
libminc
librsb
libtensorflow
libvdwxc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rix7p514k39pmb768g8bcl63zrqyr7fb-libfabric-1.16.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libfabric https://github.com/r-ryantm/nixpkgs/archive/b5d771de4f97bd347be93f603ea8154c8230d1bb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rix7p514k39pmb768g8bcl63zrqyr7fb-libfabric-1.16.1
ls -la /nix/store/rix7p514k39pmb768g8bcl63zrqyr7fb-libfabric-1.16.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @bzizou for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ofiwg/libfabric/releases.
meta.description for libfabric is: "Open Fabric Interfaces"
meta.homepage for libfabric is: "https://ofiwg.github.io/libfabric/"
meta.changelog for libfabric is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.17.0 with grep in /nix/store/n0r0whv953kmplhsp1zdgr35dvpb93nc-libfabric-1.17.0
found 1.17.0 in filename of file in /nix/store/n0r0whv953kmplhsp1zdgr35dvpb93nc-libfabric-1.17.0

Rebuild report (if merged into master) (click to expand)

236 total rebuild path(s)

236 package rebuild(s)

First fifty rebuilds by attrpath
EBTKS
apacheHttpdPackages.mod_tile
apacheHttpdPackages_2_4.mod_tile
bicgl
bicpl
cdo
cloudcompare
cntk
conglomerate
cp2k
dl-poly-classic-mpi
eccodes
elmerfem
elpa
entwine
ezminc
febio
fftwMpi
freecad
gdal
getdp
globalarrays
gmt
gnudatalanguage
gplates
gpt2tc
grass
gromacsCudaMpi
gromacsDoubleMpi
gromacsMpi
haskellPackages.haskell-mpi
haskellPackages.mpi-hs
haskellPackages.mpi-hs-binary
haskellPackages.mpi-hs-cereal
haskellPackages.mpi-hs-store
hdf5-mpi
highfive-mpi
hp2p
hpcg
hpl
inormalize
ior
lammps-mpi
libLAS
libfabric
libminc
librsb
libtensorflow
libvdwxc
mapcache

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n0r0whv953kmplhsp1zdgr35dvpb93nc-libfabric-1.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libfabric https://github.com/r-ryantm/nixpkgs/archive/f533ffb02e40cf555b2aab75761f000fa98dede8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n0r0whv953kmplhsp1zdgr35dvpb93nc-libfabric-1.17.0
ls -la /nix/store/n0r0whv953kmplhsp1zdgr35dvpb93nc-libfabric-1.17.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @bzizou for testing.

Closed in favor of https://github.com/NixOS/nixpkgs/pull/202873


Autosize of modal instead of setting explicit height and width

Changed default size of dialog with any effect to match the content size. Can still be overwritten by property.
I have changed the width and height to 'auto' and changed the tranform: translate(0,0,0) to translate(-50%, -50%, 0).

Please check npm test and npm run example.
It seems to not working well.

Of course, the lib folder should not be included. Actually, at the time of doing this pull request, I intended to propose a certain commit and did not know that the pull request follows my branch.
As I did not want to publish my own npm package, but needed the lib folder, I pushed it only for myself.
I'm going to revert the unwanted changes now and then everything should be fine.

Closing pull request.
New PR for current code is coming shortly

Replaced by new pull request: https://github.com/shibe97/react-awesome-modal/pull/19


ValueBox

See proposal #113.
To reduce allocations for boxing on every call this PR introduces a new ValueBox struct which wraps up arguments without requiring any heap allocations. Currently this is only used for function arguments, but in principle it could be used anywhere else plain old object references are passed around (e.g. function returns values).
Drawbacks

ValueBox is mostly invisible to the end user since things convert to it with an implict conversion. However, C# does not support user defined conversions from object so that has to be done with an explicit conversion method - i.e. passing my_ref_object becomes ValueBox.AsBox(my_ref_object). I've added an implict conversion for strings, since that's likely to be a fairly common case. Unfortunately I don't see a better way to handle this situation for any other references types.

I had to remove the old params object[] method, since it confliced with the new params ValueBox[] method, which is a breaking API change. If you'd rather not much such a big change to the external API I can instead remove params ValueBox[] and require that users call it explicitly with a ReadOnlySpan<ValueBox> instead.

params ValueBox[] still incurs a single allocation, which can be worked around by explicitly passing in a ReadOnlySpan<ArgBox>, but that's not very ergonomic.

I haven't done anything with return types at all, they still get boxed. It's not obvious how to fix them, since the caller does not supply the return type.

Potential Improvements
We could potentially workaround a lot of the drawbacks above by introducing a new set of generic GetFunction overloads which return Func<> or Action<> objects. This would have quite a few benefits:

Compatibility of types could be checked when GetFunction is called, instead of when Invoke is called. Potentially reducing per-call overhead.
Fixed number of arguments, so ergonomics issues with params array/span disappear.
Conversion to ValueBox can be done inside the Func/Action which is returned, making it invisible to the end user (ValueBox.AsBox doesn't need to be called externally)
Return type unboxing can be handled easily in the same way.
Fits better into a normal C# workflow - wasm functions can be used just like any other Func/Action object.

If you're interested I can put together another PR which does this (don't merge this PR if so).

@martindevans if you rebase your PR on main, that should resolve the test failures.

We may as well leave this PR for a couple of days, just in case I need to make any major changes to it to support the Func-wrapper approach.

So far I didn't have to make any changes to this for my #116 draft PR, so I think it's probably safe to merge it as is. I don't mind if you'd rather wait and do it all in one go though :)

I've swapped out the representation of v128 from a byte[] (requires an allocation, size must be runtime checked) to Vector128<byte> (no allocations, size is part of type) as proposed in #120. This change is required for #116 to move forward.

I agree, that is much nicer!
Sorry, I've been out sick this week, so I haven't been responding to GitHub notifications.
Please let me know if you want me to review this again and merge it if it's needed for the other PR.

That's no problem, I hope you're feeling better now :)
Please go ahead and review this and merge it if you're happy with it. The other PR builds on top of both changes this introduces.

I've addressed all of that feedback


API for getting the project ID

Hi everyone,
we're trying to provision azkaban jobs using Ansible and it's been great so far thanks to the rest API, one caveat though is that there seems to be no way other than scraping the project page to get the project ID, am I wrong ?
Plus, why does the Schedule Flow API needs to project ID, when all other APIs tolerate using only the project-name ?
Thanks again for the good work.
Olivier.

nevermind, you can get the projectId from curl -k -XGET "http://AZKABAN/manager?ajax=fetchprojectflows&project=MYPROJECT&session.id=SESSIONID" | jq -r '.["projectId"]'
maybe the doc should be updated.


Improvements to chat

:tada: This PR is included in version 1.2.3 :tada:
Your semantic-release bot :package::rocket:


MPI fixes + smoother builtin

This PR:

Includes some bug fixes associated with MPI data slicing along with the relevant tests.
A gaussian smoother builtin for Devito functions that mimics the scipy.ndimage gaussian_filter.

Note: Some changes and tidying are still required.

Codecov Report

Merging #931 into master will increase coverage by <.01%.
The diff coverage is 91.82%.

@@            Coverage Diff            @@
##           master    #931      +/-   ##
=========================================
+ Coverage   90.09%   90.1%   +<.01%
=========================================
  Files         148     149       +1
  Lines       19815   19991     +176
  Branches     3080    3111      +31
=========================================
+ Hits        17852   18012     +160
- Misses       1596    1611      +15
- Partials      367     368       +1

Impacted Files
Coverage Δ

devito/types/dense.py
92.95% <ø> (-0.02%)
:arrow_down:

devito/types/grid.py
93.12% <100%> (-0.04%)
:arrow_down:

devito/data/data.py
96.93% <100%> (+0.01%)
:arrow_up:

tests/test_builtins.py
100% <100%> (ø)

devito/types/dimension.py
93.64% <100%> (+0.01%)
:arrow_up:

devito/data/utils.py
92.57% <100%> (+1.52%)
:arrow_up:

tests/test_data.py
97.5% <100%> (+0.06%)
:arrow_up:

devito/builtins.py
72.18% <80.68%> (+8.77%)
:arrow_up:

devito/mpi/distributed.py
91.37% <0%> (+0.43%)
:arrow_up:

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 3911117...10ff2d6. Read the comment docs.

just noticed that basically this is a single commit with loads of changes in it 😬

just noticed that basically this is a single commit with loads of changes in it
Oh. I've messed up a rebase somewhere. Will take a look.

I've just added some more nitpicking, but I understand this is pretty much ready to go ?

Yes, should be.
Will address the comments above with a new commit shortly.

merged


RigidBody collision bug?

I have two rigid bodies on a scene, a box (dynamic type) and a floor (static type).

When I call physicsWorld->destroyRigidBody(floorRigidBodyPtr)  the box colliding with the floor should fall, but it does not.

If I destroy the floor`s rigid body before the box hit it, the ploblem does not happen.  Is that intended behavior, or it is a bug?

Hello,
It could be a bug yes. It might be because the bodies are sleeping and the box is not awaken when the floor is destroyed. Could you try to wake up the box rigid body after the floor is destroyed using the following code?
boxRigidBodyPtr->setIsSleeping(false);
Does it work now?

Hello,
It could be a bug yes. It might be because the bodies are sleeping and the box is not awaken when the floor is destroyed. Could you try to wake up the box rigid body after the floor is destroyed using the following code?
boxRigidBodyPtr->setIsSleeping(false);
Does it work now?

Hello, boxRigidBodyPtr->setIsSleeping(false); fixed it. Thanks!

Ok perfect but it is still a bug. I will need to fix this.
Thanks for reporting this.

This kind of bug is too hard for me to solve it in my simple arcade physics.
For you don't wast so many time, I solve it like this:
1-add a vector of the position to the body when the world starts the update (preUpdate)
2-with the oldPosition, check after all bodies update (postUpdate) if the oldPosition, is nearly the currentPosition (updated one).
Nearly, I would say, the current position is "almost" the oldPosition, thinking like it is in a threshold.
It's aproximately like sleeping, but, it differs that you must check the threshold for each world update, what can be hard for many updated objects.

This is now fixed in version v0.10.0 of the library.


PrairieView Reader Added

I'm not sure why it's resulting in the error for test-changelog. I'm not very familiar with semantic versioning and maybe I've missed something. I would appreciate any input to address the error

Thanks @kushalbakshi.  Is this formatted with black?

Thanks @kushalbakshi. Is this formatted with black?

It was not. I have updated it in the latest commit. Just need to add the docstring explanation now

I'm not sure why it's resulting in the error for test-changelog.

The reason that this is failing is because of our new GitHub Actions that requires each version to link (with brackets) to the tag (if it will exist after the merge) or a diff between versions.  See this changelog as an example.

I'm not sure why it's resulting in the error for test-changelog.

The reason that this is failing is because of our new GitHub Actions that requires each version to link (with brackets) to the tag (if it will exist after the merge) or a diff between versions. See this changelog as an example. We haven't updated this repo's changelog to reflect the new GitHub Actions. Would you also be able to make this update?

Yes, I'm now seeing that this repo does not have any existing tags. I can make a release for v0.2.1 and another comparing that to v0.3.0?

Hi @kabilar, I tried to update the CHANGELOG entry to reflect that of element-array-ephys but it's still failing. Not sure what I'm missing. This is the error stack I'm seeing:
Run guzman-raphael/changelog-reader-action@v5
Warning: No target version specified. Will try to return the most recent one in the changelog file.
Parse data
Error: No log entry found

Thanks @kushalbakshi! Great work. A couple of questions listed below and then we can merge.
For future reference, we try to employ a line length of 88 for readability and use PEP8 standards for naming variables without using abbreviations. That said there are plenty of locations in our codebase that don't abide by these guidelines, but we have these goals for improving our code readability.

Sounds good. Thank you. I will update the linter and Black formatter settings in VScode to trigger errors when these aren't met

@dimitri-yatsenko @kabilar I've tested a successful ingestion on my local machine. Updates here and at element-calcium-imaging now allow a user to use PrairieView as their acquisition software for populating ScanInfo.


remove _HEADERS variable from Makefile

This commit removes the _HEADERS variable as it is only used when
creating the HEADERS variable.

Landed in https://github.com/cjihrig/uvwasi/commit/4f9dcda2f0283aebfdbec3f6d7063b52ddc8cca7. Thanks!