Why relationship not working ?

Laravel Version: 5.4.21
PHP Version: 5.6
Database Driver & Version:

Description:
Hello i have a site in laravel5.4, but question i have tables categories category_translations items item_translations and item_categories
plugins Dimsav for translations and Baum for nested tree
when i make
$items = Item::all();
   return $items;

i get only items without any relationship
in item model i have
class Item extends Model {
use \Dimsav\Translatable\Translatable;

/**
 * Table name.
 *
 * @var string
 */
protected $table = 'items';

public $translatedAttributes = ['name'];
protected $fillable = ['title'];

public function categories() {
    return $this->belongsToMany(Category::class);
}
}

and in category model
class Category extends Node {
use \Dimsav\Translatable\Translatable;

protected $table = 'categories';

protected $parentColumn = 'parent_id';

protected $leftColumn = 'lft';

protected $rightColumn = 'rgt';

protected $depthColumn = 'depth';

protected $orderColumn = null;

protected $guarded = array('id', 'parent_id', 'lft', 'rgt', 'depth');

protected $scoped = array();

public $translatedAttributes = ['name'];
protected $fillable = ['title'];

public function items()
{
    return $this->belongsToMany(Item::class);
}
}

but i can t get relationship someone know how i can do that ? this return only items data but 0 relationship example
[{"id":1,"created_at":null,"updated_at":null,"title":"First Item"}]
i want var_dump($items) and get collection with all relationship
Thanks you

$items = Item::with('categories')->all();

This repo is for bug tracking. Use the forums or slack channel for solving your issue


HIP 56: Improved State Channel Disputes

HIP 56: Improved State Channel Disputes

Author(s): @macpie,@michaeldjeffrey, @Vagabond, @abhay, et al
Start Date: 2022-02-21
Category: Technical
Original HIP PR: https://github.com/helium/HIP/pull/366
Tracking Issue: https://github.com/helium/HIP/issues/369 (this)
Status: In Discussion

Summary
This HIP describes an update to the dispute mechanism for State Channels that
would improve blockchain scaling, better reconcile Data Transfer activity and
rewards for Hotspots, and address recent issues around large block sizes.
State Channel disputes provide a mechanism to validate the integrity of a State
Channel. Previously, disputes triggered by participating Hotspots contained
redundant information, and increased block size. On a couple of occasions the
number of disputes caused some large blocks to halt chain activity due to
Validators not being able to consume them. This proposal retains the State
Channel integrity check by any participant, but also updates the dispute
mechanism to prevent disputes from halting chain activity.
We propose that the first valid instance of a disputed State Channel that is
accepted by Validators becomes canonical and does the following:

All other disputes are marked as invalid and are rejected by the Consensus
Group.
No rewards are distributed to any participant of the State Channel.
The State Channel owner will still be slashed of its Data Credits and its
Data Credit overage. As a note, this point is the current implementation that
will not be changed with this proposal.

We believe these three steps (with the changes included) will reduce the impact
of State Channel disputes on the overall blockchain and not inadvertently reward
(potentially) colluding actors who could be in control of both the Hotspot and
the Router. This would allow the blockchain to increase the State Channel Grace
Period (described below) and better reward Hotpots in the majority of cases
where Routers are able to close State Channels promptly and Hotspots do not need
to file disputes.
Rendered View
https://github.com/helium/HIP/blob/main/0056-state-channel-dispute-strategy.md

The HIP has been approved via heliumvote, with +99% voting For HIP 56.
On behalf of the DeWi, the HIP Editors, and the wider Helium community, I am marking this proposal as approved and recommending that the coredev team implement the necessary changes as soon as reasonably possible.


⚠ Samsung has degraded performance

In 077d968, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2583 ms

Resolved: Samsung performance has improved in 99b6a79.


Can't keep "Solid Color" in export from Paraview

Hi,
I am attempting to export a scene from Paraview desktop into Paraview Glance. In the simplest case, I have a .vtp surface which I am selecting to display as a "Surface" in Paraview with coloring defined as "Solid Color" and a color selected from the "Basic Colors" provided in the Paraview color picker. I can successfully export this scene into an embedded Paraview Glance instance .html file using the procedure outlined here: https://blog.kitware.com/exporting-paraview-scenes-to-paraview-glance/
However, when loaded the display always defaults to a "Scalars_" coloring and the "solid color" option must be manually selected to recover the intended representation. The following errors are given:
ParaViewGlance: 4.17.1
Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
attempt to set zero width color range
attempt to set zero width color range
attempt to set zero width color range

There does not appear to be an issue with the solid color representation once it is manually selected, it displays as intended.  However in cases where we have multiple surfaces, asking each viewer to manually change each individual surface to a "Solid Color" is unreasonable.
An example of the html is available here: https://liamtimms.net/paraview/test_simple_artery.html

Workaround is setting up and saving glance displays directly instead.

My team has encountered what I believe is the same bug. I opened a new issue at #504.


feat: react-native support

User description
resolves https://github.com/nhost/projects/issues/78

PR Type
Enhancement, Documentation

Description

Added SignIn and SignUp screens with form validation and OAuth options.
Implemented Main screen with navigation and authentication status check.
Added UploadFile component for file uploads.
Added AddTodoForm component for adding new todos.
Added Button component with loading state.
Added Todo component with delete functionality.
Added Todos screen for listing all todos.
Added Drawer component for navigation drawer with sign-out functionality.

Changes walkthrough 📝
Relevant filesEnhancement
15 files

SignIn.tsxAdd SignIn screen with email/password and OAuth options

templates/react-native/template/src/screens/SignIn.tsx
Added SignIn screen with email/password and OAuth sign-in options.  Implemented form validation and submission handling.  Included OAuth sign-in using InAppBrowser.

+167/-0

SignIn.tsxAdd SignIn screen with email/password and OAuth options

examples/react_native/src/screens/SignIn.tsx
Added SignIn screen with email/password and OAuth sign-in options.  Implemented form validation and submission handling.  Included OAuth sign-in using InAppBrowser.

+167/-0

SignUp.tsxAdd SignUp screen with email/password sign-up

templates/react-native/template/src/screens/SignUp.tsx
Added SignUp screen with form validation and submission handling.  Implemented email/password sign-up with email verification.

+142/-0

SignUp.tsxAdd SignUp screen with email/password sign-up

examples/react_native/src/screens/SignUp.tsx
Added SignUp screen with form validation and submission handling.  Implemented email/password sign-up with email verification.

+142/-0

Main.tsxAdd Main screen with navigation and auth check

examples/react_native/src/screens/Main.tsx
Added Main screen with navigation setup.  Implemented authentication status check and conditional navigation.

+98/-0

Main.tsxAdd Main screen with navigation and auth check

templates/react-native/template/src/screens/Main.tsx
Added Main screen with navigation setup.  Implemented authentication status check and conditional navigation.

+77/-0

UploadFile.tsxAdd UploadFile component for file uploads

templates/react-native/template/src/components/UploadFile.tsx
Added UploadFile component for file uploads.  Implemented file picker and upload handling.

+82/-0

UploadFile.tsxAdd UploadFile component for file uploads

examples/react_native/src/components/UploadFile.tsx
Added UploadFile component for file uploads.  Implemented file picker and upload handling.

+82/-0

AddTodoForm.tsxAdd AddTodoForm component for adding todos

examples/react_native/src/components/AddTodoForm.tsx
Added AddTodoForm component for adding new todos.  Implemented form validation and submission handling.

+64/-0

Button.tsxAdd Button component with loading state

templates/react-native/template/src/components/Button.tsx
Added Button component with loading state.  Implemented customizable button styles and labels.

+67/-0

Button.tsxAdd Button component with loading state

examples/react_native/src/components/Button.tsx
Added Button component with loading state.  Implemented customizable button styles and labels.

+67/-0

Todo.tsxAdd Todo component with delete functionality

examples/react_native/src/components/Todo.tsx
Added Todo component for displaying individual todos.  Implemented delete functionality for todos.

+56/-0

Todos.tsxAdd Todos screen for listing todos

examples/react_native/src/screens/Todos.tsx
Added Todos screen for listing all todos.  Implemented loading state and data fetching.

+56/-0

Drawer.tsxAdd Drawer component with sign-out functionality

templates/react-native/template/src/components/Drawer.tsx
Added Drawer component for navigation drawer.  Implemented sign-out functionality.

+55/-0

Drawer.tsxAdd Drawer component with sign-out functionality

examples/react_native/src/components/Drawer.tsx
Added Drawer component for navigation drawer.  Implemented sign-out functionality.

+55/-0

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.95%. Comparing base (68e0622) to head (debe47a).
Report is 19 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2675      +/-   ##
==========================================
- Coverage   86.06%   85.95%   -0.11%
==========================================
  Files          86       86
  Lines        9484     9604     +120
  Branches      486      485       -1
==========================================
+ Hits         8162     8255      +93
- Misses       1322     1349      +27

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

/describe

/review


Problems with destructured object since Histoire version 0.7.3

Describe the bug
Scenario:
You have different objects for configuring the different variants of a component. You destructure from the default, to be not that repetitive. So for variants you destructure from default and only add what differs from default.
The default object contains also an array.
When rendering histoire. The view where the components are displayed is getting it right. But on the controls panel for all variants that are destructuring from default, the destructured props are empty.
This was fine in histoire version 0.7.2 and is broken since version 0.7.3

Reproduction
Working with Histoire 0.7.2:
https://stackblitz.com/edit/histoire-vue3-starter-ptkj4x?file=package.json,src%2FBaseSelect.story.vue
Broken with Histoire 0.7.3 until 0.7.9 (latest):
https://stackblitz.com/edit/histoire-vue3-starter-68v42f?file=src%2FBaseSelect.story.vue,package.json
System Info
System:
    OS: macOS 12.1
    CPU: (8) x64 Apple M1
    Memory: 18.02 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 103.0.5060.114
    Firefox: 102.0.1
    Safari: 15.2
  npmPackages:
    @vitejs/plugin-vue: ^2.3.3 => 2.3.3
    histoire: ^0.7.9 => 0.7.9
    vite: ^2.9.13 => 2.9.13

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

@Akryum would like to reopen, cause it looks like in latest version this is again completely broken


UB Sanitizer implicit-integer-sign-change warning in boost::urls::grammar::detail::find_if_not_pred

Boost: 1.82.0
Clang: 13
Ubuntu Linux / x64
Reproducer (with implicit-integer-sign-change enabled, -fsanitize=integer for example):
#include <boost/url/parse.hpp>
int main()
{
    (void)boost::urls::parse_relative_ref("/\xff");
}

