Can't import the named export on valtio 1.1.1

I have found bugs while upgrade valtio 1.1.1. And the problem is solved while I downgrade to 1.1.0
ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 88:23-41
Can't import the named export 'affectedToPathList' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 133:9-20
Can't import the named export 'createProxy' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 95:73-83
Can't import the named export 'getVersion' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 110:57-66
Can't import the named export 'isChanged' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 120:35-44
Can't import the named export 'isChanged' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 106:50-58
Can't import the named export 'snapshot' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 117:25-33
Can't import the named export 'snapshot' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 128:71-79
Can't import the named export 'snapshot' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 116:48-57
Can't import the named export 'subscribe' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 116:14-25
Can't import the named export 'useCallback' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 90:2-15
Can't import the named export 'useDebugValue' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 44:2-11
Can't import the named export 'useEffect' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 84:42-51
Can't import the named export 'useEffect' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 87:2-11
Can't import the named export 'useEffect' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 84:54-69
Can't import the named export 'useLayoutEffect' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 132:21-28
Can't import the named export 'useMemo' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 100:22-32
Can't import the named export 'useReducer' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 13:22-28
Can't import the named export 'useRef' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 86:19-25
Can't import the named export 'useRef' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 102:23-29
Can't import the named export 'useRef' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 103:23-29
Can't import the named export 'useRef' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 104:23-29
Can't import the named export 'useRef' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 15:28-36
Can't import the named export 'useState' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 4:0-77
Can't reexport the named export 'getVersion' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 4:0-77
Can't reexport the named export 'proxy' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 4:0-77
Can't reexport the named export 'ref' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 4:0-77
Can't reexport the named export 'snapshot' from non EcmaScript module (only default export is available)

ERROR in /Volumes/External/Workspace/project/node_modules/valtio/esm/index.mjs 4:0-77
Can't reexport the named export 'subscribe' from non EcmaScript module (only default export is available)

related #184, @barelyhuman ?

@fortezhuo Hey, could you add in a little more detail about the environment that you are using this in?
Could you answer the following.
Are you using Typescript?
What bundler is this error from?
What nodejs version are you using?

Yes.  I am using typescript
"typescript": "~4.3.2"
"webpack": "^4.44.1",
"webpack-bundle-analyzer": "^3.8.0",
"webpack-cli": "^3.3.12",
"webpack-dev-server": "^3.11.2"
NodeJS : 14.17.3
The error occurs while I try to build my project using webpack at console. So I can't provide codesandbox

@dai-shi long shot but can be due to proxy-compare/ can't confirm though.
@fortezhuo one more thing, can you add in your webpack config ?

I use @expo/webpack-config
base.ts
import fs from "fs"
import dayjs from "dayjs"
import webpack from "webpack"
import TerserPlugin from "terser-webpack-plugin"
import LoadablePlugin from "@loadable/webpack-plugin"
import HtmlWebPackPlugin from "html-webpack-plugin"
import CompressionPlugin from "compression-webpack-plugin"
import MiniCssExtractPlugin from "mini-css-extract-plugin"
import RefreshPlugin from "@pmmmwh/react-refresh-webpack-plugin"
import { resolve } from "path"
import { BundleAnalyzerPlugin } from "webpack-bundle-analyzer"

export const stamp = dayjs().format("YYMMDDHHmm")
export const resolvePath = (path: string) => resolve(appDirectory, path)

const createExpoWebpackConfigAsync = require("@expo/webpack-config")
const WebpackBar = require("webpackbar")
const isDev = process.env.NODE_ENV !== "production"
const isAnalyzer = process.env.ANALYZER === "true"
const appDirectory = fs.realpathSync(process.cwd())

export const extractExpoConfig = async (mode: string) => {
  const {
    module: { rules },
    resolve,
  } = await createExpoWebpackConfigAsync(
    {
      mode,
      babel: {
        dangerouslyAddModulePathsToTranspile: [
          "moti",
          "@motify",
          "@dripsy",
          "@frenxp/core",
        ],
      },
    },
    {}
  )

  return { rules, resolve }
}

export const getWebpackPlugins = (isWeb: boolean) => {
  const plugins = [
    new WebpackBar({
      name: `FRENXP ${isWeb ? "Client" : "Server"}`,
      color: isWeb ? "green" : "red",
      reporters: ["fancy"],
    }),
    new LoadablePlugin(),
    new MiniCssExtractPlugin(),
    new webpack.DefinePlugin({
      __DEV__: JSON.stringify(isDev),
      FREE_STAMP: JSON.stringify(stamp),
      FREE_NODE_ENV: JSON.stringify(isDev ? "development" : "production"),
    }),
  ]

  if (isAnalyzer) {
    plugins.unshift(new BundleAnalyzerPlugin())
  }

  if (isDev) {
    plugins.unshift(new RefreshPlugin())
    plugins.unshift(new webpack.HotModuleReplacementPlugin())
  } else {
    plugins.unshift(new CompressionPlugin())
  }

  if (isWeb) {
    plugins.unshift(
      new HtmlWebPackPlugin({
        template: "assets/web/index.html",
        filename: "./index.html",
      })
    )
  }
  return plugins
}
export const getDefaultConfig = (isWeb: boolean): webpack.Configuration => {
  return {
    optimization:
      isWeb && !isDev
        ? {
            minimize: true,
            minimizer: [
              new TerserPlugin({
                terserOptions: {
                  output: {
                    comments: false,
                  },
                },
              }),
            ],
            splitChunks: {
              minSize: 10000,
              maxSize: 250000,
            },
          }
        : undefined,
    stats: {
      all: false,
      assets: true,
      errors: true,
      warnings: true,
    },
  }
}

development.ts
import {
  getDefaultConfig,
  extractExpoConfig,
  getWebpackPlugins,
  resolvePath,
} from "./base"
import { configProxy } from "@frenxp/env"

const entryClient = resolvePath("entry/mono.js")

const webpackDevConfig = async () => {
  const { resolve, rules } = await extractExpoConfig("development")
  return {
    ...getDefaultConfig(true),
    mode: "development",
    devtool: "source-map",
    watch: true,
    entry: entryClient,
    output: {
      publicPath: `/`,
    },
    module: {
      rules,
    },
    resolve,
    plugins: getWebpackPlugins(true),
    devServer: {
      host: "<IP_ADDRESS>",
      disableHostCheck: true,
      port: 80,
      historyApiFallback: true,
      clientLogLevel: "error",
      contentBase: "./",
      hotOnly: true,
      watchOptions: {
        ignored: ["node_modules"],
        aggregateTimeout: 300,
        poll: 1000,
      },
      proxy: {
        "/api": {
          target: configProxy,
          secure: false,
          changeOrigin: true,
        },
      },
    },
  }
}

export default webpackDevConfig

 "devDependencies": {
    "@babel/core": "~7.14.8",
    "@loadable/babel-plugin": "^5.13.2",
    "@loadable/webpack-plugin": "^5.15.0",
    "@pmmmwh/react-refresh-webpack-plugin": "^0.3.3",
    "@types/compression-webpack-plugin": "^4.0.0",
    "@types/loadable__component": "^5.13.4",
    "@types/loadable__webpack-plugin": "^5.7.3",
    "@types/mini-css-extract-plugin": "^0.9.1",
    "@types/numeral": "^2.0.1",
    "@types/react": "~17.0.14",
    "@types/react-dom": "~17.0.9",
    "@types/react-flatpickr": "^3.8.4",
    "@types/react-native": "~0.63.2",
    "@types/react-table": "^7.7.2",
    "@types/terser-webpack-plugin": "^4.2.0",
    "@types/webpack-bundle-analyzer": "^3.8.0",
    "@types/webpack-node-externals": "^2.5.0",
    "compression-webpack-plugin": "^6.1.1",
    "html-webpack-plugin": "^4.3.0",
    "mini-css-extract-plugin": "^0.11.3",
    "react-refresh": "^0.10.0",
    "terser-webpack-plugin": "^4.2.3",
    "type-fest": "^1.2.3",
    "webpack": "^4.44.1",
    "webpack-bundle-analyzer": "^3.8.0",
    "webpack-cli": "^3.3.12",
    "webpack-dev-server": "^3.11.2",
    "webpack-node-externals": "^3.0.0",
    "webpackbar": "^5.0.0-3"
  },

@fortezhuo cool,
in the above configs, could you replace
module:{
  rules,
}

with
module: {
  rules: [
    ...rules,
    {
      type: "javascript/auto",
      test: /\.mjs$/,
      use: [],
    },
  ],
}

and let me know if that fixes the issue.

Yes.. add that rule fixes the issue..
export const extractExpoConfig = async (mode: string) => {
  const {
    module: { rules },
    resolve,
  } = await createExpoWebpackConfigAsync(
    {
      mode,
      babel: {
        dangerouslyAddModulePathsToTranspile: [
          "moti",
          "@motify",
          "@dripsy",
          "@frenxp/core",
        ],
      },
    },
    {}
  )

  rules.push({
    type: "javascript/auto",
    test: /\.mjs$/,
    use: [],
  })

  return { rules, resolve }
}

@fortezhuo @dai-shi one of you can close the issue.
@dai-shi  we should add this to the docs for webpack 4 configurations

@barelyhuman Thanks for your help.
Just wondered if it helps if we provide esm/index.js along with esm/index.mjs?

@dai-shi should help theoretically but then we'll have to create clones of every submodule we export ?

Reopening this for #197 to close on merge.


x/tools/go/analysis/passes/loopclosure: do not report variable capture for loop variables with the new lifetime rules

This issue tracks support in x/tools/go/analysis/passes/loopclosure for the new loop variable lifetime rules of https://go.dev/issue/60078, available now behind GOEXPERIMENT=loopvar and likely on for language versions >= 1.22.
Marking as a release blocker as this will make cmd/vet would report a large number of false positives due to the new language feature.

Example of a false positive https://go.dev/play/p/WsTuyNr6YnK
package main

import (
	"fmt"
	"sync"
)

func main() {
	const N = 4
	var wg sync.WaitGroup
	for i := 0; i < N; i++ {
		wg.Add(1)
		go func() { defer wg.Done(); fmt.Println(i) }()
	}
	wg.Wait()
}

Playground output for Go 1.21:
./prog.go:13:44: loop variable i captured by func literal

Go vet failed.

4
4
4
4

Program exited.

The dev currently branch implements the https://go.dev/issue/60078 loop lifetimes. So go vet should not continue to report on this example after 1.22.

Note this will need to support packages with a mixture of lifetimes in different files or files without //go: version declared in the files (like the playground example). See #62605 for a potential solution via go/types.

Fixed by https://go.dev/cl/c/go/+/543975

I still see this issue with 1.22.0:
$ go version
go version go1.22.0 linux/amd64

