Invariant Violation: "app" has not been registered  - AppRegistry.js | runnables[appKey] is undefined

Description
After upgrading to 0.69 and upgrading a lot of packages, I'm not able to build Android anymore.
With iOS, there is no problem but Android is impossible to build.
A simple react-native run-android launch the app on the phone, but the app won't appear. I only got this error :
ExceptionsManager.js:149 Invariant Violation: "app" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.

So, after some search, I found the AppRegistry.js file (node_modules/eact-native/Librairies/ReactNative). There is a const named runnables[appKey], and with iOS, this show me a lot of informations, but with Android, I only got undefined.
Someone has the same problem ?
Version
0.69.0
Output of npx react-native info
System:

OS: macOS 12.6
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 116.24 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash

Binaries:

Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.17 - ~/Documents/myFiles/myProject/node_modules/.bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

Managers:

CocoaPods: 1.11.3 - /usr/local/bin/pod

SDKs:

iOS SDK:

Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3

Android SDK:

Android NDK: 22.1.7171670

IDEs:

Android Studio: 2022.1 AI-221.6008.13.2211.9514443
Xcode: 13.2/13C90 - /usr/bin/xcodebuild

Languages:

Java: 19.0.2 - /usr/bin/javac
Python: Not Found

npmPackages:

@react-native-community/cli: ^4.13.0 => 4.14.0
react: ^18.2.0 => 18.2.0
react-native: ^0.69.0 => 0.69.0
react-native-macos: Not Found

npmGlobalPackages:

react-native: Not Found

Steps to reproduce
Upgrade React-Native to 0.69, and do react-native run-android.
Snack, code example, screenshot, or link to a repository
The error is here :
  runApplication(
    appKey: string,
    appParameters: any,
    displayMode?: number,
  ): void {
    if (appKey !== 'LogBox') {
      const logParams = __DEV__
        ? '" with ' + JSON.stringify(appParameters)
        : '';
      const msg = 'Running "' + appKey + logParams;
      infoLog(msg);
      BugReporting.addSource(
        'AppRegistry.runApplication' + runCount++,
        () => msg,
      );
    }
    invariant(
      runnables[appKey] && runnables[appKey].run,
      `"${appKey}" has not been registered. This can happen if:\n` +
        '* Metro (the local dev server) is run from the wrong folder. ' +
        'Check if Metro is running, stop it and restart it in the current project.\n' +
        "* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.",
    );
    SceneTracker.setActiveScene({name: appKey});
    runnables[appKey].run(appParameters, displayMode);
  },

Can you please share the contents of the index.js file at the root of the project?
The error usually points to the code below which is found at <root folder>/index.js. Also from version did you upgrade?
// index.js
import {AppRegistry} from 'react-native';
import App from './App';
import {name as appName} from './app.json';

AppRegistry.registerComponent(appName, () => App); // <- this line

Can you please share the contents of the index.js file at the root of the project?
The error usually points to the code below which is found at <root folder>/index.js. Also from version did you upgrade?
// index.js
import {AppRegistry} from 'react-native';
import App from './App';
import {name as appName} from './app.json';

AppRegistry.registerComponent(appName, () => App); // <- this line

Yes, I point to index.andoird.js and here it is :
import './src/Business/Config/ReactotronConfig'
import { AppRegistry } from 'react-native'
import App from './src/mobile/App/Containers/App'

AppRegistry.registerComponent("appName", () => App)

Btw, my file index.ios.js is exactly the same and work fine

What else have you tried to fix this error?
Side note: https://github.com/facebook/react-native/commit/57774a4a981e2f12cfe9b029447e34f203221b18
./app.json
{
  "name": "AwesomeApp",
  "displayName": "AwesomeApp"
}

I still facing this issue while upgraded to react native 0.71.4 from 0.64 any solution for this issue I tried lots of solutions which are

Matched project name in app.json
also ensure in MainActivity getMainComponentName has match with app.json
also ensure metro bundler running from proper folder
also ensure previous app is deleted from mobile
also ensure project file name was match with app.json and MainActivity names

index.js file

 import 'react-native-gesture-handler';
 import {AppRegistry, LogBox} from 'react-native';
 import {name as appName} from './app.json';
 AppRegistry.registerComponent(appName, () => App);

app.json file

{
   "name": "appname",
   "displayName": "displayName",
   "react-native-google-mobile-ads": {
   "android_app_id": "key"
  }
}

MainActivity.java file
ensuring match with app.json with this file

  @Override
    protected String getMainComponentName() {
        return "appname";
    }

Hey @vikil143  your index.js file is missing the import for App. If it still doesn't work, it would be easier to help you if you please provide a reproducer.

@carlosalmonte04 Thanks for the quick reply but you said its not a case I'm forgotten to mention this in the code so reproducer means how can I do it can you explain, please

This issue was cleared successfully. So anyone wants to resolve this make sure the below points are cleared

First match In app.json name as the same name in MainActivity.java return value of getMainComponentName
Second try to debug code by commenting in the entry(which is index.js or App.js) file check this where is exactly the main problem
My problem was I updated the app and all required packages but one function was deprecated in redux which is createStore by solving this resolved my issue

I'm facing the same issue with react-native 0.71.7. Not using redux createStore in my case. The index.js, app.json and MainActivity re same as above. Any quick help?

Can you send some more details like what are trying to do and what you did?

import { AppRegistry } from 'react-native';
index.js:
import main from './app';
import {name as appName} from './app.json';
AppRegistry.registerComponent(appName, () => main);
export default main;
app.json:
{
"name": "main",
"displayName": "main"
}
MainActivity:
@Override
protected String getMainComponentName() {
return "main";
}
These are the files I'm using. Checked the naming. It is same in all the files. Debugged the code , In AppRegistry Im getting appKey as undefined.

This error also caused when you running metro bundler of different project is not closed. So try to kill all metro bundlers as well as restart your PC check once

@TomJerry56  What was cause this issue appear?

@TomJerry56 What was cause this issue appear?

Updated react-native to 0.71, react to 18, gradle to 7, node to 16 and its respective dependencies

@TomJerry56 bro what I did after working lot with issue is debugging from index file commenting root codes (means top level code) and cross checking the app run's properly or not please try this

@vikil143 Tried debugging the issue, Understood that the issue is due to the 'require' statements in the js files. The error is thrown wherever export/import is used in tsx files ie; require in compiled js files. Trying to resolve it.

@TomJerry56 great happen coding

@vikil143 Tried debugging the issue, Understood that the issue is due to the 'require' statements in the js files. The error is thrown wherever export/import is used in tsx files ie; require in compiled js files. Trying to resolve it.

@TomJerry56 Could you please clarify precisely what resolved it??

@artemis-prime Still it is not resolved.

in my case, there were 2 files left from the previous developer and for a long time I could not understand the cause of the error