Observed warning from Undefined Behavior Sanitizer:
boost/url/grammar/detail/charset.hpp:171:14: runtime error: implicit conversion from type 'char' of value -1 (8-bit, signed) to type 'unsigned char' changed the value to 255 (8-bit, unsigned)
    #0 0x52c0903 in char const* boost::urls::grammar::detail::find_if_not_pred<boost::urls::grammar::lut_chars>(boost::urls::grammar::lut_chars const&, char const*, char const*) src.cpp
    #1 0x52c09ae in boost::system::result<boost::urls::pct_string_view, boost::system::error_code> boost::urls::detail::parse_encoded<boost::urls::grammar::lut_chars>(char const*&, char const*, boost::urls::grammar::lut_chars const&) src.cpp
    #2 0x52addec in boost::urls::detail::relative_part_rule_t::parse(char const*&, char const*) const src.cpp
    #3 0x52b1e92 in boost::urls::relative_ref_rule_t::parse(char const*&, char const*) const src.cpp
    #4 0x52b70f7 in boost::system::result<boost::urls::relative_ref_rule_t::value_type, boost::system::error_code> boost::urls::grammar::parse<boost::urls::relative_ref_rule_t>(boost::core::basic_string_view<char>, boost::urls::relative_ref_rule_t const&) src.cpp
    #5 0x5296227 in boost::urls::parse_relative_ref(boost::core::basic_string_view<char>) src.cpp

This warning in particular is not about undefined behavior. It's more of a code quality warning (https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html):
-fsanitize=implicit-integer-sign-change: Implicit conversion between integer types, if that changes the sign of the value. That is, if the original value was negative and the new value is positive (or zero), or the original value was positive, and the new value is negative. Issues caught by this sanitizer are not undefined behavior, but are often unintentional.

Origin of the warning in boost/url/grammar/detail/charset.hpp:
template<class Pred>
char const*
find_if_not_pred(
    Pred const& pred,
    char const* first,
    char const* last ) noexcept
{
[...]
    while(
        first != last &&
        pred(*first)) // <-- warning here
    {
        ++first;
    }
    return first;
}

The function being called is declared in boost/url/grammar/lut_chars.hpp:
    constexpr
    bool
    operator()(
        unsigned char ch) const noexcept
    {
        return mask_[lo(ch)] & hi(ch);
    }

These headers haven't been changed on develop since 1.82.0, so my issue should be reproducible with the current develop branch.
Suspected cause of the warning: *first is a char, but the function takes an unsigned char. The value \xff as a char is represented as -1. The implicit conversion to unsigned char changes the value to 255 which UB Sanitizer warns about.
Possible fix: pred(static_cast<unsigned char>(*first)) if that was the original intention.
Workaround: Currently suppressing the warning in Boost.URL with an entry in my suppression file: implicit-integer-sign-change:/usr/local/include/boost/url/grammar/detail/charset.hpp.
Suggestion: Run the tests with as many sanitizers warnings enabled as possible.

Interesting issue. Thanks. I'll be looking.

Suggestion: Run the tests with as many sanitizers warnings enabled as possible.

What's interesting is we are testing clang 14 with asan + ubsan, which should detect the same error.
https://github.com/boostorg/url/actions/runs/7587792728/job/20669035052
I would prefer to be able to replicate the error in CI before moving on with the solution.

mmm... according to https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html, implicit-integer-sign-change should be enabled with -fsanitize=undefined...

-fsanitize=undefined: All of the checks listed above other than float-divide-by-zero, unsigned-integer-overflow, implicit-conversion, local-bounds and the nullability-* group of checks.

The only warning enabled by -fsanitize=integer that shouldn't be enabled by -fsanitize=undefined is unsigned-integer-overflow

-fsanitize=integer: Checks for undefined or suspicious integer behavior (e.g. unsigned integer overflow). Enables signed-integer-overflow, unsigned-integer-overflow, shift, integer-divide-by-zero, implicit-unsigned-integer-truncation, implicit-signed-integer-truncation, and implicit-integer-sign-change.

I included a job with -fsanitize=integer explicitly but still can't replicate it:
https://github.com/boostorg/url/actions/runs/7793196452/job/21252638333?pr=817#step:11:162
What command are you using to build it? Is it cmake or b2?

I included a job with -fsanitize=integer explicitly but still can't replicate it:
https://github.com/boostorg/url/actions/runs/7793196452/job/21252638333?pr=817#step:11:162

In the section Test under CMake Root Workflow it says:
  🧪 Tests (C++20)
  💻 /__w/url/url> /__w/_temp/6c6bf9ea-b5d6-4f29-92d0-1f6ca8af4b27/cmake-3.15.0-Linux-x86_64/bin/ctest --test-dir /__w/url/url/__build_cmake_root__ --parallel 2 --build-config Release --no-tests=error --progress --output-on-failure
  /__w/_temp/6c6bf9ea-b5d6-4f29-92d0-1f6ca8af4b27/cmake-3.15.0-Linux-x86_64/bin/ctest --test-dir /__w/url/url/__build_cmake_root__ --parallel 2 --build-config Release --no-tests=error --progress --output-on-failure
  Test project /__w/url/url
  No tests were found!!!

Could this be an issue?

What command are you using to build it? Is it cmake or b2?

I am using b2:
./b2 link=static toolset=clang \
cxxflags="-fPIC -fstack-protector -fstack-check -D_FORTIFY_SOURCE=2 -stdlib=libc++ -v -I/usr/lib/llvm-13/include/c++/v1 -fsanitize=undefined -fsanitize=nullability -fsanitize=float-divide-by-zero -fsanitize=local-bounds -fsanitize=implicit-integer-truncation -fsanitize=implicit-conversion" \
cxxstd=20 \
-d1 -j4 \
--with-thread --with-system --with-chrono --with-date_time --with-filesystem --with-random --with-atomic --with-context --with-url install

  No tests were found!!!

 Let me check that. Thanks!


Fetch Saldo from non SEPA Account

Hi is it possible to fetch the Saldo from a Creditcard in my Bankaccount ? I use Postbank i get the Saldo from the Sepa Accounts but if i try on the "VISA Card Classic" i get an Errormessage "Fhp\FinTs::getSaldo() must be an instance of Fhp\Model\SEPAAccount"
thanks for help

👍 @mschindler83 Any news on this?


Allow HomeKit accessory information to be customized

Description:
HomeKit accessory information can be customized by specifying name, manufacturer, model, and/or serial_number within entity_config.
Related issue (if applicable): N/A
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#5314
Example entry for configuration.yaml (if applicable):
homekit:
  port: 51825
  filter:
    include_domains:
      - lock
  entity_config:
    lock.front_door:
      name: Front Door Lock
      manufacturer: Schlage
      model: Connect
      serial_number: 123456789

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

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

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

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

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

If the code does not interact with devices:

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

@cdce8p This is my first draft, take a look and let me know your feedback. As discussed in #14114, this doesn't provide much direct functionality but just gives a cleaner experience for those that care. It's a similar concept to that of the Alexa cloud component.

I have to think about it, but at the moment I'm not convinced this should be added.

There have been a few changes with #14278
If you rebase it, I can take a new look at it next week

@cdce8p Rebased with the latest updates

Regarding the config dictionary: I was thinking about how we can improve it since I don't
Iike adding it to every super call.
Why don't we use the same custruct as for hass and the entity_id? Remove the keyword in get_accessory and pass it through args. Than assign it to self.config in HomeAccessory.

@cdce8p I updated per your comments, updated the doc, and updated the test_util. I'm not sure what other tests need to be added or updated, can you give a little advice?

@schmittx As a starting point take a look at the failing tests: https://travis-ci.org/home-assistant/home-assistant/jobs/375445342#L808. Since config is no longer a keyword argument, most of the accessory tests are failing. As an example:
acc = GarageDoorOpener(self.hass, 'Cover', garage_door, 2, config=None)

# Would need to change to this:
acc = GarageDoorOpener(self.hass, 'Cover', garage_door, 2)

Basically config can be removed, except for security_systems.

Another thing would be to add checks for the newly added vars to test_home_accessory: https://github.com/home-assistant/home-assistant/blob/dev/tests/components/homekit/test_accessories.py#L91-L97

And for the name config var a test in get_accessories, here: https://github.com/home-assistant/home-assistant/blob/dev/tests/components/homekit/test_get_accessories.py#L33

@cdce8p Thanks for the help, I updated/added most of the tests without problem. But, I keep getting KeyError with test_get_accessory_customize_name and test_alarm_control_panel as they're currently written. Can you take a look and give me some suggestions?

@cdce8p Sounds good to me, this should be good to go now once the tests pass.
FYI, I'm also working on adding support for Fan entities. I should have that PR ready later this week or next weekend.

@schmittx Regarding fan support. I think someone else was already working on it, although I haven't seen an open PR yet. Take a look at #13805.
We should't talk to much about it in this PR though, to keep it clean. Find me on discord.

@cdce8p Valid point, I’ll keep fan support discussion elsewhere.

I read #14330 today. It seems that for future compatibility it might be necessary to revert some parts of #14159 in order for it to work.

The serial number must be unique. Maybe the aid?
To still have the entity_id available, the change to model should probably be reverted.
In the end, it might just be enough to be able to customize the accessory name.

@schmittx What do you think about that? Am I missing something?

@cdce8p I read through #14330 as well as the repos that it mentioned. I understand the benefit of being able to see the history for accessories and persistent storage but I'd be hesitant to implement it due to the convoluted method required and the need to use the Eve app exclusively (if history is desired). I also think there's a high risk of regular maintenance being needed in the event that Elgato changes their services/characteristics.
I think we should focus on using the native Apple HomeKit services/characteristics in order to guarantee a consistent experience for all users, regardless of what app is used (Home, Eve, etc.).
For now, I'd vote to focus on improving the current HomeKit component (i.e. add support for more entities like media_player or show switches as valve/sprinklers, adding optional characteristics to existing entities, battery tracking, etc.).
If we run out of things to improve for this component and want to revisit Fakegato in the future then let's worry about the accessory information at that time (Maybe we'd make Fakegato a config option, which would then overwrite any accessory information with unique serial numbers, etc.?)

I agree with almost all of your points. The native services and chars are just easier to maintain at the moment and the focus should be an improving support for other components (eg. Media Player, Fan, ...).
What I'm worried about however is that it's quite difficult to take a feature away once it's implemented. If we really decide to implement fakegate, it shouldn't come at the cost of overriding the serial number if it's activated (maybe through a config option).
Therefore I would prefer if we limit the configurable parameters to the name only and assign the others as explained before. We can always add features later, but removing them is really difficult.

I agree that it's difficult to remove a feature once it's implemented, I just struggle with limiting functionality now in the hopes that we might add something else in future.
I'll defer to you in the end though. If we limit the confutable parameters to just name, then I'd propose to close this PR and create a new one. Then we can always come back to this in the future if necessary.

