ctr-backoffice-frontend Sponsor setting up trial-specific questions

For the sponsor to be able to setup trial specific questions,
the sponsor app should allow creation of QuestionTypes
https://github.com/PharmaLedger-IMI/ctr-workspace/issues

Pre-release v0.8.0 shows experimental feature:

During the editing of trial-specific questions,
it is possible to create new question types (and then define an eligibility
criteria on them). Experimental (there are no features to delete new question types,
and neither to look for similar existing question types).

Meeting 2021-09-14

When adding new trial-specific questions, these should be added to the eligibility criteria by default. It seems to make no sense to have trial-specific questions that are not part of the eligibility criteria.

jpsl: Ok to re-open, but leaving that for after september...


Adding support for building installers?

More of a question for other maintainers, to see if there are strong reasons against.
I'm currently adding an ARM device to nixos-hardware, and have been thinking it would be nice to be able to build the NixOS installer images (whether SD image, or UEFI iso) with the profile baked-in.
With ARM devices, it would be sometimes necessary, as sometimes the kernel requires tweaks and such nonsense.
With your run-of-the-mill x86_64 system it might also be helpful. I'm thinking about those laptops with annoying to setup Wi-Fi, or maybe other "fun" quirks requiring "fun" configuration.
Note that I am not proposing customized images! Only the NixOS installer images.

There's another dimension to this question: would it be acceptable to also provide some sort of "harness" to make cross-compilation easier? I'm thinking about the "first time setup" for a local AArch64 system, when the user has no AArch64 hardware to use to build that installer system. Basically slipstream part of what I already have here so it's easier for end-users.

@Mic92 any opinion for or against?

I think providing installer would still fit into the scope of this project.
I am just not sure how we would provide the CI to make this happen.
Images itself can be hosted in  a github release as I demonstrate here: https://github.com/nix-community/nixos-images/releases/tag/nixos-unstable


Jerky rendering of Command Module Interior tour stop transitions/interpolation

The transitions between tour stops on the Command Module interior model are jerky. Does this have to do with rendering to 100 of the voyager window?
https://3d.si.edu/object/3d/command-module-apollo-11:d8c63e8a-4ebc-11ea-b77f-2e728ce88125
https://user-images.githubusercontent.com/49207360/133305562-9e72f1a2-41ce-4bbd-a8bf-1364e8d39a69.mov

Would be good to get a profile run of this from your machine. I was not able to reproduce it, even on my old phone.

@blundellj Is this still an issue?


ComboBox searching not works properly while using Japanese or Chinese keyboard layout

Describe the bug
ComboBox searching not works properly while using Japanese or Chinese keyboard layout. On further while using Japanese or Chinese keyboard ComboBox PreviewKeyDown does not fire. Please find the sample and video for further reference.
Sample:
ComboBox-Searching-issue.zip
Video:
ComboBox-searching-issue.zip
Steps to reproduce the bug

Run the sample.
Open ComboBox drop-down.
Now, type "devel" note developer item was not highlighted.

Expected behavior
ComboBox searching should works properly while using Japanese or Chinese keyboard layout
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.3.1: 1.3.230502000
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

After further testing, I found that it has something to do with the keyboard. If you use the Microsoft Chinese Simplified Pinyin keyboard, the problem will reproduce.

Hi Team,
Any update on this issue?

@bpulliam it's almost 9 months, any progress? any timeline?


Support transaction oplog operations

Summary
As a common error inside the original repo  mongo-connector issue with sync transactions. This PR provides a change that could support this kind of transaction oplog.
Key Changes

Change the way that the run function process the oplogs documents when it is a transaction oplog entry

See these:
1- https://pypi.org/project/mongo-connector-transaction/
2- https://pypi.org/project/elastic2-doc-manager-transaction/


spi: Fix miso configuration for pb2

The datasheet shows pb2 SPI2 MISO as AF1, not AF2.
TEST=Wired up an stm32g071 and confirmed that SPI2 with MISO on pb2
worked with this change and didn't work without.

Datasheet referenced was DS12232 rev 3, page 49: https://www.st.com/resource/en/datasheet/stm32g071cb.pdf
All the other SPI1/SPI2 AF pin configurations looked OK to me

Yes this is indeed a mistake. Thanks for reporting!


Module '"@ngneat/edit-in-place"' has no exported member 'EditableModule'.

I'm submitting a
Bug report
Current behavior
I am getting an error indicating that the EditableModule is not exported from @ngneat/edit-in-place. I am on @ngneat/edit-in-place version 1.9.0 and using Angular 17.
Expected behavior
As in the documentation https://www.npmjs.com/package/@ngneat/edit-in-place, I should be able to import the EditableModule from "@ngneat/edit-in-place"
Minimal reproduction of the problem with instructions
In Angular 17 app.component.ts, with @ngneat/edit-in-place version 1.9.0 installed:
import { EditableModule } from '@ngneat/edit-in-place';
Typescript error: Module '"@ngneat/edit-in-place"' has no exported member 'EditableModule'.ts(2305)
And ng serve fails
The library is installed and my app is otherwise working, as I have been able to import individual directives and the EditableComponent from @ngneat/edit-in-place
What is the motivation / use case for changing the behavior?
No response
Environment
No response

Hello @Dcode22 I need to push a new version to update the npm documentation. Please refer to the GitHub readme meanwhile

Thanks!


Move the image and tag to a separate config file for podman

Having the image and its tag hardcoded in the generated systemd file would force rerunning install with the same extra parameters. To make it easier for updates and avoid setting those again, move the image and tag to a systemd service config file.

Already implemented in fact: https://github.com/uyuni-project/uyuni-tools/blob/main/mgradm/shared/templates/serviceTemplate.go#L25. The only remaining piece is to create an uyuni-server.service.d/local.conf file with UYUNI_IMAGE=thenewimage:itstag


transformerVariantGroup not work correctly

UnoCSS version
latest
Describe the bug
After some upgrades unocss version, the transformer variant group seems not to be working anymore. Hope you guy take a look in the playground bellow.
<html class="text-gray-900 text-white text-white hover:(text-red-700 no-underline text-red)" />

--> Not transform to
<html class="text-gray-900 text-white text-white hover:text-red-700 hover:no-underline hover:text-red" />

Reproduction
https://uno.antfu.me/play/?html=DwEwlgbgBA7gtAJgB4BsoAtGqgMxQUySgCsBXAZwBcwcBPOAY3wDtL8AnKMNgW3MZZt2APgBQUYAENxUWXKgMUk8uQC8AIjZJKcAObtJ9AJwAGE1C06Y6bvguErNthgD2EDgC4AFJbjt8IHAA7GZQzC5wpMwgHChgzHa%2B1rYAlOoy8rLo-jga6JSUAA7kHgD0pbrc6KQARgB0DC48pVEuDCot4e3k6ZlylJLsuviUGgD6NUrMANa9mcIAEvgoKC6w6Bx2g3a0LqRhLjAA-MClkmKn4BDCQA&config=JYWwDg9gTgLgBAbwFBzgEwKYDNgDsMDCEuOA5gDQpxhQYDOGMAgjDFMAEYCuMwWAnpVQ16jAJIBjYnSHVaDGAFVcEWWwCGuOlmggMUAGrr2mmAHEoELmDVRN23foAiwWhN4A3epQC%2BcLJYgcADkXCoSdHTBSEgYAB6QsOjY6lwANvCYOPhEJMCkABTIqFDp9ABccADaVKhVwRJcdDAQIAC0pWkYweSIcFJp0JXBtGjBcD4AulSTsnQAFtAwjTB0lcWoIY3NrW0LSyvBwzDxMG1ppHAncWfQmqQYcIteUOXXZyfqadGoPrIiCjW1VqclEShUBQAlLJhPJGCw2JweHx%2BFCYaCFJJpEUQag6BIvhhKgBGAB0ACZ0agJGhcMN5qwwGsAPTM%2BggUkLZk-TY%2BaEzWz2HRQPSvYGbK52LTC0VGEy4cyWaxokEaaWOKAuNyeegq1DTPlIIA&options=N4IgTgpgzgDg9gOygSwG4RALgGYEMA2UEAvkA
System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Are you facing this issue on your project or just Playground? I see some inconsistencies on Playground but on an actual app, it seems working.

Sure from my real project. Then I go to the playground to check my config is correct. I use Unocss in my Nextjs company project. Before, this worked well but now, I don't know why but not work anymore --> Break our app style 🥲

Could you provide a minimal reproduction repository? And which version was working properly? Thanks.

Thank you for your quick response <3.
I double check on my project --> The problem is condition grouping rendering 😆.
I use combine like this --> before:(text-red ${isTrue ? 'bg-white' : 'bg-yellow'}) --> Doesn work!
I switch to before:(text-red) ${isTrue ? 'before:(bg-white)' : 'before:(bg-yellow)'}) --> This worked.
I think your team might be adding this to the document 🤔

You're welcome.
Not specifically mentions variant groups but it's already covered in readme: https://github.com/unocss/unocss#scanning


Design: redesign of the home page

We should re-design the homepage to be more presentable and reflect our progress as an organisation.

closing. new stories will be created for specific changes


Factory for initialization of monero_wallet_full subclasses

Adding to the previous pull request: https://github.com/monero-ecosystem/monero-cpp/pull/45 and https://github.com/monero-ecosystem/monero-cpp/pull/41
Initialization of monero_wallet_full and its subclasses has been moved to the abstract factory monero_wallet_factory. This change helps prevent code duplication during the initialization of monero_wallet_full subclasses.
The modification should not impact the functionality of the existing code (please double-check).

Why separate wallet initialization logic to a factory with create_origin() to override, instead of adding create_origin() to monero_wallet_full.h for subclasses to override? In other words, monero_wallet_custom extends monero_wallet_full and overrides create_origin(). This would keep with inheritance and avoid splitting logic which is specific to the full wallet.

Closing as stale. Please re-open if still relevant.


Build causing file already exists error

$ npm run build

><EMAIL_ADDRESS>build /Users/dem/projects/node-slate
> gulp

