add a utility class to switch between epoll and nio

Motivation:
Currently, user have to manual decide to use either epoll or nio.
add a utility class so switch to epoll when it is available.
Modifications:
add a new utility class to switch between epoll and nio
Result:
add a utility class to switch between epoll and nio

@brandonJY you are not the first: #6873, #7302, #8901
I personally think something like this would have great value. It's been suggested to postpone to netty 5 but I'm not not sure why it couldn't be added to 4.1 in a minimally-invasive/backwards-compatible way.
A configurable factory along the lines of what's proposed in #6873 seems like the best approach to me though. Really just a helper to make it easy to configure channels in an impl-agnostic way, where by default it will use native transports when available and default to NIO otherwise. Pretty much everyone does this themselves otherwise, and those who don't likely aren't aware of the perf benefits they're missing out on.

@njhill Hi Nick,  thanks a lot! Now I see the previous PRs. Not sure how I missed them when I did the search.
Yeah, I would aggree with you that #6873 would be a way to go if we want.
Closing this PR for now.


5341: Fixes upload bug

I cannot merge this as I do not have write permission. Can someone give me permission? Thanks!


Remove mapping types

As part of v2.0 release, mapping types are getting removed from OpenSearch engine. Below are the changes in the opensearch-engine.

Removal of type from rest end-points
Removal of include_type_name parameter from API requests.

As part of this issue, please verify if type removal change on OpenSearch engine impacts this repository. If yes, then please remove the type references/usage from this repository
Top level changes are captured in gist below:
https://gist.github.com/dreamer-89/d76eaf639171e8ab32fa7f8b9d6c93d3
For more detailed changes, please check meta issue below:
Related: OpenSearch-engine meta issue

This change goes in v2.0.0 release in OpenSearch repository and is a breaking change. Request maintainer to add appropriate labels.

I looked into this repository source code but did not find any usages of mapping types. @samuel-oci : can you please have a look and confirm ?

Hi @dreamer-89 will check and confirm, should be back shortly with an answer.

Confirmed that mapping types are not used in this repository code.


Add ram_role_node to ecs_intance graph and ecs_instance_node to ram_role graph

Closed by https://github.com/turbot/steampipe-mod-alicloud-insights/pull/77


Error: Cannot find module './freezeObject.js'

Hi community :)
I have an error :
Error: Cannot find module './freezeObject.js'
at Object. (....../node_modules/cesium/Source/Core/defaultValue.js:1)
var gltfPipeline = require('gltf-pipeline'),
    fs = require('fs');

var file = fs.readFileSync('./test/sample/dev/gltf/sample/cube_textGPU.gltf')
    processGltf = gltfPipeline.processGltf,
    gltfJSON = JSON.parse(file),
    options = {
        dracoOptions: {
            compressionLevel: 7
        }
    };

processGltf(gltfJSON, options).then( (results) => {
        fs.appendFileSync('./test/sample/dev/gltf/sample/cube_textGPU.gltf', results.gltf);
});

Can you help me please ?

It seem we must to install it globally (-g).
No way to install it locally in node_module project directory ?

@pierreglibert what version of gltf-pipeline are you using? If you're using the npm package try using 2.1.8. Otherwise if you're running from source delete your node_modules directory and run npm install.
The error you're seeing is due to a change in cesium, one of gltf-pipeline's dependencies. It should be fixed once you update with either of the two approaches above.

Hi @lilleyse ,
Thanks, it works :)
I already had 2.1.8 ... I just remove the node_module directory and reinstall all dep.
Have a nice day,
Pierre.


materiel.net wrong blacklist

Hi @Loopingo - this domain is on the whitelist (https://github.com/409H/EtherAddressLookup/commit/56feecb5875f5f27e879e9963525a27f83f6fddb#diff-659de00b3e94ab4599c3932e1ec2b6b1)
Is EAL still redirecting you away from materiel[dot]net? I can't replicate the issue on my end.

Hi @Loopingo - I believe I've fixed the issue now, apologies for that.
I'll better improve the whitelist over the coming days so it shouldn't happen again - the issue was the www. subdomain not being whitelisted.
I'll leave this issue open for a couple days in case you have any more issues.

Hi @409H,
Thank you, the issue is fixed now.


Refactored SVGSaver class and added tests + documentations

Added method to automatically change file extension to .svg when saving
Added documentations to class SVGSaver
Added tests for SVGSaver

Let's not automatically change the file extension. We should assume that the user knows best.

Please use Jimfs for you tests and I'll merge.

Please fix your commit message so that it closes issue #82.

I'll merge after the commit's fixed.


HDMI not working.

Is there a way to solve this problem?

Not that I know of. I'll keep working on it. Do let me know if you find a solution to this!

I tried a lot, but it still doesn’t work. Is there no solution?

I might get a solution @Yanshuaibing. Stay tuned for updates.

Waiting for your updates @AniKulkarn  , in first time my E4 runnings ok with your efi, but last times freezing at verbose startup and after login mouse freeze and all computer...

Waiting for your updates @AniKulkarn , in first time my E14 runnings ok with your efi, but last times freezing at verbose startup and after login mouse freeze and all computer...

My EFI partition is not to be used as is. You need to put your own generated serial number and personalised details. Also, did you verify that my ThinkPad E14 and yours have the exact same configuration?

How about this solution?
https://www.reddit.com/r/hackintosh/comments/hu46xm/fix_hdmi_port_and_possibly_others_not_working_on/

How about this solution?
https://www.reddit.com/r/hackintosh/comments/hu46xm/fix_hdmi_port_and_possibly_others_not_working_on/

Thanks for sharing! I'll try this.

@AniKulkarn did it worked?

any update ?

Nope, i bought macbook 😄


feat: Nuxt Layers + Oruga

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] POC to test Nuxt Layers + Oruga

Did your issue had any of the "$" label on it?

[ ] My DOT address: Payout

wait what? how will you handle style customization?

Since Nuxt Layers is basically a Nuxt App, we can follow their guidelines for customization: https://oruga.io/documentation/themes.html
in cf4c834, I override the $primary variable. you can check the Tabs component on the gallery detail page

Looks like font does not load as before.. imo this could introduce so many breaking changes.
I get the impression that you're embarking on a development that's far too long and won't really improve the dev experience.
Plus I don't really get the point of using nuxt layer as another internal workspace, I might need to read more ressource about that one.

Looks like font does not load as before.. imo this could introduce so many breaking changes.
I get the impression that you're embarking on a development that's far too long and won't really improve the dev experience.
Plus I don't really get the point of using nuxt layer as another internal workspace, I might need to read more ressource about that one.

no worries, this PR only POC. so anyone feel free to replies with agreement/disagrement
for font, it's replaced also to 'monospace' under $primary variable
if the extends/mixins is works, i would go with that approach instead. since currently we can't use that anymore, NeoButton approach is not so straightforward, imo. because need to reimplement the components structure again (pass the props, readd the slot, and some cases. not checked yet about programmatically use case for modal/notification). not only customization


xarray tutorial at SciPy 2018?

It would be great to hold an xarray tutorial at SciPy 2018. Xarray has matured a lot recently, and it would be great to raise awareness of what it can do among the broader scipy community.
From the conference website:

Tutorials should be focused on covering a well-defined topic in a hands-on manner. We want to see attendees coding! We encourage submissions to be designed to allow at least 50% of the time for hands-on exercises even if this means the subject matter needs to be limited. Tutorials will be 4 hours in duration. In your tutorial application, you can indicate what prerequisite skills and knowledge will be needed for your tutorial, and the approximate expected level of knowledge of your students (i.e., beginner, intermediate, advanced).

I'm curious if anyone was already planning on submitting a tutorial. If not, let's put together a team. @jhamman has indicated interest in participating in, but not leading, the tutorial. Anyone else interested?
xref pangeo-data/pangeo#97

I plan to attend SciPy this year and I'd be happy to join in.

What is needed is someone to lead the tutorial team (including submitting the application). You will clearly have help from @jhamman and @benbovy in presenting the tutorial. You will also get a stipend of $1000!
I can't volunteer because I'm not sure I'll even be able to attend the conference.

If I can get some help putting together the materials, I can lead tutorial. @kmpaul and I are already preparing an Xarray tutorial for April (link) so really we just need to adapt what we come up with for that to be useful for Scipy.

I would be happy to assist.  I have asked for travel funds to attend SciPy this year, but have not yet gotten approval.  Even if I can't go I could assist with review of materials if you are interested in feedback. If I can go, I could certainly work as a tutorial helper.

Although not active on the Xarray github, I am an early adopter and active user of the software and am looking for a good excuse to go to scipy for the first time ...I would be glad to assist!

I submitted an abstract for an xarray tutorial today. More information to come as we get closer to the conference but for now the title: Xarray for Scalable Scientific Data Analysis. Stay tuned!

Xarray for Scalable Scientific Data Analysis

Nice title!
I know xarray has its origins and most of its current users in the earth science domains, and so I would expect much of the core of an xarray tutorial to involve various geo* flavored data, but since SciPy has attendees from so many different backgrounds it could be useful to try to survey the scope of work being done with xarray right now. I imagine there must be other users in astronomy, physics, biology and perhaps even quantitative civics/demography that could have interesting snippets to share.
For my part, I am using xarray to work with microscopy data in a biological context, and would be happy to share a snippet or two.

I don't think xarray has caught on in astronomy and I'm curious why. From an outsider's perspective, it seems ideal for astronomy data.
Maybe because they already have things like astropy and yt?

@jakevdp - do you know of any astronomy applications of xarray?

I've not seen any... I think the main reason is that the field embraced Python years before xarray was created, so there were already workable solutions in place.

My colleague in astronomy said that his common data format was a set of few images taken with long exposure time and he didn't need to take care of big data until recently. I am not sure it is generally true for astronomy field.
However, one of the recent streams in astrophysics is definitely the combination of the statistics and the huge amount of measurements, such as thousands of images constantly taken by telescopes. I suspect xarray could play more role also in this field (I am also an outsider though...).

For my part, I am working in the nuclear fusion field, where we have many kinds of high-dimensional measurement data. The size of each measurement is not so huge, but we have huge kinds of data taken on different coordinates. xarray also fits such situation.
(I am also happy to share my snippest but my data is not big and I am not sure this fits the tutorial concept.)
xarray certainly helps me a lot, but I don't hear any usages of xarray around me. It might be a historical reason (many are still using a comersial software  such as IDE). I think there is a certain market also in my field.

