Add break-all utility, change word-wrap to overflow-wrap

👋
Fix #411
This PR:

Adds a .break-all class
Changes word-wrap to overflow-wrap (https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap)

Thanks!

Docs updated in #47

Thanks for this! I really want to merge it but there's an annoying decision we have to figure out...
Right now you can use break-normal to "undo" break-words at various breakpoints, like:

...

...but because break-all has to use the word-break property, there's currently no way to undo it since break-normal uses overflow-wrap.
I see two solutions:

Make break-normal do two things
If break-normal were defined like this it would fix the problem:
.break-normal {
    overflow-wrap: normal;
    word-break: normal;
}

I'm not sure if there are actually cases where you wouldn't want this to happen though, like maybe you want overflow-wrap: normal and word-break: break-all or some other combination. It's also very rare that any of Tailwind's utilities set multiple properties, I think truncate is the only other one and we have talked in the past about "fixing" that 😕

Add another class
We could add a new class specifically for word-break: normal but what the hell would we call it?
I think if we did that we'd probably need to rename the overflow-wrap utilities, or at least break-normal to wrap-normal, so word-break: normal could be called break-normal. This sucks because it's a breaking change.

Any ideas or thoughts? 🤔

Thanks for your feedback!
I see the problem, not an easy nut to crack. Been doing some thinking and this is my take on all this:

Make break-normal do two things
Instead of making .break-normal do two things we could introduce a .break-reset class similar to .list-reset but for word-wrapping in general:
.break-reset {
    overflow-wrap: normal;
    word-break: normal;
}

This way we could keep the current class names, hence not introducing a breaking change.
Then again as you said, if this kind of utility classes are going to be fixed/removed in future releases then maybe it's a bad idea to add yet another one.

Add another class
It does indeed suck that changing the names would be a breaking change, however it wouldn't make sense (at least not to me) to have overflow-wrap: normal being named .break-normal if word-break: normal was introduced to the framework. I feel a change of the class names in this scenario is a must:
'wrap-words': { 'overflow-wrap': 'break-word' },
'wrap-normal': { 'overflow-wrap': 'normal' },
'break-normal': { 'word-break': 'normal' },
'break-all': { 'word-break': 'break-all' },

Conclusion
I'm really not sure what's the best option here, or if there is another better way of doing this. At least I haven't come up with anything else so far other than my suggestion about adding a .break-reset class. I'd love to hear your thoughts on that. In the meantime, I'll keep thinking about this to see if I can come up with something better. 🤔

Coming back to this since we can break this for 1.0, I think I'm okay with these names...
'wrap-break': { 'overflow-wrap': 'break-word' },
'wrap-normal': { 'overflow-wrap': 'normal' },
'break-normal': { 'word-break': 'normal' },
'break-all': { 'word-break': 'break-all' },

Anyone have any thoughts? I don't like wrap-words because words already wrap by default, so doesn't really feel like it describes it properly. wrap-break is kind of awkward too but it feels a bit closer.
Still considering just making break-normal unset both properties, I think I would be fine with that if no one can think of a scenario (no matter how obscure) where that would be problematic.

@adamwathan sounds good to me!

Thank you @robbinworks for your work! Added in #681.

Great work on the updated PR/merge, thanks! 👍


Missing exported type VerifiedAttestation

The response of verifyAttestationResponse isn't exported in types package or server package.
TS is going inside @simplewebauthn/server/dist/attestation/verifyAttestationResponse to get it.

I played around with this too and found a few more types that could be exported to better support strict typescript users, or more complex use cases.
@MasterKale how do you feel about exporting respective Options type and then the VerifiedAttestation and VerifiedAssertion types?
Currently, the types package seems focused on the external interfaces that SimpleWebAuthn uses that dont have types (i.e. WebAuthn responses and options).
I imagine we could just export from the server package, if the types module wasnt best suited for these particular types.
I can throw up a PR if you dont have the bandwidth

I imagine we could just export from the server package, if the types module wasnt best suited for these particular types.
I can throw up a PR if you dont have the bandwidth

I think this is a great idea, I don't have any reason not to export these types from Server. The various Options will need to be renamed accordingly before export but other than that I'd approve a PR with those changes.

Great! I'll work on this and push up a PR tonight.

Additional types are now exported from the newly-published<EMAIL_ADDRESS>to help with typing inputs and outputs for its various methods
Thanks to @JayHelton for making this happen! :tada:


⚠ Bofrost.at has degraded performance

In 0baf5ec, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1860 ms

Resolved: Bofrost.at performance has improved in 6ceafd0.


refactor(ui): add real links to alerting documentation

Closes #14765

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

@timhallinflux just updated with the correct links from @noramullen1


Add waterbodies to framework base functions

Water bodies are now parsed and returned in the 'supernetwork values' collection returned by the nhd_network_utilities function. These are not used further by this version of code but a later version will use the waterbodies to add further discretization to the network traversal.

Closes #5

Juzer,
Is it correct that the change to WPC affects only the qdc and not the velc
and depthc?
James Halgren
NOAA National Water Center
+1<PHONE_NUMBER>
Lynker https://www.lynker.com/
On Mon, Apr 27, 2020 at 2:05 PM jdhondia<EMAIL_ADDRESS>wrote:

@jdhondia-noaa approved this pull request.
Except for the WPC=0.0 commented out in fortran MC Code - which needs test

all changes are excepted

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/t-route/pull/18#pullrequestreview-401243799,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMW7MUDYAEGCVUV62EANSX3ROXJP5ANCNFSM4MSE3XUQ
.

@jdhondia-noaa I just recommitted with the full correction to WPC using proper declaration and passing in the fortran code so that WPC is not used uninitialized.


Failed to use yaml lib with webpack 5

Got an error during webpack server command. And I can't figure out what I do wrong. If possible could you please help?
> webpack serve

ℹ ｢wds｣: Project is running at http://localhost:3333/
ℹ ｢wds｣: webpack output is served from undefined
ℹ ｢wds｣: Content not from webpack is served from /Users/igor/Projects/yaml-test/src
✖ ｢wdm｣: 1 asset
46 modules

ERROR in ./node_modules/yaml/browser/dist/index.js 1:0
Module parse failed: 'import' and 'export' may appear only with 'sourceType: module' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> import { d as defaultTagPrefix, _ as _createForOfIteratorHelper, a as _typeof, b as _createClass, c as _classCallCheck, e as _defineProperty, Y as YAMLSyntaxError, T as Type, f as YAMLWarning, g as YAMLSemanticError, h as _slicedToArray, i as YAMLError, j as _inherits, k as _createSuper } from './PlainValue-ff5147c6.js';
| import { parse as parse$1 } from './parse-cst.js';
| import { b as binaryOptions, a as boolOptions, i as intOptions, n as nullOptions, s as strOptions, N as Node, P as Pair, S as Scalar, c as stringifyString, A as Alias, Y as YAMLSeq, d as YAMLMap, M as Merge, C as Collection, r as resolveNode, e as isEmptyPath, t as toJSON, f as addComment } from './resolveSeq-04825f30.js';

webpack 5.3.2 compiled with 1 error in 4332 ms
ℹ ｢wdm｣: Failed to compile.

Webpack config:
const HtmlWebpackPlugin = require('html-webpack-plugin')

const path = require('path');

const srcDir = path.resolve(__dirname, 'src');

module.exports = {
  entry: `${srcDir}/index.js`,
  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: '[name].[contenthash].js',
  },
  devtool: 'source-map',
  module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: {
          loader: 'babel-loader',
          options: {
            presets: ['@babel/preset-env']
          }
        }
      }
    ]
  },
  plugins: [
    new HtmlWebpackPlugin({template: 'src/index.html'}),
  ],
  devServer: {
    port: 3333,
    contentBase: srcDir,
    stats: 'minimal',
    hot: true,
    inline: true,
  },
};

