Thin white line or thin blue line at the bottom of the screen on Windows 11 when clicking on the Maximize button

Windows Terminal version (or Windows build number)
1.10.2714.0 to 1.11.2731.0 (both Windows Terminal and Windows Terminal Preview)
Other Software
default Windows 11 installation with WSL2
Steps to reproduce
Start 2 terminals, put one slightly over the other: there is no white line as can be seen here on the corner

Click on the maximize button, the taskbar is present at the bottom, which is something someone using a maximized terminal may not want, given the strong contrast and eye strain it creates (a terminal with black background and white text with a white taskbar at the bottom and a white titlebar on top)
The next logical step for this user is to attempt a basic configuration, simply using the available menu options that are shown or known to this user: in Windows Terminal, select the dark theme, and in settings, configure the taskbar to auto hide.

However, this results in a thin line at the bottom:

Expected Behavior
Pressing on maximize should maximize the window, and never leave any thin line at the bottom, regardless of the thin line color: this can be a issue with OLED displays, where the screen may get a "burn in" of any persistent element, like this thin line.
If a thin line must be left for impervious reasons (ex: as a visual reminder), the thin line color should be configurable by the user, to match the theme or to be less distracting.
Alternatively, if a strong visual reminder of the taskbar must always be left in fullscreen mode, there should be another mode grossly equivalent to "full screen" mode, maybe called differently to avoid confusion with the default fullscreen mode, but offering the option to have no thin lines at the bottom (something irrelevant with the current workflow), while still offering the list of tabs opened (something highly relevant with the current workflow).
Actual Behavior
After these 2 settings, there is now a thin white line at the bottom. Unless reverting the taskbar autohide, any further setting will only make the situation worse.
For example, the user may at this point attempt configuring shortcuts (a more advanced approach, but desperate times call for desperate moves...), where the only 2 choices available (focus mode and fullscreen mode) will not work:

focus mode will remove the tabs and the title bar (which the user may want to keep, as it's not the theme consistent titlebar that's breaking the focus, but the thin line!)
fullscreen mode will also leave a thin line, except this time it will be a thin blue line:

It may not be easily visible outside fullscreen mode, but you can download the image and show it in Paint/fullscreen if you want check the bottom for the precise color:

This behavior of fullscreen mode is possibly due to how DWM works with full screen applications when the taskbar is set to autohide, as there is no such thin line when the titlebar is not set to autohide and using the same shortcut and Terminal configuation.
However, this DWM behavior means there is no way to:

keep the default Windows theme system wide ("light", with a whitish background)
while also using Terminal default theme ("dark", with a black background)
without either introducing visual inconsistencies (whitish elements on the top and bottom of the screen) or sacrificing the titlebar and tabs (the list of tabs being extremely useful when several remote sessions are opened, far more than a visual reminder the taskbar still exist, as it can be easily brought back when pressing the windows key)

Even worse: users who followed a "reasonable escalation" approach will be left with the worst of both worlds, with no tabs in fullscreen mode, yet the thin blue line due to setting the titlebar to autohide - a thin blue line that wouldn't be present otherwise!
Maybe there should be a "third mode" that would:

maximize the Terminal
while preserving the display of Terminal tabs (important for the work flow!)
while preventing other clutter/visual inconsistencies not important for the work flow (ex: thin lines at the bottom), or at least offering the user to fully control them

A reasonable setting would be to at least let the user control the color of the thin blue line acting as a visual reminder there is a taskbar: a better color could be configured, matching the background if necessary, whether dark (for OLED) or light (for eInk).
While colors identical to the background color may be considered "less readable" and therefore less favorable settings, user preferences should be allowed to override such concerns, for example in these specific situation due to the display technology used.
Regardless of the root causes (DWM?), some users may also object to displaying a mandatory "thin blue line" on their display, for political reasons: a bing search on "thin blue line" reveals the connotation with law enforcement in North America, and a newer but potentially more problematic political connotations as noted in wikipedia ('The "thin blue line" has also been associated with white nationalists in the US, particularly after the Unite the Right rally in 2017.[7][8]')
This issue may be related to #4837, #3064 or #3425 which was closed because "this is the issue for terminal has white borders in dark mode, which is 100% fixed. If you want to discuss changing the default for light mode, please file a separate issue"
It may have been short-sighted to ignore the separate issue for light mode, as light mode is now the default Windows-11 theme.

NB: I realize the thin white line may not be visible without a zoom, so there it is after zooming on the bottom of the picture and filling the background in a darkish red

It is slightly offwhite/grey, so here is the precise color from the pipette tool in paint:

Also, when start 2 terminals, and putting one slightly over the other: there is no white line but there is a different dark dark grey line, which could be an issue for some users?
It may benefit from being a behavior that can be tweaked by an configuration option with a similar name, due to the similar appearance of these 2 issues (thin lines, except this one is a dark grey line, and not just on the bottom but on the sides too...)

This was on a fresh Windows 11 with the default settings. To mitigate the issue, indeed I tried different accent colors, one of which may have been blue. This could explain this precise color code? I will check this test installation again to confirm that.
It may not be a pure Terminal issue, but it impacts the Terminal use: this test install was to check how possible it would be to replace existing terminals by dedicated laptops running Windows Terminal in full screen.
For such use cases, ideally the "full screen" mode of the Terminal should have an option to override all mousing targets, similar to how web browsers in kiosk mode fully occupy the screen.
If such an option isn't possible or if the indicator for the taskbar presence can't be hidden, could the color be at least made configurable?
This would achieve the same result visually if only a keyboard is connected (or by disabling the mouse)


Executive Test Traceability Card Implementation

This card is created to implement traceability card in executive and this PR has to be merged after https://github.com/Hygieia/Hygieia/pull/2880

I am not sure this is the correct way to go about this change. We should discuss this further.

@Sbrenthughes Traceability card implementation is updated as per the discussion had to map it through collectorItemId. This PR has to be merged after this PR has to be merged after https://github.com/Hygieia/Hygieia/pull/2880

@nameisaravind please resolve the conflicts and update so that the change can be accepted


typeAcquisition.exclude configuration settings changes are ignored when already cached

TypeScript Version:  4.0.5

Search Terms: typeAcquisition exclude
Code
Use the following jsconfig.json file:
{
    "compilerOptions": {
        "checkJs": true,
        "strict": true,
        "resolveJsonModule": true,
    },
    "include":[
        "./**/*",
    ],
    "typeAcquisition": {
        "exclude": [
            "copy-webpack-plugin"
        ]
    }
}

Expected behavior:
When identifying that the source of a type-related issue exists in the automatically acquired type declarations, it is natural to add that package to the typeAcquisition.exclude array in the [j/t]sconfig.json file.
Once this is done, the TypeScript language service should not use automatically acquired type declarations for the specified package (the copy-webpack-plugin package in the example above).
In other words, a user should be able to make the configuration adjustment, restart the TypeScript/JavaScript Language Service and find that any packages newly added to the "typeAcquisition.excluded" array should no longer use automatically acquired packages.
Actual behavior:
The TypeScript language service continues to use automatically acquired type declarations for the newly excluded package.
To be clear, in the example above, setting typeAcquisition.enable = false does disable the type acquisition for copy-webpack-plugin.
Manually "uninstalling" the type declarations (using, for example, npm uninstall --save-dev @types/copy-webpack-plugin) allowed the typeAcquisition.exclude setting to work as expected. In my case, the cache in question was located at ~/.cache/typescript/4.0.
Playground Link:
N/A. The Playground does not have an option to configure the typeAcquisition setting.
Related Issues:
Couldn't find any.

To be clear, this is running in VSCode v1.51.1 using the Remote Containers extension v0.148.1 (devcontainer running on node:10).

Can we have this fix? In my computer I am working on two projects using react 17 and 18 respectively. The react 18 project works fine but in the react 17 project, I encounter error message like this
'ThemeProvider' cannot be used as a JSX component.
  Its instance type 'Component<ThemeProviderProps<any, any>, any, any>' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'React.ReactNode' is not assignable to type 'import("/Users/.../Library/Caches/typescript/4.6/node_modules/@types/react/index").ReactNode'.

I think adding "typeAcquisition": {     "exclude": ["react"]   } in jsconfig.json and installing @types/react@^17 locally should resolve this warning but it is not working right now

Can we have this fix? In my computer I am working on two projects using react 17 and 18 respectively. The react 18 project works fine but in the react 17 project, I encounter error message like this
'ThemeProvider' cannot be used as a JSX component.
  Its instance type 'Component<ThemeProviderProps<any, any>, any, any>' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'React.ReactNode' is not assignable to type 'import("/Users/.../Library/Caches/typescript/4.6/node_modules/@types/react/index").ReactNode'.