@jhamman will your tutorial at UCAR be available online at some point? Are you still planning to present at SciPy 2018? I'm not part of the dev team but I really think it would be great to have a proper video with a tutorial and the related repo. It would really help getting people aware of/excited about xarray!

@GiorgioBalestrieri - Yes. Both tutorials will be made available. Stay tuned!

Bummer Joe! It sounds like you had a great proposal, but maybe the instructions for the tutorial abstract weren’t clear enough in terms of the detail required.
We should not get discouraged and instead set our sights on other opportunities (including scipy 2019) for presenting xarray tutorials. Recent comments on the mailing list suggest that a comprehensive xarray tutorial is something our community really needs.
Sent from my iPhone

On Apr 1, 2018, at 11:23 PM, Joe Hamman<EMAIL_ADDRESS>wrote:
We heard over the weekend that the xarray tutorial was not selected for Scipy 2018. From reading the reviewer comments, it sounds like we (mostly I) did not provide a sufficient outline of topics to fully describe what the tutorial would cover. This seems mostly like a misunderstanding on my part as to the expected level of detail in the abstract.
In the hopes that we'll be able to get a slot for one of these in the next few years, I'll post both the abstract and review comments here.
Abstract:
Xarray provides data structures for N-dimensional labeled arrays and a toolkit for scalable data analysis on large, complex datasets with many related variables, such as those that occur in the disciplines of earth science, astronomy, and finance. Xarray combines the power of labeled data structures from Pandas, with the N-dimensional arrays from Numpy and parallel out-of-core computation from Dask, to provide an intuitive and powerful platform for scientific analysis of large multi-dimensional datasets.
This tutorial introduces data scientists who may already be familiar with Numpy or Pandas to the Xarray data model and tool kit. Following an introduction to Xarray, we will introduce tools for scaling real-world scientific data analysis workflows using Xarray and Dask. Students will leave this tutorial with 1) a comprehensive understanding of the Xarray data model, 2) the ability to apply the Xarray tool kit to analysis workflows that fit in memory, and 3) the ability to scale those same workflows to datasets that are much too large to fit into memory (GBs to TBs). Participants are expected to have some familiarity with Jupyter, Numpy, and Pandas.
Links: http://xarray.pydata.org, http://dask.pydata.org
Short Description of the Tutorial:
Xarray provides data structures for N-dimensional labeled arrays and a toolkit for scalable data analysis on large, complex datasets with many related variables. Xarray combines the power of labeled data structures from Pandas, with the N-dimensional arrays from Numpy and parallel out-of-core computation from Dask, to provide an intuitive and powerful platform for scientific analysis of large multi-dimensional datasets. This tutorial introduces data scientists who may already be familiar with Numpy or Pandas to the Xarray package. We will guide participants through the process of scaling Xarray computations from small to big data science workflows.
Review Comments:
Dear Joseph,
We didn't select your tutorial, "Xarray for Scalable Scientific Data Analysis", for SciPy 2018, but we would like to wholeheartedly thank you for your submission. The proposals were exceptionally good this year. We received 55 applications and had only 24 spots. We made our selection based on the reviewers' feedback and the likely popularity of the tutorial. We also made a few tough calls to ensure a good diversity of topics and presenters.
Below is the raw feedback from the reviewers who looked at your application. We hope it'll prove useful and we look forward to receiving another proposal from you next year.
Best regards,
Alex, Ben & Mike.
SciPy 2018 Tutorials Committee
----------------------- REVIEW 1 ---------------------
PAPER: 70
TITLE: Xarray for Scalable Scientific Data Analysis
AUTHORS: Joseph Hamman
I do not have a conflict of interest.: yes
Overall evaluation: 2 (accept)
What level of interest do you think this tutorial will generate?: 3 (Widespread appeal)
----------- Overall evaluation -----------
This seems like a very promising presentation quite apt for attendees of the SciPy conference about an underappreciated tool for scientific Python. It also seems like the proposer is well positioned to be the instructor for such a tutorial. However, I am concerned about the lack of specific information about what topics will be presented in what order and with what coding exercises and duration. I worry the proposer has not yet developed details about what would be presented. Right now this sounds more like an hour long tutorial than a 3 or 4 hour long tutorial. It would be good if the presented could develop a more detailed outline, also so that potential attendees have a better idea of what to expect.
----------------------- REVIEW 2 ---------------------
PAPER: 70
TITLE: Xarray for Scalable Scientific Data Analysis
AUTHORS: Joseph Hamman
I do not have a conflict of interest.: yes
Overall evaluation: 1 (weak accept)
What level of interest do you think this tutorial will generate?: 3 (Widespread appeal)
----------- Overall evaluation -----------
I don't have experience with xarray, but I believe that it is revolutionary software that will change how scientists use Python to analyze data. I spent way too much time doing nasty tricks with numpy to analyze hyperspectral data in my olden days as a scientist, and I'm convinced that xarray will save people that time today. I would really want past me to see this tutorial.
That said, this proposal needs much more detail. What's your time schedule? What example data will you use? What specific functionality of xarray will you be showing (and when), and how do these examples build on each other? Based on the author's background, I trust that this tutorial will turn out fine if it is accepted, but this proposal would be stronger with more detail. I'm recommending that this tutorial be accepted on the solid foundation of the xarray project, the value that I think that project presents, and some trust based on Joseph's background.
The setup instructions are good - I am excited that cloud-based JupyterHub will remove need of local installation. I do think for your local installation guide, you'd be better off specifying version ranges for each dependency, or a link to some environment specification file, in case APIs change between now and the conference.  Not a big deal - people can update or downgrade as necessary - just saves some confusion.
----------------------- REVIEW 3 ---------------------
PAPER: 70
TITLE: Xarray for Scalable Scientific Data Analysis
AUTHORS: Joseph Hamman
I do not have a conflict of interest.: yes
Overall evaluation: 2 (accept)
What level of interest do you think this tutorial will generate?: 3 (Widespread appeal)
----------- Overall evaluation -----------
This seems like a very strong tutorial, hopefully with broad appeal to both traditional and data scientists.
----------------------- REVIEW 4 ---------------------
PAPER: 70
TITLE: Xarray for Scalable Scientific Data Analysis
AUTHORS: Joseph Hamman
I do not have a conflict of interest.: yes
Overall evaluation: 1 (weak accept)
What level of interest do you think this tutorial will generate?: 3 (Widespread appeal)
----------- Overall evaluation -----------
I know there is interesting xarray and that it is playing playing a role in solving hard problems. I would have like to see a more detailed outline, with plans for exercises and timing information.
----------------------- REVIEW 5 ---------------------
PAPER: 70
TITLE: Xarray for Scalable Scientific Data Analysis
AUTHORS: Joseph Hamman
I do not have a conflict of interest.: yes
Overall evaluation: 1 (weak accept)
What level of interest do you think this tutorial will generate?: 3 (Widespread appeal)
----------- Overall evaluation -----------
XArray is a fantastic project, and I have been very interested in seeing it grow and gain wider acceptance. The tool can be tricky to use right, and the documentation can be sparse in some places. So, a tutorial would be extremely valuable here. However, the proposal in very lacking in details, which would make it difficult to judge whether or not there is a 4-hour tutorial (I am sure there is), but also makes it hard for a potential participant to judge whether this tutorial is for them or not.
Note: while I don't have a conflict of interest with the author, I am acknowledged in a paper about XArray as an early contributor.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm actually impressed by the quality and number of reviews, good for Scipy!
I feel particularly concerned about:

The tool can be tricky to use right, and the documentation can be sparse in some places.

I would hope to meliorate this whenever possible.


[WIP] Support x and y direction at same time (aka grid)

I've found some time to hack around in this addon and try to implement grid support. It's harder than I thought.. Don't review it, I leave this here so maybe someone else can maybe make it work. I don't have the time right now to dig into it more (deadlines..), maybe someone else will :+1:
This is related to #75

Thanks for taking a crack at it :) This is something I haven’t had the confidence or clarity to tackle.

@koemeet is this something you’re still interested in pursuing? If not, do you mind if I close this PR?

Is there any update about this one?

This project is now being maintained by the team at @heroku.
To get the project healthy and maintainable again, we’re doing a bit of spring cleaning of older issues and pull requests. This pull request hasn’t been touched in a while so we’re closing it.
Please feel free to re-open if you’d like to resume work on it.


MCPWM deadtime improvements

allow changing deadtime config after pin creation
constify DeadTimeCfg
fix some wrong bit values
remove some unsafe blocks

@MabezDev Ready for review

Thank you for your work on this!
Most of our maintainers are traveling this week, but we will get to this ASAP! If @MabezDev (or somebody else) does not get to this in the next couple days I will give it a review/test later this week, but I will be traveling over the next couple days as well.

All good!  Any errors related to variant() should now use bits() instead.

Sorry I missed the bit in @MabezDev's comment about variant, was going to rebase this (hence the change to the CHANGELOG.md) but I will not do that now 😁  Sorry for the noise!

Sorry, I made a mess of the commit log 😅

Any errors related to variant() should now use bits() instead.

Oh wow, that's unfortunate. Reading through the logs there seems to be a new set method to replace variant but it's only available for Safe fields.
https://github.com/rust-embedded/svd2rust/pull/829
Maybe our PACs can be updated to enable this in the future


[release-4.15]  USHIFT-2103: Add registry mirror to metal jobs

Manual cherry pick of PRs:

https://github.com/openshift/microshift/pull/2777
https://github.com/openshift/microshift/pull/2766
https://github.com/openshift/microshift/pull/2757
https://github.com/openshift/microshift/pull/2683

Which issue(s) this PR addresses:

Closes #

/retest-required

/test test-rebase

/label cherry-pick-approved

/lgtm


DCOS-41313: telling app tasks from pods tasks

Current strategy is not bulletproof.
Container of a pod can have the same task.name as a standalone service thus making it ambiguous.
With this PR I attempted to use task.id instead of task.name.
Testing
Services to launch:
{
  "id": "/nginx",
  "backoffFactor": 1.15,
  "backoffSeconds": 1,
  "container": {
    "portMappings": [],
    "type": "MESOS",
    "volumes": [],
    "docker": {
      "image": "nginx",
      "forcePullImage": false,
      "parameters": []
    }
  },
  "cpus": 0.1,
  "disk": 0,
  "instances": 2,
  "maxLaunchDelaySeconds": 300,
  "mem": 128,
  "gpus": 0,
  "networks": [
    {
      "name": "dcos",
      "mode": "container"
    }
  ],
  "requirePorts": false,
  "upgradeStrategy": {
    "maximumOverCapacity": 1,
    "minimumHealthCapacity": 1
  },
  "killSelection": "YOUNGEST_FIRST",
  "unreachableStrategy": {
    "inactiveAfterSeconds": 0,
    "expungeAfterSeconds": 0
  },
  "healthChecks": [],
  "fetch": [],
  "constraints": []
}