package.json
{
  "name": "yaml-test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "dependencies": {
    "yaml": "^1.10.0"
  },
  "devDependencies": {
    "@babel/core": "^7.12.3",
    "@babel/preset-env": "^7.12.1",
    "@webpack-cli/serve": "^1.0.1",
    "babel-loader": "^8.1.0",
    "html-webpack-plugin": "^4.5.0",
    "webpack": "^5.3.2",
    "webpack-cli": "^4.1.0",
    "webpack-dev-server": "^3.11.0"
  },
  "scripts": {
    "start": "webpack serve"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

index.js
import YAML from 'yaml';

console.log(YAML.parse('1'));

I have the same problem here.

Huh, looks like Webpack 5 cares about the package.json "type" field, which it didn't before. Such will need to be added to the browser/dist/ directory of yaml, but in the meantime (or for yaml@1), adding this to your module.rules should make it work:
{ test: /\.js$/, type: 'javascript/auto' }

If you'd prefer to make the test really specific, use /node_modules\/yaml\/browser\/dist\/.*/.

@eemeli thanks. type: 'javascript/auto' works.
But more specific, as I understand, exclude does not work.

@eemeli thanks. type: 'javascript/auto' works.

👍

But more specific, as I understand, exclude does not work.

I'm sorry, I don't think I quite understood what you meant here?

I thought you suggest to add /node_modules\/yaml\/browser\/dist\/.*/ to exclude (read inattentively 😄). But then I realize that I need to change rule test property. So in my work project I just add another rule to handle yamlspecifically.
      {
  test: /node_modules\/yaml\/browser\/dist\/.*/,
  type: 'javascript/auto',
  use: {
    loader: 'babel-loader',
    options: {
      presets: [
        '@babel/preset-env',
      ],
    },
  },
}

Thanks

@eemeli Confirmed this works! Thanks for the solution!

@eemeli I think there's still a problem here...browser/index.js is requireing an ES module, which is not kosher anymore AFAIK.
package.json
  "browser": {
    "./index.js": "./browser/index.js",

./browser/index.js
module.exports = require('./dist').YAML

./browser/dist/index.js
import { d as defaultTagPrefix, _ as _createForOfIteratorHelper, a as _typeof, b as _createClass, c as _classCallCheck, e as _defineProperty, Y as YAMLSyntaxError, T as Type, f as YAMLWarning, g as YAMLSemanticError, h as _slicedToArray, i as YAMLError, j as _inherits, k as _createSuper } from './PlainValue-ff5147c6.js';
import { parse as parse$1 } from './parse-cst.js';

@eemeli I think there's still a problem here...browser/index.js is requireing an ES module, which is not kosher anymore AFAIK.
package.json
  "browser": {
    "./index.js": "./browser/index.js",

./browser/index.js
module.exports = require('./dist').YAML

./browser/dist/index.js
import { d as defaultTagPrefix, _ as _createForOfIteratorHelper, a as _typeof, b as _createClass, c as _classCallCheck, e as _defineProperty, Y as YAMLSyntaxError, T as Type, f as YAMLWarning, g as YAMLSemanticError, h as _slicedToArray, i as YAMLError, j as _inherits, k as _createSuper } from './PlainValue-ff5147c6.js';
import { parse as parse$1 } from './parse-cst.js';

@jedwards1211 Are you getting an error with Webpack 5 when using the type: 'javascript/auto' setting, or is it a matter of suspecting that some problem exists?
And you're right, you can't require() an ES module in Node.js, which is why that isn't done in the build of the library that Node.js gets. But it is fine with Webpack and Rollup -- unless I'm mistaken and you can provide some reproducible error case?

@jedwards1211 Are you getting an error with Webpack 5 when using the type: 'javascript/auto' setting, or is it a matter of suspecting that some problem exists?
And you're right, you can't require() an ES module in Node.js, which is why that isn't done in the build of the library that Node.js gets. But it is fine with Webpack and Rollup -- unless I'm mistaken and you can provide some reproducible error case?

What I mean is I think if you make both files use the same source type, whether it's module or script, we wouldn't have to use any special configuration for webpack to accept it.

What I mean is I think if you make both files use the same source type, whether it's module or script, we wouldn't have to use any special configuration for webpack to accept it.

Okay I was experimenting with the installed package.json.  Unfortunately even if I indicate ES modules like this:
  "exports": {
    ".": {
      "browser": {
        "import": "./browser/dist/index.js"
      }
    },
  },

Webpack 5 still complains 'import' and 'export' may appear only with 'sourceType: module', which seems like a bug.
To make matters worse Webpack 5 doesn't seem to interpret the condition-then-path style of nesting correctly:
  "exports": {
    "browser": {
      "import": {
        ".": "./browser/dist/index.js"
      }
    },
  },

This is a valid way of declaring conditional exports for Node at least according to https://nodejs.org/api/packages.html#packages_nested_conditions
but Webpack complains that "package path . is not exported" in this case.

Okay I was experimenting with the installed package.json.  Unfortunately even if I indicate ES modules like this:
  "exports": {
    ".": {
      "browser": {
        "import": "./browser/dist/index.js"
      }
    },
  },

Webpack 5 still complains 'import' and 'export' may appear only with 'sourceType: module', which seems like a bug.
To make matters worse Webpack 5 doesn't seem to interpret the condition-then-path style of nesting correctly:
  "exports": {
    "browser": {
      "import": {
        ".": "./browser/dist/index.js"
      }
    },
  },

This is a valid way of declaring conditional exports for Node at least according to https://nodejs.org/api/packages.html#packages_nested_conditions
but Webpack complains that "package path . is not exported" in this case.

Actually I was wrong, things have gotten too complicated 😭
This is valid, but I guess only when there are no subpath exports:
  "exports": {
    "node": {
      "import": "./feature-node.mjs",
      "require": "./feature-node.cjs"
    },
    "default": "./feature.mjs",
  }

Actually I was wrong, things have gotten too complicated 😭
This is valid, but I guess only when there are no subpath exports:
  "exports": {
    "node": {
      "import": "./feature-node.mjs",
      "require": "./feature-node.cjs"
    },
    "default": "./feature.mjs",
  }

Okay, sorry for all the messages but I'm slowly figuring this out.  The problem is "type": "commonjs" in your package.json causes all .js files to be parsed as CommonJS, including the ones that are supposed to be ES modules in browser/dist.
I had assumed that the "import" condition in conditional exports would automatically make both treat the file as an ES Module, but bizarrely, this is not the case.
It seems like the best thing would be to use .mjs for all ES modules in dist.  Then Node and Webpack 5 would be more likely to interpret them correctly without special configuration.

Okay, sorry for all the messages but I'm slowly figuring this out.  The problem is "type": "commonjs" in your package.json causes all .js files to be parsed as CommonJS, including the ones that are supposed to be ES modules in browser/dist.
I had assumed that the "import" condition in conditional exports would automatically make both treat the file as an ES Module, but bizarrely, this is not the case.
It seems like the best thing would be to use .mjs for all ES modules in dist.  Then Node and Webpack 5 would be more likely to interpret them correctly without special configuration.

As an experiment, could you apply locally the fix of bc4929c, which was the commit that closed this issue? As in, leave the root package.json untouched and add a file browser/dist/package.json with the following single line of contents?
{ "type": "module" }

As an experiment, could you apply locally the fix of bc4929c, which was the commit that closed this issue? As in, leave the root package.json untouched and add a file browser/dist/package.json with the following single line of contents?
{ "type": "module" }

Ah I didn't notice that commit.  That would probably work for the root import, but it wouldn't work for some subpath imports because some of the files in browser/ not browser/dist/ are ES modules.  I don't understand why a mix of CommonJS and ES modules is being used inside browser/.

Ah I didn't notice that commit.  That would probably work for the root import, but it wouldn't work for some subpath imports because some of the files in browser/ not browser/dist/ are ES modules.  I don't understand why a mix of CommonJS and ES modules is being used inside browser/.

Huh, I'd forgotten about browser/types.js and browser/util.js being ES. browser/index.js and browser/parse-cst.js were converted (back) to CommonJS due to #163, but that didn't affect the other two. In general, I much prefer keeping browser stuff as ES whenever possible, as bundlers generate clearly less scaffolding around such modules.
Will need to think of a solution for those files as well, and properly look at how Webpack 5 handles things.

Huh, I'd forgotten about browser/types.js and browser/util.js being ES. browser/index.js and browser/parse-cst.js were converted (back) to CommonJS due to #163, but that didn't affect the other two. In general, I much prefer keeping browser stuff as ES whenever possible, as bundlers generate clearly less scaffolding around such modules.
Will need to think of a solution for those files as well, and properly look at how Webpack 5 handles things.

Okay I looked through #163 and the code, looks like you've changed the export structure in browser/dist some recently too.
I think this would work:
browser/package.json
{
  "type": "module"
}

browser/index.js
export * as default from './dist'
export * from './dist'

Then I believe all of the following ways of importing would work with bundlers (assuming they support all export from syntaxes?):
require('yaml').stringify(...)

import YAML from 'yaml'
YAML.stringify(...)

import * as YAML from 'yaml'
YAML.stringify(...)

import {stringify as stringifyYaml} from 'yaml'
stringifyYaml(...)

browser/parse-cst.js though
As far as browser/parse-cst.js, if we convert that to
export { parse as default } from './dist/parse-cst'

I forget bundlers will make require('yaml/parse-cst') return the parse function in that case?

Okay I looked through #163 and the code, looks like you've changed the export structure in browser/dist some recently too.
I think this would work:
browser/package.json
{
  "type": "module"
}

browser/index.js
export * as default from './dist'
export * from './dist'

Then I believe all of the following ways of importing would work with bundlers (assuming they support all export from syntaxes?):
require('yaml').stringify(...)

import YAML from 'yaml'
YAML.stringify(...)

import * as YAML from 'yaml'
YAML.stringify(...)

import {stringify as stringifyYaml} from 'yaml'
stringifyYaml(...)

browser/parse-cst.js though
As far as browser/parse-cst.js, if we convert that to
export { parse as default } from './dist/parse-cst'

I forget bundlers will make require('yaml/parse-cst') return the parse function in that case?


[Bug]: AttributeError: 'list' object has no attribute 'on_error'

Do you need to file an issue?

[x] I have searched the existing issues and this bug is not already filed.
[x] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
[x] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the bug
Sometimes when I try to build_index, I'm getting the following:
index_result = await api.build_index(config=my_config) # this is me calling it
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/graphrag/api/index.py", line 73, in build_index
async for output in run_pipeline_with_config(
File "/usr/local/lib/python3.12/site-packages/graphrag/index/run/run.py", line 172, in run_pipeline_with_config
async for table in run_pipeline(
File "/usr/local/lib/python3.12/site-packages/graphrag/index/run/run.py", line 277, in run_pipeline
cast("WorkflowCallbacks", callbacks).on_error(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'on_error'

Not sure if there's anything I can do to fix it in my side...
Steps to reproduce
This is happening very rarely, tbh. I didn't find a consist that makes it appear.
Expected Behavior
Index should be done normally.
GraphRAG Config Used
# Paste your config here
async_mode: threaded
cache:
  base_dir: cache
  type: file
chunks:
  group_by_columns:
  - id
  overlap: 0
  size: 600
claim_extraction:
  description: Any claims or facts that could be relevant to information discovery.
  enabled: false
  max_gleanings: 1
  prompt: prompts/claim_extraction.txt
cluster_graph:
  max_cluster_size: 10
community_reports:
  max_input_length: 8000
  max_length: 2000
  prompt: prompts/community_report.txt
drift_search:
  prompt: prompts/drift_search_system_prompt.txt
embed_graph:
  enabled: false
embeddings:
  async_mode: threaded
  llm:
    api_key: ${GRAPHRAG_API_KEY}
    model: text-embedding-3-small
    type: openai_embedding
  vector_store:
    container_name: default
    db_uri: output/lancedb
    overwrite: true
    type: lancedb
encoding_model: cl100k_base
entity_extraction:
  entity_types:
  - organization
  - person
  - geo
  - event
  max_gleanings: 1
  prompt: prompts/entity_extraction.txt
global_search:
  knowledge_prompt: prompts/global_search_knowledge_system_prompt.txt
  map_prompt: prompts/global_search_map_system_prompt.txt
  reduce_prompt: prompts/global_search_reduce_system_prompt.txt
input:
  base_dir: input
  file_encoding: utf-8
  file_pattern: .*\.txt$
  file_type: text
  type: file
llm:
  api_key: ${GRAPHRAG_API_KEY}
  model: gpt-4o-mini
  model_supports_json: true
  type: openai_chat
local_search:
  prompt: prompts/local_search_system_prompt.txt
parallelization:
  stagger: 0.3
reporting:
  base_dir: logs
  type: file
skip_workflows: []
snapshots:
  embeddings: false
  graphml: false
  transient: false
storage:
  base_dir: output
  type: file
summarize_descriptions:
  max_length: 500
  prompt: prompts/summarize_descriptions.txt
umap:
  enabled: false
update_index_storage: null

Logs and screenshots
No response
Additional Information

GraphRAG Version: 0.9.0
Operating System: Linux
Python Version: 3.12.7
Related Issues: didn't find anything like it

@NathanAP  I created my first graphrag project this morning and am running in the same problem. My steps are below and mostly from the getting started steps...
environment: Windows / Azure OpenAI

Create a local folder
pip install poetry
poetry init
poetry shell
pip install graphrag
mkdir -p ./ragtest/input
curl https://www.gutenberg.org/cache/epub/24022/pg24022.txt -o ./ragtest/input/book.txt
Modify .env file with my AOAI key
Modify the settings.yaml file under "llm:" block. I modified the embedding block first and missed the first one.
graphrag index --root ./ragtest
I got the error ***
I modified the settings.yaml file under the FIRST llm block
I got the error ***

Other than running the index first and failing once due to not having the correct settings, it is pretty clean repro steps

In my case I'm using always the same file(s) to index it because we're using Playwright to make some end to end tests. This morning I got 3 times in a row this same error and then never happened again...
TBH I have no idea if this is in our control to manage.

me too

same here, i just updated and found this bug

Can someone with this error upload an indexing-engine.log so we can see the stack trace? I had the error myself yesterday with a largish dataset, and it was due to too many API requests (mine was on Azure OpenAI). It does not seem consistency, so may be temporary instability issues?

@natoverse settings.yaml
llm:
  # exllamav2
  api_key: ${GRAPHRAG_API_KEY}
  type: openai_chat # or azure_openai_chat
  model: Rombos-LLM-V2.5-Qwen-32b-4.5bpw-exl2
  model_supports_json: true # recommended if this is available for your model.
  max_tokens: 16000
  api_base: http://<IP_ADDRESS>:5001/v1
  requests_per_minute: 5_000 # set a leaky bucket throttle
  max_retries: 10
  max_retry_wait: 0

graphrag 1.0 does not call the api_base inside llm, and uses the default api_base of openai, resulting in model authentication errors,The error log is as follows:
11:34:31,347 httpx INFO HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 401 Unauthorized"

I've just setup Graphrag and was seeing this trying to go through the Getting Started example.   I did review the indexing-engine.log and found a couple of things:
My initial problem was the my deployments string was incorrect.  This was resulting in a 404 error the request to do the chat completion while extracting the graph  - The full URL with the issue was in the and I compared it to a working URL I had from test code and found my issue  (I had the deployment name incorrect --  I was using the azure resource name and it needed to be the openai deployment name  (in my case gpt-4_1  (I'm using azure openai).
I got thorough that and it make it further but I started getting it later in the process, but now I'm seeing a 429 error (rate limit error)
For references both case  ended up with the list error  in the -- but  that looks like a secondary error that occurred while processing another error.  In my case the first error was a key error on the key 'name'    I'm suspecting that the call to the LLM fails and so there is no data, which causes the key error (and then the list error occurs during the handling of the key error)

Refer to this fix
https://github.com/microsoft/graphrag/pull/1508

same error, how to fix it?

yeah guys me too fr fr

the same error for me...

Can someone with this error upload an indexing-engine.log so we can see the stack trace? I had the error myself yesterday with a largish dataset, and it was due to too many API requests (mine was on Azure OpenAI). It does not seem consistency, so may be temporary instability issues?

Below is my indexing.log, it is clean as I only run it once. I am using gpt-4o from openai and the document is about some video description. @natoverse
indexing-engine.log

@YepJin
I notice that the first error in your log is:
13:31:33,876 graphrag.index.graph.extractors.graph.graph_extractor ERROR error extracting graph
Traceback (most recent call last):
File "/home/klwonder/vscode/graphrag_v3/.venv/lib/python3.12/site-packages/graphrag/index/graph/extractors/graph/graph_extractor.py", line 127, in call
result = await self._process_document(text, prompt_variables)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/klwonder/vscode/graphrag_v3/.venv/lib/python3.12/site-packages/graphrag/index/graph/extractors/graph/graph_extractor.py", line 156, in _process_document
self._extraction_prompt.format(**{
KeyError: '"LOW AUTHENTIC VIDEO", \n"MODERATE LOW AUTHENTIC VIDEO","MEDIUM VIDEO","MODERATE HIGH AUTHENTIC VIDEO","HIGH AUTHENTIC VIDEO"'
I also notice that the Key error seems to be for the entire string (everything between the single quotes), so maybe this is an issue in some entry in the  settings.yaml?  Are these items (e.g. "LOW AUTHENTIC VIDEO", etc) configured as there in some way or in a format that it can't handle properly  or doesn't like  (are these your entity types?)  ...  its seems to be taking what looks like it should several different entries and treating it as one item

I used my own prompts and not limit the entity types. It worked perfectly before I update it (previously I used the version without Drift search).

@YepJin I notice that the first error in your log is: 13:31:33,876 graphrag.index.graph.extractors.graph.graph_extractor ERROR error extracting graph Traceback (most recent call last): File "/home/klwonder/vscode/graphrag_v3/.venv/lib/python3.12/site-packages/graphrag/index/graph/extractors/graph/graph_extractor.py", line 127, in call result = await self._process_document(text, prompt_variables) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/klwonder/vscode/graphrag_v3/.venv/lib/python3.12/site-packages/graphrag/index/graph/extractors/graph/graph_extractor.py", line 156, in _process_document self._extraction_prompt.format(**{ KeyError: '"LOW AUTHENTIC VIDEO", \n"MODERATE LOW AUTHENTIC VIDEO","MEDIUM VIDEO","MODERATE HIGH AUTHENTIC VIDEO","HIGH AUTHENTIC VIDEO"'
I also notice that the Key error seems to be for the entire string (everything between the single quotes), so maybe this is an issue in some entry in the settings.yaml? Are these items (e.g. "LOW AUTHENTIC VIDEO", etc) configured as there in some way or in a format that it can't handle properly or doesn't like (are these your entity types?) ... its seems to be taking what looks like it should several different entries and treating it as one item

Just change two things in settings.yaml:
Add the following to the llm:
api_base: https://api...... (Your website)
api_proxy: https://api......
Add llm in embeddings as follows:
api_base: https://api......
proxy: https://api......

this can happend if your api key is not valid for accessing the embedding api. try generating a new key in OpenAI and retrying ---- this will be evident in the log file

Hmm but then this error would be consistent, wouldn't? I'm getting this error 30% of my index attempts, its not happening everytime. Seems like some instability

@NathanAP Sounds like a rate limiting issue?

Seems like a bug in GraphRag code. I'm always using the same files.

有解决了这个问题的friend吗？

We believe this was a bug introducing during our adoption of fnllm as the underlying LLM library. We just pushed out a 1.0.1 patch today, please let if know if your problem still exists with that version.

🔥修改代码就可以解决 https://youtu.be/GRZ2th6s7uY


Invoke decorate in multi with selection, data and index

Resolves #890

Thanks @jleft - you're on a roll at the moment!


Common test specification document

This PR adds a common test specification document, as described by #4. This does not yet close the issue, as this does not add required test-setup to the current template, which will be done in a follow-up PR.
This is a work in progress, do NOT merge yet.

@joluj Can you please review.


NLog Integration to S3

Do you support integrating to AWS S3? If not any plan to support S3 in your road map? Also if we need to integrate to S3 what is your guidance?

NLog-repository doesn't contain any vendor specific integrations. But if you cannot find anything with google, then one create a custom target and use the AmazonS3Client.

sure @snakefoot

Closing question as resolved. If you find (or build) a nuget-package then you can always post a link here.


After simple setup: Missing mandatory keyword argument 'view_root' in constructor call

I followed the simple setup as documented in the README but bump into this error when doing poetry run runserver.
Error:
Missing mandatory keyword argument 'view_root' in constructor call

Hey @hoetmaaiers thanks for the report. What version of mountaineer / create-mountaineer-app are you using? If you're in a poetry environment you should be able to run:
poetry run pip freeze | grep mountaineer

I'm seeing that CMA is still pinned to version 0.1.x. Will push a patch for this in a second. In the meantime, you should be able to unblock yourself by modifying the pyproject.toml to pull the latest released version. In this version we removed the need to explicitly provide view_root.
[tool.poetry.dependencies]
python = "^3.11"
mountaineer = "^0.2.0"

So no need to rerun the pipx create xxx step?

No, just bump your pyproject.toml and bump the poetry deps:
vi pyproject.toml
poetry lock
poetry install
poetry run runserver

sorry, just removed my comment about rerunning using pipx run create-mountaineer-app

I also just pushed a beta that shouldn't require this manual workaround anymore. This will land in the stable 0.3.0, which should drop in the next couple days or so. In the meantime, you can try the new CMA via the pre-release.
pipx run create-mountaineer-app==0.3.0.dev2


SSL configuration is Running - [BRIEF DESCRIPTION]

App Id: dl87ize9f7mmi
Region: us-east-1
Step: SSL configuration
Status: Running

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Now I solve this issue.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.

Refer to our documentation to troubleshoot domain setup.
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html#i-get-a-cnamealreadyexistsexception-error
Let us know if you're still facing issues.


What filetype if nui windows?

Discussed in https://github.com/MunifTanjim/nui.nvim/discussions/243

Originally posted by RAprogramm March 17, 2023
Screencast_00003.webm
when opening any nui window - lualine looks like no good (tell that is not git repository but it is). to disable it i need to know filetype or buf type of nui. but i can't get it.
help me please
buf_options = { filetype = 'prompt' } - this will decide my problem, BUT where i can paste it?
somewere in init options?

Duplicate of https://github.com/MunifTanjim/nui.nvim/discussions/243


Integration stopped reporting values

It worked initially, but after a few days it reports "Niet beschikbaar" (not available). I tried reinstalling (and restarting HA) but that did not help. Is there anything I can do to pinpoint the problem?

Do you see anything in the logs?

Enable extra logging if you currently do not see anything
Add to config/configuration.yaml
logger:
  logs:
    custom_components.zonneplan_one: debug

It's complaining about the authentication:
2021-04-09 08:38:20 ERROR (MainThread) [custom_components.zonneplan_one.coordinator] Error requesting zonneplan_one data: 401, message='Unauthorized', url=URL('https://app-api.zonneplan.nl/oauth/token')

I probably need to login again. Can I use the same account as I'm using for the Zonneplan App on my phone? Or should I create a separate account for the HA integration?

I use the same account as the I use for the app.
Try to remove the integration and re-add it again.
If for some reason the request for a new token was made but for some reason the request couldn't be correctly processed this 401 can happen. Happened to me to during my first tests. Removing and re-adding it again so you go through the login process again should solve it

Yes, It started working again by removing and re-adding it again!

I had the same as well (second time). All available logs:
2021-04-16 20:12:52 INFO (MainThread) [custom_components.zonneplan_one.coordinator] _async_update_data: start
2021-04-16 20:12:52 INFO (MainThread) [custom_components.zonneplan_one.zonneplan_api.api] _async_request_new_token: {'grant_type': 'refresh_token', 'refresh_token': 'def5020080c531d46ae276b4b08c7c6cd3fdac091820a8cf684aa49670ec015940f5d732e1f9c067b5c517f239baef79e4f245ae091b869d458133de44e1bb334a524afe19936a837669610207087e6918f42d147557db40f05de22bb4a353a268b566e89a3499c3e856becce264043d8172d46f21fae128391e2cd07812040aef1a548bc3b81a1ec57847a447..........
2021-04-16 20:12:52 DEBUG (MainThread) [custom_components.zonneplan_one.zonneplan_api.api] ZonneplanAPI response header: <CIMultiDictProxy('Date': 'Fri, 16 Apr 2021 18:12:52 GMT', 'Server': 'Apache', 'Cache-Control': 'no-cache, private', 'X-RateLimit-Limit': '10', 'X-RateLimit-Remaining': '9', 'Upgrade': 'h2,h2c', 'Connection': 'Upgrade', 'Transfer-Encoding': 'chunked', 'Content-Type': 'application/json')>
2021-04-16 20:12:52 DEBUG (MainThread) [custom_components.zonneplan_one.zonneplan_api.api] ZonneplanAPI response status: 401
2021-04-16 20:12:52 ERROR (MainThread) [custom_components.zonneplan_one.coordinator] Error requesting zonneplan_one data: 401, message='Unauthorized', url=URL('https://app-api.zonneplan.nl/oauth/token')
2021-04-16 20:12:52 DEBUG (MainThread) [custom_components.zonneplan_one.coordinator] Finished fetching zonneplan_one data in 0.304 seconds


please add Paris Junior College

@testibig93 Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Sample reported to have issue

https://twitter.com/wxs/status/668266345625088000
Wesley Shields @wxs
getnetguids is broken for multiple metadata magic values (embedded binaries). e.g: a6aa53ce8dd5ffd7606ec7e943af41eb (CC: @botnet_hunter)

My dotnet branch of YARA is reporting a GUID of 2a36943f-7da0-43e2-923a-34ea03ba898d, just FYI. I suspect my code is correct.

I believe your code is correct as well.

I believe your assertion on Twitter was correct, this appears to be caused by the .NET resource "Internet", as it has the MVID that is reported (FD48D238-5112-4BB8-BF85-2DEC34557D6F).  I'm exploring methods to resolve this.

I believe I have a solution to this, but it is still in testing.
In early (pre-Github) versions of GetNETGUIDs, strict PE parsing was used, but due to differences between the specification and actually functional CLR, I reverted to less strict matching.
In this fix, both are utilized, where the strict method is attempted first, then the less strict method is used if the first fails to recover the MVID at the least.

I'd love if you could elaborate on differences between the specification and in the wild samples? Even better if you can point me at a hash or two that were giving you problems. I'd love more "weird" cases to test my YARA branch with.

In your YARA branch, are you using one of the .NET methods mentioned here? https://www.virusbtn.com/virusbulletin/archive/2015/06/vb201506-NET-GUIDs  Those are the best methods I know of, although loading assemblies in .NET can be dangerous.
Weird njRat sample: 664c599ccec5040c3ae4832c2e0458bb11b2eccd0e6a7eeafce0a49ccc07bec1

No. It is a YARA module which is a custom parser written in C. It doesn't "load" anything from the binary.
I'll try and take a look at the sample mentioned above tomorrow to make sure I get correct results. I also noticed in #2 that you mention a different sample. I'll take a look at that one too to make sure my code is correct. Thanks for pointing both of them out!

No problem.  That's awesome that you are doing it in C.  Is that code available on Github yet?  I would be interested in seeing how you are handling the parsing.

Yeah, it's here: https://github.com/wxsbsd/yara/tree/dotnet. The actual code (if you are familiar with YARA modules) is here: https://github.com/wxsBSD/yara/blob/dotnet/libyara/modules/dotnet.c.


Add proposal for circuit breaker

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

I didnot see the response recording, how could we achieve that?

I didnot see the response recording, how could we achieve that?

can we use this https://github.com/weaveworks-plugins/scope-http-statistics/blob/master/ebpf-http-statistics.c?
I'm busy for taking examines these two weeks, so my progress may be slow recently.

Can we maintain a statistic structure map in ebpf (so that can be accessed in user space), recording http statistic information like: number of connections, number of requests. We hook some functions in ebpf to collect this info, and we can do circuit breaker logic using golang in user space.

Agree, there need response handling

Mostly LGTM, so outlier detection can be designed separately

Yes, I think so.


Expo SDK 51: AirGoogleMaps dir must be added to your xCode project to support GoogleMaps on iOS

Summary
After upgrading to Expo SDK 51, and using Expo Go, we receive the following error. We did not have this error with SDK 50.

Reproducible sample code
import MapView, { PROVIDER_GOOGLE } from 'react-native-maps'

<MapView
    provider={PROVIDER_GOOGLE}
/>

Steps to reproduce
Start an Expo SDK 51 project, with the managed flow.
Run the app via Expo Go
Use provider google
Expected result
The map renders
Actual result
We get an error, saying a native dependency is missing.
But since this is Expo managed, it should be fixed with them.
React Native Maps Version
1.14.0
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.74.1
What version of Expo are you using?
SDK 48
Device(s)
iPhone SE 3 (simulator), iPhone 14 Pro Max (device)
Additional information
No response

I have the same issue, is there any way to fix it?

I have the same issue.
Default provider works fine on my apple device but renders Apple Maps

+1

Same issue here +1

Facing the same issue here.

Same issue here!!!

I'm facing the same issue. Version 50 worked perfectly..... and iOS is forcing an update to version 51.

Same here

Me too. Glad to know I'm not alone!

Hi there! Google Maps is no longer supported in Expo Go for iOS. You can use Apple Maps in Expo Go instead (remove the prop provider={PROVIDER_GOOGLE} from your <MapView />  components) or switch to a development build (recommended). If you have already configured Google Maps for your production releases, no additional configuration will be necessary. Learn how to set up a development build.
A few things to note about Expo Go:

Expo Go is intended to be a sandbox environment, and we recommend using development builds for any real app. The "Set up your environment" guide will help you get set up with a development build. We also have a full EAS tutorial if you want to learn more, and a concise video course that you can pick and choose lessons from as they are relevant to your use case.
Development builds give you full control over the native runtime (you can write native code or include any library you like), they are much closer to your production environment, and you can update SDK versions at whichever pace works for you.
You can still install Expo Go for any SDK version on Android emulators, Android devices, and iOS simulators. We've made the process for doing this as easy as possible on https://expo.dev/go.

I guess I have to switch to native because that was the only reason I used Expo... 😒

@elisabeth0bangoura - I guess I have to switch to native because that was the only reason I used Expo... 😒

I'm not sure I understand your comment :) Expo is much more than the "Expo Go" app - the sandbox app for experimenting and learning. I encourage you to take a look at development builds - which are like a version of Expo Go that you have full control over.
Ultimately, if you prefer to use other tooling, you should do what is best for you!

@elisabeth0bangoura - I guess I have to switch to native because that was the only reason I used Expo... 😒

I'm not sure I understand your comment :) Expo is much more than the "Expo Go" app - the sandbox app for experimenting and learning. I encourage you to take a look at development builds - which are like a version of Expo Go that you have full control over.
Ultimately, if you prefer to use other tooling, you should do what is best for you!

Many developers were initially attracted to Expo for its simplicity, especially for testing features like maps quickly. However, recent changes may have made the development process feel more complex.
Will Google Maps work in Build development?

That's crazy. Picture using development build on simulator on your laptop then expo go on your phone.
Lol this just made things way more complicated. Damn. Thanks for the update tho!

That's crazy. Picture using development build on simulator on your laptop then expo go on your phone.
Lol this just made things way more complicated. Damn. Thanks for the update tho!

True!!!!
But I tested it on Build Development and Google Maps on IOS is working there. But yeah they made it so complicated now and with all these files...

Yeah because for me, I’m doing like a multi app setting, so I need 2 apps open at the same time. Just was easier that way, but meh, can simple just do a constants check if in __DEV__ to use not use google maps provider and just have production / dev builds use google.
<3

@karimcambridge: That's crazy. Picture using development build on simulator on your laptop then expo go on your phone.
Lol this just made things way more complicated. Damn. Thanks for the update tho!

you can create a development build for your phone, most developers using them do this! https://docs.expo.dev/get-started/set-up-your-environment/?platform=ios&device=physical&mode=development-build

Why is this issue closed? I don't use Expo Go, I ejected Expo a long time ago and I have the same issue. If there is a way to fix it on xCode please share it.

@lluisandreu - because the issue says in the first line of the summary:

After upgrading to Expo SDK 51, and using Expo Go, we receive the following error.

if you are experiencing an issue related to this in another context, you should create a new issue and provide all of the relevant information

Hi there! Google Maps is no longer supported in Expo Go for iOS. You can use Apple Maps in Expo Go instead (remove the prop provider={PROVIDER_GOOGLE} from your <MapView />  components) or switch to a development build (recommended). If you have already configured Google Maps for your production releases, no additional configuration will be necessary. Learn how to set up a development build.
A few things to note about Expo Go:

Expo Go is intended to be a sandbox environment, and we recommend using development builds for any real app. The "Set up your environment" guide will help you get set up with a development build. We also have a full EAS tutorial if you want to learn more, and a concise video course that you can pick and choose lessons from as they are relevant to your use case.
Development builds give you full control over the native runtime (you can write native code or include any library you like), they are much closer to your production environment, and you can update SDK versions at whichever pace works for you.
You can still install Expo Go for any SDK version on Android emulators, Android devices, and iOS simulators. We've made the process for doing this as easy as possible on https://expo.dev/go.

@brentvatne thanks, anywhere where we can read up on the decision to remove this from Expo Go? Interested to know the Why.

I'm working with two apps using the react-native-maps package; both are with SDK 51, but the first app runs the MapView on iOS, but the second app doesn't.

@walker007 - that is not a problem. you can learn how to create a development build here: https://docs.expo.dev/get-started/set-up-your-environment/?platform=ios&device=physical&mode=development-build
learn more about developing an app with expo here: https://docs.expo.dev/workflow/overview/

is frustrating because it's unexpecte

@walker007 - that is not a problem. you can learn how to create a development build here: https://docs.expo.dev/get-started/set-up-your-environment/?platform=ios&device=physical&mode=development-build
learn more about developing an app with expo here: https://docs.expo.dev/workflow/overview/

ok, I'll try it, thank you

@brentvatne why is nothing about this mentioned here: https://docs.expo.dev/versions/latest/sdk/map-view/#deploy-app-with-google-maps

https://docs.expo.dev/get-started/set-up-your-environment/?platform=ios&device=physical&mode=development-build

Some of us use old Macs that can't update to macOS 14. We heavily relied on expo Go for development. You could've just displayed warnings or disclaimers about potential cases where behavior won't immediately transfer. Honestly, who wouldn't know that they need to use their own API credentials for google maps?

I have a development build + Google Maps API key but I am still getting this error

I also have a development build with API key and get the error

I also have a development build with API key and get the error

interestingly, Expo Go + Google Maps works fine on a virtual Android device, but doesn't work on an iOS simulator

thanks @brentvatne for taking the time to clarify what happened with the new Expo go release.
to everyone commenting here, this issue is not being tracked because the comments fall into two categories

complaining about the decision by the expo team (obviously out of scope)
describing a problem with expo itself (not expo go) with google maps (please submit a new issue).

@brentvatne why is nothing about this mentioned here: https://docs.expo.dev/versions/latest/sdk/map-view

They should add that in the docs

Just read de docs and follow the steps
https://docs.expo.dev/versions/latest/sdk/map-view/

because it used our Google API credentials, but when you create a development build or production build, it would no longer work and you would need to then create your own Google Maps credentials configure it. this is frustrating because it's unexpected and at this point you'll think you've already built support for maps, you may not have budgeted the time in for your release, or maybe you'll just give up and go back to Expo Go. the state we're moving towards is that, whenever possible, something that runs in Expo Go should run without changes in a development build.

Totally understand and much appreciated that this was so painless using your built in Google Map credentials for Expo Go....but if the reason was the credentials in a production build or development build did not transfer over, wouldn't that just be an easy fix?  like updating your app configs/environment variables in app.json?
To me I understand the reasoning but the solution seems really simple.  The ability to play with Google Maps in sandbox out the box outweighs what would just be a credentials update when switching over to development mode.

interestingly, Expo Go + Google Maps works fine on a virtual Android device, but doesn't work on an iOS simulator

I believe its because it defaults to the device provided map.  on iOS it would be Apple Maps and on Android OS it would be Google Map.  Unless you explicitly define the provider in your MapView

adding this just incase anyone needs the help i only ran into this issue running  "expo run:ios", but not "start": "expo start","expo start",

You guys should reconsider your choice to remove Google Maps for IOS. Apple maps cannot be styled and with google maps not working. I don't think theres a way to theme the app with the rest of the app. Light mode maps/dark mode maps etc.

You guys should reconsider your choice to remove Google Maps for IOS. Apple maps cannot be styled and with google maps not working. I don't think theres a way to theme the app with the rest of the app. Light mode maps/dark mode maps etc.

I was able to use Google maps. But I had to npx expo prebuild then I just followed the docs as if I were using a RN CLI.

You guys should reconsider your choice to remove Google Maps for IOS. Apple maps cannot be styled and with google maps not working. I don't think theres a way to theme the app with the rest of the app. Light mode maps/dark mode maps etc.

I was able to use Google maps. But I had to npx expo prebuild then I just followed the docs as if I were using a RN CLI.

Can you provide more info? Still getting the same error. You on Expo v 51?

You guys should reconsider your choice to remove Google Maps for IOS. Apple maps cannot be styled and with google maps not working. I don't think theres a way to theme the app with the rest of the app. Light mode maps/dark mode maps etc.

I was able to use Google maps. But I had to npx expo prebuild then I just followed the docs as if I were using a RN CLI.

Can you provide more info? Still getting the same error. You on Expo v 51?

Once you run  npx expo prebuild, it will create the folders for both Android and iOS then just follow this doc - https://github.com/react-native-maps/react-native-maps/blob/master/docs/installation.md

@jmejiamu Thank you ! 🚀

I agree with @jmejiamu—running Google Maps with react-native-maps in Expo command no longer works as expected. To resolve this, I ran:
npx expo prebuild

Next, I opened ios/MyProject.xcworkspace in Xcode, navigated to the AppDelegate.mm file, and added my Google Maps API key following the instructions in the react-native-maps installation guide.
After launching the app from Xcode to the simulator, Google Maps rendered correctly.

I agree with @jmejiamu—running Google Maps with react-native-maps in Expo command no longer works as expected. To resolve this, I ran:
npx expo prebuild

Next, I opened ios/MyProject.xcworkspace in Xcode, navigated to the AppDelegate.mm file, and added my Google Maps API key following the instructions in the react-native-maps installation guide.
After launching the app from Xcode to the simulator, Google Maps rendered correctly.

I'm also directly using development build, not Expo Go, but got hit with the same error. @WayneJWZLemon's fix worked for me. To further add onto the description:

After npx expo prebuild and adding the necessary lines mentioned in the guide, you could be prompted with the error 'GoogleMaps/GoogleMaps.h' file not found. To fix this, go to your Podfile (in the .iOS folder created by prebuild) and add   pod 'GoogleMaps'.
Combining with the instructions mentioned in the guide, what's actually needed is

  # React Native Maps dependencies
  rn_maps_path = '../node_modules/react-native-maps'
  pod 'react-native-google-maps', :path => rn_maps_path
  pod 'GoogleMaps'
  pod 'Google-Maps-iOS-Utils'

and it should be added before the function call use_native_modules
So in my case, the code looks like
target 'MyProject' do
  use_expo_modules!

  # React Native Maps dependencies
  rn_maps_path = '../node_modules/react-native-maps'
  pod 'react-native-google-maps', :path => rn_maps_path
  pod 'GoogleMaps'
  pod 'Google-Maps-iOS-Utils'

  config = use_native_modules!

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

after adding the snippet.
This helped fixing the issue for me.

This is the ENTIRE REASON I stopped using Expo with my Team YEARS AGO!  This is not a multi-platform solution, I should NEVER have to augment native code EVER. Whats the point in using Expo if I need to modify and maintain two code bases?? Please add this back.

For anyone encountering this and uses Expo, I wrote a config plugin https://www.npmjs.com/package/react-native-maps-expo-plugin to do this without you having to manually tweak files:
npm install react-native-maps-expo-plugin

Then add it to your app.json or app.config.js:
{
  "plugins": [
    [
      "react-native-maps-expo-plugin",
      {
        "googleMapsApiKey": "YOUR_GOOGLE_MAPS_API_KEY"
      }
    ]
  ]
}

Now you can generate the native code and build:
# Generate native code
npx expo prebuild

# Build and run on iOS
npx expo run:ios

# Or if using CNG workflow, use --clean to safely regenerate native files
npx expo prebuild --clean
npx expo run:ios

What is CNG?

Continuous Native Generation (CNG) is a process for building an Expo app where your native projects are generated on-demand from your app.json and package.json, similar to how your node_modules are generated from your package.json.
You can add the native project directories (android and ios) to your .gitignore and/or delete the project at any time, then re-generate them from the Expo app config with npx expo prebuild whenever required. You might never even run prebuild on your own development machine if you use a cloud-based development workflow.
Using CNG can make upgrading to new versions of React Native much easier. It can simplify project maintenance and facilitate setting up complex features such as App Clips, share extensions, and push notifications. This is all made possible with config plugins. Learn more about CNG.

Why this is better than tweaking the generated native files yourself:
Here's Expo documentation on why tweaking the files yourself is not a good idea: https://docs.expo.dev/workflow/overview/#what-if-i-want-to-edit-the.
In summary, the official react-native-maps installation requires manual modifications to native iOS files that get wiped out when using CNG (npx expo prebuild --clean). This plugin automatically handles:

Adding Google Maps pod to Podfile
Adding location permission to Info.plist
Initializing Google Maps in AppDelegate

In other words, it will do the react-native-maps installation instructions for you every time, so you can keep enjoying CNG!


Modify sed command usage to make it compatible with macos

Modify sed to use gnu-sed on macos as per this comment

There may be a couple places we use sed in the build scripts. I have alias sed=gsed but that shouldn't be a requirement for anyone using this stuff.

@TerryHowe I wasn't super clear in the issue description. I ran the script to build manifests locally on mac and the sed command needed some changes. Instead @abhay-krishna suggested adding in this change which based on the os picks sed or gsed for the command. so anyone running this locally wouldn't have to do anything additional

We do this in both existing and new scripts (if necessary).


Output file says - "it looks like we don't support this format"

I have a number of mhtml files produced from Microsoft Reporting Services - exporting a report to mhtml
The file can be viewed in Internet Explorer
I would like to export the mhtml to png (or jpg).  Are there settings required for this?
Here's the destination file:

Here's the code -
    Dim conversionOptions = New MimeConversionOptions With {
        .CompressCss = True,
        .CompressHtml = True,
        .CompressImages = True,
        .JpegCompressorQuality = 100,
        .MaxPngColors = 256
    }
    Dim converter = New MimeConverter(conversionOptions)

    Using sourceStream As FileStream = File.OpenRead(fi.FullName)
        Using destinationStream As FileStream = File.Open(DestinationFilePath, FileMode.Create)
            converter.Convert(sourceStream, destinationStream)
        End Using
    End Using

Unfortunatelly, no.
This this a file conversion utility that just takes mhtml files as input and outputs a single html file as output that could be opened in any browser.
My use case for it (actually, the reason why i created this tool it) is making html from headless chrome output . Probably, you should look here https://github.com/hardkoded/puppeteer-sharp -- this is the library for launching headless chrome, from which you can export page as an image:


File Nesting for Library Projects

File Nesting seems only available for Web Projects? how about Library and Console?

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

ID: 2d25dd44-f173-dd83-3afc-d6608613d450
Version Independent ID: e121cedc-5cbe-a399-e2a8-5d192aaea770
Content: File nesting rules for Solution Explorer - Visual Studio
Content Source: docs/ide/file-nesting-solution-explorer.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @AngelosP
Microsoft Alias: angelpe

@JmlSaul -- thank you for your questions.  Please consider these resources:

Visual Studio on Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit

@AngelosP -- please look into this issue.

That is correct, currently File Nesting is only supported in Web projects.

@AngelosP -- Angelos, thank you for clarifying.


Add a few guards around prerender errors

[#143883405]

Not sure if this is the idiomatic way to handle these, but it at least passes the linter.

          1 Warning

:warning:
Please provide a linked tracker story for this PR in the description

  Generated by :no_entry_sign: danger

Word 🤘


Inject bind variables in rails 4 with prepared_statements set to false

In non local envs disable prepared statements, manual SQL work relies on testing these code paths.
Allow Rails 4 to correctly inject the bind vars for the raw SQL
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

As per this Blog Post We Like (https://github.blog/2018-09-28-upgrading-github-from-rails-3-2-to-5-2/), we could leave both code paths in and switch on something like Panoptes.rails_5?. That would let us leave the newer syntax in so we don't have to remember to come back after the upgrade merges. But that only seems useful if the backward-compatible version of this is less performant or is otherwise compromising.
I'm for bundling the Travis updates with the SMS SQL changes if the PR name and desc are updated to reflect.

As per this Blog Post We Like (https://github.blog/2018-09-28-upgrading-github-from-rails-3-2-to-5-2/), we could leave both code paths in and switch on something like Panoptes.rails_5? (nothing seems to do anything like this right now, though). That would let us leave the newer syntax in so we don't have to remember to come back after the upgrade merges. But that only seems useful if the backward-compatible version of this is less performant or is otherwise compromising.
I'm for bundling the Travis updates with the SMS SQL changes if the PR name and desc are updated to reflect.

That sounds reasonable to put both code paths in to ensure our rails 5 code works as expected. Feel free to add the switch to this PR or i'll pick it up tomorrow.

A quick and dirty means of determining whether Rails 5 is running isn't pretty, but it works. This at least keeps the knowledge in the codebase, keeps it searchable, and is a decent shove toward doing the upgrade. We might want a nicer solution or maybe ten-years-rails has a better solution; I'm still going through it.
The best way to test the other half of this would be to merge https://github.com/zooniverse/Panoptes/pull/3128/ first, then rebase and run the test in 5. Not sure if there was more work on that to do on that PR, but that'd be a good place to start. That railsconf video in the desc of the ten-years-rails repo is pretty good too and I'm feeling very seen

I've tried something different with testing the Rails 5 AR interface vs the behaviour, rails 4 AR still tests behaviour.
I think this is good to go, we can revisit the tests in light of #3128 but this bug needs to be fixed asap.

Agreed it needs to be fixed, so :shipit:. Revisiting the upgrade and how we want to tackle it is worth its own discussion.


[Model] Initialize deepseek-vl support

Test On NVIDIA L40S

Test Example

from vllm import LLM
from PIL import Image

from vllm.multimodal.image import ImagePixelData
from vllm import SamplingParams

sample_params = SamplingParams(temperature=0, max_tokens=1024)

model_path = "deepseek-ai/deepseek-vl-7b-chat"

llm = LLM(
    model=model_path,
    image_input_type="pixel_values",
    image_token_id=100015,
    image_input_shape="1,3,1024,1024",
    image_feature_size=576,
    disable_image_processor=False,
    gpu_memory_utilization=0.9,
    max_model_len=3075,
    enforce_eager=True,
)
print("model load finish")
prompt = f"You are a helpful language and vision assistant. You are able to understand the visual content that the user provides, and assist the user with a variety of tasks using natural language.\n User: {'<image_placeholder>'*576} Describe each stage of this image detail.\nAssistant:"

image = Image.open("./images/training_pipelines.jpg")
image = image.convert("RGB")
outputs = llm.generate(
    {"prompt": prompt, "multi_modal_data": ImagePixelData(image)}, sample_params
)
for o in outputs:
    generated_text = o.outputs[0].text
    print(generated_text)

Output

The image depicts a three-stage process for training a vision-language model, as indicated by the labels at the top of each stage.

Stage 1: Training VL Adapter
In this stage, a DeepSeek LLM is used as the backbone for training a Vision-Language Adapter (VLA). The VLA is trained on a dataset of image-text pairs, which are represented by the blue square labeled "Image-Text Pairs." The VLA is a lightweight model that is trained to adapt the vision and language capabilities of the DeepSeek LLM.

Stage 2: Joint VL Pre-training
In this stage, the VLA is integrated into the DeepSeek LLM, which is now referred to as the "DeepSeek VLM." The VLM is pre-trained on a dataset of pure language sequences, represented by the gray square labeled "Pure Language Sequences." The goal of this stage is to combine the vision and language capabilities of the VLA with the larger language model, creating a more comprehensive vision-language model.

Stage 3: Supervised Fine-tuning
In this final stage, the VLM is fine-tuned on a dataset of pure language chat data, represented by the orange square labeled "Pure Language Chat Data." The fine-tuning process aims to adapt the model to perform well on tasks that involve understanding and generating human language in a conversational context.

Throughout all stages, the DeepSeek LLM is consistently used as the backbone model, with the VLA being integrated and adapted in each stage to enhance the model's vision-language capabilities. The visual clues in the image, such as the arrows connecting the stages and the labels, indicate the progression from training a separate adapter to integrating it into a larger model and then fine-tuning it for specific tasks.

FIX #3356
FIX #4982

Contributed by enflame-tech

now support deepseek-ai/deepseek-vl-7b-chat  deepseek-ai/deepseek-vl-1.3b-chat

This model depends on timm>=0.9.16, which depends on torch, but it will conflict with the dependencies of other third-party components and cause the pipeline to fail. Therefore, running this model requires additional installation. I don’t know if this is appropriate. In addition, it depends on many modules of timm, which is difficult to remove.

This model depends on timm>=0.9.16, which depends on torch, but it will conflict with the dependencies of other third-party components and cause the pipeline to fail. Therefore, running this model requires additional installation. I don’t know if this is appropriate. In addition, it depends on many modules of timm, which is difficult to remove.

Can you implement the individual timm modules inside vLLM? (where possible, you should use vLLM-specific layers to improve the performance anyway)

This model depends on timm>=0.9.16, which depends on torch, but it will conflict with the dependencies of other third-party components and cause the pipeline to fail. Therefore, running this model requires additional installation. I don’t know if this is appropriate. In addition, it depends on many modules of timm, which is difficult to remove.

Can you implement the individual timm modules inside vLLM? (where possible, you should use vLLM-specific layers to improve the performance anyway)

OK，I will try to do this and  I think it will take some time

This model depends on timm>=0.9.16, which depends on torch, but it will conflict with the dependencies of other third-party components and cause the pipeline to fail. Therefore, running this model requires additional installation. I don’t know if this is appropriate. In addition, it depends on many modules of timm, which is difficult to remove.

Can you implement the individual timm modules inside vLLM? (where possible, you should use vLLM-specific layers to improve the performance anyway)

OK，I will try to do this and I think it will take some time

You can make use of our implementation of CLIPVisionModel to save some effort.

To speed up the CI queue for #5905, I've cancelled the distributed tests for the latest CI run in this PR since they won't pass anyway until #5905 has been merged. Please merge main into your branch after that happens so that the CI can pass once again.

This test [tests/models/test_deepseek_vl.py] case depends on the project https://github.com/deepseek-ai/DeepSeek-VL, and it seems that pip installation will fail.I think it is possible not to add this test case
And The [examples/deepseek_vl_example.py]  can run successfully.

This test [tests/models/test_deepseek_vl.py] case depends on the project https://github.com/deepseek-ai/DeepSeek-VL, and it seems that pip installation will fail when build the docker .I think it is possible not to add this test case

In this case it won't function for users of vLLM either since they can't install it. Can you figure out which dependency is causing the issue?

This test [tests/models/test_deepseek_vl.py] case depends on the project https://github.com/deepseek-ai/DeepSeek-VL, and it seems that pip installation will fail when build the docker .I think it is possible not to add this test case

In this case it won't function for users of vLLM either since they can't install it (so you should still keep the tests). Can you figure out which dependency is causing the issue?
In the tests/models/test_deepseek_vl.py test, when hf runner loads the model, if we do not import deepseek_vl, an error will occur
(ValueError: The checkpoint you are trying to load has model type multi_modality but Transformers does not recognize this architecture. This could be because of an issue with the checkpoint, or because your version of Transformers is out of date.)
This is because the model part of the code is not in the hf repository, but in the github repository. In the code: https://github.com/deepseek-ai/DeepSeek-VL/blob/main/deepseek_vl/models/modeling_vlm.py, we can see some registration codes:
AutoConfig.register("multi_modality", MultiModalityConfig)
AutoModelForCausalLM.register(MultiModalityConfig, MultiModalityCausalLM)
If I add the dependency in vllm\requirements-test.txt:
deepseek_vl@git+https://github.com/deepseek-ai/DeepSeek-VL.git@main
Then, docker will report an error when building the image. The error is that metadata is None and cannot be recognized. The package can be packaged into whl, but it will not be found when it is installed.

You can manually registry the model to HuggingFace inside the test case.

You can manually register the model to HuggingFace inside the test case.

Ok, I'll try it

Heads up, since #6121 has been merged, you have to register the maximum number of image tokens (in your case it's probably 576) to MULTIMODAL_REGISTRY as well. (See LLaVA models for an example)
Also, you may wish to follow Phi-3-Vision's example and create a dummy CLIP config to contain variables such as the image size and number of image tokens.

Heads up: since #6121 has been merged, you have to register the maximum number of image tokens (in your case it's probably 576) to MULTIMODAL_REGISTRY as well. (See LLaVA models for an example)
Also, you may wish to follow Phi-3-Vision's example and create a dummy CLIP config to contain variables such as the image size and number of image tokens if you cannot extract them from DeepSeek-VL's config.

OK,

The Test models/test_deepseek_vl.py failed, but no exception stack was thrown. I don’t know what happened. The program seems to be terminated. Have you encountered similar problems?

The stack trace is shown near the end of the CI logs:
https://buildkite.com/vllm/ci-aws/builds/4404#0190956c-f526-40a4-b2af-232d40ffbd0c

buildkite/fastcheck/pr/tensorizer-metrics-tracing-test — Failed (exit status 1)
What functionality does this test case test?

It's unrelated to this PR.

Will this PR get merged?

Or rather where could I help, what is missing or needs work, only the models/test_deepseek_vl.py?

Or rather where could I help, what is missing or needs work, only the models/test_deepseek_vl.py?

Sorry for forgetting about this! I think we need to fix the merge conflicts and update the tests. Afterwards we can work on removing redundant code in the model file.

Sorry for forgetting about this!
No problem at all! I am sorry to prematurely have commented here, as Qwen2 VL architecturally fits my usecase way better.
Although I am having problems with the OpenAI endpoint, as Qwen2 VL is the only model that generates junk, I opened an issue for that https://github.com/vllm-project/vllm/issues/9732


Fix infinite loop when calling Control.popup_centered_minsize()

This salvages https://github.com/godotengine/godot/pull/60340. Thanks @sriramun for the original fix :slightly_smiling_face:
Bugsquad edit:

Fixes #60326
Fixes #60376

Seconding timothyqiu's comment, wouldn't it be better to have this be checked in the setter instead?

Seconding timothyqiu's comment, wouldn't it be better to have this be checked in the setter instead?

Seems like the original issue is not relevant for master, because the method was removed and I can't reproduce the issue with other methods (popups aren't even controls anymore).

Seconding timothyqiu's comment, wouldn't it be better to have this be checked in the setter instead?

That's what the current commit does. Which setter do you mean if not set_custom_minimum_size()?

Seems like the original issue is not relevant for master, because the method was removed and I can't reproduce the issue with other methods (popups aren't even controls anymore).

The 3.x bug report is the same bug as #60376 for 4.0, and this is still reproducible:
var b = Button.new()
add_child(b)
b.custom_minimum_size = Vector2(NAN, NAN)

crashes.

Thanks!

Cherry-picked for 3.6.

Cherry-picked for 3.5.2.


Change teaser image.

Docs Build status updates of commit 7dc0def:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/cvpr-2019.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/cvpr2019_teaser.jpg
:white_check_mark:Succeeded

mixed-reality-docs/images/cvpr2019_teaser2.jpg
:white_check_mark:Succeeded
View

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


Add more checks to the cpu collector

The CPU collector should at least the following stats:

frequency
SMT on/off
number of threads
physical vs virtual (perhaps in a new vm.rs collector group?)
cpu model
cpu version/revision
amount of cache (may belong in the memory section?)

consider nproc versus /proc/cpuinfo, for getting number of CPUs actually available to the process


Added my portfolio

Good work. I am merging your PR.
Do give us a star by hitting the star button of this repo!


Misc: Update Collated and Bump to v1.5 non ea.

Resolves #125

Coverage increased (+0.07%) to 92.729% when pulling 7bd97aea1c0dfbd0cc09449102ff8b93ce0b1a38 on nicholaschuayunzhi:clean-up into 70f30143e1c2546ed8bf128f0ca07b3c3d6b4348 on CS2103AUG2017-W11-B4:master.


Refactor Mine::pull

Refactor Mine::pull, using range-for, and shortening the code by using std::min.
Noticed this while working on #1014.

I think the changes make it easier to read. Also like the update to the variable naming conventions.


getSelectionType needs improvement for handling multiple types and selections

Issue Description:
The current getSelectionType function defaults most selections to extrude-wall and struggles to handle multiple selection types (e.g., edges, faces) accurately. This results in incorrect labels and counts in the command bar when different types are selected.
Expected Improvement:

Accurately distinguish between selection types (e.g., edges, faces, points).
Display correct labels and counts in the command bar for multiple selection types.

Unless this is blocking your work, I think this would be wasted cycles as https://github.com/KittyCAD/modeling-app/issues/3837 is going to stop it anyway, the selection type is going stored directly on the selections after the refactor.

since there is an upcoming update : https://github.com/KittyCAD/modeling-app/issues/3837 , I would take a shortest way just to enable multiple selections working for fillets. Just to move forward


Cannot use manager app

Your documentation mentions that you don't have any users defined in $CATALINA_HOME/conf/tomcat-users.xml.  That's fine for obvious security reasons.
I'm using vagrant to provision a centos box with docker and I want to run your tomcat image in a docker container and be able to access the manager app.  How do you recommend that I edit the container's $CATALINA_HOME/conf/tomcat-users.xml file to define a user -- in an automated way?
I very stupidly tried to use docker run --name=tomcat-container -d -p 8080:8080 -v /vagrant/.tomcat:/usr/local/tomcat tomcat:8-jre8 which blew away the entire /usr/local/tomcat directory (this is correct docker behavior - I'm just dumb).
What I was able to finally do was change the volume mapping like so: docker run -d -p 8080:8080 -v /vagrant/.tomcat:/var/tomcat-config tomcat:8-jre8 and then write a tomcat-users.xml file out to /vagrant/.tomcat and then docker exec tomcat-container cp /var/tomcat-config/tomcat-users.xml /usr/local/tomcat/conf followed by docker stop tomcat-container and docker start tomcat-container.
Is there a better way to accomplish this?

If possible, you could create your own image, using this as a base. When defining your own image, you can stage your own files, assuming they don't need to change. I happened to be putting together a tiny example of this, if it's helpful:
https://github.com/bryantrobbins/docker-tomcat-example
(If files do need to change every time the container is run, you could build this dynamic capability into a "starter script". There are some examples of this around, like this Dockerfile and script from the mongo container: https://github.com/docker-library/mongo/tree/master/3.1 . )

@jar349 You should be able to mount just that file with something like -v /path/to/tomcat-users.xml:/usr/local/tomcat/conf/tomcat-users.xml:ro

I extended the base image and added my own tomcat-users.xml to this end, and it works fine for the tomcat 8.0 base image:
FROM tomcat:8.0-jre8
ADD tomcat-users.xml $CATALINA_HOME/conf
But when I extend from the tomcat 8.5 base image I get a 403 Access Denied. Did this functionality change going from 8.0 to 8.5 ? I can't seem to find it in the migration docs.

The original issue seems to have been resolved, and a change in functionality in tomcat is outside the scope of the docker image itself. I'm closing this issue for now: if it comes back up, we can reopen.

The problem is that Tomcat doesn't list any change in functionality on that part that I can find and before I report a bug about it I would like to have some confirmation from other users that it is indeed a bug and not some oversight on my side. It's a pretty simple test to do so I thought I'd ask here, where people are (were) already looking into a similar issue.

@larsvanmourik Just experienced the same issue (403 Access Denied) with tomcat:8.5-alpine. The bug you mention was fixed in 8.5.1 but the 403 issue still appears with 8.5.4.
With tomcat:8.0-alpine it works...

Same here 403 error when trying to access to the manager. The bug is on Tomcat as I tried on a locally installed Tomcat 8.5.4 and same issue.

@NicoTexas Thank you, Can be solved

https://stackoverflow.com/questions/36703856/access-tomcat-manager-app-from-different-host

tomcat-users.xml
<tomcat-users>

  <role rolename="admin-gui"/>
  <user username="tomcat" password="s3cret" roles="manager-gui"/>

</tomcat-users>

Is there a problem with the difference between admin-gui in rolename and manager-gui in roles?


Some visual and first Prototype of statistics

Progressbar added for research and achievement
First prototype of statistics added

Branch has conflicts, can you please update your branch to the latest commit of the repo? Thanks!

Now it should work, sorry... Missed your latest commit... grrr..

No problem, thanks for hard work! :ok_hand:


Recipes do not run if composer.lock is present

I added "symfony/console": "^3.3" to the default composer.json, changed my bin location using: "config": {"bin-dir": "bin"} and then ran composer install.
Success, everything installed correctly in the expected places, the recipes ran and the console symlink was created for my custom bin directory.
I committed both composer files to an empty repository and tried the same composer install with Jenkins on an empty workspace.
It installed the vendor files as expected but as there is a composer.lock present the Symfony recipes are not executed and the console file symlink to my custom bin location is not generated.
This means composer install fails because bin/console is not accessible as it erroneously hasn't been created due to composer.lock existing??
[exec]   - Installing squizlabs/php_codesniffer (2.9.1): Loading from cache
[exec]   - Installing symfony/dotenv (v3.3.10): Loading from cache
[exec]   - Installing symfony/phpunit-bridge (v3.3.10): Loading from cache
[exec] Generating autoload files
[exec] Executing script make cache-warmup [OK]
[exec] Executing script assets:install --symlink --relative public [KO]
[exec]  [KO]
[exec] Script assets:install --symlink --relative %PUBLIC_DIR% returned with error code 1
[exec] !!  Could not open input file: bin/console

Is this expected behaviour?

Yes, recipes are only installed when using composer require, so updating your composer.json file will not trigger Flex because you'll have to run only composer install or composer update, which do not trigger Flex.

But surely the console file should be moved to the desired bin folder regardless of whether or not you're using composer require?

If you modify your composer.json file manually, Flex will run. But only if Composer decides that the dependency is new... which does not seem to be the case here. The bin/console file must be committed to your repository.


Add custom development header to CORS config

fix #372
Signed-off-by: thimmy687<EMAIL_ADDRESS>

It seems like GitHub won't fix the inconsistencies that were induced by the incident, so I'll close this manually. Please keep in mind that this PR was indeed merged: b637730a8c4b5c5b6f67db09650a1f745cecfc84


[Feature Request]: Write simple test cases for the DSPO upgrade gh workflow

Feature description
Currently workflow has placeholder tests, add simple validations for DSPO upgrades.
Describe alternatives you've considered
No response
Anything else?
No response

Implemented an SHA check on my fork, waiting for https://github.com/opendatahub-io/data-science-pipelines-operator/pull/384 to be merged, hence moving to the next sprint.


Do we need to keep updated?

Issue Description:
Hello there! We are also students who are working on building a recruiting platform for our studio currently and are excited to see this wonderful project.
Last month, we deployed the guiding-star project on our own server for recruitment and made modifications based on the original version in July 2023.
We would like to inquire about the upcoming development cycle and any related update requirements.
Details:
Development Cycle:
Could you please provide an estimate of how long the new development cycle is expected to last? Do you have a clear plan and timeline in place? If you ended your work, we shall keep updated on this.
Update Necessity:
In the previous deployment, we made modifications based on the original version. Are there any significant security fixes required after the new development cycle? Do we need to make any additional changes to our code to ensure system security?
Additional Information:
Based on the modifications we made to the previous version, we believe your previous version was already exceptional and outstanding. Thank you for your hard work and continuous working on this project.

Thanks for your interest in this platform!

Development Cycle

The main purpose of Guiding Star is to host PKU GeekGame CTF, which takes place in October~December annually. In each year we adjust this platform based on participant feedbacks and our new needs. Now adjustments from participant feedbacks are all finished (mostly user experience improvements), but there may be new adjustments according to the need of our CTF.

Update Necessity

Recent commits updated some third-party libraries (backend: sanic 21.12 → 22.12, sqlalchemy 1.4 → 2.0; frontend: react 17 → 18, antd 4 → 5, webpack 4 → 5). If you want to modernize your codebase, you can cherry pick these updates. There are no security-related changes.
Let me know if you have other questions :)

@MALossov
Also btw can you post an URL to your platform website / related advertising materials if it is public accessible? Maybe some time in the future I can use it to showcase the customizability of Guiding Star :)

@MALossov Also btw can you post an URL to your platform website / related advertising materials if it is public accessible? Maybe some time in the future I can use it to showcase the customizability of Guiding Star :)

Thanks a lot for your interest! If you need the URL, I can send it to your private mail (I can be found on MALOSSOV), the reason for keeping it out of the public domain for now is that our site is still in beta (although domains are allowed to access it), and it's not done well enough. Please be assured that the Guiding Star open source license and the original Project Guiding Star by PKUGGG Team text at the bottom of the page have been preserved.We also have great enthusiasm in being able to contribute upstream.
We just haven't made any major changes to Guiding Star, the only bit difference is: a new email verification portal has been added (mainly due to the fact that it was difficult to apply for OAuth at our school, and we didn't get the API or license), however, the encryption and decryption algorithms currently used as the backend checksum are not very reasonable (AES is currently used), and there is still some "works but not well enough" code. I'll be in touch if I need any help.
So after all the code optimizations are done and new updates are merged, I'll consider open-sourcing it as a showcase for some of the project's customizations.

@MALossov Also btw can you post an URL to your platform website / related advertising materials if it is public accessible? Maybe some time in the future I can use it to showcase the customizability of Guiding Star :)

Now it is 御林安全招新平台
We have made some preliminary changes and are currently using it as a recruitment platform.We are extremely excited and grateful to provide you with such a wonderful platform.


Have a planning workshop to go through all docs, create a plan for what needs to be consolidate, what needs new information, updated information, deleted information, etc.

This is an ongoing tasks and therefore will close for now.


Compatibility with Jest 28 and React 18

Hi,
I am not sure this library is compatible with the latest Jest (28) resp. React (18) releases. Could you please confirm/infirm? Is there any other alternative/option?
Thanks and regards,
christian

My problem with Jest 28 was hidden in this inconspicuous sentence in docs:
babel-jest now passes root: config.rootDir to Babel when resolving configuration. This improves compatibility when using projects with differing configuration, but it might mean your babel config isn't picked up in the same way anymore.
see https://jestjs.io/docs/next/upgrading-to-jest28#babel-config
So the solution was to add these lines into jest.config.js:
  transform: {
    '\\.[jt]sx?$': ['babel-jest', {rootMode: 'upward'}],
  },

I haven't found any documentation on rootMode: 'upward' - what it actually does. 🤦🏻♂

@mainfraame: so what would be the solution? (sorry to ask, not being an expert here...)


Should UseSendFileFallback IApplicationBuilder extension live in Microsoft.AspNet.Builder like all other extensions

https://github.com/aspnet/StaticFiles/blob/dev/src/Microsoft.AspNet.StaticFiles/SendFileExtensions.cs#L20
This probably is the only IApplicationBuilder extension in our code base living in a different namespace.

Yes, folks shouldn't have to add a using statement to use the extensions.
/cc @glennc

This was intentional. This is a piece of infrastructure that will rarely be used directly by app developers.
We've used this approach elsewhere too, its not unique.
Sent from my Windows Phone

From: Murat<EMAIL_ADDRESS>Sent: 3/12/2015 2:40 PM
To<EMAIL_ADDRESS>Subject: Re: [StaticFiles] Should UseSendFileFallback IApplicationBuilder extension live in Microsoft.AspNet.Builder like all other extensions (#43)
Yes, folks shouldn't have to add a using statement to use the extensions.
/cc @glennc

Reply to this email directly or view it on GitHub:
https://github.com/aspnet/StaticFiles/issues/43#issuecomment-78632514

@Tratcher sounds good.


Make the story selector responsive.

Feature Description
Currently if viewed in smaller view ports, the story selector screen ( in the stories gutenberg block ), is not specially usable. See screenshots. However the rest of the gutenberg editor is completely responsive. Our view should match the rest of gutenberg and be responsive.

Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

With #6790 it currently looks like this on iPad:


123 large lb

Applies to the v1.2.3 release. Content is already updated in the master branch. thanks

Thanks @lparis!


Plug-in does not open save dialogs on Sketch 65.1

The Plug-In does not open any save dialog box (technically nothing happens) when selecting Export Selected Artboards/Symbols (with either one or several artboards selected) in Sketch 65.1

If someone could identify the issue (I don't do sketch plug-ins) I could help solve it.


Unit calculation error

I paste the calculation txt here:
ρ = 1.6 kcal/cm^3
J = 1000 kcal/kg
ρ/J = 1.6 kcal/cm^3/1000 kcal/kg = 3.82×10-7 (4186800·t)/m3

Hi! Thank you for reporting this. Probably the result is internally correct, but Calcpad does not know how to compose and display the target units. If you add the target units at the end, say |kg/cm^3, it will convert accordingly:
ρ = 1.6kcal/cm^3
J = 1000kcal/kg
ρ/J|kg/cm^3 '= 0.0016 kg/cm3

We have taught Calcpad to properly compose target units for mechanical and electrical engineering. For other fields, we will need assistance by others. However, you can always force the desired target units by adding vertical bar "|".

Yes, it really looks strange, but this is because kcal is not a SI unit and it internally incudes this "strange" number:
1kcal|J will give: 1kcal = 4186.8 J
Calcpad, like other numerical packages, decomposes the units to vectors of factors and powers. Each element in the vector corresponds to one of the basic 7 physical dimensions. Then, it performs all the arithmetic operations on the vectors and finally composes back the resulting units. You can learn more about how units work in Calcpad from this blog post:
https://wordpress.com/post/calcpad.blog/99
If you use the SI units J, instead of kcal, you will see that the "strange" number disappears like magic, and the result looks right straight away:

Theoretically, it is possible to avoid this problem by using some kind of symbolic evaluation. However, Calcpad still do not have a symbolic engine. Also, symbolic calculations are much slower than numerical ones. So, specifying the target units explicitly in some cases may be needed and it is not a trouble.
And probably, you will also ask: Why does it keep this strange number in the units and does not let it go in the result.
The answer is to allow calculations in USCS or UK units without falling down to SI units on each formula, e.g.:

These units also include such internal factors. However, I will think about some workaround. Probably, I will be able to figure out something. So, thank you once again for your feedback. It is useful.

Yes, it really looks strange, but this is because kcal is not a SI unit and it internally incudes this "strange" number:
1kcal|J will give: 1kcal = 4186.8 J
Calcpad, like other numerical packages, decomposes the units to vectors of factors and powers. Each element in the vector corresponds to one of the basic 7 physical dimensions. Then, it performs all the arithmetic operations on the vectors and finally composes back the resulting units. You can learn more about how units work in Calcpad from this blog post:
https://calcpad.blog/2018/01/28/how-units-work/
If you use the SI units J, instead of kcal, you will see that the "strange" number disappears like magic, and the result looks right straight away:

Theoretically, it is possible to avoid this problem by using some kind of symbolic evaluation. However, Calcpad still do not have a symbolic engine. Also, symbolic calculations are much slower than numerical ones. So, specifying the target units explicitly in some cases may be needed and it is not a trouble.
And probably, you will also ask: Why does it keep this strange number in the units and does not let it go in the result. The answer is to allow calculations in USCS or UK units without falling down to SI units on each formula, e.g.:

These units also include such internal factors. However, I will think about some workaround. Probably, I will be able to figure out something. Until then, please use the manual conversion. Thank you once again for your feedback. It was useful.

Thanks for your concrete explanation.Now I understand the.reason behind the output. Maybe this could be improved by intrducing some algotithm, which preprocess all the unist.ahead before.it do the calculation, thus allowing to erase same unit at first.

Yes, but it will be more likely a kind of post-processing. It will be easier and faster. We will have to check if the residual factors are convertible to any letter-only prefixes like "kilo", "mega" or non-SI units like "lbf" or "kip" for mass or "ft", "in" for length, etc. If the factors do not match any of them, to reduce the respective factor to the nearest convertible and multiply the answer by the rest.
In your case, it will multiply 3.8210^-74186800 = 1.6 in t/m^3.
But I will do that a bit further because I have a lot of other work these days. Need to finish some urgent projects now.

Yes, but it will be more likely a kind of post-processing. It will be easier and faster. We will have to check if the residual factors are convertible to any letter-only prefixes like "kilo", "mega" or non-SI units like "lbf" or "kip" for mass or "ft", "in" for length, etc. If the factors do not match any of them, to reduce the respective factor to the nearest convertible and multiply the answer by the rest.
In your case, it will multiply 3.82_10^-7_4186800 = 1.6 in t/m^3.
But I will do that a bit further because I have a lot of other work these days. Need to finish some urgent projects now.

Thanks for your great job,Ned.

Hi!
I fixed it in version 5.9.9:
https://github.com/Proektsoftbg/Calcpad/releases/tag/v5.9.9
After calculations, units are normalized as discussed above. Any residual factors are transferred to the result and not vidiblr in the units anymore.


use commit range to avoid rewriting too much

I modified the date of the last 3 commits on my repo which have not been pushed yet.
Doing so end up rewriting the history of the last 212 commits. Those are 209 already pushed commits.
To avoid that, I add a commit range at the end of the command line :
git filter-branch --env-filter \
'if test "$GIT_COMMIT" = "c3bd0b5878f4f06c3f8482033750f83724ffc214"; then
    export GIT_AUTHOR_DATE="1593646151"
    export GIT_COMMITTER_DATE="1593646151"
elif test "$GIT_COMMIT" = "df3d1a15076dc8f8b1da1c87a0d005f80178ddd8"; then
    export GIT_AUTHOR_DATE="1593646121"
    export GIT_COMMITTER_DATE="1593646121"
elif test "$GIT_COMMIT" = "2629a79db5e33088c8cac021973fbad558b12977"; then
    export GIT_AUTHOR_DATE="1593642562"
    export GIT_COMMITTER_DATE="1593642562"
fi' 2629a79db5e33088c8cac021973fbad558b12977^..HEAD && rm -fr "$(git rev-parse --git-dir)/refs/original/"

note the extra 2629a79db5e33088c8cac021973fbad558b12977^..HEAD
I'm using the ^ suffix to point to the parent commit of 2629a79 which is the farest commit I want to modify.

That would be a great improvement, yeah
I may work on it if I have some free time soon

I found some free time
Now fixed ! 🎉

awesome ! I was preparing kind of the same !
thanks a lot !


Prepare for 2.1 release

Additional changes at https://github.com/amardeshbd/android-police-brutality-incidents/pull/131