Here we have App.js and index.js with this code in index.js
// This is the first file that ReactNative will run when it starts up. // If you use Expo (yarn expo:start`), the entry point is ./App.js instead.
// Both do essentially the same thing.
import App from "./app/app.tsx"
import React from "react"
import { AppRegistry } from "react-native"
import RNBootSplash from "react-native-bootsplash"
function IgniteApp() {
return
}
AppRegistry.registerComponent("main", () => IgniteApp)
export default App`
and code in App.js
`import App from "./app/app.tsx"
import React from "react"
import { registerRootComponent } from "expo"
import { Platform } from "react-native"
import * as SplashScreen from "expo-splash-screen"
SplashScreen.preventAutoHideAsync()
function IgniteApp() {
return
}
if (Platform.OS !== "web") {
registerRootComponent(IgniteApp)
}
export default IgniteApp`
when a build is created, expo refers to App.js and does not see the AppRegistry.registerComponent there, to solve the problem, it is enough to replace all the code in App.js with the code from Index.js and everything will work

@egarikka solution works. I am using ignite-cli with RN 0.71. In the debug build it works fine, but on the release build it crashes. The release build references the .App.js file which does not have the AppRegistry declaration instead of the .index.js file. Just make sure that both files are the same. Hope this helps anyone scaffolding with ignite-cli

@DaraUkpong It absolutely worked. Shall we raise an issue in ignite's boilerplate? If I didn't come across your comment I would have never figured it out. How did you found out about this?

@DaraUkpong It absolutely worked. Shall we raise an issue in ignite boilerplate? If I didn't come across your comment I would have never figured it out. How did you manage to find it?

I had to take a close look of where the app  was actually reading it's entry point from using the Android Studio logging tool. On both builds it read from app.js or index.js(release and dev build). I just had to make sure both had the same content.
At the time I just needed a solution the problem, I haven't researched as to why that was happening given that I had no prior interaction with those files.
An Issue - Yes that will work. I've not tried the new update to confirm if it's something that has been resolved. You trying to solve this issue  at this time means it probably hasn't.

in my case, there were 2 files left from the previous developer and for a long time I could not understand the cause of the error  Here we have App.js and index.js
with this code in index.js
// This is the first file that ReactNative will run when it starts up.
// If you use Expo (`yarn expo:start`), the entry point is ./App.js instead.
// Both do essentially the same thing.

import App from "./app/app.tsx"
import React from "react"
import { AppRegistry } from "react-native"
import RNBootSplash from "react-native-bootsplash"

function IgniteApp() {
  return <App hideSplashScreen={RNBootSplash.hide} />
}

AppRegistry.registerComponent("main", () => IgniteApp)
export default App

and code in App.js
import App from "./app/app.tsx"
import React from "react"
import { registerRootComponent } from "expo"
import { Platform } from "react-native"
import * as SplashScreen from "expo-splash-screen"

SplashScreen.preventAutoHideAsync()

function IgniteApp() {
  return <App hideSplashScreen={SplashScreen.hideAsync} />
}

if (Platform.OS !== "web") {
  registerRootComponent(IgniteApp)
}

export default IgniteApp

when a build is created, expo refers to App.js and does not see the AppRegistry.registerComponent there, to solve the problem, it is enough to replace all the code in App.js with the code from Index.js and everything will work

Hi guys
I want to let you know that you can achieve this solution more efficiently. For projects created by Ignite, there is a main property in their package.json that references to AppEntry of the expo, so if you run or build your project with expo there is no issue, but if you try to run the project by react-native run-android the index.js will be used instead of App.js. but if you try to build your app with Android Studio the Android Studio uses the main property of package.json for finding the app entry and because the final APK can not find the js bundle, you just need to remove this line from package.json without touching the App.js and index.js

in my case, there were 2 files left from the previous developer and for a long time I could not understand the cause of the error  Here we have App.js and index.js
with this code in index.js
// This is the first file that ReactNative will run when it starts up.
// If you use Expo (`yarn expo:start`), the entry point is ./App.js instead.
// Both do essentially the same thing.

import App from "./app/app.tsx"
import React from "react"
import { AppRegistry } from "react-native"
import RNBootSplash from "react-native-bootsplash"

function IgniteApp() {
  return <App hideSplashScreen={RNBootSplash.hide} />
}

AppRegistry.registerComponent("main", () => IgniteApp)
export default App

and code in App.js
import App from "./app/app.tsx"
import React from "react"
import { registerRootComponent } from "expo"
import { Platform } from "react-native"
import * as SplashScreen from "expo-splash-screen"

SplashScreen.preventAutoHideAsync()

function IgniteApp() {
  return <App hideSplashScreen={SplashScreen.hideAsync} />
}

if (Platform.OS !== "web") {
  registerRootComponent(IgniteApp)
}

export default IgniteApp

when a build is created, expo refers to App.js and does not see the AppRegistry.registerComponent there, to solve the problem, it is enough to replace all the code in App.js with the code from Index.js and everything will work

I don't use expo so this might not work for me.
Has anyone using beare RN workkflow been able to resolve this?

in my case, there were 2 files left from the previous developer and for a long time I could not understand the cause of the error  Here we have App.js and index.js
with this code in index.js
// This is the first file that ReactNative will run when it starts up.
// If you use Expo (`yarn expo:start`), the entry point is ./App.js instead.
// Both do essentially the same thing.

import App from "./app/app.tsx"
import React from "react"
import { AppRegistry } from "react-native"
import RNBootSplash from "react-native-bootsplash"

function IgniteApp() {
  return <App hideSplashScreen={RNBootSplash.hide} />
}

AppRegistry.registerComponent("main", () => IgniteApp)
export default App

and code in App.js
import App from "./app/app.tsx"
import React from "react"
import { registerRootComponent } from "expo"
import { Platform } from "react-native"
import * as SplashScreen from "expo-splash-screen"

SplashScreen.preventAutoHideAsync()

function IgniteApp() {
  return <App hideSplashScreen={SplashScreen.hideAsync} />
}

if (Platform.OS !== "web") {
  registerRootComponent(IgniteApp)
}

export default IgniteApp

when a build is created, expo refers to App.js and does not see the AppRegistry.registerComponent there, to solve the problem, it is enough to replace all the code in App.js with the code from Index.js and everything will work

I don't use expo so this might not work for me. Has anyone using beare RN workkflow been able to resolve this?

Resolved by deleting the build on my emulator and creating another build.

Resolved by deleting the build on my emulator and creating another build.

I am facing the same issue on iOS and react-native:0.73.2.
I am using bare RN workflow. and also facing the same issue.
I was used ”create-react-native-library“ to create a turbo module. After I use "npx react-native@latest run-ios --udid xxxx" to build application on my iphone. react-native version was upgrad to v0.74.3. On my iphone device I get 2 Error:
Invariant Violation: new NativeEventEmitter() requires a non-null argument.
`Invariant Violation: "CppTurboExample" has not been registered. This can happen if:

Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
A module failed to load due to an error and AppRegistry.registerComponent wasn't called.`

I am double check my appname.
vs code => "root folder/example/app.json" . My appname is "CppTurboExample"
xcode => "root folder/../AppDelegate.mm". the line 9 code is "self.moduleName = @"CppTurboExample";"
so my appname is looks same.
According to the following article. There are two best ways to fix it.
 Then Build your app.
2.4.If these 3 fail, audition for a role on Living Alaska and become one with the wild

Bad import in App.js or App.tsx will trigger this error.
For example, when upgrading librairies some import breaking changes can happen :
import Component from ../path
But now with the breaking change it is :
import { Component } from ../path
Try to comment out imports one by one and see if one comment clear the error. Then you just have to find documentation about the lib that triggers the error.
I had this error while upgrading React Native and I fixed it this way !
It has nothing to do with appname.

Bad import in App.js or App.tsx will trigger this error.
For example, when upgrading librairies some import breaking changes can happen :
import Component from ../path
But now with the breaking change it is :
import { Component } from ../path
Try to comment out imports one by one and see if one comment clear the error. Then you just have to find documentation about the lib that triggers the error.
I had this error while upgrading React Native and I fixed it this way !
It has nothing to do with appname.

Thanks a lot 🚀. I had to do the same, and in our case, it was an outdated version on react-native-code-push that was causing the problem.

Bad import in App.js or App.tsx will trigger this error.
For example, when upgrading librairies some import breaking changes can happen :
import Component from ../path
But now with the breaking change it is :
import { Component } from ../path
Try to comment out imports one by one and see if one comment clear the error. Then you just have to find documentation about the lib that triggers the error.
I had this error while upgrading React Native and I fixed it this way !
It has nothing to do with appname.

You saved me. After 3 hours of debugging, finally, the issue was due to the import issue in App.tsx. The error message definitely misleading.


update java and grade version

Hi @Bastian-Eisenmann, usually java tests should also run on smaller java versions, maybe you can have a look if gradle 8.11 has any requirements which are not met? If not, you can als try to increment the CI tests to other versions, or at least the higher version to java 23 👍

Hi,
in my previous project we tried to keep the java & tools versions as high as possible (often also with some kind of ci/cd automatic update) and also parallel at all parts of the project.
On my pc was java version 23 installed which hasn´t worked with the given config because gradle 8.9 is not compatible to java 23 (https://docs.gradle.org/current/userguide/compatibility.html) - however, with installing a lower java version the current configuration does probably work.
I can also undo the commit 3c447e2 but would keep the gradle version update so that there will be no problems when java version 23 is used.

If the version work together, I'm fine with upgrading! I aligned the versions to nextflow, but also they incremented to gradle 8.10 since then! Do you know if grade is backwards compatible with older java versions?

That did not work, have you followed the instructions in the details of the CI test? Would you mind opening a new branch and PR so we do not blow up the commits for a version bump? 😆

I did but seems like the final commit was again without that signing message... yeah, I will just create a new one, that should finally work :-)


Chef 17 fixes

Signed-off-by: Brett Pemberton<EMAIL_ADDRESS>Description
Enables unified_mode for all resources to fix deprecation warnings in chef-client v17
Issues Resolved
Check List

[X] A summary of changes made is included in the CHANGELOG under ## Unreleased
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable.

Hi,  Would you be willing to clean up the linting.  I think delivery needs to be replaced by lint-unit in .github/workflows/ci-yml
Something like.
lint-unit:
uses<EMAIL_ADDRESS>

Thanks for fixing the delivery issue.  It looks like a clean cook style run is required too.  Painful.  I was afraid of that.

/spec/unit)/recipes/default_spec.rb has tests for many different types of OS.  None of the code that I saw is sensitive to the type of server though.  I'd be good with deleting most of the tests for different OS versions.  If the amazon and fedora tests are removed the cookstyle check will probably pass.

Released as: 3.0.0


AB Test

我想了解下，基于apisix能不能实现基于uid的ab test

sure, APISIX can do AB test.
where is your uid? in the http header, uri args or post body?

sure, APISIX can do AB test.
where is your uid? in the http header, uri args or post body?

cookie or header

https://github.com/iresty/lua-resty-radixtree/pull/5/files#diff-b59453348f7312db40e6a5de48f31ff5R114
the lua-resty-radixtree supports all nginx variable for  now, that is a powerful feature for user. so it is no problem to support cookie or header.

That is what I need

https://github.com/iresty/apisix/pull/458
apisix has supported this feature now. this PR was merged ^_^
I think you can close this PR.


Aa/sample all

Note on the motivation for this PR:
Try to add weighted sampling for the all bin (weighted by frequency). Instead of taking the output of tabulate_molecules, it combines all the bins and weighs them by freq.


Bump ko version in github action

As per title, net-* repos installs ko with old version with old style:
https://github.com/knative-sandbox/net-kourier/blob/main/.github/workflows/kind-e2e.yaml#L65-L72
We should use<EMAIL_ADDRESS>like:
https://github.com/knative/serving/blob/main/.github/workflows/kind-e2e.yaml#L51-L54

Not only net-kourier but also all net-* repo have this issue https://github.com/knative-sandbox?q=net-&type=all&language=&sort=


feat: add additional reprensentation to DSC-UI API enum paymentmethod

https://github.com/International-Data-Spaces-Association/DataspaceConnector/issues/617

Adds an additional "representation" to the enum API.
Must be tested by the UI and their approval obtained. (@BastianWel)
[
{
"originalName":"FIXED_PRICE",
"displayName":"fixedPrice",
"representation":"Fixed price"
},
{
"originalName":"FREE",
"displayName":"free",
"representation":"Free"
},
{
"originalName":"NEGOTIATION_BASIS",
"displayName":"negotiationBasis",
"representation":"Negotiation basis"
},
{
"originalName":"UNDEFINED",
"displayName":"undefined",
"representation":"Undefined"
}
]

After consultation with the UI developers, this solution is ok.
Also avoids a major change due to the additional representation API output instead of changing the displayName.


Homepage board images are very high-resolution PNGs

The images for each board on the Johnny Five homepage are high-resolution pngs, which are being displayed scaled down to ~1/10th their native size. Significant page weight gains could be achieved by using smaller images or, probably better yet, using SVGs (since the images are all diagrams)

:+1: @Wilto and I were talking about this yesterday!

To clarify the weight issue, 3.4mb of the page weight currently is images.

Here's a great doc on how to deal with this:
https://github.com/bocoup/website/wiki/Managing-Images

These are all Fritzing components, so it could just be a matter of re-exporting them from Fritzing as SVGs.

