In listener broadcast back job hanging on CURL Error

Reverb Version
1.0.0 beta-10
Laravel Version
11.0
PHP Version
8.2.7
Description
I've implemented the listener and that works great but now I'm trying to broadcast back again but the job is hanging on an curl request for which I have no clue where or why it is making a curl request. When I broadcast the same event in a command it works fine. Does anyone have a idea?
Pusher error: cURL error 28: Operation timed out after 30001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://localhost:8082/apps/899713/events?auth_key=n9djupsbzokvzk9et2zs&auth_timestamp=1716000501&auth_version=1.0&body_md5=df83fae487fd3b9a6267a60d18b3302f&auth_signature=c04c6559809aabf44c7c260df43e9e81862da2f213d30de063295c1669ef6000

Received message from client

but it taking 30 seconds to broadcast , if i trigger broadcast event by command or by http request then it immedietly reflect in client
Steps To Reproduce
Create message listener using (MessageReceived $event)
trigger  broadcast event in same listener handle method code
It takes 30 second to receive the broadcasted message in client
Also when i trigger the broadcast using command with the same AlertTrigger event it immediatly reflect in client, But all broadcasting events hang on till this above curl error message displayed in reverb debugger

When i received message in client after 30 second , first it shows 4200 message format errro & then message is being received

Reverb Version
@beta
Laravel Version
11.0
PHP Version
8.2.7
Description
I've implemented the listener and that's working great but now I'm trying to broadcast back again but there is slight 20 to 30 seconds delay to broadcast and listen to frontend. Does anyone have a idea?

Your QUEUE_CONNECTION should not be sync and your broadcasting should implement ShouldQueue interface.

Your QUEUE_CONNECTION should not be sync and your broadcasting should implement ShouldQueue interface.

Yes
Queue connection is database
And i have tried should queue interface as well still getting same issue
During message receive broadcasting

Hi all!
I have the same problem!
I can't immediately send an event to another channel.
I want to receive an event from the client to trigger another event that will send a message to another channel. If I do this through a queue, everything works.

@Atmden  Reverb uses ReactPHP. It shouldn't be blocked by any resource based transaction which is why you should use ShouldBroadcast instead of ShouldBroadcastNow and run the artisan command queue:work

@Atmden Reverb uses ReactPHP. It shouldn't be blocked by any resource based transaction which is why you should use ShouldBroadcast instead of ShouldBroadcastNow and run the artisan command queue:work

Yes it’s working using queue:work
But how can we manage it using direct should broadcast
As of now delivering reply message took delay. Is there any other way to broadcast it immediately
?

@prdip queue:work has parameter sleep --sleep. Its default is 3 seconds and you can change it to 0. I don't advise changing it to 0 since it triggers the queue always so it might be high on resource usage

I solved my problem. I hope it helps others too. In the service where I process the event, I used ChannelManager.
Here is a small part of the code
    use Laravel\Reverb\Protocols\Pusher\Contracts\ChannelManager;

    public function __construct(ChannelManager $channelManager)
    {
        $this->channelManager = $channelManager;
    }

    public function eventHandle()
    {
        // .... different code

        $response = [
            "event" => "my-event",
            "channel" => "my-channel",
            "data" => [ // My data
                "success" => true,
                "message" => "......",
            ]
        ];
        $orderChannel = $this->channelManager->find('<channel name>');
        if (!empty($orderChannel)) {
            $orderChannel->broadcast($response);
        }
    }

I solved my problem. I hope it helps others too. In the service where I process the event, I used ChannelManager. Here is a small part of the code
    use Laravel\Reverb\Protocols\Pusher\Contracts\ChannelManager;

    public function __construct(ChannelManager $channelManager)
    {
        $this->channelManager = $channelManager;
    }

    public function eventHandle()
    {
        // .... different code

        $response = [
            "event" => "my-event",
            "channel" => "my-channel",
            "data" => [ // My data
                "success" => true,
                "message" => "......",
            ]
        ];
        $orderChannel = $this->channelManager->find('<channel name>');
        if (!empty($orderChannel)) {
            $orderChannel->broadcast($response);
        }
    }

Will this work without QUEUE ? Immediate broadcast

@prdip queue:work has parameter sleep --sleep. Its default is 3 seconds and you can change it to 0. I don't advise changing it to 0 since it triggers the queue always so it might be high on resource usage

Thanks @njzabala
Queue already consume lots of cpu usage & reverb also high cpu dependent.
How can we achieve superfast broadcast delivery without queue , if not then what should we keep in mind while building real time bidirectional app using reverb !

Will this work without QUEUE ? Immediate broadcast
@prdip
Yes! Try it
It's the same if I did
...connection->send(json_encode($response));

eventHandle

Where did you manage this
in event listener or direct event ?

eventHandle

Where did you manage this
in event listener or direct event ?

I'm using a listener. Which listens to MessageReceived.
My listener receives a message from the client application. I determine the ownership of this message and call the method in my service. And in the service I do an immediate sending of another message to another channel. I have a lot of different incoming messages and therefore I moved their processing into a separate service; you can use immediate sending directly in the listener

If the issue is solved, I suggest closing the issue.

@njzabala
If there is such a possibility, you need to add a plan for implementing this functionality to the package so as not to make crutches

@Atmden Sorry. I'm not a maintainer of reverb. I just helped with what I currently know.

You will need to queue the listener or broadcast directly or broadcast to the channel directly otherwise you will block the event loop.
If you don't do that, when you catch the event, any work you do blocks the loop from processing more connections or messages. As such, if you try to broadcast a mesage syncronously, the loop cannot process it so you end up in a deadlock.

@joedixon
Is @Atmden's Channel Manager the most effective way to broadcast instantly without a queue, then?

@joedixon
I didn't clearly understand your answer.
At the moment the application is just being written and there is no real load. If you check on test accounts, everything works as it should.
But did I understand your answer correctly that if I use the ChannelManager in production to immediately send messages to a channel, I will encounter a waiting problem, new incoming messages will not be processed until the outgoing one is sent?

Using the ChannelManager should be fine as you are already in the context of the event loop. The issue with broadcasting (without queuing) is because you are making an HTTP request to the WebSocket server, which can't accept the request until the current process is complete. Of course, the current process cannot complete as it's waiting on the HTTP request so you end up in deadlock.

@Atmden How were you able to find the channel by name when that information did not exist at the time? Could I see more of the code to understand how this is being done?


Mobile menu branch

Mobile Menu

Added JavaScript linters
Added more styling
Updated HTML file.

@riskmaris the dashboard has been updated and you can now request another code review request once you are ready.
Thank you and apologies for the inconvenience.

Hi @riskmaris, I am glad that your dashboard has been updated. I sincerely apologise for this inconvenience

Hi
I have made the necessary changes but the problem I have right now is that
I cant make another pull request because when you approved the first one, i
merged it. What should i do?
On Tue, 18 Apr 2023 at 21:53, Gzim Asani @.***> wrote:

Hi @riskmaris https://github.com/riskmaris, I am glad that your
dashboard has been updated. I sincerely apologise for this inconvenience
—
Reply to this email directly, view it on GitHub
https://github.com/riskmaris/mobile-menu-branch/pull/9#issuecomment-1513649400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4Q6X7H25KP6TN4K6CJO7HLXB3PJXANCNFSM6AAAAAAXCVN2HQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi I have made the necessary changes but the problem I have right now is that I cant make another pull request because when you approved the first one, i merged it. What should i do?
…

Hi @riskmaris, please ask for a code review on a new PR and mention this PR on a link so the new reviewer can see the required changes that I’ve made


Add Paulo Figueiredo to Contributers list

Hi  @pvfigueiredo, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

The tutorial is so well made with easy language where anyone, even without any knowledge is able to follow. Honestly, I'm thankful for the tutorial and how easy it makes our beginning on the way of opensource. I hope not only learn with people, but if possible, help others who chose the same path.

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Decouple backend into RISCV and ARM

This patch is prepared for importing RISC-V backend in future.
Config variable in Makefile to switch target machine,
also need to config included backend file in main.c

I've added new way to switch between modes.
Quick demo:
Demo:

$ make config ARCH=arm
Target machine code switch to arm

$ make
  CC+LD	out/inliner
  GEN	out/libc.inc
  CC	out/src/main.o
  LD	out/shecc
  SHECC	out/shecc-stage1.elf
  SHECC	out/shecc-stage2.elf

If it looks good for you, please tell me. I'll also change README about configuration (maybe in this or next PR)

I've added new way to switch between modes.
Quick demo:
Demo:

$ make config ARCH=arm
Target machine code switch to arm

$ make
  CC+LD	out/inliner
  GEN	out/libc.inc
  CC	out/src/main.o
  LD	out/shecc
  SHECC	out/shecc-stage1.elf
  SHECC	out/shecc-stage2.elf

If it looks good for you, please tell me. I'll also change README about configuration (maybe in this or next PR)

If it looks good for you, please tell me. I'll also change README about configuration (maybe in this or next PR)

It looks great. Thanks. Let's work within this pull request.

If it looks good for you, please tell me. I'll also change README about configuration (maybe in this or next PR)

It looks great. Thanks. Let's work within this pull request.


Add linefeed in the mdx and handle it

Problem:
Multiple commands are displayed in the same line with line feed missing.
page: https://beta.reactjs.org/learn/start-a-new-react-project
Solution:

We can use 2 trailing empty spaces or <br/> to add new line feed
when we have multiple lines typeof children.props.children is not string but an object. So use children.props.children directly when it is a string or an object (typeof children.props.children === 'string' )

Before:

After:

We can use 2 trailing empty spaces or  to add new line feed

This doesn't make sense to me.
Can you make it work normally?

We can use 2 trailing empty spaces or  to add new line feed

This doesn't make sense to me.
Can you make it work normally?

we could make it work normally but we need to render the children on the whole instead of doing children.props.children. Since the children.props.children is considered as a string and not a react element new line is not added 🙁 .
I was trying to look around to add empty spaces in markdowns and found this
https://www.markdownguide.org/basic-syntax/

How does this work inside triple back tick (code blocks)? Terminal blocks should be treated similarly.

Does setting whiteSpace: 'pre' in the style fix it?

Adding whitespace-pre fixed the issue 👀 . I've added that to the terminal block now. Thanks.

Thx!


The error in hooks.server.js still reports the wrong location.

