@prefresh/webpack @prefresh/next webpack_require(...) is not a function

@prefresh/webpack version 3.0.0 does not work with @prefresh/next.

Problem in method "matcher" in class "ReloadPlugin".
It looks like the constant "nextMatcherOptions" excludes the modules needed for prefresh to work.
if replace in the file "@prefresh\webpack\src\utils"
exports.nextMatcherOptions = {
   include: /\.([jt]sx?)$/,
   exclude: /node_modules\/(?!next[\\/]dist[\\/]next-server[\\/]lib).*/,
};
with
exports.nextMatcherOptions = {
   include: /\.([jt]sx?)$/,
   exclude: /node_modules/,
};
everything works fine

I guess this is only an issue with latest next since they must've changed something that breaks this regex, this regex is intentionally so so that next/async and next/router would work.

I guess this is only an issue with latest next since they must've changed something that breaks this regex, this regex is intentionally so so that next/async and next/router would work.

we still have no solution?
@JoviDeCroock

we still have no solution?
@JoviDeCroock

That's kinda rude 😅 there is no outline of what the issue is, can't reproduce it currently

That's kinda rude 😅 there is no outline of what the issue is, can't reproduce it currently

There is no outline of what the issue is, can't reproduce it currently. #260 runs next-latest and isn't running into this issue, is there some special next dep that you're using in here? @NewNik

Used this example
https://github.com/developit/nextjs-preact-demo
when npm install works correctly
when yarn install gets error __webpack_require __ (...) is not a function
The bottom line is that npm installs packages according to package-lock.json
yarn ignores package-lock.json and installs new versions of packages
package-lock.json

yarn.lock after yarn install

Comparing the versions of the prefresh packages, I came to the conclusion that the problem is in the<EMAIL_ADDRESS>This problem was described above

There is no outline of what the issue is, can't reproduce it currently. #260 runs next-latest and isn't running into this issue, is there some special next dep that you're using in here? @NewNik

Used this example
https://github.com/developit/nextjs-preact-demo
when npm install works correctly
when yarn install gets error __webpack_require __ (...) is not a function
The bottom line is that npm installs packages according to package-lock.json
yarn ignores package-lock.json and installs new versions of packages
package-lock.json

yarn.lock after yarn install

Comparing the versions of the prefresh packages, I came to the conclusion that the problem is in the<EMAIL_ADDRESS>This problem was described above

Have you tried using the official next plugin? https://github.com/preactjs/next-plugin-preact/tree/master/packages/next-plugin-preact

Have you tried using the official next plugin? https://github.com/preactjs/next-plugin-preact/tree/master/packages/next-plugin-preact

Yes, tried building next app with preact using plugin https://github.com/preactjs/next-plugin-preact/tree/master/packages/next-plugin-preact
The error described in the first message occurs

Yes, tried building next app with preact using plugin https://github.com/preactjs/next-plugin-preact/tree/master/packages/next-plugin-preact
The error described in the first message occurs

Just ran yarn when using latest and it works for me, could you describe or provide a reproduction repository?

Just ran yarn when using latest and it works for me, could you describe or provide a reproduction repository?

Here is a link to an example with an error.
https://github.com/NewNik/preact-plugin-test
The app starts and builds, but yarn dev renders a blank page (body {display: none;}). In the browser console you can see the error __webpack_require __ (...) is not a function

Here is a link to an example with an error.
https://github.com/NewNik/preact-plugin-test
The app starts and builds, but yarn dev renders a blank page (body {display: none;}). In the browser console you can see the error __webpack_require __ (...) is not a function

Will try this out later today https://github.com/JoviDeCroock/prefresh/pull/262

Will try this out later today https://github.com/JoviDeCroock/prefresh/pull/262


chore: add issue templates

Adapted from the walrus-sites repository.
Closes #89

Very cool, thanks @mlegner . In general, i find the [Item name] title to be redundant with the labels, but otherwise looks good!

Yes, I'm not too sure about them myself. I will remove them. 👍


Option blocks are not formatted

Blocks like this are not formatted:
    optional int32 fieldname = 1 [(
fieldopt
) = {
s
:
'FieldAnnotation'
}];

This issue is closed as plugin is not supported anymore.
Please switch to https://github.com/jvolkman/intellij-protobuf-editor.


Update Packet CCM to v1.0.0

What this PR does / why we need it:

Update Packet CCM to v1.0.0
Automatically create a secret with credentials and configuration needed for the CCM
Kubernetes 1.15.0+ is now required for Packet

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #750
Does this PR introduce a user-facing change?:
Update Packet CCM to v1.0.0
Automatically create a secret with credentials and configuration needed for the CCM
Kubernetes 1.15.0+ is now required for Packet

/hold cancel
the PR is tested and the doc change is not required anymore

/retest


Add redis documentation to main index.rst

Fixes #5357

@crwilcox The docs build fails on Circle CI:
reading sources... [100%] vision/index

Warning, treated as error:
autodoc: failed to import module 'google.cloud.redis_v1beta1'; the following exception was raised:
No module named 'google.cloud.redis_v1beta1'


fix(Storybook): set theme and props before render

Description
During some keyboard layout debugging, I encountered a couple glitches that could be attributed to storybook rather than the component.
With the following logs set in Keyboard:

It was observed that:

An initial render was happening without the desired props
a setTheme event was triggering after the component's first update.

After these changes, no setTheme event fires after the component mounts, and the props are set as expected on initial render.

Testing
This is not a Component change, should just confirm storybook is working as expected.
Checklist

[x] all commented code has been removed
[x] any new console issues have been resolved
[x] code linter and formatter has been run
[x] test coverage meets repo requirements
[x] PR name matches the expected semantic-commit syntax

Only thing I didn't look at was argActions... Not entirely sure what they are? Could look at bringing that up into the earlier property patch as well.

Test Execution Failed.

Test Execution Failed.

Test Execution Failed.

Test Execution Failed.


Additional Testing for Axial Expansion Changer

Add two tests to axial expansion changer.

Verify volume fraction conservation
Verify that block masses are not conserved.

This can be checked simultaneously when the target component mass conservation is checked.
There may be an opportunity to coalesce checks for i) block density conservation, ii) block mass non-conservation, iii) target component mass conservation.
This should be done with thermal expansion on a single assembly for efficiency.

Originally posted by @jakehader / @mgjarrett in https://github.com/terrapower/armi/pull/845#issuecomment-1222821586 / https://github.com/terrapower/armi/pull/845#issuecomment-1222921652

Duplicate of #848


youtube command not working

Every time i try to use the !youtube command it says this: Please setup YOUTUBE_KEY in config.js to use the !youtube command.

Fixed, sorry about that.


Not Working Laravel 7x & Nova 3x

I tried creating a redirect, which saved ok with exception to the type now updating correctly but when I try and visit a page that I added a redirect for it doesn't redirect, not sure what exactly this package is supposed to do but it doesn't seem to work.