gzipped svgs would be brilliant

These are all Fritzing components

When Francis said they were "fritzing diagrams" I'd totally taken Fritzing as a euphemism...!

So the problem with the Frizting -> svg suggestion is that that none of these was made directly from fritzing. It would actually be impossible to make these the way they are directly from fritzing, because many are scaled to fit a certain visual sizing style. I've just batch resized the pngs for the time being.

Size is now 811kb

https://github.com/bocoup/johnny-five.io/pull/78


GRIFFIN-164 GRIFFIN-186 GRIFFIN-187: Profiling Re-factor + Regex/Empty String Support

We've been working away on Griffin here at Credit Karma, and we'd love to contribute back!
This PR tackles three separate tasks:

GRIFFIN-164: Regex Support
GRIFFIN-186: Create Profiling Measure Re-Factor
GRIFFIN-187: Empty String Support

The details for each of these tasks can be found in the JIRA tickets linked above!

I've reviewed the code for GRIFFIN-164, which seems good.

Test from UI based on your current measure and service :

create Accuracy and Publish measure successfully
fail to create Data Profiling measure
pr.component.ts: line 390 fails the Profiling and Publish measure creation, as this.step3.size is undefined type
failed to create job with above created Accuracy measure
{"timestamp":1533207681903,"status":400,"error":"Bad Request","code":"40011","message":"We don't support such measure type.","path":"/api/v1/jobs"}

