test(file-list): Use path.posix to fix tests when run on Windows

Have file-list.js use path.posix instead of path itself, so the tests can expect a '/' separator on any platform.
Closes #1028

There were the following issues with your Pull Request

Commit: 8172e3e77150dacafc46f3e4af86c1146ff29e3d
Your commit message body contains a line that is longer than 80 characters

Guidelines are available at http://karma-runner.github.io/0.13/dev/git-commit-msg.html

This message was auto-generated by https://gitcop.com

Thanks a lot! :octocat:


NetConnection.Call.Failed not emitted when trying to connect to server and there is no internet conncetion

Describe the bug
When a user has no internet connection and  attempts to connect to the rtmp server, there is no connection event emitted to the flutter side of the application.
However, the following error is emitted on the java side:
java.net.ConnectException: failed to connect to "example-IP" (port 1935) from /:: (port 0): connect failed: ENETUNREACH (Network is unreachable)
From my understanding, the connection event "NetConnection.Call.Failed" should be emitted and from that we can inform the user manually that they have a connectivity issue on their side.
To Reproduce

Run example app Example2
Turn off all internet connections on android device
Try to connect to a working RTMP server
See Java exception java.net.ConnectException: failed to connect to in the logs

Expected behavior
To receive the connection event NetConnection.Call.Failed
Version
haishin_kit version 0.13.0
Smartphone info.
Google Pixel 7 Pro
Android version 14
Additional context
No response
Screenshots
No response
Relevant log output
onnect failed: ENETUNREACH (Network is unreachable) does not
[        ] W/NetSocketImpl( 1122): 	at libcore.io.IoBridge.connect(IoBridge.java:187)
[        ] W/NetSocketImpl( 1122): 	at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
[        ] W/NetSocketImpl( 1122): 	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
[        ] W/NetSocketImpl( 1122): 	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
[        ] W/NetSocketImpl( 1122): 	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
[        ] W/NetSocketImpl( 1122): 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
[        ] W/NetSocketImpl( 1122): 	at java.net.Socket.connect(Socket.java:646)
[        ] W/NetSocketImpl( 1122): 	at java.net.Socket.connect(Socket.java:595)
[        ] W/NetSocketImpl( 1122): 	at java.net.Socket.<init>(Socket.java:475)
[        ] W/NetSocketImpl( 1122): 	at java.net.Socket.<init>(Socket.java:243)
[        ] W/NetSocketImpl( 1122): 	at com.haishinkit.net.NetSocketImpl.createSocket(NetSocketImpl.kt:203)
[        ] W/NetSocketImpl( 1122): 	at com.haishinkit.net.NetSocketImpl.doConnection(NetSocketImpl.kt:165)
[        ] W/NetSocketImpl( 1122): 	at com.haishinkit.net.NetSocketImpl.access$doConnection(NetSocketImpl.kt:21)
[        ] W/NetSocketImpl( 1122): 	at com.haishinkit.net.NetSocketImpl$connect$1.invokeSuspend(NetSocketImpl.kt:64)
[        ] W/NetSocketImpl( 1122): 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:115)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:103)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:584)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:793)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:697)
[        ] W/NetSocketImpl( 1122): 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:684)
[        ] W/NetSocketImpl( 1122): Caused by: android.system.ErrnoException: connect failed: ENETUNREACH (Network is unreachable)

The design is as follows:

If it cannot connect at all, it will dispatch Event.IO_ERROR.
If it connects to the RTMP server but fails the handshake or cannot connect for other reasons, it will dispatch:
Event.RTMP_STATUS with NetConnection.Call.Failed.

Therefore, in cases like the current example-IP scenario, the design is to dispatch the Event.IO_ERROR event.


IMGPROXY_STRIP_COLOR_PROFILE doesn't work with avif source

I've tested 2 images: one source jpeg, second source avif
IMGPROXY_STRIP_COLOR_PROFILE=false

For jpeg source with display p3, it saves the same color profile in jpeg or avif output
For avif source with 10bit HDR in display p3 or rec. 2020, gets output as sRGB IEC61966-2.1

Hey @SPAHI4!
Could you provide the problematic sample? Can't reproduce this with my AVIFs :(

Never mind, I found one. I'll look at what I can do with this.

Hey @SPAHI4! Could you provide the problematic sample? Can't reproduce this with my AVIFs :(

https://spahi4-photo-dev.s3.eu-north-1.amazonaws.com/52c98368-e798-43fb-a1a9-e18f74eb1844.avif

The thing is that such AVIFs contain color profiles in the CiCp (aka NCLX) format. Such profiles don't actually contain color points, curves, matrices, etc, but contain IDs of color primaries, transfer functions, and matrix coefficients. And here we have problems:

Other image formats don't support CiCp color profiles. They support ICC profiles only.
There's no specification on converting CiCp to ICC nor support of it in libvips. Though, for most transfer functions it's not impossible, I'm working on this.
The BT.2100 PQ transfer function used in the provided sample is honestly a pain in the arse. Apple and Adobe have ICC profiles that implement BT.2100 PQ, yet I'm not sure it's legal to use any of them. I managed to build tone curves for BT.2100 PQ but the result is not perfect. So, I keep working on this.


Unbearably slow yarn in Docker

To run the frontend application, it is enough to go to the root directory of the project and do:
yarn install
yarn start

This is rather fast in my machine.
I am trying to get this working in Docker, see Dockerfile and docker-compose. In the container yarn install is slower, takes ~70 seconds in the container, when in the computer it would take <20s. yarn start, on the other hand is very fast in my computer and unbearably slow in Docker. yarn build is slow in the computer, so I never got to see it working in Docker.
Any advice on what to  do on this?
I have seen a few posts of people complaining about yarn install, but that is still bearable, and it is cached after the first time. yarn start however is very very slow.

So, I updated docker and now yarn start takes a reasonable amount of time without changing anything... Cannot say why.
Thanks for taking the time to check it on your side.


Total Browser Freeze on Invalid File Selection

As per our email conversation, by request:
1. Create an upload widget with HTML and directives containing a blacklist for .app.zip files using ngf-pattern
2. Assign that widget a filter of ngf-accept="'image/*, application/pdf, text/plain, application/msword, application/vnd.openxmlformats-officedocument.wordprocessingml.document, application/zip'"
3. Fire the file attachment directive (click on it or whatever)
4. Select All Files to bypass the accept filter
5. Select an osx application (anything from your Applications directory) which will say '.app' but are actually '.app.zip')
The primary UI execution thread will hang for about 10-20 seconds freezing the whole browser, then processing will continue.

Could you create a jsfiddle.


[REQUEST] clang-tidy too?

Thanks for this invaluable resource! Would it be possible to add clang-tidy too? And maybe some of the other clang tools (clang-query maybe?)

It should be pretty simple thing to do, unless the build is so slow, that it hits 6 hour limit. I'll take a look at it :smile:

I didn't have much time recently, so it took a while :grin:
Anyways, closed by 22538c6.
https://github.com/muttleyxd/clang-tools-static-binaries/releases/tag/master-22538c65
Feel free to reopen or post a new issue if you need more tools.


about network of video anomaly detection