[10:07:54] Using gulpfile ~/projects/node-slate/gulpfile.js
[10:07:54] Starting 'clean'...
[10:07:54] Starting 'fonts'...
[10:07:54] Starting 'images'...
[10:07:54] Starting 'highlightjs'...
[10:07:54] Starting 'js'...
[10:07:54] Starting 'sass'...
[10:07:54] Starting 'html'...
[10:07:54] Finished 'clean' after 300 ms
[10:07:54] 'highlightjs' errored after 290 ms
[10:07:54] Error: EEXIST: file already exists, mkdir '/Users/dem/projects/node-slate/build/stylesheets'

Release v1.4.3


Add uffizzi connect job to GHA workflow

When configuring Uffizzi with GitHub Actions, we need to pass container registry credentials to Uffizzi via uffizzi connect. While this can be done by manually running the CLI command locally, we should incorporate it into the workflow as a separate job to demonstrate the full end-to-end process for configuring GHA + Uffizzi.

Note: It's not clear if uffizzi connect can overwrite existing credentials, or if we need to run uffizzi disconnect to clear any existing credentials before adding credentials with uffizzi connect.

Note: It's not clear if uffizzi connect can overwrite existing credentials, or if we need to run uffizzi disconnect to clear any existing credentials before adding credentials with uffizzi connect.

That's identified in this ticket https://github.com/UffizziCloud/uffizzi_cli/issues/130

This is implemented.


rebuildOnUpdate is not working in Thumbs Gallery with Two-way Control on RTL

This is my error
TypeError: Cannot set property 'control' of undefined
ourHotelsGallerySwiper.componentWillUpdate
./components/home/ourHotelsGallerySwiper.jsx:50
47 | componentWillUpdate(nextProps, nextState) {
48 | 	if (nextState.gallerySwiper && nextState.thumbnailSwiper) {
49 | 		const { gallerySwiper, thumbnailSwiper } = nextState

50 | 		gallerySwiper.controller.control = thumbnailSwiper;
51 | 		thumbnailSwiper.controller.control = gallerySwiper;
52 | 	}
53 | }
swiperIssue.txt

You can refer code here

In that example images are not displaying swiper


"Cannot set the presence of another user" by using the Presence GraphAPI - changing the presence of another user

Describe the bug
By using the grapAPI with the presence statusmessage function, i get the following error:
"Cannot set the presence of another user... Status: 401 Unauthorized"
I tried this with the graphapi over
https://developer.microsoft.com/en-us/graph/graph-explorer
and with the
Microsoft.Graph.Users.Actions
Powershell Module.
For both with my admin user that has the required consensts . (Presence.ReadWrite)
To Reproduce in Powershell
`Import-Module ActiveDirectory
Import-Module Microsoft.Graph.Authentication
Import-Module Microsoft.Graph.Users
Connect-MgGraph Presence.ReadWrite
$params = @{
statusMessage = @{
message        = @{
content     = "Hey, this is a test"
contentType = "text"
}
expiryDateTime = @{
dateTime = "2024-04-02T20:05:33.2079781"
timezone = "Europe/Berlin"
}
}
}
Set-MgUserPresenceStatusMessage -UserId "UserID" -BodyParameter $params
Disconnect-MgGraph`
To Reproduce in the graphAPI
url: https://graph.microsoft.com/v1.0/users/[UserID]/presence/setStatusMessage Body: {     "statusMessage": {         "message": {             "content": "Hey, this is a test",             "contentType": "text"         }     } }
Expected behavior
Chaning the statusmsg in teams
Screenshots

Hi @N3XPW , this is likely an issue with the Presence API.
Please post this on the Graph Q&A forum where the appropriate team will be able to help you out.


🐛 [firebase_messaging] Error when setting up Firebase Messaging for web: The script has an unsupported MIME type ('text/html').

Bug report
Describe the bug
When I start my web application, I'm unable to use Firebase Messaging for the web.
[firebase_messaging/failed-service-worker-registration] Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('http://localhost:51068/firebase-cloud-messaging-push-scope') with script ('http://localhost:51068/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html'). .

Steps to reproduce
Steps to reproduce the behavior:

Run flutter create bug
Run cd bug
Run flutterfire configure
Choose Firebase project
Add firebase_core as a dependency
Add firebase_messaging as a dependency
Follow the Firebase Messaging Docs for Flutter
a. Generate Application Identity key in Firebase Console: Project settings -> Cloud messaging

Expected behavior
Firebase Messaging should work.

Additional context
#9215 is not helpful because there is Firebase initialized via index.html. I need to initialize via Dart.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Nils-MBP-13-M1-4:app nils$ flutter --version
Flutter 3.7.10 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 4b12645012 (4 weeks ago) • 2023-04-03 17:46:48 -0700
Engine • revision ec975089ac
Tools • Dart 2.19.6 • DevTools 2.20.1

I can reproduce the issue using the steps outlined above and the code sample from the example app. With the example app, I get the error after accepting the permission to allow notifications.
Error: [firebase_messaging/failed-service-worker-registration] Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('http://localhost:55880/firebase-cloud-messaging-push-scope') with script ('http://localhost:55880/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html'). .
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 299:10  createErrorWithStack
dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 355:28            _throw
dart-sdk/lib/core/errors.dart 120:5                                           throwWithStackTrace
dart-sdk/lib/async/zone.dart 1385:11                                          callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                              _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                               _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 166:15           <fn>

I get the same
this is mi firebase-messaging-sw.js
importScripts("https://www.gstatic.com/firebasejs/9.22.1/firebase-app.js");
importScripts("https://www.gstatic.com/firebasejs/9.22.1/firebase-messaging.js");

firebase.initializeApp({
    apiKey: "...",
    authDomain: "....
    projectId: ".....",
    storageBucket: ".....",
    messagingSenderId: "....",
    appId: "...",
    measurementId: "..."
});

const messaging = firebase.messaging();

and this is my index.html
    <script>
        if ('serviceWorker' in navigator) {
           // Service workers are supported. Use them.
           window.addEventListener('load', function () {
             // ADD THIS LINE
             navigator.serviceWorker.register('/firebase-messaging-sw.js');

             // Wait for registration to finish before dropping the <script> tag.
             // Otherwise, the browser will load the script multiple times,
             // potentially different versions.
             var serviceWorkerUrl = 'flutter_service_worker.js?v=' + serviceWorkerVersion;

             //  ...
           });
       }
    </script>

I tried like in 2345 ways, always getting this error after trying to retrieve token
Error: FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope
('http://localhost:5519/firebase-cloud-messaging-push-scope') with script ('http://localhost:5519/firebase-messaging-sw.js'): ServiceWorker script
evaluation failed (messaging/failed-service-worker-registration).

Hi @nilsreichardt,
I've come across similar issues when setting up Firebase Messaging for the web. To address this problem, I've made modifications to the official firebase_messaging plugin for the web. You might find my version helpful in resolving the MIME type error you're facing.
To use this version of the plugin, simply add the following dependency_overrides to your pubspec.yaml:
dependency_overrides:
  firebase_messaging_web:
    git:
      url: https://github.com/Bikram40/firebase_messageing_web.git

Make sure to run flutter pub get after adding the override to fetch the plugin. This should prioritize my version of firebase_messaging_web in your project and hopefully address the error you've mentioned.