{
  "id": "/pod/nginx",
  "version": "2019-04-05T12:12:29.419Z",
  "containers": [
    {
      "name": "nginx",
      "resources": {
        "cpus": 0.001,
        "mem": 32,
        "disk": 0,
        "gpus": 0
      },
      "exec": {
        "command": {
          "shell": "sleep infinity"
        }
      }
    },
    {
      "name": "web",
      "resources": {
        "cpus": 0.001,
        "mem": 32,
        "disk": 0,
        "gpus": 0
      },
      "exec": {
        "command": {
          "shell": "sleep infinity"
        }
      }
    },
    {
      "name": "mysql",
      "resources": {
        "cpus": 0.001,
        "mem": 32,
        "disk": 0,
        "gpus": 0
      },
      "exec": {
        "command": {
          "shell": "sleep infinity"
        }
      }
    }
  ],
  "networks": [
    {
      "mode": "host"
    }
  ],
  "scaling": {
    "instances": 1,
    "kind": "fixed"
  },
  "scheduling": {
    "backoff": {
      "backoff": 1,
      "backoffFactor": 1.15,
      "maxLaunchDelay": 300
    },
    "upgrade": {
      "minimumHealthCapacity": 1,
      "maximumOverCapacity": 1
    },
    "killSelection": "YOUNGEST_FIRST",
    "unreachableStrategy": {
      "inactiveAfterSeconds": 0,
      "expungeAfterSeconds": 0
    },
    "placement": {
      "constraints": []
    }
  },
  "executorResources": {
    "cpus": 0.1,
    "mem": 32,
    "disk": 10
  },
  "volumes": [],
  "fetch": []
}

Verify that nginx service doesn't have pod_nginx.instance-* tasks
While /pod/nginx has it's containers
Trade-offs

Dependencies

Screenshots

Looks good. Some integration tests are failing, I will take a look to see how can we fix them.

I fixed it, @nLight , do you mind if I push my fix?

@GeorgiSTodorov please go ahead 🙇

If I broke any other tests while fixing ServiceDetail-cy, I will take responsibility for fixing them.

I've fixed all failing tests, except one, currently working on this last one.

I can't understand why the framework is not healthy in the test.

Thanks for picking up this one! Let me check the last failing test...

No problem, I am also currently investigating. I will push my commit fixing the other tests.

@GeorgiSTodorov could that be because of the feature Pierre and Philipp are working on?

@nLight , I think it's because of the fixtures, but it could be because of the feature.

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


Chain DB: handle and test clock changes

See https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-consensus/docs/ChainDB.md#clock-changes

Possible approach: start a thread that "watches" the current time and when it rolls back, shut down the node (and restart).

TODO: do we deal correctly with blocks (on-disk) from the future?

Moving this to daedalus since exchange and core nodes won't be changing their clocks.

Marked as high priority because this is totally untested.

An NTP client will be running and notify the wallet when it is out of sync. Think about what we should do.

Current plan:

If time moved forward: waitUntilNextSlot will handle it correctly. We might briefly lag behind, but we'll correct it when waiting for the next slot.
If time moved backward: we can check in waitUntilNextSlot whether the computed next slot number is actually the next one. If it is not, time must have moved back. We could allow staying on the same slot number, but we certainly can't allow going back a slot, we should throw an exception, shutting down the node.

Note that we (the node) don't have to run an NTP client for this. We are using getCurrentTime (wall clock) in waitUntilNextSlot.

Implementation: @edsko
(Protocol) testing: @nfrisby

The implementation was completed in #1554. We have created a new ticket for testing it: #1572.

Re-opening as this isn't merged yet due to dependency on https://github.com/input-output-hk/ouroboros-network/pull/1539 . Since it's only the tests that depend on that, though, will submit two separate PRs.

Mind that it does come with tests, it just doesn't do consensus-level tests.

Closed as of https://github.com/input-output-hk/ouroboros-network/pull/1554 .


Add python3-alembic to distros

I verifed the same name is used for each dist
Signed-off-by: Luke Hinds<EMAIL_ADDRESS>

Codecov Report

Merging #1033 (77b20b4) into master (f336ad1) will decrease coverage by 0.03%.
The diff coverage is n/a.

Flag
Coverage Δ

packit-e2e
66.06% <ø> (-0.04%)
:arrow_down:

testsuite
47.98% <ø> (ø)

unittests
13.23% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

keylime/registrar_common.py
58.58% <0.00%> (-0.93%)
:arrow_down:


Pathological reallocation in memory pools

Describe the bug
With certain allocation patterns and sizes QuickPool never coalesces a backing allocation to be large enough, leading to unnecessary reallocations.
To Reproduce
Compile the following file with anything from 2024.02.01 to current develop (older versions likely also affected, but have not tested):
#include <umpire/ResourceManager.hpp>
#include <umpire/strategy/QuickPool.hpp>

#include <iostream>
#include <cstddef>

int main() {
    auto alloc = umpire::ResourceManager::getInstance().getAllocator("DEVICE");
    auto pooled_alloc =
        umpire::ResourceManager::getInstance().makeAllocator<umpire::strategy::QuickPool>(
            "DEVICE_pool", alloc,
            16,  // initial pool size important only in the sense that allocations must be larger than the initial size, otherwise no additional allocations are required
            16,  // next size is not important to reproduce
            16); // alignment important: if all allocations are multiples of alignment all is good

    const std::size_t niter = 5;
    for (std::size_t iter = 0; iter < niter; ++iter) {
            std::cerr << "iteration " << iter << '\n';
            auto* p1 = pooled_alloc.allocate(1024 + 8);
            auto* p2 = pooled_alloc.allocate(1024 + 8); // need at least two allocations not multiples of alignment
            pooled_alloc.deallocate(p2);
            pooled_alloc.deallocate(p1);
    }
}

Just to print the allocations I ran this through gdb with the following gdb script:
start

break cudaMalloc
commands
continue
end

break cudaFree
commands
continue
end

continue

and then
gdb -batch -x gdbscript umpire_test

produces:
...
iteration 0
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
iteration 1
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
iteration 2
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
iteration 3
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
iteration 4
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 2, 0x0000fffff59fac64 in cudaMalloc () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
Thread 1 "miniapp_umpire_" hit Breakpoint 3, 0x0000fffff59fb2d0 in cudaFree () from /capstor/scratch/cscs/simbergm/src/DLA-Future/build/spack/src/libDLAF.so
...

Sizes are not visible above, but the first iteration first allocates twice, once for the initial buffer and once more to accommodate the second allocation. It then coalesces, freeing the two backing allocations above, and allocating one larger block. However, this block does not take overallocation into account, and is too small for the next iteration. The pool then always allocates for the second user-triggered allocation, frees both backing allocations, and attempts to coalesce. Repeat.
If one of the user-requested allocations is 16-byte aligned the reproducer correctly allocates only on the first iteration and then never again.
I suppose using umpire's logging should produce the same results, I'm just not familiar enough with it.
I used DEVICE only to make it easier to hook gdb into cudaMalloc and avoid printing potential other allocations. The same behaviour should happen with any backing memory.
I expect this affects DynamicPoolList as well.
Expected behavior
I expect that repeating the same allocation and deallocation pattern multiple times (no matter what initial size, next size, alignment, and user-requested allocation sizes are used), letting the pool empty between iterations to allow for coalescing (with the default coalescing strategy), would lead to allocations only during the first iteration and when coalescing after the first iteration. After that all allocations should fit in the pool without any further allocations.
Compilers & Libraries (please complete the following information):

Compiler & version: GCC 12.3.0
CUDA version (if applicable): CUDA 12.2.1 (not relevant to reproduce though)

Additional context
If I understand the pools correctly, the reason for this behaviour is that the actual size and the high water mark don't include the overallocation. They only sum up the sizes requested by the user, not the sizes actually allocated eventually, so there can be cases like the above where the pool never grows big enough to fit all required allocations.

Just wanted to add that I tried to work around this in a real application by rounding all allocations to the alignment before passing them to Umpire and I still get reallocations every iteration, so that on its own might not explain the reallocation. I may also have made a mistake of course... But thought I'd mention this for a possible fix in Umpire.
Currently I'm working around this by using a custom coalescing heuristic which allocates x percent more than the previous high water mark and in our case this seems to cover the mismatch between actual high water mark and apparent high water mark, but this is obviously not a general fix.

Fixed in #917


Question - registerNotificationReceivedBackground on Android

I'm on 4.3.3 of this package and 67.5 for React Native.
When I register for registerNotificationReceivedBackground it works as expected - I put the app in the background and receive notifications, even if I close the app. When I close the app and open the app again and reregister, it fires twice now. If I unregister when the app closes, then I don't receive notifications in the background anymore. Am I missing something or is this expected behaviour? Thanks.

Just to test, I created a new project with just this package and the bare-bones latest RN code.
RN - 0.71.3
RNN - 4.3.3
It was kind of interesting. I did not dispose any of the EventEmitter returned from the .events(). I no longer saw the +1 issue when restarting the application, although once the application closed, I no longer received notifications with the application closed.
I made sure to follow the instructions in the Android setup, and it seems like including this line is out-of-date
classpath 'com.google.gms:google-services:4.0.0'

I'm getting a similar problem, did you find a solution?

No. I pulled in the react native firebase package and use that for android
and this package still for iOS.
On Wed, Apr 12, 2023 at 4:05 PM David Leavitt @.***>
wrote:

I'm getting a similar problem, did you find a solution?
—
Reply to this email directly, view it on GitHub
https://github.com/wix/react-native-notifications/issues/952#issuecomment-1506078585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRPWL4O5QKGX3M77NTQ6KDXA4YMNANCNFSM6AAAAAAVN7NPV4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add org type to orgs table, create org type table

💡 Summary
Add a new column to the organization table called org_type, this will link to a new table called org_type,
This is necessary to differentiate between federal, State, and critical infrastructure organizations in the future which may require customized reporting depending on needs and data source access
Implementation notes
Please provide details for implementation, such as:
We need to make these adjustments to the live data base
We also need to make these changes to the db schema for future database creation
Acceptance criteria
How do we know when this work is done?

[ ] Create new table called org_types
[ ] link this table to the organizations table with a new foreign key (most likely org_type_uid)

This has been changed to pull from the cyhy_db, so. we no longer really need the org type table


[SPARK-15822][SQL] Prevent byte array backed classes from referencing freed memory

