Implement a socket.io style interface

As described in #17, we require the socket to respond to event subscriptions:
mockSocket.on('chat message', function(e) {
  console.log(e.data); // 'hello'
});

mockServer.emit('chat message', 'hello');

I've not actually tested with this a socket.io application but it would be good to get your initial thoughts on this first.

cc @samselikoff

Thanks @bdvholmes for the PR. This looks like a good start! It would also be very beneficial to add room & namespace support (http://socket.io/docs/rooms-and-namespaces/)

Sure thing :+1:

To establish a connection Socket.io starts out with a GET request that looks like this:
GET http://localhost:4200/socket.io/?EIO=3&transport=polling&t=1431546178348-0

The line is here. We'll need to mock a response out to this as well, to establish the handshake - correct?

@samselikoff surely we don't have to worry about this if we're mocking out the client library as well. We're trying to get MockSocket to respond to the same interface as a global io on the client.

Ah I see, so if my app uses window.io, I'll need to inject that instead, so I can inject the mock client during testing?

Exactly, something like:
io.Socket = MockSocket;

Not sure if this is the public socket.io api but one of my apps was doing
window.io.connect(':4545/api')

but this doesn't work with the current implementation (i.e. no ws: protocol or host name).

also, seems socket.io's docs recommend connecting like this now:
window.io('localhost:4545')

so we should support that too

@samselikoff We should support io('some_url') and ideally it would be something like this:
window.io = MockSocket;
var socket = io('example.com');

@bdvholmes socket.io's client interface is actually not
mockSocket.on('chat message', function(e) {
  console.log(e.data); // 'hello'
});

it's
mockSocket.on('chat message', function(e) {
  console.log(e); // 'hello'
});

i.e. there's no event.data, it's just data that gets passed to the callback. Perhaps we'll need a config option that the user can set to let mock-socket know it wants socket.io-style messages?

I could totally bake that in. I'm Having a bash at finishing this today.
Enviado desde mi iPhone

El may 15, 2015, a las 10:39 AM, Sam Selikoff<EMAIL_ADDRESS>escribió:
Not sure if this is the public socket.io api but one of my apps was doing
window.io.connect(':4545/api')
but this doesn't work with the current implementation (i.e. no ws: protocol or host name).
—
Reply to this email directly or view it on GitHub.

sweet, I can help too. let me know, ill be on irc

@thoov @samselikoff the branch should be working well now, with the exception of rooms / namespaces. What do you think of this interface:
window.io = MockSocketIO;
var socket = io('example.com');

@bdvholmes
window.io = MockSocketIO;
var socket = io('example.com');

I think that looks great. I will play around with the branch this weekend.

@thoov If you could try it out on a working project that would be much appreciated, I'm hoping to finish out the rooms and namespace stuff tomorrow.
I've set up some example repos to test this with:

https://github.com/bdvholmes/ember-socketio-chat
https://github.com/bdvholmes/ember-socketio-server

lgtm as well

I created this very simple page:
<html>
	<head>
		<script src="dist/mock-socket.js" charset="utf-8"></script>
	</head>
	<body>
		<script type="text/javascript">
			window.io = MockSocketIO;
			var socket = io('http://testing.com');

			socket.on('connection', function () {
				debugger;
			});
		</script>
	</body>
</html>

And I am seeing these JS errors:

@thoov just got round to this. So the thing that is undefined here is the service. Is it intended that you can create a socket client without setting up MockServer first?
MockSocketIO is a thin wrapper to MockSocket so I don't think this would work in the normal case.
I've had a go putting together a basic test and it seems to work fine. See bdvholmes/ember-socketio-chat@4ae9402
I'll testing it a bit more rigorously shortly.

I've tidied this up and added very basic support for rooms.
At the moment the interface for defining callbacks with the server is not
aware of specific client connections, so we can't have certain connections
be in certain rooms without overhauling the interface.
E.g.
mockServer.on('say please', function(server) {
  // is it not the case that server == mockServer here?
}

In particular because the callback method has no information about the client, it can't subscribe a particular socket connection to one room.
I'm not worried about this because in practice we will have the server on the client-side so there will be one socket connection to the server.
If we need support for multiple sockets at once can I suggest we leave that for another pull request, I'd like to get this merged sooner rather than later.

@bdvholmes Let me test it against: https://github.com/thoov/ember-websockets

@bdvholmes Also can you update this PR as there is a conflict

@bdvholmes
So I wrote this test:
import Ember from 'ember';
import { module, test } from 'qunit';
import SocketsService from '../../../../services/socket-io';

var component;
var mockServer;
var ConsumerComponent;
var originalSocketIO;

module('Socket.io Service - on(*) tests', {
  setup() {
    var service    = SocketsService.create();
    mockServer = new MockServer('localhost:7100');

    mockServer.on('connection', function(server) {

      // This is called

      mockServer.emit('myNamespace', 'foo');

      mockServer.on('message', function() {

        // This is called

      });
    });

    originalSocketIO = window.io;
    window.io = MockSocketIO;

    ConsumerComponent = Ember.Component.extend({
      socketService: service,
      socket: null
    });
  },
  teardown() {
    window.io = originalSocketIO;

    Ember.run(() => {
      component.destroy();
    });
  }
});

test('that on(open) and on(close) work correctly', assert => {
  var done = assert.async();
  assert.expect(3);

  component = ConsumerComponent.extend({
    init() {
      this._super.apply(this, arguments);
      var socket = this.socketService.socketFor('localhost:7100');

      socket.on('connection', function() {
          // This is never called
      }, this);

      socket.on('myNamespace', function() {
        // This is called

        socket.send('a sample message');
      }, this);
    }
  }).create();
});

It seems to be working fairly well except for:
socket.on('connection', function() {
  // This is never called
}, this);

I am trying to debug why this is not being called

If this is still something we're still happy to pursue, expect to see this brought up-to-date this weekend.

:+1:  this would be very helpful!

would be so great

@bdvholmes there have been some major changes since this was originally opened. It might be easiest to simply start from scratch. I can help with adding io support as it was already in my roadmap.

@thoov, thanks I made a start over the weekend - I'll let you know if I have any questions. I'll close this pull request and submit a new one with the other code.
I put together an API check list from the socket.io docs, I don't think we have to cover it all straight away for a v1 but I'm going to bass some tests on the following:
API
Client

[ ] io()
[ ] io('http://localhost')
[ ] io.connect('http://localhost')
[ ] socket.on('connect', function() { // stuff })
[ ] socket.on('news', function(data) { // stuff })
[ ] socket.on('message', function(data) { // stuff })
[ ] socket.on('disconnect', function(data) { // stuff })
[ ] socket.emit('hi!')});
[ ] socket.emit('my other event', { my: 'data' });
[ ] socket.emit('ferret', 'tobi', function (data) { console.log(data); });
[ ] socket.send('hi!')});

Server

[ ] io.on('connection', function(socket) { // stuff })
[ ] io.of('/chat')
[ ] io.emit('news', { hello: 'world' });
[ ] socket.emit('news', { hello: 'world' });
[ ] socket.on('message', function(data) { // stuff })
[ ] socket.on('news message', function(data) { // stuff })
[ ] socket.on('disconnect', function(data) { // stuff })
[ ] socket.join('some room');
[ ] socket.leave('some room');
[ ] io.to('some room').emit('some event');
[ ] socket.broadcast.emit
[ ] socket.volatile.emit
[ ] socket.on('pm', function(id, msg){ socket.broadcast.to(id).emit('my message', msg);
});
[ ] socket.on('ferret', function (name, fn) { fn('woot'); });
[ ] io.sockets.emit('hi', 'everyone')

@bdvholmes great list. Make sure you include it on the new pr so we can track it there

Opening #50 in favour of #23.


Remove bloom thin blocks

XT was first to implement thin blocks and did so using backwards compatible protocol calls - merkleblocks.
This protocol has its downsides and has been superseeded by now widely deployed xthin and compact blocks.
It's time to remove bloom thin blocks to reduce code maintenance.

The big diff in ProcessMessage->tx is just indentation change after removing the tryMempool variable.

Pushed a commit to fallback to full block download when re-requesting compact/xthin transactions does not provide all the transcations we're missing. Regression was caught by extended rpc tests.

ACK


[vm/ffi/NNBD] treatment of non-nullable and nullable C types

Currently, our representation of C types does not encode whether something can be null, and all types are represented as non-nullable.
Now that Dart will get NNBD, we might want to revisit that.
void MyCoolFunction(Foo& foo) {
  // ...
}

final f = dynamicLibrary.lookupFunction<Void Function(Pointer<Foo>),
                                        void Function(Pointer<Foo>)>("MyCoolFunction");
f(nullptr); // Passing null, without the Dart type system understanding it.

If we would like to represent the difference between references (non-nullable) and pointers (nullable), we could do so in the following way:
Pointer<Int8>  p1;  // non-nullable, a C++ Reference
Pointer<Int8>? p2;  // nullable,     a C++ Pointer

Then, we should also change the representation of the nullptr back to a Dart null instead of Pointer<Never>(address=0).
However, this also requires us to take real care that everywhere where we currently return Pointers with address 0, we return null instead:

return values of FFI calls
arguments of FFI callbacks
loads from Pointer<Pointer<T>>.
struct field loads.

Year old discussions (before NNBD): https://github.com/dart-lang/sdk/issues/35756.
cc @mkustermann @mraleph

@dcharkes do we want this to be done for the beta release of the null-safety feature ?

@dcharkes do we want this to be done for the beta release of the null-safety feature ?

@a-siva I think this is rather a FFI design question how to represent a C pointer that is nullptr in Dart. Is not related/blocking to the NNBD work itself.

Removing from null safety tracking epic.


Root Tenant to read & write Entites of other Tenants

Hi There
I have the following use case and I'm stuck on this problem...
Use Case
In my application there is one root Tenant which has special rights to view and modify some of the entites of the other tenants. In the application there are Products which are not restricted by the .IsMultiTenant() constraint. And then there is a BasketItem Entity which each Tenant only sees their own BasketItems.
Goal
The Users of the Root Tenant should be able to add products to the Basket of another tenant.
What I’ve tried so far

Listing Basket Entites from other Tenants works by using the Query Option  .IgnoreQueryFilters()

I’ve added the TenantId property to the BasketItem Entity so I can set it manually if needed.

Then I got the “1 modified entities with Tenant Id mismatch.” Error, when I tried to add a new item with the root Tenant to another tenant.

According to the documentation I should be able to set the Mismatch Mode to TenantMismatchMode.Ignore and then it should allow me to set the tenantId manually

In the DbContext Class I tried to set this option:

public class DbContext : MultiTenantIdentityDbContext
{
    ....
    public TenantMismatchMode TenantMismatchMode { get; set; } = TenantMismatchMode.Ignore;
}

→ Still the same “TenantId Mismatch Error”

I also tried to set MyTenantInfo Class manually to the target tenant, but this doesn’t work. I assume because the tenant will be set in the ITenantInfo via the Strategy (for example the WithClaimStrategy())

public class MyTenantInfo : ITenantInfo
{
    public MyTenantInfo(
        string id,
        string name,
        string? connectionString,
    )
    {
        Id = id;
        Identifier = id;
        Name = name;
        ConnectionString = connectionString ?? string.Empty;
    }

    public string Id { get; set; } = default!;
    public string Identifier { get; set; } = default!;
    public string Name { get; set; } = default!;
    public string ConnectionString { get; set; } = default!;
  }

Questions

What is the best way to allow users of a root tenant to view, add, update, delete entites of the other tenants?
Is there a way to set the ITenantInfo manually, so I could change it before the database operation will be called?

Thank you for you help!

hi @eluvitie sorry for the slow reply. I need some time to check the TenantMisMatchMode because that would have been my first suggestion.
My next suggestion is to "new" up a dbcontext for the specific tenant you want to enter items for, then dispose of it. I'm working on convenience factory methods that will help with this but for not doing it manually isn't too bad, but it is not very efficient in some use cases.

One more thing, rather than this:
public TenantMismatchMode TenantMismatchMode { get; set; } = TenantMismatchMode.Ignore;

in your constructor do this:
this.TenantMismatchMode = TenantMisMatchMode.Ignore;

or when you use the dbcontext you can set it like this right before you call SaveChanges:
myDbContext.TenantMisMatchMode.Ignore;

I suspect your version is creating a shadow property that the base implementation isn't seeing.

Hi @AndrewTriesToCode
Thank you for your response.
Both of your approached worked for me.
I went for the latter, since I think its best to only change the TenantMisMatchMode if needed and not change it globally.
In the project I use the Ardalis.Specification Package, so I extended my IRepository Interface with a function setTenantMismatchMode(TenantMismatchMode mode)
This function changes the default TenantMismatchMode to what ever is desired in the DbContext. In my Case I'm setting it to TenantMismatchMode.Ignore.
DbRepository : IRepository
{
....
    public void setTenantMismatchMode(TenantMismatchMode mode)
    {
       this._dbContext.TenantMismatchMode = mode;
    }
....
}

In the Handler I then call this before I'm making changes to the DB: _repository.setTenantMismatchMode(TenantMismatchMode.Ignore);
Maybe this helps someone else. And if there are better ways to do it, I'm open for new approaches.

I think your approach is a good one! Thanks for sharing it for future people. I'm going to close the issue but feel free to reopen if you need to.
Cheers.


Make channel filter the default

As we open up the relayer we should not force people to relay everything. It might be good to force users to define the channels to use instead. Then we also reduce the need for the big search as we start

Need to check if already implemented.

it hasn't been implemented yet.


fix: upgrade to version 3.0.530

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign abayer
You can assign the PR to them by writing /assign @abayer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
a87a04852de6886e8ade11e8da412781191d6487
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
a87a04852de6886e8ade11e8da412781191d6487
link
/test gsm

vault
a87a04852de6886e8ade11e8da412781191d6487
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


[zh] Resync cloud-controller.md

[zh] Resync content/en/docs/concepts/architecture/cloud-controller.md
en PR: #30393

Thanks.
/lgtm
/approve


README.rst references Win XP

Rather old and outdated, thus reads funny.
Options:

use most popular (10)
use latest (11)
remove specific version if it does not matter

PR welcome 👍


Fix #2039, Replace CFE_SB_ValueToMsgId(0) with CFE_SB_INVALID_MSG_ID

Describe the contribution

Fixes #2039

Expected behavior changes

No impact to behavior

Contributor Info - All information REQUIRED for consideration of pull request
Paul Oberosler - Personal

CCB:2022-02-01 APPROVED


feat: add custom labels to deployment

This adds the ability to add custom labels to the deployment.

@fulgas hi, this repo is not maintained (https://github.com/provectus/kafka-ui/discussions/4255), see https://github.com/kafbat/kafka-ui instead


Improve Quick Question experience for conversational chat

Right now, the Quick Question experience only allows for one question and one answer.

We should explore alternatives to this UX that allows for full conversations.

Addressed in https://github.com/microsoft/vscode/pull/187780 and https://github.com/microsoft/vscode/pull/188126


explain "Isolated tests not supported in this environment. The tests will be run on the main process"

I've added cester to a system and I'm getting this warning, which is perplexing:
./cester.h:3277:17: warning: Isolated tests not supported in this environment. The tests will be run on the main process [-W#pragma-messages]
        #pragma message("Isolated tests not supported in this environment. The tests will be run on the main process")
                ^
1 warning generated.

It still works, but I'd like to know what the warning means. It's not in the documentation.

For each test case cester spawn a subprocess on the platform so if the test case crashed it will not impact the other test cases and as much information about the test case crash can be reported.
The subprocess is only possible on Windows and Unix based platforms which means your current platform is not Windows, Linux, or Unix variant. On such a platform if a test case crashes the signal.h library will be used to recover and report the crash.
So there is no big impact from the warning just that all the test cases will be executed in one process.

My current platform is MacOS, which is (literally) Unix (NeXT had a Unix license). How is the test performed?

The check for the Unix system is a simple #elif defined unix, with this issue that appears to be unreliable for all Unix platforms. Honestly, I did not test on the MacOS platform, I will do that this week.
For how the test is performed the code block inside each test case is executed. cester just watch the behavior of the test case and the provided assertion macros.
This page https://exoticlibraries.github.io/libcester/how_it_works/index.html provides some information on how this works internally.

I found the problem.
cester uses #ifdef unix to determine if it is running on a Unix-like system:
https://github.com/exoticlibraries/libcester/blob/master/include/exotic/cester.h#L3225
However, on MacOS, #ifdef unix is not true:
% cpp
#ifdef unix
unix is defined!
#endif
# 1 "<stdin>"
# 1 "<built-in>" 1
# 1 "<built-in>" 3
# 362 "<built-in>" 3
# 1 "<command line>" 1
# 1 "<built-in>" 2
# 1 "<stdin>" 2

However, __APPLE__ is defined to be 1:
 % cpp
#ifdef __APPLE__
__APPLE__ is defined!
#endif
# 1 "<stdin>"
# 1 "<built-in>" 1
# 1 "<built-in>" 3
# 362 "<built-in>" 3
# 1 "<command line>" 1
# 1 "<built-in>" 2
# 1 "<stdin>" 2

1 is defined!

Yes, that is where the check takes place. I have a MacOS set up so I will try to enable the subprocess for MacOS.

I've added support for subprocess on MacOS you can download the latest source of cester to get the update, the source code has also been refactored to resolve all the warnings outputed when compiling in C++.
I also created a Github action that you can use to install libcester in your CI workflow.
    - name: Setup Exotic Libraries
        uses: exoticlibraries/exotic-action@master
        with:
          run-cester-regression: false

The snippet above in your workflow yml file will install cester in the include folder. so you don't have to commit cester.h in your repo.

Neat. I need to look over the tutorial again, though, as I seem to be having some issues on how I'm including non-test code in my test program.  I'll need to review the tutorial
Thanks again.

You can use the CESTER_BODY macro to wrap non-test code.

#include "cester.h"

CESTER_BODY(
// the logics here

char *platform = "win32";

int compare() {
    return 0;
}

)

// the test cases

If you need help along the way don't hesitate to message me

Ah! That is not clear.
Can you point me at a description of how to do something like pytest-style fixtures?

the project uses the following macro to setup and cleanup objects
CESTER_BEFORE_ALL
CESTER_BEFORE_EACH
CESTER_AFTER_EACH
CESTER_AFTER_ALL

See the description here https://exoticlibraries.github.io/libcester/docs/macros.html?highlight=before#cester-before-all

You can use the CESTER_BODY macro to wrap non-test code.
#include "cester.h"

CESTER_BODY(
// the logics here

char *platform = "win32";

int compare() {
    return 0;
}

)

// the test cases

If you need help along the way don't hesitate to message me

Hm. That's not working, as I need to do an #include inside the block.

You can use the CESTER_BODY macro to wrap non-test code.
#include "cester.h"

CESTER_BODY(
// the logics here

char *platform = "win32";

int compare() {
    return 0;
}

)

// the test cases

If you need help along the way don't hesitate to message me

Hm. That's not working, as I need to do an #include inside the block.

I guess all my #includes should themselves have GUARD_BLOCKS to protect against multiple includes...

I ll be closing this issue, if you still need more detail on other functionalities please open another issue.


Track client errors

Sentry or something else.

Track mutation Unknown error.

https://github.com/zeit/next.js/tree/canary/examples/with-componentdidcatch

Consider middleware #1576


Docker image

Hi, could you possibly provide a docker file for easy library installation? The requirements.txt is causing countless dependency conflicts. Thank you.

desparate requirements.txt

Same here, tried both pip and conda,neither of them worked.

Same issue


test: intermittent failures in linux/ppc64 on build page due to test hangs

What version of Go are you using (go version)?
tip
Does this issue reproduce with the latest release?
intermittently
What operating system and processor architecture are you using (go env)?
linux/ppc64
I've seen intermittent failures on the golang build page for the ppc64 column, (never ppc64le) and the logs show that the failures are due to hangs when testing the runtime pkg. I have never been able to reproduce this, but I suspect it is due to the timeout value not being high enough because of its intermittent nature. It must be close to the limit and sometimes goes over due to other factors on the system.
I'm not sure what the preferred way to increase the timeout for ppc64 testing in this case to see if that will resolve this problem.  I can make the change if someone tells me what it should be.

I can make the change if someone tells me what it should be.

If I understand your theory correctly, I think you should be able to add GO_TEST_TIMEOUT_SCALE=2 to the environment in golang.org/x/build/dashboard/builders.go.
(CC: @bradfitz in case I'm mistaken.)


T64 full bit-transpose variant

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Category (leave one):

Improvement

Short description (up to few sentences):
Full bit transpose variant for T64 codec. Could lead to better compression with zstd.
Detailed description (optional):
Continuation of #5557 and #5731. Allow to set option to T64 codec: T64('byte'), T64('bit'). So it would generate byte-transposed or bit-transposed data. By default it uses 'byte' variant.

I've compressed some real data DateTime column with different variants:
lz4             833569732
zstd            515097904
t64(byte)+lz4   407128098
t64(bit)+lz4    472855596
t64(byte)+zstd  345330458
t64(bit)+zstd   318123008

It looks that full bit-transpose helps zstd and do not helps lz4.

You can also compare with different levels of ZSTD, because level 1 is used by default.
When comparing by compressed size, you should also mention compression and decompression speed.

PS. What's in stress test?

PS. What's in stress test?

Code: 202. DB::Exception: Received from localhost:9000, ::1. DB::Exception: Too many simultaneous queries. Maximum: 100.

Code: 202. DB::Exception: Received from localhost:9000, ::1. DB::Exception: Too many simultaneous queries. Maximum: 100.

This message cannot relate to stress test failure. It fails only in case of sanitizer reports or server crash.


Port from Batfish to Underreact

See https://github.com/mapbox/frontend-platform-team/issues/32. For sites like this one, which do not need to generate multiple HTML files, @mapbox/frontend-platform has a new favored tool: Underreact. It's significantly simpler than Batfish, and is using the latest, fastest versions of Webpack and Babel — so it's the better choice for any sites that don't need Batfish's HTML generation.
A few notes about the changes in this PR:

I used <link> and <script> tags in the HTML to load mbx-assembly.
The new app.js component is just the content of the old src/docs/app.js.
browserslist: ['defaults'] means Underreact won't bother building for IE11, because this is an internal site (that should speed things up).
Babel did not like the Object: type here and I'm not familiar enough with Babel to configure my way around that issue, so I just removed it.

Next steps:

[x] Get the page to render 😬
[x] Update tests

@davidtheclark: I would love to talk through this a bit with you tomorrow. I am a bit fuzzy on what's going on with the Babel 7 updates I made here and I am still not entirely sure why the page isn't being rendered.

Ok, after much flailing, I think this is ready to have its WIP tag removed. Tests are passing** and the page is rendering.
** tests are passing locally, but Travis is failing because it can't find @mapbox/underreact. @kepta: when I try to go to<EMAIL_ADDRESS>(or similar), I'm prompted to log in, which makes me think the package has recently become private.

** tests are passing locally, but Travis is failing because it can't find @mapbox/underreact. @kepta: when I try to go to<EMAIL_ADDRESS>(or similar), I'm prompted to log in, which makes me think the package has recently become private.

Looks like I have been mistakingly publishing it as private. I have publicly published it now and things should be working fine. Sorry about that.

Looks like this might be a great place to enable hot reloading feature of Underreact 🔥. We can either add it in this PR or I can send another PR to specifically enable it.

I've done some reorganizing here that I hope will make the project easier to maintain:

Moved docs and the test-cases-app into their own directories separate from the source components.
Finished scaffolding for the docs page's port to underreact.
Begain porting the test-cases-app to underreact, but hit a dead-end trying to get it working (and also got myself all kinds of turned around trying to get eslint configured). Underreact seems to be building the page without issue and my React chrome dev tools indicate that the test cases component and ReactTestKitchen component are being created, but they're not being populated with anything and are not throwing any errors. I'm a bit lost on where things are going wrong and could use some backup if anyone from @mapbox/frontend-platform is wiling to take a look with me.

@danswick this was an interesting bug. I found that the bug is with the way we are using the basePath as '/mr-ui/test-cases-app', but the react-test-kitchen expects the basePath to be / and that's the client side routing in rtk was wasn't outputting anything.
https://github.com/mapbox/react-test-kitchen/blob/1dbc8fb4e33c86cd02b66bd3f077587abe287a42/src/react-test-kitchen.js#L19-L23
We can probably send a fix to rtk to understand base paths or you can simply use / to keep it happy 😅.
Finding this bug was pretty confusing. I found the way this repo auto-generates the files pretty confusing (Maybe it is just me being unfamiliar with the rtk testing pattern). Also, I wasn't careful to see that budo server is also being used and the fact that you reorganised the repo structure made the auto scripts generation by scripts/ broken.
If it is not too much of a trouble, I suggest save the repo structure change to a separate issue/PR. This would make it easier to grok at the diff generated in this PR and also keep changes just related to porting of Underreact.

I suggest saving the repo structure change to a separate issue/PR

Yes, definitely.

I found it confusing to have two web apps that reference the component source, but the component source lives alongside just one of the apps

I don't think I understand the confusion here. We have src/components, src/docs, and src/test-cases, so the source components are already alongside both apps.

Thanks for all of the feedback, @kepta and @davidtheclark. I went ahead and fixed up the project structure, swapped the test cases app to a / basepath (thanks for that hint, @kepta! side note: I started experimenting with configurable basepath in rtk here, but was having some trouble and opted to stick with a basepath of / since the test cases app is really only ever used locally), and updated snapshots to get tests passing. Would love another review now that the diff is more manageable 🙏


Fixed compilation error

Replaced a ; by a , in the uses list.

Fixed separate to this pull request


s/join-lemmy.org/sublinks.org/

Currently demo.sublinks.org links to join-lemmy.org

https://demo.sublinks.org/

We should probably change all references to "join-lemmy.org" to be "sublinks.org"

We're temporarily using the Lemmy UI while we develop the Sublinks Official UI and API. We won't modify their front end to give the illusion that we developed that UI. I understand your concern; however, I do not plan to modify their code.

Perhaps you could host Lemmy at some other subdomain?
And replace demo.sublinks.org with Coming soon?


Preview - Change Feed Pull model

Change Feed pull model
Description
This PR adds support to consume the Change Feed through a pull model, under the Preview flag.
FeedToken and parallelization
The PR also introduces the FeedToken concept as a consumption and parallelization unit. The token represents a range inside a Container (it could be the full Container or part) and it also serves as continuation support.
The FeedToken can be used to consume the Change Feed and a user can obtain a list of these tokens by calling:
Task<IReadOnlyList<FeedToken>> Container.GetFeedTokensAsync(CancellationToken cancellationToken = default(CancellationToken));

This method provides a list of Tokens that can be used to parallelize Change Feed consumption FeedIterator. The FeedIterator is used to consume the Change Feed for a particular FeedToken. This practically allows computational distribution of tokens across multiple threads or even machines:
IReadOnlyList<FeedToken> tokens = await container.GetFeedTokensAsync();

// Machine or Thread 1
FeedIterator iteratorForToken = container.GetChangeFeedStreamIterator(tokens[0]);
while (iteratorForToken.HasMoreResults)
{
    // Stream iterator returns a response with status code
    using(ResponseMessage response = await iteratorForToken .ReadNextAsync())
    {
        if(response.IsSuccessStatusCode)
        {
            // Consume response.Content stream
        }
    }
}

// Machine or Thread 2
FeedIterator iteratorForToken = container.GetChangeFeedStreamIterator(tokens[1]);
while (iteratorForToken.HasMoreResults)
{
    // Stream iterator returns a response with status code
    using(ResponseMessage response = await iteratorForToken .ReadNextAsync())
    {
        if(response.IsSuccessStatusCode)
        {
            // Consume response.Content stream
        }
    }
}

The FeedToken can be captured from an existing iterator (FeedIterator.FeedToken) and saved/stored for later use:
FeedIterator iteratorForToken = container.GetChangeFeedStreamIterator(tokens[0]);
while (iteratorForToken.HasMoreResults)
{
    // Stream iterator returns a response with status code
    using(ResponseMessage response = await iteratorForToken .ReadNextAsync())
    {
        if(response.IsSuccessStatusCode)
        {
            // Consume response.Content stream
        }
    }
}

FeedToken lastProcessedToken = iteratorForToken.FeedToken;

// Some time later
FeedIterator iteratorThatResumesFromLastPoint= container.GetChangeFeedStreamIterator(lastProcessedToken);

FeedTokens can also be serialized if needed depending on the storing mechanism:
FeedToken lastProcessedToken = iteratorForToken.FeedToken;
string serialization = lastProcessedToken.ToString();

FeedToken restoredToken = FeedToken.FromString(serialization);

Consume the entire Container
While the GetFeedTokensAsync approach allows parallelization, in some cases the user might just want 1 consumer of the Change Feed, with no parallelization.
In that case, it is as simple as creating a FeedIterator without any FeedToken as input:
FeedIterator iteratorForTheEntireContainer= container.GetChangeFeedStreamIterator();
while (iteratorForToken.HasMoreResults)
{
    // Stream iterator returns a response with status code
    using(ResponseMessage response = await iteratorForToken.ReadNextAsync())
    {
        if(response.IsSuccessStatusCode)
        {
            // Consume response.Content stream
        }
    }
}

This iterator also provides the FeedIterator.FeedToken to store and resume at a later point in time.
Change Feed for a Partition Key
This PR also enables the same construct to read the Change Feed for a particular Partition Key, again, it's an overload of the GetChangeFeedStreamIterator / GetChangeFeedIterator:
FeedIterator iteratorForTheEntireContainer= container.GetChangeFeedStreamIterator(new PartitionKey("myPartitionKeyValueToRead");

Support for POCOs
The Change Feed iterator comes in two flavors, one with Stream support (returns ResponseMessage on ReadNextAsync) and one for POCO Types (returns FeedResponse<T> on ReadNextAsync):
FeedIterator iteratorWithStreams = container.GetChangeFeedStreamIterator();

FeedIterator<MyPOCO> iteratorWithPOCOS = container.GetChangeFeedIterator<MyPOCO>();

Scale support
If a FeedToken represents multiple units of Change Feed consumption, the IEnumerable<FeedToken> FeedToken.Scale() can be used to attempt a Scale out.
This is useful if we initially start reading the Change Feed for the entire Container, and we later want to try and parallelize the consumption:
FeedIterator iteratorForTheEntireContainer= container.GetChangeFeedStreamIterator();
while (iteratorForToken.HasMoreResults)
{
}

// Scale out
FeedToken lastUpdatedFeedToken = iteratorForTheEntireContainer.FeedToken;
IReadOnlyList<FeedToken> childTokens = lastUpdatedFeedToken.Scale();
if (childTokens.Count > 0)
{
    // Start new iterators with each token
}

Partition Key Ranges
For monitoring purposes, it is also now possible to obtain which are the Partition Key Ranges that a particular FeedToken represents, through the Container.GetPartitionKeyRangesAsync method, that takes a FeedToken as parameter:
FeedIterator iterator = container.GetChangeFeedStreamIterator(someInitialFeedToken);
while (iterator.HasMoreResults)
{
    // Stream iterator returns a response with status code
    using(ResponseMessage response = await iterator.ReadNextAsync())
    {
        if(response.IsSuccessStatusCode)
        {
            // Consume response.Content stream
            IEnumerable<string> partitionKeyRanges = await container.GetPartitionKeyRangesAsync(iterator.FeedToken);
        }
    }
}

Type of change

[X] New feature (non-breaking change which adds functionality)

Closing issues
Closes #972
Closes #831

@bchong95 The API was designed with Michael

@FabianMeiswinkel The problem with that API (TryGetContinuationToken) is that in migration scenarios, you might need to interoperate. I did remove the UpdateContinuation public API, but this one would be required, at least in V3 (V4 we can remove it).

@FabianMeiswinkel After an offline sync, the API you mentioned (TryGetContinuationToken) has been removed from the public surface.

@ealsur, thanks for all the work on this. I saw you released 3.8.0 yesterday, but this was not included. When can we expect this? This is really blocking us to upgrade from v2...

@WimVergouwe We are working on adding more features related to this and the API changed, see the latest linked PR.

@ealsur, any update on this? We're still stuck on v2...

@WimVergouwe sadly we could not GA just yet, there are new features on the service side which are coming soon (see //Build change feed announcements) so we are making sure our current API model is compatible with them.

Also waiting for this.  A quick look at 3.12.0 indicated still in preview.

In v2, we have our own custom logic to process change feed across all partitions and we're also handling partition splits our self.
We're iterating DocumentClient.ReadPartitionKeyRangeFeedAsync and checking partitionIds in PartitionKeyRange.Parents to find the split partitions. But in v3 everything needed is marked as internal.
This is currently blocking us from moving to v3.
Any chance this will change? Or is there another way how to handle partition splits?

@zbynek001 The APIs in V3 are split-proof, so when you get the FeedRanges, you can start the iterators and you won't face splits. Reference https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed-pull-model

Yes, but the FeedRange is not scaling well. If we have at the beginning collection with 1 partition, we get 1 FeedRange. If the collection grows over time to thousands of partitions, we still have that one FeedRange, so we cannot spread the processing over several machines.
Another issue is that with FeedRange, we are not in control of switching between partition to process, so processing of one partition might be far ahead then another partition, which is not desired in our case

For scaling as the partitions grow, we are having the discussion here https://github.com/Azure/azure-cosmos-dotnet-v3/issues/1680
Now for the second point you mention, it's the same behavior with V2 PartitionKeyRangeId, each one can be consumed independently and the continuation is independent. If you have 2 FeedRanges, each one is independent of the other. What you are looking for is probably what we are discussing in the scaling out support.

I have run into a problem when using the pull model.
I initiate the feed change iterator with a specific partition key, but I get changes from other, very similar, partitions.
For example, my partitions begin with a 12 character code like B3FAZLSZTZHYJL and are followed by another identifier such as "current." If I ask for only the partition "B3FAZLSZTZHYJLcurrent," I will get other changes that begin with "B3FAZLSZTZHYJL."  For example, I get the changes for partition B3FAZLSZTZHYJL0006490603.
My guess is that this is due to how the FeedRange interprets the partition key and derives a range. Is there a workaround you could suggest for this?

@benjifarmer Can you create an Issue for this? This is a PR comment 😄

Sure! But I think I may have been mistaken.
When I call GetFeedRangesAsync I see that I only have one physical partition, so this might be the expected behavior? Or should defining a partition key on GetChangeFeedIterator only return changes from the specific partition key regardless of how many physical partitions there are?

It should be returning changes just for that Partition Key value. Similar issue: https://github.com/Azure/azure-cosmos-dotnet-v3/issues/1796

I can confirm #1796 is a duplicate of my issue. I have reverted to 3.11.0-preview and everything works fine. I'll be patiently awaiting the next preview release. Thank you.


Findings on the fly

/rebase

I've found that I had a todo left in ScanResult.filterPath which I just adjusted with recent push. Please have a closer look there.


Derive 5 from language syntax

Instead of relying on a predefined value of 5, it can be derived from first principles (e.g. low level language syntax).
This also makes the assertion in test.js more meaningful since it now doesn't just assert literal values to be equal.

#96 is better though


ESP32 :  fails to build the mcuboot, zephyr v3.1.0 rc2,  sdk 0.14.2

Describe the bug
Fails to build the mcuboot with sdk0.14.2.
Logs and console output
B250M-D3H:~/zephyrproject/bootloader/mcuboot/boot/espressif$ cmake -DCMAKE_TOOLCHAIN_FILE=tools/toolchain-esp32.cmake -DMCUBOOT_TARGET=esp32 -DMCUBOOT_FLASH_PORT=/dev/ttyUSB0 -B build -GNinja
CMake Error at /usr/share/cmake-3.23/Modules/CMakeDetermineSystem.cmake:130 (message):
Could not find toolchain file: tools/toolchain-esp32.cmake
Call Stack (most recent call first):
CMakeLists.txt:11 (project)
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
Environment (please complete the following information):

OS: Ubuntu
Toolchain:   Zephyr SDK  0.14.2
Zephyr Version 3.1 rc2

@sam131208 It is necessary to follow all the steps to allow mcuboot building:
https://github.com/mcu-tools/mcuboot/blob/main/docs/readme-espressif.md#installing-requirements-and-dependencies
Would you retry?
Thanks.


How fast did you perform when detecting one image.

Hi,
Great work!
You said that you use one-stage method for object detection. I want to know more details on the performance time with corner net.
Thank you!

The average inference time is 244ms per image on a Titan X (PASCAL) GPU.


Fix PrefixPathMapping.equals()

Motivation:
PrefixPathMapping.equals() does not consider stripPrefix flag, making
the equals() method returns true on two PrefixPathMappings with the
same prefix and different stripPrefix flags
Modifications:
Modify PrefixPathMapping.equals() to consider the stripPrefix flag
Result:
One less bugs

@delegacy PTAL (assigned you for no apparent reason. Just doing a round-robin)

Just for the sake of curiosity, stripPrefix is not needed in toString?

LGTM. :shipit:


There was an error while trying to pair with BitPay using the pairing code

We are running Magento CE ver. <IP_ADDRESS>
When adding the Paring Code in Backend Magento - this is the error we receive:

There was an error while trying to pair with BitPay using the pairing code XjeXXiAiDk5k7xdyxgXXXX. Please try again or enable debug mode and send the "payment_bitpay.log" file to<EMAIL_ADDRESS>for more help.
Version of BitPay extension is 2.1.15
PHP version is 7.1, site running on SiteGround.
Thanks much for advice!

All solved - used the wrong pairing code, looking forward to be testing live.


Update plan to grafana 2.x ?

Hi @ivantopo ,
Hope you are at your best these days... Any plan to upgrade grafana dashboard to latest?

Well, we certainly thought about it and there is an open PR that makes the upgrade but I didn't have the bandwidth to get into that now.. We will, at some point, for sure! but I don't know when :S...

Done https://github.com/kamon-io/docker-grafana-graphite/pull/29


How to completely purge a particular version of nodejs using nvm?

nvm uninstall X, where X is the versionish pointer to the node/iojs version you wish to uninstall.
For future reference, nvm --help will list all commands you'd need to know.

I felt that 'uninstall' left residues, was finding ways for purging the entire version. Thanks!

It does not, that purges 100% of the traces of the node version.


Updated the list of supported filetypes for container version 3.4.0

What's Changed?

Added support for all filetypes supported in the upcoming 3.4.0 release

Ty


Update $options API docs

Added explicit focus on the non-reactive behaviour, because IMO those GitHub issue comments are linked too much across several articles and tutorials. And some people claim that this part is not even documented.
LMK what you think. And also, thank you for your time ❤.

Thanks for the review. Let me put the suggestions together in a new commit later today.


Update: Initial c3 visualization extraction

Resolves #

Description
Proposed Changes

move c3 visualization to @yavin/c3 package
rename navi-vis-c3-chart to yavin-c3-chart
removed v2 visualization serializers
removed c3 anomaly dataset feature
removed jQuery from navi-vis-c3-chart
converted request v1 mocks to v2

Screenshots
License
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Question about the v2 serializers removal. Are we ready for this? all our viz models already v2?

Question about the v2 serializers removal. Are we ready for this? all our viz models already v2?

@cythrawll yes, I confirmed this with @kevinhinterlong in the beginning. All tests pass, but we should do another PR to clean up any remaining v1 logic.


Enhance the documentation of :autocmd

Closes #1119.
This patch improves the documentation of :autocmd for the use case in which users want to source ~/.vimrc more than once.
First time I edit the help, please if the format is wrong just tell me and I'll revise.

I'll include it, thanks.


[BUG] Signup and login form not changing theme

Description of the bug
Login form and signup form is not changing their theme when darkmode button is clicked.
Please add screenshots (if applicable)

Add any other context about the problem here
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I want to work on this issue as a contributor.
Pleasure Assign so that I can show my skills under GSSoC'23.

@Deepu178 Hey, please review this issue.


Redirects not followed while getting maven metadata

Sadly, I cannot reproduce this problem anymore but this happened with Appboy SDK a few hours after they released 7.0.0
repositories {
        maven { url = uri("http://appboy.github.io/appboy-android-sdk/sdk") }
}

dependencies {
       implementation("com.appboy:android-sdk-ui-jetified:_")
}

This generated a malformed versions.properties:
version.com.appboy..android-sdk-ui-jetified=[some xml data here]

Unfortunately I cannot reproduce but it looked like an unhandled redirect, which would make sense considering there's little chance URL.readText() will follow redirects: https://github.com/jmfayard/refreshVersions/blob/502c47e7cb9394e813030b644ef7f299b430733f/refreshVersions/src/main/kotlin/de/fayard/versions/internal/LatestVersionsRetrieval.kt#L64

I expect this to be fixed once we use OkHttp (that is the "cancellable network I/O" I had in mind while writing the TODO comment).

We switched to OkHttp a while ago, so this issue should be fixed now.


Use correct normal for ReflectionProbe in GLES2

The GLES2 SpatialMaterial used unchanged normals from the vertex shader for ReflectionProbe reflections, and thus ignored the normal map. This commit makes ReflectionProbe reflections use the normals which can be perturbed by an input normal map.
Before:

After:

This fixes #43873

Thanks! And congrats for your first merged Godot contribution :tada:


[BUG] CRDs for rancher-monitoring-crd helm chart are not updated

Rancher Server Setup

Rancher version: 2.8.3
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): EKS 1.25

Proxy/Cert Details: -

Information about the Cluster

Kubernetes version: 1.25
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? Imported, EKS

User Information

What is the role of the user logged in? Admin

Describe the bug
The CRDs for the rancher-monitoring-crd helm chart are not updated. The job started by the helm hook succeeds, but the CRDs are not updated. The following error message appears in the logs of the job:
2024-05-22T08:16:43.513387966Z Error from server (Forbidden): error when replacing "/etc/crd/charts/crds/crd-alertmanagerconfigs.yaml": customresourcedefinitions.apiextensions.k8s.io "alertmanagerconfigs.monitoring.coreos.com" is forbidden: User "system:serviceaccount:cattle-monitoring-system:rancher-monitoring-crd-manager" cannot update resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope

To Reproduce

Deploy rancher-monitoring-crd
Check if CRD (e.g. alertmanagerconfigs.monitoring.coreos.com) is updated

Result
Expected Result
CRDs are updated.
Additional context
We assume that the problem is the RBAC for the ClusterRole rancher-monitoring-crd-manager. It contains the non-existing verb replace, but it doesn't contain the verb update.

This has been fixed and will go out with our next release.


Mention homebrew as an installation option in readme

What happened (or feature request):
I'm walking through the Readme and noticed that the installation instructions do not mention Homebrew.
What you expected to happen:
The readme should be updated to include mention of homebrew as an installation option.

Just noting that there doesn't seem to be a mention of homebrew in the documentation site either.

Duplicate of #434, right?

Yup, duplicate.


Image embedding in ONNX model

Why can't we include the image embedding part in the onnx model? Any specific reason to compute the embeddings beforehand before sending it to the onnx model. Is it even possible to include in the onnx model?

I have attempted to export the encoder to onnx but it did not work very well.
I have modified the SamPredictor class:
...

class SamPredictor(nn.Module):
    ...
    @torch.no_grad()
    def forward(
        self,
        transformed_image: torch.Tensor,
    ):
        input_image = self.model.preprocess(transformed_image)
        features = self.model.image_encoder(input_image)

        return features

Here is the code to export the encoder:
import torch
import onnxruntime as ort
from mobile_sam import sam_model_registry, SamPredictor
import onnxruntime
from onnxruntime.quantization import QuantType
from onnxruntime.quantization.quantize import quantize_dynamic
import numpy as np

model_type = "vit_t"
sam_checkpoint = "./weights/mobile_sam.pt"

device = "cuda" if torch.cuda.is_available() else "cpu"

mobile_sam = sam_model_registry[model_type](checkpoint=sam_checkpoint)
mobile_sam.to(device=device)
mobile_sam.eval()

predictor = SamPredictor(mobile_sam)

image = torch.randn(1, 3, 224, 224)

torch.onnx.export(
    predictor,
    (image,),
    "model.onnx",
    input_names=["image"],
    # opset_version=16,
    output_names=["features"],
    do_constant_folding=False,
    dynamic_axes={"image": {2: "height", 3: "width"}}
)

forward_features = predictor(image).clone().numpy()

session = onnxruntime.InferenceSession("model.onnx")
onnx_features = session.run(None, {
    "image": image.numpy()
})[0]

onnx_ok = np.allclose(default_features, onnx_features)
print(onnx_ok) # False

print(
    torch.nn.functional.l1_loss(
        torch.as_tensor(forward_features),
        torch.as_tensor(onnx_features),
    ).item()
) # ~0.04

As you can see while I exported the encoder, it does not produce the same output as in pytorch.
Maybe someone could help on this.

Alright thanks! I will look at that.

You can find the converter for the encoding part to the onnx format in the repository Segment Anything CPP Wrapper.
Here is the Segment Anything CPP Wrapper for macOS.
This code is originated from Segment Anything CPP Wrapper and implemented on macOS app RectLabel. We customized the original code so that getMask() uses the previous mask result called as low_res_logits and retain the previous mask array for undo/redo actions.
We hope this macOS version would help to develop the iOS version.
Please let us know your opinion.

I can confirm that my script does work as I have used it for a personal project @chaitanyakrishna1248 you can close this issue :)

Thank you, I Will try this!


Invert sensor for Goodwe inverter?

When I'm using 100 watts from the grid my Goodwe sensor output -100w so the flow on this card is the wrong way round. Could you add an option to invert the sensor?

I'll add an option to invert the animation 👍🏼

thanks :)
That's also valid for SolarEdge Inverters - and probably for many others as well 👍

Hi @TommySharpNZ @ChristophCaina,
Your requested feature is now available in the latest release!
Thank you for your patience.

i've added the inverted: true option - but the animation does not change... ?

@ChristophCaina care to share your config with me please?
Please also make sure to do a fresh reload of HA, the caching is very aggressive. (you can see the installed version in the JS console)

ok, seems to be a caching issue ... tried with Edge (even after restart and ctrl+f5) which did not help... while on Edge it seems to be working as expected.


Update jest?

What's your concern?

@djyde would be nice to use Jest 20 instead of 19.

we use the same version that react-native uses: https://github.com/facebook/react-native/blob/master/package.json#L232


Its not working for minecraft 1.21.4

Hi there i recently tied to use the mod but when i enter the gui for the seedcracker it only shows me versions 1.20.2 or lower. i instaled the latest version of the mod and of the fabricloader.

seed cracking stuff has not changed since 1.20.2 so it still works completely fine


Lost connection to device - when trying to run in debug mode

After updating to MacOs  Catalina, can't run my app in debug mode anymore.
Builds correctly and every time gets stuck at syncing files with Lost Connection to device
I tried Flutter stable and beta channel, also tried running from Visual Studio Code and Android Studio.
I also tried running on iOS emulator, Android emulator, and physical Android device.
The same thing every time.
On Windows works without problem, same code.
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Mac OS X 10.15.3 19D76, locale en-HR)
    • Flutter version 1.12.13+hotfix.8 at /Users/deva/Documents/Repos/flutter
    • Framework revision 0b8abb4724 (2 weeks ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/deva/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.3.1, Build version 11C504
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 43.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] IntelliJ IDEA Ultimate Edition (version 2019.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 39.0.5
    • Dart plugin version 192.6262.58

[✓] VS Code (version 1.42.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.8.1

[✓] Connected device (1 available)
    • GM1913 • 68f90884 • android-arm64 • Android 10 (API 29)

! Doctor found issues in 1 category.

Hi @deva666
could you provide your flutter run --verbose?

[  +31 ms] D/PhoneWindow(22856): setNavigationBarColor: fffafafa
[ +214 ms] W/DynamiteModule(22856): Local module descriptor class for providerinstaller not found.
[  +23 ms] I/DynamiteModule(22856): Considering local module providerinstaller:0 and remote module providerinstaller:0
[        ] W/ProviderInstaller(22856): Failed to load providerinstaller module: No acceptable module found. Local version is 0 and remote
version is 0.
[   +2 ms] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->getLong(Ljava/lang/Object;J)J (greylist,core-platform-api,
linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->arrayBaseOffset(Ljava/lang/Class;)I
(greylist,core-platform-api, linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->copyMemory(JJJ)V (greylist, linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->getByte(J)B (greylist,core-platform-api, linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->getByte(Ljava/lang/Object;J)B (greylist,core-platform-api,
linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->getLong(J)J (greylist,core-platform-api, linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->putByte(JB)V (greylist,core-platform-api, linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->putByte(Ljava/lang/Object;JB)V (greylist,core-platform-api,
linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->getLong(Ljava/lang/Object;J)J (greylist,core-platform-api,
reflection, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Lsun/misc/Unsafe;->getLong(Ljava/lang/Object;J)J (greylist,core-platform-api,
reflection, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden field Ljava/nio/Buffer;->address:J (greylist, reflection, allowed)
[  +15 ms] V/NativeCrypto(22856): Registering com/google/android/gms/org/conscrypt/NativeCrypto's 286 native methods...
[   +6 ms] W/devcic.foodste(22856): Accessing hidden method Ljava/security/spec/ECParameterSpec;->getCurveName()Ljava/lang/String;
(greylist, reflection, allowed)
[  +34 ms] I/ProviderInstaller(22856): Installed default security provider GmsCore_OpenSSL
[ +607 ms] W/devcic.foodste(22856): Accessing hidden field Ljava/net/Socket;->impl:Ljava/net/SocketImpl; (greylist, reflection, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Ldalvik/system/CloseGuard;->get()Ldalvik/system/CloseGuard;
(greylist,core-platform-api, linking, allowed)
[   +1 ms] W/devcic.foodste(22856): Accessing hidden method Ldalvik/system/CloseGuard;->open(Ljava/lang/String;)V
(greylist,core-platform-api, linking, allowed)
[   +1 ms] W/devcic.foodste(22856): Accessing hidden field Ljava/io/FileDescriptor;->descriptor:I (greylist, JNI, allowed)
[  +51 ms] W/devcic.foodste(22856): Accessing hidden method Ljava/security/spec/ECParameterSpec;->setCurveName(Ljava/lang/String;)V
(greylist, reflection, allowed)
[  +16 ms] W/devcic.foodste(22856): Accessing hidden method Ldalvik/system/BlockGuard;->getThreadPolicy()Ldalvik/system/BlockGuard$Policy;
(greylist,core-platform-api, linking, allowed)
[        ] W/devcic.foodste(22856): Accessing hidden method Ldalvik/system/BlockGuard$Policy;->onNetwork()V (greylist, linking, allowed)
[+4890 ms] Updating files
[ +693 ms] Service protocol connection closed.
[        ] Lost connection to device.
[+1008 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: Write failed (OS Error: Broken pipe,
errno = 32), address = <IP_ADDRESS>, port = 51921
[        ] trying again in a few - 9 more attempts left
[ +504 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51926
[        ] trying again in a few - 8 more attempts left
[ +504 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51929
[        ] trying again in a few - 7 more attempts left
[ +505 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51930
[        ] trying again in a few - 6 more attempts left
[ +507 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51931
[        ] trying again in a few - 5 more attempts left
[ +504 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51932
[        ] trying again in a few - 4 more attempts left
[ +503 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51933
[        ] trying again in a few - 3 more attempts left
[ +503 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51934
[        ] trying again in a few - 2 more attempts left
[ +502 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51935
[        ] trying again in a few - 1 more attempts left
[ +504 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51936
[        ] trying again in a few - 0 more attempts left
[ +506 ms] Error writing "build/flutter_assets/assets/foodster_fts.sqlite" to DevFS: SocketException: OS Error: Connection refused, errno =
61, address = <IP_ADDRESS>, port = 51939
[        ] DevFS sync failed. Lost connection to device: SocketException: OS Error: Connection refused, errno = 61, address = <IP_ADDRESS>,
port = 51939
[   +1 ms] Syncing files to device GM1913... (completed in 12,671ms, longer than expected)
[   +1 ms] "flutter run" took 25,548ms.

then
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:509:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)
#3      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#4      _rootRunUnary (dart:async/zone.dart:1134:38)
#5      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#6      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#9      Future._completeWithValue (dart:async/future_impl.dart:524:5)
#10     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#11     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#12     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#13     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#14     _rootRunUnary (dart:async/zone.dart:1134:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#22     IosProject.isSwift (package:flutter_tools/src/project.dart)
#23     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#24     _rootRunUnary (dart:async/zone.dart:1134:38)
#25     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#26     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#27     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#28     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#29     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#30     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#31     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#32     IosProject.buildSettings (package:flutter_tools/src/project.dart)
#33     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#34     _rootRunUnary (dart:async/zone.dart:1134:38)
#35     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#36     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#37     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#38     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#39     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#40     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#41     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#42     XcodeProjectInterpreter.getBuildSettings (package:flutter_tools/src/ios/xcodeproj.dart)
#43     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#44     _rootRunUnary (dart:async/zone.dart:1134:38)
#45     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#46     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#47     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#48     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#49     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#50     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:32:15)
#51     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:290:13)
#52     _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart)
#53     _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#54     _rootRunUnary (dart:async/zone.dart:1134:38)
#55     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#56     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#57     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#58     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#59     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#60     Future.wait.<anonymous closure> (dart:async/future.dart:400:22)
#61     _rootRunUnary (dart:async/zone.dart:1134:38)
#62     _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#63     _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#64     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#65     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#66     Future._addListener.<anonymous closure> (dart:async/future_impl.dart:389:9)
#67     _rootRun (dart:async/zone.dart:1126:13)
#68     _CustomZone.run (dart:async/zone.dart:1023:19)
#69     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#70     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#71     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#72     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#73     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#74     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

It crashes before the app can run?  Or is your app crashing on launch?
Would you mind testing on the dev channel?

I tried also the dev channel. Same thing.
The app doesn't crash, it just gets stuck at the loading screen (splash screen).
This is only when trying to attach a debugger. When running without debugger everything is fine.
But if I remove the sqlite file I am using from the assets it runs fine, debugger gets attached.

Hello @deva666. I cannot reproduce this issue currently. Can you confirm if this issue is fixed now?

Thank you for the confirmation. I'm closing the issue as fixed.


refresh error

Hello, I 'm using skywalking v6.1
Refresh the trace page and report an error
As shown below:

ref https://github.com/apache/skywalking-rocketbot-ui/issues/91

Spring Boot Actuator add /trace  as endpoints out of the box.
I solved it by disable  /trace  endpoints.
modify webapp.yml like this:
server:
  port: 8080

collector:
  path: /graphql
  ribbon:
    ReadTimeout: 10000
    # Point to all backend's restHost:restPort, split by ,
    listOfServers: <IP_ADDRESS>:12800

security:
  user:
    # username
    admin:
      # password
      password: admin

endpoints:
  trace:
   # disable  trace  endpoints
    enabled: false

Ref doc https://docs.spring.io/spring-boot/docs/1.5.1.RELEASE/reference/htmlsingle/#production-ready-endpoints
@hanahmily Do you prefer to ask UI change path or disable the endpoints/trace?

@wu-sheng The third option: change the endpoints base path

change the endpoints base path in Spring? I think that is a better way. Could you submit a pull request to fix this?

I also encountered this problem in the latest version
version: 8.7.0
docker-compose.yml
services:
  oap:
    image: apache/skywalking-oap-server:8.7.0-es7
    container_name: oap
    restart: always
    ports:
      - 11800:11800
      - 12800:12800
    environment:
      - SW_STORAGE=elasticsearch7
      - SW_STORAGE_ES_CLUSTER_NODES=<IP_ADDRESS>:9200
      - SW_NAMESPACE=skywalking
      - SW_CORE_RECORD_DATA_TTL=3
      - SW_CORE_METRICS_DATA_TTL=3
      - TZ=Asia/Shanghai
  skywaling-ui:
    image: apache/skywalking-ui:8.7.0
    container_name: ui
    depends_on:
      - oap
    links:
      - oap
    ports:
      - 8888:8080
    environment:
      - SW_OAP_ADDRESS=http://oap:12800
      - TZ=Asia/Shanghai

Is there a solution?


Improve coarse-grained parallelism

This makes better use of available processing power, by overlapping different phases of computation: memory-bound, cache-bound (and if tiles are not in memory, IO).

@thewtex Azure pipeline was not run. Probably the same problem as with main ITK repository.

Module CI needs updating. PR: https://github.com/InsightSoftwareConsortium/ITKContinuousIntegration/pull/30.

This passes now, after CI image has been updated.


Method to disable individual tests

Raising issue further to e-mail conversation with @jboddey.
Use case
User should be able to disable individual tests from running, either from test pack (preferred), or from module_config.json files.
I tried two methods as instructed.

Deleting the highlighted block below from a test pack...

...in this case the tests were still conducted, despite not being present in the test pack.

Adding "enabled": false to the module_config.json file...

...yields the below in the report. I would maybe have expected a result of "Disabled" or for the tests to not appear at all, as opposed to "Feature Not Detected" (the detection didn't happen).

These may warrant being two separate issues, but were discussed in the same thread of a need to disable individual tests. I can create a separate issue if wanted.
On a related point, it is noted that entire modules of tests can be disabled via the UI below, and so I'm unsure how the proposed disabling of individual tests may interact/interfere with the below in the UI. As an observation I would have thought test pack choice would override and even avoid the need to specify these options in the UI to some extent.

When you change a module configuration file, you need to rebuild the modules for it to take effect.
sudo cmd/build
This is not the recommended approach as it will disable these tests for all devices for all future tests and will also get overridden during upgrades.
The recommended approach is to modify the specific device configuration file.
For your example, if you navigate to the local/devices/< device folder >/device_config.json file and modify:
  "test_modules": {
    "protocol": {
      "enabled": true,
      "tests": {
        "protocol.valid_bacnet": {
          "enabled": false
        },
        "protocol.bacnet.version": {
          "enabled": false
        },
        "protocol.valid_modbus": {
          "enabled": false
        }
      }
    },

Which will give the following results:

You should be able to expand this approach to any individual test.  You do not need to itemize every test within a module, only the specific ones you want to modify.

When you change a module configuration file, you need to rebuild the modules for it to take effect.
sudo cmd/build
This is not the recommended approach as it will disable these tests for all devices for all future tests and will also get overridden during upgrades.

@jhughesbiot thanks for the nod on this. Just confirming here for my own notes that changing module_config.json and then rebuild has the below effect.

@jhughesbiot Is there scope to get the functionality as discussed in method 1 in the original post working?
I would anticipate that the expected behaviour be that the exclusion of a test from a test pack should cause it not to run at all, nor appear in the test result list. What are your thoughts?

@duncangreene We will go ahead with the disabling of tests if it is not included in the test pack.

@duncangreene We will go ahead with the disabling of tests if it is not included in the test pack.

@jboddey Sounds good, a couple of supplementary questions if possible.

If a test is not included in a test pack, will it not appear in the results at all (preferable), or will it appear in the results as 'disabled'?
Will this functionality supersede/negate the need for the options in the UI below?

If a test is not included in the test pack, it will not be included at all. It also negates the need to disable modules in the UI (if none of those module's tests are in the test pack). However, the test module must first be enabled if any of the tests are to run.

This has now been merged into dev and will be released in v2.1


0.16 update

+1

@thebigsmileXD doesn't work for 1.0.0 we can't hear anything

Sorry for late reply and testing soon


Small improvements

I am not a bit fan of finals in the code, but... new project, new approach, a small step outside of my comfort zone of coding habits :)
Travis - awesome


[BBU] Extension Request

Our team would like to request an extension to this RFP for more time to formulate our response.

We will raise this request in our Working Group session Thursday.

The Bedrock Consortium Governance Framework Working Group has approved a 1 week extensions for RFP response submissions. New date is Fri 22-May-2020. The RFP will be updated to reflect this.


[MOB-5028] removes promise processing

🔹 JIRA Ticket(s) if any

MOB-5028

✏ Description
This pull request includes removing the promise processing from the SDK. The promise is returned by the SDK and processed on the application side.

Lgtm, but is there a PR to update documentation? Sounds like customers would need to be aware of this in next release

This does not change what is returned by the APIs. So, implementation on the application side is unchanged.


after update to 0.32.1, component event has payload type error

vue 2.6
volar update to 0.32.1
ts 4.5.5
I use elementui select component. it has change event ,  has payload error after volar update to 0.32.1;
(property) 'change': ((payload: Event) => void) | undefined Type '(item: any[]) => Promise<void>' is not assignable to type '(payload: Event) => void'.   Types of parameters 'item' and 'payload' are incompatible.

Could you also provide what is the old behavior in 0.32.0?

I installed 0.32.0 VSIX, here is the old behavior;

+1

Is there an estimate for a fix for this? It causes nearly all my components to show problems and is quite detrimental to efficient development.

@barfurth please use 0.32.0 for now. I'm working on #1009 currently, this pr change all server code so I can't resolve other problem before merge it.

@ysneo seems element-ui do not have valid events define in ElSelect class, it should have $props: { onChange: (arg: ARG_TYPE) => void } or $emit: { (e: 'change', arg: ARG_TYPE): void } for event type.
https://github.com/ElemeFE/element/blob/473ef53f9317ad6ca8c629655982244902751e63/types/select.d.ts#L11
If element-ui not going to support types, I recommend you to use Vetur as it built-in support intellisense for ElementUI in Vue2.

@NikhilVerma your component does not provide a valid type, try change it to
// Component.vue
<template>
  <div @click="selectTab">hello</div>
</template>

<script lang="ts">
import Component from "vue-class-component";

@Component
export default class Comp extends Vue {
  $emit!: { (e: 'select', value: number): any }
  selectTab() {
    this.$emit("select", 1);
  }
}
</script>

// Consumer.vue
<template>
  <Component @select="selectTab" />
</template>

<script lang="ts">
import Component from "vue-class-component";
import MyComponent from "./Component.vue";

@Component({
  components: {
    Component,
  },
})
export default class Consumer extends Vue {
  static components: { Component: typeof MyComponent }
  selectTab(value: number) {
    console.log(value);
  }
}
</script>

See https://github.com/johnsoncodehk/volar/pull/750#issuecomment-1023947885.

@johnsoncodehk I’m not sure this issue is addressed considering this was working before.
We can’t really expect every UI library to type their components? Also this would not work for dynamically registered components, because Volar wouldn’t know what to look for (e.g. Nuxt directory based imports)? Perhaps this is a separate issue.

@barfurth it's changed in https://github.com/johnsoncodehk/volar/commit/99386bee9f25c73f7b13cdec2b358c6a1c09a7a7.
This issue is for invalid type components (no $props defined), so now I'm just rolling back to the previous behavior for invalid type components.
For dynamically components, see https://github.com/johnsoncodehk/volar/issues/682#issuecomment-965612541.


Window Insets support

When using default UI, there's no option to handle window insets easily.
Basically we have to create custom UI and handle it ourselves.
Is there other "simpler" method? Or would you consider adding support for window insets without the need to create custom UI controls?

Hi, I would suggest to use web ui. To stay on the safe side with YouTube terms of service.


Stop the Spongemock command from doubling digits.

This should stop the Spongemock command from doubling digits as in this example:
[9:52 PM] calrogman: !bob<PHONE_NUMBER>1234567890
[9:52 PM] BOTFBB: [meme.jpg]
123445677890012334556788900

Ignore. Am dumb.

!Char.IsNumber(input[i])


[value-move-function] Eliminate unnecessary book keeping.

Just a small optimization I saw.

@swift-ci smoke test

@swift-ci smoke test macOS platform


feat: add a feature of dashboard and search feature

Added Dashboard and Search Feature

Implemented a new dashboard for better user interaction and data visualization.
Added a search feature to enhance the user experience by allowing users to search for specific items efficiently.
Improved overall application performance and usability with these new features.

this is Bilal the first collaborator of the real estate management system which add very smooth user dashboard to the system and add some important backend functionality thank you for your support Bilal


AdoptOpenJdk has moved/rebrended to Adoptium

AdoptOpenJdk was rebrended to Adoptium https://adoptium.net/
Original AdoptOpenJdk has only JDK16, whereas Adoptium has already 17. Would be amazing if you would update your watcher to use new Adoptium

Thank you for your suggestion.
Current (v.<IP_ADDRESS>) of my updater is still branded as Update Watcher for AdoptOpenJDK *, but it allows to install and updateEclipse Adoptium (Temurin) 17 binaries:

Do you see these values in your updater? It should detect installed JDK/JRE MSI's automatically. UnZIPped instances may require adding them manually.

As for name change, I'm planning to rebrand simultaneously with the switch from api.adoptopenjdk.net to api.adoptium.net. This will be done after either IBM releases its own API for Semeru (ex. AdoptOpenJDK openj9 builds) or api.adoptium.net would start providing Semeru releases (https://github.com/adoptium/api.adoptium.net/issues/187) .


mAP and AR:  definition of small medium large ?

Hey,
i couldnt find any answer to this: at what point is an object considered small, medium or large for the calcualtion of the metrics mAP and AR?
thanks alot in advance :)

Assuming that the mAP in YOLACT is measured using pycocotools, i.e. using the mAP from the MS COCO competition, the definitions of the AP metrics for small, medium and large can be found on the MS COCO site:

@susanin1970  Thank you very much!


Create quick_sort.cpp

@ravikaranrathore Your PR has been merged successfully, Thank you for your contribution.
Give repo a star if it was useful.
Happy hacking.


Stop the server running in background prior to upgrade

Stop the server running in background prior to upgrade to 0.16
Upgrade scenario
0.13 through 0.15 > 0.16 on W7 (build # 114)
Current Behavior
In KA Lite versions 0.13 through 0.15 users had the option to run the server on system startup with the scheduled task. Since that task was run as the SYSTEM user, current user of KA Lite is not even able to stop the server. During the upgrade process, server is still running background and that is a potential problem for two reasons:

Could be causing the issue #347 - error described here. We haven't been able to reproduce it reliably, but could be still related to the server running in the background during upgrade.
Bad user experience: Once the upgrade process is finished, the old scheduled task is deleted, but server is still running (1-2 python processes are active) and current user cannot stop it. User is also unable to start the server on their own since task tray program registers the server that is running and displays only the Stop Server option as available, but it cannot stop the python process run as SYSTEM user. Task-tray program also displays the Load in browser option as available, but if user selects it, it will only open a blank page at server's IP.

At this point user is left with the only option of restarting the system to regain control of the KA Lite server. We could include that requirement in the installer, or even better: stop the server prior to starting the upgrade process.
Steps to reproduce

Install 0.15.1.
Upgrade to 0.16.
Start KA Lite.exe.
Activate "Load in browser" in KA Lite task-tray Options.

Fixed in #439

Reopening since #439 hasn't been merged or released.


nextpnr does not build on Darwin

See #67827 and ea34c61c0f1e8541de506ce627816c02c066a3f8 for details. The error is a trivially missing OpenGL dependency:
https://hydra.nixos.org/build/99106360
...
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   filesystem
--   thread
--   program_options
--   iostreams
--   system
--   chrono
--   date_time
--   atomic
--   regex
CMake Error at /nix/store/nlxwl472c6niki4an2mlga2xpv448g9r-cmake-3.14.5/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find OpenGL (missing: OPENGL_INCLUDE_DIR)
Call Stack (most recent call first):
  /nix/store/nlxwl472c6niki4an2mlga2xpv448g9r-cmake-3.14.5/share/cmake-3.14/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /nix/store/nlxwl472c6niki4an2mlga2xpv448g9r-cmake-3.14.5/share/cmake-3.14/Modules/FindOpenGL.cmake:397 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:111 (find_package)

-- Configuring incomplete, errors occurred!
See also "/tmp/nix-build-nextpnr-2019.08.21.drv-0/source/build/CMakeFiles/CMakeOutput.log".
builder for '/nix/store/zaja99pfw0bbbkxz8r4ljfca9b132f5i-nextpnr-2019.08.21.drv' failed with exit code 1

Trellis seems to work fine, as do other things, so fixing this should unblock FPGA-related projects on Darwin as well.

This does actually build for me on my macos 10.13 machine, but if we're missing the opengl framework it should be as simple as providing it with darwin.apple_sdk.frameworks.OpenGL.

It's been a long time since I used macOS, but does this have anything to do with Apple's OpenGL deprecation?

Nah don't think so - there are other packages we build that use opengl on macos.


Generating span Id also in the default case like TraceID as per OC spec

Description
Earlier we decided to generate just TraceID and TraceOptions and not SpanID in the case of default case when user app is not passing SpanContext.
Now looking at the open census spec, we need to modify this behaviour and we need to generate default span ID also in the case of default.
Change is now generating span Id also in the default case like TraceOptions and TraceID as per OC spec
Issue reference
Closes #1592
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Can we validate his on localforwarder ? I curious about how calculator-frond-end node is shown.

Sure, yes it is in progress ..

/make-me-laugh

Can we validate his on localforwarder ? I curious about how calculator-frond-end node is shown.

Sure, yes it is in progress ..