I have read your excellent paper. I have some question about the content “Accordingly, the input of the network is a cuboid constructed by stacking 16 neighbor frames in grayscale. The structures of encoder and decoder are designed as: Conv3(3, 2, 96)- Conv3(3, 2, 128)-Conv3(3, 2, 256)-Conv3(3, 2, 256) and Dconv3(3, 2, 256)-Dconv3(3, 2, 256)-Dconv3(3, 2, 128)- Dconv3(3, 2, 1), where Conv3 and Dconv3 denote 3D convolution and deconvolution, respectively. A BN and a ReLU activation follow each layer (except the last one）” in section4.2.

I would like to ask if the pool layer is used in the above structure. If used, what is the exact structure of the pool layer?
2.What is the size of the input?

when I use the hyper_parameters of network in your paper, the network product feature like:
    Layer (type)               Output Shape         Param #

================================================================
Conv3d-1       [8, 96, 7, 119, 159]           2,592
BatchNorm3d-2       [8, 96, 7, 119, 159]             192
ReLU-3       [8, 96, 7, 119, 159]               0
Conv3d-4        [8, 128, 3, 59, 79]         331,776
BatchNorm3d-5        [8, 128, 3, 59, 79]             256
ReLU-6        [8, 128, 3, 59, 79]               0
Conv3d-7        [8, 256, 1, 29, 39]         884,736
BatchNorm3d-8        [8, 256, 1, 29, 39]             512
ReLU-9        [8, 256, 1, 29, 39]               0
ConvTranspose3d-10        [8, 256, 3, 59, 79]       1,769,472
BatchNorm3d-11        [8, 256, 3, 59, 79]             512
ReLU-12        [8, 256, 3, 59, 79]               0
ConvTranspose3d-13      [8, 128, 7, 119, 159]         884,736
BatchNorm3d-14      [8, 128, 7, 119, 159]             256
ReLU-15      [8, 128, 7, 119, 159]               0
ConvTranspose3d-16       [8, 1, 15, 239, 319]           3,456
BatchNorm3d-17       [8, 1, 15, 239, 319]               2
the loss of network can not calculate because mismatch of input and output

hello,Mr GongDong,Is there open source code for this article?

when I use the hyper_parameters of network in your paper, the network product feature like:
    Layer (type)               Output Shape         Param #

================================================================
Conv3d-1 [8, 96, 7, 119, 159] 2,592
BatchNorm3d-2 [8, 96, 7, 119, 159] 192
ReLU-3 [8, 96, 7, 119, 159] 0
Conv3d-4 [8, 128, 3, 59, 79] 331,776
BatchNorm3d-5 [8, 128, 3, 59, 79] 256
ReLU-6 [8, 128, 3, 59, 79] 0
Conv3d-7 [8, 256, 1, 29, 39] 884,736
BatchNorm3d-8 [8, 256, 1, 29, 39] 512
ReLU-9 [8, 256, 1, 29, 39] 0
ConvTranspose3d-10 [8, 256, 3, 59, 79] 1,769,472
BatchNorm3d-11 [8, 256, 3, 59, 79] 512
ReLU-12 [8, 256, 3, 59, 79] 0
ConvTranspose3d-13 [8, 128, 7, 119, 159] 884,736
BatchNorm3d-14 [8, 128, 7, 119, 159] 256
ReLU-15 [8, 128, 7, 119, 159] 0
ConvTranspose3d-16 [8, 1, 15, 239, 319] 3,456
BatchNorm3d-17 [8, 1, 15, 239, 319] 2
the loss of network can not calculate because mismatch of input and output

I got the same issue when testing:
'operands could not be broadcast together with shapes (16,1,240,368) (16,1,240,360) '
It seems that after the encode-decode operations the width was wrongly extended to 368. I troubleshoot this and find it is actually a typical Conv Operation Mistake --- Since the width of input image 368 is not fully divisble by 16 (i.e. four times of Conv Op with stride 2) So after that the width will be 22.5 which will later be rounded up to 23 in Pytorch. Then after decoding process which deconv four times on the latent features map, the final height will be 23 X 16 = 368 as it turns out to be.

The code is incomplete and not bug-free. Sad.


Reduce the Width of search result pane

I guess sive meaning the width, right @Raathigesh ?

That's right. Width should be reduced. Edited!

Fixed with f621cdfcbed30b19de18563a1b8fb660513e1c6f

I think we should center the result pane.

Fixed with 1574b0b76d7917833d144c0531542bd1d8126b86

It will look good if we increase the width of search result to fit the active task width so there wont be any distractions behind the result set.

I don't agree with this since equal widths will result in a confusion between the search results and task list,
Further the search results appear "above" the tasks. as they are dynamic. This is a physical behaviour which is visually achieved by placing the search result on top of the tasks.

Just a suggestion. lets see others views aswell.

In above image i have a search result and i cant see the highlighted text because subject is too long. why don't we use the width which is already available. + keep the UX

I think we need to reduce only by few pixels. Looks like we are loosing a lot of width currently.

What if we left align the search result and increase the width up to the menu icon? Also, we could add a divider between the menu icon and search.

Fixed with eaddaa8cc23f68163260f71fd233bdfddb5e3c46


clean up upstream-dev CI

follow-up to #4583, which also added a PR upstream-dev CI. However, because the output of pytest has been redirected to a file, the failures are hard to diagnose. The fix is to duplicate stdout using tee.
~Additionally, we now have two upstream-dev CI, so I guess we should remove the old one?~ #4584 will probably set the upstream-dev CI to allow_failure: true, so it might be better to remove the new CI (or to somehow mark the new PR CI with allow_failure: true while not changing the scheduled CI).

great, thanks again, @andersy005. Let's merge now and leave the choice between the old and new PR CI to a different PR.

great, thanks again, @andersy005. Let's merge now and leave the choice between the old and new PR CI to a different PR.

Of course! I'm curious, are there any benefits to keeping the old azure upstream-dev CI around?

If I remember correctly, we decided to mark the upstream-dev CI as allowed failure. If there's a way to mark the PR CI as such, I think the only benefit is that a allowed failure of the old azure CI is a bit more visible (see https://github.com/pydata/xarray/pull/4584#issuecomment-729726028).

we decided to mark the upstream-dev CI as allowed failure. If there's a way to mark the PR CI as such,

If I understand this correctly, this is something that can be done via the branch protection settings
https://github.com/pydata/xarray/settings/branch_protection_rules

That's somewhat different, I think. Branch protection defines CI that has to pass in order to be able to merge the PR, while allowed failures change the result of the CI. For the current implementation of this, see the changes in #4584.

Oooh I see... Thank you for the clarification


thank you for this tool!

hi all
thank you for this wonderful tool. it's amazing. it's helped me understand git.
chrs

Also came here to report this important issue


iOS: Failure to build with --configuration Release

Hello!
I'm trying to use expo-community-flipper in combination with Expo prebuild/run:ios and seeing the below error when running expo run:ios --configuration Release - simply running expo run:ios (aka Debug configuration) works fine and the Flipper integration works great 💯.
I tried using FLIPPER_DISABLE=1 but was seeing the same error. I also tried a expo prebuild -p ios --clean after installing expo-community-flipper.
The error
❌  Undefined symbols for architecture x86_64
┌─ Symbol: _OBJC_CLASS_$_FlipperClient
└─ Referenced from: objc-class-ref in libreact-native-flipper.a(FlipperReactNativeJavaScriptPluginManager.o)

❌  ld: symbol(s) not found for architecture x86_64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

› Linking   tempexposandbox » tempexposandbox
❌  Undefined symbols for architecture arm64
┌─ Symbol: _OBJC_CLASS_$_FlipperClient
└─ Referenced from: objc-class-ref in libreact-native-flipper.a(FlipperReactNativeJavaScriptPluginManager.o)

❌  ld: symbol(s) not found for architecture arm64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

    Run script build phase 'Start Packager' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'tempexposandbox' from project 'tempexposandbox')
    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'tempexposandbox' from project 'tempexposandbox')
    Run script build phase '[CP-User] Generate app.config for prebuilt Constants.manifest' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'EXConstants' from project 'Pods')

› 6 error(s), and 3 warning(s)

CommandError: Failed to build iOS project. "xcodebuild" exited with error code 65.

Here's my app.config.js file:
const config = {
  expo: {
    name: "temp-expo-sandbox",
    slug: "temp-expo-sandbox",
    version: "1.0.0",
    orientation: "portrait",
    icon: "./assets/images/icon.png",
    scheme: "myapp",
    jsEngine: "hermes",
    userInterfaceStyle: "automatic",
    splash: {
      image: "./assets/images/splash.png",
      resizeMode: "contain",
      backgroundColor: "#ffffff",
    },
    plugins: ["expo-community-flipper"],
    updates: {
      fallbackToCacheTimeout: 0,
    },
    assetBundlePatterns: ["**/*"],
    ios: {
      supportsTablet: true,
      bundleIdentifier: "XXXXX",
    },
    android: {
      adaptiveIcon: {
        foregroundImage: "./assets/images/adaptive-icon.png",
        backgroundColor: "#ffffff",
      },
      package: "XXXXX",
    },
    web: {
      favicon: "./assets/images/favicon.png",
    },
  },
};

module.exports = config;

And finally, here's my package.json dependencies:
  "dependencies": {
    "@expo/vector-icons": "^13.0.0",
    "@react-navigation/bottom-tabs": "^6.0.5",
    "@react-navigation/native": "^6.0.2",
    "@react-navigation/native-stack": "^6.1.0",
    "expo": "~47.0.9",
    "expo-asset": "~8.6.2",
    "expo-community-flipper": "^47.0.0",
    "expo-constants": "~14.0.2",
    "expo-dev-client": "~2.0.1",
    "expo-font": "~11.0.1",
    "expo-linking": "~3.2.3",
    "expo-splash-screen": "~0.17.5",
    "expo-status-bar": "~1.4.2",
    "expo-system-ui": "~2.0.1",
    "expo-web-browser": "~12.0.0",
    "react": "18.1.0",
    "react-dom": "18.1.0",
    "react-native": "0.70.5",
    "react-native-flipper": "0.175.0",
    "react-native-safe-area-context": "4.4.1",
    "react-native-screens": "~3.18.0",
    "react-native-web": "~0.18.9"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@types/react": "~18.0.24",
    "@types/react-native": "~0.70.6",
    "jest": "^26.6.3",
    "jest-expo": "~47.0.1",
    "react-test-renderer": "18.1.0",
    "typescript": "^4.6.3"
  },

Thank you for all the hard work you do on this plugin 🙏

Since you're including react-native-flipper in your package.json, you'll also need to specify the rnf version in the config plugin.
// app.config.js
{
  "expo": {
    "..."
    "plugins": [
      ["expo-community-flipper", "0.175.0"]
    ]
  }
}

0.175.0 is verified as working over here so it might just be a config issue as part of the setup.

FlipperOptions, as the readme calls it, didn't used to be necessary to build the app successfully. I wonder what changed. In any event, it may call for some update to the readme since our otherwise working project suddenly stopped building on iOS.
I'm testing that solution now, but 8 hours in EAS build queue until I can report back.

The FlipperOptions should still be optional, even in 47.* and may represent a bug. @Slapbox, are you getting a TS error, one of the plugin's errors asking for the podfile to be submitted as a bug, or an error from EAS during build?
Asking because the FlipperOptions last changed during SDK 46. However, if you include a version of react-native-flipper in package.json with a version that differs from the pod bundled with react-native, things will go awry. In that scenario, the cocoapod dependency system cannot disambiguate which flipper to use, resulting in a variety of build errors.
With react-native including a flipper version by default, this might become more of an issue and be worth including in the readme.

I think the key here is that 0.175.0 or below are necessary - I guess maybe because that's the latest version compatible with what's bundled with react-native? In that case, I don't think we need to specify the version - but since EAS isn't even accepting new builds and I'm still 6 hours away from mine starting, I can't report back until tomorrow (a wildly optimistic projection.)

I guess maybe because that's the latest version compatible with what's bundled with react-native

💯 likely the cause. This is because Flipper's on 0.x.y, meaning any x can include breaking changes to pieces of AppDelegate or other parts of the ios code Expo abstracts away for us.
The only time you really need to specify the version is when you need JS plugin functionality (such as the redux inspector) inside of Flipper. If all you need is layout & debugging, you can just use plugin w/o a version (and no react-native-flipper in package.json) and it should work using the RN defaults.

I'm having the same issue. We are using JS plugin functionality (react-query-native-devtools) so we need to have react-native-flipper inside package.json.
Like @Drew-Gerber describes, a Development build builds with no problem. As soon as we try to build a Preview build, EAS fails with the same error as @Slapbox has shown.
I have tried with and without including the RNF version in the config plugin as suggested by @jakobo but this makes no difference.
Relevant parts of our setup:
package.json:
  "dependencies": {
    "....",
    "expo-community-flipper": "^47.0.0",
    "react-native": "0.70.5",
    "react-native-flipper": "^0.175.0",
    "react-query-native-devtools": "^4.0.0",
  },