What changes were proposed in this pull request?
UTF8String and all Unsafe* classes are backed by either on-heap or off-heap byte arrays. The code generated version SortMergeJoin buffers the left hand side join keys during iteration. This was actually problematic in off-heap mode when one of the keys is a UTF8String (or any other 'Unsafe*` object) and the left hand side iterator was exhausted (and released its memory); the buffered keys would reference freed memory. This causes Seg-faults and all kinds of other undefined behavior when we would use one these buffered keys.
This PR fixes this problem by creating copies of the buffered variables. I have added a general method to the CodeGenerator for this. I have checked all places in which this could happen, and only SortMergeJoin had this problem.
This PR is largely based on the work of @robbinspg and he should be credited for this.
closes https://github.com/apache/spark/pull/13707
How was this patch tested?
Manually tested on problematic workloads.

cc @davies @rxin @sameeragarwal

Test build #60674 has started for PR 13723 at commit 5c33eac.

Test build #60674 has finished for PR 13723 at commit 5c33eac.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60674/
Test PASSed.

lgtm.

LGTM,
Merging this into master and 2.0, thanks!


SAKIII-4741 fix issue with caching group roles and updating participants widget

https://jira.sakaiproject.org/browse/SAKIII-4741

Squashed and merged


Migrate jvm-services, normalization-java and platform-jvm to the jvm platform

These are the last of the JVM projects.

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.


Split battle script and match setup

Minor reorganisation of code to make the battle script solely responsible for parsing the cli args and the MatchInfo object builds and runs the actual match

These changes seem reasonable and look mergeable as-is. I do however notice that the execution runs fail at different points of their execution as they have trouble cleaning up their built docker images (even the supposedly successful windows-latest). I am not sure if these particular changes are responsible for that, but this should be cleaned up, possibly  in a separate PR.

Thank you, the automation results look sensible now.


Documentation and sample code mismatch

Hey there! :)
The main readme says:

DevTools is a store enhancer, which should be added to your middleware stack after applyMiddleware as applyMiddleware is potentially asynchronous

And just after:

const finalCreateStore = compose(
// Enables your middleware:
applyMiddleware(m1, m2, m3), // any Redux middleware, e.g. redux-thunk
// Provides support for DevTools:
devTools(),
// Lets you write ?debug_session= in address bar to persist debug sessions
persistState(window.location.href.match(/[?&]debug_session=([^&]+)\b/))
)(createStore);

However, `compose`d functions are called right to left, so in this code `devTools()` will be called _before_ `applyMiddleware`, not _after_ like the doc says we must.

You're right about the call order.
The intention was to encourage user to write it after (= below) devTools() in the compose chain.
If you see a better way of phrasing this please send a PR.


this.getNativeComponent is not a function (it is undefined) - Markers not showing on iOS react-native

Summary
When adding a Marker inside MapView the module responds with:
Render Error
this.getNativeComponent is not a function (it is undefined)
from ./lib/MapMarker.js
System:
  OS: macOS 14.2.1
  CPU: (8) arm64 Apple M1
  Memory: 160.83 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/local/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10671973
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.24
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.2
    wanted: 0.75.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: false

Reproducible sample code
<MapView
                    provider={PROVIDER_GOOGLE}
                    style={styles.map}
                    initialRegion={{
                      latitude: position?.coords.latitude || 37.78825,
                      longitude: position?.coords.longitude || -122.4324,
                      latitudeDelta: 0.015,
                      longitudeDelta: 0.0121,
                    }}
                    showsUserLocation
                    mapType="standard"
                    customMapStyle={isDarkTheme ? mapDark : mapLight}
                  >
                    {marker && (
                      <Marker
                        draggable
                        coordinate={{
                          latitude: position?.coords.latitude || 37.78825,
                          longitude: position?.coords.longitude || -122.4324,
                        }}
                        pinColor="#244c66"
                        onDragEnd={e => onDrag(e)}
                        icon={logo}
                      />
                    )}
                  </MapView>

Steps to reproduce
npx react-native run-ios
Expected result
Should show the markers
Actual result
Full page error
React Native Maps Version
1.18.0
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.75.2
What version of Expo are you using?
Not using Expo
Device(s)
iPhone 15
Additional information
No response

This issue's current status? When will the bug be fixed? Thanks 🙏

+1

+1

Also getting this issue

Both on android and iOS.
Tired AF.

Same on ^1.20.0

Also getting this error on 1.20.0.


gitea broken after wrong hook file

Gitea version: 1.8.3
Git version: 2.18.0.windows.1
Operating system: Windows
Database: SQLite
Can you reproduce the bug at https://try.gitea.io: no
Log gist:

Description
my hook file was wrong, i pushed repository and gitea does not count new commits and does not create releases after push tags
hook file is: gitea-repositories\rst-yazilim\stm-say.git\hooks\update.d
exe file was wrong like:
#!/usr/bin/env bash "H:/gitea/giteaexe"

giteaexe instead of gitea.exe
Screenshots
as you can see 1 releases with 2 tags

as you see 4 commits but have much more

Resync hooks on Admin Panel

Its ok. Thank you


De-lint and typo fix - no code changes.

Fix some typos, de-lint the markdown a little.

tnx !! :)


The Handbook of Digital Labor

https://iamcr.org/publications/iamcr-handbook
https://iamcr.org/publications/iamcr-handbook/handbook-of-political-economy-of-communications

For Friday 04/07 - we will each bring a pitch on one of the following:

Regulating the gig economy

Moral injury in digital labor

Organizing against Algorithmic Management

Information Asymmetries in the Gig Economy

How solidarity politics emerge in decentralized work

Worker owned cooperatives in digital labor

why is it important to consider in the context of digital labor

include 5 key publications

international scope

LS pitch - Organizing Against Alg Management // Solidarity Politics in Decentralized Work - https://docs.google.com/document/d/172CF2NhuXA6dO0ptLSHBWr_yI4q2OfOqxFUXGuzobco/edit

NW - Moral Injury in Digital Labor https://docs.google.com/document/d/1h95oNAIBcnH9aF2gk16mlwysTDIIVCOpKNH984pAmdw/edit?usp=sharing

For Wed 04.12 - we will each bring a 200 word draft abstract

From the original email:
We'd like to call for chapter submissions to The Handbook of Digital Labor,
which we are editing for the Global Handbooks in Media & Communication
Research Series, an initiative under the International Association for
Media and Communication Research (IAMCR), to be published by Wiley.
Despite the generic title, we designed this handbook to chart rapidly
changing global labor conditions, challenge boundaries between “online” vs
“off-line” labor, and be a resource book that addresses key debates
surrounding perennial and urgent concerns about labor questions in
contemporary capitalism from a global perspective. While this handbook will
build on existing work, it stresses the reconceptualization of digital
labor in various contexts, connecting them across the sectors and
generations, and is intended to contribute to structural analysis and
intellectual praxis toward emancipatory movements.
This handbook is organized around four themes that are defined
historically, technologically, and internationally in the realms of work
and control, solidarity politics, pedagogy, and imaginaries:

Labor Under Capitalism

Digital Technologies, Work and Control

Solidarity Politics and the Working-Class Majority

Pedagogy, Imaginary and Emancipation

In this project, we investigate foundational labor questions as well as
emerging and/or persistent patterns of labor and labor organization under
new conditions such as digital platforms, automation, artificial
intelligence (AI), the ”gig” economy, new divisions of labor, and
alternative developments.


fix(lanelet2_extension): fix getAngleDifference

Related Issue(required)
Description(required)
method 1. below can going to return bigger value than 2pi if angle is positive and negative
inline double getAngleDifference(const double angle1, const double angle2)
{
  const double normalized_angle1 = tier4_autoware_utils::normalizeRadian(angle1);
  const double normalized_angle2 = tier4_autoware_utils::normalizeRadian(angle2);
  const double diff_angle = std::fabs(normalized_angle1 - normalized_angle2);
  return diff_angle;
}

method 2. below can return value normalized in pi in difference to negative angle or positive angle.
inline double getAngleDifference(const double angle1, const double angle2)
{
  const double diff_angle = std::abs(tier4_autoware_utils::normalizeRadian(angle1 - angle2));
  return diff_angle;
}

in this test case method 2 passed
TEST(normalization, getAngleDifference)
{
  using lanelet::utils::getAngleDifference;

  constexpr double eps = 0.1;
  constexpr double pi = M_PI;
  constexpr double pi2 = 2.0*M_PI;
  // case normal
  {
    // abs diff
    EXPECT_FLOAT_EQ(getAngleDifference(-pi, 0), pi);
    // abs diff
    EXPECT_FLOAT_EQ(getAngleDifference(pi, 0), pi);
  }
  // case inverse angle
  {
    // return normalized angle diff
    EXPECT_FLOAT_EQ(getAngleDifference(-pi - eps, pi), eps);
    // return 0 if same direction
    EXPECT_FLOAT_EQ(getAngleDifference(-pi, pi), 0);
  }
  // case more than 2PI angle
  {
    // return normalized angle diff
    EXPECT_FLOAT_EQ(getAngleDifference(-pi2 - eps, pi2), eps);
    // return pi if invert direction
    EXPECT_FLOAT_EQ(getAngleDifference(-pi2, pi), pi);
  }
}

Review Procedure(required)
100% tests passed, 0 tests failed out of 9

Label Time Summary:
copyright     =   2.53 sec*proc (1 test)
cppcheck      =   0.26 sec*proc (1 test)
gtest         =   0.27 sec*proc (5 tests)
lint_cmake    =   0.20 sec*proc (1 test)
linter        =   3.18 sec*proc (4 tests)
xmllint       =   0.20 sec*proc (1 test)

Total Test time (real) =   3.45 sec
Finished <<< lanelet2_extension [3.51s]

Summary: 1 package finished [4.14s]

Related PR(optional)

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read commit-guidelines
[ ] Assign PR to reviewer

If you are adding new package following items are required:

[ ] Documentation with description of the package is available
[ ] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

494a744~eec529f revert unit test because of below standard that was in discussion with miyake-san
You need to test the functions that you provide in your own package.
If you just want to reference something that has been tested in another package, you don't need to do that part.

@kyoichi-sugahara  can you test this PR in Psim?

@taikitanaka3 -san
I checked and LGTM


fix #413

can you explain me how you generated these hashes? weird thing is print paper wallets working fine in my chrome. im on 56.0.2924.87

I am on 57 on Mac. Hashes from chrome error messages :) We can do them manually like here https://www.w3.org/TR/2015/CR-CSP2-20150721/#script-src-hash-usage
I guess this should be part of build pipeline ideally, but then i dont think we change these scripts that often.


