collapsing problem

Hi,
I am running Cogent and when running the command:
process_kmer_to_graph.py my_high_qual_isoforms.fa my_high_qual_isoforms.fa.s1000k30.dist CP1/ CP1
It gives me the error:
AttributeError: 'Graph' object has no attribute 'nodes_iter'
which seems to be a compatibility error between the code and the NetworkX new version, or maybe not; either way, I am stuck, can you help me please?.
this is the full output:
making weight graph from  CP1-high_qual_isoforms.fa.s1000k30.dist
graph contains 5974 nodes, 188873 edges
performing ncut on graph....
Traceback (most recent call last):
File "/home/calla2/anaconda2/envs/anaCogent/bin/process_kmer_to_graph.py", line 4, in
import('pkg_resources').run_script('Cogent==2.1', 'process_kmer_to_graph.py')
File "/home/calla2/anaconda2/envs/anaCogent/lib/python2.7/site-packages/pkg_resources/init.py", line 748, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/home/calla2/anaconda2/envs/anaCogent/lib/python2.7/site-packages/pkg_resources/init.py", line 1517, in run_script
exec(code, namespace, namespace)
File "/home/calla2/anaconda2/envs/anaCogent/lib/python2.7/site-packages/Cogent-2.1-py2.7.egg/EGG-INFO/scripts/process_kmer_to_graph.py", line 155, in
ncut_threshold=args.ncut_threshold)
File "/home/calla2/anaconda2/envs/anaCogent/lib/python2.7/site-packages/Cogent-2.1-py2.7.egg/EGG-INFO/scripts/process_kmer_to_graph.py", line 77, in family_finding
run_ncut(g, labels2_map, ncut_map, nodelist, ncut_threshold)
File "/home/calla2/anaconda2/envs/anaCogent/lib/python2.7/site-packages/Cogent-2.1-py2.7.egg/EGG-INFO/scripts/process_kmer_to_graph.py", line 17, in run_ncut
labels = np.array([i for i in G.nodes_iter()])
AttributeError: 'Graph' object has no attribute 'nodes_iter'
THANKS!

Hi @whispersbowl ,
Can you check your networkx version? see below:
import Python 2.7.10 (default, Sep 22 2017, 12:11:41)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import networkx
networkx.__version__
>>> networkx.__version__
'1.9.1'

i checked and it is version 2.0, do I need to downgrade?

@whispersbowl ,
It seems like nodes_iter was removed in version 2.0.
See in version 1.9, nodes_iter is described under the Nodes section:
https://networkx.github.io/documentation/networkx-1.9/reference/functions.html#graph
It appears in version 2.0 the function is now called nodes under the Nodes section:
https://networkx.github.io/documentation/stable/reference/functions.html
I'll file a bug/issue to make note of this. I'll probably write something in the code to handle both 1.9 and 2.0 cases (since I imagine many may still be using 1.9).
--Liz

thanks!