Describe the bug
I've been suffering from incorrect error locations for a long time and was very excited about #10769 and version 1.25.1.
However, it seems to be about server rendering and some IDE, and not related to errors in code executed in hooks.server.js.
Even in a stackblitz environment, the phenomenon is well reproduced. In the project I linked there is only a 2 line difference, but it is not consistent at all. Sometimes it is smaller than it actually is, but most of the time they report a larger number.
I keep the asynchronous infinite loop executed in hooks.server.js residing on the server like a daemon. And the values calculated by the infinite loop are frequently referenced and output by several pages of svelte. I don't think this is an overly unusual structure.
In that infinite loop, errors will occur frequently, and I want to quickly find their location. Currently I am having a very hard time.
Since I'm having a really hard time, I'd like to know at least a temporary solution.
For example, in #10769, I checked the following link: https://github.com/sveltejs/kit/blob/master/packages/kit/src/runtime/server/utils.js#L98
I found this to be of great help in making this temporary fix. I hope there is something similar for my case. I am not skilled enough to find it myself. Please help me.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-wsaice?file=jsconfig.json
hooks.server.js:
console.log('run: hooks.server.js (line 1)');

setTimeout(() => {
	// Dummy code to place the error location in the middle of the file.  (line 4)

	console.log('error soon  (line 6)');
}, 3000);

setTimeout(() => {
	console.log('<--- line number 10', new Error().stack);
	throw new Error('<---- line number 11');
}, 4000);

setTimeout(() => {
	console.log('dummy'); //(line 15)

	console.log('dummy'); //(line 17)

	console.log('dummy'); //(line 19)
}, 10000);

package.json:
"@sveltejs/kit": "1.25.1"