1.21: Update to Berkeley DB 5.3

Re-integration of #2245.
I took the original commits from @bjacquin and @rnicoll and re-did the CI integration previously done with a404897, because the configuration there was incomplete.
Doing the bdb 5.3 switch now will allow us to spot any regressions from a wallet perspective when we fully enable auxpow on 1.21-dev, as 1.14 wallets files are incompatible with the bdb 4.8 currently used.
Notes:

I kept the --with-incompatible-bdb flag in the centos CI for now because I'm not sure whether it's good or bad to test the scenario. Open to discussion.
It would be good if we can attempt a gitian/guix build & compare with this, but per Ross' comment back in November, it's currently broken. If that's still the case, I think we should address that separately.

It would be good if we can attempt a gitian/guix build & compare with this, but per https://github.com/dogecoin/dogecoin/pull/2245#issuecomment-983052757, it's currently broken. If that's still the case, I think we should address that separately.

I'm dropping this for now, we can work on deterministic builds under #2852, since it looks like both gitian and guix need some work.

@chromatic I went over all the docs that still referenced either the need to install 4.8, or were describing processes that were not valid for the 5.3 installation, and changed these.
Note that some of the installation instructions don't fully work yet, but I would like to keep that out of the scope of this PR - we can work on that later.


msinit() does not ensure global is not already allocated.

"global" could already be allocated with memory
Global is uninitalised, and becomes initalised after msinit(). However, msinit() does not ensure global does not already have memory allocated to it (likely by another msinit() call).
memstack* global;

void msinit(){
    // You don't check if global is NULL O_O
    global = msnew();
}

This causes issues as memory is not freed. msinit() could be called twice and the previous allocation would be overwritten.
Solution
This ensures global is correctly freed before being re-allocated.
memstack* global = NULL;

void msinit(){
    if (global != NULL) {
        global = msnew();
    } else {
        msfree(global);
        global = msnew();
    }
}

Fixed in https://github.com/Khhs167/memstack/pull/4


[converter] support new PyTorch operators

Below are the PyTorch operators that are yet to be supported.
Unclassfied (New)
N/A
Primitives (Python operators)

[x] aten::len

Very easy (Constant generation or aliasing)

[x] aten::clamp_min
[x] aten::clamp_max
[x] aten::expand_as

Easy (Direct mapping)
Medium (Composite of multiple operators)

[x] aten::im2col https://github.com/alibaba/TinyNeuralNetwork/issues/69
[x] aten::col2im https://github.com/alibaba/TinyNeuralNetwork/issues/69
[x] aten::mish
[x] aten::group_norm
[ ] torchvision::nms https://github.com/alibaba/TinyNeuralNetwork/issues/16

Hard (No mapping or the mapping is too complex)

[ ] aten::grid_sample https://github.com/alibaba/TinyNeuralNetwork/issues/69
[ ] quantized::instance_norm
[ ] quantized::layer_norm

aten::len ops is not supported when I try to convert my resnet model to tflite

aten::len ops is not supported when I try to convert my resnet model to tflite

Could you please tell me what is the corresponding op in PyTorch (e.g. torch.mean)? Looks like you are passing the TorchScript model in scripting mode, which we don't have much support for. The model produced by torch.jit.trace and torch.jit.save is better supported.

aten::len ops is not supported when I try to convert my resnet model to tflite

Could you please tell me what is the corresponding op in PyTorch (e.g. torch.mean)? Looks like you are passing the TorchScript model in scripting mode (via torch.jit.script), which we don't have much support for. The model produced by torch.jit.trace and torch.jit.save is better supported.
Update: aten::len added in a1b3c79

Actually, the main problem is the AdaptiveAvgPool2d layer. If I replace it with MaxPool2d then it is converting fine.

Any plan to support quantized::instance_norm?

Any plan to support quantized::instance_norm?

Would you please give me an example with a TFLite model quantized InstanceNorm layer? Once it is supported in TFLite, we will look into that.

Any plan to support quantized::instance_norm?

Would you please give me an example with a TFLite model quantized InstanceNorm layer? Once it is supported in TFLite, we will look into that.

@peterjc123 You can use the following code as test case. Many Thanks
import torch
from torch import nn
from tinynn.graph.quantization.quantizer import QATQuantizer
from tinynn.graph.tracer import model_tracer
from tinynn.converter import TFLiteConverter

class ChannelWiseConv(nn.Module):
    def __init__(self, in_channel, out_channel, padding=0, stride=1, dilation=1, bias=True, norm_layer='BN'):
        super().__init__()
        self.dwconv_quant = torch.quantization.QuantStub()
        self.dwconv_dequant = torch.quantization.DeQuantStub()
        self.pwconv_quant = torch.quantization.QuantStub()
        self.pwconv_dequant = torch.quantization.DeQuantStub()
        self.dwconv = nn.Conv2d(
            in_channel,
            in_channel,
            kernel_size=3,
            padding=padding,
            stride=stride,
            dilation=dilation,
            groups=in_channel,
            bias=bias
        )

        self.pwconv = nn.Conv2d(
            in_channel,
            out_channel,
            kernel_size=1,
            bias=bias
        )

        self.norm_layer = norm_layer
        self.bn = nn.BatchNorm2d(out_channel)
        self.instance_norm = nn.InstanceNorm2d(out_channel)
        self.relu = nn.ReLU()

    def forward(self, x):
        x = self.dwconv_quant(x)
        x = self.dwconv(x)
        x = self.dwconv_dequant(x)
        x = self.pwconv_quant(x)
        x = self.pwconv(x)

        if self.norm_layer == 'BN':
            x = self.bn(x)
        elif self.norm_layer == 'IN':
            x = self.instance_norm(x)

        x = self.relu(x)
        x = self.pwconv_dequant(x)

        return x

class Model(nn.Module):
    def __init__(self):
        super().__init__()
        self.convs1 = ChannelWiseConv(3, 256, norm_layer='IN')
        self.convs2 = ChannelWiseConv(256, 256, norm_layer='IN')
        self.convs3 = ChannelWiseConv(256, 1, norm_layer='IN')

    def forward(self, x):
        x = self.convs1(x)
        x = self.convs2(x)
        x = self.convs3(x)

        return  x

if __name__ == '__main__':
    model = Model()
    quantizer = QATQuantizer(
        model,
        torch.randn(1, 3, 160, 256),
        work_dir='out',
        config={'rewrite_graph': False}
    )

    quantizer.quantize()

    model.eval()
    model.cpu()
    model = quantizer.convert(model)
    torch.backends.quantized.engine = 'qnnpack'
    converter = TFLiteConverter(model, torch.randn(1, 3, 160, 256), tflite_path='instance_norm.tflite')
    converter.convert()

Any plan to support quantized::instance_norm?

Would you please give me an example with a TFLite model quantized InstanceNorm layer? Once it is supported in TFLite, we will look into that.

@peterjc123 You can use the following code as test case. Many Thanks
import torch
from torch import nn
from tinynn.graph.quantization.quantizer import QATQuantizer
from tinynn.graph.tracer import model_tracer
from tinynn.converter import TFLiteConverter

class ChannelWiseConv(nn.Module):
    def __init__(self, in_channel, out_channel, padding=0, stride=1, dilation=1, bias=True, norm_layer='BN'):
        super().__init__()
        self.dwconv_quant = torch.quantization.QuantStub()
        self.dwconv_dequant = torch.quantization.DeQuantStub()
        self.pwconv_quant = torch.quantization.QuantStub()
        self.pwconv_dequant = torch.quantization.DeQuantStub()
        self.dwconv = nn.Conv2d(
            in_channel,
            in_channel,
            kernel_size=3,
            padding=padding,
            stride=stride,
            dilation=dilation,
            groups=in_channel,
            bias=bias
        )

        self.pwconv = nn.Conv2d(
            in_channel,
            out_channel,
            kernel_size=1,
            bias=bias
        )

        self.norm_layer = norm_layer
        self.bn = nn.BatchNorm2d(out_channel)
        self.instance_norm = nn.InstanceNorm2d(out_channel)
        self.relu = nn.ReLU()

    def forward(self, x):
        x = self.dwconv_quant(x)
        x = self.dwconv(x)
        x = self.dwconv_dequant(x)
        x = self.pwconv_quant(x)
        x = self.pwconv(x)

        if self.norm_layer == 'BN':
            x = self.bn(x)
        elif self.norm_layer == 'IN':
            x = self.instance_norm(x)

        x = self.relu(x)
        x = self.pwconv_dequant(x)

        return x

class Model(nn.Module):
    def __init__(self):
        super().__init__()
        self.convs1 = ChannelWiseConv(3, 256, norm_layer='IN')
        self.convs2 = ChannelWiseConv(256, 256, norm_layer='IN')
        self.convs3 = ChannelWiseConv(256, 1, norm_layer='IN')

    def forward(self, x):
        x = self.convs1(x)
        x = self.convs2(x)
        x = self.convs3(x)

        return  x

if __name__ == '__main__':
    model = Model()
    quantizer = QATQuantizer(
        model,
        torch.randn(1, 3, 160, 256),
        work_dir='out',
        config={'rewrite_graph': False}
    )

    quantizer.quantize()

    model.eval()
    model.cpu()
    model = quantizer.convert(model)
    torch.backends.quantized.engine = 'qnnpack'
    converter = TFLiteConverter(model, torch.randn(1, 3, 160, 256), tflite_path='instance_norm.tflite')
    converter.convert()

I mean if there isn't quantized InstanceNorm support for TFLite, then there is not much we can help here. Your code only generates a quantized PyTorch with InstanceNorm, which is not thing I actually need.

Is there any chance to implement torch aten::scaled_dot_product_attention?
https://pytorch.org/docs/master/generated/torch.nn.functional.scaled_dot_product_attention.html says it could be done as
# Efficient implementation equivalent to the following:
scale_factor = 1 / math.sqrt(Q.size(-1)) if scale is None else scale
attn_mask = torch.ones(L, S, dtype=torch.bool).tril(diagonal=0) if is_causal else attn_mask
attn_mask = attn_mask.masked_fill(not attn_mask, -float('inf')) if attn_mask.dtype==torch.bool else attn_mask
attn_weight = torch.softmax((Q @ K.transpose(-2, -1) * scale_factor) + attn_mask, dim=-1)
attn_weight = torch.dropout(attn_weight, dropout_p)
return attn_weight @ V

