Divisible assets

resolves #487 #488
Adds support for divisible assets.
The main change is in how we define owners_after since now we need to pass the public keys and amounts.
owners_after is now a list of tuples of ([public_keys], amount)
Example:

# Non-divisible assets
# non-divisible assets will always have one output with amount=1
asset = Asset(divisible=False)

# single owner
Transaction.create([b.me], [([user_vk], 1)], asset=asset)

# multiple owners
Transaction.create([b.me], [([user_vk, user2_vk], 1)], asset=asset)

# Divisible Assets
asset = Asset(divisible=True)

# single output single owner
Transaction.create([b.me], [([user_vk], 100)], asset=asset)

# multiple output single owner per output
Transaction.create([b.me], [([user_vk], 50), ([user_vk), 50])], asset=asset)

# multiple outputs multiple owners per output
Transaction.create([b.me], [([user_vk, user2_vk], 50), ([user_vk, user2_vk], 50)], asset=asset)

# multiple outputs: one output with a single owner, one output with multiple owners
Transaction.create([b.me], [([user_vk], 50), ([user_vk, user2_vk], 50)], asset=asset)

We can perform any combination we want. Each tuple creates a condition.
If there is only on key in the list we create a simple signature condition.
If there are multiple keys in the list we create a threshold signature condition
Most of the changes in the tests is due to the change in the api, except for tests/assets/test_divisible_assets.py which contains the new tests for divisible assets.
TODO:

[ ] Fix failing tests
[ ] Add support for multiple owners_before in CREATE transactions
[ ] Cleanup code

Just a general comment and opinion regarding the names of variables, for fulfilments and conditions. I think using the explicit names fulfilments, and conditions rather than the shorten forms ffils and conds makes the code clearer and easier to understand.
Short forms may perhaps be used in loops, or in list/dict comprehensions where it's obvious what one deals with. But when the variable appears in multiple places and is being passed around, the full name helps making the code clearer, and faster to understand.

from PEP 8:

in many cases, abbreviations and technical terms are used which aren't English

Quite funny how they literally start to import os and sys one paragraph below.

@TimDaub

from PEP 8:
in many cases, abbreviations and technical terms are used which aren't English

Quite funny how they literally start to import os, mypkg and sys one paragraph below.

Well, they do clearly state "For Python 3.0 and beyond, ...".  os and sys pre-date Python 3.

Current coverage is 96.54% (diff: 97.53%)

Merging #794 into master will increase coverage by 0.01%

@@             master       #794   diff @@
==========================================
  Files            26         25     -1
  Lines          1643       1619    -24
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           1586       1563    -23
+ Misses           57         56     -1
  Partials          0          0

Powered by Codecov. Last update 381ffca...e35d289

Is there a size limit on the amount? Should there be?
I don't think integer overflow is a problem if all the arithmetic is done in Python (with no calls to C stuff). Is that right?
The only other problem I can think of is making a transaction so big that it causes problems, but that's possible by stuffing other fields too (e.g. metadata data). Should we create a new issue to put an upper bound on overall transaction size?

I guess at some point that can be a problem but I don't know what the limit should be

I'll make a new issue for that so we don't forget.
:+1:

I guess at some point that can be a problem but I don't know what the limit should be

http://stackoverflow.com/a/3212065/1263876

Thanks @TimDaub
So the answer is that we should limit the number of style sheets to 31 per page


Layout super navigation header initialises gem-track-click inefficiently

The layout header uses the gem-track-click module to track links in the dropdowns. The way this is being done is to apply the data-module="gem-track-click" attribute to each individual link, which is at least a few dozen links.

This is working entirely correctly however gem-track-click doesn't need to be activated like this. In the documentation it shows that the module can be applied to a parent element and tracking attributes added to children (see 'Specific tracking can also be applied to elements within a container'), in order that the module is only instantiated once.
I'm concerned that the way it's being used at the moment in the header means that unnecessary load is being added to browsers to create each instance of the module for every link - it's probably using more memory than is necessary.
(Interestingly it appears to have been configured correctly in the footer, with the data-module applied only to the parent)

I recently refactored the footer gem-track click, can pick this up too to make them in line w/ each other

When you take a look, I'd be interested to know what impact the change has on performance. I was thinking of starting by putting a console log into the gem-track-click init code (to count how many times it gets called before and after the change) but also looking at memory usage in the browser.


[Linux] Error when compiling

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2021.12.01. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
I wanted to test the new function --live-from-start, so i tried to compile from the current master.
Then this error was thrown:
Verbose log
git clone https://github.com/yt-dlp/yt-dlp.git &&\
> cd yt-dlp &&\
> make
Cloning into 'yt-dlp'...
remote: Enumerating objects: 103087, done.
remote: Counting objects: 100% (145/145), done.
remote: Compressing objects: 100% (102/102), done.
remote: Total 103087 (delta 79), reused 78 (delta 43), pack-reused 102942
Receiving objects: 100% (103087/103087), 31.31 MiB | 9.09 MiB/s, done.
Resolving deltas: 100% (79895/79895), done.
/usr/bin/env python3 devscripts/make_lazy_extractors.py yt_dlp/extractor/lazy_extractors.py
mkdir -p zip
for d in yt_dlp yt_dlp/downloader yt_dlp/extractor yt_dlp/postprocessor ; do \
  mkdir -p zip/$d ;\
  cp -pPR $d/*.py zip/$d/ ;\
done
touch -t<PHONE_NUMBER>01 zip/yt_dlp/*.py zip/yt_dlp/*/*.py
mv zip/yt_dlp/__main__.py zip/
cd zip ; zip -q ../yt-dlp yt_dlp/*.py yt_dlp/*/*.py __main__.py
rm -rf zip
echo '#!/usr/bin/env python3' > yt-dlp
cat yt-dlp.zip >> yt-dlp
rm yt-dlp.zip
chmod a+x yt-dlp
COLUMNS=80 /usr/bin/env python3 yt_dlp/__main__.py --help | /usr/bin/env python3 devscripts/make_readme.py
/usr/bin/env python3 devscripts/make_contributing.py README.md CONTRIBUTING.md
/usr/bin/env python3 devscripts/make_issue_template.py .github/ISSUE_TEMPLATE_tmpl/1_broken_site.yml .github/ISSUE_TEMPLATE/1_broken_site.yml
/usr/bin/env python3 devscripts/make_issue_template.py .github/ISSUE_TEMPLATE_tmpl/2_site_support_request.yml .github/ISSUE_TEMPLATE/2_site_support_request.yml
/usr/bin/env python3 devscripts/make_issue_template.py .github/ISSUE_TEMPLATE_tmpl/3_site_feature_request.yml .github/ISSUE_TEMPLATE/3_site_feature_request.yml
/usr/bin/env python3 devscripts/make_issue_template.py .github/ISSUE_TEMPLATE_tmpl/4_bug_report.yml .github/ISSUE_TEMPLATE/4_bug_report.yml
/usr/bin/env python3 devscripts/make_issue_template.py .github/ISSUE_TEMPLATE_tmpl/5_feature_request.yml .github/ISSUE_TEMPLATE/5_feature_request.yml
/usr/bin/env python3 devscripts/make_issue_template.py .github/ISSUE_TEMPLATE_tmpl/6_question.yml .github/ISSUE_TEMPLATE/6_question.yml
/usr/bin/env python3 devscripts/make_supportedsites.py supportedsites.md
git shortlog -s -e -n | awk '!(out[$NF]++) { $1="";sub(/^[ \t]+/,""); print}' > .mailmap
git shortlog -s -n | cut -f2 | sort > AUTHORS
pandoc -f markdown -t plain README.md -o README.txt
mkdir -p completions/bash
/usr/bin/env python3 devscripts/bash-completion.py
mkdir -p completions/fish
/usr/bin/env python3 devscripts/fish-completion.py
mkdir -p completions/zsh
/usr/bin/env python3 devscripts/zsh-completion.py
/usr/bin/env python3 devscripts/prepare_manpage.py yt-dlp.1.temp.md
Traceback (most recent call last):
  File "devscripts/prepare_manpage.py", line 97, in <module>
    main()
  File "devscripts/prepare_manpage.py", line 39, in main
    readme = move_sections(readme)
  File "devscripts/prepare_manpage.py", line 56, in move_sections
    sections = re.findall(rf'(?m)^{re.escape(MOVE_TAG_TEMPLATE) % "(.+)"}$', readme)
  File "/usr/lib/python3.6/re.py", line 222, in findall
    return _compile(pattern, flags).findall(string)
  File "/usr/lib/python3.6/re.py", line 301, in _compile
    p = sre_compile.compile(pattern, flags)
  File "/usr/lib/python3.6/sre_compile.py", line 562, in compile
    p = sre_parse.parse(p, flags)
  File "/usr/lib/python3.6/sre_parse.py", line 869, in parse
    raise source.error("unbalanced parenthesis")
sre_constants.error: unbalanced parenthesis at position 38
Makefile:97: recipe for target 'yt-dlp.1' failed
make: *** [yt-dlp.1] Error 1

Thanks! 👍


Multiple changes

Use container names instead of tags
Support for exposed ports, container private ports and ports exposed on docker swarm cluster
Added default/fallback container
Added target port
Option to connect to docker by TLS
Temporarily disabled tests because of mocking issues

Nice, thanks dude!


fix: destructive badge on hover

When you hover over the destructive badge the background uses the "secondary" color thus making the badge almost invisible.
possible fix for #188

@stormynight9 I merged a fix for this in https://github.com/shadcn/ui/pull/189
Sorry I did not see yours.


Implement Balance mapping

For making it easier to consume, we could create an entity Balance per user-token that keep track of the balance of the users on every deposit/withdraw/trade/submit-solution