app.config.js
{
  "expo": {
    "..."
    "plugins": [
      [
        "expo-notifications",
        {
          "icon": "./assets/adaptive-icon.png",
          "color": "#EFF5FC"
        }
      ],
      ["expo-community-flipper", "0.175.0"]
    ]
  }
}

eas.json
{
  "cli": {
    "version": ">= 2.6.0"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "android": {
        "buildType": "apk"
      },
      "ios": {
        "simulator": true,
        "resourceClass": "m1-medium"
      },
      "channel": "development"
    },
    "preview": {
      "distribution": "internal",
      "channel": "preview",
      "ios": {
        "resourceClass": "m1-medium"
      }
    },
    "production": {
      "channel": "production"
    }
  },
  "submit": {
    "production": {}
  }
}

Error in EAS:

Just documenting some discoveries:

https://stackoverflow.com/questions/70609829/react-native-ios-new-scheme-error-undefined-symbol-objc-class-flipperclient 163 looks verified for the RN version in SDK 47. It seems somewhere in the 170+ line that a regression emerged
https://github.com/facebook/flipper/issues/4278 documents the regression seems to imply we'll need to pass Debug and Dev.Debug configurations going forward. I will probably add Release as well since we enable/disable via our plugin and not the Metro config.

The good news is, we can test this fix locally. Here's a stripped down JS version of the plugin, specifically for iOS. I'll see about adding this with tests in the meantime.
// flipper.js
// install locally @expo/config-plugins, expo
// use this instead of the community plugin for testing
import path from "path";
import fs from "fs";
import { withDangerousMod } from "expo/config-plugins";
import {
  mergeContents,
  removeContents,
} from "@expo/config-plugins/build/utils/generateCode";

// set flipper here or `false` for default version
const FLIPPER_VERSION = "0.163.0";

/** In iOS, this is the line we anchor to for adding args to use_react_native!() */
export const IOS_URN_ARG_ANCHOR =
  /:fabric_enabled => flags\[:fabric_enabled\],/;

/** In a Podfile, this regex tells us the :production arg is already there */
export const IOS_HAS_PRODUCTION_ARG =
  /use_react_native!\([\s\S]*:production\s+=>/gm;

/** In a Podfile, this regex tells us the :flipper_configuration arg is already there */
export const IOS_HAS_FLIPPER_ARG =
  /use_react_native!\([\s\S]*^\s*:flipper_configuration\s+=>/gm;

// make a flipper arg
const createFlipperArgument = () => {
  const active = FLIPPER_VERSION
    ? `FlipperConfiguration.enabled(["Debug", "Dev.Debug", "Release"], { 'Flipper' => '${FLIPPER_VERSION }' }),`
    : `FlipperConfiguration.enabled(["Debug", "Dev.Debug", "Release"]),`;
  return `:flipper_configuration => ${active}`;
};

// strips tagged content
const removeTaggedContent = (contents, ns) => {
  return removeContents({ src: contents, tag: tag(ns) });
};

// get last mutation result
const last = (arr) => {
  const l = arr[arr.length - 1];
  if (typeof l === "undefined") {
    throw new Error(
      "No prior results. This is a bug in expo-community-flipper and should be reported"
    );
  }
  return l;
};

// edit podfile step
export function updatePodfileContentsWithFlipper(
  contents
) {
  const results = [];
  results.push(removeTaggedContent(contents, "urn"));

  const preexisting = IOS_HAS_FLIPPER_ARG.test(last(results).contents);

  if (!preexisting) {
    results.push(
      mergeContents({
        tag: tag("urn"),
        src: last(results).contents,
        newSrc: createFlipperArgument(),
        anchor: IOS_URN_ARG_ANCHOR,
        offset: 1,
        comment: "#",
      })
    );
  }

  if (!last(results).didMerge) {
    throw new Error(
      "Cannot add flipper arguments to the project's ios/Podfile. Please report this with a copy of your project Podfile. You can generate this with the `expo prebuild` command."
    );
  }
  return last(results).contents;
}

// update podfile mod
function withFlipperPodfile(config) {
  config = withDangerousMod(config, [
    "ios",
    async (c) => {
      const filePath = path.join(c.modRequest.platformProjectRoot, "Podfile");
      const contents = fs.readFileSync(filePath, "utf-8");
      const updatedContents = updatePodfileContentsWithFlipper(contents, cfg);
      fs.writeFileSync(filePath, updatedContents);
      return c;
    },
  ]);

  return config;
}

// plugin entry point
export default function withFlipperIOS(config: ExpoConfig) {
  config = withFlipperPodfile(config);
  return config;
}

// app.config.js
module.exports = {
  "expo": {
    "..."
    "plugins": [
      "./path/to/flipper.js"
    ]
}

I've just pushed v 47.0.1 which is backward compatible with 47.0.0 and should address the most likely culprits:

We enable the Release profile, along with Debug and Dev.Debug based on the linked flipper thread. It's very likely that building with the metro Release configuration is creating a scenario where the react-native scripts want to add Flipper but the pod was never included in the build. Shifting the enable/disable to our app.config.js is a more expo-like way of approaching it
47.0.1 also includes a "hard-disable" of setting the env value NO_FLIPPER to 1. This explicitly passes FlipperConfiguration.disabled which should prevent all podfile linking from happening. Going forward, this will also let us identify upstream issues easier.

@all-contributors
please add @Drew-Gerber for bugs.
please add @PimButton for bugs.

With the Dev.Debug profile added after running yarn ios I'm currently getting the following error on SDK 47
⚠  Something went wrong running `pod install` in the `ios` directory.
Command `pod install` failed.
└─ Cause: Unknown configuration whitelisted: dev.debug. CocoaPods found debug and release, did you mean one of these?

This is my Podfile, and removing Dev.Debug seems to resolve the issue.
require File.join(File.dirname(`node --print "require.resolve('expo/package.json')"`), "scripts/autolinking")
require File.join(File.dirname(`node --print "require.resolve('react-native/package.json')"`), "scripts/react_native_pods")
require File.join(File.dirname(`node --print "require.resolve('@react-native-community/cli-platform-ios/package.json')"`), "native_modules")

require 'json'
podfile_properties = JSON.parse(File.read(File.join(__dir__, 'Podfile.properties.json'))) rescue {}

platform :ios, podfile_properties['ios.deploymentTarget'] || '13.0'
install! 'cocoapods',
  :deterministic_uuids => false

target 'IOSApp' do
  use_expo_modules!
  config = use_native_modules!

  use_frameworks! :linkage => podfile_properties['ios.useFrameworks'].to_sym if podfile_properties['ios.useFrameworks']

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
# @generated begin expo-community-flipper-isprod - expo prebuild (DO NOT MODIFY) sync-828c22a1a38236bf5b7c203393f474bc68356b34
    # ENV value added to support Hermes
    :production => ENV["PRODUCTION"] == "1" ? true : false,
# @generated end expo-community-flipper-isprod
    :hermes_enabled => podfile_properties['expo.jsEngine'] == 'hermes',
    :fabric_enabled => flags[:fabric_enabled],
# @generated begin expo-community-flipper-urn - expo prebuild (DO NOT MODIFY) sync-b49de04cb8d73b4529a5f4b5f77c50dc458ee8ce
    :flipper_configuration => FlipperConfiguration.enabled(["Debug", "Dev.Debug", "Release"]),
# @generated end expo-community-flipper-urn
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/..",
    #
    # Uncomment to opt-in to using Flipper
    # Note that if you have use_frameworks! enabled, Flipper will not work
    # :flipper_configuration => !ENV['CI'] ? FlipperConfiguration.enabled : FlipperConfiguration.disabled,
  )

  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)

    # This is necessary for Xcode 14, because it signs resource bundles by default
    # when building for devices.
    installer.target_installation_results.pod_target_installation_results
      .each do |pod_name, target_installation_result|
      target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
        resource_bundle_target.build_configurations.each do |config|
          config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    end
  end

  post_integrate do |installer|
    begin
      expo_patch_react_imports!(installer)
    rescue => e
      Pod::UI.warn e
    end
  end
end

With the Dev.Debug profile added after running yarn ios I'm currently getting the following error on SDK 47

I'll get a fix out today with only debug & release profiles for metro. I don't think we need to configure the profiles, but I'm surprised there's a whitelist now

Update: 47.0.2 is out with only the Debug and Release configurations enabled. That should get everyone to a working state. LMK if more EAS issues come up. Thank you @jacob3794 for doing a build test w/ the Dev.Debug configuration removed.

I can confirm that 47.0.2 fixes the issue and a Release build is created with no problem!
@jacob3794 thanks for the great work!


Couple issues

First, should MacosTitleBar here be WindowsTitleBar?
https://github.com/FrankenApps/Avalonia-CustomTitleBarTemplate/blob/47fc0a5adb3fd8515bcd588f47e7d1703eeeb638/Views/CustomTitleBars/WindowsTitleBar.axaml.cs#L31-L32
Second, this library doesn't seem to be compatible with newer versions of Avalonia (namely: looks like this library is using 0.10.0 and I'm on 0.10.13) as the signature of IObservable.Subscribe has changed. I would love to use the examples you've written, but don't have the time to fix the breaking changes. (It's probably a quick fix, but currently don't have the time to look into it).
Thanks for making this library! It looks great and I look forward to using it

You are right, MacosTitleBar should have been WindowsTitleBar there. I haven't used (or updated) this in a while so I went ahead and just did this (+ fixed this issue).
However I am not able to reproduce your Issue regarding the changed signature of IObservable.Subscribe. For me the Code still compiles and runs fine on (now) .net6. Did you check out the repo and ran it, or did you implement this on your own?

Ah, looking at your commit perhaps I was missing an Avalonia package. I'll try again tonight

Actually I was able to fix it. There was some using I was missing (not sure which) and VS wasn't suggesting as a fix. But after copying your usings from your examples that worked! Thanks!


AzurePowerShell Task with TargetAzurePs set to latestVersion is useless

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzurePowerShell
Environment