I used the tool to create my redirects.
I then made a "Redirect" middleware and used the Model provided by the tool to chech for a redirect and redirect the user.
`<?php
namespace App\Http\Middleware;
use Closure;
use OptimistDigital\NovaRedirects\Models\Redirect as RedirectModel;
class Redirect
{
/**
* Handle an incoming request.
*
* @param  \Illuminate\Http\Request  $request
* @param  \Closure  $next
* @return mixed
*/
public function handle($request, Closure $next)
{
$redirect = RedirectModel::whereFromUrl($request->path())->first();
    if ($redirect) {
        return redirect($redirect->to_url);
    }

    return $next($request);
}

}`
Assign it in the HTTP Kernel.
protected $middleware = [         //...         \App\Http\Middleware\Redirect::class,     ];
Seems to work.

I used the tool to create my redirects.
I then made a "Redirect" middleware and used the Model provided by the tool to chech for a redirect and redirect the user.
`<?php
namespace App\Http\Middleware;
use Closure;
use OptimistDigital\NovaRedirects\Models\Redirect as RedirectModel;
class Redirect
{
/**

Handle an incoming request.

@param \Illuminate\Http\Request $request
@param \Closure $next
@return mixed
*/
public function handle($request, Closure $next)
{
$redirect = RedirectModel::whereFromUrl($request->path())->first();

    if ($redirect) {
        return redirect($redirect->to_url);
    }

    return $next($request);
}

}`
Assign it in the HTTP Kernel.
protected $middleware = [ //... \App\Http\Middleware\Redirect::class, ];
Seems to work.

I expected this to be part of the package rather than having to create my own, which could easily be done without the package.

Hi all, why is this package needed in nova?, I am trying to do a simple redirect inside a middleware I have created for nova and it is not redirectling correctly, can someone tell me why?
    public function handle($request, Closure $next)
    {

         if ($request->path() === 'admin/dashboards/main')
        {

        // This user is not a paying customer...
             return $next($request);
        }

      return redirect('/admin/dashboards/main');
    }

I have submitted a PR to introduce a middleware for this: https://github.com/optimistdigital/nova-redirects/pull/5


How can I give input rtsp?

Hello,
I want to give rtsp link instead of mp4 as input. How can I do it?
Thanks.

Were you able to use rtsp as input?


Ability to silence "Invalid arguments." response.

I don't think there's a way to silence the "Invalid arguments." response when someone uses a command incorrectly. I have a plugins setup to ignore some channels from the config, but if someone enters the command incorrectly in the ignored channel "Invalid arguments." is still posted.
The response is called from plugins/command.py before the plugin's command function so I added a quick option to the decorator 1a945cf4b94e1f9f8ae8c70d0db40760ebc8ca66 to where it can be set like the the permissions or public arguments.
@command(quiet=True)
def w(self, mask, target, args):
    # rest of command....

I don't know if the option already exists and I'm missing it or if there's a better solution. I'm not a super experienced with python, so hopefully someone else can help

No it doesn't exist. You can provide a PR if you want.

Okay cool, I'll clean it up a bit and submit a PR then.


[Feature Request] Support environment variables in log formatting

Adding a request to support environment variables in our log formatting, perhaps using the ENV key (similar to REQ, RESP, etc).  HOSTNAME is an already supported keyword pulled from the environment--this feature would expand on that.
Some values are known ahead of time and can be baked into the log format.  However, the use case would be for logging runtime values (host IP, AZ, etc) that are only known when the container is deployed.  Our current solution is to parse the config file, injecting selected envvars, etc before booting the service.
access_log:
  - name: envoy.access_loggers.file
    config:
      path: /dev/stdout
      json_format:
        hostname: "%HOSTNAME%"
        method: "%REQ(:METHOD)%"
        app_version: "%ENV(APP_VERSION)%"
        private_ip: "%ENV(PRIVATE_IP)%"
        region: "%ENV(REGION)%"

export APP_VERSION=0.1.0
export PRIVATE_IP=<IP_ADDRESS>
export REGION=us-east-1
envoy -c envoy.yaml

#=> {
  "hostname":"macbook-pro",
  "method":"GET",
  "app_version": "0.1.0",
  "private_ip": "<IP_ADDRESS>",
  "region": "us-east-1"
}

The code to edit is in here: https://github.com/envoyproxy/envoy/blob/master/source/common/formatter/substitution_formatter.h. And related users.

Hi @yozaam! Have you already started to work on this?
I also got an interest in this feature request, so if you haven't, I would like to take it. (never mind if you have:+1:)

Hi @yozaam! Have you already started to work on this?
I also got an interest in this feature request, so if you haven't, I would like to take it. (never mind if you have👍)

Hey @musaprg go ahead :D

/assign @Shikugawa


Add powerup timers to NMZ plugin

Wondering if there can be an addon that shows the time till the next powerup and the time till the powerup ends once activated

Do you know how the power ups are programmed? They almost seem random with regards to when they appear. A timer feature that lets you know how long they take until they end would be helpful but also another timer that tells you how long until the power up disappears (if you haven't activated it) would be very useful.


Typo in tslib version makes installation impossible

The double ^^ in front of the tslib version in package.json breaks the installation process of this project's version 10.0.1.
➤ YN0000: · Yarn 4.0.2
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error<EMAIL_ADDRESS>isn't supported by any available resolver
    at vd.getResolverByDescriptor (<projectpath>\.yarn\releases\yarn-4.0.2.cjs:141:1698)
    at vd.bindDescriptor (<projectpath>\.yarn\releases\yarn-4.0.2.cjs:141:1083)
    at St.preparePackage (<projectpath>\.yarn\releases\yarn-4.0.2.cjs:210:6173)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ne (<projectpath>\.yarn\releases\yarn-4.0.2.cjs:210:7583)
    at async Promise.allSettled (index 20)
    at async Uc (<projectpath>\.yarn\releases\yarn-4.0.2.cjs:140:53248)
➤ YN0000: └ Completed in 0s 358ms
➤ YN0000: · Failed with errors in 0s 373ms

Fixing this would be great! Thank you 😊

try v10.0.2

Both new versions 10.0.2 and 11.0.0 work now. Thanks!


Issue with Bond + Python bindings and nullable<>

Note: We’re using the Python bindings to consume the generated code in Python.
My bond file looks like this:
namespace Bug

struct A
{
    0: string value;
}

struct B
{
    0: nullable<A> nullableA;
    1: A a;
}

In Python, I do this:
b = B()
b.a.value = ‘test’
b.nullableA = A()
b.nullableA.value = ‘test’

I expect that both of those will do the same thing, but it looks like the second one (b.nullableA.value = ‘test’) doesn’t have any effect at all.
On the other hand, this works:
b = B()
a = A()
a.value = ‘test’
b.nullableA = a

I dug into this a little bit more and determined that in C++, the above pattern doesn’t even seem to be possible because the nullableA member of B is of type nullable<A> and thus doesn’t even have a property called value. Moreover there doesn’t seem to be an implicit conversion between A and nullable<A> in C++ -- but in Python there does seem to be (actually the nullable-ness of a property seems to make no difference at all in Python from what I can tell by looking at objects in the Python debugger). In C++ it seems you’re always forced to do a 2-step style initialization (which also works above in Python).
Is this intended behavior, or an artifact of how the python bindings in bond work?
It certainly caught me by surprise.

@chwarr suggested I try b.nullableA.value.value = ‘test’ which didn't work due to this Python error: ‘A’ object has no attribute ‘value’
He also mentioned it might be a good idea to seek advice from @sapek on this topic as he might be more familiar with the Python bindings.

Looking at the implementation of the Python bridge, it appears that full handling for nullable/maybe is missing. More debugging is needed to confirm this and propose a fix.
Unfortunately, I do not have the time right now to do this debugging, so I'm going to leave this issue open so that we have something to keep track of this problem.
If you end up digging into this, a PR with a fix would be appreciated.

I've spent over a week to figure out the issue with my feature/product and in the end it turned out this bond issue being culprit, please help to fix this bug asap, thanks.


[#55] Update UserGuide.md

General
Contacts

#55

Codecov Report

Merging #62 (b0d41ee) into master (d8659eb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #62   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d8659eb...b0d41ee. Read the comment docs.


DAC voting, base fee proposal

Why this should be merged
This PR adds feature of DAC proposals and voting which is executed with transactions.
Also, this PR renames all DAO entries to DAC.
How this works
There are 3 new transactions:

AddProposalTx, it contains proposal bytes and proposer address/auth. In addition to fee burning, this tx will bond some tokens. Also, this tx must be additionally signed by proposer.
AddVoteTx, it contains vote bytes, voter address/auth and proposalID (id of addProposalTx). This this must be additionally signed by voter.
FinishProposalsTx is system tx. It will finish all expired (both successful and failed) and early (again both successful and failed)  proposals, tx body contains those proposal ids.

Vote and proposal fields in txs represented by bytes, not some structure or interface. This is done in order to be able to add new proposal types without needing to update codec.
Block builder will try to build block with FinishProposalsTx when there are early finished proposals or expired proposals.
Proposals execution and semantic verification logic resides in its own proposalExecutor type methods in txs/executor package. Proposals are calling this methods via visitor pattern.
Proposals and votes logic are encapsulated behind interfaces, which could be implemented by different types. This PR adds BaseFeeProposal and SimpleVote types.
SimpleVote is vote that simply points to specific proposal option index, e.g. baseFee proposal with options [ {newFee: 100}, {newFee: 200} ], and simpleVote {0}, where vote is for newFee 100 option.
BaseFeeProposal is proposal to change base fee, its options are new base fees. This proposal can only be proposed by caminoProposer address state role, which is introduced in this PR as well.
All proposals can be voted only by addresses that were active validators at the moment of addProposalTx block execution. While its not required for voters to still be active valaditors when they vote, it is required for them to still be consortium members.
How this was tested
Unit-tests, integration tests

I added "version" without base fee proposal, see last 2 commits. First commit removes all base fee related stuff, then second adds it back. As you can see from first commit, it will unfortunately remove a lot of transaction tests, cause we need at least one proposal type in order to create them. And I don't want to add dummy proposal type, cause then we'll need to modify proposals visitors to include this type.


Reduce usage of transmute to the strictly necessary

Why
Transmute can result in undefined behaviour. Should be used only when there are no alternatives.
What
Some functions of the multi-signature use transmute to change between types of the underlying blst library. While this currently works, a change in the blst API could have disastrous consequences.

Closing in favour of #690. See here for a comment on why


[WIP][Feature] [REST-API]add rest api for runningjob detail

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

GET http://localhost:5801/hazelcast/rest/maps/running-jobs

return info
[
  "{\"vertices\":[{\"id\":1,\"name\":\"Console(id=1)\",\"parallelism\":2},{\"id\":2,\"name\":\"FakeSource(id=2)\",\"parallelism\":1},{\"id\":3,\"name\":\"FakeSource(id=3)\",\"parallelism\":1}],\"edges\":[{\"inputVertex\":\"FakeSource\",\"targetVertex\":\"Console\"},{\"inputVertex\":\"FakeSource\",\"targetVertex\":\"Console\"}],\"jobId\":675252797213507585}"
]

#4044

response
[
  {
    "vertices": [
      {
        "id": 1,
        "name": "Console(id=1)",
        "parallelism": 2
      },
      {
        "id": 2,
        "name": "FakeSource(id=2)",
        "parallelism": 1
      },
      {
        "id": 3,
        "name": "FakeSource(id=3)",
        "parallelism": 1
      }
    ],
    "edges": [
      {
        "inputVertex": "FakeSource",
        "targetVertex": "Console"
      },
      {
        "inputVertex": "FakeSource",
        "targetVertex": "Console"
      }
    ],
    "jobId":<PHONE_NUMBER>30910465,
    "initializationTime": "2023-02-08 13:52:03"
  },
  {
    "vertices": [
      {
        "id": 1,
        "name": "Console(id=1)",
        "parallelism": 2
      },
      {
        "id": 2,
        "name": "FakeSource(id=2)",
        "parallelism": 1
      },
      {
        "id": 3,
        "name": "FakeSource(id=3)",
        "parallelism": 1
      }
    ],
    "edges": [
      {
        "inputVertex": "FakeSource",
        "targetVertex": "Console"
      },
      {
        "inputVertex": "FakeSource",
        "targetVertex": "Console"
      }
    ],
    "jobId":<PHONE_NUMBER>35917057,
    "initializationTime": "2023-02-08 13:35:57"
  }
]


Add new AArch64 nodes to readme

Update readme to include new AArch64 nodes.

AArch64 for Amazon Linux 2
AArch64 for CentOS 8
AArch64 for Debian 10
AArch64 for Ubuntu 18.04
AArch64 for Ubuntu 20.04

I am working on a PR to update the Swift Community-Hosted CI Platforms and links on the Swift readme as well. Should be up  today.


Reconsider Api Response Wrapper Object

Some classes may be deletable
Simple request dont need an extra class

@NilsPur is this still open? if yes - is this a useful feature?


Add API response time and sanity functional test.

Update .gitignore and add .eslintignore

Make git ignore composer.covered.
Do not run eslint on all node_modules and wdio_report. Eslint ignores node_modules folder in root folder by default, but does not ignore /test/end-to-end/node_modules. There's a app.js inside wdio_report. Eslint should ignore that.

Add API response time and sanity functional test.

Check API response time to find API issue ASAP.
Reload browser before test suite starts to clear browser session.
Add "cockpit" into eslintConfig global to avoid eslint error.

In this PR, I added one API test for review. The rest of APIs will be added in the following PRs.

@larskarlitski and @martinpitt, thanks for review. I agree with you. I'll change to 1 second.


Lost host connectivity between 2 of the host in a setup with 3 hosts.

Fresh install of v0.59.1.
Had 3 hosts and connectivity between them were working as expected.
Created few services.
Upgraded to v0.63.0-rc3.
After sometime , Lost host connectivity between 2 of the host in a setup with 3 hosts.
3 hosts in the set up - sangee0591-10acre-1, sangee0591-10acre-2 and sangee0591-10acre-3
Connectivity between sangee0591-10acre-2 and sangee0591-10acre-3 is lost.
swanctl --list-sas  on sangee0591-10acre-3  shows connection to sangee0591-10acre-1 but not to sangee0591-10acre-2.

This issue was due to a ipsec rekey collision.  The rekey times need to be adjusted to avoid this.

@ibuildthecloud I see you've fixed this in network agent 0.8.1. I've hit this bug, so is there anyway of upgrading to this version in Rancher, or do I need to wait for the next version? Or can I increase the number of hosts to circumvent it?

@philmes You'll have to wait for the next RC (1.0.0-rc1, which will be in about 12 hours from now).  I've changed is such that when building a tunnel rekey will be initiated from one side only.  The rekey timeout is the default 4 hours for one side and the other will be set to 1 year.  This effectively means that only one side will initiate rekey.  https://github.com/rancher/cattle/pull/1526

Tested with rancher-server v1.0.0-rc1 and v1.0.0-rc2 .
Have not encounter the issue with connectivity between hosts being lost.


TEST-#5340: Use dev requirements in test-ray-master to get fastparquet

Signed-off-by: mvashishtha<EMAIL_ADDRESS>
What do these changes do?
TEST-#5340: Use dev requirements in test-ray-master to get fastparquet

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5340
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

How were we getting away with this before?

@pyrito environment-dev.yml is quite close to requirements-no-engine.yml. Extra dependences that I notice are scikit-learn, pymssql, and psycopg2, fastparquet, pygit2, and pandas-stubs. It doesn't look like any test uses skit-learn. pygit2is needed for the release notes tool only.pandas-stubsI'm not sure about.psycopg2andpymssql` are needed for SQL I/O tests that we run on test-ubuntu but on push-to-master.
I recall that the fastparquet test was added fairly recently.

How were we getting away with this before?

@pyrito environment-dev.yml is quite close to requirements-no-engine.yml. Extra dependences that I notice are scikit-learn, pymssql, and psycopg2, fastparquet, pygit2, and pandas-stubs. It doesn't look like any test uses skit-learn. pygit2is needed for the release notes tool only.pandas-stubsI'm not sure about.psycopg2andpymssql` are needed for SQL I/O tests that we run on test-ubuntu but on push-to-master.
I recall that the fastparquet test was added fairly recently.

I see. We also probably turned a blind eye to the push-to-master tests 😛

@mvashishtha have you checked that this change actually works?

@mvashishtha have you checked that this change actually works?

@pyrito no, but I think it should give the fastparquet dependency, so I'm pretty hopeful. Also I've tried to copy the steps from test-ubuntu, which passes in CI: https://github.com/modin-project/modin/blob/261e29606d3ff18b71396c3e2abc640f0634c5eb/.github/workflows/ci.yml#L623-L648
Unfortunately I couldn't test this locally because conda env create -f environment-dev.yml was giving
conda.exceptions.ResolvePackageNotFound:
  - ray-default[version='>=1.4.0']

Since the test is already broken and it's a bit of extra work to make a workflow that does what I'm trying here in ci.yml, test that it passes, then revert the change, I'd rather just give this a try as is.


Update angular-cli version to latest version

Using<EMAIL_ADDRESS>cause following error on run:

You have to be inside an ember-cli project in order to use the serve command.

Updating angular-cli to latest version fix it

@vincentchalamon Thank you so much for your contribution and spotting the error! I like to use fixed versions due to the frequent changes and the resulting problems with it. So I made some changes and updated the description as well.
Just realising that you might wanted to do it yourself, if I had told you. So sorry for not accepting your pull request. I'm trying to learn to delegate tasks ;-).
It would be great, if you could check whether the latest version from npm works for you.
Thanks again and hope to hear from you.


panic when MQTT broker is not running

When running device-mqtt without a MQTT broker, a friendly message is printed, but there is still a panic somewhere in the code:
Aug 22 14:14:56 systemd[1]: Started Service for snap application edgex-device-mqtt.device-mqtt.
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: Init: useRegistry: consul://localhost:8500 profile: res confDir: /var/snap/edgex-device-mqtt/x1/config/device-mqtt
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: Check registry is up... http://localhost:8500
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: Register in registry...
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: Calling service.Start.
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: EnableRemote is false, using local log file
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.639659055Z app=edgex-device-mqtt source=init.go:137 msg="Check Metadata service's status ..."
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.639701876Z app=edgex-device-mqtt source=init.go:137 msg="Check Data service's status ..."
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.646675345Z app=edgex-device-mqtt source=init.go:47 msg="Service clients initialize successful."
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.649698772Z app=edgex-device-mqtt source=service.go:135 msg="Trying to find Device Service: edgex-device-mqtt"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.649751462Z app=edgex-device-mqtt source=loader.go:250 msg="listen for config changes from Registry"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.654158009Z app=edgex-device-mqtt source=service.go:149 msg="Device Service edgex-device-mqtt exists"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.656532727Z app=edgex-device-mqtt source=loader.go:274 msg="Writeable configuration has been updated. Setting log level to DEBUG"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.658627786Z app=edgex-device-mqtt source=service.go:152 msg="Device Service in Core MetaData: edgex-device-mqtt"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.666558198Z app=edgex-device-mqtt source=profiles.go:39 msg="created absolute path for loading pre-defined Device Profiles: /var/snap/edgex-device-mqtt/current/config/device-mqtt/res"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.672861268Z app=edgex-device-mqtt source=devices.go:22 msg="Loading pre-define Devices from configuration"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.675785868Z app=edgex-device-mqtt source=restrouter.go:21 msg="init status rest controller"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.675820243Z app=edgex-device-mqtt source=driver.go:279 msg="Create MQTT client and connection: uri=tcp://admin:public@<IP_ADDRESS>:1883 clientID=CommandResponseSubscriber "
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=INFO ts=2019-08-22T19:14:56.675843807Z app=edgex-device-mqtt source=driver.go:279 msg="Create MQTT client and connection: uri=tcp://admin:public@<IP_ADDRESS>:1883 clientID=IncomingDataSubscriber "
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.678805457Z app=edgex-device-mqtt source=restrouter.go:24 msg="init command rest controller"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: level=DEBUG ts=2019-08-22T19:14:56.681865584Z app=edgex-device-mqtt source=restrouter.go:30 msg="init callback rest controller"
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: panic: start command response Listener failed, please check MQTT broker settings are correct, Network Error : dial tcp <IP_ADDRESS>:1883: connect: connection refused
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: goroutine 75 [running]:
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: github.com/edgexfoundry/device-mqtt-go/internal/driver.(*Driver).Initialize.func1()
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]:         /root/parts/device-mqtt/src/internal/driver/driver.go:73 +0xac
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]: created by github.com/edgexfoundry/device-mqtt-go/internal/driver.(*Driver).Initialize
Aug 22 14:14:56 edgex-device-mqtt.device-mqtt[40511]:         /root/parts/device-mqtt/src/internal/driver/driver.go:70 +0xa2
Aug 22 14:14:56 systemd[1]: snap.edgex-device-mqtt.device-mqtt.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

It would be nice if:

an ERROR level message was logged when this happens
we didn't panic and instead output a message and exit with os.Exit(1)

that's the issue we have to improve.
@weichou1229 please fix this when you have time

@weichou1229 please fix this issue next week


Exactly the same dashboard (with the executive summary) should be created for Lotus, so both nodes are easily comparable.

We don't plan hosting Lotus node in the Forest team.


Feat: Add logs to devices routes

Description
Adds logs to devices routes and their respective service, to put them in the same pattern as the API and make it easier to find logs.
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[x] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I run go fmt ./... to check that my code is properly formatted
[x] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #508 (9b1617e) into main (dd4dd2c) will increase coverage by 0.10%.
The diff coverage is 28.71%.

@@            Coverage Diff             @@
##             main     #508      +/-   ##
==========================================
+ Coverage   31.21%   31.32%   +0.10%
==========================================
  Files          33       33
  Lines        3232     3240       +8
==========================================
+ Hits         1009     1015       +6
  Misses       2126     2126
- Partials       97       99       +2

Impacted Files
Coverage Δ

pkg/routes/updates.go
6.59% <0.00%> (ø)

pkg/services/devices.go
60.14% <21.05%> (-1.22%)
:arrow_down:

pkg/routes/devices.go
30.47% <30.86%> (+3.29%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dd4dd2c...9b1617e. Read the comment docs.


Your Requirments could not be resolved

hey guys
i'm using :
laravel  5.6.26
PHP Version 7.2.0
i installed the voyager and i want to install the voyager-frontend and when i run :
composer require pvtl/voyager-frontend

plz help

This means that you need to enable the mentioned extensions in your Apache. The sqlite3 extension in your case.


Ligatures not working

Hi I'm a bit of a tech noob so please bear with me.
-> is not turning to → for me, it appears this is an issue with ligatures when I went to the obsidian forum, but the description for the theme says ligatures should be supported.
When I use other themes like California Coast or Sanctum either, if that matters.
I remember I've gotten them to work on Obsidian for me in the past so I'm not sure why I haven't been able to have them work in recent months.

Ok, seems like the JetBrains font was missing locally, so installing that solved the issue for me.

The default theme is using the Inter font, which provides these ligatures. You can manually add it in the Style Settings plugin at the beginning of the fonts list.

Thanks, @hsiktas for clarifying! Yes, Things uses -apple-system font, which does not feature ligatures in edit or preview mode (non-code, which uses JetBrains). If you'd like to have ligatures outside code, I'd also recommend using Inter font (featured in the default theme) as it's very similar, and adding to the beginning in Style Settings. Thanks!


plans to make the context creation re-usable?

I remember a discussion about making the context creation code (and .packages support, and sdk extensions support) more easily consumable by other packages. This would allow other tools (like dartdoc) to create contexts and analyze code without duplicating a lot of this package's logic. (I wasn't able to find a tracking bug for this)
@pq @keertip

I don't think there's a tracking bug but there's been A LOT of discussion about a rework of context management with an eye towards (among other things) improved opportunities for reuse.  It's great to bear more uses cases in mind (if @stereotype441 hasn't considered this one already...) so thanks!

Hm, I wasn't aware that the context refactoring work would touch on this. I was speaking more of reusing the code in analyzer_cli, so that CLI clients consuming the analyzer package would have less code duplication.

Yes, but our plan for doing that includes making it general enough to use in both cli and server, as well as by other clients.

Here's that tracking bug for the ContextManager rework: https://github.com/dart-lang/sdk/issues/24133.  Closing this in favor of taking any continued conversation there.


Fix/optimize images

Two fixes for images:

mogrify src/qt/res/*/*/*.png - should fix "libpng error: IDAT: chunk data is too large" error
add Dash-specific paths to folders in optimize-pngs.py script and execute it - should result in ~500Kb reduction of total size

Ideally, we should be running these 2 steps each time we add new image for this new image only. However, we added a bunch of images without running mogrify and we never used optimize-pngs.py on Dash-specific images afaik, so I executed both steps on all of them to make sure we didn't miss any.

utACK

utACK


Update Algorand Releases + Add to official repo

Summary
The latest version of indexer is 2.3.4, but the releases page: https://releases.algorand.com/ lists 2.3.3. This should be updated. Also wanted to see if indexer could be included in the package repo so that developers may be able to do something like:
apt-get install algorand-indexer instead of manually downloading the binary and running it.
Urgency/Relative Priority
Low

Thanks for the submission! The releases page should be up to date now. We've been considering the latter as well.

Scope of this would be for researching adding the existing package to our repository and testing it.

Thanks @onetechnical. Yeah not sure what your internal SDLC is, but just wanted to make the request to add it to the repo known. You can close this out or keep this open to keep track of this request. However you see fit.

Any update on this?

Just wanted to ping this issue again to make sure it's not forgotten.

Looks like this page is being updated properly now, thanks for your persistence.

This is awesome!!! Thanks!

@winder opening this again. Seems I can no longer do apt-get install algorand-indexer.


Emit 'reauthenticate' instead of 'signin' when unauthenticated

Fixes #57

Ready for review!

:clap:


Add Usage for NixOS

There is a simpler way to add hosts file on NixOS machines. I thought it would be nice to share.
Also sorry, I wanted to PR into my own branch, but git won't let me, have I done something wrong?

Hi @sheepfleece this looks really good.  Thank you for this.  This is perfect.
Except for one thing.
We have many readme.md files in this repo.  See below.  Those are ALL generated by poking data into readme_template.md.
Can you please revert this change, and apply it to readme_template.md?  That will be good to merge.
alternates/fakenews/readme.md
alternates/fakenews-gambling/readme.md
alternates/fakenews-gambling-porn/readme.md
alternates/fakenews-gambling-porn-social/readme.md
alternates/fakenews-gambling-social/readme.md
alternates/fakenews-porn/readme.md
alternates/fakenews-porn-social/readme.md
alternates/fakenews-social/readme.md
alternates/gambling/readme.md
alternates/gambling-porn/readme.md
alternates/gambling-porn-social/readme.md
alternates/gambling-social/readme.md
alternates/porn/readme.md
alternates/porn-social/readme.md
alternates/social/readme.md
extensions/readme.md
readme.md

Oh, should have noticed it sooner. There is also a question of which exact url should I specify. Now there is the most restrictive one, simply because this is the one I use. But I'm sure with templates it can be done better (with a note that it can be changed).

@sheepfleece can you add a comment, either in the Haskell code, or the text preamble, that this code fetches the full list that includes social media, gambling, porn, etc?  This will kill access to Facebook, Insta, etc.
I suggest coding for the base list.

Base list it is, with a note for other ones.

Awesome.  Thanks @sheepfleece!
Merging.


TIMESTAMP/DATE FORMAT ERROR

Greetings,
Im testing this code, and have treid maintaining the csv just as in the example folder.
My time stamp is in: Day/Month/Year format.
When I run
output_matilda = matilda_simulation(df, output=working_directory,
                                    sim_start='01-01-2003', sim_end='31-12-2022',
                                    freq="D",  # Temporal resolution ("D", "M" or "Y")
                                    lat=76,  # Latitude
                                    area_cat=20.5,  # Catchment area
                                    area_glac=10.5,  # Glaciated area in the catchment
                                    ele_dat=20,  # Reference altitude of the data (e.g. AWS altitude)
                                    ele_glac=350,  # Mean altitude of glaciated area
                                    ele_cat=500,  # Mean catchment elevation

                                    # Optional:
                                    # 1. specify model parameters, e.g.
                                    PCORR=1.5,
                                    # For a list of model parameters and default values check the Parameters file

                                    # 2. Add glacier profile (see Readme) to account for glacier change:
                                    glacier_profile= glacier_profile,
                                    elev_rescaling=True,

                                    # 3. Include interactive plots:
                                    plot_type='all'	# If you receive errors relating to plotly either try a different plotly version or change plot_type to "print"
                                    )

I get the following error
ValueError: time data "13-01-2003" doesn't match format "%m-%d-%Y", at position 12. You might want to try:
    - passing `format` if your strings have a consistent format;
    - passing `format='ISO8601'` if your strings are all ISO8601 but not necessarily in exactly the same format;
    - passing `format='mixed'`, and the format will be inferred for each element individually. You might want to use `dayfirst` alongside this.
    - ```

This is the error
###############
/tmp/ipykernel_3626/2106608888.py in <module>
----> 1 output_matilda = matilda_simulation(df, output=working_directory,
      2                                     sim_start='01-01-2003', sim_end='31-12-2022',
      3                                     freq="D",  # Temporal resolution ("D", "M" or "Y")
      4                                     lat=76,  # Latitude
      5                                     area_cat=20.5,  # Catchment area

~/.local/lib/python3.10/site-packages/matilda/core.py in matilda_simulation(input_df, obs, glacier_profile, output, warn, set_up_start, set_up_end, sim_start, sim_end, freq, lat, soi, area_cat, area_glac, ele_dat, ele_glac, ele_cat, plots, plot_type, hydro_year, elev_rescaling, pfilter, drop_surplus, parameter_set, lr_temp, lr_prec, TT_snow, TT_diff, CFMAX_ice, CFMAX_rel, BETA, CET, FC, K0, K1, K2, LP, MAXBAS, PERC, UZL, PCORR, SFCF, CWH, AG, RFS)
   2054         # Downscaling of data if necessary and the MATILDA simulation
   2055         if glacier_profile is not None:
-> 2056             output_MATILDA = matilda_submodules(df_preproc, parameter, glacier_profile=glacier_profile,
   2057                                                 elev_rescaling=elev_rescaling, drop_surplus=drop_surplus)
   2058         else:

~/.local/lib/python3.10/site-packages/matilda/core.py in matilda_submodules(df_preproc, parameter, obs, glacier_profile, elev_rescaling, drop_surplus)
   1260             if glacier_profile is not None:
   1261                 lookup_table = create_lookup_table(glacier_profile, parameter)
-> 1262                 output_DDM, glacier_change, input_df_catchment = updated_glacier_melt(df_preproc, lookup_table,
   1263                                                                                glacier_profile, parameter,
   1264                                                                                drop_surplus=drop_surplus)

~/.local/lib/python3.10/site-packages/matilda/core.py in updated_glacier_melt(data, lookup_table, glacier_profile, parameter, drop_surplus)
    658
    659     # determine hydrological years
--> 660     data["water_year"] = np.where((data.index.month) >= parameter.hydro_year, data.index.year + 1, data.index.year)
    661
    662     # initial glacier mass from the glacier profile in mm w.e. (relative to the whole catchment)

AttributeError: 'RangeIndex' object has no attribute 'month'

Please try again using the following date format. That should fix the error:
sim_start='2000-01-01', sim_end='2099-12-31'


Why do I need to download and use KITTI velodyne data?

Hello @filaPro
I was reading your paper and trying to implement your method on an RGB dataset that I have collected.
While trying to test your code, it looks like you also need KITTI Velodyne data to be downloaded.
Does your method use lidar point cloud or else you are using point cloud dataset for some other purpose.
Thank you for sharing the code and your help.

Hi @chetanmreddy ,
ImVoxelNet uses only a single rgb image and a pose for KITTI dataset as can be seen in our KittiMultiViewDataset.
The tools/create_data.py script for KITTI is simply copied from mmdetection3d, so it also processes Velodyne data. In our case it is not used after this step. You can probably comment all point cloud preprocessing in tools/data_converter/kitti_converter.py if you don't want to download this data.

Thank you @filaPro  for your kind help. That clears my question.
I am facing an issue after doing the above steps suggested.

It looks like the create_groundtruth_database is using the kitti_dataset.py instead of kitti_monocular_dataset.py
Do you know why it could be happening?
Thank you again for your help

Never mind. I got it figured out. Thank you

Hi @filaPro
I am getting the following error while training:

My image size is 1024 X 1024. I haven't changed anything in the config file.
Can you please help me?
Thank you

Can you please provide more info? Are you training on KITTI? Which config file are you using? However, the default size for KITTI is 1280 x 384, not 1024 x 1024. Also the full log file might be helpful.

My bad, I forgot to mention that I am training on my custom dataset which I have prepared according to kiiti format.
The size of my images is 1024 in my dataset.
I am using the configs/imvoxelnet/imvoxelnet_kitti.py for config file.
I am attaching my full log file from work_dirs. please find here
20210713_184140.log

Looks like some bug with RandomFlip transform. I can have a look tomorrow. For now you can probably remove dict(type='RandomFlip') from the config.
Btw, were you able to train a model on KITTI?

Yes I was able to train on KITTI first.
Do you think it has something to do with the image size? I see that there are few values(eg img_scale) set for kitti in the config file.
Thanks for your suggestion.I will try that

You can check mmdet/datasets/pipelines/transforms.py, line 440, mentioned in your traceback. It is about flip_ratio=None for RandomFlip.__init__. Probably flip_ratio should be 0.5. However it worked somehow on KITTI...

Don't quite understand how you were able to train on KITTI, as I'm getting the same bug there. Fixes flip_ratio from None to 0.5 in 5fb7d07.

I think I was training your method from mmdet3d repository instead of yours a few days ago. LINK
May be that's why I didn't encounter this issue back then

Hi @filaPro I am trying to understand your visualization part of the code while testing. It works completely fine for me.
But when I was looking at the code I see that the show_results function is not implemented in mmdet3d/models/detectors/imvoxelnet.py
While running this command python tools/test.py configs/imvoxelnet/imvoxelnet_kitti.py \     work_dirs/imvoxelnet_kitti/latest.pth --show \     --show-dir work_dirs/imvoxelnet_kitti  which show_results is being called?
Thank you for your help

We overwrite show method of all monocular and multiview datasets here.


Data Management API: negotiate a contract with an already existing policy

Feature Request
Currently it's only possible to use a custom policy passing it into the POST /contractnegotiations API request body.
Would be good to have the possiblity to specify only the policyId and have the negotiation manager fetch it from the database.
Which Areas Would Be Affected?
contract negotiation manager
Why Is the Feature Desired?
To avoid having to define a new policy every time a contract needs to be negotiated
Solution Proposal

Type of Issue
improvement
Checklist

[x] assigned appropriate label?
[x] Do NOT select a milestone or an assignee!

I just wanna clarify your idea if I understand it correctly.
The communication is now this way, if i remind and understand correctly:
POST Request with full Customized Policy -> Consumer Connector -> Provider Connector (Tries Matching his saved Policy with Customized Policy of the starting POST Request)
So i think their are two ways you can do it.
(A) First the Consumer Connector has a database of existing Policies to exchange so it could work this way:
POST Request with PolicyID -> Consumer Connector (loads the policy with the policy ID) -> Provider Connector (Tries Matching his policy with the loaded policy of the consumer connector)
(B) The second way would be like:
POST Request with PolicyID -> Consumer Connector -> Provider Connector (Checks if the PolicyID is existing)
Im right that you speak about way A?

This is issue is probably obsolete now, there were some discussions goin' on about policies, I think this will be fixed by PR #1365


Support .npmrc _auth when downloading Serenity BDD CLI jar

In a small percentage of scenarios where the Serenity BDD CLI jar needs to be downloaded from an internal artifact registry (Artifactor, Nexus, etc) that requires authentication, one needs to provide the credentials via a command-line argument, i.e.:
npx serenity-bdd update --ignoreSSL --repository https://artifactory.example.org/ --auth username:token

It would be nicer if @serenity-js/serenity-bdd supported specifying the credentials via npm _auth param, just like it does with proxies.

what is "token" in username:token?
The --help shows username:password
If it is a token, is the same as _auth in .npmrc?

I got this working for myself. password is cleartext password, and username is case sensitive.

Related to #1134


Assign multiple content types

As I found out since #33 was commtited in Hugo type cannot be an array but only a string.
Therefore this commit reverts type back into a string.
So for the HugoBasicExample to provide support for both post AND posts content types, I have assigned the type posts to half of the content files, while the other half will retain the existing post type.
This will fix the issue of several themes that use the type posts in their list pages and since https://github.com/gohugoio/hugoThemes/pull/547 currently have empty list pages, like the following:
Hamburg
Dusky Neon Potato
Potato Darl
Hyde Hyde
Also this PR is relevant to the following theme submission: https://github.com/gohugoio/hugoThemes/issues/545#issuecomment-466672234 because when this is merged the HugoBasicExample will provide support for both post AND posts content types.
cc: @digitalcraftsman

Is this PR ready to be merged? I was about to add a comment about the conflict that Git detected. But this has been resolved a moment ago.

@digitalcraftsman
Once  merged https://github.com/gohugoio/hugoBasicExample/pull/36 is merged, let me check whether this PR throws any Git conflicts.
If everything is fine I will let you know so that you can go ahead with merging.

@digitalcraftsman
#36 is now cleaned up and ready to be merged first.
Then please merge this PR.
But for both of these to take effect on the website a manual deploy needs to be triggered on Netlify.


Signals with typed arrays cannot be emitted with empty arrays

Tested versions
Reproducible in 4.3.stable, 4.1.stable
System information
Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility)
Issue description
Emitting a signal that has a typed array as a parameter with an empty array gives the error "Cannot convert argument from Array to Array" if the signal is connected. Works with untyped array.
Might be related to the issues described in proposal #7364.
A simple type safe workaround is to create a new class containing that typed array as a member and just emit that (or null).
Steps to reproduce

Emitter class:

extends Node

signal test(value: Array[String])

func _ready() -> void:
	test.emit([])

Receiver class:

extends Node

func _on_node_test(value: Array[String]) -> void:
	pass

Connect emitter to receiver class.
See error in debugger:

E 0:00:01:0996   Test.gd:6 @ _ready(): Error calling from signal 'test' to callable: 'Node2D(TestReceiver.gd)::_on_node_test': Cannot convert argument 1 from Array to Array.
  <C++ Source>   core/object/object.cpp:1200 @ emit_signalp()
  <Stack Trace>  Test.gd:6 @ _ready()

Minimal reproduction project (MRP)
testarray.zip

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/92215, as this is due to the same cause.


Custom design validation

Hello, I am trying to implement a custom validation design but when I want to get the JSON text it finds it but does not return it translated in {{messages}}. I tried to use {{messages [0]}} and I could get the message but when I use variables for MINLENGTH for example it doesn't recognize them.

I @thelastkiller99, could you please provide a reproducible example? (I suggest for example to fork this https://stackblitz.com/github/xtreamsrl/ngx-validation-errors on stackblitz)

That same example that you propose is the one that has the error since it does not show the content of the JSON (for example NEW_HERO.NAME.ERRORS.MINLENGTH)

Can you show me the translation file? according to the key it should be like:
{
  "NEW_HERO": {
     "NAME" : {
        "ERRORS": {
           "MIN_LENGTH": "error message"
         }
     }
  }
}


Extending sender doesn't work as expected

Hey,
I'm trying to implement email notifications based on the example in the wiki: https://github.com/fenos/Notifynder/wiki/Email-Notifications
So I'm extending Notifynder like this:
Notifynder::extend('sendWithEmail', function ($notification) {
    return new EmailNotificationSender($notification);
});

The class it's using is:
namespace App\Support\Notifynder;

use Fenos\Notifynder\Contracts\Sender;
use Fenos\Notifynder\Contracts\NotifynderSender;
use Fenos\Notifynder\Models\Notification;
use Mail;

class EmailNotificationSender implements Sender
{
    /**
     * @var array
     */
    protected $notifications;

    /**
     * Create a new email notification sender instance.
     *
     * @param  array  $notifications
     * @param  Mailer  $mailer
     */
    public function __construct($notifications)
    {
        $this->notifications = $notifications;
    }

    /**
     * Send the notifications.
     *
     * @param  NotifynderSender  $sender
     * @return void
     */
    public function send(NotifynderSender $sender)
    {
        foreach ($this->notifications as $notification) {
            $sender->sendOne($notification);

            if ($notification->receiver->preference('email_notifications')) {
                $this->sendEmail($notification);
            }
        }
    }

    /**
     * Send an email notification.
     *
     * @param  Notification  $notification
     * @return void
     */
    public function sendEmail(Notification $notification) {
        $user = $notification->receiver;

        Mail::send(
            'user.account.emails.notification',
            compact('user', 'notification'),
            function ($message) use ($user) {
                return $message->to($user->email)->subject('RNA Notification');
            }
        );
    }
}

Usage is:
Notifynder::category('comment.added')
    ->from($comment->user)
    ->to($model->user)
    ->url("{$model->url}#comments")
    ->extra(['model_name' => $model->friendlyName])
    ->sendWithEmail();

My understanding is that an array of Notification objects is expected to be passed to the custom sender's constructor even if it's only for a single notification, but instead, it just receives an array representation of the notification. That is, if I dd($notifications) in the constructor, this is what I get:
array:9 [▼
  "category_id" => 1
  "from_type" => "App\Models\User"
  "from_id" => 5
  "to_type" => "App\Models\User"
  "to_id" => 5
  "url" => "http://local.rna-guild.net/user/5-lilli#comments"
  "extra" => "{"model_name":"User Profile"}"
  "updated_at" => Carbon {#550 ▶}
  "created_at" => Carbon {#550 ▶}
]

This is problematic for a few reasons, chief of which being rendering the notification in the email view as I can't simply use {{ $notification->text }}.
Maybe the wiki article is out of date, but I suspect something is wrong here.

I'm totaly with you - at some points we return strange things.^^
You expect an eloquent collection or eloquent model instance!?
I will take a look at this tonight and will try to fix/update this.

As a first workaround you can create the model instance by your own.
new Notification($array)

Thanks for the tip, I'll probably do that in the meantime.
I think I would expect an individual model instance in this case - I haven't used Notifynder's looping feature but I personally think it would make sense in that context too. I can't think of any reason why you'd want to do anything special with a collection as a whole, but I could be wrong.

Ok, have digged into it and everything is right: there is no model cause no sender was called and this way no model was stored. But you call the sendOne() before you call your own sender - the sendOne() returns and instance of \Fenos\Notifynder\Models\Notification - so you can update your sender a little bit like:
public function send(NotifynderSender $sender)
    {
        foreach ($this->notifications as $data) {
            $notification = $sender->sendOne($data);

            // have changed it from 'receiver' to 'to' cause receiver doesn't exist on the normal model
            if (($notification instanceof Notification && $notification->to->preference('email_notifications')) {
                $this->sendEmail($notification);
            }
        }
    }

It's not tested yet but should work.

Aha, that makes sense. It works, the only difference being that the class is definitely only being sent the data for a single notification, so I don't have a loop in my send method. In case it's useful for anyone who comes looking, this is what my EmailNotificationSender class looks like now:
<?php namespace App\Support\Notifynder;

use Fenos\Notifynder\Contracts\Sender;
use Fenos\Notifynder\Contracts\NotifynderSender;
use Fenos\Notifynder\Models\Notification;
use Mail;

class EmailNotificationSender implements Sender
{
    /**
     * @var array
     */
    protected $notification;

    /**
     * Create a new email notification sender instance.
     *
     * @param  array  $notification
     * @param  Mailer  $mailer
     */
    public function __construct($notification)
    {
        $this->notification = $notification;
    }

    /**
     * Send the notification.
     *
     * @param  NotifynderSender  $sender
     * @return void
     */
    public function send(NotifynderSender $sender)
    {
        $notification = $sender->sendOne($this->notification);

        if ($notification->to->preference('email_notifications', 1)) {
            $this->sendEmail($notification);
        }
    }

    /**
     * Send an email notification.
     *
     * @param  Notification  $notification
     * @return void
     */
    public function sendEmail(Notification $notification) {
        $user = $notification->to;

        Mail::send(
            'user.account.emails.notification',
            compact('user', 'notification'),
            function ($message) use ($user) {
                return $message->to($user->email)->subject('RNA Notification');
            }
        );
    }
}

Also, there is one small oddity: $notification->text contains null when using it in the email view, but I render notifications with that in a view returned by a controller elsewhere and it contains the parsed notification body. I had to use $notification->notifyBody instead. I haven't taken a detailed look to find out why it's different, it just struck me as odd.
Thanks for the help :)

Ok, can you add this class to the wiki and link this issue under it pls!? This will help others in the future.
Regarding the text & notify_body problem pls open a new issue to keep it clean but I will start research. :wink:

Done and done :)

@Riari does it realy work? You call the builder with the loop method but your custom sender just handles sendOne()!? :confused:

Yup, using Notifynder 3.2.9 in this project and it only seems to pass along a single notification at a time.

So if you send 3 notifications it calls your method 3 times? Strange - the code looks different and in my first test it passes all at once.

Yeah, sorry, just edited my comment.

Related to your assume: yes that's right, you receive a multi-dimensional array like this:
array:2 [
  0 => array:6 [
    "category_id" => 1
    "to_id" => 1
    "from_id" => 2
    "url" => "www.notifynder.io"
    "updated_at" => Carbon\Carbon {#750
      +"date": "2016-06-03 18:53:47.000000"
      +"timezone_type": 3
      +"timezone": "UTC"
    }
    "created_at" => Carbon\Carbon {#750}
  ]
  1 => array:6 [
    "category_id" => 1
    "to_id" => 2
    "from_id" => 1
    "url" => "notifynder.com"
    "updated_at" => Carbon\Carbon {#751
      +"date": "2016-06-03 18:53:47.000000"
      +"timezone_type": 3
      +"timezone": "UTC"
    }
    "created_at" => Carbon\Carbon {#751}
  ]
]

I will take a look at it and update the wiki and your class to support also multiple. But this is related to #144


WikiText 103 tokenizer hangs

See issue here: https://github.com/huggingface/transformers/issues/19702

any updates on this?


Cannot connect to the Docker in Cloud Shell

Describe the issue:
Can't start the docker in Cloud Shell.
Repro Steps:

Login to Azure Portal
Open Cloud Shell terminal
Installation: to install run “mkdir -b ~/bin && curl -fsSL https://aka.ms/install-azd.sh | bash -s -- --install-folder ~/bin”
Create a folder for test templates
Run command azd init -t <template>
Run command  azd up

Error Message:

Error Trace:
After investigation, docker needs to be started, but we are neither the root user nor do we know the root password, so we can't start docker.

Environment:
OS: Cloud Shell
Template:

https://github.com/Azure-Samples/todo-nodejs-mongo-aca
https://github.com/Azure-Samples/todo-python-mongo-aca

Azd version: 0.4.0-beta.1 (commit 2bf7a529914d86d8e9f5d7b6f95a4f20a2351e01)
Expected behavior:
The docker service can successfully start.
@danieljurek for notification.

@danieljurek should we reach-out to the Cloud Shell team on this for making our ACA templates work in Cloud Shell?

Possible solution... use an ACR task to build in the ACR instance. https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tasks-overview#quick-task

Pinged the Cosmos team to check in on if there are particular scenarios they are targeting, which might help inform our path forward.

I think we can proceed and document this as a known limitation for now. I'll mark as docs, cc: @gkulin

Should be added to doc in the release which contains CloudShell support in Azd. Currently it is blocked with the JDK upgrade #1207

@danieljurek The same issue also occurs in the following cases, failed to connect to the Docker.

OS: CloudShell.
Azd version: 0.6.0-beta.2 (commit https://github.com/Azure/azure-dev/commit/c4a201e55a13eba77f9037b296a90e0f81b00dbe)
Error Message:

Repro Steps:
1.Run git clone https://github.com/danieljurek/CloudShell.git -b add-azd-validation
2.Run docker build -f ./linux/base.Dockerfile -t base_cloudshell .

closed with https://github.com/MicrosoftDocs/azure-dev-docs-pr/pull/4193
it was added to the troubleshooting page: https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/troubleshoot#cannot-connect-to-the-docker-daemon-in-cloud-shell


Missing module shapely.vectorized when installing shapely[vectorized] from sources

Expected behavior and actual behavior.
Two pre-requisites are needed to generate the shapely.vectorized module from sources: cython and numpy
When a end-user module that uses shapely is installed, the install command should be:
$ pip install end-user-module --no-binary shapely

But issues are occurring on a fresh Python environment when doing so: as Cython and numpy are not pre-installed the vectorized module is not generated, even if the dependency in end-user-module is declared like shapely[vectorized].
Main problem is that cython is still a build dependency that cannot be handled correctly by setuptools.
Steps to reproduce the problem.
On a fresh Python environment:
$ pip install shapely[vectorized] --no-binary shapely
$ python3 -c 'import shapely.vectorized'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/aaaaa/Documents/Shapely/.venv/lib/python3.8/site-packages/shapely/vectorized/__init__.py", line 3, in <module>
    from ._vectorized import (contains, touches)
ModuleNotFoundError: No module named 'shapely.vectorized._vectorized'

Operating system
Linux 64bits
Shapely version and provenance
1.7.1

A possible solution to this issue is to add a pyproject.toml (See PEP-517) file with the following content:
[build-system]
requires = ["setuptools", "wheel", "cython", "numpy"]

In this case, installation have the following results:
$ pip install Shapely/dist/Shapely-1.8a2.tar.gz[vectorized] --no-binary shapely
$ python3 -c 'import shapely.vectorized'
$ echo $?
0

$ pip install Shapely/dist/Shapely-1.8a2.tar.gz --no-binary shapely
$ python3 -c 'import shapely.vectorized'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ender/Documents/Shapely/.venv/lib/python3.8/site-packages/shapely/vectorized/__init__.py", line 3, in <module>
    from ._vectorized import (contains, touches)
  File "shapely/vectorized/_vectorized.pyx", line 1, in init shapely.vectorized._vectorized
ModuleNotFoundError: No module named 'numpy'
0


Model.prototype.get() and .has() counts own properties

Hi all! I stumbled on the following behaviour:
var model = new Backbone.Model();
console.log( model.get( 'constructor' ) );

returns the constructor function of the model.attributes object.
I was rather expecting the get() method to filter own properties and return undefined. The same should also hold true with has() (in line with Underscore's _.has(), which does filter own properties). Without this, a model's attributes object would not be a true hash.
Thoughts?

See #1495

Something to address for v2? Object.create is IE9+, might be worth looking into if we drop IE8.

It can be polyfilled with black magic in IE7 and 8. I think we should do it.

There's prior art in Exoskeleton for model.attributes and collection._byId from Object.create(null). (see #3411, #1783, etc.)
In general, I'd say that #1783 is right in that there generally isn't a real-world use case for naming your keys "constructor" or "hasOwnProperty" (keep in mind an object is not a hash) but if this change is easy and comes with minimal side effects, let's bite the bullet.

There may be good reasons to eventually drop IE7 and IE8, but using properties like constructor isn't one of them. Let's leave it for now.

There may be good reasons to eventually drop IE7 and IE8, but using properties like constructor isn't one of them. Let's leave it for now.

this trouble is actual on my current project
you made me sad
in my case treatment is to overwrite get for collection
get: function(obj) {
	if (obj == null) return void 0;
	var id = this.modelId(this._isModel(obj) ? obj.attributes : obj);
	return this._byId[obj] || this._byId.hasOwnProperty(id) && this._byId[id] || this._byId[obj.cid];
},


Uncaught (in promise): Error: Permission denied to access property "toString" sweetAlert

Hi,
I followed all steps for my angular 5 project but I am getting error:
columnNumber: 31
fileName: "http://localhost:4201/polyfills.bundle.js line 1871 > eval"
lineNumber: 824
message: "Uncaught (in promise): Error: Permission denied to access property \"toString\"\nsweetAlert/<@webpack-
internal:///../../../../sweetalert2/dist/sweetalert2.all.js:977:9\nZoneAwarePromise@webpack-
internal:///../../../../zone.js/dist/zone.js:890:29\nsweetAlert@webpack-
internal:///../../../../sweetalert2/dist/sweetalert2.all.js:650:10\nDashboardComponent@webpack-
internal:///../../../../../src/app/layout/dashboard/dashboard.component.ts:26:9\ncreateClass@webpac
k-internal:///../../../core/esm5/core.js:12359:20\ncreateDirectiveInstance@webpack-
internal:///../../../core/esm5/core.js:12206:37\ncreateViewNodes@webpack-
internal:///../../../core/esm5/core.js:13644:53\ncreateRootView@webpack-
internal:///../../../core/esm5/core.js:13534:5\ncallWithDebugContext@webpack-
internal:///../../../core/esm5/core.js:14935:39\ndebugCreateRootView@webpack-
internal:///../../../core/esm5/core.js:14236:12\nComponentFactory_.prototype.create@webpack-
internal:///../../../core/esm5/core.js:11155:37\nComponentFactoryBoundToModule.p…"

Looks like Angular doesn't like window.onkeydown.toString(), I'll take care of this issue.

Should be fixed in v7.0.1
:warning:  If you upgrading from v6.x please make sure you read the release notes with some breaking changes for the new major release: v7.0.0

I am not upgrading from older version, installing it freshly

@limonte Thank you...
IN newer version it is working fine.
(


Make iptables recheck timer dynamic

Description

Apply dynamic minimum to iptables recheck timer.

Track the peak value of iptables save/restore with an exponential decay estimator.
Set the minimum post-retry backoff to twice the combined save/restore time.

Increase default timeouts.  These were set aggressively low in the past to deal with other apps clobbering iptables state.  that problem no longer occurs since the iptables lock was widely adopted.
Related issues/PRs

CORE-9786
CORE-9780
Todos

[x] Tests
[ ] Documentation
[x] Release note

Release Note

Felix now adjusts the iptables post-write recheck interval dynamically: if iptables operations are taking longer, it will increase the time between iptables-save calls to compensate.  The default recheck time and resync intervals have also been increased.

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Thanks @mazdakn ; for a small change like this, I think it's OK to have a non-expert review, just looking for general coding mistakes (and thanks to @aaaaaaaalex for taking a look too).


Doc updates

update caveat about Java API and Scala 2.11
some general updates to Readme now that GitHub issues has been disabled for a while

lgtm +1

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success


test case 3501 - 4128

How to categorize this PR?
/area testing
/kind TODO
What this PR does / why we need it:

test case 3501 - 4128

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

test case 3501 - 4128

The following test case seems to be falling every time:
[
    { "testcase": "[sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]"},
    { "testcase": "[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]"},
    { "testcase": "[sig-scheduling] SchedulerPriorities [Serial] PodTopologySpread Scoring validates pod should be preferably scheduled to node which makes the matching pods more evenly distributed"},
    { "testcase": "[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: blockfs] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]"},
    { "testcase": "[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]"},
    { "testcase": "[sig-storage] In-tree Volumes [Driver: local][LocalVolumeType: dir-link-bindmounted] [Testpattern: Pre-provisioned PV (default fs)] subPath should unmount if pod is gracefully deleted while kubelet is down [Disruptive][Slow][LinuxOnly]"},
    { "testcase": "[sig-storage] In-tree Volumes [Driver: nfs] [Testpattern: Dynamic PV (filesystem volmode)] disruptive[Disruptive][LinuxOnly] Should test that pv written before kubelet restart is readable after restart."}
]

I think we can merge, just a final question: did you test these tests with the cloudproviders we support?

yes !
If I'm not wrong we are not supporting CSI driver. but all the other have been test in all cloudprovider

If I'm not wrong we are not supporting CSI driver. but all the other have been test in all cloudprovider

We did analyze several CSI related issues in various Hands-On sessions, so certainly we do have CSI enabled nearly everywhere ;)
Could you check why the above tests fail?


Fix PeerDAS sampling_size logic

The current sampling size logic mixes different units - SAMPLES_PER_SLOT is measured in column samples, while custody_group_count refers to custody groups:

At each slot, a node advertising custody_group_count downloads a minimum of sampling_size = max(SAMPLES_PER_SLOT, custody_group_count) total custody groups.

This discrepancy causes issues when NUMBER_OF_COLUMNS does not exactly match NUMBER_OF_CUSTODY_GROUPS, potentially leading to incorrect sampling_size.
This PR converts the custody_group_count to column count.

I'm not entirely sure if this change is correct, but I think we need to make sure the units used here are consistent.
Alternatively, we may want to change SAMPLES_PER_SLOT to mean  "Number of custody groups a node queries per slot" instead - given that the two other custody configs both use custody groups as units:
https://github.com/ethereum/consensus-specs/blob/0964db294c718b0d3574945a963cd2502a1aef32/specs/fulu/das-core.md#L70-L74


Added metadata and tagging to S3

Hi,
I need to add the same metadata to the S3 uploaded files
Due to inability to add metadata via S3 api without a copying, I added it here in protocol.
Types are chosen according s3.PutObjectInput here.

Hi
@frostbyte73 PTAL

@davidzhao PTAL

hey @nkonev, can you open the egress PR as well? We try to merge protocol changes and implementation together

https://github.com/livekit/egress/pull/154