I'm experiencing the same issue. After trolling through StackOverflow etc. for hours, I've found some partial solutions that seem to just kick the can down the road (the same/similar service worker error shows up later). Further, several sources say you have to create a custom firebase-messaging-sw.js file, but there is no indication that this is necessary in the documentation (at least from what I've seen).

Same here ... Any fix ?

Same here ... Any fix ?

Add 'firebase-messaging-sw.js' to the web folder.

importScripts("https://www.gstatic.com/firebasejs/9.10.0/firebase-app-compat.js");
importScripts("https://www.gstatic.com/firebasejs/9.10.0/firebase-messaging-compat.js");

firebase.initializeApp({
  apiKey: '........',
  appId: '.......',
  messagingSenderId: '..........',
  projectId: '........',
  authDomain: '...........',
  storageBucket: '...........',
  measurementId: '............',
});
// Necessary to receive background messages:
const messaging = firebase.messaging();

// Optional:
messaging.onBackgroundMessage((m) => {
  console.log("onBackgroundMessage", m);
});

If you are using a real-time database, add databaseUrl.
databaseURL:  'https://..........................firebasedatabase.app',

index.html

Unfortunately, Flutter does not automatically support server work.
In my case this solved the problem.

Same here ... Any fix ?

Sorry, I tested a bit more. It's still unstable. The server work is registered, but it throws additional errors like this. Also, reloading again allowed me to get the token without errors.
AbortError: Failed to execute 'subscribe' on 'PushManager': Subscription failed - no active Service Worker
Update: index.html
  <script>
    // The value below is injected by flutter build, do not touch.
    const serviceWorkerVersion = null;
  </script>
  <!-- This script adds the flutter initialization JS code -->
  <script src="flutter.js" defer></script>
  <!-- <script src="/firebase-messaging-sw.js"></script> -->
</head>
<body>
  <script src="main.dart.js" type="application/javascript"></script>
  <script>
    if ( 'serviceWorker' in navigator) {
      window.addEventListener('load', function (ev) {
        // Fcm init
        navigator.serviceWorker.register('/firebase-messaging-sw.js').then(function(registration) {
          console.log('>>> Service Worker registration successful!');
        }).catch(function(error) {
          console.error('>>> Service Worker registration failed:', error);
        });
        var serviceWorkerUrl = 'flutter_service_worker.js?v=' + serviceWorkerVersion;
        // Download main.dart.js
        _flutter.loader.loadEntrypoint({
          serviceWorker: {
            serviceWorkerVersion: serviceWorkerVersion,
          },
          onEntrypointLoaded: function (engineInitializer) {
            engineInitializer.initializeEngine().then(function (appRunner) {
              appRunner.runApp();
            });
          }
        });
      });
    }
  </script>
</body>
</html>

Same problem here.
Error Log:
Performing hot restart...
Waiting for connection from debug service on Edge...
Restarted application in 265ms.
Permission granted: AuthorizationStatus.authorized
Error: Assertion failed: file:///C:/Users/Justin/AppData/Local/Pub/Cache/hosted/pub.dev/firebase_crashlytics_platform_interface-3.6.16/lib/src/platform_interface/platform_interface_crashlytics.dart:31:12
pluginConstants['isCrashlyticsCollectionEnabled'] != null
is not true
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:3                                        throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 35:3                                         assertFailed
packages/firebase_crashlytics_platform_interface/src/platform_interface/platform_interface_crashlytics.dart 31:28  instanceFor
packages/firebase_crashlytics/src/firebase_crashlytics.dart 24:69                                                  get [_delegate]
packages/firebase_crashlytics/src/firebase_crashlytics.dart 192:22                                                 setCrashlyticsCollectionEnabled
packages/mindstreamers_app/main.dart 71:6                                                                          main
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 45:50                                                 <fn>
dart-sdk/lib/async/zone.dart 1661:54                                                                               runUnary
dart-sdk/lib/async/future_impl.dart 162:18                                                                         handleValue
dart-sdk/lib/async/future_impl.dart 846:44                                                                         handleValueCallback
dart-sdk/lib/async/future_impl.dart 875:13                                                                         _propagateToListeners
dart-sdk/lib/async/future_impl.dart 647:5                                                                          [_completeWithValue]
dart-sdk/lib/async/future_impl.dart 721:7                                                                          callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                                                                   _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                                                                    _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 181:7                                                 <fn>
Error: FirebaseError: Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('http://localhost:49592/firebase-cloud-messaging-push-scope') with script ('http://localhost:49592/firebase-messaging-sw.js'): The script has an unsupported MIME type ('text/html'). (messaging/failed-service-worker-registration).

dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 327:10  createErrorWithStack
dart-sdk/lib/_internal/js_dev_runtime/patch/core_patch.dart 337:28            _throw
dart-sdk/lib/core/errors.dart 120:5                                           throwWithStackTrace
dart-sdk/lib/async/zone.dart 1386:11                                          callback
dart-sdk/lib/async/schedule_microtask.dart 40:11                              _microtaskLoop
dart-sdk/lib/async/schedule_microtask.dart 49:5                               _startMicrotaskLoop
dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 181:7

The errors disappears with the execution of the command flutter pub add firebase_messaging, which updates the dependencies, but the app still hangs up at this point.

The same. After update to Flutter 3.16 FCM on web stopped working. I have the following error:
Uncaught (in promise) Error: AbortError: Failed to execute 'subscribe' on 'PushManager': Subscription failed - no active Service Worker

Notifications worked just before the update and still working on the production version of the app which is not updated.

The initial bug report by @nilsreichardt no longer appears. In terms of the other noted exception AbortError: Failed to execute 'subscribe' on 'PushManager': Subscription failed - no active Service Worker, this has also been resolved by having another attempt in this try/catch here. I'd also recommend updating to the latest firebase messaging web implementation here as per Flutter 3.21, see here


Update dependencies for 9.0 release

🛠 Summary of changes
Updates all dependencies to latest version, in preparation for upcoming 9.0.0 release.
Updates identified using npm-check-updates.
📜 Testing Plan
Build should pass.

The visual regression tests catch a very small difference in the appearance of the external link icon. I assume this may be due to rendering differences in the versions of Puppeteer Chromium between this branch and main.


Cannot init a project with PostgreSQL

Describe the bug
To Reproduce
Steps to reproduce the behavior:

Run command as the document.

label-studio start my_project --init -db postgresql

See error

Environment (please complete the following information):

OS: Ubuntu 22.04 LTS
Label Studio Version: 1.8.1
Expected behavior

Screenshots
$ label-studio start my_project --init -db postgresql
=> Hostname correctly is set to: http://<IP_ADDRESS>:8080
=> Database and media directory: /home/user/.local/share/label-studio
=> Static URL is set to: /static/
=> Hostname correctly is set to: http://<IP_ADDRESS>:8080
=> Database and media directory: /home/user/.local/share/label-studio
=> Static URL is set to: /static/
[Tracing] Create new propagation context: {'trace_id': '29a11d3f7ffe464a8115200c70a09270', 'span_id': '82123a390da160cf', 'parent_span_id': None, 'dynamic_sampling_context': None}
Starting new HTTPS connection (1): pypi.org:443
https://pypi.org:443 "GET /pypi/label-studio/json HTTP/1.1" 200 57379
Can't read version file: ls-version_.py. Fall back to: version_.py
[2023-08-10 01:44:10,320] [root::_read_py::61] [WARNING] Can't read version file: ls-version_.py. Fall back to: version_.py
[2023-08-10 01:44:10,549] [root::_read_py::61] [WARNING] Can't read version file: ls-version_.py. Fall back to: version_.py
Traceback (most recent call last):
  File "/home/user/anaconda3/envs/labelstudio/bin/label-studio", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/user/anaconda3/envs/labelstudio/lib/python3.11/site-packages/label_studio/server.py", line 343, in main
    _init(input_args, config)
  File "/home/user/anaconda3/envs/labelstudio/lib/python3.11/site-packages/label_studio/server.py", line 188, in _init
    user = _create_user(input_args, config)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/user/anaconda3/envs/labelstudio/lib/python3.11/site-packages/label_studio/server.py", line 148, in _create_user
    if input_args.quiet_mode:
       ^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Namespace' object has no attribute 'quiet_mode'
Sentry is attempting to send 2 pending events
Waiting up to 2 seconds
Press Ctrl-C to quit

oh hey, I just hit this.
After digging it looks like if you provide a default username and pass you avoid the line that's throwing
https://github.com/HumanSignal/label-studio/blob/develop/label_studio/server.py#L139
https://github.com/HumanSignal/label-studio/blob/develop/label_studio/server.py#L156

Thank you @ClaytonSmith , I will try it.

Thank you @ClaytonSmith  ,I succeeded.

Hi! My problem is that Azure doesn't allow to set an Environment Key called USERNAME due to it is a reserved key. Do you know any other way to skip the quiet_mode error?

@jaimeromoreno try to use LABEL_STUDIO_USERNAME, should it works

Hi! My problem is that Azure doesn't allow to set an Environment Key called USERNAME due to it is a reserved key. Do you know any other way to skip the quiet_mode error?

Found a workaround by instead providing the username and password in the startup command:
label-studio start --init -db postgresql --username defaultuser --password badpassword


[FEATURE] chat notification thingy

so when u do something that involves commands like binding something it shows
ClickGui bound to P
so what id like u to do is for every command make it do
[3arthh4ck] ClickGui bound to P

no

lol, yes


Build fail on MSVC latest and g++ 7.3

MSVC 16.0.0 fails with in a ICE something like,
1>test_ctre.cpp
1>common\compile-time-regular-expressions\include\ctre\wrapper.hpp(31): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
1>common\compile-time-regular-expressions\include\ctre\wrapper.hpp(70): note: see reference to class template instantiation 'ctre::RangeLikeType' being compiled
1>        with
1>        [
1>            Range=std::string &
1>        ]
1>test_ctre\test_ctre.cpp(12): note: see reference to function template instantiation 'auto ctre::regex_match_t<ctre::sequence<B,ctre::character<32>,A,ctre::character<33>>>::operator ()std::string&(std::string &) noexcept const' being compiled
1>        with
1>        [
1>            B=ctre::capture<1,ctre::plus<ctre::setctre::word_chars>>,
1>            A=ctre::capture<2,ctre::plus<ctre::setctre::word_chars>>
1>        ]
1>common\compile-time-regular-expressions\include\ctre\wrapper.hpp(31): fatal error C1001: An internal error has occurred in the compiler.
1>(compiler file 'd:\agent_work\3\s\src\vctools\Compiler\CxxFE\sl\p1\c\symbols.c', line 24466)
Code compiles with a CTRE version from around Feb 15. I've reported the ICE to Microsoft.
Also I tried g++ 7.3.0 on Ubuntu 18.04. Everything fails to build here too, but in a different way. This could be my finger trouble. Anyway 'make' in the ctre directory will do it, but I've tried a simple test file and get the same result.
paul@fasolt:~/compile-time-regular-expressions$ make
time g++ -std=c++17 -Iinclude -O3 -pedantic -Wall -Wextra  -MMD -c tests/range.cpp -o tests/range.o
In file included from include/ctre/../ctll/parser.hpp:4:0,
from include/ctre/../ctll.hpp:4,
from include/ctre/literals.hpp:4,
from include/ctre.hpp:4,
from tests/range.cpp:1:
include/ctre/../ctll/fixed_string.hpp:176:62: error: parameter ‘’ includes reference to array of unknown bound ‘const T []’
template  constexpr fixed_string(const T (&)[]) noexcept {
^~~~~~~~
Command exited with non-zero status 1
0.71user 0.07system 0:01.60elapsed 49%CPU (0avgtext+0avgdata 90368maxresident)k
35344inputs+8outputs (132major+19660minor)pagefaults 0swaps
Makefile:31: recipe for target 'tests/range.o' failed
make: *** [tests/range.o] Error 1
This is gcc 7.3.0.

GCC 7.2+ is working again (fixed in latest master)

Confirmed. Thanks!

MSVC problem was with SFINAE check and operator() in std::true_type / std::false_type, I found workaround in a2997436813c56d178111e94f49656d855f79532. Please confirm fix in MSVC.

Confirm MSVC fix, builds and runs as before. Thank you again.
I'll update the MSVC bug report since they will no longer be able to easily reproduce their ICE.

Please point them to the commit a2997436813c56d178111e94f49656d855f79532. Have a nice day!

Have done, tremendous service from you. Enjoy your weekend.


Unrelated error log

Description of the problem
Using the await in the non-async callback function causes the below error on the server log.
SyntaxError: Unexpected reserved word
    at ESMLoader.moduleStrategy (node:internal/modules/esm/translators:119:18)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14)
[05:51:47][Error] Failed to load resource bennys

Reproduction steps

Make a file like this in an example resource.

import * as alt from 'alt-server';

setTimeout(() => {
    await new Promise((res) => {
        setTimeout(() => {
            console.log('Hello!!!');
            res();
        }, 1000);
    });
}, 0);

Run the server.
Error log appeared in the console.

SyntaxError: Unexpected reserved word
    at ESMLoader.moduleStrategy (node:internal/modules/esm/translators:119:18)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14)
[05:51:47][Error] Failed to load resource bennys

