avoid useless calls to listeners

Avoid useless calls to listeners when they've already been notified by the deepest dispatch call.
Dispatching an action from a listener while responding to a state change starts a recursive call to dispatch. This pauses the loop currently used to notify all listeners and starts a new one at a deeper nested level.
When resuming back to higher levels, all the listeners have already been notified and the paused loop doesn't actually need to be completed.
As an example, consider the following code:
var Redux = require('redux');

var numIncrementers = 3;
var numListeners = 5;

function reducer(state, action) {
  if (typeof state === 'undefined') {
    return 0
  }
  switch (action.type) {
    case 'INCREMENT':
      return state + 1
    default:
      return state
  }
}

var store = Redux.createStore(reducer)

function createListener(store, name, value) {
  var lastState = null;
  return function () {
    var state = store.getState();
    if (state === lastState) {
      console.log(name, 'state changed FALSE');
      return;
    }
    lastState = state;

    if (!!value && state === value) {
      console.log(name, 'state changed TRUE INCREMENT!');
      store.dispatch({ type: 'INCREMENT' });
    } else {
      console.log(name, 'state changed TRUE');
    }
  }
}

var i = 1;
for( ; i <= numIncrementers; i++)
  store.subscribe(createListener(store, 'listener_' + i, i));
for( ; i <= numListeners; i++)
  store.subscribe(createListener(store, 'listener_' + i))

// Trigger first action
store.dispatch({ type: 'INCREMENT' });

Here a number of listeners subscribe to the store and the first three of them trigger an increment action only in case the current value for the state is equal to their id.
The following is the log I get with the current code:
0 listener_1 state changed TRUE INCREMENT!
1 listener_1 state changed TRUE
1 listener_2 state changed TRUE INCREMENT!
2 listener_1 state changed TRUE
2 listener_2 state changed TRUE
2 listener_3 state changed TRUE INCREMENT!
3 listener_1 state changed TRUE
3 listener_2 state changed TRUE
3 listener_3 state changed TRUE
3 listener_4 state changed TRUE
3 listener_5 state changed TRUE
2 listener_4 state changed FALSE
2 listener_5 state changed FALSE
1 listener_3 state changed FALSE
1 listener_4 state changed FALSE
1 listener_5 state changed FALSE
0 listener_2 state changed FALSE
0 listener_3 state changed FALSE
0 listener_4 state changed FALSE
0 listener_5 state changed FALSE

