Add missing strings to json file from page forbidden

Changes:

Add missing strings from the page forbidden that informs a user that he needs to log in.
The strings were missing so they were not pushed to crowdin and could not be translated.

Does it mean you want me to make that change? I'm not really sure. I was simply adding them to the json file.

If you can, you can do this yourself.

@Sekhmet I'm sorry, I don't know how I would achieve a good solution. I am going to submit an issue instead, explaining which strings ids need to be fixed.

I can create diff for you so you can apply it and commit if you want.

I will leave it to you. Working with git is not a problem but creating the formatted message with embedded link so that it could be processed as one whole string is hard for me. Working on the issue with all details


#1378 Replaced WebL10n to i18next in Maze Web Activity

@llaske pls review this pr
attaching ss of results
Replaced WebL10n to i18next in Maze Web Activity

Nice. Thanks.


bug(copypasta.py) replace "*" with "*"

Original Issue: #16
Fixes #16
Replaced all * with \* in copypasta.py file

alright, everything seems fine! thank you for your contribution to pekobot :))


Breaking changes in lcms_parser

There are breaking changes introduced in https://github.com/cooper-group-uol-robotics/lcms_parser/pull/1, which change how UPLC-MS traces are accessed by the parser. This is required by MassLynxSDK licensing, which is developed and maintained by Waters.
There are currently no plans to fix it beyond requiring lcms_parser<2.0.0. It should be addressed in the development of future codebases that build on synthesis_bots for other projects but not for this specific set of workflows.

New codebase will either require a license or operate on already transcribed open format MS files.

New codebase will either require a license or operate on already transcribed open format MS files.


Reorder matplotlib backend to run figure.draw() before self.send_deepforge_update()

Might be helpful for #1745, #1747
You probably want to re-order https://github.com/deepforge-dev/deepforge/blob/325bf698c3b23816bf47f5a0482f5b73d92f0b7b/src/plugins/GenerateJob/templates/backend_deepforge.py#L357-L359 to run figure.draw() first as that will trigger various draw-time things (like limits) that you are capturing.
Originally posted by @tacaswell in https://github.com/matplotlib/matplotlib/issues/18022#issuecomment-662682747

Closing this as this has been addressed in #1747.


Open redirect vulnerability exposed when localePrefix: 'as-needed'

Description
Hi, I have found an open redirect vulnerability when localePrefix is 'as-needed' . This vulnerability allows an attacker to redirect users to a malicious site by manipulating URL parameters.
The vulnerability occurs due to decodeURI doesn't escape decoded backslashs(%5C & %5c) and will decode them into '\' as an unsafe externalPathname. This unsafe externalPathname will be passed to new URL(normalizeTrailingSlash(url), request.url) to be the redirect destination. But URL will internally replace backslashs with slashes and take it as a new authority (host) part, the host will be parsed wrongly due to this bug(or feature?). Here's an example of what I'm talking about:
console.log(new URL("/\\example.org", "http://google.com"))
console.log(new URL("//example.org", "http://google.com"))

/*
*  They both output:
*  {
*    href: 'http://example.org/',
*    origin: 'http://example.org',
*    protocol: 'http:',
*    username: '',
*    password: '',
*    host: 'example.org',
*    hostname: 'example.org',
*    port: '',
*    pathname: '/',
*    search: '',
*    searchParams: URLSearchParams {},
*    hash: ''
*  }
*/

Example:
My project reproduces this issue, and you can access it from this url
https://nextempura.vercel.app/en/%5Cexample.org

Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://github.com/hblee12294/nextempura
Reproduction description
Steps to reproduce:

Clone this repo
Run pnpm install / npm install / yarn install
Open localhost:3000 in the browser
Visit http://localhost:3000/en/%5Cexample.org

Expected behaviour
The website will be directed to example.org

I'll create a pr to fix this issue shortly.


Resetting CVP via the arista.avd.eos_config_deploy_cvp role fails [devel]

Issue Type

[x] Bug Report

Summary
A failure occurs when performing a reset using the playbook below for example using the latest devel version.

Component Name
eos_config_deploy_cvp
Steps to reproduce

---
- name: Clenup CVP in default configuration
  hosts: cv_server
  connection: local
  gather_facts: false
  collections:
    - arista.avd
    - arista.cvp
  tasks:
    - name: run CVP provisioning
      import_role:
        name: arista.avd.eos_config_deploy_cvp
      vars:
        container_root: 'DC1_FABRIC'
        configlets_prefix: 'DC1-AVD'
        device_filter: 'DC1-'
        state: absent

Expected results

The playbook to perform a reset in CVP of all devices.
$

Actual results

Reset tasks are created but not executed. The below is output:

ASK [eos_config_deploy_cvp : Execute pending tasks on cv_server] **************************************************************************************************************************************************************************************************************************************************
fatal: [cv_server]: FAILED! =>
  msg: |-
    The task includes an option with an undefined variable. The error was: 'devices_result' is undefined

    The error appears to be in '/projects/ansible-avd/ansible_collections/arista/avd/roles/eos_config_deploy_cvp/tasks/absent.yml': line 20, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    - name: "Execute pending tasks on {{ inventory_hostname }}"
      ^ here
    We could be wrong, but this one looks like it might be an issue with
    missing quotes. Always quote template expression brackets when they
    start a value. For instance:

        with_items:
          - {{ foo }}

    Should be written as:

        with_items:
          - "{{ foo }}"

Impacted file: eos_config_deploy_cvp/tasks/absent.yml
Root Cause: variable name is not using uppercase as defined in previous tasks meaning ansible cannot access to it.
Introduced by commit https://github.com/aristanetworks/ansible-avd/commit/ac271b2bc36388e3d0ff7a8e02db1bb568df5063


Upgrade to basepom 12.6

@tpetr @ssalinas @wsorenson

Can you usher this slowly @ssalinas

sure thing, will do the baragon one as well

Baragon one will have a lot more version changes because its moving 2 major versions of basepom ahead, this should be a lot safer


Switch to new C helpers

After https://github.com/mattn/go-oci8/pull/286

Can any of the old branches be deleted?
https://github.com/mattn/go-oci8/branches

Good to go

Thanks


New version: Soss v0.4.0

Registering package: Soss
Repository: https://github.com/cscherrer/Soss.jl
Created by: @cscherrer
Version: v0.4.0
Commit: 5ca1c83a45630bd5927871849f721450688d383e
Reviewed by: @cscherrer
Reference: https://github.com/cscherrer/Soss.jl/commit/5ca1c83a45630bd5927871849f721450688d383e#commitcomment-35086510

Needs a rebase.


CI/CD Package Deployment Pipeline

Institute a CI/CD pipeline for automating package deployment of our core library and create-skeleton-app (CLI) to NPM.
Below is the release procedure for either application. I've included everything for context. The NPM portion is a small bit of this.
Core Library

NOTE: the day before I generate the release notes and blog thumbnail

Apply any last minute PRs or fixes
Upload any revisions to the release notes
Unpin old release notes, pin new release notes
Set version on dev branch and push
Create PR to merge dev -> master branch
Switch and pull master branch locally
Delete the /package directory to ensure clean build
In root, use npm run package to generate the package locally
Recommended: test locally with tarball

Move into /packge directory, run npm pack to generate tarball
Copy tarball to a newly generate project (via CLI)
Remove old Skeleton package, install tarball
(remember to follow migration steps)
Verify the basics are working

In root, use npm run publish to publish to NPM
Switch local back to dev branch (easy to forget this!)
Tag the release on GitHub

Use version to create tag (without "v")
Add version as title (with "v")
Copy emoji list and link to full release notes discussion
Set as a pre-release (if relevant)

Copy the release URL into the release notes discussion
Setup blog post on Ghost

Title is Skeleton v(version)
Use markdown block to add content
Fix feature links to tickets, hit return to drop down a line
Apply an exerpt
Upload featured graphic
Publish
Review on production doc site

Announce on Twitter
Announce on Discord #announcements

CLI
(space reserved)

@niktek I'm closing this for now, let's circle back post v1


JSON DecodeError with "minizinc:experimental"

