Move requirements to pyproject.toml

This is based on the discussion in #12173
This PR removes all requirements*.txt files and moves the dependencies to pyproject.toml.

requirements_base.txt is now declared under project.dependencies (no change )
requirements_hdf5.txt is now declared under the mne[hdf5] variant (no change)
🆕 requirements.txt is now declared under the mne[full] variant (new)
🆕 requirements_testing.txt is now declared under the mne[test_base] variant (new)
requirements_testing_extra.txt is now declared under the mne[test] variant (existed before, but was undocumented)
🆕 requirement_doc.txt is now declared under the mne[doc] variant (new)
🆕 New mne[dev] variant, which resolve to mne[test,doc]

❓I wanted to ask about the naming of those variants. I think I would prefer tests or testing over test; and docs over doc. But no super strong feelings here. Just wanted to ask what you think.
I also realized that when building the sdist via python -m build -s, I get some warnings related to (outdated) definitions in MANIFEST.in, which will warrant an investigation sometime when we have time.
warning: no files found matching 'mne/data/dataset_checksums.txt'
warning: no files found matching '*.json' under directory 'mne/gui/help'
warning: no files found matching '*.css' under directory 'mne/html'
warning: no files found matching 'mne/datasets' under directory 'mne'
warning: no files found matching 'mne/io/edf/gdf_encodes.txt'
warning: no previously-included files matching '*' found under directory 'examples/MNE-sample-data'
warning: no previously-included files matching '*' found under directory 'examples/MNE-testing-data'
warning: no previously-included files matching '*' found under directory 'examples/MNE-spm-face'
warning: no previously-included files matching '*' found under directory 'examples/MNE-somato-data'
warning: no previously-included files found matching 'tools'
warning: no previously-included files found matching 'CODE_OF_CONDUCT.md'
warning: no previously-included files found matching '.github'
warning: no previously-included files found matching '.github/ISSUE_TEMPLATE'
warning: no previously-included files found matching '.github/ISSUE_TEMPLATE/blank.md'
warning: no previously-included files found matching '.github/ISSUE_TEMPLATE/bug_report.md'
warning: no previously-included files found matching '.github/ISSUE_TEMPLATE/feature_request.md'

I will only have time to continue work on this on Wednesday.

I wanted to ask about the naming of those variants. I think I would prefer tests or testing over test; and docs over doc. But no super strong feelings here. Just wanted to ask what you think.

No strong preference here. Channeling @larsoner I'd say "see what numpy/scipy/pandas/matplotlib call them" and follow suit if there's a pattern.
One opinion I do have is that we should reconsider test_extra (really, all the variants). I'm guessing (?) that the main reason test_extra is separate is to save CI install time for CIs that don't need the "extra" ones?  If that's right then maybe having a special variant called mne[ci] or mne[citest] makes sense. The same logic could extend to doc as well: if we need separate varaints for CI efficiency, let's name them accordingly, and have fewer variants that are intended for user-usage. In other words, we could assume that anyone who wants to be able to run our tests might also want to build our docs locally (and vice versa) and just have one variant for both cases (maybe mne[contrib]?).  The (more comprehensive) user-facing variants could then inherit from the (more granular) CI variants, e.g., contrib = mne[citest], mne[citestextra], mne[cidoc].
If CI efficiency is not the reason for the granularity, well then I still think we should consider merging some of the variants. I want our (advanced) install instructions as simple as possible, and we already have 4 variants at least: mne, mne[full], mne[doc]  and mne[test] to describe to people (not to mention hdf5...). That feels like too much.

That's exactly what I mentioned previously. Let's try to make do with the smallest set of variants. For example, let's get rid of hdf5 and incorporate it in either the base requirements or in full.

That's exactly what I mentioned previously. Let's try to make do with the smallest set of variants. For example, let's get rid of hdf5 and incorporate it in either the base requirements or in full.

yes, I was echoing your prior comment, but forgot to give you credit, sorry @cbrnr.

That's exactly what I mentioned previously. Let's try to make do with the smallest set of variants. For example, let's get rid of hdf5 and incorporate it in either the base requirements or in full.

I think it makes sense to have it in "base", considering that we're now offering to save to HDF5 in several places. We will keep the then empty variant around for compatibility, like we do with "data".
Any vetos?

We will keep the then empty variant around for compatibility, like we do with "data".

I would not keep them around forever though. Let's deprecate them.

How are you going to let users know that they're deprecated, though?
I think I read in the PyPA docs that it's recommended to just keep them around, empty ...

Except for people using pip install in a script, this is not really part of their code, so I assume it won't really break a lot of people's workflows. I think it's fine to keep them around for two more releases, but then remove them. Surely there has to be a way of getting pip to print some warning?

For example, let's get rid of hdf5 and incorporate it in either the base requirements or in full.

I think it makes sense to have it in "base", considering that we're now offering to save to HDF5 in several places.

We had some extended discussion a while ago about what's required to add something to the base / required dependencies. I was trying to make the case for nibabel. It was rejected because:

Primarily, it causes legal headaches for downstream users (e.g. in managed/corporate envs). This issue still applies.
Secondarily, there was sentiment that something that is necessary for only some users/use cases might not meet the bar (e.g., EEG ML pipelines that don't do source imaging). nibabel is also an excellently maintained, pure Python library. h5py is a compiled library with more complicated deployment/installation/compat (this is my sense historically and @agramfort made the same observation when we originally considered the hdf5 option two years ago). So that adds a lot of hesitation at my end. My sense is also that nibabel is used more often than h5py by our code and possibly end users (git grep suggests this internally, but who knows once you start thinking about users and read_raw_eeglab etc.).

So to me if we reject nibabel as a core dep we should reject h5py.

I would not keep [no-op optional specifications] around forever though. Let's deprecate them.

Previously we decided to keep the legacy no-op options. There is close to zero maintenance burden for this so I wouldn't bother deprecating it.

I'm guessing (?) that the main reason test_extra is separate is to save CI install time for CIs that don't need the "extra" ones? If that's right then maybe having a special variant called mne[ci] or mne[citest] makes sense

Historically the motivation for the two files are:

_testing.txt : pytest etc. that you'd want for a fully functional test suite
_testing_extra.txt : extra deps that are not needed for full MNE functionality but that are needed for fewer tests to be skipped. A prime example is nitime which is just used for validating some multitaper implementations.

So I like the idea of citest or probably better fulltest -- I think actually 95%+ of devs and PRs do not need the stuff in requirements_testing_extra.txt in order for their tests to run. People who do advanced stuff like developing a scraper for a new GUI can be expected to do pip install sphinx_gallery or whatever to get their scraping test to run. And we should not group this all together because we want to be able to install [test] in the minimal CI build, which needs pytest infra but should not pull in stuff like SG and nitime.

I'm fine with moving h5py into [full], I agree that it probably doesn't qualify as a base dependency.
Regarding keeping the legacy variants around as no-ops, this means that they suddenly and silently stop doing what they used to do. I would print a warning for a couple of releases and eventually remove these options.

Regarding keeping the legacy variants around as no-ops, this means that they suddenly and silently stop doing what they used to do.

I don't think we should make any existing option stop doing what it used to do. IIRC [data] stuck around because we rolled pooch into base deps. I don't think we should change the behavior of [hdf5] because that would be backward incompatible. I think we should keep [hdf5] as it is.

OK. But then they are not no-ops, right?

[data] still will be a no-op, and I don't think we should bother deprecating it. [hdf5] would not be a no-op (it would still install whatever it installs now).

Yep, unless we add [hdf5] dependency to project.dependencies, [hfd5] won't be a no-op!

Sounds good @drammock !

I like your proposal, @drammock!
I'd just like to add to this:

variant test (which currently installs testing and testing_extra). To me this is another candidate for becoming legacy; I still think that many folks who want to run our tests might also want to build our docs, and it's not so onerous to bundle the doc and test dependencies together, so why not just say "contributors should install mne[dev]" (or whatever we call it) and keep mne[test] around as a legacy variant for CIs and/or downstream compatibility?

that I couldn't find any mention of mne[test] in our dev / contributor docs, so this feature seems to have never been documented or been undocumented for a long time. So no harm done kicking this one out without any deprecation whatsoever, esp since it won't affect any ordinary users

I couldn't find any mention of mne[test] in our dev / contributor docs

ah, OK. however
$ git grep "\.\[test\]"
azure-pipelines.yml:113:              python -m pip install --progress-bar off --upgrade -e .[test]

so it seems like we do want/need it for CIs anyway. But we're free to change its name if that is helpful to keeping things organized.

Please do if you have time, I'm busy with other things right now

Thanks @larsoner for resurrecting my previous opinions. I have still the same.
I am fine with Dan’s proposal
Thx for the thoughtful discussion on this important matter.

@drammock I've refactored the PR so that it only restructures the optional requirements to facilitate CI use, rather than dev etc. so that we can hopefully punt on that issue for now. If that sounds okay to you, feel free to review and mark for merge-when-green

Okay I'm going to get rid of the notebook job and adjust CI requirements. I don't think it's worth us testing the osmesa branch for this much hassle

Green! Fixes failures currently in main as well.

Thanks @larsoner, massive effort! I hope I will find some time to test this before the weekend
Thanks everybody for your input, esp @drammock, @cbrnr and @agramfort

Good team effort!
@hoechenberger feel free to come back to #12173 when you want. I don't think we should merge it this week as we push out 1.6 to be safe -- it's better as an early PR in the 1.7 cycle


[ERROR] Failed to install on peer peer0.org1.example.com with reason: Error: 8 RESOURCE_EXHAUSTED: grpc: received message larger than max (230453271 vs. 104857600)

I've been struggling with this error and have no clue how to fix it.
Can anyone help?

Same issue? Any solutions ?

where does the "104857600" number come from?


[El] Greek initial support

The failing tests occur only because the recognition model cannot handle a specific case for ,  etc. - which happens always often in Greek for words whose gender is male. Let  be a  and  a . In any case the logic is the same and the recognition model has to handle these <entity_names> as follows:
If there is any word in a / ending with "ς", that character has to be omitted/skipped when reading a sentence/test. For instance: name: "word1 word2",   "word1" ends with "ς".  But the sentence/test must include that  without the aforementioned character "ς".


schleuder: restrict to linux

Various gems have failed to build since 2023-11, and it is unlikely that we maintain schleuder on darwin.
https://hydra.nixos.org/job/nixpkgs/trunk/schleuder.aarch64-darwin
https://hydra.nixos.org/job/nixpkgs/trunk/schleuder.x86_64-darwin
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Wouldn't it make more sense to mark it broken?  At a quick glance it doesn't look to me like upstream specifically intends to only support Linux?

Of course it does, thank you.


Youtube api ( Advertisement is not working in youtube blocked country )

Dear shawnbuso
Advertisement is not working In YouTube ban countries is there is any way to bypass it ? in some of the countries youtube is accessible but it is keep fluctuate according to gov order . so plugin stop working and because of that i am having Unfilled impressions in my DFP . hope you have great idea to bypass it like before .
Many Thanks
baqarrizvi

Hi there,
Our plugin should work in countries that block YouTube. We do use some YouTube resources, but if those requests fail we fall back to alternate resources that are non-YouTube. For example, on my test page redirected youtube.com to a non-existant website and the plugin still worked. Are you getting any errors other than YouTube being blocked?

Dear shawnbuso,
Thanks For your immediate response in this issue . I am using IMA SDK PLAYER In my mobile app also. will it also call alternate option when youtube got blocked like website . I am talking about google media Framework right now . Hope you will respond .
Many Thanks
baqarrizvi

I'm a bit confused - which product are you using? If you're using the Video.js plugin, you're in the right place, and as I stated above it should be working even if YouTube is blocked. If you're using our Android or iOS Google Media Framework, could you follow up on the issue tracker for the one you're using?

Dear shawnbuso,
You always comes with great idea actually we have tried you example as well after blocking youtube in our router but its not responding also have try all of your example non of them are working. can you please try same at your side .
Many Thanks
Baqarrizvi

Hmm that's odd - what network requests are you seeing fail? I tried it again and it's still working for me - I see a request to https://www.youtube.com/iframe_api fail but yhe ad still plays (see attached screenshot).

Dear shawnbuso,
Thanks for your Response from your important time. we have tried any other software K9 . but if its working fine at your side it should be. you are awesome like always.
Many Thanks
Baqarrizvi


Add support for HTTPS #227

Allows to use Kestrel with HTTPS even without a Reverse Proxy (e. g. for development or internal purposes).
Addresses https://github.com/loic-sharma/BaGet/issues/227
See https://github.com/loic-sharma/BaGet/issues/227
Summary of the changes (in less than 80 chars)

Kestrel configuration was modified so that it can use HTTPS if configured.

@loic-sharma I hope, the PR is now okay for you. If not, please do not hesitate to contact me :)