Is there any chance to implement torch aten::scaled_dot_product_attention? https://pytorch.org/docs/master/generated/torch.nn.functional.scaled_dot_product_attention.html says it could be done as
# Efficient implementation equivalent to the following:
scale_factor = 1 / math.sqrt(Q.size(-1)) if scale is None else scale
attn_mask = torch.ones(L, S, dtype=torch.bool).tril(diagonal=0) if is_causal else attn_mask
attn_mask = attn_mask.masked_fill(not attn_mask, -float('inf')) if attn_mask.dtype==torch.bool else attn_mask
attn_weight = torch.softmax((Q @ K.transpose(-2, -1) * scale_factor) + attn_mask, dim=-1)
attn_weight = torch.dropout(attn_weight, dropout_p)
return attn_weight @ V

Please create a new issue for that.


[now dev] @now/node builder not rebuilding imported files

I've got a semi-complicated now app (shown at the bottom).
My app is all in typescript, with the following structure:
api/
    src/
        Route/
            IndexAction.ts
        Service/
            ExampleService.ts

Right now, when running now dev, if I make changes to ExampleService.ts, i need to kill now dev to get the changes to show up when I call the ExampleService from IndexAction
now.json
{
    "name":    "monorepo",
    "version": 2,
    "builds":  [
        {
            "src": "www/package.json",
            "use": "@now/next"
        },
        {
            "src": "api/src/**/*.ts",
            "use": "@now/node"
        }
    ],
    "secrets": {
        "sm_access_key_id":     "@website_sm_access_key_id",
        "sm_secret_access_key": "@website_sm_secret_access_key"
    },
    "routes":  [
        {
            "src":  "/api/hello/(.*)",
            "dest": "/api/src/Action/HelloAction.ts?name=$1"
        },
        {
            "src":  "/api",
            "dest": "/api/src/Action/IndexAction.ts"
        },
        {
            "src":     "/(.*)",
            "dest":    "/www/$1",
            "headers": {
                "x-request-path": "$1"
            }
        }
    ]
}

I do see (when running now dev -d) that it sees the change, and recompiles, but the change isnt showing up

Hey @aequasi, thanks for trying out now dev!
When you say "it recompiles", what do you see in the logs exactly? The reason I ask is because there's an in-progress PR that finishes the watching functionality for the @now/node builder.
You also might have better results with the @now/node@dev tagged builder which includes (some of) those changes.

I've tried it and still dont see changes.
After checking the logs, I don't see it actually compiling:
> [debug] [2019-04-30T23:49:50.871Z] Filesystem watcher notified of 1 events
> [debug] [2019-04-30T23:49:50.871Z] File modified: api/src/AppKernel.ts
> [debug] [2019-04-30T23:49:50.872Z] Locating files /Users/aaron/projects/secretary/website
> [debug] [2019-04-30T23:49:50.873Z] Locating files /Users/aaron/projects/secretary/website: 0.041ms
> [debug] [2019-04-30T23:49:50.876Z] Locating files /Users/aaron/projects/secretary/website
> [debug] [2019-04-30T23:49:50.876Z] Locating files /Users/aaron/projects/secretary/website: 0.053ms
> [debug] [2019-04-30T23:49:51.373Z] Filesystem watcher notified of 1 events
> [debug] [2019-04-30T23:49:51.373Z] File modified: .idea/workspace.xml
> [debug] [2019-04-30T23:49:51.374Z] Locating files /Users/aaron/projects/secretary/website
> [debug] [2019-04-30T23:49:51.374Z] Locating files /Users/aaron/projects/secretary/website: 0.030ms
> [debug] [2019-04-30T23:49:51.376Z] Locating files /Users/aaron/projects/secretary/website
> [debug] [2019-04-30T23:49:51.376Z] Locating files /Users/aaron/projects/secretary/website: 0.043ms
> GET /api
> [debug] [2019-04-30T23:49:52.760Z] Locating files /Users/aaron/projects/secretary/website
> [debug] [2019-04-30T23:49:52.760Z] Locating files /Users/aaron/projects/secretary/website: 0.047ms
> [debug] [2019-04-30T23:49:52.762Z] Locating files /Users/aaron/projects/secretary/website
> [debug] [2019-04-30T23:49:52.762Z] Locating files /Users/aaron/projects/secretary/website: 0.105ms
> [debug] [2019-04-30T23:49:52.765Z] Serving asset: [Lambda] api/src/Action/IndexAction.ts

I've also got .idea in my .nowignore, but its still watching that file?

I'm seeing some of the same. Except I have two files that are "entry points" that import other files (all Typescript). If I edit any of the entry points it reloads fine, but if I edit any file that is imported by any of those nothing happens.
now dev -d output on reload of entry points:
> [debug] [2019-05-01T16:47:03.980Z] Filesystem watcher notified of 6 events
> [debug] [2019-05-01T16:47:03.981Z] File created, but has since been deleted: api/src/index.ts___jb_tmp___
> [debug] [2019-05-01T16:47:03.981Z] File modified, but has since been deleted: api/src/index.ts___jb_tmp___
> [debug] [2019-05-01T16:47:03.981Z] File renamed, but has since been deleted: api/src/index.ts -> api/src/index.ts___jb_old___
> [debug] [2019-05-01T16:47:03.981Z] File renamed: api/src/index.ts___jb_tmp___ -> api/src/index.ts
> [debug] [2019-05-01T16:47:03.981Z] File modified: api/src/index.ts
> [debug] [2019-05-01T16:47:03.981Z] File deleted: api/src/index.ts___jb_old___
> [debug] [2019-05-01T16:47:03.983Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:47:03.983Z] Locating files /home/karl/git/project: 0.044ms
> [debug] [2019-05-01T16:47:03.984Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:47:03.984Z] Locating files /home/karl/git/project: 0.032ms
> [debug] [2019-05-01T16:47:03.986Z] Triggering 1 rebuilds
> [debug] [2019-05-01T16:47:03.986Z] Files changed: api/src/index.ts
> [debug] [2019-05-01T16:47:03.986Z] Files removed: api/src/index.ts___jb_tmp___, api/src/index.ts___jb_old___
> [debug] [2019-05-01T16:47:03.986Z] Removing asset "api/src/index.ts"
> [debug] [2019-05-01T16:47:03.986Z] Building asset "api/src/index.ts"
> Building @now/node:api/src/index.ts
> [debug] [2019-05-01T16:47:03.987Z] v0.6.0 (workPath = /tmp/co.zeit.now/dev/workPaths/irpp3na8)
downloading user files...
installing dependencies for user's code...
installing to /tmp/co.zeit.now/dev/workPaths/irpp3na8/api/src
> [debug] [2019-05-01T16:47:04.480Z] Filesystem watcher notified of 6 events
> [debug] [2019-05-01T16:47:04.481Z] File created, but has since been deleted: .idea/workspace.xml___jb_tmp___
> [debug] [2019-05-01T16:47:04.481Z] File modified, but has since been deleted: .idea/workspace.xml___jb_tmp___
> [debug] [2019-05-01T16:47:04.481Z] File renamed, but has since been deleted: .idea/workspace.xml -> .idea/workspace.xml___jb_old___
> [debug] [2019-05-01T16:47:04.481Z] File renamed: .idea/workspace.xml___jb_tmp___ -> .idea/workspace.xml
> [debug] [2019-05-01T16:47:04.481Z] File modified: .idea/workspace.xml
> [debug] [2019-05-01T16:47:04.481Z] File deleted: .idea/workspace.xml___jb_old___
running user script...
compiling entrypoint with ncc...
ncc: Version 0.18.1
ncc: Compiling file index.js
> [debug] [2019-05-01T16:47:04.482Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:47:04.482Z] Locating files /home/karl/git/project: 0.043ms
> [debug] [2019-05-01T16:47:04.484Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:47:04.484Z] Locating files /home/karl/git/project: 0.032ms
** lots of NCC output**
> Built @now/node:api/src/index.ts [5s]
> [debug] [2019-05-01T16:47:08.685Z] Built asset api/src/index.ts

Output when changing a imported file:
> [debug] [2019-05-01T16:49:02.793Z] Filesystem watcher notified of 7 events
> [debug] [2019-05-01T16:49:02.793Z] File created, but has since been deleted: api/src/utils/array.ts___jb_tmp___
> [debug] [2019-05-01T16:49:02.793Z] File modified, but has since been deleted: api/src/utils/array.ts___jb_tmp___
> [debug] [2019-05-01T16:49:02.793Z] File deleted: api/src/utils/array.ts
> [debug] [2019-05-01T16:49:02.793Z] File created, but has since been deleted: api/src/utils/array.ts___jb_old___
> [debug] [2019-05-01T16:49:02.794Z] File renamed: api/src/utils/array.ts___jb_tmp___ -> api/src/utils/array.ts
> [debug] [2019-05-01T16:49:02.794Z] File modified: api/src/utils/array.ts
> [debug] [2019-05-01T16:49:02.794Z] File deleted: api/src/utils/array.ts___jb_old___
> [debug] [2019-05-01T16:49:02.795Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:49:02.795Z] Locating files /home/karl/git/project: 0.043ms
> [debug] [2019-05-01T16:49:02.797Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:49:02.797Z] Locating files /home/karl/git/project: 0.029ms
> [debug] [2019-05-01T16:49:03.293Z] Filesystem watcher notified of 6 events
> [debug] [2019-05-01T16:49:03.293Z] File created, but has since been deleted: .idea/workspace.xml___jb_tmp___
> [debug] [2019-05-01T16:49:03.293Z] File modified, but has since been deleted: .idea/workspace.xml___jb_tmp___
> [debug] [2019-05-01T16:49:03.293Z] File renamed, but has since been deleted: .idea/workspace.xml -> .idea/workspace.xml___jb_old___
> [debug] [2019-05-01T16:49:03.293Z] File renamed: .idea/workspace.xml___jb_tmp___ -> .idea/workspace.xml
> [debug] [2019-05-01T16:49:03.294Z] File modified: .idea/workspace.xml
> [debug] [2019-05-01T16:49:03.294Z] File deleted: .idea/workspace.xml___jb_old___
> [debug] [2019-05-01T16:49:03.294Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:49:03.295Z] Locating files /home/karl/git/project: 0.048ms
> [debug] [2019-05-01T16:49:03.296Z] Locating files /home/karl/git/project
> [debug] [2019-05-01T16:49:03.296Z] Locating files /home/karl/git/project: 0.029ms