solver: "minizinc:experimental"
CPMpy: version v0.9.9 commit e79b3afedc934a9437c2ddb3a9f54d7e2d7bd3ee
minizinc-python release version 0.7.0 commit {https://github.com/MiniZinc/minizinc-python/commit/a195cf63fcfbc98665d70ab64efb5424db25bd7e)
MiniZinc's experimental solver raise a JSON error, "minizinc:gecode" and "minizinc:gist" do crash on this file as well, but seems to be a different bug which I will report in a separate issue.
minimized.zip
from cpmpy import *

file ="minimized"  # don't forget to unzip
m=Model().from_file(file)
m.solve(solver='minizinc:experimental')

expected behavior:
No crash like other solvers ("minizinc:ortools" ...)
bug found while working on my master thesis.

I don't think we should expect stable behavior from a solver that is called 'experimental'. I have never heard of it, not sure we should report it upstream with minizinc, maybe just leave the 'experimental' out of the fuzz tests? (if you agree, feel free to close)


Update default image to ubuntu 20.04 and golang to 1.16.4

I had to revert the change because the protos don't build with newer version. There is most likely a fix for it, but it should be dealt with in another PR. I think that's also the reason why it was skipped last time around.


cfa-vram

hi, thanks for your excellent work. I'm confused about one question. In my impression, the VRAM that the text2video-zero model occup will increase as the number of frames referenced by cross-frame attention. Why do you use full cross-frame attention but only need 2080ti---only 11GB?

hi, I'm alse confused about the timesteps of interleaved-frame smoother. The paper says that : "interleaved-frame smoother is performed on predicted RGB frames at timesteps {30, 31} by default" ,  But your code use 19, 20 as default. How is this parameter determined， Why not do smoother on all DDIM steps？Have you done ablation for this part of the experiment? I don't seem to see it in the paper.


<!--vector

Actively monitored security email alias for our project:
1. Have a user base not limited to your own organization.
2. Have a publicly verifiable track record up to present day of fixing security issues.
3. Not be a downstream or rebuild of another distribution.
4. Be a participant and active contributor in the community.
5. Accept the Embargo Policy.

6. Be willing to contribute back.

7. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.
Originally posted by @thekiller880 in https://github.com/etcd-io/etcd/issues/12915

Actively monitored security email alias for our project:
1. Have a user base not limited to your own organization.
2. Have a publicly verifiable track record up to present day of fixing security issues.
3. Not be a downstream or rebuild of another distribution.
4. Be a participant and active contributor in the community.
5. Accept the Embargo Policy.

6. Be willing to contribute back.

7. Have someone already on the list vouch for the person requesting membership on behalf of your distribution.
Originally posted by @thekiller880 in https://github.com/etcd-io/etcd/issues/12915


Enabling OSC freezes avatar in place

Describe the bug
Enabling OSC freezes my avatar in place for non-local players.
To Reproduce
Steps to reproduce the behavior:

Enable OSC via the Action Menu.

Expected behavior
I expect my movement to be viewed properly by other players.
Screenshots (Videos)
First video
Second video
Info:

Type: Desktop
w_2022.1.1-48b5c3fb5a

Additional context
I am still able to move around normally, and I appear to teleport to my new location and freeze again when I reset my avatar (as shown in the second video). The only thing that 'fixes' the issue is disabling OSC and re-joining the world.
This issue occurs on both the main and [ik-beta] versions, and persisted through a reinstall of VRChat. Desktop (Non-VR) mode is not affected by this bug.

I found that this happens for me only in some worlds. This world does it reliably:
https://vrchat.com/home/launch?worldId=wrld_323e9cea-1f83-45d9-8a1d-c7a9e50ee191&instanceId=41651~hidden(usr_259294ba-b773-4531-9971-ef1c5aa3d385)~region(eu)~nonce(3A37DB812123F524C1CE9B1B60265BAC57268A5A26038C53)

This is also reproducible in https://vrchat.com/home/world/wrld_0ec97c4f-1e84-4a3a-9e3a-fa3075b6c56d (at least, prior to the update yesterday; haven't checked since then)

Full Body Calibrate and Everything's Alright also seem to consistently produce the issue, though I've also found that so far "older" worlds (specifically Pillow Fort Builder and Yayoi Onsen) allow me to interact normally with others without any problems.

Almost a month later, I've found a workaround.
So, the combination of things that have solved this issue for me:
Step 1: Going to the VRChat website and clearing my block/mute/shown avatar lists.
After this, most of my avatars worked, but some would still exhibit the same issue, and I'd have to rejoin with OSC off or rejoin in a different avatar to fix it.
Step 2: Removing all stations/chairs from my avatars.
A few of my avatars had chairs on them so that I could pick smaller friends up and carry them around with me. These specifically were the ones that continued to break even after clearing my blocklist. After I removed the chairs and published the updated avatars, I no longer experienced the issue.
Hope this is helpful to others. I hesitate to close this since the true source of the problem has yet to be solved, but at the moment all works fine for me.


Deep linking is not working when app is closed/killed

Description
If app in background

specific screen will open as expected. (through deeplink)

If app is not in background or closed

it will show first screen only. (through deeplink)

I tried some of the work arounds mentioned on stackoverflow but they dont seems to work
References: Deep linking - doesn't work if app is closed , React Native - Deep linking is not working when app is not in background (Android, iOS), Deep linking not working when app is in background state React native
React Native version:
System:
OS: macOS 10.15.7
Binaries:
Node: 16.8.0 - /usr/local/bin/node
npm: 7.22.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: ^0.64.0 => 0.64.2
Expected Results
It should open the specific screen through deep link when the app is in closed/killed state also.
Snack, code example :
linking.js
 const config = {
   screens: {
      Home:'home',
      Profile:'profile,
     },
  };

 const linking = {
  prefixes: ['demo://app'],
  config,
};

 export default linking;

App.js
import React, {useState, useEffect} from 'react';
import {Linking} from 'react-native';
import AsyncStorage from '@react-native-async-storage/async-storage';
import {createStackNavigator} from '@react-navigation/stack';
import {NavigationContainer} from '@react-navigation/native';
import linking from './utils/linking';
import {Home, Profile, SplashScreen} from './components';

const Stack = createStackNavigator();

const App = () => {

function _handleOpenUrl(event) {
  console.log('handleOpenUrl', event.url);
}

  // this handles the case where a deep link launches the application
  Linking.getInitialURL()
    .then((url) => {
      if (url) {
        console.log('launch url', url);
        _handleOpenUrl({url});
      }
    })
    .catch((err) => console.error('launch url error', err));

  useEffect(() => {
    Linking.addEventListener('url', _handleOpenUrl);
    return () => {
      Linking.removeEventListener('url', _handleOpenUrl);
    };
  }, []);

  return (
    <NavigationContainer linking={linking}>
      <Stack.Navigator
        initialRouteName="SplashScreen"
        screenOptions={{...TransitionPresets.SlideFromRightIOS}}>
        <Stack.Screen
          name="SplashScreen"
          component={SplashScreen}
          options={{headerShown: false}}
        />
        <Stack.Screen
          name="Home"
          component={Home}
          options={{headerShown: false, gestureEnabled: false}}
        />
        <Stack.Screen
          name="Profile"
          component={Profile}
          options={{headerShown: false, gestureEnabled: false}}
        />
      </Stack.Navigator>
    </NavigationContainer>
  );
};

export default App;

I'm facing the same issue. Any solutions?

same here. Working with react-native 0.65.1 version.

same for me too

I found a work around to handle the situation, & assuming that your app has Auth flow as well, if not here's a solution to support Auth flow for deep-linking.
What i had noticed was when the app was in background the user's app state was in sync and deep link was working as expected and was showing the correct info but when I close/kill the app and open it from a deep-link then the user's data isn't found and it was failing because user's state is checked during app launch from splash screen but during an app launch through deep link it doesn't open from splash screen it directly opens the deep linked screen.
So to resolve it and show the correct screen with proper info i'm adding a check on each launch when its from deep link.
Profile.js
import React from 'react'
import {CommonActions} from '@react-navigation/native';
import DeepLinkLoader from '../../widgets/deeplinkloader; //A loader component to show only when deep link is opened

const Profile = () => {
 const [deepLoading, setDeepLoading] = React.useState(false);
 let isDeepLinked = React.useRef(false);

  //Handling back functionality of deep link
 // If this is not handled then on press of back the app exits completely to handle that i'm setting it to route to home screen.
  const onDeviceBackPress = () => {
    if (isDeepLinked.current) {
      navigation.dispatch(
        CommonActions.reset({
          index: 0,
          routes: [{name: 'HomeScreen'}],
        }),
      );
      return true;
    }
  };

  React.useEffect(() => {
    if (user.id === undefined) {
      setDeepLoading(true);
      isDeepLinked.current = true;
     //Storage has the `userId` which i'm fetching & making an api call to fetch the
     //user details and set it to state and then load the screen
      Storage.instance.getData('userId').then((id) => {
        API.instance.get(`/users/${id}/all`).then((res) => {
          // Adding the user to the state & setting the deep link to false to show the screen.
          dispatch(addUser(res));
          setDeepLoading(false);
        });
      });
    }
    const backHandler = BackHandler.addEventListener(
      'hardwareBackPress',
      onDeviceBackPress,
    );

    return () => backHandler.remove();
  }, []);

// If the screen is opened from a deep link then the below loader will show
// & once the user info is set then it will show the actual screen
if (deepLoading) return <DeepLinkLoader />;

  return (
       <View>
          //Profile info
        </View>
  )
}

export default Profile

When a closed app is launched from deep link it checks if user's data is found or not, if not found then it makes an api call and sets it to the state through redux & show the screen, incase the `userId` is also not found then it will fallback to the login screen.

same here

is there any solution?
i am also facing same issue.

is there any solution?
i am also facing same issue.

I was having same problem with I fixed it by adding "content available" on iOS .   Here is link to SO I posted https://stackoverflow.com/a/70869289/4724718

@blueprin4 is I am facing issue in android only.
do u have any idea how to fix for android?

Nice, seems like a possible solution @vitorbetani. Could I ask where you call your getInitialUrl function? I run mine in a useEffect inside a child component, and Linking.getInitialUrl just returns nothing.

I met the same issue (android and ios).
I made a check for permissions and auth context for every open link - it works correctly.
Any chance to solve it?

Same here, any updates ?

hello @vitorbetani  what is inside the handleDeepLinkingUrl i would like to use your code but i cant because it said handleDeepLinkingUrl is not defined please help :(

hello @vitorbetani what is inside the handleDeepLinkingUrl? I would like to use your code but i cant because it said handleDeepLinkingUrl is not defined please help :(

Hey Fernando, the handleDeepLinkingUrl is a function of your own, you can create and define what to do with the income URL. For example, you can have a switch/case to send the user to a specific screen of your app.

I'm facing the same issue in iOS only.
I handle url for deep link after getting it by calling Linking.getInitialURL() in onReady handler for NavigationContainer.
It works in Android, but not in iOS.

related?
#28727

I had the same problem, but only on ios. I've read the documentation of react native, react navigation, github issues, stack overflow questions over and over again.
Nothing worked.
But after all of that i implemented this: await Linking.canOpenURL(initialUrl) it works on ios with all type of deep linking variations (custom schema, https and dynamic link).
Can somebody confirm this behaviour?

Hellow @vitorbetani , Sorry to ask you again! My only doubt is what navigationref we need to use to navigate to particular screen? Can you give me an example?

I tried @vitorbetani's approach and it didn't work for me on ios. Fyi, I'm currently using a less pretty approach with settimeout instead but it's working in my case
`useEffect(() => {
notificationListener.current =
Notifications.addNotificationReceivedListener((notification) => {});
responseListener.current =
  Notifications.addNotificationResponseReceivedListener((response) => {
    let url = response.notification.request.content.data.url;

    setTimeout(() => {
      Linking.openURL(url);
    }, 100);
  });

return () => {
  Notifications.removeNotificationSubscription(
    notificationListener.current
  );
  Notifications.removeNotificationSubscription(responseListener.current);
};

}, []);`

For me, the following is working on iOS and Android:
import * as Linking from 'expo-linking'

// prefix for deep-links
const prefix = Linking.createURL('/')

// config for deep-links
const config = {
	screens: {
		...
		},
	},
}

// variable for url
let deepLink

// linking config for navigator
const linking = {
	prefixes: [prefix],
	config,
	async getInitialURL() {
		// Check if app was opened from a deep link
		deepLink = await Linking.getInitialURL()
		// Don't handle it now - wait until Navigation is ready
		console.log('DeepLink URL:', deepLink)
	},
}

// open url if deepLink is defined
const openDeepLink = async () => {
	if (deepLink) Linking.openURL(deepLink)
}

// check when react navigation is ready
const onNavigationReady = async () => {
	// if deep link exists, open when navigation is ready
	await openDeepLink()
}

function AppNavigator() {
	return (
		<NavigationContainer onReady={onNavigationReady} linking={linking}>
			<Stack.Navigator>
				<Stack.Group>
					...
				</Stack.Group>
			</Stack.Navigator>
		</NavigationContainer>
	)
}

const linking = { 	prefixes: ['app://'], 	config: { // your config // }, 	async getInitialURL() { 		return Linking.getInitialURL() 	}, }
this code worked for me

One solution is to wait a little before load url

Here a little write-up how I was able to solve the issue in my application. Perhaps it is helpful.
Delaying the opening of the deep link with setTimeout or similar is not a reliable solution as proposed by me earlier.
 setTimeout(() => {           Linking.openURL(url);         }, 100);
If the deep link is referring to a stack navigator (here: AppNavigator with isAuth = false) that is not yet rendered, the linking does not work.
 return  isAuth ? <AppNavigator /> : <AuthNavigator />
So I'm waiting until the AppNavigator is rendered, and then open the deep link which I stored in a useRef:
`
/*** navigation/index.jsx ***/
const deepLinkRef = useRef();
const [appNavigatorReady, setAppNavigatorReady] = useState(false);
useEffect(() => {
responseListener.current =
Notifications.addNotificationResponseReceivedListener((response) => {
let url =
response.notification?.request?.content?.data?.url ??
Constants.manifest.scheme + '://';
deepLinkRef.current = url;
   // Open link when notification is received and AppNavigator is rendered - app is in foreground OR background
    if (appNavigatorReady) {
      Linking.openURL(url);
    }
// Open link after waiting until AppNavigator is rendered - app was killed

if (appNavigatorReady && deepLinkRef.current) {
  Linking.openURL(deepLinkRef.current);
}

return () => {
  Notifications.removeNotificationSubscription(responseListener.current);
};

}, [appNavigatorReady]);
return  isAuth ?  :
/*** AppNavigator.jsx ***/
useEffect(() => {
let ignore = false;
if (!ignore) {
  onLayout(true);
}
return () => {
  ignore = true;
};

}, []);
`

here what i have done in my side
i modified didFinishLaunchWithOption and intercepted the payload of notification and get the deeplink url then created new launch options and start app with these options and it works like a charm no need for intervals neither timeouts
`  NSMutableDictionary *newLaunchOptions = [NSMutableDictionary dictionaryWithDictionary:launchOptions];
if (launchOptions[UIApplicationLaunchOptionsRemoteNotificationKey]) {
NSDictionary *remoteNotif = launchOptions[UIApplicationLaunchOptionsRemoteNotificationKey];
// here goes specific selection according to the payload structure we receive from cleverTap
// example here: { wzrk_dl : 'partoo://reviews' }
// see https://docs.clevertap.com/docs/faq#q-what-is-the-format-of-the-payload-of-the-push-notification-for-ios
if (remoteNotif[@"wzrk_dl"]) {
NSString *initialURL = remoteNotif[@"wzrk_dl"];
if (!launchOptions[UIApplicationLaunchOptionsURLKey]) {
newLaunchOptions[UIApplicationLaunchOptionsURLKey] = [NSURL URLWithString:initialURL];
}
}
}
RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:newLaunchOptions];`

Based on https://documentation.onesignal.com/v7.0/docs/react-native-sdk#handlers
Deep linking in iOS from an app closed state
And you must be Modify the application:didFinishLaunchingWithOptions in your AppDelegate.m file to use the following:
NSMutableDictionary *newLaunchOptions = [NSMutableDictionary dictionaryWithDictionary:launchOptions];
    if (launchOptions[UIApplicationLaunchOptionsRemoteNotificationKey]) {
        NSDictionary *remoteNotif = launchOptions[UIApplicationLaunchOptionsRemoteNotificationKey];
        if (remoteNotif[@"custom"] && remoteNotif[@"custom"][@"u"]) {
            NSString *initialURL = remoteNotif[@"custom"][@"u"];
            if (!launchOptions[UIApplicationLaunchOptionsURLKey]) {
                newLaunchOptions[UIApplicationLaunchOptionsURLKey] = [NSURL URLWithString:initialURL];
            }
        }
    }

RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:newLaunchOptions];

also in react-navigation:
https://reactnavigation.org/docs/deep-linking/
const linking = {
    prefixes: ["https://example.com", "example://"],
    config,
    async getInitialURL() {
      const url = await Linking.getInitialURL();
      if (url != null) {
        return url;
      }
    },
  };

<NavigationContainer linking={linking}>
   ...
</NavigationContainer>

For me, my goal is to redirect the user to the specific pages when the notification is clicked.
The below code works on iOS and Android devices.

Deep linking : can redirect user to specific page when App is in Foreground, but not killed / quitted.
If your notification not isn't used for deep linking. You can place onNotificationOpenedApp in index.js.

import * as Linking from "expo-linking";
import messaging from "@react-native-firebase/messaging";

const prefix = Linking.createURL("/");

const config = {
  screens: {
    ConnectFitness: {
      path: "fitness/:id",
      parse: {
        id: (id) => `${id}`,
      },
    },
    EventDetail: {
      path: "eventDetails/:id",
      parse: {
        id: (id) => `${id}`,
      },
    },
  },
};

const linking = {
  prefixes: [prefix],
  config: config,
  async getInitialURL() {},
  subscribe(listener) {
    const onReceiveURL = ({ url }) => listener(url);

    Linking.addEventListener("url", onReceiveURL);

    const unsubscribeNotification = messaging().onNotificationOpenedApp((message) => {
      const url = message?.data?.link;

      // for deep linking
      if (url) {
        listener(url);
      }
    });

    return () => {
      Linking.removeEventListener("url", onReceiveURL);
      unsubscribeNotification();
    };
  },
};

export default linking;

For handling the killed state notification, I just placed this is the Splash Screen.

async function getNotification() {
  try {
    const initialNotification = await messaging().getInitialNotification();

    if (initialNotification) {
      const { link } = initialNotification;

      // this is only for deep linking
      Linking.openURL(initialNotification?.data?.link);
    }
  } catch (error) {
    console.log(error);
  }
}

This is the body of my notification:

    let message = {
      tokens: ["TOKEN1", "TOKEN2"],
      data: {
        notifee: JSON.stringify({
          title: title,
          body: body,
          android: {
            channelId: "sound",
            smallIcon: "ic_launcher",
            pressAction: {
              id: "default",
              launchActivity: "default",
            },
          },
        }),
        link: "myApp://eventDetails/500",
      },
      notification: {
        title: title,
        body: body,
      },
      apns: {
        payload: {
          aps: {
            // Important, to receive `onMessage` event in the foreground when message is incoming
            contentAvailable: 1,
            // Important, without this the extension won't fire
            mutableContent: 1,
          },
          headers: {
            "apns-push-type": "background",
            "apns-priority": "5",
            "apns-topic": "org.test.myApp", // your app bundle identifier
          },
        },
      },
      android: {
        priority: "high",
      },
    };

    const result = await notification.push(message);

Thanks guys!

const linking = { prefixes: ['app://'], config: { // your config // }, async getInitialURL() { return Linking.getInitialURL() }, }
this code worked for me

Based on https://documentation.onesignal.com/v7.0/docs/react-native-sdk#handlers Deep linking in iOS from an app closed state You must be Modify the application:didFinishLaunchingWithOptions in your AppDelegate.m file to use the following:
NSMutableDictionary *newLaunchOptions = [NSMutableDictionary dictionaryWithDictionary:launchOptions];
    if (launchOptions[UIApplicationLaunchOptionsRemoteNotificationKey]) {
        NSDictionary *remoteNotif = launchOptions[UIApplicationLaunchOptionsRemoteNotificationKey];
        if (remoteNotif[@"custom"] && remoteNotif[@"custom"][@"u"]) {
            NSString *initialURL = remoteNotif[@"custom"][@"u"];
            if (!launchOptions[UIApplicationLaunchOptionsURLKey]) {
                newLaunchOptions[UIApplicationLaunchOptionsURLKey] = [NSURL URLWithString:initialURL];
            }
        }
    }

RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:newLaunchOptions];

also in reactnavigation: https://reactnavigation.org/docs/deep-linking/
const linking = {
    prefixes: ["https://example.com", "example://"],
    config,
    async getInitialURL() {
      const url = await Linking.getInitialURL();
      if (url != null) {
        return url;
      }
    },
  };

<NavigationContainer linking={linking}>
   ...
</NavigationContainer>

This worked for me, thanks! I only needed the getInitialURL part though

Implement getInitialURL inside linking properly.
...,
config: deepLinkConfigs,
async getInitialURL() {
    const url = decodeURI((await Linking.getInitialURL()) ?? '');

    if (url) return url;

    // Check if there is an initial firebase notification
    const message = await messaging().getInitialNotification();

    // Get deep link from data
    // if this is undefined, the app will open the default/home page

    return message?.data?.link ?? '';
},
...

Implement getInitialURL properly inside linking object of  <NavigationContainer linking={linking}/>
...,
config: deepLinkConfigs,
async getInitialURL() {
    const url = decodeURI((await Linking.getInitialURL()) ?? '');

    if (url) return url;

    // Check if there is an initial firebase notification
    const message = await messaging().getInitialNotification();

    // Get deep link from data
    // if this is undefined, the app will open the default/home page

    return message?.data?.link ?? '';
},
...

I was facing same issue i used some other function and it started working fine as expected
here is my code
dynamicLinks().onLink((item) => {
this.eeplinkingMethod(item);
});
as i am assuming it was happening due to listener
hope this will help
Thanks

it's been a long time since this issue was opened, is anyone working on the fix? @react-native-bot

Any news about it?

Any updates on this?


slack: 4.38.125 -> 4.39.90

Description of changes

fixed update script with new URLs
bumped versions

"Changelog": https://slack.com/release-notes/linux

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

That looks like the old URL was used.


Gitlab improvement

Yes. GITLAB_APPLICATION_LOG_PAT has been changed to point to a directory

Sorry, I wasn't aware of this PR when I did #13396. As far as I can see the log path fixes are also in my PR so I'll close this.


[TRACKING ISSUE] Report client name in logs

The tracking issue for the Java side PR.
See https://github.com/hazelcast/hazelcast/pull/19231 for details.

During authentication and while destroying client endpoint, we
print logs about the client such as UUID and version of it.
With this PR, we also add client name information to such logs
so that we would have an easier time while examining the logs.
Closes https://github.com/hazelcast/hazelcast/issues/15316

Not related to clients. See https://github.com/hazelcast/hazelcast/pull/19231#issuecomment-889937088


Support custom menu presentation

Codecov Report

Merging #584 into master will increase coverage by 0.02%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master     #584      +/-   ##
==========================================
+ Coverage   59.75%   59.78%   +0.02%
==========================================
  Files          88       88
  Lines        3730     3737       +7
==========================================
+ Hits         2229     2234       +5
- Misses       1501     1503       +2

Impacted Files
Coverage Δ

...ems/TextMessages/TextMessagePresenterBuilder.swift
88.09% <100%> (+1.6%)
:arrow_up:

...eMessage/Views/BaseMessageCollectionViewCell.swift
60.71% <33.33%> (-0.43%)
:arrow_down:

...ms/TextMessages/TextMessageMenuItemPresenter.swift
54.54% <60%> (-3.79%)
:arrow_down:

...Chat Items/TextMessages/TextMessagePresenter.swift
71.42% <92.85%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Offset filed of buffer dose not work

Hi,
This is excellent work! We try to use it to solve some memory allocation problems. We found that when we set  a value to  the offset filed of a buffer (which will be regard as a fixed position buffer according to the annotation)， the solver will re-allocate this buffer instead of using the offet we provided.
Did I use it wrong? Or is this still a todo feature?

Ah, yes that optional<Offset> field is confusing ... when reading solution files, we use it to store the final (fixed) offset assignment, but it's not a property that is honored by the solver.  It would take some extra work if you want the solver to recognize such fixed objects and place buffers around them.

Thank you for your reply. Now I understand the meaning of offset filed. Do you have any suggestions If I want to add the feature I mentioned above？

I've just pushed a change that should add solver support for fixed offsets.  Would you mind giving it a try?

That's great! I‘d like to !

Thanks for your work. I've tried this fix in our project and it works. However, we found that for some cases, minimalloc can not found a solution within the required time (which is 30s for 200 buffers)， but when we use first-fit method for memory allocation, we will get right solution in very short time. Seems that the partial-allocation problem is not friendly for minimalloc? btw, I suggest that use number of backtrack times to determine whether timeout occurs because it is more stable.

There's one more change I ought to make for the "fixed offset" feature to be fully performant -- I'll let you know once it's checked in, might take me a couple days.

Just added one more check that should allow for earlier termination -- let me know if this fixes the issue (if not, I can try a few more things).


select dijkstra() never returns

OrientDB Version, operating system, or hardware.

v2.2.13-SNAPSHOT

Operating System

[ x] Linux

Expected behavior
comparing with another function ...
orientdb {db=HumanPPI2}> SELECT shortestPath(#40:55,#33:0)
+----+---------------------------+
|#   |shortestPath               |
+----+---------------------------+
|0   |[#40:55,#34:133,#33:0]|
+----+----------------------------+
1 item(s) found. Query executed in 0.078 sec(s).
Actual behavior
orientdb {db=HumanPPI2}> SELECT dijkstra(#40:55, #33:0, 'Scale') FROM V
never returns- now 30 minutes, and counting...
Steps to reproduce the problem
download my database from google disk and check. please request share.

Hi @austx
Could you please send me a backup of the db (a copy of the db folder)? It's the only way to preserve RIDs and reproduce the exact same scenario
Thanks!
Luigi

Hi @austx
I just pushed a fix for this on branch 2.2.x (porting it to develop).
Just a couple of notes:

The fix is just an optimization, the old algorithm used an inefficient API to retrieve neighbor vertices.

Please, use the following as a query
SELECT dijkstra(#40:55, #33:0, 'Score')

instead of
SELECT dijkstra(#40:55, #33:0, 'Score') from V

you definitely don't need the from V here.

On my machine it's still much slower than a simple ShortestPath (it takes a few minutes to execute), but the algorithm of a weighted path is more complex than a simple shortestPath, so it makes sense
Thanks
Luigi


Creating method to update the watch_exec variable with the greatest c…

https://github.com/mattgreen/watchexec/issues/19
I am not thrilled about using Rcs and RefCells here, but I couldn't get it to compile otherwise.

This looks good.
Since we are post-1.0, let's define a new env var called $WATCHEXEC_COMMON_PATH that contains this, and leave $WATCHEXEC_UPDATED_PATH for simple use cases.
What platform have you tried this on? I'd like to make sure I test it manually on all three platforms.

I've added back support for the $WATCHEXEC_UPDATED_PATH as requested. I have successfully tested this on Linux.

Great, will accept this and start testing it.

Excellent work on this. I profiled this by monitoring my entire drive while deleting 20,000 files and it didn't even bat an eye.


Tests using web-test-runner time out waiting for the browser to start

Command
test
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
We are concerned about Karma not being maintained and we want to know the cost of migrating to other alternatives
We came across your blog post Moving Angular CLI to Jest and Web Test Runner and want to explore the web-test-runner, but it fails with the following error: The browser was unable to create and start a test page after 30000ms. You can increase this timeout with the browserStartTimeout option.

Minimal Reproduction
I started a new project:

ng new test-web-runner
selected SCSS and No SSR
installed @web/test-runner
switched the test builder in angular.json to @angular-devkit/build-angular:web-test-runner
run the default test

Exception or Error
No response
Your Environment
Angular CLI: 17.3.3
Node: 20.11.0
Package Manager: npm 10.2.4
OS: darwin arm64

Angular: 17.3.3
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1703.3
@angular-devkit/build-angular   17.3.3
@angular-devkit/core            17.3.3
@angular-devkit/schematics      17.3.3
@schematics/angular             17.3.3
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.4

Anything else relevant?
No response

just install @web/test-runner-core and it will work.
I think it should be added to the error message

Unfortunately installing @web/test-runner-core didn't help.

Normally @web/test-runner-core is already a dependency of test-web-runner

What sort of browser-launcher setup are you using when running your tests?  Are you trying to test against an older set of browsers, by chance?
Apologies if this ends up being unrelated, but I ran into this issue (and error message) while trying to resolve my own; perhaps notes I left at https://github.com/modernweb-dev/web/issues/2756 might help.

Add this to your angular.json file to get the tests passing for now

Correct, I found this too. Looks like this is required starting with Angular 15.

Add this to your angular.json file to get the tests passing for now

Thank you, that solved a similar issue I was having and I'm at least able to get the tests running now!


aria-hidden="true" even when buttons are hidden

I am trying to understand the reasoning behind why 'aria-hidden' is set to 'true' at all, as screen readers need to read what's inside the clamp regardless of it being truncated or not.  If there is a logical reason, then I would like to request an enhancement that when we set 'buttons' attribute to 'false', that 'aria-hidden' is also set to 'false'.

+1. I made a pull request to address it last week.
https://github.com/zoltantothcom/react-clamp-lines/pull/34

I've run into this problem with an accessibility audit. - aria-hidden true on text that is not to be expanded comes up as an issue for screenreaders. I've looked at @LordOfCorners PR and agree this would solve my issue.
My only additional observation would be - even if text is clamped, a person using a screen reader would want to know it is there, no?


Enhencement about the struct of RCAR message and TeePubKey type

Hi, this PR includes two commits:

mark extra_param and tee_evidence as serde_json::Value to allow structured data rather than simple String. This need is gradually found in issues like https://github.com/confidential-containers/trustee/issues/242
Add EC key support for TeePubKey. Although RSA is widely used key type, EC keys has advantages like smaller key size, faster operations and strong security.

The commits will not break current implementation, which could be seen in the unit test.

@tylerfanelli Thanks! Fixed the unit tests. I formatted the test request json thus Vec<u8> would be serialized into separate lines with one u8 each line, thus an explosion of changed lines.


Dexter sub-path imports don't seem to work without tsconfig "moduleResolution": "Bundler"

Using "moduleResolution": "node" in the consuming project, which is very common, seems to break dexter's typing exports as tsserver can't find them.
Example:
import { type Prompt } from '@dexaai/dexter/prompt` // this gives an error

This will probably surprise anyone who tries to use this package, since before 2 weeks ago, I had never used "moduleResolution": "node".
It would be nice to use tsc only, but I wonder if we'd be better off using something like tsup for output compatibility?

@rileytomasek what do you think of switching all example usage to import from @dexaai/dexter? We can keep the ESM exports to remain backwards compatible.
Reasoning:

The current exports version is broken in a large, non-trivial portion of TS projects (including all 3 of my own projects I've tested it on)
I know a lot of people have auto-imports, but DX-wise not everyone does, and I've found having multiple imports from dexter to be a pain so far.
As we add additional functionality to dexter (more providers, chunking, etc), this DX issue will only get worse
We can still keep the ESM exports if devs care about optimal imports for edge/serverless use cases, but right now all of our usage is Node.js, so we're really not gaining anything from not having a simple entrypoint


Bobjac/build

More iteration and testing coming, but wanted to get initial pr looked and and merged.  After testing is complete, will replace the container with the mcr.microsoft.com/container-package-app:latest container.
PR Includes:

Integration with cap container (bobjac/cpa:7.0)
Implementation of az partnercenter marketplace offer bundle build
Implementation of az partnercenter marketplace offer bundle verify

initial implementation of bundle commands. approved.


ref(k8s): simplify _create_rc with dict_merge to deal with RC templates

This PR is not viable anymore given other changes that have gone into the RC around slugbuilder


Add Python 3.12 to test matrix as upper bound and fix findings

This is done in advance to open the door for upgrading to newer Python versions on seeedsigner-os at any time.
Fixes / required changes:

Fix E   ValueError: mutable default <class 'seedsigner.views.view.Destination'> for field next_destination is not allowed: use default_factory
Install package during CI with pip instead of calling the setup.py (which got deprecated a while a ago and breaks with Python 3.11/3.12)
Update Pillow version to 10.0.1 = first version with Python 3.12 support

Description
Describe the change simply. Provide a reason for the change.
Include screenshots of any new or modified screens (or at least explain why they were omitted)
This pull request is categorized as a:

[ ] New feature
[ ] Bug fix
[ ] Code refactor
[ ] Documentation
[ ] Other

Checklist

[ ] I’ve run pytest and made sure all unit tests pass before sumbitting the PR

If you modified or added functionality/workflow, did you add new unit tests?

[ ] No, I’m a fool
[ ] Yes
[ ] N/A

I have tested this PR on the following platforms/os:

[ ] Raspberry Pi OS Manual Build
[ ] SeedSigner OS on a Pi0/Pi0W board
[ ] Other

Note: Keep your changes limited in scope; if you uncover other issues or improvements along the way, ideally submit those as a separate PR. The more complicated the PR the harder to review, test, and merge.

ACK and tested


Support global IP blocklisting

Should be done by firewall/EC2/ECS and so on.

We should support this feature for https://github.com/turms-im/turms/issues/507 (CC attack review)

Draft

Every node has its own blocklist
Every node sync its latest blocklist to Redis regularly (e.g. 15s. we don't sync them immediately for fewer requests and better performance).
When 1. user logins 2. user send a request 3. the local node gets new blocklisted users, turms-gateway should reject to serve with a response that indicates they are blocked.

Tasks

Implement the block logic as mentioned above in servers
Add APIs to CRUD blocklisted users
Add a page for blocklist in turms-admin

Pending Questions
What about the implementation of the block time?

Another bug:
When running the eval command via Lettuce with: redis.call('RPUSH', blocklist_log_key, '\x00', id, type), '\x00' is encoded as string of 3 bytes,
but is encoded as 1 byte correctly when running the eval command in redis-cli
And, we are 100% sure that the Lua file is decoded and encoded correctly in UTF-8 without BOM with LF line separator.
Solution
Use string.char(0) instead of '\x00' to ensure it can be encoded correctly.


Disable javascript generation on build

After saving a ts file is saved a js file is generated from the compilation. This can be a pain when checking files into source control.
To give a bit of background, we are using gulp for building our project in the background, it places our final product i a different folder, than our work environment. Therefore we have to remove all the newly generated js files each time we check in.

places our final product i a different folder, than our work environment.

You can use compilerOptions.outDir : I encourage you to set it up as it's going to compile faster than gulp.
But if you must. There is an option compileOnSave that you can set to false. Please see tsconfig.md

Link : https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md

Thank you for the reply! Have a nice day.

big help. thanks!


FIFO sizing bug in trng_csprng_fifo.v

In file trng_csprng_fifo.v the parameter FIFO_MAX is computed wrong (courtesy Dhana Shree Boopathy)
Line 60 in file trng_csprng_fifo.v:
localparam FIFO_MAX       = (2 >> FIFO_ADDR_BITS) - 1;
Needs to be replaced by:
localparam FIFO_MAX       = (1 << FIFO_ADDR_BITS) - 1;

That is very true. How sloppy of me. Thanks to you and Dhana Shree Boopathy.
This is fixed in commit: https://github.com/secworks/trng/commit/754a0a6112e0f20b5d77ae6c0d1bdbf9f618590e


[Moving platforms] More velocity when walking towards the direction they are moving

Bug description
Moving platforms give you more velocity when walking towards the direction they are moving.
Expected behaviour
You move with the same velocity going to the direction the platform is moving that on the opposite.
Game version
0.4

You actually have a relative speed to the platform, meaning that if you stay idle, the platform drags you (otherwise you would be all the time fighting against the platform speed), thus when you move, the speed is added to the platform current speed.
This gives a nice ilussion when you jump, and the fall, the horizontal platform will have advances its position, because you have its reference system


[AutoPR cognitiveservices/data-plane/LUIS/Authoring/cognitiveservices/data-plane/LUIS/Runtime/cognitiveservices/data-plane/SpellCheck] [Cognitive Services] unify client class names, folder cases.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3365

Closing PRs that are older than 1 month.


"mark as done" button causes chat to disappear and is no longer reachable via navigation

What you did:

create a chat
mark as done

What happened:

blank screen and following console error:

I think this happens when a chat that no longer exists on daemon is persisted (i.e. when daemon is restarted but the browser still has an old chat id in local storage).

Or it happens when refreshing the operator-app browser window.

yeah, I noticed this happening on refreshing the window. Going to dive into this now, hopefully it's small! 🐛


Incorrect information for NSG assignment

As per https://docs.microsoft.com/en-us/azure/virtual-network/network-security-group-how-it-works

@marckean : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@moagra: I'm sorry - only the author of this article, @damendo, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


Control B opens an additional class browser

When pressing control B on a class name a class browser is open in a tab with the selected class, but also it opens a second tab with an empty class browser.

Fixed.


Pass metricNameWithBrowser along with analyticsTracker

Previously this variable was unused but should in fact be passed down to the analytics tracking solution.
Kind regards,
Tim

Thank you for the PR, but I am going to not accept the suggestion because in the next version we will deprecate the Browser tracking.
A few reasons why:

Perfume aims to only to clean up and normalize the information around Performance API Metrics
Perfume aims to be as small as possible in terms of Dist Minified Kb
Perfume should simply help you out get the performance metrics and then your favorite Tracking Provider (Amplitude, NewRelic, MixPanel, DataDog, etc..) should normalize the browser and country information as they prefer.
Perfume aims to help understand Real User Measurements in the field which are very different between countries, devices, and networks. Differences between browser is more a Lab Data conversation with synthetic analysis.

Let me know if you have other curiosities.
Thank you

Perfume aims to only to clean up and normalize the information around Performance API Metrics
Perfume aims to be as small as possible in terms of Dist Minified Kb

That is fair but why does it currently include all the logging functionality and browser detection functionality?

Perfume should simply help you out get the performance metrics and then your favorite Tracking Provider (Amplitude, NewRelic, MixPanel, DataDog, etc..) should normalize the browser and country information as they prefer.

I understand that and I too think that makes most sense. That said what my change is doing is simply passing along the currently unused variable. Why are the variable and method there in the first place?
I agree that this library should focus on creating a very minimal implementation and should consider dropping browser agent detection as a whole.
Would you be interested in PR's that remove unnecessary parts of the library that are not critical for measuring performance (extensive logging, debugging, warnings, browser detection)?

Working on v4 at the moment, here the latest RC release.
The latest version is 50% smaller going from a 4k~ to a 2k~.
All browser functionality are gone, and only left some major debugging and logging methods.
Thank you for helping out with Perfume.js, after re-architecting the all library I lost some coverage on tests. It will be really helpful if you help me out adding more tests to reach 100% coverage.
Thank you

Oh great, could you push your v4 (RC release) to a branch on here so I can branch off of that?
Kind regards,
Tim

v4 is the latest master, I am aiming to release it before the end of this week. 😁


Mint button after voxel.editaverse does not mint, throws error:

Brave 1.20
This may be related to the chain switch last night - apologies if you know about it already!

It could be a port issue?

@karunakaruna Please re-open if it is not fixed.


fix(db): Fix write stalls in RocksDB (for real this time)

What ❔
A previous fix didn't really work judging by Merkle tree behavior on the stage env. This PR makes the initialization timeout configurable (and increases the default value from 10s to 30s; 30s is approximately equal to the compaction duration) and slightly increases the number of retries on stalled writes.
Why ❔
Having write stalls leads to panics and is obviously bad.
Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[x] Tests for the changes have been added / updated.
[x] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.

Couple of other options we might consider:

Increase the number of level-0 SST files for stopped writes. I feel that it doesn't solve the problem, just postpones it.
Add a subcommand to rocksdb_util (compact?) that would just create a RocksDB instance and wait indefinitely until its writes are not stopped. This could work well with the main node, but AFAICT, rocksdb_util is currently not shipped with the EN Docker image and making it work there could require some work.


Compiler flags conflict due to ARM_FP_API option

A user reported the following build failure on Gentoo Linux.
https://bugs.gentoo.org/show_bug.cgi?id=547246
ld: error: libfreerdp.so.1.2.1 uses VFP register arguments, CMakeFiles/freerdp.dir/codec/rfx_neon.c.o does not

This seems to be the result of some source files being built with -mfloat-abi=softfp, and others with -mfloat-abi=hard. It looks like this strange behavior was introduced in response to #980.
It seems to be a problem that will occur whenever CFLAGS contains -mfloat-abi=hard and ARM_FP_ABI is unspecified, causing it to default to softfp. It doesn't really make sense to me to have cmake override CFLAGS from the environment.
I see a couple of solutions here:

Remove the cmake logic for ARM_FP_ABI and adds -mfloat-abi to COMPILER_FLAGS. I'm really not sure why that resolved #980 in the first place. It seems like that issue was a result of CFLAGS being set incorrectly in the build environment, or possibly CFLAGS not being respected in that old version of the code.

Add some option to make the above mentioned behavior optional.

I can certainly submit a pull request if some some decision can be made on a suitable solution.

@floppym the response to #980 was PR #987 which basically just made the ABI configureable - instead of having it hardcoded to softfp. If you run cmake with the define ARM_FP_ABI set to the float-abi type of your system it should work without a problem.
Anyway the solution was just a work around and needs a better fix. I think we should go for 1. and completely get rid of ARM_FP_ABI since the float-abi used is something the build environment/configuration should specify. In the meanwhile it should be sufficient to remove all occurrences of ARM_FP_ABI including the configuration option.  But I don't have only an Android build environment for testing..
If you can provide a PR this would be great.


InsightVMCloud: data_connector,parsers,datasamples

Proposed Changes

new connector

@averbn , Can you please fix all PR review comments. Thanks!


Network Event Rollup

Hello,
I would love to help with rolling up network events e.g tcp_sendmsg and udp_sendmsg. Is this on the roadmap? If so, how can I help?

To my knowledge, this is not in the roadmap.
Based on the definition below:

int tcp_sendmsg(struct sock *sk, struct msghdr *msg, size_t size);

It seems that one missing piece is adding support for struct msghdr arguments.
If this is something that you (or someone else) is interested in working on, we 'd be happy to help. We do not, currently, have a lot of development documentation, but this might be a good opportunity to fix that.

There is another issue :)
tcp_sendmsg is called so many times (and very fast) that you lose calls within the circular buffer. I think it would need to be rolled up within ebpf

Hi @levigross
In test cluster I generate 5k/s tcp_sendmsg messages. Was able to reduce dropped ring buffer messages by increasing     rb-size. Default is only 65k bytes which is way to small for networking events tracing.

Another issue is that userspace is not able to keep up and consume events from Go channels. Even increasing events channel size doesn't help.

There are few issues:

Log exported can't keep up.
Most of the CPU is spent marshaling json + bunch reflect. This also creates lots of garbage on heap. Standard library json can be replaced by something like json-iter(also used in k8s).

@anjmao Thank you for this brilliant outline of the issue! IMHO the network events needs to rolled up within BPF and need to be emitted as a singular event

Currently I'm using https://vector.dev/docs/reference/configuration/transforms/reduce/ to reduce events and sum bytes field in userspace.
{
  "bytes": 384,
  "daddr": "<IP_ADDRESS>",
  "dport": [
    9990,
    2112
  ],
  "node_name": "node-e6149004",
  "pid": 45735,
  "pod_name": "metrics-0",
  "pod_namespace": "grafana",
  "saddr": "<IP_ADDRESS>",
  "sport": [
    52938,
    27350
  ]
}

Also, it's important to adjust tetragon resources and add cpu requests. In my case I got dropped exported events due to lack of cpu.
To implement such reduction on kernel something like ebpf timers https://lwn.net/Articles/862136/ could be really useful (not sure about the support yet)


Update Db code table content

Overview
Links to jira tickets

https://quartech.atlassian.net/browse/BHBC-1012

This PR contains the following changes

Update Db code table content

How Has This Been Tested?

Locally

Does this require a full refresh of the database? In other words, a drop of the current one and a complete rebuild? If so, this cannot be simply merged, some work needs to happen first (the dropping of the database pod).

I believe so yep :)


[medium]

Where can I find: medium.json  ? Any idea?

You need to create the file yourself, as described in the README.


Either.value with some updates

@cheeseng can you check this with MIMA? Also I'd like to question the SerialVersionIds. Should we have those or would it be better to leave them off. For the time being I didn't add one for the new class I added (which I'm hoping won't break binary compatibility).

@bvenners I ran this through MIMA test, for scala 2.10 and 2.11 it fails with:
[error] scalatest-core: Failed binary compatibility check against org.scalatest:scalatest-core_2.10:3.2.2! Found 1 potential problems
[error]  * method convertEitherToValuable(scala.util.Either,org.scalactic.source.Position)org.scalatest.EitherValues#Valuable in trait org.scalatest.EitherValues is present only in current version
[error]    filter with: ProblemFilters.exclude[ReversedMissingMethodProblem]("org.scalatest.EitherValues.convertEitherToValuable")
[error] java.lang.RuntimeException: Failed binary compatibility check against org.scalatest:scalatest-core_2.10:3.2.2! Found 1 potential problems
[error]         at scala.sys.package$.error(package.scala:30)
[error]         at com.typesafe.tools.mima.plugin.SbtMima$.reportModuleErrors(SbtMima.scala:75)
[error]         at com.typesafe.tools.mima.plugin.MimaPlugin$.$anonfun$projectSettings$2(MimaPlugin.scala:38)
[error]         at com.typesafe.tools.mima.plugin.MimaPlugin$.$anonfun$projectSettings$2$adapted(MimaPlugin.scala:28)
[error]         at scala.collection.Iterator.foreach(Iterator.scala:941)
[error]         at scala.collection.Iterator.foreach$(Iterator.scala:941)
[error]         at scala.collection.AbstractIterator.foreach(Iterator.scala:1429)
[error]         at com.typesafe.tools.mima.plugin.MimaPlugin$.$anonfun$projectSettings$1(MimaPlugin.scala:28)
[error]         at com.typesafe.tools.mima.plugin.MimaPlugin$.$anonfun$projectSettings$1$adapted(MimaPlugin.scala:26)
[error]         at scala.Function1.$anonfun$compose$1(Function1.scala:49)
[error]         at sbt.internal.util.$tilde$greater.$anonfun$$u2219$1(TypeFunctions.scala:62)
[error]         at sbt.std.Transform$$anon$4.work(Transform.scala:67)
[error]         at sbt.Execute.$anonfun$submit$2(Execute.scala:281)
[error]         at sbt.internal.util.ErrorHandling$.wideConvert(ErrorHandling.scala:19)
[error]         at sbt.Execute.work(Execute.scala:290)
[error]         at sbt.Execute.$anonfun$submit$1(Execute.scala:281)
[error]         at sbt.ConcurrentRestrictions$$anon$4.$anonfun$submitValid$1(ConcurrentRestrictions.scala:178)
[error]         at sbt.CompletionService$$anon$2.call(CompletionService.scala:37)
[error]         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error]         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[error]         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[error]         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[error]         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[error]         at java.lang.Thread.run(Thread.java:748)
[error] (scalatestCore / mimaReportBinaryIssues) Failed binary compatibility check against org.scalatest:scalatest-core_2.10:3.2.2! Found 1 potential problems
[error] Total time: 17 s, completed Oct 2, 2020 10:54:45 AM

which I think should be fine, do you concur?  I'll submit a PR to ignore that error against your branch.

@bvenners I submitted the following PR for ignoring the related MIMA check:
https://github.com/scalatest/scalatest/pull/1901


Quality problems with the new Google icons

A PR with new Google icons was recently merged. I was concerned about (albeit minor) quality issues during review of the PR, but wasn't able to give it my full attention. I've gone and taken a close look at the Google icons after the fact, and have found some quality issues:
google.svg:

google_calendar.svg:

google_play.svg:

gmail.svg:

There's one more, but I'm not 100% certain of it:
google_plus.svg:

I've had a hard time tracking down official Google+ logos, no doubt because of how long it has been defunct. Most seem to be a straight 90 degree corner there. Some are rounded, but the rounding is as if the G were carved out of a perfect circle, which is also not reflected in google_plus.svg here. It looks like the final part of the curve leading up to the 90 degree turn got turned into a straight line segment somehow.

I think ignore the G+ as it is defunct. But very happy for you to correct the new Google ones.

I'll take a look when I have the time :-)

Hello,
I was the one who made the PR in question, I tried to reduce these problems after you pointed them but I didn't see I left so much, thank you for your review.
Could you tell me which viewer you're using please because I didn't get most of the issues you mentioned then.
Since you seem to be ready to do a PR for these, I'll give you some informations on the icons modified by the PR :
Gmail :
The red DO go behind the yellow, that's the solution I found to the rendering quirk making white lines between two blocks with exact same coordinates (like the issue you found in google_calendar between green and red), but It is not visible in the renderers I use to qualiity check what I do (Firefox 83.0b9, Inkscape 0.92.3 (2405546, 2018-03-11) and Eye of gnome 3.28.1)

I used this technique in all of them, for exemple in gmail : red goes behind dark red and yellow, blue goes behind dark red, green goes behind yellow
Google Calendar :
Sorry for the 1, I'm really bad with characters and didn't see the little bump :pray:
For the green/red white line, it's here because I didn't use the technique mentioned above because I couldn't find a way to do it without adding a big lump of bytes.

I am just using Google Chrome, pointed directly at the .svg files. In the case of the red peeking out from behind the yellow, it only shows up when it's not zoomed in -- in a close-up like you posted, it does render perfectly, but when it's a regular sized view, something about the way it renders means that a hint of red gets mixed in along the yellow's edge.


Add EEG to nwb as ElectricalSeries

Updated files at https://dandiarchive.org/dandiset/000582/draft/files

Right, I mixed them up. Thanks, should be fixed now.


Remove copying of 'rmt' into installer filesystem

On Debian systems, /etc/rmt is a dangling symlink until after a package
which provides 'rmt' is installed (at which point the links are
/etc/rmt -> /usr/sbin/rmt -> /etc/alternatives/rmt). During the build
of the installer, alternatives are not processed, so /etc/rmt is a
link which points into the filesystem of the build host (not the build
directory).
If the build is being done on a Debian-style system, the installer will
end up with an /etc/rmt which is a binary from the host, which may not
even operate on the Raspberry Pi. If the build is being done on a
non-Debian-style system, the cp command in create_cpio() will probably
fail.
Since the installer does not connect to other systems to process tar
archives, rmt is not needed, so this patch removes any attempt to copy
it into the installer.
Signed-off-by: Kevin P. Fleming<EMAIL_ADDRESS>

Thank you!


ssd 1306 does not compile because of maybe-async-cfg 0.2.5

Version of ssd1306 in use (if applicable): 0.9.0 (7ed51935bdc6e9e976d3d9a747e768589eaea0cf26f483213bfededc947c8624)
MCU/other hardware in use: Speed Studio Expansion Board with XIAMO SP2040
Display resolution and interface: I2C, 128x64

Description of the problem/feature request/other
I have a running local project with ssd1306 crate in version 0.9.0. It all worked fine, until today I wanted a second project with basically the same setup.
In the second project the ssd1306 crate just wouldn't compile:
~/Developer/Nova-Vergleich/Embedded/sp2040-playground git:[pagr]
cargo build
   Compiling pio-parser v0.2.2
   Compiling ssd1306 v0.9.0
error[E0277]: `Result<(), DisplayError>` is not a future
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:87:56
   |
87 | ... false).send(iface).await
   |                       -^^^^^
   |                       ||
   |                       |`Result<(), DisplayError>` is not a future
   |                       help: remove the `.await`
   |
   = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
   = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
   = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0277]: `Result<(), DisplayError>` is not a future
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:105:57
    |
105 | ... false).send(iface).await
    |                       -^^^^^
    |                       ||
    |                       |`Result<(), DisplayError>` is not a future
    |                       help: remove the `.await`
    |
    = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
    = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
    = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0277]: `Result<(), DisplayError>` is not a future
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:123:57
    |
123 | ... false).send(iface).await
    |                       -^^^^^
    |                       ||
    |                       |`Result<(), DisplayError>` is not a future
    |                       help: remove the `.await`
    |
    = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
    = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
    = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0277]: `Result<(), DisplayError>` is not a future
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:143:56
    |
143 | ... false).send(iface).await?;
    |                       -^^^^^
    |                       ||
    |                       |`Result<(), DisplayError>` is not a future
    |                       help: remove the `.await`
    |
    = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
    = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
    = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0277]: `Result<(), DisplayError>` is not a future
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:144:55
    |