{job.name: "job1", job.type: "batch", measure.id: 1, cron.expression: "0 0/4 * * * ?", cron.time.zone: "GMT-8:00", …}cron.expression: "0 0/4 * * * ?"cron.time.zone: "GMT-8:00"data.segments: Array(2)0: as.baseline: truedata.connector.name: "source1533207565052"segment.range: begin: "-1day"length: "1day"__proto__: Object__proto__: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ ()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()get __proto__: ƒ __proto__()set __proto__: ƒ __proto__()1: data.connector.name: "target1533207568926"segment.range: begin: "-1day"length: "1day"__proto__: Object__proto__: Objectlength: 2__proto__: Array(0)job.name: "job1"job.type: "batch"measure.id: 1__proto__: Object```

Thanks for taking a look at my PR @icesmartjuan!
I'm unable to re-produce any of the errors you've mentioned above. Regarding #2, I've added default values to the fields in step 3, so that error should not occur. Regarding #3, I didn't change the accuracy or job code, so that error may be unrelated.
I brought up a fresh version of the service/ui and was unable to re-produce the failures described above. Are you able to provide more detailed steps and/or photos so I can attempt to re-produce these errors myself!
Thank you.

tested with newly commit, create Profiling measure successfully, create jobs with the Profiling measure sucessfully


Add Hasura Event Invocation Logs to nhost logs

The Hasura event triggers are stored inside hdb_catalog.event_invocation_logs table.
They should be added to nhost logs command.
Similarly, all other event logs, including cron jobs and scheduled invocation logs, as well as actions logs must be added to the same command.

These logs can be found in the Hasura Console.


aktualizr: use updated pkcs11 engines path for openssl 3

Due switch to OpenSSL 3 (>= kirkstone), the pkcs11 engine path needs
to be changed to follow the correct version id.
Signed-off-by: Ricardo Salveti<EMAIL_ADDRESS>

Thank you!


Task 287-309 Phase 2

@abhinawale12 1) Can you resolve the conflicts 2) Can you add the original tasks in this PR. 3) Can you rename the task variants as taskxxx.1_yyyy, taskxxx.2_yyyy, taskxxx.3_yyyy and so on. (For e.g. task547.1_spl_translation_entk_en.json, task547.2_spl_translation_entk_en.json, task547.3_spl_translation_entk_en.json and so on.) Do this for all the tasks in this PR


Mock PA2 Level 2/3 Streams Approach

While I am able to use loops for these levels, I would like to try using Streams iteration, but I cannot seem to figure out how I can use it for add, mul etc. For example in m.mul(n), when using Stream.<Optional>iterate( ... ) there is a predicate (condition) as second argument. With the first argument being n, and the third argument being n -> n + n, how can I perhaps use m as the limit for the second argument? If not, how should I be imposing the stopping condition for this Stream, or should I be using Stream in another manner? Thank you!

you should be using and seeing whose optional you want to map.
for e.g
X.opt.map(x -> //create stream (generate/iterate)).limit(x)) would probably work well.
However, the above will return a Optional<Stream>, so do take note.
otherwise, to simplify logic step by step, you can try:
Stream = //generate or iterate a stream to create it
Optional<Stream> = X.opt.map(x -> ... limit(x))
afterall, to return a new Num, you should have a Num that takes in an optional,
your problem using this approach now would be to figure out how to convert an Optional<Stream> to Optional.
Hint: you can try using flatMap (you should know this does what to the type of Optional), map, reduce, apply, and any other methods u find helpful.

Hmm I'll try this, thank you!


Fixed use of html smbols for < and > in code

This comes through in the output and does not have the desired result.

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@justsayno thanks for your contribution.


jq 1.7 will no longer support --nul-output

The 1.0 beta announcement mentions support for the --nul-output command-line option.
Please note that jq 1.7rc1 has removed that option, and mentions instead:
      --raw-output0         implies -r and output NUL after each output;

It is generally expected that jq 1.7 will be released quite soon, and that the above remarks about jq 1.7rc1 will apply to 1.7 as well.

Thanks for the heads up. This was introduced in https://github.com/jqlang/jq/pull/2684. Worth noting that --raw-output0 bails when any outputs contain a NUL:
https://github.com/jqlang/jq/blob/a6920601299913ec5f9c9a8883517ec10dd71ffe/docs/content/manual/manual.yml#L150-L154
On top of renaming --nul-output to --raw-output0, we should add that check to remain consistent with jq.
note that the behavior of -j/--join-output was already inconsistent with jq (in jaq it does not imply -r). I matched that in --nul-output for internal consistency.

For now, I have reverted your previous PR, @baod-rate, because of the change in jq.
I think that it would be great to have some option to set the "output terminator string"; let's call it --output-sep for the sake of discussion.
Then the default would be --output-sep "\n", --join would be equivalent to --output-sep "", and the --raw-output0 option would imply --output-sep "\0". On Windows, --output-sep "\r\n" could be useful.
Prohibiting certain characters in the output as foreseen by --raw-output0 seems difficult, though.


Update main.tf

Modifying deprecated "tags" to "tag" variable

This seems like a good idea; could you rename the PR to something like "Rename deprecated 'tags' variable"?
It may not get noticed right now.

Hello,
Was this merged already?


PowerToys cannot search any source file or git repository file

Description of the new feature / enhancement
I need a solution to search Visual Studio project files and git repository files while PowerToys can't.
Optional solutions:

PowerToys can search without Windows Search
PowerToys can turn off the auto excluding Visual Studio projects and git repositories of Windows Search.

Scenario when this would be used?
I have a lot of open-source projects folks on my computer, so I need a fast searching among these projects. PowerToys run can search most of my files but it can't search any project files such as the *.sln file.
So I think PowerToys can try to improve the searching experience of this kind of files.
Supporting information
If we search for something, we can notice that the PowerToys give us a tip that "Not all files are indexed". After a long time of experience, we can easily find out that we can't search any files of Visual Studio project or git repositories files.
If we click the tip to go to the Windows search settings, we can find that almost all the Visual Studio project folders and git repository folders are excluded from the Windows Index.

Here is a document describing the reason why Windows Settings excludes all the git repositories:
https://insider.windows.com/en-us/articles/desktop-search

For our developers, we also made a change where the indexer no longer covers popular source repositories, like Git. This was partly because of the sheer size of these repositories, and also because the tools developers use to interact with their repos usually have their own search tools. We also worked with our Visual Studio partners to exclude their project folders, which resulted in a quick 30% improvement in disk usage, for an even better developer experience.

OK, PowerToys is a tool for developers, but it searches files using Windows Search. Windows Search said that most developers have their own search tools. But their own search tool uses Windows Search to search...

@walterlv Please see if this helps! Windows Search settings

/needinfo

@franky920920 This document does not help.

I'm using the Enhanced Mode to search files and this has included all the drives of the PC. However, what the document says only affects the scope of the Classic Mode.
Windows Search automatically excludes project folders, that have a higher priority to including folders.

/dup #12852

that's not a duplicate. Windows Indexing forcefully exludes all directories that contain a .git directory. that means any git working directories are excluded from indexing, and that can't (so far?) be affected by users. if PowerToys relies on windows indexing, it can't work around that and magically "include" those directories again.

Actually I misread the issue I linked t. This is the inverse of that. Both would require basically same area adjustment. Lemme update that title to expand its scope

@crutkas  Unfortunately, even though you updated that title to expand its scope, it still can't solve the problem we are affected by.
Let us make a mind experiment. If we have solved that issue, then we can manually include extra folders that are on the blacklist of the Windows Indexes. But the Windows automatically excludes every git directory every day we met which means we have to include them again and again in the PowerToys, for every git directory and every day.

If memory serves,  you can do a pattern which solves this issue.

This isn't a duplicate but I guess PT can't do anything about this because Windows Indexer remains broken and Microsoft won't listen to the complaints.


Setup Lets Encrypt (ACME) with either HTTP or TLS challenge

We want to implement a configuration option in the helm chart, to automatically start Traefik with a certResolver which either uses the HTTP or TLS challenge (and provide the needed configuration like email address)
Partially fixes #185

+1

I am very interested in this kind of enhancement. In v1 of the helm chart, there was a ssl: section where you would define your certResolver stuff, but it is just plainly missing from the current version, so the only way I see it defining this is through additionalArguments, correct?

correc @Letme. And if you want to raise a PR to fix that, you're very welcome 👼

OK, I will first try to get it working (so far ports 80 and 443 on kubernetes master node are not opened) as this is my first touch with Kubernetes (and Helm). I assume it could be stolen from v1 chart as there should not be much of a difference (at least simple settings).

@SantoDE Do you think it's fixed with #285 ? Or is there something missing ?


fix(vanilla): improve performance with configurable property on snapshot

and some refactors.
close #519 again.

Finally fixed! https://codesandbox.io/s/form-test-valtio-forked-85ozhn?file=/src/App.tsx

I liked the assert-again-getUntracked idea b/c it would be more black-box and assert what we really care about (compare-proxy isn't making copies)

@stephenh Can you help with the idea of black-box tests? (Open a PR?)
Merging this for now.


BC spaces are incorrect

I wrote a test to check that the normal components of BC functions are continuous between cells (see https://github.com/bempp/bempp-cl/pull/195).
The test currently fails on main.

My mistake, there was an error in the test I wrote


Multiple traces in the Playground

Often you want to test out several different scenarios when developing a contract (e.g. "successful campaign", "failed campaign"). At the moment you have to manually clear and re-enter each every time you want to use it.
Ideally we'd let you have several (named?) traces available at any one time. That would probably mean we need to change the UI a bit too - I was thinking something a bit more like Trello lists.

This is supported in https://github.com/input-output-hk/plutus/pull/681. You can set up & run multiple simulations, and you can save/load/share via a gist.
But I'm waiting on some design work before merging it, so it's still open.

It’s merged now, so can we close this?

Yes.


No indenting in console.dir() object dump

Issue:
There is no indenting in the console.dir object dump on iOS devices. See image below.
I'd like to work on this issue and submit a PR.

Version numbers that your issue occurs with:

CLI: 4.0.0-2018-04-05-11381
Cross-platform modules: 3.4.1
Runtime(s): iOS - 4.0.1-rc-2018-04-05-01
Plugin(s): NA

Steps to reproduce

create new project with hello world template.
paste this anywhere in the files...

console.dir({
    name1: "value1",
    name2: "value2",
    name3: {
      name3_1: "value3_1",
      name3_2: "value3_2",
      name3_3: {
        name3_3_1: "value",
        name3_3_2: "value"
      }
    }
  });

I was working on this but there was a commit by someone that appeared to have fixed this issue. I'll get onto this of no-one else is.

@aaayushsingh, thank you for the willingness to help. We've checked that this still is not fixed, so you can continue with it if you want.

sure. I'm on it then

I was working on this but there was a commit by someone that appeared to have fixed this issue.

@mbektchiev I can't reproduce this when I add the ios runtime like the readme. That way everything logs fine. This why I thought it was fixed already

@aaayushsingh I just found out that indeed it's fixed. PR #884 has addressed it. I'm really sorry for misleading you.

@aaayushsingh Thank you very much for willing to help us. If you feel it suits you, you may work on the other issue that is marked with help wanted. It is suitable for first time committers as well.

I still reproduce it with CLI: 5.0.0 and ios-runtime: 5.0.0 on simulator and device.

@Natalia-Hristova yeah, It is reproducible with NativeScript cli but when I try to reproduce using steps mentioned here in comment by @mbektchiev and run using xcode, the log is indented properly.

@aaayushsingh @Natalia-Hristova I've tested and can confirm that the iOS Runtime actually indents the output, but it seems like there's some trimming happening in {N} CLI. We will move the issue to the CLI repository. Thank you both for helping clear this out!

Issue moved to NativeScript/nativescript-cli #4160 via ZenHub


Rename "direct CassIO" to sth like "Usage" on the website

Careful about redirects but sounds about right. (suggested by Ryan).

being addressed now


Add support for hostname address in conformance tests

What type of PR is this?
Add one of the following kinds:
/kind test
Optionally add one or more of the following kinds if applicable:
/area conformance
What this PR does / why we need it:
This PR adds support for addresses of type Hostname in the Address section for the status of gateway objects. This change is needed so that cloud load balancers can provide a DNS name in as the address assigned to the gateway and pass the conformance tests.
Which issue(s) this PR fixes:
There was a TODO section in the helpers.go file that that PR addresses, there is no github issue for it.
Does this PR introduce a user-facing change?:
NONE

/ok-to-test

Thanks for catching this @snehachhabria!
/lgtm
/approve

Thanks @robscott for the approval, is it possible for this change to be cherry picked in to release v1 ?

/cherry-pick release-1.0


Build selinux policy

Create an selinux policy at image build time - despite the -i flag, this
won't attempt to install it into the running kernel.

LGTM


Bug when use xkb-switch in xbindkeys

Hello everyone !
I develop analog PuntoSwitcher for Windows. It is OpenSwitcher and its github here OpenSwitcher.
I faced with a problem when I use xkb-switch in xbindkeys. At first run xbindkeys key combination Ctr+Alt script run correctly but i another cases it doesnt work. Without xkb-switch xbindkeys key combination Ctr+Alt script run normaly.
Code here:
$HOME/.xbindkeysrc
# Activate OpenSwitcher
# To read about how to customise read `man xbindkeys`
# To read where is keys see #include <X11/keysym.h>
"openswitcher.sh"
Control + Alt_L

/usr/local/bin/openswitcher.sh
# sleep 0.5
xkb-switch -n
sleep 0.5
xsel | sudo openswitcher

uname -a
Linux MyDebian 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux

Hihi. Could you please clarify what behavior do you expect in this case?
xkb-switch -n should select next kb layout. Does it work if you run it in terminal manually?

Yes it works in terminal manually, after several test I think the problem may occur because of xbindkeys,. Now I search solution for xbindkeys.

Hihi. Could you please clarify what behavior do you expect in this case? xkb-switch -n should select next kb layout. Does it work if you run it in terminal manually?

I dont not how an why bu me help sleep 0.5 AFTER script

No, my problem is still here :) Exactly after I add xkb-switch -n to the script problem occur, I tried add before and after sleep 0.5 and it doesnt solve my problem. At beginning of discussion I had two problems with xbindkeys and xkb-switch -n first I solve with sleep 0.5 and second I didnt solve

No, my problem is still here :) Exactly after I add xkb-switch -n to the script problem occur, I tried add before and after sleep 0.5 and it doesnt solve my problem. At beginning of discussion I had two problems with xbindkeys and xkb-switch -n first I solve with sleep 0.5 and second I didnt solve

Could you please clarify what your script is supposed to do exactly? I see it calls xkb-switch to change the layout and then it pipes the X11 selection into your openswitcher app. What should happen next? It is not clear to me how switching the layout correlates to this second part. Does xkb-switch fail to change the layout or there is some other problem?

No, my problem is still here :) Exactly after I add xkb-switch -n to the script problem occur, I tried add before and after sleep 0.5 and it doesnt solve my problem. At beginning of discussion I had two problems with xbindkeys and xkb-switch -n first I solve with sleep 0.5 and second I didnt solve

Could you please clarify what your script is supposed to do exactly? I see it calls xkb-switch to change the layout and then it pipes the X11 selection into your openswitcher app. What should happen next? It is not clear to me how switching the layout correlates with this second part. Does xkb-switch fail to change the layout or there is some other problem?

Sure ! My program take a text from input and transform to the Keycodes after that it print via /dev/input/event0 (keybord driver, function write())

No, my problem is still here :) Exactly after I add xkb-switch -n to the script problem occur, I tried add before and after sleep 0.5 and it doesnt solve my problem. At beginning of discussion I had two problems with xbindkeys and xkb-switch -n first I solve with sleep 0.5 and second I didnt solve

Could you please clarify what your script is supposed to do exactly? I see it calls xkb-switch to change the layout and then it pipes the X11 selection into your openswitcher app. What should happen next? It is not clear to me how switching the layout correlates with this second part. Does xkb-switch fail to change the layout or there is some other problem?

Sure ! My program take a text from input and transform to the Keycodes after that it print via /dev/input/event0 (keybord driver, function write())

Hmm, I see. I have installed your app, had to change event0 -> event2 and I think I am able to see it works. Pretty cool! But that means I can not reproduce the problem.. I think I saw a couple of buffer overflows, had to build the app wiht -O0 -g.

Are you able to run your app without xkb-switch normally?

Also, even if it doesn't work properly, do you see the keyboard layout is changed after your script exits?

Are you able to run your app without xkb-switch normally?

That is interesting. After several tests I think that bug appear more likely because of xbindkeys, but I dont know why when I use xkb-switch -n it is getting worse. BUT when I use openswitcher.sh via terminal it works absolutely good.

Also, even if it doesn't work properly, do you see the keyboard layout is changed after your script exits?

Yes, layouts changed )


Check for duplicate status code entries in 'errors' directive

Check for duplicate status code entries in 'errors' directive as  was proposed by @vchimishuk in #1028

Nice! Thanks.


no barrel files

Do you know of a good codemod for migrating away from barrel files?
I found this codemod to address https://vite.dev/guide/performance#reduce-resolve-operations and am looking for one for https://vite.dev/guide/performance#avoid-barrel-files too.

Glad to hear that you're finding this codemod useful!
AFAIK the best available solution for avoiding barrel file imports is to use no-restricted-imports to disallow imports from the barrel file.
Unfortunately, if you already have a lot of barrel file imports, the only options that I know of are:

Change the imports manually, or
Write your own codemod

When I have the time, I might write another codemod for "de-barreling." 👨🏻💻

Update: I found an existing codemod for this, direct-import-codemod (shout-out to awesome-codemods!). Please give it a try and let me know how it goes.


DeveloperGuide: update converting docs to PDF format

Ready for review

@damithc as requested in gitter

This overlaps with #673 right, and there seems to be conflict in the way you are deciding on how to generate the PDF files :P

@Zhiyuan-Amos yeah xD this comes after #673

ready for review

DeveloperGuide: modify converting docs instructions to use local file

Please add some simple background info on why the docs instructions need to be updated as well. (e.g. It is easier for developers to just generate the PDF directly on their local machines without having to go through the steps of publishing the documentation on GitHub Pages.)

For commit titles for both commits, capitalise the first word after the colon e.g DeveloperGuide: Modify...

You missed this, but it's ok this time (just a small thing), but take note in future ^^

For commit titles for both commits, capitalise the first word after the colon e.g DeveloperGuide: Modify...

@Zhiyuan-Amos The official guide actually recommends it to be lower case :-P See the examples: https://oss-generic.github.io/process/docs/FormatsAndConventions.html#commit-message

Gosh opps. I deserved to be sacked :(

@Zhiyuan-Amos it's okay, i've remembered I read somewhere to lower case but can't remember where :P
don't try to get yourself sacked on purpose 😄 we still need you in addressbook


Update GSoC-interest.md

Signed-off-by: Amaan Sayyad<EMAIL_ADDRESS>

Hi @AmaanSayyad, thanks for your interest in CHAOSS.
I appreciate your efforts or working on this idea but I'm sorry to say that the application deadline has already passed and the mentors are currently reviewing the applications submitted before the deadline.

You must complete these things by April 19, 2022 13:00 US Central Time (UTC-5). Make sure to also submit the information required by GSoC for applicants (i.e., project proposal), linking to it from your pull request to this file. Here is an Proposal Template to get you started.

https://github.com/chaoss/community/blob/main/GSoC-interest.md
I think the rules were pretty clear that all the things must be completed before the deadline and it would be totally unfair on our part if we accept any applications after the deadline. So, I'm closing this PR for the same reason.
Thanks for your work and looking forward to your contributions to CHAOSS in future.

Hi @vchrombie, it looks like @TejasMate submitted his proposal to GSOC before the cutoff date and just forgot to add their name here. I am not sure we need to close this.

Hi @vchrombie, it looks like @AmaanSayyad submitted his proposal to GSOC before the cutoff date and just forgot to add their name here. I am not sure we need to close this.

Yes, I forgot to add my name here.
Thanks, @klumb @vchrombie for merging my pull request.


[OTHER] Question: is it possible to send a new message and afterwards get the replies?

What would you like to share?
I would like to be able to send messages to a new contact and asynchronously get the incoming replies from chat.
It is possible with this lib?
Additional information
No response

Yes, linkedin.message.service.ts, send a message and also scrape the inbox after


CompletableFuture for queueShipSpawn

Use case is conveniently changing ship parameters (enable physics or grid alignment) after spawn.
Wasn't able to test it properly yet because dev environment is not starting. Wait until I test it (or somebody else). Changes are not that significant though.

Seems to work but vs-controls have to be rebuilt with this as a dependency for it to work because methods signature is changed (JVM one, not java).

¯\_(ツ)_/¯

We decided with Rubydesic that it is better to keep binary compatibility. So I will add new methods soon.


Automatic Intro Skipping does not work in combination with add-on upnext

I'm submitting a ...

[X] bug report
[ ] feature request
[ ] support request

General information
Prerequisites

[X] Are you running the latest version?

yes
Description
In combination with the upnext add-on the automatic intro skipping function is not working after upnext started a new episode. If the automatic skipping (by default) is off you are able to manual skip.
Opened an issue with upnext as well.
https://github.com/im85288/service.upnext/issues/9
Steps to Reproduce

[First Step]

Enable automatic intro skipping

[Second Step]

Wait until upnext started the second episode

[and so on...]

Expected behavior: [What you expected to happen]
Intro is going to be skipped
Actual behavior: [What actually happened]
Intro is playing, manual skipping is not offered
Context (Environment)
Installation

[ ] I installed the plugin via zip from the Releases page
[X ] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[ X] Linux (ARM)
[ ] Android

Additional informatin on the environment
LibreElec v8.90.007 ALPHA on Asus tinkerboard S

I'm not having UpNext addon in Kodi, and yet "skip intro" feature is not working.
I utilize now nVidia Shield with Android TV, this is completely fresh install with Kodi 18, official Netflix plugin repo.
Of course, option is enabled in Netflix plugin settings. But it's not working.

What version are you using? 0.13.x from the repo or any of the 0.14.0 betas? This should be more stable in the latest 0.14.0 beta. If you're on 0.13.x you'll have to wait for 0.14.0 to be released or switch to the beta. I won't backport any fixes into 0.13.x.

Hi,
yeah sorry I missed that information. Right now I am on 0.13.18.  I tried to use 0.14 but had some issues with a samba share for the exports that I use for 0.13 to keep two installations in sync.
I understand that you won't wanna backport everything back to the old branch, maybe I give 0.14 another try during the weekend. Thanks


CORS on API doesn't work with Safari 17.3.1

What is the issue?
Requesting ollama api from localhost:1420 to <IP_ADDRESS>:11434 works in Chrome but not Safari, it got an CORS error: ""
While fething the api from the console works, which is strange:

After examining the headers for both request:
fetch from source:

fetch from console:

I suspect it might be related to the missing host header in the source fetch.
What did you expect to see?
No cors error.
Steps to reproduce
No response
Are there any recent changes that introduced the issue?
No response
OS
macOS
Architecture
arm64
Platform
No response
Ollama version
No response
GPU
No response
GPU info
No response
CPU
No response
Other software
No response

Hi there! Thanks for creating an issue. To enable CORS access for now you'll need to set an environment variable: https://github.com/ollama/ollama/blob/756c2575535641f1b96d94b4214941b90f4c30c7/docs/faq.md#how-can-i-allow-additional-web-origins-to-access-ollama
We're working on making this easier in the macOS app – stay tuned!

Hi @jmorganca , the document says "Ollama allows cross-origin requests from <IP_ADDRESS> and <IP_ADDRESS> by default", and in the code https://github.com/ollama/ollama/blob/main/server/routes.go#L957-L980
func allowedHost(host string) bool {
	if host == "" || host == "localhost" {
		return true
	}

	if hostname, err := os.Hostname(); err == nil && host == hostname {
		return true
	}

	var tlds = []string{
		"localhost",
		"local",
		"internal",
	}

	// check if the host is a local TLD
	for _, tld := range tlds {
		if strings.HasSuffix(host, "."+tld) {
			return true
		}
	}

	return false
}

I think we were meant to allow core requests from localhost by default right?


form/queryParams -> empty lists

Changing form/queryParams(x) to return empty lists instead of null values #239

WsSession also needs this. I'm starting to wonder if there should be a shared interface for them.

omg, I keep forgetting about it. Done.
Yea, I think we might think about common interface, I was actually thinking about exposing all Javalin public API in form of interfaces. Kotlin has extension functions so that is easy to bring more customizations to javalin if one needs, but java does not, and inheritance is not a good tool for the job IMO.
I'll expand on it in separate ticket once I summarize how could it look like.

@majorpasza if you resolve the conflicts I can merge this.

Done


prettified code once and for all

addresses #92

@nikooo777 would suggest either targeting this only at *.js files or have it explicitly exclude .md. It looks like it inserted a lot of newlines into your markdown files, which is probably not desirable.

@kauffj i had the very same concern and asked Fil, he said it was meant to format the md as well so I went on with it.
Should we exclude it?


adding hasing technique

@manan-shxrma  please check out my pull request

@manan-shxrma  please check out my pull request

try adding 1-2 file(s) at a time so that others can contribute too.


VM Linux extensions

Cleaning

@iainfoulds,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Websocket Server with HTTP callback is not working. Callback is not triggered

Describe the bug
The HTTP callback is failing to execute. The server seems to be trying to call the method whenever there is a change of the text editor content, but it gives the following error message in the console:
Callback request error. Error: socket hang up     at connResetException (internal/errors.js:609:14)     at Socket.socketOnEnd (_http_client.js:459:23)     at Socket.emit (events.js:326:22)     at endReadableNT (_stream_readable.js:1223:12)     at processTicksAndRejections (internal/process/task_queues.js:84:21) {   code: 'ECONNRESET'
To Reproduce
Steps to reproduce the behavior:

Go to https://github.com/BitPhinix/slate-yjs-example
Clone the repository locally
Run npm install
Modify the start:server command to "set HOST=localhost&&set PORT=1234&&set CALLBACK_URL=https://localhost:5001/weatherforecast&&set CALLBACK_OBJECTS={\"prosemirror\":\"XmlFragment\"}&& npx y-websocket-server"
Run npm run start:server

Expected behavior
I expect that the HTTP method will be called instead of getting that error message in the console.
Screenshots

Environment Information

Chrome 88.0.4324.150 / Node.js v12.19.0
Yjs version: npm ls yjs

NOTE:  I changed the CALLBACK_URL to use HTTP instead of HTTPS and now it works. I suppose the problem was with using self-signed HTTPS certificates for localhost.


[Device Support Request] Sercomm SZ-DWS04 Door/Window Sensor

Please add support for the following device?

{
"node_descriptor": "",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0402",
"in_clusters": [
"0x0000",
"0x0001",
"0x0003",
"0x0020",
"0x0402",
"0x0500",
"0x0b05"
],
"out_clusters": [
"0x0003",
"0x0019"
]
}
},
"manufacturer": "Sercomm Corp.",
"model": "SZ-DWS04",
"class": "zigpy.device.Device"
}

The contact sensor works OOTB. A quirk can be added for battery.

Thanks yes Battery and tamper alarm is missing

I have this contact sensor and it's missing the Battery function. Any help pointing me in the right direction?

I have this contact sensor and it's missing the Battery function. Any help pointing me in the right direction?

Did you have any luck with this? I’d like to create a quirk for this but getting setup for development wasn’t as straightforward as I expected and I’ve been short on time to research further.


Elements (Button, Link, Paragraph)

What does this PR do?

Adds rules for button, link, and paragraph elements (with variants as appropriate)
Updates doc site to display each element_type in it's own table
Addresses some issues brought up in initial WIP PR

Where should the reviewer start?

Screenshots
css/design_system/elements

How should this be manually tested?
Run locally to see what is created/available, specifically on /elements
Any background context you want to provide?
It's in place and working and all displaying the information needed on doc site, which is all a huge win. There are a couple things I don't love, questions I have still. I'm not sure if they should hold up the PR getting merged but wanted to note:

The examples to explain links v buttons take up a lot of space and something about the way the page is formatted makes it ... just not super user friendly at the moment. I don't know if I used the best sub-header text to describe things. I could use some help/opinions on that!
I wanted to make a variant for the paragraph element for dark backgrounds since that is used in many places across Turing_io - to get those to show up with a dark background, well... I didn't love my solution but it's all I could get working.
I'd love input on the naming for the paragraph text classes. Is s-p too short? s-paragraph then those with extra tags if you will, felt super long, so I trimmed to s-p.
Also on paragraphs - notice that the sample HTML code does not display the closing HTML <p> tag. I can't figure out why but that's the only tag it doesn't display for.
The multi-line code snippets are hideous; feel like that should be addressed it it's own PR or maybe grouped in with some other "style doc site" specifics.
I'd like to make another PR that creates a minimap of sorts (screenshot from Sage below) for easier navigation within a page. As well as address our left-side bar being a little too wide IMO.

What are the relevant tickets?

https://3.basecamp.com/3494409/buckets/19192671/todolists/3501120206
https://3.basecamp.com/3494409/buckets/19192671/todolists/3475467357
https://3.basecamp.com/3494409/buckets/19192671/todolists/3458194994

Screenshots (if appropriate)

See full page screenshot here: https://www.awesomescreenshot.com/image/6513983?key=fc8eba4fa4ec214d71ed3c3710d0f00b

I made updates based on 2/3 of Tanners notes above (thank you Tanner!)

Changed link filed name to link and class is s-link
Adjusted paragraph so there is just one base util, then devs can add any other util they want. In doc site, I showed one small example where a different size is being applied. Not sure if we'd like more examples, or context for that, maybe links to other util pages? Curious to hear your thoughts.

As for the note about using rouge - yes, I plan to do that in another PR more focused on styling of the doc site itself!

@kat3kasper do you want to re-review this before it's merged?

This is the updated full page of the /elements path:
https://www.awesomescreenshot.com/image/6921744?key=0501b625ce8a8c2f7ac88b3eae55e5a6
/tokens page:
https://www.awesomescreenshot.com/image/6921756?key=d12e9b6beaff9a611612886dee87b8b9
'/typography` page:
https://www.awesomescreenshot.com/image/6921779?key=c947d725870e66bcc88fbb1ec17ce13d