I agree that it's difficult to remove a feature once it's implemented, I just struggle with limiting functionality now in the hopes that we might add something else in future.

Take in mind that this doesn't add any new functionality, just the option to customize some additional parts.

If we limit the confutable parameters to just name, then I'd propose to close this PR and create a new one. Then we can always come back to this in the future if necessary.

We shouldn't do that. This PR has some great foundations in place to implement this feature. A new PR would just copy most of it. A better way might be to create a new PR once this is merge that adds the additional parameters as well and close that for the time being.

@cdce8p OK, everything should be good now. Rebased with #14377 and a small cleanup afterwards.

@schmittx Will take a closer look tomorrow. Thanks for taking the time!

@schmittx BTW: I have started looking into the complete async conversion for the homekit component. homekit-async if you want to take a look.
Are you in the HA discord channel? Discussing it there or in direct msg might be the easiest.


Release Google.Cloud.Notebooks.V1 version 2.3.0

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.Notebooks.V1-2.3.0


Updates the backport tool

Updates the backport tool
Checklist

[x ] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

What does this change do?

@hdhalter It prevents us from creating backport PRs on PRs that have not been merged yet.


Log Level

when i set log level as warning or error and exec start ,program panic. My topology like this:

2022-09-16 14:26:35.964 CST [nwo.runner] Run -> INFO 015 running [fabric.default-OrdererOrg.orderer] with ginkgo stdout/stderr
panic: Timed out after 1.002s.
Error: Exit must be passed a gexec.Exiter (Missing method ExitCode() int) Got:
: -1
goroutine 69 [running]:
github.com/hyperledger-labs/fabric-smart-client/integration.failMe({0xc000052680?, 0x16?}, {0xc00072d9f8?, 0x5?, 0x5?})
/Users/shengyulong/workspace/go/src/github.com/hyperledger-labs/fabric-smart-client/integration/integration.go:335 +0x2d
github.com/onsi/gomega/internal.(*AsyncAssertion).match.func1({0x4cb76f4, 0x9})
/Users/shengyulong/workspace/go/pkg/mod/github.com/onsi/gomega@v1.19.0/internal/async_assertion.go:184 +0x31d
github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0006440a0, {0x4f344d0, 0xc000638018}, 0x1, {0x0, 0x0, 0x0})
/Users/shengyulong/workspace/go/pkg/mod/github.com/onsi/gomega@v1.19.0/internal/async_assertion.go:206 +0x598
github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0006440a0, {0x4f344d0, 0xc000638018}, {0x0, 0x0, 0x0})
/Users/shengyulong/workspace/go/pkg/mod/github.com/onsi/gomega@v1.19.0/internal/async_assertion.go:107 +0x6b
github.com/hyperledger-labs/fabric-smart-client/integration/nwo/common/runner.(*Runner).Run(0xc0002986c0, 0xc0000a8660, 0xc000644000?)
/Users/shengyulong/workspace/go/src/github.com/hyperledger-labs/fabric-smart-client/integration/nwo/common/runner/runner.go:140 +0x10c4
github.com/tedsuo/ifrit.(*process).run(0xc0004e40c0)
/Users/shengyulong/workspace/go/pkg/mod/github.com/tedsuo/ifrit@v0.0.0-20191009134036-9a97d0632f00/process.go:71 +0x31
created by github.com/tedsuo/ifrit.Background
/Users/shengyulong/workspace/go/pkg/mod/github.com/tedsuo/ifrit@v0.0.0-20191009134036-9a97d0632f00/process.go:49 +0x125

Hi @Virus-Syl , good catch.
Indeed, we need at least info to allow NWO to catch a log line that signals that the node has started.
Is there a special reason why you want to have 'error` there?

oh, this is interesting.
@mbrandenburger, do you want to jump in here?
@Virus-Syl , do you have more info on the memory leak that can help us?

i rename iou as rbcsn

@Virus-Syl , any update on this?

closing this, it is too old


Presenter surivival

Is it possible to add template for this strategy?

Sorry, didn't understood

Sorry, for this "panic", I logged some methods and here is result:
D/MainPresenterImpl: MainPresenterImpl: creation: 292446359
D/MainActivity: onCreate: 747806087
D/MainPresenterImpl: onStart: view: 747806087, presenter: 292446359
D/MainPresenterImpl: MainPresenterImpl: creation: 356988377
D/MainPresenterImpl: onRestoreState: view: 9452446, presenter: 356988377
D/MainActivity: onCreate: 9452446
D/MainPresenterImpl: onStart: view: 9452446, presenter: 356988377

I've heard, that Android N multi-window feature will trigger same behavior as Screen Rotating, how to save data/presenter between screen rotation since it recreates after every activity recreation?

Hi Tony,
Indeed the presenter lifecycle is tied to its activity so if the activity is destroyed then its presenter too.
You have 3 ways (maybe more) to handle that problem:

Easiest: Declare in your manifest to not recreate your activity on rotation/resize/whatever with the configChange tag
Safest: Save your data into the bundle on onSaveInstanceState and restore it on onRestoreState, this is the exact purpose of those methods but it has limitations (like if you're in the middle of a data loading process)
Advanced: Use your presenter as a loader to survive activity recreation, more on that here

Hope it helps!

Hey @tonyshkurenko,
Just wanted to let your know that the last version I pushed a few days ago now supports presenter survival.
More on that on the README.
Best


n/N skip some entries

Seems to be approx 10% of entries. n and N skip a different set of entries.
I haven't had time to look at steps to reproduce this (and I'm not sure I will).
My entries are fairly sporadic rather than all bunched up.

Thanks for the report. Unfortunately I could not reproduce the issue (was using the diary-nightly build). I close the issue for now. Hope that is fine.


Feature Request: Log to SDCard

is it possible to stream RX to a log file on the SDCard?

Unfortunately, there is no such possibility in the current implementation. Recently, I myself had such a need, I plan to implement it in the near future.

Hello, I'm in need of an uart logger for a recent project and a handheld like a flipper zero would come very handy. Is there any plans on this? Is there any alternative app?


Crossdart fails for plugins

Crossdart has no info for url_launcher:
https://pub.dartlang.org/packages/url_launcher + click 'source code'
Log file:
https://www.crossdart.info/p/url_launcher/0.1.1/log.txt

I don't think this blocks M2.  But I'm glad we noticed. :)

I think the fix for this is to:

get a Flutter SDK installed on the crossdart builder, and
set the environment variable FLUTTER_ROOT to the path of the Flutter SDK so that Pub/Dartdoc/etc. can locate the Flutter SDK.

A bit of experimentation to back this theory:
mit-macbookpro2:url-launcher mit$ dartdoc
Resolving dependencies...
Resolving dependencies...

The Flutter SDK is not available.
Depended on by:
- url_launcher
mit-macbookpro2:url-launcher mit$ export FLUTTER_ROOT=~/dev/github/flutter
mit-macbookpro2:url-launcher mit$ dartdoc
Resolving dependencies...
Got dependencies!
Generating documentation for 'url_launcher' into /Users/mit/tmp/plugins/packages/url-launcher/doc/api/

/cc @astashov

I tried that, now it complains:
$ pub get
Resolving dependencies...
Could not find package sky_engine at "/flutter/bin/cache/pkg/sky_engine".
Depended on by:
- flutter 0.0.22

I checked - there's no that sky_engine indeed. Where to get it?

Oh, sorry, I think we are missing a step: After the git clone, can you try to run flutter\bin\flutter precache?

Umm, it complains:
   Woah! You appear to be trying to run flutter as root.
   We strongly recommend running the flutter tool without superuser privileges.
  /
📎

I know, I know, but I really want to run it with root... Is there a way to workaround this?

Don't think that we currently support that; let me dig a bit and see if that can get changed!

@astashov  Why do you want to run as root?

I just run everything in a GCE startup script, which is root by default. Maybe not a best decision, but would require some effort to change that. Curious why it's so bad to run it under root?

@astashov do you think you will be able to change your script to not run as root?

@astashov maybe a solution like this would work (i.e., keep your current script, but call out to a second script that installs Flutter with a second non-root account)?

Also, note that we are seeing the exact same failure on dartdocs.org: https://github.com/flutter/flutter/issues/9796

@astashov did you have a chance to look at this?

No, not yet, sorry.

Would really like to see a resolution to this. Having 404s from plugin landing pages is not a good user experience. @astashov do you think you will get to this soon?

Don't have much time now, unfortunately. Actually, gonna try to look into it this night, will see what I could do there.

We can remove the root restriction if absolutely necessary (or at a temporary flag to override the check).  Running as root inside a VM isn't really that harmful.  But letting normal users accidentally run as root is just handing them a footgun.

@astashov we removed the root restriction, can you try the fix from three weeks ago again?

Oh really? And I'm trying to run it not under root like right now... :)

Yes, sorry about flip-flopping. Just merged it in https://github.com/flutter/flutter/commit/97f7ddf2915d725e25ac2f06901e1b4cc8bbc5d2.

@astashov Long term we want to put the restriction back, FWIW. But we wanted to unblock you.

@astashov is it working now with the root restriction removed? Or are you hitting new problems?

Hitting new problems - by some reason the script either ignores or doesn't see FLUTTER_ROOT. I'll continue investigating tonight.

Okay, I think it is fixed. I also think it'd work now even with the root restriction.

Excellent news, great to see this fixed. Thanks a lot!


html-color-code

Can you write me the html-codes of all colors you suported? thank you very much

Duplicate https://github.com/oznu/homebridge-config-ui-x/issues/228


Does anyone know how to get dynamic tree data from server?

1.Here is my html code snippet:

2.get dynamic data from server:
`var DataSourceTree = function (options) {
this.url = options.url;
}
DataSourceTree.prototype.data = function (options, callback) {
    var param = null

    if (!("name" in options) && !("type" in options)) {
        param = 0;//load the first level
    }
    else if ("type" in options && options.type == "folder") {
        if ("additionalParameters" in options && "children" in options.additionalParameters) {
            param = options.additionalParameters["id"];
        }
    }

    if (param != null) {
        $.ajax({
            url: this.url,
            data: 'id=' + param,
            type: 'POST',
            dataType: 'json',
            success: function (data) {
                    callback({ data:data })
            },
            error: function (response) {
            }
        })
    }
};
$('#tree1').ace_tree({
    dataSource: new DataSourceTree({url:"/menu/tree"}),
    multiSelect:false,
    loadingHTML:'

',
    'open-icon' : 'ace-icon tree-minus',
    'close-icon' : 'ace-icon tree-plus',
    'selectable' : true,
    'selected-icon' : 'ace-icon fa fa-check',
    'unselected-icon' : 'ace-icon fa fa-times'
});`