144 | ..., true).send(iface).await
    |                       -^^^^^
    |                       ||
    |                       |`Result<(), DisplayError>` is not a future
    |                       help: remove the `.await`
    |
    = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
    = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
    = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0277]: `Result<(), DisplayError>` is not a future
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:164:56
    |
164 | ... false).send(iface).await
    |                       -^^^^^
    |                       ||
    |                       |`Result<(), DisplayError>` is not a future
    |                       help: remove the `.await`
    |
    = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
    = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
    = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0277]: `Result<(), DisplayError>` is not a future
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:184:56
    |
184 | ... false).send(iface).await
    |                       -^^^^^
    |                       ||
    |                       |`Result<(), DisplayError>` is not a future
    |                       help: remove the `.await`
    |
    = help: the trait `Future` is not implemented for `Result<(), DisplayError>`, which is required by `Result<(), DisplayError>: IntoFuture`
    = note: Result<(), DisplayError> must be a future or must implement `IntoFuture` to be awaited
    = note: required for `Result<(), DisplayError>` to implement `IntoFuture`

error[E0119]: conflicting implementations of trait `size::DisplaySize` for type `size::DisplaySize128x64`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:77:1
   |
77 | impl DisplaySize for DisplaySize128x64 {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   | |
   | first implementation here
   | conflicting implementation for `size::DisplaySize128x64`

error[E0119]: conflicting implementations of trait `size::DisplaySize` for type `size::DisplaySize128x32`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:95:1
   |
95 | impl DisplaySize for DisplaySize128x32 {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   | |
   | first implementation here
   | conflicting implementation for `size::DisplaySize128x32`

error[E0119]: conflicting implementations of trait `size::DisplaySize` for type `size::DisplaySize96x16`
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:113:1
    |
113 | impl DisplaySize for DisplaySize96x16 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    | |
    | first implementation here
    | conflicting implementation for `size::DisplaySize96x16`

error[E0119]: conflicting implementations of trait `size::DisplaySize` for type `size::DisplaySize72x40`
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:131:1
    |
131 | impl DisplaySize for DisplaySize72x40 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    | |
    | first implementation here
    | conflicting implementation for `size::DisplaySize72x40`

error[E0119]: conflicting implementations of trait `size::DisplaySize` for type `size::DisplaySize64x48`
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:152:1
    |
152 | impl DisplaySize for DisplaySize64x48 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    | |
    | first implementation here
    | conflicting implementation for `size::DisplaySize64x48`

error[E0119]: conflicting implementations of trait `size::DisplaySize` for type `DisplaySize64x32`
   --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:172:1
    |
172 | impl DisplaySize for DisplaySize64x32 {
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    | |
    | first implementation here
    | conflicting implementation for `DisplaySize64x32`

error[E0277]: the trait bound `size::DisplaySize128x64: DisplaySizeAsync` is not satisfied
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:36:30
   |
36 | impl TerminalDisplaySize for DisplaySize128x64 {
   |                              ^^^^^^^^^^^^^^^^^ the trait `DisplaySizeAsync` is not implemented for `size::DisplaySize128x64`
   |
help: this trait has no implementations, consider adding one
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:33:1
   |
33 | pub trait DisplaySize {
   | ^^^^^^^^^^^^^^^^^^^^^
note: required by a bound in `TerminalDisplaySizeAsync`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:23:32
   |
23 | pub trait TerminalDisplaySize: DisplaySize {
   |                                ^^^^^^^^^^^ required by this bound in `TerminalDisplaySizeAsync`

error[E0277]: the trait bound `size::DisplaySize128x32: DisplaySizeAsync` is not satisfied
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:48:30
   |
48 | impl TerminalDisplaySize for DisplaySize128x32 {
   |                              ^^^^^^^^^^^^^^^^^ the trait `DisplaySizeAsync` is not implemented for `size::DisplaySize128x32`
   |
help: this trait has no implementations, consider adding one
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:33:1
   |
33 | pub trait DisplaySize {
   | ^^^^^^^^^^^^^^^^^^^^^
note: required by a bound in `TerminalDisplaySizeAsync`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:23:32
   |
23 | pub trait TerminalDisplaySize: DisplaySize {
   |                                ^^^^^^^^^^^ required by this bound in `TerminalDisplaySizeAsync`

error[E0277]: the trait bound `size::DisplaySize96x16: DisplaySizeAsync` is not satisfied
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:60:30
   |
60 | impl TerminalDisplaySize for DisplaySize96x16 {
   |                              ^^^^^^^^^^^^^^^^ the trait `DisplaySizeAsync` is not implemented for `size::DisplaySize96x16`
   |
help: this trait has no implementations, consider adding one
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:33:1
   |
33 | pub trait DisplaySize {
   | ^^^^^^^^^^^^^^^^^^^^^
note: required by a bound in `TerminalDisplaySizeAsync`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:23:32
   |
23 | pub trait TerminalDisplaySize: DisplaySize {
   |                                ^^^^^^^^^^^ required by this bound in `TerminalDisplaySizeAsync`

error[E0277]: the trait bound `size::DisplaySize72x40: DisplaySizeAsync` is not satisfied
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:72:30
   |
72 | impl TerminalDisplaySize for DisplaySize72x40 {
   |                              ^^^^^^^^^^^^^^^^ the trait `DisplaySizeAsync` is not implemented for `size::DisplaySize72x40`
   |
help: this trait has no implementations, consider adding one
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:33:1
   |
33 | pub trait DisplaySize {
   | ^^^^^^^^^^^^^^^^^^^^^
note: required by a bound in `TerminalDisplaySizeAsync`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:23:32
   |
23 | pub trait TerminalDisplaySize: DisplaySize {
   |                                ^^^^^^^^^^^ required by this bound in `TerminalDisplaySizeAsync`

error[E0277]: the trait bound `size::DisplaySize64x48: DisplaySizeAsync` is not satisfied
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:84:30
   |
84 | impl TerminalDisplaySize for DisplaySize64x48 {
   |                              ^^^^^^^^^^^^^^^^ the trait `DisplaySizeAsync` is not implemented for `size::DisplaySize64x48`
   |
help: this trait has no implementations, consider adding one
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/size.rs:33:1
   |
33 | pub trait DisplaySize {
   | ^^^^^^^^^^^^^^^^^^^^^
note: required by a bound in `TerminalDisplaySizeAsync`
  --> /CENSORED/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ssd1306-0.9.0/src/mode/terminal.rs:23:32
   |
23 | pub trait TerminalDisplaySize: DisplaySize {
   |                                ^^^^^^^^^^^ required by this bound in `TerminalDisplaySizeAsync`

Some errors have detailed explanations: E0119, E0277.
For more information about an error, try `rustc --explain E0119`.
error: could not compile `ssd1306` (lib) due to 18 previous errors
warning: build failed, waiting for other jobs to finish...

My tests indicate, that the culprit is the update of maybe-async-cfg from 0.2.4 (in the first project) to 0.2.5 (in the second project), as the following diff on the cargo.lock makes the difference between compiling and failing:
:100644 100644 8decaec 0000000 M	Cargo.lock

diff --git a/Cargo.lock b/Cargo.lock
index 8decaec..b04de4a 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -948,13 +948,37 @@ version = "0.4.22"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "a7a70ba024b9dc04c27ea2f0c0548feb474ec5c54bba33a7f72f873a39d07b24"

+[[package]]
+name = "manyhow"
+version = "0.11.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "b33efb3ca6d3b07393750d4030418d594ab1139cee518f0dc88db70fec873587"
+dependencies = [
+ "manyhow-macros",
+ "proc-macro2",
+ "quote",
+ "syn 1.0.109",
+ "syn 2.0.85",
+]
+
+[[package]]
+name = "manyhow-macros"
+version = "0.11.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "46fce34d199b78b6e6073abf984c9cf5fd3e9330145a93ee0738a7443e371495"
+dependencies = [
+ "proc-macro-utils",
+ "proc-macro2",
+ "quote",
+]
+
 [[package]]
 name = "maybe-async-cfg"
-version = "0.2.4"
+version = "0.2.5"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "a1e083394889336bc66a4eaf1011ffbfa74893e910f902a9f271fa624c61e1b2"
+checksum = "8dbfaa67a76e2623580df07d6bb5e7956c0a4bae4b418314083a9c619bd66627"
 dependencies = [
- "proc-macro-error",
+ "manyhow",
  "proc-macro2",
  "pulldown-cmark",
  "quote",
@@ -1178,6 +1202,17 @@ dependencies = [
  "version_check",
 ]

+[[package]]
+name = "proc-macro-utils"
+version = "0.10.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "eeaf08a13de400bc215877b5bdc088f241b12eb42f0a548d3390dc1c56bb7071"
+dependencies = [
+ "proc-macro2",
+ "quote",
+ "smallvec",
+]
+
 [[package]]
 name = "proc-macro2"
 version = "1.0.89"

I had the same issue, and solved this problem by:
[patch.crates-io]
ssd1306 = { git = "https://github.com/rust-embedded-community/ssd1306.git", rev = "f3a2f7aca421fbf3ddda45ecef0dfd1f0f12330e" }

at Cargo.toml
see also https://github.com/rust-embedded-community/ssd1306/pull/218


Gdax (pro coinbase) - HTTP 429 Error: Public rate limit exceeded

I'm submitting a ...
[x] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Running live Gekko (as tradebot) on gdax exchange from Gekko UI. When my trading strategy start executing order it fails with this error:
Error: HTTP 429 Error: Public rate limit exceeded
(full log:
gekko_error_log.txt
)
Expected result (what you hoped would happen)
Gekko place order on Gdax market
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
Gdax (pro coinbase) probably change its API and gdax.js wrapper needs to be fixed.
Running Gekko in paper trader mode on Gdax market works fine.
I'm using version: 0.6.8

The error is clear, you've exceeded the public rate limit. That means you have too many bots running on the same exchange, or are trying to run the bot and importer at the same time, or sometimes the importer does this if importing a lot of data.
Try running only 1 bot per exchange and see if it works.

Thanks for the reply. I've tried to run it again and it seems to be working.


[SPARK-46826][INFRA] Reset grpcio installation version of Python linter dependencies for branch-3.4/branch-3.5

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/43942 upgraded the grpcio version and simultaneously upgraded the grpcio version installed in Install Python linter dependencies for branch-3.4 and Install Python linter dependencies for branch-3.5 in build_and_test.yml. These two steps are used to install Python linter dependencies for branch-3.4/branch-3.5 in daily tests. They should use the same configuration as branch-3.4/branch-3.5 for safety. So this pr reset the version of grpcio installed in these two steps:

branch-3.4

https://github.com/apache/spark/blob/e56bd97c04c184104046e51e6759e616c86683fa/.github/workflows/build_and_test.yml#L588-L595

branch-3.5

https://github.com/apache/spark/blob/0956db6901bf03d2d948b23f00bcd6e74a0c251b/.github/workflows/build_and_test.yml#L637-L644
Why are the changes needed?
The versions of the dependencies installed in Install Python linter dependencies for branch-3.4 and Install Python linter dependencies for branch-3.5 should be consistent with branch-3.4/branch-3.5.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Monitor GA after merged
Was this patch authored or co-authored using generative AI tooling?
No

Since this aims to recover the old status for branch-3.4/3.5, it looks good to me.

Merged into master. Thanks @dongjoon-hyun  ~
I will monitor daily test of branch-3.4/3.5


Support for top-level await operators

This is a followup to #38316, so I'll mostly be copying the details from there. #38316 was closed in March, but yesterday a project member of Chromium commented on the linked Chromium bug report to say that there are no plans to work on this, so I wanted to followup here and see if something could be done outside of Chromium, or if an alternate solution already exists.

VSCode Version: 1.51.1
OS Version: Mac OS Catalina 10.15.6

Steps to Reproduce:

Open the attached code in VSCode. Set a debug break point at line 7.
Click Debug then Start Debbuging. In the debug console type "await testFunction(); " then press enter. SyntaxError: Unexpected identifier appears in the Debug Console.
In the debug console, type "(async () => { await testFunction();} )();" then press enter. Promise { pending } appears.

async function testFunction() {
    return new Promise((resolve) => {
        resolve('test');
    });
}

testFunction().then((res) => {
    console.log(res);
});

Does this issue occur when all extensions are disabled?: Yes

Click Debug then Start Debbuging. In the debug console type "await testFunction(); " then press enter. SyntaxError: Unexpected identifier appears in the Debug Console.

I'm not able to reproduce this. Can you confirm that debug.javascript.usePreview is not false. If that's already the case, please collect logs
/jsDebugLogs

Promise { pending } appears.

There's not a workaround for this. The runtime is paused which does not allow the tasks and microtasks associated with the promise to run. I cannot say I expected anything other than the author's last reply on that chromium issue, as making this would work require a whole lot of work and special casing on V8's side of things.

My bad, I should have read the original ticket's steps more carefully. It no longer throws an error, and now produces Promise {<pending>}. It sounds like there's nothing that can be done for now, and if so, this can probably be closed. Thanks for your time!

no worries, thanks for the issue
/duplicate


ColliderUserTracker doesn't deregister users on respawn

Steps to replicate:

Have a user inside the volume of a collider using a ColliderUserTracker
Respawn the user
The user remains listed under _usersInside and the IsAnyUserInside and IsLocalUserInside (if applicable) remain checked
If the user re-enters the collider volume, a second entry is added for them under the _usersInside
If they exit the volume normally their entries will clear normally as expected

Issue observed by Turk.

Wrong GitHub, sorry.


[loc][query][VSCode]  Please clarify "Welcome experience"

Hi, we have a question from our translator. Can you help please? Thanks!
Source:
When enabled, will show the Welcome experience on startup.
File Name:
src\vs\workbench\parts\welcomePage\electron-browser\welcomePage.contribution.nls.resx
Resource ID:
".resx", 0; "welcomePage.enabled"
Query:
In this contect, "experience" seems to be the page that have "welcome" page function. Please confirm.

Yes, that is correct. When enabled the Welcome page will be shown in an editor tab right after startup.

I will replace "experience" with "page" here. Thanks.


Renaming master to main. Step 1

Here we just enable GitHub to watch both master and main.

Codecov Report

Merging #1425 (b764497) into master (e08cd70) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1425   +/-   ##
=======================================
  Coverage   82.29%   82.29%
=======================================
  Files          65       65
  Lines        5332     5332
=======================================
  Hits         4388     4388
  Misses        944      944

Continue to review full report at Codecov.

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

Part of #1308


PHP8.x support

Bumped PHP version to be able to use with the latest version of PHP and new syntax features.

Hi @cytopia can you merge it please?


Add macro to automatically generate common cases for autotune

Adds a small proc macro to generate the autotune boilerplate in most common cases.
See examples in doc comments for how they would be used.

Just to make sure, this creates the tune operation as well as the autotune set from an autotune key, but it doesn't create the high level function actually creating a static tuner right?

Just to make sure, this creates the tune operation as well as the autotune set from an autotune key, but it doesn't create the high level function actually creating a static tuner right?

Exactly. That boilerplate is extremely minor so I don't think it's worth making a macro for.

Exactly. That boilerplate is extremely minor so I don't think it's worth making a macro for. Here's an example of the usage in the new conv2d tuner

We could actually generate it as well, since it's the same signature as the tune_set function.
We could have another macro tune that does most of the thing:
#[tune(
    operations(Conv2dDirect, Conv2dIm2col),
    key = create_key,
    inputs = bench_inputs
)]
pub fn conv2d<R: JitRuntime, E: FloatElement, I: IntElement>(
    key: JitAutotuneKey,
    input: JitTensor<R, E, 4>,
    weights: JitTensor<R, E, 4>,
    bias: Option<JitTensor<R, E, 1>>,
    options: ConvOptions<2>,
) -> JitTensor<R, E, 4>;

What do you think?


Create TLS integration test

So that this doesn't happen again https://github.com/stellar/go/pull/3010

Actually, it could even be a unit test


Component rerender does not behave as expected

Vue version
9a36f2a
Link to minimal reproduction
https://play.vuejs.org/#eNqlVEtv2kAQ/ivT7QEjgQlJTxYgJW0q0UMapTnuxdhj19TedfcBVIj/3tk1JubRqFHkg73z/Oabb71lt3UdriyyiE10ooragEZj6xkXRVVLZeBrLJI/d9YYKSBTsoJeOOrYXHLvEHy7Ri0rnCed4I7tOHirMBuAFE8oUlTPqshzVJju9plNLBeUpw38ttIgTIFygm0cx9F4AIvFIroeQJIk0c2u72LPigUBrlCYPkxnsOUCwFWTJYalzIMeDX/ev0eVmmrExFwYVKu4DIKXEh5KSEbrAHkTgIMEX2JyCLkO+oPGukfYHDxO97mjBgO4vrq66pPLPZNRQz7RTgeDVV1SKToBTDpkewOZ2gD4aApTNnHe0eU/8jinnPk3ZzBq00fdBtxMuvskU8fPBuxk104ox/jSYgVJGWtNrTIXPFwYwZl3UnFdSgMirhwSj5YzB8S1pczjdn76yzLcni8KTpXyxu13lf1PFRw2Q1ScKNlR8WE4BKsLkUMsACu5LGBpSa6ZVJDSGWqraqlRw3DoZj2jbjYejy8y8Q4eUswKgY9K1jrwY3txPthqgcoL08myPXtxOmnuDa3433qVOsr7LzKNptCsyMOlloKo9CU5S2RVFyWq77UpqD5nUXvDOIvLUq6/eZtRFvd3jHJ+YvLrgn2pN87G2aNCTdeYpHfwmVjlaBr3/Y8H3ND3wVnJ1DqhvuJ8onFL6zA2YXdWpAS7E+fRzv3WSB/P+n5jUOh2KAfU/wt8PGe0u8+vjP4C9yb81P5D2O4v5rT3TQ==
Steps to reproduce
No additional operations are required. Open the demo console and you will see printing that does not meet expectations.
What is expected?
The onRenderTriggered of the three components should not be triggered
What is actually happening?
FancyButton's onRenderTriggered is always triggered when quote changes. In my understanding, because quote is not used in the template and is only passed transparently to the component as props, it should not trigger the rerender of any component. So I don’t know if there is a problem with my understanding of responsiveness, or if it is indeed a bug in the slot scenario. I couldn’t find any relevant instructions in the official website documentation to support this case.
System Info
No response
Any additional comments?
No response

// the render function of App.vue
function render(_ctx, _cache, $props, $setup, $data, $options) {
  return (_openBlock(), _createBlock($setup["FancyButton"], null, {
    title: _withCtx(() => [
      _createVNode($setup["AwesomeIcon"], { quote: $setup.quote }, null, 8 /* PROPS */, ["quote"])
    ]),
    _: 1 /* STABLE */
  }))
}

this is the expected behavior

$setup.quote is accessed during render FancyButton
FancyButton should be re-render if $setup.quote changed

@edison1105 So only computed will collect dependencies when used in template, while props will collect dependencies as long as they are passed?

@edison1105 So only computed will collect dependencies when used in template, while props will collect dependencies as long as they are passed?

Sorry. I didn't get your point. The essence of the reactivity system is the relationship between reactivity data and functions. When a function accesses a reactive data during execution, it is collected as a dependency.

@edison1105 Thank you for your answer, I understand clearly


Remind command

Create remind command that will send message at specified time.

We can use the internal self._at_add() and self._at_del() methods while implementing the remind command in the base plugin.
You can also use the at_reply_output job parameter self._at_add(..., at_reply_output=False) to suppress sending of Scheduled job ... finished with output info message to job owner.


Bot clicks to early

Is it possible, to add an option, to change the sensitivity of the hook detection?
my Fishbot clicks to early, if i use a bigger bobber

Try to tweak Checking delay, it's also depends on camera position and video settings. Try it from the first person view as well as with different max/min graphics settings.

thx. i have testet higher delays and now it works better. :)

Will add some kind of sensitivity in the future updates, so stay tuned.


Credit Risk Modeling with Artificial Neural Networks (ANNs) and K-Nearest Neighbors (KNN)

Description:
This repository contains a comprehensive implementation of Credit Risk Modeling using Artificial Neural Networks (ANNs) and K-Nearest Neighbors (KNN) to explore complex relationships in financial data for credit risk assessment.
The project successfully demonstrates:

High Model Performance: Achieving impressive metrics, including:

High Recall and Precision scores, ensuring fewer false negatives.

A strong F1 score, balancing precision and recall.

An outstanding ROC-AUC score of 91%, showcasing the model's ability to distinguish between good and bad credit risks effectively.

Techniques Applied:

Artificial Neural Networks (ANNs) to capture non-linear relationships and improve predictive accuracy.

K-Nearest Neighbors (KNN) for baseline modeling and comparison.

Precision-Recall and ROC-AUC curves for performance visualization.

This project provides key insights into credit risk prediction and can aid financial institutions in making more informed lending decisions.
Key Features:

End-to-End Workflow: Data preprocessing, model training, hyperparameter tuning, and evaluation.

Visualization: Precision-Recall and ROC-AUC curves to analyze trade-offs in prediction performance.

Reproducible Code: Python scripts built with libraries like TensorFlow, #Keras, #scikit-learn, #seaborn and #matplotlib.

credit_risk_with_KNN_&_ANNs.ipynb


update readme to v3 to support node 20 gh actions

Replace the bullet points below with your answers
Description
To update the readme from retry@v2 to retry@v3 to support node 20 and prevent others from getting the 'Node.js 16 actions are deprecated.' warning on github actions

Feel free to merge once approved.

This PR has no changes now, I think it's fixed.