Ideally we would have the historic valance. So we could have the balance and the batch range where the user had that balance. That way we can as for the balance for a given batch always (as long as we make the ranges: (1) complete (2) no overlapping of the ranges

Something similar to the MOVEMENTS view in Dune


Revert "Add type hints to functions according to PEP 0484"

Reverts mattlisiv/newsapi-python#34

Why was this reverted?

Yes this was reverted due to Python 2 compatibility.


(docs): fixed small errors

I'm happy to merge these fixes but the commit graph here is a little confused/complicated. With these kinds of changes there are really three ways you can structure them.

A sequence of simple commits rebased against the HEAD of master.
One or more daggy fixes (https://wiki.monotone.ca/DaggyFixes/) hanging from the source of the bug, with one PR each.
A branch from the HEAD of master with one or more daggy fixes merged in to it and then PR'ed as a single unit.

I would suggest that 1 is sufficient in this case unless you want to follow 2 or 3 out of curiosity (they are required for code bug fixes).

I'm not really sure what to do?

No worries. Let assume you want to go with the first approach. Working from your current branch you can see that we have a more complex graph of commits than we need:
ehcache3 % git log --graph master..
*   commit c1d94aa564f5cb8c31921d4367903bca787ca074 (HEAD -> patch-1, origin/patch-1)
|\  Merge: cdd9afe77 b3309185c
| | Author: 0xflotus<EMAIL_ADDRESS>| | Date:   Sun Apr 26 23:53:51 2020 +0200
| |
*   commit c1d94aa564f5cb8c31921d4367903bca787ca074 (HEAD -> patch-1, origin/patch-1)
|\  Merge: cdd9afe77 b3309185c
| | Author: 0xflotus<EMAIL_ADDRESS>| | Date:   Sun Apr 26 23:53:51 2020 +0200
| |
| |     Merge pull request #2 from 0xflotus/patch-2
| |
| |     Update tiering.adoc
| |
| * commit b3309185c4efa830bd5470796fa99027be374266
|   Author: 0xflotus<EMAIL_ADDRESS>|   Date:   Sun Apr 26 23:53:31 2020 +0200
|
|       Update tiering.adoc
|
*   commit cdd9afe773669123c40dd863e70a7619cc051b8f
|\  Merge: fe45c7320 072ec49d0
| | Author: 0xflotus<EMAIL_ADDRESS>| | Date:   Sun Apr 26 23:51:18 2020 +0200
| |
| |     Merge pull request #1 from 0xflotus/patch-2
| |
| |     Update osgi.adoc
| |
| * commit 072ec49d01b931120efa694327cd84ebfa9bc5dd
|   Author: 0xflotus<EMAIL_ADDRESS>|   Date:   Sun Apr 26 23:50:55 2020 +0200
|
|       Update osgi.adoc
|
* commit fe45c7320ae4f958448b967aa6646da10edfcb90
  Author: 0xflotus<EMAIL_ADDRESS>  Date:   Sun Apr 26 23:45:04 2020 +0200

      Update caching-terms.adoc

To get these commits as single sequence running from the HEAD of master we simply have to:
ehcache3 % git rebase master
First, rewinding head to replay your work on top of it...
Applying: Update caching-terms.adoc
Applying: Update osgi.adoc
Applying: Update tiering.adoc

This will replay your commits on top of master, and because rebase will by default drop all merge commits it will flatten everything in to a nice sequence. This leaves us with:
ehcache3 % git log --graph master..
* commit c65f3a7c87e0ac3c2e35a97edfe646b5bd15ac85 (HEAD -> patch-1)
| Author: 0xflotus<EMAIL_ADDRESS>| Date:   Sun Apr 26 23:53:31 2020 +0200
|
|     Update tiering.adoc
|
* commit f618b0702e75a253544fa3ce89251cba6496ec42
| Author: 0xflotus<EMAIL_ADDRESS>| Date:   Sun Apr 26 23:50:55 2020 +0200
|
|     Update osgi.adoc
|
* commit f7308d49d85d62049c67b642902d26f5516181c4
  Author: 0xflotus<EMAIL_ADDRESS>  Date:   Sun Apr 26 23:45:04 2020 +0200

      Update caching-terms.adoc

Assuming everything looks right after this you can then just force push these commits to your remote and the PR will get updated automatically:
ehcache3 % git push -f

Hope this helps!
Chris

@chrisdennis thanks for the hint. Is it ok so?

I took the liberty of rebasing this against current master (it had moved since you last fetched). I will merge once CI has completed.


Update php.sh

Description
Install phpunit according to php version

Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

Hey, @shivammathur
Could you please review the PR?

@Tarasovych
PHPUnit versions do not correspond directly to PHP versions. So this will have to be handled in the script in order to get PHPUnit for each PHP version.
https://phpunit.de/supported-versions.html
Thus, I would recommend using composer to install the required PHPUnit in your CI workflow, or use symfony/phpunit-bridge.
But, if you want to implement this:

Follow the table here for fetching the latest version of PHPUnit for a PHP version.
Use the URL with just the major version of PHPUnit as mentioned by @al-cheb above to get the latest patch version.
Move the curl command to fetch the PHPUnit phar inside the for loop, else it will only fetch the phar for the latest PHP version supported by the Ubuntu version.
Suffix the PHP version to the output filename in the curl command so that it is not overwritten in the next iteration.
Create a copy of phpunit8.0 in the bin directory as phpunit to avoid breaking any existing workflows.

Hi @Tarasovych, this is not something we'd like to change in our installation scripts due to possible unpredictable impact, please use symfony/phpunit-bridge as suggested above.
I am closing this PR and related issue. Please, let me know if you have any concerns.
Thanks.


Is there an option to provide system message if chat deployment type is used?

Hello, did you find an answer to this question?

Hello, I am also looking for an answer to this. Has anyone managed to include a system message with the chain?


project:xxx is not a rake task -> is filtered from the ARGV array to …

…prevent unknown task calls

Can you provide an example of a failure that you've run into regarding this? I've not seen the problem you are citing.

Use case as followed: A project with multiple project-YAML files (e.g. project.yml -> for testing; xxx.yml -> for release configuration 1; yyy.yml -> for release configuration 2.
As you mentioned in this post (http://www.throwtheswitch.org/forums?place=msg%2Fthrowtheswitch%2FYDYiaH6yCb0%2FAH2d0VFwAwAJ) , I use ‘ceedling project:yyy release’ to build the release configuration 2. With version 0.27.0 this works as expected. With version 0.28.1 however, ceedling returns an error (‘Don’t know how to build task ‘project:yyy’’).

When you upgraded to 0.28.1, did you just upgrade your gem or did you actually run "ceedling upgrade" on your project? Does it behave the same if you remove (or rename) your rakefile to something else?
Our online tests for this feature are passing and I just created a few modules with 0.28.1 myself and it went fine. I'm just trying to hunt down what might be different with your setup so I know where the bug is. :)

I did upgrade my gem and reinit the project with "ceedling new PROJECT_NAME". With version 0.28.1, I removed the rakefile (seems to be obsolet?).
Today I tested it again. First with version 0.27.0 -> project:yyy works, but the error "NameError: uninitialized constant ReleaseInvoker:: EXTENSION_SUBPROJECT" appears.
With version 0.28.1 I get the same as I mentioned in post #199 . Before I tested each version, I removed the old one (gem uninstall ceedling --version xx.xx.xx)
Or maybe I miss a project option? Currently my project.yml file looks like follow:
:project:
  :build_root: build
  :graceful_fail: true
  :test_file_prefix: test_
  :use_deep_dependencies: true
  :use_exceptions: false
  :use_test_preprocessor: true
  :default_tasks: test:all

:environment:
- :path:
  - '#{ENV[''ATOLLIC_PC_HOME'']}'
  - '#{ENV[''ATOLLIC_ARM_HOME'']}'

:defines:
  :common: &id001
  - STM32L486xx

  :test:
  - *id001
  - TEST

  :test_preprocess:
  - *id001
  - TEST

:paths:
  :source:
  - src/**
  :support:
  - test/support/**
  :test:
  - +:test/**
  - -:test/support/**
  :test_toolchain_include:
  - '#{ENV[''ATOLLIC_PC_INCLUDE'']}'
  - '#{ENV[''ATOLLIC_PC_LIB_INCLUDE'']}'
  - '#{ENV[''ATOLLIC_PC_LIB_INCLUDE_FIXED'']}'
  - '#{ENV[''ATOLLIC_PC_MINGW_INCLUDE'']}'

:extension:
  :assembly: .s
  :executable: .out
  :header: .h
  :object: .o
  :source: .c

:tools:
  :test_compiler:
    :executable: gcc
    :arguments:
    - -D$: COLLECTION_DEFINES_TEST_AND_VENDOR
    - -I"$": COLLECTION_PATHS_TEST_SUPPORT_SOURCE_INCLUDE_VENDOR
    - -std=gnu11
    - -c
    - -fmessage-length=0
    - -g
    - -O2
    - ${1}
    - -o "${2}"

  :test_linker:
    :executable: gcc
    :arguments:
    - ${1}
    - -o ${2}

  :test_assembler:
    :executable: ar

:cmock:
  :enforce_strict_ordering: true
  :mock_prefix: mock_
  :plugins:
  - :ignore
  - :ignore_arg
  - :callback
  :treat_as:
    bool: UINT8
    int8: INT8
    uint16: HEX16
    uint32: UINT32
    uint8: HEX8
  :treat_externs: :include
  :when_no_prototypes: :warn
  :when_ptr: :smart

:plugins:
  :enabled:
  - stdout_pretty_tests_report
  - module_generator
  - warnings_report
  - xml_tests_report
  :load_paths:
  - vendor/ceedling/plugins

My apologies, @grosi . It was I who wasn't refreshing my local changes well enough. The bug you found is much more consistent than I was seeing. Thanks for sticking with it and thanks for the help!

No problem! Thank you for developing and sharing Ceedling! It makes my life much easier :-)


Switch to using event-impl-gen in its AP form

See https://github.com/SpongePowered/event-impl-gen/pull/12
This is the changes necessary to update for that PR, tracking in a PR until I've had a chance to test these changes more thoroughly.

This will be ready to merge once Gradle 7.2 is released, fixing issues with incremental compilation.

@zml2008
ETA on 7.2?

7.2's RC1 is scheduled for Monday (via https://github.com/gradle/gradle/milestone/174) -- I expect the final release will be a few weeks after that. This PR should maintain an identical API for users -- there was one generics change necessary, but that has been applied to the api-8 branch separately.

What's our thinking on this - merge conflicts aside are we ready to go with this?

there are still some issues with incremental builds in intellij that I haven't had a chance to resolve yet - I think that's the only blocker though

I think the blocker here is still incremental processing unfortunately


Move the opening checkbox higher in the menu

Look at what killproof.me did to move it up, not sure if it's just about using a different callback.

Implemented in a50feeb7547177cf8d23433acb7f04e8237991af.


Don't build unnecessary ICU4X components

Display names is experimental

Display names is experimental

Then I am fine with leaving it out, or taking it in. We are pinned to an ICU4X version anyhow.

It's in, it's enabled by the experimental_components feature


Clean up warning text component styles

remove negative margin left and reduce padding left to match

Fixes https://github.com/alphagov/govuk-frontend/issues/1083

Thanks very much for picking this up, Andy – the change looks good 👍
Would you mind adding an entry to the CHANGELOG under 'Unreleased'? I think this would count as a fix.


Draft

Reopen this draft PR, as certain things changed according to tracing in .NET Core 3.0 and because this contribution is part of work for a Swiss Post project, hence the work will be done under swisspush.

Move to own class but don't use behavior as this gets called to late
Extend examples
Write Unit Tests

As we are unsure how to continue with the DiagnosticsConsumer & DiagnosticsProducer, I moved all logic out of them. Then, I added unit tests for the new functionality.
The following classes aren't yet covered, as they might get deleted.

DiagnosticsConsumer
DiagnosticsProducer
ActivityScope

Furthermore, there is still the visibility of "OutboundMessage" which will also change as part of the refactoring.
As discussed, there is a problem with the dependency to system.memory.
In addition, I didn't wrote any integration tests, as I didn't want to include the classes to be refactored (DiagnosticsConsumer & DiagnosticsProducer)


updating dependencies

Updating dependencies.

Replaced by PR #112. Whatever had been pulling in 2.0.0rc1 of werkzeug lib was updated to pull in version 1.0.1, so PR #112 only had a different pipfile.lock with the correct version of werkzeug, it didn't need to pin werkzeug to v 1.0.1.


"HTMLElement is not defined" on start of a new project (fresh install)

Version
2.7.1
Reproduction link
http://localhost:3000/
Steps to reproduce
Current version of Nuxt (2.7.1) on Windows 10.
npx create-nuxt-app test1
cd test1
npm run dev

The application is built (with one error:  ERROR  (node:22396) DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead but I do not think it is relevant)
Opening a browser on http://localhost:3000
What is expected ?
A demo page
What is actually happening?
An error page with ReferenceError: HTMLElement is not defined.
Error is apparently in node_modules/element-ui/lib/element-ui.common.jsopen on line 36822 (the one defining scrollContainer:
props: {
    src: String,
    fit: String,
    lazy: Boolean,
    scrollContainer: [String, HTMLElement],
    alt: String
  },

  data: function data() {
    return {

This bug report is available on Nuxt community (#c9241)

Duplicate of #5622
https://github.com/nuxt/nuxt.js/issues/5622#issuecomment-492213789


Fix Arm relocs

This change makes it possible to fully compile and link (and even run till the first NYI assertion) a tiny executable built against Test.CoreLib on Linux/armel.

@mskvortsov,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

The changes needed on the ObjWriter's side are in the gist here.

@sandreenko Could you please take a look (and the related ObjWriter change)?

I do not see llilc PR with this change, and the llilc change looks like a copy-paste.
So usually the algorithm to such changes is:

merge LLVM PR;
create LLILC PR with new ObjectWriter version, then publish new ObjectWriter;
3, create CoreRT PR that uses the newest ObjectWriter version.

cc @Dmitri-Botcharnikov @sergign60 @BredPet

@mskvortsov Could you please submit PR with the ObjectWriter delta against https://github.com/dotnet/llilc/ ObjectWriter branch?

@jkotas ObjWriter change is not ready to be submitted, unfortunately. It needs more testing for at least HIGHLOW and REL32 reloc types, and this will be possible only when we are able to run substantial portion of the executable - currently it asserts on NYI almost immediately and does not make any accesses to the data section where those types of relocs reside.
Could this CoreRT change be merged without submitting ObjWriter change before? It will help a lot our Linux/ARM bring up process (less patches to carry around).

I've updated the LLILC/LLVM patch, it is in the same gist as before (see revision 2). I've verified it by compiling and executing a tiny .NET executable as described in CoreCLR issue #13400.
 I've checked it on my tizen device with the simplest test. It's working.


Javadoc accessMode READ_ONLY not correct

https://javadoc.io/doc/io.swagger.core.v3/swagger-annotations/latest/io/swagger/v3/oas/annotations/media/Schema.html#accessMode--
Allows to specify the access mode (AccessMode.READ_ONLY, READ_WRITE)
AccessMode.READ_ONLY: value will only be written to during a request but not returned during a response.
AccessMode.WRITE_ONLY: value will only be written to during a request but not returned during a response.
AccessMode.READ_WRITE: value will be written to during a request and returned during a response.
READ_ONLY description is wrong, its not the same as WRITE_ONLY.
Should be something like:
"value will not be written to during a request but only returned during a response. "

this is implemented in #3537


Undefined StorageClass

Hi,
I have followed the installation instructions, but, I had an "Undefined StorageClass" error on the ServiceProvider.php file at line 91.
I think it is because the condition is
!is_null($app['config']['mangopay']['StorageClass'])

instead of
isset($app['config']['mangopay']['StorageClass']) && !is_null($app['config']['mangopay']['StorageClass'])

Now it is working in my app.
What do you think about it ?

I agree. This would be as a result of PR #1 from @brayniverse.
Can you make a PR to fix this? And I'd use array_get(), rather than the isset && ... construct.
Thanks!

Hey, sorry about that. I'll submit a PR as soon as I can.

@DzKerr Let me know if this change fixes things for you (0.9.4 release)


Update syslog documentation for typo

There is a typo of UDP which is spelled as UP.
Corrected it.
Signed-off-by: Swapnil Kulkarni<EMAIL_ADDRESS>Fixes #3501

Thanks, @coolsvap :)


[minor] update: invalid client name warning handling

[x] This contribution adheres to CONTRIBUTING.md. (Required)
[ ]  Automatically post PR comments with images for G code changes? (Recommended for small changes)

What does this Pull Request accomplish?

Updated the workflow of handling the warning for invalid client names.

Currently, we highlight all the invalid client names among the populated list of available measurements when the user edits or selects a measurement service.
In this PR, the workflow is updated to highlight the invalid client names of the measurement services that are selected for client creation.

Removed the Validate Client Names.vi, due to change in workflow and also updated the automated test case to use the Validate Selected Client Names.vi instead of the Validate Client Names.vi.

Updated the scope of Validate Selected Client Names.vi to 'community' scope, to use the VI in the automated test case.

Why should this Pull Request be merged?

To update the workflow of handling the warning for invalid client names.
To update the automated test case, which checks for duplicate client names in the multicolumn listbox.

What testing has been done?

Manually tested the highlighting of invalid client names and visibility of warning for various test cases.

Update Measurement Selection.vi

Remove the highlight of the invalid client's name, if the measurement is unchecked (not selected).

Diff image
Before:

After:

Create Measurement Client.vi
Diff image
Mouse down case
Before:

After:

Create Measurement Client.vi
Diff image
Edit cell case
Before:

After:

test_DuplicateClientNames_CheckClientNameIsNotRepeated_NameInvalid.vi

Updated the automated test case to check for invalid client names only for the selected measurements in the multicolumn listbox.

Diff image
Before:

After:


File upload renders json response in browser

I'm adding a file upload form with cocoon. I've removed some things for clarity and privacy, but this is hopefully enough. Here is the diff and the new attached_file_fields partial
diff --git a/app/controllers/work_groups_controller.rb b/app/controllers/work_groups_controller.rb
index 26bb1f4..e691740 100644
--- a/app/controllers/work_groups_controller.rb
+++ b/app/controllers/work_groups_controller.rb
@@ -271,6 +271,10 @@ class WorkGroupsController < ApplicationController
                                          :experience, :notes
+                                         attached_files_attributes: [:id, :attachable_id,
+                                           :attachable_type, :name, :type,
+                                           :file, :work_group_id,
+                                           :size, :url, :_destroy],
                                          redacted_things_attributes: [:id],

diff --git a/app/models/attachment.rb b/app/models/attachment.rb
index 3961a01..ebb236b 100644
--- a/app/models/attachment.rb
+++ b/app/models/attachment.rb
@@ -1,4 +1,5 @@
 class Attachment < ActiveRecord::Base
+  belongs_to :work_group
   belongs_to :attachable, polymorphic: true
   belongs_to :user
   mount_uploader :file, AttachmentUploader

diff --git a/app/models/work_group.rb b/app/models/work_group.rb
index cc1942d..d7eb409 100644
--- a/app/models/work_group.rb
+++ b/app/models/work_group.rb
@@ -8,6 +8,7 @@ class WorkGroup < ActiveRecord::Base
   has_many :attached_files, -> { order('created_at DESC') }, class_name: 'Attachment'
+  accepts_nested_attributes_for :attached_files, allow_destroy: true, reject_if: lambda {|a| a[:file].blank?}

diff --git a/app/views/work_groups/new.html.erb b/app/views/work_groups/new.html.erb
index cb34e42..c4c942c 100644
--- a/app/views/work_groups/new.html.erb
+++ b/app/views/work_groups/new.html.erb
@@ -26,7 +26,8 @@
       Success! Your progress has been saved.

-<%= simple_form_for @work_group, html: {id: :new_work_group}, remote: true, format: :json do |f| %>
+<%= simple_form_for @work_group, html: {id: :new_work_group, multipart: true}, remote: true, format: :json do |f| %>
+  <%= token_tag %>

diff --git a/app/views/work_groups/steps/_step3.html.erb b/app/views/work_groups/steps/_step3.html.erb
index 4be9b01..588aa5a 100644
--- a/app/views/work_groups/steps/_step3.html.erb
+++ b/app/views/work_groups/steps/_step3.html.erb
@@ -103,8 +103,20 @@

+

+              <%= f.simple_fields_for :attached_files, f.object.attached_files.build do |attached_file| %>
+                <%= render 'attached_file_fields', f: attached_file %>
+              <% end %>
+

+

-          + Add a Report
+              <%= link_to_add_association '+ Add a Report', f, :attached_files, {:"data-association-insertion-node" => "tbody#work-group-files-3", :"data-association-insertion-method" => "append"} %>

Partial

    <%= f.input :id, as: :hidden %>
    <%= f.association :work_group, as: :hidden, input_html: {class: :work_group_association} %>
    <%= f.file_field :file %>

    <%= link_to_remove_association image_tag('remove-member.png'), f %>

When I submit the form, instead of handling the response with the javascript (as it did before), it is rendering the json response in the browser. Not sure what is going on here.

One thing that I'm working toward fixing is the association in the nested-fields should be to the polymorphic Attachable, but that's another issue. Just might see some relics of that in here.

Hmmmm confused. I seem to be missing some context. Showing diffs of code I have never seen before? Wrong repository?

I just thought a diff was a straightforward way to show the changes i've made to an existing form to try to add file uploads using cocoon. For some reason, it is changing how the form acts when it is submitted.
You can see that I've only added multipart true and now it causes a form that used to submit remotely to render a response in the browser. simple_form_for @work_group, html: {id: :new_work_group, multipart: true}, remote: true, format: :json do |f| %>

Mmmmm using cocoon does not change how a form is posted, it only allows to dynamically add extra fields inside the form (form-content).
So imho this problem is not cocoon related at all.
You did add some code to your controller as well, right? Why do specify format json? How do you handle the returned json? I generally do not specify a format (default is just js) and add js views that will do the updating.

So the controller just returns a formatted response with the created/updated entity
class WorkGroupsController < ApplicationController
  def update
    respond_to do |format|
      if @work_group.update(work_group_params)
        format.json { render json: {work_group: @work_group, members: @work_group.work_group_memberships}, status: :ok, location: @work_group }
      else
        format.json { render json: @work_group.errors, status: :unprocessable_entity }
      end
    end
  end
end

I then listen on ajax events to do things with the formatted json
  $('#new_work_group').on('ajax:error', (xhr, status, error) ->
    enable_form()
    clear_errors()
  ).on('ajax:success', (xhr, status, error) ->
    enable_form()
    clear_errors()
    do_some_stuff_with_the_json(status)
  ).on 'ajax:send', (xhr, status, error) ->
    disable_form()

So it looks like your javascript/handlers is not triggered?

Even more so, the form isn't submitting remotely anymore.

Things I can think of to verify:

check the <form> line in the html, if it still contains the data-remote option?
check/log in the controller if it is a xhr request? (request.xhr?)
maybe you have a javascript error somewhere, which causes the data-remote to be skipped/the handlers to be skipped

Still not a cocoon problem though, so maybe best ok this question on stackoverflow?

Sure thing. I'll check those things and move it over there. Unless the javascript error is somewhere in cocoon, you're probably right. But I don't see any anyways.

Solved?

Not really. I was able to solve the problem with remotipart that was pushing me down the road of doing it this way

Ok. I generally use something like jqeury file upload or dropzone, and let my serverside handle the nested stuff. Easier for the user: just drop a bunch a files :smile: But good you got it solved.

I'll have to look at those. I'm guessing they play well with cocoon if you use them! Really appreciate cocoon

Cocoon works fine for doing file-uploads, it is just not as user-friendly as using dropzone or jquery file upload. So I generally do not use cocoon for doing multiple file upload. It is way easier to just drop a bunch of files, and let the server side handle an array of files instead of a single one.


Simplify the construction of qualified name context in marked source. [phab:D2085]

Created by fromberger at 2017-12-07 20:46:53:
Add additional parent relationships for name resolution.
By default, concrete methods were not being parented to their types, and
parameters were not being parented to their functions, for the purposes of
qualified name assignment.  (This was not for any good reason, we just did not
need this information before).
Ensure that these types get mapped, which allows the subsequent improvements to
the way qualified names are assigned to parameters, and simplification of the
marked source context code.
Now that the parent tree has all the relationships we need, it is no longer
necessary to have so many special cases; we can just walk up the parent chain
directly toward the package. Pull that out into a function.
Add a method parameter name test that was missing.
No functional change.

fromberger wrote at 2017-12-07 22:43:16:

Add a doc comment to typeContext.

zarko accepted this revision at 2017-12-07 22:47:02

fromberger closed via commit a3955c10c7cb3d32c7aacfc04b7f215af41db081 at 2017-12-07 22:51:42


Validate sparse bindings at submit time

Sparse binding is a queue-based operation and therefore proper sparse memory bindings should not be validated until their related resources are used at submit time. Currently validation for sparse bindings is limited so opening this up as a tracking issue.
As a short-term mitigation technique it may be useful to track on a global scale if any spare bindings are ever made and, if so, warn the user that spare validation is currently incomplete.

@tobine @chrisforbes I'm doing a bit of an overhaul/leak pulling for Pipeline Layout Compatibility that could go out a couple weeks, but possibly could be available after that to take look (modulo higher priorities).


Simplify mul-up and mul-down function

This PR simplify mul-up and mul-down function by forcing them to return uint value instead of (response uint uint)
Main benefit of this change is more readable and cheaper in execution code because there is no need to unwrap results of these functions.

I agree to this approach. In this case, do we want to do the same to div-up, div-down, pow-up and pow-down (and any other fixed point functions I missed)?


dicrease the complexity of  CalcDep from exponential to linear

The DCE pass bug is not caused by infinite loop, it is just time consuming.
@MarisaKirisame  please review, thanks!

LGTM.
note that you should not pass in a graph to DCE. We only intend for it to support tree form. In general, all the high level analysis/pass (pointer analysis, partial eval, dead code elimination, ad) all assume the input is in tree form.

Why is it assumed a tree form? I can see that the base class ExprVisitor also use the visit_counter_ to make sure all the expr are visited once.

@yaochengji because what does it mean for a graph form program to have scope and effect?

@MarisaKirisame but I think since using a visit_counter is a default behavior in ExprVisitor, it should not be dropped in CalcDep .
cc @icemelon9

you can still has it. I just mean you should not pass graph in.

@MarisaKirisame  do you think this commit should be merged?

sure. It will increase the robustness of the DCE.

Please add a test case

@vinx13 Done.

Thanks @yaochengji  @MarisaKirisame this is merged


Remove support to specify cluster settings in the track

So far we allow to specify a cluster-settings element in the track. This is trappy because it only works in certain circumstances, namely when Rally sets up the benchmark candidate itself.
However, as we split Rally's functionality into individual subcommands, this should be done differently:

static cluster settings should be defined via rally-teams and the additional_cluster_settings
dynamic cluster settings should be defined via the put-settings operation in Rally

Note that the geonames track for 2.x and 5.x requires the setting indices.query.bool.max_clause_count to be set when starting the node. We need to change our integration tests accordingly before we can do the actual change in rally-tracks.

We should work on this in the context of https://github.com/elastic/rally/issues/1107 when we'll remove support for 5.x


Allow to change authentication configurations within the sample app

Description
The sample app should provide the capability to change the authentication configuration within the sample app without having to rely on an external file.

@gayashanbc any update on this feature?

Closing the issue as this repo is no longer maintained.


Permissions per level not working

Using the format: https://dev.bukkit.org/projects/jobs/pages/permissions
And the format in the Config, I've tried almost about everything, and nothing has worked.
It's not executing any commands, nor giving me any permissions.
I'm using: LuckPerms + Vault on the latest version of spigot 1.12.2 and the latest version of Jobs Reborn
My buddy told me it could be because LuckPerms isn't officially supported, so I came here.

Just gonna state this in case you need it, “my buddy” refers to me.

The official permissions are here: https://github.com/Zrips/Jobs/wiki/Permissions
Please send the permission you are having a problem with. (in jobConfig.yml)

That's literally quite like the one above, and I told you, I've done it the same way the config gives me for formatting, and I've made sure it's the correct permission.
Permissions per level isn't working, not the Jobs Reborn permissions. Say like I reach level 2, and I get this permission, I don't get it. Thank you, help is highly appreciated!

Did you try to use another permission system or just use the LuckPerms plugin? E.g PermissionEx or GroupManager?

@ShadowPauler - the Jobs plugin you provided on bukkit is NOT the same resource as Jobs on Spigot.  That's the old 2014 files.  Are you sure you are using Jobs Reborn (v4.5.4 - this resource) or Jobs v2.x.
Providing what you have in LuckPerms for how it is configured will help determine if it is a permissions issue or a configuration issue.
Note that Group Manager and PermissionsEx are no longer supported.  I'm using LP v4.5.4, with the latest Jobs Reborn version and perms are working fine on Spigot 1.12.2 and 1.13 servers I host.

The issue is persisting.

Well, any way to fix it, or any recommendation of what permissions plugin to use with jobsreborn? Please, I'll use anything! 😞

Sorry, but you quoted a resource from Bukkit for "Jobs" by another developer and assumed "Jobs Reborn" is this one and are one and the same - which they are not!
I quote from you:
"I'm using: LuckPerms + Vault on the latest version of spigot 1.12.2 and the latest version of Jobs Reborn"  But you did not list the version of LuckPerms, Vault or Jobs Reborn and as we have no visibility into what your server configuration/setup looks like, we can't assume anything when trying to find a root cause of a behavior issue being reported.
It could be one or all three plugins mentioned or another plugin causing a conflict.  Paint the bigger picture, so that we can help.

https://timings.aikar.co/?id=364b842532e749518d28a2d1eeb54126
That's all of my plugins.
I forgot to mention, JobsReborn commands per levels also doesn't work.

now that's great picture painting @ShadowPauler  and very helpful.  Thank you.  So you are only a few builds behind and nothing fixed afterwards would account for the behavior with permissions for leveling up or commands for leveling up to not work.
From the list of plugins I recognized, some are a bit outdated but nothing stood out (to me anyways) that would cause either issue.  So I've got a few questions if you can bear with me.
When the server starts up, are you seeing "any" errors, warnings or plugins not loading of any type? In other words, do you have a clean startup with no issues?
You mentioned using LuckPerms (as I am also), can you share what your permission structure looks like?  I ask because I ran into a scenario where most of the jobs permission nodes had to be at the user level and not at the group level.  I had issues with my complex 7-12 Titles per Job each granted at different levels achieved for 18 Job types I have. This only became apparent when testing I was doing for Jobs Reborn and using PermissionsEx, then GroupManager and finally LuckPerms where I found the issue.  Long winded scenario and it may not be what you have, but seeing how you setup the permissions to match your configuration would help.  Also, if you can provide steps on how to duplicate it, that goes a long way to solving it for Zrips and getting it fixed.

Great. Alright, well my structure is...
The player must join 2 out of 12 - 18 jobs (specifically the 3 harvester jobs in this case), once they join, there's 100 levels, which has 12 nodes, of unlocking new permissions for each one (ranging from 1 - 30 permissions each) but I have only just tested 1 permission node.
For testing, I'm joining a job, which in the configuration shows at X level, I should get this permission, which will allow me to mine a new type of ore. Well, I reach that level in the job, and I mine the new ore, but I don't get the drop that the permission is supposed to give me. So, to make sure it wasn't the custom drops plugin, I added it manually, and it worked. I remove my permissions again, and OP, and I reset my job level and went to the JobsReborn configuration to alter and change it to see if I can get it to work several times. All of the times, I've failed.
Now, I have a major question. For permissions based per levels, does it have to be underneath the job it's created for in the config? Because it would be rediclious if that was so, and I've been wasting my entire time. I also didn't think it would make sense because your able to allow multiple jobs acquire the same permissions based on different levels.

So does that help at all?

Unfortunately, this permission condition has never been tested for how it works, but I will soon test it whether it works or not.
Adding permission without a separate plugin works with us to use the pluginManager that adds the specified permission to the plugin that has registered for the server's permission system. I do not know if it works for LuckPerms, but I still have a lot of practice on it.
Perhaps, you may need to reload LuckPerms with the /lp reload command. But I also know that LuckPerms automatically updates itself.
When you checked the permission with you, group.owneradmin, did you consider that the server gave the 3 permission to the owneradmin group?

Okay, now I've tested and permission per-level worked for me.
I have given you this to work properly:
    conditions:
      first:
        requires:
        - j:Woodcutter-2
        - p:jobs.join.Woodcutter
        perform:
        - p:essentials.fly-true

I began to do this and add LuckPerms to the jobs.join.Woodcutter permission. Then I joined the server and raised the job to level 2 (no command) and if level 2 reached (which was set), it did not immediately add permission but when I reached level 3 it added.
I also experienced that, not to add permission to LuckPerms.

hey, thanks for the quick reply.  I think there would need to be explicit support built into Jobs for this to work with different permission systems as the commands to enable/disable the permission nodes vary.
There isn't a need to do an /lp reload since the permissions I added are available immediately upon joining the game.  I do not have luckperms auto-updating the version since I test each release first.
I setup the "default" group which is the parent for "owneradmin" with these three permissions set to false.  The "true" nodes do not exist in the owneradmin, default or smmmadden (my user). So they were not added.  I would only expect that Jobs be adding the permission nodes to the user, not the group since that would enable something for all users.
The equivalent command if I did this in LuckPerms would be:
/lp user smmmadden permission set ridables.allow.ride.chicken true server=world world=world
/lp user smmmadden permission set ridables.allow.ride.cows true server=world world=world
/lp user smmmadden permission set ridables.allow.ride.pig true server=world world=world
The config I have is identical to what you provided.  You are saying that your user has the permission of essentials.fly true and your default group still has essentials.fly false?  That's the test I'm working on which does not work.

Unfortunately, I do not know why not adding Jobs to LuckPerms permissions because it does not add to the LP for me. This could be improved by hooking LP to Jobs and retrieving the LP database to include permissions. But since there are plenty of permissions schemes, it will not be added.
No. If the configuration is set to true for permission, then the player gets it, but if false it is not.

I'm confused - are you saying it worked or did not work?
Also - I'm reading that Jobs does NOT support LuckPerms.  Is this correct?

Sorry. I said it worked.
No. The plugin support for all permission system plugin because we not added to hook into a plugin.

sorry, must be a language barrier here.  I know Jobs supports multiple permission systems, that's not the question here.  It's specifically for jobConfig.yml where one can add a condition and based on it "perform" the permission (set) whether it be granting or denying that permission.
When I tested this, it is not working for the permissions setup the same as you but with different plugin (Ridables). None of the permissions that were added in the conditions section were performed including adding - p: essentials.fly-true so I have no idea how it worked for you.  Are you using PaperSpigot 1.13.2 Build 481+ with Jobs 4.9.3+ of 11/18 and LuckPerms 4.3.49?  If you are can you provide a screen shot of your LuckPerms editor showing that the permission was added?

I'll tell you more clearly.
Adding permission did not work for me, just like you did, and Jobs did not give permission to LP.
I using PaperSpigot 1.13.2 Build 483 with Jobs 4.9.3 (dev version) and LuckPerms dev version. The image would be the same as yours.

okay - got it now :-)  At least you were able to confirm what I did and what @ShadowPauler was trying to do and that it is not working.
Can you check with @Zrips to see what/how he expected this to work or whether or not it can be fixed to work? It is documented that it should work.  Question is, how and for what?  Thanks! :-)

Hi, sorry tout dig it up, but is there any updates on this issue ?
I'm trying to work around it with SQL and triggers but this would make everything way more easy !

After a good while ... We realized (finally) that when Jobs registers new permission names, they can't be added by Bukkit, that is, they can't be integrated into the permission systems database, or the plugin can't accept them. This is not a fix, as a lot of data is still saved in Jobs causing server delays and will not be fixed. Otherwise, this Jobs plugin is not a permission handler, but a job handler.


Need reporters and position updates during energy minimization

During the energy minimization, it will be nice to look at the free energy (bond, angles) at every step and also the position update of the PDB at sampling step.

duplicate of issue #87


feat: adding try_valid macro

Summary:
Adding a macro try_valid which works similar to how ? operator works for Result and Option types.
Example usage
fn square_if_valid(x: Valid<i32, String>) -> Valid<i32, String> {
  let x = try_valid!(x); // returns early if the value is an Errror
  Valid::succeed(x*x)
}

Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[x] I have performed a self-review of my code.
[x] PR follows the naming convention of <type>(<optional scope>): <title>

Closing this PR because I am not sure this is adding much value over what we already have.


Version 0.44.0 应用一启动闪退 Open the application crash

react-native run-android
installDebug is SUCCESSFUL
但是应用打开（Open the application），就闪退（crash）

React Native version: 0.44.0
Platform: Android
Development Operating System: Windows
Dev tools:  Android Studio

05-09 16:38:13.982 15873-15914/cn.miguche.shcs.internal E/AndroidRuntime: FATAL EXCEPTION: mqt_js
Process: cn.miguche.shcs.internal, PID: 15873
java.lang.RuntimeException: Error calling AppRegistry.runApplication
at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
at android.os.Looper.loop(Looper.java:148)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:208)
at java.lang.Thread.run(Thread.java:818)
Caused by: com.facebook.jni.CppException: Could not get BatchedBridge, make sure your bundle is packaged correctly
at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
at android.os.Looper.loop(Looper.java:148)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:208)
at java.lang.Thread.run(Thread.java:818)
05-09 16:38:19.424 7116-7116/? E/DEVICE_SDKTAG: Error reading from /proc/1.
05-09 16:38:19.426 7116-7116/? E/DEVICE_SDKTAG: Error reading from /proc/2.
05-09 16:38:19.428 7116-7116/? E/DEVICE_SDKTAG: Error reading from /proc/3.
05-09 16:38:19.429 7116-7116/? E/DEVICE_SDKTAG: Error reading from /proc/6.

Look inside package.json for versions of react and react-native.
For example in mine this is what I see:
"react": "^16.0.0-alpha.6",
"react-native": "^0.43.4",
most people believe that when you do:
npm install
You are guaranteed that these versions are the ones installed.  But that is not always the case. Sometimes npm just grabs whatever it can find from internet.
You may need to do:
npm install --save<EMAIL_ADDRESS>npm install --save<EMAIL_ADDRESS>Dont assume that 'npm install' puts exactly what you need into node_modules.  You might have to occasionally clean out node_modules
rm -rf node_modules
npm install --save<EMAIL_ADDRESS>npm install --save<EMAIL_ADDRESS>// in your case 0.44.0  but check what's in package.json
npm install
Let us know if that fixes it.  (Also note in SOME cases you need to do 'react-native link' after the installs but you should see some messages about this after npm install if that's the case.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/version-0440--open-the-application-crash


Add a test case to check whether the ballerina ErrorValues that are thrown from java side works properly

$subject

implementation - https://github.com/ballerina-platform/ballerina-lang/pull/20078


Fix path issue

fix path issue for the relationship sample

Thank you so much for spotting the error and taking the time to fix it, @snowmanmsft !


Inconsistencies between find widget and find viewlet

If you have no search term in the find in current file widget and the find viewlet why do the replace commands behave differently?
ctrl+h will open the find widget and focus the find textbox

ctrl+shift+h will open the find viewlet and focus the replace textbox

Also the different wording of Find/Search seems easy to fix.

Hm, I think the find widget is right. I don't think we should change the wording though.

A good discussion about this happening on Reddit https://www.reddit.com/r/vscode/comments/6i9dut/better_findreplace/


Add enabled parameter to Tooltip

This allows the user to suppress tooltips in some circumstances. It is implemented with the if in the TooltipArea's tooltip composable since it preserves focus on the content() when switching it on/off.

Tested on Windows as well. Nothing to report.


the model version is too old?

I try to install it on Orange Pi 5 Plus and get this error
rkllm init start
rkllm-runtime version: 1.0.1
Warning: The model version is too old, please use the latest toolkit to reconvert the model!
The model target_platform does not match!
RKLLM: failed to load model '/home/orangepi/qwen-chat-1_8B.rkllm'!!!
RKLLM init failed!

I have downloaded the model from this link https://huggingface.co/Pelochus/qwen-1_8B-rk3588

Thank you for bringing this to my attention. This is because that model was converted for RKLLM 1.0 and the current server version is for 1.0.1. I just pushed the legacy version to the repo as the file server_1_0.cpp, this will run that model.

while compiling the server_1_0.cpp, i got error from
131 |     param.modelpath = rkllm_model.c_str();
this error i have fixed with change modelpath  to model_path
however, this error i don't know where to fix it
server_1_0.cpp:138:52: error: invalid conversion from ‘void (*)(const char*, void*, LLMCallState)’ to ‘LLMResultCallback’ {aka ‘void (*)(RKLLMResult*, void*, LLMCallState)’} [-fpermissive]
  138 |     int initResult = rkllm_init(&llmHandle, param, callback);
      |                                                    ^~~~~~~~
      |                                                    |
      |                                                    void (*)(const char*, void*, LLMCallState)
In file included from server_1_0.cpp:13:

Are you using ezrknpu or RKLLM / RKNN, and did you pull the latest version or an older version? Just wondering because the latest version of either is 1.0.1 and the rkllm.h shared library changed since 1.0, so it is incompatible with the older server version (server_1_0.cpp). If you pulled the newer one, can you try with this instead?

I am using ezrknpu , and already pull the old brand, install it but still get the error as above.
Is there any way that i can check which RKLLM version i am using now?

i found how to check which RKLLM version is running by typing command rklllm model
i still using the version 1.0.1
now don't know how to uninstall the version 1.0.1 and reinstall the version 1.0.0

You can find the location of the binary by typing which rkllm. It's likely located at /usr/bin/rkllm. If you wanted to remove it you can rename it or delete it, but this binary shouldn't affect compiling the server, so long as the server is compiled from within the correct version of the toolkits. I would be more concerned that the rkllm.h (probably located at /usr/local/include/rkllm.h) file doesn't match the correct version. Can you make a new directory then put this script into it? Name it something like environment.sh then execute it by typing bash environment.sh.  It will save your environment information into a text file, which may help debug.

You can find the location of the binary by typing which rkllm. It's likely located at /usr/bin/rkllm. If you wanted to remove it you can rename it or delete it, but this binary shouldn't affect compiling the server, so long as the server is compiled from within the correct version of the toolkits. I would be more concerned that the rkllm.h (probably located at /usr/local/include/rkllm.h) file doesn't match the correct version. Can you make a new directory then put this script into it? Name it something like environment.sh then execute it by typing bash environment.sh. It will save your environment information into a text file, which may help debug.

use rk3588s
================================
RAM: 3921
================================
Disk usage: 465G total, 30G used, 431G available, 7% used%
================================
Distributor ID: Debian
Description:    Armbian 24.5.1 bookworm
Release:        12
Codename:       bookworm
================================
Kernel version: 5.10.160-legacy-rk35xx
================================
RKLLM.h version: RKLLM 1.0.1
================================
Python version: Python 3.11.2
================================
dmesg output:
[    5.187024] rk_gmac-dwmac fe1c0000.ethernet: clock input or output? (output).
[    5.493307] input: rk805 pwrkey as /devices/platform/feb20000.spi/spi_master/spi2/spi2.0/rk805-pwrkey.6.auto/input/input0
[    5.514809] vdd_npu_s0: supplied by vcc5v0_sys
[    5.518888] vdd_npu_s0: 550 <--> 950 mV at 800 mV, enabled
[    5.565130] rkisp_hw fdcb0000.rkisp: max input:0x0@0fps
[    5.565930] rkisp_hw fdcc0000.rkisp: max input:0x0@0fps
[    5.665242] input: rockchip-dp0 rockchip-dp0 as /devices/platform/dp0-sound/sound/card0/input1
[    5.667059] input: rockchip-hdmi0 rockchip-hdmi0 as /devices/platform/hdmi0-sound/sound/card1/input2
[    5.668212] input: headset-keys as /devices/platform/es8388-sound/input/input3
[    5.733425] input: rockchip-es8388 Headset as /devices/platform/es8388-sound/sound/card2/input4
[    5.786075] input: adc-keys as /devices/platform/adc-keys/input/input5
[    5.790229] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu-supply from device tree
[    5.790265] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu-supply property in node /power-management@fd8d8000/power-controller failed
[    5.792608] RKNPU fdab0000.npu: Adding to iommu group 0
[    5.792828] RKNPU fdab0000.npu: RKNPU: rknpu iommu is enabled, using iommu mode
[    5.792972] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[    5.793814] RKNPU fdab0000.npu: Looking up mem-supply from device tree
[    5.794531] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff]
[    5.794565] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff]
[    5.794588] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff]
[    5.795292] [drm] Initialized rknpu 0.9.2 20231018 for fdab0000.npu on minor 1
[    5.795716] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up nputop-supply from device tree
[    5.795739] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up nputop-supply property in node /power-management@fd8d8000/power-controller failed
[    5.795810] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu1-supply from device tree
[    5.795830] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu1-supply property in node /power-management@fd8d8000/power-controller failed
[    5.795887] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu2-supply from device tree
[    5.795906] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up npu2-supply property in node /power-management@fd8d8000/power-controller failed
[    5.796026] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[    5.796043] vdd_npu_s0: could not add device link fdab0000.npu: -EEXIST
[    5.796046] vdd_npu_s0: Failed to create debugfs directory
[    5.796604] RKNPU fdab0000.npu: Looking up mem-supply from device tree
[    5.796622] vdd_npu_s0: could not add device link fdab0000.npu: -EEXIST
[    5.796626] vdd_npu_s0: Failed to create debugfs directory
[    5.797269] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[    5.797286] vdd_npu_s0: could not add device link fdab0000.npu: -EEXIST
[    5.797289] vdd_npu_s0: Failed to create debugfs directory
[    5.799200] RKNPU fdab0000.npu: RKNPU: bin=0
[    5.799375] RKNPU fdab0000.npu: leakage=8
[    5.799398] RKNPU fdab0000.npu: Looking up rknpu-supply from device tree
[    5.799415] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!
[    5.807607] RKNPU fdab0000.npu: pvtm=873
[    5.813542] RKNPU fdab0000.npu: pvtm-volt-sel=3
[    5.815213] RKNPU fdab0000.npu: avs=0
[    5.815585] RKNPU fdab0000.npu: l=10000 h=85000 hyst=5000 l_limit=0 h_limit=800000000 h_table=0
[    5.827866] RKNPU fdab0000.npu: failed to find power_model node
[    5.827880] RKNPU fdab0000.npu: RKNPU: failed to initialize power model
[    5.827890] RKNPU fdab0000.npu: RKNPU: failed to get dynamic-coefficient
[    6.138863] input: USB Keyboard USB Keyboard as /devices/platform/fc840000.usb/usb3/3-1/3-1:1.0/0003:1A81:203E.0001/input/input6
[    6.139105] input: USB Keyboard USB Keyboard Consumer Control as /devices/platform/fc840000.usb/usb3/3-1/3-1:1.0/0003:1A81:203E.0001/input/input7
[    6.197976] hid-generic 0003:1A81:203E.0001: input,hiddev96,hidraw0: USB HID v1.10 Device [USB Keyboard USB Keyboard] on usb-fc840000.usb-1/input0
[    6.205575] input: USB Keyboard USB Keyboard as /devices/platform/fc840000.usb/usb3/3-1/3-1:1.1/0003:1A81:203E.0002/input/input8
[    6.261630] hid-generic 0003:1A81:203E.0002: input,hidraw1: USB HID v1.10 Keyboard [USB Keyboard USB Keyboard] on usb-fc840000.usb-1/input1
[    6.267663] hid-generic 0003:1A81:203E.0003: hiddev97,hidraw2: USB HID v1.10 Device [USB Keyboard USB Keyboard] on usb-fc840000.usb-1/input2
[  351.360041] RKNPU fdab0000.npu: RKNPU: set rknpu freq:<PHONE_NUMBER>, volt: 812500


Package Version

Hi,
When I tried to execute example, I encountered with this issues.
I think it's a problem with the torch and sensorboardX version. Do you have the same problem?

It runs for me locally.
What pytorch version are you using?

It runs for me locally.
What pytorch version are you using?

0.4.1
I have tried 0.4.0. It can't work, too.

This repository needs at least version 1.3.0 I believe.
At least that's what the liteflownet implementation references in the requirements

I did not update the dockerfile. Did you install using the docker?

Ok. Thank you. I will try 1.3.0.
I did't use the docker.  I use anaconda for management. Is docker more convenient?

This repository needs at least version 1.3.0 I believe.
At least that's what the liteflownet implementation references in the requirements

It works! Thank you

You're welcome


User execute query is hide in Slowest Individual Queries

Hello there,
When I execute the pgbadger command with parameter -z "/bin/zcat" the user who executes the query in Slowest Individual Queries is disappearing.
PS: declaring --format stderr, the pgbadger auto detected log format 'rds'

$ pgbadger --version
pgBadger version 11.2

Command pgbadger without zcat piped:

$ pgbadger -v --format stderr --exclude-query "^(COPY)" --extension html --title "PostgreSQL teste" --prefix '%t:%r:%u@%d:[%p]:' --outfile - -z "/bin/zcat" ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz > teste.html
DEBUG: timezone not specified, using 10800 seconds
DEBUG: Output 'html' reports will be written to -
DEBUG: Looking for file size using command: gunzip -l ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz | grep -E '^\s*[0-9]+' | awk '{print $2}'
DEBUG: Starting progressbar writer process
DEBUG: Compressed log file, will use command: /bin/zcat "ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz"
DEBUG: Autodetected log format 'rds' from ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz
DEBUG: pgBadger will use log format rds to parse ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz.
DEBUG: Processing log file: ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz
DEBUG: Compressed log file, will use command: /bin/zcat "ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz"
DEBUG: Starting reading file "ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz"...
DEBUG: Start parsing postgresql log at offset 0 of file "ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz" to 376347183
[========================>] Parsed 376347183 bytes of 376347183 (100.00%), queries: 27465723, events: 991
DEBUG: the log statistics gathering took:123 wallclock secs ( 0.09 usr  0.01 sys + 122.26 cusr  0.93 csys = 123.29 CPU)
DEBUG: Output 'html' reports will be written to -
LOG: Ok, generating html report...
DEBUG: building reports took:  6 wallclock secs ( 6.71 usr +  0.00 sys =  6.71 CPU)
DEBUG: the total execution time took: 129 wallclock secs ( 6.80 usr  0.01 sys + 122.26 cusr  0.93 csys = 130.00 CPU)

Using zcat piped to pgbadger:

$ zcat ras-rds-1-postgresql.log.2020-06-25-07-1593072000000.log.gz | pgbadger -v --format stderr --exclude-query "^(COPY)" --extension html --title "PostgreSQL teste" --prefix '%t:%r:%u@%d:[%p]:' --outfile - - > teste-zcat.html
DEBUG: timezone not specified, using 10800 seconds
DEBUG: Output 'html' reports will be written to -
DEBUG: Can not autodetect log format, assuming stderr.
DEBUG: Starting progressbar writer process
DEBUG: Processing log file: -
DEBUG: Starting reading file "-"...
DEBUG: Start parsing postgresql log at offset 0 of file "-" to -1
[+] Parsed 376347183 bytes, queries: 27465723, events: 991
DEBUG: the log statistics gathering took:136 wallclock secs ( 0.07 usr  0.02 sys + 133.24 cusr  0.41 csys = 133.74 CPU)
DEBUG: Output 'html' reports will be written to -
LOG: Ok, generating html report...
DEBUG: building reports took:  7 wallclock secs ( 6.69 usr +  0.02 sys =  6.71 CPU)
DEBUG: the total execution time took: 143 wallclock secs ( 6.76 usr  0.04 sys + 133.24 cusr  0.41 csys = 140.45 CPU)

I tested the command with zcat piped to pgbadger declaring "--format rds" and the result is the same to first (user is disappearing)
How do I force the format?
My database is an Aurora RDS PostgreSQL.

This issue has been solved with commit 3e3c1ae6, you need to upgrade to latest development code or wait for new release 11.3 coming soon.


Series.__or__ and Series.__mod__ don`t work correctly at MODIN_STORAGE_FORMAT=omnisci

When I run:
import pandas
import modin.pandas as pd
from modin.pandas.test.utils import test_data_values
from modin.pandas.test.test_series import inter_df_math_helper
import modin.config as cfg
cfg.StorageFormat.put('omnisci')

data = test_data_values[0]
modin_series = pd.Series(data[next(iter(data.keys()))])
pandas_series = pandas.Series(data[next(iter(data.keys()))])
inter_df_math_helper(modin_series, pandas_series, "__or__")

I have error:
RuntimeError: TException - service has thrown: TOmniSciException(error_msg=non-boolean operands cannot be used in logic operations.)

Also function __mod__ have this error.

@modin-project/modin-omnisci  could someone please check if this still happens?

The reproducer works on master.


grpc conflicting versions

grpc is released into kinetic and melodic but that is going to conflict with the system version.
This was flagged in #19184 and  talking with the maintainer @BillWSY we talked about reducing the ROS packages to just provide the extras that are not in the upstream repositories: https://github.com/ros/rosdistro/pull/19184#issuecomment-424827756
For reference the Melodic PR: #19185
And an incoming rosdep key which will trigger the collision #19292
@BillWSY Would you be able to switch this to the stripped down version soon?

The problem is that we cannot let users choose between the versions as it will just cause problems for downstream users.
If package A chooses implementation 1 and package B choose implementation 2. If a 3rdparty builds package C and depends on package A and package B it will be getting symbols from both conflicting versions but only one can be linked in so you'll get at best linking failures at worst non-deterministic runtime failures.
@nuclearsandwich Looking at it a little closer I think that the python implementation in #19292 doesn't appear to rely on the grpc library I think it has a pure implementation so that's actually slightly separated.

That makes sense. I think ROS had similar issues about OpenCV in indigo, but of course, this is much easier to solve than OpenCV.
The problem for me is that our robot is still running indigo, which makes supporting kinectic/melodic and testing them a lower priority to me. I will check with my colleagues @ruffsl and @MaidouPP to see if they are willing to work on this. Otherwise, I will try to get it done myself in a month or two.

I'm going to close this in favor of tracking it at: https://github.com/CogRob/catkin_grpc/issues/35


clippy: allow non_local_definitions

Problem
some changes for bumping Rust version: https://github.com/anza-xyz/agave/pull/1309

error: non-local `impl` definition, they should be avoided as they go against expectation
   --> sdk/program/src/poseidon.rs:220:9
    |
220 | /         impl From<PoseidonError> for PoseidonSyscallError {
221 | |             fn from(error: PoseidonError) -> Self {
222 | |                 match error {
223 | |                     PoseidonError::InvalidNumberOfInputs { .. } => {
...   |
243 | |             }
244 | |         }
    | |_________^
    |
    = help: move this `impl` block outside the of the current function `hashv`
    = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl`
    = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type
    = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363>
    = note: `-D non-local-definitions` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(non_local_definitions)]`

Summary of Changes
seems this behavior get our code blocks look more elegant. I think maybe we can keep them 🤔

sorry for pinging 😢 looks like this one need to be created in the bump rust version PR.


ENH: Random direction distribution

Reference issue
Closes #16205
What does this implement/fix?
Implements a multivariate distribution to sample uniformly from the surface of the unit sphere.
API wise an important question is how to call this distribution. For now I decided for stats.random_direction. Alternatives could be:

stats.random_unitvector
stats.uniform_direction

One name I would opt against is stats.uniform_sphere as this could also mean a random sample inside the unit sphere. This distribution could easily be implemented in a follow up PR (simply multiply a random direction with $u^{\frac{1}{d}}$ where $u=U(0, 1)$ and dimension $d$ as stated here).
Additional information
My dev environment is somehow broken, so I cannot test properly. I hope that this can still serve as a starting point.
I do not fully understand the whole frozen/non frozen machinery, so a lot of the code is mimiced/copy-pasted from random_correlation.
What is missing is a test that the sampled vectors are indeed uniformly distributed on the unit sphere. Possible tests are listed for example here: https://arxiv.org/pdf/1804.00286.pdf
I am not really familiar with such kind of tests (more a Bayesian guy in the past), so any help appreciated. The algorithms used to generate the samples are theoretically guaranteed to result in the desired distribution though.
CC @saroad2 @rkern

I am +1 on having such distribution. There are so many methods though. We might want to add some methods param?
FYI this dist would he useful for qmc.PoissonDisk. Also remember @stefanv you had a list of different algorithms on one of your repo?

For the name I would like to have hypersphere in the name. As for surface vs volume, it could just be a param.

Linking #17882

I am +1 on having such distribution. There are so many methods though. We might want to add some methods param? FYI this dist would he useful for qmc.PoissonDisk. Also remember @stefanv you had a list of different algorithms on one of your repo?

Agreed, more methods could be very useful. QMC based methods would definitely achieve a better coverage of the surface for the same number of samples.
Can we leave them for a follow-up PR though? My current goal is a merged implementation for the next release, so I would like to keep the scope quite narrow here.

I am +1 on having such distribution. There are so many methods though. We might want to add some methods param? FYI this dist would he useful for qmc.PoissonDisk. Also remember @stefanv you had a list of different algorithms on one of your repo?

Agreed, more methods could be very useful. QMC based methods would definitely achieve a better coverage of the surface for the same number of samples.
Can we leave them for a follow-up PR though? My current goal is a merged implementation for the next release, so I would like to keep the scope quite narrow here.

I am +1 on having such distribution. There are so many methods though. We might want to add some methods param? FYI this dist would he useful for qmc.PoissonDisk. Also remember @stefanv you had a list of different algorithms on one of your repo?

The code I have is for generating approximately equally distributed points on the unit sphere:
https://github.com/fperez/spheredwi/blob/master/src/point_dist.py

I think all reviewer comments were addressed here.
Leftover pain point still: how to call this distribution?
Suggestions so far:

random_direction
random_unitvector
hypersphere_surface
uniform_direction

Kindly asking for more votes here: CC @tirthasheshpatel @rkern @saroad2

Hey @dschmitz89 , thanks for all the hard work on this PR!
As for the name, all names with random in it are problematic in my opinion because the word "random" can mean many things. uniform is a better word, because this is the premis of the new distribution.
If you're asking me, uniform_unit_vector or uniform_direction are the best ones.

I am +1 on having such distribution. There are so many methods though. We might want to add some methods param? FYI this dist would he useful for qmc.PoissonDisk. Also remember @stefanv you had a list of different algorithms on one of your repo?

Agreed, more methods could be very useful. QMC based methods would definitely achieve a better coverage of the surface for the same number of samples.

Yes, although here I was not even referring to QMC but to other methods to sample a hypersphere. There are many different strategies you can use to do that. C.f. the code that Stéfan shared.

Can we leave them for a follow-up PR though? My current goal is a merged implementation for the next release, so I would like to keep the scope quite narrow here.

Sure this can be left for later. Just something to keep in mind to not restrict the API now to allow this kind of improvement.

Leftover pain point still: how to call this distribution?

I took the liberty to edit your comment with emoji so we can use that for voting.

The other methods for sampling a hypersphere are really out of scope for a multi_rv_generic class, IMO. No other distribution gets such distribution-specific, much less non-probabilistic, methods on them. Those other algorithms would be a perfect fit for scipy.spatial, however. There, the design space is completely free.

The distribution was renamed to stats.uniform_direction which won the poll.

I think all reviewer comments were addressed here.
Leftover pain point still: how to call this distribution?
Suggestions so far:

random_direction 😄
random_unitvector 🎉
hypersphere_surface 🚀
uniform_direction 👀

Kindly asking for more votes here: CC @tirthasheshpatel @rkern @saroad2
Please use emoji to express your preference towards a name

Thanks everyone, uniform_direction was implemented.

Sorry about the merge conflicts @dschmitz89 but another distribution just merged. I tried to resolve them online, but I think doing it locally would be safer because git didn't recognize differences as neatly as I might like. LMK if you need help resolving those and if you want me to address https://github.com/scipy/scipy/pull/17277#pullrequestreview-1159147380 and https://github.com/scipy/scipy/pull/17277#pullrequestreview-1159123268 while I'm at it. This is probably ready after that.

Sorry about the merge conflicts @dschmitz89 but another distribution just merged. I tried to resolve them online, but I think doing it locally would be safer because git didn't recognize differences as neatly as I might like. LMK if you need help resolving those and if you want me to address #17277 (review) and #17277 (review) while I'm at it. This is probably ready after that.

It would probably be faster if you directly finish off the rest, this shape and seed business is becoming really confusing without prior contribution experience in stats. Thanks again, your help is highly appreciated.

Thanks @dschmitz89 et al!


Dynamic values in tooltip

Hi!
Following sample:
use Outl1ne\NovaTooltipField\Tooltip;
public function fields(Request $request) {
Tooltip::make('Content', 'someValue')
->text('Text displayed as field value')
->content('Content displayed in tooltip'),
}
, how to get dynamic values - text and content?

You can implement whatever logic / text generation you need on the Eloquent model and then simply rely on $this->resource in order to get to it from the Nova resource.
I'm creating dynamic Tooltips like this and it works fine:
Tooltip::make('')
    ->allowTooltipHTML()
    ->text($this->resource && $this->resource->hasUserNotes() ? '📝' : null)
    ->content($this->resource && $this->resource->hasUserNotes()
        ? '' .__("User notes") .':
' .$this->resource->userNotes()
        : null),

@wdelfuego answer is correct.
We're doing it the same way.
$this->resource should be available at all times.


kubectl get events --watch prints other resource information instead of events

LAST SEEN   TYPE      REASON                     OBJECT                                                  MESSAGE
15s         Normal    Pulled                     pod/greenplum-operator-5575c9fc9d-kx92d                 Container image "greenplum-operator:latest" already present on machine
14s         Normal    Created                    pod/greenplum-operator-5575c9fc9d-kx92d                 Created container greenplum-operator
NAME                                               AGE
my-greenplum-pgdata-segment-a-0.15d6831e50a3f780   0s
master-0.15d6831ea907f0c3                          0s
segment-a-0.15d6831ea99bb164                       0s
master-0.15d6831ee11db490                          0s
master-0.15d6831ee4b8e843                          0s
master-0.15d6831ef4e342f6                          0s
segment-a-0.15d6831efe35790b                       0s
segment-a-0.15d6831f02d2ea06                       0s
segment-a-0.15d6831f1062c08d                       0s

OS: MacOS
K8s: Minikube
Kubectl version:
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T23:41:55Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.5", GitCommit:"0e9fcb426b100a2aea5ed5c25b3d8cfbb01a8acf", GitTreeState:"clean", BuildDate:"2019-08-05T09:13:08Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Duplicate of #734


Using edit_physio() in Spyder breaks console after closing interactive plot session and jupyter is also not working.

This happens in Spyder 4 (didn't test on previous Spyder versions), in Ubuntu 18.04 and latest winpython.
If we can figure out why, it would be great - starting with trying to reproduce the problem in different environments @physiopy/all .

Revisiting that issue: The interactive plot is working for me in jupyter notebook when I specified either %matplotlib widget or %matplotlib ipympl. I can delete and add peaks. However, the deleted/added peaks do not appear afterward in the history of the Physio object...

Yes.

See: https://github.com/matplotlib/matplotlib/issues/13302

Update: it works when using %matplotlib qt:

[X]  Interacting with the figure (i.e. zoom in, moving across it)
[X] Deleting / adding peaks / troughs
[X] Updating the peaks/troughs list (i.e., data.peaks) and history


Recommend full URI to issues instead of just the number

We always copy paste the entire URL to the issue in the last line instead of just #123.

This makes it easy to open the issue when you're browsing the repo somewhere other than your issue tracker — I could just cmd-click on Fixes https://github.com/slashsBin/styleguide-git-commit-message/issues/1 in the terminal while reading the git log.
It allows you to migrate to a new issue tracker (such as github to gitlab) without any confusion.

@slashsBin not interested in this change?

hi
I'm sorry for the delay, I was super busy with a new product launch.
Actually, I don't totally agree with you, although I agree that doing so will improve terminal log viewing.
Personally, for me, it's an overkill to paste the full URL because I need to copy/paste it from somewhere else beforehand.
Another thing is, doing so may break automatcally closing issues using keywords.
Maybe we should simplify browsing issues by other means like:

PHPStorm: Issue Navigation
iTerm2: Smart Selection & Triggers

What do you think?

It seems like GitLab is OK with automatic closing of issues by full URL.

GitHub is also okay with automatic closing by full URL. I also found that I
almost never remember the issue number I'm working on so I need to
copy-paste it anyway. Especially when working with three-four digit issue
numbers.
On Wed, Aug 23, 2017, 9:14 AM Mohammad Shokri<EMAIL_ADDRESS>wrote:

It seems like GitLab is OK with automatic closing of issues by full URL
https://docs.gitlab.com/ee/user/project/issues/automatic_issue_closing.html
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/slashsBin/styleguide-git-commit-message/issues/19#issuecomment-324242576,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAuVAWvUrVnOHdCbADsJUqK-RGc99dqks5sa9FUgaJpZM4N-HE7
.

hi
please check rule#4.
any suggestions?

Perfect, we can consider this issue closed, thank you!


Error in 1.9.11: Cannot resolve module 'build' in /home/...

Version: webpack 1.9.11
Time: 8622ms
   [0] multi main 40 bytes {0} [built] [1 error]
       factory:0ms building:1ms = 1ms
    + 421 hidden modules

ERROR in multi main
Module not found: Error: Cannot resolve module 'build' in /home/user/project/
resolve module build in /home/user/project
  looking for modules in /home/user/project/node_modules
    /home/user/project/node_modules/build doesn't exist (module as directory)
    resolve 'file' build in /home/user/project/node_modules
      resolve file
        /home/user/project/node_modules/build doesn't exist
        /home/user/project/node_modules/build.js doesn't exist
        /home/user/project/node_modules/build.jsx doesn't exist
[/home/user/project/node_modules/build]
[/home/user/project/node_modules/build]
[/home/user/project/node_modules/build.js]
[/home/user/project/node_modules/build.jsx]
 @ multi main
Child extract-text-webpack-plugin:
        + 8 hidden modules

only happens in 1.9.11 - what is going on?

:+1:

I recognized $ webpack build is deprecated or something, so $ webpack is enough.

Had the same issue using webpack-dev-server build. Removing the build worked like a charm.


Kindly update Wiki

My mistake from #2111 is based on confusion because of outdated Wiki: https://github.com/serge-rider/dbeaver/wiki/New-Table-creation on Primary Key creation.

Thanks for information, we'll fix wiki


Json in body

Hi,
Very good work! i am working on a my api documentation. I need to put some json code in the body,like example. how can i do?
##~ o = a.operations.add
##~ o.set :httpMethod => "POST", :summary => "Returns all of the foos.", :deprecated => false, :nickname => "test"
##~ p = o.parameters.add
##~ p.set :name => "body", :dataType => "String" ,:required => true
Thank in advance
Federico

hi @federicolucca , you will send the json object encoded as a string, so why do you use the :dataType => String
I  do not know if the evolution of swagger spec is proving additional dataType, if so, try just to change the type "String" to whatever dataType is available, that should do the trick. The source2swagger is just a "half-assed"  way to declare a swagger spec, which is basically a json object with the grammar.
hope it helps,

Thanks a lot!!! i resolved like this example
##~ signup = {:id => "Signup", :properties => {:email => {:type => "string"}, :device => {:type => "string"}, :id => {:type => "string"}, :name => {:type => "string"}, :surname => {:type => "string"}}}
##~ s.models = {"SignUp" => signup}
##~ p.set :name => "body", :dataType => "SignUp" ,:paramType => "body" ,:required => true
thanks again


Allow ETH1 to run standalone

When trying to run an ETH1 client in standalone mode, I get
ERROR: The Compose file is invalid because:
Service beacon has neither an image nor a build context specified. At least one must be provided.
Look into options

Completed.


Document how to enable github authentication

Got far enough to need this one. Do it and I'll review instantly. :+1:

So I dug up the variables grep GITHUB empire/cmd/empire/main.go and created a new task revision with that. Now I just need the callback url.

My shoelace version of instructions, you are free to use them:

Create a new Github Application under your organization with /oauth/authorizations as callback
Find the appropriate cluster on AWS ECS Console
Select the appropriate service empir-...
Select the task definition
Create new revision
Add three environment variables EMPIRE_GITHUB_CLIENT_ID, EMPIRE_GITHUB_CLIENT_ID and EMPIRE_GITHUB_ORGANIZATION with the details you got from Github. Your organization being the one in the URL.
Go back to the service and click on Update
Select the new task definition (which is TheOldOneXYZ:2 if the previous ended with :1)

And while we're at it, should notice to enable HTTPS before throwing your production credentials over and mention to do that on the respective ELB.

Does enabling GH auth disable the "fake" user?

Definitely need SSL as a part of this.

The answer to my question appears to be yes :)
When you say this should be behind SSL do you image that this would normally be behind an ELB doing the SSL termination?

@phobologic ACK. I'll have a look tomorrow.

@public That's the standard mode of operation. If you want a security in depth approach with this... which would make sense, you would possibly decide not to terminate on ELB. However that is far more complex.

Yeah - in general, the easiest way to do the SSL is to have the ELB terminate it.  The hard part about automating that is that you can't create SSL certificates via Cloudformation, you have to submit them then refer to them in the Cloudformation template.
We're working on the 'production best practices' doc this week, so hopefully we'll have something up for you guys ASAP.

Is there any way to restrict github authentication to a specific github team?

@crohr not right now, but that would be a great addition and should be relatively easy to add by adding a check after checking the organization. We're also talking about adding an ACL system to restrict access to certain features for certain groups (e.g. some group can't use emp run or emp env, etc), which may be backed by github teams.

@ejholmes sounds great! I'll see if I can make a single team restriction work with my limited Go knowledge ;)

Going to close this out for now. FYI, team authorization restrictions will be really easy to add after https://github.com/remind101/empire/pull/687.


Migrate to ESM

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Model field tag "default" not working correctly

GORM Playground Link
https://github.com/go-gorm/playground/pull/498
Description
I need to create record in DB with false (bool), but when I have field with default field tag set to 1, it set it to 1 instead of 0

Use sql.NullBool
- Test bool `gorm:"default:1"`
+ Test sql.NullBool `gorm:"default:1"`

Sorry, but it' is'nt clear to me, why I can't use simple bool type from go types? Is there some problem in the library, which couldn't be easily fixed or is there some general "problem" which I don't understand? I'd like to know more than just use this. Because I use it like this on a project in many places in code and changing it, won't be easy. Thank you for your explanation.

If a value is zero, there is no way to tell whether it is a default value or a user-specified value. You can also use *bool to tell us it is specified value

Hey, on a similar note, it seems that when the value is 0 for an int64 field, GORM just removes the field from the insert (it runs an INSERT INTO with all fields except that one).
It looks like this is pointing to a bigger issue with default values.
This is particularly an issue for me because said field is my primary key

Ok well if it can help anyone, if you're trying to insert a 0 value, you need to set the field to a pointer-to-value (int64 -> *int64 in my case). By default, empty values like 0 for numbers are removed by Go


Something gnarly happening with this code block

Same effect in both Firefox and Chrome on Linux.
https://developer.fermyon.com/wasm-languages/grain

And differently borked in Edge on Windows 11.  I think we've seen this before - @karthik2804 @flynnduism ring any bells?

I believe there is some messed up formatting. I can take a look in the morning.

Oh, the block has a grain highlight marking.  I bet the highlighter doesn't recognise that and chooses to express its confusion in the tradition of its people.

@itowlson you are right. I will open a PR.


Add staticrequired to pre-push hooks

The Problem/Issue/Bug:
The provided (optional) githooks don't provide make staticrequired which is one thing we'd like them to have.
How this PR Solves The Problem:
Adds it.
This change affects only developers who link the pre-push hooks, it doesn't affect users, testing, etc.

Thanks @andrewfrench  - I actually just moved the make staticrequired into the pre-push.allchecks. I guess maybe I'll add a script to turn it on and off still.


add ContainerServiceFleet test support

Add CRUD Test for ContainerServiceFleet, with assets from: https://github.com/Azure/azure-sdk-assets/releases/tag/net%2Ffleet%2FAzure.ResourceManager.ContainerServiceFleet_3a38e8ed58
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Add compatibility check for primitive schema types

Motivation
To fix #4831
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (yes)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)
Documentation
Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes
Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (yes)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)
Documentation
Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

run cpp tests


Add in babel polyfill to build, update link for messages

Hopefully global nav will work in IE9+ with this update.

:+1:


igv: 2.3.77 -> 2.3.89

Motivation for this change
Update igv to the last version
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

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

Merged in 29cb10c0217c0e72cabbe2c43b93ea57ef9a1558 thank you!


Use less confusing terminology for string parts in DiagnosticPath

Fixes #11438
Changed confusing mentions of 'components' in DiagnosticPath that were referring to strings.
Alice 'thumbs up'-ed JMS55's suggestion of using the term 'section', so I went with that instead of 'part' like mentioned in the issue.

components is very standard when speaking of parts of a path, section is a lot more confusing to me

I find this meaningfully clearer, but I don't feel strongly here. Thank you @capt-glorypants for making this PR regardless :)


why the SMPL pose looks a little shaky?

I download the code and run test_skeleton() in 3DViewer.py and find smpl skeleton is shaky.
Is it a numerical precision problem?

I guess it's because when transferring pose from ASF skeleton to SMPL skeleton some small errors are introduced and accumulated through the skeleton hierarchy, finally result in the visible shaking. I think numerical precision problem shouldn't be that obvious.


provide sharding jdbc as storage

Please answer these questions before submitting your issue.
What version of sky-walking are you using?
3.1
What version of your OS?
Linux
What version of your JRE?
1.8
What company or project?
DangDang
Provide sharding jdbc as storage

Provide sharding jdbc as storage

Glad to know this from dangdang tech team. Hope this can be provided in Skywalking 3.3.x . If you need any help, you can call anyone from @OpenSkywalking/pmc and @hanahmily .

@clevertension Can you export or provide a list of H2 table(Include columns, data type)?
FYI @peng-yongsheng

@oracle219 @chidaodezhongsheng Do you have news to update?

I need some examples codes of strorage module,but these codes do not implements by @peng-yongsheng ,i still waiting him.

@chidaodezhongsheng You want to ref the H2 implementations?

Yes,i need 8 ui dao codes.

Not active, closing. MySQL storage would be provided.


Relations as list of values in a property

Assuming there is a relation admin -> accounts like:
{
    "id": 1,
    "firstName": "Test",
    "lastName": "User",
    "active": true,
    "accountIds": [1, 2, 3, 4, 5]
}

it is possible to load all those accounts when requesting admins for example? Something like /admins/1/accounts?
Is there a ways to have that or it is required to put the admin id in the account object anyways?
thanks in advance,
David

No, but you can use a module and access the json directly via a custom route. You would use lowDBs documentation to map through the array of IDs and grab each account that matches the iterated id and add it to your response.

Thanks!

111

123

555