I think adding "typeAcquisition": { "exclude": ["react"] } in jsconfig.json and installing @types/react@^17 locally should resolve this warning but it is not working right now

exactly same issue for me


OwrTransportAgent: Fix helper server/candidate gathering race

This is a fix for https://github.com/EricssonResearch/openwebrtc/issues/165 .
All helper servers must be added to the transport agent before any sessions are added.
No locks are needed, given the rule above and that all other relevant functions are called from the main thread.

Note that I have not yet tested this patch, but it looks right. :smile: I'll try to reproduce the issue tomorrow and re-test with the fix.

How can I reproduce the error before this patch?

I think using a STUN server with a known IP address and using the IP address instead of host name. And then a minor modification to to add some arbitrarily large timeout to emulate a slow DNS resolution. We can try it tomorrow.

I don't know if this is the same race, but I pretty often get in the situation that all candidates are already gathered when the offer has been created (initial offer), so the offer contains all of them and there are no onicecandidate events with valid candidates fired.
Seems to happen more than half of the time.

Does not build :-1:

I fixed the patch and have tested and verified that the patch causes gathering to wait until all helper servers that were queued to be added have indeed been added. Only then does gathering begin. Unfortunately I have not been able to access a specific NAT setup to test this in reality so I would welcome testers.

Otherwise this looks good to go IMHO.

Are we landing this?

I need to fix Sebastian's comment and then we can land it.

I fixed that now and merged it all :smile:


[tool_crash] FileSystemException: readInto failed, OS Error: The operation completed successfully., errno = 0

Command
flutter --no-color build apk

Steps to Reproduce

...
...
...

Logs
FileSystemException: readInto failed, OS Error: The operation completed successfully.
, errno = 0
#0      _RandomAccessFile.readIntoSync (dart:io/file_impl.dart:834:7)
#1      _File.readAsBytesSync (dart:io/file_impl.dart:593:35)
#2      _File.readAsStringSync (dart:io/file_impl.dart:624:18)
#3      _File.readAsLinesSync (dart:io/file_impl.dart:630:36)
#4      ForwardingFile.readAsLinesSync (package:file/src/forwarding/forwarding_file.dart:107:16)
#5      ForwardingFile.readAsLinesSync (package:file/src/forwarding/forwarding_file.dart:107:16)
#6      ProjectMigrator.processFileLines (package:flutter_tools/src/base/project_migrator.dart:40:37)
#7      TopLevelGradleBuildFileMigration.migrate (package:flutter_tools/src/android/migrations/top_level_gradle_build_file_migration.dart:37:5)
#8      ProjectMigration.run (package:flutter_tools/src/base/project_migrator.dart:84:16)
#9      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:278:15)
#10     AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:208:11)
#11     BuildApkCommand.runCommand (package:flutter_tools/src/commands/build_apk.dart:116:27)
<asynchronous suspension>
#12     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1336:27)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#14     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#15     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#17     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:244:5)
<asynchronous suspension>

[!] Flutter (Channel stable, 3.10.3, on Microsoft Windows [Version 10.0.19045.3324], locale en-US)
    • Flutter version 3.10.3 on channel stable at I:\flutter_sdk\flutter_windows_3.10.3-stable\flutter
    ! Warning: `flutter` on your path resolves to I:\flutter_sdk\3.13.2\flutter\bin\flutter, which is not inside your current Flutter SDK checkout at I:\flutter_sdk\flutter_windows_3.10.3-stable\flutter. Consider adding I:\flutter_sdk\flutter_windows_3.10.3-stable\flutter\bin to the front of your path.
    ! Warning: `dart` on your path resolves to I:\flutter_sdk\3.13.2\flutter\bin\dart, which is not inside your current Flutter SDK checkout at I:\flutter_sdk\flutter_windows_3.10.3-stable\flutter. Consider adding I:\flutter_sdk\flutter_windows_3.10.3-stable\flutter\bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f92f44110e (4 months ago), 2023-06-01 18:17:33 -0500
    • Engine revision 2a3401c9bb
    • Dart version 3.0.3
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at C:\Users\alamin\AppData\Local\Android\sdk
    • Platform android-34, build-tools 33.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Android Studio (version 2022.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)

[✓] Connected device (2 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 116.0.5845.188
    • Edge (web)   • edge   • web-javascript • Microsoft Edge 116.0.1938.81

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Flutter Application Metadata
Type: app
Version: 1.0.8+8
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: 18a827f3933c19f51862dde3fa472197683249d6
Plugins
facebook_auth_desktop-0.0.4
firebase_auth-4.9.0
firebase_auth_web-5.8.0
firebase_core-2.15.1
firebase_core_web-2.7.0
flutter_facebook_auth-5.0.1
flutter_facebook_auth_web-4.1.0
flutter_pdfview-1.3.1
flutter_secure_storage-6.0.0
flutter_secure_storage_linux-1.1.1
flutter_secure_storage_macos-1.1.1
flutter_secure_storage_web-1.0.2
flutter_secure_storage_windows-1.1.2
flutter_webview_plugin-0.4.0
flutter_windowmanager-0.2.0
fluttertoast-8.1.1
google_sign_in-5.4.2
google_sign_in_android-6.1.1
google_sign_in_ios-5.5.0
google_sign_in_web-0.10.2
image_gallery_saver-2.0.3
path_provider-2.0.11
path_provider_android-2.0.21
path_provider_ios-2.0.11
path_provider_linux-2.1.7
path_provider_macos-2.0.6
path_provider_windows-2.1.3
shared_preferences-2.0.15
shared_preferences_android-2.0.14
shared_preferences_ios-2.1.1
shared_preferences_linux-2.1.1
shared_preferences_macos-2.0.4
shared_preferences_web-2.0.4
shared_preferences_windows-2.1.1
sqflite-2.2.0+3
url_launcher-6.1.6
url_launcher_android-6.0.21
url_launcher_ios-6.0.17
url_launcher_linux-3.0.1
url_launcher_macos-3.0.1
url_launcher_web-2.0.13
url_launcher_windows-3.0.1

Hi @alamincse6615
You are using an old Flutter version. Could you try upgrading to the latest stable/master channel and retry?
flutter channel master
flutter upgrade

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.13.4, on macOS 13.5 22G74 darwin-x64, locale en-VN)
    • Flutter version 3.13.4 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 367f9ea16b (31 hours ago), 2023-09-12 23:27:53 -0500
    • Engine revision 9064459a8b
    • Dart version 3.1.2
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode15RC.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (5 available)
    • RMX2001 (mobile)       • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)        • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • iPhone 14 Pro (mobile) • 3BD60F46-FB95-41A0-A179-8AA3F637DA4E     • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)        • macos                                    • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)           • chrome                                   • web-javascript • Google Chrome 117.0.5938.62

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.14.0-14.0.pre.307, on macOS 13.5 22G74 darwin-x64, locale en-VN)
    • Flutter version 3.14.0-14.0.pre.307 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1e4a1be681 (60 minutes ago), 2023-09-14 19:10:37 -0700
    • Engine revision 45bc4307cd
    • Dart version 3.2.0 (build 3.2.0-162.0.dev)
    • DevTools version 2.28.0-dev.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • Pixel 7 (mobile) • 2B171FDH20084L                           • android-arm64  • Android 13 (API 33)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 117.0.5938.62

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.


Not able to interact with DropdownMenu.Trigger when the Dropdown is open

Bug report
Current Behavior
https://user-images.githubusercontent.com/35605914/208173460-98c8c0ac-d448-470a-96b3-6790a322d9cd.mov
Expected behavior
To be able to interact with that textfield (I am building a combobox)
Reproducible example
<DropdownMenu.Root modal={false} open={open} defaultOpen={true} onOpenChange={setOpen}>
			<DropdownMenu.Trigger asChild={false}>

 {
					event.stopPropagation();
					event.currentTarget.focus()
					// if (React.isValidElement(props.dropdown) && !(props.disableShowOnClick ?? false)) setOpen(!open)
				}}>{(props.dropdown instanceof Function) ? props.dropdown(setOpen) : props.dropdown}

			</DropdownMenu.Trigger>

			<DropdownMenu.Portal >
				<DropdownMenu.Content className="rounded bg-white shadow-2xl z-50 max-h-96 max-w-[100vw] overflow-y-scroll" sideOffset={5}>
					{(props.children instanceof Function) ? props.children(setOpen) : props.children}
					{props.arrow && <DropdownMenu.Arrow className="fill-white" />}
				</DropdownMenu.Content>
			</DropdownMenu.Portal>
		</DropdownMenu.Root>

