How can I get transactionId in springboot application, not in log

How can I get transactionId in springboot application, like skywalking
import org.apache.skywalking.apm.toolkit.trace.TraceContext;

   @ResponseBody
    @PostMapping("/Hello")
    public FdMessageVO Hello(@RequestBody Map<String,String> param) throws IOException {
        String traceid = TraceContext.traceId();
       // insert into mysql
        return  fdMessageVo;
    }

I want to insert transactionId  to mysql

@ighack This PR #6801 might be what you want.

Maybe you need the SDK.
SDK PR is currently under development, but transactionId export function is not included.
https://github.com/pinpoint-apm/pinpoint/issues/7654
@yjqg6666
The design pattern of SDK PR seems like a very good idea.
A similar pattern seems to be possible with transactionid export.
What do you think?

@emeroad If possible, i would prefer to migrate this feature into the official SDK. It wouldn't be hard.

It would be so much better to get the transaction info from a stable api.

when will the sdk to be relased?

When will the SDK be released?

@ighack @ljgstudy @emeroad The feature is migrated to the PR #9175 branch. You could try it out.

Class.forName is very performance consuming, cache the result maybe better?

@yjqg6666 I have a question, why not use a plugin to enhancement the agent sdk to set the txid in, it may be more efficient

Class.forName is very performance consuming, cache the result maybe better?

@aalinyu Class.forName is called only 4 times per a request. According to this benchmarking, it may be not necessary.

Alternative
Non-invasive implementation that does not require SDK
The current implementation has a problem of high complexity across ClassLoader, ThreadLocal, and SDK.
Here are some ideas for this

ServletRequest.getAttribute() approach

public class Sample extends HttpServlet{

	protected void doGet(HttpServletRequest request, HttpServletResponse response) {
	       // This information is injected by the pinpoint interceptor
	        String transactionId = request.getAttribute("PINPOINT_TRANSACTIONID")
		Long spanId = request.getAttribute("PINPOINT_SPANID")
	}

}

Pros
Simple implementation.
Simple Object Lifecycle, Easy thread propagation. Most frameworks handle propagation of request object automatically.

public class HttpServletRequestAdaptor implements RequestAdaptor<HttpServletRequest> {
     @Override
     public void setAttribute(HttpServletRequest request, String name, Object o) {
          request.setAttribute(name, o);
      }
}

Cons
Some modules do not have setAttributes(). (grpc stream, reactive netty request....)
Solution? : A module without setAttribute() does not implement the feature.


tab bug