I don't understand why it's reacting to files changed in the .idea folder as it is ignored. It even explicitly says so at startup:
``` [debug] [2019-05-01T16:50:10.912Z] Reading now.json file

[debug] [2019-05-01T16:50:10.913Z] Locating files /home/karl/git/project
[debug] [2019-05-01T16:50:10.914Z] Ignoring /home/karl/git/project/.git
[debug] [2019-05-01T16:50:10.914Z] Ignoring /home/karl/git/project/.gitignore
[debug] [2019-05-01T16:50:10.914Z] Ignoring /home/karl/git/project/.idea
[debug] [2019-05-01T16:50:10.914Z] Ignoring /home/karl/git/project/api/.gitignore
[debug] [2019-05-01T16:50:10.915Z] Ignoring /home/karl/git/project/api/node_modules
[debug] [2019-05-01T16:50:10.915Z] Ignoring /home/karl/git/project/web/.gitignore

Thank you for articulating my issue better than I could! Precisely the issue I'm running in to

Ok, I see now. So ya, that PR I referenced earlier will need to be merged before watching imported files will work as expected.
In the meantime, if you do a hard-refresh in your browser (i.e. so that it sends the Cache-Control: no-cache HTTP request header), then that forces now dev to rebuild the lambda that is being requested, so that should be a usable workaround for now.

Yes, disabling the network cache in chrome dev tools forces rebuilds on every page reload:

I switched my now.json to use @now/node@dev and it just deleted (actually, removed the contents of) all my local source files. Should I file this separately/anywhere else? 😅

Can you all please try out now (at least) v15.4.0-canary.4 and @now/node@canary and let me know if it's working as expected for you now?

@TooTallNate looks like it's working to me in canary. I can update a file that is imported from the entrypoint of my function and it triggers a recompile!

Closing because this was implemented in https://github.com/zeit/now-builders/pull/582.


Missing From header

in Spring mail tutorial https://www.baeldung.com/spring-email you are missing put setFrom in mime message (SimpleMailMessage) without it many email server refused this email

Hi @dacopan,
Thanks for the feedback. Indeed, many SMTP servers reject such emails. We'll update the article.

@dacopan we've updated the article. Thanks!


Can't install gem

when I do gem install backbone-on-rails
I'm getting this error:
ERROR:  Could not find a valid gem 'eco-source' (>= 0) in any repository     ERROR:  Possible alternatives: to_source, chsource, taosource, epf-source, outsource

gem install backbone-on-rails is throwing an Error: Could not find a valid gem 'eco-source' (>= 0) in any repository
Error: Possible alternatives: to_source, chsource, taosource, epf-source, outsource
Please I've been trying to complete a backbone / rails app

I'm having this same issue... Is this gem still being maintained? Is the eco-source gem being maintained? What should I be using instead? I tried the backbone-rails gem but they only have coffeescript generators...


Post the build status to a commit

Couldn't work out in this client implementation if POST /projects/:id/statuses/:sha was implemented within this library.
Came to this library from a previous library which seems to not getting the latest API endpoints also https://github.com/nmklotas/GitLabApiClient/issues/219
Cheers

The endpoint is accessible using NGitLab: IGitLabClient.GetCommitStatus(projectid).AddOrUpdate(...)


No IPv6 Default gateway, no IPv6 internet when manually assigned.

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
DHCPv6 is not populating the IPv6 default gateway when using pfatt to bypass AT&T RGW. IPv4 is unaffected and LAN clients receive valid IPv6 addresses via SLACC.
The correct IPv6 default gateway can be manually populated, but internet connectivity over IPv6 is not functional. Partial traceroutes succeed but do not exit the AT&T address space.
rtsol -d -D $WAN_INTERFACE receives an RA from the upstream IPv6 device. This RA matches the default gateway address that the original AT&T RGW acquires.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

Follow IPv6 instructions here: https://github.com/MonkWho/pfatt/blob/supplicant_OPNsense_testing/README.md
Ignore the part about checking "Do not wait for a RA", the checkbox no longer exists as the option is enabled by default.
No Default Gateway is defined for WAN IPv6 or displayed on main Dashboard.
Enter CLI and enter: rtsol -d -D $WAN_INTERFACE
Use the line that says rtsol: received RA from $IPv6_address on $WAN_INTERFACE, state is 2
Manually enter $IPV6_address in System -> Gateways -> Single -> WAN_DHCP6 -> IP Address in place of "Dynamic"
Attempt traceroute6 route-server.ip.att.net

Expected behavior
Default IPv6 Gateway is populated with appropriate routes and IPv6 internet access.
Describe alternatives you considered
I attempted to use the static IPv6 address method, with no success, and manually populating the gateway IP.
Additional context
I suspect there are two problems here.

A Gateway population issue.
An IPv6 route population issue.

Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 21.7.7 (amd64, OpenSSL).
Intel® Xeon™ E3-1225 3.1Ghz Quad Core

Hello I have similar issue since I upgraded to 22.1.
PING6(56=40+8+8 bytes) 2a01:XXXX:3ba:cb90::2 --> fe80::YYYY:8fff:fe6a:95d
ping6: sendmsg: No route to host
ping6: wrote fe80::YYYY:8fff:fe6a:95d 16 chars, ret=-1
I used to work well

Any idea of why there is no route on my LAN interface?
Thanks
XabiX

Same situation here. IPv6 public IPs delivered to all clients, but "no route" or "destination net unreachable".

Same here

Also running into this

I don’t know about pfatt and if everyone is having the exact same issue. Normally the issue arises because no proper RA is received and the ISP won’t send solicitations after one connects using the opportunistic try (which resembles do not wait for RA). An answer from the RA server does not equate to a mandatory use of that sending address as a router…
and I know I’ve helped @xabix with the issue reported, which had nothing to do with pfatt… it was about link-local behaviour change in FreeBSD 13.1 update.
That being said OPNsense 23.1 will add a SLAAC fallback router if the ISP is willing to offer one. We already know it doesn’t help all who reported a missing gateway, but that is mostly for ISP policy, e.g. no solicit before DHCP v4 is bound.
Cheers,
Franco


skipSelector is not exported

The functions in buildSelector.ts check if queryArgs === skipSelector, but we don't export it anywhere. We do use skipSelector over in buildHooks.ts, but as of right now no one else can use that.
We need to export skipSelector.

Hmm, the intention was really to just use that internally, to enable a skip behavior with the hooks. I don't really see a use case outside of hooks for that, but I might be wrong.
@SaulMoro - you've given that a :tada: - do you have a use case for that?

In the build-hooks logic I have had to implement the skipSelector operation differently, to achieve the same behavior as https://github.com/rtk-incubator/rtk-query/blob/next/src/core/buildSelectors.ts#L98

This is done by now.


Renormalize line endings for Storage

We're formalizing the line ending in CONTRIBUTING.md with #7570 and
\sdk\storage> git add . --renormalize

ensures all Storage files comply.  Please verify your client is correctly configured by checking that
git config --global core.autocrlf

returns true on Windows and input elsewhere.

FYI to configure the client, I believe you would execute:
git config --global core.autocrlf true


fine-tune a predecessor model

Would you provide the checkpoint of the predecessor model on the RTE dataset?
I cannot obtain the score as same as your BERT-base in the paper with the mentioned hyperparameter set.

I finally obtained the scores with other hyperparameters.


Unable to create agent from suggested method in README

Selecting "Start over" will say template already exists. Viewing template in dialogflow shows an empty template. Creating template again with different name produces same error as encountered initially.
https://storage.googleapis.com/dialogflow-oneclick/Regex-matching-agent.zip

@alex-dixon
Thanks for letting us know! Here's the correct one-click agent creation link the meantime while we update the README, https://console.dialogflow.com/api-client/oneclick?templateUrl=https://storage.googleapis.com/dialogflow-oneclick/Regex-sample.zip


mingw h265_find_startcode warning

src/h265/nal.c: In function ‘h265_find_startcode’:
src/h265/nal.c:129:30: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast]
  129 |  const uint8_t *a = p + 4 - ((long)p & 3);
      |                              ^
cc1: all warnings being treated as errors

@alfredh can you have a look?

Looks like this fixes the issue, but I`m not sure if this is the right fix and works on all platforms.
diff --git a/src/h265/nal.c b/src/h265/nal.c
index d51abec..f1624f5 100644
--- a/src/h265/nal.c
+++ b/src/h265/nal.c
@@ -126,7 +126,7 @@ bool h265_is_keyframe(enum h265_naltype type)

 static const uint8_t *h265_find_startcode(const uint8_t *p, const uint8_t *end)
 {
-       const uint8_t *a = p + 4 - ((long)p & 3);
+       const uint8_t *a = p + 4 - ((long long)p & 3);

        for (end -= 3; p < a && p < end; p++ ) {
                if (p[0] == 0 && p[1] == 0 && p[2] == 1)


Added mingw32-make compatible makefile

Added mingw32-make compatible makefile for ease-of-use on Windows. Had to manually alter the existing makefiles to get it setup on my system, as there was no MSYS archive.

:closed_book: MEV SW OD Build #27839 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-ts-trunk
FAILURE
59604
 Artifacts
IPU SDK Build

mev-trunk
FAILURE
56680
 Artifacts
Simics_C0_ACC

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

:closed_book: MEV SW OD Build #27894 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-trunk
FAILURE
56702
 Artifacts
IPU_IMC_6_6_4

mev-ts-trunk
SUCCESS
59633
 Artifacts

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

mev-ts-trunk BAT tests: success - build 59633 - it is required if PR have BAT MEV status check as mandatory. If failed, please review Tasks in provided link to Berta. For questions please contact with<EMAIL_ADDRESS>


Question about sectionizer in case of incomplete SectionRules

Hi, first of all, thanks for creating and open-sourcing this awesome module!
I was wondering how I should approach the problem of sectionizing a text with an incomplete list of SectionRules. For example: I'm only interested in a few sections, so I added SectionRules for those categories in my language. Currently, sections following my section of interest are also included in my section_span of interest. I could make a rule to catch those, but I expect that list could be quite long. Is there a way to put all other sections in an "other"-section? All my sections are separated by an empty line.

Hi! This is an issue I deal with pretty regularly and don't necessarily have a perfect solution to yet. One thing I do is take a sample of documents and run a regular expression pattern to match possible section titles (like re.compile("[a-zA-Z]+:\n") ), sort them by frequency, and then manually review them and add them to my SectionRules with a category of "other" or "unknown".
You could also just write a catch-all SectionRule using a regular expression like the one above to match unknown sections, but that runs the risk of overwriting the section rules you've manually curated. For that reason I usually try to generate an explicit list of "Other" patterns.

Thanks for the suggestions. I'll give it a try!


Scenario: Failed Login

Child Task of #16
Given I am on the New Tours Login Page
When I fill the account information for account BadUser into the Username field and the Password field
And I click the Sign In Button
Then I am redirected to the New Tours Sign On Page
And I verify the Registration Form Link exists

Part of an example project for showing how you should create stories and tasks to track your automated tests. Using Sentinel successfully is part of a larger process in which tests should be tied to tickets, which should be tied to code commits.


[Dialog] By default, actions display left-aligned

Material spec shows that actions appear end-aligned by default, but our dialog actions do not. We do have an align SCSS rule but it is undocumented.
I propose that we should be default right-align the actions. If this ends up being too big of a change for internal tests, then we should at least bring more awareness to the option in our docs.

A new MatDialogConfig property, which we could change the default button alignment would be nice. Something like:
{
   provide: MAT_DIALOG_DEFAULT_OPTIONS
   useValue: {
      buttonAlignPosition: 'end',
      restoreFocus: false
   }
}


Implement rules for AuthenticationTicket and ISecureDataFormat

Description
Currently we lack porting rules for Microsoft.Owin.Security. AuthenticationTicket and ISecureDataFormat.
Solution idea(s)
Implement porting rules.
Additional context
Add any other context or screenshots about the feature request here.

Looks fixed. Re-open if needed


found duplicate series

i'm getting this error on grafana dashboard "slow queries panel" both query A & B
would you please suggest?
execution: found duplicate series for the match group {ns="nytaxi.nyGreenTaxi", query_hash="8880B5AF"} on the right hand-side of the operation: [{db="nytaxi", instance="<IP_ADDRESS>:9179", job="mongodb-profiler", ns="nytaxi.nyGreenTaxi", op="command", query_framework="classic", query_hash="8880B5AF", query_shape="{'explain': {'find': '?', 'filter': {}, 'skip': '?', 'maxTimeMS': '?'}, 'verbosity': '?'}"}, {db="nytaxi", instance="<IP_ADDRESS>:9179", job="mongodb-profiler", ns="nytaxi.nyGreenTaxi", op="command", plan_summary="COUNT_SCAN { _id: 1 }", query_framework="classic", query_hash="8880B5AF", query_shape="{'aggregate': '?', 'pipeline': [{'$match': {}}, {'$count': '?'}], 'hint': '?', 'maxTimeMS': '?'}"}];many-to-many matching not allowed: matching labels must be unique on one side
query A

query B

try 1.8 or docker

thanks a lot it works now


[VCDA-3173] Control plane join using join script

For a multimaster cluster, the joining control plane nodes should use the join script instead of the control plane script.
Testing: successfully deployed multimaster cluster

This change is

controllers/vcdmachine_controller.go, line 194 at r2 (raw file):

var joinPostCustPhases = []string{
	NetworkConfiguration,
	KubeadmNodeJoin,

are there two phases of the same name @ltimothy7 ?


Use current time for aggregation

This PR is based on a discussion I had with Po-Han and Haleema. Basically, we actually should be using the current time to determine obsoletion in wifiscan entry aggregation. However, if we do not have a recent entry (so there is nothing to aggregate over), we just return the most recent entry (without any aggregation). This PR updates the aggregation logic as well as the tests.

Comments addressed, and I fixed javadoc issues (mvn javadoc:javadoc passes now, forgot to run it earlier).


count of faces detected

how do I know how many faces have been identified ?

  For example:
SparseArray<Face> faces = detector.detect(frame);
System.out.println("# of faces = " + faces.size());

thanks


About the hardware

Hello,
In your project, you used Google Coral Edge TPU USB Accelerator for deep learning model. Did you use a host machine with this USB, or mount the USB directly to the drone?
Thank you and best regards.

I personally have not had any issues with OpenCV and the ANAFI drone - the only little thing was I had to install opencv-contrib-python instead of the standard opencv build - no issues other than that.
Hopes this helps


Feature] create detector | make data source multi select field

Description
Makes the data source field a multisect field so that the user can select one or more indices. If mapping fields are not the same across the indices a callout message is shown.
Issues Resolved
Resolves #419
Screenshots

Check List

[ ] 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 #424 (d7cf62f) into main (0150c89) will decrease coverage by 1.62%.
The diff coverage is n/a.

:exclamation: Current head d7cf62f differs from pull request most recent head b2b15da. Consider uploading reports for the commit b2b15da to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #424      +/-   ##
==========================================
- Coverage   37.27%   35.65%   -1.62%
==========================================
  Files         111      111
  Lines        2986     3026      +40
  Branches      457      473      +16
==========================================
- Hits         1113     1079      -34
- Misses       1758     1832      +74
  Partials      115      115

Impacted Files
Coverage Δ

...gin/public/pages/CreateDetector/utils/constants.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

...mponents/DetectorDataSource/DetectorDataSource.tsx
6.25% <0.00%> (-65.63%)
:arrow_down:

...nts/ConfigureAlerts/containers/ConfigureAlerts.tsx
6.66% <0.00%> (-44.62%)
:arrow_down:

...alytics-dashboards-plugin/public/utils/helpers.tsx
58.44% <0.00%> (-5.20%)
:arrow_down:

...ts/UpdateAlertConditions/UpdateAlertConditions.tsx
50.00% <0.00%> (-5.18%)
:arrow_down:

.../components/AlertCondition/AlertConditionPanel.tsx
42.42% <0.00%> (-1.52%)
:arrow_down:

...pages/CreateDetector/containers/CreateDetector.tsx
8.51% <0.00%> (+0.08%)
:arrow_up:

...mponents/UpdateBasicDetails/UpdateBasicDetails.tsx
50.76% <0.00%> (+1.53%)
:arrow_up:

...onents/UpdateFieldMappings/UpdateFieldMappings.tsx
63.26% <0.00%> (+2.04%)
:arrow_up:

...nents/DefineDetector/containers/DefineDetector.tsx
12.30% <0.00%> (+9.80%)
:arrow_up:

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


[macOS export, 3.x] Simplify code signing options, add support for rcodesign tool for signing and notarization.

Backport of https://github.com/godotengine/godot/pull/64207

Thanks!


Exception of QR code generated by specific length data

e.g.
200505150001

Whaow, I'll look into it, thanks for your report!

Fixed and deployed<EMAIL_ADDRESS>Thanks for your report :)


Fetch support

thx for this amazing lib :)

