Build the basis for the notification framework

There are numerous notification requirements / opportunities in the system; but the biggest need is to think through the framework for registering and delivering notifications.
Notification types should at least begin with:

Email
A notifications interface on the home screen of HospitalRun

In the future, tying into a text messaging service or even a mobile version of the system could be supported. The point is that the framework needs to allow developers to easily register to listen for notifications surrounding a given object (or document) and then to deliver a series of notifications based on an event.

Hi.
Today, at the Hack Day Lisbon, I started working in the notifications system based on some tips from @jkleinsc.

Design doc for the Lisbon Hack Day https://docs.google.com/document/d/1tQzECDRgBkbvtMizsR-Prh0-fX_djivadFe_fK4eCW4/edit#heading=h.23y5yhjqf9dn

After a conversation in Lisbon with @jkleinsc I went home thinking about the notifications system.

Phase 1: Basic push native notifications
Step 1 is to create a HospitalRun server (Node-based) framework/utility for registering and sending notifications using the native notification constructs in modern browsers, etc. These notifications do not persist and are surfaced purely to ensure that user work (actions needed in the system) are made apparent to a user (or set of users) in as close to real-time as possible.

The first step leads us right away to push notifications. Wouldn't be better to start with someting like the following?
Step 1
Create dblisteners that listens for changes and send notifications to users/roles. These notitifications are stored in the DB.
Step 2
Create a component to show the notifications for the current user.
Something like this:

And maybe as a popup menu like this:

Step 3
Create a dblistener that listens for new notifications and dispatches them using the native notification constructs in modern browsers, SMS, e-mail or any other mean.

@tangollama what do you think? can the designs be adjusted to this proposal?

@sericaia sorry for my delay in responding.  I was away but I am back now.  I think the suggestion @titonobre is great and we should adjust the design to to accommodate.

Hi All,
Is help still needed/wanted on this issue?

Diago: in a few words - yes please.

On Oct 8, 2017, at 7:10 PM, Diogo Silva<EMAIL_ADDRESS>wrote:
Hi All,
Is help still needed/wanted on this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi All,
Tried to have a first stab at the problem and how the system "would" work. This will most likely change based on your feedback.
Model
{
  "SourceType": 0,
  "Source": "",
  "Persisted": false,
  "Target": "Dr. Who",
  "Title": "Imaging Results",
  "Message": "Please collect results from desk X"
}

SourceType: Would describe the document originating the notification, this would allow for richer options on notification presentation
Source: The origin document identification.
Persisted: If the notification should be persisted or just attempted presentation and forgotten afterwards.
Target: The User identification.
Title: Small summary description
Message: Notification messaging/description

Db Listeners
Would decide depending on the DB Change what notification to sent, and if it should be sent for a Role would create all individual necessary User notifications.
PS: This should most likely change into a simple event creator and an extra aggregator should exist to create the notifications. (Again first stab at the problem.)
Dispatcher
Dispatcher would deliver the notifications to the User based on:

User preferences
Available delivery venues (Email, SMS, App)
Active status of the User, i.e. if the user is currently on-line in the app would be faster to send push notification to the browser than would be to send an email.

Please let me know your thoughts, hopefully now I will have some time to start working on it.
Cheers,
Diogo Silva


Provide Emergency Shutdown (Panic Button) functionality

In the event of a systems breach (e.g., through compromised secrets, or holes in auth libraries), a Bad Actor could potentially wreak a lot of chaos. It would be useful to have a mechanism to globally shut down the system in an emergency in such a way that it can't be overridden by the (compromised) API, and which would more positively disable active resource records (as opposed to no longer serving them authoritatively and waiting for them to eventually timeout across layers of caches).

Thanks for filing this.  What sort of mechanism do you imagine this being?  What does the workflow look like?

I'm not clear what action to take here and don't have further feedback.  Closing for now, but feel free to re-open or file something new if you want to explore.


Unable to set custom backTitle on Scene

I was not able to change the title on the back button, I only got "Back" no matter what I tried:
<Scene
    back={true}
    backTitle="New title"
    backTitleEnabled={true}
    key="pdfView"
    title={() => {
    return "";
    }}
   component={PdfView}
   hideNavBar={false}/>