Issue Type: Bug
select all rows 。 ctrl + [   create bug;
VS Code version: Code 1.61.2 (6cba118ac49a1b88332f312a8f67186f7f3c1643, 2021-10-19T14:57:20.575Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

/gifPlease

Ctrl+[ is outdent line
Ctrl+] is indent line
Which are you trying to do?


fix: Make cluster_autoscaler mapping support k8s 1.28

Adds k8s 1.28 and the respective cluster_autoscaler image to the mapping
What does this PR do?

Resolves #272

Thanks for the PR!


Is dir cache coming to buck2?

In buck1 you could specify dir = <some local path> in your buckconfig, and it would use that as a local object cache.  It doesn't seem to be doing anything in buck2, despite being documented here.  Am I holding it wrong, and it's supposed to work?  Or will this be coming later?  Or is it not planned for buck2?

No, a cursory glance indicates that dir isn't supported in buck2; as usual I suspect the answer is "use a remote cache service" for those cases since it's a superset of functionality, anyway.
The docs you're linking to are actually the original buck1 docs, but in many (most?) cases do not apply at all to buck2. They're just stuffed under docs/legacy, as the URL indicates.
Frankly, the docs/legacy directory should, IMO, just be blown away and deleted, or at minimum not part of the built website, because then it will come up when using e.g. the search bar, and it's just misleading and confusing because most of the options not only don't apply, they don't even tell you they're invalid (after all, Starlark itself can use read_config)
See also #152 and #250

You could possibly glue https://github.com/allada/turbo-cache onto buck2 via using them both as libs in your own tool if you want functionality in the same binary. It might even be worth putting something like turbo-cache in buck2 behind a feature flag.

You could possibly glue https://github.com/allada/turbo-cache onto buck2 via using them both as libs in your own tool if you want functionality in the same binary. It might even be worth putting something like turbo-cache in buck2 behind a feature flag.

"Untested on Windows, but might work" rules it out for me.  I'd like something that supports all of the same platforms that buck2 supports with the same SLA, or at the very least the same process for submitting fixes upstream.  No word from the buck2 team yet, so I'll wait to draw any conclusions about the future here until they respond.

Also, turbo-cache unfortunately is only really available to use as a Bazel target, not as a Rust crate from https://crates.io — crates make integrating into buck2 a lot easier since Reindeer can generate rules for it, rather than porting the build rules or porting the codebase directly into here. Turbo cache does look pretty good though, aside from that...

I think there might be a vague plan to roll out a dir cache, but thus far it hasn't been required for anything we've done. It has some value, so I imagine eventually it will bubble its way up to the top.


Team password verification for registration is broken

As of right now, trying to send a payload to create a Player or Manager with the exact same string provided as team password fails with "Invalid password", despite the strings being completely equal.

Fixed with #97


Less crappy Chrome DevTools and Tools homepages

PTAL. All should be good.

Just the kbd thing then looks all good - thanks Paul.

LGTM just waiting on travis to confirm all is well.


Add opactl

I would like to add an open source tool opactl to the list. Hope it becomes some help for OPA community growth. Thank you.

Awesome, thanks! 👍


"File name is" messages in v5.70 for Linux RH 7.1

Reported by Andrew Wittenberg on 29 Jun 2004 21:56 UTC
Copious diagnostic messages scroll by in v5.70 for Linux RH7.1.
(They don't occur in v5.70 for Irix.)  Did some "verbose flag" get
left on by mistake?
    NOAA/PMEL TMAP
    FERRET v5.70
    Linux(g77) 2.4.18 - 06/25/04
    29-Jun-04 17:41

yes? set window 1
File name is ./default.spk
File name is /usr/local/ferret/ppl/default.spk
yes? use coads_climatology
File name is ./coads_climatology.cdf
File name is /usr/local/ferret/fer_dsets/data/coads_climatology.cdf
yes? shade/l=1 sst
yes? go fland
File name is ./fland.jnl
File name is /usr/local/ferret/go/fland.jnl
File name is ./etopo60.des
File name is /usr/local/ferret/fer_dsets/descr/etopo60.des
File name is ./etopo60.des
File name is /usr/local/ferret/fer_dsets/descr/etopo60.des
File name is ./etopo60.cdf
File name is /usr/local/ferret/fer_dsets/data/etopo60.cdf
File name is ./etopo60.cdf
File name is /usr/local/ferret/fer_dsets/data/etopo60.cdf
File name is ./etopo60.cdf
File name is /usr/local/ferret/fer_dsets/data/etopo60.cdf
File name is ./gray.spk
File name is /usr/local/ferret/ppl/gray.spk
yes?
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/911

Comment by<EMAIL_ADDRESS>on 30 Jun 2004 21:05 UTC
This was a stray debugging line, only in the build
of Rh7 at GFDL.  Fixed, and new executable has been
posted to the Downloads web page.


panic: failed to init GTK

Ran wails dev in repo with

Got error of

Machine~ Linux, 6.1.0-18-cloud-arm64

@shivamsouravjha Can you please check your wails installation using wails doctor? Also, Please check https://wails.io/docs/gettingstarted/installation installation page.

Seems like wails is installed right

@shivamsouravjha Seems like it's panic at this line.  There's a similar issue on wails repository too. https://github.com/wailsapp/wails/issues/3086


gparted: add mtools, dosfstools

the impact on closure size is 1M
adding mtools to base.nix adds 400K

Motivation for this change
Closes #146288
Closes #119177
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
21.11 Release Notes (or backporting 21.05 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

[x] Fits CONTRIBUTING.md.

@ofborg eval


feat: add precompile not supported event

Throw custom event when user tries to call unsupported precompile to allow for granular knowledge of what precompile users need most.
Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Resolves #372
What is the new behavior?

Other information

Time spent on this PR:  0.1d

Closing this as the current way to implement is incorrect.


fix gateway illumination sensor value

Description:
My earlier PR https://github.com/home-assistant/home-assistant/pull/10024 broke gateway illumination sensor when illumination value is 0. There were two conditions to check the illumination value. I think that one is enough.

Can we milestone this for 0.56.2?


Main function usable from any code

not tested, but it should be almost correct.
In this way, one can just call the execute function and run hypermax from code instead of cli

Little error found! Is it possible to update this pull request?

I think you just push additional commits and they will be added into the pull request automatically.

Tested both from cli and from code. From code, you can call hypermax.cli.execute

merged


[topgen] Support non memory-mapped module

Need to support IPs that don't have any memory port, bus_device in hjson is none or empty.

i don't quite follow.. what's an example of this?

The IP doesn't have TL-UL device port.
For instance, if AST module doesn't have TL-UL port and want to be
instantiated in the top_earlgrey (or subsystem), then current topgen
cannot handle it unless hacking the top_earlgrey.sv.tpl
On Fri, Apr 24, 2020 at 04:02:55PM -0700, tjaychen wrote:

i don't quite follow.. what's an example of this?
--
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub:
https://github.com/lowRISC/opentitan/issues/2064#issuecomment-619273492

Let me close this issue as AST will have TL-UL port.
Rather I will create an issue to support topgen/tlgen/reggen enabling Tl-UL port externally.


🤖 Android build failed: Gradle build failed with unknown error. Please see logs for the "Run gradlew" phase.

Summary
I was using expo build:android but after upgrading to eas-build It is showing me this error :
🤖 Android build failed:
Gradle build failed with unknown error. Please see logs for the "Run gradlew" phase.
Environment
{
  "name": "test-app",
  "version": "1.0.0",
  "type": "module",
  "scripts": {
    "start": "expo start --dev-client",
    "android": "expo run:android",
    "ios": "expo run:ios",
    "web": "expo start --web",
    "eject": "expo eject"
  },
  "dependencies": {
    "@react-native-community/netinfo": "8.2.0",
    "expo": "~45.0.0",
    "expo-asset": "~8.5.0",
    "expo-av": "~11.2.3",
    "expo-splash-screen": "~0.15.1",
    "expo-status-bar": "~1.3.0",
    "expo-system-ui": "~1.2.0",
    "expo-updates": "~0.13.2",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-native": "0.68.2",
    "react-native-video"<EMAIL_ADDRESS>    "react-native-web": "0.17.7",
    "react-native-webview": "11.18.1"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "metro": "^0.71.1"
  },
  "private": true
}

Please specify your device/emulator/simulator platform, model and version
ADB TV OS, Expo SDK
Error output
`Running './gradlew :app:bundleRelease' in /home/expo/workingdir/build/android
Downloading https://services.gradle.org/distributions/gradle-7.3.3-all.zip
10
%.
20
%.
30
%.
40%.
50
%.
60%.
70
%.
80
%.
90%.
100%
Welcome to Gradle 7.3.3!
Here are the highlights of this release:

Easily declare new test suites in Java projects
Support for Java 17
Support for Scala 3
For more details see https://docs.gradle.org/7.3.3/release-notes.html
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.3.3/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build
Unable to list file systems to check whether they can be watched. Assuming all file systems can be watched. Reason: Could not query file systems: could not open mount file (errno 2: No such file or directory)

Task :react-native-gradle-plugin:compileKotlin
'compileJava' task (current target is 1.8) and 'compileKotlin' task (current target is 11) jvm target compatibility should be set to the same Java version.
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (10, 37): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (119, 30): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (135, 26): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (155, 32): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (161, 31): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactExtension.kt: (169, 36): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/ReactPlugin.kt: (100, 48): 'reactRoot: DirectoryProperty' is deprecated. reactRoot was confusing and has been replace with rootto point to your root project and reactNativeDir to point to the folder of the react-native NPM package
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (10, 37): 'ApplicationVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (11, 37): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (12, 37): 'LibraryVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (28, 51): 'BaseVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (131, 12): 'ApplicationVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (132, 12): 'LibraryVariant' is deprecated. Deprecated in Java
w: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/TaskConfiguration.kt: (252, 14): 'BaseVariant' is deprecated. Deprecated in Java
Task :react-native-gradle-plugin:compileJava
[stderr]
Note: /home/expo/workingdir/build/node_modules/react-native-gradle-plugin/src/main/java/com/facebook/react/codegen/generator/SchemaJsonParser.java uses or overrides a deprecated API.
[stderr]
Note: Recompile with -Xlint:deprecation for details.
Task :react-native-gradle-plugin:pluginDescriptors
Task :react-native-gradle-plugin:processResources
Task :react-native-gradle-plugin:classes
Task :react-native-gradle-plugin:inspectClassesForKotlinIC
Task :react-native-gradle-plugin:jar
Configure project :app
Unable to detect AGP versions for included builds. All projects in the build should use the same AGP version. Class name for the included build object: org.gradle.composite.internal.DefaultIncludedBuild$IncludedBuildImpl_Decorated.
Configure project :expo-av
Checking the license for package NDK (Side by side) 21.4.7075529 in /home/expo/Android/Sdk/licenses
License for package NDK (Side by side) 21.4.7075529 accepted.
Preparing "Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)".
"Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)" ready.
Installing NDK (Side by side) 21.4.7075529 in /home/expo/Android/Sdk/ndk/21.4.7075529
"Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)" complete.
"Install NDK (Side by side) 21.4.7075529 (revision: 21.4.7075529)" finished.
Checking the license for package CMake <IP_ADDRESS>88404 in /home/expo/Android/Sdk/licenses
License for package CMake <IP_ADDRESS>88404 accepted.
Preparing "Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)".
"Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)" ready.
Installing CMake <IP_ADDRESS>88404 in /home/expo/Android/Sdk/cmake/<IP_ADDRESS>88404
"Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)" complete.
"Install CMake <IP_ADDRESS>88404 (revision: 3.10.2)" finished.
Configure project :expo-eas-client
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Configure project :expo-structured-headers
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Configure project :expo-updates-interface
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
Configure project :expo
Using expo modules

expo-application (4.1.0)
expo-av (11.2.3)
expo-constants (13.1.1)
expo-eas-client (0.2.1)
expo-error-recovery (3.1.0)
expo-file-system (14.0.0)
expo-font (10.1.0)
expo-json-utils (0.3.0)
expo-keep-awake (10.1.1)
expo-manifests (0.3.0)
expo-modules-core (0.9.2)
expo-splash-screen (0.15.1)
expo-structured-headers (2.2.1)
expo-system-ui (1.2.0)
expo-updates (0.13.2)
Checking the license for package Android SDK Build-Tools 30.0.2 in /home/expo/Android/Sdk/licenses
License for package Android SDK Build-Tools 30.0.2 accepted.
Preparing "Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)".
"Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)" ready.
Installing Android SDK Build-Tools 30.0.2 in /home/expo/Android/Sdk/build-tools/30.0.2
"Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)" complete.
"Install Android SDK Build-Tools 30.0.2 (revision: 30.0.2)" finished.
Checking the license for package Android SDK Platform 31 in /home/expo/Android/Sdk/licenses
License for package Android SDK Platform 31 accepted.
Preparing "Install Android SDK Platform 31 (revision: 1)".
"Install Android SDK Platform 31 (revision: 1)" ready.
Installing Android SDK Platform 31 in /home/expo/Android/Sdk/platforms/android-31
"Install Android SDK Platform 31 (revision: 1)" complete.
"Install Android SDK Platform 31 (revision: 1)" finished.
Checking the license for package Android SDK Build-Tools 31 in /home/expo/Android/Sdk/licenses
License for package Android SDK Build-Tools 31 accepted.
Preparing "Install Android SDK Build-Tools 31 (revision: 31.0.0)".
"Install Android SDK Build-Tools 31 (revision: 31.0.0)" ready.
Installing Android SDK Build-Tools 31 in /home/expo/Android/Sdk/build-tools/31.0.0
"Install Android SDK Build-Tools 31 (revision: 31.0.0)" complete.
"Install Android SDK Build-Tools 31 (revision: 31.0.0)" finished.

Task :app:generatePackageList
Task :app:preBuild
Task :app:preReleaseBuild
Task :app:bundleReleaseJsAndAssets FAILED
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/expo/workingdir/build/metro.config.js from /home/expo/workingdir/build/node_modules/import-fresh/index.js not supported.
metro.config.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
Instead rename metro.config.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in /home/expo/workingdir/build/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
[stderr]
error require() of ES Module /home/expo/workingdir/build/metro.config.js from /home/expo/workingdir/build/node_modules/import-fresh/index.js not supported.
[stderr]
metro.config.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
[stderr]
Instead rename metro.config.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in /home/expo/workingdir/build/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
at module.exports (/home/expo/workingdir/build/node_modules/import-fresh/index.js:28:9)
at loadJs (/home/expo/workingdir/build/node_modules/cosmiconfig/dist/loaders.js:9:18)
at Explorer.loadFileContent (/home/expo/workingdir/build/node_modules/cosmiconfig/dist/createExplorer.js:230:12)
at /home/expo/workingdir/build/node_modules/cosmiconfig/dist/createExplorer.js:252:21
info Run CLI with --verbose flag for more details.
[stderr]
FAILURE: Build failed with an exception.
[stderr]

What went wrong:
[stderr]
Execution failed for task ':app:bundleReleaseJsAndAssets'.
[stderr]

Process 'command 'node'' finished with non-zero exit value 1
[stderr]

Try:
[stderr]

Run with --stacktrace option to get the stack trace.
[stderr]
Run with --info or --debug
[stderr]
option to get more log output.
[stderr]
Run with --scan to get full insights.
[stderr]

Get more help at https://help.gradle.org
[stderr]
BUILD FAILED in 3m 44s
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
8 actionable tasks: 8 executed
Unable to list file systems to check whether they can be watched. The whole state of the virtual file system has been discarded. Reason: Could not query file systems: could not open mount file (errno 2: No such file or directory)
Error: Gradle build failed with unknown error. Please see logs for the "Run gradlew" phase.`

Reproducible demo or steps to reproduce from a blank project
`import { StyleSheet, View, Dimensions, Text } from 'react-native';
import appData from "./data.json"
import NetInfo from "@react-native-community/netinfo"
import React, { Component } from 'react';
import * as Updates from "expo-updates"
import * as SplashScreen from 'expo-splash-screen';
import {Asset} from "expo-asset"
import { Video } from 'expo-av';
var i=0
const data = appData
const {width, height} = Dimensions.get("screen")
export default class App extends Component {
constructor(props){
super(props);
this.state = {
conn_status: "",
playlist: data,
}
/*     this.prepare()
this.InternetChecker()
this.reactToUpdates() /
}
cacheResources = async () => {
var videosA = data[0].src
var dataCached = []
var videosB = data[1].src
var videosC = data[2].src
console.log(videosA)
console.log(videosB)
console.log(videosC)
const cacheVideosA = Asset.fromModule(videosA).downloadAsync()
dataCached.push(cacheVideosA)
const cacheVideosB = Asset.fromModule(videosB).downloadAsync()
dataCached.push(cacheVideosB)
const cacheVideosC = Asset.fromModule(videosC).downloadAsync()
dataCached.push(cacheVideosC)
console.log(dataCached)
/ videos.map(video => {
return Asset.fromModule(video).downloadAsync()
}) */
return Promise.all(dataCached)
}
componentDidMount = () => {
loadResource = async () => {
await this.cacheResources()
await this.prepare()
await this.InternetChecker()
await this.reactToUpdates()
}
loadResource()
}
reactToUpdates = async () => {
Updates.addListener((e)=>{
if (e.type === Updates.UpdateEventType.UPDATE_AVAILABLE) {
Updates.reloadAsync()
}
})
}
prepare = async () => {
try {
await SplashScreen.preventAutoHideAsync();
await new Promise(resolve => setTimeout(resolve, 3000));
} catch (e) {
console.warn(e);
} finally {
SplashScreen.hideAsync();
}
}
InternetChecker = async () => {
await NetInfo.fetch().then( state => {
console.log("Connection Type", state.type)
console.log("Is connected?", state.isConnected)
if(state.isConnected === true){
this.setState({
conn_status: "online"
})
} else {
this.setState({
conn_status: "offline"
})
}
})
}
videoUpdated(playbackStatus){
if(playbackStatus['didJustFinish']){
console.log(this.state.playlist[i].name+" just finished",Date().toLocaleString(),i);
this.playNext();
}
}
playNext(){
let playlist = this.state.playlist;
let temp = playlist[0];
playlist.shift();
playlist.push(temp);
this.setState({playlist,})
this.InternetChecker()
}
render() {
if(this.state.conn_status === "online"){
return (

<Video
onPlaybackStatusUpdate={(playbackStatus)=> this.videoUpdated(playbackStatus)}
resizeMode="contain"
source={{uri: this.state.playlist[0].src}}
useNativeControls = {false}
rate={1.0}
shouldPlay
autoPlay
volume={1.0}
muted={false}
style={{height:height,width:width}}
/>

);
} else {
return(

<Video
resizeMode="contain"
source={require("./assets/offline.mp4")}
useNativeControls = {false}
rate={1.0}
shouldPlay
autoPlay
isLooping
volume={1.0}
muted={false}
style={{height:height,width:width}} />

)
}
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: '#fff',
alignItems: 'center',
justifyContent: 'center',
},
});
`

I have the same problem

I've also the same problem, and still unable to resolve it.
Please help!

Any update on this?

I used this json.
{
"name": "highway-app",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web",
"eject": "expo eject"
},
"dependencies": {
"@eliav2/react-native-collapsible-view": "^1.4.0",
"@expo/vector-icons": "^13.0.0",
"@react-native-async-storage/async-storage": "~1.17.3",
"@react-native-community/datetimepicker": "6.5.2",
"@react-native-community/netinfo": "9.3.5",
"@react-native-picker/picker": "2.4.8",
"@react-navigation/bottom-tabs": "^6.3.1",
"@react-navigation/drawer": "^6.2.0",
"@react-navigation/native": "^6.0.7",
"@react-navigation/stack": "^6.0.11",
"expo": "^47.0.3",
"expo-app-loading": "~2.1.1",
"expo-camera": "~13.1.0",
"expo-font": "~11.0.1",
"expo-image-manipulator": "~11.0.0",
"expo-image-picker": "~14.0.2",
"expo-location": "~15.0.1",
"expo-permissions": "~14.0.0",
"expo-secure-store": "~12.0.0",
"expo-status-bar": "~1.4.2",
"formik": "^2.2.9",
"install": "^0.13.0",
"pusher-chatkit-gifted-chat": "^1.0.19",
"pusher-js": "^7.1.1-beta",
"react": "18.1.0",
"react-dom": "18.1.0",
"react-hook-form": "^7.28.1",
"react-native": "^0.70.5",
"react-native-chart-kit": "^6.11.0",
"react-native-dropdown-picker": "^5.3.0",
"react-native-form-validator": "^0.1.3",
"react-native-gesture-handler": "~2.8.0",
"react-native-gifted-chat": "^1.0.2",
"react-native-maps": "1.3.2",
"react-native-modern-datepicker": "^1.0.0-beta.91",
"react-native-range-slider-expo": "^1.4.2",
"react-native-ratings": "^8.1.0",
"react-native-reanimated": "^2.12.0",
"react-native-safe-area-context": "4.4.1",
"react-native-storage": "^0.2.4",
"react-native-svg": "13.4.0",
"react-native-web": "~0.18.9",
"react-redux": "^7.2.6",
"redux": "^4.1.2",
"redux-thunk": "^2.4.1",
"yup": "^0.32.11"
},
"devDependencies": {
"@babel/core": "^7.12.9",
"@types/react-native": "~0.64.12",
"typescript": "~4.3.5"
},
"private": true
}
then build was created successfully!

I have the same problem.

I've also the same problem, and still unable to resolve it.
Please help!

any update bro? I've same issue 🤓

Some one please reply on this i am also struggling with this error

Having the same problem. Any solution yet ??

Probably dependencies versioning incompatibility
Try run
expo doctor expo doctor --fix-dependencies
then try to rebuild

not working for me bro.

Some one please reply on this i am also struggling with this error

still error dude? any solution ?

hey there, check out the guide for troubleshooting build errors: https://docs.expo.dev/build-reference/troubleshooting/
at the bottom of the page there is more information on how to ask a good question after you've followed the guide if you're still stuck: https://docs.expo.dev/build-reference/troubleshooting/#how-to-ask-a-good-question

delete some error package in package.json and re export file png, I don't know why I had to remove the "react-native-navigation" but it worked
[stderr] FAILURE: Build completed with 2 failures. [stderr] 1: Task failed with an exception. [stderr] ----------- [stderr] * Where: [stderr] Build file '/home/expo/workingdir/build/node_modules/react-native-navigation/lib/android/app/build.gradle' line: 5 [stderr] * What went wrong:
[stderr] > Multiple task action failures occurred:
[stderr]    > A failure occurred while executing com.android.build.gradle.internal.res.Aapt2CompileRunnable
[stderr]       > Android resource compilation failed
[stderr]         ERROR:/home/expo/workingdir/build/android/app/build/generated/res/react/release/drawable-mdpi/assets_user.png: AAPT: error: file failed to compile.

I keep trying this error any help I've followed all the guidelines and I'm still with the same error

I also have the same problem. It appeared after installing the react-native-orientation package. After removing this package, the problem disappeared. If I can find solutions without removing the package, I will let you know

I don't have this lib in my project, does anyone know how to use the expo key to set in build.graldew to build with ./gradlew buindRelease?

i had a problem with react-native-navigation, i uninstall and installed again, it worked. But now i had the same problem and it doesn't worked.

i had a problem with react-native-navigation, i uninstall and installed again, it worked. But now i had the same problem and it doesn't worked.

I went to package.json and deleted react-native-navigation. Thats work for me

My package.json -->
{
"name": "misapp",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web",
"eject": "expo eject"
},
"dependencies": {
"@react-native-community/datetimepicker": "6.5.2",
"@react-native-picker/picker": "^2.4.8",
"@react-navigation/native": "^6.0.2",
"@react-navigation/native-stack": "^6.1.0",
"axios": "^0.26.1",
"bd-geojs": "^1.0.0",
"expo": "^47.0.13",
"expo-status-bar": "~1.4.2",
"expo-updates": "~0.15.6",
"firebase": "^8.10.1",
"react": "18.1.0",
"react-dom": "18.1.0",
"react-native": "0.70.5",
"react-native-modern-datepicker": "^1.0.0-beta.91",
"react-native-paper": "^4.9.2",
"react-native-safe-area-context": "4.4.1",
"react-native-screens": "~3.18.0",
"react-native-shadow-cards": "^1.0.2",
"react-native-web": "~0.18.7"
},
"devDependencies": {
"@babel/core": "^7.19.3"
},
"private": true
}
Getting same error, please help me.

same issue, i think this issue is due to, "react-native-webview"

@umang752 Did you ever find a solution? currently using webview on our app and would like to continue to use it.

can you show us the error log?

Please help i am also stuck at this build error  Execution failed for task ':app:compileReleaseJavaWithJavac'.

this error happens.
1 - or your Expo is in version <=45 minor versions and are obsolete, the way to solve my problem was to compile it by react-native even with the command that is in react-native documentation, if it is just expo Eject it and use react-native's native template.

I tried creating build using eas build --platform android in a fresh expo project and it works perfectly fine.
As soon as I installed and used react-navigation packages, I see this  Gradle build failed error:
🤖 Android build failed:
Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

So there must be something wrong/compatibility issues with the react-navigation packages. Stuck on this for few weeks now. Any help is appriciated.

Please help i am also stuck at this build error Execution failed for task ':app:compileReleaseJavaWithJavac'.

I solve this by removing expo-cli after I upgraded to expo SDK 48.
as per the documentation, expo-cli is now part of SDK 48 internally I guess

Я решаю эту проблему, удалив expo-cli после обновления до expo SDK 48. Согласно документации, expo-cli теперь является внутренней частью SDK 48, я думаю.

Thanks a lot, it worked for me!

Fixed this by creating a new file .npmrc in project folder then, setting ‘legacy-peer-deps=true’ and also run ‘npm config set legacy-peer-deps true’ in terminal

Thank you yes your solution is worked for me thank  you so much dear

i have updated my expo version from 48 to 49 and after i am
getting error in building in my ternimal
like below

✖ Build failed

🤖 Android build failed:
Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

i need help if anyone resolve it so please give me response.
and my package.json is below
  "dependencies": {<EMAIL_ADDRESS>"^1.0.2"<EMAIL_ADDRESS>"^1.0.0",     "@expo/vector-icons": "^13.0.0",     "@fortawesome/fontawesome-svg-core": "^1.3.0",     "@fortawesome/free-brands-svg-icons": "^6.0.0",     "@fortawesome/free-regular-svg-icons": "^6.0.0",     "@fortawesome/free-solid-svg-icons": "^6.0.0",     "@fortawesome/react-fontawesome": "^0.1.17",     "@fortawesome/react-native-fontawesome": "^0.3.0",     "@native-html/iframe-plugin": "^2.6.1",     "@react-native-async-storage/async-storage": "1.18.2",     "@react-native-community/datetimepicker": "7.2.0",     "@react-navigation/bottom-tabs": "^6.5.2",     "@react-navigation/drawer": "^6.6.2",     "@react-navigation/native": "^6.0.2",     "@react-navigation/stack": "^6.0.7",     "@shopify/flash-list": "1.4.3",     "@tanstack/react-query": "^4.19.1",     "@types/react": "~18.2.14",     "dayjs": "^1.11.5",     "expo": "49",     "expo-apple-authentication": "~6.1.0",     "expo-application": "~5.3.0",     "expo-asset": "~8.10.1",     "expo-auth-session": "~5.0.2",     "expo-build-properties": "~0.8.3",     "expo-constants": "~14.4.2",     "expo-dev-client": "~2.4.12",     "expo-file-system": "~15.4.5",     "expo-font": "~11.4.0",     "expo-image-picker": "~14.3.2",     "expo-linking": "~5.0.2",     "expo-media-library": "~15.4.1",     "expo-navigation-bar": "~2.3.0",     "expo-random": "~13.2.0",     "expo-secure-store": "~12.3.1",     "expo-sharing": "~11.5.0",     "expo-splash-screen": "~0.20.5",     "expo-status-bar": "~1.6.0",     "expo-updates": "~0.18.19",     "firebase": "^9.15.0",     "lodash": "^4.17.21",     "node-fetch": "2.6.1",     "prop-types": "^15.7.2",     "expo-web-browser": "~12.3.2",     "randombytes": "^2.1.0",     "react": "18.2.0",     "react-dom": "18.2.0",     "react-hook-form": "^7.40.0",     "react-merge-refs": "^1.1.0",     "react-native": "0.72.6",     "react-native-calendars": "^1.1293.0",     "react-native-check-version": "^1.1.1",     "react-native-crypto": "^2.2.0",     "react-native-device-info": "^10.6.0",     "react-native-draggable-flatlist": "^4.0.1",     "react-native-draglist": "^3.4.0",     "react-native-gesture-handler": "~2.12.0",     "react-native-get-random-values": "~1.9.0",     "react-native-image-viewing": "^0.2.2",     "react-native-indicators": "^0.17.0",     "react-native-keyboard-aware-scroll-view": "^0.9.5",     "react-native-modalize": "^2.1.1",     "react-native-popup-menu": "^0.15.12",     "react-native-portalize": "^1.0.7",     "react-native-progress": "^5.0.0",     "react-native-purchases": "^7.3.0",     "react-native-reanimated": "~3.3.0",     "react-native-reanimated-carousel": "^3.3.0",     "react-native-render-html": "^6.3.4",     "react-native-safe-area-context": "4.6.3",     "react-native-screens": "~3.22.0",     "react-native-shadow-2": "^7.0.6",     "react-native-svg": "13.9.0",     "react-native-swipeable-item": "^2.0.9",     "react-native-toast-message": "^2.1.5",     "react-native-url-polyfill": "^1.3.0",     "react-native-web": "~0.19.6",     "react-native-webview": "^11.6.2",     "typescript": "^5.1.6",     "uuid": "^8.3.2",     "wpapi": "^1.2.2"   },

same issue, i think this issue is due to, "react-native-webview"

i have used webview in my project,i think your right
if you get solution please share with me.

same issue, i think this issue is due to, "react-native-webview"

I have used Webview in my project, i think you are right if you get a solution please share it with me.

I am facing similar issue have you found any solution?

same issue, i think this issue is due to, "react-native-webview"

I have used Webview in my project, i think you are right if you get a solution please share it with me.

I am facing similar issue have you found any solution?

Yes i got solution
Please check you build log existing any library name
i have resolve it
if anyone facing issue same like me so please check your expo dashboard error log and try to find library name and install library
in my case i have install
"expo-modules-autolinking": "1.2.0",

remove all unnessary packages then try npx expo-doctor and try  npx expo install --check

hey, my problem is solved my making solve the logs error... suppose incompatiblity  check expo doctor then , other errorr  will definetely solve this problem


Follow HTTP redirects after failed WS dials

This commit allows the opamp client to follow redirects after websocket handshake failures. Redirect following is not implemented by gorilla/websocket, but can be handled by inspecting the returned response object for 3xx status and Location header.
Closes #250

Thank you for the PR @echlebek
Please sign the CLA.

@tigrannajaryan Thanks for taking a look, I've signed the CLA.

Coverage is now improved, with only one line missing coverage from the method. It would require a TLS server in test to cover it. Let me know if you think it's worthwhile. Thanks!

Thank you @echlebek !


[ENHANCEMENT] Let challenger know they submit the wrong language or file

When a submission fails, let them know if they selected the wrong language or file if they do not match

If it can detect if a file isn't the correct language, why don't we just auto-detect the language in the first place?

Correction on title: have a message for when their submission fails that to check their syntax & selected language matches their file.


Mhd import fail: Failed to create asset

First of all, thank you very much for this plugin and the repo! I've been playing around with it all day, saw the tutorial on youtube and wanted to give it a try with some testfiles.
I opened your existing project, recompiled it. Not using the plugin in my own project, yet.
For testing some other content than your demo content (MHD_70), I loaded some dicom sample files and converted them to mhd using ImageJ, specifically this build: https://imagej.net/Fiji
I used "open image sequence" and then selected the a dicom file, and then "save as.." and selected mhd.
Here are the dicom sample files I used:
https://www.visus.com/fileadmin/content/pictures/Downloads/JiveX_DICOME_Viewer/democases.zip
I can re-open the generated mhd  in imageJ just fine, but when I try to drag & drop the mhd file into my content browser with your project open, I get:
Failed to import 'case2.mhd'. Failed to create asset '/Game/DefaultResources/case2'. Please see Output Log for details.
Output log, however, is empty. I am also not able to load mhd files with your provided In-Game-GUI, when I click load normalized  or Load F32, and select a mhd file, just nothing happens.
I can only guess imageJ converts the dicom files to some form of mhd, which this plugin does not like and cannot parse. I don't know what goes wrong, though, because as said, the Output Log does not show any additional errors.
Any advice is highly appreciated. Thanks!

Thanks for the heads-up, I'll check it out tomorrow when I get to my workstation. Honestly, the MHD parser isn't very robust, so it's probably some MHD tag I ignore and it's important.
If you could upload the generated .mhd header for me, that would be jolly good.

wow, that was quick!
Sure thing, please find the demo mhd attached as a zip (mhd + raw inside zip).
democases.zip
let me know if you need anything else, screenshare, coffee, beer, etc.

Open the .mhd in notepad and try replacing "ElementSize" with "ElementSpacing" and see what happens.

Thanks for the head-up. That works - kind of. It now loads, both via drag & drop and also with the GUI, but the file itself seems to be all messedd-up and not readable / useful, as everything is just plain black.

so it is definitely a problem with the "wrong" mhd file format, we just have to figure out how to provide useful and "good" mhd files for the plugin to be processed.

Aight, will take a look at it tomorrow after work :) My first guess would be little/big endian issue, since I just flat-out ignore that MHD tag in my reader 😁

Awesome! Thank you so much for looking into this!

Just as an update, I made some progress and I am sometimes at least able to open some mhd files. In essence, the mhd loader seems to be quite squeamish on what you throw at it. The window and width sliders actually don't work with any file that I tried.
I am not quite sure what to file as a bug here, but I guess the bottomline is, that the mhd loader needs a lot of real-world testing with different files from different sources.
What I did was to google dicom sample files from various places, with this as a starting point:
https://talk.openmrs.org/t/sources-for-sample-dicom-images/6019
I then converted the dcom files with Fiji ( https://imagej.net/Fiji ):
Import -> Image Sequence ->
then
save as... -> mhd. Be sure to manually add "mhd" to the filename as a file extension, then imageJ will create the .mhd header file and .raw file for you! You can also open these files in imageJ just fine and it will then show a slider to "march" through the image layers.
To be able to open these files in your plugin, I have been replacing "ElementSize" with "ElementSpacing" in the .mhd header file like you said, and when I then try to throw it at Unreal Engine Content Editor, the results vary from:

does not open at all
opens, but is all black
opens, but is red/black checkerboard / unusable
crashes Unreal Engine
opens and looks good if you don't move anything, but we cannot adjust the sliders, because as soon as we touch them, UE crashes or the framerate drops to 1 fps.

Hope this helps you and everyone else who is reading tis in the future as a starting point.
I can provide you with some dicom and also converted mhd files to play around with but basically it boils down to the fact that some do open, some do not, and I was definitely completely out of luck on doing any width or window adjustments on the files that DO work, as it crashes the plugin almost instantly and ranges of the sliders are crazy high / low / nonsenical.
Let me know if you need additional input or files to play around and/or test with!

Heya again, finally got around to taking a look at this. I did find a bug in the MHD factory where I wasn't properly setting up the bNormalized flag, which resulted in the sliders screwing up.
Also found and fixed a bug that I didn't label a member UPROPERTY, so it got garbage collected and caused a crash when loading a new MHD file.
Other than that, I tried importing like 3 different dicom files converted to MHD through Fiji and all of them worked fine, pls share with me the ones that don't work and I'll take a look.
I'm not gonna spend too much time fixing the MHD reader though, as the real solution to this is a proper DICOM reader using some 3rd party library, I'll work in the coming weeks to abstract away the MHD-related stuff and make the volumes more generic (not specifically MHD or DICOM).

Thank you so much! I will take a look at your changes, make some tests and also make sure that you can get a hold of any mhd files which then still might not be working.
I agree that the mhd loader is not a final solution but a step in between, and that something like a wrapper for pydicom would be the way to go, although Unreal Engine can be really trricky when it comes to wrappers and third party libraries.
I'll keep you posted!

Sorry for the delay. The import works fine now and I had more issues thus far. Great job! issue can be closed :-)

Sorry for the delay. The import works fine now and I had more issues thus far. Great job! issue can be closed :-)