AzureAppConfigurationRefreshOptions - Add support for ignoring refresh failures

Currently, you can specify the optional at the top level, but would be nice to have this as required, but indicate failures on refresh to be ignored. Something like:
config.AddAzureAppConfiguration(options =>
{
  options.Connect(...).ConfigureRefresh(refresh =>
  {
    refresh.IgnoreFailures = true;
  });
}, optional: false);

Is something like this already available? If not, does it make sense to add such functionality?
Thank you.

If you use App Configuration middleware for ASP.NET Core, failures during configuration refresh are always ignored.
If you call refresh in your code, you can use TryRefreshAsync to ignore the error or use RefreshAsync to get exceptions in case an error occurs.

I see, appreciate your prompt help. Thank you.


Release 2018-11-30

Codecov Report

Merging #339 into 0 will increase coverage by 5.57%.
The diff coverage is 41.74%.

@@            Coverage Diff             @@
##                0     #339      +/-   ##
==========================================
+ Coverage   33.41%   38.98%   +5.57%
==========================================
  Files          84      101      +17
  Lines        2460     4250    +1790
  Branches       10       22      +12
==========================================
+ Hits          822     1657     +835
- Misses       1637     2592     +955
  Partials        1        1


CPP: Improvements for ConditionallyInitializedVariable.ql

Add tests.  Fix examples in the qldoc.  Make several performance improvements to the new libraries used by this query.
  The first only makes a small difference noticeable on very large snapshots (for which computing control flow etc dominates if you run from a clean cache).

All issues fixed.


No sound on some devices (Android)

No sound on some Android devices (Vivo and some Samsung).
Notifications come and you can see them on the lock screen.
In the settings on the devices, the sound of notifications is allowed.
    "notification": {
        "body": "my body",
        "title": "my title",
        "sound": "default"
    },

I have the same problem with Samsung


My memory was filled and my computer hanged and stopped responding.

Describe the bug
I was just trying to run a blitz project from this repo udecode/plate-playground-template. But after waiting for a short time my PC stopped responding to any input and froze. The only option I had was to forcibly reboot the PC. After rebooting I tried again but the same happened.
Link to the blitz that caused the error
https://stackblitz.com/~/github.com/udecode/plate-playground-template
Steps to reproduce

Got to dashboard
Create a new project from udecode/plate-playground-template repo

Expected behavior
Work normally and fast as I used to.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform

OS: Windows
Browser: Edge

Additional context
No response

I also see an immoderate level of memory consumption.


issues

cmd crashed when starting main.py

Hi, can you be a little more specific?
Was there a crash error?
Have you tried running main.py as a command in cmd? e.g., python main.py

Added a batch file in commit a6e9abb. Closing now due to inactivity.


#174 Update styles.css

Issues Identification
Closes: #(issue number)
Description
Summary
Provide a brief description of what this pull request does and why it is needed.
Details
Include any detailed information about the changes in this pull request.
Types of Changes
Please check the boxes that apply

[ ] Bugfix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] My changes do not break the current system and pass all existing test cases
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots
If applicable, please attach screenshots of the changes made to the user interface.
Additional Information
Please provide any other information that is relevant to this pull request.

closes #174

@Piyushsahu99 write pr properly this is the last time Im explaining i cant explain every individual You dont have to copy paste any templet write what you do add ss and issue no

@Piyushsahu99 refer this https://github.com/GarimaSingh0109/Resum-Resume/pull/362


Launcing failure; error while loading shared libraries: libre2.so.7:

As executed ungoogled-chromium version 83.0.4103.116-2 in https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/archlinux/83.0.4103.116-2
It was interrupted,
/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.7: cannot open shared object file
It's not installed as,
$ find /usr -regex '.*libre2\.so.*'
find: ‘/usr/lib/firmware/b43’: Permission denied
find: ‘/usr/lib/firmware/b43legacy’: Permission denied
/usr/lib/libre2.so
/usr/lib/libre2.so.8
/usr/lib/libre2.so.8.0.0

How to install it and to resolve this?

You need to update to a new version and recompile the package.

It is the latest as was said: n https://ungoogled-software.github.io/ungoogled-chromium-binaries/releases/archlinux/83.0.4103.116-2

The binaries are contributed by third party contributors so they are not always up to date. You can get a latest version from @jstkdng's OBS repository though: https://download.opensuse.org/repositories/home:/justkidding:/arch/standard/x86_64/ungoogled-chromium-84.0.4147.89-1-x86_64.pkg.tar.zst

@jstkdng Actually is it possible to make an Action that pulls from your OBS and make a PR to -binaries?

Latest on link works. Thanks.

@wchen342 I'm not sure tbh, might have to think a solution if really required. In the meantime I'll just PR my builds to -binaries.


renamed adyenCheckout functions to match API endpoints

Summary
renamed adyenCheckout functions to match API endpoints for doPaymentsCall and doPaymentsDetailsCall

I did not refactor createPaymentRequest in adyenCheckout.js on purpose as it does not directly relate to an API call. Interested to hear your thoughts!

I did not refactor createPaymentRequest in adyenCheckout.js on purpose as it does not directly relate to an API call. Interested to hear your thoughts!
you mean refactor to "createPaymentsRequest"? it's not a huge deal for me, but we do say "payments request" when we speak about it to each other, rather than "payment request", so it would make sense if you changed it.


Allow in offline apps

This widget works just fine in offline apps, for the part that works without microflow calls.
I needed it because we need the forgot password functionality and have an offline app.
I changed the offline flag in the XML and added a paragraph to the documentation for offline usage.

Please edit the documentation for this Mendix App Store content directly in the App Store on the Documentation tab:
https://appstore.home.mendix.com/link/app/87/Mendix/Login-form
We do not keep Mendix App Store documentation in this repo.
Thanks!

Jelte, please review documentation and widget changes.


yarn link causing -bash: /usr/local/bin/kuroko: Permission denied error

https://github.com/yarnpkg/yarn/issues/3587
https://nodejs.org/api/fs.html#fs_fs_chmod_path_mode_callback