however,it didn't work! and I get an error  "Uncaught TypeError: this.options.dataSource is not a function". if anyone knows how to fix it, please tell me.Thank you!

dataSource is expected to be a function. I don't know what your constructor for DataSourceTree looks like because you didn't include it, but it likely is not returning a function and returning an object or maybe the implicit this. Find out what new DataSourceTree({url:"/menu/tree"}) returns and down that path lies your problem.


Cell populations in topTable() wrong

Hi,
first I want to thank you for this very useful package!
I am working with spatial experiment objects comprising IMC data and was struggling a bit to transform my SPE into a catalyst compatible SCE object. I managed by creating a new SCE object based on my count matrix, colData, clusters and reducedDims and adding experiment_info to the metadata slot. Using this newly created SCE, I worked through the CyTOF workflow and everything worked fine until the differential abundance section. For some reason, I obtain NA values for my p-values and the proportions returned by
topTable(da_res1, show_props = TRUE, format_vals = TRUE, digits = 2)

differ from the true proportions which I obtained by:
p <- plotAbundances(sce, k = "celltype", by = "cluster_id", shape_by = "sample_id")
p$data$Freq

Here is how I performed the DA testing:
ei <- metadata(sce)$experiment_info
design <- createDesignMatrix(ei, cols_design = "condition")
contrast <- createContrast(c(0,1))

da_res1 <- diffcyt(sce,
    design=design,
    contrast = contrast,
    analysis_type = "DA", method_DA = "diffcyt-DA-edgeR",
    clustering_to_use = "celltype",
     #min_cells=1, min_samples=1,
    verbose = T)

I initially thought that the reason for this might be that I only have very few cells for some samples per cluster and conditon, as I am comparing clusters within a metaclusters. However, setting min_cells and min_samples to a lower value did not fix the problem.
I am new to DA testing, but I compared the outputs using HDCytoData to my data and found no difference. I also sent you the generated SCE object per email.
Thanks so much already!

Really hard to tell without more information. Probably there is a difference in the proportions from plotAbundances and in topTable because a normalization is applied to the latter. I would advise to take the (cluster/celltype-sample) count table and run the DA analyses direct on that, but more or less following the steps of diffcyt does. At least, that way, you can troubleshoot all the intermediate steps.

Thank you for your quick reply!
I will try to provide more information. In the figure below, which I generated according to the cytof workflow, you can see the cluster proportions per sample for two conditions (i.e. timepoints), which correspond to the true proportions:

Same thing shown in boxplots:

It looks like there is a problem with the design or contrast matrix or with the experiment_info. Because everything is correct until I get to the DA testing:
ei <- metadata(sce)$experiment_info
design <- createDesignMatrix(ei, cols_design = "condition")
contrast <- createContrast(c(0,1))

da_res1 <- diffcyt(sce,
    design=design,
    contrast = contrast,
    analysis_type = "DA", method_DA = "diffcyt-DA-edgeR",
    clustering_to_use = "celltype",
    min_cells=1, min_samples=1,
    verbose = T)

rowData(da_res1$res)

This returns:

For some reason, the p value for clusters 7 to 13 is NA. And interestingly, the function topTable() return zero for the proportions of exactly those clusters across all samples, which, as can be seen in the figures above, is not correct.
topTable(da_res1, show_props = TRUE, format_vals = TRUE, digits = 2)

Maybe I am overseeing something obvious...
Hope this was informative enough. Thank you so much for your help!

Thanks for the extra info; quite a lot of variability there!
If it were me, I would want to step through the testDA_edgeR function and just double check that everything going in is ok .. design matrix, count table, etc. .. check the intermediate objects.
I'm going on vacation now for 2 weeks, but could check when I get back.

I now tested it with edgeR:
library(edgeR)

abundances <- table(metadata(sce)$cluster_codes$celltype, sce$sample_id)
abundances <- unclass(abundances)
extra.info <- colData(sce)[match(colnames(abundances), sce$sample_id),]
y.ab <- DGEList(abundances, samples=extra.info)

design <- model.matrix(~factor(condition), y.ab$samples)
y.ab <- estimateDisp(y.ab, design, trend="none")

fit.ab <- glmQLFit(y.ab, design, robust=TRUE, abundance.trend=FALSE)
res <- glmQLFTest(fit.ab, coef=ncol(design))

topTags(res)

And here, I get reasonable results:

So, it seems to be related to diffcyt or how I input my data to diffcyt. I guess I will just use edgeR directly.
Have a nice vacation!

The count per cellType is incorrect, which impacts the next calculations.
# From initial object
> table(sce$cluster_id)
 celltype_1 celltype_10 celltype_11 celltype_12 celltype_13  celltype_2  celltype_3
       8684         632         670         129        7292        3193        1765
 celltype_4  celltype_5  celltype_6  celltype_7  celltype_8  celltype_9
      19786        3071        1065        6426        2505        1188
# From diffcyt output
> rowSums(da_res1$d_counts@assays@data$counts)
 celltype_1 celltype_10 celltype_11 celltype_12 celltype_13  celltype_2  celltype_3
       9316           0           0           0           0         670       18154
 celltype_4  celltype_5  celltype_6  celltype_7  celltype_8  celltype_9
       7292       19786        1188           0           0           0

Found results similar to @LazDaria edgeR results when running code line by line but excluding the following line. I excluded it because I did not catch what it is for. Maybe very specific to the use of FlowSOM. Excluding it results in no zero count per celltype (table above) and ensures that code_id == cluster_id.


Interested in adding this to Contentfuls samples repo?

Hey @suhmantha1 ,
Nice shopify UI Extensions! If you are interested, you could send a PR to our official samples repo so this extensions will be more discoverable? The only ask I would have is to add a license file with something like MIT.
https://github.com/contentful/extensions/tree/master/samples
Thanks,
Frederik

@floelhoeffel Would love to see this extension more discoverable! Just submitted a PR to the repo


New Pricing Page Design - Implementation

We have redesigned the pricing page to align with our new sustainability model.

Featuring two main sections: "For Collectives" and "For Fiscal Hosts," as well as a FAQ module (@alanna, @piamancini, what content do we want there?)

For any copy change, comment here or add as a comment in Figma :)

See the design file 🎨 in figma
@znarf

I love how the colors and illustrations make it look much friendlier.
We've been through this before, but I still think we should consider whether we really want to put everything on one page, or whether it makes more sense to get users to pick the path they are interested in and only see the info relevant to them, because otherwise it's so much information and pretty confusing. You can imagine a person who doesn't understand our platform or the terminology getting really lost on this page. I personally liked the tabs on the old page, but I
One big issue I see is that it's missing self-hosted Collectives.
We have never really nailed a good way to communicate about them. We don't want to attach the complicated term "fiscal host" because we want the message to be as simple as "just connect your bank account". But actually where you have 3 categories of fiscal host (start, grow, scale) there's actually another one, "self", which is limited to a single Collective and can't charge host fees. Or you could think of the "Collectives" section as being divided into "Hosted Collectives" and "Self-Hosted Collectives" (but probably not those words), with the difference being to hold your own funds or apply to a Host to hold them for you.
Another issue: it says platform tips applies everywhere, but actually they are not turned on for OSC, which is the largest Host. So this might be confusing. I raised #3811 because I think we should bring OSC into line with the new model, to avoid exactly this kind of complexity when explaining pricing, but it's not resolved yet.
Besides that, I have a lot of tiny text changes to make... but I think it's actually easier if we just implement it and then I make a pull request with the text changes after (or while it's on staging), because it's too hard to work with Figma and a pain to pull all the text out into a document. I can work within the design and just make small text changes once it's implemented.

I love how the colors and illustrations make it look much friendlier.
We've been through this before, but I still think we should consider whether we really want to put everything on one page, or whether it makes more sense to get users to pick the path they are interested in and only see the info relevant to them, because otherwise it's so much information and pretty confusing. You can imagine a person who doesn't understand our platform or the terminology getting really lost on this page. I personally liked the tabs on the old page, but I
One big issue I see is that it's missing self-hosted Collectives.
We have never really nailed a good way to communicate about them. We don't want to attach the complicated term "fiscal host" because we want the message to be as simple as "just connect your bank account". But actually where you have 3 categories of fiscal host (start, grow, scale) there's actually another one, "self", which is limited to a single Collective and can't charge host fees. Or you could think of the "Collectives" section as being divided into "Hosted Collectives" and "Self-Hosted Collectives" (but probably not those words), with the difference being to hold your own funds or apply to a Host to hold them for you.
Another issue: it says platform tips applies everywhere, but actually they are not turned on for OSC, which is the largest Host. So this might be confusing. I raised #3811 because I think we should bring OSC into line with the new model, to avoid exactly this kind of complexity when explaining pricing, but it's not resolved yet.
Besides that, I have a lot of tiny text changes to make... but I think it's actually easier if we just implement it and then I make a pull request with the text changes after (or while it's on staging), because it's too hard to work with Figma and a pain to pull all the text out into a document. I can work within the design and just make small text changes once it's implemented.

Thinking about this a bit more: we should radically simplify it. We can put all the detail behind links to more detailed pages. That way we can avoid hitting people with a wall of too much detail that might not apply to them, while allowing them to dig deeper to find out what they need to know.
Here's a version....
Pricing
FREE For Collectives

Unlimited access to all features
Platform Tips enabled
No fees if you hold money in your own bank account
Fiscal Host fees may apply
Payment processor fees may apply

For Fiscal Hosts

Host unlimited Collectives and get access to all features
FREE if you don't charge Host fees
Platform Tips enabled
15% revenue share if you charge Host fees
If you manage >$150,000, we'll get in touch about an enterprise agreement

... and basically put everything else behind links to more detailed pages, or expandable details, or something, so when you look at the page you can quickly take it all in and figure out what applies to you.
Obviously there are a lot of terms used people might not understand, but we can have a detailed FAQ explaining Platform Tips, Fiscal Hosts, Host Fees, etc etc.
Note, this does not solve the issue of OSC not fitting in the new model, as mentioned above.

Thinking about this a bit more: we should radically simplify it. We can put all the detail behind links to more detailed pages. That way we can avoid hitting people with a wall of too much detail that might not apply to them, while allowing them to dig deeper to find out what they need to know.
Here's a version....
Pricing
FREE For Collectives

Unlimited access to all features
Platform Tips enabled
No fees if you hold money in your own bank account
Fiscal Host fees may apply
Payment processor fees may apply

For Fiscal Hosts

Host unlimited Collectives and get access to all features
FREE if you don't charge Host fees
Platform Tips enabled
15% revenue share if you charge Host fees
If you manage >$150,000, we'll get in touch about an enterprise agreement

