fix(atomic): possible @coveo/headless version mismatch

https://coveord.atlassian.net/browse/KIT-1515
See this related PR for samples
Root problem
When installing @coveo/atomic, @coveo/headless is both a “subpackage” (@coveo/atomic/headless) and a dependency (@coveo/headless).
Stemming issues

Both versions can have a possible mismatch
The typescript of Atomic’s Headless points to @coveo/headless instead of @coveo/atomic/headless.
You start getting completions for both packages in VS code, because of the dependency. Not a big deal, but can be a bit annoying.
Using the CDN & npm packages could also lead to version mismatches.

Solutions

For issue # 1, by using lerna’s --exact option, it will ensure that the exact version is installed for our packages https://github.com/lerna/lerna/tree/main/commands/version#--exact
For issue # 4, there should be no major issues when building custom components with a different Atomic & Headless patch version, but there may be some internal bugs if it’s using different minor version (we should specify in the doc to stick to the same minor when using an hybrid CDN/NPM setup, and perhaps advise against it entirely). To fix this in the CLI project, we could either:

Ensure the CDN path fits the installed minor (e.g. I have<EMAIL_ADDRESS>installed, CDN should be https://static.cloud.coveo.com/atomic/v1.34/atomic.esm.js
Remove the hybrid mode and use the installed @coveo/atomic build (personally favoring that option, see PR)

For issues # 2 & # 3, removing @coveo/atomic/headless from NPM in our next major bump and only keeping it for the CDN is a possible fix. This will make better use of NPM without workaround when using NPM. A doc change will be required.
For issue # 2 replacing the path “@coveo/headless” with “@coveo/atomic/headless” in our declaration files for the Atomic package could do it.
For issue # 2 now in the CLI project, use a different path in the tsconfig mapping @coveo/headless to Atomic’s (see PR)

We could go for fixes # 1, # 2, (# 4 or # 5) for now and perhaps fix # 3 when we bump?

@btaillon @olamothe

We could go for fixes # 1, # 2, (# 4 or # 5) for now and perhaps fix # 3 when we bump?

number 4 or 5 ?

number 4 or 5 ?

I think 4 is the most solid solution that will work for people that also manually install/start a project (and not done through the CLI).

For issue # 1, by using lerna’s --exact option, it will ensure that the exact version is installed for our packages https://github.com/lerna/lerna/tree/main/commands/version#--exact

I'm not sure if Lerna proceed topologically for the release, i.e., let's say I do a release where atomic and headless changes, will the new version atomic use the new version of headless?


Freezes/Crashes tab on ui-grid.info

http://ui-grid.info/
Steps to replicate:

Visit page
Trigger ng-inspector

This one has proven pretty difficult to debug so far, since the Chrome console crashes fairly frequently with the tab. I'm guessing it's a performance issue related to the amount of data the inspector probably needs to render on a page using multiple "grid" components, but that's purely speculation.

This is super surprising to me - http://plnkr.co/edit/yLAIMZcvBLK9kBqDOzpx?p=preview
In that plnkr, a single record in ui-grid causes a huge performance issue. 3+ starts making the page unusable.
I'm going to try to dig into this one soon. This doesn't seem like the typical "big app" performance problems.

I was having issues with errors being thrown in older versions of angular after #82, so I switched the detection to test if the definition of the directive is an array, otherwise annotate it in 9b35153.
For UI-Grid, the extension was throwing an error and displaying the infamous gray pane, but with this change it seems to work for me, and looks very performatic with your exemple.

I'm closing the issue, but please re-open if you're still having errors and/or performance issues.

Doesn't look like it's fixed, unfortunately :disappointed:
One thing I really dislike about plnkr: they always try to stick you within an iframe. Testing on the page you linked to is actually inspecting the plnkr app itself, not the example.
If you drill down into the iframe(http://run.plnkr.co/plunks/yLAIMZcvBLK9kBqDOzpx/), the same issue is still happening.

Are you able to re-open the existing issue, or should I open up a new one?


Merge pull request #29 from EBI-Metagenomics/dev

Dev

Looks fine for me! Just some small changes to the profile handling of Nextflow.
I'm just wondering, because I know that Guillermo also added some changes to the voting system recently but maybe that is in another branch. I will check this and start a PR if I can find it (because we anyway need these changes to re-run the pipeline for the current manuscript)

Sure, one the CWL tests is failing. Before mering this I'll take a look at those.

I'm merging this, I'll fix the failling test in the docker branch anyway.

I'm merging this, I'll fix the failling test in the docker branch anyway.

yip great, thx

yip great, thx


Decouple Cell and CrossSection

This PR decouples the CrossSection from the Cell. This has the advantage that a CrossSection will no longer have a z_min and z_max (present in Cell) which should improve caching of previously calculated modes.
This required some breaking changes:

Cell is no longer an attribute of CrossSection. Wherever you used cs.cell or similar you'll have to find an alternative way of accessing the needed information. Note: mesh is now a native attribute of CrossSection.
Use CrossSection.from_cell(cell=cell, env=env) wherever you used to use CrossSection(cell=cell, env=env)
A Mode depends on a CrossSection not on a Cell and hence its .cell attribute is now also gone. This will obviously improve caching but unfortunately this also means you'll have to provide cells as a second argument to compute_s_matrix from now on. Since compute_s_matrix only depends on the cell length you can also skip supplying cells and specify cell_lengths as a keyword argument for that function.
The ez_interfaces attribute (previously in Cell) is now moded to Mesh.

There are a bunch of other minor changes under the hood (such as Geometry->Geometry2D,Geometry3D and Structure->Structure2D,Structure3D) but these should not touch the user API.
@Jan-David-Black , feel free to comment or request changes. I'm planning to merge this branch on Thursday.

👍 Do we delete the branch?


frontdoor readme t2 config

frontdoor readme t2 config

@RAY-316 We have released package, so it is better to delete 'package-version' in 'readme.python.md'

/azp run


[BUG] "Cannot read property 'guild' of undefined" when trying to play more than one playlist

Bug Description
"Cannot read property 'guild' of undefined" when trying to play more than one playlist
Reproduction Steps
Steps to reproduce the behavior:

Play one playlist (dosen't matter if it's from YT or Spotify)
Try to play another playlist

Expected Result
The other playlist gets added to the queue
Attachments
my code for the command (mostly the same as in example)
    if (command === 'playlist' || command === 'pl') {
            message.channel.send(`Szukam playlisty...`);
        // If maxSongs is -1, will be infinite.
        await client.player.playlist(message, {
            search: args.join(' '),
            maxSongs: -1
        });
    }

It's of course running in async function
client.on('message', async (message) => {
    const args = message.content.slice(config.prefix.length).trim().split(/ +/g);
    const command = args.shift().toLowerCase();

Versioning:

OS: Arch Linux
NPM Version 15.12.0
Module Version 7.0.1

I will be looking into it today.

It happens too when there are already songs in queue and you try to add a playlist

this also happens to me, still havent found a fix yet

I fixed your issue and I will be pushing the update to NPM in ~4 hours.
I will let you know, thanks for reporting!

Hey! Update time!
I hope everything got fixed, please check within v7.1.0 and let me know if the error still exists!
https://www.npmjs.com/package/discord-music-player
Thanks for reporting,
Sushi!


Carousel Notification

Hi @rafaelsetragni
first of all thank you for your work and your contribution!
I'm here to ask you if it is possible to implement a new style for notifications.
In particular it would be nice to implement a notification that contains an image carousel.
Here I am attaching some useful links:
Android package
https://github.com/shaileshmamgain5/Carousel-Notification
iOS package:
https://documentation.onesignal.com/docs/ios-image-carousel-push-notifications
Thanks again and have a nice day.

Hi Franky!
Thank you so much for your project links. They are and will be very useful, in fact.
It's on my future plans to implement it. For now i need to finish the FCM add-on plugin first and the web portal to implement it. I believe i will take 3 months to reach that point.
I added to the project planing this enhancement, and you can track the progress there. 👍


Very long compilation time on big projects

I have note that Bridge take a lot of time to compile our project(about ~11 minutes). And i note that compilation without Bridge take about 10-20sec.
2016-09-30T01:28:41:870 	Info		Sorting references done
2016-09-30T01:28:41:870 	Info		Before emitting...
2016-09-30T01:28:41:870 	Info		Before emitting done
2016-09-30T01:28:41:871 	Info		Emitting...
2016-09-30T01:28:41:871 	Trace		Emitting block Bridge.Translator.EmitBlock
//8 min. later
2016-09-30T01:28:49:761 	Info		Transforming outputs...
2016-09-30T01:28:49:762 	Trace		Wrapping to modules...
2016-09-30T01:28:49:762 	Trace		Wrapping to modules done
2016-09-30T01:28:49:762 	Trace		Combining outputs...

Can you check compilation time with logging turned off:
"logging:" {
    "level": "None"
}

How many classes does the project contain?

10-20 sec compilation using visual studio compiler? How many lines/kB does your project have?

full project have about 3k source files...

Wow, you can probably split that into libraries instead of compiling everything in one shot every time, should help.

Its splited. But compilation root library cause full rebuild and its take about 15min

I dont know your project settings, but full rebuild should be only done when you ask for that explicitly, when you reference other bridge dlls with embedded js it should be a lot faster

Full rebuild happen when we change the root library, because all projects in solution depends on it.

I there way to profile Bridge? May be i can find a bottle neck

If you want profile compilation process then clone Bridge repository, add sandbox project to Bridge solution and run translation from sandbox (also it allows to debug Bridge)
using System;
using System.Collections.Generic;
using System.Diagnostics;
using System.IO;
using System.Linq;
using System.Text;
using Bridge.Contract;
using Bridge.Translator;
using Bridge.Translator.Logging;

namespace Bridge.Sandbox
{
    class Program
    {
        static void Main(string[] args)
        {
            var logger = new Logger("Bridge.Builder.Console", true, new ConsoleLoggerWriter(), new FileLoggerWriter());
            logger.LoggerLevel = LoggerLevel.Error;
            // PLEASE ENSURE THAT Bridge.dll file is available in the output folder (bin/Debug/)

            var root = @"C:\projects\Bridge\v1\";
            var projectLocation = root + @"Sandbox\TestLibrary\Bridge.TestLibrary.csproj ";
            var clrLocation = root + @"Bridge\Bridge\bin\Debug\Bridge.dll";
            var outputLocation = Path.ChangeExtension(projectLocation, "js");

            var bridgeOptions = new Bridge.Translator.BridgeOptions()
            {
                ProjectLocation = projectLocation,
                OutputLocation = outputLocation,
                BridgeLocation = clrLocation,
                Rebuild = false,
                ExtractCore = true,
                Configuration = null,
                Source = null,
                Folder = null,
                Recursive = false,
                Lib = null,
                DefinitionConstants = null,
                Help = false,
                NoTimeStamp = null,
                FromTask = false,
                Name = "Sandbox"
            };

            TimeSpan begin = Process.GetCurrentProcess().TotalProcessorTime;

            var processor = new TranslatorProcessor(bridgeOptions, logger);

            var result = processor.PreProcess();

            if (result != null)
            {
                return;
            }

            try
            {
                processor.Process();
                processor.PostProcess();
                TimeSpan end = Process.GetCurrentProcess().TotalProcessorTime;
                Console.WriteLine("Compilation time: " + (end - begin).TotalSeconds + " ms.");

                Console.WriteLine(processor.Translator.GetCode());
                Console.ReadLine();
            }
            catch (Exception e)
            {
                Console.ForegroundColor = ConsoleColor.Red;
                Console.WriteLine("Error: {0}", e.Message);
                Console.ResetColor();
                Console.ReadLine();
            }
        }
    }
}

@AndreyZM, can you check https://github.com/bridgedotnet/Bridge/issues/1902#issuecomment-250585489

In the log above you can see that betwen "emmiting block" and "transforming outputs"

@AndreyZM - Was this Issue closed accidentally?

In the log above you can see that 8min betwen "emmiting block" and "transforming outputs", and there no any message betwen.

Hi again. We can provide a stripped project that took 5 minutes to compile with a Bridge. May be it can help to profile and optimize. Just give me a email to mail to.

Hi @AndreyZM - Can you create a GitHub repo for the sample project? That would be much better and allow for efficient collaboration.

I just don't want to put it into public domain.

Here is
https://github.com/Shkarin/TestBuildBridge

HI @AndreyZM - Thanks for the demo project. We were able to make some improvements. With our revisions, your project is now compiling 300% faster for us.
More improvements will come in stages. These recent changes will be included in 15.4, and others are planned for 16.0 (or beyond).
At least your project is compiling in a much more reasonable time now, and we're still investigating a few other revisions that will hopefully further improve those numbers for the 15.4 release.
More information will be posted once the changes have hit the master branch.

Compilation time before and after

Before
After

TestProject
3min
33sec

Batch1
37sec
22.54sec

Batch2
5.45sec
5.7sec

Batch3
14.98sec
10.75sec

Batch4
25.1sec
17.85sec


squad alerts should appear in the middle of the screen

things like ammo drops, new squad leaders, and overwatch messages
john parity says "parity" unless this is mandela effect

should look like this. noting that cm13 doesnt have an alert for squad drops, but i think thats a nice change for rmc. its like your SO telling you you got a drop but they dont have to remember to now (epic)
https://github.com/user-attachments/assets/d1d1b277-7b91-4b34-995b-d21064be2ab2

semi related to #4523


Update docker-machine create command

If docker-machine --create is invoked, the user will receive an error: "Incorrect Usage."  This PR changes the example command to docker-machine create.

Thanks @uncompiled :)


Comment out an unreachable statement

This comments out a currently unreachable statement in MiqWorker. This is just to silence "statement not reached" warnings.

@miq-bot add_label refactoring, ivanchuk/no, changelog/no

@bdunne Please review

@bdunne Ok, updated.


Fix: recursive delete calls no longer use activePublish

This should fix the slow deletion process for large groups of objects. Previously every child node deletion and every recursive call used activePublish = true, which slowed down sciview by a lot.

Good question, but I'd also assume no.
And I tested this with the Protein you can add via the Add menu. The deletion is almost instant now.

I'd agree that if it's known that the parent node is gone is enough 👍

Thanks, @smlpt 👍


#1872 Add right-click menu for bonds

Resolves: #1872
1. Feature description
#1872
2. UI styles
Just follow styles of the existing context menu:

2.1 When right-clicking a bond

2.2 When right-clicking a bond in a selection

3. Use cases
3.1 General usage
Scenario 1
Given: a molecule and any active tool
When: the user right-clicks on the bond
Then: the context menu shows
Scenario 2
Given: a molecule and any active tool
When: the user right-clicks on the atom(or any other non-bond things)
Then: the context menu doesn't show
GIF of the general usage:

3.2 Batch updates
Scenario 1
Given: the user has selected a bunch of things
When: the user right-clicks any selected bond
Then: the context menu shows
Scenario 2
Given: Scenario 1
When: the user clicks "Delete"
Then: All selected bonds are deleted (note that if left atoms become detached, they will be deleted too)
Scenario 3
Given: the user has selected a bunch of things
When: the user right-clicks a non-selected bond
Then: the context menu doesn't show
GIF of batch updates:

3.3 Handling conflict with the existing functional-group context menu
Note: the following scenarios are compatible with the existing logic process, but maybe will change after refactoring the functional-group context menu.
Scenario 1
Given: an expanded functional group
When: the user right-clicks a bond in the f-group
Then: only the functional-group context menu shows
Scenario 2
Given: the user has selected a bunch of things including functional groups
When: the user right-clicks a selected or non-selected bond
Then: only the functional-group context menu shows
4. My mind map before coding
https://excalidraw.com/#json=PtVEKcmFEDYpJ7MGCU7Ye,W21nPx7QUdIeCAAs_apUQw
5. Next steps

Refactor the existing functional-group context menu by react-contexify
Add right-click menu for atoms
Add context menu document to internal KB (Ketcher first step - Code structure) and help.md

Thanks for your review @Nitvex, I am going to create a new issue on refactoring the existing functional-group context menu. And list all the things I plan to do:

[ ] Reduce two context-menu triggers to one
[ ] Put all things related to the context menu into the folder where StructEditor is
[ ] Refactor the existing functional-group context menu by react-contexify, and remove the library react-contextmenu from dependencies.

What's your take on this?

Thanks for your review @Nitvex, I am going to create a new issue on refactoring the existing functional-group context menu. And list all the things I plan to do:

[ ]  Reduce two context-menu triggers to one
[ ]  Put all things related to the context menu into the folder where StructEditor is
[ ]  Refactor the existing functional-group context menu by react-contexify, and uninstall the library react-contextmenu from dependencies (preparation for upgrading to React 18)

What's your take on this?

Yes, that's a good point. I agree with all. Small notes:
– Please, describe in a refactoring task a conflict between two menus and how to avoid a conflict.
– Actually, we already have a PR (https://github.com/epam/ketcher/pull/1829) for React 18 – and here react-contextmenu is replaced by MUI menu.

Thanks for your review @Nitvex, I am going to create a new issue on refactoring the existing functional-group context menu. And list all the things I plan to do:

[ ]   Reduce two context-menu triggers to one
[ ]   Put all things related to the context menu into the folder where StructEditor is
[ ]   Refactor the existing functional-group context menu by react-contexify, and uninstall the library react-contextmenu from dependencies (preparation for upgrading to React 18)

What's your take on this?

Yes, that's a good point. I agree with all. Small notes: – Please, describe in a refactoring task a conflict between two menus and how to avoid a conflict. – Actually, we already have a PR (#1829) for React 18 – and here react-contextmenu is replaced by MUI menu.

Oh, 😮 I didn't notice that we already have a PR (#1829) for React 18. Actually, all these refactoring things are based on replacing react-contextmenu with react-contexify.
As react-contextmenu has been replaced by MUI menu, I recommend all these refactoring things happen after merging the two PRs, otherwise, it's really hard to resolve the code conflicts.


hadolint tasks fails with no much info

[lint] 2021/04/26 21:26:33 Error executing command: fork/exec /tekton/scripts/script-1-qm58j: no such file or directory
container step-lint has failed  : [{"key":"StartedAt","value":"2021-04-26T21:26:33.384Z","resourceRef":{}}]

Root cause is that image hadolint/hadolint using :latest tag uses sratch base image, so it doesn't have sh or even bash
Using a different image works ghcr.io/hadolint/hadolint:v2.3.0-alpine

This is fix now using a different image


Compile test body normally if :COMPILE-AT is :DEFINITION-TIME

This enables better reporting for compile-time warnings and errors.
I have used this locally for several months without problems, but the change could theoretically lead to problems because:

the test thunk is no longer evaluated in the null lexical environment
the value of *package* for the :run-time case is captured at macroexpansion-time instead of load-time

Both, in principle and in my experience, these don't seem like serious problems, but I still wanted to point them out.

Merged, thanks.

I reverted this commit because if broke several users:

http://report.quicklisp.org/2018-02-18/failure-report/trivialib.bdd.html#trivialib.bdd.test
http://report.quicklisp.org/2018-02-18/failure-report/cl-oauth.html#cl-oauth.tests

As far as I can't tell, it's because SBCL can't dump into a fasl the result of a NAMED-LAMBDA.

I will try to look in to the issue. Sorry for the inconvenience.

At least http://report.quicklisp.org/2018-02-18/failure-report/cl-oauth.html#cl-oauth.tests seems questionable. Its with-signed-request macro splices CLOS instances into the result form.
Similarly, http://report.quicklisp.org/2018-02-18/failure-report/trivialib.bdd.html#trivialib.bdd.test has
a with-odd-context macro which splices function objects into the result form.
I would argue that both are cases of macro programming errors that didn't surface because test bodies are not compiled. For example, with-odd-context could likely be fixed trivially by changing #'name to '#'name or '(function name) in one place.
That said, I can understand not wanting to break client code.

trivialib.bdd should no longer be a problem. See guicho271828/trivialib.bdd#1.


Helm deployment

Thank you for contributing to Retraced!
Please add a summary of your change
Does your change fix a particular issue?
Fixes #(issue)

Should rename helm-retaced folder to helm


[Bug]: Build has been failing for over a year on live website- only local netlify CLI deploys work

Summary
I am a new developer for a client whose Gatsby website hosted on Netlify has not been building or deploying automatically for over a year. Cloning the repo locally, installing node modules, and using the Netlify CLI to netlify deploy --prod builds and works perfectly to deploy changes to the site manually but automatic deploys all fail.
The repo is private on Github but our Netlify instance is set to deploy automatically from either changes in the repo or with a deploy hook from the Sanity CMS. Both of those fail.
The last successful automatic deploy from the Sanity hook was September 21, 2021 and the last successful deploy from Github was March 7, 2022.
 Cloning fresh repo
7:03:17 PM: git clone git@github.com:MAU-Estate/sanity-gatsby-blog
7:03:18 PM: Preparing Git Reference refs/heads/main
7:03:19 PM: Parsing package.json dependencies
7:03:20 PM: Different build dir detected, going to use the one specified in the Netlify configuration file: '' versus '/' in the Netlify UI
7:03:20 PM: Section completed: initializing
7:03:20 PM: Starting build script
7:03:20 PM: Installing dependencies
7:03:20 PM: Python version set to 2.7
7:03:20 PM: Attempting node version '12.18.0' from .nvmrc
7:03:21 PM: Downloading and installing node v12.18.0...
7:03:21 PM: Downloading https://nodejs.org/dist/v12.18.0/node-v12.18.0-linux-x64.tar.xz...
7:03:21 PM: Computing checksum with sha256sum
7:03:21 PM: Checksums matched!
7:03:22 PM: Now using node v12.18.0 (npm v6.14.4)
7:03:22 PM: Started restoring cached build plugins
7:03:22 PM: Finished restoring cached build plugins
7:03:22 PM: Attempting ruby version 2.7.1, read from environment
7:03:23 PM: Required ruby-2.7.1 is not installed - installing.
7:03:23 PM: Searching for binary rubies, this might take some time.
7:03:23 PM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86_64/ruby-2.7.1.tar.bz2
7:03:23 PM: Checking requirements for ubuntu.
7:03:23 PM: Requirements installation successful.
7:03:23 PM: ruby-2.7.1 - #configure
7:03:23 PM: ruby-2.7.1 - #download
7:03:24 PM: ruby-2.7.1 - #validate archive
7:03:27 PM: ruby-2.7.1 - #extract
7:03:29 PM: ruby-2.7.1 - #validate binary
7:03:29 PM: ruby-2.7.1 - #setup
7:03:30 PM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1@global
7:03:30 PM: ruby-2.7.1 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems........................................
7:03:30 PM: ruby-2.7.1 - #generating global wrappers........
7:03:30 PM: ruby-2.7.1 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.7.1
7:03:30 PM: ruby-2.7.1 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list
7:03:30 PM: ruby-2.7.1 - #generating default wrappers........
7:03:31 PM: Using /opt/buildhome/.rvm/gems/ruby-2.7.1
7:03:31 PM: Using ruby version 2.7.1
7:03:31 PM: Using PHP version 8.0
7:03:31 PM: No npm workspaces detected
7:03:31 PM: Started restoring cached node modules
7:03:31 PM: Finished restoring cached node modules
7:03:31 PM: Installing NPM modules using NPM version 6.14.4
7:03:32 PM: npm ERR! Cannot read property 'match' of undefined
7:03:32 PM: npm ERR! A complete log of this run can be found in:
7:03:32 PM: npm ERR!     /opt/buildhome/.npm/_logs/2022-12-08T00_03_32_111Z-debug.log
7:03:32 PM: Creating deploy upload records
7:03:32 PM: Error during NPM install
7:03:32 PM: Build was terminated: Build script returned non-zero exit code: 1
7:03:32 PM: Failing build: Failed to build site
7:03:32 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1 (https://ntl.fyi/exit-code-1)
7:03:32 PM: Finished processing build request in 15.173426231s

The things I’ve tried so far are:
(1) Verify that the build image is up to date - Ubuntu Focal 20.04 (default)
(2) Setting up a simplified version of the site using the same versions of Gatsby 3 and Node 12 to determine if either of those might be the issue. (They are not)
(3) Deleting package-lock.json files to see if the node modules were incompatible. This approach at least got me past the Initialization phase and into the build phase. New build fail log is the following:

12:12:14 PM: Netlify Build
12:12:14 PM: ────────────────────────────────────────────────────────────────
12:12:14 PM:
12:12:14 PM: ❯ Version
12:12:14 PM:   @netlify/build 29.11.5
12:12:14 PM:
12:12:14 PM: ❯ Flags
12:12:14 PM:   baseRelDir: true
12:12:14 PM:   buildId: 646b9417db543e0008b6650a
12:12:14 PM:   deployId: 646b9417db543e0008b6650c
12:12:14 PM:
12:12:14 PM: ❯ Current directory
12:12:14 PM:   /opt/build/repo
12:12:14 PM:
12:12:14 PM: ❯ Config file
12:12:14 PM:   /opt/build/repo/netlify.toml
12:12:14 PM:
12:12:14 PM: ❯ Context
12:12:14 PM:   branch-deploy
12:12:15 PM:
12:12:15 PM: ❯ Installing plugins
12:12:15 PM:    -<EMAIL_ADDRESS>12:12:29 PM:
12:12:29 PM: ❯ Loading plugins
12:12:29 PM:    -<EMAIL_ADDRESS>from Netlify app
12:12:33 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
12:12:31 PM: @netlify/plugin-gatsby (onPreBuild event)
12:12:31 PM: ────────────────────────────────────────────────────────────────
12:12:31 PM:
12:12:31 PM: No Gatsby cache found. Building fresh.
12:12:31 PM: Please install gatsby-plugin-netlify and enable it in your gatsby-config.js. https://www.gatsbyjs.com/plugins/gatsby-plugin-netlify/
12:12:31 PM:
12:12:31 PM: (@netlify/plugin-gatsby onPreBuild completed in 8ms)
12:12:31 PM:
12:12:31 PM: Build command from Netlify app
12:12:31 PM: ────────────────────────────────────────────────────────────────
12:12:31 PM:
12:12:31 PM: $ npm run build-web
12:12:31 PM: npm ERR! missing script: build-web
12:12:31 PM: npm ERR!
12:12:31 PM: npm ERR! Did you mean this?
12:12:31 PM: npm ERR!     build
12:12:31 PM: npm ERR! A complete log of this run can be found in:
12:12:31 PM: npm ERR!     /opt/buildhome/.npm/_logs/2023-05-22T16_12_31_176Z-debug.log
12:12:31 PM:
12:12:31 PM: "build.command" failed
12:12:31 PM: ────────────────────────────────────────────────────────────────
12:12:31 PM:
12:12:31 PM:   Error message
12:12:31 PM:   Command failed with exit code 1: npm run build-web (https://ntl.fyi/exit-code-1)
12:12:31 PM:
12:12:31 PM:   Error location
12:12:31 PM:   In Build command from Netlify app:
12:12:31 PM:   npm run build-web
12:12:31 PM:
12:12:31 PM:   Resolved config
12:12:31 PM:   build:
12:12:31 PM:     base: /opt/build/repo
12:12:31 PM:     command: npm run build-web
12:12:31 PM:     commandOrigin: ui
12:12:31 PM:     environment:
12:12:31 PM:       - MAILCHIMP_API_KEY
12:12:31 PM:       - SANITY_DEPLOY_STUDIO_TOKEN
12:12:31 PM:     publish: /opt/build/repo/web/public
12:12:31 PM:     publishOrigin: ui
12:12:31 PM:   functionsDirectory: /opt/build/repo/web/functions
12:12:31 PM:   plugins:
12:12:31 PM:     - inputs: {}
12:12:31 PM:       origin: ui
12:12:31 PM:       package: '@netlify/plugin-gatsby'
12:12:33 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
12:12:33 PM: Failing build: Failed to build site
12:12:33 PM: Finished processing build request in 1m5.078s

gatsby-config.js file is the following:
// Load variables from `.env` as soon as possible
require('dotenv').config({
  path: `.env.${process.env.NODE_ENV || 'development'}`,
})

const clientConfig = require('./client-config')

const isProd = process.env.NODE_ENV === 'production'

module.exports = {
  flags: {
    FAST_DEV: true,
    DEV_SSR: false,
  },
  plugins: [
    'gatsby-plugin-postcss',
    'gatsby-plugin-react-helmet',
    {
      resolve: `gatsby-plugin-sharp`,
      options: {
        defaults: {
          formats: [`auto`, `webp`],
          placeholder: `blurred`,
          defaultQuality: 50,
          backgroundColor: `transparent`,
        },
      },
    },
    `gatsby-transformer-sharp`,
    `gatsby-plugin-image`,
    {
      resolve: `gatsby-plugin-purgecss`,
      options: {
        printRejected: false,
        tailwind: true,
      },
    },
    {
      resolve: 'gatsby-plugin-svgr',
      options: {
        prettier: true,
        svgo: true,
        replaceAttrValues: {
          '#000000': 'currentColor',
          '#000': 'currentColor',
        },
      },
    },
    `gatsby-plugin-modal-routing-3`,
    {
      resolve: 'gatsby-plugin-sanity-image',
      options: {
        ...clientConfig.sanity,
        customImageTypes: ['SanityPreviewImage', 'SanityFigure', 'SanitySlide'],
        defaultImageConfig: {
          quality: 35,
          maxWidth: 1000,
          fit: 'clip',
          auto: 'format',
        },
      },
    },
    {
      resolve: 'gatsby-source-sanity',
      options: {
        ...clientConfig.sanity,
        token: process.env.SANITY_READ_TOKEN,
        watchMode: !isProd,
        overlayDrafts: !isProd,
      },
    },
    {
      resolve: `gatsby-plugin-manifest`,
      options: {
        name: `maryannunger.com`,
        short_name: `maryannunger`,
        description: 'Website for the estate of Mary Ann Unger.',
        start_url: `/`,
        background_color: `#1f1f1f`,
        theme_color: `#1f1f1f`,
        display: `minimal-ui`,
        icon: 'src/assets/images/favicon.png',
      },
    },
    {
      resolve: `gatsby-plugin-netlify`,
    },
  ],
}

Any help or suggestions would be so greatly appreciated. Thanks for reading!
Steps to reproduce

Create a Gatsby 3 & Node 12 site within a web folder in the root project
Deploy to Netlify via Github CD
Local manual deploys work, Netlify automatic deploys do not

A link to a reproduction repository
https://github.com/MAU-Estate/public-testing-repo
Plugin version
<EMAIL_ADDRESS>More information about your build

[ ] I am building using the CLI
[X] I am building using file-based configuration (netlify.toml)

What OS are you using?
None
Your netlify.toml file

`netlify.toml`
[build]
  functions = "functions"
[[redirects]]
  from = "/api/*"
  to = "/.netlify/functions/:splat"
  status = 200

Configuration

`gatsby-config.js` and options
// Load variables from `.env` as soon as possible
require('dotenv').config({
  path: `.env.${process.env.NODE_ENV || 'development'}`,
})

const clientConfig = require('./client-config')

const isProd = process.env.NODE_ENV === 'production'

module.exports = {
  flags: {
    FAST_DEV: true,
    DEV_SSR: false,
  },
  plugins: [
    'gatsby-plugin-postcss',
    'gatsby-plugin-react-helmet',
    {
      resolve: `gatsby-plugin-sharp`,
      options: {
        defaults: {
          formats: [`auto`, `webp`],
          placeholder: `blurred`,
          defaultQuality: 50,
          backgroundColor: `transparent`,
        },
      },
    },
    `gatsby-transformer-sharp`,
    `gatsby-plugin-image`,
    {
      resolve: `gatsby-plugin-purgecss`,
      options: {
        printRejected: false,
        tailwind: true,
      },
    },
    {
      resolve: 'gatsby-plugin-svgr',
      options: {
        prettier: true,
        svgo: true,
        replaceAttrValues: {
          '#000000': 'currentColor',
          '#000': 'currentColor',
        },
      },
    },
    `gatsby-plugin-modal-routing-3`,
    {
      resolve: 'gatsby-plugin-sanity-image',
      options: {
        ...clientConfig.sanity,
        customImageTypes: ['SanityPreviewImage', 'SanityFigure', 'SanitySlide'],
        defaultImageConfig: {
          quality: 35,
          maxWidth: 1000,
          fit: 'clip',
          auto: 'format',
        },
      },
    },
    {
      resolve: 'gatsby-source-sanity',
      options: {
        ...clientConfig.sanity,
        token: process.env.SANITY_READ_TOKEN,
        watchMode: !isProd,
        overlayDrafts: !isProd,
      },
    },
    {
      resolve: `gatsby-plugin-manifest`,
      options: {
        name: `maryannunger.com`,
        short_name: `maryannunger`,
        description: 'Website for the estate of Mary Ann Unger.',
        start_url: `/`,
        background_color: `#1f1f1f`,
        theme_color: `#1f1f1f`,
        display: `minimal-ui`,
        icon: 'src/assets/images/favicon.png',
      },
    },
    {
      resolve: `gatsby-plugin-netlify`,
    },
  ],
}

Environment

Environment
# Paste output from `npx envinfo` here.

Gatsby info

gatsby info
# Paste output from `gatsby info` here.

Your _redirects file

`_redirects`
/free-standing /work
/wall-mounted /work
/small-bronzes  /work
/public-art     /work
/works-on-paper /work
/bio            /#intro
/obituary       /#intro
https://maue.netlify.app/*            https://www.maryannunger.com/:splat 301!
https://www.maryannungerestate.com/*  https://www.maryannunger.com/:splat 301!
https://maryannungerestate.com/*      https://www.maryannunger.com/:splat 301!

Builds logs (or link to your logs)

Build logs
> 12:12:14 PM: Netlify Build
12:12:14 PM: ────────────────────────────────────────────────────────────────
12:12:14 PM:
12:12:14 PM: ❯ Version
12:12:14 PM:   @netlify/build 29.11.5
12:12:14 PM:
12:12:14 PM: ❯ Flags
12:12:14 PM:   baseRelDir: true
12:12:14 PM:   buildId: 646b9417db543e0008b6650a
12:12:14 PM:   deployId: 646b9417db543e0008b6650c
12:12:14 PM:
12:12:14 PM: ❯ Current directory
12:12:14 PM:   /opt/build/repo
12:12:14 PM:
12:12:14 PM: ❯ Config file
12:12:14 PM:   /opt/build/repo/netlify.toml
12:12:14 PM:
12:12:14 PM: ❯ Context
12:12:14 PM:   branch-deploy
12:12:15 PM:
12:12:15 PM: ❯ Installing plugins
12:12:15 PM:    -<EMAIL_ADDRESS>12:12:29 PM:
12:12:29 PM: ❯ Loading plugins
12:12:29 PM:    -<EMAIL_ADDRESS>from Netlify app
12:12:33 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
12:12:31 PM: @netlify/plugin-gatsby (onPreBuild event)
12:12:31 PM: ────────────────────────────────────────────────────────────────
12:12:31 PM:
12:12:31 PM: No Gatsby cache found. Building fresh.
12:12:31 PM: Please install `gatsby-plugin-netlify` and enable it in your gatsby-config.js. https://www.gatsbyjs.com/plugins/gatsby-plugin-netlify/
12:12:31 PM:
12:12:31 PM: (@netlify/plugin-gatsby onPreBuild completed in 8ms)
12:12:31 PM:
12:12:31 PM: Build command from Netlify app
12:12:31 PM: ────────────────────────────────────────────────────────────────
12:12:31 PM:
12:12:31 PM: $ npm run build-web
12:12:31 PM: npm ERR! missing script: build-web
12:12:31 PM: npm ERR!
12:12:31 PM: npm ERR! Did you mean this?
12:12:31 PM: npm ERR!     build
12:12:31 PM: npm ERR! A complete log of this run can be found in:
12:12:31 PM: npm ERR!     /opt/buildhome/.npm/_logs/2023-05-22T16_12_31_176Z-debug.log
12:12:31 PM:
12:12:31 PM: "build.command" failed
12:12:31 PM: ────────────────────────────────────────────────────────────────
12:12:31 PM:
12:12:31 PM:   Error message
12:12:31 PM:   Command failed with exit code 1: npm run build-web (https://ntl.fyi/exit-code-1)
12:12:31 PM:
12:12:31 PM:   Error location
12:12:31 PM:   In Build command from Netlify app:
12:12:31 PM:   npm run build-web
12:12:31 PM:
12:12:31 PM:   Resolved config
12:12:31 PM:   build:
12:12:31 PM:     base: /opt/build/repo
12:12:31 PM:     command: npm run build-web
12:12:31 PM:     commandOrigin: ui
12:12:31 PM:     environment:
12:12:31 PM:       - MAILCHIMP_API_KEY
12:12:31 PM:       - SANITY_DEPLOY_STUDIO_TOKEN
12:12:31 PM:     publish: /opt/build/repo/web/public
12:12:31 PM:     publishOrigin: ui
12:12:31 PM:   functionsDirectory: /opt/build/repo/web/functions
12:12:31 PM:   plugins:
12:12:31 PM:     - inputs: {}
12:12:31 PM:       origin: ui
12:12:31 PM:       package: '@netlify/plugin-gatsby'
12:12:33 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
12:12:33 PM: Failing build: Failed to build site
12:12:33 PM: Finished processing build request in 1m5.078s

Function logs

Function logs
# Paste logs here

Was able to get past this specific issue. Deleting package-lock.json in the root but leaving those files within the subdirectories being built seems to get us past this. Will open a new issue for new problems if they occur.


feat: Print local network URL in log

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
This is draft pull request for this https://github.com/open-webui/open-webui/issues/2888
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?

https://github.com/open-webui/docs/pull/105

[x] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[x] Testing: Have you written and run sufficient tests for validating the changes?

It appears that the backend for server start up does not come with a test file. See manual test in coming section.

[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Print local network URL in log for local devices to access UI

Description
This enhance the server startup process to display the local network IP address and port in the log, making it easier to access the locally hosted LLM from other devices on the same network. There are better ways to extract the IP and port information, this is a proof of concept.
Added

Print local network URL in log for local devices to access UI

Additional Information
This is draft pull request for this https://github.com/open-webui/open-webui/issues/2888
Screenshots or Videos
Manuel test
While not connect to a network, the <IP_ADDRESS> address is show (localhost)

This is typical view when host device is connect to a network

Here is view connected from iPhone in the same local network

Here is view connected from Mac in the same local network

Please advise if there is a better way to extract the port from args


[AutoPR cost-management/resource-manager] PR - Introduce new API version (2019-01-01) with new (Export-related APIs) introduced

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5127

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2924


Create new testsuite to cover rfs on Testlodge

we need to add test cases from scratch on testlodge to cover all the rfs features.
Docs: https://github.com/threefoldtech/rfs

currently reviewing the created test suite and fixing some test cases
and started to create the missing sections for parts which was not covered
testsuite

@khaledyoussef24
please add estimate

finished creating the test suite and testing only will try to create the flist on zdb machine today
RFS testsuite

finished creating the test suite and testing only will try to create the flist on zdb machine today
RFS testsuite

created an flist on zdb and created test section for it on test lodge


Refactor Request: Statistics Outside data.json

Can you move the history outside of the data.json file? I like to synchronize certain settings across Vaults and it can be distracting/impractical to have keyboard statistics sync, too. Instead, like for example various complements which keeps a histories.json, could the stats be their own json file?
Small implementational request, I know, but it would save me a small headache and keep the data.json file more aligned with the intent of it being a "config" file. Much appreciated!

Oh weird, good to know since I don't use sync.
I see now how odd what I want is - to sync settings across different vaults, not just the same vault in different places - so I respect not supporting this.


Fix README consistency

Keep process names consistent
Add missing command
Consistent control socket path

Signed-off-by: Joe Gross<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 52.61%

Merging [#859][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.18%

2 files (not in diff) in protobuf/plugin were modified. more

Misses +5
Partials -3
Hits -2

3 files (not in diff) in manager/orchestrator were modified. more

Misses +7
Partials +3
Hits -10

2 files (not in diff) in ca were modified. more

Misses +5
Partials +4
Hits -9

@@             master       #859   diff @@
==========================================
  Files            70         70
  Lines         11135      11135
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           5880       5859    -21
- Misses         4432       4449    +17
- Partials        823        827     +4

[][cc-pull]

Powered by Codecov. Last updated by [9b1bd15...1e4dfbd][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/9b1bd1519779fd1f14be731fda4a611a173c46f2...1e4dfbd135e27cc8408e5f4db919b8c1b907966d
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/859?src=pr

LGTM


Odd naming convention when missing site_env

Just found this as odd wording in an error response. What's siteish?
Not enough arguments (missing: "siteish, name, value").

https://github.com/pantheon-systems/terminus-secrets-manager-plugin/blob/952a52b06f9a28baeb78427d739c1daa4866632b/src/Commands/SiteSetCommand.php#L33

Tracking internally as LOPS-2255

Resolved in the latest release :) TY


Pods Unable to be created due to being unable to create Endpoints

Bug report

General Information

Cilium version (run cilium version)

Client: 1.9.5 079bdaf 2021-03-10T13:12:19-08:00 go version go1.15.8 linux/amd64
Daemon: Not responding

Kernel version (run uname -a)

Linux ip-172-18-50-73.ap-southeast-2.compute.internal 4.14.219-161.340.amzn2.x86_64 #1 SMP Thu Feb 4 05:54:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Orchestration system version in use (e.g. kubectl version, Mesos, ...)

Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.9-eks-d1db3c", GitCommit:"d1db3c46e55f95d6a7d3e5578689371318f95ff9", GitTreeState:"clean", BuildDate:"2020-10-20T22:18:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Running 1.18 on eks

Link to relevant artifacts (policies, deployments scripts, ...)

Logs from the cilium agent,
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=75062f71-8b83-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context canceled" name=endpoint-delete parallelRequests=4 subsys=rate uuid=75062f71-8b83-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context canceled" name=endpoint-delete processingDuration=0s subsys=rate totalDuration=1m30.000121368s uuid=75062f71-8b83-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=ab236f72-8b83-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context canceled" name=endpoint-delete parallelRequests=4 subsys=rate uuid=ab236f72-8b83-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context canceled" name=endpoint-delete processingDuration=0s subsys=rate totalDuration=1m30.00014872s uuid=ab236f72-8b83-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" maxWaitDuration=15s name=endpoint-create parallelRequests=4 subsys=rate uuid=e1391011-8b83-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context deadline exceeded" maxWaitDuration=15s name=endpoint-create parallelRequests=4 subsys=rate uuid=e1391011-8b83-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context deadline exceeded" name=endpoint-create processingDuration=0s subsys=rate totalDuration=15.00019634s uuid=e1391011-8b83-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=ea2e132e-8b83-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context canceled" name=endpoint-delete parallelRequests=4 subsys=rate uuid=ea2e132e-8b83-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context canceled" name=endpoint-delete processingDuration=0s subsys=rate totalDuration=1m30.000130175s uuid=ea2e132e-8b83-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=20433800-8b84-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context canceled" name=endpoint-delete parallelRequests=4 subsys=rate uuid=20433800-8b84-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context canceled" name=endpoint-delete processingDuration=0s subsys=rate totalDuration=1m30.000134149s uuid=20433800-8b84-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" maxWaitDuration=15s name=endpoint-create parallelRequests=4 subsys=rate uuid=5646d7e5-8b84-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context deadline exceeded" maxWaitDuration=15s name=endpoint-create parallelRequests=4 subsys=rate uuid=5646d7e5-8b84-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context deadline exceeded" name=endpoint-create processingDuration=0s subsys=rate totalDuration=15.000224477s uuid=5646d7e5-8b84-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=5f3bd06e-8b84-11eb-bee1-0610ca3146ec
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context canceled" name=endpoint-delete parallelRequests=4 subsys=rate uuid=5f3bd06e-8b84-11eb-bee1-0610ca3146ec
level=info msg="API call has been processed" error="timed out while waiting to be served with 4 parallel requests: context canceled" name=endpoint-delete processingDuration=0s subsys=rate totalDuration=1m30.000156491s uuid=5f3bd06e-8b84-11eb-bee1-0610ca3146ec waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=9566469f-8b84-11eb-bee1-0610ca3146ec

Interestingly, cilium endpoint list also times out,
# cilium endpoint list
Error: cannot get endpoint list: Cilium API client timeout exceeded

When creating pods on that particular node, we get
Events:
  Type     Reason                  Age                   From     Message
  ----     ------                  ----                  ----     -------
  Warning  FailedCreatePodSandBox  103s (x34 over 109m)  kubelet  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "19a749086f762bdf161cba2587e31ad148f9b45b545da5f977cde406c1e46812" network for pod "pelican-5cd8549595-drz7n": networkPlugin cni failed to set up pod "pelican-5cd8549595-drz7n_pelican" network: unable to create endpoint: response status code does not match any response statuses defined for this endpoint in the swagger spec (status 429): {}

Spinning up pods on other nodes seems to be fine, and if we restart the cilium agent pod on that particular kubernetes node, it seems to be fine.

Generate and upload a system zip:

curl -sLO https://git.io/cilium-sysdump-latest.zip && python cilium-sysdump-latest.zip

cilium-sysdump-20210323-140231.zip
How to reproduce the issue
I'm not sure on how to reproduce it, but we are consistently getting it every other day in our kubernetes cluster.

We may have a bug in the rate limiter. /cc @tgraf
I see four endpoint-delete API requests that are followed by Delete endpoint request:
2021-03-23T00:37:58.394498080Z level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=03f563cd-8b70-11eb-bee1-0610ca3146ec
2021-03-23T00:37:58.394519995Z level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=03f563cd-8b70-11eb-bee1-0610ca3146ec waitDurationTotal="63.548µs"
2021-03-23T00:37:58.394524220Z level=info msg="Delete endpoint request" id="container-id:3b8947bddc02f426ba6d37d6fc5a28c6b66dfd35d5f20fd30c28560ab4ee13ad" subsys=daemon

However, there doesn't seem to be any corresponding API call has been processed message. Subsequent endpoint-delete API requests are rejected because there are already 4 requests being processed.
So it's as if the API rate limiter somehow missed the end of the endpoint-delete processing and assumes they are being processed indefinitely.

This might be a completely wrong and misguided comment (please disregard if it is, I don't have any experience with this code base)
What was interesting to me was that cilium endpoint list times out,
# cilium endpoint list
Error: cannot get endpoint list: Cilium API client timeout exceeded

This indicated to me it might be more to do with some underlying lock or resource contention rather than rate limiting?

Is there any update on this issue @pchaigno @tgraf ?

I am experiencing the same issue in 1.10.0

Cilium version: 1.10.0.rc1
Kernel version: Linux ip-172-18-46-124 5.4.0-1045-aws #47-Ubuntu SMP Tue Apr 13 07:02:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Orchestration system version in use: Using EKS, with Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.9-eks-d1db3c", GitCommit:"d1db3c46e55f95d6a7d3e5578689371318f95ff9", GitTreeState:"clean", BuildDate:"2020-10-20T22:18:07Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Logs in the cilium pod
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context deadline exceeded" maxWaitDuration=15s name=endpoint-create parallelRequests=3 subsys=rate uuid=f81a478b-d3ab-412c-8c7b-d2f13f124c76
level=info msg="API call has been processed" error="timed out while waiting to be served with 3 parallel requests: context deadline exceeded" name=endpoint-create processingDuration=0s subsys=rate totalDuration=15.00054719s uuid=f81a478b-d3ab-412c-8c7b-d2f13f124c76 waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=3c7978c3-6843-495c-b85b-7a35c2a527cd
level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=3c7978c3-6843-495c-b85b-7a35c2a527cd waitDurationTotal="61.222µs"
level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="2.832µs" subsys=rate totalDuration="75.93µs" uuid=3c7978c3-6843-495c-b85b-7a35c2a527cd waitDurationTotal="61.222µs"
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=b1c8e6b6-00cb-4414-ace7-42e403d4e44b
level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=b1c8e6b6-00cb-4414-ace7-42e403d4e44b waitDurationTotal="66.027µs"
level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="2.91µs" subsys=rate totalDuration="81.83µs" uuid=b1c8e6b6-00cb-4414-ace7-42e403d4e44b waitDurationTotal="66.027µs"
level=info msg="Processing API request with rate limiter" maxWaitDuration=15s name=endpoint-create parallelRequests=3 subsys=rate uuid=edfca395-99d8-4949-bfe8-57ecf36c3923
level=warning msg="Not processing API request. Wait duration for maximum parallel requests exceeds maximum" error="context deadline exceeded" maxWaitDuration=15s name=endpoint-create parallelRequests=3 subsys=rate uuid=edfca395-99d8-4949-bfe8-57ecf36c3923
level=info msg="API call has been processed" error="timed out while waiting to be served with 3 parallel requests: context deadline exceeded" name=endpoint-create processingDuration=0s subsys=rate totalDuration=15.001201443s uuid=edfca395-99d8-4949-bfe8-57ecf36c3923 waitDurationTotal=0s
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=d207fea3-e98b-4b47-88d1-d872afa251e2
level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=d207fea3-e98b-4b47-88d1-d872afa251e2 waitDurationTotal="59.936µs"
level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="2.944µs" subsys=rate totalDuration="74.803µs" uuid=d207fea3-e98b-4b47-88d1-d872afa251e2 waitDurationTotal="59.936µs"
level=info msg="Processing API request with rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=58932521-9a9b-4131-a2f9-c17040df81d5
level=info msg="API request released by rate limiter" name=endpoint-delete parallelRequests=4 subsys=rate uuid=58932521-9a9b-4131-a2f9-c17040df81d5 waitDurationTotal="61.334µs"
level=info msg="API call has been processed" error="endpoint not found" name=endpoint-delete processingDuration="3.449µs" subsys=rate totalDuration="76.034µs" uuid=58932521-9a9b-4131-a2f9-c17040df81d5 waitDurationTotal="61.334µs"
level=info msg="Processing API request with rate limiter" maxWaitDuration=15s name=endpoint-create parallelRequests=3 subsys=rate uuid=94c784f6-4e20-4de7-8727-6c250bb7cbc3

No pod is able to be able to scheduled on that node.
➜  ~ k exec -it cilium-rq95g  -n kube-system cilium endpoint list
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Defaulted container "cilium-agent" out of: cilium-agent, wait-for-node-init (init), clean-cilium-state (init)
Error: cannot get endpoint list: Cilium API client timeout exceeded

command terminated with exit code 1
➜  ~

Delete the cilium pod on the node seems to be working again.

I'm getting it on EKS 1.19 with aws-cni chain mode as well, and yes deleting the cilium pod on the node makes it work again.
sysdump: cilium-sysdump-20210625-114341.zip

Looks like a deadlock from the sysdump:
goroutine 20725 [semacquire, 108 minutes]:
sync.runtime_SemacquireMutex(0xc00037fb3c, 0x406400, 0x0)
	/usr/local/go/src/runtime/sema.go:71 +0x47
sync.(*RWMutex).RLock(...)
	/usr/local/go/src/sync/rwmutex.go:50
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).unconditionalRLock(...)
	/go/src/github.com/cilium/cilium/pkg/endpoint/lock.go:60
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).HasLabels(0xc00037fb00, 0x0, 0x0)
	/go/src/github.com/cilium/cilium/pkg/endpoint/endpoint.go:1018 +0xb3
github.com/cilium/cilium/daemon/cmd.(*Daemon).getEndpointList.func1(0xc00225e068, 0xc000ec1070, 0xc004503800, 0xc0045037a0)
	/go/src/github.com/cilium/cilium/daemon/cmd/endpoint.go:107 +0x75
created by github.com/cilium/cilium/daemon/cmd.(*Daemon).getEndpointList
	/go/src/github.com/cilium/cilium/daemon/cmd/endpoint.go:105 +0x1c5

goroutine 26571 [semacquire, 96 minutes]:
sync.runtime_SemacquireMutex(0xc00037f234, 0xc004e9c400, 0x1)
	/usr/local/go/src/runtime/sema.go:71 +0x47
sync.(*Mutex).lockSlow(0xc00037f230)
	/usr/local/go/src/sync/mutex.go:138 +0x105
sync.(*Mutex).Lock(...)
	/usr/local/go/src/sync/mutex.go:81
sync.(*RWMutex).Lock(0xc00037f230)
	/usr/local/go/src/sync/rwmutex.go:98 +0x90
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).lockAlive(0xc00037f200, 0x289bf60, 0xc004e9c5e8)
	/go/src/github.com/cilium/cilium/pkg/endpoint/lock.go:21 +0x3a
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).SetRegenerateStateIfAlive(0xc00037f200, 0xc00162e6c0, 0x0, 0x0, 0xc004e9c640)
	/go/src/github.com/cilium/cilium/pkg/endpoint/policy.go:517 +0x2f
github.com/cilium/cilium/pkg/endpoint.(*Endpoint).RegenerateIfAlive(0xc00037f200, 0xc00162e6c0, 0xc004e9c7b8)
	/go/src/github.com/cilium/cilium/pkg/endpoint/policy.go:556 +0x50
github.com/cilium/cilium/pkg/endpointmanager.(*EndpointManager).RegenerateAllEndpoints.func1(0xc00162e6c0, 0xc00221f0c0, 0xc00037f200)
	/go/src/github.com/cilium/cilium/pkg/endpointmanager/manager.go:435 +0x35
created by github.com/cilium/cilium/pkg/endpointmanager.(*EndpointManager).RegenerateAllEndpoints
	/go/src/github.com/cilium/cilium/pkg/endpointmanager/manager.go:434 +0x225

Hello @ldelossa, any news on this issue ? we are facing the same behavior on some of our clusters using cilium v1.10.7

@solarnz @othmane399 can you check if this is fixed with v1.10.10? Thank you

@aanm Can you please provide the details of the 1.9 version where the fix was backported?


A numerical experiment problem of darcy flow experiment.

Hi Shuhao.
Great of your work. I am running your ex2_darcy.py, the L2 loss is about 0.00914. I tried many times and the result is similar, never reach 0.00847 shown in your paper. The fine resolution is 211 and coarse resolution is 61. Is it normal?
Thanks.

😂 this is totally possible. The result reported in the paper was obtained circa mid-May (for example the eval notebook here: https://github.com/scaomath/galerkin-transformer/blob/main/eval/ex2_darcy_eval.ipynb), and it turned out I never got chance to double check over 50 branches in my dev repo after that (teaching two class back in Spring 2021, the time near the final was crazy).
After June, the biggest change is that I found a careless bug fixed in 42f17f10dd9c47885113cdaf55079e24722cb17a , and it possibly attributes to the degradation of the benchmark. The bug essentially said that the evaluation is sensitive to the eps hyperparam used in normalization (including layer norm) because truncation error stability in FP32 is an issue for these tasks.
I will clean the repo during the winter break and update with you the results.

Thank you for your response.  Your method improved a lot in Burger's equation. I am looking forward to your result in the Darcy flow experiment.


Update sbt-scalajs, scalajs-compiler to 1.0.1

Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler

from 0.6.32 to 1.0.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

labels: library-update, semver-major

superseded by #341

Wait, it might be helpful to stay on 1.0.1 because of https://github.com/playframework/play-json/pull/454#discussion_r429558406 ?

The Scala.js upgrade requires more work
https://travis-ci.com/github/playframework/twirl/jobs/340885534#L765

see #362


[DS-3841] enable CORS header for security controller

This PR contains:

setup current user into context object
enable and expose the cors header for security controller

Please rebase this PR against the latest master branch.  The master branch now requires adherence to our new Java Code Style documented at: https://wiki.duraspace.org/display/DSPACE/Code+Style+Guide
If you have any questions, feel free to ask in this PR or on our Slack: https://wiki.duraspace.org/display/DSPACE/Slack

Closing in favor of #1983 (rebased version).  The other PR was merged, and it included these commits


ISPN-9437 translation hotrod properties into spring yaml

Can't be integrated yet. I'm modify at the same time infinispan for the 9.4 release.
Will be mergeable with Infinispan 9.4.0.Final
https://issues.jboss.org/browse/ISPN-9437
Related to  https://github.com/infinispan/infinispan-spring-boot/issues/48

@karesti Is this ready to be reviewed? The do not integrate tag is still on

@galderz can be reviewed

@galderz not in this PR

@galderz I would like to merge and release 2.0.0 😄


[Y2K-1481] Format add to channels page correctly on mobile

cc @keybase/y2ksquad

@jakob223 this might be affected by your ChannelInfo changes...

It would probably be easier for you to do it since you did the refactor.

@buoyad ready to approve?


[BUG]Old Bloxstrap Location download delete.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[X] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v281
What problem did you encounter?
Hello there, I counter this problem as bloxstrap or my problem. Yesterday My AntiVirus Detected the bloxstrap for IDP.Generic so i dont know what to do and i cant play roblox. So i pop up like "Bloxstrap has been installed this location before and is still present, however the installer cannot overwrite the old executable"

Bloxstrap Log
N/A

first, you checked the fourth box
second, have you tried doing what the window says


Per rank mlflow tracking location and updating fcn_afno config for easier benchmarking

Modulus Pull Request
Description

Small PR that adds:

per rank mlflow tracking location to fix multi-gpu race conditions
small updates to fcn_afno config for easier benchmarking

Closes https://github.com/NVIDIA/modulus-launch/issues/66
Checklist

[x] I am familiar with the Contributing Guidelines.
[ ] The CHANGELOG.md is
up to date with these changes.

Dependencies

/blossom-ci

/blossom-ci


pull request for e2e test at 11/25/2016 05:26:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Added output for the affiliated trajectories id

Now the output textfile can include the id of the trajectories that are being clustered.

Hi, thanks for sending the pull request. Can you explain a bit more about this feature? How can the clustering result be associated with the trajectories ids since this is a partition-based algorithm. One trajectory id can be associated with multiple clusters, one cluster can also be associated with multiple trajectories. Thanks!

The purpose of the feature is to find out/visualize the cluster contains which trajectory. The picture below is an example of this feature. Cheers!


Test failure: dashboard should show a Gritter notification should show a close button when hovering over it

/home/mdz/.rvm/rubies/ruby-1.8.7-p352/bin/ruby -S rspec ./spec/integration/dashboard_spec.rb
......F
Failures:

dashboard should show a Gritter notification should show a close button when hovering over it
Failure/Error: page.execute_script(<<"BLORF")
Selenium::WebDriver::Error::UnhandledError:
Script execution failed. Script:     socket.$events.viewer({
type:'view/github',
via:'github',
timestamp:1320881456139,
action:'update',
obj:{
source:'github_view',
data:{
id:'smurthas/Skeleton-Viewer',
manifest:'smurthas/Skeleton-Viewer/manifest.app',
at:'2011/11/09 15:23:33 -0800',
viewer:'photos',
_id:'4ebb0ce297e5172111034f6b'
}
}
});
;
data is not defined
Backtrace:
0x43f80e
0x4320ae
0x4327e1
0x41fd42
0x42c843
0x41b397
0x484df8
0x4861f2
0x486491
start_thread [0x7f55d68eeefc]
0x7f55d3f2589d
./spec/integration/dashboard_spec.rb:74

Finished in 11.53 seconds
7 examples, 1 failure
Failed examples:
rspec ./spec/integration/dashboard_spec.rb:71 # dashboard should show a Gritter notification should show a close button when hovering over it
rake aborted!
ruby /home/mdz/.rvm/rubies/ruby-1.8.7-p352/bin/ruby -S rspec ./spec/integration/dashboard_spec.rb failed
Tasks: TOP => default => spec
(See full trace by running task with --trace)

I helped smurthas create this test case in the first place, and I'm explaining the client tests to Singletons, so I'll take this one on.

This test got blown away


Error while compiling RNSweetAlertPackage.java for Android

Hi,
There seems to be a bug when compiling for android, more specifically in RNSweetAlertPackage.java, on line 23.
Output from ./gradlew installDebug:
[snip]/node_modules/react-native-sweet-alert/android/src/main/java/com/clipsub/RNSweetAlert/RNSweetAlertPackage.java:23: error: method does not override or implement a method from a supertype
@Override
^
1 error
:react-native-sweet-alert:compileReleaseJavaWithJavac FAILED

Removing line 23 from RNSweetAlertPackage.java seems to fix the issue.
Steps to reproduce:

react-native init SweetAlertTest
cd SweetAlertTest && yarn add react-native-sweet-alert
react-native link
(edit AndroidManifest.xml as described here)
react-native run-android

New version has been released. It is now fixed.


Simulate interaction states

Would it be possible to simulate :hover/:active/:focus states when rendering? It seems like many sketch symbol libraries include some combination of these states for interactive components like buttons and inputs (e.g. a default button, a hovered button, and an active button). Right now to do this with html-sketchapp you have to build a way to manually force these states into your component code (e.g. a special .focused class). It would be nice if there was an API that could direct html-sketchapp to simulate these states instead. I'm thinking something like a "data-sketch-simulate-hover" attribute that you add to the "data-sketch-symbol" wrapper.

Is it possible to force hover state from JS? If it is, then it might be a good idea to add it to html-sketchapp. If it isn't and it has to be done via puppeteer, I'd leave it to tools like html-sketchapp-cli or custom integrations like html-sketchapp-style-guide.

Looks like this is in fact a job for puppeteer. I didn't realize the generic nature of html2asketch, I'll consider reopening this discussion on html-sketchapp-cli. Thanks!


Create README_odia.md

This was a good first issue. The issue stated about adding new languages. This is my contribution towards the Open source and i added the readme file in odia language.

If you read the issue about adding more languages, you'll notice that it's talking about translating the app, not the README file. If you want to translate the app to Odia language, please create a translation file and submit another PR.


regenerating a palette

If I generate a custom palette, say "user_palette", then later, I want to regenerate it, I get:
Chroma::Errors::PaletteDefinedError (Palette `user_palette' already exists):

Is there a way to support regenerating an already existing palette?

I did try some simple changes and it seems to work. See here: https://github.com/jfairbank/chroma/compare/master...seiferteric:eric-wip?expand=1
Not sure if there is more I need to do though for a pull request, or if there was a reason redefining the palette was disallowed in the first place.

Hi, @seiferteric.
Honestly, I can't remember why I decided to prevent redefining palettes besides that use case didn't make sense to me. I'm curious why you want to redefine a palette, but I'm not necessarily opposed to opening it up to redefinition.

Not sure if I am just using it incorrectly, but I just wanted to create a palette to get N unique colors (starting from a base color and rotate 360/N for each). N may increase, and I have no need for the old palette, so I just redefine the palette for the new N.

Sorry I'm lagging on responses. I've been out for conferences and other things.
I'm not fully opposed to this change, but I do like the "staticness" of setting it once. I'm curious how you're wanting to call it, and if maybe defining palettes and using them at the same time would work better?
Some new feature like:
'red'.paint.custom_palette do
  spin 60
  spin 180
end

However if you need to reuse it in other places, then that may not be as nice. Again, I'm open to removing the error entirely since there isn't a strong reason to really have it there.

That could work... Would just be more efficient to avoid redefining the palette each time it is needed. To further clarify what I am doing, I have a web application where each user needs a unique color. The only time the palette will change is when a new user is added, or one removed (fairly rare, since this is for a small business). So I (re)create a user_palette anytime a change in the users count happens. Using your suggested code above though, I could just store the color in the user model and not keep the palette around at all.

Cool. I'm on vacation through the rest of the week, but I can dive into adding a new feature like this when I get back home. I'm not ultimately opposed to dropping the error anyway, but this at least avoids bumping the major version.

@seiferteric Finally got the custom_palette method implemented in the latest release. Try it out and let me know if you have any issues. Closing this issue. Thanks!


feat(CX-3158): add screen tracking

This PR resolves CX-3158
Description

PR Checklist

[ ] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

add screen tracking to my collection home feed onboarding -daria

Need help with something? Have a look at our docs, or get in touch with us.

Nice


Update artifact icons to match visual style of the other map icons

Instead of using images of the Somersloop and Mercer Sphere for icons some custom icons should be created to better match the style of the rest of the map markers.
I am by no means a professional, but here is an example for the Somersloop I whipped up real quick.

Hi,
Thanks for the feedback! We are working on the next batch of icons for the map which includes Somersloops, Mercer spheres and geysers amongst other things. We needed to launch with something that’s why we opted for the in game images :)

@bro15047 New icons just made it to staging can you tell me what do you think of those: https://staging.satisfactorymap.com/#199140.0390625;65223.4375;7;808976398 ?

Looks good, that somersloop is a difficult one to mock up for sure.


Can classifier update() be faster than training from scratch?

I am building a dataset and am training NaiveBayesClassifier as the dataset grows. Instead of retraining the classifier every time after adding few new entries, I was hoping to use the update() method just to add new entries and retrain the model with them, in order to cut training time when new data added. What I discovered that loading a pickled trained classifier and updating it just with new entries is not faster than re-training it from scratch. Re-reading the docs they do say that update() "Update the classifier with new training data and re-trains the classifier", which implies re-training on the entire data set...
Question: is there such thing as incremental re-training, or realistically it is processing the entire dataset from scratch, every time I want to update the classifier with new data?

Hey, i have a question. How do you save the classifications ? I have sqlite database with string and status, but how to save the classifications itself ?

#136 is now merged and released.


sendMessage method has high delay time

Hello.
I'm using my bot via webhooks and incoming messages from telegram are being handled by express js:
 app.post(`/bot${token}`, (req, res) => {
        bot.processUpdate(req.body);
        res.sendStatus(200);
 });

Then I'm trying to respond to telegram by using sedn message method
bot.on('message', (message) => {
      let startTime = (new Date()).getTime();
      bot.sendMessage(message.chat.id, 'Some text').then(payload => {
          let endTime = (new Date()).getTime();
          console.log(`Send time ${endTime - startTime} milliseconds`);
      });
});

My bot receives messages very fas. However, responding via sendMessage takes from 2-5 seconds.
i'm using NodeJS v.8.6.0
OS is RHEL 7
Bot is launched via PM2
My remote machine internet access works via proxy. However, it has no delay, because I have made curl requests to telegram API and it responsd very fast.
Did I miss something?

Why are you using express for handling ??

Use setWebhook instead and provide a crt.pem file with open-ssl

@AliSawari using express js will provide more control of webhook endpoints.
If you wont be using express you should install Nginx, to make routing to your webhook url.
I have solved my problem regarding slow send time. It was because of proxy that is used to get access to internet. My virtual machine providers intentionally made it slow for their own reasons.

@SuperMasterBlasterLaser so now the bot is doing fine ? can I use express just like you for routing?

@AliSawari Yes. Bot works fine. If you open this example you can see how express is being used for handling Telegram's data.

Thanks a lot :)

@AliSawari @SuperMasterBlasterLaser i have done the same by running other websockets in the system and it drives the api slow. how do we resolve that?


transaction.insert('Order', oder) does return order id but does not save on DB

I want to save the order to MongoDB (cloud-hosted ). However, if I use transaction.insert('Order', order) to save data,  it does return the ID of the saved object but does not save on DB.
`
async function start() {
try {
const orderId = transaction.insert("Order", order);
  res.status(200).json({
    sucess: true,
    data: orderId,
  });
} catch (error) {
  console.error(error);
  const rollbackObj = await transaction.rollback().catch(console.error);
  transaction.clean();
}

}
start();
`

Have you solved it?I also cannot save into DB. When transaction,run(), will always be loaded.Can't get to the next step


[DBZ-1519] Debezium Erroneously Reporting No Tables to Capture

https://issues.jboss.org/browse/DBZ-1519
This PR supersedes PR #1087.

@Naros Could you please squash the commits and add test related to the situation reported in Jira?

@jpechane Will do.

@dvfeinblum @Naros Applied, thanks for the improvement!

Thanks to you both for the help! Can't wait to contribute again 😄


fix typo in ResolverOptions.Credentials documentation

Fixes a small typo in ResolverOptions.Credentials documentation.
Signed-off-by: Charles Kenney<EMAIL_ADDRESS>

Codecov Report

Merging #2753 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2753   +/-   ##
=======================================
  Coverage   43.72%   43.72%
=======================================
  Files         100      100
  Lines       10734    10734
=======================================
  Hits         4693     4693
  Misses       5311     5311
  Partials      730      730

Flag
Coverage Δ

#linux
47.39% <ø> (ø)
:arrow_up:

#windows
40.89% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

remotes/docker/resolver.go
58.36% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Missing Eks svc CIDR to avoid overlap with the vpn one

The EKS Installer and Furyctl should support scpecifing the CIDR for the Services in EKS


Restore does not work for solution with project dependencies

From @atanasa on June 20, 2017 14:54
Steps to reproduce

Create a solution with 2 projects - A and B.
Edit the solution so that B depends on A.
Run dotnet restore on the solution file.

Expected  behavior
Both project A and B are restored.
Actual behavior
Only project A is restored.
Environment data
dotnet --info output:
.NET Command Line Tools (2.0.0-preview1-005977)
Product Information:
Version:            2.0.0-preview1-005977
Commit SHA-1 hash:  414cab8a0b
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.14393
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.0.0-preview1-005977\
Microsoft .NET Core Shared Framework Host
Version  : 2.0.0-preview1-002111-00
Build    : 1ff021936263d492539399688f46fd3827169983
Sample solution that I used to reproduce this:
ReproSlnDepsRestore.zip
Copied from original issue: dotnet/cli#6953

@rainersigwald Another one that seems related to metaproj. Should I move to msbuild?

Please, move it back to the CLI if this turns out to be a CLI issue.


QuartoNotebookWorker precompile error when trying quarto render

I am trying to render a quarto document after updateing the quarto version to 1.6.33 and Julia 1.11 and I get the following error when running quarto render
(env) (base) fcremer@javorina:~/Documents/NFDI4Earth/lhbarticles$ quarto render Intro_Raster_Data_Analysis_ENG.qmd -to pdf --toc
ERROR: Julia server returned error after receiving "run" command:
Failed to run notebook: /home/fcremer/Documents/NFDI4Earth/lhbarticles/Intro_Raster_Data_Analysis_ENG.qmd
ERROR: Remote exception from Malt.Worker on port 9225 with PID 27225:

Failed to precompile QuartoNotebookWorker [38328d9c-a911-4051-bc06-3f7f556ffeda] to "/home/fcremer/.julia/compiled/v1.11/QuartoNotebookWorker/jl_LMzCNU".

Does that notebook use a specific Project.toml, is so what is the contents of that project and manifest?

If /home/fcremer/.julia/compiled/v1.11/QuartoNotebookWorker/jl_LMzCNU is removed manually and you then retry does the error happen in the exact same place? Or does it then run fine?

Additionally, is there any difference for you when running this with 1.5.57, https://github.com/quarto-dev/quarto-cli/releases/tag/v1.5.57?

Additionally, is there any difference for you when running this with 1.5.57<EMAIL_ADDRESS>(release)?

I upgraded from 1.5.57 because I ran into the error that was fixed by this PR https://github.com/quarto-dev/quarto-cli/pull/10244
I missed, that I have QuartoNotebookWorker added to my local environment. But even after removing it from the environment it does not work.
Rendering a single quarto file without a Project.toml works.
I don't find this file in the compiled folder jl_LMzCNU

Same issue for me with julia-1.11.1 on macos and quarto 1.5.57 and quarto 1.6. I thought few days ago, everything was fine.... 🤔

Same issue for me on macos with julia-1.11.1 and quarto 1.5.57 (/Applications/quarto/share/julia/ensure_environment.jl edited manually) and quarto 1.6. I thought few days ago, everything was fine.... 🤔

Found a Workaround by activating a local environment and adding only QuartoNotebookRunner.jl and packages used inside my qmd document.  Quarto uses this local environment and everything is fine. So I guess the precompilation of QuartoNotebookWorker failed because of incompatibility with some packages installed inside environment  @v1.11. I will investigate later....

I think I fixed it for me by upgrading the local environment that I use for the packages in the Quarto Document.

I think  I also had to do an update of the local environment. I can't reproduce the exact steps anymore.

Thanks, that's a few more clues at least from these two reports so we might be able to track down and resolve the underlying issue.

How do I find which julia environment is used from Quarto to run QuartoNotebookRunner?
Even though simple examples run something is still off, because I can't plot from an RCall cell but I checked it from a QuartoNotebookRunner environment with the latest release and it works there.
This is the error I get from just running quarto preview with the attached qmd.
$ quarto preview /home/fcremer/Documents/NFDI4Earth/lhbarticles/rplot.qmd
Running [1/1] at line 16:  using RCall
ERROR: Julia server returned error after receiving "run" command:
Failed to run notebook: /home/fcremer/Documents/NFDI4Earth/lhbarticles/rplot.qmd
ERROR: EvaluationError: Encountered 1 error during evaluation

Error 1 of 1
@ /home/fcremer/Documents/NFDI4Earth/lhbarticles/rplot.qmd:16
Error showing value of type QuartoNotebookWorker.SVG
UndefVarError: `Random` not defined in `QuartoNotebookWorker`
Suggestion: check for spelling errors or missing imports.
Hint: Random is loaded but not imported in the active module Main.

ERROR: Internal julia server error

Stack trace:
    at writeJuliaCommand (file:///opt/quarto/bin/quarto.js:41381:19)
    at eventLoopTick (ext:core/01_core.js:175:7)
    at async executeJulia (file:///opt/quarto/bin/quarto.js:41275:22)
    at async Object.execute (file:///opt/quarto/bin/quarto.js:41012:20)
    at async renderExecute (file:///opt/quarto/bin/quarto.js:85311:27)
    at async renderFileInternal (file:///opt/quarto/bin/quarto.js:85479:43)
    at async renderFiles (file:///opt/quarto/bin/quarto.js:85347:17)
    at async render (file:///opt/quarto/bin/quarto.js:90246:21)
    at async renderForPreview (file:///opt/quarto/bin/quarto.js:91273:26)
    at async render (file:///opt/quarto/bin/quarto.js:91156:29)

This is the content of the qmd file that is run:
---
title: R plot from julia
fig-width: 4
fig-height: 3
fig-dpi: 150
julia:
    exeflags<EMAIL_ADDRESS>---

# This is all confusing

```{julia}

using RCall
using Pkg
Pkg.status()
#@show RCall.Rhome
R"plot(1:10)"

without the  R"plot(1:10)" this works as expected.

UndefVarError: Random not defined in QuartoNotebookWorker

That might be unrelated. Possibly a different bug here https://github.com/PumasAI/QuartoNotebookRunner.jl/blame/407921d34a671873280728f0dd8948c0c0bc03ce/src/QuartoNotebookWorker/src/render.jl#L452
Looks like Random isn't imported into the particular module that defines that code. Adding the import would probably be sufficient.

The thing is that the qmd is correctly rendered into an ipynb when I use the Dev docs and run the QNR from a dedicated environment with QNR 0.11.6

Yes, the ipynb is attached:
rplot.txt
This is a txt file to enable uploading it into the issue.

Nice digging. I can reproduce this with your script. I also tried to test it on nightly instead of julia 1.11 but then the versioninfo that printed in the resulting html is 1.11 when I run it without the REPL dependency so I am wondering whether the QUARTO_JULIA environment variable is even doing what it is supposed to do.

Yes, there was some quarto process still hanging around. I run it now with nightly and ran into some new problems that I might open as a new issue. When I am switching from 1.12 to 1.11 I also get some problems from a Manifest file that is still hanging around and resolved with julia 1.12.
I am not sure, what exactly could be done, but it seems to me that these switches between julia versions could be annoying because it is not clear where this is exactly coming from as a user.
This is the error I get from the switch from 1.12 to 1.11:
Precompiling Pkg...
Info Given Pkg was explicitly requested, output will be shown live
ERROR: LoadError: ArgumentError: Package LibGit2 does not have Base64 in its dependencies:
- Note that the following manifests in the load path were resolved with a different
  julia version, which may be the cause of the error. Try to re-resolve them in the
  current version, or consider deleting them if that fails:
    /run/user/1001/julia/Manifest.toml (v1.12.0-DEV)
- You may have a partially installed environment. Try `Pkg.instantiate()`
  to ensure all packages in the environment are installed.
- Or, if you have LibGit2 checked out for development and have
  added Base64 as a dependency but haven't updated your primary
  environment's manifest file, try `Pkg.resolve()`.
- Otherwise you may need to report an issue with LibGit2
Stacktrace:
 [1] macro expansion
   @ ./loading.jl:2226 [inlined]
 [2] macro expansion
   @ ./lock.jl:273 [inlined]
 [3] __require(into::Module, mod::Symbol)
   @ Base ./loading.jl:2198
 [4] #invoke_in_world#3
   @ ./essentials.jl:1089 [inlined]
 [5] invoke_in_world
   @ ./essentials.jl:1086 [inlined]
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:2191
 [7] include
   @ ./Base.jl:557 [inlined]
 [8] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::String)
   @ Base ./loading.jl:2790
 [9] top-level scope
   @ stdin:5
in expression starting at /home/fcremer/.julia/juliaup/julia-1.11.1+0.x64.linux.gnu/share/julia/stdlib/v1.11/LibGit2/src/LibGit2.jl:3
in expression starting at stdin:5
ERROR: LoadError: Failed to precompile LibGit2 [76f85450-5226-5b5a-8eaa-529ad045b433] to "/home/fcremer/.julia/compiled/v1.11/LibGit2/jl_LNfzcY".

ERROR: LoadError: ArgumentError: Package LibGit2 does not have Base64 in its dependencies:
- Note that the following manifests in the load path were resolved with a different
  julia version, which may be the cause of the error. Try to re-resolve them in the
  current version, or consider deleting them if that fails:
    /run/user/1001/julia/Manifest.toml (v1.12.0-DEV)
- You may have a partially installed environment. Try `Pkg.instantiate()`
  to ensure all packages in the environment are installed.
- Or, if you have LibGit2 checked out for development and have
  added Base64 as a dependency but haven't updated your primary
  environment's manifest file, try `Pkg.resolve()`.
- Otherwise you may need to report an issue with LibGit2
Stacktrace:
 [1] macro expansion
   @ ./loading.jl:2226 [inlined]
 [2] macro expansion
   @ ./lock.jl:273 [inlined]
 [3] __require(into::Module, mod::Symbol)
   @ Base ./loading.jl:2198
 [4] #invoke_in_world#3
   @ ./essentials.jl:1089 [inlined]
 [5] invoke_in_world
   @ ./essentials.jl:1086 [inlined]
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:2191
 [7] include
   @ ./Base.jl:557 [inlined]
 [8] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::String)
   @ Base ./loading.jl:2790
 [9] top-level scope
   @ stdin:5
in expression starting at /home/fcremer/.julia/juliaup/julia-1.11.1+0.x64.linux.gnu/share/julia/stdlib/v1.11/LibGit2/src/LibGit2.jl:3
in expression starting at stdin:5
ERROR: LoadError: Failed to precompile LibGit2 [76f85450-5226-5b5a-8eaa-529ad045b433] to "/home/fcremer/.julia/compiled/v1.11/LibGit2/jl_UTnVZD".

Stacktrace:
  [1] error(s::String)
    @ Base ./error.jl:35
  [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, keep_loaded_modules::Bool; flags::Cmd, cacheflags::Base.CacheFlags, reasons::Dict{String, Int64}, isext::Bool)
    @ Base ./loading.jl:3085
  [3] (::Base.var"#1082#1083"{Base.PkgId})()
    @ Base ./loading.jl:2492
  [4] mkpidlock(f::Base.var"#1082#1083"{Base.PkgId}, at::String, pid::Int32; kwopts::@Kwargs{stale_age::Int64, wait::Bool})
    @ FileWatching.Pidfile ~/.julia/juliaup/julia-1.11.1+0.x64.linux.gnu/share/julia/stdlib/v1.11/FileWatching/src/pidfile.jl:95
  [5] #mkpidlock#6
    @ ~/.julia/juliaup/julia-1.11.1+0.x64.linux.gnu/share/julia/stdlib/v1.11/FileWatching/src/pidfile.jl:90 [inlined]
  [6] trymkpidlock(::Function, ::Vararg{Any}; kwargs::@Kwargs{stale_age::Int64})
    @ FileWatching.Pidfile ~/.julia/juliaup/julia-1.11.1+0.x64.linux.gnu/share/julia/stdlib/v1.11/FileWatching/src/pidfile.jl:116
  [7] #invokelatest#2
    @ ./essentials.jl:1057 [inlined]
  [8] invokelatest
    @ ./essentials.jl:1052 [inlined]
  [9] maybe_cachefile_lock(f::Base.var"#1082#1083"{Base.PkgId}, pkg::Base.PkgId, srcpath::String; stale_age::Int64)
    @ Base ./loading.jl:3609
 [10] maybe_cachefile_lock
    @ ./loading.jl:3606 [inlined]
 [11] _require(pkg::Base.PkgId, env::String)
    @ Base ./loading.jl:2488
 [12] __require_prelocked(uuidkey::Base.PkgId, env::String)
    @ Base ./loading.jl:2315
 [13] #invoke_in_world#3
    @ ./essentials.jl:1089 [inlined]
 [14] invoke_in_world
    @ ./essentials.jl:1086 [inlined]
 [15] _require_prelocked(uuidkey::Base.PkgId, env::String)
    @ Base ./loading.jl:2302
 [16] macro expansion
    @ ./loading.jl:2241 [inlined]
 [17] macro expansion
    @ ./lock.jl:273 [inlined]
 [18] __require(into::Module, mod::Symbol)
    @ Base ./loading.jl:2198
 [19] #invoke_in_world#3
    @ ./essentials.jl:1089 [inlined]
 [20] invoke_in_world
    @ ./essentials.jl:1086 [inlined]
 [21] require(into::Module, mod::Symbol)
    @ Base ./loading.jl:2191
in expression starting at /opt/quarto/share/julia/ensure_environment.jl:1
ERROR: Ensuring an updated julia server environment failed

Stack trace:
    at ensureQuartoNotebookRunnerEnvironment (file:///opt/quarto/bin/quarto.js:41203:15)
    at eventLoopTick (ext:core/01_core.js:175:7)
    at async startOrReuseJuliaServer (file:///opt/quarto/bin/quarto.js:41111:13)
    at async getJuliaServerConnection (file:///opt/quarto/bin/quarto.js:41224:24)
    at async executeJulia (file:///opt/quarto/bin/quarto.js:41283:18)
    at async Object.execute (file:///opt/quarto/bin/quarto.js:41028:20)
    at async renderExecute (file:///opt/quarto/bin/quarto.js:85764:27)
    at async renderFileInternal (file:///opt/quarto/bin/quarto.js:85932:43)
    at async renderFiles (file:///opt/quarto/bin/quarto.js:85800:17)
    at async render (file:///opt/quarto/bin/quarto.js:90702:21)

Maybe we could use version specific Manifest files so that we won't run into this reresolving issue. See https://pkgdocs.julialang.org/v1/toml-files/#Different-Manifests-for-Different-Julia-versions

I ran into this issue with precompilation too, and as above the failure condition involves (at least) a 1.10 Manifest and Quarto being run with 1.11.

Thanks for the additional investigation @penelopeysm.

Maybe we could use version specific Manifest files so that we won't run into this reresolving issue. See https://pkgdocs.julialang.org/v1/toml-files/#Different-Manifests-for-Different-Julia-versions

Yes, that probably is part of the solution.

I am not sure, what exactly could be done, but it seems to me that these switches between julia versions could be annoying because it is not clear where this is exactly coming from as a user.

Making it clearer to the user that they need to update their manifest first is likely what the behaviour should be here as far as I'm concerned. Another option is to detect if the manifest is a different Julia version and then automatically resolve it, but I'm inclined to avoid modifying user environments and instead just inform them that they need to re-resolve and try again.


Add a "Safemode" to restrict peer connections

What current issue(s) does this address, or what feature is it adding?
One issue I had during the most recent bad block hiccup was after I resynced my node using the most recent bootstrap files, it ended up getting stuck again because it was connected to a node which was also still stuck (the bootstrap files were behind the bad blockheight). My idea is to implement a safemode which restricts peer connections to addresses within the SEED_LIST which is populated from the config files.
Normally, whenever there is an issue with nodes, I check http://monitor.cityofzion.io/ to see which nodes are still good. In this case, there were still about 4 nodes which were still good. But updating my SEED_LIST with only these nodes did not restrict my node from connecting to nodes which were still up but also stuck.
How did you solve this problem?
I implemented a safemode which can be manually set in Settings.py or during startup of np-api-server, or np-prompt. Additionally, I added a safemode command to the config group so safemode could be disabled after headers have exceeded the bad block, or toggled any other time at the user's discretion.
NOTE: I also include a restart of NodeLeader anytime safemode is toggled on because the expectation is that the user is trying to protect his/her node from getting stuck and having to resync.
How did you make sure your solution works?
Personal Testing and unittest
Are there any special changes in the code that we should be aware of?
No
Please check the following, if applicable:

[x] Did you add any tests?
[x] Did you run make lint?
[x] Did you run make test?
[x] Are you making a PR to a feature branch or development rather than master?
[x] Did you add an entry to CHANGELOG.rst? (if not, please do)

@ixje I understand you are reworking the servers from Twisted to asyncio; however, I think this PR or the idea behind it is still relevant and should be incorporated. For example, I am using it again after my testnet node got stuck at 2379318 to make sure that my node doesn't get stuck again.

While at first sight the implementation looks sound, I currently don't have the bandwidth to run this code and observe it does what it's supposed to do without breaking something else. If we'd add IP filtering I'd rather see a blacklist/whitelist policy type implementation rather than being restricted to a "good seedlist" only option.
I'll leave the PR open such that others can take notice of it or be referred to when asked about such an option.

If we'd add IP filtering I'd rather see a blacklist/whitelist policy type implementation rather than being restricted to a "good seedlist" only option.

My idea was for a dynamic seedlist which constantly updated from a curated list based on blockheight. This should avoid connecting to "stuck" nodes.
Also, I have heard that neo-cli v2.10.2 should eliminate the "forking" issue entirely, so perhaps this idea is obsolete. What do you think @ixje? If you still think it is useful, I would like to try to port it into the asyncio branch.

I'm not convinced the potential of forking is resolved until at least 6 months (ideally a year) of it not happening. Even then it's just a matter of "what new changes do they apply that might cause regression?". So that could justify it.
Note that the asyncio branch already has blacklist/whitelist support, so it would need the service interface.
Regarding that part; I'm concerned about who's going to maintain the service backend. The IPFilter updating part could be as simple as periodically requesting a JSON file with ip's from the server, parse and apply. I'd like to see it work and used before making it a permanent part of neo-python.

Okay, sounds good. I am gonna try to integrate my idea.  The whitelist I am using is essentially the json file which feeds monitor.cityofzion.io and then this list would be periodically updated to reflect height and the connected nodes would be edited to always connect to the best nodes.

@ixje closing this and tabling the idea until I can think of a better implementation.

Also reference https://github.com/jseagrave21/neo-python/tree/safemode-asyncio