(I've added by hand the recursion level on the leftmost column)
With the proposed modification, the output would be only the following one:
0 listener_1 state changed TRUE INCREMENT!
1 listener_1 state changed TRUE
1 listener_2 state changed TRUE INCREMENT!
2 listener_1 state changed TRUE
2 listener_2 state changed TRUE
2 listener_3 state changed TRUE INCREMENT!
3 listener_1 state changed TRUE
3 listener_2 state changed TRUE
3 listener_3 state changed TRUE
3 listener_4 state changed TRUE
3 listener_5 state changed TRUE

The idea is to prune the exploration of the recursive dispatch calls and stop notifying once the deepest notification loop completes. After this point in time each listener was already notified and it does not need to check the status on the same chain of actions.
Please let me know what do you think about this schema and do not hesitate to start a discussion on it.

Are there any edge cases this is breaking? In particular I’m concerned that we shouldn’t break this invariant:

The listener should not expect to see all state changes, as the state might have been updated multiple times during a nested dispatch() before the listener is called. It is, however, guaranteed that all subscribers registered before the dispatch() started will be called with the latest state by the time it exits.

I always find it hard to wrap my mind around this piece of code so maybe if you could add more test cases verifying the behavior we have in the docs, we can take this.

They only edge case I can think of, is a listener unsubscribing another listener.
Lets make an example.
A, B, and C subscribe to the store in this very same order.

An action is dispatched, the new state is generated by the reducer, and the notification loop starts.
A is called and it somehow unregisters C.
B is called and dispatch an action: the recursion starts! The new state is generated by the reducer, and the notification loop starts with the new snapshot of listeners (which no more includes C!).

3-a. A is called (...nothing to do)
3-b. B is called (...nothing to do)
3-c. the notification loop ends and needToNotify is set to false: the inner recursion is complete.

C is called (this is not happening because A unregistered C!)
the notification loop ends because needToNotify is true
the management of the action originally dispatched at point 1 is complete

My personal opinion is that this might be more of a feature than of an issue.
I think that if A needs to unsubscribe C, C should not respond the the action which made A unsubscribing C ...but this might change from case to case.  ;-)
What I'm seeing in some tests I'm doing is that with this modification I cas easily save up to 30% of the processing time
(FYI, I'm using Redux on the server-side to respond to high-frequency incoming data though and I appreciate it could be a very specific use case...)
Certainly the proposed changes break what stated in the quote you reported!
And since it's a breaking change, in case, it should be shipped with the next major release.
What do you think about the above example?

On the other hand, everything works correctly in case a subscriber unsubscribe itself...

...btw, adding a final call to a listener just before it gets unsubscribed (somewhere around here) would be enough to keep the current behaviour unchanged and still granting that

all subscribers registered before the dispatch() started will be called with the latest state by the time it exits.

Sure, want to give it a try?

Ok, this is how it would look like.
I managed to get all green checks for the tests (it seems tests are failing for other reasons at the moment...) although they're now a little less understandable in my opinion.
I think the documentation should also be updated to let people know about the one last call to listeners within unsubscribe (which could otherwise easily lead to infinite loops...).

There's probably another way to solve the same problem differently...
...I'll get back to this soon!

I'm :-1: on this. The listener can choose to ignore notifications if it wants (most likely by checking the ref. equality of the state). I'd rather have a guarantee of giving me all notifications, than have some sort of different behavior because of listeners added outside of my control.

I know the proposal is not perfect and I'm trying to improve it.
I think the real point here is that I'm trying to lower the computational complexity of this piece of code, not just saving a few function calls.

As promised with this previous comment I've made a new proposal: please see #1867.
I'm happy to discuss about it.

OK, let's keep this in one PR. #1867 it is.


Add prop that disables dragging of list items

A la issue #72

I'm not seeing the value in this prop -- why can't the list item component decide whether to call drag or not?

It's useful for instances where you need to toggle draggability for all props, e.g. for a list where you can only drag items when at least one is selected, or a similar reordering mode is activated.
You're right that this can be achieved on a per-component basis, but having a global switch makes the code cleaner for these situations where all components should be affected. This is just a small quality of life change.

Is there a solution to disable drag?

Is there a solution to disable drag?

See issue #72. Just don't call the drag function in the list items onLongPress handler.


Support hybrid search

During search, hybrid search, similar search and keyword search will be supported and submitted to LLM.
I am willing to submit this feature. Does the community have any better suggestions for my feature?

We are working on this feature now in an Agent model.  It allows for multiple retrievers and then post processing those results.  I hope to have it released in the 1.0 M1 next week, if not by a M2 release.  Either way when there is a branch or PR to share, I’ll post back here.

@markpollack Hi, I have implemented a hybrid search for PG that uses full-text retrieval and vector similarity. If the community needs me to implement it, I can submit it.

Hello everyone, I have also developed this feature that enables the user to define within the SearchRequest whether to use similarity search (vector-based, enabled by default), full-text search, or both (hybrid search). Additionally, it provides the possibility of using reranking approaches.
This implementation is applied to the vector store Azure SearchAI, and the implementation done by @impactCn can be seamlessly integrated as well.
The PR is #1227

Duplicate.


Re-write SimplePerturbation

[x] for sync test suite -> on MUCH smaller graph
[x] for performance tests -> refactor out into performance test suite

CLOSED -> corrected some errors & cut runtime from ~17 secs. to a 3-400 ms.


raylib: Init at 2.6.0

Motivation for this change
I like raylib and would like it to be more accessible (since that's kind of the point of raylib).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Also, please put everything you do in a single commit with message raylib: init at 2.6.0.

I didn't realise this PR existed when I created mine (#98029).
FYI, my PR uses the later 3.0.0 version and includes fixes to make audio work.

I didn't realise this PR existed when I created mine (#98029).
FYI, my PR uses the later 3.0.0 version and includes fixes to make audio work.

Thanks for that, @adamlwgriffiths

Thanks for that, @adamlwgriffiths


ServiceAccountCredentials should support directly passing in key file contents

(breaking out my comment from #401 as separate feature request)
Previously, SignedJwtAssertionCredentials allowed you to pass in the key file contents directly instead of passing in a file path (as shown here) It would be great if ServiceAccountCredentials also supported this, for both JSON and p12 keys.
In the meantime, this has prevented us from upgrading to v2.0.0, as our keys are pulled in dynamically at runtime and it's much easier for us to directly pass in the contents instead of having to first write to disk, pass in the path, and then do all the necessary cleanup.

That's what I need, it will be easier to upgrade to version 2.0.0 if SignedJwtAssertionCredentials is used before.

@allenpc I just peeked at the old source and it doesn't actually seem like a buffer was supported:
self.private_key = base64.b64encode(_to_bytes(private_key))

Any thoughts here?

@dhermes You are totally right, I was mistaken when I stated before that SignedJwtAssertionCredentials took in a buffer directly, looks like it just takes a string. For the purposes of easing every's migration to 2.0.0, I think we should keep the semantics consistent and just a string, as before.

No worries. Adding this functionality didn't take away from the existing.

@dhermes Can you paste an example of ServiceAccountCredentials that takes a string for pkey as input

import io
file_buffer = io.BytesIO(pkey_as_str)
creds = ServiceAccountCredentials.from_p12_keyfile_buffer(
    service_account_email, file_buffer)


Resolve merge conflicts

@jordan-rogers-ge, I pulled in upstream changes to resolve merge conflicts. Would you mind merging so the PR in the PowerShell repo can get updated?
Thanks!

@jordan-rogers-ge, have you had a chance to take a look?


Update the event handling "lesson" to talk about working with the actual event.

The new "learning" page for event handling over on https://react.dev/learn/responding-to-events doesn't show a single example of the event handler actually getting sent the event itself as argument, which is a bit weird when the whole point of event handling is that there's an event payload to handle, not just a signal to act on =)
There should at least be one example that has a simple input element and a button, and when you click the button, the alert says something like "you typed: <event.target.value>" so that people can be sent to that part of the learning docs when they ask questions about what they're doing wrong in their code and how to get form field values, something that is technically entirely unrelated to state and should not be held back until the state "lesson".
E.g.
export default function ValueButton() {
  function handleClick(event) {
    alert(`You wrote ${event.target.value}!`);
  }

  return (
    <>
      <input type="text" placeholder="Write something here..." />
      <button onClick={(event) => handleClick(event)}>
        Click me
      </button>
    </>
  );
}

(And on that note, it would be super useful if the examples would stop using ' and " as string syntax, and exclusively used backticks unless it's crititcal that legacy string delimiters are used, such as for object property names)

This is handled in the Reacting to Input with State guide.

In that case you'll want to address the discoverability, because that is not an obvious or intuitive place for that information, so only people who already know where it is will be able to find it.


Too many tools for a starter project

In the starter project we add a lot of tools and scripts:
  "scripts": {
    "start": "owc-dev-server --open src",
    "lint:eslint": "eslint --ext .js,.html .",
    "format:eslint": "eslint --ext .js,.html . --fix",
    "lint:prettier": "prettier \"**/*.js\" --list-different || (echo '↑↑ these files are not prettier formatted ↑↑' && exit 1)",
    "format:prettier": "prettier \"**/*.js\" --write",
    "lint": "npm run lint:eslint && npm run lint:prettier",
    "format": "npm run format:eslint && npm run format:prettier",
    "test": "karma start --coverage",
    "test:watch": "karma start --auto-watch=true --single-run=false",
    "test:update-snapshots": "karma start --update-snapshots",
    "test:prune-snapshots": "karma start --prune-snapshots",
    "test:legacy": "karma start --legacy --coverage",
    "test:legacy:watch": "karma start --legacy --auto-watch=true --single-run=false",
    "test:bs": "karma start karma.bs.config.js --legacy --coverage",
    "site:build": "npm run storybook:build",
    "storybook": "start-storybook -p 9001",
    "storybook:build": "build-storybook -o _site -s storybook-static",
    "start:dev": "webpack-dev-server --mode development --open",
    "start:dev:legacy": "webpack-dev-server --mode development --legacy",
    "start:prod": "http-server dist/ -o",
    "build": "webpack --mode production",
    "build:stats": "webpack --mode production --profile --json > bundle-stats.json"
  },

this seems like a lot, especially when we intend to promote a tool-free development setup.
I propose the following changes:
Apps and component init:

Remove prettier. In my opinion it doesn't add significant benefit and is not worth the extra overhead for the average developer. It also doesn't format template literals correctly, which is used a lot with web component.
Remove storybook. I think storybook is suitable for design systems and element collections. It has no use in apps and for single small/medium size component projects it seems quite overkill. We could add an extra init option for a design system which includes storybook.

Component init:

Remove rollup/webpack. Components should not be built/bundled.

Yeah, this wasn't the case before (see starter-app repo). Starter-app should already come without storybook, so something is off here.

would it be possible to change the amount of scripts based on choises in the genarator?
For Polymer I also used to add addtional scripts for my team.
An exaple would be 'npm run codereview'. This would trigger a complete reinstall of the dependencies.
"//clean": "removes the node_modules folder",
"clean": "FOR /d /r . %d in (node_modules) DO @IF EXIST \"%d\" rm -rf \"%d\"",

Let's revisit this

any idea how?

Some suggestions I made before:
Make prettier optional besides eslint.
Make commitlint optional, or maybe keep it out entirely.
Offer choice of simple vanilla demo besides storybook

Putting some of the configs in the package.json really helps with this too so thats a great move I think.

Commitlint does put some special pressure on a new dev...


live preview hides rest of code after image with link

I have a file similar to below and it loads the image, but hides the rest of the text afterward. It only shows the preview correctly if I remove the "img" tag or the "a" tag.

GRcalculator dockerfile
The dockerfile in this container... etc. etc.

It seems to work fine with version 3.0 :slightly_smiling_face: So I'm going to close this, please re-open if it doesn't work for you as well.

Oh wait, I just realized a quirk: you have to make sure you do that:

NOT

Because otherwise Beautiful soup converts it into this:

And sublime doesn't like that...


Add a sdk to Golang category

Thank you for your contribution.

@awcullen could you please drop me a line by mail? https://vdw.de/en/contact-persons-in-vdw/


workaround for dexcom error

Please see details here: https://trello.com/c/NZKjk2An/3-chrome-590307186-invalid-time-value-error-when-uploading-dexcom-receiver

 Chrome 59.0.3071.86 "Invalid Time Value" error when uploading Dexcom Receiver


LSQBivariateSpline segmentation fault when quitting the Python terminal

This is not really bugging me, but just would like to know if there is anything wrong with the code (I am on Ubuntu 18.04 if that helps).
Reproducing code example (test.py):
import numpy as np
from scipy.interpolate import LSQBivariateSpline

# generate data
x, y = np.meshgrid(
    np.linspace(0, 10, 30),
    np.linspace(0, 5, 40)
)
x = x.flatten()
y = y.flatten()
z = np.exp(-(x-5)**2/4) + np.exp(-(y-2)**2/3)

# define the knot positions
tx = [1, 2, 4, 5, 6, 8, 9]
ty = [0.2, 0.8, 1.1, 1.8, 2.5, 3, 3.7, 4.2, 4.9]

# get spline fit
s = LSQBivariateSpline(x, y, z, tx, ty, kx=3, ky=3)

# new evaluation
x2, y2 = np.meshgrid(
    np.linspace(0, 10, 50),
    np.linspace(0, 5, 60)
)
z_new = s(x2, y2, grid=False)

Error message:

Run code in terminal as python -i test.py, with the following error bumps out before quitting Python terminal:
python -i tmp.py
>>>
corrupted size vs. prev_size
Aborted (core dumped)

or
python tmp.py
Segmentation fault (core dumped)

This error message shows up randomly, roughly 1 out of 5 trials will trigger the error.
Scipy/Numpy/Python version information:
1.6.0 1.19.4 sys.version_info(major=3, minor=8, micro=0, releaselevel='final', serial=0)

I have been having memory errors with LSQBivariateSpline too.
A fairly reliable way to trigger this problem is to call the instantiation of LSQBivariateSpline multiple times in a script, possibly by just increase the coverage of the offending code. Whether python is called with interactive shell (-i) is immaterial.
I've set up a loop that repeatedly call the script, and beside simply Aborted or Segmentation Fault, occasionally I manage to get a Python traceback like this:
ValueError: 0-th dimension must be fixed to 1332 but got<PHONE_NUMBER>961601024

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "t.py", line 27, in <module>
    z_new = s(x2, y2, grid=False)
  File "[redacted]/lib/python3.8/site-packages/scipy/interpolate/fitpack2.py", line 939, in __call__
    z, ier = dfitpack.bispeu(tx, ty, c, kx, ky, x, y)
ValueError: failed in converting 3rd argument `c' of dfitpack.bispeu to C/Fortran array

I have been having memory errors with LSQBivariateSpline too.
A fairly reliable way to trigger this problem is to call the instantiation of LSQBivariateSpline multiple times in a script, possibly by just increase the coverage of the offending code. Whether python is called with interactive shell (-i) is immaterial.
I've set up a loop that repeatedly call the script, and beside simply Aborted or Segmentation Fault, occasionally I manage to get a Python traceback like this:
ValueError: 0-th dimension must be fixed to 1332 but got<PHONE_NUMBER>961601024

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "t.py", line 27, in <module>
    z_new = s(x2, y2, grid=False)
  File "[redacted]/lib/python3.8/site-packages/scipy/interpolate/fitpack2.py", line 939, in __call__
    z, ier = dfitpack.bispeu(tx, ty, c, kx, ky, x, y)
ValueError: failed in converting 3rd argument `c' of dfitpack.bispeu to C/Fortran array

@CongliWANG If you can build scipy, could you please test your script against a build with the patch #13394? I think what happened was that the array allocated for one of the knot-location arrays was too small and causing out-of-bound access. This could happen, for example, when the spline degrees along x and y are the same but the numbers of knots differ.

@CongliWANG If you can build scipy, could you please test your script against a build with the patch #13394? I think what happened was that the array allocated for one of the knot-location arrays was too small and causing out-of-bound access. This could happen, for example, when the spline degrees along x and y are the same but the numbers of knots differ.

Hi @congma ,
Thank you for the fix. I checked out #13394 and built scipy with python -m pip install .. Then:
$ python -c "import scipy; print(scipy.__version__)"
1.7.0.dev0+c28f721

But there is a missing library when I run the test script:
Traceback (most recent call last):
  File "test.py", line 2, in <module>
    from scipy.interpolate import LSQBivariateSpline
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/interpolate/__init__.py", line 165, in <module>
    from .interpolate import *
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/interpolate/interpolate.py", line 11, in <module>
    import scipy.special as spec
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/special/__init__.py", line 636, in <module>
    from . import _basic
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/special/_basic.py", line 15, in <module>
    from . import specfun
ImportError: /home/wangc0a/.local/lib/python3.8/site-packages/scipy/special/specfun.cpython-38-x86_64-linux-gnu.so: undefined symbol: npy_PyErr_ChainExceptionsCause

I believe the installation was not complete. May you advise on how to fix this? Thanks.

Hi @congma ,
Thank you for the fix. I checked out #13394 and built scipy with python -m pip install .. Then:
$ python -c "import scipy; print(scipy.__version__)"
1.7.0.dev0+c28f721

But there is a missing library when I run the test script:
Traceback (most recent call last):
  File "test.py", line 2, in <module>
    from scipy.interpolate import LSQBivariateSpline
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/interpolate/__init__.py", line 165, in <module>
    from .interpolate import *
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/interpolate/interpolate.py", line 11, in <module>
    import scipy.special as spec
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/special/__init__.py", line 636, in <module>
    from . import _basic
  File "/home/wangc0a/.local/lib/python3.8/site-packages/scipy/special/_basic.py", line 15, in <module>
    from . import specfun
ImportError: /home/wangc0a/.local/lib/python3.8/site-packages/scipy/special/specfun.cpython-38-x86_64-linux-gnu.so: undefined symbol: npy_PyErr_ChainExceptionsCause

I believe the installation was not complete. May you advise on how to fix this? Thanks.

@CongliWANG that's hard to say without a complete build log. Note that pip won't give you one unless you add the -v (for "verbose") flag. I usually use python setup.py develop or some such thing for an in-place build in a separate dev environment. There's documentation for different OSes at http://scipy.github.io/devdocs/dev/contributor/contributor_toc.html#development-environment
If you're doing it just to verify the fix: I can confirm that the segfaults are gone with gh-13394.

@CongliWANG that's hard to say without a complete build log. Note that pip won't give you one unless you add the -v (for "verbose") flag. I usually use python setup.py develop or some such thing for an in-place build in a separate dev environment. There's documentation for different OSes at http://scipy.github.io/devdocs/dev/contributor/contributor_toc.html#development-environment
If you're doing it just to verify the fix: I can confirm that the segfaults are gone with gh-13394.

Hi @rgommers  and @congma ,
Thank you for the message. I have built scipy from source and verified that the fix is working. Thank you again!

Hi @rgommers  and @congma ,
Thank you for the message. I have built scipy from source and verified that the fix is working. Thank you again!


Inherit Jekyll's rubocop config for consistency

This PR is the result of adding inherit_gem:\n jekyll: .rubocop.yml to .rubocop.yml and running rubocop -a so that this project follows Jekyll core's coding styles for consistency like other core plugins. This way, as Jekyll's Ruby style changes, so too will this project's.

@jekyllbot: merge +dev


Hello, excuse me for the interruption. Could you please explain the function of PROMPT_MAPPING mentioned in constants.py?

GRAPHIX_RELATIONS = ['question-question-dist-1', 'question-column-star', 'question-question-modifier', 'question-question-argument',
'question-table-exactmatch', 'question-column-partialmatch', 'question-column-valuematch', 'table-question-exactmatch', 'table-column-pk',
'table-column-has', 'table-table-fkr', 'column-question-partialmatch', 'column-table-pk', 'column-column-sametable', 'column-column-fkr',
'column-column-star', 'column-table-has', 'column-question-valuematch', 'table-table-fk', 'column-column-fk', 'column-question-star',
'question-column-exactmatch', 'column-question-exactmatch', 'question-table-partialmatch', 'table-question-partialmatch']

PROMPT_MAPPING = {
    'question-question-dist-1': 'This question word is the closet neighbor of another question word.',
    'question-column-star' : "This question word is connected with the special column item: '*'.",
    'question-question-modifier': 'The modifier of this question word is another word.',
    'question-question-argument': 'The argument of this question word is another word.',
    'question-table-exactmatch': 'This question word is matched exactly with the table item.',
    'question-column-partialmatch': 'This question word is matched partially with the column item.',
    'question-column-valuematch': 'This question word is matched with one of values in this column item.',
    'table-question-exactmatch': 'This table item is matched exactly with the question word.',
    'table-column-pk': 'This table item contains this column item as a primary key.',
    'table-column-has': 'This table item owns this column item as a normal relation.',
    'table-table-fkr': 'The other table item is linked with this table item by a foreign key.',
    'column-question-partialmatch': 'This column item is matched partially with the question word.',
    'column-table-pk': 'This column item is the unique primary key of the table item.',
    'column-column-sametable': 'This column item and the other column item appear in the same table.',
    'column-column-fkr': 'The other column item and this column item is linked as foreign key.',
    'column-column-star': "This column item is special column item: '*' or the other column item is the special column item: '*'.",
    'column-table-has': 'This column item belongs to the table item.',
    'column-question-valuematch': 'This column item contains the value that are matched with the question word.',
    'table-table-fk': 'This table item is linked with the other table item by a foreign key.',
    'column-column-fk': 'This column item and the other column item is linked as foreign key.',
    'column-question-star': "This speical column item: '*' links with the question word.",
    'question-column-exactmatch': 'This question word is matched exactly with the column item.',
    'column-question-exactmatch': 'This column item is matched exactly with the question word.',
    'question-table-partialmatch': 'This question word is matched partially with the table item.',
    'table-question-partialmatch': 'This table item is matched partially with the question word.'
}

I didn't see any calls, is this a technique you use to enhance performance?

@ChenLBs Thanks for your interest in our work and for asking insightful questions! We didn't actually use this file in our implementation. It represents an experimental approach we took to initialize the relation_embedding. In the original paper, the relation_embedding was initialized randomly, which already achieved the SOTA on both EM and EX at that time. However, a more refined method would be to convert these relations into natural language and use the T5 model's representations of these sentences as the initial embeddings.


feat: create this plugin (and add semantic-release to CI)

This plugin replaces the internal address-validation-test package that is currently in Reaction. It has not been tested by anyone aside myself yet, so although the changes in this particular PR only enable semantic release, please test the full functionality of the plugin before approving.
Once this PR is merged and this plugin is published to npm, there will be a related PR in reaction to swap out this plugin for the existing version.
Testing

see that the plugin is loaded upon startup in Reaction. This plugin is used with Radial and therefore won't be anything to test in our core app, aside from seeing it loads. You can use the systemInformation query to query and see which plugins are loaded.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(plugin-legacy): Add experimental option to use swc.

Description

DISCLAIMER: It's first time I'm using SWC, so a lot of things here are not final.

This PR is just the proof of concept for the further consideration of the swc  usage
I tried to make minimal changes, so it would be easier to check changes and compare files side by side
I've considered to make a separate plugin first, but there are a lot of things going on in original plugin, and the actual transformation part that has to be updated is small. (also original plugin is uses internal flag vite_skip_esbuild, which I assume can be changed or removed in future)

Additional context
Cons:

I didn't use official Visitor class from @swc/core/visitor, since it was breaking output code in weird ways, and I din't want to waste time on investigation
I couldn't make source maps work, looks like passing source maps generated from one swc transformation to another as inputSourceMap does not work
Overall I got a feeling that swc is good enough if you're using it's built in transformers and not messing with the plugin api.

no way to run plugins after main transformations (that's why I had to run transforms twice)
Visitor api is very limited (not to mention is buggy as I've pointed before) and better to be avoided (missing super call can break whole traverse chain)
no helpers to create ast objects, everything has to be created manually, and I had to put dummy spans everywhere

Pros:

Insanely fast on multiple cores
There are plans to add support for the babel plugins https://github.com/swc-project/swc/issues/1392

Maybe changing direction, and instead of transforming the final chunk it would be better to run swc in transformation  hook, and get rid of custom plugins. But it will require a lot of internal changes, and better to be extracted as an external plugin.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks for the PR @umidbekk, this is an interesting alternative! We'll discuss this with the team. My personal take is that we could first try to have this approach as a separate vite-plugin-legacy-swc plugin, and we may end up merging this upstream at one point. But let's wait to see what others think.

Hello @umidbekk, we discussed this proposal with the team and we think this approach is worth exploring. The only issue apart from polishing this solution is that for the moment we should keep both babel and swc (in case people want to keep using the babel based alternative due to maturity and stability), and introducing this dependency could be heavy for people not using it.
A good way forward is that you could offer a new vite-plugin-legacy-swc that is a fork of the official plugin respecting and following its API but based on swc. Once this plugin is mature enough, we can link to it from the official plugin-legacy docs and encourage people to use it. At one point in the future, we could directly made the switch in the official vitejs org plugin-legacy.
What do you think?

Hello @umidbekk, we discussed this proposal with the team and we think this approach is worth exploring. The only issue apart from polishing this solution is that for the moment we should keep both babel and swc (in case people want to keep using the babel based alternative due to maturity and stability), and introducing this dependency could be heavy for people not using it.
A good way forward is that you could offer a new vite-plugin-legacy-swc that is a fork of the official plugin respecting and following its API but based on swc. Once this plugin is mature enough, we can link to it from the official plugin-legacy docs and encourage people to use it. At one point in the future, we could directly made the switch in the official vitejs org plugin-legacy.
What do you think?

Hi @patak-js thank for the review!
I also hate the idea of installing optional packages (especially with giant binaries), and I agree that using separate package is the best way to approach.
One think that stops me now is vite_skip_esbuild flag. But I have an idea how to handle that - add use esbuild plugin that will transform *-legacy.* chunks itself, so esbuild would not modernize them by mistake.
But there another problem I see with plugin-legacy - it has two purposes:

Emit legacy bundle
Scan source and create polyfill bundle

Maybe using separate plugin to generate polyfill bundle was the better approach. But again, vite was made for the modern browsers, and maintenance of this plugin should not be a core team priority.
Also, I don't even use polyfill bundle myself, and use polyfill.io instead, I only thinking about it so vite-plugin-legacy-swc would be fully backward compatible with the @vitejs/plugin-legacy.
I guess it's better to start with the minimal working approach, and start adding things on demand.
I will close this, and start working on the esbuild plugin proposal for the plugin-legacy.

Also, I don't even use polyfill bundle myself, and use polyfill.io instead, I only thinking about it so vite-plugin-legacy-swc would be fully backward compatible with the @vitejs/plugin-legacy.
I guess it's better to start with the minimal working approach, and start adding things on demand.

Sounds good. Since it will be your plugin, I think you should design it as you see fit. The idea of keeping the API as close as possible was to enable an easy transition in the future if we go that road. But it would be a new mayor version and the API can be changed if there are good reasons.

I will close this, and start working on the esbuild plugin proposal for the plugin-legacy.

Thanks again and please share your work later on https://chat.vitejs.dev!

Should we somehow promote it especially on https://github.com/vitejs/awesome-vite?

Should we somehow promote it especially on vitejs/awesome-vite?

Let's wait to see how the plugin evolves and is being used, for sure it should be listed there. I think there isn't any concept of that in awesome-vite, to me a link from the readme of plugin-legacy is good here (and maybe a note in the production section of the docs).

As this PR is now closed, I have ported it with the latest plugin-legacy and released the package vite-plugin-legacy-swc. If anyone else has the same needs as me, feel free to try it out and make suggestions.


Python 3 Support

Hats off to @bambash for kicking this off!
This migration is intended to enable future deprecation of python 2.7 but also supporting python 3.6 & 3.7.
This PR:

Enables pytest being run on python 2.7, 3.6 and 3.7
Changes in python code to support both 2 and 3

This is just adding visibility to non-python3 changes going forward in the library. It will also fail if something is added that breaks python2, but the idea is that we should move away from that asap.

This looks super awesome.  I'm firing up a functional testing env for this right now.

Ok the last change fixes some issues with string comparisons in reckoner with python3. Stdout and Stderr from Popen().communicate() return as bytes in python 3 so comparing them to other strings loaded from yaml would have different behavior between versions.
We're having all calls return all stdout and stderr as string data now which should keep the behavior consistent.


google analytics verification file

@pyronicide let me know when this change is live on the external site, and we begin using Google Analytics.


[IDEA] Remove external annotator

Description:
We have added the external annotator to provide the semantic analyzing capabilities in the IDEA plugin. Now that we have added LS support in the plugin, we should get the errors from LS. So we should remove external annotator since it is redundant now.

Removed the external annotator add language server diagnostic support with #11110.


Support links as result menu items

Navigate to the link destination rather than committing the link text as the auto-completed value. This is useful for including actions at the end of the result list, like "learn more" or "create new item".

What if the anchors don't have href set?

That's a <button>!

But they should probably have href

Yeah, I think we should discourage anchors without an href target.


namespace custom unbound here

can't set attributes with custom: textToggleLeft
version us.belka:androidtoggleswitch:1.2.2

Check your parent layout to see whether the namespace for http://schemas.android.com/apk/res-auto  is present. By default you should have one  like
    xmlns:app="http://schemas.android.com/apk/res-auto"

if you do have it, then  change it to app:textToggleLeft instead of custom:textToggleLeft
if you dont have it, you can add the namespace to your parent layout:
xmlns:custom="http://schemas.android.com/apk/res-auto"


ci: GitHub Action - Error: Could not find satisfied version for SemVer '1.8'.

Summary
Looks like the bump to<EMAIL_ADDRESS>requires a more specific Java 8 version. https://github.com/googlemaps/android-maps-utils/pull/943/checks?check_run_id=3292933407 failed with:

Run<EMAIL_ADDRESS>with:
java-version: 1.8
distribution: adopt
java-package: jdk
architecture: x64
check-latest: false
server-id: github
server-username: GITHUB_ACTOR
server-password: GITHUB_TOKEN
overwrite-settings: true
Trying to resolve the latest version from remote
Error: Could not find satisfied version for SemVer '1.8'.


Composite key with Respository

Hi Rik,
Could you show me how to use a composite key with a respository ?

Hi Long
[Key]
[DatabaseGenerated(DatabaseGeneratedOption.Identity)]
Have a look at fastcrud:
https://github.com/MoonStorm/Dapper.FastCRUD/wiki/Entity-registration


Remove duplicate awesome-apple

Huh, not sure how it got there. Thanks Pietro! Just for curiosity, do you use the CSV data?

Well, I was just browsing around and I got on the CSV file first, then I discovered that the lists were also on the main page. I have no particular need for CSV data if you want to know that :)


cache selectStmt inside where exists (select...)

Closes #159
Based on   #164
Don't merge before #164

@cznic I have a question.
If I submit a PR and It has been reviewed, should I wait for someone else to merge the PR? And what about the case when I want to squash the commits before merging?

If the review is an approval you can merge. Then the reviewer is to blame ;-)

😄  lol! Fair enough!

And what about the case when I want to squash the commits before merging?

@gernest Forgot to answer this one, sorry. Please feel free to squash or not to squash on a per case basis and/or your personal preferences. Sometimes it's better to --squash, sometimes it's not, but you cannot make a really wrong decision either way.
(Eg. I'm used to making a lot of "noisy" commits on a dev branch, so a later --squash is often justified.)


[BUG] Typing error in README.md

Describe the bug
Hi Kaiwalya, there is a small typo error in the README.md file .The letter P from the work "Competitive Programming" is missing on line 32.
To Reproduce
Typo on line 32 in Readme file
Expected behavior
- [Competitive rogramming](https://github.com/kaiwalyakoparkar/Data-Structures-And-Algorithm-Interview-Kit/tree/main/Competitive_Programming)
+ [Competitive Programming](https://github.com/kaiwalyakoparkar/Data-Structures-And-Algorithm-Interview-Kit/tree/main/Competitive_Programming)
Screenshots

Additional context
Kindly add me to contribute in this repository and let me fix it.

Hey Kaiwalya! I opened an issue here so do check it out and assign me to fix the typo error.
@kaiwalyakoparkar

Thank You for the opportunity, I made a PR so do check it out.
Seeing forward in future to contribute into more as code form.
Regards
Harsh Kapoor
On Tue, Sep 27, 2022 at 12:33 PM Kaiwalya Koparkar @.***>
wrote:

Assigned #145
https://github.com/kaiwalyakoparkar/Data-Structures-And-Algorithm-Interview-Kit/issues/145
to @Harsh-Kapoorr https://github.com/Harsh-Kapoorr.
—
Reply to this email directly, view it on GitHub
https://github.com/kaiwalyakoparkar/Data-Structures-And-Algorithm-Interview-Kit/issues/145#event-7465406979,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A23GYUUNCBZAFZVJJO5HWDLWAKL5PANCNFSM6AAAAAAQWO6IR4
.
You are receiving this because you were assigned.Message ID:
<kaiwalyakoparkar/Data-Structures-And-Algorithm-Interview-Kit/issue/145/issue_event/7465406979
@github.com>


Is outlook addin supported in last versions of SPFX

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[X] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[X] mobile (iOS/iPadOS)
[X] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Issue description
SharePoint Framework v1.18.2

...or: when will Outlook add-in be supported in SPFX?

it was deprecated,  it won't be available


Unable to launch XPipe 1.7.8 on Windows (No cmd.exe access, No Administrator access, Yes PowerShell)

I'm trying to run xpipe on a Windows machine that doesn't have Administrator privileges nor access to cmd. I do have access to powershell though. I'm getting the error "The pipe is being closed".  Below is the log when running xpiped_debug.bat.
Is this resolvable or is my system too limited?
12:54:04:318 - trace: [proc] Writing line {
    line=echo -NoEnumerate "a"
}
12:54:04:379 - trace: [proc] Read: Microsoft Windows [Version 10.0.19045.3570]
12:54:04:380 - trace: [proc] Read: (c) Microsoft Corporation. All rights reserved.
12:54:04:381 - trace: [proc] Read:
12:54:04:383 - trace: [proc] Read: The command prompt has been disabled by your administrator.
12:54:04:384 - trace: [proc] Read:
12:54:04:385 - trace: [proc] Read: Press any key to continue . . .
12:54:14:386 - trace: [proc] Read:  (no LF)
12:54:14:386 - trace: [proc] Writing line {
    line=echo "Checking whether we are in fish"
}
12:54:14:388 - trace: [proc] Killing local shell ...
12:54:14:406 - error: java.io.IOException: The pipe is being closed
java.io.IOException: The pipe is being closed
        at java.io.FileOutputStream.writeBytes(Native Method)
        at java.io.FileOutputStream.write(FileOutputStream.java:367)
        at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:125)
        at java.io.BufferedOutputStream.implFlush(BufferedOutputStream.java:252)
        at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:240)
        at io.xpipe.ext.proc.g.writeLine(SourceFile:37)
        at io.xpipe.ext.proc.util.c.a(SourceFile:137)
        at io.xpipe.ext.proc.d.start(SourceFile:247)
        at io.xpipe.core.store.LocalStore.init(LocalStore.java:23)
        at io.xpipe.app.core.mode.BaseMode.onSwitchTo(BaseMode.java:49)
        at io.xpipe.app.core.mode.OperationMode.set(OperationMode.java:273)
        at io.xpipe.app.core.mode.OperationMode.switchTo(OperationMode.java:142)
        at io.xpipe.app.launcher.LauncherCommand.call(LauncherCommand.java:123)
        at io.xpipe.app.launcher.LauncherCommand.call(LauncherCommand.java:24)
        at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
        at picocli.CommandLine.access$1500(CommandLine.java:148)
        at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
        at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
        at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
        at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
        at picocli.CommandLine.execute(CommandLine.java:2170)
        at io.xpipe.app.launcher.LauncherCommand.runLauncher(LauncherCommand.java:64)
        at io.xpipe.app.core.mode.OperationMode.init(OperationMode.java:114)
        at io.xpipe.app.Main.main(Main.java:15)

12:54:22:117 - info: Loading stylesheets ...

That is a case I have not considered yet when cmd is blocked. Administrator privileges are not needed, but cmd is required in order to function right now.
I could evaluate whether it would be possible to run on only powershell though but that would take some time.
Out of curiosity, what is the reason for the cmd block? Is this something you can find more often in organizations than I anticipated?

My client is a government department that runs a fleet of Azure Virtual Desktops. They're used by technical and non-technical users so they don't want users being able to install software or run commands. I manage a number of applications on their servers so they granted me access to Powershell in order to run ssh commands.
I came across your app on reddit the other other, thought it looked useful for providing a list of my ssh connections in a modern way. Got this error when using the portable Windows app.

Alright, so is PowerShell usage also limited then to only certain commands in your case?
Having access to some shell is required by XPipe to run commands like ssh but also to launch terminals and editors, and more.

I don't believe it's been limited in other ways, but I won't know until I try.
I'm able to run "notepad" and Notepad opens. I'm also able to run "start powershell" and it launches a new Powershell terminal.

That is good news at least, so I should be able to work with that.
I will try to experiment how I can make the cmd dependency optional.

So good news, I experimented with it and I'm confident that this is possible to implement.
This will just take some time, I will let you know when it's ready.

XPipe 8 should now support falling back to powershell exclusively in case cmd does not work

That's awesome! Thanks for your help.

Did you test whether it actually works for you? Because it should work, but I didn't test it in an environment like yours.

I just tried it. I initially got a few Null Pointer Exceptions but after clicking Ignore a few times, the app opened and I was able to browse and SSH to my servers. :grinning:

Thanks for the heads up, the null pointers will be fixed in the next release.


Incorrect url request to load chunk in production when used with minifier

Bug report
Describe the bug
Incorrect url request to load chunk in production when used with minifier
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Build next.js in production mode with a minifier https://github.com/webpack-contrib/babel-minify-webpack-plugin or https://github.com/webpack-contrib/uglifyjs-webpack-plugin
So the config will look something like this

    if (!dev) {
      config.optimization = {
        minimizer: [
          new UglifyJsPlugin({
            uglifyOptions: {
              comments: false,
            },
            sourceMap: true
          })
        ]
      }
    }

Use one component which is dynamically imported in your home page. Make sure it is rendered to the DOM.
Run the project in production next start
You will see that the url is to load a lot of the chunks is wrong. This issue only happens with chunks. runtimes load perfectly fine with the right url. Also this error seems to occur occationally after a few refreshes in the console.

Note Not all chunks have this issue. As can be seen in the screenshots.
Expected behavior
The url should instead have _next/static/chunks/*
Screenshots

System information

MacOS
Chrome
7.0.0-canary

Additional context
This issue does not occur if I don't use a minifier.
Github repository
https://github.com/imbhargav5/next-dynamic-bug
I made two branches. master and without-bug. I deployed them both to now.sh.
With bug https://next-canary-dynamic-bug-efeynywjqu.now.sh/
Without bug https://next-canary-dynamic-no-bug-gjkyepzkdj.now.sh/

This is not really a reproduction. Your steps to reproduce don't mention setting up dynamic imports. Can you provide a minimal github repository.

@timneutkens True. I updated the issue.

I don't see anything different from before 🤔 Can you provide a minimal GitHub repository?

Hmm weird this morning it wasn't showing up for me 😭Thanks! I'll have a look.

Can you direct me how to fix this? I can send a PR.

@imbhargav5  You can try adding plugins instead of rewriting
const { minimizer = [] } = config.optimization;

minimizer.push(new UglifyJsPlugin({
  uglifyOptions: {
    comments: false,
  },
  sourceMap: true,
}));

Just tried your reproduction and installing yarn add next@latest fixes the issue.


Migrating the migration guides to the new docs site

Could you please document the path to upgrade from v5 to v6 as you did in the old docs pages ?
Thanks :)

Good point! @malchata, just want to get this on your radar.
The following links all still work in the meantime:

https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-v5
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-v4
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-v3
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-v2
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw

Thanks a lot :)

I think we should have a separate ToC for migration guides, @jeffposnick, something that lives at a URL like developer.chrome.com/docs/workbox/migration. You think that might work?

Absolutely. That sounds 👍
(And no rush, since the old pages are still hosted and discoverable. I know that there are other priorities, but I wanted to keep this open so that we don't lose track.)

Migration guides have been migrated to developer.chrome.com: https://developer.chrome.com/docs/workbox/migration/


Fix EventDispatcher Error While dispatching event

Fix #1364

Codecov Report
Base: 40.68% // Head: 18.16% // Decreases project coverage by -22.53% :warning:

Coverage data is based on head (48e8308) compared to base (4e2bba3).
Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head 48e8308 differs from pull request most recent head 1f266a8. Consider uploading reports for the commit 1f266a8 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1373       +/-   ##
===========================================
- Coverage   40.68%   18.16%   -22.53%
===========================================
  Files         350      350
  Lines       17720    17719        -1
  Branches     2588     2588
===========================================
- Hits         7210     3219     -3991
- Misses       9874    14244     +4370
+ Partials      636      256      -380

Impacted Files
Coverage Δ

packages/core/src/base/EventDispatcher.ts
78.75% <100.00%> (-2.74%)
:arrow_down:

packages/math/src/SphericalHarmonics3.ts
6.81% <0.00%> (-90.91%)
:arrow_down:

packages/core/src/material/BlinnPhongMaterial.ts
3.63% <0.00%> (-87.28%)
:arrow_down:

packages/math/src/Matrix3x3.ts
7.04% <0.00%> (-86.17%)
:arrow_down:

packages/core/src/VirtualCamera.ts
14.28% <0.00%> (-85.72%)
:arrow_down:

packages/core/src/material/PBRMaterial.ts
11.76% <0.00%> (-82.36%)
:arrow_down:

packages/math/src/BoundingBox.ts
10.38% <0.00%> (-81.82%)
:arrow_down:

packages/core/src/material/UnlitMaterial.ts
8.33% <0.00%> (-79.17%)
:arrow_down:

packages/core/src/material/PBRSpecularMaterial.ts
10.52% <0.00%> (-78.95%)
:arrow_down:

packages/core/src/shadow/ShadowSliceData.ts
25.00% <0.00%> (-75.00%)
:arrow_down:

... and 99 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Feature Request: Add option to choose register for clipboard action

Happy to help with a PR

Thanks for the PR! Just wanted to know a bit more about what use case this addresses for you. Is it simply to paste from another register, or is it part of a hacky solution?

It is simply to paste to a separate register. I like to keep the unnamed and system registers separate.


feature: Add a new string validate rule for json format

This pr commit new feature which extend the validation rule for string field to validate json.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.joshuozhang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Advanced View for items in BC SaaS return wrong value

Describe the bug
Advanced View for items - does not return selected value if you have added extension to page.
To Reproduce

Add an extension to the page "Item Lookup" with 1 additional field
Go to Sales Order
Add New Line of type Item
Lookup Number, and go to Process - Advanced View
Select an item, and notice it does not use the selected item from the Advanced View

Like this
pageextension 70148 ItemLookupMG extends "Item lookup"
{
    layout
    {
        addafter(Description)
        {
            field(VendorItemNoMG; "Vendor Item No.")
            {
                ApplicationArea = all;
                Editable = true;
            }
        }
    }
}

Expected behavior
That it adds the selected item to the order.
I can´t reproduce in BC 14.0 On Premise, but I can´t see any mention of this bug if I search
Screenshots
Versions:

AL Langauge: 3.0.102444

Business Central:  DK Dynamics NAV 13.4 (29469)

Let's get the issue to a team who will backport it, as this repo is only for issues related to the latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company


[Bug]: Query client fails when using a vector store

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
Bash client fails when running a local search query using a vector store.
Steps to reproduce

Define a vector store in your settings.yaml.

embeddings:
  <other-params>
      ...
  vector_store:
      type: lancedb
      overwrite: true
      db_uri: /path/to/vector/db

Run a local query using the bash client.

python -m graphrag.query \
    --config <path/to/settings>/settings.yaml \
    --data <path/to/index/dir>/storage \
    --community_level 2 \
    --method local "Local Query"

Expected Behavior
Expect to see a ValueError notifying you that there is no vector column in the data. See image in the Logs and screenshots section for full stack trace.
GraphRAG Config Used
# Define anchors to be reused
openai_api_key_smt_octo: &openai_api_key_smt_octo ${OPENAI_API_KEY_SMT_OCTO}

#######################
# pipeline parameters #
#######################

# data inputs
input:
  type: file
  file_type: text
  file_pattern: .*\.txt$
  base_dir: <path/to/base/dir>/data-01p

# tokenizer model name
encoding_model: &encoding_name o200k_base # gpt-4o
# encoding_model: &encoding_name cl100k_base # gpt-4-turbo

# text chunking
chunks:
  size: &chunk_size 700 # 700 tokens (about 2800 characters)
  overlap: &chunk_overlap 100 # 100 tokens (about 400 characters)
  strategy:
      type: tokens
      chunk_size: *chunk_size
      chunk_overlap: *chunk_overlap
      encoding_name: *encoding_name

# chat llm inputs
llm: &chat_llm
  api_key: *openai_api_key_smt_octo
  type: openai_chat
  model: gpt-4o-mini
  max_tokens: 4096
  request_timeout: 180 # 3 minutes should make sure we can handle busy AOAI instances
  api_version: "2024-02-01"
  # deployment_name: gpt-4o-mini
  model_supports_json: true
  tokens_per_minute: 1000000
  requests_per_minute: 10000
  max_retries: 20
  max_retry_wait: 10
  sleep_on_rate_limit_recommendation: true
  concurrent_requests: 50

parallelization: &parallelization
  stagger: 0.25
  num_threads: 100

async_mode: &async_mode asyncio
# async_mode: &async_mode threaded

entity_extraction:
  llm: *chat_llm
  parallelization: *parallelization
  async_mode: *async_mode
  prompt: <path/to/base/dir>/prompts/entity_extraction.txt
  max_gleanings: 1

summarize_descriptions:
  llm: *chat_llm
  parallelization: *parallelization
  async_mode: *async_mode
  prompt: <path/to/base/dir>/prompts/summarize_descriptions.txt
  max_length: 500

community_reports:
  llm: *chat_llm
  parallelization: *parallelization
  async_mode: *async_mode
  prompt: <path/to/base/dir>/prompts/community_report.txt
  max_length: &max_report_length 2000
  max_input_length: 8000

# embeddings llm inputs
embeddings:
  llm:
    api_key: *openai_api_key_smt_octo
    type: openai_embedding
    model: text-embedding-ada-002
    request_timeout: 180 # 3 minutes should make sure we can handle busy AOAI instances
    api_version: "2024-02-01"
    # deployment_name: text-embedding-ada-002
    model_supports_json: false
    tokens_per_minute: 10000000
    requests_per_minute: 10000
    max_retries: 20
    max_retry_wait: 10
    sleep_on_rate_limit_recommendation: true
    concurrent_requests: 50
  parallelization: *parallelization
  async_mode: *async_mode
  batch_size: 16
  batch_max_tokens: 8191
  vector_store:
      type: lancedb
      overwrite: true
      db_uri: <path/to/base/dir>/index/storage/lancedb
      query_collection_name: entity_description_embeddings

cache:
  type: file
  base_dir: <path/to/base/dir>/index/cache

storage:
  type: file
  base_dir: <path/to/base/dir>/index/storage

reporting:
  type: file
  base_dir: <path/to/base/dir>/index/reporting

snapshots:
  graphml: true
  raw_entities: true
  top_level_nodes: true

#####################################
# orchestration (query) definitions #
#####################################
local_search:
  text_unit_prop: 0.5
  community_prop: 0.1
  conversation_history_max_turns: 5
  top_k_entities: 10
  top_k_relationships: 10
  temperature: 0.0
  top_p: 1.0
  n: 1
  max_tokens: 12000
  llm_max_tokens: 2000

global_search:
  temperature: 0.0
  top_p: 1.0
  n: 1
  max_tokens: 12000
  data_max_tokens: 12000
  map_max_tokens: 1000
  reduce_max_tokens: 2000
  concurrency: 50

Logs and screenshots

Additional Information

GraphRAG Version: 0.2.0
Operating System: 22.04.1-Ubuntu
Python Version: 3.11.9
Related Issues:

The expected behavior ought to be the behavior if the bug did not exist.
The ValueError is the actual behavior, i.e. what actually and erroneously happens, correct?

I have the same issue after  #771  is merged

same issue, do you solve it?

same issue, do you solve it?


Add a sort of progress indicator

As stated, there is currently no real indication of the overall progress which makes it hard to guess an eta.

With the implementation of Dask Runners #53 , this might be resolved because the dashboard actually has an indicator for completed/ open nodes.


[WIP][SQL] Support SimpleDateFormat and FastDateFormat as legacy date/timestamp formatters

What changes were proposed in this pull request?
TODO
Why are the changes needed?
TODO
Does this PR introduce any user-facing change?
TODO
How was this patch tested?
TODO

Test build #118172 has started for PR 27524 at commit 38d90d8.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22933/
Test PASSed.

Test build #118175 has started for PR 27524 at commit ab1d57f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22936/
Test PASSed.

Test build #118172 has finished for PR 27524 at commit 38d90d8.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait LegacyTimestampFormatter extends TimestampFormatter
class LegacyFastDateFormatter(
class LegacySimpleDateFormatter(

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118172/
Test PASSed.

Test build #118175 has finished for PR 27524 at commit ab1d57f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait LegacyDateFormatter extends DateFormatter
class LegacyFastDateFormatter(pattern: String, locale: Locale) extends LegacyDateFormatter
class LegacySimpleDateFormatter(pattern: String, locale: Locale) extends LegacyDateFormatter
class LegacyFastTimestampFormatter(
class LegacySimpleTimestampFormatter(

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118175/
Test FAILed.

Test build #118185 has started for PR 27524 at commit 566170a.

@cloud-fan @HyukjinKwon Please, look at the draft PR.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22947/
Test PASSed.

Approach seems okay.

Test build #118185 has finished for PR 27524 at commit 566170a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118185/
Test PASSed.

Test build #118213 has started for PR 27524 at commit ddf127d.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22973/
Test PASSed.

Test build #118213 has finished for PR 27524 at commit ddf127d.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118213/
Test FAILed.

Test build #118215 has started for PR 27524 at commit 93f3ae1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22975/
Test PASSed.

Test build #118215 has finished for PR 27524 at commit 93f3ae1.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118215/
Test FAILed.

jenkins, retest this, please

Test build #118219 has started for PR 27524 at commit 93f3ae1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22979/
Test PASSed.

Test build #118219 has finished for PR 27524 at commit 93f3ae1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118219/
Test FAILed.

jenkins, retest this, please

Test build #118232 has started for PR 27524 at commit 93f3ae1.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/22992/
Test PASSed.

Test build #118232 has finished for PR 27524 at commit 93f3ae1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118232/
Test PASSed.

thanks, merging to master/3.0!


New package: SuiteSparse_GPU_jll v5.8.1+0

Autogenerated JLL package registration

Registering JLL package SuiteSparse_GPU_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/SuiteSparse_GPU_jll.jl
Version: v5.8.1+0

[noblock]
Is this good to merge? @staticfloat @giordano @vchuravy @maleadt

Yeah, we haven't quitte figured out run-time dependencies on the CUDA stack, so this is good to go for now. The JLL will be usable if you have CUDA installed system-wide.

Done.
It would be nice if eventually you could do import SuiteSparse_GPU_jll on a non-GPU machine. Is that something that might be possible one day in the future?


🐛自定义ColCell后列名会被格式化

🏷 Version

Package
Version

@antv/s2
-   1.3.0 ～

@antv/s2-react
-

🖋 Description
设置自定义colcell后，列名的文本会按照meta中设置的formatter进行格式化。

⌨ Code Snapshots

🔗 Reproduce Link
https://riddle.alibaba-inc.com/riddles/c8bbcaab
🤔 Steps to Reproduce

😊 Expected Behavior
😅 Current Behavior
💻 System information

刚试了下, 明细表和透视表都有这个问题

ref: https://github.com/antvis/S2/pull/845

:tada: This issue has been resolved in version @antv/s2-v1.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.11.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.11.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.12.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.11.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.14.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.13.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.13.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.12.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.14.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.13.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.15.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.16.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.15.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.15.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.16.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.15.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.17.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.15.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.18.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.16.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.18.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.16.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.16.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.19.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-vue-v1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.20.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-vue-v1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.21.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.21.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.19.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.22.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-vue-v1.1.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.22.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.20.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.23.0-alpha.4 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.21.0-alpha.3 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.24.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.22.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v1.24.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.22.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


puller(ticdc): fix frontier metrics label

What problem does this PR solve?

Issue Number: close #8027
What is changed and how it works?
not use span size to check if the puller is a ddl puller, use a bool passed by caller
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/run-all-tests

/merge

/run-integration-tests
/run-verify-test

/run-verify-tests

/run-verify
/run-integration-test


abc

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.453%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
38

Relevant Lines:
41

💛  - Coveralls


Generic/Extensible API for adding variables to the python console

What is the feature you'd like to have?
I want to add my own magic variables to the python console from plugins (eg the Debugger).
Is your feature request related to a problem?
I want more extensibility of the python console (and also really want the giant update_locals block in scriptingprovider.py to Go Away)
Are any alternative solutions acceptable?
The only way of doing this right now is via a nasty hack poking values into the locals of a python interpreter, which I have directed several of our users to do. It's not very clean and probably would break in many situations.

This has been added as of >= 4.1.5430-dev


Clean up configuration a bit

Travis tests have failed
Hey @silasary,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.


Chat should be automatically renamed if the conversation is started from the beginning after clearing all messages

Chat should be automatically renamed if the conversation is started from the beginning after clearing all messages. Mainly this issue is inconvenient in overlay functionality, as there is no way to rename the chat.

Create a chat and send the first message -> the chat is named automatically, where the 1st message = the name
In chat header click on "Clear all messages" button; confirm -> messages from the chat are removed (ok); chat settings appears (ok); chat name stays the same -> issue1?
Send new first message -> chat name is not changed -> issue2

Expected result: After "Clear all messages" action, the chat should be renamed automatically to the new first message if previous name was also named automatically. Please do nothing if the chat was renamed manually.
To be discussed what is the best approach: should we rename the chat to New conversation on the 2nd step or only on the 3rd step
Note: If all the messages were deleted one by one, expected result is the same

The fix was verified on staging environment successfully.
Now the behaviour is the following:

Create a chat and send a message -> chat is named to the 1st message
Clear all the messages on the button in chat header or deleting user-messages one by one -> all the messages are deleted, chat is named as it was in the 1st step
Send new message -> chat is renamed to this new message automatically -> ok! fixed!

Note: if the chat was renamed manually, it is not renamed automatically on the 3rd step


Query on how to delete the files

Your macbook model and year:
MacBook Air M3
Your version number: (run "battery version" to find out)
v2.0.13
Your battery status: (run "battery status" to find out)
12/06/24-01:06:04 - Battery at 94.8%, 12.758V, 31.3°C, no charging
12/06/24-01:06:04 - Battery health 87.6%, Cycle 51
12/06/24-01:06:04 - Your battery is currently being maintained at 80% with sailing to 75%
12/06/24-01:06:04 - You haven't scheduled calibration yet
What is the issue?

It does a good job overall except that when I am trying to discharge while charging, the battery display on the status bar does not change. I am trying to delete it using  battery uninstall, the status of the battery is recovered but I found that the battery command still works in the terminal. Could you help me on how to wipe it out from my disk?

Why the battery status is different from what should in the settings:

Error logs: (run "battery logs" to find out)
12/06/24-00:59:44 - 🔼🪫 Disabling battery discharging
12/06/24-00:59:45 - 🔌🔋 Enabling battery charging
12/06/24-00:59:47 - 🔼🪫 Disabling battery discharging

The capacity Apple shows is 2~7 percent higher than real one. Mine is same with another famous app called coconutBattery.
I have some doubts about your first question.

The status shows "no charging", why did you say you were trying to discharge while charging? What commands did you use to result in the condition
According to the logs, the status changes from disable discharging/ enable charging/ disable discharging within 3 seconds. Again, what commands did you use to make it happen?
All files are supposed to be completely removed when you run "battery uninstall". Could you check if /usr/local/bin/battery still exist? If it's already gone, try to open another terminal and run the command and see what happens.

Hi,
Thanks very much, my problem is solved.
Awaiting your new updates!


Enable running Google.Cloud.Diagnostics.AspNetCore integration tests in parallel.

This was a restriction put in place when the tests were not as robust but is no longer needed.

LGTM if the tests go green after rebasing to fix the AppVeyor issues.


Use iid when setting up harmonized github PR object in getPr

I've returned with the latest and greatest tweak for gitlab v4 support!
This tweak is essentially the same as https://github.com/singapore/renovate/pull/295.
We're ensuring that when we pass the pr object to other libraries we won't get errors on v4. (Ensure PR was throwing some errors in certain edge case scenarios)

Codecov Report

Merging #332 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #332   +/-   ##
=======================================
  Coverage   76.43%   76.43%
=======================================
  Files          22       22
  Lines        1494     1494
  Branches      257      258    +1
=======================================
  Hits         1142     1142
  Misses        352      352

Impacted Files
Coverage Δ

lib/api/gitlab.js
5.76% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

:+1: Awesome!


fix SAM issue 1137

DC power loss due to snow (%) output changed from fraction to percentage and tests updated

https://github.com/NREL/SAM/issues/1137


Feature/external tool model documenter v2

Added command line program to export the power bi model as an vpax file.
The exported vpax file i used in the power bi document model report.
All this can be started using the power bi external program feature.

Major update to the Power BI Model documenter!
New version released with an entirely rebuild backend! Shout out to @tonswart for his help in rebuilding!
New in Model Documenter v2.0.0 is:

Easy next-next-finish installer to put the files in the right location on the computer.
New and enhanced backend of the tool, which is not relying on DMVs nor PowerShell anymore.
Ground-up rebuild model documentation Power BI Template file, to present all information in a report.
Live connected Analysis Services models are read by the Model Documenter.
(Live connected datasets or Premium XMLA endpoints not yet)
No longer pop-up windows to allow native query execution.
No more failing loads due to privacy levels (though, ignoring privacy levels improves Model Documenter run time).
Deprecation of the Excel model documenter report. Going forward, only Power BI report will be supported.

Major update to the Power BI Model documenter!
New version released with an entirely rebuild backend! Shout out to @tonswart for his help in rebuilding!
New in Model Documenter v2.0.0 is:

Easy next-next-finish installer to put the files in the right location on the computer.
New and enhanced backend of the tool, which is not relying on DMVs nor PowerShell anymore.
Ground-up rebuild model documentation Power BI Template file, to present all information in a report.
Live connected Analysis Services models are read by the Model Documenter.
(Live connected datasets or Premium XMLA endpoints not yet)
No longer pop-up windows to allow native query execution.
No more failing loads due to privacy levels (though, ignoring privacy levels improves Model Documenter run time).
Deprecation of the Excel model documenter report. Going forward, only Power BI report will be supported.


new descendents of cell migration

New descendents of cell migration
Proposed new appearance of the process DAG, as detailed
below:
cell migration ;  GO:0016477
---% immune cell migration ;  GO:NewTerm
------% cellular extravasation ;  GO:0045123
---------< leukocyte tethering/rolling ;  GO:NewTerm
---------< leukocyte adhesive activation ;  GO:NewTerm
---------< leukocyte activation-dependent arrest ;
GO:NewTerm
---------< diapedesis ;  GO:NewTerm
------% diapedesis ;  GO:NewTerm
immune cell activation ;  GO:0045321
---% leukocyte adhesive activation ;  GO:NewTerm
leukocyte cell adhesion ;  GO:0007159
---% leukocyte tethering/rolling ;  GO:NewTerm
---% leukocyte activation -dependent arrest ;  GO:NewTerm
1)  New Term:  immune cell migration
Definition:  The movement of immune cells/leukocytes
within or between different tissues and organs of the body.
Synonym:  leukocyte trafficking
Parentage:  is-a to GO:0016477 cell migration
Reference:  PMID:7507411, PMID:8600538, PMID:14680625,
PMID:14708592 ISBN:072735149
2)  Term movement and rewording of definition:
GO:0045123 cellular extravasation
Current definition: The migration of immune cells, for
example leukocytes, from the blood vessels into the
surrounding tissue as a response to injury or disease.
Current parentage:  is-a to GO:0016477 cell migration
Proposed new definition:  The migration of immune cells/
leukocytes, from the blood into the surrounding tissue.
Proposed new parentage:  is-a to "immune cell migration"
proposed above.
There are two changes here.  First of all, as far I am
concerned, immune cells and leukocytes are the same
things, and can be used interchangeably in the GO.
Secondly, cellular extravasation occurs both in response to
injury and disease and during normal immune surveillance
of the body.  Thus, the definition should encompass both
possibilities.
Reference:  PMID:7507411, PMID:8600538, PMID:14680625,
PMID:14708592 ISBN:072735149
New Term:  leukocyte tethering/rolling
Definition:  Transient adhesive interactions between
leukocytes and endothelial cells lining blood vessels
mediated primarily by selectins and which are typically the
first step in cellular extravasation.
Parentage:  part-of to GO:0045123 cellular extravasation, is-
a to GO:0007159, leukocyte cell adhesion
Reference:  PMID:7507411, PMID:8600538, PMID:14680625,
PMID:14708592 ISBN:072735149
New Term:  leukocyte adhesive activation
Definition:  The activation of loosely bound or rolling
leukocytes by signals displayed on blood vessel endothelial
cells, which is typically the second step in cellular
extravasation.
Synonym: leukocyte adhesive triggering
Parentage:  part-of to GO:0045123 cellular extravasation, is-
a to GO:0045321 immune cell activation
Reference:  PMID:7507411, PMID:8600538, PMID:14680625,
PMID:14708592 ISBN:072735149
New Term:  leukocyte activation-dependent arrest
Definition:  The formation of an integrin-dependent strong
adhesive bond between leukocytes and blood vessel
endothelial cells which is dependent on prior activation of
the leukocyte and leads to the firm attachment of the
leukocyte to the endothelial surface, typically the third step
in cellular extravasation.
Parentage:  part-of to GO:0045123 cellular extravasation, is-
a to GO:0007159, leukocyte cell adhesion
Reference:  PMID:7507411, PMID:8600538, PMID:14680625,
PMID:14708592 ISBN:072735149
New Term:  diapedesis
Definition:  The passage of leukocytes between the tight
junctions of endothelial cells lining blood vessels, typically
the fourth and final step of cellular extravasation.
Comment:  Note that the term diapedesis, although
sometimes used as a direct synonym for cellular
extravasation, is used here for the specific final step of the
process, in concordance with recent reviews of the topic.
Parentage:  part-of to GO:0045123 cellular extravasation, is-
a to "immune cell migration" (for logical completeness of
the GO)
Reference:  PMID:7507411, PMID:8600538, PMID:14680625,
PMID:14708592 ISBN:072735149
Reported by: addiehl
Original Ticket: "geneontology/ontology-requests/1480":https://sourceforge.net/p/geneontology/ontology-requests/1480

thanks www.movied.org


Multiple values in web forms

What's vibe.d's stand on multiple values in web forms? There seems no standard across web frameworks (wikipedia query string).
The place to add is parseURLEncodedForm I'll guess.

On the HTTP layer this is already supported using FormFields.getAll or using opApply. The web framework (vibe.web.web) currently doesn't support it, because it still requires a decision on how to annotate parameters accordingly (e.g. using a UDA or a special type, or maybe even using auto-detection at runtime).

getAll is fine in my case. Thanks. Sorry for the noise.


Used TestPurposes in DisPro12

Closes #294

We have already decided not to use SUT for these cases in #289
But it's not possible to use TestPurposes without SUTs.
@pjljvandelaar should these changes be merged or ditched?

I had made these changes in the past in a local branch and applied them now, but now that we have #289 I don't know if these changes should be merged. Waiting for @pjljvandelaar to comment on this.

Discussed with @pjljvandelaar. Not only we don't want SUTs but we don't want Test Purposes for these cases, either.


chore: restore merchant payments feature

Description
Restores the Merchant Payment feature removed in #3190.
Test plan
WIP
Related issues

Fixes RET-564

Backwards compatibility
Yes

Associated PR to update dependencies in @celo-org/payments.

@Kathy @Jean there appears to be an issue with the initial start of the app and getting the DEK which is needed for the merchant payment features. On a fresh install after a restore when attempting to scan the QR code from https://sandbox-celo-demo-store.demo.firstdag.com. The DEK is undefined when hitting if (!wallet.isAccountUnlocked(account) || !wallet.isAccountUnlocked(dekAddress)) in src/merchantPayment/hooks.ts; however, if I close and reopen the app the DEK is present and merchant payments is working as expected.

@jeanregisser and @kathaypacific just want to test this a bit more, but I think this is ready for review.


rtx global --install-missing has unintuitive behavior

Describe the bug
My expectation from reading #188 and the PR for #263 is that rtx global --install-missing would install any missing tools that are defined in ~/.tool-versions or $XDG_CONFIG/rtx/config.toml
However, that is not the case as shown below.
If I set RTX_MISSING_RUNTIME_BEHAVIOR=autoinstall, then the rtx shell hook immediately kicks off an install, which is expected. But also not the explicit behavior I thought --install-missing was supposed to provide.
To Reproduce
[WARN] Tools not installed<EMAIL_ADDRESS><EMAIL_ADDRESS>
[~] (master *)
$ rtx global --install-missing
[tools]
python = [ '3.10', '3.11' ]
[~] (master *)
$ rtx global python --install-missing
3.10 3.11
[~] (master *)
$ rtx global<EMAIL_ADDRESS>--install-missing
rtx python https://github.com/jdxcode/rtx-python.git#5853786
Downloading Python-3.10.10.tar.xz...
-> https://www.python.org/ftp/python/3.10.10/Python-3.10.10.tar.xz
Installing Python-3.10.10...

Maybe I'm "holding it wrong" ? I also realize that last command is explicitly installing the version of Python, so --install-missing would really have no effect anyways.
rtx doctor output
$ rtx doctor
rtx version:
  1.23.5 linux-x64 (built 2023-03-13)

shell:
  /usr/bin/fish
  fish, version 3.6.0

rtx environment variables:
  RTX_SHELL=fish
  RTX_USE_TOML=1
  RTX_EXPERIMENTAL=1

settings:
  {"experimental": "true", "missing_runtime_behavior": "prompt", "always_keep_download": "false", "legacy_version_file": "true", "plugin_autoupdate_last_check_duration": "10080", "verbose": "false", "asdf_compat": "false", "jobs": "4", "disable_default_shorthands": "false", "log_level": "INFO", "raw": "false"}

config files:
  /home/dsully/.config/rtx/config.toml

plugins:
  python   https://github.com/jdxcode/rtx-python.git#5853786

toolset:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
No problems found

for now as a workaround you can use rtx i --install-missing && rtx global to get the behavior you're looking for