... and basically put everything else behind links to more detailed pages, or expandable details, or something, so when you look at the page you can quickly take it all in and figure out what applies to you.
Obviously there are a lot of terms used people might not understand, but we can have a detailed FAQ explaining Platform Tips, Fiscal Hosts, Host Fees, etc etc.
Note, this does not solve the issue of OSC not fitting in the new model, as mentioned above.

Thanks @alanna - I think we can make some improvements but I don't want to delay having a functioning pricing page anymore. Let's see what can we fix:
I personally like the fact that all the information is there and you are not forced to click through separate things to see more stuff. But maybe we can do an initial page that has to options for Collectives and Fiscal Hosts and the right box shows up when you click on one of the options. That would solve the problem of seeing twice for example the platform tips box. @Memo-Es can we do an option like this please?
We could also remove the long paragraph after the title For Collectives. We should assume people read the homepage before landing there. That will clear the space a lot. I would leave the one under Fiscal Host because I think tit's worth clarifying the term.
To the self hosted collective comment: that is exactly wha the first box is about. A self hosted collective is just a collective and we say it at the beginning, it is free for collectives. You've (and we all have) inherited this idea of hosts, self hosted, etc. but a new collective is not thinking about that. It's just reading it's a collective. I think what triggered this was the fact that we added a comment about host fees there, because we need to communicate that but the phrasing needs to be improved. @Memo-Es I'll make a couple of suggestions in figma to remove wording.
On OSC I don't think we it's a problem right now. We want to experiment with platform tips but there are many hosts still on a plan that haven't activated platform tips either. It's an arrangement between host and platform. I think that adding the complexity here of making a message for OSC is not the right call.

Thanks @alanna - I think we can make some improvements but I don't want to delay having a functioning pricing page anymore. Let's see what can we fix:
I personally like the fact that all the information is there and you are not forced to click through separate things to see more stuff. But maybe we can do an initial page that has to options for Collectives and Fiscal Hosts and the right box shows up when you click on one of the options. That would solve the problem of seeing twice for example the platform tips box. @Memo-Es can we do an option like this please?
We could also remove the long paragraph after the title For Collectives. We should assume people read the homepage before landing there. That will clear the space a lot. I would leave the one under Fiscal Host because I think tit's worth clarifying the term.
To the self hosted collective comment: that is exactly wha the first box is about. A self hosted collective is just a collective and we say it at the beginning, it is free for collectives. You've (and we all have) inherited this idea of hosts, self hosted, etc. but a new collective is not thinking about that. It's just reading it's a collective. I think what triggered this was the fact that we added a comment about host fees there, because we need to communicate that but the phrasing needs to be improved. @Memo-Es I'll make a couple of suggestions in figma to remove wording.
On OSC I don't think we it's a problem right now. We want to experiment with platform tips but there are many hosts still on a plan that haven't activated platform tips either. It's an arrangement between host and platform. I think that adding the complexity here of making a message for OSC is not the right call.

Design update

GIF showing the page interactions
@alanna @piamancini

Design update

GIF showing the page interactions
@alanna @piamancini

@Memo-Es is the Valid for All Plans behind a button or do you see it for everyone? If the latter - I think it lacks some coherence. Plans is related to hosts so I wouldn't expect collectives to read it.
Maybe we display  Valid for All Plans + The Host Box under a Know More that brings it up and the info under Valid for All plans (with another title) in a know more under the Collective

@Memo-Es is the Valid for All Plans behind a button or do you see it for everyone? If the latter - I think it lacks some coherence. Plans is related to hosts so I wouldn't expect collectives to read it.
Maybe we display  Valid for All Plans + The Host Box under a Know More that brings it up and the info under Valid for All plans (with another title) in a know more under the Collective

Design update

GIF showing the page interactions
@alanna @piamancini

Design update

GIF showing the page interactions
@alanna @piamancini

great! thank you @Memo-Es We can go ahead and do mobile versions

great! thank you @Memo-Es We can go ahead and do mobile versions

Design update - Mobile versions

Desktop
Tablet Landscape
Tablet Portrait
Mobile

See the production-ready file in figma 🎨
@znarf  @piamancini @alanna

Design update - Mobile versions

Desktop
Tablet Landscape
Tablet Portrait
Mobile

See the production-ready file in figma 🎨
@znarf  @piamancini @alanna

Closing this as it's live in production https://opencollective.com/pricing


Can you tell me how can i add sign in this project

please explain

First you need to capture the new signs which you want to add, into the training and testing dataset, for that you need to run the TrainingDataCollection.py and TestingDataCollection.py files and insert the new signs which you want.
After you get the new signs, make changes in the Model.ipynb file and ad the logic for your signs.
And trying the model.
After the training is completed, make the changes to the Application.py file and add the new signs logics and then you would be able to run the project.


How to retrieve the results from js and how store those values in salesforce?

I wrote the small javascript code in visualforce page by using boomerang tool. It shows the result in same page. I want to store the result in sobject. can any one tell me how to store the data? here i am giving my sample code.
<apex:page >

Boomerang Exp

Boomerang Example:

my result is
This page took 21 ms to load
Other timers measured:
boomerang = 2 ms
boomr_fb = 16 ms
t_resp = 0 ms
t_page = 21 ms
Your latency to this server is 1±0.32ms
Other parameters:
rt.start = navigation
rt.bstart =<PHONE_NUMBER>553
rt.end =<PHONE_NUMBER>558
bw_time =<PHONE_NUMBER>
I want to stor eatleast one value, example page loading time.

Please make your changes against the main repository at https://github.com/lognormal/boomerang
This repository is obsolete.

Please make your changes against the main repository at https://github.com/lognormal/boomerang
This repository is obsolete.


How can I also download live video