Suggested solution
Have a property to enable interacting with the  DropdownMenu.Trigger (similar to how modal property performs)
Your environment

Software
Name(s)
Version

Radix Package(s)

"@radix-ui/react-dropdown-menu": "^2.0.1",

React
n/a
"react": "^18.2.0",

Browser
Chrome

Node
n/a

npm/yarn
pnpm

Operating System
Macos

DropdownMenu isn't intended to be used to build a combobox. Trying to shoe-horn it won't work unless you rebuilt a ton of functionality yourself. This is due to how focus is currently managed as well as layering.
I will close the issue as it's not really the intended use of the package.


Fix (denoify) imports for three/examples

The JS files form the Three.js/examples also need to have their relative imports fixed. They could be manually updated if you are only using a few of them. (which is the current adhoc fix hehehe)
But it would be nice to modify the already existing "denoify.ts" script to address this issue.
import { ... } from 'three';
should look like:
import { ... } from '../../../three.module.js';
Given the folder structure we are currently using on ./lib

So far, i think the issue is fixed given the change in the reg ex :D

See #7 I will close this for the same reason


Add api attributes to the attribute vocabulary.

Design doc: https://goo.gl/3WTUfW
Release note:
None

This change is

/lgtm

qq: should these be added to the istio-mixer tmpl CRs?
https://github.com/istio/istio/blob/master/install/kubernetes/templates/istio-mixer.yaml.tmpl ?


Clarify java 11.0.7 requirement in release notes

As of Presto 347, Java 11.0.7 is required. This should be prominent in the release notes.

Thanks!


add option to box results for multi returns

Started this finally and I got it to compile. I tried to follow the hacking guide but not entirely sure if / what tests I should write. I will try and write a better description for the box results config option next time I get back to it. Just wanted to get this up to get something up here.
Fixes #185
Will make a second PR for tables as you suggested.

Thanks for this PR. The main application changes look pretty good.
In terms of tests, you may want to write a new example. All of the examples are executable tests. There is a driver test that iterates through all the example directories, uses the db.sql file to initialize a database, runs pggen using the pggen.toml file in the example directory, executes the main.go file, then diffs the output against the output.txt file. The nice thing about writing your test as an example is that you document the feature at the same time that you test it.
It's worth reading through the comment at the top of the test driver for some more details: https://github.com/opendoor/pggen/blob/master/examples/examples_test.go

I tried to add a small example for the box query, I named the example just "boxed values" so I/someone can add the box results to tables using the sample example. I think there is a slight issue with running the examples on windows where the newlines of the file doesn't match the go output so it fails locally but will work in CI. Not really a problem just kinda something I noticed.

Thanks for adding this feature!


ci_sim: the version of nodejs obtained by apt install is too low

Summary
so using npm to upgrade the nodejs tool to the latest
Impact
Testing
sim:local

@zhhyu7 very nice!!! Do you have some build time comparison before this change and after it?


Add MRSelectCountry in List

MRSelectCountry - An easy way to get country data which includes the country name and dial code for iOS Developers
Project URL
https://github.com/mrazam110/MRSelectCountry
Category
UI
Description
An easy way to get country data which includes the country name and dial code for iOS Developers
Why it should be included to awesome-ios (mandatory)
It's easy to use just plug and play type so devs can use it easily. Devs follow awesome-ios that's why I want my repo to be there.
Checklist

[x] Only one project/change is in this pull request
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

1087
301
https://github.com/rs/SDWebImage redirects tohttps://github.com/SDWebImage/SDWebImage

1403
301
https://github.com/Hearst-DD/ObjectMapper redirects tohttps://github.com/tristanhimmelman/ObjectMapper

  Generated by :no_entry_sign: Danger

Hi @mrazam110 thanks for contributing!
I'm not sure if your tests cover all features of project. Can you add more tests to improve code coverage?  Feel free to reopen this PR when you get done. :heart:


[redfish] Update http response code

Depends on: https://github.com/RackHD/on-http/pull/478

👍

BUILD RackHD #807 : UNSTABLE
   - ** BUILD build-config-setup  #105649: SUCCESS

BUILD RackHD #807  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

Jenkins: Depends on: https://github.com/RackHD/on-http/pull/478   and test this please
@zyoung51  confirmed with @changev need add 'Jenkins:' before 'depends on' to let dependency build work

test this please

@RackHD/corecommitters please review.

BUILD RackHD #808 : UNSTABLE
   - ** BUILD build-config-setup  #105796: SUCCESS

BUILD RackHD #808  Error Logs:

Test Name: redfish_emc_catalogs_test
Error Details: EMC Redfish Catalog size failure
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/v1_1/redfish_endpoint_tests.py", line 229, in redfish_emc_catalogs_test
    assert_not_equal(len(catalog), 0, message='EMC Redfish Catalog size failure')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 151, in assert_not_equal
    raise ASSERTION_ERROR(message)
AssertionError: EMC Redfish Catalog size failure

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

Build finished.

test this please

BUILD RackHD #809 : UNSTABLE
   - ** BUILD build-config-setup  #105814: SUCCESS

BUILD RackHD #809  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

test this please

BUILD RackHD #811 : UNSTABLE
   - ** BUILD build-config-setup  #105975: SUCCESS

BUILD RackHD #811  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

Build finished.

test this please

BUILD RackHD #812 : UNSTABLE
   - ** BUILD build-config-setup  #105996: SUCCESS

BUILD RackHD #812  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

Build finished.

test this please
sorry for that the Dependency-PR test suffered the error
Test Name: redfish_emc_catalogs_test
Error Details: EMC Redfish Catalog size failure

This is a common error appear in other test too.
Except this error your PRs are ok.
I'm trying to test some more times see if it can pass this error.

BUILD RackHD #813 : UNSTABLE
   - ** BUILD build-config-setup  #106029: SUCCESS

BUILD RackHD #813  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

According to the test details your PRs are good.
I advice to do the merge just as before when no dependency-PR test, merge-one-test-another.
Till we fix the EMC Redfish Catalog size failure.

BUILD RackHD #816 : UNSTABLE
   - ** BUILD build-config-setup  #106382: SUCCESS

BUILD RackHD #816  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

jenkins: test this please

BUILD RackHD #817 : UNSTABLE
   - ** BUILD build-config-setup  #106597: SUCCESS

BUILD RackHD #817  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

BUILD RackHD #821 : UNSTABLE
   - ** BUILD build-config-setup  #107117: SUCCESS

BUILD RackHD #821  Error Logs:

Test Name: test_delete_subscriptions
Error Details: unexpected status on DELETE
Stack Trace: Traceback (most recent call last):
  File "/usr/lib/python2.7/unittest/case.py", line 331, in run
    testMethod()
  File "/usr/lib/python2.7/unittest/case.py", line 1043, in runTest
    self._testFunc()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 296, in testng_method_mistake_capture_func
    compatability.capture_type_error(s_func)
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/compatability/exceptions_2_6.py", line 27, in capture_type_error
    func()
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/case.py", line 350, in func
    func(test_case.state.get_state())
  File "/home/jenkins/workspace/RackHD/build/test/tests/api/redfish_1_0/event_service_tests.py", line 124, in test_delete_subscriptions
    assert_equal(204, status, message='unexpected status on DELETE')
  File "/tmp/.venv/local/lib/python2.7/site-packages/proboscis/asserts.py", line 55, in assert_equal
    raise ASSERTION_ERROR(message)
AssertionError: unexpected status on DELETE

test this please

Build finished.

+1


AWS Connection Error

What issue do you have? Please be as thorough and explicit as possible.
Getting a not connected to AWS Error while using the credential auth method. I went to bed with the plugin working fine, and this morning I noticed no lights were working
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI-X on a raspberry pi. All packages are updated as well as node.js

Which version of Homebridge/HOOBS do you have?

V1.6.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Raspberry Pi

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

npm 9.1.2

Which Govee devices do you have that are causing issues? Please include product models if applicable.

All devices, I have a set of twinkly brand christmas lights that are working fine on my homebridge setup.
Please paste any relevant logs below.

Log Errors ( They arent showing in the above post )
[29/11/2022, 14:44:34] [Govee] [Living Room Couch] not using AWS connection as not connected to AWS.
[29/11/2022, 14:44:34] [Govee] [Living Room Couch] could not be updated as no connection method available at file:///usr/local/lib/node_modules/homebridge-govee/lib/platform.js:1803:13.
[29/11/2022, 14:44:34] [Govee] [Living Room Couch] not using AWS connection as not connected to AWS.
[29/11/2022, 14:44:39] [Govee] [Living Room Couch] could not be updated as no connection method available at file:///usr/local/lib/node_modules/homebridge-govee/lib/platform.js:1803:13.