@nicolaskopp From this discussion it was unclear what the necessary steps were to create a mhd file that was readable by this plugin. Could you elaborate?
For example, your democase still provides the same strange red imagery as before. Any tips would be great as I am having the same difficulties importing mhd files. Thanks.

@nicolaskopp From this discussion it was unclear what the necessary steps were to create a mhd file that was readable by this plugin. Could you elaborate?
For example, your democase still provides the same strange red imagery as before. Any tips would be great as I am having the same difficulties importing mhd files. Thanks.

The "strange red imagery" is to be expected when importing without normalization.
Do the volumes look corrupted in the viewport? Upload me the files and I can try.

The "strange red imagery" is to be expected when importing without normalization.
Do the volumes look corrupted in the viewport? Upload me the files and I can try.

When I attempt to bring in the .mhd file I created (using ParaView), the created volume texture is just black if I select "No" on the mhd import prompt regarding G8/G16. If I select "Yes" UE crashes.
Here is the current file I'm using to test. It loads into Slicer just fine it seems.
https://www.dropbox.com/s/yzw7miksz89up4p/test.zip?dl=0

When I attempt to bring in the .mhd file I created (using ParaView), the created volume texture is just black if I select "No" on the mhd import prompt regarding G8/G16. If I select "Yes" UE crashes.
Here is the current file I'm using to test. It loads into Slicer just fine it seems.
https://www.dropbox.com/s/yzw7miksz89up4p/test.zip?dl=0