Thx for the youtube video download module.
But as I tried, I can't download youtube live video.
like the sky news live (https://www.youtube.com/watch?v=y60wDzZt8yg)
Is any suggestion to do that?
Thx

@adwin5 what option have you tried?

@przemyslawpluta  Oops. I only tried "--format=18"
I should try other options.
Thx

As per above looks like avconv was probably built without https support, you have to compile ffmpeg with https support.


Remove unused and broken code

This code is not needed for our cause and breaks the build. Just remove it!

Interesting, it does configure and compile fine for me even with this code. But if it's unused anyway, let's delete it.


修改：docsify 引入方式及增加单图的 cdn 引入示例

Check List

[x] Every Commit message is meaningful
[x] Synchronized with the master branch
[x] CI passed
[x] Add suitable label

What Changed

edit: docsify and cdn example for single chart.

Breaking Change

[ ] Yes
[x] No

Document Update

[x] Yes
[ ] No


[cluster-test] exclude seed node val-0 from twin list

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@bors-libra r=andll

:pushpin: Commit 0b22421 has been approved by andll

:hourglass: Testing commit 0b224217bedb2e4ffa94e82f14588b3e418ae863 with merge 382b23e31e184a38243b0b5e3d6e7220f75534e1...

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


Broken links on website in README output

Go to https://docs.opentitan.org/ -- click the README link on the left side.
Issues;

Broken OpenTitan logo
CONTRIBUTING link in the page goes to non-existent https://docs.opentitan.org/README/CONTRIBUTING.md
LICENSE link in the page goes to https://docs.opentitan.org/README/LICENSE

The CONTRIBUTING page on the left side has similar issues.
It is unclear to me if the README / CONTRIBUTING files were actually meant to be included in the output or not?

Thanks for reporting this (somehow this issue got lost).
The logo issue has been addressed by now, but the links still seem broken.
I will create PR shortly to fix this.


Add support for custom envFrom secretRef's and configMapRef's

Hi,
Would it be possible to add custom envFrom support in the future?
Background, I am running rook-ceph (operator for running distributed storage ceph).
It has a ObjectBucketClaim that can create s3 buckets. The OBC in turn creates a ConfigMap and a Secret that contains following keys BUCKET_REGION, BUCKET_HOST, BUCKET_PORT, BUCKET_NAME, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. In order for me to use these with this helm chart I need to first apply the OBC. Then open the configmap and secret and copy the values from the keys and insert them for this helm chart values and then install the helm chart. Makes it impossible for me to automate.
If you could make it so I can add additional envFrom[].secretRef and envFrom[].configMapRef into the values that are applied to the pod container specs. Then I could easily use the above mentioned auto-generated keys as values like so:
secrets.s3.accessKey=$(AWS_ACCESS_KEY_ID)
secrets.s3.secretKey=$(AWS_SECRET_ACCESS_KEY)
s3.region=$(BUCKET_REGION)
s3.regionEndpoint=$(BUCKET_HOST)
s3.bucket=$(BUCKET_NAME)

Thanks!

It was added after you created the issue (https://github.com/twuni/docker-registry.helm/pull/35) and a new release hasn't been released (yet).

@canterberry can you push v1.14.0 to the helm repo so I can test pr #35?

For some reason the variable interpolation is not working for some reason, in normal cases it should work like this:
$ cat pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: busybox
spec:
  containers:
  - name: busybox
    image: busybox:latest
    env:
    - name: HOSTNAME
      valueFrom:
        fieldRef:
          fieldPath: metadata.name # or "status.hostIP" or "spec.nodeName" etc
    - name: INTERPOLATION
      value: abc-$(HOSTNAME)
    command: ['sh', '-c', 'sleep 3600']
  restartPolicy: Never
$ kubectl apply -f pod.yaml
pod/busybox created

$ kubectl exec -it busybox -- sh -c 'echo $INTERPOLATION'
abc-busybox
$ kubectl delete pod busybox
pod "busybox" deleted

For the registry pods it simply looks like this
$ kubectl exec -it registry-c46cf8b8c-6m54d -- sh -c 'echo $REGISTRY_STORAGE_S3_SECRETKEY'
$(AWS_SECRET_ACCESS_KEY)

I expected the output to be my actual s3 secret key.
Any idea on what is wrong?

So the S3 integration should definitely support other S3 provider than AWS. I'm having issues with Minio:
2b6b3509ddbc: Pushing [==================================================>]  44.08MB 791274611ac9: Layer already exists  dc365698f1f2: Layer already exists  636159d907db: Pushing [==================================================>]  8.871MB 485115e86f04: Layer already exists  30f3545290f2: Retrying in 5 seconds  7fcd2600f5ad: Pushing [=======================>                           ]  8.582MB/18.47MB 8f56c3340629: Pushing [====================>                              ]    216MB/528.4MB ba6e5ff31f23: Pushing [============================================>      ]  135.3MB/151.9MB 9f9f651e9303: Waiting  0b3c02b5d746: Waiting  62a747bf1719: Waiting  received unexpected HTTP status: 500 Internal Server Error

Using other S3 than AWS works. The part that doesn't work for me is to reuse the already existing secret keys I got.

I got it running with Minio, but layers are partly failing with:
2b6b3509ddbc: Pushing [==================================================>]  44.08MB
791274611ac9: Pushed
dc365698f1f2: Pushed
636159d907db: Pushing [==================================================>]  8.871MB
485115e86f04: Pushed
30f3545290f2: Pushing [==================================================>]  56.94MB
7fcd2600f5ad: Pushing [==================================================>]  19.04MB
8f56c3340629: Pushing [====================================>              ]  388.9MB/528.4MB
ba6e5ff31f23: Pushing [====================>                              ]  63.28MB/151.9MB
9f9f651e9303: Retrying in 11 seconds
0b3c02b5d746: Retrying in 5 seconds
62a747bf1719: Waiting
received unexpected HTTP status: 500 Internal Server Error

@darox I expect that to be an separate issue, what does it have to do with adding support for custom envFrom that are interpolated?

Closing this issue as the extraEnvVars was implemented and there has been no new activity in quite some time.


bunch of typos

For channel binding token, the powershell command is extended protection token check...yours says extend, no ED on the end...also it doesn't say None.

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

ID: cae6d9d8-4a22-f41e-a43f-b88816ae4519
Version Independent ID: aad0e220-49d9-b9bc-10b7-ea0155af1d96
Content: AD FS Troubleshooting - Integrated Windows Authentication
Content Source: WindowsServerDocs/identity/ad-fs/troubleshooting/ad-fs-tshoot-iwa.md
Product: windows-server
Technology: ad-fs
GitHub Login: @billmath
Microsoft Alias: billmath

Thanks again for contacting Microsoft. We've submitted a documentation change based on your suggestion. Changes will be live after the next business day. This issue has been resolved and we are closing the issue. #please-close

#assign:xelu86


fixes #6149 + removing deprecated variable variables in general

remove deprecated variable variables / string interpolation in variable names

I'm not sure the change to system/libraries/Xmlrpc.php is necessary as this was previously a literal string, so no variable interpolation would have taken place anyway? :/

Yes, for sure that was a string interpolation bug in Xmlrpc.php.
Thanks for this PR!


Start HTTP/GRPC/Cron servers on demand

Only start the server if at least one handler is provided.

Not easy to do in the current abstraction.


Cannot process windows ar files

The htmlhelp.lib AR file included in http://download.microsoft.com/download/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/helpdocs.zip
(from https://msdn.microsoft.com/en-us/library/windows/desktop/ms669985(v=vs.85).aspx )
fails to extract (note that it also contains symbol table most likely)
>>> import arpy
>>> ar = arpy.Archive('x/htmlhelp.lib')
>>> ar.read_all_headers()
Traceback (most recent call last):
  File "/tmp/tk/lib/python3.6/site-packages/arpy.py", line 106, in __init__
    self.uid = int(uid)
ValueError: invalid literal for int() with base 10: b'      '

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/tmp/tk/lib/python3.6/site-packages/arpy.py", line 342, in read_all_headers
    while self.read_next_header() is not None:
  File "/tmp/tk/lib/python3.6/site-packages/arpy.py", line 320, in read_next_header
    header = self.__read_file_header(self.next_header_offset)
  File "/tmp/tk/lib/python3.6/site-packages/arpy.py", line 243, in __read_file_header
    file_header = ArchiveFileHeader(header, offset)
  File "/tmp/tk/lib/python3.6/site-packages/arpy.py", line 112, in __init__
    "cannot convert file header fields to integers", err)
arpy.ArchiveFormatError: ('cannot convert file header fields to integers', ValueError("invalid literal for int() with base 10: b'
  '",))

Hmm... I'm not sure what that file even is. My system's ar is not able to list the contents.
I'll investigate some more.

@pombredanne Did you want to read something specific from that file? I can certainly mark this header as "weird windowsy thing" and skip it. At least I don't crash in that case :) If you know where to find more info, I could maybe do something more creative...

Ok, I see what's happening. Windows doesn't do things like uid and gid, so they will need to be None.
PR incoming.

@pombredanne let me know if the linked PR solves the issues for you.

@viraptor that was quick! let me test that ASAP
FWIW I keep a bunch of ar test files there https://github.com/nexB/scancode-toolkit/tree/develop/tests/extractcode/data/archive/ar
there https://github.com/nexB/scancode-toolkit/tree/develop/tests/extractcode/data/archive/weird_names and there https://github.com/nexB/scancode-toolkit/tree/develop/tests/extractcode/data/archive/ar/winlib

It works for that archive but I am not 100% sure this is correct as windows ar lib may contain more than one entry with the same name and you track these in a dict keys by path so there cannot be more than one file at the same path in your model... is this true? I think it is per https://github.com/viraptor/arpy/blob/1437531491916873e06083a973952284cb737fd1/arpy.py#L207
Also these archives are not processed OK:

https://github.com/nexB/scancode-toolkit/blob/develop/tests/extractcode/data/archive/ar/winlib/freetype.lib

https://github.com/nexB/scancode-toolkit/blob/develop/tests/extractcode/data/archive/weird_names/weird_names.ar

https://github.com/nexB/scancode-toolkit/blob/develop/tests/extractcode/data/archive/ar/winlib/gsdll32.lib seems fine but there are more than one file entries there.

The files dict is there for convenience, but if you have special cases, you can handle them directly:
ar = arpy.Archive...
ar.read_all_headers()
for header in ar.headers:
  if header.type in (arpy.HEADER_BSD, arpy.HEADER_NORMAL, arpy.HEADER_GNU):
    filename = header.name
    content = arpy.ArchiveFileData(ar_obj: ar, header: header)

it works with repeated file names too. I guess it's not an amazing interface though. Any suggestions that don't break the current interface?

Thanks!
And you wrote:

I guess it's not an amazing interface though. Any suggestions that don't break the current interface?

My suggestion would be to let the existing API as-is and craft a new class that would use the same API as the standard lib zipfile/tarfile e.g. hide the use of read_all_headers() and does the right thing by default handling all header types.

Vaguely related you may be interested to peek into that lesser-known and now-abandoned ar implementation used in Chromium, possibly for its tests?
https://chromium.googlesource.com/infra/luci/luci-py/+/650536bb4b4c8b1a6ecd58deb80df8be200fc19d/client/libs/arfile/

Hmmm... how I wonder if I can register myself to the zipfile interface and just let it handle most things.
But even if I can't, I could certainly reuse the idea dual access via name or info.

Oops, I read it as zipfile supporting multiple formats, but actually it just supports multiple compressions in zip. I'll have to reuse the idea rather than the interface.

I'll have to reuse the idea rather than the interface.

Yes this is what I meant: having a similar and familiar API, not reusing the code itself

Added in https://github.com/viraptor/arpy/pull/11


Fix: ConnectApi incorrect default initialization

Resolves #70

@InbarGazit could we add the hacktoberfest-accepted label to this PR so it counts towards my hacktoberfest submissions?


[vm] Create entry point for MoveVM

Motivation
This is the follow up cleanup for #1946. The goal here is to have a clear separation between Move, the language runtime and the Libra transaction logic. This PR will create an entry point for wrapping the logic for the Move language runtime.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
cargo test
Related PRs
#1946

this looks good to me and something we can work and iterate over. Please see @sblackshear comments.
Thanks!

@bors-libra r=dariorussi

:pushpin: Commit 1394670 has been approved by dariorussi

:hourglass: Testing commit 1394670c2600e05c30aeb57946427effdc95479b with merge 82bad928372410b1e9ea3cf46ed5f1f20160d2db...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: dariorussi
Pushing 82bad928372410b1e9ea3cf46ed5f1f20160d2db to master...


ARCH-1916 - Commit designed to test refactored build

Summary of PR changes
This PR is for testing the new workflow.  It will be closed once the build and review PR workflow runs.

Done with testing


How to keep my custom resolver codes instead overwrite when regenerate?

For example: I wrote custom subscription method in a UserCrudResolver.

Custom methods only in custom resolvers in a separate files. Typegraphql merges all the resolvers, so no need to add something to the generated one.

Custom methods only in custom resolvers in a separate files. Typegraphql merges all the resolvers, so no need to add something to the generated one.

Next time please ask on gitter - GitHub issues is not a helpdesk, it's for bug reports and feature requests.

Next time please ask on gitter - GitHub issues is not a helpdesk, it's for bug reports and feature requests.


Conversion of about 1100 expoted notes failed

en2md failed a few seconds after being run with following error message ..
FATAL ERROR: CALL_AND_RETRY_0 Allocation failed - process out of memory
Abort trap: 6
Is there a work-around to this .. perhaps having en2md serially process the .enex file instead of attempting to load it all in one go ?
Thanks

I cut back down to about 101 records, and no errors were thrown, but en2md failed to convert any records .. well, it created one xml record .. I gave up .. and tried something else .. evernote-markdown, which required an API key but did convert the the evernote notes to markdown ..
en2md sounds like a great concept .. hope you have not given up on it .. thanks


using vendorCargoDeps leads to permission errors when building sqlite-sys

After upgrading crane:
-    crane.url = "github:ipetkov/crane?rev=98894bb39b03bfb379c5e10523cd61160e1ac782"; # https://github.com/ipetkov/crane/releases/tag/v0.11.0
+    crane.url = "github:ipetkov/crane?ref=master&ref=953b70da2813fb882c39890f2514e7db76fc8843";

and with some minor changes that are probably(?) unrelated cross-compiling sqlite is failing with:
client-pkgs-aarch64-android>    Compiling pin-project v1.0.12
client-pkgs-aarch64-android> error: failed to run custom build command for `libsqlite3-sys v0.24.2`
client-pkgs-aarch64-android> Caused by:
client-pkgs-aarch64-android>   process didn't exit successfully: `/build/source/target/release/build/libsqlite3-sys-0323aa547c5cd008/build-script-build` (exit status: 101)
client-pkgs-aarch64-android>   --- stderr
client-pkgs-aarch64-android>   thread 'main' panicked at 'Could not copy bindings to output directory: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', /nix/store/nmzj27xi1xb0w2jj28gxl7410l32a9z2-vendor-cargo
-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/libsqlite3-sys-0.24.2/build.rs:102:18
client-pkgs-aarch64-android>   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
client-pkgs-aarch64-android> warning: build failed, waiting for other jobs to finish...
error: builder for '/nix/store/dcv5s7av22jmjkgxxj7cn8pzcvcavs92-client-pkgs-aarch64-android-0.0.1.drv' failed with exit code 101;
       last 10 log lines:
       >    Compiling tracing v0.1.37
       >    Compiling pin-project v1.0.12
       > error: failed to run custom build command for `libsqlite3-sys v0.24.2`
       >
       > Caused by:
       >   process didn't exit successfully: `/build/source/target/release/build/libsqlite3-sys-0323aa547c5cd008/build-script-build` (exit status: 101)
       >   --- stderr
       >   thread 'main' panicked at 'Could not copy bindings to output directory: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', /nix/store/nmzj27xi1xb0w2jj28gxl7410l32a9z2-vendor-cargo-deps/c19b7c6f923b58
0ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0/libsqlite3-sys-0.24.2/build.rs:102:18

The corresponding line in the build script: https://github.com/rusqlite/rusqlite/blob/9880cdef12c1b624e351ed077dd71a2f77978f77/libsqlite3-sys/build.rs#L101

I bet it's https://github.com/ipetkov/crane/commit/18ef99b1e0e033f2f9f09798642e146be81afb80# but I don't see how.

@dpc Could you please provide a reproduction of the failure?
I use libsqlite3-sys in a few of my personal projects but I wasn't able to reproduce the issue there

Oh dear. :D
Now that you mention it one difference might be that this is a cross-compilation to aarch64-linux-android, but I don't know how this could make it different.

If it is of any help, here is the PR to our project that triggers it: https://github.com/fedimint/fedimint/pull/1720

Cross compilation can get quite hairy, but I can try to take a quick look...
@dpc what nix build .#??? invocation do I need to trigger the issue?

@ipetkov nix build -L .#cross.aarch64-android.client-pkgs

Fails to build with nix build -L github:dpc/fedimint/crane-rebuilds-fix#cross.aarch64-android.client-pkgs --accept-flake-config --override-input crane github:ipetkov/crane/v0.11.0
I also tried all other v.0.11.x and even some older versions for good measure, but it still fails to build, so I can't tell if this is a recent crane regression.

--override-input crane github:ipetkov/crane/v0.11.0 will not work as some things about src etc. handling had changed. But our master branch uses v0.11.0 and it works.

Building with the latest commit on the master branch seems to work fine with v0.11.3
nix build -L github:fedimint/fedimint/4c914914ca46cf02dea501735fe41cc026ef6d49#cross.aarch64-android.client-pkgs --accept-flake-config --override-input crane github:ipetkov/crane/v0.11.3

I don't understand how and why, but that command does work for me, but when I run nix build -L .#cross.aarch64-android.client-pkgs it fails, and it also does in our CI: https://github.com/fedimint/fedimint/actions/runs/4228754507/jobs/7344488178
If you look at this PR (I just rebased it, but it didn't change anything): https://github.com/fedimint/fedimint/pull/1720/files I'm setting crane input to crane.url = "github:ipetkov/crane?ref=master&ref=953b70da2813fb882c39890f2514e7db76fc8843"; which seems like exactly same commit as v0.11.3 is.
:confused:
Will investigate more later.

Oh. You're testing master of fedimint with v0.11.3 ... Hmmm... Will check it later.

OK, so the root of the problem is removing src = ./.; and adding cargoVendorDir = craneLib.vendorCargoDeps { src = ./.; }; instead in the buildDepsOnly call. I remove src because now it complains about that buildDepsOnly will ignore srcwhendummySrc is specified, but after removing src it complains that:
error: unable to find `src` attribute. consider one of the following:
       - set `cargoVendorDir = vendorCargoDeps { cargoLock = ./some/path/to/Cargo.lock; }`
       - set `cargoVendorDir = vendorCargoDeps { src = ./src/containing/cargo/lock/file; }`
       - set `cargoVendorDir = null` to skip vendoring altogether
(use '--show-trace' to show detailed location information)

so I have to add that cargoVendorDir = craneLib.vendorCargoDeps { src = ./.; }; and then compilation fails somehow.
@ipetkov

BTW. set cargoVendorDir = vendorCargoDeps { cargoLock = ./some/path/to/Cargo.lock; } does not seem to be correct as it doesn't work as specified, neither if I try to use cargLock = (builtins.readFile Cargo.lock) (complains about string context then).

I have also confirmed that the problem is there with v0.11.0, so it seems entirely about the usage of vendorCargoDeps.

@dpc

Yes vendorCargoDir needs a src attribute so you will need to explicitly set cargoVendorDir if you are going to be setting dummySrc instead of src
I don't know what that permissions issue is, but I'll need a minimal repro I can run and look at (there's been lots of debugging in this thread already so maybe a clean slate would be useful)

@ipetkov OK. I think I've figured out the root cause.
First, I've noticed that when I use cargoVendorDir, I get the dependencies being rebuilt again. That is what is causing the permission issue as the file in question is there:
[-r--r--r-- nixbld   nixbld  ]  bindgen.rs

and doesn't have a w.
So the problem is not the permissions, but the fact that ./target/ is there, yet everything is being rebuilt from scratch.
Initially I suspected some timestamps, but that didn't seem like the case.
Turns out the vedored config.toml that is being appended is different:
> diff -u /nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/config.toml /nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/config.toml
--- /nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/config.toml   1969-12-31 16:00:01.000000000 -0800
+++ /nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/config.toml   1969-12-31 16:00:01.000000000 -0800
@@ -1,17 +1,17 @@
 [source.nix-sources-c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0]
-directory = "/nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0"
+directory = "/nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0"
 [source.crates-io]
 registry = "https://github.com/rust-lang/crates.io-index"
 replace-with = "nix-sources-c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0"

 [source.nix-sources-49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad]
-directory = "/nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad"
+directory = "/nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad"
 [source.nix-sources-7b3ec600ad985a32a8367f459b9daa32421b08cf3f641c9eeed5b27bb8fe7916]
-directory = "/nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/7b3ec600ad985a32a8367f459b9daa32421b08cf3f641c9eeed5b27bb8fe7916"
+directory = "/nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/7b3ec600ad985a32a8367f459b9daa32421b08cf3f641c9eeed5b27bb8fe7916"
 [source.nix-sources-a68b9b47e08aa92cbe800ee65f8835d0ff8dc152cc7557a9e5dcbcffd188485d]
-directory = "/nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/a68b9b47e08aa92cbe800ee65f8835d0ff8dc152cc7557a9e5dcbcffd188485d"
+directory = "/nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/a68b9b47e08aa92cbe800ee65f8835d0ff8dc152cc7557a9e5dcbcffd188485d"
 [source.nix-sources-c6ac1166e8d5fb3cca134f5488fbc0796e323e56dab7b0dc4a84ae8cb361cdc3]
-directory = "/nix/store/nvhhxpvphziaibzdgwbxa9k17hspp799-vendor-cargo-deps/c6ac1166e8d5fb3cca134f5488fbc0796e323e56dab7b0dc4a84ae8cb361cdc3"
+directory = "/nix/store/xjp9wg7zqzcii8i29shwsijrb1fh3jd7-vendor-cargo-deps/c6ac1166e8d5fb3cca134f5488fbc0796e323e56dab7b0dc4a84ae8cb361cdc3"
 [source."https://github.com/dpc/rust-secp256k1-zkp/?branch=sanket-pr"]
 replace-with = "nix-sources-7b3ec600ad985a32a8367f459b9daa32421b08cf3f641c9eeed5b27bb8fe7916"
 git = "https://github.com/dpc/rust-secp256k1-zkp/"

As you can see the content is roughly the same, but the exact paths where the vendored dependencies are located are different, which (I think) is causing cargo to think that config.toml is different, so the whole project requires a rebuild. Which causes the sqlite-sys to hit a problem overwriting it's own out file (I'll report it to them, it seems that might cause issues).
I don't know why content of that confit.toml is different, but I bet it will be obvious to you.

In addition the fact that this bindgen.rs has lost w seems also caused by crane. The original file is in called bindgen_bundled_version.rs and has w set both in git, and in the extracted crate directory , but in the /nix/store it lost it:
> ls -alh /nix/store/9hk4985cliilyq8ly4dzydyl9r2aa5rz-cargo-package-libsqlite3-sys-0.24.2/sqlite3/bindgen_bundled_version.rs
-r--r--r-- 3 root root 182K Dec 31  1969 /nix/store/9hk4985cliilyq8ly4dzydyl9r2aa5rz-cargo-package-libsqlite3-sys-0.24.2/sqlite3/bindgen_bundled_version.rs

It would probably be safest for crane to preserve it.

I don't know why content of that confit.toml is different, but I bet it will be obvious to you.

vendorCargoDeps will look at the top level Cargo.lock of the provided source, along with any .cargo/config.toml files which can be found anywhere in the provided source tree. If you are providing a different source than was used before, then the hashes will change if there is a difference (e.g. an extra .cargo/config.toml file was added or removed). I'd probably need to see the code calling vendorCargoDeps before and after the change which led to the rebuild

In addition the fact that this bindgen.rs has lost w seems also caused by crane (or ... nix, I guess?).
Crates are vendored in /nix/store which is always read-only, there isn't anything we can "preserve" there.

Build scripts must not change any source files and only make changes to the $OUT_DIR only. The next question is why did the build suddenly start trying to modify source files where it didn't before (maybe a feature flag also changed indirectly enabling a build script path which didn't run before)

If you are providing a different source than was used before, then the hashes will change if there is a difference

I'm uncommenting these 3 lines, and commenting out the one right after:
https://github.com/fedimint/fedimint/blob/51f76884a3d0ec73b5b51a1b94af781ae38b06e5/flake.nix#L336

Build scripts must not change any source files and only make changes to the $OUT_DIR only. The next question is why did the build suddenly start trying to modify source files where it didn't before (maybe a feature flag also changed indirectly enabling a build script path which didn't run before)

Yes. But the build script is trying to overwrite a file that is already there as it's running again (it put this file there in the previous run), and now the file is ro because vendoring in /nix/store turned it into ro.

@dpc here's what I noticed:
Setting the following will break running nix build -L .#cross.aarch64-linux-android.client-pkgs
        commonArgsDepsOnly = commonArgsBase // {
          cargoVendorDir = craneLib.vendorCargoDeps {
            src = filterWorkspaceFiles ./.;
          };
          src = null;
          # other args
      };

BUT also setting the following fixes it again:
        commonArgs = commonArgsBase // {
          src = filterWorkspaceFiles ./.;
          cargoVendorDir = craneLib.vendorCargoDeps {
            src = filterWorkspaceFiles ./.;
          };
        };

Clearly there is a difference between the explicit vendorCargoDeps { src = filterWorkspaceFiles ./.; } call and the default vendoring that crane will apply with the provided args (which is what you noticed above given that the hashes changed). My hunch is that maybe it has something to do with the differences between filterWorkspaceFiles and filterModules
As to why this difference manifests in a build script failure I have absolutely no idea. I'd guess that if somehow the different filters are adding/omitting either a .cargo/config.toml or a Cargo.toml which somehow leads to changing the build behavior (e.g. either by changing what feature flags are used or how the dependencies are rebuilt).
If you do manage to come up with a really small reproduction (both in terms of Nix configs and cargo dependencies) I'd love to see it! But until then, I've reached my limits in being able to debug your project given my lack of familiarity and its complexity.
Hope this is useful!

Clearly there is a difference between the explicit vendorCargoDeps { src = filterWorkspaceFiles ./.; } call and the default vendoring that crane will apply with the provided args (which is what you noticed above given that the hashes changed). My hunch is that maybe it has something to do with the differences between filterWorkspaceFiles and filterModules

Well, the easy way to test it is to do:
          cargoVendorDir = craneLib.vendorCargoDeps {
            src = ./.;
          };

(no filtering). And that also fails, all the same. So filtering is not an issue. I assume craneLib.vendorCargoDeps should do whatever filtering it needs.
It seems to me that the difference is between my flake.nix calling craneLib.vendorCargoDeps directly vs crane calling it internally somehow. Isn't that kind of exactly the same issue that was causing https://github.com/ipetkov/crane/issues/242#issuecomment-1436108762 ? Then it was mkDummySrc if IIRC, here is some vendoring.

As to why this difference manifests in a build script failure I have absolutely no idea.

I've described it couple of times, and I think it's important you understand:
cargo build detecting that config.toml change seems to re re-run the whole build from the start while keeping the ./target extracted from deps-only build in place.
The build script of libsqlite3-sys does effectively:
fs::copy(somefile_rs_file_from_src,$out/bingen.rs);

In normal (non nix build ... run) $out/bingen.rs is RW:
> ls -alh (find . -name bindgen.rs)
-rw-r--r-- 1 dpc dpc 182K Feb 24 21:16 ./target/debug/build/libsqlite3-sys-350e0779e242deef/out/bindgen.rs

so overwriting it is not a problem, so the build script doesn't bother detecting if it exists, or deleting it.
But in nix build target/.../out/bindgen.rs is RO as the vendored source code lost the u+w and fs::copy seems to copy the permissions into ./target directory. So the overwriting fails.
I don't know if it's necessary for crane to preserve permissions on the vendored source code files, but it is a difference from the original behavior that might trip build script in certain scenarios (maybe?).

But in nix build target/.../out/bindgen.rs is RO as the vendored source code lost the u+w and fs::copy seems to copy the permissions into ./target directory.

Hmmm... just occurred to me that https://github.com/ipetkov/crane/commit/18ef99b1e0e033f2f9f09798642e146be81afb80#diff-119bd89c89c2f9eb9fa8a9c1f9a1e98fb14f0d473bfe1d1061122fbb8053c178R42
is doing chmod -R u+w ./target ... so why did I see:
[-r--r--r-- nixbld   nixbld  ]  bindgen.rs

when running recursive tree in a preBuild(?) hook? That does not seem to compute.

Alright, I found the issue: you are mixing artifacts from two different
toolchains which causes cargo to rebuild everything. Still no clue why the
libsqlite3-sys permission issue crops up but let's ignore that as a red herring
for now.

First apply this change to flake.nix:
        commonArgsDepsOnly = commonArgsBase // {
          cargoVendorDir = craneLib.vendorCargoDeps {
            src = filterWorkspaceFiles ./.;
          };
          src = null;
          # other args
      };