disregard, I see an issue opened already regarding this. Will monitor that ticket.

Closing, please see https://github.com/bwp91/homebridge-govee/issues/367


Adding New Jobs for the blockchain developers

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

This repository is intended to learn Web3 and not to post job opportunities.


Move extensions into the workspaces layer

Move some common extensions into the workspaces layer so they can be access from both the editor and LSP projects. Recommend review commit-by-commit for this to make the diff more readable.

@dotnet/razor-tooling for review.


Add button adapter to run program without Raspberry Pi

It would be nice to be able to run morse-code-twitter on a normal computer without RPi GPIO, for testing purposes. We can do this by breaking the logic between the Morse Code handling, the RPi Button Handling, and adding a keyboard button through a library like pygame. Some research will be required to figure out the best way to do this.

branch separate_logic starts to work on this, breaks the button callback logic away from the actual RPI GPIO. Another class could be written to be a regular computer adapter so long as keyup and keydown events could call callback with appropriate arguments.


Update OSS CAD Suite version to 2024-12-01.

Monthly update; auto-generated by create-pull-request.

Yosys cannot be upgraded until https://github.com/amaranth-lang/amaranth/pull/1543 shows up in a new Amaranth release.


Snackbar autoHideDuration not working

    <Snackbar
        open
        autoHideDuration={2000}
        anchorOrigin={{ vertical: 'top', horizontal: 'center' }}
        message={asdsadsa}
      />

Message never goes away... what am I doing wrong ?

You need to control the component. Setting autoHideDuration mean that onRequestClose will be called when needed.

@oliviertassinari I have the exact same situation. Could you please elaborate more your answer?

@byoigres I was making a reference to those lines
https://github.com/callemall/material-ui/blob/6172bd0af0c7a0ad66626a9c3d9f5aaa34e1a6f7/docs/src/pages/demos/snackbars/SimpleSnackbar.js#L45-L47

same issue,but resolve when I add   <Snackbar
open={!success||!this.state.success}
onClose={()=>{this.setState({open:false})}}
/>
you must have onClose method to setState open:false


Page freeze

Executing this code
void main() {
	String str = '''
@Component(
    selector: 'channels-editor',
    templateUrl: 'sale_detail_component.html')
class SaleDetailComponent extends BaseChannelsEditor  {
}
  ''';
  print(str.replaceAllMapped(new RegExp('@Component(.*\\n*)*class\\s+(\\S+)\\s+(extends\\s+\\S+\\s+)?(with\\s+\\S+\\s+)?', multiLine: true, caseSensitive: false), (match)=>"##" ));
}

leads to page freeze with no output and no errors.

This appears to be a duplicate of https://github.com/dart-lang/dart-pad/issues/384.
If you run the same code in the terminal it doesn't terminate. We might need to come up with a better UI for handling this, but it's non-trivial to do so.


r1.0 python 3.5 fixes

Aww man, I just triggered release builds.
I'll kill them to quickly run these PR builds instead.

How to set up GPU driver on Ubuntu ?

This is definitely not the correct location for any questions.
GPU driver setup i manufacturer for its driver installation instructions.

Jenkins, test this please


Compare TextDB with MeTA

MeTA: https://meta-toolkit.org
GitHub: https://github.com/meta-toolkit/meta/
MeTA is a modern C++ data sciences toolkit. I will basically focus on following provided functions:
-text tokenization, including deep semantic features like parse trees
-inverted and forward indexes with compression and various caching strategies
-a collection of ranking functions for searching the indexes

MeTA has really long setup time and we need to install homebrew and Command Line Tools for Xcode to make it work. (30 minutes - MacOS)

@fukoyui Hopefully TextDB will be easy and fast to install :-)

In order to write codes to utilize this tool in C++ project, learning and using CMake might be the best way to build a C++ project like this. I tried Eclipse (C/C++) and g++ (terminal in Mac) and both ways have dependency problems whenever I organize the directory. I googled for solutions and people on StackOverflow suggest to use CMake instead of invoking g++.

Hmmm, I forgot that MeTA is in C++.  Not sure whether and how we should include it in our Java package.  Let's discuss it F2F today.

MeTA is a modern C++ text processing tool intended for command-line users only. It does not enable its users to install it as library. Users can add their own features by edit source code.

Introduction to some features of MeTA: https://www.youtube.com/watch?v=hdGL3cBIM9U&feature=youtu.be

Thanks!


More new quotes

This is the first time I'm contributing to an open source project. I've created a new quotes file 023.json. Please advise if I've not followed the proper procedure.
https://github.com/mubaris/motivate/commit/4a3fa741b01abfe8c2815f9e01e8d39b2f08b31a

Don't delete data/020.json, Otherwise everything looks good.


Elastic search SocketTimeoutException while upgrading  from conductor 2.30.3 to conductor 3.4.1