fix codegen for multiple file type

arguments for addUpdate were the wrong way around leading to a broken declaration file

Good catch thank you!


Serializing null for non finit metric values

Seems like the APM Server does not like null values:
java.io.IOException: Server returned HTTP response code: 400 for URL: https://apm.europe-west3.gcp.cloud.es.io:443/intake/v2/events
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1894)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263)
	at co.elastic.apm.agent.report.IntakeV2ReportingEventHandler.flush(IntakeV2ReportingEventHandler.java:283)
	at co.elastic.apm.agent.report.IntakeV2ReportingEventHandler.handleEvent(IntakeV2ReportingEventHandler.java:152)
	at co.elastic.apm.agent.report.IntakeV2ReportingEventHandler.onEvent(IntakeV2ReportingEventHandler.java:140)
	at co.elastic.apm.agent.report.IntakeV2ReportingEventHandler.onEvent(IntakeV2ReportingEventHandler.java:58)
	at co.elastic.apm.agent.shaded.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
	at co.elastic.apm.agent.shaded.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
	at java.lang.Thread.run(Thread.java:748)
2019-02-22 19:03:39.195 [apm-reporter] WARN co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - {"accepted":14,"errors":[{"message":"Problem validating JSON document against schema: I[#] S[#] doesn't validate with \"metricset#\"\n  I[#] S[#/allOf/0] allOf failed\n    I[#/samples/system.cpu.total.norm.pct/value] S[#/allOf/0/properties/samples/patternProperties/%5E%5B%5E%2A%22%5D%2A$/properties/value/type] expected number, but got null","document":"{\"metricset\":{\"timestamp\":1550858576638000,\"samples\":{\"system.process.cpu.total.norm.pct\":{\"value\":0.125},\"jvm.memory.heap.used\":{\"value\":1071700752.0},\"jvm.memory.non_heap.used\":{\"value\":93600808.0},\"jvm.memory.heap.max\":{\"value\":3817865216.0},\"jvm.gc.alloc\":{\"value\":4364208480.0},\"jvm.memory.non_heap.committed\":{\"value\":97607680.0},\"system.cpu.total.norm.pct\":{\"value\":null},\"system.process.memory.size\":{\"value\":10463731712.0},\"jvm.memory.heap.committed\":{\"value\":1654652928.0},\"jvm.memory.non_heap.max\":{\"value\":-1.0},\"system.memory.actual.free\":{\"value\":103964672.0},\"system.memory.total\":{\"value\":17179869184.0}}}}"}]}