Seems like the HeaderBackButton uses label instead of title.
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-router-flux/src/NavBar.js b/node_modules/react-native-router-flux/src/NavBar.js
index bb154e0..b4827b5 100644
--- a/node_modules/react-native-router-flux/src/NavBar.js
+++ b/node_modules/react-native-router-flux/src/NavBar.js
@@ -28,7 +28,7 @@ export function BackButton(state) {
   // returning react-navigation's back button well styled for ios and android if rnrf4-supported customization
   // is not required
   if (!state.backButtonImage) {
-    return <HeaderBackButton onPress={onPress} title={state.backTitle} titleStyle={textButtonStyle} tintColor={tintColor} truncatedTitle={state.truncatedTitle} />;
+    return <HeaderBackButton onPress={onPress} label={state.backTitle} titleStyle={textButtonStyle} tintColor={tintColor} truncatedTitle={state.truncatedTitle} />;
   }

   const text = state.backTitle ? <Text style={textButtonStyle}>{state.backTitle}</Text> : null;

I'm using the 4.3.1 version
Thanks for all your work on this library.
This issue body was partially generated by patch-package.

Same here, looking at the SceneProps interface I think we should use headerBackTitle, but it doesn't work.


FetchMock.getMock seems always undefined as of 4.0.0

I am using FetchMock with Mockery as Node 4 module, hence I need to get a handle on the mocked fetch() function.
Registering the node-fetch mock with myMock.getMock() as shown below leads to an undefined fetch function in the code under test.
'use strict';

var fetchMock = require('fetch-mock');
var mockery = require('mockery');

describe('fetch mockery', function () {

  beforeEach(function () {
    mockery.enable({useCleanCache: true});
    var myMock = fetchMock
      .mock('http://auth.service.com/user', '{"foo": 1}');
    mockery.registerMock('node-fetch', myMock.getMock());        <-- undefined
  });

  afterEach(function () {
    fetchMock.restore();
    mockery.deregisterMock('node-fetch');
    mockery.disable();
  });

  it('should mock a request', function () {

    var goFetch = require('../lib/fetchsample'); // just a call to fetch in a separate module

    return goFetch('http://auth.service.com/user').then(function (response) {
      return response.json();
    }).then(function (json) {
      console.log(json);
    });
  });

});

As a workaround, the necessary fetch function mock is availabe as myMock.mockedContext.fetch:
mockery.registerMock('node-fetch', myMock.mockedContext.fetch);

Maybe the fix would be to change getMock() in fetch-mock.js like so:
	/**
	 * getMock
	 * Returns a reference to the stub function used to mock fetch
	 * @return {Function}
	 */
	getMock () {
		return this.mockedContext.fetch;
	}

Or am I using fetch-mock incorrectly here?

thanks for pointing this out. Not sure what in v4 would've broken it, or why the tests still pass. I'll fix the tests and add your solution

Ah no, you're missing fetchMock.useNonGlobalFetch(require('node-fetch')); before your tests. That should fix it.


rclc_executor_spin allows only one service call

When executing the example service node, spinning by a calling of rclc_executor_spin (example_service_node.c#L77), just one service call is processed, then the process closes.
Steps to reproduce:

Start the example_service_node executable from rclc_example
Call the example service, e.g., on the terminal with ros2 service call /addtwoints example_interfaces/srv/AddTwoInts "{a: 17, b: 42}"
Call the example service again

Expected behavior:
Service remains active after the first service call, accepting further service calls.
Observed behavior:
Example service executable closes after (successfully) handling the first service call.

Potential Workaround:
Change (example_service_node.c#L77) to use rclc_executor_spin_some instead of rclc_executor_spin, e.g.,
while (true) {
  rclc_executor_spin_some(&executor, 10);
}

Potential Workaround:
Change (example_service_node.c#L77) to use rclc_executor_spin_some instead of rclc_executor_spin, e.g.,
while (true) {
  rclc_executor_spin_some(&executor, 10);
}

Can no longer reproduce with current master.


Using this implementation with paris-lille or semantic3D (outdoor data)

How can we use this implementation with a different dataset such as paris-llile3D and semantic3D (outdoor data)? Do we need to use a modification of gen_indoor3D_h5.py is it possible to use a simple data structure like just tiles of data?

I think how to preprocess your dataset depends on your own. You can try the preprocessing style of S3DIS and modify it for your dataset.


Add support for context option

Also refactor

Hi,
I am interested in your pull request. It seems the original don't have activity since long time.
So, I try to copy and paste your code straight away but no sure how to do it.
I follow these steps:

Comment out the original plugin in the configuration (gatsby-config.js).
Copy the utils.js file into my project and configure cloudinary with my details.
Replace gatsby-node.js with your code.
Re-install all the node modules.

It seems there is a first error in gatsby-node.js:
`
"gatsby-node.js" threw an error while running the sourceNodes lifecycle:
TypeError: Cannot read property 'api' of undefined
`
So, the nodes are no created.

Thanks @cortazar11 I'll fix it soon

@cortazar11 Fixed!
please remember to also copy package.json from this pr to the plugin folder

Hello,
Thank you for your code.
I check it. I clone your code and add up the libraries of Gatsby. So, the cloudinary nodes are created from scratch, without any other library.
The Graph IDE shows the cloudinary staff, but between the fields no any about the context. From the DEFAULT_KEYS of utils.js only shows resourceType and type.
As I am starting with Gatsby (and no too advanced in Development) I might be missing some steps:

I need to require in some file of Gatsby (layout, pages) the sourceNodes exported in your gatsby-node.js file?
I put in the configuration of "cloudinary" library the parameters context: true, but the result is the same. I need to put this option somewhere else?
As Gatsby is client-side and the library "cloudinary" belongs to the Node.j SDK that is server-side, I need to organize the directories as a Full-Stack project? (Gatsby with their dependencies in a folder within a Node directory with their own dependencies)

You need to add
context: true
to this source plugin options in gatsby-config.js
As for you're other questions, gatsby builds your site on the server side (nodejs), and the result is client side code. You can read some of gatsby docs, or watch a youtube tutorial to understand more

Hi,
Yeap, I set a Gatsby project as usual and add a plugin directory.
In that directory I placed your code as a local plugin.
In gatsby-config.js I set a opbject with the resolve to the path where the local plugin is and set the options as in the original adding context: true.
Now, I can retrieve context => custom => caption with Graphql
Thank you for all

great!

Thanks for the PR @nirmaoz amazing! 👍 👍


No support for changed ass style

The webms are currently using the styling from the subtitles, instead of using mpvs sub-ass-force-style option.

Just to be clear, you are using the hardsub mode, right?

Yes, I am.

Should be fixed.


crash on startup

It crashes instantly after starting it up with no error showing. When I launch it, it shows white screen for about 3 sec and closes.
and yes I installed every requirements

This means the vulkan renderer is failing to start. Make sure it's being launched on an nvidia or amd non-integrated gpu. One troubleshooting solution that sometimes works is disabling the integrated graphics device in devicemanager

I have amd gpu installed and there is no integrated graphics device showing in device manager and I don't know what's causing it

What do the error messages say in windows event viewer?

I fixed it, All I had to do is degrade my amd adrenalin

It crashes instantly after starting it up with no error showing. When I launch it, it shows white screen for about 3 sec and closes.
and yes I installed every requirements

Same

I have all the requirements but for some reason, DSMapStudio opens to black screen for three seconds and then crashes to desktop.


Better (masthead) tests

The current end-to-end tests I've written are in test/e2e.js and were written before I did the masthead animation stuff. So there probably needs more tests to be written in the style of the other ones (shouldn't take a whole lot of new learning etc) to verify masthead contents were swapped appropriately. It would be nice to see not only a h1 swap test, but also an image test by maybe digging into element.style.backgroundImage if this will work?

@SpoonDoctor how do you feel about digging around in the test/e2e.js file and possible making a few more tests to ensure that the masthead content is properly displayed on different pages?


missing comma and wrong ref (#23)

Thanks @kon-mal 😅 Our CI/CD has been broken for this package, so I missed this. I just finished fixing CI, and the new models build and pass, so we should be good. Created a release with your additions (0.4.3) 👍

Thanks and sorry again! Glad it's working now 😃


Improve usage warning format

As discussed with @lostpebble, usage warnings shouldn't have a custom format, but should be "classical" Nodejs exceptions.
Same for internal errors.
Also, all warning/error messages should be one-liners (albeit potentially very long one liners).

:heavy_check_mark: Test infra is ready to assert stdout and stderr.
:heavy_check_mark: stdout is tested - no stdout spam guaranteed.
Changing the format in itself will/should be easy.

cc @lostpebble
:heavy_check_mark: Core is now TS typed.
:heavy_check_mark: Code is more readable/cleaner (still far from perfect, but better than before)
:heavy_check_mark: Redesigned some important aspects of error handling. It's simpler now.
:heavy_check_mark: Reworded all error/warning messages.
:heavy_check_mark: Wildcard will always return an HTTP response, never throw, and do a single console.error for usage errors. Among others, this means that a frontend can now always gracefully handle errors. (The exception being if Wildcard has a bug then it will actually throw.) Wildcard does throw instead of console.error when doing SSR.
:heavy_check_mark: The error/warning messages are now tested against.
:heavy_check_mark: All error/warning messages have a "normal" format: a stack trace and a single-line err.message. All unit tests are verified against this. No more stdout/stderr spam.
:heavy_check_mark: Around 50% more tests to catch more error handling and edge cases (everything is not covered yet but getting close to it).
:heavy_check_mark: It's now import { server } from '@wildcard-api/server'; instead of import { endpoints }.
That's on top of my head.
It's published as 0.4.0 but it still contains the donation-reminder GCE bug. I'll let you now once I've published a minor that fixes this.
I'm going to rename Wildcard API to telefunc. I want to get away from all API terminology. Going to talk about telefunctions instead of endpoints.
FYI, I've developed a full vision for telefunc. It's going to be insane...

Fully managed and dead-simple session/auth management. Design is pretty stable.
Simple realtime comm. Design could still have leaks, but I don't think so AFAICT.
Independent but works-well-with-telefunc project tackling this long-standing nasty problem of schema queries, basically like GraphQL but 10x simpler, on all sides: much much simpler resolvers, simpler queries, simpler permissions. No unnecessary DSL, everything is JSON, hence compatible with telefunc.

But for now I'm heads down on the Lsos.

Migration path: https://github.com/reframejs/wildcard-api/releases/tag/v0.4.0 - should remain the same after the GCE bugfix.

@lostpebble
Some new little breaking changes: https://github.com/reframejs/wildcard-api/releases/tag/v0.5.0
Note the argumentsAlwaysInHttpBody rename to shortUrl.
I will publish a GCE bugfix in 0.5.1 soon


Make TestHandler::hasRecord assert context, not only message

The current implementation of hasRecord in the TestHandler only checks that the message is correct, not the context. This has also been reported in issue #1002 .
In this pull request, I'm changing the hasRecord method to also verify the context. However, I'm not sure if the hasRecordThatContains should also be modified, and if so, what that should actually mean.
I'm also adding two new tests to verify this behaviour.

Thanks, would you mind rebasing the PR on the 1.x branch though?

Thanks, would you mind rebasing the PR on the 1.x branch though?

Sure, I can do that. But what is the intention with the master branch? Will there be a Monolog 2 some day?

Yes master is targetting 2.0, so if you want this available in 1.x I need it for the 1.x branch (which I then merge into master)

Thanks, merged in 1.x and master as b381a973bcca4a2acb01dbe57e37bf5474fb7768


Bot tries to set nickname of Discord owner when "Sync Names" is on

I was having a problem getting to my account setting on my website and it was throwing errors. I read into the logs and determined that it was caused by the bot trying to set my nickname on Discord which it did not have permissions for since I am the creator of the Discord and administrators apparently can't change the nicknames of the creator.
  'code' => 0,
  'message' => 'Privilege is too low...',
)

#0 C:\inetpub\wwwroot\hyped-gamingcom\applications\discord\sources\Api\AbstractResponse.php(68): IPS\_Log::log('array (\n  'code...', 'discord_excepti...')
#1 C:\inetpub\wwwroot\hyped-gamingcom\applications\discord\sources\Api\GuildMember.php(57): IPS\discord\Api\_AbstractResponse->handleApi()
#2 C:\inetpub\wwwroot\hyped-gamingcom\applications\core\sources\ProfileSync\Discord.php(63): IPS\discord\Api\_GuildMember->update(Object(IPS\Member))
#3 C:\inetpub\wwwroot\hyped-gamingcom\applications\core\sources\ProfileSync\Discord.php(128): IPS\core\ProfileSync\_Discord->user()
#4 C:\inetpub\wwwroot\hyped-gamingcom\system\Theme\Theme.php(824) : eval()'d code(7536): IPS\core\ProfileSync\_Discord->name()
#5 C:\inetpub\wwwroot\hyped-gamingcom\system\Theme\SandboxedTemplate.php(56): IPS\Theme\class_core_front_system->settingsOverview(Array, NULL)
#6 C:\inetpub\wwwroot\hyped-gamingcom\applications\core\modules\front\system\settings.php(160): IPS\Theme\_SandboxedTemplate->__call('settingsOvervie...', Array)
#7 [internal function]: IPS\core\modules\front\system\_settings->_overview()
#8 C:\inetpub\wwwroot\hyped-gamingcom\applications\core\modules\front\system\settings.php(54): call_user_func(Array)
#9 C:\inetpub\wwwroot\hyped-gamingcom\system\Dispatcher\Controller.php(96): IPS\core\modules\front\system\_settings->manage()
#10 C:\inetpub\wwwroot\hyped-gamingcom\applications\core\modules\front\system\settings.php(34): IPS\Dispatcher\_Controller->execute()
#11 C:\inetpub\wwwroot\hyped-gamingcom\system\Dispatcher\Dispatcher.php(146): IPS\core\modules\front\system\_settings->execute()
#12 C:\inetpub\wwwroot\hyped-gamingcom\index.php(12): IPS\_Dispatcher->run()
#13 {main}

is the bot's role above your role? and have the administrator flag on it?

Yes. My only rank is Owner.

I had a friend give me administrator on his Discord and I was unable to change his nickname.


The system prompt is not displaying fully on mobile

Installation Method
pip
Environment

**Open WebUI Version: v0.4.6

**Ollama (if applicable): v0.4.3

**Operating System: Windows 11 22H4

**Browser (if applicable): tested on all Chrome, Firefox, Firefox beta Android

Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[ ] I have included the browser console logs.
[ ] I have included the Docker container logs.
[ ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
Show all text in the system prompt.
Actual Behavior:
It only shows a part of the prompt and you can't scroll.
Description
Bug Summary:
[Provide a brief but clear summary of the bug]
Reproduction Details
Steps to Reproduce:
Just try to add a model/edit a model in open-webui on a mobile browser.
Logs and Screenshots
Browser Console Logs:

[ ]

Docker Container Logs:

[ ]

Screenshots/Screen Recordings (if applicable):
https://drive.google.com/file/d/1-7lkco6pEw34aFvmSPvsi87xKdKCwR9_/view?usp=drivesdk
Additional Information

Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Investigating!

Should be fixed on dev, testing wanted here!


ARROW-14256: [CI][Package] Re-enable disabled conda packaging builds

@github-actions crossbow submit -g conda


[E2E refactor - 3] re-introduce generated clientsets to prepare for simpler e2e tests

I decided to break out the kind E2E test refactor PR https://github.com/GoogleCloudPlatform/prometheus-engine/pull/738 into smaller, digestible PRs for reviewing.
Note: because of the nature of the change, presubmits (i.e. Github Actions) may fail until the final PR is merged.
This is the third one, where we reintroduced generating k8s clientsets of our CRD types. This sets us up to ensure e2e tests don't require controller-runtime, which can be beneficial when importing the library elsewhere. This is an effective revert of c5eeee3209b63920ba888f2025f127ac4202564c.

Thanks! Waiting on @TheSpiritXIII's review on #744 and once that looks good, i'll merge this as well 👍


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter wled for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.wled
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
[X] :heavy_exclamation_mark: [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 3.0.4 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E046] devDependency must not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@alcalzone/release-script-plugin-iobroker:3.7.0"
[ ] :heavy_exclamation_mark: [E046] devDependency must not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@alcalzone/release-script-plugin-license:3.7.0"
[ ] :heavy_exclamation_mark: [E046] devDependency must not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@alcalzone/release-script:3.7.0"
[ ] :heavy_exclamation_mark: [E136] No "common.news" found for actual version 0.7.3-beta.0 in io-package.json
[X] :heavy_exclamation_mark: [E145] No "common.news" found for actual version 0.7.3-beta.0 in io-package.json
[ ] :heavy_exclamation_mark: [E157] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[X] :heavy_exclamation_mark: [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[X] :heavy_exclamation_mark: [E204] Version "0.6.2" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[ ] :heavy_exclamation_mark: [E254] Version "0.6.2" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2024 DutchmanNL<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E606] Current adapter version 0.7.3-beta.0 not found in README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2024 DutchmanNL<EMAIL_ADDRESS>at the start of LICENSE
[ ] :heavy_exclamation_mark: [E955] iob_npm.done not found in .npmignore

WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[X] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
[X] :eyes: [W853] .npmignore found - consider using package.json object "files" instead.
[ ] :eyes: [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

[X] :pushpin: [S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
[ ] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).
[ ] :pushpin: [S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Thu, 12 Sep 2024 05:52:57 GMT based on commit f0f9de80ffca3caad83f1b3bcba7e9084168d165
ioBroker.repochecker 3.0.2

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
[E145] No "common.news" found for actual version 0.7.3-beta.0 in io-package.json
[E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[E204] Version "0.6.2" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[W853] .npmignore found - consider using package.json object "files" instead.
[S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
[E136] No "common.news" found for actual version 0.7.3-beta.0 in io-package.json
[E157] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[E254] Version "0.6.2" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
[E955] iob_npm.done not found in .npmignore
[W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[W953] .npmignore found - consider using package.json object "files" instead.
[S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

Issue outdated due to RECREATE request. Follow up issue #704 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Improve demo

The number of options have grown and the demo page needs to be improved to better document them.

New demo page pushed yesterday. Will close this issue even though some more examples will be added soon.


[Bug]: [OpenAIClient] There was an issue generating the title with the completion method this.options.attachments?.then is not a function

What happened?
When adding an attatchment to a chat, using azure openai model, with rag_api connection. Its unable to generate a title for the conversation, LibreChat         | 2024-03-25 19:04:17 error: [OpenAIClient] There was an issue generating the title with the completion method this.options.attachments?.then is not a function is the error
Steps to Reproduce
setup rag_api with librechat
setup azure openai model
have a conversation with azure model, attatching a file to your first message

Error happens, no title will be set to your converation, just New Chat
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots
No response
Code of Conduct

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

Already fixed on the latest commit of LibreChat

Thanks again for the reports. With Azure specifically, there can be more going on but no issues with any of these models, titling + files


Add ability to disable plug-ins via feature toggle

Is your feature request related to a problem? Please describe.
For support reasons we need to provide an easy way for users to run the modeler without plug-ins enabled. Such a feature toggle mechanism could be used in a more general sense to give users more control over modeler behavior and allow introducing new features (for example https://github.com/camunda/camunda-modeler/issues/982) in a sane way.
Describe the solution you'd like

[ ] The modeler reads some sort of configuration and disables individual features based on it

[ ] The modeler displays a log message that it runs without plug-ins disabled

[ ] Features can be enabled / disabled in three different places (lowest to highest precedence):

Per distribution, relative to the modeler executable
Per user in the user config
Via command line flag

Describe alternatives you've considered

Only allow disabling via command line (this is, e.g. how Chrome does it for many of its args)

Additional context
Properly implemented this should allow us to gracefully introduce https://github.com/camunda/camunda-modeler/issues/982 and https://github.com/camunda/camunda-modeler/issues/872.

Please consider that it may confuse users as they have installed the plugins correctly but they didn‘t show up because of the configuration...

Good point. I added a notification that plug-ins are disabled to the issue description.


Missing Quotes for Site1

Site1 should be in quotes or else it's not valid string
(Get-Cluster).PreferredSite = Site1
https://docs.microsoft.com/en-us/azure-stack/hci/deploy/create-cluster-powershell#step-53-set-a-preferred-site

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: df3012c4-22e5-004d-da6f-60744f2cfb4f
Version Independent ID: 57e21edd-9a2b-f1ca-2ff7-48e3da5dc260
Content: Create an Azure Stack HCI cluster using Windows PowerShell - Azure Stack HCI
Content Source: azure-stack/hci/deploy/create-cluster-powershell.md
Service: azure-stack
GitHub Login: @v-dasis
Microsoft Alias: v-dasis

@hfu949 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

content updated in staging. Will merge and publish live later today.

push live Monday as missed Fri window


Raised crossing is not detecting all the possible values for traffic_calming

Creating a raised crossing with ID editor adds to the crossing node a tag
traffic_calming=table
EveryDoor seems to know only about
traffic_calming=yes
So the crossing is not detected as raised.
I think EveryDoor should consider any value for traffic_calming as valid for raised (and keep using a default of yes or use ID default value)

Huh. iD indeed adds the table value when you check the box. The preset uses an undocumented feature. I'll look into that.
And yes, I agree it should treat any value as "yes".

Done in 3.2.


Update customer-lockbox-requests.md

Added a note about using PowerShell to approve/deny customer lockbox requests

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2483

@JohanFreelancer9  Please copy review

Please also confirm that the link is correct.

updated the link.

@KCCross Please merge this PR. Thanks


support dots in brackets

@bkendall

@bkendall

I added a few more tests for you. If those pass, looks good :)

:+1: thanks


Allow GOVERSION to be overridden

The fix in #818 appears to block the ability to specify a GOVERSION other than the go.mod value. In my own scenario, I deploy a library with associated binaries, compile the binaries with the latest version of Go, but leave the go.mod a few releases back to avoid forcing an upgrade on anyone importing the library. Would it be possible to default to GOVERSION if it is defined, or to give a configuration option to allow injecting a version to use?

#850 seems to take an osv-scanner configuration specific approach, which is fine, but is there any value in also supporting the Go native way of doing things via a toolchain directive (if present)?
I assume precedence (from highest to lowest) would go:

config override
toolchain directive
go directive

That sounds reasonable to me, no need to block #850 for this change, but let's keep this issue open until we add a tool chain version extraction as well.


parfors fails to lower

This fails to lower
import numpy as np
from numba import njit, prange
@njit(parallel=True)
def foo(n):
    d = np.zeros(n+1)
    a = np.zeros(n)
    for i in prange(n):
        a[i] = 1
    return a

print(foo(4))

yields:
  File "<path>numba/numba/errors.py", line 253, in new_error_context
    yield
  File "<path>numba/numba/lowering.py", line 216, in lower_block
    self.lower_inst(inst)
  File "<path>numba/numba/lowering.py", line 360, in lower_inst
    parfor.lower_parfor_parallel(self, inst)
  File "<path>numba/numba/npyufunc/parfor.py", line 49, in _lower_parfor_parallel
    assert parfor.params
numba.errors.LoweringError: Failed at nopython (nopython mode backend)

switching  d = np.zeros(n+1) to  d = np.zeros(n) works, but d should be dead.

Ping @DrTodd13 @ehsantn @ninegua

Changing line 49 in npyufunc/parfor.py from assert parfor.params to:
assert parfor.params != None

would fix the problem.

Fix is now put in PR #2492

Closing as #2492 is merged.


Support Complex and Nested Types

Review Owner: @ravipesala

[x] Nested Types-Support to create cube with Complex Types(Array,Struct) with nesting	[@nareshpr]	[13-04-2016	to	16-04-2016]
[x] Nested Types-Carbon Store to support complex types 	[@nareshpr]	[13-04-2016	to	16-04-2016]
[x] Nested Types-Handle Complex and nested types in data load	[@nareshpr]	[13-04-2016	to	16-04-2016]
[x] Nested Types-Support Complex datatypes in select statement(projection)	[@nareshpr]	[13-04-2016	to	16-04-2016]
[x] Nested Types-Support Complex datatypes in filter	[@nareshpr]	[13-04-2016	to	16-04-2016]
[x] Nested Types-Support UDF for complex data types	[@nareshpr]	[13-04-2016	to	16-04-2016]

closing as already handled


[release-4.7] Bug 1924523: Ensure the github.com/gogo/protobuf dependency uses the v1.3.2 version.

Manual cherrypick of #56
Also bumps the Golang version to 1.15 to keep in sync with the Golang version we've already been using for this release.
Ensure the github.com/gogo/protobuf dependency uses the v1.3.2 version.
This was done by running the following commands locally:
$ go get<EMAIL_ADDRESS>$ go mod vendor && go mod tidy && go mod verify
$ go list -mod=readonly -m all | grep gogo/protobuf
github.com/gogo/protobuf v1.3.2 => github.com/gogo/protobuf v1.3.2

/lgtm
/bugzilla refresh

/bugzilla refresh

/bugzilla refresh

/bugzilla refresh
/lgtm

/bugzilla refresh

/retitle [release-4.7] Bug 1924523: Ensure the github.com/gogo/protobuf dependency uses the v1.3.2 version.

/bugzilla refresh


findAllRefs doesn't work for property of typeof import("./foo")

TypeScript Version: 3.2.0-dev.20181006
Code
/// <reference path="fourslash.ts" />

// @Filename: /a.ts
////export const [|x|] = 0;

// @Filename: /b.ts
////function f(a: typeof import("./a")) {
////    a.[|x|];
////    a.[|x|];
////}

verify.singleReferenceGroup("const x: 0");

Expected behavior:
Test passes.
Actual behavior:
Test fails. The references in function f aren't found.

I wonder if a fix for this would enable typescript to be able to track React component usage across React.lazy boundaries.
// a.tsx
export default function AComponent() {
  return null
}

// b.tsx
// does not count as a reference for either "AComponent" or "default"
const LazyAComponent = React.lazy(() => import('./a'))

This would involve being able to make the "typeof" a thing also be a reference to "thing".
Unless some "advanced magic" was involved this probably wouldn't be able to track it all the way to the actual usage site of LazyAComponent, but at least finding the place where it is transformed into a different component would be a big help.


Do not save drafts until typing has stopped for X milliseconds

Summary
Currently, we were saving drafts for messages being typed into the post and comment textboxes on animation frames which can occur quite frequently. Saving drafts also seems to be less performant on some browser/OS/device combinations than on others. They also fire off a number of dispatches and change redux state which can negatively impact performance too. During some local testing, where I added a console log for each draft save, I was seeing it saved on every single key press which is 1) saving significantly more often than necessary and 2) could be negatively impacting performance, particularly in certain environments.
This is after typing about 100 characters into the post textbox:

In addition some very useful profiles from the community on Firefox are showing saveDraftFrame being called about every 100ms during typing and was taking up the majority of the JS processing time in the profile:

This PR moves from using animation frames to save the draft to a more controlled setTimeout which will only save the draft after 500ms of no typing has occurred (or the component unmounts).
Release Note

Improve typing performance in affected environments by reducing the frequency at which drafts are saved

@jgilliam17 can you test to make sure that post and comment drafts are still saved correctly?

Found a minor issue with the comment button staying disabled too long that might be related to this change. Going to investigate that

Fixed the issues. @jgilliam17 can you smoke test commenting on posts/threads with this change too?

Also @jgilliam17 (and anyone else) please leave the test server up since I'm going to ask some people to create accounts and see if improves performance for them

@jwilander Do we have a Jira ticket for this?

No, I didn't create one since it was a bit reactionary. I can create one if you want, though.

I'll add one as a reminded to test again after merge. 🙂


Harvester:  virtualCluster namespace filter & singleVirtualCluster feat and bug fix

Enhancements to the NamespaceFilter component to support harvester cluster namespace filtering
Commit: https://github.com/rancher/dashboard/pull/4293/commits/4ed9c32fd14b3b45910a792bb0b7c2c028876575

Enhanced Scheduling component for adapting VM node scheduling
Commit: https://github.com/rancher/dashboard/pull/4293/commits/ab94c161a5b81b44849b7349574634c9af02f6ec

Add the isSystemResource attribute to resource-instance to filter the list of harvester clusters

singleHarvesterCluster feat and bug fix

@nwmac   Done. Thanks for your review. Could you review it again.  thanks.

@WuJun2016 How does the system namespaces setting get populated?

https://github.com/rancher/dashboard/pull/4293/files#diff-2886ae8dc0ffc0d351cc2e75fe977ac32d0067891113a6ec3c25c3761edb9633R545-R550
system-namespace is the value populated by the back-end.


Creating instance from a cloned mesh makes the cloned mesh and its instances disapear

This is the example - https://www.babylonjs-playground.com/index.html#QE7KM#130
If you clone a mesh that already has instances and then create an instance from the cloned mesh, the original mesh and its clones are not being rendered. Their position and bounding info stays correct.
If you clone a mesh with no instances and create an instance it works correctly - https://www.babylonjs-playground.com/index.html#QE7KM#131 .

This is a known limitation. You need to first call clone.makeGeometryUnique() before being able to createInstance.


apriltag_mit: 2.0.0-1 in 'iron/distribution.yaml' [bloom]

Increasing version of package(s) in repository apriltag_mit to 2.0.0-1:

upstream repository: https://github.com/ros-misc-utilities/apriltag_mit.git
release repository: https://github.com/ros2-gbp/apriltag_mit-release.git
distro file: iron/distribution.yaml
bloom version: 0.12.0
previous version for package: 1.0.3-1

Holding for Iron sync


W002 check should be case insensitive

Over at the html5boilerplate project, they recently changed the recommended x-ua-compatible meta tag to be lowercase: https://github.com/h5bp/html5-boilerplate/issues/1656

Hi,
Just spend some time with an upper case missing
$('head>meta[http-equiv="X-UA-Compatible"]').attr('content').match(/IE=edge/i) != null
And will handle the Chrome version (chrome=1) even it's deprecated

And will handle the Chrome version (chrome=1) even it's deprecated

We want to warn about it. See #152.

agree with you but this tricks make it's right with no case sensitive

Meh. Any capitalization besides IE=edge or ie=edge is bizarre/insane.

Too bad, emmet will generate <meta http-equiv="X-UA-Compatible" content="ie=edge"> when i typed !<tab>. And I still having error and have to change ie=edge into IE=edge.


ROX-7771: Re-enable Indentation codenarc rule

Description
Enable codenarc rule that was disabled during bump of gradle:

https://github.com/stackrox/stackrox/pull/4924

Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI style
make -c qa-tests style

/test

/test osd-gcp-qa-e2e-tests

@gavin-stackrox Looks like everything is green 💚


feat: Change to typescript and vite

I am having a slightly hard time following the code in some places and think that Typescript would help make it more clear.
Although Vite is not designed to work with Node and something more low-level would be a better choice, this is working.
I ran all the tests, and the only thing that is missing is testing the parse-server-gcs-adapter which is likely not working because of the require call.

Looks great, much cleaner 👍


Bump version from 2020.7.6 to 2020.7.28

Issue Number

N/A
Overview

[ ] I have bumped version from 2020.7.6 to 2020.7.28

Comments

bors r+


make /lockable-resources /api accessible

Dependencies
None
Feature Request
With a couple minor changes, we can enable the standard /api API to retrieve lockable resources as JSON or XML.  This has been very helpful for my deployment.  Here is a PR with the changes:
https://github.com/jenkinsci/lockable-resources-plugin/pull/256

Recently merged, closing the issue.
Just in case: is #103 related to this?


Bump elixir and otp in docker

ping

@princemaple thanks, I missed the notification!

I needed to reverse to OTP 24, because the image fails to build for arm. Minimal Dockerfile:
FROM hexpm/elixir:1.14.0-rc.0-erlang-25.0.3-debian-bullseye-20210902-slim

# mix local.hex --force fails, but looks like it's the mix script itself
RUN mix --version

Cross-building for arm results in a segfault
docker build --platform linux/arm64 -t arm_test .

Can be further simplified to:
FROM erlang:<IP_ADDRESS>-slim
RUN rebar3 --version

And it works fine on <IP_ADDRESS>.

It's an issue with QEMU that Docker uses to cross-build images for arm, see https://github.com/hexpm/bob/issues/117. So we likely need to build the arm image on an actual arm instance.


Automatic Arch support and handpicked iasl version

Here's some changes I made to your version of the script with some inspiration from @kdkavanagh (source)
Changelog

Downloads this specific version of iasl (https://acpica.org/sites/acpica/files/acpica-unix2-20181031.tar.gz)
Detects if the user is running a Debian/Ubuntu based distro or an Arch based distro by checking which package manager is installed.
Removed the outdated "acpi-tools" from being installed bia apt-get because a newer version was aleady manually picked out and installed.

Room for improvement
I ended up leaving a trail of installation tools installed that some end users might not want to keep on their system. I tried to avoid having to install Yay, but it was just simpler for me to install it an use it.
I'm still a little new to using git, so I accidentally pushed to my forked master branch first, so I merged it with the x1y3 branch and reverted the commit to the master branch after that.

I hope it's not too weird that I forked your repo instead of the main one. @fiji-flo doesn't seem too interested in continuing the project, and I don't blame him. He doesn't have to worry about this problem on the Carbon model.

Thanks for pinging me on this. I'll do better. Feel free to do a PR against my repo.

I agree about having an opt-in prompt for the dependencies. At this moment, I'm unsure how to do that, but I'm sure it's just a Google search away for me.

Sounds great. You'll figure it out. Ping me if you need help.
Feel free to open a PR (https://github.com/fiji-flo/x1carbon2018s3/compare/master...ryankhart:master)


add script

The file is not shown in the Shardeum Docs during testing locally
and I think this should be linked potentially outside the docs since this is a very large file.
We can discuss this on Telegram.


Modify shortcuts/mappings

Hi, I've tried to change the default 's' escape key so that vimsidian stops calling its functions when I press something like
'sd' or 'sj'. I've modified my init.vim commenting what I thought was the mappings but nothing happened. The shortcuts kept working the same way.
I previously created a new function (daily_journal_note) to write daily notes on another path to differentiate study notes from daily ones, but i haven't been able to find anything about shortcuts on those files. I thought everything about mappings was defined in init.vim, and now I'm kind of lost. For now, I've changed the way vimsidian opens new files so that I don't lose changes on the current one.
Any guidance?
Cheers.

I think I found something doing some research (:verbose nmap ). Due to the  statement, the mapping is inserted in the view of the document. What I don't know yet is why I can't modify that record from init.vim. I guess it's because that local map is done just once in the view creation. What I'm gonna do now is remove all lines from init.vim and delete the mapping from each view manually.
Still, I'd appreciate some help.
Cheers.


Add inviscid unsteady test

Adds a test for unsteady FUN3D+TACS fully coupled discipline derivatives. Right now, this only tests inviscid along the aeroelastic path. Currently, the structural functions are failing while lift and drag seem to be passing. However, changing flow_dt in the Python run script seems to have no impact on the test results. Changing the time step set to TACS also has limited effect.

Can you remove the .DS_store files?


[sw, dif] Introduce AES smoke test

[sw, dif] Introduce AES smoke test
This change introduces an AES smoke test that is refactored copy of sw/device/tests/aes_test.c to use dif_aes. The original test has not been removed (should be done by the SCA/HW team) in case there is need to compare performance between two, etc...
Due to C strict aliasing u8 pointers cannot be freely cast into u32 pointers, which makes the API somewhat cumbersome to use (see in_data, out_data and key_share packing through memcpy).

Had to change static const kKeySize... to be defines, as CI was failing due to GCC not being happy with kPlainText[kKeySize...].

Had to change static const kKeySize... to be defines, as CI was failing due to GCC not being happy with kPlainText[kKeySize...].

Added back the smoke test config for aes.

Added back the smoke test config for aes.


[boost-python] linkage error

The boost-python debug version links to the non-debug version of python, this causes linker errors while boost-python is used in a debug configuration.

Duplicate with #5097.


Add pipeline descriptor

As a Pipeline Builder I want to be able to add pipeline descriptor to the pipeline's Repository.
User Story implementation details:

Upon reception of add pipeline request, HKube will perform the following validation checks:
1.1 Verify that there isn't another pipeline descriptor with the same name in the P.L repository, so the Pipeline Builder won't override by mistake another pipeline descriptor.
1.2 Verify that all of the algorithms which are used in the pipeline descriptor are installed in the system.
If one of the validation checks will fail, HKube will response with error and appropriate error description.
If all the validation checks will pass, HKube will add the pipeline descriptor to the P.L repository.

TID-320

all issues with asserting that all algorithms are present,
are being closed for now (only if they pass without this requirement). adding an issue that this task should be implemented .
once the requirement is implemented a test will be written and tested as part of this test

Fetch all pipeline descriptorsTest
File: tid_310.js
describe : "pipeline actions"

Test
description

TID-340- get all pipeline (git 70 41)
validate  Fetch all pipeline

TID-330- delete pipeline (git 69 41)
validate delete pipeline

TID-320 add the same pipeline twice (git 67 41)
validate that cant have two pipelines with the same name


pin go-swagger 0.7.4

This pins the version of go-swagger used, because
the results generated by different versions
can differ quite a bit (tested between 0.7.2 - 0.7.4),
and can cause CI / validation to fail.

LGTM


Add parameter to "only renew certificate when outdated"

I ran into the issue that I hit the rate limits of letsencrypt (https://letsencrypt.org/docs/rate-limits/), because I have lots of subdomains and generate a certificate via win-acme on every deployment (maybe that's not best practice altogether but lets ignore this for now...)
As the scheduler renews the certificate anyway, it would help if the tool can look into existing certificates first and use it to set it to the iis binding instead of generating a new one.

maybe that's not best practice altogether but lets ignore this for now...)

Let's not ignore the fact that you seem to have an uncommon setup. Understanding why and how you do things might lead to a better solution than the one you proposed.
So do you actually recreate the IIS bindings on each deployment of your application?
Because if you don't, there's no need to run WACS, because the bindings will keep working. You'd only have to run it when you add another (sub)domain.

I'm going to close this issue due to it being quiet in the thread for a long time. Please feel free to post again though if you keep having issues with the latest release. Thanks for using WACS and providing us with feedback.


pvc stays pending on K3s v1.26.4+k3s1 and namespaced docker

I use a setup with namespaced docker daemon (to be able to run systemd in containers with cgroups v2). Up to K3s v1.26.3+k3s1 everything worked fine. With K3s v1.26.4+k3s1 the pvc stays in the Pending status, and so does the pod that tries to use the provisioned volume.
The steps to reproduce on Ubuntu 22.10 are:
# apt update
# apt install -y docker.io
# echo -e "dockremap:$( id -u ):1\ndockremap:200001:65535" | sudo tee -a /etc/subuid
# echo -e "dockremap:$( id -g ):1\ndockremap:200001:65535" | sudo tee -a /etc/subgid
# echo '{ "userns-remap": "default" }' | sudo tee /etc/docker/daemon.json
# systemctl restart docker
# curl -s https://api.github.com/repos/Mirantis/cri-dockerd/releases/latest | jq -r '.assets[].browser_download_url' | grep jammy_amd64.deb | tee /dev/stderr | xargs curl -LO
# apt install -y ./cri-dockerd_*.deb
# mkdir /etc/systemd/system/cri-docker.service.d
# ( echo '[Service]' ; echo 'ExecStart=' ; sed 's/ExecStart=.*/& --network-plugin=/;t;d' /lib/systemd/system/cri-docker.service ) | sudo tee /etc/systemd/system/cri-docker.service.d/network-plugin.conf
# systemctl daemon-reload
# systemctl restart cri-docker
# curl -sfL https://get.k3s.io | sh -s - --write-kubeconfig-mode 644 --container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --kubelet-arg=cgroup-driver=systemd --egress-selector-mode=disabled
# cat > test-local-path.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: test-pvc-1
  namespace: default
spec:
  accessModes:
    - ReadWriteOnce
  storageClassName: local-path
  resources:
    requests:
      storage: 1Gi
---
apiVersion: v1
kind: Pod
metadata:
  name: test-local-path
spec:
  restartPolicy: Never
  containers:
  - name: freeipa-server
    image: busybox
    imagePullPolicy: IfNotPresent
    volumeMounts:
    - name: data
      mountPath: /data
  volumes:
  - name: data
    persistentVolumeClaim:
      claimName: test-pvc-1
<Ctrl-D>
# kubectl create -f ./test-local-path.yaml

Wait at most two minutes, then try
# kubectl get pvc
# kubectl events pvc/test-pvc-1

With K3s v1.26.4+k3s1 I now get
# kubectl get pod
E0426 09:07:51.196603    9853 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0426 09:07:51.202042    9853 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0426 09:07:51.203084    9853 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0426 09:07:51.204857    9853 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
NAME              READY   STATUS    RESTARTS   AGE
test-local-path   0/1     Pending   0          8m3s

# kubectl events pvc/test-pvc-1
LAST SEEN             TYPE      REASON                    OBJECT                                  MESSAGE
11m                   Normal    Starting                  Node/k3s-13-ubuntu-22-10.example.test   Starting kubelet.
11m                   Warning   InvalidDiskCapacity       Node/k3s-13-ubuntu-22-10.example.test   invalid capacity 0 on image filesystem
11m (x2 over 11m)     Normal    NodeHasSufficientMemory   Node/k3s-13-ubuntu-22-10.example.test   Node k3s-13-ubuntu-22-10.example.test status is now: NodeHasSufficientMemory
11m (x2 over 11m)     Normal    NodeHasNoDiskPressure     Node/k3s-13-ubuntu-22-10.example.test   Node k3s-13-ubuntu-22-10.example.test status is now: NodeHasNoDiskPressure
11m (x2 over 11m)     Normal    NodeHasSufficientPID      Node/k3s-13-ubuntu-22-10.example.test   Node k3s-13-ubuntu-22-10.example.test status is now: NodeHasSufficientPID
11m                   Normal    NodeAllocatableEnforced   Node/k3s-13-ubuntu-22-10.example.test   Updated Node Allocatable limit across pods
11m                   Normal    NodeReady                 Node/k3s-13-ubuntu-22-10.example.test   Node k3s-13-ubuntu-22-10.example.test status is now: NodeReady
11m                   Normal    Starting                  Node/k3s-13-ubuntu-22-10.example.test
11m                   Normal    Synced                    Node/k3s-13-ubuntu-22-10.example.test   Node synced successfully
11m                   Normal    RegisteredNode            Node/k3s-13-ubuntu-22-10.example.test   Node k3s-13-ubuntu-22-10.example.test event: Registered Node k3s-13-ubuntu-22-10.example.test in Controller
11m                   Normal    WaitForFirstConsumer      PersistentVolumeClaim/test-pvc-1        waiting for first consumer to be created before binding
3m14s (x4 over 11m)   Normal    Provisioning              PersistentVolumeClaim/test-pvc-1        External provisioner is provisioning volume for claim "default/test-pvc-1"
79s                   Warning   FailedScheduling          Pod/test-local-path                     running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition
74s (x4 over 9m)      Warning   ProvisioningFailed        PersistentVolumeClaim/test-pvc-1        failed to provision volume with StorageClass "local-path": failed to create volume pvc-c2f655e4-6aad-426e-a3f2-856cbe257c4e: create process timeout after 120 seconds
72s (x43 over 11m)    Normal    ExternalProvisioning      PersistentVolumeClaim/test-pvc-1        waiting for a volume to be created, either by external provisioner "rancher.io/local-path" or manually created by system administrator

When I create the K3s with
# curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.26.3+k3s1 sh -s - --write-kubeconfig-mode 644 --container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --kubelet-arg=cgroup-driver=systemd --egress-selector-mode=disabled

I get the pvc Bound and the container Completed.
Any clues or pointers how to debug this would be appreciated.

Checking kubectl logs pod/local-path-provisioner-76d776f6f9-brl96 -n kube-system shows
E0426 09:20:34.628342   16212 memcache.go:287] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0426 09:20:34.629382   16212 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0426 09:20:34.632212   16212 memcache.go:121] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I0426 09:00:06.509644       1 controller.go:811] Starting provisioner controller rancher.io/local-path_local-path-provisioner-76d776f6f9-brl96_44de8247-1068-4d56-8570-22f1f7e55856!
I0426 09:00:06.612062       1 controller.go:860] Started provisioner controller rancher.io/local-path_local-path-provisioner-76d776f6f9-brl96_44de8247-1068-4d56-8570-22f1f7e55856!
I0426 09:00:06.612969       1 controller.go:1337] provision "default/test-pvc-1" class "local-path": started
time="2023-04-26T09:00:06Z" level=info msg="Creating volume pvc-c2f655e4-6aad-426e-a3f2-856cbe257c4e at k3s-13-ubuntu-22-10.example.test:/var/lib/rancher/k3s/storage/pvc-c2f655e4-6aad-426e-a3f2-856cbe257c4e_default_test-pvc-1"
time="2023-04-26T09:00:06Z" level=info msg="create the helper pod helper-pod-create-pvc-c2f655e4-6aad-426e-a3f2-856cbe257c4e into kube-system"
I0426 09:00:06.616747       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-pvc-1", UID:"c2f655e4-6aad-426e-a3f2-856cbe257c4e", APIVersion:"v1", ResourceVersion:"470", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/test-pvc-1"
W0426 09:02:07.129975       1 controller.go:937] Retrying syncing claim "c2f655e4-6aad-426e-a3f2-856cbe257c4e" because failures 0 < threshold 15
E0426 09:02:07.130028       1 controller.go:957] error syncing claim "c2f655e4-6aad-426e-a3f2-856cbe257c4e": failed to provision volume with StorageClass "local-path": failed to create volume pvc-c2f655e4-6aad-426e-a3f2-856cbe257c4e: create process timeout after 120 seconds
I0426 09:02:07.130064       1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"test-pvc-1", UID:"c2f655e4-6aad-426e-a3f2-856cbe257c4e", APIVersion:"v1", ResourceVersion:"470", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "local-path": failed to create volume pvc-c2f655e4-6aad-426e-a3f2-856cbe257c4e: create process timeout after 120 seconds

in a loop but not a real description of the problem.
No directory exists under /var/lib/rancher/k3s/storage/ but I cannot rule out that a directory got created and then deleted. Running stat on the directory shows Modify: 2023-04-26 09:00:06.809976956 +0000 so that would be higher than the 09:00:06.612969 timestamp in the log.

Hint from https://stackoverflow.com/questions/71601496/unable-to-create-a-pv-due-to-vol-dir-parameter-not-set/71605241#71605241 pointed to by https://github.com/rancher/local-path-provisioner/issues/39 worked -- running
kubectl apply -f https://raw.githubusercontent.com/rancher/local-path-provisioner/v0.0.21/deploy/local-path-storage.yaml

made the pvc immediatelly Bound.

Thanks for raising the issue. Will check and fix it soon.

Same for me thanks @adelton  i downgrade and it works !

@derekbit Were you able to figure out what might be causing the problem? I just checked fresh k3s v1.27.7+k3s2 installation and the issue seems to be still present there ...

@derekbit Sure. Will check it soon.
@yodatak Which version did you down grade?

@adelton
I would like to clarify the issue more.
Does the issue happen in v1.26.4+k3s (v1.27.7+k3s2) with v0.0.24, but not happen with v0.0.23?

Yes, v1.26.4+k3s with v0.0.24 fails (gets stuck in the Pending state), with v0.0.23 it passes.

@adelton
Fixed in https://github.com/rancher/local-path-provisioner/pull/370. Thanks.


pythonPackages.sphinxcontrib-tikz: init at 0.4.6

Limited texlive package to minimal packages schema-small + standalone + pgfplots
Motivation for this change
I want tikz for my documentation (nothing beats tikz in editable graphics :) )
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

I have verified that this works locally with my documentation.

@GrahamcOfBorg build python2Packages.sphinxcontrib-tikz python3Packages.sphinxcontrib-tikz

@dotlambda I am not completely sure how to write the patch to include texlive. That is why I have not finished this PR.

You get a checkout of the source code and look for all places where a texlive binary is called, let's say the code is Popen('pdflatex'). You replace this by Popen('@texlive@/bin/pdflatex'). Then you save the diff as e.g. binary-paths.patch and add
patches = [
  (substituteAll {
    src = ./binary-paths.patch;
    inherit texlive pdf2svg;
  })
];

@GrahamcOfBorg build python2Packages.sphinxcontrib-tikz python3Packages.sphinxcontrib-tikz

@dotlambda I have created the patch (that was fun to figure out how to do with git). I have checked that documentation that uses this package works properly. Ready for merge

Ping ready for merge


Metrics-syncer changes

-- enforce timeout in throttler
-- fix typos in logs
-- use map-from-keys instead of loop

@dposada this PR has had code changes since you last approved.
I added how we monitor failed websocket requests by moving the registration outside the callback in ws/connect!

RTM

RTM


BST added

Fixes #4

It’s showing 41 files because your branch has extra changes from earlier commits. To fix it, create a new branch from the main branch, add only the new file, and push that branch. Then make a PR again. This will ensure only the new file is included.

I didn't do any extra changes I already told you this will happen coz it's
giving an error that's why I had to make this change its giving error
cloned successful and failed I already told you this before tho
On Fri, 22 Nov, 2024, 6:32 pm T Mohamed Yaser, @.***>
wrote:

It’s showing 41 files because your branch has extra changes from earlier
commits. To fix it, create a new branch from the main branch, add only the
new file, and push that branch. Then make a PR again. This will ensure only
the new file is included.
Screenshot_20241122_183053_Chrome.jpg (view on web)
https://github.com/user-attachments/assets/43730e57-5127-4f7e-9a1c-d295f4e4be9e
—
Reply to this email directly, view it on GitHub
https://github.com/Yaser-123/Cpp-Fundamentals/pull/6#issuecomment-2493716200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBN3EP5NK5ETIDW2HAWO4WT2B4TPPAVCNFSM6AAAAABSI2KLR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTG4YTMMRQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I understand, but the PR is showing unrelated files because your fork isn’t fully synced with the main repo. To fix this:

Sync your fork with the main branch.
Create a new branch from the synced fork.
Add only your changes and make a new PR.


Include latest gameobject creation changes

Description
Include latest gameobject creation changes from https://github.com/spatialos/gdk-for-unity/pull/1332
Tests

[x] local fps

Documentation

[x] changelog

Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.

replaced by https://github.com/spatialos/gdk-for-unity-fps-starter-project/pull/261


Integrate Mayhem

I'm getting the same issue even when I try to fuzz the binary in REPL mode; in Mayhem, nearly every test case is a crashing test case but I can't reproduce the crash when the test case is run locally in a Docker container.
I can't see any stdout/stderr Mayhem logs either for debugging. The event log seems fine.

Looking at this more closely - is this just a Python interpreter? I don't expect fuzzing to be particularly interesting in this case. I do notice a tests/ dir here that may have more relevant/interesting test cases, but as it stands fuzzing an interpreter (or a compiler), while can occasionally be interesting, is usually not useful or effective (most test cases will be thrown away by the lexer).

There is indeed a good variety of test cases in that folder, and even without it Mayhem is able to discover quite a few. But even when I upload the corpus, every test case is still (spuriously?) crashing the binary.

Hmm, I'm still not clear on what you mean. I'm only seeing a bunch of test .py files and some Python scripts to run them through the same pycopy binary and compare them to some expected output. Harnessing those scripts would be identical to the current behavior, I think--could you give an example of the kind of module you'd like to see harnessed?

Bump on this

See the integration for micropython here:
https://github.com/mayhemheroes/micropython/pull/2/files#diff-9bb2346f245f1620fcde4a99925baac2ebca0d2d2957dfbf38937b9476f77b4f
This was based off of the following example:
https://github.com/micropython/micropython/blob/6e71cde6aad2b2ed3d431d8d94c9bd2ee52e319d/examples/embedding/hello-embed.c
There are similar examples in this project, such as :
https://github.com/mayhemheroes/pycopy/blob/master/examples/usercmodule/cppexample/examplemodule.c
Of course you may select whatever you like.

Please review and see if any new harnesses can be added, otherwise this will be closed due to inactivity.

I appreciate the pointers. Unfortunately, though, I don't think I have time to see this one through right now.


warnings in prepare.py step

dear developers
i ran the try_benz tutorial in my workstataion.  while running prepare.py the following warining came. Please suggest whether  these errors can safely avoidable and does not affect the final kon, koff values to a large extent. in case of large effect please suggest the source of error and possible way to avoid these errors.
(SEEKR) cadd-sys3@caddsys3:~/Documents/seekr_tutorial$ python /home/cadd-sys3/setupfiles/seekr2/seekr2/prepare.py input_tryp_ben_hidr.xml
Warning: importing 'simtk.openmm' is deprecated.  Import 'openmm' instead.
Vpmg_ctor2:
Warning: External energies are not used in BCFL_MAP calculations!
Vpmg_ctor2:
Warning: External energies are not used in BCFL_MAP calculations!
MGparm_check:  you're using a very small nlev (1) and therefore
MGparm_check:  will not get the optimal performance of the multigrid
thanking you in anticipation

This is the same set of warning mentioned in https://github.com/seekrcentral/seekr2/issues/17#issuecomment-1305944283
In short, these errors are safe, and should not affect the outcomes of any SEEKR2 calculations.


Lazy Loaded Module Inside Another Module Imported w/ .forRoot() Doesn't Load

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
macOS Sierra

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.26
node: 6.5.0
os: darwin x64
@angular/common: 2.4.5
@angular/compiler: 2.4.5
@angular/core: 2.4.5
@angular/flex-layout: 2.0.0-beta.3
@angular/forms: 2.4.5
@angular/http: 2.4.5
@angular/material: 2.0.0-beta.1
@angular/platform-browser: 2.4.5
@angular/platform-browser-dynamic: 2.4.5
@angular/router: 3.4.5
@angular/compiler-cli: 2.4.5

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Create a module with routes, including a lazy loaded route
export const exampleRouting = RouterModule.forChild([
  {
    path : 'examples', component : DefaultLayoutComponent, children : [
    {path : '', redirectTo : 'dashboard', pathMatch: 'full'},
    {path : 'dashboard', component : DashboardComponent},
    {path : 'fake', component : FakeComponent},
    {path : 'lazy', loadChildren : './lazy/lazy.module#LazyModule'},
  ]
  }
]);

Have your module need a .forRoot() function
@NgModule({
  imports : [
    exampleRouting,
    ...other stuff
  ],
  declarations : [DashboardComponent, FakeComponent],
})
export class ExamplesModule {
  static forRoot(): ModuleWithProviders {
    return {
      ngModule: ExamplesModule,
      providers: [MyService]
    }
  }
}

Import this ExamplesModule into your AppModule like so:
imports: [ExamplesModule.forRoot()]

The log given by the failure.
When trying to navigate to the lazy loaded route, I get the following error:
Unhandled Promise rejection: Cannot find module './lazy/lazy.module'. ; Zone: angular ; Task: Promise.then ; Value:

@brtnshrdr Hi! Try to remove './' from the loadChildren path and add the full path, something like  app/lazy/lazt.module#LazyModule

I changed the lazy loaded route to:
{path : 'lazy', loadChildren : 'app/examples/lazy/lazy.module#LazyModule'},
and still get the error:
Error: Cannot find module 'app/examples/lazy/lazy.module.ngfactory'.

I'm seeing this now since upgrading from beta.21-1 to beta.26. It's not generating the lazy loaded module bundles anymore.
My route format is as suggested.
{path : 'lazy', loadChildren : 'app/examples/lazy/lazy.module#LazyModule'}

I believe the core reason for this was https://github.com/angular/angular-cli/issues/2496. It has been fixed meanwhile (after beta.26).


Adding paramaters to onAfterChange

This fixes #50 including documentation. Please re-minify as I don't trust I did that correctly.

Closing as it's now stale.


Feature/complete revamp of github actions

This PR brings order to the CI actions.

Tests and examples are now separated from packaging and deployment tests with FetchContent and conan
For the sake of efficiency coverage stays with tests and examples (but is executed only for gcc-12, shared)
rdf4cpp is tested as a shared and as a static library
Packaging and deployment tests are executed on one compiler only (for now clang-14)

Checkout the actions views of Packaging and deployment tests and Run unit tests and examples. They are much cleaner now. It should be easier to track down where something went wrong and what is still working.
Open question:

[ ] @nkaralis  Do you have any idea why the coverall integration is no longer working? I changed the used compiler from gcc-11 to gcc-12. Might that be a problem? The error can be found e.g. here: https://github.com/rdf4cpp/rdf4cpp/actions/runs/3593178749/jobs/6049803368#step:10:14

I do not know why the coverage stopped working. I will have a look at it as soon as possible and get back to you.


Add retry mechanism when a medium uploads files to an object store

This PR adds a retry mechanism around put_file on the Medium resource when uploading to the remote object store.
When exporting data, the exports are created on the file system and the files have been compressed but when uploading to the object store (s3, azure blob, etc) the put_file call fails (e.g. Faraday::ConnectionFailed: Connection reset by peer) and the export never finishes and the UX shows broken export requests.
The problem is outlined in this error https://app.honeybadger.io/projects/40595/faults/78910693
This error is transient thus we can't really predict the failure mode, thus using the retry mechanism seems a reasonable approach to attempt to avoid this error. Longer term having the our network or object store provider not error on upload seems a more reasonable solution.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

Everything seems fine to me. I have a quick question for my understanding:
* https://app.honeybadger.io/projects/40595/faults/78910693 linked in comments errored on `put_file` of `azure_adapter.rb`, is the `put_file` (of `DirectToS3`) in the PR related?

Sadly yes - see the commit message in https://github.com/zooniverse/panoptes/pull/3655/commits/3740cf1c9dbb2f0cdb5c83cd2793010050acda3d

However as the medium interface is used for DirectToS3 uploader class we need to support this method as it's used in the exporter code.

So all the exporter code re-uses this same interface that now calls put_file_with_retry https://github.com/zooniverse/panoptes/blob/3740cf1c9dbb2f0cdb5c83cd2793010050acda3d/app/models/csv_dumps/dump_processor.rb#L53
so DirectToS3 has to implement that method. I chose to add the retry behaviour instead of a method alias that didn't retry at all as it doesn't hurt to retry this on some kind of failure mode connecting to the object store.
FWIW - DirectToS3 is/was a workaround class (it's really a ducktype of Medium but uses a different storage adapter) to write code to a different bucket in S3 vs the default for normal media resources (an encrypted one for private data). We re-use this now to write to a different cloud provider vs the default one setup in MediaStorage.adapter (Azure blob). Longer term when we convert the email list exportes / uploaders to write to Azure we can remove the DirectToS3 class.


feat(test): Check that the state service handles errors correctly when committing finalized blocks

Motivation
We recently refactored the process of committing blocks to the finalized state. This PR tests if Zebra handles errors correctly.
Solution
In this PR, we trigger a failure when committing a block, and make sure the state service handles it as expected.
Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?
[ ] How do you know it works? Does it have tests?

Follow Up Work
We might need to do a similar test for the non-finalized state as well.

The new test works well locally.

We could also disable the test by default in CI using #[ignore], and merge it?
Then it will run locally when people ask for it, but it won't break CI or other weird test environments.

We could add some logging to each line in each thread, and see there it hangs in CI?
But that could be a lot of work for a low-priority test.
@mpguerra what do you think? Should we work on this sync test more, or just close the PR and update the ticket with this draft branch?

@mpguerra what do you think? Should we work on this sync test more, or just close the PR and update the ticket with this draft branch?

Let's just close the PR and update with draft branch. Sorry @upbqdn  :(

I discovered that it hangs when there is only 1 CPU available.

You're right, running
taskset 0x1 cargo test -- state_handles_error_correctly

dead-locks since there' no CPU activity. However, running the test on two CPUs like this
taskset 0x3 cargo test -- state_handles_error_correctly

works fine. I was trying to find out where the dead-lock happens, but I didn't manage to figure it out.

Let's just close the PR and update with draft branch.

Sure, I referenced this PR in ticket #2654 so that it's easy to find the description and the comments. I also updated the description of this PR.


⚠ RbxVeri has degraded performance

In f88c6de, RbxVeri (https://verify.triza.dev) experienced degraded performance:

HTTP code: 200
Response time: 1564 ms

Resolved: RbxVeri performance has improved in 0a7b798.


fix: update the script name for speedtest

The speedtest has a wrong name for the script (speedteXt.sh vs speedteSt.sh).
This PR fixes that.
PS: The whitespace trimming is performed automatically by VSCode. I can undo that if needed.

Haha, thx


[WIP] Start work on split direction preselection support

Describe your PR, what does it fix/add?
Support for split direction preselection support. Implements #836.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
This PR is work in progress. The basic functionality works, but there are unhandled edge cases and there is no visual feedback for a preselection existing yet.
I don't have a lot of experience with rendering code, so it would help me a lot if someone could contribute something there.
Is it ready for merging, or does it need work?
No.

Sorry, I completely missed your issue somehow.
Anyways, I think this is a bad idea. Dwindle is a dynamic layout and not manual one like i3.
Why would we want that? Defeats the entire point of dynamic tiling.

I'm coming from bspwm, which is mostly a dynamic tiling wm, but also has some manual features.
I'm currently testing Hyprland on one of my machines.
I have dwindle.preserve_split set, as I don't like my wm to change my layout just because I'm resizing a window.
Usually I want new windows to be placed dynamically, but sometimes I want to put a window at a specific position. With preserve_split this is already kind of possible by opening multiple new windows and then moving windows around and closing some again in the right order (which I don't recommend. I just want to illustrate that the end result is already reachable, just not practical)
This PR would make it possible to bind a new key-combination that allows you to preselect where the next window appears.
When not using the splitpresel dispatcher everything behaves exactly as before. When dispatching the splitpresel dispatcher the position and split direction of the next window will be preselected. After the next window was opened the preselection is automatically deactivated and the default behavior applies again for all further windows.

Feel free. For rendering, I'd encourage not doing that and leaving it to me once everything else in this PR is ready.

This is something I'm also missing, coming from bspwm

Also looking for this functionality. Any ETA?

Closing because

I no longer use Hyprland
Was already implemented by another PR
https://drewdevault.com/2023/09/17/Hyprland-toxicity.html


Wallet scaning is possibly triggered while upgrading

Before upgrading a wallet, it need to be unlocked first,

_wallet_password is set to a value here: https://github.com/BitShares/bitshares/blob/edf9b381284b8abf8eedf1a58f92a0bbb03d82ee/libraries/wallet/wallet.cpp#L1179  thus wallet_impl::is_unlocked() will return true
when the client receives a new block, wallet_impl::block_pushed() will call start_scan() : https://github.com/BitShares/bitshares/blob/edf9b381284b8abf8eedf1a58f92a0bbb03d82ee/libraries/wallet/wallet.cpp#L37

Since the wallet is in an insistent state while upgrading, scanning at the same time may cause trouble.

I was wrong. wallet_impl::block_pushed() won't execute while upgrading wallet.


[Super Issue] Benchmarks

[ ] #673
[ ] #674
[ ] #677
[ ] #676
[ ] #675

Let’s try also:

[ ] revm

@naure I converted all tasks into issues to track them more easily

Reference: https://github.com/scroll-tech/sp1/tree/scroll-dev-0914/examples
(@icemelon correct?)


[loc][Query][VSCode] Please clarify "Process"

Hi, we have a question from our translator. Can you help please? Thanks!
Source:
Process
File Name:
src\vs\workbench\parts\debug\electron-browser\debugViewer.nls.resx
Resource ID:
".resx", 0; "process"
Query:
Is this a verb or a noun?	Cristina Carrasco	11/1/2016 6:24:06 PM

assign to @roblourens first as @roblourens takes over debugging stuff these few days.

It is a noun in that context - added a comment to the nls call


[DOCFIX] Add tar command that saves permissions

Retain permissions when unzipping the tarball so that user logs can be written correctly.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6218/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6220/
Test FAILed.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.1 please

alluxio-bot, cherry-pick this to branch-2.0 please


Please use Unix-style slashes when generating GlobalUsings.cs in Mac/Linux

When applying the lint in a solution in which projects aren't within the same directory, the file incorrectly gets placed on Solution/Project\GlobalUsings.cs as oppose to Solution/Project/GlobalUsings.cs. Please use Path.DirectorySeparatorChar as oppose to \ when concatenating paths so that it works platform-independently.

Thanks for the detailed description (and the correct solution :))!
I completely forgot to test this on something other than Windows.
This should now be fixed in verson 1.2


DockerHub with Private Registries.

When using DockerHub with private registries, it keeps on telling me: 500 Server Error: Internal Server Error ("Could not get container for 0be613fc-dd9d-42da-917f-d3a32679774a" when i enter in docker:<my registry name>/<my image name>:latest for the image to use.
I have setup the registry in Rancher and on the host that i'm trying to deploy to.  Am I missing something?

@jwhitcraft which version of rancher/server are you using? if running in a docker container just do docker inspect. Need the value of CATTLE_RANCHER_SERVER_IMAGE

@hibooboo2,
I am running CATTLE_RANCHER_SERVER_IMAGE=v0.22.0-rc2 and i used this command to start the server: docker run -d --restart=always -p 8080:8080 rancher/server

Ok. So is your registry one through say quay.io, or are you hosting your own?

it's dockers private registry, and even then, if i goto the machine and do a docker pull <registry>/<image> after i login, it pulls fine, but when i try and do it though Rancher, i always get the same error.

Hmm.. So you can do a docker pull on the box. But not when using rancher.

Correct.  I've tried on two different hosts and i get the same error.

Can you send me more of the logs from your server as this seems to not be a problem with pulling it is something else.

here is the full log from the server: https://gist.github.com/jwhitcraft/e0deee5e23c8bd7c5c39
here is the full log from the agent: https://gist.github.com/jwhitcraft/71e810035ec5d051fded

So if you pull the images first on each host and then try launching the containers does that at least work? Just wanting to make sure.

@hibooboo2, it does not.  It seems like thinks it's missing a layer or something.

Yeah that is what it looked like based on the rancher-agent logs. Hard to say since I can't duplicate this locally without a registry using your setup.

Hrmm, since i'm just in the testing phase, i'll delete the registry from docker and re-push it to see if that solves it.

ok

It seems to only be an issue when i link it to my mysql container (not created via Rancher)  I'll try this locally.

so, i just created a new machine on digital ocean and setup mysql and my site again and it worked fine.  I am using the managed networking now, where as before i was using bridged.  I'll chalk this up to trying to use an existing docker install vs a fresh one.

Glad you were able to fix it.


[DIR-1730] integrate tracing with slog

Description

this PR remove grpc from telemetry since we don't use grpc anymore.
also it moves the logging initialization logic earlier so that the debug level setting is also applied to the legacy server.
updates the install.sh with proper configuration for a monitoring installation
integrates open-telemetry whit slog
fixes broken tracing chain for sub-flows and actions
replaces slog in favor for slog.*Context where ever possible to enable tracing
fixing a bug causing a rc in the instance.
fixed a bug in the old pubsub system causing a panic
Some Jest test-cases where fixed

Checklist

[x] Documentation updated if required
[x] Test coverage is appropriate

Checklist Internal

[x] Linear issue linked (e.g. [DIR-XXXX] pull request title)
[x] Has the PR been labeled

this pr will be split into multiple after the bug in CreateInstanceData is fixed

@h8718 TODO: check if the new instance-telemetry-info version logic is not causing crashes

This PR should be ready to be merged


"Unable to find compatible target in system image" when running compiled binary on other machine

Hi,
I'm trying to create portable binary of your commandline_hello example. It's built fine and works on the building machine. But when I copy binaries to the other computer, I get single line "ERROR: Unable to find compatible target in system image.". At the beginning I did it with julia built from source, but switching to portable julia build (either 0.7 or 1.0.2) doesn't help. Both computers have the same Ubuntu 14.04. I also tried third one with Gentoo, result is the same.
My building script is as simple as it can be:
using ApplicationBuilder
build_app_bundle("hello.jl", appname="Hello");

There was large discussion that julia portable requires cx16 CPU flag, and it's not set in some virtual machines, which cause the same problem. But I use real machine, not virtual. And I have this flag in my /proc/cpuinfo. Do you by chance have any suggestions on what can I check and where to look?

Hi, sorry for my unreasonably long delay. :(
This was happening because the default cpu_target in PackageCompiler was native, so it was building specific to your exact CPU.
This was fixed in 28b5528d02 by changing to x86_64 as the default (here: https://github.com/NHDaly/ApplicationBuilder.jl/commit/28b5528d0224e3588f2df9bb41f70bd5c75b833a#diff-ce9a26098d45e7ef68fb851c1f4548c6R179) and made configurable via the cpu_target argument, here: 54dd856c05c408a59cf59408f.
Sorry again for my radio silence, and thanks for the issue report!

Thank you so much!


React/Twig: Fix tooltip styles

In both libraries:

[ ] the position of the icon is wrong
[ ] the arrow is pointing in the wrong place
[ ] the box needs to be variable according to the amount of content there is
[ ] the tooltip only shows when we hover the 'i' symbol, but should show when we hover any part of the dark grey shape
[ ] there is a weird behaviour on hover - see video below

https://github.com/international-labour-organization/designsystem/assets/22772102/e55226bf-473e-4775-a81e-ce9df4241931

@justintemps @inesdgomes Can you elaborate on what you mean when you say "the box needs to be variable according to the amount of content there is"?
Does this mean that the tooltip should not have a max width and should expand in a single line to fill the entire window size and then wrap when it goes beyond it?
Or is the tooltip not intended to be used with very long text and what is the typical length expected to be used in it?

@GGKapanadze in standup suggests using standard scale values to handle the tooltip size (sm, lg, etc..) that would determine width may be also padding. Then the actual position of the tooltip is determined automatically based on how much space is around it.
For the sake of simplicity, let's start with 2 variants.
cc @inesdgomes

@Shashika6 I think you can start on this. We can address the following points without input from design.
the position of the icon is wrong
the arrow is pointing in the wrong place
the tooltip only shows when we hover the 'i' symbol, but should show when we hover any part of the dark grey shape
there is a weird behaviour on hover - see video below
For now assume that there is a 100px and 130px width variant of the tooltip as indicated in figma but be ready to change these widths later.
Also assume that tooltip should be displayed on the right of the hover target by default and then top or bottom if there is no space on the right. I noticed that there is no design for the top and bottom direction for the 130px variant so assume that it is the same as the 100px version but taller.

Hi @bashlk

We're going to update the tooltips' design documentation to reflect the various possible widths and in which cases they should be used, but we won't be able to action it this week. While we don't have detailed guidance, could we make the size change according to the content with two thresholds:

If text is shorter than 50 characters, max. width is 180px
If text is longer than 50 characters, max. width should be 400px
Does this make sense?

As for arrow directions, I think the second option makes more sense: the tooltip try to adapt based on available space to display in an direction that it has space for. Priority of directions should: top, bottom, right, left.

@inesdgomes Yes this is clear enough for us to start working on it.
Just to confirm when you say the priority of directions should be top, bottom, right, left - you mean that when you hover over the i, the tooltip should first try to show above the i and it if there is not space above, show below and so on yes?

@bashlk Yes, that's what I meant. But it's fine to start on the right as well, if that's easier for you. Otherwise, let's stick to top, right, bottom, left.

@Shashika6 we should probably use a library for this. Let's do some homework to find some modern version of popper.js and use that to handle all these weird edge cases.
Very important to find something with zero deps.

For behaviour on mobile,

Tap on the icon to make the tooltip appear
Tap anywhere to make the tooltip go away

Feature
Popper
Tippy

Positioning
Flexible
Flexible

Themes
No
Yes

Animations
No
Yes

Customizations
Limited
Extensive

Performance
Good
Very good

Maintainability
Active
Active

Size
10 KB
20 KB

Based on my investigation the two best candidate's would be popper and tippy.
Since we do not need a lot of customisations Popper would be the best option.
Popper is also more actively maintained and used more in comparison to tippy.

What do you think ? @bashlk @justintemps @GGKapanadze

Plan is to also do a small demo with the tooltip implemented using popper.js.
cc :- @justintemps @bashlk

Hey @Shashika6 great work, that looks nice. @inesdgomes what do you think?

Hi @inesdgomes,

The logic for mobile is when screen size is below medium (Same screen size measuring in other components), the max width remains at 180px.

Small screens (phones): Less than 600px
Medium screens (tablets): 600px to 1024px
Large screens (desktops): 1025px and above

The width of the tooltip will be based on the content and if there is a small text the tooltip will hug the content.

Will have a look at this issue as well @inesdgomes Will make sure the text font is always constant in the tooltips.

@justintemps Should i go ahead with the implementation there are few more changes to be done.

Hey @Shashika6 Can you verify the issue with the fonts that @inesdgomes pointed out? Apart from that, this looks like a good solution to me.

Thanks @Shashika6 What you described for mobile makes sense, just wondering if it should apply only to screens smaller than 600px, rather than 1024px. Let's keep it as it is and we'll test it afterwards on tablets. Thanks!

Sure @inesdgomes for the time being ill leave it as it is, do let me know if this needs to be changed in the future.