Describe the bug
I am trying to upgrade from conductor 2.30.3 to conductor 3.4.1 and getting below issue for elastic search.
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2022-08-19 01:48:02.867 [main] ERROR org.springframework.boot.SpringApplication [] - Application run failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'workflowBulkResource' defined in URL [jar:file:/app/libs/conductor-server-3.4.1-boot.jar!/BOOT-INF/lib/conductor-rest-3.4.1.jar!/com/netflix/conductor/rest/controllers/WorkflowBulkResource.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'workflowBulkServiceImpl' defined in URL [jar:file:/app/libs/conductor-server-3.4.1-boot.jar!/BOOT-INF/lib/conductor-core-3.4.1.jar!/com/netflix/conductor/service/WorkflowBulkServiceImpl.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'workflowExecutor' defined in URL [jar:file:/app/libs/conductor-server-3.4.1-boot.jar!/BOOT-INF/lib/conductor-core-3.4.1.jar!/com/netflix/conductor/core/execution/WorkflowExecutor.class]: Unsatisfied dependency expressed through constructor parameter 5; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'executionDAOFacade' defined in URL [jar:file:/app/libs/conductor-server-3.4.1-boot.jar!/BOOT-INF/lib/conductor-core-3.4.1.jar!/com/netflix/conductor/core/orchestration/ExecutionDAOFacade.class]: Unsatisfied dependency expressed through constructor parameter 2; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'es6IndexDAO': Invocation of init method failed; nested exception is java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-0 [ACTIVE]
at org.spr
Details
Conductor version: 2.30.3
Persistence implementation: Postgress
Queue implementation: Postgres
Lock: Redis
Workflow definition: N/A
Task definition: N/A
Event handler definition: N/A
Additional context
conductor running in a Kubernetes cluster.

@trivedishalini looks like Conductor is not able to connect to the Elasticsearch cluster. Can you check the connection settings like hostname, port etc or the firewall settings if connection from Conductor to Elasticsearch is allowed?

java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-0 [ACTIVE]

@aravindanr ,yes all properties are fine . Actually we already have conductor 2.30.3 and elastic search up and running on my client machine and everything working fine with that But Now I have to upgrade this cluster with conductor 3 .
Conductor 3 and elastic search fresh installation is working fine But I have to do upgrade on client machine from conductor 2 to conductor 3 to avoid data loss .
And upgrade path where conductor 3 and elastic search communication breaking.
Any idea ?

@trivedishalini  2.30.3 depend on  elasticsearch 5.x, but Conductor 3 depnd on elasticsearch 6.x, and docker-compose.yaml use the same volume path. try docker compose -f docker-compose.yaml down --volumes remove es volume.

Conductor3.X checking es health by adding default color status filter as green always and my ES status yellow somehow but as of now its . Thats why it got break when I upgrade from conductor2.X to conductor 3.X .
Solution:
There is property name 'conductor.elasticsearch.clusterHealthColor' in conductor 3.X , I was able to override status color to yellow from green and got it working.
Which is short term solution but I need to improved my elastic search or green status still.
Closing this issue and got it working now


Doesn't seem to work on 1.21

Doesn't work on my 1.21 server

Can you provide more technical info? I'll try to reproduce

Ah, nevermind, Mojang just broke all the datapacks... I'll publish a new release soon. You can just rename functions and advancements folders to function and advancement to fix that.

Mojang is being funny and not considering a big community with its internal changes as always... Anyway, fixed it and made a pull request so you don't have to fix anything. Check if it works with /tick sprint first though just in case.

Actually I appreciate their work, their changes are quite important for optimizing and improving the game. I already updated (and backported) the pack, so this can be closed.


Autodeployment to PyPi does not work

The pypi-publish.yaml workflow is configured correctly as far as I know. I mirrors what we've had in other projects (linkml, neat-schema etc.). It throws an error in gh-action during the install dependencies step:
[1]Run poetry install --no-interaction
[2](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:2)
  poetry install --no-interaction
[3](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:3)
  shell: /usr/bin/bash -e {0}
[4](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:4)
  env:
[5](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:5)
    pythonLocation: /opt/hostedtoolcache/Python/3.9.13/x64
[6](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:6)
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.9.13/x64/lib
[7](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:7)
    VENV: .venv/bin/activate
[8](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:8)

[9](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:10)
[10](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:11)
  RuntimeError
[11](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:12)
[12](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:13)
  Poetry could not find a pyproject.toml file in /home/runner/work/sssom/sssom or its parents
[13](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:14)
[14](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:15)
  at ~/.local/venv/lib/python3.9/site-packages/poetry/core/factory.py:369 in locate
[15](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:16)
      365│             if poetry_file.exists():
[16](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:17)
      366│                 return poetry_file
[17](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:18)
      367│
[18](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:19)
      368│         else:
[19](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:20)
    → 369│             raise RuntimeError(
[20](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:21)
      370│                 "Poetry could not find a pyproject.toml file in {} or its parents".format(
[23](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:24)
      371│                     cwd
[21](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:22)
      372│                 )
[22](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:23)
      373│             )
[23](https://github.com/mapping-commons/sssom/runs/6729619135?check_suite_focus=true#step:5:24)
Error: Process completed with exit code 1.

Not sure where the problem lies.

Fixed by 8c55b3598584d8dfa0d1530b7a7caca4c13bf9d9


Events stop working after first end

Hi.  Using a static nipple everything works great on first use.  On second use, only the start is captured; move and end are ignored.
Fiddle here...
https://jsfiddle.net/ykotkzow/18/
Thanks!

Oh... looks like the lib is missing some triggers.
Specifically the ones with the id of the joystick.
I've updated the fiddle to have a temporary solution: https://jsfiddle.net/ykotkzow/19/
By listening to general events.
This is a bug though.

That works.  Thanks @yoannmoinet

This has been fixed in 0.6.7


Eliminate wrapperProps

this is a pre-fc pass to cut some  700 lines, from app and props of yesteryear, @gatzjames is working on a FC pass on app.tsx so hoping this will help.
next step would be to rethink the pagelayout component and try to nest the mouse handlers and pan height and width story within rather than drilling from app.tsx through wrapperProps. #4994
highlights

moved each function from app.tsx and wrapper.tsx to "appropriate" place in component tree.
I exercised some discretion about where is appropriate based on props and selectors available in a given context.
avoided any which involved react rendering hacks.
curiously send and download request behaviour  is coupled to redux state.

@filfreire fixed! Thanks! 🙏


[WIP] Implement links (finally only links :D )

WIP
WIP
WIP

We will have a nice call with @danielsaidi on how to polish this so we can merge this ASAP :) dont mind the formatting, this is still WIP

@DominikBucher12 Is this ready for review?

I think you can review this, so we can merge it soon... But I would say finishing https://github.com/danielsaidi/RichTextKit/pull/154 and https://github.com/danielsaidi/RichTextKit/pull/146 before this is needed more I'd say :)

@DominikBucher12 I have reviewed the PR in its current state. It will be amazing to get link support, but this PR needs a bit more work before we can merge it.

What's the current status on having link support integrate into the main branch. Would love to use this...


add detail of output for file object

specify that path and full filename with extension are returned
provide sample output for example included in doc

Docs Build status updates of commit 3fb2437:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/path-property-filesystemobject-object.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


docker-machine env gives 'read: connection reset by peer'

I'm trying to connect docker-machine to a fresh new remote docker host running Ubuntu 14.04, but running env keeps giving me 'connection reset by peer'. The docker client on the machine itself just works. The port is not blocked by a firewall or iptables.
docker-engine        1.9.0-0~trusty
docker-machine       0.5.0 (04cfa58)

$ netcat -vz <ip> 2376
 <ip> 2376 open

$ docker-machine create -d generic \
  --generic-ssh-user ubuntu \
  --generic-ssh-key ~/.ssh/id_rsa \
  --generic-ip-address <ip> \
  chpc
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
To see how to connect Docker to this machine, run: docker-machine env chpc

$  docker-machine env chpc
Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": read tcp <IP_ADDRESS>:65075-><IP_ADDRESS>:2376: read: connection reset by peer
You can attempt to regenerate them using 'docker-machine regenerate-certs name'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

$  docker-machine regenerate-certs chpc
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...

$ docker-machine env chpc
Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": read tcp <IP_ADDRESS>:65113-><IP_ADDRESS>:2376: read: connection reset by peer
You can attempt to regenerate them using 'docker-machine regenerate-certs name'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

Same issue here on OSX using latest docker toolkit. Destroying the virtulbox VM and recreating one even with different name didn't help.

Did you get it to work?
Here is what i have and facing the same issue:
$ docker-machine version
docker-machine version 0.5.2 ( 0456b9f )
$ docker version
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.3
Git commit:   a34a1d5
Built:        Fri Nov 20 17:56:04 UTC 2015
OS/Arch:      darwin/amd64

Hi @harsh-apigee, @gijzelaerr can you gist the output for docker-machine -D env HOST? That would help us understand the issue. Thanks.

it turned out in my case it was a firewall issue. Sorry for the noise.

@gijzelaerr Can we close the issue then?

for me you can, but it looks like other people have similar (unsolved) issues.

@ypaq @harsh-apigee did you find a solution to your issue? Have you tested 0.5.0?

Closing for bookkeeping. If you still have issues, let us know and we will reopen.


rPackages.apsimx: fixed build

Description of changes
Added pkgs.which to nativebuildinputs.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks for spotting this, looks like an external piece of software is needed: https://www.apsim.info/download-apsim/
the R package is an interface to this. And it doesn't look like this offers a free download. I moved pkgs.which from nativeBuildInputs to BuildInputs, so at least which finds Mono when it starts, but the package still complains that APSIM is not found (obviously). I don't think we can really fix that, since APSIM requires a fee for downloading.

The R package itself is gpl3, so I guess that's fine, no?
https://cran.r-project.org/web/packages/apsimx/index.html
I guess we could provide the package still, and user would need to provide APSIM on their own ?

Put which under buildInputs instead of nativeBuildInputs, it builds and doesn't error:
> library(apsimx)
APSIM(X) not found.
                        If APSIM(X) is installed in an alternative location,
                        set paths manually using 'apsimx_options' or 'apsim_options'.
                        You can still try as the package will look into the registry (under Windows)

I guess this could be shipped in this state, the users just need to provide APSIM. What do you think?

Merge conflict solved. So in summary, the package needed which in the buildInputs, but users will need to provide APSIMX on their own. If that's ok for you this should be ready to merge.


Revert "chore: disable caching of secrets and serviceaccounts (#276)"

This reverts commit 519d9fe3
Description
When investigating https://github.com/aquasecurity/trivy-operator/issues/327, I notice that the operator complains about missing RBAC permissions to list/watch secrets. So I am pretty convinced that the fix proposed and merged in https://github.com/aquasecurity/trivy-operator/pull/276 does not work. This PR reverts it, and https://github.com/aquasecurity/trivy-operator/issues/230 should be reopened.
W0715 08:11:25.882410       1 reflector.go:324] pkg/mod/k8s.io/client-go@v0.24.2/tools/cache/reflector.go:167: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:trivy-system:trivy-operator" cannot list resource "secrets" in API group "" at the cluster scope
E0715 08:11:25.882442       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.24.2/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:trivy-system:trivy-operator" cannot list resource "secrets" in API group "" at the cluster scope

Related issues

Reopen https://github.com/aquasecurity/trivy-operator/issues/230
Relates to https://github.com/aquasecurity/trivy-operator/issues/327

Checklist

[x] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[ ] I've updated the documentation with the relevant information (if needed).
[ ] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

hamm.... wonder why it not working should be pretty simple change

hamm.... wonder why it not working should be pretty simple change

I will ask the controller-runtime maintainers about this. Controller-runtime is a bit of complex software, so not always easy to find your way.

LGTM!

@chen-keinan Maybe you can reopen https://github.com/aquasecurity/trivy-operator/issues/230? I don't seem to have the permissions to do it.


caravel test fails

after copying caravel test directory to verilog/dv/ and running make
I first get this error:

then after copying params.v to includes dir I get this error:

Are you able to run it locally? how?

both images are the same
yes, I was able to run it locally, but maybe there is some problem with my paths.


Add a command to manually accept a token response.

This sets up a command triggered by clicking on the status indicator during auth. The command prompts for the token (really for the URI response), parses it as a URI, and dispatches it.
Fixes #570 #573

Ping for review on this? We're getting a lot of folks on Linux who can't use the protocol handler :/ #591

Ok, PTAL.


Ensure files are read with UTF-8 encoding by default

On Windows, simply running
$ bin/licensee LICENSE.md

resulted in
content_helper.rb:22: in `gsub!': incompatible encoding regexp match
(UTF-8 regexp with IBM437 string)

because both the input file and the license files (like "afl-3.0.txt"
which contains Unicode quotes) were read as IBM437-encoded strings. Fix
this by explicitly reading them as UTF-8 strings.

Makes sense. Thanks @sschuberth!


score of tournament participants is wrong in ranking tab

issue #671

merged, tested and deployed.

:+1:


Set up pending Naming cops

Configures Naming department cops which are pending in Rubocop 1.31.1
(There's just one cop and there are no current offenses, so it's just a matter of explicitly enabling it.)

Coverage remained the same at 91.99% when pulling 60f71a982b9de927aec7b9d2f74a9658a4bcd821 on jdc-pending-naming-cops-182027741 into a87f76051a8b011d223398155a58101e83f1e1e4 on master.

I'm merging this. It's a trivial change only in Rubocop configuration.


Update release gating documentation

TRT-1036
This documentation is quite old (still refers to build cop), this updates it to the latest guidelines from TRT for becoming a release informer or gating job.

/lgtm


Jump search

🛠 Issue (Number)

Issue no #408
👨💻 Changes proposed
Hey, @Kumar-laxmi I have added the Jump Search Algorithm in C++, C, Java, and Python. Please review my pr and merge it. Thank you!
✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

@Sanjanabharadwaj25 Kindly review this PR


Links to documentation section highlight previous section in right sidebar

Click https://chanzuckerberg.github.io/cryoet-data-portal/python-api.html#cryoet_data_portal.Dataset
Notice that the page is pre-scrolled to the Dataset section (this is desirable).
However, in the right sidebar, the Client section is highlighted.

I don't know if I can fix this, since this funcionality comes from sphinx-immaterial. But I will investigate at some point, thanks!


Cant host Local P2Pool after Core 12.0 update

Describe the issue
After updating to core wallet 12.0, can no longer host own node.
Can you reliably reproduce the issue?
Yes, it just doesn't work (Local P2Pool).
If so, please list the steps to reproduce below:

Fresh install of core wallet 12.0 and OCM 1.1.6.
Local P2Pool node gives error "Only one usage of each socket address (protocol/network address/port) is normally permitted" when toggled to Network 2.

Expected behaviour
Node should go from loading to running.
Actual behaviour
Status stays at loading.
Screenshots.

What version of bitcoin-core are you using?
12.0 (latest)
Machine specs:

OS: Windows 10
CPU: i7-3770
RAM: 16 GB
Disk size: 1TB
Disk Type (HD/SDD): SDD

Any extra information that might be useful in the debugging process.
OCM version 1.1.6. I can mine on other people nodes on network 2 no problem. Self node works fine on v11.X. When I open resmon.exe, it shows OCM is using ports 9181 and 9347 as expected.

Same issue. I've tried the one-click-miner and p2pool-vtc but it looks like p2pool is not compatible with the new wallet v12.0.
I've tried to launch the wallet v11.X instead but the v12.0 is already running (even when the app is closed it's running in the background) and it cannot "obtain a lock on data directory".
If anyone knows how to stop the v12.0 and run v11.0 or even better on how to run p2pool with the wallet v12.0 it would be great 👍

The latest p2pool-vtc works with Core 0.12, there are several nodes hosting it. This seems like an OCM specific issue.

Hi James, I disagree. Because if I roll back to 11.0 wallet, and change nothing on the miner, it works. How can you straight up close the ticket without even trying to resolve it? Typically tickets dont get closed until they are resolved and or the user is satusfied.
l went out of my way to try and provide feedback, write up the ticket and it is straight up dismissed. I am just trying to help make Vert a better product.
Also, I have 2 friends with the EXACT same issue. It will need to be fixed before it goes mainstream. I have seen multiple people ask about this in the tech support channel as well. We all ended up rolling back to 11.0 to "fix it".
After being stumped and unsuccessfully trying to help me troubleshoot, Jin (mod on Discord) asked me to write this ticket.
Good luck,
Discord Name - Ritzypoo

From: James Lovejoy<EMAIL_ADDRESS>Sent: Monday, December 18, 2017 3:55:49 PM
To: vertcoin/vertcoin
Cc: zstreet86; Author
Subject: Re: [vertcoin/vertcoin] Cant host Local P2Pool after Core 12.0 update (#18)
The latest p2pool-vtc works with Core 0.12, there are several nodes hosting it. This seems like an OCM specific issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvertcoin%2Fvertcoin%2Fissues%2F18%23issuecomment-352570120&data=02|01||74015ce9846d417725f608d546621b0b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636492309524696221&sdata=0IUX6mzXjfkZR2KuZCf043aBc6ahsvzoKmjHR3DJ7nY%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAg9i0zB_sHqAEwLOaDvjEyR845xAzy1Vks5tBt9lgaJpZM4RDC5x&data=02|01||74015ce9846d417725f608d546621b0b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636492309524696221&sdata=87EtmWwELMInIYW31q78vM4PaWCAsx5xu3nh8RAKnbs%3D&reserved=0.

OCM launches a version of P2Pool that is only compatible with 11.0.  That's why rolling back to 11 fixes your issue, and upgraded to 12 breaks it.
When OCM upgrades the P2Pool version to the latest pre-release, compatible with Wallet 12.0, OCM will then be able to start the node like you want.
Until then, you can manually launch a node but it's not nearly as easy as OCM makes it.  My recommendation would be to stay on 11.0 wallet until OCM updates.


Polymorphic input types

I'd like to go ahead and present this RFC for implementation, possibly early as it looks to have full support. Or, at the least, I'd like to get the discussion and ideas flowing for implementation in the future.
https://github.com/graphql/graphql-spec/blob/master/rfcs/InputUnion.md
This is particularly of interest in cases where you have an update mutation that has optional relational inputs. In this case, you have to support creating and updating for the relation. It's also the case for one:many relationships, if you wish to update relations within a parent mutation.
There are a number of other use cases that are also important. The above use case is one that we're finding to be very common and a continual frustration point with the API/schema.

This implementation would be very useful for API Platform (related issues: https://github.com/api-platform/core/issues/1964, https://github.com/api-platform/core/issues/3258).
Maybe it would be a way to enforce this long-awaiting feature.

We'll add it but it has to become a part of the spec first and implemented in the reference implementation (graphql-js).

It's worth noting that since this issue was created, the RFC has gone on a complete tangent from the original "accepted" solution. Instead of introducing a new directive called @oneOf that's only valid on input objects, they've decided to introduce a new syntax type prefix called tagged that functionally does the same thing (but is not backwards compatible and is unclear what it does just based on the name).
In my projects I've decided to embrace the @oneOf directive, since I can implement it locally without waiting for a library or syntax update, and ignore the concept of tagged since it's not likely to get into the official Spec for possibly another year or two.

The current rfc i could find on this is https://github.com/graphql/graphql-spec/pull/825 which moves back to a directive approach using oneOf instead of a new tagged type.

@zimzat did you make a custom directive of @oneOf that you can share?

@Roensby The implementation was limited to the directive declaration and a helper method to validate. I didn't build it into the library as an input validation rule because we only had half a dozen places it was used.
directive @oneOf on INPUT_OBJECT

    private function validateOneOf(array $args): void
    {
        if (count($args) !== 1) {
            throw new RequestError('@oneOf requires only one property to be set');
        }
    }

ICYMI this got merged into graphql-js three weeks ago https://github.com/graphql/graphql-js/pull/3513

I am not planning to work on this myself just now, but will happily accept pull requests that implement @oneOf like https://github.com/graphql/graphql-js/pull/3513. Please also incorporate https://github.com/graphql/graphql-js/pull/3937.

Hi there,
Is anyone planed to work on this feature?
If not, could you please provide some tips to help people to contribute?
Regards


feof and fgets issue on 5.4.2

Warning: feof() expects parameter 1 to be resource, bool given in /var/www/html/wp-content/plugins/static-html-output-plugin/plugin/WP2Static/SitePublisher.php on line 2
PHP Warning:  fgets() expects parameter 1 to be resource, bool given in /var/www/html/wp-content/plugins/static-html-output-plugin/plugin/WP2Static/SitePublisher.php on line 2
Generating appears to work, though slower than usual

Apologies i was on wordpress version. The lastest version from here gives the below:
PHP Warning:  fopen(/var/www/html/wp-content/uploads/WP2STATIC-FILES-TO-DEPLOY.txt): failed to open stream: No such file or directory in /var/www/html/wp-content/plugins/static-html-output-plugin/src/SitePublisher.php on line 268

Thanks for reporting @dltmurphy - luckily, we should have a new release going out to wordpress.org soon.
I should have been running my local WP on latest upcoming release, but was still on 5.4.1.
The latest changes I'm working on do away with those WP2STATIC* files in the uploads dir, so those issues may be removed when latest development branch is merged in, but I'll leave this issue open until sure.

Ah yes I saw you was working on using a database instead! Sounds much more efficient than the current method. Do you know roughly which week it'll be released?

Not sure (my go to response is https://wp2static.com/roadmap/), but I feel the hardest parts were cleared last night and I should be able to clear the 3 remaining open tasks on https://wp2static.com/roadmap/ tonight.
Will need to also check how things are looking from the WP_CLI commands side and test it out on a few real world sites. I'm itching to get my focus back to V7 development (https://github.com/WP2Static/wp2static), so the sooner I clear this the better.

@dltmurphy could you please try this build and see if you get any of the same issues? https://github.com/WP2Static/static-html-output-plugin/releases/tag/6.6.19

I'm n ot seeing an error on the command line now however it doesn't work. It generates in just over 15 minutes and the deployment says it's instant to Github Pages
sudo -u www-data -i -- wp statichtmloutput deploy --path='/var/w
ww/html'
Deploying static site
Deployed to: github in 00:00:00

When i do it from the UI it says successfully deployed but the export log shows the below for all URLs:
2020-06-15 21:07:03 	 cURL error:Failed to connect to dev.local port 443: Connection timed out
2020-06-15 21:07:03 	 BAD RESPONSE STATUS (0): /

@dltmurphy probably DeployCache from previous deploy - try Advanced Tab - Delete Deploy Cache, then it should take its time

sorry, the 443 issue - do you have HTTP basic authentication on the site? Is that input in the plugin's Crawl tab?

Okay I've just deleted the cache and set the deployment going again from the UI
No i don't have basic authentication enabled. The crawl log lists all my URLs (i think) and say the below:
Pending   /   Note: initial_crawl_list
Pending   /2020/   Note: initial_crawl_list
Pending   /2020/06/   Note: initial_crawl_list
Pending   /2020/06/03/   Note: initial_crawl_list
Pending   /about/   Note: initial_crawl_list

@dltmurphy if you refresh that log, have any changed to 200/400/other status?
If not, there's definitely something blocking the crawling....
in your Mac's /etc/hosts file do you have an entry for dev.local in there?

None changed, they are all saying pending still.
Yeah i have my hosts file set and it loads the website up correctly. I have a redirect to https within apache
If it helps, I'm using Windows 10 with the Windows Subsystem for Linux 2 running Ubuntu. Apache2, MariaDB and PHP 7.4. Wordpress 5.4.2 and letsencrypt for my SSL.

OK, I'd bet on the TLS/https setup. As it's on your local computer, I'd recommend turning it off, as little need, unless you're serving to other computers on your network/remotely from your machine.
Whilst the plugin should work with self-signed local certificates, it's going to be more pain than it's worth.

That was it. All issues resolved :)
I have lost the ability to publish into a sub directory though in the new version, is this on purpose?

@dltmurphy w00t! Glad that is sorted! I think there was some progress at some point to make it easier on local https, but I'll leave it down the priorities as shouldn't block anyone to disable it.
re subdir publishing, see: https://github.com/WP2Static/static-html-output-plugin/issues/96
it will still be available in a subdirectory, if you want to pipe it into other processes by using the ZIP deploy. the UI will show the folder location (still needs an update) but will be the same as zip, without the .zip

Sorry I meant a subdirectory on github deployment. I need to publish into the "public" folder within the github repo

ah, that.
whilst subdir for export URL should be supported (see some chat here: https://github.com/WP2Static/wp2static/issues/573)
I'm not sure about that for this version, as it's extra complexity when there's still a lot of work to get core functions working.
which kind of deploy are you doing for GitHub? ie, org or personal or project repo? hosting with your own domain or as a something.github.io?
I think you can still choose to use master, gh-pages branches or the public dir.
If the public dir is a must, it may be better to do Zip deploy and local git client (to commit to the public dir, this will also be faster than this Static HTML Output's GitHub deploy, which does 1 commit per file, which works, but isn't great).
In WP2Static, there's a new GitHub Add-on, which @bookwyrm is working on here: https://github.com/Red-Madrone-Solutions/wp2s-addon-github that may have/get options for the subdir vs branch static site deployment option when ready.
You may also be able to use a custom hook to move the files after export, such as this:  https://github.com/WP2Static/static-html-output-plugin/issues/96#issuecomment-644523577

I'm not sure about that for this version

meaning deployment subdirectory option

closing this issue for now, but can continue discussion here about subdirs


Git Integration for Identity Providers

Problem definition
Current way of introducing an update of the IDP, or adding new IDP to a particular environment is by doing that change manually through the management console. Most of the time same IDP configs mostly used across all tenants as well.
This is an error prone approach and make the configuration changes propagated through environments.
Preferred Solution
Having Identity Server capable of pulling IDP artifacts through its representation stored in a VCS like Github solve this. This will allow to automate configuration changes automatically propagated through different environments, with correct CI\CD pipelines and test suits in place, similar to SPs.
Retrieving the configuration updates can be done with both pull (periodic pulling), and push (with GitHub Webhook) models
Tasks

[ ] Remote fetch support for IS
[ ] VS Code extension to pull/push IDPs
[ ] VS code language server support to build adaptive authentication scripts
[ ] Rest API for remote fetch service
[ ] Add support for git hooks for GIT integration
[ ] Add GIT integration UI to the developer portal
[ ] Documentation

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Fix NextUI node tooltip to accommodate long image URLs.

NextUI has a fixed max-width for the node tooltip. This PR sets the size to be based on the space needed by the content.

thanks @ahmedalodhari
that crosses off one of the feedback points https://github.com/srl-labs/containerlab/discussions/818.


RuntimeError: dictionary changed size during iteration

from flask import Flask, jsonify, request
from flasgger import Swagger, SwaggerView
from marshmallow import Schema, fields
StudentData = {
1: {"name": "A", 'roll': 1, 'status': 'Pass'},
2: {"name": "B", 'roll': 2, 'status': 'Pass'},
3: {"name": "C", 'roll': 3, 'status': 'Pass'},
4: {"name": "D", 'roll': 4, 'status': 'Pass'},
5: {"name": "E", 'roll': 5, 'status': 'Pass'}
}
class Student(Schema):
roll = fields.Integer(required=True)
class StudentDetails(Schema):
name = fields.Str()
roll = fields.Str()
status = fields.Str()
class StudentView(SwaggerView):
definitions = {'Input': Student, 'Response': StudentDetails}
def post(self):
    '''
        parameters:
            schema:
                $ref: '#/definitions/Input'
        responses:
            200:
                schema:
                    $ref: '#/definitions/Response'
    '''
    request_data = request.json
    roll = request_data.get('roll')
    if roll in StudentData.keys():
        return jsonify(StudentData[roll])
    else:
        return jsonify("Sorry No Record Found...!")

app = Flask(name)
swagger = Swagger(app)
app.add_url_rule(
'/student',
view_func=StudentView.as_view('student'),
methods=['POST']
)
app.run(debug=True)
The above is my sample code, when I am executing this I am facing an issue as mention below:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1997, in call
return self.wsgi_app(environ, start_response)
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1985, in wsgi_app
response = self.handle_exception(e)
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1540, in handle_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.5/dist-packages/flask/_compat.py", line 33, in reraise
raise value
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1982, in wsgi_app
response = self.full_dispatch_request()
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1614, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1517, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/usr/local/lib/python3.5/dist-packages/flask/_compat.py", line 33, in reraise
raise value
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1612, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/local/lib/python3.5/dist-packages/flask/app.py", line 1598, in dispatch_request
return self.view_functionsrule.endpoint
File "/usr/local/lib/python3.5/dist-packages/flask/views.py", line 84, in view
return self.dispatch_request(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/flask/views.py", line 149, in dispatch_request
return meth(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/flasgger/base.py", line 125, in get
return jsonify(self.loader())
File "/usr/local/lib/python3.5/dist-packages/flasgger/base.py", line 348, in get_apispecs
doc_dir=self.config.get('doc_dir'))
File "/usr/local/lib/python3.5/dist-packages/flasgger/utils.py", line 126, in get_specs
convert_schemas(apispec_swag, apispec_definitions)
File "/usr/local/lib/python3.5/dist-packages/flasgger/marshmallow_apispec.py", line 101, in convert_schemas
v = convert_schemas(v, definitions)
File "/usr/local/lib/python3.5/dist-packages/flasgger/marshmallow_apispec.py", line 99, in convert_schemas
for k, v in d.items():
RuntimeError: dictionary changed size during iteration

Duplicates #236.


Question about notebook 7

Hi! Thanks for making this great learning resource for free. I was wondering, is there a reason in notebook #7 that you do c = consts.gather(-1, t) instead of c = consts[t], given that it seems like you're indexing into a 1-dimensional tensor of beta values?

Actually wait; I think becomes obvious later the notebook -- my bad


500 error with Google Auth, production.log - NoMethodError (undefined method `tr' for nil:NilClass

Hi, I tried login with Google Authentication after upgrade gcc, install redis, redmine_sidekiq, redmine_bots, redmine_2fa.
In installing redmine_sidekiq, I was modified sidekiq_sandbox_controller.rb from before_filter into before_action.
And in installing redmine_bots, modified Gemfile from gem 'database_cleaner', '1.5.1' into gem 'database_cleaner'.
And in installing redmine_2fa, I saw 500 error after log in by admin account and input Google Authentication code.
Here the Redmine production log as below.

Started POST "/redmine_2fa/otp_code/confirm" for xxx.xxx.xxx.xxx at 2020-09-14 18:46:37 +0900
Processing by AccountController#confirm_otp as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"Fe/RpT8W0CX9tEofhV9J2XeVek411fWl1yuKumm+AFZkOBioPOh0D/PMiieyFcwxuV37eu4dYe+nP4aq29iYfw==", "otp_code"=>"355684", "login"=>"Login »"}
   (0.4ms)  SELECT MAX("settings"."updated_on") FROM "settings"
  AnonymousUser Load (0.5ms)  SELECT  "users".* FROM "users" WHERE "users"."type" IN ('AnonymousUser') AND "users"."lastname" = $1 LIMIT $2  [["lastname", "Anonymous"], ["LIMIT", 1]]
  Current user: anonymous
  User Load (0.5ms)  SELECT  "users".* FROM "users" WHERE "users"."type" IN ('User', 'AnonymousUser') AND "users"."id" = $1 LIMIT $2  [["id", 1], ["LIMIT", 1]]
Completed 500 Internal Server Error in 6ms (ActiveRecord: 1.4ms)

NoMethodError (undefined method `tr' for nil:NilClass
Did you mean?  try):

plugins/redmine_2fa/lib/redmine_two_fa/patches/account_controller_patch/confirm_methods.rb:36:in `confirm_otp'
plugins/redmine_reporting/lib/redmine_reporting/sweeper.rb:23:in `around'
plugins/redmine_reporting/lib/redmine_reporting/sweeper.rb:23:in `around'
lib/redmine/sudo_mode.rb:65:in `sudo_mode'
plugins/redmine_dmsf/lib/redmine_dmsf/webdav/custom_middleware.rb:60:in `call'

I also tried install gem manually according to Gemfile, However that is not solution and same 500 error pop.

gem active_model_otp
gem rotp
gem rqrcode
gem shoulda
gem rails-controller-testing

Nevermind, I was fresh install Redmine and confirmed that the issue has been not occurred again.

The problem also happens to me, after tracing lib/redmine_two_fa/patches/account_controller_patch/confirm_methods.rb, vendor/bundle/ruby/2.6.0/gems/rotp-4.0.2/lib/rotp/otp.rb, vendor/bundle/ruby/2.6.0/gems/rotp-4.0.2/lib/rotp/totp.rb and vendor/bundle/ruby/2.6.0/bundler/gems/active_model_otp-6ed9927ac245/lib/active_model/one_time_password.rb.
I found that it is because that the following line is not executed when migration(I've checked the otp_secret_key column of users table, it is full of nil after migration):
https://github.com/southbridgeio/redmine_2fa/blob/2312a2067ee3af3deb168edc7a224de28fe9bede/db/migrate/003_add_otp_secret_key_to_users.rb#L8
After migration, I have to manually run the line above in rails console to resolve this problem.
My environment:
Environment:
  Redmine version                4.1.1.stable
  Ruby version                   2.6.5-p114 (2019-10-01) [x86_64-linux]
  Rails version                  <IP_ADDRESS>
  Environment                    production
  Database adapter               PostgreSQL
  Mailer queue                   ActiveJob::QueueAdapters::AsyncAdapter
  Mailer delivery                smtp

@funk-yourself Do you have any ideas?


si.services() shows wrong service status on Linux

Describe the bug
On a Linux system I have the following problem.
There used to be a service called "botBackend", it was checked. Meanwhile the service was deleted, but si.services('botBackend') still says "running:true".
This is because there is now a service called "botBackendM". So the full name is not compared.
If I terminate "botBackendM", then si.services('botBackend') also says running: false
To Reproduce
Steps to reproduce the behavior:

Select a service.
2 Query only a part of the name with si.services.

Expected behavior
When querying for "botBackend" running:false should appear. and only querying for "botBackendM" should result in a running:true.
Environment (please complete the following information):

systeminformation package version: 5.16.9
OS: Debian
Hardware: Server in MS Azure

@meepleschubser ... the reason for this was that some services added some additional information after the name ... will check it again and probably come up with a solution ...

Hi, any news on this one? :) I believe that i'm facing the same problem at the moment. When I'm filtering out the services depending on a string, then I'm getting "Running": "False" even when I know that they are up and running...

Hi,
Sorry for the long delay...
Im running this one:
		const computerComponents = {
			osInfo: "hostname, platform, release",
			cpu: "manufacturer, brand",
			cpuTemperature: "main, max, chipset",
			fsSize: "mount, size, used, use",
			services: "(*) name, running",
		};

let computerData = await si.get(computerComponents);

services: computerData.services.filter((service) => {
return service.name.startsWith("test_");
}),

And im having some services that are called test_123213312
And some of them are up and running but when I'm retrieving the data, then I'm getting "Not running" or "false".
Im running this on an Linux server.

@carlo98100 ... thank you! Would it be possible to run the exact code I posted above? And post the whole result? This would help a lot.

@sebhildebrandt Sorry I will not be able to do that since my project is secrecy marked... But I will try do describe it.
I have some services that are starting with the same name so "test_". When im doing my code above. Then im getting out all the services and I filter that list later on. But the problem is that all the services that im getting out from this says that running = false. But when im going in to the actual server that im runnning this on. Then its says "running".
This one is an ubuntu server.

Have you come any further on this one @sebhildebrandt? The reason I ask is because I'm using this for a current production solution. If the problem still is the commands, then I can check with my manager if we can solve it in some way.

@carlo98100 ... In fact, I have been putting off the problem for a while. Sorry. I will have a look at it in the coming days. In particular, I need to look again at why I implemented it this way. I'll have to run some tests on my various computers. Again, I apologize for the long wait.

Even with exact names, I now have some anomalies.
If I query all services, a service is displayed as running:false, if I ask specifically, it is started.
async function services() {     const s = await si.services('*');     console.log(s)     const s2 = await si.services('Test20_ccbackend');     console.log(s2)     const s3 = await si.services('test20_ccbackend');     console.log(s3) }
Result:
 {     name: 'Test20_ccbackend',     running: false,     startmode: '',     pids: [],     cpu: 0,     mem: 0   },   {     name: 'user-runtime-dir@0',     running: false,     startmode: '',     pids: [],     cpu: 0,     mem: 0   },   {     name: 'user@0',     running: false,     startmode: '',     pids: [],     cpu: 0,     mem: 0   } ] Test2 [   {     name: 'test20_ccbackend',     running: true,     startmode: '',     pids: [ 1915231 ],     cpu: 0.000389125580372123,     mem: 2.2   } ] Test3 [   {     name: 'test20_ccbackend',     running: true,     startmode: '',     pids: [ 1915231 ],     cpu: 0,     mem: 2.2   } ]

However, the way via ps does not seem to be so good. Now I have another service here that is displayed as running in systemctl status, but cannot be seen with the name in ps. So it cannot be displayed as running. That is a pity.
[
root@1 system]# systemctl status WebManager.service
● WebManager.service - WebManager app
Loaded: loaded (/etc/systemd/system/WebManager.service; enabled; vendor preset: disabled)
Active: active (exited) since Sat 2023-09-02 14:59:50 CEST; 2 months 0 days ago
Main PID: 13722 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/WebManager.service
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
[root@1 system]# ps -axo pcpu,pmem,pid,command | grep "WebManager"
0.0  0.0  9319 grep --color=auto WebManager

When running the below command
systemctl --all --type=service --no-legend | grep php
I see the services are active, but si.services() says it's not running. Any reason? Or its a bug? Below is lof of si.services('*')