Server - Azure Pipelines - Hosted Agent running on ubuntu-latest
Also behaves like this on a (self-hosted) 'Azure virtual machine scale set agent' (ubuntu)

Issue Description
Setting TargetAzurePs: 'latestVersion' will actually use az_7.3.2 instead of the latest.
According to https://github.com/Azure/az-ps-module-versions/blob/main/versions-manifest.json az_8.1.0 is already out (with stable set to true), so the task is 4 months behind on this module. This is not what i call 'Latest Version'. I can set preferredAzurePowerShellVersion: '8.1.0' to use the latest version, but it should just get the latest version when you call for it, not something from somewhere in the current year. If there is a reason to delay it on the default 'Azure Pipelines' agents, it should explicitly stated that it's a somewhat recent version and not the latest.

Please check

Bump


fix: only create migrations folder if migrationsList is not used

https://github.com/mikro-orm/mikro-orm/issues/907#issuecomment-713532649

Looking good, lets wait for the CI.

@B4nan I don't think the failing code climate has anything to do with my changes.

Yeah that's fine, some configuration mismatch. Tests are passing and full coverage is remained, that is what is important.


Added DataFactory Blob Copy Example, reordered missing types tests

Example based off of: https://github.com/Azure/azure-quickstart-templates/blob/master/101-data-factory-v2-blob-to-blob-copy/azuredeploy.json
Also reordered the missing types to be alphabetical and grouped together.

Not sure on this one as the type values are defined in ARM template documentation and looks like bicep recognizes type but does not have the correct values pulling in.

@JFolberth - it looks like you have merge conflicts with the latest in main. Can you fix the conflicts?

Conflicts updated.

Codecov Report

Merging #999 (2393f57) into main (6baaaeb) will increase coverage by 0.47%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #999      +/-   ##
==========================================
+ Coverage   94.26%   94.73%   +0.47%
==========================================
  Files         328      324       -4
  Lines       15810    15660     -150
  Branches       12        0      -12
==========================================
- Hits        14903    14836      -67
+ Misses        907      824      -83

Flag
Coverage Δ

dotnet
94.73% <100.00%> (-0.09%)
:arrow_down:

typescript
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/Bicep.Core.Samples/ExamplesTests.cs
98.73% <100.00%> (+0.01%)
:arrow_up:

...cep.Core.UnitTests/FileSystem/FileResolverTests.cs
79.31% <0.00%> (-20.69%)
:arrow_down:

.../Bicep.Core.UnitTests/Assertions/BaselineHelper.cs
63.63% <0.00%> (-15.91%)
:arrow_down:

src/Bicep.Core/FileSystem/PathHelper.cs
96.15% <0.00%> (-3.85%)
:arrow_down:

src/Bicep.Core.UnitTests/Utils/CompilerFlags.cs
33.33% <0.00%> (ø)

...Bicep.Core.UnitTests/FileSystem/PathHelperTests.cs
100.00% <0.00%> (ø)

src/vscode-bicep/src/utils/telemetry.ts

src/vscode-bicep/src/utils/logger.ts

src/vscode-bicep/src/language/client.ts

src/vscode-bicep/src/extension.ts


Support node8 ?

#10 Hi,
I try my application with node8 (from v6.11.1 to v8.9.0).
When i require the module const RedisStore = require('passwordless-redisstore'), i've got this error :
Error: Module version mismatch. Expected 48, got 57.
    at Error (native)
    at Object.Module._extensions..node (module.js:597:18)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at bindings (/Users/me/myWorkspace/myOrga/myApp/node_modules/bindings/bindings.js:76:44)
   at Object.<anonymous> (/Users/me/myWorkspace/myOrga/myApp/node_modules/bcrypt/bcrypt.js:3:35)
...

It seems that node v8.9.0 (LTS) is not supported by bcrypt.
Maybe, this : https://github.com/kelektiv/node.bcrypt.js/issues/513
Should it be better to use bcryptjs to avoid this kind of issue ? https://github.com/dcodeIO/bcrypt.js
Thks

I just find : https://github.com/lloydcotten/passwordless-redisstore

@JBustin. If you update node, you must recompile your native addons. NodeJS v8+ are fully supported by bcrypt.
npm rebuild bcrypt

This should do the task.

@agathver it was a problem with pm2 + yarn + nvm, and a curious manage of natives libraries.
Totally clean of pm2 resolves the problem.
Thks


BluetoothLEDevice.FromBluetoothAddressAsync() can return null?

It seems like BluetoothLEDevice.FromBluetoothAddressAsync() can return null. This is not documented. What does it mean when it returns null? Is there a way to get an error code for more information?

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

ID: cedb9559-6da0-2e91-eaef-12d9e9bfff4f
Version Independent ID: cf9ff409-0028-5b6c-b77e-3987ad23671d
Content: BluetoothLEDevice.FromBluetoothAddressAsync Method (Windows.Devices.Bluetooth) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.Devices.Bluetooth/BluetoothLEDevice.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @stevewhims
Microsoft Alias: stwhi

Here is some more info on this from someone who helped design the API: https://github.com/microsoft/Windows-universal-samples/issues/1089#issuecomment-487586755

Super!


[bug] Text describing the error

In "select your server" of "Settings", the distinction between "China" and "Taiwan", "Hong Kong" and "Macao" appears in the options.Taiwan, Macao and Hong Kong belong to China.Please change "China" to "Chinese Mainland" and indicate "Taiwan,China", "Macao of China" and "Hong Kong of China".Thank you."Genshin Impact" is a Chinese game. If you really love it, please respect the Chinese people.

IMO the server options are seperated because it's in fact that TW/HK/MO and Asia uses the same timezone and same API entry point for wish counter and that servers in China mainland (天空岛 and 世界树) uses same timezone but different API entry point.


[SPARK-41709][CORE][SQL][UI] Explicitly define Seq as collection.Seq to avoid toSeq when create ui objects from protobuf objects for Scala 2.13

What changes were proposed in this pull request?
This pr explicitly define Seq as collection.Seq in the ui related class definitions to avoid collection conversion when creating ui objects from protobuf objects to make no performance difference between Scala 2.13 and Scala 2.12.
Why are the changes needed?
Avoid  collection conversion when creating ui objects from protobuf objects for Scala 2.13.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions

Codecov Report

Merging #39215 (1af0a51) into master (d5865d0) will decrease coverage by 46.75%.
The diff coverage is 52.50%.

:exclamation: Current head 1af0a51 differs from pull request most recent head ad179a1. Consider uploading reports for the commit ad179a1 to get more accurate results

@@             Coverage Diff             @@
##           master   #39215       +/-   ##
===========================================
- Coverage   90.94%   44.18%   -46.76%
===========================================
  Files         342      171      -171
  Lines       76680    40980    -35700
  Branches    10462     6478     -3984
===========================================
- Hits        69733    18106    -51627
- Misses       5353    22138    +16785
+ Partials     1594      736      -858

Flag
Coverage Δ

unittests
44.18% <52.50%> (-46.75%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ython/pyspark/sql/connect/proto/expressions_pb2.py
52.32% <0.00%> (ø)

python/pyspark/sql/connect/proto/relations_pb2.py
57.72% <0.00%> (ø)

python/pyspark/sql/connect/column.py
87.63% <91.66%> (-0.01%)
:arrow_down:

python/pyspark/sql/connect/dataframe.py
76.93% <100.00%> (+0.11%)
:arrow_up:

python/pyspark/sql/connect/expressions.py
89.05% <100.00%> (-0.07%)
:arrow_down:

python/pyspark/sql/connect/plan.py
80.25% <100.00%> (+0.15%)
:arrow_up:

python/pyspark/sql/connect/types.py
92.00% <100.00%> (+0.16%)
:arrow_up:

...on/pyspark/sql/tests/connect/test_connect_basic.py
99.06% <100.00%> (ø)

...n/pyspark/sql/tests/connect/test_connect_column.py
97.26% <100.00%> (+0.67%)
:arrow_up:

...l/tests/connect/test_connect_column_expressions.py
97.58% <100.00%> (ø)

... and 291 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Seems OK to me, un-mark it as Draft to let it test

Local maven test with Scala 2.13, all passed

Merged to master

Thanks @srowen


Create acischools.txt

ACI Student Secondary Domain

Açı High School uses 2 types of domains for different students.
stu.acischools.k12.tr for students enrolled after 2020
acischools.k12.tr for students enrolled pre 2020

Açı High School uses 2 types of domains for different students.
stu.acischools.k12.tr for students enrolled after 2020
acischools.k12.tr for students enrolled after 2020

@simitbey First stage of verification passed, official domain is acischools.k12.tr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@simitbey Thank you for your patience while waiting for a review and processing your request. Pull request merged.

thanks :)


add sonnen-charger to latest

https://github.com/ChrisWbb/ioBroker.sonnen-charger

First of all - THANK YOU for the time and effort you spend to maintain this adapter.
I would like to give some (preliminary) feedback based on my personal oppinion. This is NOT an offical review and @Apollon77 might have several additional suggestions or even a different oppinion to one or the other statement. Please feel free to contact him (or wait for a response from him) if you cannot follow my suggestsions or before you spend major effort.

Readme.md is very short
If you have some spare time, please consider adding some more infos to readme, especially a clear description what device(s) this adapter is for. Add a link to the manufactorers website i.e. Also a short description what kind of information / manipulation is possible.

Field _id:chargerSettings.serialNumber seems to be duplicated at io-package.json
https://github.com/ChrisWbb/ioBroker.sonnen-charger/blob/main/io-package.json#L168
https://github.com/ChrisWbb/ioBroker.sonnen-charger/blob/main/io-package.json#L181

Check onStateChange handling
It looks like your onStateChange code does not respect the ack flag.
Normally Adaptercode should only react on state changes issued with ack=false and ignore state changes with ack=true as long as it does not want to react on vales set by other adapters etc. Users should enter commands / set states with ack=false.
See https://forum.iobroker.net/topic/61876/bestätigt-acknowledged-flag-bedeutung-ein-mysterium?_=1680075857780 and eventually discuss this with @Apollon77