The generated .mhd file is compressed, I have no idea how to handle that.
Try creating it uncompressed somehow.

The generated .mhd file is compressed, I have no idea how to handle that.
Try creating it uncompressed somehow.

So, I hacked in support for compressed .mhd files, but your file being black is not a huge surprise - the values are extremely close to zero. The windowing parameters need to be very, very close to zero to see anything.
Try importing it now and setting these settings in the generated MHDAsset.

So, I hacked in support for compressed .mhd files, but your file being black is not a huge surprise - the values are extremely close to zero. The windowing parameters need to be very, very close to zero to see anything.
Try importing it now and setting these settings in the generated MHDAsset.

What data is that? Looks wonky :)
And this TF + Windowing params look good with it :)

What data is that? Looks wonky :)
And this TF + Windowing params look good with it :)

Excellent! Thanks a bunch. Looks like I definitely need to do some pre-scaling on the data, but that isn't a problem. Thank you very much for working your magic. Haha, yea... the data isn't biomedical imagery. Playing around in some other fields :) Again, thank you thank you thank you.

Excellent! Thanks a bunch. Looks like I definitely need to do some pre-scaling on the data, but that isn't a problem. Thank you very much for working your magic. Haha, yea... the data isn't biomedical imagery. Playing around in some other fields :) Again, thank you thank you thank you.