You're welcome 😀
Can you explain more what you mean by "fetch support" - what does it look like in practice for you?

thanks for your reply, this is what i mean

the possibility of popularizing the selections with resources from outside

It is possible today. Here is an example:
import { createResource, createSignal } from "solid-js";
import { Select } from "@thisbeyond/solid-select";

const fetchData = async (inputValue) =>
  await new Promise((resolve, reject) => {
    setTimeout(() => {
      resolve(
        ["apple", "banana", "pear", "pineapple", "kiwi"].filter((option) =>
          option.startsWith(inputValue)
        )
      );
    }, 800);
  });

export const AsyncFetchExample = () => {
  const [inputValue, setInputValue] = createSignal("");
  const [options] = createResource(inputValue, fetchData, { initialValue: "" });
  const loadingOption = "Loading...";

  return (
    <Select
      readonly={false}
      onInput={setInputValue}
      options={options.loading ? [loadingOption] : options()}
      isOptionDisabled={(option) => option === loadingOption}
    />
  );
};

That said, this could be made nicer by supporting async functions and a 'loading' message directly in the component itself. I'll have a think about that.

This is now simpler with release 0.8.0 and the createAsyncOptions helper.
import { Select, createAsyncOptions } from "@thisbeyond/solid-select";

const fetchData = async (inputValue) => {
  return await new Promise((resolve) => {
    setTimeout(
      () =>
        resolve(
          ["apple", "banana", "pear", "pineapple", "kiwi"].filter((option) =>
            option.startsWith(inputValue)
          )
        ),
      500
    );
  });
};

export const AsyncFetchExample = () => {
  const props = createAsyncOptions(fetchData);
  return <Select {...props} />;
};

I was looking for a way to debounce HTTP requests. Here's the code I'm using for future reference:
import { createAsyncOptions, Select } from '@thisbeyond/solid-select';
import { debounce } from '@solid-primitives/scheduled';

export default function () {
    const props = createAsyncOptions(fetchData);

    return <Select {...props} onInput={debounce(props.onInput, 300)} />;
}

Let me know if there's a better way to do it. Would be nice to have more examples of common use cases in the documentation.

This is also something else that I'm interested in!


Add loading Skeleton instead of simple loading for cards in Posts page to look professional

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

Something like this

Use Case
Add loading skeleton instead of simple loader
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Confused between level 1 and 2 for label. Will assign it after reviewing the work.

@VaibhavArora314 okay added the skeletons kindly check it

Confused between level 1 and 2 for label. Will assign it after reviewing the work.


[Nord Dark] Centaur-tabs displaying incorrectly

What happened?
Upon loading a file in doom emacs, the tabline is displaying incorrectly.

What did you expect to happen?
The tabline should display correctly as it does with other themes
Steps to reproduce

Open doom emacs
Enable centaur tabs in init.el
Doom Sync and open a file

System Information

Emacs version: emacs-plus@28 with native-comp
Emacs distro: Doom-Emcas
Operating system: MacOS 11.4
Installed commit of doom-themes: Latest
Which theme are you using: Doom-nord

This was fixed in 5d30984, but I haven't yet bumped the pin for the doom-themes package in Doom Emacs yet.
To unpin the package:added (unpin! doom-themes) to ~/.doom.d/packages.el, then run doom sync -u and restart Emacs.


proposal: go get should trim https:// from package arguments affected/package: cmd/go

Proposal
go get should strip leading https:// off package arguments automatically.
That is to say if I for instance execute
$ go get https://github.com/shurcooL/githubv4

it should be smart enough to negotiate https://github.com/shurcooL/githubv4 to github.com/shurcooL/githubv4, perhaps with a message informing the user it has done so.
Rationale
This happens to me all the time:
I find the package I want to use on GitHub. I see the name of the package in the address bar presented without the protocol portion of the address (e.g. https://)

I hit ⌘-L and select the address, still no visible protocol. ⌘-C to copy

Then I open my terminal and type go get  and hit ⌘-C and enter

I receive

go: malformed module path "https:/github.com/shurcooL/githubv4": invalid char ':'

Other notes
I concede this isn't a Go issue but rather a a Chrome issue, hiding the protocol from the user, or a personal issue given that my brain can't seem to remember I'm not copying what I see selected.
That said, I also suspect I can't be the only person who encounters this on a regular basis. I suspect handling it more gracefully would make the go get command just a little more friendly.

Duplicate of #12701