consider using adapter.setTimeout / this.setTimeout instead of (standard) setTimeout
The adapter package provides wrapper routines for native setTimeout, setInterval, clearTimeout and clearInterval. Using those routines ensures that timers are cancelled on onLoad. Additional checks on those limits might be performed, too. So consider replacing native setTimeout/clearTimeout by adapter.setTimeout/adapter.clearTimeout or this.setTimeout/this.clearTimeout. The same refers to setInterval/clearInterval.

Thanks for reading and evaluating these suggestions.
McM1957

Hello,
i want to test the adapter for the sonnen charger too.
But i dont't find the adapter in iobroker.
where can i download the adapter and how can i install the sonnen charger adapter on the rpi 4 / iobroker ?

Adapter repository: https://github.com/ChrisWbb/ioBroker.sonnen-charger
Currently only available via github installation in expert mode.
Thios adapter is not yet release as stable in repositories.
If you need further Instructions please ask at forum (forum.iobroker.net) or contact developer via adapter repository.
This PR is not the place to discuss adapter usage, issues or feature requests.

RE-CHECK!

Automated adapter checker
ioBroker.sonnen-charger

:thumbsup: No errors found

[ ] :eyes: [W400] Cannot find "sonnen-charger" in latest repository

Add comment "RE-CHECK!" to start check anew

"sonnen-charger": {
"meta": "https://raw.githubusercontent.com/ChrisWbb/ioBroker.sonnen-charger/master/io-package.json",
"icon": "https://raw.githubusercontent.com/ChrisWbb/ioBroker.sonnen-charger/master/admin/sonnen.png",    <<< wrong filename
"type": "energy"
},
@ChrisWbb - please fix PR, filename is OK as the picture normally is named identical to adapter

@mcm1957 But the image naming is no requirement and also not really a best practice ... no need to enforce that. so This is ok fpr me

@mcm1957 But the image naming is no requirement and also not really a best practice ... no need to enforce that. so This is ok fpr me

@Apollon77
I noticed that the icon url points to a non existing file. So EITHER the PR / icon url OR the filename need to be corrected.
This causes the github checks to fail (see screenshot) - so I think this must be corrected. It not about the name itself - it might by xtzrcs6if453hjc.jpg too as long as the url point to this file.

Or is this statement incorrect too? In this case sorry for the statements.
McM1957

This statement is meaning that the UR is wrong completely ... and the file is not there.
SO yes it needs to be changed to https://raw.githubusercontent.com/ChrisWbb/ioBroker.sonnen-charger/master/admin/sonnen-charger.png ... but not because the file needs to be named like the adapter ... but because the file was not there because it was an copy/paste error :-)

RE-CHECK!

Automated adapter checker
ioBroker.sonnen-charger

:thumbsup: No errors found

[ ] :eyes: [W202] Version of package.json (1.1.1) doesn't match latest version on NPM (1.1.0)
[ ] :eyes: [W400] Cannot find "sonnen-charger" in latest repository

ioBroker.frontier_silicon

:thumbsup: No errors found
ioBroker.logparser

:thumbsup: No errors found

[ ] :eyes: [W171] "common.title" is deprecated in io-package.json

Add comment "RE-CHECK!" to start check anew

RE-CHECK!

Automated adapter checker
ioBroker.sonnen-charger

:thumbsup: No errors found

[ ] :eyes: [W202] Version of package.json (1.1.1) doesn't match latest version on NPM (1.1.0)
[ ] :eyes: [W400] Cannot find "sonnen-charger" in latest repository

ioBroker.comfoair

:thumbsup: No errors found