bug-fix/make-arangosearch-tests-deterministic

Scope & Purpose
Adjust some arangosearch tests to be more deterministic

[x] :hankey: Bugfix (requires CHANGELOG entry)
[ ] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[ ] No backports required
[ ] Backports required for: (Please specify versions and link PRs)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket number:
[ ] Design document:

Testing & Verification
(Please pick either of the following options)

[ ] This change is a trivial rework / code cleanup without any test coverage.
[ ] The behavior in this PR was manually tested
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run:
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13203/
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

External contributors / CLA Note
Please note that for legal reasons we require you to sign the Contributor Agreement
before we can accept your pull requests.

tests blue


Facilities, OS, and Plans should be fetched via API, not hardcoded

At the moment, this driver requires entirely too much handholding to keep up with Packet's continuous improvements. They provide an API for fetching the information currently hardcoded into the driver, so why aren't we using it?

completely agree.  @crunchywelch @mmlb looping you in.

Yeah there's no reason for not doing it that way, I think so far it's just been easier to add a facility vs reworking the code to be dynamic. PR welcome!

Fixed, closing it.


Add "events" container to firewall config unit tests

This is a follow-up to:
https://github.com/openshift/ingress-node-firewall/pull/123

Nice while you are here let’s add the initContainer too to ut

Done in https://github.com/openshift/ingress-node-firewall/compare/f7defac63446db3c3fb13528d7cac10110c8c9df..c3372714c7382673aaa25572102f07151c8341f3.

/hold

/hold cancel

/lgtm
/approve


Feat: Adding hover to social icons on all webpages

Describe the feature
It looks more good if social icons are given hover and transition effects . It will make it more user-friendly.
Add ScreenShots
https://github.com/mdazfar2/HelpOps-Hub/assets/162733812/f58540aa-e6e1-425e-b268-c8044b0d1146
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@mdazfar2 I want to work on this issue ,kindly assign it to me .

Hi @Maana-Ajmera, We can skip the hover effect on the footer for now.


Label float on auto fill

Fix for issue #7

@cymen Can you please review it?

I apologize for the slow review -- thanks for pinging me again as I missed the first notification. I have released this as 4.3.1.
Thanks!


Installation

Hello, can someone please guide me on how to install it? I downloaded Python and installed it where I wanted it to be then I ran the installer.bat and it downloaded some stuff and that's it, how can I find the launcher and any other files and where are the rest of the bot files on the thread for me to download, I'm new to this sorry.

latest release: launcher.bat in root directory; resources in resources folder, scripts in scripts folder
source version: main.pyw in root directory; resources in app/resources folder, scripts in app/bot and app/common folders, gui in app/gui folder

If you download the latest release you will have the launcher.bat, if you clone the repo you just need to double click on main.pyw

I downloaded the latest release file which is v1.3.2 and extracted it in the Python file and whenever I click on the launcher it says Python not found press any key to continue then it closes the window right after

are you sure that you checked the button that says "add to path"?

There is now a .exe that you can simply download and run without python or any dependencies. @CarouselV


Question about the Qualatitive Results

Hi, I have used the BFmathcer in evaluation code to draw matched points between image pair, but I got some worse matching result compare to the qualatitive results in the README.md. I wander is there some post-processing procedure I missed?

Hi - could you maybe check that you get the same quantitative results as we reported? I don't think we used any additional filtering or post-processing on the matches.


Analyzer assigns incorrect exact type to set literals

According to https://github.com/dart-lang/language/blob/master/accepted/future-releases/set-literals/feature-specification.md, under the heading "Exact Types of Literals":

Currently, the Dart 2 type inference infers an "exact type" for map literals, either Map<K, V> for const literals or LinkedHashMap<K, V> for non-constant literals. The inferred exact type makes it a compile-time error to require a down-cast, since that down-cast is known to fail at runtime. For set literals with element type T, the static type is always Set<T>, but static analysis will reject an assignment of a non-constant set literal to a type that is not a super-type of LinkedHashSet<T> (an implicit down-cast below the type LinkedHashSet<T>), and of a constant set literal to a type that is not a super-type of Set<T> (that is, any implicit down-cast).

I believe this implies the following behaviors:
import 'dart:collection';
abstract class C<T> implements LinkedHashSet<T> {}

LinkedHashSet<Null> s1 = {null}; // ok; `{null}` is guaranteed to be a LinkedHashSet
Set<Null> s2 = {null}; // ok
Object s3 = {null}; // ok
C<Null> s4 = {null}; // compile-time error; LinkedHashMap is not a subtype of C
const LinkedHashSet<Null> s5 = {null}; // compile-time error; `{null}` is only guaranteed to be a Set
const Set<Null> s6 = {null}; // ok
const Object s7 = {null}; // ok
const C<Null> s8 = {null}; // compile-time error; Set is not a subtype of C

However if I feed the above code into the analyzer (passing in --enable-experiment set-literals on the command line), it rejects the assignment to s1, saying The set literal type 'Set<Null>' isn't of expected type 'LinkedHashSet<Null>'. The set's type can be changed with an explicit generic type argument or by changing the element types.

FYI @bwilkerson.  I've marked it as P1 because it concerns a new feature, but I think it would be ok to can wait until the language team decides whether to land https://github.com/dart-lang/language/pull/129 before working on this.

@lrhn as of c565d4e477efc72a27edd182cc149cd629b6568c, the spec has been changed to avoid specific mention of LinkedHashSet.  Does that mean that the notion of the "exact type" of a set literal will be changing as well?  What's the status of https://github.com/dart-lang/language/pull/129?


Agent healthcheck/disable interaction

Healthchecks shouldn't re-enable a disabled agent. Ad hoc disabling vs health toggling should be distinct.

Fixed a while ago


restructuring towards python client library #455

So this is my restructuring attempt and starting a common python client library. I think this should be very near the state that it should be.
A summary of what when on here:

I have moved file_cmds, ractl_cmds and socket_cmds into a new python module common/src/rascsi
ractl_cmds, socket_cmds and file_cmds have been moved into python classes and parameterized with respect to token, locale, rascsi host and port.
Everything in common/src/rascsi has been de-flasked, i.e., all web specific stuff has been moved out of the common python module and moved into web. This is reflected on the one hand in changes in the return payloads of file_cmds and ractl_cmds so that there isn't any content that needs translation in there. Instead, those strings have been replaced by return codes in return_codes.py. In the web module, the return codes are mapped back to translated strings using the generic class return_code_mapper.py.
Web specific error handling has also been removed from those common classes. This yields a subclass socket_cmds_flask.py for usage in web.py instead of the direct usage of socket_cmds.py in common. In order to make this generic, a bunch of custom exceptions have been defined in exceptions.py that are passed to the child class to interprete those specific error situations.
start.sh scripts have been adapted to find the common python rascsi module
easy_install.sh has been adapted to generate the protobuf python interface only once for the common module.
web and oled modules have been adapted use use the new client library.

web/return_code_mapper.py takes care of mapping return_codes + parameters back to i18n strings.
I have removed code in oled that was now duplicated with common/src/racscsi (and previously web).
Due to the usage of the common python lib, I have added the now cheap added feature to direct the web and oled app to a different rascsi host/port.

I have tested the migration from the latest release to this branch and to me it seems to work fine. However, I wasn't able easily to trigger all situations that are covered in the return_code_mapper.py. The following strings are still open for test as of writing:
    ReturnCodes.RENAMEFILE_UNABLE_TO_MOVE: _(u"Unable to move file to: %(target_path)s"),
    ReturnCodes.WRITECONFIG_COULD_NOT_WRITE: _(u"Could not write to file: %(file_name)s"),
    ReturnCodes.READCONFIG_COULD_NOT_READ: _(u"Could not read configuration file: %(file_name)s"),
    ReturnCodes.WRITEDRIVEPROPS_COULD_NOT_WRITE: _(u"Could not write to properties file: %(file_path)s"),
    ReturnCodes.READDRIVEPROPS_SUCCESS: _(u"Read properties from file: %(file_path)s"),
    ReturnCodes.READDRIVEPROPS_COULD_NOT_READ: _(u"Could not read properties from file: %(file_path)s"),

I'm happy to hear the feedback. It would definately be good if a few people could give this a test run before this is merged.

@bzeiss I think this is turning out well overall! Thanks again for your effort.
Did you get the chance to run pylint against each of the source files? I ran it on the major files and spotted a handful of potential code quality issues, plus some newly introduced noise (e.g. a whole lot of "Method could be a function (no-self-use)").
Would you prefer to address each yourself, or should I point out the ones that I think should be addressed?
There is a bunch of "known issues" that are definitely out of scope, so I'm not expecting a 100% quality score. :)
And while on the topic of pylint, two structural things:
I think it'd be great to have pylinting documented in a README under the top level python/ dir. Right now, there's a paragraph in the web/README.md file that could be cut out and made into its own README.
Secondly, what to do about the .pylintrc file? Before, I had a symlink in each python source dir so that pylint could find it automatically. Should we replicate this in the new structure, or do you have a better suggestion?

Thanks!
True, pylint I didn't do, but should've done. I mostly rely on the IDEA code inspection. Don't worry about commenting on each issue, that is too much unnecessary work for you. I will run it and try to improve and what is complained about.
Yes, I'm aware about the pylint parts of the Web README. I will take care of this and take a look what a good solution for the .pylintrc file is. I have to play around with it to make a suggestion.

@bzeiss Sounds good! And please don't hesitate to propose changing the linting rules, if it's complaining loudly about non-issues.

@rdmark I have pushed a new commit to this branch containing a lot of little pylint fixes. Actually, most fixes weren't related to the restructuring ;-)
Anyway, there are still a lot of open issues, like too broad exceptions, suggested f-string usage etc.. You will see that I have also added a few ignore annotations to shut pylint up for specific things:

pylint wasn't able to properly figure out the import paths. I have tried to fiddle around with the sys.path in the init-hook= line in .pylintrc, but didn't manage to make it properly recognize the imports. Not sure what is happening here, but I thought it is probably better to locally disable that check than to disable it altogether. I may give this another try to properly make it find the packages.
At some places, pylint wanted me to make functions static. As with the IDEA code inspections, I have disabled those as well as I think those classes should be instantiated.

Also, I have added a README.md and a .pylintrc. I think the config file is fine, I rather prefer to disable checks locally (and thus documenting an actual developer decision to purposefully accept something to be the way it is) than to disable rules altogether.
Let me know whether you like the new changes.

@rdmark One more thing: pylint suggested to provide the encoding for open and save explicitly. For compatibility, I have used ISO-8859-1 and not UTF-8. I wasn't actually too sure about this, but I thought that utf-8 based filenames are probably still rather rare so I think it is probably sufficient to save in ISO-8859-1.

@bzeiss The import path not being recognized is a problem, since it may mask other real code quality issues. If we can't figure it out here, an issue ticket is appropriate, I think.

@bzeiss The import path not being recognized is a problem, since it may mask other real code quality issues. If we can't figure it out here, an issue ticket is appropriate, I think.

Let me try again tonight. I'm pretty sure there are no problems due to the import as the idea code inspection would complain about it. So there are two safety nets in my case, but it's true that others might rely on pylint alone, so it's better to have this working.

Branch updated as suggested and discussed on discord.


[FEATURE] GitHub issues integration

Is there an existing request for this?

[X] I have searched for any related issues and avoided creating a duplicate issue.

Have you read our code of conduct?

[X] I have read and agree to the code of conduct

Feature as a user story
As a GitHub user, I want to view my assigned github issues inside the tasks app, so that I can centralize issues from multiple systems

This is potentially a bit out there, but what if we could pull a list of tasks from many different systems so Tasks App is a one-stop shop.
GitHub seems like a good test case here, but I'm open to being told this is a terrible idea.


httpclient.SOCKS5DialFuncFromEnvironment should return "BOSH_ALL_PROXY" parsing errors

Hi bosh team,
When investigating how to use BOSH_ALL_PROXY in https://github.com/cloudfoundry/bosh-cli/issues/432, we have found that when the BOSH_ALL_PROXY is misconfigured, there is no helpful error message returned from the bosh cli, even when setting BOSH_LOG_LEVEL=debug. We think that when BOSH_ALL_PROXY is set, the value of BOSH_ALL_PROXY should be valid, and any parsing error should be shown to the operator for easier debugging.  When BOSH_ALL_RPOXY is misconfigured, instead of returning the original dialer in httpclient.SOCKS5DialFuncFromEnvironment, we can return a function that returns the parsing error.
Cheers,
Chunyi && @jamesjoshuahill

Resolved by https://github.com/cloudfoundry/bosh-utils/pull/45


Some initial fixes and code style updates

Removes hard-coded credentials
Adds .editorconfig
Fixes formatting on files

🚀 Deployed to staging by @AndrewGable in version: 1.1.8-10 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (Exported)

🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.3.86-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.86-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


fix(wallets): improve in-app wallet message signing logic

#3411  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gregfromstl and the rest of your teammates on  Graphite


Provide a utility to collect logs from LCFS

LCFS displays its logs on stdout when run in daemon mode.  There is no way to collect those when LCFS is run in daemon mode.  Provide a method to collect LCFS logs on a demand basis.

Now lcfs uses syslog for logging.


expired session/token

hey.
just wondering - how do you handle session expiration - hard logout?

Hello all, forgive me if I am completely off-base here. I am pretty new to this token stuff.
I thought that the best practice for JWT-based APIs would be to generate a new token on every request. When you make a request with your token, the server would authorize the token, then proceed to invalidate that token and return a new one. This would prevent the need for any kind of session expiration, as if someone were to get your token by packet sniffing or something, they would not be able to use the same token again as it would have been invalidated after first use.
You run into problems with this method when you make multiple concurrent requests (the first request would invalidate the token and the other requests would return 401 because the new token would not yet be returned to the client). To handle this, you would wait 5 seconds to invalidate a token on the server. This would allow the concurrent requests to be processed with the same token, and then you would get the new token with the response.
Does this sound plausible?

@kanzelm3 You can do what you want, JWT is just a token and with that token you can do what you want. Authentication is one of the usages of this token. How would you implement that? Is up to you.
What you ended doing, just be sure you use SSL because the token will be in all the requests and you don't want someone to getting it.
All comes down to your type of application. Is it a normal app? One token, save it on localstorage and live the life, it is not that important. It is a bank-type app? Put a short expiration, session storage. More security ? rotate the token.
Think about your app, think about what kind of security you want to put on it and do it. As I said, JWT is an empty canvas, it doesn't provide any solution, it is only a tool.

What is the current best way to refresh tokens? I see this is on hold, but I think it'd be pretty important to be able to easily refresh tokens to make it possible to use short expiration times.

@sahat do we have any updates on refreshing the token? :smile:

@iammary @nikopolv  I haven't found the best way to handle this yet, but perhaps this approach is one viable solution that may require emitting events on $rootScope:
From angular-oauth2 library:
 $rootScope.$on('oauth:error', function(event, rejection) {
      // Ignore `invalid_grant` error - should be catched on `LoginController`.
      if ('invalid_grant' === rejection.data.error) {
        return;
      }

      // Refresh token when a `invalid_token` error occurs.
      if ('invalid_token' === rejection.data.error) {
        return OAuth.getRefreshToken();
      }

      // Redirect to `/login` with the `error_reason`.
      return $window.location.href = '/login?error_reason=' + rejection.data.error;
    });

Similar to @owentran's strategy, I've implemented token refreshing for satellizer/jwt by using http-auth-interceptor to listen to a certain event, and wrote a service to use $http to refresh the token (hitting an api endpoint defined in laravel).  For anyone interested, since @owentran didn't include his code, this is how I'm doing it:
Use npm/bower to install angular-http-auth and inject it into your main module:
var tsportal = angular.module('tsportal', [
....
    'satellizer',
    'http-auth-interceptor',
....
]);