@elastic/apm-server we did this (sending null in metrics when the infrastructure query returns NaN) based on #445. Is there something we should do to fix the error we get above or would you change to allow nulls? (the latter should be validated with UI as well I guess).

When sending a sample, a value is required, so sending null values for samples is not allowed. This is consistent handling throughout the Intake API: required attributes aren't allowed to be null, optional attributes are.
I assume the value has been set as required, as it wouldn't make sense to send up a metric sample without a value (@graphaelli please correct me if I'm wrong). From my perspective the Intake API makes sense as is, and it probably also makes sense from an agent perspective to not send data that won't be stored anyways. However, if this is a problem for any agent, I don't see a problem loosening this and making the value optional and therefore nullable.

@simitt to me it makes perfect sense to avoid sending it when we have no value if this is not stored anyway, as long as the server doesn't expect to get specific metric keys.
@elastic/apm-ui just to make sure- if we omit specific metric samples occasionally (when we don't have a valid value for them)- would aggregations made for graph creation be affected by the lack of documents?

@eyalkoren This shouldn't affect the UI too much. Obviously there'll be fewer data points, so instead of having a datapoint every 30s there'll be a gap of 60s. The UI should handle this fine, and it is only if the user zooms in a lot that they'll notice it.

Issue above fixed by #501 - avoid sending samples with NaN instead of sending null


operator/test: fix update pmemPercentage test failure

Incrementing the default pmemPerencentage of 100 leads to out of
bounds(101) and tests fails as below:
Status: "Failure",
Message: "Deployment.pmem-csi.intel.com \"pmem-csi-with-defaults\" is invalid: .... : validation failure list:\nspec.pmemPercentage in body should be less than or equal to 100",

The change itself looks reasonable, but I'd still like to know under which circumstances this becomes a problem.

With this patch applied there are test failures:
https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-731/1/tests

Message: "Deployment.pmem-csi.intel.com "pmem-csi-with-defaults" is invalid: spec.pmemPercentage: Invalid value: 100: spec.pmemPercentage in body should be less than or equal to 100",

Looks like the original failure observed in https://github.com/intel/pmem-csi/pull/718 was due to result of other changes(I guess patch updating the deployment, witch updated the default value) and now this change is not needed any more.


Separate Contact Us page added.

Issue no : #214

@AbhijitMotekar99 Resolve the conflicts ...

Hey @ROKUMATE
I am not able to solve the conflicts its shows you can solve it in editor , I also reinstall node modules still its not going can you help me ?

@AbhijitMotekar99  create new pr after fetching latest changes.. maybe there's conflicts in package-lock which usually is very large and cannot be fixed this way

@AbhijitMotekar99  any updates? Or I close this PR?

Hey @Luson045
I am working on this I will raise PR till tomorrow.

Hey @Luson045
I raise another PR #380 plz check it once


Diamonds not working as intended when manually deploying facets

I noticed that this plugin, while offering native support  for Diamond Standard-compliant contracts, does not seem to allow for manual deployment and setup of the Diamond and its Facets. More precisely, with the following code: https://github.com/ARM-Finance/kingmaker/blob/1e7bb406e99108e8a87076d6fcc33d13be59df58/protocol/deploy/governance/02_kingmaker_governance_facet.ts#L16-L56 I will get the following error:

However, if I use the supported approach to deploying Diamonds with Faucets then the plugin is able to correctly interact with them with read() / execute() (e.g. https://github.com/ARM-Finance/kingmaker/blob/1e7bb406e99108e8a87076d6fcc33d13be59df58/protocol/deploy/01B_kingmaker_cowl.ts#L19). Can you point at this behavior in your code?
The rationale for my approach is the desire not to be bound to keep track of the existing facets and not to be forced to seemingly re-deploy a new Diamond with different facets, judging from the Diamantaire code and plugin API (e.g.
await diamond.deploy('ADiamondContract', {
    from: deployer,
    owner: diamondAdmin,
    facets: ['Facet1', 'Facet2', 'Facet3'],
  });

 await diamond.deploy('ADiamondContract', {
    from: diamondAdmin, // this need to be the diamondAdmin for upgrade
    owner: diamondAdmin,
    facets: ['NewFacet', 'Facet2', 'Facet3'],
 });

Hey @lepidotteri note that the work on Diamond is still in beta and I did not have time to take care of it since some time. It is unlikely I ll have resources to look at it soon. I plan to remove it from the documentation in the mean time to avoid confusion.
Regarding your problem though, which implementation of Diamond are you using ?

Hey @lepidotteri note that the work on Diamond is still in beta and I did not have time to take care of it since some time. It is unlikely I ll have resources to look at it soon. I plan to remove it from the documentation in the mean time to avoid confusion.

Hi, thank you for the clarifications, your plugin is too valuable not to be relied upon, so if you agree I would just go ahead and fork it for our own organization, with the sole intent to update and better its current Diamond Standard support

Regarding your problem though, which implementation of Diamond are you using ?
I am using the 3rd one here: https://github.com/mudgen/diamond-3. However, note that the implementation itself is not the issue, rather the problem is supposed to lie in the way your plugin interacts with the "custom" Diamonds that is not able to interface with correctly (e.g. https://github.com/ARM-Finance/kingmaker/blob/1e7bb406e99108e8a87076d6fcc33d13be59df58/protocol/deploy/governance/02_kingmaker_governance_facet.ts#L31 execute() fails here because, I suspect, the plugin uses the vanilla ethers.js to lookup the Facet method ABI, in this case 'diamondCut', against the "custom" Diamond ABI)

So that's how you avoid ethers.js raising issues when performing checks on ABIs? https://github.com/wighawag/hardhat-deploy/blob/a842674b5a5a47ad2ee5b91c2fae1d3e1840e9b6/src/helpers.ts#L48

@lepidotteri yes, so not sure why it does not work in your case, since as you see it include the diamondCutFact in the ABI
You should see it in the deployments//Crow.json file
Regarding forking, it would be great if you make a PR. I would be happy to review it with the goal of being included back.
Thanks

latest hardhat-deploy has revamped diamond support. reopen if there are any issue


Is checkYii() needed?

Looking at the code, it's not really needed for the API, and it has the drawback of being Yii specific (for a non-Yii specific package).
Should we consider removing it and introduce a checkRequirements($filepath) ?

Yes.

Nice for common use.


Edits to "New Resources" section of Topical Toolkit

Three issues we'd like to correct:

[x] Every resource includes the text "- All Content Types -" instead of the name of the associated content type.
[ ] Would like to limit each list to the top five most recent.
[ ] Extra white space above "New Resources" text - white space should align with the white space for "Introduction"

Example:
https://aashe-hub-dev.herokuapp.com/browse/topics/curriculum/

In addition to aligning the text under introduction and new resources, the whole new resources box should be widened and/or shifted to the right so that the right edge lines up with the end of the green underline below the submit a resource button.

The only piece I'd push back on is this:

Extra white space above "New Resources" text - white space should align with the white space for "Introduction"

The text of "Introduction" and the text of "New Resources" align. I'd say that is preferable. If it really bothers more than one of you, I can extend the border around the new resources to go along the top too and that will align with the grey box to the left.

Having Introduction and New Resources be aligned is good but I think Monika was talking about the white space below the headings, not above it. The text under Introduction is higher than the text associated with the first item under New Resources. This is not a big deal, but it would be nice to align that as well.

Ok, I see what you're saying. I'll see if I can tweak that.


Changing the input slot names, on the switch node, gives error

If I change the input slot names on the switch node I get this error:

Error occurred when executing 0246.Switch:

'MiDaS Depth'

File "C:\Cui\cu_121_2\ComfyUI_windows_portable\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Cui\cu_121_2\ComfyUI_windows_portable\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Cui\cu_121_2\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-0246\utils.py", line 381, in new_func
res_value = old_func(*final_args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Cui\cu_121_2\ComfyUI_windows_portable\ComfyUI\execution.py", line 65, in map_node_over_list
results.append(getattr(obj, func)(**input_data_all))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Cui\cu_121_2\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-0246\nodes.py", line 2887, in execute
res.append(kwargs[kwargs[key][0]])
~~~~~~^^^^^^^^^^^^^^^^

Hm not intended to allows changing since the nodes rely on names to locate pins. I could see what I can do for custom names.

I don't need to change the input slot names on the Switch node.
What I like about this, is that the names were converted to a COMBO list !
Could it be possible to display the title name of the connected nodes in the COMBO list ?
If you need the slot names, the title name could be added after the slot name, eg: 0:IMAGE Marigold Depth.

the ability to relable the names would make Hub my go to in every workflow. might it be possible to relable without actually changing the name itself?

the ability to relable the names would make Hub my go to in every workflow. might it be possible to relable without actually changing the name itself?

I think that could possibly since that just change label not name. Label is different from name as name is the internal name that only shown when label does not exist, and label does not influence name identifier which is the main purpose of name.
Currently I'm a bit busy in life so not many update are happening but hopefully I'll try to fix things up for next month.

This should no longer crash with recent fixes. Hopefully everything should works now for changing input slot label directly. Changing switch slot label based on connected node is currently infeasible due to implementation issues but probably could add that in the future.

It's working for me. Thanks.
Changing the switch labels would also be great, if possible.
The switch labels could change when we change the output labels.


proposal: preImport

This adds a preImport hook proposal.

PR: https://github.com/nodejs/node/pull/43245
Discussion: https://github.com/nodejs/loaders/issues/83

The main text here corresponds to the readme for the PR, while including a more comprehensive end-to-end example.
Naming is still provisional, specifically the topLevel boolean context name and the preImport hook name are still being ironed out.

I don't have the background context on why resolve had to be made synchronous in the first place, but this proposal makes me wonder if an implementation detail is being leaked into userspace. Specifically, it seems that something like this would be perfectly valid:
const results = new Map();

export async function preImport(specifier, context) {
  const key = makeKey(specifier, context); // some deterministic mapping to (say) a string
  const result = /* some async operation here */;
  results.set(key, result);
}

export function resolve(specifier, context) {
  return results.get(makeKey(specifier, context));
}

At which point, the details of results and resolve could be hidden away and preImport just becomes the resolve of old?
I assume I must be missing something; for example is there some data which is only available at the (synchronous) resolve time, and not the earlier preImport? As a user of this API, I'd currently be very confused about what the intended (semantic) distinction is between the two methods.

I don’t have the background context on why resolve had to be made synchronous in the first place

Because import.meta.resolve will be sync in browsers: https://github.com/whatwg/html/pull/5572. Node’s version of import.meta.resolve should therefore be sync as well to avoid user confusion and code that works in one environment but breaks in the other; and import.meta.resolve calls the resolve hook (either Node’s internal one, or that internal one that’s been patched by a user loader). This change was made in https://github.com/nodejs/node/pull/43363.

Because import.meta.resolve will be sync in browsers: whatwg/html#5572. Node’s version of import.meta.resolve should therefore be sync as well to avoid user confusion and code that works in one environment but breaks in the other; and import.meta.resolve calls the resolve hook (either Node’s internal one, or that internal one that’s been patched by a user loader). This change was made in nodejs/node#43363.

What's the intent for how import.meta.resolve interacts with preImport? I assume this means that import.meta.resolve will not invoke preImport? In that case, I'd say preImport isn't fit for purpose: we can't rely on it having been called for a corresponding resolve call, so if we need to load (e.g.) an import map as in the example to figure out how it should resolve, then that won't have happened. It also means it wouldn't be possible to use it for operations like resolving actual URLs over a network which I described in my 4th point here: https://github.com/nodejs/loaders/issues/64#issuecomment-1140251730.
This will lead to very confusing behaviour where import.meta.resolve will be inconsistent with the results of an actual import (and will usually be missed by authors since import.meta.resolve is not commonly used).
I wonder:

when "Move loaders off-thread" is implemented, won't that require async behaviour of resolve again? The only other options I can think of would be for resolve to never go off-thread (problematic for sharing state between hooks), or for the resolve call to be blocking like the old filesystem calls (and in that world, the resolve code itself can be as async as it likes in the other thread while the main thread blocks on it)

some of the use cases for async resolve code might be handled by running an operation once per file before any resolve calls, which is already available to usercode via the load hook, and perhaps just needs some added ability to share state between calls. I could imagine a world like this:
export function resolve(specifier, context, defaultResolve) {
  const importMap = context.moduleContext?.importMap; // moduleContext is null for the main entry point
  return /* ... */;
}

export async function load(url, context, defaultLoad) {
  const importMap = await doThing(url);
  return {
    ...defaultLoad(url, context, defaultLoad),
    moduleContext: { importMap }, // this is now available to all import/resolve calls from the current module
  };
}

This would solve use-cases like loading config or import maps which depend on the location of the importing file (and do not yet need knowledge of the imported file). But note that it will not solve the use-case of things like importing files over a network (which might need to do operations like trying file extensions)

I haven't had a chance to read this entire thread, so I might be repeating stuff, but here are my thoughts ahead of the meeting:

Thought experiment to validate proposals
Useful thought experiment for discussion:

imagine loader that allows mounting an async filesystem: could be networked, IPC, or not, but the point is it's async
imagine a loader that adds a new file extension to resolver algorithm

users really want to omit file extensions; I get asked about this a ton

imagine a loader that allows filesystem "overlay" of multiple virtual directories (perhaps for mocks?)

won't know which module to resolve to without attempting async stat of multiple candidates in the overlaid directories
Real-world use-case: this is what typescript does for outDir <-> rootDir & rootDirs: are essentially overlays
similar requirements to omitting file extensions, but I include this bullet point in case file extension omission is dismissed

imagine resolutions rely on reading package.json and tsconfig.json to correctly map paths

necessity of this is explained above

^-- Loaders for those use-cases need to compose with each other.  (compose/chain/whatever)
Concern that preImport is just async resolve
worried preImport will essentially need to run the full resolve.  The problem is:
a) need to async read stuff such as package.json or tsconfig.json
b) need to do the equivalent of async fs.stat to
c) the only way to know which of those things to read, is by stepping through the resolution logic (cannot pre-download all relevant files without doing resolution logic)
Given (c), we should be doing the resolution at the same time as the fetching.  In which case, we should not / can not be repeating that work in resolve.
If preImport is gonna need to do resolve, then loader authors will want some sort of reliable way to connect a preImport invocation to the subsequent resolve invocation.  (and the whole exercise will feel a bit silly and un-ergonomic)  Pseudo code to illustrate the concept without prescribing an implementation:
export async function preImport(url, {reliableWayToLinkInvocations}) {
  resolutions.set(reliableWayToLinkInvocations, await doResolution(...))
}
export async function resolve(url, {reliableWayToLinkInvocations}) {
    return resolutions.get(reliableWayToLinkInvocations);
}

Should we keep this open? Per our last meeting this is the backup plan if we can’t get an appears-to-be-sync resolve working via threads.

Closing as we’re going in a different direction per the last meeting, but happy to reopen if there’s some reason to keep working on this in parallel.


AutoPr-Blueprint-filizt-REST Spec PrNumber 5872

@dsgouda please don't close the PR, we don't have any customization this time. When ready, the changes can be merged. Could you help with the CI failures?

@filizt failures are unrelated to the changes. will merge soon


Add support for EBNF

:wave: @dwijnand! I'm assuming that EBNF is https://en.wikipedia.org/wiki/Extended_Backus–Naur_Form?
If so, we'd welcome a pull request implementing this. You can read more about how to that that here: https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language

Hey. Thank you for the link. I only mentioned it because I created a gist and couldn't get it to highlight in any way, but I don't use EBNF often enough to look into implementing the highlighting myself.

@dwijnand I can take care of adding support for BNF if you'd like. I'll just need a few pieces of information:

Do you have a few BNF files under open source license I could use as samples/examples?
Is .bnf the main file extension? Are there other?
Is there an official logo or color?

https://github.com/mackoj/language-bnf could be used as a grammar for syntax highlighting.

There are sections of EBNF is the Scala spec: https://github.com/scala/scala/search?utf8=✓&q=ebnf
I would assume .ebnf, but I'm not sure
Doesn't look like there are either.

Erm, EBNF (and BNF) is less a language than a formalised notation...

True, but it still has syntax that would be more pleasant to read with some highlighting. Are you saying it's out of scope for linguist?

Yes, I would say so.
First and foremost, Linguist exists to identify languages (with certain data formats added to stop it misclassifying some languages based on shared file extensions, etc). Managing syntax highlighting is only a secondary responsibility.

Support for EBNF and the .ebnf file extension seems to have been added in the meantime, but not BNF .bnf or ABNF etc.

Cool. Thanks for letting me know.

Hi @Crissov  and others, .ebnf is not working, see syntax.ebnf file: no syntax highlighting.

Well, the file is correctly recognised by Linguist as EBNF:
λ trazdia (master): $LING/bin/linguist docs/fragId-syntax.ebnf
fragId-syntax.ebnf: 39 lines (22 sloc)
  type:      Text
  mime type: text/plain
  language:  EBNF

But this is happening in Lightshow too. I suspect there've been changes upstream, in the grammar that's providing EBNF highlights...
I'll investigate.

Ah wait. You're not looking at an EBNF grammar. :-) I'm not sure what that is, but it isn't EBNF. Notice how the syntax is very different to the one you're using. And you're also using DocBlock-style comments, which I've never seen used in an *BNF-type grammar before...

Hi @Alhadis, thanks (!). Yes very different, how to obtain syntax highlighting of the popular W3C and http://www.bottlecaps.de/rr/ui syntax?

Okay, there's your answer. The EBNF example you showed earlier is actually an "XQuery Grammar", which is an extension of it.

Hi @Alhadis,
Hum... We advance in the consensus, summarizing:

you expressed the fact: the standard adopted at github/linguist for the language name "EBNF" was ISO 14977, so it is not an language, is a dialect, we can say  the "EBNF-ISO"  dialect. Other people need (it is  also popular and important) other dialect, the "EBNF-W3C" (ref. TR/xml/#sec-notation and TR/xquery/#nt-bnf)...

We, the users of the  EBNF-W3C dialect,  need the solution:  syntax highlighting our dialect.

In other words: the semantic of the language label ebnf is "language dialect EBNF-ISO", and there are users that need other dialect, the ebnf-w3c... How to create the new dialect from the old dialec, with minimal cost of work and time?

Well, I'd be more than happy to pledge my help,...

Thanks @Alhadis (!), I am starting, but only will really work next week... The first task where I need help is to understand how to express space as \s+  instead ,  and how to express * and ? operators over (...) gorup, all at Syntaxes/EBNF.tmLanguage.

Is there anyway to get ebnf highlighting in markdown segments?
i.e. something like
\```enbd
char = "c"
\```


JSON decode error parsing is_encryption_enabled

When running the example app on my Mac (either using native dotnet for Mac, or docker), after completing the 2FA, I receive an internal server error:
An unhandled exception occurred while processing the request.
InvalidOperationException: Cannot get the value of a token type 'True' as a string.
System.Text.Json.Utf8JsonReader.GetString()

JsonException: The JSON value could not be converted to System.String. Path: $.access_device.is_encryption_enabled | LineNumber: 0 | BytePositionInLine: 646.

Digging into the code and server's response, it seems this client is expecting a String value for is_encryption_enabled, but the server is returning the boolean true, causing the Deserialization error and exception.
This same issue also like affects is_firewall_enabled and is_password_set
Snippet of JSON from the server response:
"os":"Mac OS X","os_version":"12.3.1","browser":"Chrome","browser_version":"100.0.4896.75","flash_version":"uninstalled","java_version":"uninstalled","is_encryption_enabled":true,"is_firewall_enabled":true,"is_password_set":true},

@tloveland1 and @devtendenz, I'd appreciate your input on this issue.  I see a few ways to address this:
A) Keep the field type 'string' and the possible values would be 'true', 'false', or 'unknown' - then it's the responsibility of anyone who cares about those fields to deal with the fact that this is effectively a string boolean
B) Change the field type to bool? so the possible values are true, false, or null
C) Leave the fields out entirely
Any ideas which would be most suitable for users of this client?

D) make the field type object :yolo:

Fixed by https://github.com/duosecurity/duo_universal_csharp/commit/c3e3b1293e5809d26c3a0c94af182c86c7d6ad01


update release image tag with suffix '-rc'

Use case

Describe the solution you'd like

Describe alternatives you've considered

Additional context

https://github.com/timeplus-io/proton/pull/126

(Jove Github Bot) added it to the current sprint.

done in sprint52

(Jove Github Bot) moved this ticket out of the GitHub project(up to 1200 tickets for one project).


Sync with Latest Templating Engine

The next release of the templating engine, going out today or tomorrow, as some breaking changes to semi-private data structures which you may have used. I'm not sure. But if you accessed the executionContext property anywhere, that has been renamed to bindingContext.

executionContext doesn't appear to have been referenced anywhere, closing for now (will re-open if needed)


⚠ ETF has degraded performance

In 0cf9a55, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 5510 ms

Resolved: 거래대금 performance has improved in fb6bd2a.


Error Handling System

Have a common error handling system. Between responses and catching for the handler.

Done, now res.error and res.sendError exist.


binaryen: 44 -> 45

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/binaryen/versions.
These checks were done:

built on NixOS
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-shell -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-shell --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-opt -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-opt --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-merge -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-merge --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-metadce -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-metadce --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/asm2wasm -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/asm2wasm --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm2asm -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm2asm --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/s2wasm -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/s2wasm --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-emscripten-finalize -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-emscripten-finalize --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-as -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-as --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-dis -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-dis --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-ctor-eval -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-ctor-eval --help got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-reduce -h got 0 exit code
ran /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-reduce --help got 0 exit code
found 45 with grep in /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45
directory tree listing: https://gist.github.com/d46c9206b6d0b68c0f9dcc3bf83b6540

cc @asppsa for review

Success on x86_64-linux (full log)
Attempted: binaryen
Partial log (click to expand)
shrinking /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-merge
shrinking /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-metadce
shrinking /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-as
shrinking /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin/wasm-reduce
shrinking /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/lib/libbinaryen.so
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/lib  /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45/bin
patching script interpreter paths in /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45
checking for references to /tmp/nix-build-binaryen-45.drv-0 in /nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45...
/nix/store/vqjm60x3syaf55njww7a4g4dq7r0x6qy-binaryen-45

Success on x86_64-darwin (full log)
Attempted: binaryen
Partial log (click to expand)
-- Installing: /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/bin/wasm-emscripten-finalize
-- Installing: /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/bin/wasm-as
-- Installing: /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/bin/wasm-dis
-- Installing: /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/bin/wasm-ctor-eval
-- Installing: /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/bin/wasm-reduce
post-installation fixup
strip is /nix/store/0fzpxnsanc02i4jsb1yhchjp4p62b2n3-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/lib  /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45/bin
patching script interpreter paths in /nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45
/nix/store/s4aaxrk5nvdxwczs1dxav4jiakyb143w-binaryen-45

Success on aarch64-linux (full log)
Attempted: binaryen
Partial log (click to expand)
shrinking /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/bin/wasm-metadce
shrinking /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/bin/wasm-merge
shrinking /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/bin/wasm-opt
shrinking /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/bin/wasm-shell
shrinking /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/lib/libbinaryen.so
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/lib  /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45/bin
patching script interpreter paths in /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45
checking for references to /build in /nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45...
/nix/store/9ma4xlza15mrxdrh86yw9g48fa8i9mvg-binaryen-45


[BugFix] Fix issue with routine Load audit logging bug

This PR resolves the issue of dbname and routine load job name being displayed as null in the audit logs when a user connects to the FE's follower node and creates a routine load job.

What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[x] 2.5
[ ] 2.4

[FE PR Coverage Check]
:disappointed: fail : 6 / 9 (66.67%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/AstToStringBuilder.java
6
9
66.67%
[337, 338, 344]

[FE PR Coverage Check]
:heart_eyes: pass : 9 / 9 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/AstToStringBuilder.java
9
9
100.00%
[]

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Remove console log

That log statement adds noise to the console to report something going right. If logging is required for debugging, it should be togglable in settings and / or report when something goes wrong.
Presumably, if atom-package-deps did have an issue that prevented the then clause from activating, it would throw an error and this will catch it.

@Arcanemagus Can you take a look at this? It should be a reasonable and straightforward change. Maybe more could be done with the error, but this PR is to clean up my console, not add functionality.


tflite micro without any of the other stuff?

Is it possible to get the tensorflow folder without any of the board specific things, examples, etc to end up with just the simple tensorflow lite micro library?

I suggest trying Make project generation:
make -f tensorflow/lite/micro/tools/make/Makefile generate_hello_world_make_project

This will generate a standalone Makefile project under tensorflow/lite/micro/tools/make/gen/<host system>/prj/hello_world/make
You can then modify / replace the hello_world example with your own code, or delete it entirely if you just wish to copy core TFLM files into your own project.
Alternatively, you can build libmicrolite.a to link into your project by running:
make -f tensorflow/lite/micro/tools/make/Makefile microlite

This will generate libmicrolite.a under tensorflow/lite/micro/tools/make/gen/<host system>/lib/libtensorflow-microlite.a

One more alternative would be to use tensorflow/lite/micro/tools/project_generation/create_tflm_tree.py directly.

Please see https://github.com/tensorflow/tflite-micro/issues/332#issuecomment-888546457 for more details on the Python project generation script which is the recommended way going forward.


Reduce technical debt / Code Smells

Description
This pull request is very simple and aims to reduce the technical debt. It specifically targets the "Duplicate casts should not be made" rule in SonarQube.
Update:
As pointed out by @ealsur, the SonarQube fixes touched OSS files that probably should't be modified. To make this contribution more valuable, I fixed the following ReSharper issues:

"Replace if statement with null-propagating code" rule
"Merge sequential checks in && or || expressions"  rule

Type of change

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

/azp run

/azp run