$ grep go go.mod
go 1.22.0

$ cat main.go
package main

func main() {
	for i := range 10 {
		go func() { println(i) }()
	}
}

$ go vet main.go
./main.go:5:23: loop variable i captured by func literal

@alexaandru Thank you for the report. I opened #65612. Looks like a plumbing issue when running vet on files listed on the command line. You can either invoke vet differently, suppress the finding (add _ = i at the end of the loop) or follow along on the new bug for a fix. If you have any more questions please ask them on #65612.


Test hung with snRuntime-rtl-snRuntime-rtl-tls

Dear spatz team,
I followed the instructions and compiled the platform on Unbuntu 22.04 without seeing any obvious error.
However when I run "make sw.test.vlt", the test hung at the following position for 1 hour.
cd sw/build && make test
make[1]: Entering directory '/home/kevin/works/spatz/hw/system/spatz_cluster/sw/build'
Running tests...
Test project /home/kevin/works/spatz/hw/system/spatz_cluster/sw/build
      Start  1: snRuntime-rtl-snRuntime-rtl-tls

I very much appreciate it if you could provide tips to fix this issue.
Best regards .
Kevin

I encountered the same issue, but I noticed there was an error when compiling the software
error: address range table at offset 0x0 has a premature terminator entry at offset 0x10
[ 16%] Linking C static library libdp-fconv2d.a
make[3]: Leaving directory '/spatz/hw/system/spatz_cluster/sw/build'
[ 16%] Built target snRuntime-cluster

not sure if this is related

There was an issue with the runtime. I solved it with #6, thanks for reporting the issue!


Thoughts on global SSR components?