Expected behaviour
alt:V's js-module should generate logs like Node.js official error.
This is the normal error on Node.js console.
await new Promise((res) => {
^^^^^
SyntaxError: await is only valid in async functions and the top level bodies of modules

Additional context
No response
Operating system
Windows 10
Version
dev/15.0-dev15
Scope
server
Reproduction tested

[X] I confirm that I have made sure that this issue is also present on the newest dev version

With the current way we handle it, it's not fixable and we won't rewrite the whole bootstrapper anymore.


Bagisto Version 1.5.1 - Catalog Rule Bug - If i create catalog rule it not affect on Product price due to product_price_indices table

Bagisto Version 1.5.1 - Catalog Rule Bug - If i create catalog rule it not affect on Product price due to product_price_indices table
When i create catalog rule its not working until i update product because when we create catalog rule its entry only updates in catalog rule ralated product but it not updating entry of product_price_indices table
Because of this product updated price as per cart rule is not working. Then i have to update the product then after that product update function updates product_price_indices table values as per active cart rule and then it works
So can you please update this, Just need to write the code for Update product_price_indices table after Create/Update catalog rule
To Reproduce
Steps to reproduce the behavior:

Create one catalog rule in bagisto version 1.5.1
Check in front end it will not affect product price
Then update any product that matched the criteria of that cart rule
Then again check the front end then it works
Again.... Update the cart rule and make it inactive
Check front end again, Even after inactive the cart rule it will show the cart rule discounted price
Now again go to admin and update that specific product and check front end only after it will update the latest price

Issue is clear....
Need to trigger one function which update the product_price_indices table after Create/Update cart rule
Expected behavior
After Updating cart rule it will direct affect front end to product price

Hello @miteshpanchaltechsevin,
We will fix this issue in the next release.
Meanwhile, you can add the below command in your cron job.
php artisan indexer:index --mode=full

Hi @miteshpanchaltechsevin
Hope your issue will be fix by adding the above command.
And if still you are getting the same issue then please let me know..

Above command doesn't work for me (V 2 beta)
In my opinion, This is not good idea storing prices in table. Think about updating million records in product_price_indices table!


Role Management

What to do?
Make a single controller which will accept necessary parameters and update roles and permissions accordingly to the database.
Behaviour
RBAC mutations should be decoupled from rest of the apis. In layman terms, updation to any role should require queries to the role and permission table and nothing else.

Prerequisite
Entities for roles and permission.


Passing config variables

As I'm trying to create something that dynamically changes the scanning area, I'm wondering if it's possible to pass the config-vars as parameters in the command line?
Something like:
python worker.py --map-start="(12.3456, 14.5)" --map-end="(13.4567, 15.321)"

"dynamically changes the scanning area"
I think this will work against the goals of the pokeminer-project? Could you explain why you want this?

@Aiyubi In my app, I want to change the scanning area when I'm arriving at work. So the easiest way for me is to start the worker.py script with different parameters.

Combining this with #183 gives me an idea for allowing to overwrite config values from command line. I think I'll take care of it in my spare time.


Panic is a valid state of being, Goots Panik would be useful to express that

Even through the late Kobe Bryant said

If I panic, everyone else panics.

this is not a thought he could express via the medium of goots. I imagine that a Goots Panik emoji might take inspiration from the image below and provide peace for those with panic on their minds.

closed with https://github.com/christrotter/gootsmoji/pull/59


Update package properties tools to use one argument

Based on feedback, extending Get-AllPkgProperties such that passing the PackageName argument filters the result down to one package. Also starting the process of converting the argument for Get-PkgProperties from PackageName to ArtifactName which is more accurate

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

Closing the PR in favor of https://github.com/Azure/azure-sdk-tools/pull/1403


Mqtt thread

Remove shared cicrular buffer;
Moved MQTT publish subscribe in parallel thread;
Add mutex on logging to avoid spikes;


Tracking Tests

[ ] Add minimal (two color) test data set for tracking
[ ] Add a headless test function

Fulfilled with Commit 848f556c297c3de43bbd375b8f8bbbd8e8edc0c3


Implements the OkHttp extension

Hi,
I'm try to play shoutcast AAC stream, but works only in android API  20+.
I search this bug in ExoPlayer repositorie and I find this issue: https://github.com/google/ExoPlayer/issues/1157#issuecomment-173125170 and I got success when I build Java APP with this new OkHttpDataSource(client, "ExoPlayer", null, null) ´part of OkHttp extension...
I try binding ths class and re code in C# but I fail...
Can you implement this? Or say what I do?
Thanks so much!

Done in https://github.com/martijn00/ExoPlayerXamarin/commit/441eab0cd308906200fa7796872c43c435199fe2


upgrade to nom 2.0

Hi!
as a part of the release process for nom 2.0, I selected a few crates to test it with, and make sure everything works correctly.
I'm happy to tell you that this crate built fine with nom 2.0 out of the box, no need to change anything!
If you want more information on this release, see the blogpost: https://unhandledexpression.com/2016/11/25/this-year-in-nom-2-0-is-here/ (reddit discussion: https://www.reddit.com/r/rust/comments/5espfm/this_year_in_nom_20_is_here/ )
There are a few new features that could be of interest for this project :)

Excellent!  Thanks Geal.


Use Pipenv

The Makefile trickery to construct virtual environments and lock requirements is novel, but there is A Better Way

Zappa complicates pipenv somewhat because it wants to deploy from inside a virtualenv (somehow pipenv run zappa update x ins't sufficient).
Also, deploying a zappa application is sortof problematic anyhow because it slurps up everything in the current venv and working directory. I don't really want ansible or the tests included in the slug that goes to AWS, but maybe that's worrying about hypothetical performance for no real gain.

Pynacl on termux seems to be at the root of much of this struggle: https://wiki.termux.com/wiki/Instructions_for_installing_python_packages

no longer relevant, no more termux


storage: Recover from corrupted indices for archived series

An unopenable archived_fingerprint_to_timerange is simply deleted and
will be rebuilt during crash recovery (wich can then take quite some time).
An unopenable archived_fingerprint_to_metric is not deleted but
instructions to the user are logged. A deletion has to be done by the
user explicitly as it means losing all archived series (and a repair
with a 3rd party tool might still be possible).
Fixes #2210.
@stuartnelson3 @brian-brazil @juliusv whoever…

:+1:


Hub failing to launch

I am having this error getting the hub to run. Any ideas how to solve it?

I just built the current master branch as v0.1-alpha3. So now the releases and the documentation should match up again.
This version should not show this problem when running production mode, but it now appears in dev mode – so this still needs fixing. But I hope this helps you in the mean time!?
Background about the error. Best fix seems to be to use cross-env.

I just pushed 35a3714. Can someone verify the issue is gone for good?

Confirmation
Hub works fine for me.
Tested v0.1-alpha3 and v0.1-alpha4 on Windows10 64bit

This still does not seem to work without running npm install before.

submitted a different fix


Font size in settings

Could you please implement changing the font size in the settings

This feature would be very helpful!


Feature: indicate JST timezone for when the page was last updated

👏 解決する issue / Resolved Issues

close #1207

📝 関連する issue / Related Issues

#1207

⛏ 変更内容 / Details of Changes

The "last updated" date of the page header is taken from the lastUpdate value in the data/data.json file. The time zone of the lastUpdate value in the data/data.json file is Japan Standard time and is periodically updated by the data loader managed by the Tokyo Metropolitan Government (see https://github.com/tokyo-metropolitan-gov/covid19/issues/1207#issuecomment-664172525).
Research & Explanation 🕵
In the components directory, lastUpdate is cited twice:
$> grep -rn "lastUpdate" components
components/SiteTopUpper.vue:62:      return convertDatetimeToISO8601Format(this.$data.Data.lastUpdate)
components/SiteTopUpper.vue:65:      return `${this.$d(new Date(Data.lastUpdate), 'dateTime')} JST`

The first instance of lastUpdate is passed to the convertDatetimeToISO8601Format utility function returning a formatted date and time. The Day.js Format documentation offers a variety of options, including a way to escape characters using square brackets ([]). Because JST is also known as UTC+9, the inclusion of[+09:00] indicates the appropriate timezone for lastUpdate:
export const convertDatetimeToISO8601Format = (dateString: string): string => {
  return dayjs(dateString).format('YYYY-MM-DDTHH:mm:ss[+09:00]')
}

I checked MDN documentation for the <time> element and the w3.org time element documentation and verified this format is one of the acceptable valid global date and time strings. 👍
The second instance of lastUpdate is cited within a string literal. This change specifies JST as a more approachable indicator of time than UTC+9:
    formattedDateForDisplay() {
      return `${this.$d(new Date(Data.lastUpdate), 'dateTime')} JST`
    }

It's also worth noting that lastUpdate is also found in the layouts directory:
$> grep -rn "lastUpdate" layouts
layouts/default.vue:135:            date: convertDateToSimpleFormat(Data.lastUpdate)
layouts/default.vue:164:            date: convertDateToSimpleFormat(Data.lastUpdate)

However, this function wasn't updated because it only specifies date, not date and time:
https://github.com/tokyo-metropolitan-gov/covid19/blob/f0905dc60b676208b26626acc4b956a963e09d10/utils/formatDate.ts#L39-L46
For context, this was included as a part of https://github.com/tokyo-metropolitan-gov/covid19/pull/2780 to include the last update in the meta description (motivated by https://github.com/tokyo-metropolitan-gov/covid19/issues/2587).
📸 スクリーンショット / Screenshots

I realize that my branch name doesn't follow the convention 😳  I'll reopen this shortly :v:


how to use addWidget ?

how to get an instance
cm.addWidget(pos: {line, ch}, node: Element, scrollIntoView: boolean)
Puts node, which should be an absolutely positioned DOM node, into the editor, positioned right below the given {line, ch} position. When scrollIntoView is true, the editor will ensure that the entire node is visible (if possible). To remove the widget again, simply use DOM methods (move it somewhere else, or call removeChild on its parent).

Do you read the documentation carefully?

In addition, it can be obtained by ref.

OK, thanks


[DoNotMerge] Feature/cplat 2021 07 01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. June 2021
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. June 2021
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[x] SDK of Java
[x] SDK of Js
[x] SDK of Go
[x] PowerShell
[x] CLI
[x] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Not sure why following was checked?
What's the purpose of the update?
new service onboarding
new API version
This is neither new service nor new API version. This does not require ARM review, removing the tag.

Closing the PR as the changes will be going into version 2021-04-01. Synced with Theodore Chang<EMAIL_ADDRESS>


Allow to use local workers when there is no settings.yaml

When working locally, we need to substitute the workers by LocalWorker so we can trigger builds as desired locally and also deactivate auth (so we don't need to log into the local instance using GitHub).

Will update the PR soon :)
Thanks for the review @zware !


update android/build.gradle

Fix error during the build the projects.
Execution failed for task ':react-native-spinkit:verifyReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aa

It would help a lot if we can merge this soon

Actually, can we change this PR to use
def safeExtGet(prop, fallback) {
    rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
}

android {
    compileSdkVersion safeExtGet('compileSdkVersion', 26)
    buildToolsVersion safeExtGet('buildToolsVersion', '27.0.3')
     defaultConfig {
        minSdkVersion safeExtGet('buildToolsVersion', '23')
        targetSdkVersion safeExtGet('buildToolsVersion', '26)
        versionCode 1
        versionName "1.0"
    }

last commit was over a year ago :) I think your best bet it to use/fork zeayal:master's branch


FileStreamReader member initializer list does not match actual initialization order

On Linux, there is a warning with g++ and clang for the member initializer list in FileStreamReader constructor:
g++ -MT build/obj/Streams/MemoryStreamWriter.o -MMD -MP -MF build/deps/Streams/MemoryStreamWriter.Td -std=c++14 -g -Wall -Wno-unknown-pragmas  -c -o build/obj/Streams/MemoryStreamWriter.o Streams/MemoryStreamWriter.cpp
In file included from Streams/FileStreamReader.cpp:1:0:
Streams/FileStreamReader.h: In constructor ‘FileStreamReader::FileStreamReader(std::__cxx11::string)’:
Streams/FileStreamReader.h:29:20: warning: ‘FileStreamReader::filename’ will be initialized after [-Wreorder]
  const std::string filename;
                    ^
Streams/FileStreamReader.h:28:16: warning:   ‘std::ifstream FileStreamReader::file’ [-Wreorder]
  std::ifstream file;
                ^
Streams/FileStreamReader.cpp:5:1: warning:   when initialized here [-Wreorder]
 FileStreamReader::FileStreamReader(std::string filename) :
 ^

One fix is to swap the declaration order of the fields:
private:
	const std::string filename;
	std::ifstream file;

The other alternative is to swap the order in the member initializer list:
	//filename(filename), file(filename, std::ios::in | std::ios::binary)
	file(filename, std::ios::in | std::ios::binary), filename(filename)

Either way, the declaration order should then match the listed initialization order. Or in other words, the listed initialization order will then match the actual initialization order.
Any preference?

I hadn't thought about class member variable destruction order until it was brought up in an earlier thread, which is probably why this is written how it is.
It would make more sense to me to construct the filename first, then construct the std::ifstream. Then for destruction, destroy the std::ifstream first, then the filename. (I recognize that in practice the ifstream doesn't actually depend on the class level filename, but this seems more logical to me?)

A few other details that can be added to the issue as they touch similar parts of the code. I'd like to match FileStreamReader and FileStreamWriter closer with variable names and initialization list.

Construct the FileStreamWriter's ifstream in the member initialization list (mirroring FileStreamReader)
Switch the order of FileStreamWriter's class level variables filename and ifstream to match FileStreamReader as mention above.
Match the name of the class level ifstream to match in both FileStreamReader and FileStreamWriter. I think using the name fileStream makes more sense to me, but I don't mind it being file or something else either.

Ok, I think I have the same inclination here too. I'll put together a patch. I'll re-order the member variable declarations to match the intializer list. I'll also look into renaming member variables to match across classes in the stream library.


Add support for sidecars to migrate and minder, add tests for same

Since many people probably care about their helm versions, I didn't make it part of the bootstrap command, and instead rely on helm already being installed for this test.
I started with trying to use https://github.com/mittwald/go-helm-client/, but it turns out that has a bunch of out-of-date dependencies, and all the APIs changed because that's how k8s API dependencies work.

Note that this replaces https://github.com/stacklok/minder/pull/1599 and allows us to start retiring the aws cloud provider in favor of a sidecar for both GCP (sql proxy sidecar) and AWS (AWS using the pattern in https://github.com/prometheus-community/postgres_exporter/issues/498#issuecomment-833579014)


HL-499: Replace handlers initials with full name in header

Description :sparkles:
-Initials removed
-one column added with full name of the handler to the application header
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #998 (efd26ce) into develop (348ce45) will decrease coverage by 39.23%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##           develop     #998       +/-   ##
============================================
- Coverage    63.63%   24.39%   -39.24%
============================================
  Files          865      190      -675
  Lines        23994     4603    -19391
  Branches      2369     1147     -1222
============================================
- Hits         15269     1123    -14146
+ Misses        8331     3368     -4963
+ Partials       394      112      -282

Impacted Files
Coverage Δ

...components/applicationHeader/ApplicationHeader.tsx
0.00% <0.00%> (ø)

backend/benefit/applications/enums.py

backend/benefit/terms/models.py

...er/src/hooks/employments/useGetEmploymentErrors.ts

...rc/utils/get-activation-link-expiration-seconds.ts

...kend/shared/shared/oidc/tests/test_auth_backend.py

backend/shared/shared/common/decorators.py

...tend/shared/src/components/benefit/tabs/Tabs.sc.ts

...ntend/shared/src/constants/attachment-constants.ts

...shared/src/components/forms/inputs/DateInput.sc.ts

... and 666 more

Continue to review full report at Codecov.

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


Render format labels on /projects

What is it and who's it for?
All site visitors
We have the option in Prismic to set a Format on /projects. However, this label isn't rendering.
The format labels should render on all content types where we offer a format option in the model.
Here's an example page https://wellcomecollection.org/pages/YCEq1RIAACMAXBLL
Implementation
Acceptance criteria

Format labels display on cards and content pages

I think this possibly needs @GarethOrmerod and/or @DominiqueMarshall to suggest label placement

@davidpmccormick For consistency purposes, it looks like the label would be best in the same place as the others (so underneath the heading)

@davidpmccormick It doesn't look like the labels are rendering on the cards - is this a separate piece of work? I noted it in the Acceptance Criteria above but can see that it'd be easy to overlook.

Ah, I missed that. I'll reopen this.


Added EMAIL_SUBJECT_PREFIX to settings.py

Set EMAIL_SUBJECT_PREFIX to 'Student Explorer'
Possible issue
Ideally this should be specified in the .env file but I did not want to make any change to that without authorization
Secondly, I will be working on moving to django-constance after this
Thirdly, I do not know how to test this change as I don't think I can send emails

Thanks, sorry for the delay on the review.
If you don't get Django constance implemented that's fine too, not sure how much effort you needed to put into this. I gave some feedback.
It looks like you commented a little about the testing of this on the issue, I'll comment there.

Just made those changes

Accepted @jonespm suggestion


Update gcp-workload-identity.md

fixing the service account used in the iam policy binding

I believe that the change should be made at https://github.com/CrowdStrike/falcon-operator/blob/main/apis/falcon/v1alpha1/falconcontainer_types.go#LL48C33-L48C40 to be crowdstrike-falcon-sa vs the documentation change. With the permissions we apply to the service accounts, it is better not to use default.

Actually falcon-operator is using the default service account AND in our official document (on falcon console) it's also default used.
and based on existing deployment it could be a breaking change for those who are using OIDC or Workload Identity

I've made the change last december to match crowdstrike-falcon-sa here : https://github.com/CrowdStrike/falcon-operator/pull/317 but unfortunately it's creating more issues because falcon-operator is using default and our internal doc is stating default as well (which is correct because operator is using default while helm is using crowdstrike-falcon-sa)

I think @redhatrises is right -- the only case in which I can see it would matter, is the event in which a customer users the operator to deploy both the node and container sensors on the same cluster -- but in that case, it would provide the node sensor with permissions to read from GCR, which is unnecessary and thus should likely be changed (back) to a dedicated SA.  Thanks for the catch Gabe.
I'll discuss with a couple people internally to see if they have opinions on how to handle the break.

Closing this PR as setting the default serviceAccount is no longer allowed. Thanks for opening!


The map widget is overlapping other widgets

Steps to Reproduce
Navigate to other page route.
Minimize the app and open it again.
The map will be above everything.

a code sample could help to understand the problem


Visualized Schema View

Schema being rendered/modified in Graph View

可视化读、写 schema

https://discuss.nebula-graph.com.cn/t/topic/6826?u=wey

3.5.0 已初步支持


Add content right above map about what you're seeing

In paragraph tags right by the map header:
Shortages: "Percentage of reports citing shortage of any kind"
Testing: "Percentage of reports indicating 'not tested'"

See Janet's mockup powerpoint (slack)


Failed to attach depth buffer to target.

Jonathan,
The new depth functions work well when I run my code on a Mac ( I think it's using OpenGL 3 implementation ). However, when I'm running the same code on Raspberry Pi ( GLES 2.0 ), I get "Failed to attach depth buffer to target." error from GPU_AddDepthBuffer. Looks like attaching depth buffers to targets is not supported on RPi's VC4 chip.
Do you know of any workarounds I could employ, in my quest of drawing sprites in order of their z-coordinate? Other types of buffers, or anything? I'm using my own shaders to draw sprites.
Also, I found that if I even call GPU_AddDepthBuffer on RPi ( and it returns false ), nothing can be drawn afterwards, as if the target is left in some invalid state.
Thanks!

Actually, I saw something online that may fix this:
https://stackoverflow.com/questions/44343363/opengl-es-2-0-gl-depth-component-and-glteximage2d
Suggests to use GL_DEPTH_COMPONENT16 in place of GL_DEPTH_COMPONENT on GLES2.0
I've modified your source locally in renderer_GL_common.inl:
Modified line 1985 to:
glRenderbufferStorage(GL_RENDERBUFFER, GL_DEPTH_COMPONENT16, target->base_w, target->base_h);
and now it lets me attach depth buffer and depth test/z coord works correctly on Raspberry Pi!
I'm not sure how this affects other platforms.

I think that’s probably right and it’s a common error to use GL_DEPTH_COMPONENT.  I’ll commit that fix tomorrow!

This should be resolved in 5dfac56e3573156e128e3bee69c98b97831d8e7a.


Updated Slack Connector for new Events API

Proposed changes:

Updated Slack Connector for new Events API format documented here

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Just wondering if there are any updates on this PR.

@jkuan1 The issue has been addressed in the latest Rasa 2.0 release by this PR


test

test

In the future, please perform tests like this on a repository under your own namespace or organization. :wink: :heart:

Sorry about that!
On Wed, Oct 2, 2019 at 4:33 PM Tianon Gravi<EMAIL_ADDRESS>wrote:

In the future, please perform tests like this on a repository under your
own namespace or organization. 😉 ❤
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/docker-library/postgres/issues/612?email_source=notifications&email_token=ABZPN7IF4NZ6WQ7HQDI6RODQMUHRRA5CNFSM4I43WTL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAGIETI#issuecomment-537690701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZPN7JD7RG7STYDOSY2RATQMUHRRANCNFSM4I43WTLQ
.


Improv: Source all .secret files from mrsauravsahu profile and mark them in .gitignore

closed by #21


Remove chalk after use

In my application log statements are printed to the console and written to a log file.
When the logs are printed to the console, I want them to be colorful (using chalk) but this has the side effect that statements in the log file are enclosed by special characters:
This text is green and this text is not green.

Is there a good way of getting rid of the color placeholders (like  & )?

Ok, I found the solution. 😁
To keep track of it:
const ansiRegex = require('ansi-regex');
const text = 'This text is green and this text is not green.\n';
const withoutChalk = text.replace(ansiRegex(), '');
console.log('withoutChalk', withoutChalk);

Yes, don't use chalk when logging to files.

We have a module for this exact purpose: https://github.com/chalk/strip-ansi

We have a module for this exact purpose: https://github.com/chalk/strip-ansi

Even better!
But what do you think about making it a feature of chalk itself? I can think of something like a on and off method. Or even clean because sooner or later a "chalk" board needs to be cleaned. 😁


Minor edits to the README.md

These are some very minor edits.  s/product/produce/ and also capitalizing a few proper nouns.

Awesome editor eyes! Thanks!


test(e2e): add expected startupTaints for e2e testing

Fixes #
Description
How was this change tested?

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

We should also launch 10 tests without taints and see waht fails, here we only see one failure case for utilization, and its due to underprovisioning


Add source file jar to distributed artifact

Add source file jar to distributed artifact to see and jump to the source code in IDE.

Good


Litemol wip do not merge

For reference:
Coloring will be done with a list of position ranges and associated colors in HEX form, e.g.,
[
    {start: 0, end: 10, color: #ff0000},
    {start: 100, end: 100, color: #00ff00}.
    ...
]

The coloring function should take in this list of objects and apply the transforms respectively. Order shouldn't matter
There's going to be three chains for the Spike protein (A, B, and C), so apply these colorings to each chain


Dynamic Composable Kernel Initial Integration

PR description
Add new dynamic composable kernel under:
src/composable_kernel/, which is pulled in as a "git subtree" from composable kernel repo
remote repo: https://github.com/ROCmSoftwarePlatform/composable_kernel
remote branch: miopen_upstream
Move old static composable kernel to:
src/kernels/static_composable_kernel/
Add a new iGEMM solver for Forward NCHW FP32/FP16/Int8 (int8 is not supported by ConvolutionContext so the solver support for Int8 cannot be used yet):
src/solver/conv_ck_igemm_fwd_v6r1_dlops_nchw.cpp::ConvCkIgemmFwdV6r1DlopsNchw , which is calls into composable kernel solver:
src/composable_kernel/host/driver_online/include/conv_igemm_fwd_v6r1_dlops_nchw_kcyx_nkhw.hpp::ConvIgemmFwdV6r1DlopsNchwKcyxNkhw
Sync between composable_kernel and MIOpen with "git subtree"

Relation between MIOpen solver class ConvCkIgemmFwdV6r1DlopsNchw and composable_kernel class ConvIgemmFwdV6r1DlopsNchwKcyxNkhw

Previous review comment
[@atamazov] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-887904351

Add new dynamic composable kernel under: src/composable_kernel/, which is pulled in as a "git subtree" from composable kernel repo

I am sorry but I do not remember the motivation for subtree... Where can I refresh my memory (mail thread or ticket in the repo...)?

[@asroy] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-888344195

The motivation is to be able to sync composable kernel repo and MIOpen automatically.

We had the meeting in 07/06 "MIOpen and composable kernel", between you, @JehandadKhan @pfultz2, me and @zjing14. Subtree approach was suggested there

[@atamazov] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-890181927

Previous comment
[@atamazov] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-887902333

src/composable_kernel/host/online_compilation/addkernels/*

Does it differ from addkernels that we already have in the tree?

[@asroy] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-888342409

It's used when building composable kernel alone (and outside MIOpen). It is not used in MIOpen.

The whole composable kernel is pulled in as subtree

[@atamazov] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-890170955

[Notice]
This does not answer my question. Let me assume that this addkernels is a copy of the one that resides in MIOpen.

If the efforts to make the composable kernels independent has resulted in the addition of another implicit dependency (a copy of addkernels), then I'm afraid that something is wrong.

But well, I signed off from reviewing this, so let's actual reviewers decide.

[@asroy] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-890191005

I don't have a good way to avoid this issue (some composable kernel host codes are not used in MIOpen) if using subtree feature. I actually brought up this issue during our 07/06 meeting as a side effect of using subtree (or submodules).

The only way I can think of it's to make composable_kernel as a separately compiled library and provide a API that return a string of kernel source code to MIOpen. This was an alternative brought up by @JehandadKhan. But the in the meeting, it was decided subtree is the way to go.

I'm fine with either approach, my goal is keep composable_kernel maintainable, by keeping kernel source codes in one place instead of manually copying source files between two repos.

If we can reach a consensus on the best approach to achieve this goal, and if time permit, I can change accordingly
cc @atamazov @pfultz2 @JehandadKhan @junliume @aserio

Previous comment
[@atamazov] https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1059#issuecomment-887905136

@asroy Have you looked at DeepCode's analysis?

I've removed online compilation code from this PR.

Also line 580 of src/reducetensor.cpp should be changed to use the "static_kernel_xxx"  kernel file name.

Also line 580 of src/reducetensor.cpp should be changed to use the "static_kernel_xxx" kernel file name.

Thanks. Fixed

CI has passed. This PR is ready to be reviewed

CI has passed. This PR is ready to be reviewed

Ping @pfultz2 @zjing14 @JehandadKhan @qianfengz for review :)

@junliume @JehandadKhan CI just passed

@junliume @JehandadKhan CI just passed

@asroy would you need to make more code changes? e.g. comments from https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1071#discussion_r691221750
If not, any objections that we merge it tonight? (2000 CDT, 1800 PDT)

@junliume No more change is needed for this PR.


[Storage] az storage blob upload(-batch)/set-tier/copy start(-batch): Cold Tier GA

Related command

Description

Cold Tier GA
Bump storage blob version to 2022-11-02
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage


Better io

move some io functionality from core here to reduce duplicate code and make spec slightly more useful.
Biggest change is that load_raw_resource_description now behaves like it does in core, i.e. returns urls for fields containing local relative files if the source is a url (otherwise relative paths are returned, which are relative to root_path)

Can you add a platform condition so we don't install that for pyodide? The thing is that pyodide download every time all the new libraries, so it's better to keep very few dependencies.
@constantinpape you can find examples in the setup.py if we are already using it.

as tqdm is only used in conjunction with requests when downloading and I don't see it listed in https://github.com/pyodide/pyodide/tree/main/packages I added it as dep for native python only.


Callendar section

Gatsby Build successful.
Works on all browsers.
Not sure if the animation for the Menu links is what you wanted but that's an easy fix if we need to change it.

I think the checks have failed because we need to add the google Api key.


Consumer Groups and Reblancing

He, i'm just getting my head into Kafka.
Looking through the code client code I cannot see anything that interacts with Zoo Keeper. (I think) The design document says consumers should use Zoo Keeper to coordinate access to partitions and balance load.
Are these features supported ?

Yep, pykafka doesnt implement any of the zookeeper-based offset persistence that the official Scala client does. We at Datadog are working on a full zookeeper-based python client called brod. Check it out:
https://github.com/DataDog/brod

Cool, thanks.


see #143

see #143

Codecov Report

Merging #144 into master will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #144      +/-   ##
=========================================
+ Coverage   94.13%   94.2%   +0.07%
=========================================
  Files          32      32
  Lines        1398    1398
=========================================
+ Hits         1316    1317       +1
+ Misses         52      51       -1
  Partials       30      30

Impacted Files
Coverage Δ

bench/task.go
87.8% <0%> (+1.21%)
:arrow_up:

Continue to review full report at Codecov.

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


Implement 'Test-SbMessageBatchSize'

@Splaxi had the idea for this cmdlet in #13.  The purpose is to verify whether a given message or batch of messages will not exceed the message size limit for the in-scope namespace.

There are several things to consider here.
I would argue that a complete overview, that displays true/false for each tier/sku and less than 100 messages, would be very helpful. No need to parse a connection string or query the namespace for a generic response.
But if we pass or have a stored connection string in memory, it should an additional property ValidForNamespace true/false.

Yeah, a richer output would definitely be useful.  How about something like this...?

I would think that the base output should be:
BatchSize: xxx MB
NumberOfMessages: yy
ValidForBasicSku: {result: true/false; reason: too big / too many msgs}
ValidForStandardSku: {result: true/false; reason: too big / too many msgs}
ValidForPremiumSku: {result: true/false; reason: too big / too many msgs}

And if the Namespace is in play, we should add the
CurrentNamespaceSku: {Free, Standard, Premium}
ValidForCurrentNamespace: {result: true/false; reason: too big / too many msgs}

What ever reason we might find, should be posted as a warning message.
I'll dig around my search history, to see if I can find back to the reference of the 100 messages.

Cool, agreed on those points.  Let me know if you find details of that limit because I can't find documentation related to it - the only limit I've seen is on the total size of the batch.  If that's the case then we can probably do away with the reason property in that base output.

That is a deal!

This is were I read about the 100.
https://github.com/MassTransit/MassTransit/issues/1409

Good find.  Let's add that constraint in then.

My testing shows that there ISN'T a hard limit on the number of messages allowed in a single batch. It is only size that counts.


Added support for description, estimate, milestone_id, and owner_ids

I added support for a few more fields, made them optional, and documented them.

Thank you, @ericraymond


Is there a way to batch read values from the RMap using key pattern?

I'm looking through the documentation and it doesn't seem currently possible to batch multiple values(pattern) calls.
If this functionality doesn't exist will it be possible to add it in the future versions?

I'm afraid it's impossible since it's a scan command which can return even empty result for the first call for non empty data. So requires multiple calls.


01-AzureOpenAIAPI: required package & API_KEY fix

For the labs in the '02_integrating-ai' section various package are required. Added those as the 1st step of the labs.
The API_KEY variable refers to the wrong .env entry ("OPENAI_API_KEY") -> should be AZURE_OPENAI_API_KEY

Not sure if we want to change that. In Langchain the env var is expected to be named OPENAI_API_KEY.
@MarkWme your thoughts?

ok fix that to
openai_api_type = os.getenv("OPENAI_TYPE")
openai_api_version = os.getenv("OPENAI_VERSION")
openai_api_base = os.getenv("OPENAI_API_BASE")
openai_api_key = os.getenv("OPENAI_API_KEY")
COMPLETION_DEPLOYMENT = os.getenv("AZURE_OPENAI_DEPLOYMENT_NAME")


expand node data received and device data received events to include group id, node id and device id detail

I found during testing when I had multiple devices with the same metric, I never knew which device's metric had changed when the event fired. I've added the extra details to each application event.

Looks very good, I will try to put in into the next release :)

@all-contributors please add @cjmurph for code test


launcher: workaround zig cc -Wl,--version

A hack for https://github.com/ziglang/zig/issues/15549

Fixed upstream in https://github.com/ziglang/zig/issues/15549


Prevent deletion of tcp-lite connector and listener pseudo connections

The tcp-lite adaptor creates pseudo core connections corresponding to tcpConnector and tcpListener instances. Management should not be allowed to disable/delete these connections directly. The connection's lifecycle corresponds to its owning tcpConnector/tcpListener and will be deleted when those objects are deleted.
Similar issue to https://github.com/skupperproject/skupper-router/issues/1225 seen in the legacy tcp adaptor.

The fix for this needs to have the TCP adaptor management CI tests enabled for tcp-lite. These test exercise the related failure case.


config.txt - "File not found"

xxx:~/EvilPortal/EvilPortalGenerator/EvilPortalGeneratorEN/source$ sudo sh generate.sh  : No such file: cannot open ../config.txt : not found: 4:  generate.sh: 5: Bad substitution

Changed shebang  to "/usr/bin/bash"
Rewrote EOL with nano
Changed path ./../config.txt <-> ../config.txt
sudo -s and regular user

Always the same result!
Found by cat etc.
Ubuntu 23/Plasma
Konsole/Yakuake

Had the same issue, looks like the new line is in windows format.
Run dos2unix against the script and it will fix it: $ dos2unix generate.sh


[GHSA-9vvw-cc9w-f27h] debug Inefficient Regular Expression Complexity vulnerability

Updates

Affected products

Comments
https://github.com/debug-js/debug/issues/924
https://github.com/expressjs/express/issues/5088

Closed as duplicate of #1599.


Unify headings

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 Guide: Unify sidebar headings


Note Class

[ ] Test Suite
[ ] Class

interface NoteObject {
  id: string
  title: string
  text: string
}

declare class Note {
  _id: string
  _title: string
  _text: string
  _created: Date
  _updated: Date
  get id(): string
  get created(): Date
  get updated(): Date
  get toObject():  NoteObject
  get toString(): string

  title(): string
  title(text: string): this
  title(text?: string): (string | this)

  text(): string
  text(text: string): this
  text(text?: string): (string | this)

  static toNote(noteObject: NoteObject): Note
}

Change in the design.  Had decided not to include the created and updated times in the interface, however when added that interface to the toNote static method it will break because the created and updated times are not introduced.
interface NoteCollectionObject extends Array<NoteObject> {}

declare class Note {
  _id: string
  _title: string
  _text: string
  _created: Date
  _updated: Date
  get id(): string
  get created(): Date
  get updated(): Date
  get toObject():  NoteObject
  toString(): string

  title(): string
  title(text: string): this
  title(text?: string): (string | this)

  text(): string
  text(text: string): this
  text(text?: string): (string | this)

  static toNote(noteObject: NoteObject): Note
}```


Use ssh_url rather than clone_url

Didn't spot this in #8, sorry!
clone_url seems to always return the HTTP URL so asks for authentication
for private repos.

Thanks again :) Both are released as 0.6.0

Amazing, thanks :+1:


fix(email-nodemailer): Fix skipVerify behaviour being reversed

Description
Fixes #6789
The skipVerify field in NodemailerAdapterArgs worked in reverse of what it was supposed to do:

With skipVerify = true -> Verified transport
With skipVerify = false -> Did not verify transport

This PR makes the property work in the intended way:

With skipVerify = true -> DO NOT verify transport

With skipVerify = false -> DO verify transport

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

@denolfe Whoops, I missed that indeed. Made changes as requested.
I also added a few tests that validate the flag's behaviour.

Thanks for the PR @JasperBeaurain ! Love that you added tests 🙏


Sumatra should not delete an empty data directory unless explicitly told to do so.

This happens in the __del__() method: http://neuralensemble.org/trac/sumatra/browser/src/datastore.py?rev=203%3A64113941b6f2#L75
Imported from Bitbucket issue 61,  created by apdavison on 03-28-2011 at 14:42, last modified: 06-23-2011 at 12:09

Deleted __del__() in r254.
Trac comment by apdavison on 06-23-2011 at 12:09


build: limit cargo-zigbuild version due to bug in newly released version

Proposed changes

The new cargo-zigbuild version (0.17.2) fails to build on aarch64. Fixing the version to 0.17.1 until the bug is solved (https://github.com/rust-cross/cargo-zigbuild/issues/179)
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Merged without approval to minimize number of build errors


fixes for pafs with multiple shared references

paf fixes needed for multiple pafs with shared references
addmin=1for paf reference repeat inputs

@bgruening - need these patches on your rebased tools-iuc fork - what's the easiest way?
Working on my own fork so cannot figure out how to make a PR for yours safely?

Single commit would be the easiest way for me.

@bgruening Need this to fix treevalgal workflows on EU for now - the pafs are broken at present :(
Might be more to come. Tell me what to do?

I will deal with it

🐰🐣🐰 happy Easter

@bgruening - thanks. Will test tomorrow. There will be plenty more to merge I'm sure.


fix(functional): correct the typo: witdth to width

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.P2oileen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

请尝试 rebase 最新的 master 分支再跑 CI 看看


initialize (avoid free of uninitialized pointer at exit_cleanup)

I notice that the code uses both NULL and cupdlp_NULL. What is the distinction?

These changes are merged as part of https://github.com/COPT-Public/cuPDLP-C/pull/34


Fixing style issues

Can remove this to use the image tag width and height otherwise it's not necessary
img {
width: 45px;
height: 45px;
}

Can add this as well .search { input[type="text"], input[type="search"] {}} otherwise +1


type password has no asterisks to hide the password

Hi, thanks a lot for the type password added to your vue-search-input. I am probably not seeing it, but how do I hide the input data behind asterisks. I couldn't figure it. Can you point me in the right direction? Same kind of a prop I am not aware of?

Hey @coudys thanks for reporting this issue, it's now fixed with a5d52569dc9d7e5d91464feb7d0d12984979a965


refactor: traceable magic comments warnings

Summary
Make warnings of magic comments traceable
Test Plan

Add packages/rspack/tests/diagnostics/module-parse-failed/magic_comment_warning

Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

Current dependencies on/for this PR:

main

PR #5341   👈

PR #5342

This stack of pull requests is managed by Graphite.


Typo at Chapter 9 notebook

with tf.Session() as sess:
    y_val, z_val = sess.run([y, z])
    print(y)  # 10
    print(z)  # 15

In this code block, based on the book print(y) and print(z) part should be print(y_val) and print(z_val)
Book page:235

Good catch, thanks.  Just pushed a fix.


Daedalus starts a cardano-node process which listens on all network interfaces (<IP_ADDRESS>)

When I start Daedalus, its cardano-node process publishes a network service on <IP_ADDRESS>:<some high order port number>. This introduces a vector for network attacks that is unnecessary.
> netstat -plant | grep cardano-node
tcp        0      0 <IP_ADDRESS>:45681           <IP_ADDRESS>:*               LISTEN      762865/cardano-node
...
tcp6       0      0 :::45681                :::*                    LISTEN      762865/cardano-node

I suggest that cardano-node publishes on loopback addresses only.
Jira issue
ADP-899

Fair point, it should be safe; in any case thanks for your consideration.


Omnibus: SPI DMA + use new ICM-20602 driver (disabled DLPF)

The Omnibus does not have a DRDY.
Testing
Note: this was tested before https://github.com/PX4/Firmware/pull/14208 (the driver had some compile errors).
I tested and compared 3 different settings:

DLPF=98, master, 1khz rate loop
DLPF=off, this PR, 1khz rate loop
DLPF=off, this PR, 2khz rate loop

For 2khz I had to disable mavlink streams, as the CPU load was too high otherwise.
Results

Both changes noticeably improve flight performance (smoother & calmer flight)
higher P gains are possible. I was able to increase them from 0.09 to 0.14 (which is more than 50%!)
or the other way around (which might be even more important): the same gains will work on a wider range of setups.

This again shows that every ms (and even sub-ms) of removed control-delay make a noticeable difference.
This is also measurable, is shows up in the PID analysis plots:

DLPF=98, master, 1khz rate loop:

Slight overshoots.
DLPF=off, this PR, 2khz rate loop:

DLPF=off, this PR, 2khz rate loop, increased P gains:

Quicker response.

Noise levels

The sw-filtered gyro signal does not look more noisy, and I did not have to change the filter settings (IMU_GYRO_CUTOFF=120)
The raw accel data looks considerably more noisy. This is expected, but is a problem for external toolings, like Flight Review, because a good setup now looks like it has vibration issues.

Logs

DLPF=98, master, 1khz rate loop: https://logs.px4.io/plot_app?log=fecf7598-4850-4d34-bfc9-7a7ec8fe6e8a
DLPF=off, this PR, 1khz rate loop: https://logs.px4.io/plot_app?log=c7ab9196-4a73-4deb-8075-d817d673637c
DLPF=off, this PR, 2khz rate loop: https://logs.px4.io/plot_app?log=172c4ef0-15cf-441e-9d94-6af9cbe5141b
DLPF=off, this PR, 2khz rate loop, increased gains: https://logs.px4.io/plot_app?log=241b2fa4-1a85-4747-b5b3-6d61aaa0d30d

@dagar do you know where the 512 come from in BOARD_DMA_ALLOC_POOL_SIZE?
Thanks for all the groundwork for this, Daniel!
@bresch @MaEtUgR fyi

@dagar do you know where the 512 come from in BOARD_DMA_ALLOC_POOL_SIZE?

The magic 5120? I believe it was determined manually by testing the different fat allocation cases.
https://github.com/PX4/Firmware/blob/f3fefd7d9372ec98d404e2e99da2e251114a2d7e/boards/px4/fmu-v2/src/board_config.h#L426

Not critical, but any chance you still have the DLPF changes? I was considering that path for making the new drivers work for I2C as well (once we have a good pattern for supporting both interfaces cleanly).


UTC time is shown as local time

Describe the bug
The estimated charging finish time shown is UTC and not local time.
To Reproduce
Steps to reproduce the behavior:

Start charging the car.
Examine the sensor.estimated_charging_finish_time entity
It will show the time in UTC rather than the local time.

Expected behavior
The time should be shown as local time.
Screenshots
N/A
Version info
hassio 2023.6.3
Additional context
Additional info can be supplied on request as well as testing if nessecary.

Ahhh, will have a look later!

Is your "Last Data Update" timestamp right ?

Is your "Last Data Update" timestamp right ?

No it is Aldo in UTC, ie offset with 2 hours from CET in my case.

You probably want to look into HA UTC & Time zone awareness as you probably get the correct time in UTC from the VCC API but need to adapt it

Please test v1.5.1!

Works fine now!


upgrade dependencies

Codecov Report

Merging #2081 (8286701) into master (c473c5f) will decrease coverage by 0.73%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2081      +/-   ##
==========================================
- Coverage   95.25%   94.51%   -0.74%
==========================================
  Files         387      387
  Lines        3516     3516
  Branches      423      423
==========================================
- Hits         3349     3323      -26
- Misses         83      107      +24
- Partials       84       86       +2

Impacted Files
Coverage Δ

packages/client/lib/commands/SINTERCARD.ts
50.00% <0.00%> (-50.00%)
:arrow_down:

packages/client/lib/commands/ZINTERCARD.ts
50.00% <0.00%> (-50.00%)
:arrow_down:

packages/client/lib/commands/CLUSTER_LINKS.ts
50.00% <0.00%> (-50.00%)
:arrow_down:

packages/client/lib/commands/COMMAND_LIST.ts
60.00% <0.00%> (-40.00%)
:arrow_down:

...ges/client/lib/commands/COMMAND_GETKEYSANDFLAGS.ts
60.00% <0.00%> (-40.00%)
:arrow_down:

packages/client/lib/commands/EXPIRETIME.ts
66.66% <0.00%> (-33.34%)
:arrow_down:

packages/client/lib/commands/PEXPIRETIME.ts
66.66% <0.00%> (-33.34%)
:arrow_down:

packages/client/lib/commands/SORT_RO.ts
80.00% <0.00%> (-20.00%)
:arrow_down:

packages/client/lib/errors.ts
95.45% <0.00%> (-4.55%)
:arrow_down:

packages/client/lib/client/commands-queue.ts
76.47% <0.00%> (-3.93%)
:arrow_down:

Continue to review full report at Codecov.

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


Create StripeAPI.md File

Added in the learning StripeAPI in JS environment topic file

I think your contribution is well put together and quite thorough in ensuring that all the steps for installing and setting up Stripe are included. I like that you even included information about keeping the integration secure and and testing. However I think that maybe it would be easier to follow if the subsections had more detailed descriptions summarizing what they are about. Of course some sections are straightforward and won't need much context and descriptions, but it would help to include more details in some of the sections.

I reviewed the changes, and I feel like it's now a bit more clear what the whole thing is about. Giving a descriptive summary about Stripe as well as highlighting the pros and cons will definitely serve as something useful that makes this document more digestible.

Thanks for the feedback, and suggestions. Can you also clarify if I should expand upon other sections in the readme

Yeah I think that could definitely be a good idea. Specifically, I think you can briefly discuss the significance of a few sections. For the section on obtaining API keys, you can discuss what they are used for, and emphasize that they should be kept safe. You can also talk about the significance of handling webhook events. I think these might be helpful for providing context, especially for someone new to web development.

Thanks for the feedback, you are right about needing to provide more insight there, feel free to look at the changes made

Very comprehensive contribution! I think that your document would benefit from a diagram to provide a supporting example to the webhook explanation. Something like this

ok thanks for the feedback, implemented it and going to merge now!


Remove pointer events check

It's not clear to me why this functionality was added since the component does not use pointer events on the hint (https://github.com/alphagov/accessible-autocomplete/blob/master/src/autocomplete.css) so I'm attempting to remove it, and see if there's another way to resolve issues with IE9 that don't break CSP

Don't display  on browsers without pointer events (fixes IE9 tests)
https://github.com/alphagov/accessible-autocomplete/pull/101

I've tested the autoselect example in IE9 and it works as expected.
Related: https://github.com/alphagov/accessible-autocomplete/issues/398

Theo:

yeap, if I recall correctly, IE9 does not overlap inputs nicely
the hint text is based on an overlayed input as you know (edited)
and it was misbehaving in IE9

Will do some more testing in IE9 and see if I can reproduce this.

Had another look at this, I think this is safe to remove for users of IE9 but it may be failing a Saucelabs test, worth checking once we've resolved the flakey saucelabs dashboard.


Minimalized plain text for embedded devices with low memory?

Hello, I'd like to suggest a very minimalized version that is just a text with the weather state (e. G. sunny).

Hi @lorhof1
Yes sure, just use the the one-line-format:
$ curl 'wttr.in/Nuremberg?format=%C\n'
Sunny
$ curl 'fr.wttr.in/Paris?format=%C\n'
Partiellement couvert

thanks


Add v0 of versioning to AAE hashtree locks, upgrades, and object hashing

This PR adds version 0 of AAE hashing to riak_kv_entropy_manager, riak_kv_index_hashtree, riak_object, and the riak_kv_vnode. Specifically, we've added logic which requires getting a hashtree lock to provide an appropriate version and then our hashtree version determines what version of riak_object:hash will be used for the incoming data.
Upgrading is completed automatically for the user. The upgrade uses a combination of riak_core_capability with a new riak_kv variable object_hash_version and logic within the riak_kv_entropy manager to intelligently upgrade hashtrees once all conditions have been met. THe upgrade flow is as follows:

User upgrade all nodes to 2.2.
Each node locally starts checking to begin upgrade in riak_kv_entropy_manager within the management tick.
IIF all partitions are built and have exchanged with all sibling partitions, we'll mark the riak_kv_entropy_manager state with a new pending_version.(need to exchange all siblings to catch any pre 2.1 data potentially suffering from kv679).
Each poke on a riak_kv_index_hashtree check the pending version of the manager and if it's set, calls the vnode to upgrade it's local tree.
Vnode destroys and makes a new hashtree with the upgrade atom included in the start opts.
Once all upgraded hashtrees have registered with entropy_manager, flip our entropy_manager version to 0 to indicate this node has completed the upgrade for all local nodes.

Open areas for discussion:

How best to handle default case of riak_object:hash without provided version(yz hashing). Current logic flips the hash when the entropy_manager notes all local trees have upgraded.
hashtree:destroy only removes data within the partition dir(i.e. ./data/antie_entropy/PARTID/*). The partition ID's still need to be cleaned up out of the anti-entropy directory.

@bsparrow435 So it occurred to me this morning that we should probably have an option to disable automatically upgrading to the new tree format. It doesn't necessarily have to be documented or supported, but I think it would be good to provide an escape hatch. If nothing else, it may make testing much easier if we want to, say, write a riak_test module that starts with 2.2 and then performs a downgrade (e.g. something like verify_riak_object_reformat).

+1 0e6bb3e

@borshop merge


Can history nodes work within a compound state?

I've discovered that for the state to be saved you have to exit the compound state - this is counter intuitive to me, although now that I know that I can design around it.   This is more of a question/suggestion than an issue.
My original state chart that does not save state on atomic task exit but is simpler and more intuitive IMO but does not work.

This works, but is more complex.

I'm ok with the way it works now that I have figured it out, but it seems also keeping track of state inside a compound state would lead to simpler state charts in some cases.  You have to really read the documentation carefully to catch that you have to leave the state and return for the history to work.

The current implementation is according to the specification (https://statecharts.dev/glossary/history-state.html) and all state chart implementation that I have seen work this way. Interestingly, it is nowhere defined what should happen if you enter a history state without leaving the surrounding compound state, so technically this behaviour is undefined. I'm not quite sure what a useful behaviour would be in this case, especially if the compound state contains additional compound states.  E.g. let's assume we have this:

We start in B then go to C then go to A1 which transitions to A2 which transitions to the History State. Where do we end up now? In A1 or in C ? This probably depends on whether the history state is deep or not. But for the history state to be able to go back to A1 it would need to continuously track all sub-state changes (and their substate changes) which will lead into quite the rabbit hole. I guess that's the reason why the spec conveniently leaves this point out.


feat: update sources to match generated schema

Summary
The current CRDs where generated but then edited. This pull request updates the code sources to match the current crd such that if you were to rerun the code generator, the output would match the current crd.

I had to remove a few lines to make the sources compile since they referenced the controller-runtime project and that dependency cannot be referenced in this project without some rework.

@dmatch01 those float64 fields are not supported types on Kubernetes and will not roundtrip. You should think about another way to express that value.