Then we check the vendored dependencies derivation this will create:
nix show-derivation --accept-flake-config .#cross.aarch64-linux-android.client-pkgs | jq 'to_entries[].value.env.cargoVendorDir'
# "/nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps"

Next we apply the second change to flake.nix (which "fixes" the build):
        commonArgs = commonArgsBase // {
          src = filterWorkspaceFiles ./.;
          cargoVendorDir = craneLib.vendorCargoDeps {
            src = filterWorkspaceFiles ./.;
          };
        };

Then we check the vendored dependencies derivation this will create:
nix show-derivation --accept-flake-config .#cross.aarch64-linux-android.client-pkgs | jq 'to_entries[].value.env.cargoVendorDir'
# "/nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps"

They are different! Let's compare their differences:
diff -r /nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps /nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps

2c2
< directory = "/nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0"
---
> directory = "/nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps/c19b7c6f923b580ac259164a89f2577984ad5ab09ee9d583b888f934adbbe8d0"
8c8
< directory = "/nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps/49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad"
---
> directory = "/nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps/49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad"
10c10
< directory = "/nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps/7b3ec600ad985a32a8367f459b9daa32421b08cf3f641c9eeed5b27bb8fe7916"
---
> directory = "/nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps/7b3ec600ad985a32a8367f459b9daa32421b08cf3f641c9eeed5b27bb8fe7916"
12c12
< directory = "/nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps/a68b9b47e08aa92cbe800ee65f8835d0ff8dc152cc7557a9e5dcbcffd188485d"
---
> directory = "/nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps/a68b9b47e08aa92cbe800ee65f8835d0ff8dc152cc7557a9e5dcbcffd188485d"
14c14
< directory = "/nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps/c6ac1166e8d5fb3cca134f5488fbc0796e323e56dab7b0dc4a84ae8cb361cdc3"
---
> directory = "/nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps/c6ac1166e8d5fb3cca134f5488fbc0796e323e56dab7b0dc4a84ae8cb361cdc3"