In my authController.js, which controls the login form, when satellizer receives the token, I duplicate it in localStorage.. The reason I do this is because satellizer_token seems to get deleted from localStorage as soon as a 401 is detected.
// Use satellizer's $auth service to login
				$auth.
					login(credentials).
					then(function(payload) {
						// set a copy of the token to use for refresh requests
						localStorage.setItem('_satellizer_token', payload.data.token);

...

Write a service that will hit a server endpoint to refresh. Inject authService into it (provided by angular-http-auth). Create a function in the service that takes a token parameter.  When you get a successful response from the server, update the token in localStorage.  Call authService.loginConfirmed() to continue and retry the previous HTTP request:
	var jwtRefreshService = angular.module('jwtRefreshService', []);
	jwtRefreshService.factory('jwtRefreshService', ['$http', 'authService', function($http, authService) {
		return {
			refresh: function(token) {
				$http({
					method: 'GET',
					url: 'api/authenticate/refresh',
					headers: {
						'Authorization': 'Bearer ' + token
					}
				}).then(function(payload) {
					localStorage.setItem('satellizer_token', payload.data.token);
					localStorage.setItem('_satellizer_token', payload.data.token);
					authService.loginConfirmed();
				})
			}
		}
	}]);

Inject the service after http-auth-interceptor in your main module:
var tsportal = angular.module('tsportal', [
....
    'satellizer',
    'http-auth-interceptor',
    'jwtRefreshService'
]);

I then inject it (and $rootScope if you haven't) into my main controller:
.controller('TradeshowController', ['$rootScope', ....  'jwtRefreshService', function TradeshowController($rootScope, ...  jwtRefreshService) {
In my main view's controller, I first check if the token is good, and if not refresh using the copy of the token I stored and my service:
		// No token, no access
		if (localStorage.getItem('satellizer_token') == null) {
			if (localStorage.getItem('_satellizer_token') != null) {
				// Try to refresh
				jwtRefreshService.refresh(localStorage.getItem('_satellizer_token'));
			}
			else {
				// Go to auth view
				$state.go('auth', {});
			}
		}

If the controller can continue, I then register an event listener on the $rootScope listening for http-auth-interceptor's event called event:auth-loginRequired
	// Refresh authorization token when it is expired transparently to the user
		// and re-run the request that failed (happens automatically from http-auth-interceptor)
		$rootScope.$on('event:auth-loginRequired', function(event, data) {
			var token = localStorage.getItem('_satellizer_token');
			if (token !== null) {
				jwtRefreshService.refresh(token);
			}
		})

My refresh function in my controller in Laravel:
	public function refresh(Request $request){
	     $oldtoken = JWTAuth::getToken();
	     try {
	         // attempt to refresh token for the user
	         if (! $token = JWTAuth::parseToken('bearer','authorization',$oldtoken)->refresh()) {
	             return response()>json(['error' => 'invalid_token'], 401);
	         }
	     } catch (JWTException $e) {
	         return response()->json(['error' => 'could_not_refresh_token'], 500);
	     }
	     return response()->json(compact('token'));
	 }

Seems to work well enough for me, but I don't like the fact I have to duplicate the token, nor that hitting a page for the first time, if you have an expired token, seems not to emit the http-auth-interceptor event.  That is why I have the check at the initial point of my main controller.
If this works for anyone else or they have questions, or if there are improvements to be made in my code, please let me know!

Hi @cviccaro Thank you so much for sharing your code on how to refresh the jwt token. I was having a hard time and your sample worked perfect for me. I was thinking of adding the refresh to a timer first but I liked your idea of just coupling it with the http-auth-interceptor and only refresh it when the auth fails. That is a good idea. However, I didnt find the use to store token in both _satellizer_token and satellizer_token which seemed redundant to me so I updated the token directly when refreshed. Nevertheless, the answer you shared helped me a lot in getting inspiration from and thank you for that. Cheers!

At the moment satellizer not removes expired token from storage, but doesn't attach it to Authorization header. So in some cases, your server can respond with status differs from 401. You can hack http-auth-interceptor.js on line 57 by adding your custom error number, it can be -1, 400 or whatever, so the event:auth-loginRequired will fire. Example:
            switch (rejection.status) {
              case -1: // my addition
              case 401:
                var deferred = $q.defer();
                var bufferLength = httpBuffer.append(config, deferred);
                if (bufferLength === 1)
                  $rootScope.$broadcast('event:auth-loginRequired', rejection);
                return deferred.promise;
              case 403:
                $rootScope.$broadcast('event:auth-forbidden', rejection);
                break;
            }


Day 373

Good morning! Here's your coding interview problem for today.
This problem was asked by Facebook.
Given a list of integers L, find the maximum length of a sequence of consecutive numbers that can be formed using elements from L.
For example, given L = [5, 2, 99, 3, 4, 1, 100], return 5 as we can build a sequence [1, 2, 3, 4, 5] which has length 5.

Appears to be nearly identical to https://github.com/vaskoz/dailycodingproblem-go/issues/205


[Dashboard] Available networks endpoint

Description
Create a new API endpoint that returns the list of available networks. The list should exclude any networks that have not been used in the last x months, where x is defined by an environment variable. The response should also be cached, with the Time-to-Live (TTL) duration passed as another environment variable.
We should not cache data from subgraph for disabled networks.
Criteria to consider a network without usage:
Have at least 1 escrow created in the last month and 5 HMT transfers in the last X months.
Motivation
This feature is necessary to improve the performance and relevancy of the network data we provide. By filtering out inactive networks and caching the response, we can reduce unnecessary processing and API calls, leading to better resource management and response times for clients.
Implementation details

Filtering:
Implement a mechanism to retrieve networks and filter out those without usage in the last x months.
The x value should be configurable via an environment variable.

Caching:
Cache the response of this endpoint, setting the cache expiration to a TTL (Time-to-Live) value defined by another environment variable.
Ensure that data from subgraphs for disabled networks is not cached.

Environment Variables:
Define two new environment variables:
NETWORK_USAGE_FILTER_MONTHS: Number of months to use for filtering out networks with no usage.
NETWORKS_AVAILABLE_CACHE_TTL: The TTL for caching the response.

Response:
Return a list of networks that meet the filtering criteria.
Ensure that once the TTL expires, the cache is invalidated and the network list is re-generated upon the next request.

Define new env vars:

NETWORK_USAGE_FILTER_MONTHS: Number of months to use for filtering out networks with no usage.
NETWORKS_AVAILABLE_CACHE_TTL: The TTL for caching the response.

Create new endpoint GET /stats/available-networks.
Create new method getAvailableNetworks:

For each network request statisticsClient.getHMTDailyData() for the last NETWORK_USAGE_FILTER_MONTHS months.
For each network request statisticsClient.getEscrowStatistics() for the last month.
Cache response by NETWORKS_AVAILABLE_CACHE_TTL.


Installing python-social-auth as a dependecie for mailman3 with buildout fails

I tried to install Mailman 3 and its companions (Hyperkitty, Postorius) on a
Ubuntu 14.04.2 LTS using the mailman-bundler. I followed the docs:
http://mailman-bundler.readthedocs.org/en/latest/
It fails while trying to install 'python-social-aut':
(venv)mailman@jiffy02:~/mailman-bundler$ buildout
Getting distribution for 'python-social-auth>=0.2.3'.
No eggs found in
/tmp/easy_install-LK6bYy/python-social-auth-0.2.9/egg-dist-tmp-FzLeGP (setup
script problem?)
While:
Installing mailman-web.
Getting distribution for 'python-social-auth>=0.2.3'.
Error: Couldn't install: python-social-auth 0.2.9
I checked with the folks from mailman3 and they told me to file a bug here.

You can test the install with buildout by creating a file called "buidout.cfg" in a temporary directory with the following content:
[buildout]
parts = main
[main]
recipe = zc.recipe.egg
eggs = python-social-auth

And running the "buildout" command.

I created a new temporary user, build a virtual environment and tested python-social-auth with buildout in two different versions.
testing@jiffy02:~$ virtualenv venv
testing@jiffy02:~$ source venv/bin/activate
(venv) testing@jiffy02:~$ pip install zc.buildout
(venv) testing@jiffy02:~$ buildout

buildout.cfg (#1)
[buildout]
parts = main
[main]
recipe = zc.recipe.egg
eggs = python-social-auth

It fails:
(venv)testing@jiffy02:~$ buildout
Creating directory '/home/testing/bin'.
Creating directory '/home/testing/parts'.
Creating directory '/home/testing/eggs'.
Creating directory '/home/testing/develop-eggs'.
Getting distribution for 'zc.recipe.egg>=2.0.0a3'.
Got zc.recipe.egg 2.0.1.
Installing main.
Getting distribution for 'python-social-auth'.
warning: no previously-included files matching '*' found under directory '.tox'
warning: no previously-included files matching '*.pyc' found under directory 'social'
warning: no previously-included files matching '*.pyc' found under directory 'examples'
warning: no previously-included files matching '*.db' found under directory 'examples'
warning: no previously-included files matching 'local_settings.py' found under directory 'examples'
warning: no previously-included files matching '*' found under directory 'examples/webpy_example/sessions'
No eggs found in /tmp/easy_install-wyDf6z/python-social-auth-0.2.9/egg-dist-tmp-7Pz6Vl (setup script problem?)
While:
  Installing main.
  Getting distribution for 'python-social-auth'.
Error: Couldn't install: python-social-auth 0.2.9

buildout.cfg (#2)
[buildout]
parts = main
[main]
recipe = zc.recipe.egg
eggs = python-social-auth<0.2.9

It succeeds:
(venv)testing@jiffy02:~$ buildout
Creating directory '/home/testing/bin'.
Creating directory '/home/testing/parts'.
Creating directory '/home/testing/eggs'.
Creating directory '/home/testing/develop-eggs'.
Getting distribution for 'zc.recipe.egg>=2.0.0a3'.
Got zc.recipe.egg 2.0.1.
Installing main.
Getting distribution for 'python-social-auth<0.2.9'.
warning: no previously-included files matching '*.pyc' found under directory 'social'
warning: no previously-included files matching '*.pyc' found under directory 'examples'
warning: no previously-included files matching '*.db' found under directory 'examples'
warning: no previously-included files matching 'local_settings.py' found under directory 'examples'
warning: no previously-included files matching '*' found under directory 'examples/webpy_example/sessions'
Got python-social-auth 0.2.7.
Getting distribution for 'PyJWT>=1.0.0'.
zip_safe flag not set; analyzing archive contents...
Got PyJWT 1.1.0.
Getting distribution for 'six>=1.2.0'.
no previously-included directories found matching 'documentation/_build'
zip_safe flag not set; analyzing archive contents...
six: module references __path__
Got six 1.9.0.
Getting distribution for 'requests-oauthlib>=0.3.1'.
Got requests-oauthlib 0.5.0.
Getting distribution for 'oauthlib>=0.3.8'.
zip_safe flag not set; analyzing archive contents...
Got oauthlib 0.7.2.
Getting distribution for 'requests>=1.1.0'.
Got requests 2.7.0.
Getting distribution for 'python-openid>=2.2'.
warning: no files found matching 'CHANGELOG'
warning: no files found matching '*.css' under directory 'doc'
warning: no files found matching '*.html' under directory 'doc'
zip_safe flag not set; analyzing archive contents...
Got python-openid 2.2.5.

Same problem over here. I did a manual download of python-social 0.2.9, untar, python setup.py bdist_egg, unzip of that egg, and the mailman3 buildout continued without complaints.
(No idea what I did though, I never use buildout nor eggs.)

Apparently this change:
--- python-social-auth-0.2.7/python_social_auth.egg-info/requires.txt   2015-04-19 09:13:58.000000000 +0200
+++ python-social-auth-0.2.9/python_social_auth.egg-info/requires.txt   2015-05-25 22:01:54.817050206 +0200
@@ -1,6 +1,6 @@
-python-openid>=2.2
+python3-openid>=3.0.1

I had to install the former to make things work. Installing the latter complained about py3-only stuff. (mailman setup scripts use py2).

OK I found the reason. In MANIFEST.in, the egg-info directory is ignored, and these files are necessary for easy_install to work. Buildout uses easy_install, thus triggers the error.
This can be easily reproduced with the command:
$ easy_install -md /tmp http://pypi.python.org/packages/source/p/python-social-auth/python-social-auth-0.2.10.tar.gz

The fix is as easy as:
diff --git a/MANIFEST.in b/MANIFEST.in
index 2cf5b48..d2fef43 100644
--- a/MANIFEST.in
+++ b/MANIFEST.in
@@ -7,7 +7,6 @@ recursive-include social/tests *.txt
 graft examples

 recursive-exclude .tox *
-recursive-exclude python_social_auth.egg-info *
 recursive-exclude social *.pyc
 recursive-exclude examples *.pyc
 recursive-exclude examples *.db

I'll send you a pull request ASAP.

Please, apply the patch from abompard and release a new version. Until that happens, I can only use the version 0.2.7


DateTimePicker behaviors

Category
[ ] Enhancement
[X] Bug
[ ] Question
Version
Please specify what version of the library you are using: [1.16.0]
Observed Behavior
The DateTimePicker component does not have a homogeneous behavior with the onChange event. When entering a invalid value, the onChange event is triggered sometime with latest valid value, and sometime it return Invalid Date
Steps to Reproduce
I created a repository with a small webpart containing only the DateTimePicker and a onChange Handler
https://github.com/bpa-solutions/demo-webpart-datepicker
Steps:

Place the WebPart on the page. picker date is empty, the picker hour is set to "12 AM" and the picker minute is set to "00"
Click on the Date picker, and select the current date (03 March 2020) => the onChange event return "Tue, 03 Mar 2020 11:00:00 GMT"
Change the Hour to "08 AM" => the onChange event return "Tue, 03 Mar 2020 07:00:00 GMT"
Remove the Hour => the onChange event return the last valid value ("Tue, 03 Mar 2020 07:00:00 GMT")
Set the Hour to "13 AM" => the onChange return "Tue, 03 Mar 2020 00:00:00 GMT", and a label "Incorrect hour value" is displayed under the Hour picker
Set to a correct date (03 Mar 2020 21:00:00 GMT) and then remove the Minute part => the onChange return an invalid date, and the Date picker is now set to Invalid Date too!
Click on the Date picker, and select any date => the new date is not set, because the Minute is empty

The component is stuck after the step 6. The user has to first set a new Minute value, and after that he can select a date again.
Desired Behavior
The Picker must either only return the last valid date, or not triggering the onChange.
The Picker must not be stuck. Changing the Minute must not change the Date to Invalid Date.
If a invalid minute is set, a error message must be displayed.

Fixed in the next drop


aggressively continue loops when errors happen in DirectoryVisitor

#9405

@mikedanese  An error happens when visiting one file in directory, the loops stop, I think we should continue loops to visit the left files.

Carrying forward the milestone on #9405

This PR is replaced by 9787


Support for uploading qlog artifacts

It would depend on Python.

It would depend on Python.

Then perhaps it should actually depend on if python is available or not.  The module IPC::Cmd has a functions can_run for that sort of thing

It would depend on Python.

Then perhaps it should actually depend on if python is available or not. The module IPC::Cmd has a functions can_run for that sort of thing

We use that for probing in Configure which is expected. It seems... rather "surprising" for us to vary how much of our unit test suite based on random environmental factors in this way...

It would depend on Python.

Then perhaps it should actually depend on if python is available or not. The module IPC::Cmd has a functions can_run for that sort of thing

We use that for probing in Configure which is expected. It seems... rather "surprising" for us to vary how much of our unit test suite based on random environmental factors in this way...

...
https://github.com/openssl/openssl/blob/925118e8c3b1041ce7f9840c2d67e7f878123e6b/test/recipes/01-test_symbol_presence.t#L27-L28
It's not like we don't have previous experience 😉

This is now working. Artifacts: https://github.com/openssl/openssl/actions/runs/7871749345?pr=23551

I've moved some of the artifacts upload code out of the unit test recipe.
The QLOGDIR code should definitely remain in the recipe; test-runs is exactly where this data is supposed to go and it is useful data even if not running in CI.
The qlog Python CI test was already merged so I don't think enabling it by default should be discussed in this PR. IMO a new issue should be opened regarding this.

I think this can be closed, as https://github.com/openssl/openssl/pull/23715 has been merged.  We now will get the qlog json output dumped to the ci log in the event that qlog testing fails

Err no. This is separate and much more useful

Still needs a second review! @nhorman

@nhorman Do you want this for 3.3?
It is pure CI so IMO it is acceptable post-alpha. We are going to be maintaining this branch for some time and having coverage here would be desirable. So I would support this. Your call.

I'd be ok with the addition of this, but for clarification, I think this would generally be an RSC decision, no?

also @hlandau given https://github.com/openssl/openssl/pull/23715 is merged, is this a high priority?  That is to say, while I'm not opposed to this at all, a failure in verifying qlog output dumps the json directlly to the console now as well for review.

This item is likely small enough that I'll just make the call, this can go in (#23715 notwithstanding)

Merged to master and cherry picked to 3.3.


Fix info test: new xref source

Description
The info.t test counting the external DBs for Xref sources is failing, after updating the test DB for release 109.
Use case
The number of DBs is hardcoded in info.t and it hasn't updated since the addition of a new DB source in Ensembl repo with PR#619.
As a result, the test suite is failing and likewise the automatic Travis build and related CI/CD pipeline.
Travis build for this PR is expected to fail, before test DBs are updated to 109.
Benefits
Preserve full functionality of the test suite from release 109 on.
Possible Drawbacks
None
Testing
The only - and straightforward - modification is about the expected (hardcoded) number of external DBs in file info.t.
The test suite can now successfully run.
Changelog
Public endpoints are not affected.

Coverage increased (+0.02%) to 44.405% when pulling 9166efffa7aec03068e6cf0c5b55e5eb459b183d on fix/info_t_new_db into 8e97787dc79eadd5ed64a42c79f6e95cc4057506 on main.

Closing this - changes already merged in with #553


Evaluate a possibility of calling codegen scripts in vendorless projects

Exploration, is it possible to call code gen scripts in vendorless projects.
If so, this might provide a bridge solution to https://github.com/knative/infra/issues/134

/assign


Home, Search, Library Icons Misaligned After The Theme Is Applied

I Have A Problem Here... After These Failed Tries, I Got It Working Again But Those Icons Like Home, Search, & Library Are Misaligned. Is There A Way To Fix It?

I have the same problem, even after adding
[Patch] xpui.js_find_8008 = ,(\w+=)32, xpui.js_repl_8008 = ,${1}56,
to the config-xpui.ini file. I also can't resize the sidebar. Any fixes yet?

I'm having the same problem, can the devs please get around to fixing this soon

I have the same problem on Fedora Linux, was anyone able to fix this problem?

also, the play button is not displayed correctly and the magnifying glass symbol is overlapping the text in the search bar

Oh, I see. So, I'm going to do the play button issue!

Hey bro @rlaphoenix! Miraculously the play button is working correctly after updating the theme. thanks for helping me!

This is fixed as of https://github.com/williamckha/spicetify-fluent/commit/5d299510c7de2dcc553f79ffbc1730a09f2aadcf

I am getting this issue,