Logs
run: hooks.server.js (line 1)
page option:  { prerender: false, ssr: false }
error soon  (line 6)
<--- line number 10 Error
    at Timeout.eval (/home/projects/sveltejs-kit-template-default-wsaice/src/hooks.server.js:12:37)
    at listOnTimeout (node:internal/timers:62:4448)
    at processTimers (node:internal/timers:62:5285)
    at <anonymous> (https://sveltejskittemplatedefaultwsai-dctb.w-credentialless.staticblitz.com/blitz.d6c42aca.js:334:292836)
    at <anonymous> (https://sveltejskittemplatedefaultwsai-dctb.w-credentialless.staticblitz.com/blitz.d6c42aca.js:334:293145)
Error: <---- line number 11
    at Timeout.eval (/home/projects/sveltejs-kit-template-default-wsaice/src/hooks.server.js:13:8)
    at listOnTimeout (node:internal/timers:62:4448)
    at processTimers (node:internal/timers:62:5285)
    at <anonymous> (https://sveltejskittemplatedefaultwsai-dctb.w-credentialless.staticblitz.com/blitz.d6c42aca.js:334:292836)
    at <anonymous> (https://sveltejskittemplatedefaultwsai-dctb.w-credentialless.staticblitz.com/blitz.d6c42aca.js:334:293145)

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
    pnpm: 8.6.10 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^2.0.0 => 2.1.0
    @sveltejs/kit: 1.25.1 => 1.25.1
    svelte: ^4.0.5 => 4.2.0
    vite: ^4.4.2 => 4.4.9

Severity
annoyance
Additional Information
No response

@lzdetourer Is this specific to using setTimeout? If so there's not much really do for that or any other asynchronous errors since those can't be intercepted by SvelteKit or Vite.
The errors need to be caught by the framework somehow to fix the stack and that can't happen if they're thrown asynchronously without being awaited.

@lzdetourer Is this specific to using setTimeout? If so there's not much really do for that or any other asynchronous errors since those can't be intercepted by SvelteKit or Vite.
The errors need to be caught by the framework somehow to fix the stack and that can't happen if they're thrown asynchronously without being awaited.

It is used in setTimeout and async/await infinite loop.
But since it's so painful to me, I don't mind changing the method as long as I can find the location of the error. For example, it is enough to know the exact location of the Error object generated in the try-catch statement inside async.

Does anyone have any opinions regarding this?
In fact, I visit this page every time I get tired of looking for the error location. 😁
It helps a little to keep me sane.

I came in again. Because I just went through a lot of trouble trying to find the error location. I hope this gets resolved someday.


Suggestion to optimize identification

Watson visual recognition has a built in food classifier, we could make a call to that before going to our built one and if it comes back with decent confidence then we can assume it's food that should go to a landfill.

Food goes to compost :)

derp


Update package.json to include the repository key

With the rise in supply chain attacks and OSS dependencies being used as a attack vector, Microsoft is working with our ecosystem partners, such as the Linux Foundation's OpenSSF, to enable OSS consumers to track packages back to their public sources.
We've identified that the following packages published to NPM do not report where sources can be found, typically accomplished by including a link to your GitHub repository in your package.json REPOSITORY field. This PR was created to add this value, ensuring future releases will include this provenance information.
Published NPM packages with repository information:

sp-client-custom-fields

Is there anything that is needed to land this pull request ?

ls there anything else I can do to land this pull request ?

Is there anything that is needed to land this pull request?


Debug not working with NYTProf active

Error Could not connect to debugger, connection closed was reported in the debug console.
Steps to reproduce:
OS: Windows10 64bit
Dist: ActiveState Perl v5.24.1 (MSWin32-x86-multi-thread-64int)
Environment: PERL5OPT=-d:NYTProf
Deleting the environment variable fixed the issue.

@mihaipopescu thanks for reporting, I'm curious if the debugger should overwrite the PERL5OPT?
(Allowing the user to set options in the vs settings instead)

@mihaipopescu this should be fixed in v0.2.1 PERL5OPT are no longer passed on pr. default - need to set environment variables in settings.
Let me know if it's not working

I'll check. Thanks @raix.


chore: add tests for quarkusio/quarkus#4408

tests for https://github.com/quarkusio/quarkus/issues/4408

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/294/


Endpoint Handler Behaviour

allow (per scheme) configuration of an Endpoint Handler
to be passed as childspec to Phoenix.Endpoint.Server supervisor

defaults to Phoenix.Endpoint.CowboyHandler

will be moved to phoenix framework repo


Rename SymbolizeResult type

Please see individual commits for descriptions.

Unfortunately that is a breaking change and will cause a bit of pain, but I believe it's the right step. Landing...


Use pyright for static type checking of implemenation code

mypy can not and will not get functionality to be able to type check files that have both implemenation and type stubs (both .py and .pyi files). Pyright does seem to support it, so this adds it to the CI pipeline for checking implemenations.
This only adds functions.py to the whitelist of files to test, since it's quite an undertaking to fix all of the client code at once. Once we have fixes for all files we can let pyright traverse the entire repo instead of using this whitelist.
If I understand things correctly, pyright is also what's used as the python language server by vscode, so getting rid of type warnings for vscode devs is another benefit.
Initial batch of fixes for: #1372 and MOD-2387

Yeah it's not very pretty. Perhaps we can refactor the code at some point to make a few of the "connected" types like client have a separate type for their connected/initialized version and unconnected versions, and then make sure all "active" wrappers like FunctionCall only contain non-optional references to the connected versions, which would get rid of some of the assertions.
But this should at least not lead to any errors that weren't previously errors further down the call stack :)

@freider Interesting, I didn't realize pyright reviews both .py and .pyi files. I still don't have a good feel for what error it raises so I'll play around with it a bit more.
One thought - modal.functions is a bit further down the dependency tree, might be easier to start off at the top like in https://github.com/modal-labs/modal-client/pull/1374.

@prbot approve


Flow control analysis is not performed on discriminatable types flowed from a type guard

TypeScript Version:  2.4.0 / nightly (2.5.0-dev.201xxxxx)
Code
enum Kind {
    A,
    B,
}

interface Base {
    kind: Kind
}

interface A extends Base {
    kind: Kind.A;
    yar: any;
}

interface B extends Base {
    kind: Kind.B;
    gar: any;
}

type Both = A | B;
function isBoth(x: Base): x is Both {
    return true;
}

let foo: Base = undefined;
if (isBoth(foo)) {
    switch (foo.kind) {
        case Kind.A:
            foo; // <-- type of foo here
    }
}

Expected behavior:
foo to be of type A at the indicated line.
Actual behavior:
foo is of type Both.

IIUC, the type of foo inside the typeguard is effectively treated as Base&(A|B).

Likely same root cause as #13176.


Enable replication, sql agent, etc.

Is the above possible? Can the Linux version of sql server do replication or run agent jobs? If so how?

The SQL Server Agent will be included in the mid-Feb or mid-March release.

Awesome. I will look for it then.

Will transactional replication also be supported?

(I'd edit my comments if it would let me on mobile) I'd like to suggest support for both the SQL agent and transactional replication (merge would be nice too) on the windows container as well.

Gave a presentation on running sql on Linux and the only things that are holding us back is full replication support and sql agent jobs (although we could get around that pretty easily with SQLCMD pointing to the containerized instance.

Sql agent comes in march or so but is there a target month for replication (as a publisher)?

Agent should come next week, barring any last minute show stopper issues.  We will work on all aspects of replication for next month's release and see how far we can get.

Awesome! Much appreciated. I continue to watch the project very closely and be an advocate for its use at work. Good luck and thanks for the update.

Saw the announcement of HA for the Linux sql containers, and that the developer sku came back for the windows side, is replication on track for the Linux sql containers?

Yes, Always On Availability Groups was released for SQL Server on Linux in CTP 1.3 on Feb 17.  That covers installs on RHEL, SLES, and Ubuntu, but not in containers just yet.  There is a dependency on Pacemaker.  We are working with Red Hat to figure out the best way forward for providing HA in containers.  There are several different options ranging from using Pacemaker in the container to leveraging Kubernetes services like Stateful Sets.
Yes, the Developer SKU is available on Windows containers again now.  Sorry for the delay on getting that out there again.  We had some internal wrangling about that to sort out.
You can get it here now:
https://hub.docker.com/r/microsoft/mssql-server-windows-developer
We were tracking having the SQL Server agent released in the 1.3 release but it didnt quite make it.  We are shooting for the 1.4 release in mid-March now.  That is a prerequisite for replication to be fully operational on Linux.
Stay tuned!

@twright-msft thank you for the transparency. And good luck with 1.4 and replication!
This might be outside of the scope of this particular issue but I was curious as to why the linux docker implementation of SQLServer is so much smaller than the docker images for SQLServer but on windows? Is there a paper or some resource I could read?

The reason that the SQL Server on Linux image is so much smaller is because it is the engine only.  It doesnt currently include agent, full text search, the clustering pieces required for WSFC, localization packs, etc.
The current version of the Windows containers for SQL Server simply downloads and installs SQL Server as part of the docker build.  In the future, we will likely create a similarly optimized SQL Server image for SQL on Windows.

That makes sense. Thanks for the insight.

Maybe a bit off topic too but any plans to run SQL Server Containers on Nano base image? Just curious as windowsservercore is over 4 GB. Also, SQL Server Agent on the Windows container still not released?

@richmurph - It's something we are considering but no concrete plans yet for Nano-based image.  Quite a bit of testing required for that and we would need to change the way the image is created.  It would need to be a "ADD" approach as opposed to a RUN that executes the .exe.  Nano doesnt support MSI.
Agent is on the list of things to look into as well, but for now, sorry, it's not working.
Crawl, walk, run...

Hey @twright-msft, is there any update on the addition of SQL Server Agent to the Docker image? The last mention above indicated March; is there any more recent estimate of its availability? Thanks!

I am also looking for being able to run sql agent to try some change data capture feature. Is there any update on the availability?

Current thinking is that we would just have a base image - mssql-server-linux.  People can then create their own images that add the combination of additional packages they require - i.e. agent +fts, fts+ha, integration services + agent, etc.  There will be several different packages so creating images that cover all the combinatorial of them all seems like overkill.  Please let us know what you all think about that....

That works for me. Just throw up a guide on how to do it and I'll give it a shot. I liked the idea of a modular system

I detailed guide on how to do it will be helpful

Useful article here on how to do this guys. Simply installing the required features within a windows server core base image and then building a container image from completed build. http://searchsqlserver.techtarget.com/tip/Use-these-commands-to-deploy-SQL-Server-Docker-containers

Is there a way install the full-text search?  I'd really like to be able to experiment with this feature.

@thorntonrp - two options: 1) build your own image with FTS in it using the Dockerfile at the link here.  2) SSH into the container and install mssql-server-fts

Does this image support R service (in-database)? I tried to follow the instruction here: https://docs.microsoft.com/en-us/sql/advanced-analytics/tutorials/rtsql-working-with-inputs-and-outputs, but kept getting the following error: "SQL Server was unable to communicate with the LaunchPad service. Please verify the configuration of the service. "

Neither the Windows- nor the Linux-based image have support for running R/Python in them yet.

I have had this same issue.  I think, but am not certain, that it is because I have SQL2016/SMSS installed on my host machine.  I run trhe same container on a different machine w/o SqlServer/SSMS on it and do not encounter the error.  Also, I have not gotten it when I stop the SQLServer service on my host machine.

Has there been an official guide published on installing SQL Agent in the standard SQL Server - Linux docker image?
Following guides from blogs and now I'm getting Error: The evaluation period has expired     and the container does not start.

@hartman17  - Please use the latest Dockerfile here:
https://github.com/Microsoft/mssql-docker/blob/master/linux/preview/examples/mssql-agent-fts-ha-tools/Dockerfile

Hi @twright-msft , thanks for your answers. I did use your dockerfile ( https://github.com/Microsoft/mssql-docker/blob/master/linux/preview/examples/mssql-agent-fts-ha-tools/Dockerfile ) but even though the SQL Agent is displayed, I can't enable it, here's how it looks:

Any ideas?

On Linux, you also need to enable the Agent using this env var:
MSSQL_AGENT_ENABLED=true
https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-configure-environment-variables?view=sql-server-2017#environment-variables

Hello, I have the same problem the sqlmanage starts but I am not able to give start

##the same problem as here:
https://github.com/Microsoft/mssql-docker/issues/27#issuecomment-427774480
##docker-compose
version: "3.7"
services:
  sqlserver:
    image: sql-server
    build: ./Sqlserver
    container_name: sql-server
    hostname: Sqlserver
    ports:
    - "1433:1433"
    tty: true
    environment:
    - 'ACCEPT_EULA=Y'
    - 'SA_PASSWORD=1234PW!'
    - 'MSSQL_AGENT_ENABLED=true'
    - 'MSSQL_PID=Standard

I'm running into this very issue with Azure Container Instances AND local Docker containers.  The strange thing is that I have one container, C1, where I use 'MSSQL_AGENT_ENABLED=true' and the agent starts and works correctly.  I deployed a second container, C2, in the exact same way, using the same image, and also setting 'MSSQL_AGENT_ENABLED=true'.  C2 shows SQL Server Agent as disabled.  Any ideas as to why this is happening?  This is very frustrating.

Has anyone gotten this going?  I've tried getting this going but I keep getting this error.

Replication doesn't exist for SQL Server 2017 Linux. This is being introduced for SQL Server 2019.

@sschwenker - you will need the SQL Server 2019 container image. Try this using this container image mcr.microsoft.com/mssql/server:2019-CTP3.1-ubuntu
Also here are examples to get SQL Server Replication in Containers up and running.
https://github.com/microsoft/sql-server-samples/tree/master/samples/containers/replication
https://dbafromthecold.com/2018/12/13/setting-up-sql-server-replication-in-containers/

Is there an official docker image for SQL Server 2019-CTP with SQL Server Agent enabled?

try this:
sudo docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=<YourStrong!Passw0rd>' \
   -e 'MSSQL_AGENT_ENABLED=true' \
   -p 1433:1433 --name sql1 \
   -d mcr.microsoft.com/mssql/server:2017-latest

@vin-yu I'm running this as a container in AKS. So do I have to create another docker image and use that?

@susanthab No, just add an environment variable 'MSSQL_AGENT_ENABLED=true' when you start the SQL Server pod definition/yaml and SQL Server Agent should be started.

Fantastic! Thanks @vin-yu

sqlserver 2019 Red Hat images
Is it possible to publish and subscribe?
Collaboration with technical staff (Microsoft) but not effective progress

sqlserver 2019 Red Hat images
Is it possible to publish and subscribe?
Collaboration with technical staff (Microsoft) but not effective progress

You can retrieve the list of RHEL published images through command line, here are a few examples:
Using bash:
curl -L https://mcr.microsoft.com/v2/mssql/rhel/server/tags/list/

Using PoSh:
$rhel_response = Invoke-WebRequest -URI https://mcr.microsoft.com/v2/mssql/rhel/server/tags/list/
$rhel_response.content

You can also check the Red Hat Container registry here.


Fix mismatch between schema builder and connection

In CrudPanel::getSchema() the use of Schema::setConnection() would properly set the connection but would not return the correct schema builder instance, using the correct grammar class for the DB driver.
This created some conflicts with SQL Server usage that uses a slightly different syntax than MySQL.
By using built in method-chaining, we are able to return the correct schema builder.
See comment https://github.com/Laravel-Backpack/CRUD/issues/1797#issuecomment-547528146 for detailed explanation .
Resolves #1797

This is excellent! Thank you @brianjohnhanna - this makes total sense. And it looks cleaner too 😄
I've just merged this into master, it'll be available with composer update later today as 4.0.29. Sorry for taking so long to merge this.
Cheers!


Coverage regressions on 3.10.rc1

See up to date codecov status and the build artifact.  Coveragepy at 57a691f.
I'll select some cases (codecov shows more regressions, but only ones in the power.py and rde.py seems to be in the build artifact, perhaps it's a codecov issue).

L1032, L1037 of power.py: no jumps to exit.  These lines could be covered, for example, by: exp(Symbol('', real=True, transcendental=True)).is_algebraic and exp(Symbol('', integer=True)).is_algebraic.
L309 of rde.py and similar lines with the DecrementLevel context manager.  These can be triggered by tests in the diofant/tests/integrals/test_rde.py.

PS: You can see more "green" lines counted in the codecov statistics.  Maybe it's a codecov issue.  I've reopened the pr request as https://github.com/diofant/diofant/pull/1162 to see if this and mentioned above disagreement with the codecov.xml in the build artifact will disappear.

Please provide specific instructions about how I can reproduce the problem.  Specific commits of your repo to clone, commands to run, and specific lines that you believe are incorrectly measured.

I though I did this...
Ok, next try.  You can use diofant/diofant#1162, last commit (c59bd75).

L1032 and L1037 of the diofant/core/power.py are not covered (no jumps to exit).  This should be covered by tests:

exp(Symbol('', integer=True)).is_algebraic  # L1032
exp(Symbol('', real=True, transcendental=True)).is_algebraic  # L1037

In principle, pytest --cov diofant -m 'not slow' diofant/tests/core should also cover these lines.

L309 of the diofant/integrals/rde.py (and similar lines with the DecrementLevel context manager).  I'm unsure, maybe it's not a bug, but this line was marked as covered on the master, see the codecov output.  Now coveragepy report "line 309 didn't except from function 'bound_degree', because the raise on line 320 wasn't executed or the raise on line 342 wasn't executed"  (pytest --cov diofant -m 'not slow' diofant/tests/integrals/test_rde.py should trigger all tests for the bound_degree() function).

FYI: here is the codecov bugreport

I've reported the L1032 issue against CPython: https://bugs.python.org/issue44840

For the L309 issue, I see this in my coverage results:

It has executed line 336, but then neither line 339 or line 341.  That makes it seem like some other exception was raised at line 336, which could explain why the context manager on line 309 never jumped to 371.  Can you confirm this theory?

Hmm, I did pytest -m 'not slow and not xfail and not regression' diofant/tests/integrals/.  It seems, L344 (exit from with) has hit from the test_integration() of diofant/tests/integrals/test_integrals.py.

@skirpichev I'm sorry, I don't understand what your last comment means.
I tried adding another except clause. It shows that line 336 is raising an uncaught exception:

So I think the L309 issue is not a regression.

I don't understand what your last comment means.

Well, perhaps I misunderstood you, but it seems your guess was that the only exit from the with clause was by an exception (from L336).  That's not true.  E.g. you can replace L344 with print(111) (i.e. right after "with" statement) and run pytest -q -n0 -s diofant/tests/integrals/test_integrals.py -k test_integration - you will see some hits.  Or run in console from diofant import *; integrate(exp(-log(x)**2)).

So I think the L309 issue is not a regression.

Clearly, there is an exit by an uncaught exception AND a normal exit.
I'll try to reduce this example, of course.

PS: You can see more "green" lines counted in the codecov statistics. Maybe it's a codecov issue.

Regarding this, it seems to be a coveragepy "feature".  Indeed, some new lines are counted.  For instance, L1489 of rings.py, which is "while True" statement.

I'll try to reduce this example, of course.

Another example is in the cancel_primitive():

coverage.xml:
<line number="546" hits="1" branch="true" condition-coverage="66% (2/3)" missing-branches="exit"/>
IIUC, three branches are: normal exit from "with", an uncaught exception from some function inside of "with" and the NotImplementedError on L552?
Probably, you were right, this is not an issue.  On another hand, in this example we have only a NotImplementedError, which is ignored by my config.  Shouldn't then this branch be ignored by the coveragepy (like for if/else blocks)?
At least, the coveragepy behaviour was changed significantly, could be this documented?

FYI, unless I miss something, 1st issue wasn't solved in cpython:

Coveragepy at 57a691f.  I've tested this issue on the recent 3.10 head, which has backport from your issue:
$ python
Python 3.10.0rc1+ (heads/3.10:d5c8ad2471, Aug  9 2021, 15:31:13) [GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.

@skirpichev I really appreciate your dedication to finding these problems, but please please please please please PLEASE always include the steps you used to produce the results you are showing.
And can you say specifically what about that output is incorrect?
This is what I did (with output showing versions):
$ mktmpenv -p /usr/local/cpython/bin/python3 -n
$ python -VV
Python 3.10.0rc1+ (heads/3.10:d5c8ad2471, Aug  9 2021, 10:24:02) [Clang 12.0.0 (clang-1<IP_ADDRESS>)]
$ cd diofant
$ git log --oneline | head -1
c59bd753e XXX removed all workarounds for issue2506 & skipif ground types != gmpy
$ pip install -e '.[develop,docs,tests]'
$ pip install git+https://github.com/nedbat/coveragepy@57a691f15dc8296f91ec1e321d3ed53e165a1f10
$ pytest --cov diofant -m 'not slow' diofant/tests/core

My HTML report looks like this:

We seem to be running different tests.

include the steps you used to produce the results you are showing

Sorry, I thought I did it before.

And can you say specifically what about that output is incorrect?

Exactly same as in the issue description, 1st point.

We seem to be running different tests.

I see no difference for L1032 and L1037.
The source of discrepancy seems to be that I did tests with -m 'not slow and not xfail and not regression' instead.  That's not an important thing: mentioned before steps should cover exit's from L1032 and L1037.  (On the current https://github.com/diofant/diofant/pull/1162 you can run pytest -k test_Pow_is_algebraic --cov diofant diofant/tests/core/test_assumptions.py to trigger these exits.)

I mistakenly skipped the step of generating the HTML report after running the tests.  When I re-do the HTML report, I get this:

Unfortunately, I run this step.  Are you sure you didn't run tests on CPython 3.9 or more older?
I've tested by pytest -k test_Pow_is_algebraic --cov diofant diofant/tests/core/test_assumptions.py  && coverage html on the current https://github.com/diofant/diofant/pull/1162 (merge commit: https://github.com/diofant/diofant/pull/1162/commits/e62cf84aee0110e8719e1e273f0019d8cb6df230).  Both for 3.9 and 3.10 CPython (heads/3.10:d5c8ad2471).  I still see uncovered exits on L1032 and L1037, as it shown before.
Probably, this is my fault, but I've no glue on what can be wrong on my side.

After adding "pass" statements I see this:

for latest CPython 3.10:
$ python
Python 3.10.0rc1+ (heads/3.10:a3185da26f, Aug 10 2021, 06:42:46) [GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>

and
pytest -k test_Pow_is_algebraic --cov diofant diofant/tests/core/test_assumptions.py && coverage html

PS: coveragepy version as before.

Are you in a virtualenv?  The python command may be finding the latest Python 3.10, but the pytest command may be finding a different python.   Try using python -m pytest instead.

Are you in a virtualenv?

No, I use venv.

Try using python -m pytest instead.

No, both pytest & python -m pytest - report same version.
It seems, git clean -Xdf did the trick.  I guess, some old *.pyc files were used.
Thank you very much for help!  1st issue is solved.
What about the second one?  I think, the original example may be a non-issue (or a documentation issue), but another one (with a NotImplementedError, which should be ignored) - is.

@skirpichev I am going to close this issue as solved for #1.  Please open a new issue for #2, with specific instructions about the tests you ran to get the output you saw, and specific details about exactly what you think is wrong.  I tried running tests to reproduce #2, and got a completely different result than you showed.
Again, I really appreciate your persistence, but we have to get a smoother flow here with reproducible instructions.  Assume I know nothing. Give me exact commands to run.  Thanks.

This is now released as part of coverage 6.0.


Option -h does not list itself

Option -h (help) does not list itself as option, i.e.
$ asciidoctor-web-pdf -h 2>&1 | fgrep -- -h
  --no-header-footer, -s  suppress enclosing document structure and output an embedded document  [boolean]

Upstream issue: https://github.com/asciidoctor/asciidoctor-cli.js/issues/149

With @asciidoctor/core 3.5.0:
$ asciidoctor-web-pdf -h 2>&1 | fgrep -- --help
      --help              print a help message


Revert "Stick to containerd 1.7 environment"

Reverts kubernetes-sigs/provider-aws-test-infra#382
with https://github.com/kubernetes-sigs/provider-aws-test-infra/pull/385 and the PRs linked from there, we should be all set to go back to main

/assign @hakuna-matatah

/lgtm


[WIP]Add klayout container.

WIP as it currently uses https://github.com/hdl/smoke-tests/pull/5 which has not been merged yet.

@Fatsie, shall I review this PR?

@Fatsie, shall I review this PR?

I plan to update it to non WIP in coming days, so you can wait til then. Just busy with other things ATM.

Pushed new (squashed) commit for review. klayout smoke test is still commented out.
Removed WIP flag.

I discovered that smoke test could be run without X using the -b option. See https://github.com/hdl/smoke-tests/pull/6
I'll update this PR after that PR is merged.

I'll update this PR after that PR is merged.

Force pushed update with some-tests enabled.

Thanks!


docs for auth query param

Codecov Report
Base: 66.10% // Head: 66.10% // No change to project coverage :thumbsup:

Coverage data is based on head (ca5ec53) compared to base (cbc912d).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #433   +/-   ##
=======================================
  Coverage   66.10%   66.10%
=======================================
  Files          35       35
  Lines        3720     3720
=======================================
  Hits         2459     2459
  Misses        908      908
  Partials      353      353

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Should this mention that this is also applicable for subscribing to an authenticated topic via websockets?

Thank you. I'll modify it a bit, but this looks great!


jPtr operation does not throw

What is the issue you have?

When I use jptr like below( it is a bad request), I can't catch any throw. Is there any problem on my operation or Is this a bug?
 try
 {
     // try to use the array index '-'
     json::reference ref = j.at("/array"_json_pointer);
 } catch (json::out_of_range& e)
   {
     std::cout << e.what() << '\n';
   } catch (json::out_of_range& e) {
     std::cout << e.what() << '\n';
   }

Thanks a lot

Can you provide a working sample that this bug could be reproduced?
Also, in addition to json::out_of_range,  you might try other exception types, or base json::exception or even std::exception types, to see whether some other exception is being thrown.

of course,
i will try your propose
here is my sample
    nlohmann::json val;
    json::json_pointer jsonPtr("/services/2/serviceName");
    try {
        val =  (std::string)j.at(jsonPtr);
    } catch (json::parse_error& e) {
        val = 0;
    } catch (json::out_of_range& e)
    {
        val = 0;
    }

There was a typo in the sample code. I've cleaned up a bit:
#include "json.hpp"
#include <iostream>

using namespace std;
using namespace nlohmann;

void check()
{
    nlohmann::json val;

    json::json_pointer jsonPtr("/services/2/serviceName");
    try
    {
        cout << "Checking..." << endl;
        val =  (std::string)val.at(jsonPtr);
        cout << "no exception." << endl;
    }
    catch (json::parse_error& e)
    {
        val = 0;
        cout << "thrown parse_error: " << e.what() << endl;
    }
    catch (json::out_of_range& e)
    {
        val = 0;
        cout << "thrown out_of_range: " << e.what() << endl;
    }
    catch (std::exception& e)
    {
        val = 0;
        cout << "thrown unknown exception: " << e.what() << endl;
    }
}

int main(void)
{
    check();
    cout << "Done." << endl;
    return 0;
}

This outputs
Checking...
thrown out_of_range: [json.exception.out_of_range.404] unresolved reference token 'services'
Done.

which is expected (tested on version 3.6.1).

By the way, I try something like that;
what if wrong path was came from like "services" (it should be "services/2/serviceName"). I know it is wrong request but I assume that client side sent it.
json::json_pointer jsonPtr("/services");
Then, I tried to catch it with json::exception and it works.
Thanks a lot.


UX Study Discussion #4: Accessing Progress

One participant was surprised that progress in transfer(_:didUpdateWIthState:andProgress:) was optional. The reason is that sometimes progress information is irrelevant, such as when a transfer is canceled or deleted. Options include:

document and do nothing else
create specific delegate methods/callbacks for those states that wouldn’t care about progress and make progress non-optional
possibly make progress a property of the .inProgress enum state, thus removing it from the argument list.

Per discussion, we agreed that these mechanisms are sufficient since progress is no longer optional. Closing.


Operator tutorial outdated

The killercoda Operator tutorial is outdated and broken. Thanks @salaboy who made me realise this.

Helm chart is now open-feature/open-feature-operator not open-feature/ofo
Need kubectl create namespace open-feature-demo
kubectl apply end-to-end.yaml needs a namespace added
Need to create a standlone featureflagconfiguration for two reasons: 1) It makes editing more logical. 2) kubectl applying end-to-end fails as it contains the service which is already bound to port 30000.
Move the port-forwarding to a nohup operation in the creation script

In short, this issue will fix the OpenFeature operator Killercoda tutorial and bring it up to date.

Re-opening until #10 is merged.

This is now resolved.


Notes on core.py

self_managed seems like a useful attribute. It’s not mentioned anywhere else in the package, but this implementation seems reasonable and maybe it works?
https://github.com/chriskiehl/re-wx/blob/882967e5cbe14a2b65f45b5cfccea3cccdb293f4/rewx/core.py#L86
component_will_unmount is never called anywhere, so this feature is not yet implemented.
https://github.com/chriskiehl/re-wx/blob/882967e5cbe14a2b65f45b5cfccea3cccdb293f4/rewx/core.py#L195
This re-wx package seems like the best cross-platform native GUI Python package on the internet. Or anyway, the least insane. Everything else is either web-based (Streamlit), or 20th-century object-oriented trash (QT for Python), or looks so horrible that you can’t distribute it to any users. (DearPyGUI).
But the Alpha Note on the README is not just false modesty. This package really is not yet reliable. Is there any possibility that you will resume your interest in this project @chriskiehl ? I would like to work on improvement to re-wx but my Python is bad and I don’t understand the code for re-wx as well as you.  What are your thoughts on the future of this package?

There is also https://github.com/fding/pyedifice , which is in about the same partially-finished condition as re-wx.
When I research “declarative” “Elm architecture” “virtual DOM” native GUIs for Python I see a lot of agreement that this should exist, but no-one has yet accomplished it. I think the re-wx approach is the most promising.

updatewx appears to be some kind of hack for native components, but it’s not called from anywhere?
https://github.com/chriskiehl/re-wx/blob/882967e5cbe14a2b65f45b5cfccea3cccdb293f4/rewx/core.py#L47

Howdy!
Glad to hear you've gotten some use out of the project! Dragging Python into the declarative world was indeed the initial goal of the project. I still think there's a pretty good niche that could be carved out here. However, the best it'll ever be is a niche. It's not going to compete with, say, Electron. The demand for the type of program built from native widgets in 2022 seems vanishingly small.
When initially written, my grand plans for the framework involved creating a serious competitor in the Python GUI landscape. However, there wasn't as much demand as I thought, and open source doesn't pay the bills, so the future of this project is now scoped to mostly just being "good enough" to support my needs while developing Gooey. It'll receive maintenance updates as needed for that use case.
Cheers!

Thanks for the note @chriskiehl , and thanks for all the work you’ve done on re-wx.
Gooey is a very nice project, and it has 16K stars, and I see that it depends on re-wx, which is nice to know, because that reassures me that re-wx will not be completely neglected.
I'm going to keep trying to use re-wx, and I'll submit PRs as much as possible.

( Love this blog post https://chriskiehl.com/article/webscraping-on-hard-mode )

Here's an example of a self_managed component: https://github.com/chriskiehl/Gooey/blob/be4b11b8f27f500e7326711641755ad44576d408/gooey/gui/components/config.py#L15


Fix #302: Support escaped forward slashes

This provides better compatibility with JSON, and is what Vibe.d does by default:
https://github.com/vibe-d/vibe.d/blob/7604eea772b1a733f7bfd16591ddc5bd37850bd9/data/vibe/data/json.d#L2555-L2563

You could avoid adding a new test module by just writing a .data and .canonical file pair

You could avoid adding a new test module by just writing a .data and .canonical file pair

Not a big fan of those to be honest, they are very non-obvious.

You could avoid adding a new test module by just writing a .data and .canonical file pair

Not a big fan of those to be honest, they are very non-obvious.

I'm not a big fan of adding even more modules solely for running tests, either.

I can move the UT to an existing module, I just didn't find one that was suitable. Where should it go ?

dyaml/escapes.d, of course. It's the only module you've changed

Updated


[docs] Add XCM / XCMP article

Add an article for parachain builders. Work in progress.

Add info on using public good parachains.
Tracking:

[ ] https://github.com/paritytech/cumulus/issues/908

any estimations on when will this be available?

I think the best we can do is have a page that explains basic XCM principles and how to use them, and link to all other current resources on XCM. For more advanced things, we could maintain a Q&A list - what do you think @NukeManDan @shawntabrizi ?

stub is included in #1140 , still at this time not in a place I would consider user facing

this Audit Report on XCMv2 could be a really good reference for XCM documentation.


Expose Git commit hash in Rollbar

When investigating a previous error in Rollbar, I wanted to know which
version of the code was running when the error occurred. We can achieve
this by setting Rollbar’s config.code_version.
I think it makes sense to bake the Git commit hash into the Docker
image, since it provides metadata about which code is contained inside
the image and the context in which the image was built. I’ve put the
ENV instruction below the COPY instructions for caching reasons, since
the commit hash changes more frequently than the copied files.
I haven’t found a way to test this end to end. I’ve confirmed that the
web image built by CI, which gets pushed to Docker Hub, contains the
GIT_COMMIT_HASH environment variable, but I don't know if there's an
easy way to actually test that the exceptions triggered end up tagged
properly in Rollbar.

I'd welcome opinions on whether we need to test this end-to-end.

One way we could test this is in test - tag and push a Docker image and then deploy to test (we'd need to change the DOCKER_IMAGE_TAG in the deploy script). We can then raise an error manually and confirm it shows up in Rollbar.

Ah, cool, I'll give that a go. And I think I can trigger an error manually by running Rollbar.error in a console.

Tested it and updated the commit message.


Net::ReadTimeout

I just got alert from bugsnag:
Net::ReadTimeout/usr/lib/ruby/2.3.0/net/protocol.rb:158

/usr/lib/ruby/2.3.0/net/protocol.rb:158rbuf_fill
/usr/lib/ruby/2.3.0/net/protocol.rb:106read
/usr/lib/ruby/2.3.0/net/http/response.rb:291block in read_body_0
/usr/lib/ruby/2.3.0/net/http/response.rb:276inflater
/usr/lib/ruby/2.3.0/net/http/response.rb:281read_body_0
/usr/lib/ruby/2.3.0/net/http/response.rb:202read_body
gems/down-4.0.1/lib/down/chunked_io.rb:154each
gems/down-4.0.1/lib/down/chunked_io.rb:154block in chunks_fiber

Looks like Down didn't intercept Net::HTTP's Net::ReadTimeout exception.
I rescue only Down::Error and hope Down will intercept its dependencies' exceptions.
In my code I use Down.open.

@mvasin Can you show me the full stack trace of the error? Does it by any chance originate from lib/down/net_http.rb:175?

It's an IoT project, and currently logs accumulation is limited: I have only last 40 minutes of logs accessible (that's how resin.io works), and now log records regarding the error are gone; I had the error just once, today early in the morning.
The fact that the bugsnag's log stack does not include my app code is also a little weird.

@mvasin Ok, no problem actually, I know two possible places where this could happen (I just checked the Net::HTTP source code), so I'll just make fixes for both places.

Salut, @janko-m!
Here's one more Net::HTTP exception creeping in:
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/net/http.rb:882:in `rescue in block in connect'
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/net/http.rb:879:in `block in connect'
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/timeout.rb:101:in `timeout'
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/net/http.rb:878:in `connect'
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/net/http.rb:863:in `do_start'
Errno::ENETUNREACH: /usr/lib/ruby/2.3.0/net/http.rb:852:in `start'
E, [2017-09-27T18:30:09.418214 #421] ERROR -- : Errno::ENETUNREACH: /var/lib/gems/2.3.0/gems/down-4.1.0/lib/down/net_http.rb:152:in `block in open'

It occurs when my IoT thing is offline.

@mvasin I've just released version 4.1.1 with the fix.


Fix: must take xlct into account while determine_rtt

Problem:
Client request with 0RTT paras may failed with timeout but not success with 1RTT.
Reproduce:

http_client launch 0rtt requests with -0 prog_0rtt.info, like
http_client -H test.com -s <IP_ADDRESS>:3333 -p / -o version=Q043 -n 1 -r 10 -R 1 -0 ./prog_0rtt.info
server update CERT
http_client launch 0rtt again
http_client failed with timeout but not success with 1RTT.

Analysis:
Lsquic ignore XLCT tag while parse_hs_data and not cmp XLCT with hash(enc_session->cert_ptr)

Thank you!  We will examine this shortly.

I understand what the patch does, but I am not able to reproduce the symptom where the client times out.  In Step (4) above, do you mean that one of the 0-RTT connections issues in Step (3) fails?
Which server are you using?

I am not able to reproduce the symptom where the client times out.

I can reproduce it now.


Choice of linear algebra library

We need a solution for linear algebra. There's a file "xr_linear.h" in the OpenXR SDK which we could use.
We can copy it directly into the project, that obviously separates it from its intended source, plus it's PDX-License-Identifier: Apache-2.0, and copyright Khronos and "Oculus VR LLC" i.e. Meta.
We could add a new minimal header-only lib, or we could use something like glm.

If possible I like using xr_linear.h as it has the right types already supported.


Added functionality for starring  of messages

Summary

Ticket Link

Related Pull Requests

Has server changes (please link here)
Has redux changes (please link here)
Has mobile changes (please link here)

Screenshots

Thanks @PratikmohanSrivastav for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.


Error: user .linuxbrew doesn't exist

Attempting to install neovim on Arch Linux and I get: Error: user .linuxbrew doesn't exist

Please post the exact command that you're attempting to run and the exact error message. You likely forgot the slash between ~/.linuxbrew. To avoid typos, copy and paste the instructions. See http://brew.sh/linuxbrew

Hi @sjackman
$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/linuxbrew/go/install)"
$ brew doctor
Error: user .linuxbrew doesn't exist
Please report this bug:
    https://github.com/Homebrew/linuxbrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting
/home/aidy/.linuxbrew/Library/Homebrew/utils.rb:203:in `expand_path'
/home/aidy/.linuxbrew/Library/Homebrew/utils.rb:203:in `block in which'
/home/aidy/.linuxbrew/Library/Homebrew/utils.rb:202:in `each'
/home/aidy/.linuxbrew/Library/Homebrew/utils.rb:202:in `which'
/home/aidy/.linuxbrew/Library/Homebrew/cmd/doctor.rb:1094:in `check_for_bad_python_symlink'
/home/aidy/.linuxbrew/Library/Homebrew/cmd/doctor.rb:1285:in `block in doctor'
/home/aidy/.linuxbrew/Library/Homebrew/cmd/doctor.rb:1283:in `each'
/home/aidy/.linuxbrew/Library/Homebrew/cmd/doctor.rb:1283:in `doctor'
/home/aidy/.linuxbrew/Library/brew.rb:135:in `<main>'

Put ~/.linuxbrew/bin at the beginning of the path and 'brew prune' to fix broken soft links.

Please report

Please report
echo $PATH

There's probably a tilde character in there that shouldn't be in there. Try
export PATH="$HOME/.linuxbrew/bin:$PATH"

Many thanks for your work and help. It looks like I had broken soft links.


[BUG] rich.text - Text.highlight_words() : highlights letters, not words

[ ] I've checked docs and closed issues for possible solutions.
[ ] I can't find my issue in the FAQ.

Describe the bug
Using the Text class, I try to highlight a specific word in the text using the highlight_words() function. The word does get highlighted, however all other letters that match any letter in the highlight word within the Text object get highlighted as well.

The fact both the function and keyword use "words" and not "letters" indicates to me this is a bug. I looked at the source code and I think I see the problem.
This line of the code treats keyword "words" as an iterable which it is, as a string.
re_words = "|".join(re.escape(word) for word in words)

It ends up splitting the keyword string like this:
'j|s|o|n'

I think it's just missing split on the end like this. That changes the iterable to a list of words.
re_words = "|".join(re.escape(word) for word in words.split(" "))

I made the change on my local text.py and get what I think should be the correct output. Works on 1 and 2 words with a space separating. I don't know if this would break any edge cases.

With that, the keyword string becomes this:
'json'

Or with a second word, 'json output', like this:
'json|output'

Platform

Click to expand
What platform (Win/Linux/Mac) are you running on? What terminal software are you using?
Linux OpenSuse Tumbleweed (2023-11-02) / Python 3.11.5 / Konsole 23.08.2 / rich 13.6.0

The signature for highlight_words says that it takes an argument of type words: Iterable[str].
This means you need to pass your words as, for example, a list:
text.highlight_words(["one", "two", "three"], style="blue")

In your original example, you should do:
j.highlight_words(["json"], style="blue")

Closing this issue - but feel free to let me know if you're still having trouble.


Corrupted Console

Bug Report
System Information

Debian GNU/Linux 9 (stretch)
v<IP_ADDRESS>, built 11/04/2019 13:12
Mainline

I confirm:

[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.

Symptoms
Players with special characters in their name do cause expression issues on the Instance Console.
E.g. there are 14 Players on the Server but only 2 are visible on Instance console
Reproduction
Add some special characters in the name like 浅い or ♫™
Attachments
This error is taken from the chrome console.

There corrupted instance console even without log view

Ingame players

I see what's happening, should be a straight forward fix.

This has been fixed in a nightly.

It seems like with v<IP_ADDRESS> there issue is still persists. Browser and CDN cache are cleared.


Battery Status Live Change

Hii Maintainers
-- Add a Feature Where Battery Icon Will change Based On the System Battery Status.

It is not supported for firefox

Yeah!
You are Right. The Battery Status API is not supported by firefox,safari.
But it will be a good feature.

Yeah!
You are Right. The Battery Status API is not supported by firefox,safari.
But it will be a good feature.

Ehhh, I don't think it is... 5/12 (41.66%) of browsers do not support it, so it will be useless for a lot this repos users, as seeing a lot of the issues are made from firefox users...

Chrome and edge support it. You can test it here https://pazguille.github.io/demo-battery-api/

https://developer.mozilla.org/en-US/docs/Web/API/Battery_Status_API#browser_compatibility

Chrome and edge support it. You can test it here pazguille.github.io/demo-battery-api

The last few issues I have either replied to, or seen, have been errors in Firefox, not Chrome or Edge. Firefox has issues with the blur effect, which is a major issue, adding this could cause some other issue that would make more work, than if not implemented.

True. Wonder if we could add an if statement based on the users browser.

True. Wonder if we could add an if statement based on the users browser.

That may work, I might test that later today.

we can add a if statement and check if the Battery API is supported or not by the browser.
In that way it will not affect other features.

Chrome and edge support it. You can test it here pazguille.github.io/demo-battery-api

The last few issues I have either replied to or seen, have been errors in Firefox, not Chrome or Edge. Firefox has issues with the blur effect, which is a major issue, adding this could cause some other issue that would make more work, than if not implemented. In fact, I will go tally up the past 25 issues in this repo that have a browser in the issue.

3/47 in this repo, mention Firefox, including one that I have made. That is a pretty big ratio, considering the number of stars and forks this has. That means out of 4.7k stargazers, 300 of them use Firefox. Also, out of 418 forks, 26 of them use Firefox. That's 6.4% of the users on just GitHub. I am not counting the users who don't use GitHub.

True. Wonder if we could add an if statement based on the users browser.

That may work, I might test that later today.

Aww, shoot... I totally forgot to work on it. My bad... :(

https://caniuse.com/battery-status according to caniuse it is supported 75%

https://caniuse.com/battery-status according to caniuse it is supported 75%

Thats percent of users, not browsers

True. Wonder if we could add an if statement based on the users browser.

That may work, I might test that later today.

And yes, I will work on this today ;)

I see a pull just opened #123

I see a pull just opened #123

I see it too


ZQS-359 Include contractor tests for estimators

FYI: This branch was originally created from the master branch so it contained some of Alex's release commits, the force push just now was to reset this branch to the condition of the dev branch prior to our commit :)


Changing pin does not work due to 4 digit placeholder

Description
When trying to reset connection settings or changing the pin in settings a 4 digit empty pin placeholder appears and connection settings can not be resetted / pin can not be changed
Expected Behavior
6 digit pin placeholder should appear
Actual Behavior
4 digit pin placeholder appears
Possible Fix
Steps to Reproduce

Open app and unlock by entering 6 digit pin
Go to settings and push change pin in security section
4 digit placeholder appears

Context
Your Environment

Zap version: 0.2.11-alpha
Android version: Android 10 (LineageOS)
Device: OnePlus3
LND Version: 0.92

Thanks for your report. I just tested it and same behavior on my phone. Probably missed to test this with longer PINs.
I will fix this asap!

I have just made a PR to fix this.
Due to our update cycles and store review waiting times it will still take a few weeks until this makes it into an official release, I guess.
In the meantime if you want to get rid of your PIN now, you have to clear the App data or uninstall Zap and then reconnect.

Fix has been released in v0.3.1-beta


Remove 'ens-' prefix from colour variable names

Type

[ ] Bug fix
[ ] New feature
[x] Improvement to existing feature

(Not sure - really just a code cleanup.)
Related JIRA Issue(s)

https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-205 (not directly relevant, but I want to make sure the CSS is clean before I start making major edits)
Importance

This is only urgent in the sense that any new or updated components with colour variables in the CSS will be incompatible with this branch (see Complications, below).
Description

I have removed the 'ens-' prefix from all the colour variable names. It made sense to use this prefix when we still used Foundation, to avoid name clashes, but now the longer names just make the CSS harder to read. There was also a potential confusion between $white (#fefefe) and $ens-white (#fff), which this PR fixes by renaming them $off-white and $white respectively.
Views affected

All views - colours should be (and are) completely unchanged, as the code change is behind-the-scenes.
Other effects

No automated tests needed, as this only affects cosmetic CSS. Browser and Storybook have been visually checked for issues and none found so far.

[ ] I have checked any requirements for Google Analytics
[ ] I have created any required tests
[ ] The PR has as its final commit a WASM/JS update commit if any Rust files were updated.

Possible complications

If any new components are merged in from branches that don't have this update, they will appear as black. However this can be avoided (after this PR is merged) by merging dev into your branch and updating any CSS colours before submitting your PR.

The failed check is because our CI/CD system has troubles with underscores in branch names. This shouldn't affect the merge.


Allows PMs for bot commands

Users can now PM the bot as well, rather than only using the channel #bot-commands
(I realized after doing this that this probably shouldn't have required a branch and that I should've probably used the fork for this?)

Users can now PM the bot as well, rather than only using the channel #bot-commands
(I realized after doing this that this probably shouldn't have required a branch and that I should've probably used the fork for this?)

LGTM


Add support for remote vector tile

Hi :)
This is a suggestion to add support for remote vector tiles, pushed for discussion.
This is our current use case, and I guess it will be for others, as soon as you want to separate the vector tiles provider server and the servers that style those tiles to produce raster images.
This implementation also changes the options API: instead of having hard coded a two indices array, we pass an object as tilesource, which defines the behaviour: use tilestrata-vtile dependecy (and then pass layer and file keys), or use a remote URL with TMS format. This change is to allow more format to be supported in the future (like a tilejson URL, or maybe a local directory with tiles).
I'm just playing around with tilestrata (nice move :) ) since today, so I may be totally missing a concept.
I've first thought about making my own plugin instead of trying to patch this one, but I quickly changed my mind because of the amount of code duplication.
Thanks for your review!

I really like where this is going! I've had it in the back of my head for awhile but haven't gotten around it. I think a dedicated tilestrata-proxy plugin would be great for this. That way, this sort of behavior would be available for any type of format / use case. For instance, if you wanted to fetch satellite tiles and composite them with another layer, you could do that (not that any satellite providers allow proxying unfortunately). Something like this:
.layer('vectortiles').route('t.pbf')
    .use(proxy('http://domain.com/tiles/{z}/{x}/{y}.pbf'));
.layer('rastertiles').route('t.png')
    .use(vtileraster({tilesource: ['vectortiles','t.pbf'], ...}));

This would also open up caching the vector tiles locally through any of the cache plugins, if you need to. I thought about adapting tilestrata-dependency, but then when considering all the possible sources, it could quickly get huge. Loading from urls, disk, mbtiles, ... I'd like to keep plugins small and dedicated to a single thing when possible. What do you think?

I think I see your point :)
I'm missing the both the overall picture and the knowledge of the details of tilestrata, so I think my understanding is a bit raw though ;)
I'll see if I can come up with something :)
Do you have an IRC chan where we can chat BTW?

Ah, also, it would be nice to add an .eslintrc file to the project, so it's easier for contributors to know which JS conventions to follow. (For example).

Let's continue the discussion with this (yet working) POC https://github.com/yohanboniface/tilestrata-proxy
To comment the code: https://github.com/yohanboniface/tilestrata-proxy/commit/2a19faf8063591a42c0ce706fd0908bb32935c81

@yohanboniface Skype work? My handle is the same: brianreavis

Ah, also, it would be nice to add an .eslintrc file to the project, so it's easier for contributors to know which JS conventions to follow. (For example).

Agree. I'll try to see what I can come up with soon!

Skype work? My handle is the same: brianreavis

Heee, no, I haven't Skype installed (private code, global company, that kind of things ;) ) :(
Let's say we can discuss through Github for now then :)
Have you reviewed the tilestrata-proxy POC, and do you think the direction is good? I've added you as collaborator in the repo, so fill free to move it to naturalatlas orga and take control over it.

@yohanboniface Sorry for the slowness! I'll try to look over it soon.

@yohanboniface Hey again, thanks for your work again! I made some modifications (small) and published a version on NPM: https://www.npmjs.com/package/tilestrata-proxy. The main changes I made were:

Headers from the upstream source are now included in the response (useful for Content-Type)
Non 200 OK statuses will return the appropriate error code now

Great! I'll have a look at the code :)
(Sorry for the lag, I was offline 10 days (sailing… :) ).


use voyager in lumen framework ?

Version information

Laravel: v#.#.#
Voyager: v#.#.#
PHP: #.#
Database: [type] [version] (e.g. MySQL 8.0)

Description:
A clear and concise description of what the problem is.  Please also explain why this doesn't fit into the defined issue templates
Additional context
Add any other context or screenshots about the feature request here.

Template is not optional.  Also, as noted in the template, questions should be asked in our slack group.
Beyond that, no, that won't work


Change Cache-Control

Changes are not applied, because page is cached.
Cache-Control: no-cache ?

Not applicable


Unable to properly define Type Guard

interface A {
    a: string
    b: string
}

interface B {
    b: string
    c: string
}

type AB = A & B;

function isA(obj: AB): obj is A {  // ERROR here
    return !!obj.a &&
        !!obj.b &&
        !obj.c;
}

Error:

That is because type assertions cannot widen the type, only narrow it.
AB extends A, but A does not extend AB.
What you actually want is to say obj is not B, which is not currently possible.

Is this what you wanted?
type AB = A | B;

function isA(obj: AB): obj is A {
    return "a" in obj && "b" in obj && !("c" in obj);
}

The signature is nonsensical as written; its only valid return value is true. All ABs are As.


add environment IngressStore field

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Cannot reset a group power sensor

Logger: homeassistant.components.automation.power_reset
Source: helpers/service.py:707
Integration: Automation (documentation, issues)
First occurred: 00:00:05 (2 occurrences)
Last logged: 00:00:05

Energy Sensor Reset: Error executing script. Unexpected error for call_service at pos 1: 'GroupedPowerSensor' object has no attribute 'async_reset_energy'
While executing automation automation.power_reset
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/script.py", line 447, in _async_step
    await getattr(self, handler)()
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/script.py", line 680, in _async_call_service_step
    await service_task
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/core.py", line 1713, in async_call
    task.result()
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/core.py", line 1750, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity_platform.py", line 751, in handle_service
    await service.entity_service_call(
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/service.py", line 676, in entity_service_call
    future.result()  # pop exception if have
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity.py", line 930, in async_request_call
    await coro
  File "/srv/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/service.py", line 707, in _handle_entity_call
    result = hass.async_run_job(partial(getattr(entity, func), **data))  # type: ignore[arg-type]
AttributeError: 'GroupedPowerSensor' object has no attribute 'async_reset_energy'

This is expected. There is no such thing as resetting a power sensor, this would not make any sense.
Because a power sensor is just a measurement in point in time (in Watt), not a total sum.
You can only reset energy sensors (kWh meters).
I am surprised how you were able to select the power sensor as the select should be limited to only energy sensors. You must have either an older version of powercalc running or defining the entity id with YAML in the automation.

Of course, I think I made that mistake once before.
Sorry for troubling you.


Create list events view

Create simple view (with template) that will list all events in the DB order by upcoming date.

still not closed?

sorry for delay...


Should github-dark theme match official Github Dark mode?

Hello!
I was curious to get your thouts on the "github-dark" theme. Currently it doesn't match the official GitHub Dark mode colors.
Do you think the "github-dark" them should be updated or a new them added?
Thank you!

For sure, just waiting on the next primer update

For sure, just waiting on the next primer update

Is this something that will be automatically updated (e.g. Primer provides it) or will the color codes need to be changed here?
I ask because I'm testing locally and modified the github-dark theme to match the current Github Dark Mode. I can submit a PR if you want either as a separate theme or updated github-dark.
Thanks!

Is this something that will be automatically updated (e.g. Primer provides it) or will the color codes need to be changed here?
I ask because I'm testing locally and modified the github-dark theme to match the current Github Dark Mode. I can submit a PR if you want either as a separate theme or updated github-dark.
Thanks!

Utterances uses standard primer for the GitHub light theme, then a modified primer for the rest of the themes, including GitHub dark. Mostly variable changes. Once GitHub ships a new version of primer with all the css custom property and dark theme work, I’ll update utterances to use it.

Utterances uses standard primer for the GitHub light theme, then a modified primer for the rest of the themes, including GitHub dark. Mostly variable changes. Once GitHub ships a new version of primer with all the css custom property and dark theme work, I’ll update utterances to use it.

Hi @jdanyow
Would it be possible to get your input on https://github.com/utterance/utterances/pull/463 ?
Thank you very much!

Hi @jdanyow
Would it be possible to get your input on https://github.com/utterance/utterances/pull/463 ?
Thank you very much!


[feat] support for default system browser

Describe the problem
when i was building my app i ran into a problem.it was not on my part it just didnt work with my browser.i tried searching for docs for this but found nothing.
Describe the solution you'd like
a boolean called useSysBrowser should be added to tauri.conf.json or idk
Alternatives considered
No response
Additional context
No response

Tauri can't work, and is not supposed to work, with a normal browser in full capacity.
That said, if you just want to expose your frontend to the browser you can check out https://github.com/tauri-apps/tauri-plugin-localhost/ and if you want some invoke calls to also work you may be able to use https://github.com/tauri-apps/tauri-invoke-http/ on top.
Other than that, this is out of scope for Tauri, thank you :)


update sqlitetracker docs

as part of the new experiment tracker we made some improvements to SQLiteTracker, which remain undocumented. We should ensure that the new methods have docstrings and that the tutorial shows the new features.
to know what changed, check out the blog post: https://ploomber.io/blog/experiment-tracking/
and the changes to the source code: https://github.com/ploomber/sklearn-evaluation/blame/master/src/sklearn_evaluation/tracker.py
once that's documented, we should post it on socials, please include a GIF.
@RodolfoFerro: please add this to your tasks for the nov 21-25 week.

TODO:

Review git history to verify if Docstrings are needed
Document in the docs notebook these changes

This was documented in release 0.8.2.


How to prune the mobilenets?

There are some schedules of pruing the mobilenets in distiller. I'm curious about the principle of pruning the mobilenets, or more specifically, pruning the depth-wise seperable convolution? Really appreciate if anyone could expain this.

Hi @Ringhu
The unique characteristic of DWS convolutions, when it comes to filter pruning, has to do with the thinning procedure, and this is due to data dependencies.
To understand what I mean, let's first review the data dependencies in a "regular convolution" (when groups=1), which I discuss at length here.  If A, B and C are all convolution operators connected sequentially (i.e. A ==> B ==> C), then removing a filter from the weights of A, will (1) remove one channel from the activations of A, which means that (2) we need to remove that channel from the weights of B.  If between A and B we have a batch-normalization layer (i.e. A ==> BN ==> B ==> C), then this layer is also affected and we need to remove the parameters of the activation channel that was removed.
  Now on to DWS.   Let's imagine that we make the B convolution from above a DWS convolution: i.e. A ==> (B1 ==> B2) ==> C.  B1 is a DW convolution, which means that it has filters of size kk1, and groups equal to the number of channels in its input.  B2 is a point-wise convolution.  If we now remove a filter from the weights of A, then (1) we have one less channel in A's output activations (as above); (2) we need to remove that one channel from the weights of B1 (as above).  Nothing new so far. But B1 is a DW convolution so each filter has only one channel - if we remove this single channel, we also remove that filter.  Removing a filter from the weights of B1 means that (3) B1's output has one less channel; which means that (4) we need to remove a channel from the weights of B2.
DWS have more intricate data dependencies because of the number of groups != 1, and this makes things a bit more complicated.
Hope this helped,
Neta

Thank you for your reply @nzmora . Maybe I didn't describe my question well. For example, for regular convolution, there are some principle such as Song Han's pruning weights with a threshold, or pruning filters according to the L1norm. So my question is what rules do we follow when we pruning the DWS convolution?

The DWS convolutions have very little computational load, and therefore it would make very little sense to prune them.
Best,
Dan


cordova-plugin-camera not working in Windows Phone 8.1 ionic framework.

when i try invoking camera app closes after throwing error NotFoundError

xception is about to be caught by JavaScript library code at line 460, column 17 in ms-appx://com.example.app/www/plugins/cordova-plugin-camera/src/windows/CameraProxy.js
0x800a139e - JavaScript runtime error: NotFoundError
Unhandled exception at line 871, column 9 in Function code
0x800a139e - JavaScript runtime error: NotFoundError

Ionic Version: 1.1.0
Cordova CLI: 6.0.0
Ionic Version: 1.1.0
Ionic CLI Version: 1.7.14
Ionic App Lib Version: 0.7.0
OS:
Node Version: v5.6.0

This issue was moved to driftyco/ionic-cli#781


Update Dockerfile

I think it could be more useful to update current Dockerfile to:
# syntax=docker/dockerfile:1

ARG  PY_VERSION=3.7
FROM python:${PY_VERSION}-buster

WORKDIR /py4ai-core

# RUN apt-get update && apt-get upgrade -y && apt-get install make git gcc libpq-dev -y --no-install-recommends

COPY requirements/requirements.in requirements/requirements.in
COPY requirements/requirements_dev.in requirements/requirements_dev.in
COPY LICENSE MANIFEST.in versioneer.py setup.py pyproject.toml README.md Makefile ./
COPY .git .git
COPY py4ai py4ai
COPY tests tests

RUN addgroup --system tester && adduser --system --group tester
RUN chown -R tester:tester /py4ai-core

# change to the tester user: switch to a non-root user is a best practice.
USER tester
ENV PATH ${PATH}:/home/tester/.local/bin

CMD make checks

This would allow us to easily test our package with different python versions (which is the most common usage I make of containers in this project).
If we find a value in keeping a python entrypoint to che container I'd suggest instead this solution:
# syntax=docker/dockerfile:1

ARG PY_VERSION=3.7
FROM python:${PY_VERSION}-buster as builder

WORKDIR /py4ai-core

COPY requirements/requirements.in requirements/requirements.in
COPY requirements/requirements_dev.txt requirements/requirements_dev.txt
COPY LICENSE MANIFEST.in versioneer.py setup.py pyproject.toml README.md Makefile ./
COPY .git .git
COPY py4ai py4ai
COPY tests tests
RUN addgroup --system tester && adduser --system --group tester
RUN chown -R tester:tester /py4ai-core
USER tester
RUN make checks

FROM python:${PY_VERSION}-slim-buster
WORKDIR /py4ai-core
COPY --from=builder /py4ai-core/dist /py4ai-core/dist
RUN addgroup --system runner && adduser --system --group runner
RUN chown -R runner:runner /py4ai-core
USER runner
RUN ls -t ./dist/*.tar.gz | xargs pip install
ENTRYPOINT ["python"]

I'm totally up for adding the arguments to be able to build under different python versions, parametrically!
Also, I kinda liked the two-stage build we had, with the image that is built only having minimal dependencies (not the test ones)
The two things are orthogonal and we could have both actually (parametric python version input AND minimal docker image with two-stage build). Why are you proposing a larger refactoring of the Dockerfile?

Actually the main use I found for Docker in this context was exactly to test the package under different python versions (and, maybe, Operating Systems). Thus I found a little bit useless the second build with minimal requirements: I never felt the need to actually do something different than testing the package in a different environment...
What use case do you have in mind?

For what it takes copying .git folder in the container the reason is that we use versioneer to handle semantic versioning and it  gets the version number from the git tag. Thus we need to have that information in the container to correctly version the pacakge.
Not having it is no real big deal since what happens in that case is simply that we will always have 0.0.0 (or something similar) as version number when building package in the container, but it kinda hurt my sight not seeing the correct version number in the logs.

Actually the main use I found for Docker in this context was exactly to test the package under different python versions (and, maybe, Operating Systems). Thus I found a little bit useless the second build with minimal requirements: I never felt the need to actually do something different than testing the package in a different environment...
What use case do you have in mind?

Well, it is to have a functioning environment where to use the package. I agree that if this would be a direct application (with a rest API and/or services embedded), that would be more relevant. But yet, I believe it is a good practice to have a two-stage build, where in the first one you build and test the package, while in the second you only install the required dependencies and the application itself. I understand It is not as crucial as in other contexts, but why not. I don't see extra complexity in doing this, and indeed the images we produce are actually smaller.

Not having it is no real big deal since what happens in that case is simply that we will always have 0.0.0 (or something similar) as version number when building package in the container

BTW, the version could rather be embedded in the version of the docker container which would show up as "py4ai:x.y.z"

For sure the package version could be added to the image tag, and probably we could also change the makefile so that would be done automatically with a single command. I'll amend my PR with your suggestions.


fix(behavior_path_planner): additional buffer during lane change for intersection

This is so that if lane change is performed on restricted areas, the final lane
change point will be before the restricted areas.
Signed-off-by: Muhammad Zulfaqar Azmi<EMAIL_ADDRESS>Related Issue(required)
https://github.com/autowarefoundation/autoware.universe/issues/531
Description(required)
The PR adds additional check to see the end trajectory is in the intersection, and if it is in the intersection, the the function will compute the necessary distance for the vehicle to stop just in front of the intersection.
Review Procedure(required)
Place goal just after the intersection and see that the end of trajectory is before the intersection
https://user-images.githubusercontent.com/93502286/160962209-776238b0-11d7-4a92-97fe-69cfe1c4076a.mp4
Related PR(optional)

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

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

If you are adding new package following items are required:

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

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

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

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

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

CI Checks

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

This is the current result of the bug fix
https://user-images.githubusercontent.com/93502286/160962578-0515abfb-7f01-49e1-903c-97a723bc8aee.mp4


odgi cover parallel sort

odgi cover takes advantage of parallel sorting.
Here an example for creating 200 new paths in the yeast pangenome:
time odgi cover -i Sc+Sp.pan.fpal2k.s.odgi -o Sc+Sp.pan.fpal2k.s.cover.n200.og -n 200 -d

time
master
cover-parallel-sort

real
3m7,479s
1m54,870s

Cool. Parallel sorting is awesome.
On Sat, Sep 5, 2020, 10:25 Andrea Guarracino<EMAIL_ADDRESS>wrote:

Merged #161 https://github.com/vgteam/odgi/pull/161 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vgteam/odgi/pull/161#event-3732725501, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABDQEK3L6GP635QUOHJWVLSEHYV3ANCNFSM4Q2SOXZQ
.


⚠ Mobitopup has degraded performance

In 1526ab3, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4155 ms

Resolved: Mobitopup performance has improved in 07ac140 after 7 minutes.


Support CrowdStrike for amazon-eks-node-al2023-x86_64-standard-1.30

CrowdStrike for amazon-eks-node-al2023-x86_64-standard-1.30 is rfm-state=true
--rfm-state=true indicating whether the sensor is in Reduced Functionality Mode
rfm-reason=The kernel backend does not support the running kernel, code=0xC0000225.
Any idea when EKS 1.30 amd64 supports CrowdStrike falconSensor ?
Environment: EKS

AWS Region: Any
Instance Type(s): t2micro
EKS Platform version (use aws eks describe-cluster --name <name> --query cluster.platformVersion):
Kubernetes version (use aws eks describe-cluster --name <name> --query cluster.version): 1.30
AMI Version: amazon-eks-node-al2023-x86_64-standard-1.30-v20240703
Kernel (e.g. uname -a):  6.1.94-99.176.amzn2023.x86_64
Release information (run cat /etc/eks/release on a node):

sh-5.2$ cat /etc/eks/release
BASE_AMI_ID="ami-07abf5a3675e9b4d6"
BUILD_TIME="Wed Jul  3 05:03:36 UTC 2024"
BUILD_KERNEL="6.1.94-99.176.amzn2023.x86_64"
ARCH="x86_64"

That's a question for CrowdStrike (though they're probably a bit busy today!)

🙃 @cartermckinnon


Replace custom removePadding with base64.NoPadding

Base64 encoder officially provides an ability to avoid adding the padding characters.
Calling strings.TrimRight() would add overhead onto it, so we should just use WithPadding(base64.NoPadding) instead.

Can you squash down to a single commit?

@liggitt Okay, Done :)


Logging in Windows

Logging in Windows
what you made is VERY cool.
now, most Customers use Windows, and it would be cool if we find easy Windows tools for logging.
one is Putty, which many Customers already use a lot.
https://www.putty.org/
is it visible to make https://github.com/nopnop2002/esp-idf-net-logging compatible with Putty ?
or find another Customer friendly Client ?
Thanks,
Franz

is it visible to make https://github.com/nopnop2002/esp-idf-net-logging compatible with Putty ?

I don't use Putty, so I don't know what features I need.
Please tell me in detail.

i need any user friendly Logging Client.
https://github.com/nopnop2002/esp-idf-net-logging/blob/main/README.md --> all command line Stuff, which is VERY difficult for non Computer Scientists.

putty is a simple client and does not seem to have server functionality.
This project requires server functionality.

We need any user friendly Logging Server.

i understand. this makes sense.
it is too much Overhead to have inside the ESP32 a Server for Logging,
so the Server is on the PC, what makes a lot of Sense.
so next Question: Would it be possible inside the Browser ?
the ESP32 could host the Webserver, deliver the Server to the Clients Browser, and the Server runs in the Browser. HTML5 and such. Javascript.

I found it.
https://apps.microsoft.com/detail/9nblggh52bt0

I found it.
cool cool cool ...

You can disable this if you are unable to display ANSI color codes correctly.

You can reopen this issue at any time.


connlib: fix wildcard checking in gateways

the way we were checking for subdomains in the gateways completely broke, didn't detect it before because the deployed staging version for gateways is too old.
Added a few CI tests so this doesn't' happen again. seems like github runners doesn't support pinging the outside world so I'm putting that off for now.

CI seems to be passing, merging this since gateways in main are broken ATM


Webpack errors are not logged

I'm submitting a feature request
Webpack version:
2.x
Webpack Karma version:
2.0.x
Karma version:
1.x
Please tell us about your environment:
OSX 10.x
Current behavior:
karma-webpack do not log webpack configuration issues. Simply reports
26 02 2017 22:08:57.640:ERROR [preprocess]: Can not load "webpack"!
  Error
    at webpack (..../node_modules/webpack/lib/webpack.js:19:9)

code here https://github.com/webpack-contrib/karma-webpack/blob/v2/src/karma-webpack.js#L65
Expected/desired behavior:
Instead karma-webpack should catch expcetion thrown by webpack and log message on exception.
Replacing above line with
  var compiler;
  try {
    compiler = webpack(webpackOptions);
  } catch(e) {
    console.error(e.message);
    throw e;
  }

Report is
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.module has an unknown property 'preLoaders'. These properties are valid:
   object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp? }
   Options affecting the normal modules (`NormalModuleFactory`).
 - configuration.resolve.extensions[0] should not be empty.
26 02 2017 22:08:57.640:ERROR [preprocess]: Can not load "webpack"!
  Error
    at webpack (..../webpack/lib/webpack.js:19:9)

What is the motivation / use case for changing the behavior?
Make easier to resolve webpack configuration issues.

That's not an error, that is a malformed configuration.
Everything you need to resolve the issues with your configuration are in the stack you pasted in.
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.module has an unknown property 'preLoaders'. These properties are valid:
   object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp? }
   Options affecting the normal modules (`NormalModuleFactory`).
 - configuration.resolve.extensions[0] should not be empty.

@d3viant0ne yes, i know. But, that is not point of this report. Could you reread this?
karma-webpack currently keeps this information hidden from user and reports only Can not load "webpack"!. Which is not very informative and generates unneccessary support requests for you.

@patope - Yeah, I misread the first part. I'll have this fixed and out to npm shortly.

Do you have an ETA on the fix?

@marcusellis05 - It's next on my list after css-loader to go out. Couple of hours to npm


Added check if content-type header is present for transformResponse

This PR adds a small check for the content-type header in the transformResponse override in the AxiosStrategy file.
This PR fixes #894

Hey @AndrewBastin,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: d380c580-9db3-11ea-80ab-25118b76b5d1