We can see that the vendoring is generating the same contents, except just
pointing to different store hashes (which happen to have the same contents).
config.toml differs because it refers to those different hashes.
Let's compare one of those vendored directories in more detail:
diff -u \
<(nix show-derivation $(readlink /nix/store/cy6498gn79brjz1mmpjp208q10kkk6v0-vendor-cargo-deps/49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad)) \
<(nix show-derivation $(readlink /nix/store/vwgxblsq4z9c6hf0yaw7y53rfx4ykslb-vendor-cargo-deps/49a40141ec3504d7802b09cb1cadde46c2ab4d5c45cc1a77317d06cea31d69ad))

The interesting thing this shows us is that the cargo-git derivation is
different. Let's look closer:
diff -u \
<(nix show-derivation /nix/store/h735ia59r947c75nca9hvdy74sh0gd0m-cargo-git) \
<(nix show-derivation /nix/store/y1xfjb5nqz1kv1r2jg51n9w50zz35dqy-cargo-git)

Finally we see that one derivation depends on
/nix/store/2f9aqnssah73fypfz59j7hr6wg6lx2py-rust-mixed.drv while the other
depends on
/nix/store/vyij3bkvpw4s5n2z3rpzncgq4imd9f6i-rust-stable-with-components-2023-01-26.drv.

This highlights that the buildDepsOnly derivation is probably being built with
one toolchain while the actual buildPackage derivation is built with another
(I see the flake contains craneLib and craneLibCross).
Caching will never properly function if toolchains are mixed, so it's something for
you to fix @dpc

As to why vendoring with two different toolchains leads to different hashes
(with the same results): this is because vendoring git deps requires some
processing of Cargo.toml files. This is implemented by the crane-utils
package, which also uses the current toolchain to be built. Perhaps
crane-utils should be built with a fixed toolchain just to avoid confusion as
to why they are different, but this is an independent thing to investigate.

Alright, I found the issue: you are mixing artifacts from two different
toolchains which causes cargo to rebuild everything.

Oh wow. I get it now. Thank you!

Perhaps
crane-utils should be built with a fixed toolchain just to avoid confusion as
to why they are different, but this is an independent thing to investigate.

Looked into this, although it is possible to build crane-utils with a fixed toolchain, we still need to pull in cargo when vendoring git deps (cargo needs to tell us what crates are part of the workspace so we don't blindly vendor the wrong thing and cause other problems), meaning there isn't a way that we can make vendoring-git-deps not rely on the current toolchain...
I'll document this limitation for the time being, thanks for reporting this!

I fixed our flake.nix after all, it just requires parametrizing bunch of stuff over craneLib to use.
Closing and thanks for help!


Worldview caching name problems

I was having a problem opening worldview zip files that were not named with a particular naming format.
This was causing a problem during data caching.
Changed worldview.py to query the zip file for a *.tif, and use that to extract the meta data about the sensor and collection date.

Updated the branch.  Removed the check and made it an assert, will fail if
the extension doesn't contain ".zip". This may be bad if we let people name
zip files without a .zip extension.
Also restored executable permission to model2config.
On Tue, Aug 18, 2020 at 11:38 PM Brian Coltin<EMAIL_ADDRESS>wrote:

@bcoltin requested changes on this pull request.
I also think you didn't mean to make scripts/model2config non-executable.
In delta/imagery/sources/worldview.py
https://github.com/nasa/delta/pull/23#discussion_r472550241:

@@ -101,10 +102,21 @@ def _prep(self, paths):
TODO: Apply TOA conversion!
"""
assert isinstance(paths, str)

   parts = os.path.basename(paths).split('_')

   (_, ext) = os.path.splitext(paths)

   if ext == '.zip':

Will this work with non-zip files? when we call unpack later I thought we
assumed it was a zip. (not sure this check is needed)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nasa/delta/pull/23#pullrequestreview-469898413, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALSQ7HAXLWBCVWB53XZEGDSBMGGHANCNFSM4QEH4YXQ
.


Can not use struct in enum variant

The following will result in an error:
pub enum T(a, b) =
| T(struct(List(a), b))

error: Syntax error
- </home/nmelzer/projects/tlob/src/tlob/combi.gleam>:2:5
  |
2 | | F(fn (List(sym)) -> List(struct(List(sym), tree)))
  |     ^^ Unexpected token
  |

struct is a new feature that only exists on the master branch. If you're using v0.3 please using the tuple syntax T({List(a), b}). Sorry for the confusion!

Then please remove the struct section from the book and replace it with a chapter about tuples.
Or put a big warning that it won't work with v0.3.0 in the book…

This has already been done :)


nixd: 2.1.2 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for nixd is: Nix language server
meta.homepage for nixd is: https://github.com/nix-community/nixd
meta.changelog for nixd is: https://github.com/nix-community/nixd/releases/tag/2.2.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 2.2.0 with grep in /nix/store/rx6f3325297c6qxmf4bckv3ld3zp5w7c-nixd-2.2.0
found 2.2.0 in filename of file in /nix/store/rx6f3325297c6qxmf4bckv3ld3zp5w7c-nixd-2.2.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

nixd

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/304706e32c368d2154049c42856699c0735195fa#nixd

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

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

nixd

Maintainer pings
cc @inclyc @Ruixi-rebirth for testing.

Superseded by https://github.com/NixOS/nixpkgs/pull/316394


DBZ-6123 fix typo "evemts" to "events" in docs.

fix typo in sql server docs

Thanks a lot, merging via https://github.com/debezium/debezium/pull/4296