[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

ioBroker.frontier_silicon

:thumbsup: No errors found
ioBroker.go-e

[ ] :heavy_exclamation_mark: [E144] common.installedFrom field found in io-package.json. Must be removed.
[ ] :heavy_exclamation_mark: [E405] Icon must be in the following path: https://raw.githubusercontent.com/MK-2001/ioBroker.go-e/main/
[ ] :heavy_exclamation_mark: [E407] Meta URL (latest) must be equal to https://raw.githubusercontent.com/MK-2001/ioBroker.go-e/main/io-package.json
[ ] :heavy_exclamation_mark: [E426] Icon (stable) must be in the following path: https://raw.githubusercontent.com/MK-2001/ioBroker.go-e/main/
[ ] :heavy_exclamation_mark: [E428] Meta URL (stable) must be equal to https://raw.githubusercontent.com/MK-2001/ioBroker.go-e/main/io-package.json
[ ] :heavy_exclamation_mark: [E506] More non translated in german or russian words found in admin/words.js. You can use https://translator.iobroker.in/ for translations
[ ] :eyes: [W171] "common.title" is deprecated in io-package.json
[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)

ioBroker.hm-rega

:thumbsup: No errors found

[ ] :eyes: [W171] "common.title" is deprecated in io-package.json
[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

ioBroker.homekit-controller

[ ] :heavy_exclamation_mark: [E142] logo is too big. It must be less or equal than 512x512
[ ] :heavy_exclamation_mark: [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: npm owner add bluefox iobroker.homekit-controller
[ ] :eyes: [W171] "common.title" is deprecated in io-package.json
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

ioBroker.kostal-piko-ba

:thumbsup: No errors found

[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI

ioBroker.logparser

:thumbsup: No errors found

[ ] :eyes: [W171] "common.title" is deprecated in io-package.json

ioBroker.loxone

:thumbsup: No errors found

[ ] :eyes: [W171] "common.title" is deprecated in io-package.json
[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)

ioBroker.meteoalarm

[ ] :heavy_exclamation_mark: [E606] Current adapter version 2.3.5 not found in README.md
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

ioBroker.puppeteer

[ ] :heavy_exclamation_mark: [E114] No adapter are allowed in the repo without admin support (set "common.noConfig = true" and "common.adminUI.config = none" if adapter has no configuration)
[ ] :heavy_exclamation_mark: [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: npm owner add bluefox iobroker.puppeteer
[ ] :heavy_exclamation_mark: [E518] "@alcalzone/release-script" is used, but ".releaseconfig.json" not found
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2023 Moritz Heusinger<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2023 Moritz Heusinger<EMAIL_ADDRESS>at the start of LICENSE
[ ] :eyes: [W171] "common.title" is deprecated in io-package.json
[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)

ioBroker.solarmanpv

:thumbsup: No errors found
ioBroker.statistics

:thumbsup: No errors found

[ ] :eyes: [W202] Version of package.json (2.3.1) doesn't match latest version on NPM (2.3.0)

ioBroker.vds2465-server

[ ] :heavy_exclamation_mark: [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: npm owner add bluefox iobroker.vds2465-server
[ ] :heavy_exclamation_mark: [E605] No actual year found in copyright. Please add "Copyright (c) 2023 Hirsch-DE<EMAIL_ADDRESS>at the end of README.md
[ ] :heavy_exclamation_mark: [E701] No actual year found in LICENSE. Please add "Copyright (c) 2023 Hirsch-DE<EMAIL_ADDRESS>at the start of LICENSE
[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W515] Why you decided to disable i18n support?
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

ioBroker.vis

:thumbsup: No errors found

[ ] :eyes: [W171] "common.title" is deprecated in io-package.json
[ ] :eyes: [W105] "common.titleLang" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W109] "common.desc" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W145] Each "common.news" should be translated into all supported languages (en, de, ru, pt, nl, fr, it, es, pl, uk, zh-cn)
[ ] :eyes: [W202] Version of package.json (2.0.29) doesn't match latest version on NPM (1.4.16)
[ ] :eyes: [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

Add comment "RE-CHECK!" to start check anew

RE-CHECK!

I would like to give some additional (preliminary) feedback based on my personal oppinion. This is NOT an offical review and @Apollon77 might have several additional suggestions or even a different oppinion to one or the other statement. Please feel free to contact him (or wait for a response from him) if you cannot follow my suggestsions or before you spend major effort.

[ ] reevaluate state roles
Only the values specified here (https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md) may be used as state roles. Do not invent new names as this might disturb the functionalyity of other adapters or vis.
In addition the roles MUST match the read/write functionality. As an example a role value.* requires that the state is a readable state. Input states (write only) should have roles like level.*. Please read the description carefully. States with role 'button' should (must) have attribute 'common.read=false' set. A button ( "Taster" in german only triggers when you press but else has no state), so it should also be not readable. This is also like HomeMatic does it. A switch has clear states true or false and so can be read.
As an example customMaxCurrent currently has role "indoicator" set. As this state is of type number and has a unit "A" assigned, this state seems to contain a value. So role value.current seesm to be appropiate. "numberOfPhases" is quite sure no indicator either. States with role indicator must have type boolen.
Please review roles. Those are i.e. used by tapyedetector and vis ans should match standards.

[ ] adapt testing to supported node releases
Consider adding node 20 tests unless you already know incompatibilities.
So the recommended testmatrix is [16.x, 18.x, 20.x],

Everything looks good to me.
Thanks for reading and evaluating this suggestions and sorry for the late / addition remarks. Please fix and/or comment I'll set the request to lgtm so that Apollon77 will continue asap.
McM1957
Please add a comment when you have reviewed and fixed the suggestionsor at least commented the suggestions and you think the adapter is ready for a re-review!

How shall we continue?
Please let us know if you plan zu fix the noted issues in the near future - or as an alterntive - like to discuss some / all of those points.

@mcm1957 : thanks for your review. I fixed your findings.

RE-CHECK!

@ChrisWbb
Looks goog now.
Please note that release 1.1.1 has not yet been published at npm

This adapter has been released to latest repository and should be visible within 24h maximum.
Please create a thread at https://forum.iobroker.net/category/91/tester titled like "Test Adapter  " to collect some user feedback and provide a link to this topic when requesting addition to stable repository later.
Note: If an other testing topic already exists, ist OK to continue using this topic too.


new group: Play Ransomware

host location
http://mbrlkbtq5jonaqkurjwmxftytyn2ethqvbxfu4rgjbkkknndqwae6byd.onion
group name
Play Ransomware
group information
Hi, can you please add "Play" to Ransomwatch? The group is relatively new, it started being active in mid 2022. It has a number of major victims, like BMW France or CH Media.
Here is their blog:
http://mbrlkbtq5jonaqkurjwmxftytyn2ethqvbxfu4rgjbkkknndqwae6byd.onion
Thanks,
Kamila
host
v1 (onion)
parser
No response

Hi @milxss, Play is already tracked in Ransomwatch, including that same leak site.
Here's their profile: https://ransomwatch.telemetry.ltd/#/profiles?id=play


Feat: Make cloudflare production ready

Changes

Fix: Cloudflare tunnel with new Multiplexing helper
Fix: Made Cloudflare configuration less confusing
Improve: Helper text for ssh and IP Address/Domain
Feat: Cleaned up manual configuration flow
Feat: Cleaned up automatic configuration flow
Thanks to GitHubs merge conflict editor some of the changes are on next via this commit https://github.com/coollabsio/coolify/pull/3506/commits/7aab44645f306552eb85f7381a81cac6927cc35f

Thank you for the PR!


Feature/effectiveness article

Thanks Armin
grammarly is very helpful, already using it. forgot it on this page...
didn't removed image from the assets, done now


API docs? examples? specs? integration tests?

Hello, thanks for your effort.
I can't seem to find any of the subj.
I'm considering using this (or alternatives) for simple embedded MQTT client-server communication.

Embedded as in embedded with OS or bare metal?

Embedded as in-process — building a tiny pre-auth MQTT bridge to... NATS at the moment.

https://docs.rs/rumq-client/0.1.0-alpha.9/rumq_client
https://github.com/tekjar/rumq/tree/master/rumq-client/examples

@tekjar Thank you, but the client is of less concern, there's a pretty lot of client implementations for Rust etc, I'm looking for an elaborate broker library, so I can manage sockets by myself and have callbacks for a subset of protocol events, e.g. a client sends subscribe and I want to reply with a deny if it fails some custom application logic or accept otherwise.

Ahh..Sorry the broker is not ready yet. We are working on a distributed broker in a private repo. There is a basic version in rumq-broker folder which doesn't have much documentation
See this for basic usage
https://github.com/tekjar/rumq/blob/master/rumq-cli/src/main.rs

There is an alpha release of broker. Feel free to reopen this if you are still interested


Check why we needed to add lots of React imports to the sample store project

I added React imports to basically all files until these errors disappeared:

See https://github.com/concrete-utopia/hydrogen-may/commit/e0510771076eee95e57b5a543b3cf3923d9cdc4c
But valid react projects should work without additional imports

Removing the imports and even rolling back my code a couple of days and I wasn't able to reproduce this...


Update link in https://github.com/thoughtbot/design-sprint README

The link in the README in https://github.com/thoughtbot/design-sprint should be updated to point to the new guide instead.

This is all set.


[Bug] Dicom Upload Button is not enabling

Describe the Bug
dicomUploadEnabled configuration was set to "true" but upload button is not showing in the desired page.
Steps to Reproduce

Opened "../platform/app/public/config/default.js"
Written dicomUploadEnabled in
dataSources: [
{
...
configuration: {
...
dicomUploadEnabled: true,
...
}
...
}
...
]

The current behavior
No Upload Button is showing
The expected behavior
Upload button should show as per the documentation
OS
Ubuntu
Node version
v16.20.2
Browser
Edge

This is the UI func shown in the docs.

But this is how UI is shown without upload button

i think it depends on your configuration. take a look at the google.js config that has the correct setup

I add "dicomputadEnabled：true，" in all .js files, but it's useless

@white1-doggy what is your backend dicom server?


Unable to upload images files as attachments when using summernoteinplacewidget

I am unable to upload files as attachments using the summernoteinplacewidget.   I have followed the instructions, and I have a row in my database, and the upload modal is displayed, and I can select an image, but nothing happens after that.

Same behavior. It happens in Chrome. I tried Safari and works well.

Try restart your browser and it works:


Document system requirements

Document system requirements for Teku. Fixes #399.

As a starting point, I'd say the minimum requirements for running a full node (Beacon Node + Validator):
CPU: 4+ cores @ 2.8+ GHz
Memory: 16GB+ RAM
Storage: SSD with at least 2TB free space
(similar to Prysm)


Remove /notebooks directory, as they moved to "tutorials" repo already

This directory should be removed

https://github.com/PyThaiNLP/pythainlp/tree/dev/notebooks

as they already moved to this repo: https://github.com/PyThaiNLP/tutorials
All future official tutorials (including Jupyter notebooks) should be at https://github.com/PyThaiNLP/tutorials

@artificiala I think we can do this as discussed. Can you make sure the tutorials will update from https://github.com/PyThaiNLP/tutorials? Not high priority.

Now, all the notebooks in PyThaiNLP/tutorials are the same as notebooks listed in PyThaiNLP/pythainlp/tree/dev/notebooks
We could remove the directory notebooks from this repo.


You must login to access this area.

Hi,
I have used flexi auth and CI on many application but not the latest CI3, and I usually on set $instant_activate = TRUE; and logs the user in. But for some reason, I can't get in ... I get the error above. Any suggestion?

Ill check this out and get back to you asap

Could you explain in detail what you have done:
are you using a copy of this download or trying to integrate it in an existing site ?

Well now I took a fresh installation and this is what I get:
A PHP Error was encountered

Severity: Notice

Message: Array to string conversion

Filename: core/Input.php

Line Number: 389

Backtrace:

File: /Applications/MAMP/htdocs/craigslist/application/models/Flexi_auth_model.php
Line: 2335
Function: set_cookie

File: /Applications/MAMP/htdocs/craigslist/application/models/Flexi_auth_model.php
Line: 1746
Function: regenerate_ci_session_id

File: /Applications/MAMP/htdocs/craigslist/application/models/Flexi_auth_model.php
Line: 1599
Function: set_login_sessions

File: /Applications/MAMP/htdocs/craigslist/application/libraries/Flexi_auth.php
Line: 61
Function: login

File: /Applications/MAMP/htdocs/craigslist/application/models/Demo_auth_model.php
Line: 152
Function: login

File: /Applications/MAMP/htdocs/craigslist/application/controllers/Auth.php
Line: 180
Function: register_account

File: /Applications/MAMP/htdocs/craigslist/index.php
Line: 292
Function: require_once

Maybe this is the issue Update the 'sess_use_database'? ... I have it here:
$config['sess_use_database'] = TRUE;
$config['sess_driver'] = 'database';
$config['sess_save_path'] = 'ci_sessions';
$config['sess_expiration'] = 7200;
$config['sess_match_ip'] = FALSE;
$config['sess_time_to_update'] = 300;

I suggest you read the CI3 documentation
$config['sess_use_database'] = TRUE;  is not used anymore

But what does this mean?
This step must be completed to all flexi auth installations. Update the 'sess_use_database' config setting to TRUE. This instructs CodeIgniter to save session data to the database rather than as a browser cookie. This is required as the auth session data is too big to store in a cookie.?

not in CI3 in  anymore read the ci doc mate
'sess_driver'
|
|	The storage driver to use: files, database, redis, memcached
|
| 'sess_cookie_name'
|
|	The session cookie name, must contain only [0-9a-z_-] characters
|
| 'sess_expiration'
|
|	The number of SECONDS you want the session to last.
|	Setting to 0 (zero) means expire when the browser is closed.
|
| 'sess_save_path'
|
|	The location to save sessions to, driver dependant.
|
|	For the 'files' driver, it's a path to a writable directory.
|	For the 'database' driver, it's a table name.
|	Please read up the manual for the format with other session drivers.
|
|	IMPORTANT: You are REQUIRED to set a valid save path!
|
| 'sess_match_ip'
|
|	Whether to match the user's IP address when reading the session data.
|
| 'sess_time_to_update'
|
|	How many seconds between CI regenerating the session ID.
|
| Other session cookie settings are shared with the rest of the application,
| except for 'cookie_prefix' and 'cookie_httponly', which are ignored here.
|
*/
$config['sess_driver'] = 'database';
$config['sess_save_path'] = 'ci_sessions';
$config['sess_expiration'] = 7200;
$config['sess_match_ip'] = FALSE;
$config['sess_time_to_update'] = 300;
thats my session info and working just downlowed my files and did fresh install on another server all is working

go to www.leap-it.be/test/

Yes I saw yours works and re-downloaded a new copy just now and installed the sql you had there, changed config url, database setting, .htaccess folder. I have done the other security setups like encryption_key since there optional.
I would expect this basic setup to work but still the same error. I'm sorry for disturbing you on this.

Contact me privately on<EMAIL_ADDRESS>thx

I'm getting the same notice error. Looks like its coming from
Flexi_auth_model.php
Line: 2335
Function: set_cookie

I get this too and can confirm CI3 setting are correct

I can't 100% remember my solution but I think one of my changes has to do with PHP version

What version are you using? I get the same notice on both 5.4 and 5.5.

I have 5.6, sorry but I can't really remember the fix :(

It's Working.....

great i will update to Ci 3.03 soon

Good Job Actually...

Thank's  a lot.......

you can get latest version from here http://www.leap-it.be/flexiauth

Is this still available? I am going to the above link, but requested URL is not found.

Yes ill fix the link. I have changed server latly.

Try https://www.leap-it.be/dev/flexiauth/
Let me know if all goes well

Hello,
I have exactly the same problem for the login flexiauth. This works with version 5.5 php but not with version 5.6. Do you find the problem after this discussion? Any suggestion? Thank you.

You have already answered this question. You have indicated a link to download the patch. But it does not work.

hi
I have same problem with   flexi_auth and CI 3   and  PHP  7
this is my conifg
$config['sess_driver'] = 'database';
$config['sess_save_path'] = 'ci_sessions';
$config['sess_expiration'] = 7200;
$config['sess_match_ip'] = FALSE;
$config['sess_time_to_update'] = 300;
and this is my error
A PHP Error was encountered
Severity: Notice
Message: Array to string conversion
Filename: core/Input.php
Line Number: 408
Backtrace:
File: /datas/faslebardasht/public_html/application/models/Flexi_auth_model.php
Line: 2335
Function: set_cookie
File: /datas/faslebardasht/public_html/application/models/Flexi_auth_model.php
Line: 1746
Function: regenerate_ci_session_id
File: /datas/faslebardasht/public_html/application/models/Flexi_auth_model.php
Line: 1599
Function: set_login_sessions
how can i fix  it ?

You could give this a try.
Note: is the full demo
https://github.com/Reconix/Flexi-Auth-CI3


⚠ Beamable Beamo (Basic) has degraded performance

In 6effeee, Beamable Beamo (Basic) (https://api.beamable.com/basic/beamo/platform/docs) experienced degraded performance:

HTTP code: 504
Response time: 10019 ms

Resolved: Beamable Beamo (Basic) performance has improved in 1ac1e56 after 11 minutes.


Dapr crypto scheme v1 (high level methods)

Description
This PR implements the Dapr crypto scheme v1, as defined in dapr/proposals#3
It includes the methods Encrypt and Decrypt which are high-level methods to encrypt and decrypt messages of arbitrary length (up to 256TB). These methods work on streams and don't hold more than 64KB of data in a buffer.
This PR includes extensive unit tests that cover all edge cases.
Example usage
To encrypt a message, you invoke the Encrypt method with a readable stream containing the plaintext data and an object containing options.
The most important option is WrapKeyFn, which is a function that, given a plaintext file key (randomly-generated by the Encrypt method), the name of a key in the vault, and the algorithm, returns the wrapped key. Callers are required to pass this method as a lambda, which will perform wrapping using a component (for example, Azure Key Vault).
enc, err := Encrypt(
    bytes.NewReader(message),
    EncryptOptions{
        WrapKeyFn: func(wrappedKey []byte, algorithm, keyName string, nonce, tag []byte) (plaintextKey jwk.Key, err error) {
            //…
        },
        KeyName:   keyName,
        Algorithm: algorithm,
    },
)

The method returns a readable stream enc which will have the data written to it.
The method does not accept a context because it is not needed when working with streams. Callers can stop the method by stopping the input stream. The WrapKeyFn should manage its context (for the network call) internally (i.e. inside the lambda).
The signature of the Decrypt method is similar, except it takes less options, with the only required one being an UnwrapKeyFn (same concept as key wrapping for Encrypt):
dec, err := Decrypt(
    enc,
    DecryptOptions{
        UnwrapKeyFn: unwrapKeyFn,
    },
)

Here too, enc is a readable stream to the encrypted document, and the returned dec is a readable stream containing the plaintext.
Issue reference
Tracked by: dapr/dapr#6147
Proposal: dapr/proposals#3
Checklist

[X] Code compiles correctly
[X] Created/updated tests

Codecov Report

Merging #42 (8d9a445) into main (efcc1af) will increase coverage by 0.54%.
The diff coverage is 82.77%.

@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
+ Coverage   80.01%   80.55%   +0.54%
==========================================
  Files          26       31       +5
  Lines        1481     1841     +360
==========================================
+ Hits         1185     1483     +298
- Misses        217      251      +34
- Partials       79      107      +28

Impacted Files
Coverage Δ

crypto/schemes/enc/v1/filekey.go
66.03% <66.03%> (ø)

crypto/schemes/enc/v1/scheme.go
85.31% <85.31%> (ø)

crypto/schemes/enc/v1/algorithms.go
100.00% <100.00%> (ø)

crypto/schemes/enc/v1/ciphers.go
100.00% <100.00%> (ø)

crypto/schemes/enc/v1/manifest.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@ItalyPaleAle there seems to be a flaky test in here. Can you take a look?

@mukundansundar looks like there was a bug in the crypto code but not in what was added with this PR. Fixed here: https://github.com/dapr/kit/pull/44

@ItalyPaleAle not completely finished the code part of the review, but thought it was worth sending my comments about the design early :slightly_smiling_face:

I recommend not marking comments as resolved unless the reviewer agrees or is unresponsive.


Family Table write needs to consider the pedigree when determining which families to update.

We had a behavior regression at some point and are only using the list of families present on the project table, instead we need to set union with the pedigree.

This was a behavior change/regression from this optimization pr

Resolved


UI is broken

commit: [22bcc7be]
I updated extension and now my UI is not the same as before

See #146.
TL;DR:

Make sure your webui itself is also updated
Update your other extensions, especially openpose-editor since older versions broke other extensions.


add fluid craft pattern terminal prioritize mode support

add fluid craft pattern terminal prioritize mode support

@GlodBlock could you pls help me rebuild

@GlodBlock

push the spotless apply here


[WIP] update gomobile

@chrisnojima talk about cutting test builds with this tomorrow?

The CircleCI failure is due to some weird interaction with Alpine Linux in the Docker Image. Still trying to fix...

This is ready for review now. Will do a test build with go 1.10 on Monday. r? @keybase/react-hackers


Sensor Extension

The prototype supports only the geolocation and mic sensor of the phones, but there are a lot more browser APIs we can use. With the help of project fugu there are a lot improvements that comes to the browsers like the already implemented Generic Sensor API to get a more uniform behavior through different device sensors. More sensor APIs will be on the way using the new Generic Sensor API like the Ambient Light Sensor or the Proximity Sensor.
List of available Sensors with APIs:

[x] Microphone
[ ] #25
[x] Geolocation: Geolocation API https://www.webondevices.com/9-javascript-apis-accessing-device-sensors/#geolocation-api
[x] Accelerometer
[x] Gyroscope
[x] LinearAccelerationSensor
[x] AbsoluteOrientationSensor
[x] RelativeOrientationSensor
[x] GravitySensor
[x] Magnetometer
[x] Device Light: Device Light API https://www.webondevices.com/9-javascript-apis-accessing-device-sensors/#device-light-api
[x] Battery: Battery Manager API https://www.webondevices.com/9-javascript-apis-accessing-device-sensors/#battery-manager-api
[ ] Proximity: Proximity Events API https://www.webondevices.com/9-javascript-apis-accessing-device-sensors/#proximity-events-api
% TODO: add api links

Can be closed because sensors are implemented and camera is tracked by another sensor.
Proximity sensor is highly experimental. So will not include that.


Port base OS image change from photon to scratch

This will reduce our CVE burden greatly by not including a full OS where it's not needed.

Mostly copied from https://github.com/vmware-tanzu/carvel-secretgen-controller/pull/76/


Avoid unnecessarily calling slower functions

For example, in strcpy (ignoring the UB overlapping check):
https://github.com/jvoisin/fortify-headers/blob/9aa4490263ead62dc545cf0e8b83e0ef77eb7a6e/include/string.h#L139-L150
By the time, __orig_strcpy is called, the length has already been computed and has been established to be in bound. There's no need to pay for the nul-byte search again inside of __orig_strcpy when the faster memcpy can be called instead.
Some of the other str* functions suffer from the same issue.

The rationale behind this was that maybe other things were "hooking" strcpy, but you're right, a call to memcpy makes sense.


⚠ Bofrost.be has degraded performance

In 9ffd36c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1589 ms

Resolved: Bofrost.be performance has improved in 4d88b0d.


suggestion：希望可以自定义显示哪些选项，及顺序。

比如首页这里的个性推荐、正在关注、····
我想首先显示正在关注的，随后可以手动选择个性推荐，另外后边的订阅剧集则是我不需要的。

另外还有侧边栏的按钮，这个到是可以进行排序，但目前不能取消某一个的显示，比如取消番剧。

is anyone doing this, i want do it

is anyone doing this, i want do it

if you wanna add this feature, please use the dev branch for implementation :)

It's coming soon

is anyone doing this, i want do it

if you wanna add this feature, please use the dev branch for implementation :)

I have completed it, waiting merge

It's coming soon

Could you remove the default home tab configuration? Just like the dock content configuration, the first tab will become the default tab on the homepage

It's coming soon

Default home tab configuration might not be important, just like the dock content configuration, the first tab will become the default tab on the homepage

completed it


Feature: jinja templating in doc

E.G:
Your cluster {{ instance.spec.cluster.name }} is now online.
You can use SSH in address  {{ instance.spec.cluster.ip }}

Done and merged in dev branch


Typing , and hitting enter inserts result from code completion (too aggressive)

Consider this case:
Map data = {
  'one': 1,
  'two': 2// <== right here, put a comma and then hit enter
};

Expected: a comma and cursor inserted into next line
Actual: code completion window pops up, and enter selects the top result, and the result is inserted.

cc @iposva-google

Curious if we can bump up the priority.
Code completion is pretty aggressive. Also happens at the end of lines, too often.
We're hitting Escape (to disable the code completion) too often...
Thanks for taking a look!

I'll put a fix in for the completion auto-delay. I suspect there's a bigger issue where atom autocomplete-plus UI is not really expecting latency in the returned completions, and the analysis server has some non-zero latency.

This is possibly number one issue. I am not sure about it but is it possible to call autocompletion with ctrl+space only (i.e. disable it while regular typing) until this is fixed?

There's a setting in the autocomplete-plus package to control just this. We've gotten a lot of feedback about this issue. It may be the right call to disable auto-triggering, at least for dart files.

Did we ever disable auto-triggering for Dart files?

We:

disable auto-completion in certain unlikely places (immediately after ; or ,)
change the default delay from 100ms to 500ms

We experimented with disabling autocompletion completely for dart files, but got feedback that this was on the whole undesired.

Sgtm thanks for the update


no expression type for OpSRem

fix issue#582

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Merged. I committed the test results on top since the SPIR-V was slightly wrong. Thanks!


Watch option does not reload the actual changed file

Running mocha with the --watch option will only reload the tests sources, and never reload changes in the application's source files. It means that it is actually impossible to fix the offending application code while running in watch mode. I assume this is not the desired behavior :-)
Attached commit fixes this by removing the changed file from the require-cache before re-running the suite.

haha, this is what happens when I dont use the feature at all :D

actually no, this doesn't fix anything, you're still not require()ing it af

Oh, thats a good point! Yeah, guess this would only reload changed files as long as they are require'd directly from one of the tests.
Anyways, that means the watcher feature is still kinda broken. Any ideas on how to fix it?

we'll have to walk the .parent properties and kill the cache for all of them

That will still not work quite as it should. Consider the following example:
in bar.js:
exports.foo = require("./foo");

in test/foo.js:
var foo = require('./bar').foo
// (...) tests for foo

Now changes to foo.js will not be reloaded and the test will fail somewhat unexpectedly until bar.js is changed...
IMHO, a better solution would be to invalidate cache for all watched files. I've done this already in my fork, here: https://github.com/bjoerge/mocha/commit/d256ad7602d4fa35b1d0c0b615f78bf0173641c4.
Let me know if you'd like me to send a new pull request.

yeah that would be fine too, no point with the while/shift though we can just forEach them

Same here, my project is split into several node_modules and anything in another module won't ever get reloaded.

@jareware you will want to investigate other options.
@mochajs/mocha what if we threw a "DEPRECATED" label on --watch in the docs?  This would make me happy.

@boneskull yeah I get that feeling reading any issues related to watching here... :) The sad part is when you're e.g. transpiling a large codebase with Babel, the --watch method is a lot faster than an external watch tool (I've been using https://github.com/kimmobrunfeldt/chokidar-cli for that), as it only recompiles changed modules. Whereas the external one will just start from scratch every time.


fludex package neither show flutter icon on pub nor listed under flutter packages

https://pub.dartlang.org/search?q=fludex
Tried this solution, yet facing same issue.
output of pub publish --dry-run :
Publishing fludex 0.0.3 to https://pub.dartlang.org:
|-- .gitignore
|-- CHANGELOG.md
|-- LICENSE
|-- README.md
|-- fludex.iml
|-- lib
|   '-- fludex.dart
|-- pubspec.yaml
'-- test
    '-- fludex_test.dart

Package has 0 warnings.

The latest issue in analysis:
Incompatible version constraints on meta:
- fludex depends on version ^1.1.2
- flutter 0.0.37 depends on version 1.1.1

I guess my version constraint were too optimistic, if you set it to 1.1.1, it shall work. Please do a flutter packages pub upgrade before publishing, to check if the constraints resolve properly.

Tried setting meta to 1.1.1 and also did flutter packages pub upgrade . It's not working.

What's the output?

for flutter packages pub upgrade :
Resolving dependencies...
  analyzer 0.30.0+4 (0.31.0-alpha.1 available)
  args 1.0.2
  async 1.13.3 (2.0.1 available)
  barback 0.15.2+13
  boolean_selector 1.0.2
  charcode 1.1.1
  cli_util 0.1.2+1
  collection 1.14.3
  convert 2.0.1
  crypto 2.0.2+1
  csslib 0.14.1
  flutter 0.0.38-dev from sdk flutter
  front_end 0.1.0-alpha.4.1 (0.1.0-alpha.6 available)
  glob 1.1.5
  html 0.13.2
  http 0.11.3+14 (0.11.3+16 available)
  http_multi_server 2.0.4
  http_parser 3.1.1
  io 0.3.0
  isolate 1.1.0
  js 0.6.1
  kernel 0.3.0-alpha.1.1 (0.3.0-alpha.3 available)
  logging 0.11.3+1
  matcher 0.12.1+4
  meta 1.1.1 (1.1.2 available)
  mime 0.9.4
  node_preamble 1.4.0
  package_config 1.0.3
  package_resolver 1.0.2
> path 1.5.0 (was 1.4.2)
  plugin 0.2.0+2
  pool 1.3.3
  pub_semver 1.3.2
  shelf 0.7.1
  shelf_packages_handler 1.0.3
  shelf_static 0.2.6
  shelf_web_socket 0.2.2
  sky_engine 0.0.99 from path ../../flutter/bin/cache/pkg/sky_engine
  source_map_stack_trace 1.1.4
  source_maps 0.10.4
  source_span 1.4.0
> stack_trace 1.9.1 (was 1.9.0)
  stream_channel 1.6.2
  string_scanner 1.0.2
  term_glyph 1.0.0
> test 0.12.27+1 (was 0.12.27)
  typed_data 1.1.4 (1.1.5 available)
  utf 0.9.0+3
  vector_math 2.0.5
  watcher 0.9.7+4
  web_socket_channel 1.0.6
  yaml 2.1.13
Downloading test 0.12.27+1...
Downloading path 1.5.0...
Downloading stack_trace 1.9.1...
tar: Failed to set default locale
tar: Failed to set default locale
tar: Failed to set default locale
Changed 3 dependencies!
Precompiling executables...
Precompiled test:test.

pub publish  --dry-run :
Publishing fludex 0.0.4 to https://pub.dartlang.org:
|-- .gitignore
|-- CHANGELOG.md
|-- LICENSE
|-- README.md
|-- fludex.iml
|-- lib
|   '-- fludex.dart
|-- pubspec.yaml
'-- test
    '-- fludex_test.dart

Package has 0 warnings.

Ah, got it from analysis, it is not the publish part that is not working. Your code seem to have a static type warning:  {"severity":"ERROR","errorType":"STATIC_TYPE_WARNING","errorCode":"UNDEFINED_GETTER","file":"lib/fludex.dart","line":58,"col":57,"description":"The getter 'type' isn't defined for the class 'Object'."}
You need to cast Object to Action (with a type check ideally), otherwise it will not work in strong mode. If you create an analysis_options.yaml file with the following content, you can check it for yourself:
analyzer:
  strong-mode: true
# Source of linter options:
# http://dart-lang.github.io/linter/lints/options/options.html
linter:
  rules:
    - camel_case_types
    - hash_and_equals
    - iterable_contains_unrelated_type
    - list_remove_unrelated_type
    - unrelated_type_equality_checks
    - valid_regexps

In the project dir:
dartanalyzer .

That was really helpful. Thanks. Up and working now.


Render error output name and message always

For #6929

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #6931 (a825978) into main (c13fe7f) will increase coverage by 0%.
The diff coverage is n/a.

:exclamation: Current head a825978 differs from pull request most recent head 1754174. Consider uploading reports for the commit 1754174 to get more accurate results

@@          Coverage Diff          @@
##            main   #6931   +/-   ##
=====================================
  Coverage     65%     65%
=====================================
  Files        410     410
  Lines      28525   28525
  Branches    4263    4263
=====================================
+ Hits       18560   18577   +17
+ Misses      8332    8314   -18
- Partials    1633    1634    +1

Impacted Files
Coverage Δ

src/client/terminals/codeExecution/helper.ts
13% <0%> (-6%)
:arrow_down:

...datascience/editor-integration/codelensprovider.ts
67% <0%> (-3%)
:arrow_down:

...client/datascience/kernel-launcher/kernelDaemon.ts
53% <0%> (-2%)
:arrow_down:

...lient/datascience/variablesView/notebookWatcher.ts
90% <0%> (-2%)
:arrow_down:

.../datascience/editor-integration/codeLensFactory.ts
67% <0%> (-1%)
:arrow_down:

...t/datascience/notebook/vscodeNotebookController.ts
79% <0%> (-1%)
:arrow_down:

src/client/datascience/baseJupyterSession.ts
65% <0%> (-1%)
:arrow_down:

src/client/datascience/jupyter/kernels/helpers.ts
73% <0%> (-1%)
:arrow_down:

...ient/datascience/editor-integration/codewatcher.ts
67% <0%> (-1%)
:arrow_down:

src/client/datascience/jupyter/kernels/kernel.ts
63% <0%> (+<1%)
:arrow_up:

... and 8 more


Update http client package to resolve build failure

Signed-off-by: Heemin Kim<EMAIL_ADDRESS>Description
org.apache.http package was migrated to org.apache.hc.core5.http in OpenSearch core.
Issues Resolved
Current build failure
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #168 (efc8b7e) into main (89b676a) will not change coverage.
The diff coverage is 66.66%.

@@            Coverage Diff            @@
##               main     #168   +/-   ##
=========================================
  Coverage     85.13%   85.13%
  Complexity      320      320
=========================================
  Files            44       44
  Lines          1063     1063
  Branches         86       86
=========================================
  Hits            905      905
  Misses          124      124
  Partials         34       34

Impacted Files
Coverage Δ

...eospatial/stats/upload/UploadStatsNodeRequest.java
0.00% <ø> (ø)

...geospatial/index/mapper/xypoint/XYPointParser.java
70.76% <50.00%> (ø)

...earch/geospatial/index/mapper/xypoint/XYPoint.java
74.13% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[YUNIKORN-1215] multi architecture build

What is this PR for?
Makefile and docker update to support multi architecture build
What type of PR is it?

[X] - Feature

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1215
How should this be tested?
Part of the release process normal build should not be affected

Successfully built all 4 architectures from amd64 mac w/Docker Desktop, amd64 debian linux w/ docker, and arm64v8 debian linux w/ docker:
$ make REGISTRY=local image && \
make REGISTRY=local DOCKER_ARCH=amd64 image && \
make REGISTRY=local DOCKER_ARCH=i386 image && \
make REGISTRY=local DOCKER_ARCH=arm64v8 image &&
make REGISTRY=local DOCKER_ARCH=arm32v7 image

$ docker images | grep yunikorn
local/yunikorn   web-arm32v7-latest   56a9fdd0ace4   12 minutes ago   17.5MB
local/yunikorn   web-arm64v8-latest   fa616d032d9d   12 minutes ago   23.5MB
local/yunikorn   web-i386-latest      03dfd3709dc6   12 minutes ago   25MB
local/yunikorn   web-amd64-latest     a2f4e0f2e2fc   14 minutes ago   24.8MB

NOTE: For the debian linux systems, it was neceessary to install the qemu-user-static package to enable foreign architecture emulation.


Create job app

Creating job model.
Migrating the jobs model.
Adding basic tests to the model.
Registering the jobs model to admin.

I will create tomorrow a new PR with the necessary changes. @AshkenYariv