(#324) add send message to slack when developer was screening complet…

https://github.com/howtohireme/give-me-poc/issues/324
Description
(#324) add send message to slack when developer was screening completed, refactoring messsage to slack ideas
Testing steps
Explain how to test your PR manually

rails db:schema:load && rails db:seed
Loging user via GitHub, complete all steps
When developer completed last test task, will be send message to slack in channel bootcamp-recruiting

Features PR URL
PR #ID
Checklist
Make sure that all steps a checked before the merge

[x] RSpec tests are passing on CI
[x] Cucumber features are passing localy
[x] bin/cop -a does not return any warnings
[x] Tested manually

Screenshots
https://monosnap.com/file/bHP4NQryHAdW8JDsIF1Iw1CZRI4Ap0
https://monosnap.com/file/5DV1oQbKEC2vwKOpeURlnm369217l9

rebase needed


Fixed click on items in Search tab #664

Description
Before: I enter in the Search tab, I see all the items on Top Apps. When I click on an item, the click works only if I click on the image (but not on the item itself, for example in the grey background).
As a solution, now it is possible to click on the item instead of the image.
- Hacktoberfest 2022 entry -
Fixes #664
Type of change
Please delete options that are not relevant.

[ X ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

recheck

fixed in bf0c11435d46e6db3e53e72b6418deebe572a8e1


Prevent adding apiKey twice and add custom user-agent header

In version 1.0.2 I still see malformed URL like this
https://geocode.xyz/59.6586467,10.9956267&auth=123...?geoit=json&auth=123...
The apiKey is included twice and the url has an & before the query parameters begin. This patch removes the & and apiKey from the url, as the API key also get added to the query params where it belongs.
After applying the patch I see url's like this
https://geocode.xyz/59.6488783,11.0190283?geoit=json&auth=123...

@imvalient Could you take a look at his, please, and maybe put in in a new release? I am seeing some problems on iOS that I believe are due to the malformed urls

The problem lies in that the geocode.xyz service is using Cloudflare, and they have started to block requests with the regular Dart user agent.
Example request that I copied from Flutter DevTools and ran manually, which failed with status 403 and an error message from Cloudflare saying I had been blocked.
curl --location --request GET 'https://geocode.xyz/59.6597683,11.002845?geoit=json&auth=xxx' --header 'user-agent: Dart/2.19 (dart:io)' --header 'content-length: 0' --header 'host: geocode.xyz'
When changing the user agent to "geocode", then the request goes through as normal
curl --location --request GET 'https://geocode.xyz/59.6597683,11.002845?geoit=json&auth=xxx' --header 'user-agent: geocode (dart:io)' --header 'content-length: 0' --header 'host: geocode.xyz'.
I added an extra commit that changes the user-agent header from Dart to geocode.

Thanks and great work @ahaaje , merged.


react-native init fails to set up new project, without yarn (Windows)

On windows, "react-native init" fails to setup proper working environment, if no yarn is installed and default npm is used to set up new react-native project.
I got "Cannot find entry file index.android.js in any of the roots" error, i manually patched this issue, and then i get next error "Cannot resolve module react".
I installed yarn, executed new project. All issues are gone.
Additional Information
npm 3.10.10
node 6.10.0
react-native-cli 2.0.1
Windows 7
Path used "C:\hub\sec", where react-native cli was referring to "c:\hub\sec", i don't know, if it had any problems with path's capital letters.

+1
I assume that yarn may be the source of evil

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


iPython notebook not loading with Jupyter extension on remote machine

Issue Type: Bug

Connect to remote server
Install Pylance
Create sample.ipynb

This results in a blank screen, with no jupyter notebook interface
VS Code version: Code 1.57.0 (b4c1bd0a9b03c749ea011b06c6d2676c8091a70c, 2021-06-09T17:22:31.215Z)
OS version: Darwin x64 20.4.0
Restricted Mode: No
Remote OS version: Linux x64 5.8.0-53-generic
Remote OS version: Linux x64 5.8.0-53-generic
Remote OS version: Linux x64 5.4.89+

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
5, 4, 3

Memory (System)
32.00GB (1.38GB free)

Process Argv
--crash-reporter-id 1572910a-3d68-41d5-8b2d-a8224b00f95b

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: torino

OS
Linux x64 5.8.0-53-generic

CPUs
Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (32 x 1205)

Memory (System)
125.80GB (0.72GB free)

VM
0%

Item
Value

Remote
SSH: torino

OS
Linux x64 5.8.0-53-generic

CPUs
Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz (32 x 1205)

Memory (System)
125.80GB (0.72GB free)

VM
0%

Item
Value

Remote
pod-arjun in pod-arjun (gcr.io/hai-gcp-fine-grained/default)

OS
Linux x64 5.4.89+

CPUs
Intel(R) Xeon(R) CPU @ 2.20GHz (8 x 2199)

Memory (System)
29.40GB (13.44GB free)

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

remote-containers
ms-
0.183.0

remote-ssh
ms-
0.65.7

remote-ssh-edit
ms-
0.65.7

remote-wsl
ms-
0.56.5

vscode-remote-extensionpack
ms-
0.21.0

python
ms-
2021.5.926500501

vscode-pylance
ms-
2021.6.1

jupyter
ms-
2021.6.999406279

Example image:

@ad12 can you open Developer Tools and share logs from there?

@rebornix which particular logs would be helpful? this is the console output:

@ad12 the logs didn't show any errors which can relate to this. Can you check if you have workbench.editorAssociations in your user setting and share the value?

@rebornix Yup, I do have it, and it appears to include the correct item,value pair for jupyter notebooks

same problem

Also running into this

I've had this issue too


Cannot make with latest forge version

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.4.0
Electron version
30.0.1
Operating system
macOS 14.4.1
Last known working Electron Forge version
6.4.2
Expected behavior
Hello guys,
i need your help to resolve a strange problem i have running "electron-forge make"
i just started a new project with the template vite + typescript.
for this project i needed to read serial port so i installed node-serialport.
i don't have problem during development but when i try to make the app i receive this error:

An unhandled rejection has occurred inside Forge:
Error: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-LCABM6/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-LCABM6/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package
at Filesystem.insertLink (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/filesystem.js:106:13)
    at handleFile (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:132:20)
    at next (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:148:11)
    at next (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:149:12)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MacApp.asarApp (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:245:5)
    at async MacApp.buildApp (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:150:5)
    at async MacApp.initialize (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:141:7)
    at async MacApp.create (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/mac.ts:435:5)
    at async Promise.all (index 0)
    at async packager (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/packager.ts:246:20)

this is my forge.config.ts

import type { ForgeConfig } from "@electron-forge/shared-types";
import { MakerSquirrel } from "@electron-forge/maker-squirrel";
import { MakerZIP } from "@electron-forge/maker-zip";
import { MakerDeb } from "@electron-forge/maker-deb";
import { MakerRpm } from "@electron-forge/maker-rpm";
import { VitePlugin } from "@electron-forge/plugin-vite";
import { FusesPlugin } from "@electron-forge/plugin-fuses";
import { FuseV1Options, FuseVersion } from "@electron/fuses";
import { readFileSync, writeFileSync, rmSync,  } from "node:fs";
import { rm } from "node:fs/promises";
import { resolve, join } from "node:path";
import { spawnSync } from "node:child_process";
import { globSync } from "glob";

const config: ForgeConfig = {
  packagerConfig: {
    asar: true,
  },
  rebuildConfig: {},
  makers: [
    new MakerSquirrel({}),
    new MakerZIP({}, ["darwin"]),
    new MakerRpm({}),
    new MakerDeb({}),
  ],
  plugins: [
    new VitePlugin({
      // `build` can specify multiple entry builds, which can be Main process, Preload scripts, Worker process, etc.
      // If you are familiar with Vite configuration, it will look really familiar.
      build: [
        {
          // `entry` is just an alias for `build.lib.entry` in the corresponding file of `config`.
          entry: "src/main.ts",
          config: "vite.main.config.ts",
        },
        {
          entry: "src/preload.ts",
          config: "vite.preload.config.ts",
        },
      ],
      renderer: [
        {
          name: "main_window",
          config: "vite.renderer.config.ts",
        },
      ],
    }),
    // Fuses are used to enable/disable various Electron functionality
    // at package time, before code signing the application
    new FusesPlugin({
      version: FuseVersion.V1,
      [FuseV1Options.RunAsNode]: false,
      [FuseV1Options.EnableCookieEncryption]: true,
      [FuseV1Options.EnableNodeOptionsEnvironmentVariable]: false,
      [FuseV1Options.EnableNodeCliInspectArguments]: false,
      [FuseV1Options.EnableEmbeddedAsarIntegrityValidation]: true,
      [FuseV1Options.OnlyLoadAppFromAsar]: true,
    }),
  ],
  hooks: {
    packageAfterPrune: async (
      _forgeConfig,
      buildPath,
      _electronVersion,
      platform,
      _arch
    ) => {
      /**
       * Serialport, usb and uiohook-napi are problematic libraries to run in Electron.
       * When Electron app is been built, these libraries are not included properly in the final executable.
       * What we do here is to install them explicitly and then remove the files that are not for the platform
       * we are building for
       */
      const packageJson = JSON.parse(
        readFileSync(resolve(buildPath, "package.json")).toString()
      );

      packageJson.dependencies = {
        serialport: "^10.0.0",
        usb: "^2.9.0",
        "uiohook-napi": "^1.5.2",
      };

      writeFileSync(
        resolve(buildPath, "package.json"),
        JSON.stringify(packageJson)
      );
      spawnSync("npm", ["install", "--omit=dev"], {
        cwd: buildPath,
        stdio: "inherit",
        shell: true,
      });

      const prebuilds = globSync(`${buildPath}/**/prebuilds/*`);
      const matchString = new RegExp(`prebuilds/${platform}`);
      prebuilds.forEach(function (path) {
        if (!path.match(matchString)) {
          rmSync(path, { recursive: true });
        }
      });

      // const gypPath = join(
      //   buildPath,
      //   "node_modules",
      //   "node-gyp-build",
      //   // "build",
      //   // "node_gyp_bins"
      // );
      // console.log("Removing gypPath", gypPath);
      // await rm(gypPath, { recursive: true, force: true });
    },
  },
};

export default config;

i tried to use "overrides" in package.json to try to use node-gyp version 8.2.0 as someone suggests on internet but i really don't understand how to resolve this issue
Thanks!
Actual behavior

An unhandled rejection has occurred inside Forge:
Error: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-LCABM6/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-LCABM6/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package
at Filesystem.insertLink (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/filesystem.js:106:13)
    at handleFile (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:132:20)
    at next (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:148:11)
    at next (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:149:12)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MacApp.asarApp (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:245:5)
    at async MacApp.buildApp (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:150:5)
    at async MacApp.initialize (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:141:7)
    at async MacApp.create (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/mac.ts:435:5)
    at async Promise.all (index 0)
    at async packager (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/packager.ts:246:20)

Steps to reproduce
Create a new electron project with vite+typescript
Install node-serialport (i don't know if this is the cause)
Try to make the project
Additional information

user@192 Servizio % DEBUG=electron-forge:* npx electron-forge make
✔ Checking your system

electron-forge:check-system checking system, create ~/.skip-forge-system-check to stop doing this +0ms
❯ Loading configuration
  electron-forge:project-resolver searching for project in: /Users/user/project/project/Servizio +0ms
  electron-forge:project-resolver package.json with forge dependency found in /Users/user/project/project/Servizio/package.json +1ms
The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.
  electron-forge:plugin:vite hooking process events +0ms
  electron-forge:hook hook triggered: resolveForgeConfig +0ms
✔ Loading configuration
❯ Resolving make targets
› Making for the following targets:
✔ Resolving make targets
❯ Running package command
❯ Preparing to package application
  electron-forge:project-resolver searching for project in: /Users/user/project/project/Servizio +804ms
  electron-forge:project-resolver package.json with forge dependency found in /Users/user/project/project/Servizio/package.json +1ms
  electron-forge:plugin:vite hooking process events +5ms
  electron-forge:hook hook triggered: resolveForgeConfig +5ms
  electron-forge:hook hook triggered: readPackageJson +0ms
✔ Preparing to package application
❯ Running packaging hooks
❯ Running generateAssets hook
  electron-forge:hook hook triggered: generateAssets +1ms
✔ Running generateAssets hook
❯ Running prePackage hook
  electron-forge:hook hook triggered: prePackage +0ms
❯ [plugin-vite] Building vite bundles
renderer config {
  command: 'build',
  mode: 'production',
  root: '/Users/user/project/project/Servizio',
  forgeConfig: { build: [ [Object], [Object] ], renderer: [ [Object] ] },
  forgeConfigSelf: { name: 'main_window', config: 'vite.renderer.config.ts' }
}
vite v5.2.10 building for production...
vite v5.2.10 building for production...
vite v5.2.10 building for production...
✓ 1 modules transformed.
.vite/build/preload.js  0.29 kB │ gzip: 0.18 kB
✓ built in 41ms
✓ 2 modules transformed.
.vite/build/main.js  3.63 kB │ gzip: 1.44 kB
✓ built in 71ms
✓ 11370 modules transformed.
.vite/renderer/main_window/index.html                                              0.38 kB │ gzip:   0.26 kB
.vite/renderer/main_window/assets/roboto-vietnamese-500-normal-Bwg8Dbh6.woff       4.73 kB
.vite/renderer/main_window/assets/roboto-vietnamese-700-normal-Mc0c6qif.woff       4.73 kB
.vite/renderer/main_window/assets/roboto-vietnamese-400-normal-BkEBOAV9.woff       4.75 kB
.vite/renderer/main_window/assets/roboto-vietnamese-300-normal-DOxDZ6bW.woff       4.77 kB
.vite/renderer/main_window/assets/roboto-vietnamese-300-normal-CnPrVvBs.woff2      5.47 kB
.vite/renderer/main_window/assets/roboto-vietnamese-700-normal-SekShQfT.woff2      5.55 kB
.vite/renderer/main_window/assets/roboto-vietnamese-400-normal-kCRe3VZk.woff2      5.56 kB
.vite/renderer/main_window/assets/roboto-vietnamese-500-normal-CcijQRVW.woff2      5.60 kB
.vite/renderer/main_window/assets/roboto-greek-700-normal-CjuTpGfE.woff            6.30 kB
.vite/renderer/main_window/assets/roboto-greek-500-normal-CVjdsdX9.woff            6.32 kB
.vite/renderer/main_window/assets/roboto-greek-400-normal-BnGNaKeW.woff            6.35 kB
.vite/renderer/main_window/assets/roboto-greek-300-normal-Dgbe-dnN.woff            6.44 kB
.vite/renderer/main_window/assets/roboto-greek-700-normal-Cc2Tq8FV.woff2           6.94 kB
.vite/renderer/main_window/assets/roboto-greek-500-normal-CpESfwfG.woff2           7.02 kB
.vite/renderer/main_window/assets/roboto-greek-400-normal-BRWHCUYo.woff2           7.11 kB
.vite/renderer/main_window/assets/roboto-greek-300-normal-ndiuWqED.woff2           7.12 kB
.vite/renderer/main_window/assets/roboto-cyrillic-400-normal-DCQqOlfN.woff         8.39 kB
.vite/renderer/main_window/assets/roboto-cyrillic-300-normal-UX5PCucy.woff         8.43 kB
.vite/renderer/main_window/assets/roboto-cyrillic-700-normal-DAIxw5xX.woff         8.66 kB
.vite/renderer/main_window/assets/roboto-cyrillic-500-normal-QpWeYsca.woff         8.70 kB
.vite/renderer/main_window/assets/roboto-cyrillic-300-normal-D6mjswgs.woff2        9.58 kB
.vite/renderer/main_window/assets/roboto-cyrillic-400-normal-DVDTZtmW.woff2        9.63 kB
.vite/renderer/main_window/assets/roboto-cyrillic-700-normal-B5ZBKWCH.woff2        9.64 kB
.vite/renderer/main_window/assets/roboto-cyrillic-500-normal-DAkZhMOh.woff2        9.84 kB
.vite/renderer/main_window/assets/roboto-latin-ext-700-normal-DwUXTeTv.woff       10.17 kB
.vite/renderer/main_window/assets/roboto-latin-ext-500-normal-B9pAx_JH.woff       10.18 kB
.vite/renderer/main_window/assets/roboto-latin-ext-400-normal-DloBNwoc.woff       10.21 kB
.vite/renderer/main_window/assets/roboto-latin-ext-300-normal-CaUuWeqj.woff       10.36 kB
.vite/renderer/main_window/assets/roboto-latin-ext-300-normal-DEsNdRC-.woff2      11.80 kB
.vite/renderer/main_window/assets/roboto-latin-ext-500-normal-BWKy6SgX.woff2      11.80 kB
.vite/renderer/main_window/assets/roboto-latin-ext-700-normal-BYGCo3Go.woff2      11.82 kB
.vite/renderer/main_window/assets/roboto-latin-ext-400-normal-4bLplyDh.woff2      11.87 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-700-normal-dDOtDc5i.woff    13.43 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-500-normal-sraxM_lR.woff    13.45 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-400-normal--KougVX-.woff    13.47 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-300-normal-C7AGhuC_.woff    13.55 kB
.vite/renderer/main_window/assets/roboto-latin-400-normal-BU1SoK4h.woff           14.38 kB
.vite/renderer/main_window/assets/roboto-latin-700-normal-Bh431LEL.woff           14.42 kB
.vite/renderer/main_window/assets/roboto-latin-500-normal-Dcm-rhWF.woff           14.42 kB
.vite/renderer/main_window/assets/roboto-latin-300-normal-lq7MgJXa.woff           14.59 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-700-normal-CsrCEJIc.woff2   14.68 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-500-normal-G9W8hgzQ.woff2   14.97 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-300-normal-TzZWIuiO.woff2   15.00 kB
.vite/renderer/main_window/assets/roboto-cyrillic-ext-400-normal-DORK9bGA.woff2   15.34 kB
.vite/renderer/main_window/assets/roboto-latin-300-normal-ThHrQhYb.woff2          15.74 kB
.vite/renderer/main_window/assets/roboto-latin-400-normal-mTIRXP6Y.woff2          15.74 kB
.vite/renderer/main_window/assets/roboto-latin-700-normal-CeM5gOv8.woff2          15.86 kB
.vite/renderer/main_window/assets/roboto-latin-500-normal-Dxdx3aXO.woff2          15.92 kB
.vite/renderer/main_window/assets/index-DuIfAhQ7.css                              23.24 kB │ gzip:  10.30 kB
.vite/renderer/main_window/assets/index-xUKAgONt.js                              366.79 kB │ gzip: 117.73 kB
✓ built in 3.53s
✔ [plugin-vite] Building vite bundles
✔ Running prePackage hook
✔ Running packaging hooks
❯ Packaging application
› Determining targets...
  electron-forge:packager packaging with options {
  asar: true,
  overwrite: true,
  ignore: [Function (anonymous)],
  quiet: true,
  dir: '/Users/user/project/project/Servizio',
  arch: 'arm64',
  platform: 'darwin',
  afterFinalizePackageTargets: [ [AsyncFunction (anonymous)] ],
  afterComplete: [ [AsyncFunction (anonymous)] ],
  afterCopy: [ [AsyncFunction (anonymous)] ],
  afterExtract: [ [AsyncFunction (anonymous)] ],
  afterPrune: [ [AsyncFunction (anonymous)] ],
  out: '/Users/user/project/project/Servizio/out',
  electronVersion: '30.0.1'
} +0ms
  electron-forge:packager targets: [ { platform: 'darwin', arch: 'arm64' } ] +3ms
❯ Packaging for arm64 on darwin
❯ Copying files
❯ Preparing native dependencies
❯ Finalizing package
  electron-forge:hook hook triggered: packageAfterExtract +5s
✔ Copying files
  electron-forge:hook hook triggered: packageAfterCopy +12ms
✔ Preparing native dependencies: 1 / 1
  electron-forge:hook hook triggered: readPackageJson +21s
  electron-forge:hook hook triggered: packageAfterPrune +1ms
  electron-forge:hook calling hook: packageAfterPrune with args: [
  '/var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app',
  '30.0.1',
  'darwin',
  'arm64'
] +0ms

added 4 packages, removed 94 packages, changed 17 packages, and audited 24 packages in 40s

12 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
✖ Finalizing package [FAILED: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package]
✖ Packaging for arm64 on darwin [FAILED: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package]
✖ Packaging application [FAILED: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package]
✖ Running package command [FAILED: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package]

An unhandled rejection has occurred inside Forge:
Error: /var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/.bin/node-gyp-build: file "../../../../../../../../../../../../var/folders/6x/jlwly1vx4dg6122w4ds182k00000gn/T/electron-packager/tmp-39bBbb/Electron.app/Contents/Resources/app/node_modules/node-gyp-build/bin.js" links out of the package
at Filesystem.insertLink (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/filesystem.js:106:13)
    at handleFile (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:132:20)
    at next (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:148:11)
    at next (/Users/user/project/project/Servizio/node_modules/@electron/asar/lib/asar.js:149:12)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async MacApp.asarApp (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:245:5)
    at async MacApp.buildApp (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:150:5)
    at async MacApp.initialize (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/platform.ts:141:7)
    at async MacApp.create (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/mac.ts:435:5)
    at async Promise.all (index 0)
    at async packager (/Users/user/project/project/Servizio/node_modules/@electron/packager/src/packager.ts:246:20)
  electron-forge:plugin:vite handling process exit with: { cleanup: true } +1m
  electron-forge:plugin:vite handling process exit with: { cleanup: true } +1ms

Setting asar: false i can make the program successfully

@dj-fiorex I am seeing similar issue but for my better-sqlite3 native lib. Did you ever make any progress on this other than setting asar to false?

Nothing to do, I tried two or three solutions but the problem remain

Same error as the screenshot for me when using serial port

Does anyone have any updates on this issue?
I'm also having trouble generating the package with better-sqlite3

I share my personal experience, hoping to help those who use C/C++ native modules.
First of all, we need to know that Webpack/Vite can only build static code that can be parsed into an abstract syntax tree (AST).
After building, the C/C++ native module will be a binary file ending with .node, which can be loaded by Node.js with the require function, but it cannot be built correctly by Webpack/Vite.
Of course, this is not absolute for Webpack. The community has mature C/C++ build tools, such as node-gyp, which always outputs .node files with a fixed file structure. For this reason, @vercel/webpack-asset-relocator-loader can determine that it is a C/C++ module based on the file structure, and then only needs to copy the .node file from node_modules to complete the build.
This is for modules with a "fixed build format". In other words, if the .node file path made by some module authors cannot be effectively analyzed by Webpack, then such modules will not be built normally. Unfortunately, serialport and better-sqlite3 cannot be built normally by Webpack.
I listed some C/C++ modules I have used.

Name
Bundle with Webpack/vite
Reason

serialport
❌
Dependency @serialport/bindings-cpp

utimes
❌

        https://github.com/baileyherbert/utimes/blob/v5.2.1/src/main.ts#L5-L11

better-sqlite3
❌

sqlite3
✅

fsevents
✅

Let's talk about what to do with C/C++ modules in Vite? I encapsulated vite-plugin-native using Webpack's build mode, which is compatible with those C/C++ modules that can be built normally by Webpack.
Finally, I want to talk about how Forge solves such problems. If you happen to use those C/C++ modules that cannot be built normally by Webpack/Vite, you can copy them to the node_modules of the built App. This seems stupid, but it works properly. For this reason, I only made electron-forge-plugin-dependencies to help you do this.

I share my personal experience, hoping to help those who use C/C++ native modules. First of all, we need to know that Webpack/Vite can only build static code that can be parsed into an abstract syntax tree (AST). After building, the C/C++ native module will be a binary file ending with .node, which can be loaded by Node.js with the require function, but it cannot be built correctly by Webpack/Vite. Of course, this is not absolute for Webpack. The community has mature C/C++ build tools, such as node-gyp, which always outputs .node files with a fixed file structure. For this reason, @vercel/webpack-asset-relocator-loader can determine that it is a C/C++ module based on the file structure, and then only needs to copy the .node file from node_modules to complete the build. This is for modules with a "fixed build format". In other words, if the .node file path made by some module authors cannot be effectively analyzed by Webpack, then such modules will not be built normally. Unfortunately, serialport and better-sqlite3 cannot be built normally by Webpack. I listed some C/C++ modules I have used.
Name	Bundle with Webpack/vite	Reason
serialport	❌	Dependency @serialport/bindings-cpp
utimes	❌
https://github.com/baileyherbert/utimes/blob/v5.2.1/src/main.ts#L5-L11
better-sqlite3	❌	The author may want people to customize the binding logic.
sqlite3	✅
fsevents	✅
Let's talk about what to do with C/C++ modules in Vite? I encapsulated vite-plugin-native using Webpack's build mode, which is compatible with those C/C++ modules that can be built normally by Webpack.
import { defineConfig } from 'vite';
import native from 'vite-plugin-native';
// https://vitejs.dev/config
export default defineConfig({
plugins: [
native({
// Enable Webpack
webpack: {},
}),
],
});
Finally, I want to talk about how Forge solves such problems. If you happen to use those C/C++ modules that cannot be built normally by Webpack/Vite, you can copy them to the node_modules of the built App. This seems stupid, but it works properly. For this reason, I only made electron-forge-plugin-dependencies to help you do this.
import type { ForgeConfig } from '@electron-forge/shared-types';
import { DependenciesPlugin } from 'electron-forge-plugin-dependencies';
const config: ForgeConfig = {
plugins: [
new DependenciesPlugin({
dependencies: [
'serialport',
],
}),
],
};
export default config;

You are truly amazing!!! This is the first actual solution that worked for me with the nfc-pcsc libary, you have no clue how many hours I have been researching this. I am now able to make a executable.
Works on Mac OS with electron 31 and 32, but not with electron 33 with all the node gyp errors.

Doesn't work on windows unfortunately


openai.api_base url change

openai.api_key = "..."
openai.api_base = "https://example-endpoint.openai.azure.com"
How do I change the base url of the called API?

export OPENAI_API_BASE="https://your-custom-url.com"


DASHBUILDE-78: Wrong URL redirect in Tomcat after login

Fix broken webapp security-contraints

+1 Tested in my local and works fine, but I cannot push it.

master: bdbcae1803020ddb9e2a94c8fc71fd605a983c84


Dev0 6

cleaned up the show function for IS.Results for cases where the results are verrrry large

@Lilyhanig please correct the formating


Added a table of contents and numbered the sections.

I added a table of contents at the beginning of the README, because even though GitHub provides an automated table of contents in the small top right icon, new users could not know about it. Also, I numbered the sections to make it easier navigation through the file.

@mixkrip Thanks for the contribution, merged!


Version change

Implement new API format for easier JSON handling.
Restructured for more standard and easier implementation of input parameters, output parameters, and row handling.
Adjust tests for new structure and add additional tests.

Addresses #9 and #8


patch express js vuln

fixes the following CVE which appears twice since qa shows up twice in express' dependency tree
https://github.com/advisories/GHSA-hrpp-h998-j3pp

Closed, issue is resolved in #3


For instance, racer complete core::option::Opt finds the type Option correctly, but racer complete core::option::Option::Som does not find the constructor Some (nor does racer complete Option::Som in a file in which option is implicitely in scope).

Doing an Option::Som completion in an editor works. I'm not sure why command line doesn't
E.g. /tmp/file.rs
fn main() {
    ::std::option::Option::Som
}

% racer complete 2 30 /tmp/file.rs
PREFIX 27,30,Som
MATCH Some,173,4,/usr/local/src/rust/src/libcore/option.rs,EnumVariant,Some(T)
END


I get an error: "The application was unable to start correctly (0xc000007b). Click OK to close application.

I followed all the steps and everything seemed to install correctly. There were no errors installing python 3.3.5 ,pip, or python neovim. Finally I unzipped NeoSFML and ran the exe and this was the error:
---------------------------
neosfml.exe - Application Error
---------------------------
The application was unable to start correctly (0xc000007b). Click OK to close the application.
---------------------------
OK
---------------------------

I'm on Windows 10 64bit
Do I unzip the neosfml anywhere? How can I verify everything installed properly? I have checked the Path variable User variables for adabao not System variables. There is c:\Python33 and C:\tools\neovim\Neovim\bin. Am I missing something?

I compiled on Windows 7 x64, so the OS is probably not the problem.
Unzipping is necessary, but the place where you do it does not matter.
Could you, please, do the following things and see what happens?
From the command prompt (Win + R), run:

python
then
nvim
If these two work (are found, that is), then it would help to see the output of neosfml.exe itself:
cd NeoSFML/build_windows
neosfml

Since neovim is unstable, I would not be surprised to find out that API has changed. In this case, I am not sure when I can investigate, since I don't even have a Windows machine now.
If you are looking for a neovim front end for work and not for experiments, I would suggest using neovim-qt. I will soon update readme to warn about this.

Win+R > python > nvim says:
Python 3.3.5 (v3.3.5:62cf4e77f785, Mar  9 2014, 10:35:05) [MSC v.1600 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> nvim
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'nvim' is not defined
>>>

I can call nvim from Win+R and cmd, however.

Since neovim is unstable, I would not be surprised to find out that API has changed. In this case, I am not sure when I can investigate, since I don't even have a Windows machine now.

Not a problem. I'm content using GVim. Truth be told I am just looking for a c++ autocomplete, syntax check, and snippets. I use Visual Studio Community to build/run. I prefer GVim as my editor, but out-of-the-box it is lacking these key features that I want.

If you are looking for a neovim front end for work and not for experiments, I would suggest using neovim-qt. I will soon update readme to warn about this.

I've tried many times over neovim's development cycle to make the switch, but I could not.
To be honest, I really don't know understand completely what your project is or intends to do. I just gave it my best shot to get it up and running.
I'd be willing to assist if you would like.

I can call nvim from Win+R and cmd, however.

This is in fact what I was wondering about :+1:
I googled for the 0xc000007b error - proposed fixes vary from running as admin to running chkdsk. Maybe there is something wrong with the zip file (packing, downloading, unpacking). Anyway, since python and nvim are found, it would still be nice to see what the output of neosfml.exe is.
cd NeoSFML/build_windows # or wherevere it is
neosfml.exe

This might hint at the root of the problem, at this point I am just curious what went wrong.

To be honest, I really don't know understand completely what your project is or intends to do.

This project was a milestone to Viy - basically Vim with pictures. I use emacs now.

I use Visual Studio Community to build/run.

You could compile straight from vim - it can show you all the errors and you could jump to them.

I just gave it my best shot to get it up and running.

Thank you for that : ) And sorry that it didn't work.

There is no output in cmd:
Microsoft Windows [Version 10.0.16299.125]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Users\Skooch>cd C:\Users\Skooch\Downloads\neosfml

C:\Users\Skooch\Downloads\neosfml>neosfml.exe

C:\Users\Skooch\Downloads\neosfml>

It's just the window with the previously mentioned error message.

I did not figure out how to embed visuals in an elegant way.
Hahah but does it work? Can't you just revisit it later?


Failed to connect error when entering Tapo app credentials when adding a new device

Version of the integration 3.1.2
 Version 3.1.4 downloaded and manually updated, but integration stilll shows 3.1.2 as does entry in const.py file (date of file 11.07.24
Configuration
Trying to add Tapo H100 hub, firmware version 1.5.20 build 240911 release 110830
Add your logs here.

Describe the bug
Home Assistant recognizes the addition of the H100 hub, however when I try to configue and enter the app credentials it fails with a message of "FAILED TO CONNECT"
email address used for crediatials does not contain any up case characters, but does contain numbers and an underscore.
Debug log
This error originated from a custom integration.
Logger: custom_components.tapo.config_flow
Source: custom_components/tapo/config_flow.py:231
integration: TP-Link Tapo (documentation, issues)
First occurred: 21:54:04 (2 occurrences)
Last logged: 22:07:29
Failed to setup cannot connect
Traceback (most recent call last):
File "/config/custom_components/tapo/config_flow.py", line 317, in _async_get_device
await device.update()
File "/usr/local/lib/python3.12/site-packages/plugp100/new/tapodevice.py", line 79, in update
await component.update(state)
File "/usr/local/lib/python3.12/site-packages/plugp100/new/components/hub_children_component.py", line 47, in update
await child_device.update()
File "/usr/local/lib/python3.12/site-packages/plugp100/new/tapodevice.py", line 79, in update
await component.update(state)
File "/usr/local/lib/python3.12/site-packages/plugp100/new/components/smart_door_component.py", line 15, in update
self.is_open = current_state["is_open"]
~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'is_open'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/config/custom_components/tapo/config_flow.py", line 231, in async_step_discovery_auth_confirm
device = await self._async_get_device_from_discovered(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/config_flow.py", line 295, in _async_get_device_from_discovered
return await self._async_get_device(config | {CONF_HOST: discovered.ip}, discovered)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/config_flow.py", line 322, in _async_get_device
raise CannotConnect from error
custom_components.tapo.errors.CannotConnect

Add your logs here.

Perhaps this helps you as well ...
https://github.com/petretiandrea/home-assistant-tapo-p100/issues/781#issuecomment-2421872696

@JimmyKer, thanks for the pointer, unfortunatley it did not resolve the issue. I followed the procedure noted in the post, but received the same error message. My Tapo app pasword does contain alpha and numeric characters, and meets the minimmum character count, however, my app password does not incude any symbols or special characters. The credentials have always worked previousl when adding a P110 smart plug. To check I have added a further smart plug today with out issue, So I figue there is no issue with the credentials themselves.
The issue seems to be limited to adding the H100 hub, would I be better with the H200 hub? is this supported?
I have got around the issue somewhat by linking to the hub, and its linked device (T110) Smart Contact Sensor via Matter. But I would ike to resolve the matter for the Tapo Integration..
Just as a side note, when I changed the password, my existing Tapo smart plugs would not connect, obviousy due to the change in password, how do I update these for the new password? Not a biggy as I have reverted back to my orignal password, but worth knowing for the future. (I did reboot HA after changing the password)
Ad.

Just to update this, I have found I have to change the Tapo password in the Tapo app when I get this error. After changing password I can connect again from HA

@Adrian281701 Hello Adrian.. How do you do to configure the T110 via Matter? I am having the same problem, that after I add the sensor, HA stops working.

Do we have to keep changing the password in the Tapo app every time we add a device?

@Adrian281701 Hello Adrian.. How do you do to configure the T110 via Matter? I am having the same problem, that after I add the sensor, HA stops working.

@ebanin Apologies for a late response work keeps getting in the way. To be honest I dont really recall what i did I know I click on something that referenced linking to matter, and it seemed to work. I eventually switched over to using the TP Link Smart Home Integration over the TP Link Tapo custom integration, everything then fell into place and everythink worked.

Do we have to keep changing the password in the Tapo app every time we add a device?

@TheShai1 No, I just tried changing my password the once to see if that I had miss rembered or miss typed my password. I eventually switched over to using the TP Link Smart Home Integration over the TP Link Tapo custom integration, everything then fell into place and everythink worked as it should from that point


Add IMAGES results type, to be used for releases

This way, we can easily specify all of the images built during the release build process, and chains can sign all of them

/lgtm


[hlx up] Requesting / fires an error

PR for https://github.com/adobe/petridish/issues/70

Fallback to README is more complicated. For now, only mapping properly / to /index.html

Shouldn't we read this from the index configuration property in the strain?

Pb is that Petridish does not know about strains (yet)... It does not read the strains.yaml file nor having something strain related.

I improved the code to use the computed index (index.md or README.md): computation is made by HelixServer on init. Better than before and cover the 2 files.

I also change the checkPaths() code which I think was wrong: priority was given to README.md (computed after index.md) - if both are here, README.md wins which should be the other way around.

Need to fix the tests.

Codecov Report

Merging #69 into master will decrease coverage by 0.73%.
The diff coverage is 62.5%.

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
- Coverage   94.25%   93.52%   -0.74%
==========================================
  Files           7        7
  Lines         383      386       +3
  Branches       54       55       +1
==========================================
  Hits          361      361
- Misses         22       25       +3

Impacted Files
Coverage Δ

src/RequestContext.js
100% <100%> (ø)
:arrow_up:

src/HelixProject.js
93.52% <50%> (-2.07%)
:arrow_down:

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 076e5f4...6c02a9d. Read the comment docs.

The fact is that we need to decide based on the path requested without knowing the actually folder / file structure. As mentioned above, the only rule I see for now is if the requested path does not have an extension, then automatically append the index.
And yes, we could have an extra config somewhere to define what is the default index (I like though the fact that we compute it automatically for local content)

As mentioned above, the only rule I see for now is if the requested path does not have an extension, then automatically append the index.

That would be consistent with our VCL.

I suggest:

remove this._indexMd and all that logic
add simple this._directoryIndex, withDirectoryIndex(), get directoryIndex()
if path has no . after last slash, append this._directoryIndex

I added:
2. add simple this._directoryIndex, withDirectoryIndex(), get directoryIndex()
3. if path has no . after last slash, append this._directoryIndex
I wonder if this is worth for me spending more time on this since every will change again with #76, especially the this._indexMd and all that logic.

let's fix this for now, and then improve it later with #76


Bluetooth: ATT: Fix crash if bt_l2cap_send_cb fails

This fixes a regression introduced by
10841b9a14b748a34c05cdebf0e9a278433a6ddc as it did remove a call to
net_buf_ref which was used not only to keep a reference for resending
but also to prevent bt_l2cap_send_cb to unref the buffer in case it
fails.
Signed-off-by: Luiz Augusto von Dentz<EMAIL_ADDRESS>

This reminds me, we should probably document, both for internal and external functions, the semantics wrt buffer handling, i.e. do they take ownership and if so always or under specific conditions like success. E.g. chan_send() has zero documentation currently (note I don't mean doxygen documentation but just any code comment describing the behaviour of the function)

This reminds me, we should document, for both internal and external functions, the semantics wrt buffer handling, i.e. do they take ownership and if so always or under specific conditions like success. E.g. chan_send() has zero documentation currently (note I don't mean doxygen documentation but just any code comment describing the behaviour of the function)

The bt_l2cap_chan_cb do have this documented: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/bluetooth/host/l2cap_internal.h#L303
So this is specific to chan_send if does handles faiilures gracefully by restoring the state thus why it needs to keep a reference for itself, I will add a comment to chan_send regarding this logic.

@Vudentz @jhedberg I think it would be to have the bug fixed first and then do the refactoring separately.
We could then have the fix backported, and the refactoring only on master branch.
The public API bt_l2cap_chan_send has now a different behavior in buffer handling.

@Vudentz @jhedberg I think it would be to have the bug fixed first and then do the refactoring separately.
We could then have the fix backported, and the refactoring only on master branch.
The public API bt_l2cap_chan_send has now a different behavior in buffer handling.

Hmm, I didn't change the buffer management there since it would still queue the buffer or you meant to say we would need something like:
diff --git a/subsys/bluetooth/host/l2cap.c b/subsys/bluetooth/host/l2cap.c
index 55d59c0110..af1a084f47 100644
--- a/subsys/bluetooth/host/l2cap.c
+++ b/subsys/bluetooth/host/l2cap.c
@@ -2603,6 +2603,7 @@ int bt_l2cap_chan_send(struct bt_l2cap_chan *chan, struct net_buf *buf)
                        return data_sent(buf)->len;
                }
                BT_ERR("failed to send message %d", err);
+               net_buf_unref(buf);
        }

        return err;

@joerchan btw, I did update BR code as well.

@jhedberg @joerchan Ive updated the changes, so bt_l2cap_chan_send (the only public API affected) behaves just as before.

Is this still the case @Vudentz? Doesn't seem like it in the code as per inspection.

@Vudentz Now we have two different buffer semantics for the two functions: bt_iso_chan_send and bt_l2cap_chan_send.
In my opinion we should update bt_iso_chan_send to have the same semantics as bt_l2cap_chan_send and not unref the buffer.
I think it makes for better application code to unref the buffer on error instead of ref'ing and unref on success if the application wishes to have a queue.
If we do this then we don't need the internal bt_conn_send_(cb)_unref function since there is no more users of it.
Also the buffer semantics of bt_iso_chan_send should be documented in the public API header.
I can see that the central_iso sample does not unref the buffer while the shell does unref it, so atleast one of them is wrong.
I guess it is a definition question for the L2CAP API if this is a behavior change or a bugfix but to me this seems like a behavior change and should be documented in the release notes.

Well while I agree that bt_iso_chan_send shall have the same semantics it seems the direction you are given is that this would not be backported to 2.5 leaving it broken there as well, this debate for behavior change sounds a little conflicting with the direction given initially and in the meantime we could have applied the initial fix.


Poisoning problem

see Wansbrough, Keith, and Simon Peyton Jones. "Once upon a polymorphic type." Proceedings of the 26th ACM SIGPLAN-SIGACT symposium on Principles of programming languages. ACM, 1999.

Closing this as I now find it mood.
If you are programming agains Member constraints there are no problems. Even handlers only concretize one cons  worth of the effect type which is then stripped away.


Angular v6 with RxJS v6

Package
Version
Released

apollo-angular
1.1.0-rc.0
May 09 2018 15:39

apollo-angular-link-http-common
1.1.0-rc.0
May 09 2018 15:39

apollo-angular-link-http
1.1.0-rc.0
May 09 2018 15:39

apollo-angular-link-http-batch
1.1.0-rc.0
May 09 2018 15:39

apollo-angular-link-persisted
1.0.0-beta.1
May 09 2018 15:39

apollo-angular-link-headers
1.1.0-rc.0
May 09 2018 15:39

apollo-angular-cache-ngrx
1.0.0-beta.1
May 09 2018 15:39

All have been released with next tag, so yarn add apollo-angular@next will work.

so exciting!!! when is this gonna merge?

Nice work so far, can't wait to use it!

An update. I released new versions that supports angular 6.
Glad to hear it works without any issues :)

Thank you for nice job @kamilkisiela!
I'm currently recording a course about Angular + GraphQL, do you have any expected date for the final version?
Hug!

@plinionaves probably day or two.

Wow, great @kamilkisiela!
I will await then, thank you so much for the fast feedback!


OCM-10778 | ci: Reset rhcs CI using latest terraform version

What this PR does / why we need it:
Reset rhcs CI using latest terraform version
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story (OCM-xxxx):
Fixes #
OCM-10778
Change type

[ ] New feature
[ ] Bug fix
[ ] Build
[x] CI
[ ] Documentation
[ ] Performance
[ ] Refactor
[ ] Style
[ ] Unit tests
[ ] Subsystem tests

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.

/test unit

/test unit

/test unit

/approve


[Event Extension Request] Table 221 "Gen. Jnl. Allocation" - new Parameter in Publisher OnAfterShowDimensions

Hello, we need a new Parameter in the Publisher OnAfterShowDimensions. Can you please check that? Thank you!
procedure ShowDimensions()
begin
    "Dimension Set ID" :=
      DimMgt.EditDimensionSet("Dimension Set ID",
        StrSubstNo('%1 %2 %3', "Journal Template Name", "Journal Batch Name", "Journal Line No."),
        "Shortcut Dimension 1 Code", "Shortcut Dimension 2 Code");

    OnAfterShowDimensions(Rec, xRec);            <===============
end;

New Event signature:
[IntegrationEvent(false, false)]
local procedure OnAfterShowDimensions(var GenJnlAllocation: Record "Gen. Jnl. Allocation"; var xGenJnlAllocation: Record "Gen. Jnl. Allocation")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 47702.


Optimizing inducing points

@karlnapf
take a look at this

@karlnapf
may take a look at the notebook for demonstration
http://nbviewer.ipython.org/gist/yorkerlin/e69926dbea6d47946d79#optInd

Fine to merge this one apart from some technical minors

Ill merge since travis error is unrelated.
BTW are there any unit tests for this?

As usual, it would be cool to have a patch that addresses the comments above
Just trying it on my machine


feat: burpference switcher hotkey

🏴☠ Burpference
Ahoy, Mateys!
Ahoy, ye scurvy dogs, and welcome aboard Burpference! For non-forks, leave that there pull request description blank, and let rigging work its sorcery like a true sea wizard. Arrr!

comples #5


CLOUD-44323 added ability to define scopes

@akanto pls check.
Uaa migartion process added

We need this ASAP as QA doesn't work for now due to the lack of migration - documentation is coming.


Fabric view: slight flicker of ErrorBoundary component on page load

Expected Behavior
Page loads only with elements that "should" be visible.
Actual Behavior
Page loads with the ErrorBoundary component briefly present.

Steps to Reproduce the Problem

Refresh page
Observe ErrorBoundary component briefly visible with no text in it

Specifications

Version: 0.9.1
Platform: macOS Sierra 10.12.4
Subsystem: Safari 10.1

Unable to reproduce the problem in browserstack.  Confirming with others...

@tilleryd Unable to reproduce the problem in browserstack. I'd like to test again with slow load but Safari doesn't seem to have devtool network throttling option.

@spmcbride1201 I dont see this issue anymore.

@karinakeen - Okay go ahead an close!


Cleaned up logging in build server

Issue - #1954
Meta - #1921
Before this we weren't passing the output from the different commands in the build server to the task that is waiting for the result. Included some general cleanup as well.

🆙 📅


SpdxDocumentReporter: Report information about the dependencies

See individual commit messages for the details.

With this PR the SPDX reporter is producing useful SPDX document so I recommend you also add it to README.md file as one of the available reporter.

With this PR the SPDX reporter is producing useful SPDX document so I recommend you also add it to README.md file as one of the available reporter.

I'll do that in a follow up PR.


closes #163

HistoricalGeneratorStream added
tests improved

Coverage decreased (-0.5%) to 92.889% when pulling 9d1e6b19988e67e5fdabdb4ffb31f39e1aed966e on task/163-historical-gen into 53c58d309f3bf1c2164ece067eb343af8295ddf8 on release/1.10.0.


[SPARK-45634][PS] Remove DataFrame.get_dtype_counts from Pandas API on Spark

What changes were proposed in this pull request?
This PR proposes to remove old API get_dtype_counts from Pandas API on Spark
Why are the changes needed?
This API was deprecated a long time ago, but has not been removed since it's internally used in our code base. But it's no longer used in anywhere currently.
Does this PR introduce any user-facing change?
DataFrame.get_dtype_counts is removed.
How was this patch tested?

No new test is required for API removal. The existing CI should pass.
Was this patch authored or co-authored using generative AI tooling?

No.

Merged to master.


Missing tensorflow/core/debug/debug_service.grpc.pb.h header file

Hi,
debug_io_utils.h includes a header file tensorflow/core/debug/debug_service.grpc.pb.h, which is missing from the repo. This causes build on Linux failed.
`// TODO(cais): Support grpc:// debug URLs in open source once Python grpc
//   genrule becomes available. See b/23796275.
#ifndef PLATFORM_WINDOWS
#include "tensorflow/core/debug/debug_service.grpc.pb.h"
`
Anyone see this issue?
Thanks,
RLE

@caisq I think this change may relates to the problem: https://github.com/tensorflow/tensorflow/commit/41803db36d4f4a3239bd81e5d460eb0e6e2eea88
That changes #if defined(PLATFORM_GOOGLE) to #ifndef PLATFORM_WINDOWS, which essentially allows it to #include "tensorflow/core/debug/debug_service.grpc.pb.h" on Linux but that file does not exist on the master branch.
Could you help taking a look?

debug_service_grpc.pb.h is an automatically generated file from this bazel BUILD rule:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/debug/BUILD#L45
So there should be no problem building TF is you are using bazel. What build tool are you using?

I used Linux Continuous Integration Build steps from this link: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/cmake/README.md

So I see that you are running cmake build on Linux. This is our nightly build:
http://ci.tensorflow.org/view/Nightly/job/nightly-cmake-cpu/
It seems to be okay. You can look at the log to see what commands / configuration it uses:
http://ci.tensorflow.org/view/Nightly/job/nightly-cmake-cpu/368/consoleFull

On Ubuntu 16 with anaconda 2.7, when running
cmake -DCMAKE_BUILD_TYPE=Release ../tensorflow/contrib/cmake
make -j6 all
I get the error: fatal error: tensorflow/core/debug/debug_service.grpc.pb.h: No such file or directory
Any ideas how to resolve this?

Encountered the similar issue. The
tensorflow/core/debug/debug_service.pb.h

was generated but not
tensorflow/core/debug/debug_service.grpc.pb.h

so the make fails.
I assume *.grpc.pb.h might be generated with grpc plugins though I am not familiar with cmake so not sure how to fix it.

Confirmed on Mac OS X using CMake 3.7.2.

Created a PR #13145 that should fix the cmake issue on Linux.


setup: fix mac os x toolkit local install

Without the versions added in the commit, the make first-run command failed

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

 How's it going? I hope you're having a fantastic day! Is there anything you'd like to talk about or any questions you have in mind? I'm here to help and provide some enjoyable and informative conversations.", "citations": [], "documents": [], "search_results": [], "search_queries": [], "tool_calls": [], "finish_reason": "COMPLETE"}}

@francisco-perez-sorrosal thanks for doing this! ✅

Hey, sorry for the delay in doing this. Updated the main branch, rebased my commits, squashed them into a single one and signed it. Hope is what you need! Thanks!

I had to remove completly psycopg2 on my side otherwise it fails
psycopg2-binary seems to be enough

@francisco-perez-sorrosal pytest is failing because you need to update the lock file. run poetry lock

Done! Just, updated poetry.lock


[BUG] - Autocomplete - Shift + Home/End isn't working

NextUI Version
2.4.8
Describe the bug
Shift + Home/End doesn't work in Autocomplete input.
It works in Input component, but not in Autocomplete.
For example, I can make Shift + Left/Right Arrow and it works just fine. But the other key combination no...
It happens in Firefox and Chrome browsers, in my project or even in your website...
Is it possible to make it work?
Your Example Website or App
https://nextui.org/docs/components/autocomplete
Steps to Reproduce the Bug or Issue
1 - Click in autocomplete
2 - Type something...
3 - Click of mover the cursor to the middle of the text, for example.
4 - Make Shift + Home/End
It will do nothing...
Expected behavior
It should Select the text from the initial position of the cursor up the start (Shift + Home) or to the end (Shift + End).
Screenshots or Videos
No response
Operating System Version
Linux
Browser
Firefox

It worked when I tested it in the docs. Please send a minimal reproduction. By the way, I don't think the Shift key needs to be pressed. ref: Combobox Pattern | APG | WAI | W3C

It worked when I tested it in the docs. Please send a minimal reproduction. By the way, I don't think the Shift key needs to be pressed. ref: Combobox Pattern | APG | WAI | W3C

You can check it on NextUI website or in CodeSandbox.
The cursor doesn't move when you click Home / End. So when you try to make Shift + Home / End, it will not work also...

same issue, unable to select selected text with shortcut key,
tested at Chorme browser in Windows OS.

I tried it again, and it works as expected. If possible, could you use a tool like KeyCastr to record your key inputs along with a screen recording and send it to me?
https://github.com/user-attachments/assets/1b54cd97-e5c7-43c1-b27e-8f5c5893bb04

It is possible to navigate in options. If you use ↓ to go there, then it is possible to use Home/End to jump to the first/last option.
But I was talking about text selection in autocomplete input. Like this:
Screencast from 08-10-2024 14:40:09.webm

Ah, I see. Thanks for the clarification.
When something is selected, using Home/End will work as expected. However, while the options are displayed, you’re navigating through the select element itself, which is why Home/End won’t function for text selection at that moment. I believe this is natural behavior.

I think that should happen only if the user clicked ↓ to navigate in that list with the arrows.
When you are typing something and then you decide to remove half of the text with Shift + End, but it doesn't work using only your keyboard, you will need to use your mouse to select the text or close the options part to be able to remove that part of the text...
If you have work with many big forms during your day, and use them multiple times, this action of always need to go to your mouse can be a bit annoying or less productive to some users...
Is it possible to allow the user to use Home / End if he is interacting with the text input? If the user is navigating on options part, then Home / End will do what they do at the moment: jump to first / last option...

@ryo-manba, do you think that it will be possible to implement something like I suggested?

You make a valid point. This behavior comes from React Aria hooks.
https://github.com/nextui-org/nextui/blob/8a33eabb2583202fcc8fbc33e8f2ed23bb45f1a4/packages/components/autocomplete/src/use-autocomplete.ts#L20
Could you please open an issue for this problem upstream?

It looks like Adobe React Spectrum took my issue in consideration and applied some fixes.
I tested their ComboBox in their website and it works just fine.
Is it possible to do the same in NextUI Autocomplete?


Assert at ble_ll_scan_aux_data_unref

Seeing an assert under load in ble_ll_scan_aux_data_unref at line 1079: , running latest master, commit: https://github.com/apache/mynewt-nimble/commit/cf8e8125fd2428adffd78ef0ea03fdae4faec88c
BLE_LL_ASSERT(aux_data);

We have BLE_EXT_ADV enabled and are initiating the scan proc periodically, with duration of 1500ms, then restarting it once it completes.

@sjanc @andrzej-kaczmarek this looks like the same assertion that was attempted to be fixed by this PR: https://github.com/apache/mynewt-nimble/pull/748 . Any help in fixing this would be appreciate.

(I have not yet been able to repro this on the bench with the debugger attached but as soon as I hit it, I will upload the full gdb backtrace).

@lance-proxy I've seen this assert a few times when running qualification testcases but also was not able to catch it on a debugger. there was a bit of refactoring done in scanner so I guess I missed a corner case somewhere, but don't have clue so far. backtrace would definitely help a lot.

@andrzej-kaczmarek @rymanluk  I finally caught a test device in the debugger. See attached gdb backtrace:
(gdb) bt
#0  hal_debug_break () at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/include/mcu/cortex_m4.h:37
#1  ble_ll_scan_aux_data_unref (aux_data=0x0) at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll_scan.c:1079
#2  0x000309a8 in ble_ll_scan_rx_pkt_in_on_aux (addrd=0x2001396c <g_ble_ll_stack+380>, hdr=0x2000d694 <os_msys_1_data+1168>, om=0x2000d67c <os_msys_1_data+1144>, pdu_type=<optimized out>)
    at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll_scan.c:3183
#3  ble_ll_scan_rx_pkt_in (ptype=<optimized out>, om=om@entry=0x2000d67c <os_msys_1_data+1144>, hdr=0x2000d694 <os_msys_1_data+1168>) at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll_scan.c:3207
#4  0x00029896 in ble_ll_rx_pkt_in () at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll.c:834
#5  ble_ll_event_rx_pkt (ev=<optimized out>) at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll.c:1161
#6  0x000297ae in ble_npl_event_run (ev=<optimized out>) at repos/apache-mynewt-nimble/porting/npl/mynewt/include/nimble/nimble_npl_os.h:116
#7  ble_ll_task (arg=<optimized out>) at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll.c:1211
#8  0x000163d2 in os_time_ms_to_ticks (ms=536951248, out_ticks=0x2001398c <g_ble_ll_stack+412>) at repos/apache-mynewt-core/kernel/os/src/os_time.c:346
#9  0x00000000 in ?? ()

Some LL global variable inspections:
(gdb) p g_ble_phy_data
$1 = {phy_stats_initialized = 1 '\001', phy_txpwr_dbm = 0 '\000', phy_chan = 37 '%', phy_state = 0 '\000', phy_transition = 2 '\002', phy_transition_late = 0 '\000', phy_rx_started = 1 '\001',
  phy_encrypted = 0 '\000', phy_privacy = 0 '\000', phy_tx_pyld_len = 12 '\f', phy_cur_phy_mode = 1 '\001', phy_tx_phy_mode = 1 '\001', phy_rx_phy_mode = 1 '\001', phy_bcc_offset = 0 '\000',
  rx_pwr_compensation = 0 '\000', phy_aar_scratch = 0, phy_access_address =<PHONE_NUMBER>, rxhdr = {{rxinfo = {flags = 2050, channel = 37 '%', handle = 0 '\000', rssi = -92 '\244', phy = 1 '\001',
        phy_mode = 1 '\001', user_data = 0x0}, txinfo = {flags = 2 '\002', offset = 8 '\b', pyld_len = 37 '%', hdr_byte = 0 '\000'}}, beg_cputime = 616833506, rem_usecs = 18}, txend_arg = 0x0,
  txend_cb = 0x0, phy_start_cputime = 616833416}

(gdb) p g_ble_ll_data
$2 = {ll_supp_features = 4110, ll_state = 0 '\000', ll_num_acl_pkts = 4 '\004', ll_acl_pkt_size = 255, ll_pref_tx_phys = 0 '\000', ll_pref_rx_phys = 0 '\000', ll_evq = {evq = {
      evq_owner = 0x200139d0 <g_ble_ll_task>, evq_task = 0x0, evq_list = {stqh_first = 0x20016b68 <g_ble_ll_rfmgmt_data+52>, stqh_last = 0x20016b74 <g_ble_ll_rfmgmt_data+64>}}}, ll_wfr_timer = {
    bsp_timer = 0x0, cb_func = 0x0, cb_arg = 0x0, expiry = 0, link = {tqe_next = 0x0, tqe_prev = 0x0}}, ll_rx_pkt_ev = {ev = {ev_queued = 0 '\000', ev_cb = 0x29831 <ble_ll_event_rx_pkt>, ev_arg = 0x0,
      ev_next = {stqe_next = 0x20016b68 <g_ble_ll_rfmgmt_data+52>}}}, ll_rx_pkt_q = {stqh_first = 0x0, stqh_last = 0x20013790 <g_ble_ll_data+72>}, ll_tx_pkt_ev = {ev = {ev_queued = 0 '\000',
      ev_cb = 0x297c9 <ble_ll_event_tx_pkt>, ev_arg = 0x0, ev_next = {stqe_next = 0x0}}}, ll_tx_pkt_q = {stqh_first = 0x0, stqh_last = 0x200137a8 <g_ble_ll_data+96>}, ll_dbuf_overflow_ev = {ev = {
      ev_queued = 0 '\000', ev_cb = 0x297c3 <ble_ll_event_dbuf_overflow>, ev_arg = 0x0, ev_next = {stqe_next = 0x0}}}, ll_comp_pkt_ev = {ev = {ev_queued = 0 '\000',
      ev_cb = 0x297bd <ble_ll_event_comp_pkts>, ev_arg = 0x0, ev_next = {stqe_next = 0x0}}}, ll_hw_err_timer = {co = {c_ev = {ev_queued = 0 '\000', ev_cb = 0x298a5 <ble_ll_hw_err_timer_cb>, ev_arg = 0x0,
        ev_next = {stqe_next = 0x0}}, c_evq = 0x20013758 <g_ble_ll_data+16>, c_ticks = 0, c_next = {tqe_next = 0x0, tqe_prev = 0x0}}}}

(gdb)  p g_ble_ll_scan_sm
$3 = {scan_enabled = 0 '\000', own_addr_type = 1 '\001', scan_filt_dups = 0 '\000', scan_rsp_pending = 0 '\000', scan_rsp_cons_fails = 1 '\001', scan_rsp_cons_ok = 0 '\000',
  scan_peer_rpa = "\000\000\000\000\000", pdu_data = {hdr_byte = 195 '\303', {scana = "|\210\034\063", <incomplete sequence \303>, inita = "|\210\034\063", <incomplete sequence \303>},
    adva = "9~H\276\317", <incomplete sequence \327>}, upper_limit = 4, backoff_count = 3, scan_win_start_time = 0, scan_sched_ev = {ev = {ev_queued = 0 '\000',
      ev_cb = 0x2fabf <ble_ll_scan_event_proc>, ev_arg = 0x20016db4 <g_ble_ll_scan_sm>, ev_next = {stqe_next = 0x0}}}, scan_timer = {bsp_timer = 0x2000c610 <nrf52_hal_timer5>,
    cb_func = 0x2f925 <ble_ll_scan_timer_cb>, cb_arg = 0x20016db4 <g_ble_ll_scan_sm>, expiry = 616833867, link = {tqe_next = 0x20016f50 <g_ble_ll_sched_timer>, tqe_prev = 0x0}},
  scan_interrupted_ev = {ev = {ev_queued = 0 '\000', ev_cb = 0x30441 <ble_ll_scan_interrupted_event_cb>, ev_arg = 0x0, ev_next = {stqe_next = 0x0}}}, duration_timer = {
    bsp_timer = 0x2000c610 <nrf52_hal_timer5>, cb_func = 0x30149 <ble_ll_scan_duration_timer_cb>, cb_arg = 0x20016db4 <g_ble_ll_scan_sm>, expiry = 616833516, link = {
      tqe_next = 0x20016de8 <g_ble_ll_scan_sm+52>, tqe_prev = 0x0}}, period_timer = {bsp_timer = 0x2000c610 <nrf52_hal_timer5>, cb_func = 0x2fcc5 <ble_ll_scan_period_timer_cb>,
    cb_arg = 0x20016db4 <g_ble_ll_scan_sm>, expiry = 0, link = {tqe_next = 0x0, tqe_prev = 0x0}}, duration_ticks = 51773, period_ticks = 0, ext_scanning = 0 '\000',
  restart_timer_needed = 0 '\000', cur_aux_data = 0x0, scanp = 0x20016e58 <g_ble_ll_scan_sm+164>, scanp_next = 0x0, scanp_phys = {{phy = 1 '\001', own_addr_type = 1 '\001',
      scan_filt_policy = 0 '\000', configured = 1 '\001', scan_type = 1 '\001', scan_chan = 37 '%', timing = {interval = 1310, window = 983, start_time = 616832884}}, {phy = 3 '\003',
      own_addr_type = 0 '\000', scan_filt_policy = 0 '\000', configured = 0 '\000', scan_type = 0 '\000', scan_chan = 0 '\000', timing = {interval = 0, window = 0, start_time = 0}}}}

(gdb) p p ble_ll_stats
No symbol "p" in current context.
(gdb)

(gdb) p p g_ble_ll_conn_create_sm
No symbol "p" in current context.
(gdb)

I will keep the DUT trapped in the debugger in this state. Please let me know if there is any other globals you would like me instead while its in this state to help you root cause the issue here.

@lance-proxy thanks a lot. the problem seems to be triggered by ADV_EXT_IND received at the same time scan is disabled although I need to look through the code to figure out proper fix. could you please also dump hdr and om->om_data[0] parameters in frame 2 or 3?

this should fix the problem (and some more...) https://github.com/apache/mynewt-nimble/pull/836

Many thanks @andrzej-kaczmarek! I will load your PR on the same test device, and monitor if this assertion occurs or not.

@andrzej-kaczmarek I see #836 is approved, so if we can get this merged to master today that would be great so we can do broader confidence testing of this patch.

@lance-proxy I've just merged it

@andrzej-kaczmarek no sign of this assertion after updating our test device fleet with master (including your PR fix above). Many thanks again for the quick turnaround fix on this! Im going to close this issue unless the issue re-appears.


[docs] Not that popular

[x] I have followed (at least) the PR section of the contributing guide.

:100: for changing it
On Wed, Jul 10, 2019, 18:15 Sebastian Silbermann<EMAIL_ADDRESS>wrote:

@eps1lon commented on this pull request.
In docs/translations/translations.json
https://github.com/mui-org/material-ui/pull/16548#discussion_r302153631:

@@ -66,7 +66,7 @@
"copySourceLinkJS": "Copy link to JavaScript source",
"copySourceLinkTS": "Copy link to TypeScript source",
"stackblitz": "Edit in StackBlitz (JS only)",

"headTitle": "The world's most popular React UI framework - Material-UI",

"headTitle": "The world's second most popular React UI framework - Material-UI",

I wasn't all that serious. Would still change it though.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mui-org/material-ui/pull/16548?email_source=notifications&email_token=AAYE3Q7YSFIUEQABCZJA5LDP6YDJJA5CNFSM4H7OAI6KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB6BG6RQ#discussion_r302153631,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYE3Q7WVTHFJLHCKR2U3X3P6YDJJANCNFSM4H7OAI6A
.

I agree that we can no longer claim those bragging rights, but the current suggestion seems a bit bland. How about we use part of the strap-line?
"Material-UI – React components for faster and easier web development."

@mbrookes Would it be a duplicate with the existing description?

Brainstorming time!
Material-UI – Ready-made React components for faster and easier web development.
Material-UI – Accessible React components for faster and easier web development.
etc. ?

Material-UI – Ready-made React components for faster and easier web development.

Sounds nice

Material-UI – Accessible React components for faster and easier web development.

Not yet. "Accessible" implies focus on a11y which we don't currently.

Not yet. "Accessible" implies focus on a11y which we don't currently.

If it was in our strap-line we would have to :wink:

Material-UI – Ready-made React components for faster and easier web development.

👍

Material-UI – Accessible React components for faster and easier web development.

I think that is too early. I think that we need first to run a professional manual audit of the components to better understand how well accessible our components are.
We could have a non-neglieale number of issues. If we are lagging far behind, it would require updating the priorities: https://material-ui.com/discover-more/roadmap/#our-priorities and to fix them.

I have pushed a change with Material-UI: A React UI component framework. Let me know what you think about it. It has the following constraints in mind:

as short as possible
describe what we do
contains important SEO keywords

A component library / framework is defacto “ready-made”...

Maybe?

Perhaps replace the word "popular" with "production-ready"? It reinforces the strap-line that follows.

What's the underlying core value of production ready? I went back to the popular angle to optimize for the long tail of users that are getting started and have little experience.
A popular project is often all it takes to onboard new users. The incentive for somebody starting is to avoid picking the wrong tools. A popular project is less likely to be the wrong choice.

Angular and Vue doesn't have any description. React has something very descriptive that doesn't stand out. It looks what whatever we pick only matter to the maintainers.

What does production ready optimize for?

Enterprise, but it speaks to a broader range of users. Maybe it's vanity that has me thinking that new users already know that Material-UI is popular.

@mbrookes I’ve been having the same vanity debate :P React can choose a simple tag line because it’s so popular. I’m not sure if we can do the same 🤷🏽♂

I'm closing. Don't think that this is a good use of our time. It won't change anything at the end of the day.
I will handle it in my next batch of changes. I will only replace "most popular" with "popular" to minimize the scope and to be fair. We can further discuss it on the Gitter channel.

3 years later, we are on track to get this 🥇 spot back. At the current speed, we are 32 days away.

((82076-81673)/(24.6-11.8)) = 32

82076: Current Ant Design stars
81673: Current Material UI stars
24.6: average stars/days over the last 30 days with Material UI
11.8: average stars/days over the last 30 days with Ant Design


tmp folder does not have rw permissions set

tmp folder does not have correct rw permissions set for all users
currently only root user can write to the tmp folder.
permissions need to be :
chmod 1777 /tmp
drwxrwxrwt 21 root root 12288 Apr 28 16:18 /tmp

This is odd, that baselayout build installs with permissions 1777, but the folder still has permissions set to 0777. I've changed it manually though and this should not be an issue with future releases, thanks for the help!

The latest release (0.4.0) still has issues with rw, /tmp's permissions are set to 1755 instead 1777. In case it makes a difference, I'm using Arch as a host, btrfs as the filesystem, and tar vxf gkiss-chroot.tar.xz -C /mnt as the tar command.

I updated the tarball, thanks for notifying me!


fix: PropTypes of Drawer.HeaderAccount

This fixes a warning with the PropTypes

There's also this warning but I can't figure out who's setting the property. I'd just allow the RippleFeedback color to be an object, since it gets parsed by Color anyway, but it's up to you.


Detect __ARM_FEATURE_SVE

The svtbl2 instructions seem to be not on all sve enabled processors, including the ones we care about.

I guess you mean __ARM_FEATURE_SVE2 too ?

I think that's what I meant yes


[Map] Show marker for groups of smaller features at lower zoom levels

Problem:
Smaller polygons aren't visible when zoomed out, and appear only as several pixels on the map.

Also, multiple markers at the same location pile up and overlap.
Potential solution:
At lower zoom levels we can group features using a marker with a number overlaid indicating the number of polygons at that location.
See also https://github.com/google/ground-platform/issues/673.

Obsolete due to #1152


Cleanup user-guide pages mu-t

The last pages of the User Guide requiring cleanup have been addressed. Simplified language and rst, style fixes.
QA Steps: Did not step through all instructions. Rendered HTML was inspected visually. Ran linter and linkcheck.
This commit applies to FFTK 988
Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[x] Review for wordiness
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Docs for 2bfbb0843d0664b0503400ed3681b7f0d6bc5da7 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2322/docs/artifacts/html/index.html

Docs for ce0fa3be5ff0281a7587cce9709b6fbfb548f24c are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2323/docs/artifacts/html/index.html


White page when viewing the changes

Describe the bug
When I go to the changes I get only a white page displayed, I noticed this since the last update.
Steps To Reproduce
Steps to reproduce the behavior:

Go to 'https://books.rollenspiel.monster/books/grundregelwerk/page/6-aspekte/revisions'
Click on 'changes'
See a blank page

Expected behavior
That the changes of the page are displayed.
Screenshots
If applicable, add screenshots to help explain your problem.
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): BookStack v0.31.4
PHP Version: 7.4.14
Hosting Method (Nginx/Apache/Docker): nginx

Additional context
nginx error.log
2021/01/21 20:53:36 [error] 1014#1014: *1917097 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/customers/webs/Anzah/books.rollenspiel.monster/vendor/ssddanbrown/htmldiff/src/WordSplitter.php on line 23PHP message: PHP Fatal error:  Uncaught ErrorException: file_exists(): open_basedir restriction in effect. File(/de/errors.php) is not within the allowed path(s): (/var/customers/webs/Anzah/books.rollenspiel.monster:/var/customers/tmp/Anzah:/usr/share/php:/usr/share/php5:/tmp) in /var/customers/webs/Anzah/books.rollenspiel.monster/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:23
Stack trace:
#0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError()
#1 /var/customers/webs/Anzah/books.rollenspiel.monster/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php(23): file_exists()
#2 /var/customers/webs/Anzah/books.rollenspiel.monster/vendor/laravel/framework/src/Illuminate/Translation/FileLoader.php(122): Illuminate\Filesystem\Filesystem->exists()
#3 /var/customers/webs/Anzah/books.rollenspiel.monster/app/Translation/FileLoader.php(23): Illuminate\Translation\FileLoader->loadPath()
#4 /var/customers/webs/Anzah/books.rollenspiel.monster/vendor" while reading response header from upstream, client: <IP_ADDRESS>, server: books.rollenspiel.monster, request: "GET /books/grundregelwerk/page/6-aspekte/revisions/336/changes HTTP/2.0", upstream: "fastcgi://unix:/var/lib/fastcgi/1-anzah-books.rollenspiel.monster-php-fpm.socket:", host: "books.rollenspiel.monster", referrer: "https://books.rollenspiel.monster/books/grundregelwerk/page/6-aspekte/revisions"

Thanks for raising @Tealk.
We did swap out the diff library in the latest release which can affect things.
Looking at your page, I can see there's a lot going on in the HTML code of the content. There are a lot of additional attributes and non-visible elements within the code. Looks like the content may have been created or copied from a platform using the "Slate" editor?
One thing in the code is a large amount of base64 encoded content (About 54KB worth). From my testing, removing just that improves things massively. I've opened (https://github.com/ssddanbrown/HtmlDiff/issues/1) to look into that further but ideally that would not be in your page content.
I'd imagine all the other content in the code is also having an affect here.

Thanks for raising @Tealk.
We did swap out the diff library in the latest release which can affect things.
Looking at your page, I can see there's a lot going on in the HTML code of the content. There are a lot of additional attributes and non-visible elements within the code. Looks like the content may have been created or copied from a platform using the "Slate" editor?
One thing in the code is a large amount of base64 encoded content (About 54KB worth). From my testing, removing just that improves things massively. I've opened (https://github.com/ssddanbrown/HtmlDiff/issues/1) to look into that further but ideally that would not be in your page content.
I'd imagine all the other content in the code is also having an affect here.

How can I remove this?
I copied the texts from a PDF which I created using LaTeX.

How can I remove this?
I copied the texts from a PDF which I created using LaTeX.

@Tealk I can't think of really simple way unfortunately, the editor does some cleaning rules but this content seems to miss detection.
I've created a little cleaner for this here though: https://jsfiddle.net/ssddanbrown/8tf5opda/20/
Just paste the raw HTML content in the ouput and get cleaned stuff in the output, Should have minimal affect on styles and not touch text.
There's a button in the editor toolbar, towards the right to get/set the raw code.

@Tealk I can't think of really simple way unfortunately, the editor does some cleaning rules but this content seems to miss detection.
I've created a little cleaner for this here though: https://jsfiddle.net/ssddanbrown/8tf5opda/20/
Just paste the raw HTML content in the ouput and get cleaned stuff in the output, Should have minimal affect on styles and not touch text.
There's a button in the editor toolbar, towards the right to get/set the raw code.

Thanks for the script, there seems to have been some superfluous code in it
IN: 151052; OUT: 11396; (chars)
IN: 21261; OUT: 8031; (chars)
IN: 77611; OUT: 14238; (chars)
IN: 92279; OUT: 16209; (chars)
IN: 9037; OUT: 1907; (chars)
IN: 105235; OUT: 6908; (chars)

Thanks for the script, there seems to have been some superfluous code in it
IN: 151052; OUT: 11396; (chars)
IN: 21261; OUT: 8031; (chars)
IN: 77611; OUT: 14238; (chars)
IN: 92279; OUT: 16209; (chars)
IN: 9037; OUT: 1907; (chars)
IN: 105235; OUT: 6908; (chars)

Awesome, Gald that helped! Did that get the "Changes" view working? (Might still not be able to see changes between the old and cleaned code, only between two cleaned revisions).
There only donation channel i have is github sponsors (https://github.com/sponsors/ssddanbrown) but it's re-occuring although you could probably cancel right after. It's not needed at all though.

Awesome, Gald that helped! Did that get the "Changes" view working? (Might still not be able to see changes between the old and cleaned code, only between two cleaned revisions).
There only donation channel i have is github sponsors (https://github.com/sponsors/ssddanbrown) but it's re-occuring although you could probably cancel right after. It's not needed at all though.

Yes the changes can be seen only from the corrected version.
this is a very good project and your commitment to solve my problem is also wonderful, something like this deserves support

Yes the changes can be seen only from the corrected version.
this is a very good project and your commitment to solve my problem is also wonderful, something like this deserves support

Thanks @Tealk,
I've now dived into the diffing library and found the biggest point of slowdown, which would have originally led you a white screen.
Changes in https://github.com/ssddanbrown/HtmlDiff/commit/73f41bd4d23b1b9e3860aeaefdddd212c580f2ed should speed things up by 20x from my testing, maybe more/less depending on content.
This updated version of the library is now in the main branch, ready to be part of the next feature release so I will close this off.

Thanks @Tealk,
I've now dived into the diffing library and found the biggest point of slowdown, which would have originally led you a white screen.
Changes in https://github.com/ssddanbrown/HtmlDiff/commit/73f41bd4d23b1b9e3860aeaefdddd212c580f2ed should speed things up by 20x from my testing, maybe more/less depending on content.
This updated version of the library is now in the main branch, ready to be part of the next feature release so I will close this off.


feat(SP-2457): using mirrored gitleaks container when possible

Because are were being rate limited by Docker let's use the mirrored version of zricethezav/gitleaks when possible (i.e. running in a private Github runner).
Wait until we've synchronized the mirror.

:tada: This PR is included in version 1.27.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Check for error responses from elasticsearch

I ran into an issue where we were getting 401 responses back from elasticsearch because of the issue in #155. These were getting swallowed though so that it looked as though everything was ok but that no results were found.
Not sure is this is an ideal way of dealing with this though.

Not sure about this way as well. But besides that: I'm not sure what happened actually, because as far as I can see (haven't tried to reproduce yet), elasticsearch client already throws exceptions and we only catch the 404's.

Will take another look, the elasticsearch client is not throwing an exception, so may well be a bug with that.

@richardmiller Did you manage to find anything?

Will close as I think this is an issue in the elasticsearch client


feat: Stale GitHub Action for PR's older than 50 days

Pull Request Template
Description
A new GitHub action is added. That will scan all the PRs and mark those PRs which have had no activity for the past 50 days. It will also mark the issues as stale based on the days that passed.
Fixes #550
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue).
[x] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] This change requires a documentation update.

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.
[x] I have added corresponding tests.
[x] Any dependent changes have been merged and published in downstream modules.

The error is not relevant to the code. input: feat: Stale PR github action It is giving an error because I have used a capital letters in my commit messages.

I have read the CLA Document and I hereby sign the CLA

@SanjaySinghRajpoot you can soft reset and commit again following the conventional commit, try cz c. Also, please sign the CLA by making the comment.

This is not working. I tried to change the name of the commits but they are not getting updated.

We're currently not able to meet a 30 days TAT for issues and PRs, however, we want to make sure we address all of those at least once. This would make more sense once we have bigger team and better process in place. Thanks for the PR.


Updating gemfile, but the gem being installed is not changed

Hi,
I am attemting to change my gemfile from:
gem 'rspec-rails', '~> 3.6

to
gem 'rspec-rails', '~> 3.5', '>= 3.5.2'

I have removed everything such as the volumes and the cached images but nothing seems to work.
I am also running
docker-compose up --build

Could this be a bug?

I just removed  '>= 3.5.2' from the end and it looks like it's done the trick, apologies my mistake!

When installing new gems docker-compose up --build is all you'll ever have to do.
~> 3.5 will install the latest 3.5.x release.
Typically that's a safe play. If you wanted 3.5.2 exactly you could change it to just ~> 3.5.2.

Thanks very much for the clarification I completely mis-interpreted the '>= 3.5.2', I didn't realise it would install 3.6! (it's not my day today!)
I am copying the lines from rubygems  I feel this isn't something they used to do? Or It's just never caused me a problem before!

There is an example of using a gem range in the Gemfile.
gem 'listen', '>= 3.0.5', '< 3.2'
That will make sure you always get a version in between those 2 ranges.
But in your case, it sounds like you want some variant of 3.5 so ~> 3.5 works perfectly.


Design and Develop a Footer Component

Pull Request Details:

Title: Design and Develop a Footer Component
PR Link: #2
Issue: #1

Next Steps:
I'm ready for feedback and any necessary revisions. Please review at your earliest convenience, and feel free to provide comments or suggest improvements.
Thank you for your time and consideration!

Hi Divya,
Thank you for your pull request. I appreciate your contribution to our project.
I have reviewed your changes and everything looks good. Please be patient, and I'll get back to you as soon as possible.
If you have any questions or need further assistance, don't hesitate to ask.
Best regards,
User


New arguments, --bytes and --largest

-b / --bytes
allows you to filter the results by keys that are greater than or equal to the supplied value
-l / --largest
allows you to only return the top N keys where N is the supplied value

https://github.com/sripathikrishnan/redis-rdb-tools/pull/35 #


Idea: Have a region property on LavalinkNode for sorting.

What about a function where we can we enter a region like "eu" and it will pick the best eu feature.
Or just a variable we can put on the node like "eu" or "us" so we can do a filter?

I'll think about it

what about a extra parm within player with {} in it so we can leave extra data inside like shuffle etc?

@Dream-cake could you elaborate?

Example the state variable in player but instead have an extra one named extra where the user can store extra dataa.
{
...
state: {volume: 0, ...},
extra: {}
}

also this extra could be used for nodes to store extra data about them like region etc

The state idea wont happen, thats not what state is used for. its actually something lavalink sends over and I just add the volume to it, As i needed somewhere to set it

I'm pretty sure he isn't talking about modifying state, but adding an extra on the same level instead, so we can store metadata about the node

I agree, a state implies something temporary, which a region wouldn't fit into.

May I suggest using the id property?
if there is a good reason why that doesn't work, I'll add a region property.

I could see a use case in large bots where nodes are dynamically created and destroyed by a load balancer when required, and an ID could just be a numerical value, or something random, and so that could not be relied on, the region however, would be the same

@BennyDiscord Feel free to pr it,

This is now available in #52


./ROUGE-1.5.5.pl: Permission denied

I run the code in GPU server,but when run the rouge to value the result ,the error come out:
/bin/sh: 1: ./ROUGE-1.5.5.pl: Permission denied

Do you know what happen? I cann't solve  it .

@panpan197
Hello,
Have you solved this problem? I ran this model on Colab and met the similar problem with you, which is "./ROUGE-1.5.5.pl: not found". I am trying to build rouge environment and re-run it again. Thank you .

@panpan197
You should run "chmod 777 ROUGE-1.5.5.pl" before running train.py.

@panpan197 You should run "chmod 777 ROUGE-1.5.5.pl" before running train.py.

I am using Windows, I want to know wherther can this code run on windows or merely on Linux?


[WIP] update scripts for dandi deployment

ansible scripts for jupyterhub deployment

this has been moved over to https://github.com/dandi/dandihub


Create the Login page

The login page should allow the user to sign in using either a username and password or a third-party service like Google or Facebook. It should also include a link to the register page if the user does not have an existing account.
Create a form for users to sign in using a username and password. Also include buttons that can redirect users to log in using a third-party service if they choose. Remember to add functionality to the login endpoint to hash the incoming password in order to compare it correctly to the one on file.