(<●>ω<●>) 。。。。。 (絶対使ってね・・・) (#3)

Ref: p10k not using ps1. Search prompt_example in ~/.p10k.zsh.
Fix #3

Thank you Thank you !!! ∠( ᐛ 」∠)_
@ulwlu

oh merged for real, lol. I hope it helps you customize easily from this base.


Electricity consumption low-normal-high are unknown

With the last update, the three sensors that display the three different electricity consumption by tariff group, are all stuck on 'unknown'. Rebooting HA or the integration won’t work to resolve the problem…

Looks that these values aren't available anymore. I'm not able to find them in the app.
Need to double check the API responses

I removed the sensors as they are not part of the api response anymore


:sparkles: add support for remote resource fetching

Description

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires a change to the official Guide documentation.

@ianardee The integration test technically follows a redirect, so I don't think having a non-redirect test is all that important


Tell users what Design System support can help with

What
Create a doc that defines what we can help users with. In the first instance we won't document what we can't help users with.
Why
We're concerned that we are providing support when we shouldn't. This takes time away from the team to fix another things that's more valuable. It also unhelpful for users, as they are waiting for responses from us and we can't help users resolve their problem.
Who needs to work on this
Content, DM, anyone on support
Who needs to review this
Most people who provide support
Done when

[ ] draft doc that defines what we can help users with
[ ] team has reviewed and agreed
[ ] we've posted it somewhere users can access the document from the start of the support journey (ie Slack, support page on website)
[ ] write a ticket to monitor whether users have open the doc / page and changes to what queries we get on support.

Close for now. Reopen if we still want to do this.


add multicolumn for row view

It is possible to break the row, it will allow to set the column width more flexibly
for example: 2 coll + 1 row

'width' => 'w-1/2',

'width' => 'w-1/2',

'width' => 'w-full',

@webspilka - thanks for the PR and sorry for slow response.  I've made a few small tweaks to tidy up the layout but your PR will be in the next release.  Thanks again for the help


Added 2.2 release notes.

Description
Added 2.2 release notes.
Check List

[x] New functionality includes testing.

[ ] All tests pass

[x] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

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

Codecov Report

Merging #212 (953afe7) into main (366bf16) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 953afe7 differs from pull request most recent head 9f4c8b4. Consider uploading reports for the commit 9f4c8b4 to get more accurate results

@@            Coverage Diff            @@
##               main     #212   +/-   ##
=========================================
  Coverage     83.76%   83.76%
  Complexity      434      434
=========================================
  Files            66       66
  Lines          2205     2205
  Branches        254      254
=========================================
  Hits           1847     1847
  Misses          261      261
  Partials         97       97

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Quick question. Did you mean to add backport tags?

@AWSHurneyt the version changes in the build script.


[ci] fall back to source installs of R packages if binary missing (fixes #3875)

I believe this will fix #3875. Right now in the Mac CI jobs for the R package, we set type = "binary" in install.packages(). This can lead to failures shortly after a new package needed in those jobs is uploaded to CRAN, when only source versions are available. Precompiled binaries from CRAN usually take 1-2 days to become available, in my experience.
the package {withr} was updated yesterday (https://cran.r-project.org/web/packages/withr/index.html), and I think the failures observed in #3875 happened because of this phenomenon.
This PR changes the strategy for installation on Mac to "both". From ?install.packages

An alternative (and the current default) is "both" which means ‘use binary if available and current, otherwise try source’. The action if there are source packages which are preferred but may contain code which needs to be compiled is controlled by getOption("install.packages.compile.from.source"). type = "both" will be silently changed to "binary" if either contriburl or available is specified.

So as of this PR, Mac builds will look for binaries (which are faster to install), but will install source packages from CRAN if the source package is newer.
This should prevent future issues like this from blocking LightGBM's CI.

@StrikerRUS we'll have to use admin rights to merge this, since I haven't fixed #3873 yet. Is that ok?
Otherwise I can remove the linting job temporarily from all-successful in the GitHub Actions config, then put it back in the fix for #3873

@StrikerRUS we'll have to use admin rights to merge this, since I haven't fixed #3873 yet. Is that ok?
Otherwise I can remove the linting job temporarily from all-successful in the GitHub Actions config, then put it back in the fix for #3873

@jameslamb

we'll have to use admin rights to merge this,

And this one #3874 to fix CUDA tests.
I think admin rights is better than mess in CI code between PRs.

@jameslamb

we'll have to use admin rights to merge this,

And this one #3874 to fix CUDA tests.
I think admin rights is better than mess in CI code between PRs.

I see in macOS R4:
 Error in loadNamespace(name) : there is no package called 'withr'
  Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
  Execution halted

Seems having both is not enough.

I see in macOS R4:
 Error in loadNamespace(name) : there is no package called 'withr'
  Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
  Execution halted

Seems having both is not enough.

I see in macOS R4:
 Error in loadNamespace(name) : there is no package called 'withr'
  Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
  Execution halted

Seems having both is not enough.

ok seeing that, now I think the issue is that something somewhere in {testthat}'s many recursive dependencies (it was more than 100, the last time I checked), needs {withr} but didn't correctly specify it in their metadata. I can just add an install.packages("withr") to try to fix it.
I still think the "both" fix is a good one and will also improve stability, even if it didn't end up fixing this specific issue.

I see in macOS R4:
 Error in loadNamespace(name) : there is no package called 'withr'
  Calls: test_check ... loadNamespace -> withRestarts -> withOneRestart -> doWithOneRestart
  Execution halted

Seems having both is not enough.

ok seeing that, now I think the issue is that something somewhere in {testthat}'s many recursive dependencies (it was more than 100, the last time I checked), needs {withr} but didn't correctly specify it in their metadata. I can just add an install.packages("withr") to try to fix it.
I still think the "both" fix is a good one and will also improve stability, even if it didn't end up fixing this specific issue.

hmmmm interestingly, it DOES look like R tried to install {withr} (https://github.com/microsoft/LightGBM/pull/3876/checks?check_run_id=1785068087).

trying URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/withr_2.4.1.tgz'
Error in download.file(url, destfile, method, mode = "wb", ...) :
cannot open URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/withr_2.4.1.tgz'
In addition: Warning message:
In download.file(url, destfile, method, mode = "wb", ...) :
cannot open URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/withr_2.4.1.tgz': HTTP status was '404 Not Found'
Warning in download.packages(pkgs, destdir = tmpd, available = available,  :
download of package ‘withr’ failed
trying URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/data.table_1.13.6.tgz'
Content type 'application/x-gzip' length 2335683 bytes (2.2 MB)

But it still only looked for the binary. Ok, let me experiment a little. I commented out all other CIs so I don't hurt our capacity too much while testing.

hmmmm interestingly, it DOES look like R tried to install {withr} (https://github.com/microsoft/LightGBM/pull/3876/checks?check_run_id=1785068087).

trying URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/withr_2.4.1.tgz'
Error in download.file(url, destfile, method, mode = "wb", ...) :
cannot open URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/withr_2.4.1.tgz'
In addition: Warning message:
In download.file(url, destfile, method, mode = "wb", ...) :
cannot open URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/withr_2.4.1.tgz': HTTP status was '404 Not Found'
Warning in download.packages(pkgs, destdir = tmpd, available = available,  :
download of package ‘withr’ failed
trying URL 'https://cloud.r-project.org/bin/macosx/contrib/4.0/data.table_1.13.6.tgz'
Content type 'application/x-gzip' length 2335683 bytes (2.2 MB)

But it still only looked for the binary. Ok, let me experiment a little. I commented out all other CIs so I don't hurt our capacity too much while testing.

I think admin rights is better than mess in CI code between PRs.

I agree!

I think admin rights is better than mess in CI code between PRs.

I agree!

Ah!!! I can see on CRAN that the {withr} r-release binaries exist, but for 2.4.0 only (the package is on 2.4.1). This is why the builds are only failing for R 4.x and not R 3.6.

I think R is getting confused by this.
No amount of trickery with install.packages() can fix this and still preserve our binary installs, I don't think. So I guess we do have to add a separate installation of {withr}, from source, to resolve this.

Ah!!! I can see on CRAN that the {withr} r-release binaries exist, but for 2.4.0 only (the package is on 2.4.1). This is why the builds are only failing for R 4.x and not R 3.6.

I think R is getting confused by this.
No amount of trickery with install.packages() can fix this and still preserve our binary installs, I don't think. So I guess we do have to add a separate installation of {withr}, from source, to resolve this.

@jameslamb

So I guess we do have to add a separate installation of {withr}, from source, to resolve this.

This will be reverted after a day or two, right? When version will be in a sync state at CRAN, I mean.

@jameslamb

So I guess we do have to add a separate installation of {withr}, from source, to resolve this.

This will be reverted after a day or two, right? When version will be in a sync state at CRAN, I mean.

It probably could be reverted, yes. I don't know a more permanent fix for this problem :/
type = "both" is supposed to exactly solve this problem, but it looks like it isn't.

It probably could be reverted, yes. I don't know a more permanent fix for this problem :/
type = "both" is supposed to exactly solve this problem, but it looks like it isn't.

This seems to have worked: https://github.com/microsoft/LightGBM/pull/3876/checks?check_run_id=1785421659

This seems to have worked: https://github.com/microsoft/LightGBM/pull/3876/checks?check_run_id=1785421659

#3874 and #3877 have been merged into master and I've merged master into this PR, so all CI jobs should now pass on this PR

#3874 and #3877 have been merged into master and I've merged master into this PR, so all CI jobs should now pass on this PR


Fix sample obj

This PR is build on top of #1072 (merged) and #1073. At least #1072 should be merged in master before merging this one, so the commits from there (quite a few) disappear here.
This PR fixes the BaseSample, Sample and PrepSample objects and their tests. The tests for these objects are expected to pass.

#1073 was just merged, can you pull upstream on this?

@squirrelo Done!

:+1:

Looks good. @squirrelo @josenavas is there a way to test this, or are we merging everything into the relax-md-req first, and saving the testing for later?

@adamrp all the functionality is not in place after a couple more PR. I think the best path is to review the code to see if there is anything horribly wrong, and then wait for the PR that everything is in place to make sure that everything is correct. Is really hard to test until everything is in place, but if the code looks good, I can fix the remaining issues later. Does everybody agrees with that?

@josenavas, yes that's a good strategy moving forward.

great! Thanks.


Confiuration not applied before docker-entrypoint-initdb.d scripts are applied

Bug report
Per the postgres docker image it should be possible to place initial sql files in the docker-entrypoint-initdb.d folder for them to execute when postgres starts. When this is done in the supabase/postgres image default users are non-existing on the execution time wy this function does not work properly.
To Reproduce

Start a development instance of the normal supabase infrastructure
Populate the database with some data
export the data using the pg_dump util
Start a database in a docker-compose environment  database:
    image: supabase/postgres:latest
    ports:
      - 5432:5432
    command: postgres -c config_file=/etc/postgresql/postgresql.conf
    volumes:
      - the-dump.sql:/docker-entrypoint-initdb.d/the-dump.sql
    environment:
      POSTGRES_PASSWORD: postgres

Observe following error:database_1  | [local] 2022-09-07 12:46:16.815 UTC [70] postgres@postgres ERROR:  role "supabase_admin" does not exist
database_1  | [local] 2022-09-07 12:46:16.815 UTC [70] postgres@postgres STATEMENT:  ALTER SCHEMA auth OWNER TO
supabase_admin;
database_1  | psql:/docker-entrypoint-initdb.d/preview_data.sql:26: ERROR:  role "supabase_admin" does not exist
preview-infrastructure_database_1 exited with code 3

Expected behavior
I would expect the database to start and populate the database with the contents of the dump.
System information

OS: PopOs 22.04

❯❯❯ docker-compose -v
docker-compose version 1.29.2, build unknown
❯❯❯ docker -v
Docker version 20.10.17, build 100c701
❯❯❯ supabase -v
1.4.2

TL;DR: Apply appropriate initialization. If the goal is to have it working like Supabase, take inspiration from here: https://github.com/supabase/supabase/tree/master/docker/volumes/db/init
I am letting myself out


hotfix: fixed old meeting links

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


feat: liminf and limsup add/mul lemmas in Real

Lemmas such as limsup u f + liminf v f ≤ limsup (u + v) f (and its multiplicative avatars) in (basically) reals. These lemmas had already been done in EReal/ENNReal. The strategy is the same; using reals brings some complexity with the gestion of IsBoundedUnder/IsCoboundedUnder properties.
Summary of the modifications:

In Mathlib/Algebra/Order/Group/DenselyOrdered.lean: proof of le_mul_of_forall_lt and mul_le_of_forall_lt, as well as their additive versions, which are key for the final results on (R, +).
In Mathlib/Algebra/Order/Field/Basic.lean: proof of le_mul_of_forall_lt' and mul_le_of_forall_lt_of_nonneg, which are key for the final results on (R+, *).
In Mathlib/Order/LiminfLimsup.lean: four lemmas from IsCobounded.frequently_le to IsCobounded.of_frequently_le are moved to the beginning of the file, so they can be used within. Four new elementary lemmas about IsBoundedUnder which I found quite practical. Four new lemmas about boundedness/coboundedness of sums and products.
In Mathlib/Topology/Algebra/Order/LiminfLimsup.lean: eight new lemmas about addition/multiplication and limsup/liminfs.

Lemma limsup_mul_le would be useful in #18172. Pinging @mariainesdff

bors r+
Thanks!


Experiment on SARCOS dataset

Can you provide the experiment on the SARCOS dataset?

We've added code to reproduce the SARCOS experiment results: https://github.com/AvivNavon/pareto-hypernetworks/tree/master/experiments/sarcos

Thank you for sharing, I will close my issue.


Watch mode should remember failures from tests it does not rerun.

Issue
failing-test.js:
import test from 'ava';

test(t => t.fail('oh no!'));

passing-test.j2:
import test from 'ava';

test(t => t.pass('yeah!'));

// add more tests here

Given the above tests in watch mode, if you continue to edit passing-test.js (or any file that does not cause failing-test.js to be rerun), you will not be reminded that there are previously failing tests which were not rerun.
Solution
I think we should track previous failures and show a message like:
3 passed
2 failing
2 previously failing tests were not rerun

The above shows 3 passing and 2 failing tests that were rerun. It also mentions 2 tests that were not rerun because the watch algorithm did not detect any changes.
Alternate solution
Always rerun files that had failing tests regardless.

Always rerun files that had failing tests regardless.

I'd like to avoid that overhead.
If we tackle #672 then it should be fairly straightforward to inform the reporter of the previously failed tests. Shouldn't be too hard to track them in the watcher either.

Is it possible to disable this message now? I realize it can be useful, but most of the time its just noise. I really care about the test I am currently iterating on. When I want to know if all tests pass, I will run the whole test suite. Also, consider this use case:
ava --watch

// a.test.js
test('sometest', t => {
  t.is(1, 1)
  t.is(1, 2)
})

now I edit a.test.js
// a.test.js
test('sometest', t => {
  t.is(1, 1)
})

and I am stuck with the message

1 previous failure in test files that were not rerun
until I stop and start the test runner.

Is it possible to disable this message now?

I don't think this is something we need to have an option for.


OpenROAD flow variables document

Signed-off-by: vijayank88<EMAIL_ADDRESS>OpenROAD flow public platforms environment variables document contributed.

Looks good now @vijayank88. I will approve and merge once the = -> ?= PR is merged in ORFS.


Emberfire hasMany storage and order question?

I store hasMany relationships on a model and it works as expected in most ways. However, the way the "array" is stored seems very unconventional. See below:

I have read the following blog post which explains the 'why": https://www.firebase.com/blog/2014-04-28-best-practices-arrays-in-firebase.html but this still is causing some issues for me because I am using https://github.com/jgwhite/ember-sortable to allow users to SORT the related items so I need to store this relationship in a certain order which would normally be possible if it stored a pure array of keys. Screen below:

@tstirrat et al.
Is this something that people have come across before? I couldnt find any answers related to this here. Just looking for a workaround if anyone has one.
Cheers!

I am not sure why the second value is always true in the storage image above but I assume there is likely a good reason. I guess for my use case it would be optimal to serialize with a sequence integer value instead of always being boolean true. Something like:
employments
 -K8V9qndsl6cTfcaWHVA: 3
 -K92bn9xmi6RTMiH_BHI: 4
 -K92hQ-44QaxfnkwAL3l: 2
 -K92hqVrEoXglwqAZ924: 1

And then have the array sorted in the serializer using the sequence value. Just thinking aloud...

This is not something that has directly been asked for, but I can definitely see the need. I think we can use priorities for this, so that we can remain backwards compatible with existing data sets.

Thanks @tstirrat. So below works fine:
    reorderEmployment(newOrder) {
      const modelId = this.get('model.id');
      newOrder.forEach(function(employment, index) {
        let ref = new Firebase('https://amber-fire-9286.firebaseio.com/personSkills/' + modelId + '/employments/' + employment.get('id'));
        ref.setPriority(index);
      });
    },

That's good as a short term solution, but you might have problem getting correct ordering from the server. For this we need to use Firebase's forEach implementation on relationships.

Because of the way JavaScript object hashes work, the ordering of data in the JavaScript object returned by val() is not guaranteed to match the ordering on the server nor the ordering of child_added events. That is where forEach() comes in handy. It guarantees the children of a DataSnapshot will be iterated in their actual order, the same order as they are kept in your Firebase database.

Yeah this is just a workaround for now but so far ordering has always been consistent.
@tstirrat if you know what you want to do and just need someone to help with an Emberfire implementation - I can give you some time. I would just need guidance as I do not have a handle on the Firebase internals.

We were using an approach similar to @brendanoh above—iterating over each record and setting priority with:
itemModels.forEach(function(item, index) {
    let itemId = get(item, 'id');
    let ref = new Firebase(`https://<app-name>.firebaseio.com/<model-name>/${itemId}`;
    ref.setPriority(index);
});

However, since bumping up to emberfire 2.0.1 and Firebase SDK 3.2.0, we receive the following error:
_firebase.default is not a constructor

I suspect that new Firebase() is no longer able to create a valid connection?

You could use the model's .ref()
itemModels.forEach(function(item, index) {
  item.ref().setPriority(index);
});

Or you could inject the firebase service:
const ref = this.get('firebase');
itemModels.forEach(function(item, index) {
    let itemId = get(item, 'id');
    let modelRref = ref.child(`<model-name>/${itemId}`);
    modelRef.setPriority(index);
});

The latter worked like a charm, since I needed to reach down into a nested child model. Thank you!

I dont get this to work.
I have a model with:
documents: hasMany('document', { async: true });
Before I save I set a priority:
model.get('documents').forEach((doc, index)=> {   doc.ref().setPriority(index); })
It doesnt do anything when I show it in the template.
The hasManyArray doesnt have any collection ref, which I could sort by priority.
It seems to be possible when manally querying, but with an async relationship emberfire does it all.
Im abit lost.

I am assuming what you are wanting to is have the documents in a certain order? If so below is how I update the order of the hasMany array.
I don't know what your model is called so in the example below I am assuming it is a hasMany on a person model. So if you have injected firebase at the top of your controller or component file the you pass a sorted array of documents to an action called update and the following should work:
  actions: {
    update(orderedDocuments) {
      const fb = this.get('firebase');
      const personId = this.get('person.id');
      orderedDocuments.forEach(function(doc, index) {
          let docId = Ember.get(doc, 'id');
          let personRef = fb.child(`people/${personId}/documents/${docId}`);
          personRef.setPriority(index);
      });
    }
}

This works for me.
Then if you do the following in your template it should always show in the correct order:
{{#each person.documents as | document |}}
  {{document.name}} <br>
{{/each}}

Thank. I found my error. I added the index on the documents and not the relation-ids.
Im not very used to contribute to public repos, but I did alot of ember-data internals and will try to write a PR for emberfire. Thank you again.

Priorities are DEPRECATED now, as far as I could see, this is the line that saves true to the relationship, by playing around with it I managed to save the order

Is there any plan on supporting this?


ReferenceError: btoa is not defined

I'm passing the audio blob file using JavaScript XMLHttpRequest();
here's the my current code where the audio is the blob type audio/wav
  var xhr = new XMLHttpRequest();
  xhr.open('POST', "/", true);
  xhr.setRequestHeader("Content-Type", "application/x-www-form-urlencoded");
  xhr.send(audio);

then on my Express JS node, I'm receiving the params using req.body
blobUtil.blobToBase64String(req.body).then(function (base64String) {
   console.log('success')
 }).catch(function (err) {
   console.log('error')
 });

but I'm getting an error which is ReferenceError: btoa is not defined
Did I missed something here?

This is a library for browsers, and it appears you're using it in Node.js where btoa is unavailable. I suggest looking into Buffers instead: https://nodejs.org/api/buffer.html


'use of undeclared ZKCarousel' error

Hi Sir, I installed this successfully using cocoapods but when I use it, it gives me this
'use of undeclared ZKCarousel' error. Why am I getting this?

Oh I just missed the import. Sorry. I'm really new to iOS Dev.
Thanks


Great Job

Very nice selection of theme and unique design, very user friendly, but a bit less interactive. Wish your social icons have some efects, overal Gret job.

well done @felixodette your project looks so good, kindly please update your live demo with the last version of your project

Thanks for the info guys! I've addressed the live demo issue, and will be looking into the effects Willy brought up.


confd processes all files in /etcd/confd/conf.d

I'm not sure if I'm missing something, but when I run:
 confd -onetime -node $ETCD -config-file /etc/confd/conf.d/backends-apache.toml

confd processes also other files in /etc/confd/conf.d (e,g.: backends-f5.toml). The problem is that both configurations creates same file /etc/varnish/backends.vcl. Is this correct behaviour?

@DixonsBrnoDevs Yes, this is by design. You can create more than one confdir if you want to only generate one set of templates at a time.


Can we use env variables in devcontainer json?

Can we use environment variables in devcontainer.json like we do in settings.json (i.e. ${env:VAR_NAME}) ?
I try using it on Windows opening a folder in a Debian container by defining a configuration setting in devcontainer.json without success.
In case is not feasible, is there a workaround ?

See "Variables in devcontainer.json" at https://aka.ms/devcontainer.json for what is available here.


Compiling under Windows 7 failed

Another try to build the bootloader under Windows.
Cloned the repo with submodules.
Installed  GNU Tools ARM Embedded version 8 2018-q4-major for Windows (only 32bit version available)
Running make gives the following output:
Beegee@Bernd-Dev MSYS /b/Projects/Nordic/Adafruit_nRF52_Arduino_Bootloader/src
$ make
Making feather52832 board
----------------------
Compiling file: main.c
Compiling file: dfu_ble_svc.c
Compiling file: bootloader.c
Compiling file: bootloader_settings.c
Compiling file: bootloader_util.c
Compiling file: dfu_init_template.c
Compiling file: dfu_transport_serial.c
Compiling file: dfu_transport_ble.c
Compiling file: dfu_single_bank.c
Compiling file: app_timer.c
Compiling file: app_timer_appsh.c
Compiling file: app_scheduler.c
Compiling file: app_error.c
Compiling file: app_util_platform.c
Compiling file: crc16.c
Compiling file: hci_mem_pool.c
Compiling file: hci_slip.c
Compiling file: hci_transport.c
Compiling file: nrf_assert.c
Compiling file: app_uart.c
Compiling file: nrf_delay.c
Compiling file: nrf_drv_common.c
Compiling file: nrf_drv_uart.c
Compiling file: ble_srv_common.c
Compiling file: ble_dfu.c
Compiling file: ble_dis.c
Compiling file: pstorage_raw.c
Compiling file: system_nrf52.c
Assembly file: gcc_startup_nrf52.S
Linking target: feather52832_bootloader.out
Preparing: feather52832_bootloader.hex feather52832_bootloader_6.0.0_s132.hex
B:\DevTools\GNU Tools ARM Embedded\8 2018-q4-major\bin\arm-none-eabi-objcopy.exe: _build/feather52832_bootloader.hex 64-bit address 0x4b4fa300074000 out of range for Intel Hex file
B:\DevTools\GNU Tools ARM Embedded\8 2018-q4-major\bin\arm-none-eabi-objcopy.exe:_build/feather52832_bootloader.hex: bad value
make[2]: *** [Makefile:319: genhex] Error 1
make[1]: *** [Makefile:284: feather52832] Error 2
make: *** [Makefile:247: all] Error 2

Is it because of the 32bit version of the GNU tools?

Problem is the toolchain version.
The error occurs when using latest GNU tools 8 2018-q4-major.
Switching to older version 7 2018-q2-update solves the problem.

Development is moved to new repo https://github.com/adafruit/Adafruit_nRF52_Bootloader, this repo is obsolete and for reference only


Step 4. Check UDR and NSGs on the gateway subnet

Hello Team,
Step 4 mentions that remove user-defined routing (UDR) or Network Security Groups (NSGs) on the gateway subnet, UDR is fine but NSGs don't apply to gateway Subnet as mentioned in notes section here : https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings#gwsub
Can you please check and remove that after verification.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 089a64fa-6ccb-6c2c-9d32-9a1a1fd04d1d
Version Independent ID: 657867e8-d7ae-b091-81b7-5b65f61ccd45
Content: Troubleshoot an Azure site-to-site VPN connection that cannot connect titleSuffix: Azure VPN Gateway
Content Source: articles/vpn-gateway/vpn-gateway-troubleshoot-site-to-site-cannot-connect.md
Service: vpn-gateway
GitHub Login: @chadmath
Microsoft Alias: genli

@arvinder-dhar Thanks for your question. We are checking on this and will respond to you soon.

Thank you Sumanth!!

@arvinder-dhar , Appreciate your patience. Yes, exactly planting NSGs on top of gateway subnet will block the gateway creation.

We will update the doc accordingly and it would take some time for the changes to get reflect over the doc.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Error! Bad return status for module build on kernel: 4.19.42+ (armv6l)

Just got the AIY-vision kit and it worked fine at first. For some reason I did apt update and apt upgrade and after that it has been a long day of debugging, but nothing helps.
When trying to run any vision scripts I'm getting
File "/home/pi/AIY-projects-python/src/aiy/_drivers/_spicomm.py", line 219, in __init__
    self._dev = os.open(SPICOMM_DEV, os.O_RDWR)
FileNotFoundError: [Errno 2] No such file or directory: '/dev/vision_spicomm'

I've uninstalled all aiy-* packages and reinstalled according to HACKING.md but still the same issue.
I think the kernel upgrade messed up the system. Is there any other way besides flashing the SD card?
When trying to install aiy-vision-dkms, I'm getting the following error.
DKMS make.log for aiy-1.1 for kernel 4.19.42+ (armv6l)
Tue May 28 19:28:33 UTC 2019
make: Entering directory '/usr/src/linux-headers-4.19.42+'
  AR      /var/lib/dkms/aiy/1.1/build/aiy/gpio/built-in.a
  CC [M]  /var/lib/dkms/aiy/1.1/build/aiy/gpio/gpio-aiy-io.o
  AR      /var/lib/dkms/aiy/1.1/build/aiy/iio/adc/built-in.a
  CC [M]  /var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.o
/var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.c:138:2: error: unknown field 'driver_module' specified in initializer
  .driver_module = THIS_MODULE,
  ^
In file included from ./include/linux/linkage.h:7:0,
                 from ./include/linux/kernel.h:7,
                 from ./include/asm-generic/gpio.h:5,
                 from ./arch/arm/include/asm/gpio.h:10,
                 from ./include/linux/gpio.h:59,
                 from /var/lib/dkms/aiy/1.1/build/aiy/iio/adc/../../include/aiy-io.h:20,
                 from /var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.c:16:
./include/linux/export.h:16:21: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
 #define THIS_MODULE (&__this_module)
                     ^
/var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.c:138:19: note: in expansion of macro 'THIS_MODULE'
  .driver_module = THIS_MODULE,
                   ^~~~~~~~~~~
./include/linux/export.h:16:21: note: (near initialization for 'aiy_adc_info.read_raw_multi')
 #define THIS_MODULE (&__this_module)
                     ^
/var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.c:138:19: note: in expansion of macro 'THIS_MODULE'
  .driver_module = THIS_MODULE,
                   ^~~~~~~~~~~
cc1: some warnings being treated as errors
scripts/Makefile.build:309: recipe for target '/var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.o' failed
make[4]: *** [/var/lib/dkms/aiy/1.1/build/aiy/iio/adc/aiy-adc.o] Error 1
scripts/Makefile.build:544: recipe for target '/var/lib/dkms/aiy/1.1/build/aiy/iio/adc' failed
make[3]: *** [/var/lib/dkms/aiy/1.1/build/aiy/iio/adc] Error 2
scripts/Makefile.build:544: recipe for target '/var/lib/dkms/aiy/1.1/build/aiy/iio' failed
make[2]: *** [/var/lib/dkms/aiy/1.1/build/aiy/iio] Error 2
scripts/Makefile.build:544: recipe for target '/var/lib/dkms/aiy/1.1/build/aiy' failed
make[1]: *** [/var/lib/dkms/aiy/1.1/build/aiy] Error 2
Makefile:1524: recipe for target '_module_/var/lib/dkms/aiy/1.1/build' failed
make: *** [_module_/var/lib/dkms/aiy/1.1/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.42+'

I too cannot get vision bonnet to work on RPI strech lite (updated os and kernel, rpi zero)
I believe HACKING.md needs refactoring
regarding your specific issue, you can build aiy-vision-dkms if you run:
sudo apt-get --purge remove linux-headers-3.6-trunk-common
-> according to: https://stackoverflow.com/questions/54450251/build-of-aiy-vision-dkms-fails
personally I've tried and successfully built aiy-vision-dkms, yet still cannot get "Myriad ready" in dmesg

I had a similar issue with my Voice kit. I found a script that will revert the kernel to 4.14.98 (last version I had installed that worked). After reverting the kernel version and rebooting you should be able to either do a dpkg-reconfigure on the installed modules, or just reinstall them.
https://gist.github.com/psyke83/cb3ca50561480809c246f42727cb7cf2

after rpi kernel upgrade just rebuild of dkms packages is enough for me to get AIY back working
(see workaround in https://github.com/google/aiyprojects-raspbian/issues/570 )

This project is in real need of a new disk image with updated kernel, etc. It has been nearly 8 months since the last working disk image release. Is the AIY project dead?

had a quick look and the patches are not that hard to do
basically for
/var/lib/dkms/aiy/1.1/
apply https://github.com/raspberrypi/linux/commit/97623c0a80a605ef3fae337081ed008796bf8cc2#diff-3ec871a8e75c9ea85161805bbdee22a1 and https://github.com/raspberrypi/linux/commit/3f3a89e1d7c31558c070692241e3d6146d2cf1bf
the harder part is to update google deb repos for everybody to get the fixes

I got it working with kernel 4.19.57.
There are two files you'll need to edit (note that you'll need to use sudo to edit them). First one:
/usr/src/aiy-1.1/aiy/iio/adc/aiy-adc.c
(note that /usr/src/aiy-1.1 is where the source code is copied from when the module is being built).
Remove the line starting with .driver_module =.
Second one:
/usr/src/aiy-1.1/aiy/mfd/aiy-io-i2c.c
Replace two occurrences (in aiy_io_reset and in aiy_io_update_firmware) of
i2c_lock_adapter(i2c->adapter);
with
i2c_lock_bus(i2c->adapter, I2C_LOCK_ROOT_ADAPTER);
and replace two occurrences of
i2c_unlock_adapter(i2c->adapter);
with
i2c_unlock_bus(i2c->adapter, I2C_LOCK_ROOT_ADAPTER);
Then run the following command:
sudo dkms install aiy/1.1
Reboot, and Bob's your uncle. Literally five lines of code to change. :)

@ginkage will you be able to update deb packages too? ;-)
Or know someone who can patch them and build and upload to googles repo?

I have updated and rebuilt the package. You can get it here:
https://drive.google.com/open?id=1s6ru6Clz0pmX0VS3BOW9XJoqKE7E8y12

I have updated and rebuilt the package. You can get it here:
https://drive.google.com/open?id=1s6ru6Clz0pmX0VS3BOW9XJoqKE7E8y12

@CEBasile where is the source code all of the AIY debian packages?  It's not in this project, right?

@HeatfanJohn This is just the python framework. The drivers are another repo. Look at HACKING.md

@CEBasile I see the reference to add the AIY vision package repo and I downloaded https://dl.google.com/aiyprojects/deb/dists/stable/Release to see the Debian release information:
Origin: Google LLC
Label: Google
Suite: stable
Codename: stable
Version: 1.0
Date: Fri, 19 Apr 2019 18:38:23 UTC
Architectures: armhf
Components: main
Description: Google AIY software repository
MD5Sum:
 7206381e7c543d5beb3272c52f6dff97 9183 main/binary-armhf/Packages
 7e0f0653397e626c7840c148722ea824 2840 main/binary-armhf/Packages.gz
 a0001a8b1dbdcd88b01d07009f8c3d8f 142 main/binary-armhf/Release
SHA1:
 01e66fff79dd958f5924f9d8057b16d1af9c3690 9183 main/binary-armhf/Packages
 83e85ca2e0f73c88c912eae473c6bfba22b3e726 2840 main/binary-armhf/Packages.gz
 bd6f1274a87b14ffcd4b110e1a3dc0cb60cf38eb 142 main/binary-armhf/Release
SHA256:
 5a01c5d0b68d0480c24daeafa42758e49eaafe6a009eebf4a4dd094caaf2fb23 9183 main/binary-armhf/Packages
 91a11fca702324b79486edef9cefe0b53e62c0eee69dfed7f0207e3a5ca4f913 2840 main/binary-armhf/Packages.gz
 5e600eb82427bc30bf6b1abdca202eb0413c1e41247d1891ef57a4c23bc55806 142 main/binary-armhf/Release

And then downloaded the package information https://dl.google.com/aiyprojects/deb/dists/stable/main/binary-armhf/Packages
But that only shows the deb locations.  Where / how do you find the source code?  Or is the source code included in the deb files?

sudo dkms install aiy/1.1

Tried doing that
`Kernel preparation unnecessary for this kernel.  Skipping...
Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.19.58-v7l+ -C /lib/modules/4.19.58-v7l+/build M=/var/lib/dkms/aiy/1.1/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.58-v7l+ (armv7l)
Consult /var/lib/dkms/aiy/1.1/build/make.log for more information.
`
no go there

Just wanted to let everyone know that downgrading to kernel 4.7 fixes these issues. Currently working on fixing this for kernel 4.19.66


Please share more information about internal EF Core reverse engineering services.

One of the greatest features you can find in EF Core is Scaffolding.
We can use this via the following command as a sample:
dotnet ef dbcontext scaffold "Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=Chinook" Microsoft.EntityFrameworkCore.SqlServer

Iد some scenarios like CI/CD integration We need to work with reverse engineering APIs directly instead of passing arguments to the command line system. (Less trouble/better performance)
You can find an article show us the way here.

Warning: Internal Services In Use
In EF Core everything is public, including all the inner workings of EF that would historically have been internal. We did this so that folks that really want to mess around with internal services can do so without using reflection.
We put these services into *.internal namespaces and reserve the right to break the APIs at any point. This code listing uses a number of these services – so be aware that future versions of EF may break this code.

As outlined in the article, this information is outdated for future releases.
I hope your documentation will be up-to-date on this information as well.
How can we use reverse engineering APIs instead of the command line way with the latest version of EF Core?
It can be an interesting subject for your documentation to be more complete.

I have some sample 2.x code here! https://github.com/ErikEJ/EFCorePowerTools/blob/21e4e5be1de5cae06187aebb4e701eeddcdb9443/src/GUI/ReverseEngineer20/EFCoreReverseEngineer.cs#L36

How can we use reverse engineering APIs instead of the command line way with the latest version of EF Core?

Scaffolding at runtime is not a good idea from customer perspective. If you are writing a tool which uses EF Scaffolding then please file a product issue if you are running into issues or need to use internal API. There is nothing actionable to document here as the warning says, use .Internal APIs at your own risk.


Rethink binary distribution

Figure out a way to build static linux bin
Signed binaries, built locally

That would be great! I have created a docker image until then: https://github.com/kapolos/docker-mysteryshack

We cannot distribute binaries without adding all licenses of all dependencies.


[Java bindings] Improve javadoc + update dependencies

We create a javadoc jar when we package the java bindings in https://github.com/ConsenSys/jc-kzg-4844 , so it would be useful to run the javadoc task as part of the check.
Added some small comments to few fields + a rename in the binding to be consistent
Updated dependencies (gradle + plugins)

Thanks, looks good.


Fix Disabled test

what

Update testing of enabled = false
Fix Makefile to run all tests
Update git.io -> cloudposse.tools

why

Proper test structure
Was running only a single test even when multiple tests were present
EOL for git.io

/test all


panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x0]

Hi, I have built etcd and flannel on my system. I have setup etcd cluster too ( two VMs ). When i am running running ./flanneld -iface=eth0 &, i am getting "panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x0]".  My OS is Ubuntu 15.10 .
etcd log on first node
root@ubuntu:/home/etcd# bin/etcd -name infra0 -initial-advertise-peer-urls http://<IP_ADDRESS>:2380   -listen-peer-urls http://<IP_ADDRESS>:2380   -listen-client-urls http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:2379   -advertise-client-urls http://<IP_ADDRESS>:2379   -initial-cluster-token etcd-cluster-1   -initial-cluster infra0=http://<IP_ADDRESS>:2380,infra2=http://<IP_ADDRESS>:2380 --election-timeout 1000 --heartbeat-interval 150  -initial-cluster-state new
2015/10/20 06:16:22 etcd: no data-dir provided, using default data-dir ./infra0.etcd
2015/10/20 06:16:22 etcd: listening for peers on http://<IP_ADDRESS>:2380
2015/10/20 06:16:22 etcd: listening for client requests on http://<IP_ADDRESS>:2379
2015/10/20 06:16:22 etcd: listening for client requests on http://<IP_ADDRESS>:2379
2015/10/20 06:16:22 etcdserver: datadir is valid for the 2.0.1 format
2015/10/20 06:16:22 etcdserver: name = infra0
2015/10/20 06:16:22 etcdserver: data dir = infra0.etcd
2015/10/20 06:16:22 etcdserver: member dir = infra0.etcd/member
2015/10/20 06:16:22 etcdserver: heartbeat = 150ms
2015/10/20 06:16:22 etcdserver: election = 900ms
2015/10/20 06:16:22 etcdserver: snapshot count = 10000
2015/10/20 06:16:22 etcdserver: advertise client URLs = http://<IP_ADDRESS>:2379
2015/10/20 06:16:22 etcdserver: initial advertise peer URLs = http://<IP_ADDRESS>:2380
2015/10/20 06:16:22 etcdserver: initial cluster = infra0=http://<IP_ADDRESS>:2380,infra2=http://<IP_ADDRESS>:2380
2015/10/20 06:16:22 etcdserver: start member 8d495f0a22da5e in cluster ecde20d529f1eba0
2015/10/20 06:16:22 raft: 8d495f0a22da5e became follower at term 0
2015/10/20 06:16:22 raft: newRaft 8d495f0a22da5e [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/10/20 06:16:22 raft: 8d495f0a22da5e became follower at term 1
2015/10/20 06:16:22 etcdserver: added local member 8d495f0a22da5e [http://<IP_ADDRESS>:2380] to cluster ecde20d529f1eba0
2015/10/20 06:16:22 etcdserver: added member c61e2a519a899a7f [http://<IP_ADDRESS>:2380] to cluster ecde20d529f1eba0
2015/10/20 06:16:23 raft: 8d495f0a22da5e is starting a new election at term 1
2015/10/20 06:16:23 raft: 8d495f0a22da5e became candidate at term 2
2015/10/20 06:16:23 raft: 8d495f0a22da5e received vote from 8d495f0a22da5e at term 2
2015/10/20 06:16:23 raft: 8d495f0a22da5e [logterm: 1, index: 2] sent vote request to c61e2a519a899a7f at term 2
2015/10/20 06:16:23 raft: 8d495f0a22da5e received vote from c61e2a519a899a7f at term 2
2015/10/20 06:16:23 raft: 8d495f0a22da5e [q:2] has received 2 votes and 0 vote rejections
2015/10/20 06:16:23 raft: 8d495f0a22da5e became leader at term 2
2015/10/20 06:16:23 raft.node: 8d495f0a22da5e elected leader 8d495f0a22da5e at term 2
2015/10/20 06:16:24 etcdserver: published {Name:infra0 ClientURLs:[http://<IP_ADDRESS>:2379]} to cluster ecde20d529f1eba0

etcd log on second node
root@ubuntu:/home/etcd# bin/etcd -name infra2 -initial-advertise-peer-urls http://<IP_ADDRESS>:2380   -listen-peer-urls http://<IP_ADDRESS>:2380   -listen-client-urls http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:2379   -advertise-client-urls http://<IP_ADDRESS>:2379   -initial-cluster-token etcd-cluster-1   -initial-cluster infra0=http://<IP_ADDRESS>:2380,infra2=http://<IP_ADDRESS>:2380 --election-timeout 1000 --heartbeat-interval 150  -initial-cluster-state new
2015/10/20 06:16:23 etcd: no data-dir provided, using default data-dir ./infra2.etcd
2015/10/20 06:16:23 etcd: listening for peers on http://<IP_ADDRESS>:2380
2015/10/20 06:16:23 etcd: listening for client requests on http://<IP_ADDRESS>:2379
2015/10/20 06:16:23 etcd: listening for client requests on http://<IP_ADDRESS>:2379
2015/10/20 06:16:23 etcdserver: datadir is valid for the 2.0.1 format
2015/10/20 06:16:23 etcdserver: name = infra2
2015/10/20 06:16:23 etcdserver: data dir = infra2.etcd
2015/10/20 06:16:23 etcdserver: member dir = infra2.etcd/member
2015/10/20 06:16:23 etcdserver: heartbeat = 150ms
2015/10/20 06:16:23 etcdserver: election = 900ms
2015/10/20 06:16:23 etcdserver: snapshot count = 10000
2015/10/20 06:16:23 etcdserver: advertise client URLs = http://<IP_ADDRESS>:2379
2015/10/20 06:16:23 etcdserver: initial advertise peer URLs = http://<IP_ADDRESS>:2380
2015/10/20 06:16:23 etcdserver: initial cluster = infra0=http://<IP_ADDRESS>:2380,infra2=http://<IP_ADDRESS>:2380
2015/10/20 06:16:23 etcdserver: start member c61e2a519a899a7f in cluster ecde20d529f1eba0
2015/10/20 06:16:23 raft: c61e2a519a899a7f became follower at term 0
2015/10/20 06:16:23 raft: newRaft c61e2a519a899a7f [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2015/10/20 06:16:23 raft: c61e2a519a899a7f became follower at term 1
2015/10/20 06:16:23 etcdserver: added member 8d495f0a22da5e [http://<IP_ADDRESS>:2380] to cluster ecde20d529f1eba0
2015/10/20 06:16:23 etcdserver: added local member c61e2a519a899a7f [http://<IP_ADDRESS>:2380] to cluster ecde20d529f1eba0
2015/10/20 06:16:23 raft: c61e2a519a899a7f [term: 1] received a MsgVote message with higher term from 8d495f0a22da5e [term: 2]
2015/10/20 06:16:23 raft: c61e2a519a899a7f became follower at term 2
2015/10/20 06:16:23 raft: c61e2a519a899a7f [logterm: 1, index: 2, vote: 0] voted for 8d495f0a22da5e [logterm: 1, index: 2] at term 2
2015/10/20 06:16:24 raft.node: c61e2a519a899a7f elected leader 8d495f0a22da5e at term 2
2015/10/20 06:16:24 rafthttp: starting client stream to 8d495f0a22da5e at term 2
2015/10/20 06:16:24 etcdserver: published {Name:infra2 ClientURLs:[http://<IP_ADDRESS>:2379]} to cluster ecde20d529f1eba0

Now i ran flanneld on my first node
root@ubuntu:/home/flannel/bin# ./flanneld -iface=eth0 &
[1] 4992
root@ubuntu:/home/flannel/bin# I1020 05:59:13.897450 04992 main.go:275] Installing signal handlers
I1020 05:59:13.899223 04992 main.go:189] Using <IP_ADDRESS> as external interface
go-etcd2015/10/20 05:59:13 DEBUG: get /coreos.com/network/config [http://<IP_ADDRESS>:2379]
go-etcd2015/10/20 05:59:13 DEBUG: Connecting to etcd: attempt 1 for keys/coreos.com/network/config?quorum=false&recursive=false&sorted=false
go-etcd2015/10/20 05:59:13 DEBUG: send.request.to http://<IP_ADDRESS>:2379/v2/keys/coreos.com/network/config?quorum=false&recursive=false&sorted=false | method GET
go-etcd2015/10/20 05:59:13 DEBUG: recv.response.from
go-etcd2015/10/20 05:59:13 DEBUG: recv.success
go-etcd2015/10/20 05:59:13 DEBUG: get /coreos.com/network/config [http://<IP_ADDRESS>:2379]
go-etcd2015/10/20 05:59:13 DEBUG: Connecting to etcd: attempt 1 for keys/coreos.com/network/config?quorum=false&recursive=false&sorted=false
go-etcd2015/10/20 05:59:13 DEBUG: send.request.to http://<IP_ADDRESS>:2379/v2/keys/coreos.com/network/config?quorum=false&recursive=false&sorted=false | method GET
go-etcd2015/10/20 05:59:13 DEBUG: recv.response.from
go-etcd2015/10/20 05:59:13 DEBUG: recv.success
go-etcd2015/10/20 05:59:13 DEBUG: get /coreos.com/network/subnets [http://<IP_ADDRESS>:2379]
go-etcd2015/10/20 05:59:13 DEBUG: Connecting to etcd: attempt 1 for keys/coreos.com/network/subnets?quorum=false&recursive=true&sorted=false
go-etcd2015/10/20 05:59:13 DEBUG: send.request.to http://<IP_ADDRESS>:2379/v2/keys/coreos.com/network/subnets?quorum=false&recursive=true&sorted=false | method GET
go-etcd2015/10/20 05:59:13 DEBUG: recv.response.from
go-etcd2015/10/20 05:59:13 DEBUG: recv.success
I1020 05:59:13.902897 04992 etcd.go:136] Found lease (<IP_ADDRESS>/24) for current IP (<IP_ADDRESS>), reusing
go-etcd2015/10/20 05:59:13 DEBUG: put /coreos.com/network/subnets/<IP_ADDRESS>-24, {"PublicIP":"<IP_ADDRESS>"}, ttl: 86400, [http://<IP_ADDRESS>:2379]
go-etcd2015/10/20 05:59:13 DEBUG: Connecting to etcd: attempt 1 for keys/coreos.com/network/subnets/<IP_ADDRESS>-24
go-etcd2015/10/20 05:59:13 DEBUG: send.request.to http://<IP_ADDRESS>:2379/v2/keys/coreos.com/network/subnets/<IP_ADDRESS>-24 | method PUT
go-etcd2015/10/20 05:59:14 DEBUG: recv.response.from
go-etcd2015/10/20 05:59:14 DEBUG: recv.success
I1020 05:59:14.016817 04992 etcd.go:91] Subnet lease acquired: <IP_ADDRESS>/24
I1020 05:59:14.018867 04992 udp.go:222] Watching for new subnet leases
go-etcd2015/10/20 05:59:14 DEBUG: get /coreos.com/network/subnets [http://<IP_ADDRESS>:2379]
go-etcd2015/10/20 05:59:14 DEBUG: Connecting to etcd: attempt 1 for keys/coreos.com/network/subnets?quorum=false&recursive=true&sorted=false
go-etcd2015/10/20 05:59:14 DEBUG: send.request.to http://<IP_ADDRESS>:2379/v2/keys/coreos.com/network/subnets?quorum=false&recursive=true&sorted=false | method GET
go-etcd2015/10/20 05:59:14 DEBUG: recv.response.from
go-etcd2015/10/20 05:59:14 DEBUG: recv.success
I1020 05:59:14.020343 04992 udp.go:247] Subnet added: <IP_ADDRESS>/24
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0]

goroutine 28 [running]:
udp.setRoute
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/cproxy.go:66
github_com_coreos_flannel_backend_udp.processSubnetEvents.pN48_github_com_coreos_flannel_backend_udp.UdpBackend
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:249
github_com_coreos_flannel_backend_udp.monitorEvents.pN48_github_com_coreos_flannel_backend_udp.UdpBackend
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:235
github_com_coreos_flannel_backend_udp.Run.pN48_github_com_coreos_flannel_backend_udp.UdpBackend
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:141
network.$nested4
	/home/flannel/gopath/src/github.com/coreos/flannel/network/network.go:109
created by github_com_coreos_flannel_network.Run.pN41_github_com_coreos_flannel_network.Network
	/home/flannel/gopath/src/github.com/coreos/flannel/network/network.go:108

goroutine 16 [chan receive]:
main.main
	/home/flannel/gopath/src/github.com/coreos/flannel/main.go:288

goroutine 18 [finalizer wait]:
created by runtime_createfing
	../../../src/libgo/runtime/mgc0.c:2572

goroutine 19 [syscall]:
	goroutine in C code; stack unavailable
created by os_signal..import
	../../../src/libgo/go/os/signal/signal_unix.go:25

goroutine 20 [chan receive]:
github_com_coreos_flannel_Godeps__workspace_src_github_com_golang_glog.flushDaemon.pN79_github_com_coreos_flannel_Godeps__workspace_src_github_com_golang_glog.loggingT
	/home/flannel/gopath/src/github.com/coreos/flannel/Godeps/_workspace/src/github.com/golang/glog/glog.go:839
created by glog.$init0
	/home/flannel/gopath/src/github.com/coreos/flannel/Godeps/_workspace/src/github.com/golang/glog/glog.go:406

goroutine 24 [chan receive]:
github_com_coreos_flannel_network.Run.pN41_github_com_coreos_flannel_network.Network
	/home/flannel/gopath/src/github.com/coreos/flannel/network/network.go:113
main.$nested2
	/home/flannel/gopath/src/github.com/coreos/flannel/main.go:217
created by main.initAndRun
	/home/flannel/gopath/src/github.com/coreos/flannel/main.go:199

goroutine 26 [IO wait]:
net.runtime_pollWait
	../../../src/libgo/runtime/netpoll.goc:151
net.Wait.pN12_net.pollDesc
	../../../src/libgo/go/net/fd_poll_runtime.go:84
net.WaitRead.pN12_net.pollDesc
	../../../src/libgo/go/net/fd_poll_runtime.go:89
net.Read.pN9_net.netFD
	../../../src/libgo/go/net/fd_unix.go:242
net.Read.pN8_net.conn
	../../../src/libgo/go/net/net.go:121
net.Read.pN11_net.TCPConn
	../../../src/libgo/go/net/tcpsock_posix.go:57
net_http.Read.N22_net_http.noteEOFReader
	../../../src/libgo/go/net/http/transport.go:1270
bufio.fill.pN12_bufio.Reader
	../../../src/libgo/go/bufio/bufio.go:97
bufio.Peek.pN12_bufio.Reader
	../../../src/libgo/go/bufio/bufio.go:132
net_http.readLoop.pN20_net_http.persistConn
	../../../src/libgo/go/net/http/transport.go:842
created by net_http.dialConn.pN18_net_http.Transport
	../../../src/libgo/go/net/http/transport.go:660

goroutine 27 [select]:
net_http.writeLoop.pN20_net_http.persistConn
	../../../src/libgo/go/net/http/transport.go:945
created by net_http.dialConn.pN18_net_http.Transport
	../../../src/libgo/go/net/http/transport.go:661

goroutine 29 [syscall]:
	goroutine in C code; stack unavailable
created by github_com_coreos_flannel_backend_udp.Run.pN48_github_com_coreos_flannel_backend_udp.UdpBackend
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:131

goroutine 30 [select]:
github_com_coreos_flannel_subnet.LeaseRenewer
	/home/flannel/gopath/src/github.com/coreos/flannel/subnet/renew.go:32
udp.$nested1
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:137
created by github_com_coreos_flannel_backend_udp.Run.pN48_github_com_coreos_flannel_backend_udp.UdpBackend
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:136

goroutine 31 [select]:
github_com_coreos_flannel_subnet.watchSubnets.pN51_github_com_coreos_flannel_subnet.etcdSubnetRegistry
	/home/flannel/gopath/src/github.com/coreos/flannel/subnet/registry.go:151
github_com_coreos_flannel_subnet.WatchLeases.pN44_github_com_coreos_flannel_subnet.EtcdManager
	/home/flannel/gopath/src/github.com/coreos/flannel/subnet/etcd.go:313
github_com_coreos_flannel_subnet.WatchLeases
	/home/flannel/gopath/src/github.com/coreos/flannel/subnet/watch.go:33
udp.$nested2
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:228
created by github_com_coreos_flannel_backend_udp.monitorEvents.pN48_github_com_coreos_flannel_backend_udp.UdpBackend
	/home/flannel/gopath/src/github.com/coreos/flannel/backend/udp/udp.go:227

goroutine 33 [runnable]:
created by github_com_coreos_flannel_subnet.watchSubnets.pN51_github_com_coreos_flannel_subnet.etcdSubnetRegistry
	/home/flannel/gopath/src/github.com/coreos/flannel/subnet/registry.go:129

can i know, what is going wrong..
My network config file is
etcdctl mk /coreos.com/network/config '{"Network":"<IP_ADDRESS>/16"}'

@sujitfulse what commit did you build flannel from?

i was building with old commit. just now i cloned it with latest commit and it solved this problem. apologies .
root@ubuntu:/home/temp/flannel# git log -n2
commit 86ec8945474a159f20dbc6128f53b19471129aa3
Merge: 9889a4d 878c525
Author: Eugene Yakubovich<EMAIL_ADDRESS>Date:   Sun Oct 18 15:06:37 2015 -0700


Get a publishing unit ID

I followed the following to implement native advance ads.

https://support.google.com/admob/answer/7187428?hl=en
https://developers.google.com/admob/android/native-advanced

Everything is working fine. But, currently I'm using the test unit ID and I can't find any information on how to create a native advance ad in AdMob accept the first link above (Line 6 in that link is not there). The only options that are giving is banner, Interstitial and Rewarded.
So what unit Id should I use when releasing my application?
I have asked groups.google.com and on stackoverflow, with no answers. Here is the link to that

https://stackoverflow.com/questions/47693005/adding-native-advance-admob-ad
https://groups.google.com/forum/#!category-topic/google-admob-ads-sdk/android/h_AUSMQhk48

OK... After some research I have found that native advance is STILL in beta and only available to a small group of publishers, the VIP's if you will.
With native express discontinued and stop serving ads on 1 March 2018 I would have thought that AdMob would make native advance available to all publishers. Unfortunately that is not the case.
AND.. There is no way of contacting them and no info on when Native Advanced will be made available to all publishers.
So, I'm sorry Google AdMob but I will have to look at other options.. Time is money ;)

I tried to integrate admob to this sample app, but it doesn't worked as expected. Can anyone help me in integrating admob(both banner and interstitial ad ) with this app ?


Support pandas' category type in scans and append

Dear Mark and Hannes,
based on a suggestion by @larsrinn to use categorical operations, we are looking into supporting the Pandas category type at https://github.com/earthobservations/wetterdienst/issues/226.
When trying to go forward on this, @gutzbenj received:
df = duckdb.query(self.df, "data", sql).df()
E       RuntimeError: unsupported python type category

I don't know whether there is a chance to improve this as quickly as #959? I don't quite dare to ask.... ;]
With kind regards,
Andreas.
P.S.: Maybe Benjamin will be able to provide a concise MRE like pandas_duckdb_test.py.

I've just added a concise MRE at pandas_duckdb_category_unsupported.py.

Thanks for the example! Will have a look at implementing this tomorrow.

This should be fixed in the master now, @amotl can you have a look to see if it works as expected?

Dear Mark,
thank you. Again, that was really quick. I can confirm this does not raise any runtime error anymore.
I believe the fact that DuckDB will not be able to fully roundtrip Pandas data types is by design? Sorry for my naive statement in this regard ;].
So, just for the sake of completeness: When amending duckdb_pandas_category.py to expect an int64 type and an object type to be returned from the DuckDB query, everything works as expected.
In turn, the in- and out-dataframes will be identical when amending the former one before comparison like
df_in["int"] = df_in["int"].astype("int64")
df_in["string"] = df_in["string"].astype("object")

I believe this is totally fine. What do you think, @gutzbenj?
Thank you so much again and with kind regards,
Andreas.

No problem! Let me know if you run into any further issues :)

I believe the fact that DuckDB will not be able to fully roundtrip Pandas data types is by design? Sorry for my naive statement in this regard ;].

DuckDB currently only returns "simple" arrays (i.e. NumPy arrays) when converting back to Python. Perhaps we will return category arrays there in the future, but there is no guarantee the type of the array will be the same as what was put into the system. (i.e. round-trip compatibility is not guaranteed).
Pandas has a weird type system where there is a mix between the logical type (i.e. what is stored in the column, such as integers or strings) and the physical representation of that type (e.g. NumPy array, categorical, etc). DuckDB will maintain the logical type, but not the physical representation.
It would be possible to add other functions such as e.g. as_category, that would output a category array instead of a NumPy array for a specific column, but this is then specified by the user when fetching the result, and not related to what was put into the system.

Thanks for the elaboration on this topic. I recognize being fully roundtrippable wrt. Pandas is not the scope of DuckDB. Adding convenience functions like as_category as we go might make sense, but we can well let this be the obligation of the user for a while.
Thanks again for your responsiveness. Cheers!


fix Accordion as per design

resolves : https://github.com/optimizely-axiom/optiaxiom/issues/180

Keeping it for future design instruction.
https://github.com/radix-ui/primitives/discussions/583


fix coveralls report

We see quite some fails #892-#904, let's fix that

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
802 unchanged lines in 20 files lost coverage.
Overall coverage decreased (-11.05%) to 78.253%

Files with Coverage Reduction
New Missed Lines
%

straxen/plugins/acqmon_processing.py
1
87.5%

straxen/numbafied_scipy.py
2
87.5%

straxen/common.py
6
86.85%

straxen/scada.py
8
76.69%

straxen/plugins/veto_veto_regions.py
9
82.69%

straxen/url_config.py
11
87.15%

straxen/plugins/led_calibration.py
15
85.71%

straxen/plugins/event_processing.py
16
90.63%

straxen/analyses/records_matrix.py
20
58.21%

straxen/plugins/daqreader.py
21
80.23%

Totals

Change from base Build<PHONE_NUMBER>:
-11.05%

Covered Lines:
5653

Relevant Lines:
7224

💛  - Coveralls


Cannot handle fractions of a second (and potentially other fractions)

If I get some free time I'll take a look at it myself.
should output 1h 2m with input PT3723.14159S:
    Error: Unexpected duration format. Refer to ISO 8601.
     at new Duration (node_modules/durationjs/js/duration.js:49:11)

Per Wikipedia (https://en.wikipedia.org/wiki/ISO_8601)

The smallest value used may also have a decimal fraction, as in “P0.5Y” to indicate half a year. This decimal fraction may be specified with either a comma or a full stop, as in “P0,5Y” or “P0.5Y”.

I'm part way through this PR #15 but haven't sorted out the karma tests yet