This is more of a general question, not an issue.
I'm currently working on implementing next-iron-session in my project. (thanks for the work btw it came at a perfect time for me) I see there is an SSR example for a single user-profile page, which I think works great, but I'm wondering what anyone's thoughts are on more global or site-wide SSR solutions.
We have an application layout being rendered in our custom _app.js page that includes some need for data stored in the session. Simple things like the application header showing "Welcome, XYZ"  vs "Sign in"
Right now in order to accomplish this, I'm using something similar to the useUser hook. But on hard-refreshes the initial page is loaded as if there is no user logged in, then once the data is returned from the API it updates the page to reflect a logged-in user's view.
One approach (though I have no idea if it's a good one) that I've used in the past to take advantage of next-redux-wrapper and basically initialize the redux app state with data from req. Then read all the session data from redux. I had various issues with this approach around keeping the redux store and the actual session itself in-sync for changes.
I'm wondering if that is a "valid" approach, or if there is a better solution that you've found to avoid the redux stuff?

Right now in order to accomplish this, I'm using something similar to the useUser hook. But on hard-refreshes the initial page is loaded as if there is no user logged in, then once the data is returned from the API it updates the page to reflect a logged-in user's view.

To solve that you either have to:

Use SSR, which can be less performant than static generation in Next.js (code will run for every customer request)
Use a generic wording like "Your dashboard" (not per user) and when you click on it it goes to an API route like /api/login. If the cookie is present then you log the user in, otherwise you present them the login/signup page.
Hide/show loader on the "login" text until you get the customer details

I am a fan of static generation so I am really fine with a text that turns from "login" to "welcome X", I don't think that's a big deal at all UI wise.
If you really want the server-side to already recognizes the user and send immediately the right data, then you have to use the SSR way (getServerSideProps) on every page OR you could try to use getServerSideProps or getInitialProps on the _app file directly like shown here: https://nextjs.org/docs/advanced-features/custom-app
And then forward the user data in the pageProps of every page.
I hope this helps. (My personal advice, go with static generation and use loaders, its fine)

Thanks, @vvo! You're totally right. I spent some more time on this and ended up just following your advice and not worrying so much about it.
Thanks again for the great library.


Issue 453: Update the version for ahash

Change log description
Update the ahash version to 0.8.6
Purpose of the change
Fixes #453
What the code does
Update ahash verion to 0.8.6
How to verify it
All tests should pass

Codecov Report

Merging #454 (9b5dc6f) into master (3a9434f) will decrease coverage by 8.73%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #454      +/-   ##
==========================================
- Coverage   72.74%   64.01%   -8.73%
==========================================
  Files          48       48
  Lines       12345    11761     -584
  Branches    12345    11761     -584
==========================================
- Hits         8980     7529    -1451
- Misses       3365     4232     +867

see 22 files with indirect coverage changes

ahash dependency is being used in only one Cargo.toml file.


Improve information architecture of our docs

Does the current structure of pages make sense right now? Probably not, it accreted over time, without much thought to what a sensible organization might be. A lot of the names of subpages are confusing, and relevant information on similar topics is scattered across a number of different pages. For instance, information about setting up Snowflake can be found here, here, and here.
Let's think about how we can reorganize the pages and the content therein to make it easier to navigate.

@JamesSLogan will drive this one but can reach out to @britt-allen for review.


Cursor disappears on forward-delete

Gif is better to explain.

In words, when using forward delete (fn-backspace for example), the cursor disappear until it is moved.

This is weird. What terminal application are you using?
gnome-terminal and xterm don't seem to have the issue.

iTerm2, OS X, Build 2.9.20160510

iTerm2, OS X, Build 2.9.20160510

Ouh, i just realised it's a date: 2016-05-10. And it's the latest non-nightly.

Hi @Carreau,
I'm closing this issue. I haven't heard of anyone else that had the same issue, and I don't believe I could reproduce it. Feel free to open again, if you think it's still the case.


Add support for deprecated/obsolete identifiers

We've had a bunch of requests for deprecated or obsolete terms in Babel:

https://github.com/TranslatorSRI/NodeNormalization/issues/17
https://github.com/TranslatorSRI/NodeNormalization/issues/264
https://github.com/TranslatorSRI/Babel/issues/25
https://github.com/TranslatorSRI/Babel/issues/70
https://github.com/TranslatorSRI/Babel/issues/71
https://github.com/TranslatorSRI/Babel/issues/84
https://github.com/TranslatorSRI/Babel/issues/160
https://github.com/TranslatorSRI/Babel/issues/177
https://github.com/TranslatorSRI/Babel/issues/241
https://github.com/TranslatorSRI/Babel/issues/243

Note that in some cases (e.g. MONDO) deprecated terms can point to a non-deprecated term that replaces them, while in other cases (e.g. UMLS) there does not appear to be a clear mapping to a non-deprecated term.
Should we add deprecated terms to Babel? If we do that, we will need to mark them in some way so that we can ensure (1) that deprecated terms are never used as the primary identifier of a clique, and (2) so that NodeNorm and NameRes can warn users not to use deprecated terms.
This issue is to discuss whether this would be useful, what changes would be necessary in NodeNorm and NameRes to support them, and how we should go about including them.

Note that in some cases (e.g. MONDO) deprecated terms can point to a non-deprecated term that replaces them, while in other cases (e.g. UMLS) there does not appear to be a clear mapping to a non-deprecated term.

Not just MONDO, but any OBO ontology commits to never deleting IDs. It's not always possible to specify a replacement of course.
https://incatools.github.io/ontology-access-kit/guide/obsoletion.html


Update Logging Approach

The logging approach used in secure-smtpd should be updated so that it's easier to filter on specific log levels.

Logging can now properly be configured. see 2314293


Hub SSOT - Implementation Strategy

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/219
Originally created by @pnadolny13 on 2022-03-24 13:31:16

There are lots of moving parts for getting the Hub to act as the SSOT for Meltano. We need to decide on an implementation strategy so the timing works out and we have a smooth migration.
Things like:

a new API endpoint for serving discovery data
transitioning Meltano to consume from the hub vs a discovery data
a new plugin schema that all plugins can conform to plugin.yml
updating the hub Singer metadata files to conform to a new plugin.yml
updating the hub front end when the file format and organization changes
probably a lot more too..

@aaronsteers wdyt?

View 21 previous comments from the original issue on GitLab


Appstudio update test-component-pac-lzbz

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-lzbz-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
1 minute
sast-snyk-check

✅ Succeeded
23 seconds
build-container

✅ Succeeded
36 seconds
inspect-image

✅ Succeeded
36 seconds
deprecated-base-image-check

✅ Succeeded
40 seconds
clamav-scan

✅ Succeeded
1 minute
clair-scan

✅ Succeeded
18 seconds
sbom-json-check

✅ Succeeded
6 seconds
show-summary

✅ Succeeded
5 seconds
show-sbom

Pipelines as Code CI/test-component-pac-lzbz-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
27 seconds
build-container

✅ Succeeded
8 seconds
sast-snyk-check

✅ Succeeded
26 seconds
inspect-image

✅ Succeeded
26 seconds
deprecated-base-image-check

✅ Succeeded
14 seconds
clair-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
41 seconds
clamav-scan

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


New version: Circuitscape v5.5.5

Registering package: Circuitscape
Repository: https://github.com/Circuitscape/Circuitscape.jl
Created by: @ranjanan
Version: v5.5.5
Commit: 2fe4517f4e811d3074fd6fe214413350445d41de
Reviewed by: @ranjanan
Reference: https://github.com/Circuitscape/Circuitscape.jl/commit/2fe4517f4e811d3074fd6fe214413350445d41de#commitcomment-36199550

There's a bit of an urgency to merge this. The upper bounds will be added in a few days by @ranjanan


Tf independent download of dataset in data_download.py

This branch is created from https://github.com/mlperf/reference/pull/77 hence diff shows changes from both. I have not made changes independently since the dead code used lot of tf based apis

@ddkang download log link for this PR

@tremblerz  can you rebase please?

@ddkang done.

@deepakn94 can you approve this pull request?


Fix typo in README

Linked Issue:

Checklist:

[ ] Is the linter reporting 0 errors?
[ ] Did you comply with our styleguide?
[ ] Is there adequate test coverage for your new code?
[ ] Does the CI pipeline pass?
[ ] Is the static analysis tool reporting 0 issues?
[x] Did you update the documentation?
[ ] Did you update the sample app?
[ ] Do we need to increment the minor/major version?
[ ] Did you change the public API?
[ ] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

If Applicable:

[ ] Did you test when the first item is skipped?
[ ] Did you test when the last item is skipped?
[ ] Did you test when middle items are skipped?
[ ] Did you test when incorrect data is passed forward?
[ ] Did you test proceeding backwards?

If Public API Has Changed:

[ ] Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
[ ] Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
[ ] If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

Thank you for the email @pg !
@cla-bot check

I am merging without the sonar scan results because this is documentation only.  For the sonar_scan failure I've created an Issue to track #20
Thanks, @pg for exercising our pipeline and the documentation fix!


Implemented filtering by repository on my tickets page

OK, I think I got it right now. Pulled develop, then merged my ticket-57 changes on top of it.

Aside from the little comments I made we have two larger problems.  One is easily fixable.  The other.... not sure.

You can't search by the repository name.  It's problematic because of punctuation marks, slashes, etc.  Instead we must specify and search for the rid which is a hash of the repository name.  So everywhere you specify a repository name value it must be the rid instead.  RepositoryModel.getRID() will give you this value.

We have a scaling problem.  I have 50+ repos in my test environment.  This generates a lengthy dropdown menu which scrolls offscreen.  And it really won't scale for those with hundreds or thousands of repos so we need a better plan.  The bootstap in-use is really old and we don't have scrollable dropdown menus.  :(  I think we need to list only the repos that are in the infiltered My Tickets resultset.  That means we need to execute two Lucene queries.  Hopefully the performance impact will be minor compared to the entire page-loading cycle.

@James, re-submitted with changes based on your code review. Also changed the repository options to constrain to those relevant to the user's watched tickets.
(Sorry about the changes of tabs to spaces, please ignore white-space differences when you compare.)

Good work.  We are very close now and this will be a nice usability improvement.

@gitblit These changes should be it. If no more review comments, I'll proceed with fixing the mentions bug, err, mentioned above.

Thanks Eddy!  Merged.

A pleasure. I'd really like to look into implementing tickets across groups. Is that on the roadmap for 1.7.0? Otherwise, I can pick another 1.7.0 item.

Tickets are intricately tied to repositories.  It would take some heroic changes (i.e. likely not mergeable) to accommodate  that.
If you really wanted to explore that I would suggest implementing some sort of ticket-container object with it's own persistence mechanism and UI.  Maybe this could be a plugin but I haven't spent more than 30 seconds thinking about this so maybe that is a dumb idea.  ;)

Hmm. I forgot about the integration of tickets within repositories, but your idea of a “repository group ticket service” is worth pursuing. I’ll think about that a bit more this week-end.
From: James Moger<EMAIL_ADDRESS>Sent: 27 May 2015 22:18
To: gitblit/gitblit
Cc: Eddy Young
Subject: Re: [gitblit] Implemented filtering by repository on my tickets page (#259)
Tickets are intricately tied to repositories. It would take some heroic changes (i.e. likely not mergeable) to accommodate that.
If you really wanted to explore that I would suggest implementing some sort of ticket-container object with it's own persistence mechanism and UI. Maybe this could be a plugin but I haven't spent more than 30 seconds thinking about this so maybe that is a dumb idea. ;)
—
Reply to this email directly or view it on GitHub https://github.com/gitblit/gitblit/pull/259#issuecomment-106081914 .  https://github.com/notifications/beacon/AAEGeQ7SfcrFMsr3E7Ox_AOTwonZBlYoks5oNiwFgaJpZM4Eg_wa.gif


docs: wip integrating entity secure channel with streams

WIP source for Secure Channels via Hub, using Entities.
This code builds, but when the Stream is initiated, a panic is received in the initiator. There may also be problems when host names are used for hub node routes, I think i saw a different class of error there.
Responder output
Jul 30 11:03:05.579  INFO ockam_node::node: Initializing ockam node
Jul 30 11:03:05.581  INFO ockam_vault::software_vault: Creating vault
Jul 30 11:03:05.589  INFO ockam_channel::secure_channel: Starting SecureChannel listener at 0#4d8f051ffd1e2509a0fc088b9084d555
Jul 30 11:03:05.589  INFO ockam::stream::consumer: Initialising stream consumer 0#035f1f078951adb750b91fc83453ec01
Jul 30 11:03:07.155  INFO ockam::stream::consumer: Initialised consumer for stream 'sc-initiator-to-responder' and route: 1#<IP_ADDRESS>:4000 => 0#61810b3006cee1ea
Jul 30 11:03:08.104  INFO ockam::stream::producer: Initialised consumer for stream 'sc-responder-to-initiator' and route: 1#<IP_ADDRESS>:4000 => 0#78acf013dc511ecf
Jul 30 11:03:08.789  INFO ockam::stream::consumer: Updating index 'sc-initiator-to-responder' to: 5
Jul 30 11:03:09.049  INFO ockam::stream::consumer: Forwarding sc-initiator-to-responder message to addr: 0#secure_channel_listener
Jul 30 11:03:16.941  INFO ockam::stream::consumer: Forwarding sc-initiator-to-responder message to addr: 0#secure_channel_listener
Jul 30 11:03:17.256  INFO ockam::stream::consumer: Forwarding sc-initiator-to-responder message to addr: 0#secure_channel_listener

Process finished with exit code 130 (interrupted by signal 2: SIGINT)

Initiator output
Jul 30 11:03:14.566  INFO ockam_node::node: Initializing ockam node
Jul 30 11:03:14.568  INFO ockam_vault::software_vault: Creating vault
Jul 30 11:03:14.574  INFO ockam::stream::consumer: Initialising stream consumer 0#e49841a09199e460c8a17e7e2abf02d6
Jul 30 11:03:15.633  INFO ockam::stream::consumer: Initialised consumer for stream 'sc-responder-to-initiator' and route: 1#<IP_ADDRESS>:4000 => 0#78acf013dc511ecf
Jul 30 11:03:15.780  INFO ockam::stream::consumer: Updating index 'sc-responder-to-initiator' to: 4
Jul 30 11:03:16.072  INFO ockam::stream::consumer: Forwarding sc-responder-to-initiator message to addr: 0#bbd9ff9ced5aa0e88f87b33d85b886b9
Jul 30 11:03:16.072 ERROR ockam::stream::consumer: Failed forwarding stream message: Error { code: 11004, domain: "OCKAM_NODE" }
Jul 30 11:03:16.306  INFO ockam::stream::consumer: Forwarding sc-responder-to-initiator message to addr: 0#bbd9ff9ced5aa0e88f87b33d85b886b9
Jul 30 11:03:16.307 ERROR ockam::stream::consumer: Failed forwarding stream message: Error { code: 11004, domain: "OCKAM_NODE" }
Jul 30 11:03:16.592  INFO ockam::stream::producer: Initialised consumer for stream 'sc-initiator-to-responder' and route: 1#<IP_ADDRESS>:4000 => 0#61810b3006cee1ea
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Error { code: 11011, domain: "OCKAM_NODE" }',

Hey folks,
While integrating Streams to use Entities, I'm hitting this. Have not dug deeply yet, but please have this on your radar. If I have a chance to debug further today I'll leave notes here

Also ran into this earlier today with example 15. Don't get it when I'm running against local hub and local Kafka.

Sounds like something more to do with routing and transports perhaps than Entities and SC, then

I've seen something similar when playing with rust workers. Maybe it's not related, but error 11011 is a timeout and because default timeout is relatively small some workers were terminating and then returning error 11004.
What I did in the end is to increase the timeout, but to debug this issue I've added logs to this line: https://github.com/ockam-network/ockam/blob/develop/implementations/rust/ockam/ockam_node/src/error.rs#L50
I couldn't figure out how to log the timeout reason though.
Some errors swallow important information, we could add at least debug log there.

Could someone point what should I run to check this?

After investigating this and a single-page kafka examples, the issue seems to be the timeouts when handling streams with secure channels.
When running secure channel with stream examples with higher latencies streams (e.g. using cloud nodes), there are following errors reported by the examples:
Error { code: 11011, domain: "OCKAM_NODE" } - regular tokio timeout
Error { code: 12009, domain: "OCKAM_VAULT" } - encryption failure
Former happens with higher latencies, latter with relatively low ones (around 200ms).
Around 400ms added latency, I start to see 11011.
Maybe we can adjust some timeouts to fix that.
I was using a local Elixir node with the following changes to reproduce the latency: https://gist.github.com/hairyhum/464409c1d3619223ef2785f884bde56a
And running the local Hub with SERVICES_CONFIG_SOURCE=list SERVICES_LIST=stream,stream_index iex -S mix
Lines from the diff with :timer.sleep can be used to adjust the latency

Very outdated branch, recreating


Can't register a Request.macro from Provider?

Brief
As mentioned here I am trying to normalize some keys from querystring in purpose for easier data filtering on the Model but I got an error from inside macro closure.
From the error stack below, I'm pretty sure that it's happened because this inside the closure doesn't actually got instance of Request, am I right? But, the inspection tell me otherwise. 😕
Not sure if it was a bug but it bother me so bad 😅

Why is this could happened?
Where is the best place to register Request.macro?

Sample Code
// ~/app/Models/SomeModel.js
class SomeModel extends Model {
  static scopeFilters (query, filters) {
    for (const load of (filters.with)) {
      query.with(relation)
    }

    // some other stuffs

    return query
  }
}

// ~/app/Controllers/Http/SomeController.js (usage)
class SomeController {
  async index ({ request }) {
    const filters = request.filters()

    filters.includes('brand', 'category')

    const method = filters.page > 0 ? 'paginate' : 'fetch'

    const model = await Model.query()
      .filters(filters)[method](filters.page)

    return model
  }
}

// ~/providers/Base/Provider.js
class BaseProvider extends ServiceProvider {
  register () {
    const Request = this.app.use('Adonis/Src/Request')

    Request.macro('filters', () => {
      const query = this.get()

      return {
        with: query.with || [],
        page: query.page > 0 ? query.page : 0,
        sort: query.sort ? sanitize(query.sort) : {},
        search: query.search ? sanitize(query.search) : {},
        includes (...params) {
          this.with = query.includes || params
        }
      }
    })
  }
}

Error Stack (if any)
TypeError: this.get is not a function
    at Request.macro [as filters] ([d:\Workspaces\personal\codes\adonan]\providers\Base\Provider.js:24:27)
    at ItemsController.index ([d:\Workspaces\personal\codes\adonan]\app\Controllers\Http\ItemsController.js:7:30)
    at Server._routeHandler ([d:\Workspaces\personal\codes\adonan]\node_modules\@adonisjs\framework\src\Server\index.js:326:32)
    at Server._resolveMiddleware ([d:\Workspaces\personal\codes\adonan]\node_modules\@adonisjs\framework\src\Server\index.js:216:29)
    at Runnable._invoke ([d:\Workspaces\personal\codes\adonan]\node_modules\co-compose\src\Runnable.js:76:43)
    at once ([d:\Workspaces\personal\codes\adonan]\node_modules\co-compose\src\Runnable.js:73:35)
    at f ([d:\Workspaces\personal\codes\adonan]\node_modules\once\once.js:25:26)
    at Auth.handle ([d:\Workspaces\personal\codes\adonan]\node_modules\@adonisjs\auth\src\Middleware\Auth.js:113:12)
    at <anonymous>

Screenshots

Thanks & regards.
Sorry for my bad english 🥂

Hey @feryardiant! 👋
Since you are using an arrow function you are sharing the scope of the parent.
Use a normal function and everything should be fine.

Thanks for quick reply @RomainLanz and yes you're right.
Seem's I have to reopen this book tho 😅


port over better stemming support

so an instance of "breads" comes up when you search "bread"
and an instance of "bread" comes up when you search "breads"
that's https://github.com/newsdev/stevedore-jruby/commit/9737749fead25ce42b33c2b3d244a89e7b7646c3 and https://github.com/newsdev/beerbelly/commit/e81fe27e2a0101dd33d159acf8924a1ea694f6e0 in my various closed-source repos...

and port over alias support too, from https://github.com/newsdev/beerbelly/commit/1ba54d7cdb674935aad1a3a3f204adcc7ae7713b


#1667 Fix watcher for Kubernetes resources

The v6 KubernetesClient library changed the implementation of the watcher - see https://github.com/kubernetes-client/csharp/pull/681.
This change updates the AnyResourceKind.ListClusterAnyResourceKindWithHttpMessagesAsync() method to match the change in the KubernetesClient library.
Unfortunately, the LineSeparatedHttpContent class in the KubernetesClient library is inaccessible to us (internal), so has been duplicated here. This change then required the addition of the HttpOperationResponseExtensions.CustomWatch() extension method to ensure the correct stream reader was created.

@MihaZupan The KubernetesClient library doesn't really make it easy to have a generics-based solution, which probably explains why AnyResourceKind was created in the first place.
Here's an alternative potential fix that removes the need for AnyResourceKind, which would make library upgrades easier going forward. Keen to get your thoughts on which approach you'd prefer.
https://github.com/dpbevin/reverse-proxy/commit/c6641096663eea2f539481009ef27f1016cebcb5

Trying to understand the difference here:
Previously we had our own logic for dealing with arbitrary resources (ResourceKinds).
Since KubernetesClient provides out-of-the-box helpers for all the resources we care about, we are simplifying the logic to just use the helpers instead (e.g. ListIngressClassWithHttpMessagesAsync, ListPodForAllNamespacesWithHttpMessagesAsync).
I'm not sure I understand what the downsides are. Is it that the OperatorFramework can't be used with different resource kinds in this case (which is fine if we're removing it as a dedicated library anyway)?
Especially if you believe it will make future upgrades easier, I prefer the alternative approach.

@MihaZupan I think you've captured it well.
The only downside is probably not a valid scenario anymore considering the removal of the OperatorFramework. Introducing concrete classes for resource specific informers (e.g. V1IngressResourceInformer) would not be practical for a generic library. However, because we are moving to being a specific purpose, we only need a small, known set of informers. So I agree that the removal of genetics is fine in this case.
The only question now is which order to do the two PRs I have open in. Going with the type-specific resource informers will be easier after the library is collapsed into a single project.

Going with the type-specific resource informers will be easier after the library is collapsed into a single project.

If that means less work for you, that's fine by me.

Going with the type-specific resource informers will be easier after the library is collapsed into a single project.

If that means less work for you, that's fine by me.

It certainly does. My preferred sequence would be:

Complete https://github.com/microsoft/reverse-proxy/pull/1642
Abandon this PR https://github.com/microsoft/reverse-proxy/pull/1668
Fix #1667 with a new PR based off https://github.com/dpbevin/reverse-proxy/commit/c6641096663eea2f539481009ef27f1016cebcb5

If 1. is going to take a while that I'd prefer not to leave the library in a broken state, in which case I would suggest:

Complete this PR
Complete https://github.com/microsoft/reverse-proxy/pull/1642 (after fixing merge conflict that this PR will cause)
Improve this fix by reworking main based off https://github.com/dpbevin/reverse-proxy/commit/c6641096663eea2f539481009ef27f1016cebcb5

Closing in favour of https://github.com/microsoft/reverse-proxy/pull/1706


docs(spec): north star spec reporting

Surfacing this type of information isn't dependent on a monorepo, but that would make the reporting a lot easier (wouldn't have to have CI PR into the reporting repo). Concepts from monorepo re-architecting that are included: "add-ons" are now called "community components", every component is independently published, but there are also published packages for each framework as a whole.
Demo
This PR demonstrates what a dynamic component status page could look like, with one example of a detailed component view (button). All content is fictional. This is meant to facilitate discussion around a reporting north star.
https://github.com/carbon-design-system/carbon-spec/blob/ffea894324da8f3a993319e98a4bd652e8145a15/docs/component-status.md
https://github.com/carbon-design-system/carbon-spec/blob/ffea894324da8f3a993319e98a4bd652e8145a15/docs/components/button.md
Assumptions
This assumes that each component has a specification, that includes:

Written requirements that describe behavior for every user type (general, keyboard-only, screen reader, etc.)
Tests that can be ran on each implementation verifying expected behavior, DOM structure, element types, attributes (pertaining to accessibility), and content

There's also be separate documentation on "what it takes to be a component" which includes how to author your component's spec and maintain it over time.
Scenarios
Questions that we want a "component status" page to answer:

What framework packages and component packages are available?
Is this component available in framework X?
Is this component fully available in framework X (including all the variants, states, modifiers that I need)?
How accessible is each component?
Who maintains each framework and/or component?
Which framework and/or component is used the most?
Which components are new this release?
Which components are deprecated this release?
Which components are not stable (a.k.a. experimental)?
Where are there contribution opportunities to either improve existing components, create missing components, or make something more accessible through the spec?

Implementation considerations
downloads and npm badge content is dynamic - those SVGs coming directly from NPM. It'd be great to include dynamic badges for commit activity | 457/month or last commit | today or release date | april 2018, but those badges hit the GitHub API which is per repository. With one monorepo, that's not possible per component package. We could possibly generate that during our build by looking at commit history and file modified dates per component directory... but may not be worth the trouble.
Outstanding questions

More related to monorepo in general, but how do we handle breaking changes with community components when something higher-order (utility functions, helper Sass) causes the breaking changes?
Related to that, do we have a third group of components called "sunset components" or something once the next major release and previously deprecated items are no longer supported? Or do we purge those components and somebody would have to revert to a previous release in the repo to find that sunset source?
How do we show exactly what failed or is throwing warnings in the spec test reporting? Or do we keep it simple and expose such information when locally running the spec tests?
How can we provide contribution short cuts to improve spec adherence? Or like above, you locally run the spec tests to identify specifics?
Is there a better way to sort the core and community components besides alphabetically? We don't have NPM usage stats at build when the markdown page is generated, so alphabetical may be our only option.
For each component, for each framework, how do we link to a demo environment like Storybook? Would we be able to deep link to a specific variant/state/modifier or just to the default component?

This looks really great 👍 I'll echo that it's not super clear what "spec 1"/"spec 9" refers to in the component sample (maybe "n passed"/"n warning"/"n errored" instead?), but the overall layout looks solid.

Is there a better way to sort the core and community components besides alphabetically? We don't have NPM usage stats at build when the markdown page is generated, so alphabetical may be our only option.

Alphabetical is definitely easiest for finding components in the absence of filtering. If the status is consumed by some other tool sorting a filtering would be awesome additions.


Instance feedback for Soundcraft Ui Series

Hi everyone,
It would be great if there would be a feedback instance for at least the muting state of the channels.
numeric feedback for fader level would be a plus

Can somebody show a good example implementation of how we can set instance feedback?

Seems like these guys have made feedback work on the quite similar Behringer x32
https://github.com/bitfocus/companion-module-behringer-x32
Hope this helps  🙌

Good to know, thanks! In the meantime, I have worked on a separate library that allows communicating with the Soundcraft mixer. It also handles the mixer state and resolves feedback. The enxt step will be to integrate the library into this module. After this, we can actually bring the feedback to Companion.

That's amazing! you won't believe how much easier my life will be thanks to that! Thanks already

@fmalcher i run into issues, according to the api sending a INIT command should return a JSON object. It doesn't it returns text lines. They say keep the connection alive each second by sending ALIVE. From that you should get updated json objects. Because that all doesn't work, I tried to resend the INIT command several times, but after a while no data will return. How did you keep receiving the data?

@JeffreyDavidsz I'm not really sure what API description you're talking about. can you please elaborate? 🙂
The mixer keeps sending incremental updates via se socket connection. I used those to assemble a full state object.
I'm currently working on integrating my connection lib into this companion module, see my draft PR. Feedback already works in theory, but I couldn't test it with the real hardware yet.

I have an api from Soundcraft (not allowed to send) the initial status is coming in, but after that nothing untill I send INIT. I'll check the pr!

@fmalcher Besides the original module had it already, is there a reason why you use a random number in the connection string?
ws://${this.targetIP}/socket.io/1/websocket/${Math.random() * 10000} It might be the solution of my update problems, but I would like to know why

@JeffreyDavidsz Actually, I just took this from the original module. This might be due to how socket.io (which is used by the original Soundcraft web app) structures its URLs. Maybe @TheMrPoseidon can tell us more?
I wanted to use Socket.io as well, but the mixer has a super old version of the protocol that is not supported anymore by recent releases of socket.io. Thus, I still stuck with plain websocket through rxjs/websocket.

@fmalcher I don't see any INIT command command in your code to keep receiving updates?

@JeffreyDavidsz Actually, I just took this from the original module. This might be due to how socket.io (which is used by the original Soundcraft web app) structures its URLs. Maybe @TheMrPoseidon can tell us more?
I wanted to use Socket.io as well, but the mixer has a super old version of the protocol that is not supported anymore by recent releases of socket.io. Thus, I still stuck with plain websocket through rxjs/websocket.

clear, I already spoke about it, I remember main thing was stability.
So my main issue is still how to receive incremental updates

@fmalcher I don't see any INIT command command in your code to keep receiving updates?

 The current implementation of this module doesn't use it either and it also worked for me without.
Does the original Soundcraft webclient send an INIT or is this just written in the API spec?
btw, you can ping me in the Slack at any time if you like to chat!

@JeffreyDavidsz @fmalcher The reason of why I used a random number was that I had issues reconnecting with the mixer. I assumed that the number behind /websocket/ was some sort of a session id. When I allocated a random number after the connection got lost everything worked fine. I tested ws://${this.targetIP}/ with the new connection handling from @fmalcher. I see no problem in changing it.

FYI, I changed the WS URL to ws://${this.targetIP}.


Update on signature of special/_ufuncs.py

Hi,
simple request.. in the signatures of many functions inside special/_ufuncs the signature does not coincide with the description text. For example the function sph_harm, the description contains this
  Parameters
    ----------
    m : array_like
        Order of the harmonic (int); must have ``|m| <= n``.
    n : array_like
       Degree of the harmonic (int); must have ``n >= 0``. This is
       often denoted by ``l`` (lower case L) in descriptions of
       spherical harmonics.
    theta : array_like
       Azimuthal (longitudinal) coordinate; must be in ``[0, 2*pi]``.
    phi : array_like
       Polar (colatitudinal) coordinate; must be in ``[0, pi]``.

However, the signature of the function is defined as
def sph_harm(x1, x2, x3, x4, *args, **kwargs)
which makes it quite confusing on what each x1, x2, ... does. If this can be updated to
def sph_harm(m, n, theta, phi, **kwargs):
then that would remove unnecessary checking of the input variables.

Hi @zwep, what you are observing is a consequence of how ufunc docstrings are created.
From the ufunc docs:

doc | A docstring for each ufunc. The first part of the docstring is dynamically generated from the number of outputs, the name, and the number of inputs. The second part of the docstring is provided at creation time and stored with the ufunc.

The def sph_harm(x1, x2, x3, x4, *args, **kwargs) part is only the first part and it's generated by the ufunc machinery.  The second part should be the complete docstring as in the documentation.
For example:
>>> print(ss.sph_harm.__doc__)
sph_harm(x1, x2, x3, x4, /, out=None, *, where=True, casting='same_kind', order='K', dtype=None, subok=True[, signature, extobj])

sph_harm(m, n, theta, phi)

Compute spherical harmonics.

The spherical harmonics are defined as

.. math::

    Y^m_n(\theta,\phi) = \sqrt{\frac{2n+1}{4\pi} \frac{(n-m)!}{(n+m)!}}
      e^{i m \theta} P^m_n(\cos(\phi))

where :math:`P_n^m` are the associated Legendre functions; see `lpmv`.

Parameters
----------
m : array_like
    Order of the harmonic (int); must have ``|m| <= n``.
n : array_like
   Degree of the harmonic (int); must have ``n >= 0``. This is
   often denoted by ``l`` (lower case L) in descriptions of
   spherical harmonics.
theta : array_like
   Azimuthal (longitudinal) coordinate; must be in ``[0, 2*pi]``.
phi : array_like
   Polar (colatitudinal) coordinate; must be in ``[0, pi]``.
etc...

All the functions in scipy.special._ufunc are also autogenerated, but all the documentation is provided to the ufunc constructor, so it should all be there.
Are you not able to see the whole docstring?  Can you provide any more information about why you're only seeing the first ufunc-generated part?

Might be a case for using __text_signature__, https://twitter.com/raymondh/status/1343063496330637313.

I might be doing something wrong, but when I get AttributeError: 'numpy.ufunc' object has no attribute '__text_signature__' when I try to to set __text_signature__' for a ufunc

@zwep If you're still wanting to remove the ufunc generated signature, the only way I see to do it is from within numpy.
The function numpy.core._internal._ufunc_doc_signature_formatter is called each time a docstring is requested by the ufunc.  Numpy would need to provide some mechanism to override this function or prevent it from being called in the ufunc C code.

Sounds like this is not actionable within SciPy, so closing.


Unable to install on Windows

I am trying to install saleor referring to page https://docs.saleor.io/docs/developer/installation/windows
When i do migrate the following issue is showing
 OSError: cannot load library 'gobject-2.0': error 0x7e.  Additionally, ctypes.util.find_library() did not manage to locate a library called 'gobject-2.0'
Note: The requirements.txt was installed successfully

I found the issue. Thanks

@pupattan  I met the same problem. How did you solve it?

me too

Following this https://doc.courtbouillon.org/weasyprint/stable/first_steps.html#windows is how I solve this


[CRUD Specification] Proposal to add more generic CRUD capabilities

Overview
The Graphback CRUD Specification defines a simplistic set of CRUD capabilities.
These are fine in very basic CRUD scenarios, but people usually want to perform CRUD operations based on certain filters or criteria.
Update Mutation
The update mutation relies on the ID field to do the update. This presents two problems for the future:

If a model does not have an ID field, the update cannot be performed
The current approach is very limited and people would have to write their own custom update resolvers for scenarios other than updating by ID field.

Proposed spec change:
updateNote(where: NoteFields, input: NoteInput)
This change would allow the user to update multiple items by a matching criteria; For example if somebody wants to set all notes from published: false to published: true where created > 3 days ago.
This would make a much more useful standard Update resolver.
Delete Mutation
The exact same logic as Update Mutation can be applied to delete mutations.
deleteNote(where: NoteFields)

Other
This would represent in a pivot in our CRUD specification philosophy - where we provide a simple CRUD channel between the client and server and the user performs filtering client-side.

The challenge here will be to asses the permission model.
A typical scenario for the data processing is that user gets his projection of the data that can operate on and then this data is replicated to the server - thus why we have update, delete based on ID.

Yes this could require a set of directives or annotations making the datamodel complex to manage.

This could work this way but it will also mean that we no longer can work with hasRole on the operation level and need some form of ACL that brings operation type and resource name into the game (which also can be tricky to replicate on the model)
This also complicates data sync implementation.
I might sound trivial but we also should check what our other friends are doing in terms of those types of filtering and add more info here.
Challenge here is to give users more features while not compromise other features or complicate entire implementation.

I actually agree now that it was explained in these terms that our CRUD libraries should not be for handling complex CRUD conditionals.

I think this issue requires investigation of how other GraphQL tools written for different languages doing it. Ruby Python etc.

With the possibility to extend CRUDServices it should become more advantageous to add more generic CRUD operations, since any concerns about things like Auth can be handled in the model-specific CRUDService extensions.
See https://github.com/aerogear/graphback/issues/1059

Yes!

Hey, I just wanted to chime in. I think it is crucial to have more powerful filtering capabilities. The basic CRUD operations are nice, but not sufficient for anything more than a trivial application that probably can't do much in a production situation. Prisma had a really nice set of basic filtering capabilities. I'm running into this problem right now with the app I'm building with graphback, and I'm going to have to leave graphback and drop down into raw SQL queries.
Imagine a model like this:
type User {
  id: ID!
  age: Int!
}

I would expect to be able to filter users by age, like this:
query {
  findUsers(fields: {
    age_gt: 18
  }) {
    id
  }
}

I would like to be able to do things like age_gt, age_lt, age_eq, age_neq, etc.
I'm not sure why permissions are a critical concern here, since the schema that graphback generates is mostly orthogonal to permissions (or should be as I see it). Each permissions framework will need to figure out how to deal with whatever graphback generates, right? I just don't know if it's a good idea to limit graphback's design based on a singular implementation of a permissions framework, since there will be many.

 [Graphback] New CRUD specification

I have updated schema based on current progress.

MErged to master with release happening soon. 🎊

Closing. Merged and will release along with new runtime API!


Remove signer hardcoding of SHA-256

Summary

Closes https://github.com/sigstore/timestamp-authority/issues/304
Currently when signers are created, SHA-256 is always used. A KMS based key may use a different supported algorithm, like SHA-384 or SHA-512, so this hardcoding should be removed.

Adds a new timestamp-server flag signer-hash-function that allows the user to specify a signer hash function. This is used in several different signer schemes
Adds two new fetch-tsa-certs flags, intermediate-hash-function and leaf-hash-function, that allow the user to specify the leaf and intermediate key hash functions
Updates the signer code to handle a specified hash function

Release Note

Documentation

Closing as the hardcoding bug should be resolved by https://github.com/sigstore/timestamp-authority/pull/452


fix: invalid integer when using -v flag in ape test

What I did
For some reason, ape test -v debug was no longer working - I was getting an Invalid Integer problem.
How I did it
Hack click to ignore type checking..
I wish the callback was enough for this but I guess click does what it wants.
How to verify it
Run:
ape test -v debug

Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

very weird fix, but I approve nonetheless

Agreed it is weird, I may consult with click

So click recommends making a custom type: https://github.com/pallets/click/issues/1729


Fix lazy list tests copied from androidx

Proposed Changes
I don't know exactly why, but items for horizontal lazy list not visible items are placed after visible ones, that causes tests to fail.
Practically there should be no difference in order, but weird that android tests seems to work in another way
Testing
Test: run LazyListBeyondBoundsTest

Hmm, this could break scrollbars for lazy lists.

@m-sasha you mean for non-fixed item size?

@m-sasha you mean for non-fixed item size?

Even fixed-sized. I'm calculating the average visible item size like this:
    override fun averageVisibleLineSize() = with(scrollState.layoutInfo.visibleItemsInfo){
        val firstFloatingIndex = firstFloatingVisibleItemIndex() ?: return@with 0.0
        val first = this[firstFloatingIndex]
        val last = last()
        val count = size - firstFloatingIndex
        (last.offset + last.size - first.offset - (count-1)*lineSpacing).toDouble() / count
    }

So if last() isn't actually the item closest to the end of the list, it will break.

I'm calculating the average visible item size like this:

But you take visible items. The test differs for invisible ones.
Also, ScrollbarTest passes


Getting 401 response as cookies are not set in requests

Bug Description
We are trying to connect to the Cloudant database using java client.
First it gets AuthSession by executing POST request to https://cloudant-host:443/_session .
Here we get 200 OK response and AuthSession info. Then it says that it is storing a cookie. And cookies are stored for URIs: [http://cloudant-host]
Here is the response for _session-
https://:443/_session response headers {null=[HTTP/1.1 200 OK], Server=[CouchDB/2.1.1 (Erlang OTP/20)], X-Content-Type-Options=[nosniff], X-Cloudant-Backend=[bm-cc-us-south-04], X-Cloudant-Request-Class=[unlimited], Date=[Wed, 15 Apr 2020 12:54:57 GMT], Via=[1.1 lb2.bm-cc-us-south-04 (Glum/1.88.0)], X-Frame-Options=[DENY], X-Cloudant-Action=[cloudantnosqldb.session.write], Strict-Transport-Security=[max-age=31536000], Cache-Control=[must-revalidate], Set-Cookie=[AuthSession=<session_id>; Version=1; Expires=Thu, 16-Apr-2020 12:54:58 GMT; Max-Age=86400; Path=/; HttpOnly; Secure], Content-Length=[57], Content-Type=[application/json]}
Next, we start querying data from Cloudant. However, it fails with 401 Unauthorized response.
Somehow It is unable to find cookie values to set in the request header. AuthSession is missing in the request header.
Here is request header-
request headers {Accept=[application/json], User-Agent=[java-cloudant/2.17.0/1.8.0_211/IBM Corporation/Linux/ppc64le]}
1. Steps to reproduce and the simplest code sample possible to demonstrate the issue
We are using below code to connect to Cloudant-
CloudantClient client = ClientBuilder.account(cloudantUsername).username(cloudantApiKey).password(cloudantApiPw).build();
this.db = client.database(dbName, false);
InputStream inputStream = null;
try {
inputStream = db.find(CONFIG_FILE_ID);
return CharStreams.toString(new InputStreamReader(inputStream, "UTF-8"));
}
2. What you expected to happen
Cookie-based authentication should work as expected. AuthSession information should be used in subsequent requests.
3. What actually happened
It has not set AuthSession info in follow up requests which caused in 401 error from the Cloudant.
cloudant.log
Environment details
Cloudant Client - 2.17.0
Java version including vendor -
java version "1.8.0_211"
Java(TM) SE Runtime Environment (build <IP_ADDRESS> - pxl6480sr5fp37-20190618_01(SR5                                                                                FP37))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux ppc64le-64-Bit Compressed References 20190                                                                                617_419755 (JIT enabled, AOT enabled)
OpenJ9   - 354b31d
OMR      - 0437c69
IBM      - 4972efe)
JCL - 20190606_01 based on Oracle jdk8u211-b25
Using the optional okhttp dependency - Yes
com.squareup.okhttp3:okhttp-urlconnection:4.0.0
This java application is hosted on HMC. Below are HMC details-
*OS Embedded Operating Systems
*DS Platform Firmware
*RM V9R1.941.0

Hi @Lalit-Bharate ,
Thank you for this ticket!
Looking at the environment details, there is

Cloudant Client - 2.17.0

and the latest available release is https://github.com/cloudant/java-cloudant/releases/tag/2.19.0 which has improvements for session handling. Also, for okhttp-urlconnection, the supported version is 3.12.5.
Can you please let us know if the problem you are encountering still appears with 2.19.0 for java-cloudant and 3.12.5 for okhttp-urlconnection?

@bessbd Yes. I will try with latest version of Cloudant Client. First, I will try without any okhttp dependency.

It was the issue with cloudant client host timezone not properly set and date-time being out of sync as that of Cloudant DB. It caused cookies set by the server to be considered as expired on cloudant client.


v-model init value

Please implement proper working v-model with datepicker to be able to set initial date value.

What's your issue? I think it works properly.
<datepicker :inputClass="{ test: true }" v-model="value"></datepicker>

Is there cdn or any public access to the datepicker plugin to show example in a sandbox?

I have the same problem...
<datepicker v-model="value"></datepicker> if I set value, it won't be shown in the input.

@luventa what is a reason to assign v-model="value" here?
The value is always empty string there that's why the input is always empty in the begining.
I dropped this v-model on my side and use defaultDate option (flatpickr) to assign initial value as a workaround.
But it is not the way the v-model directive should work. It should be allowed to put an initial value in the datepicker's v-model.

Thought you want a init date for it and here is the example code.
<template>
  <datepicker v-model="value"></datepicker>
</template>

Yes, but using wrap: true option.
<template>
  <datepicker v-model="value" :config="{ wrap: true }">

  </datepicker>
</template>

@dimamarksman I think this is a bug. Will fix

Thank you!
21 февр. 2017 г. 12:22 PM пользователь "Pan Yue"<EMAIL_ADDRESS>написал:

@dimamarksman https://github.com/dimamarksman I think this is a bug.
Will fix
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vue-bulma/datepicker/issues/19#issuecomment-281302779,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADHNACDXbnnpOSbVSKT29JvMp5Cgz9YHks5rerrQgaJpZM4L_PxQ
.

fixed. Will publish soon. Feel free to reopen
Thanks!

I have to rebase my commits to keep minimum code change.
Please check the fix 4dce70f
I will publish this component after other issues are fixed.
Please make change locally for time being. Really appreciate.


mig_av - duplicate entries for filenames containing strings that match other filenames

Two filenames containing the same string can result in duplicate entries for the same file in the Meadow inventory.
Example: An inventory contains the filenames "my_file_001" and "my_file_001a". The resulting Meadow inventory will match both filenames to "my_file_001a", resulting in duplicate entries for those files in the Meadow inventory.
A simple solution would be to have the script run a final check on the Meadow inventory for duplicate filenames and warn the user if they are found. More recent file naming policies should prevent this problem, but it may be encountered occasionally with legacy projects.

Since this primarily impacts only a small number of legacy files and current file naming schemes should avoid this issue, it is being closed for now.


⚠ Site ANTS has degraded performance

In 1fbd490, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 3631 ms

Resolved: Site ANTS performance has improved in 565a90a after 54 minutes.


Build Error (Visual Studio 2019)

Describe the bug
Hi so when building deadcell i get a error with this line "#include experimental::filesystem and it wont build please try to fix it or tell me how i can fix it Thank you
To Reproduce
Try to build using the most updated visual studio (If this is for real the problem i will install visual studio 2017 just tell me
Expected behavior
I expected it to build correctly
Screenshots
i already deleted it for now sorry but i think you can get what kinda error that would look like
Additional context
i dont really have anything else

you should do #include  insteaf of whatever you have there

use 2017 SDK instead of whatever u use


Default activity not found.

Hi, I did not change any code in the original project folder. However, when I run the code in android studio, it appears "default activity not found".
Does anyone know why?

Select the main activity "LocationActivity" before running. You may be able to right click on it and run?

Sorry for the disturbance.
May I know do I need to create "LocationActivity" by myself?
It is because I cannot find "LocationActivity" in the zip. file.

You should be able to find it at:
ARCore-Location/examples/sceneform/app/src/main/java/uk/co/appoly/sceneform_example/


feat: Build Windows 2022 Containerd Gen 2 VHD

What type of PR is this?
Build Gen2 VHD for 2022 containerd

/kind feature
What this PR does / why we need it:
To add support of building Windows 2022 containerd Gen 2 VHD in AgentBaker.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Please remove the empty file "cd"


Cannot generate xcode project

I followed the instructions step by step but still unable to generate the xcode project with tulsi
This is the error I got each time I press "generate" with tulsi, any help please ?
ERROR: /Users/hebamohamed/mediapipe/mediapipe/examples/ios/edgedetectiongpu/BUILD:24:1: in ios_application rule //mediapipe/examples/ios/edgedetectiongpu:EdgeDetectionGpuApp: Traceback (most recent call last): 	File "/Users/hebamohamed/mediapipe/mediapipe/examples/ios/edgedetectiongpu/BUILD", line 24 		ios_application(name = 'EdgeDetectionGpuApp') 	File "/private/var/tmp/_bazel_hebamohamed/90e5d7c4bc9f07629d7207ff133da7c0/external/build_bazel_rules_apple/apple/internal/ios_rules.bzl", line 160, in _ios_application_impl 		run_support.register_simulator_executable(ctx, executable) 	File "/private/var/tmp/_bazel_hebamohamed/90e5d7c4bc9f07629d7207ff133da7c0/external/build_bazel_rules_apple/apple/internal/run_support.bzl", line 28, in run_support.register_simulator_executable 		ctx.actions.expand_template(output = output, is_executable = T..., <2 more arguments>) 	File "/private/var/tmp/_bazel_hebamohamed/90e5d7c4bc9f07629d7207ff133da7c0/external/build_bazel_rules_apple/apple/internal/run_support.bzl", line 36, in ctx.actions.expand_template 		shell.quote(ctx.fragments.objc.ios_simulator...) 	File "/private/var/tmp/_bazel_hebamohamed/90e5d7c4bc9f07629d7207ff133da7c0/external/bazel_skylib/lib/shell.bzl", line 49, in shell.quote 		s.replace("'", "'\\''") type 'NoneType' has no method replace() ERROR: Analysis of aspect '@tulsi//:tulsi/tulsi_aspects.bzl%tulsi_sources_aspect of //mediapipe/examples/ios/edgedetectiongpu:EdgeDetectionGpuApp' failed; build aborted: Analysis of target '//mediapipe/examples/ios/edgedetectiongpu:EdgeDetectionGpuApp' failed; build aborted General failure: Bazel aspects could not be built.

I'm stuck here as well. Initially, I was getting the same error when trying to build tulsi, but I made the changes to my WORKSPACE as recommended here:
https://github.com/bazelbuild/tulsi/pull/106/commits/aa98d4ca71281448cdb6878631ebdedc7813d2cc
Now tulsi is up and running, but hitting "generate" creates the same error as above.

Hello team @mgyong @camillol @jiuqiant
Any updates on that issue please? Im really stuck here for a long time :(
Thanks in advance all

I also have the same issue.

See https://github.com/google/mediapipe/issues/187#issuecomment-544723390

See #187 (comment)

Solved! thank you so much 🙏

This may be a better solution. Instead of downgrading Bazel, you can update your apple rules in your mediapipe WORKSPACE file.  Apple has changed things recently and does not accept release tags anymore (see the comments at the top of their README). They want you to use a commit.  I changed my rules to match what's in the master repository for the iOS hello world example and that has worked well for Bazel 1.0.0.
https://github.com/bazelbuild/examples/blob/master/tutorial/WORKSPACE


Token audience is set to Microsoft Graph, API refuses to accept it

Hi!
I followed the example and everything was just fine, but then I tried to implement the same approach in my existing application and got the following error: Bearer error="invalid_token", error_description="The signature is invalid". This is caused by the fact that the access token I get from AzureAD is intended for Microsoft Graph and not for my application (its headers are ["aud": "00000003-0000-0000-c000-000000000000",
"iss": "https://sts.windows.net/5bb4edc8-7c6e-4911-97b0-06a9ef95dd6a/"], whereas the ones I get when following the example are ["aud": "3ef2f30b-0668-4aa1-868c-70b61e786299",
"iss": "https://login.microsoftonline.com/5bb4edc8-7c6e-4911-97b0-06a9ef95dd6a/v2.0"]).
The only difference I've made to the readme configuration was concerned with redirectUri (set to "https://localhost:44307/") and resourceUri (set to "http://localhost:5001/api/profile").
Could this be a reason for such a behavior? If not then what am I doing wrong?
Thanks in advance!
Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Description
Please provide your question here, including as much relevant details as possible.
Examples:

"How do I use MSAL with Vue.js"
"How do I SSO between tabs?"
"How do I use MSAL to protect my custom Web API?"
"How can my app support multiple AAD tenants?"
"When will my scenario be supported?"
"When will this framework be supported"

@alexeybogusevich can you confirm that:

when you register your front-end app on Azure Portal, you added API permission for 'access_as_user'

ProfileSPA/src/utils/authConfig.js is configured as:

export const loginRequest = {
    scopes: ["openid", "profile", "offline_access"]
}

// Add here scopes for access token to be used at the API endpoints.
export const tokenRequest = {
    scopes: [api://{client_id_of_API}/.default]
}

@derisen, Yes, I do, absolutely.

@alexeybogusevich in that case please send me a network trace (you can use Fiddler for that). You can find my email on my profile.

@derisen, okay, thank you! Did it.

This issue has been resolved over email correspondence. Closing now.


Resolve swagger parsing issues

Resolves https://github.com/odota/core/issues/1703
This doesn't fix the incorrect API definitions, but does fix parsing. So tools can be used to generate clients that are mostly correct.
This PR also adds a new dependency, I'm not sure the guidelines on adding those, but it adds https://www.npmjs.com/package/@apidevtools/swagger-parser in order to parse the spec in a unit test to ensure validity.

unclear why CI is failing--maybe due to the package-lock change?
travis error is:
$ sudo bash scripts/build.sh
Error: Cannot perform an interactive login from a non TTY device
The command "sudo bash scripts/build.sh" exited with 1.

I think its actually related to the DOCKER_PASSWORD environment var, its not getting set somehow.
I was able to replicated it locally by setting DOCKER_USERNAME, but leaving DOCKER_PASSWORD unset. With that, the docker login command within the build script fails with that same interactive login error message
Though Im not sure why the master build you recently tried succeeded fine. Is the environment variable dependent on who is running the build? Like I don't have access to the DOCKER_PASSWORD var, so it doesnt set it?

Yeah, looking more into it, Im almost positive thats the issue.
Your master build output has this near the top
Setting environment variables from repository settings
$ export DOCKER_USERNAME=howardc93
$ export DOCKER_PASSWORD=[secure]
$ export STRIPE_SECRET=[secure]
$ export STRIPE_API_PLAN=[secure]

While mine only has this
Setting environment variables from repository settings
$ export DOCKER_USERNAME=howardc93

So for some unknown reason, this build isn't getting the password set.

Oh I believe this is due to security reasons, PRs don't get env vars.

Ah interesting, I thought package.json was the only file that controlled versions.
I can create a new PR resolving those rules if you'd like. Looks like its a few really simple fixes (and I introduced a few of em : ) . I didn't check to see if linting was a part of the build process


As the Product Manager for MDN I want to see the performance is on par with the current implementation so we don’t take a hit on SEO

User story
As the Product Manager for MDN I want to see the performance is on par with the current implementation so we don’t take a hit on SEO
Acceptance criteria

[ ] Performance measurements have been set up for main KPI in Kuma Next
[ ] Performance reported for main KPI in Speed-curve
[ ] Performance is on par with with current Kuma

Tasks
If relevant, you can make a checklist for tasks.

[ ] This is an incomplete task.

I'm pulling this user story into the new sprint, since we need to have this data before we go live.
The data we need should be being reported now, but I haven't seen it showing up in speedcurve yet, so this user story is to capture any remaining work toward getting that data.

In issue #1450, @atopal wrote:

Hey David, I looked into it. What we need is js-ie-load-event-end-measure and css-ie-load-event-end-measure. That's available in the non-react version, but missing in the react version

I think I enabled the measure that these two are based on in that other issue, but I guess I need to go one step further to get these two working. Hopefully this is just a Kuma issue, not another BoB or interactive examples issue.

So unfortunately, this is both a Kuma and a BoB issue. I've filed two PRs:
https://github.com/mozilla/kuma/pull/5445
https://github.com/mdn/bob/pull/244
@schalkneethling: do you have time this sprint to push out another BoB release and regenerate the interactive examples?

do you have time this sprint to push out another BoB release and regenerate the interactive examples?

Done.

Thanks, Schalk!
I was able to get Speedcurve to run the react tests manually, and have verifiied that there is one datapoint shown on the speedcurve charts. I guess we won't get a line or a curve until we've got another data point.  I also noticed that we were running the non-react checks 3 times a day, but the react ones only once a day. I've bumped that back up to 3x/day so we get some data more quickly.
It will be interesting to see what LUX adds to this...
I've check off the first two tasks for this user story. If we can verify that performance is on-par, then we (probably Kadir, actually) can close this.

Can confirm that it's showing up on Speedcurve. I'd give it 2 days before we call performance parity, but the single data point does look good so far (considering the 1+ second variation on Speedcurve for synthetic tests)

hmm, the data for JS pages seems to be fine, but the CSS page has only reported a single data point for the react version 2 days ago: it's https://beta.developer.mozilla.org/en-US/docs/Web/CSS/box-shadow

Even the non-react reporting is flaky for that test, with a bunch of dropped data points.
The one data point we do have for the beta site on that test is from the time I manually ran the tests. I'm trying that again now, to see if we get another data point from it.
Given that the page is reporting data, however, I don't know how I could debug this. It seems likely to be a load-related issue or a bug on speedcurve's side?
I'm hoping that once we ask people to start trying out the beta site, that LUX data will save us...

The data is still fragmentary, but at least we've got some now. It is hard to tell with speedcurve, but it looks to me as if there is not a performance regression. What do you think @atopal?

We discussed this at the sprint meeting this morning and Kadir agreed that the data show no significant performance regression. So I'm marking this as done and closing it. See issue #1703 for a LUX-related followup issue.


Same line detection fails.

@JaMe76  I have a document like below:

Code:
import deepdoctection as dd

analyzer = dd.get_dd_analyzer()
doc_pred = analyzer.analyze(path="example_doc.pdf")
doc_pred.reset_state()
doc = iter(doc_pred)
page = next(doc)
print(page.text)

Text Output:

38.3
Lithium metal and lithium ion batteries
38.3.1
Purpose
This section presents the procedures to be followed for the classification of lithium metal and lithium ion cells and batteries (see UN Nos. 3090, 3091, 3480 and 3481, and the applicable special provisions of Chapter 3.3 of the Model Regulations).
38.3.2
Scope

Text in the same line is breaking into different line, How can I control this behaviour? @JaMe76
For example

38.3.1 Purpose

is split into:

38.3.1
Purpose

You can control line break to some extent by tweaking some of the following variables:
TEXT_ORDERING.STARTING_POINT_TOLERANCE
TEXT_ORDERING.BROKEN_LINE_TOLERANCE
TEXT_ORDERING.HEIGHT_TOLERANCE
TEXT_ORDERING.PARAGRAPH_BREAK

You can find a description of these variables in the docstrings here:
https://github.com/deepdoctection/deepdoctection/blob/9658119bc9ad786d8c49e665569ec1caceccbee6/deepdoctection/pipe/order.py#L448


Bug: Can't create a shortcut to a folder

Description
If I try to create a shortcut to a folder, a dialog that says it requres administrator privileges appears and I can't create the shortcut even if I choose creating the shortcut on the desktop instead.
Steps To Reproduce

Select New -> Shortcut on the toolbar.
Enter the location of a folder.
Press Create. A dialog that says it requres administrator privileges will appear.
Press Create again. No shortcuts will be created.

Requirements
The shortcut should be created with no warnings.
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.4651
Log File
debug.log

Is this an issue before #15934?

Is this an issue before #15934?

Yes

Fyi I an planning to remove UIFilesystemHelpers and create IStorageShortcutService and service.CreateNormalLink/Async/(string path, string arguments).
It's totally up to someone who work on though.

@hishitetsu this functionality looks totally malfunctioning because you can't also target to drive root. Do you think those fixes would require major change on shortcutting abilities and it worth having a service  IStorageShortcutService?

To resolve the issue with the drag-and-drop functionality in the Files app:
Update the App: Ensure you are using the latest version of the Files app.
Run as Administrator: Try running the Files app as an administrator to grant necessary permissions.
Check Windows Settings: Verify that no Windows settings, especially User Account Control (UAC), are blocking the functionality.
These steps might resolve the problem.

Drag and drop doesn't work when Files is running as admin

Problem Description:
When trying to create a shortcut to a folder using the "New -> Shortcut" option, a dialog requesting administrator privileges appears, and the shortcut cannot be created, even when selecting the desktop as the destination.
Steps to Reproduce:
Select "New -> Shortcut" on the toolbar.
Enter the folder location.
Press "Create" (a dialog requesting administrator privileges appears).
Press "Create" again; the shortcut isn't created.
Solution:
Run as Administrator: Try running the application as an administrator to bypass the permission issues.
Change Folder Permissions: Ensure that the folder's permissions allow shortcut creation without requiring elevated privileges.

This is an issue with the code base. Hishitetsu is a developer of Files and Yair who owns the project has approved this. Creating a shortcut should work like Windows File Explorer and not required the user to change folder security options either.

English
To resolve the shortcut creation issue in the Files application:

Identify the Problem Area: Focus on the part of the code responsible for handling the shortcut creation process.
Modify the Code: Adjust the logic to avoid requiring administrator privileges when creating shortcuts, similar to how Windows File Explorer handles it.
Testing: Test the changes locally to ensure that the shortcut creation works without security prompts.
Submit a Pull Request: After testing, submit the changes via a pull request on GitHub for review.

Example Code Snippet:
// Hypothetical example: Ensure the shortcut creation doesn't require elevated privileges
function createShortcut(targetPath) {
    if (!isElevated()) {
        // Standard shortcut creation process
        createLink(targetPath, getUserDesktopPath());
    } else {
        // Handle scenarios requiring elevation differently
        requestAdminPrivileges();
    }
}

Türkçe
Files uygulamasındaki kısayol oluşturma sorununu çözmek için:

Sorunlu Alanı Belirle: Kısayol oluşturma sürecinden sorumlu olan kod bölümüne odaklan.
Kodu Değiştir: Kısayol oluştururken yönetici ayrıcalıkları gerektirmeyen bir mantık oluştur, tıpkı Windows Dosya Gezgini'nde olduğu gibi.
Test Etme: Yapılan değişiklikleri yerel olarak test ederek, kısayol oluşturmanın güvenlik uyarısı olmadan çalıştığından emin ol.
Pull Request Gönder: Testlerden sonra, değişiklikleri inceleme için GitHub üzerinden bir pull request ile gönder.

Örnek Kod Parçası:
// Örnek: Kısayol oluşturmanın yükseltilmiş ayrıcalık gerektirmemesini sağla
function createShortcut(targetPath) {
    if (!isElevated()) {
        // Standart kısayol oluşturma işlemi
        createLink(targetPath, getUserDesktopPath());
    } else {
        // Yükseltme gerektiren durumları farklı şekilde ele al
        requestAdminPrivileges();
    }
}

Bu adımları izleyerek sorunu çözebilir ve katkıda bulunabilirsin.

@hishitetsu this functionality looks totally malfunctioning because you can't also target to drive root. Do you think those fixes would require major change on shortcutting abilities and it worth having a service IStorageShortcutService?
Also, I think shortcut creation needs a COM 'IShellLink' interface.

I haven't had time to work on Files for a while and haven't checked it out yet, but I'm sure there are all sorts of problems with creating shortcuts.
But this is a basic feature, so if there is a way to fix it quickly before taking the time to completely rewrite it, I'd like to fix it quickly first.

Same. Was it working before? I'm might try to check past versions and report on it. If I'm in the mood later I might try and fix it myself, but no promises.
Maybe this is a good repo for learning the windows side of things. I mainly do Linux backend app development.

The bug happened in between "v3.3.1" and "v3.3.2". I might narrow it down more tomorrow.

I'm pretty sure this is the commit that broke it. https://github.com/files-community/Files/commit/7cde881b6aea31fb128781dbd802fb8778bfcfd9

@jross11211 are you working on this? I was going to fix it but will wait if you are working on it.

I have a very fast computer, like +/- 5% the fastest in the world. So it's relatively easy for me to identify when a feature broke.
For this I might need to let an established developer on this project take it. Personally, I just enjoy learning new stacks. Since this bug will require a dependency change, it may not be something I can do in a timely manner. I took a couple attempts, but it doesn't seem to build on the current version of main by simply changing the version.
FYI, make sure you do a full clean (only committed files) and uninstall the app in the start menu when reproducing it. I'm not familiar with this stack, so sorry if that was already obvious. I'm mostly here to learn about the C#,C++,Visual Studio 2022 stack because I've never used it before.
Note for the developer: The new Microsoft licensing agreement is kind of scary for American users. I'd happily pay $8, but I'm absolutely not trusting Microsoft with any payment information anymore.


method added to extract emojis from text

I added a method to extract all emojis from a given text.

Coverage increased (+0.1%) to 92.722% when pulling fdf73d92f7152b4084f6004551c813a86104364d on t4deon:master into d75b072acd97ccab4c32e1b9a07fcd079648580d on vdurmont:master.

This is awesome!
I'm ready to merge the request with one condition: can we return a List<String> instead of a String[]? I'm using Collections in the rest of the library and I think we should stay consistent.

ok no problem, I just changed the return type.

Coverage increased (+0.1%) to 92.722% when pulling a695ca4b8d6574892e883f14a3ee5024d1578d34 on t4deon:master into d75b072acd97ccab4c32e1b9a07fcd079648580d on vdurmont:master.

I will try to release a new version including this today (or over the week end). Thanks for your contribution!


Disable console on windows for release builds

See https://github.com/janhohenheim/foxtrot/blob/274563b701a4d2002ff4d585d02d54f56a7704e5/src/main.rs#L1 for an example of this.

goal of this template is "This repo show how to set up CI on a GitHub project for Bevy"
I would prefer to keep it limited to that

This repo already includes the AssetMetaCheck::Never workaround and #![allow(clippy::too_many_arguments, clippy::type_complexity)]. So this seems in scope.

#![allow(clippy::too_many_arguments, clippy::type_complexity)] is to pass CI, AssetMetaCheck::Never is to be able to publish (through CI) to itch.io

I mean IMO this is required to publish on Windows. But I guess you could argue that having the release build open a console doesn't completely prevent the build from running.


Elec lead

Updated flying lead functionality can be tested with either of the following demos (only the second includes the new plug/receptacle model):
ros_launch dave_demo_launch dave_electrical_mate.launch

or
roslaunch dave_demo_launch dave_plug_and_socket_demo.launch

Updates include the following:
Force calculations for insert & extract aligned with the plug link
New meshes and models
Male-to-female and female-to-male plug/receptacle combos
Underwater platform model (incorporated into both SDF and URDF demos)
Added ROS functionality to expose calculated force applied to the plug link during insert & extract
rqt_plot /m_to_f_plug/appliedForce/vector to visualize the message
Tutorial updates to account for changes

Is the example roslaunch dave_demo_launch dave_plug_and_socket_demo.launch represented in the wiki pages somewhere?    I see roslaunch dave_demo_launch dave_electrical_mate.launch in https://github.com/Field-Robotics-Lab/dave/wiki/Electrical-Plug-Mating-Plugin.
Maybe we could add the first roslaunch to the existing wiki, add a screenshot and explain the differences between the two examples?

I was able to run both roslaunch examples and see that the /m_to_f_plug/appliedForce/vector was advertised.  I'm probably not skilled enough to drive the vehicle and arm to test this, so my proposed plan is...

Once the documentation (see comment above) is addressed, then I'll approve.
Go ahead and merge
Find someone to take on https://github.com/Field-Robotics-Lab/dave/issues/193
Once we have solved https://github.com/Field-Robotics-Lab/dave/issues/193, use that to test/demonstrate the mating forces and create a highlight video.

@dtdavi1 Sound like a plan?

I've updated the wiki some to better differentiate between the two demos (the dave_plug_and_socket_demo is towards the end).  I'm working on a video demo and will finalize that before the release.

For a quick test of the plugin functionality, the world file that is used in the dave_electrical_mate.launch demo can be modified as follows:
Comment out line 174
Uncomment line 175
This will position the plug in the socket's opening (but not engaged) upon startup.  The prismatic joint will be formed right after startup, but there won't be enough applied force to lock it.  If you maneuver the RexROV to the stand and lightly bump the plug downward, the joint should lock almost immediately (and should be indicated in the terminal window).
Unlocking will still require you to grab the plug handle with the gripper and pulling upwards (but that's much easier than doing the whole insertion evolution).

@dtdavi1 Both of the launch examples run for me.
I ran the example you suggest to start with the plug aligned.  When I nudge it with the ROV I get some errors reported to the terminal:
Msg] m_to_f_socket and m_to_f_plug are aligned in orientation and distance
[Msg] m_to_f_socket and m_to_f_plug within proximity
[Msg] m_to_f_socket-m_to_f_plug joint formed
[Msg] m_to_f_socket-m_to_f_plug joint locked!
Error [Param.cc:457] Out of range. Unable to set value [6.94416e-310 ] for key[upper].
Error [Param.cc:457] Out of range. Unable to set value [6.94416e-310 ] for key[lower].
[Msg] m_to_f_socket-m_to_f_plug joint unlocked!
[Msg] m_to_f_socket-m_to_f_plug joint removed
[Msg] m_to_f_socket and m_to_f_plug are aligned in orientation and distance

Are these expected?

@bsb808 They're all either expected or at least not surprising.  Here's a summary of what the stream is telling you:
The first is a report that the plug and socket are properly aligned.
The second is a report that the prismatic joint was created (i.e., they've been properly aligned for the requisite amount of time)
The third is a report that the joint was locked (i.e., it's plugged in) because the right amount of pressure was applied
I have no idea what the errors are (they occur on occasion but don't really affect anything).  You can write it up as an issue (or I will) if you want, but I don't think they should prevent the merge.
The "joint unlocked" and "joint removed" mean that it was unplugged.  If you didn't actually grab it and pull, it was probably a byproduct of the plug being jostled when it was plugged in (i.e., it plugged in successfully but then popped loose).
The last line is from the process starting all over because it's not plugged in but is properly aligned.

@dtdavi1 Understood.  The [Msg]s are really helpful and I understood those - it was the Error that makes me unsure if things are operating as expected.
I opened an issue so we can run this to ground post 4.3.0 - https://github.com/Field-Robotics-Lab/dave/issues/227
Please merge when you can.

@bsb808 Sounds good.  My best guess is that the error is associated with a race condition that occurs when the joint is locked and then removed too quickly (which occurs somtimes when the insertion is rough).


I don't see any heartbeat mechanism in the souce code!!!

My client need to get into subscribe mode, and there is no other way to determine if the connection is still active except for using timed ping in JedisPubSub.java, is there any plan of heartbeat mechanism???

Nope, there's no plans to implement heartbeat as it's use-case specific. Please open a proper proposal so it can be discussed accordingly. This issue doesn't help

Thanks a lot!


clang: Not a directory

use pyenv shell
install pyqt5 and sip ,when execute make command prompt the following error message.
/usr/local/Cellar/pyenv/20160509/libexec/pyenv: line 43: cd: clang: Not a directory

#502, #580, #588,
Please remember to search the issues list first :)


Allow dockerfile in hat path

Resolves #193, #192 #189

Do you guys think that the chown command should be run in the codercom/ubuntu-dev-go container?

Also, please sign your commits with PGP so we can add them to sail. :key:

@deansheather I think this PR is good to go

@nathanpotter @deansheather This PR is ready to be merged


Add builder for options

Change exampl and test  options to builder
@jovany-wang

CI failed.

Thanks, LGTM.


Other languages

Is there any way to translate Netbox or how it was developed does not fit this upgrade?
I am willing to help with the translation process, especially for Portuguese (Brazil).

Willing to contribute a Spanish translation

While the Django framework does support translations, NetBox is not currently set up to use them. The first part of this would be to iterate over the entire code base and insert a translation wrapper around virtually every string. This wouldn't be difficult, but it would obviously take a good bit of time.
The second part of this is establishing the actual translation databases. These are essentially static mappings of natives (English) string to their equivalents in a different language, which means that every time a string is modified (even slightly), every translation has to be updated as well, or the translation for that string breaks. Considering the size of the NetBox code base, you can imagine how much maintenance this would require.
At this relatively early stage of development, I don't think it makes sense to support translations yet. It would introduce a lot of development overhead, and translators would constantly be playing catch-up.

Thank you for your clarification. When a translation is possible, I will be willing to contribute.

Thanks for understanding. We'll get there one day, once the pace of development slows down a bit.

There are nice tools to make translating a community effort, at least once the groundwork has been done. Two such services that I know off and which are free for opensource projects are POEditor and LingoHub, but there are lots of other tools as well.

It's been a year and a half since NetBox released 2.0. Do you think we're at a point where this would be feasible to implement now? I'd be willing to assist (and have implemented i18n for another Django project before).


feat: add basic realm import script for faster test startup

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for inclusion in changelog

Just adds a simple realm import script that gets keycloak to a point of the latest changes in 2.15.4.
Start keycloak with the environment variable KEYCLOAK_TEST_REALM_IMPORT=true and if the realm doesn't exist, it will import from the import file.
This significantly speeds up keycloak startup time. The migrations still take place after the import but only those that need to change.

We can probably remove the KEYCLOAK_TEST_REALM_IMPORT variable and just have it only run if the realm doesn't already exist.

Just from local testing from running make ui-logs-development to get a minimal core running, you're looking at about 30 seconds to get keycloak from 0 to ready. Which is considerably faster than the 4-5 minutes waiting for all the migrations to take place just to get a new keycloak to a desired state.
IMAGE_REPO=lagoon docker-compose -p lagoon --compatibility up -d api api-db actions-handler local-api-data-watcher-pusher ui keycloak keycloak-db broker api-redis logs2notifications local-minio mailhog
[+] Running 14/14
<snip container status>
Tue 12 Dec 2023 20:04:03 AEDT
keycloak_1                       | Config of Keycloak done. Log in via admin user 'admin' and password 'admin'
^Ccanceled
make: *** [Makefile:315: logs] Error 130
$ date
Tue 12 Dec 2023 20:04:39 AEDT